Content for TS 29.122 Word version: 18.4.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 T8 reference point
4.1 Overview
4.2 Reference model
4.3 Functional elements
4.3.1 SCEF
4.3.2 SCS/AS
...
...
1 Scope p. 21
The present specification describes the protocol for the T8 reference point between the SCEF and the SCS/AS. The T8 reference point and the related stage 2 functional requirements are defined in TS 23.682.
2 References p. 21
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 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[3]
TS 23.032: "Universal Geographical Area Description (GAD)".
[4] Void.
[5]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[6]
Hypertext Transfer Protocol (HTTP) Status Code Registry at IANA: http://www.iana.org/assignments/http-status-codes .
[7]
RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[8]
RFC 9457: "Problem Details for HTTP APIs".
[9]
TS 29.154: "Service capability exposure functionality over Nt reference point".
[10]
TS 29.214: "Policy and Charging Control over Rx reference point".
[11]
TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
[12]
TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications".
[13]
TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)".
[14]
TS 23.003: "Numbering, addressing and identification".
[15]
RFC 3339: "Date and Time on the Internet: Timestamps".
[16]
RFC 9112: "HTTP/1.1".
[17]
RFC 9110: "HTTP Semantics".
[18] Void.
[19] Void.
[20]
RFC 9111: "HTTP Caching".
[21] Void.
[22]
RFC 9113: "HTTP/2".
[23]
TS 29.155: "Traffic steering control; Representational state transfer (REST) over St reference point".
[24]
TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)".
[25]
TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications".
[26]
TS 29.250: "Nu reference point between SCEF and PFDF for sponsored data connectivity".
[27]
Open API: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[28]
RFC 1166: "Internet Numbers".
[29]
RFC 5952: "A recommendation for Ipv6 address text representation".
[30]
TS 29.153: "Service capability exposure functionality over Ns reference point".
[31]
TS 24.250: "Protocol for Reliable Data Service; Stage 3".
[32]
RFC 6455: "The Websocket Protocol".
[33]
TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
[34]
TS 29.338: "Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)".
[35]
TS 33.187: "Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements".
[36]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE);MB2 Reference Point;Stage 3".
[37]
TS 29.116: "Presentational state transfer over xMB reference point between Content Provider and BM-SC".
[38]
RFC 5789: "PATCH method for HTTP".
[39]
RFC 7396: "JSON Merge Patch".
[40]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[41]
YAML (10/2009): "YAML Ain't Markup Language (YAML™) Version 1.2", http://www.yaml.org/spec/1.2/spec.html .
[42]
TS 29.572: "5G System; Location Management Services; Stage 3".
[43]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[44]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[45]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[46]
RFC 6733: "Diameter Base Protocol".
[47]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[48]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[49]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[50]
TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".
[51]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[52]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[53]
TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[54]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[55]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); stage 2".
[56]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[57]
TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[58]
TR 21.900: "Technical Specification Group working methods".
[59]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification".
[60]
TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[61]
TS 29.675: "User Equipment (UE) radio capability provisioning service; Stage 3".
[62]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[63]
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[64]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[65]
TS 29.515: "5G System; Gateway Mobile Location Services; Stage 3".
[66]
RFC 5322: "Internet Message Format".
[67]
RFC 6902: "JavaScript Object Notation (JSON) Patch".
[68]
TS 33.558: "Security aspects of enhancement of support for enabling edge applications; Stage 2".
[69]
RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
[70]
TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[71]
RFC 6901: "JavaScript Object Notation (JSON) Pointer".
3 Definitions and abbreviations p. 23
3.1 Definitions p. 23
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
3.2 Abbreviations p. 23
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
AF
Application Function
AI/ML
Artificial Intelligence/Machine Learning
AS
Application Server
ASP
Application Service Provider
BAT
Burst Arrival Time
BDT
Background Data Transfer
CAPIF
Common API Framework
CP
Communication Pattern
DDN
Downlink Data Notification
DNN
Data Network Name
DL
Downlink
eNB
Evolved Node B
GMD
Group Message Delivery
IMEI-TAC
Type Allocation Code part of an IMEI
IWK-SCEF
Interworking SCEF
JSON
JavaScript Object Notation
LC
Load Control
LCI
Load Control Information
MIME
Multipurpose Internet Mail Extensions
MT
Mobile Terminated
MTC
Machine Type Communications
MT-LR
Mobile Terminated Location Request
NEF
Network Exposure Function
NIDD
Non-IP Data Delivery
NP
Network Parameter
NSAC
Network Slice Admission Control
OCI
Overload Control Information
OLC
OverLoad Control
PCRF
Policy and Charging Rule Function
PDN
Packet Data Network
PDV
Packet Delay Variation
PFD
Packet Flow Description
PFDF
Packet Flow Description Function
RCAF
RAN Congestion Awareness Function
REST
Representational State Transfer
SACH
Service Announcement Channel
SCEF
Service Capability Exposure Function
SCS
Services Capability Server
S-NSSAI
Single Network Slice Selection Assistance Information
TAI
Tracking Area Identity
TLTRI
T8 Long Term Transaction Reference ID
TSC
Time Sensitive Communication
TSCAI
Time Sensitive Communication Assistance Information
WB
Wide Band
YAML
YAML Ain't Markup Language
4 T8 reference point p. 24
4.1 Overview p. 24
The T8 reference point is between the SCS/AS and the SCEF. It specifies APIs that allow the SCS/AS to access the services and capabilities provided by 3GPP network entities and securely exposed by the SCEF.
This document also specifies the procedures triggered at the SCEF by API requests from the SCS/AS and by event notifications received from 3GPP network entities.
The stage 2 level requirements and signalling flows for the T8 reference point are defined in TS 23.682.
The T8 reference point supports the following procedures:
- Monitoring Procedures
- Procedures for resource management of Background Data Transfer
- Procedures for changing the chargeable party
- Procedures for Non-IP Data Delivery
- Procedures for Device Triggering
- Procedures for Group Message Delivery
- Procedures for Reporting of Network Status
- Procedures for Communication Pattern Parameters Provisioning
- Procedures for PFD Management
- Procedures for Enhanced Coverage Restriction Control
- Procedures for Network Parameter Configuration
- Procedures for setting up an AS session with required QoS
- Procedures for MSISDN-less Mobile Originated SMS
- Procedures for RACS Parameter Provisioning
4.2 Reference model p. 25
The T8 reference point resides between the SCEF and the SCS/AS as depicted in Figure 4.2-1. The overall SCEF architecture is depicted in clause 4.2 of TS 23.682.
4.3 Functional elements p. 25
4.3.1 SCEF p. 25
The SCEF is a functional element which provides means to securely expose the services and capabilities provided by 3GPP network interfaces. The SCEF provides access to network capabilities through homogenous application programming interfaces.
Individual instances of SCEF may vary depending on what service capabilities are exposed and what API features are supported.
The SCEF shall protect the other PLMN entities (e.g. HSS, MME) from requests exceeding the permission arranged in the SLA with the third-party service provider.
When needed, the SCEF supports mapping between information exchanged with SCS/AS (e.g. geographical identifiers) and information exchanged with internal PLMN functions (e.g. cell-Id, eNB-Id, TAI, MBMS SAI, etc.). This mapping is assumed to be provided by the SCEF based on local configuration data.
4.3.2 SCS/AS p. 26
The SCS is the entity which connects MTC application servers to the 3GPP network to enable them to communicate through specific 3GPP defined services with UEs used for MTC and with the SCEF in the HPLMN. The SCS offers capabilities for use by one or multiple MTC application servers. The MTC applications in the external network are hosted on one or more ASs.
An SCS/AS can get services from multiple SCEFs, and an SCEF can provide services to multiple SCS/ASs.
The SCS is controlled by the operator of the HPLMN or by a MTC Service Provider.
The AS can be controlled by a 3rd party.
