Content for TR 23.721 Word version: 14.0.0
5 Key Issues p. 7
5.1 Key Issue 1 - Provisioning of Packet Flow description. p. 7
5.1.1 Description p. 7
5.2 Key Issue 2 - Managing sponsored data connectivity information inside the operator's network p. 8
5.2.1 Description p. 8
5.3 Key Issue 3 - Encrypted traffic detection p. 8
5.3.1 Description p. 8
5.4 Key Issue 4 - TDF based sponsored data connectivity p. 8
5.4.1 Description p. 8
6 Solutions p. 9
6.1 Solution #1: Standalone SDCF based solution -Key Issue 2 p. 9
6.1.1 Solution Description p. 9
6.1.2 Impacts on existing nodes and functionality p. 14
6.2 Solution #2 - Provisioning of Packet Flow description outside the IP-CAN session context -Key Issue 1 p. 15
6.2.1 Solution Description p. 15
6.2.1.1 Flow Diagram p. 16
6.2.2 Impacts on existing nodes and functionality p. 17
6.2.3 Solution evaluation p. 18
6.3 Solution #3: Provisioning sponsored data connectivity information via SCEF -Key Issue 1 p. 18
6.3.1 Solution Description p. 18
6.3.2 Impacts on existing nodes and functionality p. 19
6.3.3 Solution evaluation p. 19
6.4 Solution #4: SCEF and PCRF Provisioning of Packet Flow Descriptions -Key Issue 1 p. 19
6.4.1 Solution Description p. 19
6.4.1.1 Nt and Spt/Ud Procedures p. 20
6.4.1.1.1 Nt: Create Sponsored Service Profile p. 20
6.4.1.1.2 Nt: Update Sponsored Service Profile p. 20
6.4.1.1.3 Nt: Delete Sponsored Service Profile p. 21
6.4.1.1.4 Spt/Ud: Sponsor/Un-sponsor Subscriber p. 21
6.4.1.2 Using Rx to Trigger Predefined PCC/ADC Rule Activation p. 21
6.4.1.3 Sponsored Service Profile Parameters p. 21
6.4.1.4 Predefined PCC/ADC Rule Derivation from Sponsored Service Profile p. 22
6.4.2 Impacts on existing nodes and functionality p. 22
6.4.3 Solution evaluation p. 22
6.5 Solution #5: PCRF Management of Packet Flow Descriptions - Key Issue 2 p. 22
6.5.1 Solution Description p. 22
6.5.1.1 Predefined PCC/ADC Rule Management Procedures p. 23
6.5.1.1.1 Create Predefined PCC/ADC Rule p. 23
6.5.1.1.2 Update Predefined PCC/ADC Rule p. 24
6.5.1.1.3 Delete Predefined PCC/ADC Rule p. 24
6.5.1.2 PCRF Selection and Coordination p. 24
6.5.1.3 Predefined PCC/ADC Rule Parameters p. 25
6.5.2 Impacts on existing nodes and functionality p. 25
6.5.3 Solution evaluation p. 25
6.6 Solution #6: Usage of a sponsoring context Identifier -Key Issue 2 p. 26
6.6.1 Solution Description p. 26
6.6.1.1 Background for the solution p. 26
6.6.1.2 Overview of the solution p. 26
6.6.1.3 Signalling flows p. 27
6.6.2 Impacts on existing nodes and functionality p. 32
6.6.3 Solution evaluation p. 32
6.7 Solution #7: Unified rule storage for request of sponsored data related information -Key Issue 2 p. 33
6.7.1 Solution Description p. 33
6.7.1.1 Request of sponsored data related information - Sponsored service for all users p. 33
6.7.1.1a Request of sponsored data related information - Sponsored service for some users p. 35
6.7.1.2 Local SDC storage of frequently used Sponsored data related rule p. 36
6.7.2 Impacts on existing nodes and functionality p. 37
6.7.3 Solution evaluation p. 37
6.8 Solution #8: New reference point for management of PFDs to PCEF/TDF - Key Issue2 p. 38
6.8.1 Solution Description p. 38
6.8.1.1 General Description and assumptions p. 38
6.8.1.2 New functional entity: PFDF and new reference points Gw/Gwn p. 38
6.8.1.3 Information flows to provision/update/remove PFDs p. 39
6.8.2 Impacts on existing nodes and functionality p. 40
6.8.3 Solution evaluation p. 40
6.9 Solution #9: Traffic detection by using domain name matching - Key Issue 3 p. 40
6.9.1 Solution Description p. 40
6.9.1.1 Assumptions p. 40
6.9.1.2 Proposed framework p. 41
6.9.2 Impacts on existing nodes and functionality p. 41
6.9.3 Solution evaluation p. 41
6.10 Solution #10: TDF based sponsored data connectivity - Key Issue 4 p. 42
7 Overall evaluation p. 42
8 Conclusions p. 42
$ Change History p. 44
