Content for TR 23.708 Word version: 13.0.0
5 Key Issues p. 7
5.1 Key Issue 1 - Service Capability Exposure Framework p. 7
5.2 Key Issue 2 - Setting up an AS session with required QoS p. 7
5.3 Key Issue 3 - Change the chargeable party at the session set-up or during the session p. 7
5.4 Key Issue 4 - Support of 3rd party interaction on information for predictable communication patterns p. 8
5.5 Key Issue 5 - Informing the 3rd party about a UE's connection properties p. 8
5.6 Key Issue 6 - Informing the 3rd party about potential network issues p. 9
5.7 Key Issue 7 - 3GPP resource management for background data transfer p. 9
5.7.1 Description p. 9
5.7.2 Required functionality p. 10
6 Solutions p. 10
6.1 Solution 1: AESE Architecture p. 10
6.1.1 Description p. 10
6.1.1.1 General p. 10
6.1.1.2 Architectural Diagram p. 10
6.1.1.3 Service Capability Exposure Function p. 11
6.1.1.4 Example: SMS Service Capability Exposure p. 12
6.1.2 Impacts on existing nodes and functionality p. 12
6.1.3 Solution Evaluation p. 12
6.2 Solution 2: Rel-12 MTC architecture with API-GWF p. 12
6.2.1 Description p. 12
6.2.2 Impacts on existing nodes and functionality p. 13
6.2.3 Solution Evaluation p. 13
6.3 Solution 3: Setting up an AS session with required QoS p. 13
6.3.1 Description p. 13
6.3.2 Impacts on existing nodes and functionality p. 14
6.3.3 Solution Evaluation p. 15
6.4 Solution 4: Change the chargeable party at the session set-up or during the session p. 15
6.4.1 Description p. 15
6.4.1.1 Set the chargeable party at the session set-up p. 15
6.4.1.2 Change the chargeable party during the session p. 16
6.4.2 Impacts on existing nodes and functionality p. 17
6.4.3 Solution Evaluation p. 17
6.5 Solution 5: 3GPP resource optimizations based on providing predictable communication patterns of a UE or a group of UEs to the MME p. 17
6.5.1 Description p. 17
6.5.1.1 Communication pattern examples p. 17
6.5.1.2 Architectural assumptions p. 17
6.5.1.3 Provisioning of CP parameters p. 18
6.5.1.4 Provisioning of CP parameters for enable Core Network assisted eNodeB parameters impact p. 18
6.5.2 Impacts on existing nodes and functionality p. 19
6.5.3 Solution Evaluation p. 19
6.6 Solution 6: Inform the 3rd party about a UE's connection properties p. 19
6.6.1 Description p. 19
6.6.1.1 Inform the 3rd party about a UE's connection properties when PCRF is available p. 20
6.6.1.2 Inform the 3rd party about a UE's connection properties when PCRF is absent (variant A) p. 21
6.6.1.3 Inform the 3rd party about a UE's connection properties when PCRF is absent (variant B) p. 22
6.6.2 Impacts on existing nodes and functionality p. 22
6.6.3 Solution Evaluation p. 23
6.7 Solution 7: Informing the 3rd party about potential network issues p. 24
6.7.1 Description p. 24
6.7.1.1 Request procedure for continuous reporting on network status changes p. 24
6.7.1.2 Report procedure for continuous reporting on network status changes p. 25
6.7.1.3 Procedure for one-time reporting of network status p. 26
6.7.2 Impacts on existing nodes and functionality p. 26
6.7.3 Solution Evaluation p. 26
6.8 Solution 8: 3GPP resource management for background data transfer p. 27
7 Overall Evaluation p. 29
8 Conclusions p. 29
8.1 Final Conclusions p. 29
$ Change History p. 31
