tech-invite   World Map
3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TR 23.708 (SA2)
Architecture enhancements for
Service Capability Exposure

|   ToC   |   3GPP‑Page  |   Help   |

(W-zip) V13.0.0    2015/06    31 p.


Rapporteur:  Mr. Jain, Puneet
See also:  –


The present document studies and evaluates architecture enhancements for a service capability exposure framework wherein 3GPP system provided service capabilities are exposed via one or more standardized APIs, e.g. the OMA-API(s). As part of this work it will be identified how the APIs and the 3GPP system functionality act together to expose 3GPP service capabilities. The definition of APIs is out of scope of this work item.

The present document will also define the architectural enhancements for new service capabilities and services (based on the Stage 1 normative requirements) that are exposed via the service capability exposure framework.


 

Here        Top

 

1 Scope    2 References    3 Definitions and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Architectural Considerations    5 Key Issues    5.1 Key Issue 1 - Service Capability Exposure Framework    5.2 Key Issue 2 - Setting up an AS session with required QoS    5.3 Key Issue 3 - Change the chargeable party at the session set-up or during the session    5.4 Key Issue 4 - Support of 3rd party interaction on information for predictable communication patterns    5.5 Key Issue 5 - Informing the 3rd party about a UE's connection properties    5.6 Key Issue 6 - Informing the 3rd party about potential network issues    5.7 Key Issue 7 - 3GPP resource management for background data transfer    6 Solutions    6.1 Solution 1: AESE Architecture    6.2 Solution 2: Rel-12 MTC architecture with API-GWF    6.3 Solution 3: Setting up an AS session with required QoS    6.4 Solution 4: Change the chargeable party at the session set-up or during the session    6.5 Solution 5: 3GPP resource optimizations based on providing predictable communication patterns of a UE or a group of UEs to the MME    6.6 Solution 6: Inform the 3rd party about a UE's connection properties    6.7 Solution 7: Informing the 3rd party about potential network issues    6.8 Solution 8: 3GPP resource management for background data transfer    7 Overall Evaluation    8 Conclusions    8.1 Final Conclusions    A Change history   

 

1   Scope   Word-p. 6
2   References
3   Definitions and abbreviations
4   Architectural Considerations
5   Key Issues   Word-p. 7
6   Solutions
6.1   Solution 1: AESE Architecture
6.2   Solution 2: Rel-12 MTC architecture with API-GWF
6.3   Solution 3: Setting up an AS session with required QoS
6.4   Solution 4: Change the chargeable party at the session set-up or during the session
6.5   Solution 5: 3GPP resource optimizations based on providing predictable communication patterns of a UE or a group of UEs to the MME
6.6   Solution 6: Inform the 3rd party about a UE's connection properties
6.7   Solution 7: Informing the 3rd party about potential network issues   Word-p. 24
6.8   Solution 8: 3GPP resource management for background data transfer   Word-p. 27
7   Overall Evaluation      Up
8   Conclusions
A   Change history   Word-p. 31

Up        Top