Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.502  Word version:  18.5.0

Top   Top   None   None   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Overview  4.1 Introduction 
...

 

1  Scope  p. 11

The present document specifies the stage 3 protocol and data model for the Nsmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMF other than the Session Management Event Exposure service and Session Management services for Non-IP Data Delivery (NIDD).
The 5G System stage 2 architecture and procedures are specified in TS 23.501 and TS 23.502.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 and TS 29.501.
The Session Management Event Exposure Service is specified in TS 29.508. The Session Management services for Non-IP Data Delivery (NIDD) are specified in TS 29.542.
Up

2  References  p. 11

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.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6]
TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[7]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[8]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[9]
TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)".
[10]
RFC 2387:  "The MIME Multipart/Related Content-type".
[11]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[12]
RFC 2045:  "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[13]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[14]
RFC 9113:  "HTTP/2".
[15]
OpenAPI Initiative, "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[16]
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[17]
TS 33.501: "Security architecture and procedures for 5G system".
[18]
RFC 6749:  "The OAuth 2.0 Authorization Framework".
[19]
TS 29.510: "Network Function Repository Services; Stage 3".
[20]
TS 29.518: "5G System; Access and Mobility Management Service; Stage 3".
[21]
TS 23.380: "IMS Restoration Procedures".
[22]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[23]
RFC 9457:  "Problem Details for HTTP APIs".
[24]
TS 23.527: "5G System; Restoration Procedures".
[25]
TS 32.255: "Charging management; 5G data connectivity domain charging; stage 2".
[26]
TS 32.291: "Charging management; 5G system, charging service; Stage 3".
[27]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[28]
TR 21.900: "Technical Specification Group working methods".
[29]
TS 29.244: "Interface between the Control Plane and the User Plane Nodes; stage 3".
[30]
TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[31]  Void
[32]
RFC 9110:  "HTTP Semantics".
[33]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access; Stage 2".
[34]
TS 29.524: "5G System; Cause codes mapping between 5GC interfaces; Stage 3".
[35]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[36]
TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[37]
TS 29.542: "5G System; Session Management Services for Non-IP Data Delivery (NIDD); Stage 3".
[38]
TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Control Data, Application Data and Structured Data for Exposure; Stage 3".
[39]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[40]
TS 29.531: "5G System; Network Slice Selection Services; Stage 3".
[41]
TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[42]
TS 23.015: "Technical realization of Operator Determined Barring (ODB)".
[43]
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[44]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[45]
TS 23.007: "Restoration procedures".
[46]
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
Up

3  Definitions and abbreviations  p. 13

3.1  Definitions  p. 13

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.
Alternative S-NSSAI:
Indicating a compatible S-NSSAI for an S-NSSAI in the Allowed NSSAI that the AMF uses to replace an S-NSSAI when the S-NSSAI is not available or congested, as specified in TS 23.501.
Up

3.2  Abbreviations  p. 13

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.
BP
Branching Point
DNAI
Data Network Access Identifier
DNN
Data Network Name
HR
Home Routed
HR-SBO
Home Routed Session BreakOut
H-SMF
Home SMF
I-SMF
Intermediate SMF
JSON
Javascript Object NotationNAS Non-Access Stratum
LADN
Local Area Data Network
MA
Multi-Access
MO
Mobile Originated
MT
Mobile TerminatedPSA PDU Session Anchor
RSN
Redundancy Sequence Number
SM
Session Management
SMF
Session Management Function
SNPN
Stand-alone Non-Public Network
TNGF
Trusted Non-3GPP Gateway Function
TWIF
Trusted WLAN Interworking Function
UAS
Uncrewed Aerial System
UAV
Uncrewed Aerial Vehicle
UL CL
Uplink Classifier
UPF
User Plane Function
USS
UAS Service Supplier
UUAA
USS UAV Authorization/Authentication
V-SMF
Visited SMF
W-AGF
Wireline Access Gateway Function
Up

4  Overview  p. 14

4.1  Introduction  p. 14

Within the 5GC, the SMF offers services to NF service consumers via the Nsmf service based interface (see TS 23.501 and TS 23.502).
Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the SMF services specified within the present specification.
Reproduction of 3GPP TS 29.502, Fig. 4.1-1: Reference model - SMF
Figure 4.1-1: Reference model - SMF
Up
N16 is the reference point between the V-SMF and H-SMF in Home Routed (HR) roaming cases.
N16a is the reference point between SMF and I-SMF.
N38 is the reference point between I-SMFs or V-SMFs.
The functionalities supported by the SMF are listed in clause 6.2.2 of TS 23.501.

Up   Top   ToC