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)
... |
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
AI... |
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_AIMLEClientPart... |
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
... |
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
... |
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 ... |
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, authe... |
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.
- Fo... |
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 Ac... |
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
5... |
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 ide... |
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 functi... |
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 Funct... |
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 ser... |
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 ... |
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 ... |
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:... |
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 Networ... |
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 archit... |
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... |
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 fun... |
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 architectu... |
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-... |
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 untr... |
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 reque... |
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 ... |
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-R... |
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 sup... |
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 fu... |
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 devi... |
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 o... |
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 Of... |
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... |
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 v... |
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 cor... |
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 anoth... |
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... |
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 acc... |
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... |
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... |
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-... |
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... |
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... |
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 add... |
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 compatibilit... |
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 t... |
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.