Content for TR 23.708 Word version: 13.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Architectural Considerations
...
...
1 Scope p. 6
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.
2 References p. 6
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.368: "Service Requirements for Machine-Type Communications".
[3]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[4]
OMA API Inventory: "http://technical.openmobilealliance.org/API/APIsInventory.aspx".
[5]
TS 22.101: "Service Aspects; Service Principles".
[6]
TS 22.115: "Service aspects; Charging and billing".
[7]
TS 23.203: "Policy and charging control architecture".
[8]
TR 23.789: "Monitoring Enhancements".
[9]
TR 23.769: "Group based Enhancements".
3 Definitions and abbreviations p. 6
3.1 Definitions p. 6
For the purposes of the present document, the terms and definitions given in TR 21.905, TS 22.368 apply.
3.2 Abbreviations p. 6
4 Architectural Considerations p. 6
The current 3GPP system allows for exposure of some of the 3GPP service capabilities to external 3rd party Application providers via the OSA framework as defined in 23.198. There is a need to further enhance the 3GPP network architecture to allow operators to interact with 3rd party service providers in exposing a greater set of 3GPP service capabilities as requested by 3rd parties using a standardized service capability exposure framework. The following is a list of architectural considerations for the provision of such a service capability exposure framework (SCEF) within the 3GPP system:
- SCEF shall be within an operator's trust domain;
- SCEF shall have the flexibility to allow operators to expose selected 3GPP service capabilities to 3rd party application providers, via standardized APIs defined by OMA, GSMA, other SDOs, or operator proprietary APIs;
- Impacts to existing 3GPP interfaces and entities shall be minimized.
