hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.3.3.3 MLR_ModelInformationDiscovery_Request operation
| API operation name: MLR_MLModelInformationDiscovery_Request
Description: The consumer requests to perform discovery of ML models.
Inputs: See clause 8.11.4.3.
Outputs: See clause 8.11.4.4.
See clause 8.11.3 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4 AIMLE client APIs
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.1 ML model training capability evaluation API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.1.1 General
| Table 9.4.1.1-1 illustrates the API for ML model training capability evaluation. This API enables the AIMLE Server to communicate with the AIMLE client(s) for ML model training capability evaluation.
Table 9.4.1.1-1: Aimlec_MLModelTrainingCapabilityEva API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_MLModelTrainingCapabilityEva
Request
Request/Response
AIMLE Server
Response
AIMLE Client
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.1.2 Aimlec_MLModelTrainingCapabilityEva_Request operation
| API operation name: Aimlec_MLModelTrainingCapabilityEva_Request
Description: The consumer requests for ML Model training capability evaluation.
Inputs: See clause 8.19.3.1.
Outputs: None.
See clause 8.19.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.1.3 Aimlec_MLModelTrainingCapabilityEva_Response operation
| API operation name: Aimlec_MLModelTrainingCapabilityEva_Response
Description: The consumer responses for ML Model training capability evaluation.
Inputs: See clause 8.19.3.2.
Outputs: None.
See clause 8.19.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.2 HFL training API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.2.1 General
| Table 9.4.2.1-1 illustrates the API for HFL training to enable an AIMLE server to subscribe to HFL training.
Table 9.4.2.1-1: Aimlec_HFLTraining API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_HFLTraining
Subscribe
Subscribe/Notify
AIMLE server
Notify
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.2.2 Aimlec_HFLTraining_Subscribe operation
| API operation name: Aimlec_HFLTraining_Subscribe
Description: The consumer subscribes to HFL training.
Inputs: See clause 8.12.3.1.
Outputs: See clause 8.12.3.2.
See clause 8.12.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.2.3 Aimlec_HFLTraining_Notify operation
| API operation name: Aimlec_HFLTraining_Subscribe
Description: The consumer receives notifications from HFL training.
Inputs: See clause 8.12.3.3.
Outputs: None.
See clause 8.12.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.3 Client data processing API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.3.1 General
| Table 9.4.3.1-1 illustrates the API for Client data processing to enable an AIMLE server to request data processing to be performed on AIMLE clients.
Table 9.4.3.1-1: Aimlec_ClientDataProcessing API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_ClientDataProcessing
Request
Request/Response
AIMLE server
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.3.2 Aimlec_ClientDataProcessing_Request operation
| API operation name: Aimlec_ClientDataProcessing_Request
Description: The consumer requests data processing to be performed on AIMLE clients.
Inputs: See clause 8.15.3.4.
Outputs: See clause 8.15.3.5.
See clause 8.15.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.4 AIMLE Client Service Operations API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.4.1 General
| Table 9.4.4.1-1 illustrates the API for AIMLE Client Service Operations.
Table 9.4.4.1-1: Aimlec_AIMLEClientServiceOperations APIs
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_AIMLEClientServiceOperations
Request
Request/Response
AIMLE Server
Response
AIMLE Client
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.4.2 Aimlec_ AIMLEClientServiceOperations_Request operation
| API operation name: Aimlec_AIMLEClientServiceOperations_Request
Description: The consumer requests for AIMLE client service operations.
Inputs: See clause 8.20.3.3.
Outputs: None.
See clause 8.20.2.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.4.3 Aimlec_ AIMLEClientServiceOperations_Response operation
| API operation name: Aimlec_AIMLEClientServiceOperations_Response
Description: The consumer responses for AIMLE client service operations
Inputs: See clause 8.20.3.4.
Outputs: None.
See clause 8.20.2.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.5 AIMLE Client Participation API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.5.1 General
| Table 9.4.5.1-1 illustrates the APIs for AIMLE client participation. This API enables the communication between the AIMLE client and the AIMLE server for AIMLE client participation.
Table 9.4.5.1-1: Aimlec_AIMLEClientParticipation API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_AIMLEClientParticipation
Request
Request/Response
AIMLE Server
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.5.2 Aimlec_AIMLEClientParticipation_Request operation
| API operation name: Aimlec_AIMLEClientParticipation_Request
Description: The consumer requests AIMLE server for AIMLE client participation.
Inputs: See clause 8.10.3.1.
Outputs: See clause 8.10.3.2.
See clause 8.10.2.1 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6 AIMLE AI/ML Task Transfer APIs
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.1 General
| Table 9.4.6.1-1 illustrates the APIs for AI/ML task transfer. This API enables the communication between VAL UE (via AIMLE Client) and the AIMLE server for AI/ML Task Transfer.
Table 9.4.6.1-1: Aimlec_AIMLTaskTransfer API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_AIMLTaskTransfer
Request
Request/Response
AIMLE Server
Table 9.4.6.1-2: Aimlec_DirectAIMLTaskTransfer API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_DirectAIMLTaskTransfer
Request
Request/Response
AIMLE Client
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.2 Aimlec_AIMLTaskTransfer_Request operation
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.2.1 General
| API description: This API enables the AIMLE server to communicate with the target AI/ML member (AIMLE Client) for request AIML task transfer from source AI/ML member (AIMLE Client) to the target AI/ML member (AIMLE Client).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.2.2 AIML task transfer request operation
| API operation name: Aimlec_AIMLTaskTransfer_Request
Description: The consumer requests for AI/ML task transfer.
Inputs: See clause 8.6.3.4.
Outputs: See clause 8.6.3.5.
See clause 8.6.2.2 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.3 Aimlec_DirectAIMLTaskTransfer_Request operation
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.3.1 General
| API description: This API enables the AIMLE client to communicate with the target AI/ML member (AIMLE Client) for request direct AIML task transfer from the source AI/ML member (AIMLE Client) to the target AI/ML member (AIMLE Client).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.6.3.2 Direct AIML task transfer request operation
| API operation name: Aimlec_DirectAIMLTaskTransfer_Request
Description: The consumer requests for direct AI/ML task transfer.
Inputs: See clause 8.6.3.6.
Outputs: See clause 8.6.3.7.
See clause 8.6.2.3 for details of usage of this operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.7 FL grouping indication API
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.7.1 General
| Table 9.4.7.1-1 illustrates the APIs for FL grouping indication. This API enables the communication between the AIMLE server and the FL member for indicating the FL grouping procedure.
Table 9.4.7.1-1: Aimlec_FLGroupIndication API
API Name
API Operations
Operation
Semantics
Consumer(s)
Aimlec_FLGroupIndication
Request
Request/Response
AIMLE Server
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 9.4.7.2 Aimlec_FLGroupIndication operation
| API operation name: Aimlec_FLGroupIndication
Description: The consumer indicates to FL member (AIMLE clients which are deployed on UEs) for FL grouping procedure.
Inputs: See clause 8.17.3.3.
Outputs: See clause 8.17.3.4.
See clause 8.17.2 for details of usage of this operation.
Annex A (informative):
Deployment scenarios
A.1 General
This Annex provides the different deployment models for AIMLE services. There could be three deployment options:
- AIMLE server can be deployed at a centralized cloud platform and collects data from multiple EDNs.
- AIMLE server can be deployed at the edge platform.
- Hierarchical AIMLE server deployment, where multiple AIML enablement services are deployed in edge or central clouds (e.g., in hierarchical architecture). Such deployment allows for local-global analytics for system wide optimization.
A.2 Deployment model #1: Cloud-deployed AIMLE server
In this deployment, , the AIMLE server is centrally located and can provide support for AIML operations to the application and edge services (EAS/EES, VAL server). An example deployment option for AIMLE server at the cloud is shown in Figure A.2-1
Figure A.2-1: Example deployment for AIMLE at the cloud
A.3 Deployment model #2: Edge-deployed AIMLE server
In this deployment, the AIMLE server deployed as EAS is located at the EDN and provides AIML enablement services to the other EAS(s) or other edge native applications at the edge platform. AIMLE services can be deployed by the ECSP or the MNO to provide value-add services related to AI/ML operations.
The ML support operations, that the edge deployed AIMLE Server provides, are applicable to the AIMLE service areas (as shown in the example deployment scenario in Figure A.3-1), which are equivalent to the EDN service areas.
NOTE: AIMLE server deployed as EAS can provide application enablement service to EES.
Figure A.3-1: Example deployment for AIMLE at the cloud
A.4 Deployment model #3: Hierarchical AIMLE server deployment
In this deployment, multiple AIMLE servers can be located at different EDNs (deployed as EASs)/DNs and can be deployed by the same provider. Such hierarchical deployments allow the local – global ML operations (e.g., federated learning across domains).
The ML support services that the edge deployed AIMLE server correspond to the AIMLE service areas (as shown in the example in Figure A.4-1), which is equivalent to the EDN service areas. The central AIMLE server covers all PLMN area and is used to coordinate the ML related operations (e.g., FL server / aggregator) with the distributed AIMLE servers.
Figure A.4-1: Example hierarchical deployment of AIMLE
Annex B (informative):
Business Scenarios
Figure B-1 shows the business relationships that exist for the AIMLE functionality and that are needed to support a single VAL user.
Figure B-1: Business relationships for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL service provider can have VAL service agreements with several VAL users. The VAL user can have VAL service agreements with several VAL service providers.
The VAL service provider can have AIMLE provider arrangements with multiple AIMLE providers.
The AIMLE server is part of the AIMLE provider. The AIMLE provider can have SEAL service agreements with other SEAL service providers and in particular ADAE provider if needed for utilizing AIMLE services for ADAE analytics. Such arrangements allow the ADAE provider to utilize the AIMLE provider services.
The AIMLE and ADAE providers can either be part of the PLMN or have service arrangements with PLMN operators.
NOTE: The ADAE provider can have further arrangements with PLMN operator and VAL service provider; however, this is not shown in the figure.
Annex C (informative):
Role of AIMLE in ML Model Lifecycle
C.1 General
ML model lifecycle (aka ML model operation workflow) contains several parts including ML model training, ML model testing, AI/ML inference emulation, ML model deployment, AI/ML inference, Data Management, intermediate model aggregation, Trained AI/ML model delivery, and so on. The consumer can delegate all or part of ML model lifecycle to the AIML enablement layer. In doing so the AIML enablement layer can take over some AI/ML related work for the consumer and reduce the complexity of implementation for consumers. In the below sub-clauses, some options for the role of AIMLE in the ML model lifecycle are provided.
C.2 Role#1 of AIMLE in ML Model Lifecycle
In this scenario, the consumer completely rely on the AIML enablement layer for managing the ML operational workflow. That is, the consumer send the requirements of the AI/ML application, then the AIML enablement layer can perform ML operational workflows and determine the required AI/ML model to send to the consumer. Such role of AIMLE is captured in the capability related to AIML service operations control and management as described in clause 8.20.
Figure C.2-1: Example of Role#1
C.3 Role#2 of AIMLE in ML Model Lifecycle
In this scenario, consumer would like to perform part of the ML operational workflow, then consumer partially rely on the AIML enablement layer to assist with ML operational workflowss. Due to different ML operational workflow division, the AIML enablement layer can provide different levels of assistance on ML workflows for consumers.
Such capability is captured for example for ML model training (as in clause 8.3), HFL training (as in clause 8.12), model evaluation (which is captured in clause 8.19 in model capability evaluation, and 8.22 in model performance monitoring procedures). Figure C.3-1 illustrates an example where ML model training is handled by the AIMLE where the other operations are performed by the VAL / ASP.
Figure C.3-1: Example of Role#2
C.4 Role#3 of AIMLE in ML Model Lifecycle
In this scenario, the AIMLE is not performing part of the ML operational workflow; however it serves as a platform to enable the AI/ML apps to utilize ML operational workflows which are provided by VAL. In this role, the AIMLE supports tasks like the discovery, registration, storage, grouping and selection of entities to be performing the ML operations in the lifecycle. Such role is more applicable to ML model lifecycle enablement which provides assistance for use cases where an ASP/VAL wants to find other application entities to perform some ML operations (e.g. ML model inference) and AIMLE server as a mediator to accomplish this.
An example including some capabilities is illustrated in Figure C.4-1. In this figure, the support capabilities are based on AIMLE capabilities identified in this specification. In particular, AIMLE is undertaking:
- ML model related support capabilities such as model retrieval, discovery and storage (as covered in procedures in clauses 8.2 and 8.11 )
- ML operation related support capabilities such as VFL/ HFL and TL enablement, Split AI/ML Operation support, Data management assistance, AI/ML task transfer, FL assistance in member grouping, registration and event notification (as covered in procedures in clauses 8.4, 8.6, 8.12, 8.14, 8.15-8.18).
- AIMLE client related support capabilities, including AIMLE client registration, discovery, participation, monitoring, selection (as covered in procedures in clauses 8.7-8.10, 8.13).
Figure C.4-1: Example of Role#3
Annex D:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2024-07
SA6#62 ad hoc-e
TS skeleton
0.0.0
2024-07
SA6#62 ad hoc-e
Implementation of the following pCRs approved by SA6:
S6a240288, S6a240289.
0.1.0
2024-08
SA6#62
Implementation of the following pCRs approved by SA6:
S6-243211, S6-243580, S6-243699, S6-243589, S6-243714, S6-243591, S6-243734, S6-243727, S6-243728, S6-243729, S6-243751, S6-243752, S6-243702, S6-243659, S6-243660, S6-243752, S6-243642, S6-243721, S6-243644, S6-243645.
0.2.0
2024-10
SA6#63
Implementation of the following pCRs approved by SA6:
S6-244583, S6-244584, S6-244585, S6-244586, S6-244677, S6-244587, S6-244707, S6-244590, S6-244591, S6-244068, S6-244592, S6-244713, S6-244071, S6-244595, S6-244678, S6-244162, S6-244597, S6-244662, S6-244736, S6-244164, S6-244601, S6-244663, S6-244708, S6-244605, S6-244684, S6-244607, S6-244705, S6-244727.
0.3.0
2024-11
SA6#64
Implementation of the following pCRs approved by SA6:
S6-245637, S6-245666, S6-245557, S6-245685, S6-245560, S6-245324, S6-245562, S6-245561,S6-245667, S6-245564, S6-245565, S6-245638, S6-245567,S6-245668, S6-245694, S6-245571, S6-245572, S6-245573, S6-245669, S6-245672, S6-245670,S6-245671, S6-245578, S6-245695, S6-245580, S6-245701, S6-245582, S6-245583, S6-245321, S6-245587, S6-245588, S6-245729, S6-245586, S6-245673, S6-245591,S6-245675, S6-245593, S6-245731.
0.4.0
2024-12
SA#106
SP-241703
Submitted to SA#106 for information and approval
1.0.0
2024-12
SA#106
SP-241703
MCC Editorial update for publication after TSG SA approval (SA#106)
19.0.0
2025-03
SA#107
SP-250206
0001
1
F
Delete term of AI/ML server
19.1.0
2025-03
SA#107
SP-250206
0002
1
F
Unified use of AIML enablement
19.1.0
2025-03
SA#107
SP-250206
0003
1
F
Resolving Editor's Notes in clause 8.8 and 8.13
19.1.0
2025-03
SA#107
SP-250206
0004
1
F
Aligning AIMLE client discovery with the AIMLE client registration IEs
19.1.0
2025-03
SA#107
SP-250206
0005
1
F
AIMLE client selection subscription update and subscription cancel
19.1.0
2025-03
SA#107
SP-250206
0006
1
F
Corrections related to ML model data types
19.1.0
2025-03
SA#107
SP-250206
0007
1
F
Consistent VAL Service ID usage
19.1.0
2025-03
SA#107
SP-250206
0008
2
F
Corrections to AIMLE client registration
19.1.0
2025-03
SA#107
SP-250206
0009
1
F
Update to AIMLE client selection
19.1.0
2025-03
SA#107
SP-250206
0010
1
F
Additional AIMLE identifiers
19.1.0
2025-03
SA#107
SP-250206
0013
1
F
EN resolutions in TS 23.482
19.1.0
2025-03
SA#107
SP-250206
0018
1
F
Definitions of terms and abbreviations
19.1.0
2025-03
SA#107
SP-250206
0022
1
F
Updates to the Response of ML Model Information Storage and Discovery
19.1.0
2025-03
SA#107
SP-250206
0023
1
F
Updates to ML Model Training Notification
19.1.0
2025-03
SA#107
SP-250206
0024
1
F
Updates to AI/ML Task Transfer
19.1.0
2025-03
SA#107
SP-250206
0025
1
F
Corrections to AIML Service Operations
19.1.0
2025-03
SA#107
SP-250206
0026
2
F
Updates to FL Member Grouping
19.1.0
2025-03
SA#107
SP-250206
0027
1
F
Adding AIMLE Client to FL Member Registration Procedure and Information Flows
19.1.0
2025-03
SA#107
SP-250206
0028
F
Adding Missing Service Operations to API Clauses
19.1.0
2025-03
SA#107
SP-250206
0029
1
F
Add Functional Description for the Hierarchical Computing
19.1.0
2025-03
SA#107
SP-250206
0030
F
Align Termination for ADAE Analytics ID
19.1.0
2025-03
SA#107
SP-250206
0031
1
F
Corrections to Procedures and Information Flows
19.1.0
2025-06
SA#108
SP-250593
0032
1
F
Adding Reference and General Description for Security Aspects
19.2.0
2025-06
SA#108
SP-250593
0033
1
F
Updates to Information Flows for Responses
19.2.0
2025-06
SA#108
SP-250593
0034
F
Clarification on AIMLE Server Deployment for Supporting Hierarchical Computing
19.2.0
2025-06
SA#108
SP-250593
0035
2
F
Modification of the business relationship in TS23.482
19.2.0
2025-06
SA#108
SP-250593
0036
1
F
EN resolutions and minor fixes
19.2.0
2025-06
SA#108
SP-250593
0038
4
F
Addition of missing operations in FL Member Grouping
19.2.0
2025-06
SA#108
SP-250593
0041
2
F
Deregistration of an FL Member
19.2.0
2025-06
SA#108
SP-250593
0042
2
F
Correction on AIMLE Server to assist AI/ML task transfer
19.2.0
2025-06
SA#108
SP-250593
0043
1
F
Correction on ML model information storage and discovery
19.2.0
2025-09
SA#109
SP-251051
0044
3
F
ML model training procedure alignment with client selection and HFL/VFL procedures
19.3.0
2025-09
SA#109
SP-251051
0051
1
F
Corrections to Deployment Models for Edge AIMLE Server
19.3.0
2025-09
SA#109
SP-251051
0052
1
F
Correction on ML model information discovery
19.3.0
2025-09
SA#109
SP-251051
0053
2
F
AIMLE context transfer correction
19.3.0
2025-09
SA#109
SP-251051
0054
1
F
AIMLE ML model training request correction
19.3.0
2026-01
SA#110
SP-251470
0056
1
F
HFL training completion
19.4.0
2026-01
SA#110
SP-251470
0057
1
F
Clarifications to clause 8.15.2
19.4.0
2026-01
SA#110
SP-251495
0055
2
B
The clarification on the FL member registration/deregistration
20.0.0
|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 1 Scope | The present document defines the Stage 2 system architecture for the 5G System. The 5G System provides data connectivity and services.
This specification covers both roaming and non-roaming scenarios in all aspects, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and charging, authentication and in general 5G System wide features e.g. SMS, Location Services, Emergency Services.
ITU‑T Recommendation I.130 [11] describes a three-stage method for characterisation of telecommunication services and ITU‑T Recommendation Q.65 [12] defines Stage 2 of the method.
TS 23.502 [3] contains the stage 2 procedures and flows for 5G System and it is a companion specification to this specification.
TS 23.503 [45] contains the stage 2 Policy Control and Charging architecture for 5G System and it is a companion specification to this specification. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 2 References | 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 23.203: "Policies and Charging control architecture; Stage 2".
[5] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Stage 2".
[6] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface: Stage 3".
[7] IETF RFC 7157: "IPv6 Multihoming without Network Address Translation".
[8] IETF RFC 4191: "Default Router Preferences and More-Specific Routes".
[9] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[10] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[11] ITU‑T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
[12] ITU‑T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities".
[13] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS): Stage 3".
[14] Void.
[15] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[16] 3GPP TS 22.173: "IMS Multimedia Telephony Service and supplementary services; Stage 1".
[17] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".
[18] 3GPP TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions".
[19] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[20] IETF RFC 7542: "The Network Access Identifier".
[21] 3GPP TS 23.002: "Network Architecture".
[22] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2".
[23] 3GPP TS 23.221: "Architectural requirements".
[24] 3GPP TS 22.153: "Multimedia priority service".
[25] 3GPP TS 22.011: "Service Accessibility".
[26] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[27] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description".
[28] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification".
[29] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[30] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[31] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
[32] 3GPP TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2".
[33] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".
[34] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[35] 3GPP TS 33.126: "Lawful Interception Requirements".
[36] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[37] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[38] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[39] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[40] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[41] 3GPP TS 32.240: "Charging management; Charging architecture and principles".
[42] 3GPP TS 38.401: "NG-RAN Architecture description".
[43] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[44] IETF RFC 4960: "Stream Control Transmission Protocol".
[45] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System".
[46] 3GPP TS 23.041: "Public Warning System".
[47] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[48] 3GPP TS 24.502: "Access to the 5G System (5GS) via non-3GPP access networks; Stage 3".
[49] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[50] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode".
[51] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[52] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[53] Void.
[54] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[55] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[56] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[57] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
[58] 3GPP TS 29.510: "5G System: Network function repository services; Stage 3".
[59] 3GPP TS 29.502: "5G System: Session Management Services: Stage 3".
[60] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2) ".
[61] 3GPP TS 23.380: "IMS Restoration Procedures".
[62] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[63] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2".
[64] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs".
[65] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3".
[66] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[67] 3GPP TS 32.290: "5G system; Services, operations and procedures of charging using Service Based Interface (SBI)".
[68] 3GPP TS 32.255: "5G Data connectivity domain charging; Stage 2".
[69] 3GPP TS 38.306: "NR; User Equipment -UE) radio access capabilities".
[70] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access -E-UTRA); User Equipment -UE) radio access capabilities".
[71] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[72] Void.
[73] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)".
[74] IETF RFC 3162: "RADIUS and IPv6".
[75] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
[76] 3GPP TS 26.238: "Uplink streaming".
[77] 3GPP TR 26.939: "Guidelines on the Framework for Live Uplink Streaming (FLUS)".
[78] International Telecommunication Union (ITU), Standardization Bureau (TSB): "Operational Bulletin No. 1156"; http://handle.itu.int/11.1002/pub/810cad63-en (retrieved October 5, 2018).
[79] 3GPP TS 28.533: "Management and orchestration; Architecture framework".
[80] 3GPP TS 24.250: "Protocol for Reliable Data Service; Stage 3".
[81] IETF RFC 8684: "TCP Extensions for Multipath Operation with Multiple Addresses".
[82] IETF RFC 8803: "0-RTT TCP Convert Protocol".
[83] IEEE Std 802.1CB-2017: "IEEE Standard for Local and metropolitan area networks-Frame Replication and Elimination for Reliability".
[84] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[85] WiFi Alliance Technical Committee, Hotspot 2.0 Technical Task Group: "Hotspot 2.0 (Release 2) Technical Specification".
[86] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[87] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[88] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[89] CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification".
[90] BBF TR-124 issue 5: "Functional Requirements for Broadband Residential Gateway Devices".
[91] BBF TR-101 issue 2: "Migration to Ethernet-Based Broadband Aggregation".
[92] BBF TR-178 issue 1: "Multi-service Broadband Network Architecture and Nodal Requirements".
[93] BBF TR-456 issue 2: "AGF Functional Requirements".
[94] BBF WT-457: "FMIF Functional Requirements".
Editor's note: The reference to BBF WT-457 will be revised when finalized by BBF.
[95] Void.
[96] Void.
[97] IEEE Std 802.1AB-2016: "IEEE Standard for Local and metropolitan area networks -- Station and Media Access Control Connectivity Discovery".
[98] IEEE Std 802.1Q-2022: "IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks".
[99] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[100] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[101] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[102] 3GPP TS 23.632: "User Data Interworking, Coexistence and Migration; stage 2".
[103] 3GPP TS 29.563: "5G System (5GS); HSS services for interworking with UDM; Stage 3".
[104] IEEE Std 802.1AS-2020: "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-Sensitive Applications".
[105] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
[106] IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[107] IEEE Std 1588-2008: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems".
[108] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[109] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting; Stage 3".
[110] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[111] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
[112] 3GPP TR 38.824: "Study on physical layer enhancements for NR ultra-reliable and low latency case (URLLC)".
[113] IEEE: "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI) and Company ID (CID)", https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf.
[114] 3GPP TS 32.256: "Charging Management; 5G connection and mobility domain charging; Stage 2".
[115] 3GPP TS 33.210: "Network Domain Security (NDS); IP network layer security".
[116] 3GPP TS 38.415: "PDU Session User Plane Protocol".
[117] 3GPP TS 24.535: "Device-side Time-Sensitive Networking (TSN) Translator (DS-TT) to network-side TSN Translator (NW-TT) protocol aspects; Stage 3".
[118] 3GPP TS 32.274: "Charging Management; Short Message Service (SMS) charging".
[119] 3GPP TS 23.008: "Organization of subscriber data".
[120] 3GPP TS 38.314: "NR; Layer 2 measurements".
[121] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[122] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[123] 3GPP TS 32.254: "Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging".
[124] 3GPP TS 33.535: "Authentication and Key Management for Applications based on 3GPP credentials in the 5G System (5GS)".
[125] 3GPP TS 38.410: "NG-RAN; NG general aspects and principles".
[126] IEEE Std 1588: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", Edition 2019.
[127] ST 2059-2:2015: "SMPTE Standard - SMPTE Profile for Use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications".
[128] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[129] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
[130] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[131] IEEE Std 802.3: "Ethernet".
[132] 3GPP TS 29.561: "5G System; Interworking between 5G Network and external Data Networks; Stage 3".
[133] 3GPP TS 29.513: "Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3".
[134] 3GPP TS 23.558: "Architecture for enabling Edge Applications (EA)".
[135] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[136] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[137] GSMA NG.116: "Generic Network Slice Template".
[138] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets".
[139] 3GPP TS 24.539: "5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3".
[140] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture".
[141] 3GPP TS 33.223: "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function".
[142] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2".
[143] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[144] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3".
[145] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository Services for Subscription Data; Stage 3".
[146] IEEE Std 802.1Qdj-2024: "IEEE Draft Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment XX: Configuration Enhancements for Time-Sensitive Networking".
[147] Void.
[148] 3GPP TS 28.557: "Management and orchestration; Management of Non-Public Networks (NPN)".
[149] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM)".
[150] IETF RFC 8655: "Deterministic Networking Architecture".
[151] IETF RFC 8343: "A YANG Data Model for Interface Management".
[152] IETF RFC 8344: "A YANG Data Model for IP Management".
[153] IETF RFC 7224: " IANA Interface Type YANG Module".
[154] IETF RFC 9633: "Deterministic Networking (DetNet) YANG Model".
[155] IETF RFC 6241: "Network Configuration Protocol (NETCONF)".
[156] IETF RFC 8040: "RESTCONF Protocol".
[157] IETF RFC 8939: "Deterministic Networking (DetNet) Data Plane: IP".
[158] IETF RFC 5279: "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)".
[159] IETF RFC 9330:"Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture".
[160] IETF RFC 9331: "Explicit Congestion Notification (ECN) Protocol for Very Low Queuing Delay (L4S)".
[161] IETF RFC 9332: "Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss and Scalable Throughput (L4S)".
[162] IETF RFC 6603: "Prefix Exclude Option for DHCPv6-based Prefix Delegation".
[163] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[164] ITU‑T Recommendation G.810: "Definitions and terminology for synchronization networks".
[165] 3GPP TS 38.470: "NG-RAN; F1 general aspects and principles".
[166] IETF RFC 9000: "QUIC: A UDP-Based Multiplexed and Secure Transport".
[167] IETF RFC 9001: "Using TLS to Secure QUIC".
[168] IETF RFC 9002: "QUIC Loss Detection and Congestion Control".
[169] IETF RFC 9221: "An Unreliable Datagram Extension to QUIC".
[170] IETF RFC 9298: "Proxying UDP in HTTP".
[171] IETF RFC 9114: "Hypertext Transfer Protocol Version 3 (HTTP/3)".
[172] IETF RFC 9297: "HTTP Datagrams and the Capsule Protocol".
[173] IETF RFC 9220: "Bootstrapping WebSockets with HTTP/3".
[174] draft-ietf-quic-multipath: "Multipath Extension for QUIC".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[175] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements".
[176] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[177] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[178] IEEE Std 802.1CBdb-2021: "Amendment 2: Extend Stream Identification Functions".
[179] 3GPP TS 26.522: "5G Real-time Media Transport Protocol Configurations".
[180] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning".
[181] 3GPP TS 23.542: "Application layer support for Personal IoT Network".
[182] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[183] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[184] 3GPP TS 23.289: "Mission Critical services over 5G System; Stage 2".
[185] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications".
[186] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)".
[187] IETF RFC 6184: "RTP Payload Format for H.264 Video".
[188] IETF RFC 7798: "RTP Payload Format for High Efficiency Video Coding (HEVC) ".
[189] IETF RFC 8285: "A General Mechanism for RTP Header Extensions".
[190] 3GPP TS 28.405: "Quality of Experience (QoE) measurement collection; Control and configuration".
[191] 3GPP TS 37.355: " LTE Positioning Protocol (LPP)".
[192] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[193] IETF RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP".
[194] 3GPP TS 33.503: "Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)".
[195] 3GPP TS 38.414: "NG-RAN; NG data transport".
[196] Void.
[197] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[198] IETF RFC 6040: "Tunnelling of Explicit Congestion Notification".
[199] IETF RFC 9599: "Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP".
[200] IETF draft-ietf-masque-quic-proxy: " QUIC-Aware Proxying Using HTTP".
Editor's note: The above reference will be revised to RFC when finalized by IETF.
[201] IETF draft-ietf-moq-transport: "Media over QUIC Transport".
Editor's note: The above reference will be revised to RFC when finalized by IETF.
[202] IETF draft-ietf-tsvwg-udp-options: "Transport Options for UDP".
Editor's note: The above reference will be revised to RFC when finalized by IETF.
[203] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port".
[204] IETF RFC 5764: "Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)".
[205] IETF RFC 7983: "Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)".
[206] IETF RFC 8872: "Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams".
[207] IETF RFC 9143: "Negotiating Media Multiplexing Using the Session Description Protocol (SDP)".
[208] IETF RFC 9443: "Multiplexing Scheme Updates for QUIC".
[209] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[210] 3GPP TS 23.527: "5G System; Restoration Procedures".
[211] IETF RFC 5357: "A Two-Way Active Measurement Protocol (TWAMP)".
[212] IETF RFC 4656: "A One-way Active Measurement Protocol (OWAMP)".
[213] IETF RFC 8762: "Simple Two-Way Active Measurement Protocol".
[214] IETF RFC 9484: "Proxying IP in HTTP".
[215] IETF draft-ietf-masque-connect-ethernet: " Proxying Ethernet in HTTP".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[216] IEC/IEEE 60802: "Time-Sensitive Networking Profile for Industrial Automation".
[217] 3GPP TS 38.424: "NG-RAN; Xn data transport".
[218] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[219] 3GPP TS 28.532: "Management and orchestration; Generic management services". |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 3 Definitions and abbreviations | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] 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 [1].
5G VN Group: A set of UEs using private communication for 5G LAN-type service.
5G Access Network: An access network comprising a NG-RAN and/or non-3GPP AN connecting to a 5G Core Network.
5G Access Stratum-based Time Distribution: A time synchronization distribution method that is used by an NG-RAN to provide the 5GS time to the UE(s) over the radio interface using procedures specified in TS 38.331 [28].
5G Core Network: The core network specified in the present document. It connects to a 5G Access Network.
5G LAN-Type Service: A service over the 5G system offering private communication using IP and/or non-IP type communications.
5G LAN-Virtual Network: A virtual network over the 5G system capable of supporting 5G LAN-type service.
5G NSWO: The 5G NSWO is the capability provided by 5G system and by UE to enable the connection to a WLAN access network using 5GS credentials without registration to 5GS.
5G QoS Flow or QoS Flow: The finest granularity for QoS forwarding treatment in the 5G System. All traffic mapped to the same 5G QoS Flow receive the same forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding treatment requires separate 5G QoS Flow.
5G QoS Identifier: A scalar that is used as a reference to a specific QoS forwarding behaviour (e.g. packet loss rate, packet delay budget) to be provided to a 5G QoS Flow. This may be implemented in the access network by the 5QI referencing node specific parameters that control the QoS forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.).
5G System: 3GPP system consisting of 5G Access Network (AN), 5G Core Network and UE.
5G-BRG: The 5G-BRG is a 5G-RG defined in BBF.
5G-CRG: The 5G-CRG is a 5G-RG specified in DOCSIS MULPI [89].
5G-RG: A 5G-RG is a RG capable of connecting to 5GC playing the role of a UE with regard to the 5G core. It supports secure element and exchanges N1 signalling with 5GC. The 5G-RG can be either a 5G-BRG or 5G-CRG.
Access Traffic Steering: The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. Access traffic steering is applicable between one 3GPP access and one non-3GPP access.
Access Traffic Switching: The procedure that moves all traffic of an ongoing data flow from one access network to another access network in a way that maintains the continuity of the data flow. Access traffic switching is applicable between one 3GPP access and one non-3GPP access.
Access Traffic Splitting: The procedure that splits the traffic of a data flow across multiple access networks. When traffic splitting is applied to a data flow, some traffic of the data flow is transferred via one access and some other traffic of the same data flow is transferred via another access. Access traffic splitting is applicable between one 3GPP access and one non-3GPP access.
Allowed NSSAI: Indicating the S-NSSAIs values the UE could use in the Serving PLMN in the current Registration Area.
Allowed Area: Area where the UE is allowed to initiate communication as specified in clause 5.3.2.3.
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 clause 5.15.19.
AMF Region: An AMF Region consists of one or multiple AMF Sets.
AMF Set: An AMF Set consists of some AMFs that serve a given area and Network Slice(s). AMF Set is unique within an AMF Region and it comprises of AMFs that support the same Network Slice(s). Multiple AMF Sets may be defined per AMF Region. The AMF instances in the same AMF Set may be geographically distributed but have access to the same context data.
Application Identifier: An identifier that can be mapped to a specific application traffic detection rule.
AUSF Group ID: This refers to one or more AUSF instances managing a specific set of SUPIs. An AUSF Group consists of one or multiple AUSF Sets.
Backhaul PLMN/SNPN (BH PLMN/SNPN): The PLMN or SNPN serving a MWAB-UE. It can be a Terrestrial Network or a Non-Terrestrial Network.
Binding Indication: Information included by a NF service producer to a NF service consumer in request responses or notifications to convey the scope within which selection/reselection of target NF/NF Services may be performed, or information included by the NF service consumer in requests or subscriptions to convey the scope within which selection/reselection of notification targets or the selection of other service(s) that the NF consumer produces for the same data context may be performed. See clause 6.3.1.0.
BSF Group ID: This refers to one or more BSF instances managing a specific set of SUPIs or GPSIs. A BSF Group consists of one or multiple BSF Sets.
Configured NSSAI: NSSAI provisioned in the UE applicable to one or more PLMNs.
CHF Group ID: This refers to one or more CHF instances managing a specific set of SUPIs.
Credentials Holder: Entity which authenticates and authorizes access to an SNPN separate from the Credentials Holder.
Data Burst: A set of multiple PDUs generated and sent by the application in a short period of time.
NOTE 1: A Data Burst can be composed of one or multiple PDU Sets.
Default UE credentials: Information configured in the UE to make the UE uniquely identifiable and verifiably secure to perform UE onboarding.
Default Credentials Server (DCS): An entity that can perform authentication based on the Default UE credentials or provide means for another entity to perform authentication based on the Default UE credentials.
Delegated Discovery: This refers to delegating the discovery and associated selection of NF instances or NF service instances to an SCP.
Direct Communication: This refers to the communication between NFs or NF services without using an SCP.
Disaster Condition: See definition in TS 22.261 [2].
Disaster Inbound Roamer: See definition in TS 22.261 [2].
Disaster Roaming: See definition in TS 22.261 [2].
DN Access Identifier (DNAI): Identifier of a user plane access to one or more DN(s) where applications are deployed.
Emergency Registered: A UE is considered Emergency Registered over an Access Type in a PLMN when registered for emergency services only over this Access Type in this PLMN.
Endpoint Address: An address in the format of an IP address or FQDN, which is used to determine the host/authority part of the target URI. This Target URI is used to access an NF service (i.e. to invoke service operations) of an NF service producer or for notifications to an NF service consumer.
Energy Consumption: As defined in TS 28.310 [197].
Energy Efficiency: As defined in TS 28.310 [197].
Energy State: As defined in TS 22.261 [2].
En-gNB: as defined in TS 37.340 [31].
Expected UE Behaviour: Set of parameters provisioned by an external party to 5G network functions on the foreseen or expected UE behaviour, see clause 5.20.
Feeder link: As defined in TS 38.300 [27].
Fixed Network Residential Gateway: A Fixed Network RG (FN-RG) is a RG that it does not support N1 signalling and it is not 5GC capable.
Fixed Network Broadband Residential Gateway: A Fixed Network RG (FN-BRG) is a FN-RG specified in BBF TR‑124 [90].
Fixed Network Cable Residential Gateway: A Fixed Network Cable RG (FN-CRG) is a FN-RG with cable modem specified in DOCSIS MULPI [89].
Forbidden Area: An area where the UE is not allowed to initiate communication as specified in clause 5.3.2.3.
GBR QoS Flow: A QoS Flow using the GBR resource type or the Delay-critical GBR resource type and requiring guaranteed flow bit rate.
Group ID for Network Selection (GIN): An identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder.
(g)PTP-based Time Distribution: a method to distribute timing among entities in a (g)PTP domain using PTP messages generated by a GM (in the case the GM is external to 5GS) or by 5GS (in the case the 5GS acts as a GM for a given (g)PTP domain). Possible dependencies between (g)PTP-based Time Distribution and 5G Access Stratum-based Time Distribution are described in clause 5.27.1. The synchronization process is described in clause 5.27.1 and follows the applicable profiles of IEEE Std 802.1AS [104] or IEEE Std 1588 [126].
Home Network Public Key Identifier: An identifier used to indicate which public/private key pair is used for SUPI protection and de-concealment of the SUCI as specified in TS 23.003 [19].
IAB-donor: This is a NG-RAN node that supports Integrated access and backhaul (IAB) feature and provides connection to the core network to IAB-nodes. It supports the CU function of the CU/DU architecture for IAB defined in TS 38.401 [42].
IAB-node: A relay node that supports wireless in-band and out-of-band relaying of NR access traffic via NR Uu backhaul links. It supports the UE function and the DU function of the CU/DU architecture for IAB defined in TS 38.401 [42].
Non-3GPP Device Identifier: The Non-3GPP Device Identifier is a generic string bound to a non-3GPP device connecting behind a UE or 5G-RG enabling QoS differentiation by 5GC of the traffic that originates from or is directed to the non-3GPP device as defined in clause 5.52.
Indirect Communication: This refers to the communication between NFs or NF services via an SCP.
Initial Registration: UE registration in RM-DEREGISTERED state as specified in clause 5.3.2.
Intermediate SMF (I-SMF): An SMF that is inserted to support a PDU session as the UE is located in an area which cannot be controlled by the original SMF because the UPF(s) belong to a different SMF Service Area.
Local Area Data Network: a DN that is accessible by the UE only in specific locations, that provides connectivity to a specific DNN and whose availability is provided to the UE.
Local Break Out (LBO): Roaming scenario for a PDU Session where the PDU Session Anchor and its controlling SMF are located in the serving PLMN (VPLMN).
LTE-M: a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of E-UTRA RAT type and defined to identify in the Core Network the E-UTRA when used by a UE indicating Category M.
MA PDU Session: A PDU Session that provides a PDU connectivity service, which can use one access network at a time, or simultaneously one 3GPP access network and one non-3GPP access network.
Mobile Base Station Relay: A mobile base station acts as a relay between a UE and the 5G network. Such mobile base station relay can for example be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle). See description of TS 22.261 [2]. A mobile Base Station Relay is supported in 5GS with the IAB-architecture with mobility as specified in clause 5.35A and that described in TS 38.401 [42].
Mobile gNB with Wireless Access Backhauling (MWAB): A NG-RAN device comprised of a UE (MWAB-UE) and a gNB (MWAB-gNB). The MWAB provides an NR access link to UEs and connects wirelessly to the 5GC (using NR) of a PLMN or SNPN broadcasted by its cell(s), through an IP connectivity provided by a Backhaul (BH) PDU sessions established by the MWAB-UE via the NG-RAN of a Backhaul(BH) PLMN/SNPN. Such device may be mobile, e.g. it may be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle).
MWAB Broadcasted PLMN/SNPN: A PLMN or SNPN whose identifier a MWAB-gNB cell(s) is(are) configured to broadcast in the system information. This is a PLMN/SNPN the MWAB-gNB provides access to.
Master RAN node: A Master node as defined in TS 37.340 [31].
Mobility Pattern: Network concept of determining within the AMF the UE mobility parameters as specified in clause 5.3.2.4.
Mobility Registration Update: UE re-registration when entering new TA outside the TAI List as specified in clause 5.3.2.
MPS-subscribed UE: A UE having a USIM with MPS indication set, and having an MPS subscription in the HPLMN.
Multi-USIM UE: A UE with multiple USIMs, capable of maintaining a separate registration state with a PLMN for each USIM at least over 3GPP Access and supporting one or more of the features described in clause 5.38.
NB-IoT UE Priority: Numerical value used by the NG-RAN to prioritise between different UEs accessing via NB-IoT.
NGAP UE association: The logical per UE association between a 5G-AN node and an AMF.
NGAP UE-TNLA-binding: The binding between a NGAP UE association and a specific TNL association for a given UE.
Network Function: A 3GPP adopted or 3GPP defined processing function in a network, which has defined functional behaviour and 3GPP defined interfaces.
NOTE 2: A network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
Network Instance: Information identifying a domain. Used by the UPF for traffic detection and routing.
Network Slice: A logical network that provides specific network capabilities and network characteristics.
Network Slice Area of Service (NS-AoS): The area where a network slice is available i.e. the UE can access and get service of a particular network slice as more than zero resources are allocated to the network slice in the NG-RAN cells. This area may be, depending on the specific network slice, the whole PLMN, one or more TAs, or one or more cells when the NS-AoS does not match deployed TAs as defined in clause 5.15.18.
Network Slice instance: A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice.
Non-GBR QoS Flow: A QoS Flow using the Non-GBR resource type and not requiring guaranteed flow bit rate.
NSI ID: an identifier for identifying the Core Network part of a Network Slice instance when multiple Network Slice instances of the same Network Slice are deployed and there is a need to differentiate between them in the 5GC.
NF instance: an identifiable instance of the NF.
NF service: a functionality exposed by a NF through a service-based interface and consumed by other authorized NFs.
NF service instance: an identifiable instance of the NF service.
NF service operation: An elementary unit a NF service is composed of.
NF Service Set: A group of interchangeable NF service instances of the same service type within an NF instance. The NF service instances in the same NF Service Set have access to the same context data.
NF Set: A group of interchangeable NF instances of the same type, supporting the same services and the same Network Slice(s). The NF instances in the same NF Set may be geographically distributed but have access to the same context data.
NG-RAN: A radio access network that supports one or more of the following options with the common characteristics that it connects to 5GC:
1) Standalone New Radio.
2) New Radio is the anchor with E-UTRA extensions.
3) Standalone E-UTRA.
4) E-UTRA is the anchor with New Radio extensions.
Non-3GPP QoS Assistance Information: A set of QoS assistance information provided to the UE (e.g. PEGC) to enable the UE to perform QoS differentiation for the connected devices in the non-3GPP network behind the UE.
Non-Allowed Area: Area where the UE is allowed to initiate Registration procedure but no other communication as specified in clause 5.3.2.3.
Non-Public Network: See definition in TS 22.261 [2].
Non-Seamless Non-3GPP offload: The offload of user plane traffic via non-3GPP access without traversing either N3IWF/TNGF or UPF.
Non-Seamless WLAN offload: Non-Seamless Non-3GPP offload when the non-3GPP access network is WLAN.
NR Femto Hosting Party: An NR Femto Hosting Party has a contractual relationship with the operator, related to the provision of access to the operator's network via one or more NR Femto nodes. An NR Femto Hosting Party plays the role of a CAG owner as specified in clause 5.50.
Onboarding Network: Either a PLMN enabling Remote Provisioning for a registered UE, or an Onboarding SNPN.
Onboarding Standalone Non-Public Network: An SNPN providing Onboarding access and enabling Remote Provisioning for a UE registered for Onboarding as specified in clause 4.2.2.2.4 of TS 23.502 [3].
Partially Allowed NSSAI: Indicating the S-NSSAIs values the UE could use in the Serving PLMN or SNPN in some of the TAs in the current Registration Area. Each S-NSSAI in the Partially Allowed NSSAI is associated with a list of TAs where the S-NSSAI is supported.
PCF Group ID: This refers to one or more PCF instances managing a specific set of SUPIs. A PCF Group consists of one or multiple PCF Sets.
PDU Connectivity Service: A service that provides exchange of PDUs between a UE and a Data Network.
PDU Session: Association between the UE and a Data Network that provides a PDU connectivity service.
PDU Session Type: The type of PDU Session which can be IPv4, IPv6, IPv4v6, Ethernet or Unstructured.
PDU Set: One or more PDUs carrying the payload of one unit of information generated at the application level (e.g. frame(s) or video slice(s) etc. for eXtended Reality (XR) Services). All the PDUs of a PDU set are transmitted within the same QoS Flow.
Pending NSSAI: NSSAI provided by the Serving PLMN during a Registration procedure, indicating the S-NSSAI(s) for which the network slice-specific authentication and authorization procedure is pending.
Periodic Registration Update: UE re-registration at expiry of periodic registration timer as specified in clause 5.3.2.
Personal IoT Network (PIN): A network with group of elements (i.e. UE or non-3GPP device) that are able to communicate with each other directly, communicate with each other via intermediate element(s), communicate with each other via 5GS, or communicate with external DN via 5GS.
PIN Element (PINE): A UE or non-3GPP device that is part of the group of elements in a PIN.
PIN Element with Gateway Capability (PEGC): A PINE with the ability to provide DN connectivity via the 5G network for other PINEs and/or a PINE with the ability to provide relay functionality for communication between PINEs. Only a UE is able to act as a PEGC. A PIN includes at least one PEGC.
NOTE 3: In the context of PIN, the terms PEGC and UE with PEGC capability are synonymous, therefore when the term PEGC is used, it is also intended as UE.
PIN Element with Management Capability (PEMC): A PINE with capability to manage the PIN and the management is supported by an AF if deployed. A PIN includes at least one PEMC.
NOTE 4: A UE that is a PINE may both act as PEMC and PEGC in a PIN.
PIN management traffic: The traffic among PINE, PEGC, PEMC and AF for PIN related to the management of PIN.
PIN-DN communication: The communication between PINE and DN via a PEGC and 5G network, as well as the communication between PEGC and DN via 5G network. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic towards the internet or the PIN management traffic towards the AF for PIN).
PIN direct communication: The communication without traversing 5G network between two PINEs (e.g. between a PINE and a PEGC, between a PINE and a PEMC, between a PEMC and a PEGC and between two PEGCs). The communication traverses intermediate PINE(s) or not. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic between 2 PINEs or the PIN management traffic between PINE and PEMC).
PIN indirect communication: The communication with traversing 5G network between PINEs connected to different PEGCs of the same PIN and between a PINE and a PEMC via PEGC and 5G network. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic between 2 PINEs or the PIN management traffic between PINE and PEMC).
PLMN with Disaster Condition: A PLMN to which a Disaster Condition applies.
Pre-configured 5QI: Pre-defined QoS characteristics configured in the AN and 5GC and referenced via a non-standardized 5QI value. Corresponding to Operator-specific 5QI in TS 24.501 [47].
Primary cell: as defined in TS 36.331 [51].
Primary RAT: RAT of the Master RAN node, when Dual Connectivity is used; otherwise RAT of the RAN node.
Private communication: See definition in TS 22.261 [2].
Provisioning Server: Entity that provisions network credentials and other data in the UE to enable SNPN access.
PTP domain: As defined in IEEE Std 1588 [126].
Public network integrated NPN: A non-public network deployed with the support of a PLMN.
(Radio) Access Network: See 5G Access Network.
RAT type: Identifies the transmission technology used in the access network for both 3GPP accesses and non-3GPP Accesses, for example, NR, NB-IOT, Untrusted Non-3GPP, Trusted Non-3GPP, Trusted IEEE 802.11 Non-3GPP access, Wireline, Wireline-Cable, Wireline-BBF, etc.
NR RedCap: a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type and defined to identify in the Core Network the NR when used by a UE indicating NR RedCap.
NR eRedCap: a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type and defined to identify in the Core Network the NR when used by a UE indicating NR eRedCap.
Requested NSSAI: NSSAI provided by the UE to the Serving PLMN during registration.
Residential Gateway: The Residential Gateway (RG) is a device providing, for example voice, data, broadcast video, video on demand, to other devices in customer premises.
Routing Binding Indication: Information included in a request or notification and that can be used by the SCP for discovery and associated selection to of a suitable target. See clauses 6.3.1.0 and 7.1.2
Routing Indicator: Indicator that allows together with SUCI/SUPI Home Network Identifier to route network signalling to AUSF and UDM instances capable to serve the subscriber.
RRC_IDLE, RRC_CONNECTED, RRC_INACTIVE: As defined in TS 38.331 [28] and TS 38.306 [69].
SCP Domain: A configured group of one or more SCP(s) and zero or more NF instances(s). An SCP within the group can communicate with any NF instance or SCP within the same group directly, i.e. without passing through an intermediate SCP.
Secondary RAN node: A Secondary node as defined in TS 37.340 [31].
Secondary RAT: RAT of the secondary RAN node.
Service link: As defined in TS 38.300 [27]
SNPN-enabled UE: A UE configured to use stand-alone Non-Public Networks.
SNPN access mode: A UE operating in SNPN access mode only selects stand-alone Non-Public Networks over Uu, Yt, NWu.
NOTE 5: If there are multiple instances of Uu/Yt/NWu, whether the UE is in SNPN access mode is determined for each instance independently. NWu can be either direct access via untrusted non-3GPP access or access via underlay network (see Annex D, clause D.3).
Service based interface: It represents how a set of services is provided/exposed by a given NF.
Service Continuity: The uninterrupted user experience of a service, including the cases where the IP address and/or anchoring point change.
Service Data Flow Filter: A set of packet flow header parameter values/ranges used to identify one or more of the (IP or Ethernet) packet flows constituting a Service Data Flow.
Service Data Flow Template: The set of Service Data Flow filters in a policy rule or an application identifier in a policy rule referring to an application detection filter, required for defining a Service Data Flow.
Session Continuity: The continuity of a PDU Session. For PDU Session of IPv4 or IPv6 or IPv4v6 type "session continuity" implies that the IP address is preserved for the lifetime of the PDU Session.
SMF Service Area: The collection of UPF Service Areas of all UPFs which can be controlled by one SMF.
SNPN ID: PLMN ID and NID identifying an SNPN.
(S)RTP Multiplexed Media Identification Information: Component of the Packet filter information used to identify different media flows that are transported in (S)RTP, or the (S)RTCP that controls the (S)RTP transmission, when (S)RTP, (S)RTCP and other associated protocols are multiplexed into a single IP traffic flow as specified in IETF RFC 5761 [203], IETF RFC 5764 [204], IETF RFC 7983 [205], IETF RFC 8872 [206], IETF RFC 9143 [207] and IETF RFC 9443 [208].
Stand-alone Non-Public Network: A non-public network not relying on network functions provided by a PLMN
Subscribed S-NSSAI: S-NSSAI based on subscriber information, which a UE is subscribed to use in a PLMN
Subscription Owner Standalone Non-Public Network: A Standalone Non-Public Network owning the subscription of a UE and providing subscription data to the UE via a Provisioning Server during the onboarding procedure.
Survival Time: The time that an application consuming a communication service may continue without an anticipated message.
NOTE 6: Taken from clause 3.1 of TS 22.261 [2].
Target NSSAI: NSSAI provided by the Serving PLMN to the NG-RAN to cause the NG-RAN to attempt to steer the UE to a cell supporting the Network Slices identified by the S-NSSAIs in this NSSAI. See clause 5.3.4.3.3 for more details.
Time Sensitive Communication (TSC): A communication service that supports deterministic communication (i.e. which ensures a maximum delay) and/or isochronous communication with high reliability and availability. It is about providing packet transport with QoS characteristics such as bounds on latency, loss and reliability, where end systems and relay/transmit nodes may or may not be strictly synchronized.
TSN working domain: Synchronization domain for a localized set of devices collaborating on a specific task or work function in a TSN network, corresponding to a gPTP domain defined in IEEE 802.1AS [104].
UDM Group ID: This refers to one or more UDM instances managing a specific set of SUPIs. An UDM Group consists of one or multiple UDM Sets.
UDR Group ID: This refers to one or more UDR instances managing a specific set of SUPIs. An UDR Group consists of one or multiple UDR Sets.
UE-DS-TT Residence Time: The time taken within the UE and DS-TT to forward a packet, i.e. between the ingress of the UE and the DS-TT port in the DL direction, or between the DS-TT port and the egress of the UE in the UL direction. UE-DS-TT Residence Time is provided at the time of PDU Session Establishment by the UE to the network.
NOTE 7: UE-DS-TT Residence Time is the same for uplink and downlink traffic and applies to all QoS Flows.
UE-Satellite-UE (UE-SAT-UE) communication: It refers to the specific case of communication between UEs under the coverage of the same or different serving satellites, using satellite access where the user traffic is transferred between the UEs without transiting through the ground segment.
UPF Service Area: An area consisting of one or more TA(s) within which PDU Session associated with the UPF can be served by (R)AN nodes via a N3 interface between the (R)AN and the UPF without need to add a new UPF in between or to remove/re-allocate the UPF.
Uplink Classifier: UPF functionality that aims at diverting Uplink traffic, based on filter rules provided by SMF, towards Data Network.
WB-E-UTRA: In the RAN, WB-E-UTRA is the part of E-UTRA that excludes NB-IoT. In the Core Network, WB-E-UTRA also excludes LTE-M.
Wireline 5G Access Network: The Wireline 5G Access Network (W-5GAN) is a wireline AN that connects to a 5GC via N2 and N3 reference points. The W-5GAN can be either a W-5GBAN or W-5GCAN.
Wireline 5G Cable Access Network: The Wireline 5G Cable Access Network (W-5GCAN) is the Access Network defined in CableLabs.
Wireline BBF Access Network: The Wireline 5G BBF Access Network (W-5GBAN) is the Access Network defined in BBF.
Wireline Access Gateway Function (W-AGF): The Wireline Access Gateway Function (W-AGF) is a Network function in W-5GAN that provides connectivity to the 5G Core to 5G-RG and FN-RG.
NOTE 8: If one AUSF/PCF/UDR/UDM group consists of multiple AUSF/PCF/UDR/UDM Sets, AUSF/PCF/UDR/UDM instance from different Set may be selected to serve the same UE. The temporary data which is not shared across different Sets may be lost, e.g. the event subscriptions stored at one UDM instance are lost if another UDM instance from different Set is selected and no data shared across the UDM Sets. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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 [1].
5GC 5G Core Network
5G DDNMF 5G Direct Discovery Name Management Function
5G LAN 5G Local Area Network
5GS 5G System
5G-AN 5G Access Network
5G-AN PDB 5G Access Network Packet Delay Budget
5G-EIR 5G-Equipment Identity Register
5G-GUTI 5G Globally Unique Temporary Identifier
5G-BRG 5G Broadband Residential Gateway
5G-CRG 5G Cable Residential Gateway
5G GM 5G Grand Master
5G NSWO 5G Non-Seamless WLAN offload
5G-RG 5G Residential Gateway
5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier
5G VN 5G Virtual Network
5QI 5G QoS Identifier
ADRF Analytics Data Repository Function
AF Application Function
AI/ML Artificial Intelligence/Machine Learning
AKMA Authentication and Key Management for Applications
AnLF Analytics Logical Function
AMF Access and Mobility Management Function
AoI Area of Interest
AS Access Stratum
ATSSS Access Traffic Steering, Switching, Splitting
ATSSS-LL ATSSS Low-Layer
AUSF Authentication Server Function
BMCA Best Master Clock Algorithm
BSF Binding Support Function
CAG Closed Access Group
CAPIF Common API Framework for 3GPP northbound APIs
CH Credentials Holder
CHF Charging Function
CN PDB Core Network Packet Delay Budget
CP Control Plane
CQRCI Clock Quality Reporting Control Information
DAPS Dual Active Protocol Stacks
DCCF Data Collection Coordination Function
DCS Default Credentials Server
DetNet Deterministic Networking
DL Downlink
DN Data Network
DNAI DN Access Identifier
DNN Data Network Name
DRX Discontinuous Reception
DS-TT Device-side TSN translator
EAC Early Admission Control
EIF Energy Information Function
ePDG evolved Packet Data Gateway
EBI EPS Bearer Identity
EUI Extended Unique Identifier
FAR Forwarding Action Rule
FL Federated Learning
FN-BRG Fixed Network Broadband RG
FN-CRG Fixed Network Cable RG
FN-RG Fixed Network RG
FQDN Fully Qualified Domain Name
GBA Generic Bootstrapping Architecture
GBRSS Guaranteed Bit Rate Streaming Service
GEO Geostationary Orbit
GFBR Guaranteed Flow Bit Rate
GIN Group ID for Network Selection
GMLC Gateway Mobile Location Centre
GPSI Generic Public Subscription Identifier
GUAMI Globally Unique AMF Identifier
HMTC High-Performance Machine-Type Communications
HR Home Routed (roaming)
IAB Integrated access and backhaul
IMEI/TAC IMEI Type Allocation Code
IPUPS Inter PLMN UP Security
I-SMF Intermediate SMF
I-UPF Intermediate UPF
LADN Local Area Data Network
LBO Local Break Out (roaming)
LEO Low Earth Orbit
LMF Location Management Function
LoA Level of Automation
LPP LTE Positioning Protocol
LRF Location Retrieval Function
L4S Low Latency, Low Loss and Scalable Throughput
MBS Multicast/Broadcast Service
MBSF Multicast/Broadcast Service Function
MBSR Mobile Base Station Relay
MBSTF Multicast/Broadcast Service Transport Function
MB-SMF Multicast/Broadcast Session Management Function
MB-UPF Multicast/Broadcast User Plane Function
MEO Medium Earth Orbit
MFAF Messaging Framework Adaptor Function
MCX Mission Critical Service
MDBV Maximum Data Burst Volume
MFBR Maximum Flow Bit Rate
MICO Mobile Initiated Connection Only
MINT Minimization of Service Interruption
ML Machine Learning
MPQUIC Multi-Path QUIC
MPS Multimedia Priority Service
MPTCP Multi-Path TCP Protocol
MTLF Model Training Logical Function
MWAB Mobile gNB with wireless access backhauling
N3IWF Non-3GPP InterWorking Function
N3QAI Non-3GPP QoS Assistance Information
N5CW Non-5G-Capable over WLAN
NAI Network Access Identifier
NAT Network Address Translation
NCR Network Controlled Repeater
NCR-MT NCR Mobile Termination
NEF Network Exposure Function
NF Network Function
NGAP Next Generation Application Protocol
NID Network identifier
NPN Non-Public Network
NR New Radio
NRF Network Repository Function
NS-AoS Network Slice Area of Service
NSAC Network Slice Admission Control
NSACF Network Slice Admission Control Function
NSAG Network Slice AS Group
NSI ID Network Slice Instance Identifier
NSSAA Network Slice-Specific Authentication and Authorization
NSSAAF Network Slice-specific and SNPN Authentication and Authorization Function
NSSAI Network Slice Selection Assistance Information
NSSF Network Slice Selection Function
NSSP Network Slice Selection Policy
NSSRG Network Slice Simultaneous Registration Group
NSWO Non-Seamless WLAN offload
NSWOF Non-Seamless WLAN offload Function
NW-TT Network-side TSN translator
NWDAF Network Data Analytics Function
ONN Onboarding Network
ON-SNPN Onboarding Standalone Non-Public Network
PCF Policy Control Function
PDB Packet Delay Budget
PDR Packet Detection Rule
PDU Protocol Data Unit
PDV Packet Delay Variation
PEGC PIN Element with Gateway Capability
PEI Permanent Equipment Identifier
PEMC PIN Element with Management Capability
PER Packet Error Rate
PFD Packet Flow Description
PIN Personal IoT Network
PINE PIN Element
PLR Packet Loss Rate
PNI-NPN Public Network Integrated Non-Public Network
PPD Paging Policy Differentiation
PPF Paging Proceed Flag
PPI Paging Policy Indicator
PSA PDU Session Anchor
PSDB PDU Set Delay Budget
PSER PDU Set Error Rate
PSIHI PDU Set Integrated Handling Information
PTP Precision Time Protocol
PVS Provisioning Server
QFI QoS Flow Identifier
QMC QoE Measurement Collection
QoE Quality of Experience
RACS Radio Capabilities Signalling optimisation
(R)AN (Radio) Access Network
RG Residential Gateway
RIM Remote Interference Management
RQA Reflective QoS Attribute
RQI Reflective QoS Indication
RSN Redundancy Sequence Number
RTT Round Trip Time
SA NR Standalone New Radio
SBA Service Based Architecture
SBI Service Based Interface
SCP Service Communication Proxy
SD Slice Differentiator
SEAF Security Anchor Functionality
SEPP Security Edge Protection Proxy
SF Service Function
SFC Service Function Chain
SMF Session Management Function
SMSF Short Message Service Function
SN Sequence Number
SNPN Stand-alone Non-Public Network
S-NSSAI Single Network Slice Selection Assistance Information
SO-SNPN Subscription Owner Standalone Non-Public Network
SSC Session and Service Continuity
SSCMSP Session and Service Continuity Mode Selection Policy
SST Slice/Service Type
SUCI Subscription Concealed Identifier
SUPI Subscription Permanent Identifier
SV Software Version
TA Tracking Area
TAI Tracking Area Identity
TNAN Trusted Non-3GPP Access Network
TNAP Trusted Non-3GPP Access Point
TNGF Trusted Non-3GPP Gateway Function
TNL Transport Network Layer
TNLA Transport Network Layer Association
TSC Time Sensitive Communication
TSCAC TSC Assistance Container
TSCAI Traffic Assistance Information
TSCTSF Time Sensitive Communication and Time Synchronization Function
TSN Time Sensitive Networking
TSN GM TSN Grand Master
TSP Traffic Steering Policy
TSS Timing Synchronization Status
TT TSN Translator
TWIF Trusted WLAN Interworking Function
UAS NF Uncrewed Aerial System Network Function
UCMF UE radio Capability Management Function
UDM Unified Data Management
UDR Unified Data Repository
UDSF Unstructured Data Storage Function
UL Uplink
UL CL Uplink Classifier
UPF User Plane Function
URLLC Ultra Reliable Low Latency Communication
URRP-AMF UE Reachability Request Parameter for AMF
URSP UE Route Selection Policy
VID VLAN Identifier
VLAN Virtual Local Area Network
W-5GAN Wireline 5G Access Network
W-5GBAN Wireline BBF Access Network
W-5GCAN Wireline 5G Cable Access Network
W-AGF Wireline Access Gateway Function |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4 Architecture model and concepts | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.1 General concepts | The 5G System architecture is defined to support data connectivity and services enabling deployments to use techniques such as e.g. Network Function Virtualization and Software Defined Networking. The 5G System architecture shall leverage service-based interactions between Control Plane (CP) Network Functions where identified. Some key principles and concept are to:
- Separate the User Plane (UP) functions from the Control Plane (CP) functions, allowing independent scalability, evolution and flexible deployments e.g. centralized location or distributed (remote) location.
- Modularize the function design, e.g. to enable flexible and efficient network slicing.
- Wherever applicable, define procedures (i.e. the set of interactions between network functions) as services, so that their re-use is possible.
- Enable each Network Function and its Network Function Services to interact with other NF and its Network Function Services directly or indirectly via a Service Communication Proxy if required. The architecture does not preclude the use of another intermediate function to help route Control Plane messages (e.g. like a DRA).
- Minimize dependencies between the Access Network (AN) and the Core Network (CN). The architecture is defined with a converged core network with a common AN - CN interface which integrates different Access Types e.g. 3GPP access and non-3GPP access.
- Support a unified authentication framework.
- Support "stateless" NFs, where the "compute" resource is decoupled from the "storage" resource.
- Support capability exposure.
- Support concurrent access to local and centralized services. To support low latency services and local access to data networks, UP functions can be deployed close to the Access Network.
- Support roaming with both Home routed traffic as well as Local breakout traffic in the visited PLMN. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2 Architecture reference model | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.1 General | This specification describes the architecture for the 5G System. The 5G architecture is defined as service-based and the interaction between network functions is represented in two ways.
- A service-based representation, where network functions (e.g. AMF) within the Control Plane enables other authorized network functions to access their services. This representation also includes point-to-point reference points where necessary.
- A reference point representation, shows the interaction exist between the NF services in the network functions described by point-to-point reference point (e.g. N11) between any two network functions (e.g. AMF and SMF).
Service-based interfaces are listed in clause 4.2.6. Reference points are listed in clause 4.2.7.
Network functions within the 5GC Control Plane shall only use service-based interfaces for their interactions.
NOTE 1: The interactions between NF services within one NF are not specified in this Release of the specification.
NFs and NF services can communicate directly, referred to as Direct Communication, or indirectly via the SCP, referred to as Indirect Communication. For more information on communication options, see Annex E and clauses under 6.3.1 and 7.1.2.
In addition to the architecture descriptions in clause 4, the following areas are further described in other specifications:
- NG-RAN architecture is described in TS 38.300 [27] and TS 38.401 [42].
- Security architecture is described in TS 33.501 [29] and TS 33.535 [124].
- Charging architecture is described in TS 32.240 [41].
- 5G Media streaming architecture is described in TS 26.501 [135].
NOTE 3: The NFs listed in clause 4.2.2 are described in the following clauses or in the specifications above. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.2 Network Functions and entities | The 5G System architecture consists of the following network functions (NF):
- Authentication Server Function (AUSF).
- Access and Mobility Management Function (AMF).
- Data Network (DN), e.g. operator services, Internet access or 3rd party services.
- Unstructured Data Storage Function (UDSF).
- Network Exposure Function (NEF).
- Network Repository Function (NRF).
- Network Slice Admission Control Function (NSACF).
- Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF).
- Network Slice Selection Function (NSSF).
- Policy Control Function (PCF).
- Session Management Function (SMF).
- Unified Data Management (UDM).
- Unified Data Repository (UDR).
- User Plane Function (UPF).
- UE radio Capability Management Function (UCMF).
- Application Function (AF).
- User Equipment (UE).
- (Radio) Access Network ((R)AN).
- 5G-Equipment Identity Register (5G-EIR).
- Network Data Analytics Function (NWDAF).
- CHarging Function (CHF).
- Time Sensitive Networking AF (TSN AF).
- Time Sensitive Communication and Time Synchronization Function (TSCTSF).
- Data Collection Coordination Function (DCCF).
- Analytics Data Repository Function (ADRF).
- Messaging Framework Adaptor Function (MFAF).
- Non-Seamless WLAN Offload Function (NSWOF).
NOTE: The functionalities provided by DCCF and/or ADRF can also be hosted by an NWDAF.
- Edge Application Server Discovery Function (EASDF).
The 5G System architecture also comprises the following network entities:
- Service Communication Proxy (SCP).
- Security Edge Protection Proxy (SEPP).
The functional descriptions of these Network Functions and entities are specified in clause 6.
- Non-3GPP InterWorking Function (N3IWF).
- Trusted Non-3GPP Gateway Function (TNGF).
- Wireline Access Gateway Function (W-AGF).
- Trusted WLAN Interworking Function (TWIF).
- Energy Information Function (EIF). |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.3 Non-roaming reference architecture | Figure 4.2.3-1 depicts the non-roaming reference architecture. Service-based interfaces are used within the Control Plane.
Figure 4.2.3-1: Non-Roaming 5G System Architecture
NOTE: If an SCP is deployed it can be used for indirect communication between NFs and NF services as described in Annex E. SCP does not expose services itself.
Figure 4.2.3-2 depicts the 5G System architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other.
Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation
NOTE 1: N9, N14 are not shown in all other figures however they may also be applicable for other scenarios.
NOTE 2: For the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary.
NOTE 3: The UDM uses subscription data and authentication data and the PCF uses policy data that may be stored in UDR (refer to clause 4.2.5).
NOTE 4: For clarity, the UDR and its connections with other NFs, e.g. PCF, are not depicted in the point-to-point and service-based architecture diagrams. For more information on data storage architectures refer to clause 4.2.5.
NOTE 5: For clarity, the NWDAF(s), DCCF, MFAF and ADRF and their connections with other NFs, are not depicted in the point-to-point and service-based architecture diagrams. For more information on network data analytics architecture refer to TS 23.288 [86].
NOTE 6: For clarity, the 5G DDNMF and its connections with other NFs, e.g. UDM, PCF are not depicted in the point-to-point and service-based architecture diagrams. For more information on ProSe architecture refer to TS 23.304 [128].
NOTE 7: For clarity, the TSCTSF and its connections with other NFs, e.g. PCF, NEF, UDR are not depicted in the point-to-point and service-based architecture diagrams. For more information on TSC architecture refer to clause 4.4.8.
NOTE 8: For exposure of the QoS monitoring information as specified in clause 5.8.2.18, exposure of data collected for analytics as specified in clause 5.2.26.2 of TS 23.502 [3] and exposure of the TSC management information as specified in clause 5.8.5.14, direct interaction between UPF and NFs can be supported via the Nupf interface (see clause 4.2.16).
NOTE 9: For clarity, the EASDF and its connections with SMF is not depicted in the point-to-point and service-based architecture diagrams. For more information on edge computing architecture refer to TS 23.548 [130].
Subscription-based routing to a particular core network as specified in clause 6.44 of TS 22.261 [2] enables forwarding of the signalling and user traffic of certain UEs to a target (partner) PLMN that is not the HPLMN of the UE. This is achieved by selecting NFs residing in the target PLMN. The NRF of the HPLMN, with optional support of the NRF in that target PLMN as specified in clause 4.17.4 of TS 23.502 [3], is responsible to provide proper network function instance information during network function discovery and selection.
Figure 4.2.3-3 depicts the non-roaming architecture for UEs concurrently accessing two (e.g. local and central) data networks using multiple PDU Sessions, using the reference point representation. This figure shows the architecture for multiple PDU Sessions where two SMFs are selected for the two different PDU Sessions. However, each SMF may also have the capability to control both a local and a central UPF within a PDU Session.
Figure 4.2.3-3: Applying Non-Roaming 5G System Architecture for multiple PDU Session in reference point representation
Figure 4.2.3-4 depicts the non-roaming architecture in the case of concurrent access to two (e.g. local and central) data networks is provided within a single PDU Session, using the reference point representation.
Figure 4.2.3-4: Applying Non-Roaming 5G System Architecture for concurrent access to two (e.g. local and central) data networks (single PDU Session option) in reference point representation
Figure 4.2.3-5 depicts the non-roaming architecture for Network Exposure Function, using reference point representation.
Figure 4.2.3-5: Non-Roaming Architecture for Network Exposure Function in reference point representation
NOTE 1: In Figure 4.2.3-5, Trust domain for NEF is same as Trust domain for SCEF as defined in TS 23.682 [36].
NOTE 2: In Figure 4.2.3-5, 3GPP Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.4 Roaming reference architectures | Figure 4.2.4-1 depicts the 5G System roaming architecture with local breakout with service-based interfaces within the Control Plane.
Figure 4.2.4-1: Roaming 5G System architecture- local breakout scenario in service-based interface representation
NOTE 1: In the LBO architecture. the PCF in the VPLMN may interact with the AF in order to generate PCC Rules for services delivered via the VPLMN, the PCF in the VPLMN uses locally configured policies according to the roaming agreement with the HPLMN operator as input for PCC Rule generation, the PCF in VPLMN has no access to subscriber policy information from the HPLMN.
NOTE 2: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture.
NOTE 3: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288 [86].
NOTE 4: Depending on the architecture deployed, the Primary or Centralized NSACF at the VPLMN can fetch the maximum number of registered UEs or the maximum number of LBO PDU sessions to be enforced from the HPLMN Primary or Centralized NSACF as described in clause 5.15.11.3.1.
Figure 4.2.4-2: Void
Figure 4.2.4-3 depicts the 5G System roaming architecture in the case of home routed scenario with service-based interfaces within the Control Plane.
Figure 4.2.4-3: Roaming 5G System architecture - home routed scenario in service-based interface representation
NOTE 5: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture.
NOTE 6: UPFs in the home routed scenario can be used also to support the IPUPS functionality (see clause 5.8.2.14).
NOTE 7: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288 [86].
NOTE 8: In the home routed scenario, the H-UPF operated by HPLMN operator can be deployed nearby VPLMN. (see Annex U).
Figure 4.2.4-4 depicts 5G System roaming architecture in the case of local break out scenario using the reference point representation.
Figure 4.2.4-4: Roaming 5G System architecture - local breakout scenario in reference point representation
NOTE 7: The NRF is not depicted in reference point architecture figures. Refer to Figure 4.2.4-7 for details on NRF and NF interfaces.
NOTE 8: For the sake of clarity, SEPPs are not depicted in the roaming reference point architecture figures.
NOTE 9: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288 [86].
The following figure 4.2.4-6 depicts the 5G System roaming architecture in the case of home routed scenario using the reference point representation.
Figure 4.2.4-6: Roaming 5G System architecture - Home routed scenario in reference point representation
The N38 references point can be between V-SMFs in the same VPLMN, or between V-SMFs in different VPLMNs (to enable inter-PLMN mobility).
NOTE 10: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288 [86].
For the roaming scenarios described above each PLMN implements proxy functionality to secure interconnection and hide topology on the inter-PLMN interfaces.
Subscription-based routing to a particular core network as specified in clause 6.44 of TS 22.261 [2] enables forwarding of the signalling and user traffic of certain UEs to a target PLMN that may be neither the serving PLMN nor the HPLMN of the UE. This is achieved by selecting NFs residing in the target PLMN. The NRF of the HPLMN, with optional support of the NRF in that target PLMN as specified in clause 4.17.5 of TS 23.502 [3], is responsible to provide proper network function instance information during network function discovery and selection.
Figure 4.2.4-7: NRF Roaming architecture in reference point representation
NOTE 11: For the sake of clarity, SEPPs on both sides of PLMN borders are not depicted in figure 4.2.4-7.
Figure 4.2.4-8: Void
Operators can deploy UPFs supporting the Inter PLMN UP Security (IPUPS) functionality at the border of their network to protect their network from invalid inter PLMN N9 traffic in home routed roaming scenarios. The UPFs supporting the IPUPS functionality in VPLMN and HPLMN are controlled by the V-SMF and the H-SMF of that PDU Session respectively. A UPF supporting the IPUPS functionality terminates GTP-U N9 tunnels. The SMF can activate the IPUPS functionality together with other UP functionality in the same UPF, or insert a separate UPF for the IPUPS functionality in the UP path (which e.g. may be dedicated to be used for IPUPS functionality). Figure 4.2.4-9 depicts the home routed roaming architecture where a UPF is inserted in the UP path for the IPUPS functionality. Figure 4.2.4-3 depicts the home routed roaming architecture where the two UPFs perform the IPUPS functionality and other UP functionality for the PDU Session.
NOTE 12: Operators are not prohibited from deploying the IPUPS functionality as a separate Network Function from the UPF, acting as a transparent proxy which can transparently read N4 and N9 interfaces. However, such deployment option is not specified and needs to take at least into account very long lasting PDU Sessions with infrequent traffic and Inter-PLMN handover.
The IPUPS functionality is specified in clause 5.8.2.14 and TS 33.501 [29].
Figure 4.2.4-9: Roaming 5G System architecture - home routed roaming scenario in service-based interface representation employing UPF dedicated to IPUPS |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.5 Data Storage architectures | As depicted in Figure 4.2.5-1, the 5G System architecture allows any NF to create/read/update/delete its unstructured data in a UDSF (e.g. UE contexts). If such an NF is using UDSF is part of an NF set, then any of the NF instance within this NF set may read/update/delete the unstructured data that was created by this NF. The UDSF belongs to the same PLMN where the network function is located. CP NFs/NF Sets may share a UDSF for storing their respective unstructured data or may each have their own UDSF (e.g. a UDSF may be located close to the respective NF).
NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications.
NOTE 2: If a NF Set has its own UDSF, it is up to UDSF implementation and deployment that only the NF instance within the set can access the data created by another NF instance within the NF set. If a UDSF is shared between several NFs not part of the same set or is shared between several NF sets, it is up to UDSF implementation and deployment to make sure that only NFs that are authorized can access the data. For further information about Guidelines and Principles for Compute-Storage Separation see Annex C.
Figure 4.2.5-1: Data Storage Architecture for unstructured data from any NF
NOTE 3: 3GPP will specify (possibly by referencing) the N18/Nudsf interface.
As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF. UDR can be deployed in each PLMN and it can serve different functions as follows:
- UDR accessed by the NEF belongs to the same PLMN where the NEF is located.
- UDR accessed by the UDM belongs to the same PLMN where the UDM is located if UDM supports a split architecture.
- UDR accessed by the PCF belongs to the same PLMN where the PCF is located.
NOTE 4: The UDR deployed in each PLMN can store application data for roaming subscribers.
Figure 4.2.5-2: Data Storage Architecture
NOTE 5: There can be multiple UDRs deployed in the network, each of which can accommodate different data sets or subsets, (e.g. subscription data, subscription policy data, data for exposure, application data) and/or serve different sets of NFs. Deployments where a UDR serves a single NF and stores its data and, thus, can be integrated with this NF, can be possible.
NOTE 6: The internal structure of the UDR in figure 4.2.5-2 is shown for information only.
The Nudr interface is defined for the network functions (i.e. NF Service Consumers), such as UDM, PCF and NEF, to access a particular set of the data stored and to read, update (including add, modify), delete and subscribe to notification of relevant data changes in the UDR.
Each NF Service Consumer accessing the UDR, via Nudr, shall be able to add, modify, update or delete only the data it is authorised to change. This authorisation shall be performed by the UDR on a per data set and NF service consumer basis and potentially on a per UE, subscription granularity.
The following data in the UDR sets exposed via Nudr to the respective NF service consumer and stored shall be standardized:
- Subscription Data,
- Policy Data,
- Structured Data for exposure,
- Application data: Packet Flow Descriptions (PFDs) for application detection and AF request information for multiple UEs, as defined in clause 5.6.7.
The service based Nudr interface defines the content and format/encoding of the 3GPP defined information elements exposed by the data sets.
In addition, it shall be possible to access operator specific data sets by the NF Service Consumers from the UDR as well as operator specific data for each data set.
NOTE 7: The content and format/encoding of operator specific data and operator specific data sets are not subject to standardization.
NOTE 8: The organization of the different data stored in the UDR is not to be standardized.
4.2.5a Radio Capabilities Signalling optimisation
Figure 4.2.5a-1 depicts the AMF to UCMF reference point and interface. Figure 4.2.5a-2 depicts the related interfaces in AMF and UCMF for the Radio Capabilities Signalling optimisation in the roaming architecture.
Figure 4.2.5a-1: Radio Capability Signalling optimisation architecture
NOTE: The AF in the VPLMN (i.e. the one having a relationship with the VPLMN NEF) is the one which provisions Manufacturer Assigned UE radio capability IDs in the VPLMN UCMF. RACS is a serving PLMN only feature (it requires no specific support in the roaming agreement with the UE HPLMN to operate).
Figure 4.2.5a-2: Roaming architecture for Radio Capability Signalling optimisation |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.6 Service-based interfaces | The 5G System Architecture contains the following service-based interfaces:
Namf: Service-based interface exhibited by AMF.
Nsmf: Service-based interface exhibited by SMF.
Nnef: Service-based interface exhibited by NEF.
Npcf: Service-based interface exhibited by PCF.
Nudm: Service-based interface exhibited by UDM.
Naf: Service-based interface exhibited by AF.
Nnrf: Service-based interface exhibited by NRF.
Nnsacf: Service-based interface exhibited by NSACF.
Nnssaaf: Service-based interface exhibited by NSSAAF.
Nnssf: Service-based interface exhibited by NSSF.
Nausf: Service-based interface exhibited by AUSF.
Nudr: Service-based interface exhibited by UDR.
Nudsf: Service-based interface exhibited by UDSF.
N5g-eir: Service-based interface exhibited by 5G-EIR.
Nnwdaf: Service-based interface exhibited by NWDAF.
Nchf: Service-based interface exhibited by CHF.
Nucmf: Service-based interface exhibited by UCMF.
Ndccf: Service based interface exhibited by DCCF.
Nmfaf: Service based interface exhibited by MFAF.
Nadrf: Service based interface exhibited by ADRF.
Naanf: Service-based interface exhibited by AANF.
NOTE 1: The Service-based interface exhibited by AANF is defined in TS 33.535 [124].
N5g-ddnmf: Service-based interface exhibited by 5G DDNMF.
Nmbsmf: Service-based interface exhibited by MB-SMF.
Nmbsf: Service-based interface exhibited by MBSF.
NOTE 2: The Service-based interfaces exhibited by MB-SMF and MBSF are defined in TS 23.247 [129].
Ntsctsf: Service-based interface exhibited by TSCTSF.
Nbsp: Service-based interface exhibited by an SBI capable Boostrapping Server Function in GBA.
NOTE 2: The Service-based interfaces exhibited by an SBI capable Boostrapping Server Function are defined in TS 33.220 [140] and TS 33.223 [141].
Neasdf: Service-based interface exhibited by EASDF.
NOTE 3: The Service-based interfaces exhibited by EADSF is defined in TS 23.548 [130].
Nupf: Service-based interface exhibited by UPF.
Neif: Service-based interface exhibited by EIF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.7 Reference points | The 5G System Architecture contains the following reference points:
N1: Reference point between the UE and the AMF.
N2: Reference point between the (R)AN and the AMF.
N3: Reference point between the (R)AN and the UPF.
N4: Reference point between the SMF and the UPF.
N6: Reference point between the UPF and a Data Network.
N9: Reference point between two UPFs.
The following reference points show the interactions that exist between the NF services in the NFs. These reference points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure.
N5: Reference point between the PCF and an AF or TSN AF.
N7: Reference point between the SMF and the PCF.
N8: Reference point between the UDM and the AMF.
N10: Reference point between the UDM and the SMF.
N11: Reference point between the AMF and the SMF.
N12: Reference point between AMF and AUSF.
N13: Reference point between the UDM and Authentication Server function the AUSF.
N14: Reference point between two AMFs.
N15: Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario.
N16: Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network).
N16a: Reference point between SMF and I-SMF.
N17: Reference point between AMF and 5G-EIR.
N18: Reference point between any NF and UDSF.
N19: Reference point between two PSA UPFs for 5G LAN-type service.
N22: Reference point between AMF and NSSF.
N23: Reference point between PCF and NWDAF.
N24: Reference point between the PCF in the visited network and the PCF in the home network.
N27: Reference point between NRF in the visited network and the NRF in the home network.
N28: Reference point between PCF and CHF.
N29: Reference point between NEF and SMF.
N30: Reference point between PCF and NEF.
NOTE 1: The functionality of N28 and N29 and N30 reference points are defined in TS 23.503 [45].
N31: Reference point between the NSSF in the visited network and the NSSF in the home network.
NOTE 2: In some cases, a couple of NFs may need to be associated with each other to serve a UE.
N32: Reference point between a SEPP in one PLMN or SNPN and a SEPP in another PLMN or SNPN; or between a SEPP in a SNPN and a SEPP in a CH/DCS, where the CH/DCS contains a UDM/AUSF.
NOTE 3: The functionality of N32 reference point is defined in TS 33.501 [29].
N33: Reference point between NEF and AF.
N34: Reference point between NSSF and NWDAF.
N35: Reference point between UDM and UDR.
N36: Reference point between PCF and UDR.
N37: Reference point between NEF and UDR.
N38: Reference point between I-SMFs and between V-SMFs.
N40: Reference point between SMF and the CHF.
N41: Reference point between AMF and CHF in HPLMN.
N42: Reference point between AMF and CHF in VPLMN.
NOTE 4: The functionality of N40, N41 and N42 reference points are defined in TS 32.240 [41].
N43: Reference point between PCFs.
NOTE 5: The functionality of N43 reference point is defined in TS 23.503 [45].
NOTE 6: The reference points from N44 up to and including N49 are reserved for allocation and definition in TS 32.240 [41].
N50: Reference point between AMF and the CBCF.
N51: Reference point between AMF and NEF.
N52: Reference point between NEF and UDM.
N55: Reference point between AMF and the UCMF.
N56: Reference point between NEF and the UCMF.
N57: Reference point between AF and the UCMF.
NOTE 7: The Public Warning System functionality of N50 reference point is defined in TS 23.041 [46].
N58: Reference point between AMF and the NSSAAF.
N59: Reference point between UDM and the NSSAAF.
N60: Reference point between AUSF and NSWOF.
NOTE 8: The functionality of N60 reference point is defined in TS 33.501 [29].
N80: Reference point between AMF and NSACF.
N81: Reference point between SMF and NSACF.
N82: Reference point between NSACF and NEF.
N83: Reference point between AUSF and NSSAAF.
N84: Reference point between TSCTSF and PCF.
N85: Reference point between TSCTSF and NEF.
N86: Reference point between TSCTSF and AF.
N87: Reference point between TSCTSF and UDM.
N88: Reference point between SMF and EASDF.
N88a: Reference point between I-SMF and EASDF.
N89: Reference point between TSCTSF and AMF.
N96: Reference point between TSCTSF and NRF.
N97: Reference point between two NSACFs in different PLMNs.
N99: Reference point between two NSACFs within the same PLMN.
N110: Reference point between EIF and AF.
N111: Reference point between EIF and NEF.
N112: Reference point between EIF and UDM.
N113: Reference point between EIF and PCF.
N114: Reference point between EIF and SMF.
NOTE 9: The reference points from N90 up to and including N95 are reserved for allocation and definition in TS 23.503 [45].
NOTE 10: The reference points from N100 up to and including N109 are reserved for allocation and definition in TS 32.240 [41].
The reference points to support SMS over NAS are listed in clause 4.4.2.2.
The reference points to support Location Services are listed in TS 23.273 [87].
The reference points to support SBA in IMS (N5, N70 and N71) are described in TS 23.228 [15].
The reference points to support AKMA (N61, N62 and N63) are described in TS 33.535 [124].
The reference points to support 5G ProSe are described in TS 23.304 [128].
The reference points to support 5G multicast-broadcast services are described in TS 23.247 [129].
The reference points to Support Uncrewed Aerial Systems (UAS) connectivity, identification and tracking are described in TS 23.256 [136].
The reference points to support SBA in GBA and GBA push (N65, N66, N67 and N68) are described in TS 33.220 [140] and TS 33.223 [141].
The reference points to support SMS delivery using SBA are described in TS 23.540 [142].
The reference points to support Ranging based services and Sidelink Positioning are described in TS 23.586 [180]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8 Support of non-3GPP access | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.0 General | In this Release of the specification, the following types of non-3GPP access networks are defined:
- Untrusted non-3GPP access networks;
- Trusted non-3GPP access networks; and
- Wireline access networks.
The architecture to support Untrusted and Trusted non-3GPP access networks is defined in clause 4.2.8.2. The architecture to support Wireline access networks is defined in clause 4.2.8.2.4 and in TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access | The 5G Core Network supports connectivity of UEs via non-3GPP access networks, e.g. WLAN access networks.
Only the support of non-3GPP access networks deployed outside the NG-RAN is described in this clause.
The 5G Core Network supports both untrusted non-3GPP access networks and trusted non-3GPP access networks (TNANs).
An untrusted non-3GPP access network shall be connected to the 5G Core Network via a Non-3GPP InterWorking Function (N3IWF), whereas a trusted non-3GPP access network shall be connected to the 5G Core Network via a Trusted Non-3GPP Gateway Function (TNGF). Both the N3IWF and the TNGF interface with the 5G Core Network CP and UP functions via the N2 and N3 interfaces, respectively.
A non-3GPP access network may advertise the PLMNs or SNPNs for which it supports trusted connectivity and the type of supported trusted connectivity (e.g. "5G connectivity"). Therefore, the UEs can discover the non-3GPP access networks that can provide trusted connectivity to one or more PLMNs or SNPNs. This is further specified in clause 6.3.12 (Trusted Non-3GPP Access Network selection).
The UE decides to use trusted or untrusted non-3GPP access for connecting to a 5G PLMN or SNPNs by using procedures not specified in this document. Examples of such procedures are defined in clause 6.3.12.1.
When the UE decides to use untrusted non-3GPP access to connect to a 5G Core Network in a PLMN:
- the UE first selects and connects with a non-3GPP access network; and then
- the UE selects a PLMN/SNPN and an N3IWF in this PLMN/SNPN. The PLMN/SNPN/N3IWF selection and the non-3GPP access network selection are independent. The N3IWF selection is defined in clause 6.3.6.
When the UE decides to use trusted non-3GPP access to connect to a 5G Core Network in a PLMN:
- the UE first selects a PLMN/SNPN; and then
- the UE selects a non-3GPP access network (a TNAN) that supports trusted connectivity to the selected PLMN/SNPN. In this case, the non-3GPP access network selection is affected by the PLMN/SNPN selection.
A UE that accesses the 5G Core Network over a non-3GPP access shall, after UE registration, support NAS signalling with 5G Core Network control-plane functions using the N1 reference point.
When a UE is connected via a NG-RAN and via a non-3GPP access, multiple N1 instances shall exist for the UE i.e. there shall be one N1 instance over NG-RAN and one N1 instance over non-3GPP access.
A UE simultaneously connected to the same 5G Core Network of a PLMN/SNPN over a 3GPP access and a non-3GPP access shall be served by a single AMF in this 5G Core Network.
When a UE is connected to a 3GPP access of a PLMN, if the UE selects a N3IWF and the N3IWF is located in a PLMN different from the PLMN of the 3GPP access, e.g. in a different VPLMN or in the HPLMN, the UE is served separately by the two PLMNs. The UE is registered with two separate AMFs. PDU Sessions over the 3GPP access are served by V-SMFs different from the V-SMF serving the PDU Sessions over the non-3GPP access. The same can be true when the UE uses trusted non-3GPP access, i.e. the UE may select one PLMN for 3GPP access and a different PLMN for trusted non-3GPP access.
NOTE: The registrations with different PLMNs over different Access Types doesn't apply to UE registered for Disaster Roaming service as described in the clause 5.40.
The PLMN selection for the 3GPP access does not depend on the PLMN that is used for non-3GPP access. In other words, if a UE is registered with a PLMN over a non-3GPP access, the UE performs PLMN selection for the 3GPP access independently of this PLMN.
A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5G Core Network over non-3GPP access. Further details about the UE registration to 5G Core Network over untrusted non-3GPP access and over trusted non-3GPP access are described in clause 4.12.2 and in clause 4.12.2a of TS 23.502 [3], respectively.
It shall be possible to maintain the UE NAS signalling connection with the AMF over the non-3GPP access after all the PDU Sessions for the UE over that access have been released or handed over to 3GPP access.
N1 NAS signalling over non-3GPP accesses shall be protected with the same security mechanism applied for N1 over a 3GPP access.
User plane QoS differentiation between UE and N3IWF is supported as described in clause 5.7 and clause 4.12.5 of TS 23.502 [3]. QoS differentiation between UE and TNGF is supported as described in clause 5.7 and clause 4.12a.5 of TS 23.502 [3].
4.2.8.1A General Concepts to support Wireline Access
Wireline 5G Access Network (W-5GAN) shall be connected to the 5G Core Network via a Wireline Access Gateway Function (W-AGF). The W-AGF interfaces the 5G Core Network CP and UP functions via N2 and N3 interfaces, respectively.
For the scenario of 5G-RG connected via NG RAN the specification for UE defined in this TS, TS 23.502 [3] and TS 23.503 [45] are applicable as defined for UE connected to 5GC via NG RAN unless differently specified in this TS and in TS 23.316 [84].
When a 5G-RG is connected via a NG-RAN and via a W-5GAN, multiple N1 instances shall exist for the 5G-RG i.e. there shall be one N1 instance over NG-RAN and one N1 instance over W-5GAN.
A 5G-RG simultaneously connected to the same 5G Core Network of a PLMN over a 3GPP access and a W-5GAN access shall be served by a single AMF in this 5G Core Network.
5G-RG shall maintain the NAS signalling connection with the AMF over the W-5GAN after all the PDU Sessions for the 5G-RG over that access have been released or handed over to 3GPP access.
The 5G-RG connected to 5GC via NG-RAN is specified in TS 23.316 [84].
For the scenario of FN-RG, which is not 5G capable, connected via W-5GAN to 5GC, the W-AGF provides the N1 interface to AMF on behalf of the FN-RG.
An UE connected to a 5G-RG or FN-RG can access to the 5GC via the N3IWF or via the TNGF where the combination of 5G-RG/FN-RG, W-AGF and UPF serving the 5G-RG or FN-RG is acting respectively as Untrusted Non-3GPP access network or as a Trusted Non-3GPP access network defined in clause 4.2.8.2; for example a UE is connecting to 5G-RG by means of WLAN radio access and connected to 5GC via N3IWF. The detailed description is specified in TS 23.316 [84].
The roaming architecture for 5G-BRG, FN-BRG, 5G-CRG and FN-CRG with the W-5GAN is not specified in this Release. The Home Routed roaming scenario is supported for 5G-RG connected via NG RAN, while Local Breakout scenario is not supported.
5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.2 Architecture Reference Model for Trusted and Untrusted Non-3GPP Accesses | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.2.1 Non-roaming Architecture | Figure 4.2.8.2.1-1: Non-roaming architecture for 5G Core Network with untrusted non-3GPP access
Figure 4.2.8.2.1-2: Non-roaming architecture for 5G Core Network with trusted non-3GPP access
NOTE 1: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 only shows the architecture and the network functions directly connected to non-3GPP access and other parts of the architecture are the same as defined in clause 4.2.
NOTE 2: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 supports service based interfaces for AMF, SMF and other NFs not represented in the figure.
NOTE 3: The two N2 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 terminate to a single AMF for a UE which is simultaneously connected to the same 5G Core Network over 3GPP access and non-3GPP access.
NOTE 4 The two N3 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.2.2 LBO Roaming Architecture | Figure 4.2.8.2.2-1: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access
Figure 4.2.8.2.2-2: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different PLMN from 3GPP access
Figure 4.2.8.2.2-3: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access
Figure 4.2.8.2.2-4: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using a different PLMN than 3GPP access
NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access and other parts of the architecture are the same as defined in clause 4.2.
NOTE 2: The reference architecture in all above figures supports service based interfaces for AMF, SMF and other NFs not represented in the figures.
NOTE 3: The two N2 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously.
NOTE 4: The two N3 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.2.3 Home-routed Roaming Architecture | Figure 4.2.8.2.3-1: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access
Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access
Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN
Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access
NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access and other parts of the architecture are the same as defined in clause 4.2.
NOTE 2: The two N2 instances in Figure 4.2.8.2.3-1 and in Figure 4.2.8.2.3-4 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.3 Reference Points for Non-3GPP Access | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.3.1 Overview | The description of the reference points specific for the non-3GPP access:
N2, N3, N4, N6: these are defined in clause 4.2.
Y1 Reference point between the UE and the untrusted non-3GPP access (e.g. WLAN). This depends on the non-3GPP access technology and is outside the scope of 3GPP.
Y2 Reference point between the untrusted non-3GPP access and the N3IWF for the transport of NWu traffic.
Y4 Reference point between the 5G-RG and the W-AGF which transports the user plane traffic and the N1 NAS protocol. The definition of this interface is outside the scope of 3GPP.
Y5 Reference point between the FN-RG and the W-AGF. The definition of this interface is outside the scope of 3GPP.
Yt Reference point between the UE and the TNAP. See e.g. Figure 4.2.8.2.1-2.
Yt' Reference point between the N5CW devices and the TWAP. It is defined in clause 4.2.8.5.
NWu Reference point between the UE and N3IWF for establishing secure tunnel(s) between the UE and N3IWF so that control-plane and user-plane exchanged between the UE and the 5G Core Network is transferred securely over untrusted non-3GPP access.
NWt Reference point between the UE and the TNGF. A secure NWt connection is established over this reference point, as specified in clause 4.12a.2.2 of TS 23.502 [3]. NAS messages between the UE and the AMF are transferred via this NWt connection.
Ta A reference point between the TNAP and the TNGF, which is used to support an AAA interface. Ta requirements are documented in clause 4.2.8.3.2.
Tn A reference point between two TNGFs, which is used to facilitate UE mobility between different TNGFs (inter-TNGF mobility).
Tn and inter-TNGF mobility are not specified in this Release of the specification. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.3.2 Requirements on Ta | Ta shall be able to
- Carry EAP-5G traffic and user location information before the NWt connection is established between the UE and the TNGF.
- Allow the UE and the TNGF to exchange IP traffic.
In deployments where the TNAP does not allocate the local IP addresses to UE(s), Ta shall be able to:
- Allow the UE to request and receive IP configuration from the TNAN (including a local IP address), e.g. with DHCP. This is to allow the UE to use an IP stack to establish a NWt connection between the UE and the TNGF.
NOTE: The "local IP address" is the IP address that allows the UE to contact the TNGF; the entity providing this local IP address is part of TNAN and out of 3GPP scope
In this Release of the specification, Ta is not specified. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.4 Architecture Reference Model for Wireline Access network | Figure 4.2.8.4-1: Non- roaming architecture for 5G Core Network for 5G-RG with Wireline 5G Access network and NG RAN
The 5G-RG can be connected to 5GC via W-5GAN, NG RAN or via both accesses.
NOTE 1: The reference architecture in figure 4.2.8.4-1 only shows the architecture and the network functions directly connected to Wireline 5G Access Network and other parts of the architecture are the same as defined in clause 4.2.
NOTE 2: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure.
NOTE 3: The two N2 instances in Figure 4.2.8.4-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network.
NOTE 4 The two N3 instances in Figure 4.2.8. 4-1 may apply to different UPFs when different PDU Sessions are established over 3GPP access and Wireline 5G Access Network.
Figure 4.2.8.4-2: Non- roaming architecture for 5G Core Network for FN-RG with Wireline 5G Access network and NG RAN
The N1 for the FN-RG, which is not 5G capable, is terminated on W-AGF which acts on behalf of the FN-RG.
The FN-RG can only be connected to 5GC via W-5GAN.
NOTE 5: The reference architecture in figure 4.2.8.4-2 only shows the architecture and the network functions directly connected to Wireline 5G Access Network and other parts of the architecture are the same as defined in clause 4.2.
NOTE 6: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.5 Access to 5GC from devices that do not support 5GC NAS over WLAN access | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.5.1 General | The devices that do not support 5GC NAS signalling over WLAN access are referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short. A N5CW device is not capable to operate as a 5G UE that supports 5GC NAS signalling over a WLAN access network, however, it may be capable to operate as a 5G UE over NG-RAN.
Clause 4.2.8.5 specifies the 5GC architectural enhancements that enable N5CW devices to access 5GC via trusted WLAN access networks. A trusted WLAN access network is a particular type of a Trusted Non-3GPP Access Network (TNAN) that supports a WLAN access technology, e.g. IEEE 802.11. Not all trusted WLAN access networks support 5GC access from N5CW devices. To support 5GC access from N5CW devices, a trusted WLAN access network must support the special functionality specified below (e.g. it must support a TWIF function).
When a N5CW device performs an EAP-based access authentication procedure to connect to a trusted WLAN access network, the N5CW device may simultaneously be registered to a 5GC of a PLMN or SNPN. The 5GC registration is performed by the TWIF function (see next clause) in the trusted WLAN access network, on behalf of the N5CW device. The type of EAP authentication procedure, which is used during the 5GC registration to authenticate the N5CW device, is specified in TS 33.501 [29]. In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.5.2 Reference Architecture | The architecture diagram in Figure 4.2.8.5.2-1 is based on the general 5GS architecture diagrams in clause 4.2 and shows the main network functions required to support 5GC access from N5CW devices. Other network functions are not shown for simplicity.
Figure 4.2.8.5.2-1: Non-roaming and LBO Roaming Architecture for supporting 5GC access from N5CW devices
The reference architecture in Figure 4.2.8.5.2-1 also supports N5CW device access to the subscribed SNPN or access to the SNPN with credentials owned by Credentials Holder. Other parts of the architecture are the same as defined in clause 5.30.2.9. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.5.3 Network Functions | Trusted WLAN Access Point (TWAP): It is a particular type of a Trusted Non-3GPP Access Point (TNAP) specified in clause 4.2.8.2, that supports a WLAN access technology, e.g. IEEE 802.11. This function is outside the scope of the 3GPP specifications.
Trusted WLAN Interworking Function (TWIF): It provides interworking functionality that enables N5CW devices to access 5GC. The TWIF supports the following functions:
- Terminates the N1, N2 and N3 interfaces.
- Implements the AMF selection procedure.
- Implements the NAS protocol stack and exchanges NAS messages with the AMF on behalf of the N5CW device.
- On the user plane, it relays protocol data units (PDUs) between the Yw interface and the N3 interface.
- May implement a local mobility anchor within the trusted WLAN access network. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.8.5.4 Reference Points | The Yt' and Yw reference points are both outside the scope of the 3GPP specifications. The Yt' reference point transports WLAN messages (e.g. IEEE 802.11 messages), while the Yw reference point:
- Shall be able to transport authentication messages between the TNAP and the TWIF for enabling authentication of a N5CW device;
- Shall allow the N5CW device to request and receive IP configuration from the TWIF, including an IP address, e.g. with DHCP.
- Shall support the transport of user-plane traffic for the N5CW device.
The N1, N2 and N3 reference points are the same reference points defined in clause 4.2.7. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.9 Network Analytics architecture | The Network Analytics architecture is defined in TS 23.288 [86]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.10 Architecture Reference Model for ATSSS Support | In order to support the ATSSS feature, the 5G System Architecture is extended as shown in Figure 4.2.10-1, Figure 4.2.10-2 and Figure 4.2.10-3. The additional functionality that is supported by the UE and the network functions shown in these figures is specified in clause 5.32 below. In summary:
- The UE supports one or more of the steering functionalities specified in clause 5.32.6. Each steering functionality in the UE enables traffic steering, switching and splitting across 3GPP access and non-3GPP access, in accordance with the ATSSS rules provided by the network.
NOTE 1: The "MPQUIC-UDP functionality" is referred to as "MPQUIC functionality" in previous releases of this specification that do not support the MPQUIC-IP functionality and the MPQUIC-E functionality.
- The UPF may support the MPTCP Proxy functionality, which communicates with the MPTCP functionality in the UE by using the MPTCP protocol (IETF RFC 8684 [81]), as defined in clause 5.32.6.2.1.
- The UPF may support one or more of the MPQUIC Proxy functionalities (i.e. the MPQUIC-UDP, MPQUIC-IP, MPQUIC-E Proxy functionalities), which communicate with the respective MPQUIC-UDP functionality, the MPQUIC-IP functionality, or the MPQUIC-E functionality in the UE by using the QUIC protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and its multipath extensions (draft-ietf-quic-multipath [174]), as defined in clause 5.32.6.2.2.
- The UPF shall support at least ATSSS-LL functionality with Active-Standby steering mode and may support ATSSS-LL functionality with other steering modes. There is no user plane protocol defined between the ATSSS-LL functionality in the UE and the ATSSS-LL functionality in the UPF.
NOTE 2: Either ATSSS-LL or MPQUIC-E functionality is enabled in the 5GC for MA PDU Session of type Ethernet.
- In addition, the UPF supports Performance Measurement Functionality (PMF), which may be used by the UE to obtain access performance measurements (see clause 5.32.5) over the user-plane of 3GPP access and/or over the user-plane of non-3GPP access.
- The AMF, SMF and PCF are extended with new functionality that is further discussed in clause 5.32.
Figure 4.2.10-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS support
NOTE 2: The interactions between the UE and PCF that may be required for ATSSS control are specified in TS 23.503 [45].
NOTE 3: The UPF shown in Figure 4.2.10-1 can be connected via an N9 reference point, instead of the N3 reference point.
Figure 4.2.10-2 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to the same VPLMN over 3GPP and non-3GPP accesses. In this case, the MPTCP Proxy functionality, the MPQUIC Proxy functionality(ies), the ATSSS-LL functionality and the PMF are located in the H-UPF.
Figure 4.2.10-2: Roaming with Home-routed architecture for ATSSS support (UE registered to the same VPLMN)
Figure 4.2.10-3 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to a VPLMN over 3GPP access and to HPLMN over non-3GPP access (i.e. the UE is registered to different PLMNs). In this case, the MPTCP Proxy functionality, the MPQUIC Proxy functionality(ies), the ATSSS-LL functionality and the PMF are located in the H-UPF.
Figure 4.2.10-3: Roaming with Home-routed architecture for ATSSS support (UE registered to different PLMNs) |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.11 Architecture for 5G multicast-broadcast services | The architecture for 5G multicast-broadcast services is defined in TS 23.247 [129]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.12 Architecture for Proximity based Services (ProSe) in 5GS | The architecture for Proximity based Services (ProSe) in the 5G System is defined in TS 23.304 [128]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.13 Architecture enhancements for Edge Computing | The architecture enhancements for edge computing are outlined in clause 5.13 and further described in TS 23.548 [130]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.14 Architecture for Support of Uncrewed Aerial Systems connectivity, identification and tracking | The architecture for Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking is defined in TS 23.256 [136]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.15 Architecture to support WLAN connection using 5G credentials without 5GS registration | The reference architecture shown with reference point representation in Figure 4.2.15-1 and with Service Based Interface (SBI)-representation in Figure 4.2.15-2, enables a UE to connect to a WLAN access network using its 5GS credentials without registration to 5GS. This architecture is based on the Non-Seamless WLAN Offload Function (NSWOF), which interfaces to the WLAN access network using the SWa' reference point and interfaces to the AUSF using the Nausf SBI. The SWa' reference point corresponds to SWa reference point as defined in TS 23.402 [43] with the difference that SWa' the EAP procedure ensures that the permanent user ID is not visible over the access as defined in TS 33.501 [29] and that SWa' connects the Untrusted non-3GPP IP Access, possibly via 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI.
The functionality of the NSWOF and the procedures applied for supporting a WLAN connection using 5GS credentials for Non-seamless WLAN offload are further defined in TS 33.501 [29] Annex S. The roaming architectures are shown with reference point representation in Figure 4.2.15-3 and with SBI representation in Figure 4.2.15-4. The architecture in Figure 4.2.15-1 and Figure 4.2.15-2 applies to UEs with PLMN or SNPN credentials.
NOTE 1: For a UE with SNPN credentials it is assumed that the realm part of UE identifier in SUCI format is defined in a way that enables routing of SWa requests from the WLAN AN to the NSWOF in the SNPN's 5GC.
The architectures in Figure 4.2.15-3a and Figure 4.2.15-4a apply to UEs with PLMN or SNPN credentials from a CH using UDM.
The architecture in Figure 4.2.15-3b applies to UEs with SNPN credentials from a CH using AAA Server. In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply. Except the UE, all NFs in Figure 4.2.15-3b are out of scope of 3GPP.
The architectures in Figure 4.2.15-3c and Figure 4.2.15-4b apply to UEs with SNPN credentials from a CH using AAA Server via 5GC (NSWOF/AUSF/UDM/NSSAAF). In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply.
NOTE 2: How to protect the user identity over the WLAN interface in architecture defined in Figure 4.2.15-3b and Figure 4.2.15-3c is defined in TS 33.501 [29].
The UE can also connect to a WLAN access network using 5GS credentials by performing the 5GS registration via Trusted non-3GPP access procedure defined in clause 4.12a.2.2 of TS 23.502 [3]. With this procedure, the UE connects to a WLAN access network using 5GS credentials and simultaneously registers in 5GS. However, the architecture defined in Figure 4.2.15-1, Figure 4.2.15-2, Figure 4.2.15-3 and in Figure 4.2.15-4, enables a UE to connect to a WLAN access network using 5GS credentials but without registration in 5GS.
If the WLAN is configured as Untrusted Non-3GPP access, in the case that the WLAN supports IEEE 802.1x, the UE may first use the 5G NSWO procedure to obtain a connection with and the local IP address from the WLAN and any time after that, the UE may initiate the Untrusted Non-3GPP Access to obtain the access to 5GC.
Figure 4.2.15-1: Reference architecture to support authentication for Non-seamless WLAN offload in 5GS
Figure 4.2.15-2: Service based reference architecture to support authentication for Non-seamless WLAN offload in 5GS
Figure 4.2.15-3: Roaming reference architectures to support authentication for Non-seamless WLAN offload in 5GS
Figure 4.2.15-3a: Reference architectures to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM
Figure 4.2.15-3b: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server
Figure 4.2.15-3c: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC
NOTE 2: Configuration 2) in Figure 4.2.15-3 and Figure 4.2.15-3a is a deployment variant of configuration 1)
Figure 4.2.15-4: Service based Roaming reference architecture to support authentication for Non-seamless WLAN offload in 5GS
The SWd' reference point corresponds to the SWd reference point as defined in TS 23.402 [43] with the difference that SWd' connects the 3GPP AAA Proxy, possibly via intermediate 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI.
In both roaming and non-roaming scenarios, the NSWOF acts towards the WLAN Access as a 3GPP AAA server, with the difference that the EAP user ID is a SUCI and not an IMSI.
Figure 4.2.15-4a: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM
Figure 4.2.15-4b: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface | As depicted in Figure 4.2.16-1, the 5G System architecture allows user plane information exposure to some NFs via service-based interface in UPF.
Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface
NOTE 1: In this Release of the specification, only NWDAF/DCCF/MFAF, NEF/AF, SMF and TSNAF/TSCTSF are considered as the receiver of the UPF event notifications.
NOTE 2: UPF information exposure is not restricted to SBI interface, i.e. reporting via PFCP over N4 to SMF is still applicable.
Not all events can be subscribed to UPF directly. The details and constraints for the subscription to UPF event exposure service (i.e. direct vs. indirect) and the information exposed to certain NFs by UPF, as well as the information contained in the event notifications, are defined in clause 5.2.26.2 of TS 23.502 [3] and clause 5.8.2.17. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.17 Architecture for Ranging based services and Sidelink Positioning | The architecture for Ranging based services and Sidelink Positioning is defined in TS 23.586 [180]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.18 Architecture Reference Model for Energy Efficiency and Energy Saving | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.18.0 General | In order to support the Energy Efficiency and Energy Saving feature, the 5G System Architecture is extended as shown in Figure 4.2.18.1-1 and Figure 4.2.18.1-2. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.2.18.1 Non-roaming architecture | Figure 4.2.18-1 depicts the non-roaming reference architecture using service-based interfaces. The figure depicts only the NFs enhanced to support the Energy Efficiency and Energy Saving functionality.
Figure 4.2.18-2 depicts the non-roaming reference architecture, using the reference point representation showing how various network functions interact with each other. The figure depicts the direct interface of the Energy Information Function (EIF) with other NFs only.
Figure 4.2.18.1-1: Non-roaming architecture for Energy Efficiency and Energy Saving
Figure 4.2.18.1-2: Non-roaming architecture for Energy Efficiency and Energy Saving in reference point representation
NOTE 1: The reference points between NF and NRF is not shown in the figure 4.2.18.1-2.
NOTE 2: The interface between EIF and OAM are not shown. The EIF requests energy-related information from OAM by creating management objects defined in TS 28.622 [218] using procedures defined in TS 28.532 [219].
NOTE 3: The functionality of interface N113 is not specified in this Release.
In this Release, the roaming architecture for Energy Efficiency and Energy Saving is not supported. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3 Interworking with EPC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.1 Non-roaming architecture | Figure 4.3.1-1 represents the non-roaming architecture for interworking between 5GS and EPC/E-UTRAN.
Figure 4.3.1-1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN
NOTE 1: N26 interface is an inter-CN interface between the MME and 5GS AMF in order to enable interworking between EPC and the NG core. Support of N26 interface in the network is optional for interworking. N26 supports subset of the functionalities (essential for interworking) that are supported over S10.
NOTE 2: PGW-C + SMF and UPF + PGW-U are dedicated for interworking between 5GS and EPC, which are optional and are based on UE MM Core Network Capability and UE subscription. UEs that are not subject to 5GS and EPC interworking may be served by entities not dedicated for interworking, i.e. by either by PGW or SMF/UPF.
NOTE 3: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed.
NOTE 4: Figures and procedures in this specification that depict an SGW make no assumption whether the SGW is deployed as a monolithic SGW or as an SGW split into its control-plane and user-plane functionality as described in TS 23.214 [32]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.2 Roaming architecture | Figure 4.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GS and EPC/E-UTRAN.
Figure 4.3.2-1: Local breakout roaming architecture for interworking between 5GS and EPC/E-UTRAN
NOTE 1: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed.
NOTE 2: S9 interface from EPC is not required since no known deployment exists.
Figure 4.3.2-2: Home-routed roaming architecture for interworking between 5GS and EPC/E-UTRAN |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.3 Interworking between 5GC via non-3GPP access and E-UTRAN connected to EPC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.3.1 Non-roaming architecture | Figure 4.3.3-1 represents the non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN.
Figure 4.3.3.1-1: Non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN
NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed.
NOTE 2: N26 interface is not precluded, but it is not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.3.2 Roaming architecture | Figure 4.3.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GC via non-3GPP access and EPC/E-UTRAN.
Figure 4.3.3.2-1: Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN
NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed.
NOTE 2: S9 interface from EPC is not required since no known deployment exists.
NOTE 3: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN.
Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN
NOTE 4: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.4 Interworking between ePDG connected to EPC and 5GS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.4.1 Non-roaming architecture | Figure 4.3.4.1-1 represents the non-roaming architecture for interworking between ePDG/EPC and 5GS.
Figure 4.3.4.1-1: Non-roaming architecture for interworking between ePDG/EPC and 5GS
NOTE 1: The details of the interfaces between the UE and the ePDG and between EPC nodes (i.e. SWm, SWx, S2b and S6b), are documented in TS 23.402 [43].
NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]). |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.4.2 Roaming architectures | Figure 4.3.4.2-1 represents the Roaming architecture with local breakout and Figure 4.3.4.2-2 represents the Roaming architecture with home-routed traffic for interworking between ePDG/EPC and 5GS.
Figure 4.3.4.2-1: Local breakout roaming architecture for interworking between ePDG/EPC and 5GS
NOTE 1: The details of the interfaces between the UE and the ePDG and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402 [43].
NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]).
Figure 4.3.4.2-2: Home-routed roaming architecture for interworking between ePDG/EPC and 5GS
NOTE 1: The details of the interfaces between the UE and the ePDG and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402 [43].
NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]). |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.5 Service Exposure in Interworking Scenarios | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.5.1 Non-roaming architecture | Figure 4.3.5.1-1 shows the non-roaming architecture for Service Exposure for EPC-5GC Interworking. If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF node for Service Capability Exposure.
Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking
NOTE 1: In Figure 4.3.5.1-1, Trust domain for SCEF+NEF is same as Trust domain for SCEF as defined in TS 23.682 [36].
NOTE 2: In Figure 4.3.5.1-1, EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc. All southbound interfaces from SCEF are defined in TS 23.682 [36] and are not shown for the sake of simplicity.
NOTE 3: In Figure 4.3.5.1-1, 5GC Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity.
NOTE 4: Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when the SCEF+NEF supports monitoring APIs, the SCEF and NEF need to share context and state information on a UE's configured monitoring events if the UE moves between from EPC and 5GC.
NOTE 5: The north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node via the CAPIF function and/or via local configuration of the SCEF+NEF node. Different sets of APIs can be supported by the two network types. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.3.5.2 Roaming architectures | Figure 4.3.5.2-1 represents the roaming architecture for Service Exposure for EPC-5GC Interworking. This architecture is applicable to both the home routed roaming and local breakout roaming.
Figure 4.3.5.2-1: Roaming Service Exposure Architecture for EPC-5GC Interworking
NOTE: Figure 4.3.5.2-1 does not include all the interfaces and network elements or network functions that may be connected to SCEF+NEF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4 Specific services | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.1 Public Warning System | The Public Warning System architecture for 5G System is specified in TS 23.041 [46]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.2 SMS over NAS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.2.0 General | This clause introduces legacy SMS over NAS architecture, in which the interfaces between SMSF/UDM and SMS-GMSC/SMS-IWMSC/IP-SM-GW/SMS Router are still based on legacy protocol (i.e. MAP or Diameter).
The SBI-based SMS architecture and interfaces are specified in TS 23.540 [142]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.2.1 Architecture to support SMS over NAS | Figure 4.4.2.1-1 shows the non-roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane.
Figure 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS
Figure 4.4.2.1-2 shows the non-roaming architecture to support SMS over NAS using the reference point representation.
Figure 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation
NOTE 1: SMS Function (SMSF) may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040 [5].
NOTE 2: UDM may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040 [5].
NOTE 3: Each UE is associated with only one SMS Function in the registered PLMN.
NOTE 4: SMSF re-allocation while the UE is in RM‑REGISTERED state in the serving PLMN is not supported in this Release of the specification. When serving AMF is re-allocated for a given UE, the source AMF includes SMSF identifier as part of UE context transfer to target AMF. If the target AMF, e.g. in the case of inter-PLMN mobility, detects that no SMSF has been selected in the serving PLMN, then the AMF performs SMSF selection as specified in clause 6.3.10.
NOTE 5: To support MT SMS domain selection by IP-SM-GW/SMS Router, IP-SM-GW/SMS Router may connect to SGs MSC, MME and SMSF via one of the standardized interfaces as shown in TS 23.040 [5].
Figure 4.4.2.1-3 shows the roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane.
Figure 4.4.2.1-3: Roaming architecture for SMS over NAS
Figure 4.4.2.1-4 shows the roaming architecture to support SMS over NAS using the reference point representation.
Figure 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.2.2 Reference point to support SMS over NAS | N1: Reference point for SMS transfer between UE and AMF via NAS.
Following reference points are realized by service based interfaces:
N8: Reference point for SMS Subscription data retrieval between AMF and UDM.
N20: Reference point for SMS transfer between AMF and SMS Function.
N21: Reference point for SMS Function address registration management and SMS Management Subscription data retrieval between SMS Function and UDM. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.2.3 Service based interface to support SMS over NAS | Nsmsf: Service-based interface exhibited by SMSF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.3 IMS support | IMS support for 5GC is defined in TS 23.228 [15].
The 5G System architecture supports N5 interface between PCF and P-CSCF and supports Rx interface between PCF and P-CSCF, to enable IMS service. See TS 23.228 [15], TS 23.503 [45] and TS 23.203 [4].
NOTE 1: Rx support between PCF and P-CSCF is for backwards compatibility for early deployments using Diameter between IMS and 5GC functions.
NOTE 2: When service based interfaces are used between the PCF and P-CSCF in the same PLMN, the P-CSCF performs the functions of a trusted AF in the 5GC. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.4 Location services | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.4.1 Architecture to support Location Services | Location Service feature is optional and applicable to both regulatory services and commercial services in this Release of the specification. The non-roaming and roaming architecture to support Location Services are defined in clause 4.2 of TS 23.273 [87]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.4.2 Reference point to support Location Services | The reference points to support Location Services are defined in clause 4.4 of TS 23.273 [87]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.4.3 Service Based Interfaces to support Location Services | The Service Based Interfaces to support Location Services are defined in clause 4.5 of TS 23.273 [87]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.5 Application Triggering Services | See clause 5.2.6.1 of TS 23.502 [3].
Application trigger message contains information that allows the network to route the message to the appropriate UE and the UE to route the message to the appropriate application. The information destined to the application, excluding the information to route it, is referred to as the Trigger payload. The Trigger payload is implementation specific.
NOTE: The application in the UE may perform actions indicated by the Trigger payload when the Triggered payload is received at the UE. For example initiation of immediate or later communication with the application server based on the information contained in the Trigger payload, which includes the PDU Session Establishment procedure if the related PDU Session is not already established. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.6 5G LAN-type Services |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.