3gpp tr ab cde
Enhancement to Flexible Mobile Service Steering
Yüklə 0,91 Mb.
|
- Bu səhifədəki naviqasiya:
- Sponsored data connectivity improvements
Enhancement to Flexible Mobile Service SteeringSummary based on the input to be provided by China Mobile at SA#78.
This Work Item enhances the feature developed in the previous Rel-13 Work Item on FMSS for supporting third party owned (S)Gi-LAN service. Stage 1 is covered by the Rel-14 Study Item FS_eFMSS. Based on the study and its conclusions, SA1 has completed the Work Item eFMSS with CRs to update TS 22.101, TS 22.115 for the normative work. The scope is to define the following major requirements: • The 3GPP core network shall be able to apply traffic steering policies for the third party owned (S)Gi-LAN service functions. • The 3GPP core network shall be able to generate accounting information to support accounting between operator and the third party service provider. Stage 2 is covered by the Rel-14 Work Item eFMSS which made changes into TS 23.203 to provide architecture enhancements to introduce eFMSS feature in the stage 2 specifications based on the stage 1 requirements defined in TS 22.011 and TS 22.115: • Ensure that traffic steering is supported via operator owned as well as third party provided (S)Gi-LAN service functions • Specify how the 3GPP core network is able to collect accounting information to distinguish the traffic steering to third party service enablers.
[1] 3GPP TR 22.808, Study on Flexible Mobile Service Steering (FMSS) [2] 3GPP TS 22.101, Service aspects; Service principles [3] 3GPP TS 22.115, Service aspects; Charging and billing [4] 3GPP TS 23.203, Policy and charging control architecture
Summary based on the input provided by China Unicom in SP-170523.
The Work Item "Sponsored data connectivity improvements" (SDCI) is an improvement of the Rel-10 Feature "Policy Enhancements for Sponsored Connectivity and Coherent Access to Policy related Databases" (PEST). "Sponsored Connectivity" relates to the context where the connectivity cost is not paid by the end user but by a third party, the Sponsor, so it is seen as "free" by the end user. The Sponsor has a business relationship with the operator: he reimburses the operator for the user's data connectivity in order to allow the user access to an associated Application Service Provider's (ASP) services. SDCI aims at solving the problem of heavy load occurred when too many sponsored data related rules are transmitted via the Rx interface (between the AF and the PCRF) and/or the Gx interface (between the PCRF and the PCEF/TDF), as shown in the figure below. SDCI introduces one new entity, the PFDF (Packet Flow Description Function) and three new interfaces: Gw, Gwn, Nu. The PFDF is used to store and manage the PFDs (Packet Flow Descriptions) and charging rules for sponsored data services. The new interfaces link the PFDF to existing entities, as shown in the figure below. They enable the PFDs and the corresponding charging rules to be provisioned dynamically to the PCEF and/or the TDF by PULL mode, PUSH mode, or a combined mode. The PFDs and charging rules for sponsored services can be stored in PCEF and/or PFDF according to implementation. The following figure shows the SDCI entity and its related interfaces.
Stage-3 fully defines these interfaces and their related protocol, namely HTTP Restful protocol, where all the functionalities are realized via GET/PUT/POST/DELETE operations. Stage 3 work is covered by CRs on TS 29.212, TS 29.213 and TS 29.214 on by two new specs, TS 29.250 and TS 29.251, which specify how to realize the SDCI functionalities using HTTP RESTful.
|
