hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.15 BSF Services | The following NF services are specified for BSF as described in TS 23.503 [45]:
Table 7.2.15-1: NF Services provided by BSF
Service Name
Description
Reference in TS 23.502 [3]
Nbsf_Management
Allows a PCF to register/deregister itself and to be discoverable by NF service consumers (NOTE 1).
5.2.13.2
NOTE 1: There may b... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.16 LMF Services | The following NF services are specified for LMF:
Table 7.2.16-1: NF Services provided by LMF
Service Name
Description
Reference in TS 23.273 [87]
Nlmf_Location
This service enables an NF to request location determination for a target UE for the Immediate Location Request and to subscribe / get notified of the location ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.17 CHF Services | The following NF services for spending limits and charging are specified for CHF.
Table 7.2.17-1: NF Services provided by CHF
Service Name
Description
Reference in TS 23.502 [3] or other TS
Nchf_SpendingLimitControl
This service enables transfer of policy counter status information relating to subscriber spending limit... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.18 UCMF Services | The following NF services are specified for UCMF:
Table 7.2.18-1: NF Services provided by UCMF
Service Name
Description
Reference in TS 23.502 [3]
Nucmf_Provisioning
Allows the NF consumer to provision a dictionary entry in the UCMF consisting of a Manufacturer-assigned UE Radio Capability ID, the corresponding UE Radi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.19 AF Services | The following NF services are specified for AF:
Table 7.2.19-1: NF Services provided by AF
Service Name
Description
Reference in TS 23.502 [3] or other TS
Naf_EventExposure
This service enables consumer NF(s) to subscribe or get notified of the event as described in TS 23.288 [86].
5.2.19.2
Naf_ProSe
This service is fo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.20 NSSAAF Services | The following NF services are specified for NSSAAF:
Table 7.2.20 -1: NF Services provided by NSSAAF
Service Name
Description
Reference in TS 23.502 [3]
Nnssaaf_NSSAA
The NSSAAF provides NSSAA service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as need... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.21 DCCF Services | The following NF services are specified for DCCF:
Table 7.2.21-1: NF Services provided by DCCF
Service Name
Description
Reference in TS 23.288 [86]
Ndccf_DataManagement
This service enables a Data Consumer to request data and have it delivered via a messaging framework or via the DCCF, while avoiding redundant requests... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.22 MFAF Services | The following NF services are specified for MFAF:
Table 7.2.22-1: NF Services provided by MFAF
Service Name
Description
Reference in TS 23.288 [86]
Nmfaf_3daDataManagement
This service allows a DCCF to request a messaging framework to provide collected data to consumers or notification endpoints according to processing... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.23 ADRF Services | The following NF services are specified for ADRF:
Table 7.2.23-1: NF Services provided by ADRF
Service Name
Description
Reference in TS 23.288 [86]
Nadrf_DataManagement
This service allows consumers to store, retrieve and delete data or analytics in an ADRF.
10.2
Nadrf_MLModelManagement
This service allows consumers to... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.24 5G DDNMF Services | The 5G DDNMF supports the N5g-ddnmf service defined in clause 7.1 of TS 23.304 [128]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.25 EASDF Services | The following NF services are specified for EASDF.
Table 7.2.25-1: NF Services provided by EASDF
Service Name
Description
Reference in TS 23.548 [130]
Neasdf_DNSContext
This service enables the consumer to create, update and delete DNS context in EASDF, or subscribe to DNS message reporting from EASDF and receives the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.26 TSCTSF Services | The following NF services are specified for TSCTSF.
Table 7.2.26-1: NF Services provided by TSCTSF
Service Name
Description
Reference in TS 23.502 [3]
Ntsctsf_TimeSynchronization
Provides support for time synchronization service based on (g)PTP or 5G access stratum time distribution method as described in clause 5.27.1... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.27 NSACF Services | The following NF services are specified for NSACF:
Table 7.2.27-1: NF Services provided by NSACF
Service Name
Description
Reference in TS 23.502 [3]
Nnsacf_NSAC
This service enables consumer NF to check the availability per network slice and update the number of UEs registered with a network slice, or the number of UEs... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.28 MB-SMF Services | The following NF service is specified for MB-SMF.
Table 7.2.28-1: NF Services provided by MB-SMF
Service Name
Description
Reference in TS 23.247 [129]
Nmbsmf_TMGI
This service enables NF service consumer to allocate, refresh and deallocate TMGI(s).
9.1.2
Nmbsmf_MBSSession
This service enables the consumer to create, up... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.29 UPF Services | The following NF service is specified for UPF.
Table 7.2.29-1: NF Services provided by UPF
Service Name
Description
Reference in TS 23.502 [3]
Nupf_EventExposure
This service exposes UPF related information to the consumer NFs.
5.2.26.2
Nupf_GetUEPrivateIPaddrAndIdentifiers
This service exposes UPF information related ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.30 SCP Services | The following NF service is specified for SCP.
Table 7.2.30-1: NF Services provided by SCP
Service Name
Description
Reference in TS 23.502 [3]
Nscp_EventExposure
This service exposes SCP related information to the consumer NFs.
5.2.28.2 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.31 EIF Services | The following NF service is specified for EIF.
Table 7.2.31-1: NF Services provided by EIF
Service Name
Description
Reference in TS 23.502 [3]
Neif_EventExposure
Enables other NF consumers to subscribe of the energy consumption information as described in clause 5.51.
5.2.28 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.3 Exposure | Network exposure is described in clauses 5.20, 5.20d and in clause 4.15 of TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8 Control and User Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.1 General | Clause 8 specifies the overall protocol stacks between 5GS entities, e.g. between the UE and the 5GC Network Functions, between the 5G-AN and the 5GC Network Functions, or between the 5GC Network Functions. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2 Control Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1 Control Plane Protocol Stacks between the 5G-AN and the 5G Core: N2 | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.1 General | NOTE 1: N2 maps to NG-C as defined in TS 38.413 [34].
Following procedures are defined over N2:
- Procedures related with N2 Interface Management and that are not related to an individual UE, such as for Configuration or Reset of the N2 interface. These procedures are intended to be applicable to any access but may cor... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.2 5G-AN - AMF | Legend:
- NG Application Protocol (NG-AP): Application Layer Protocol between the 5G-AN node and the AMF. NG-AP is defined in TS 38.413 [34].
- Stream Control Transmission Protocol (SCTP): This protocol guarantees delivery of signalling messages between AMF and 5G-AN node (N2). SCTP is defined in RFC 4960 [44].
Figure ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.3 5G-AN - SMF | Legend:
- N2 SM information: This is the subset of NG-AP information that the AMF transparently relays between the 5G-AN and the SMF and is included in the NG-AP messages and the N11 related messages.
Figure 8.2.1.3-1: Control Plane between the 5G-AN and the SMF
NOTE 1: From the 5G-AN perspective, there is a single ter... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2 Control Plane Protocol Stacks between the UE and the 5GC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.1 General | A single N1 NAS signalling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signalling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE.
The NAS p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.2 UE - AMF | Legend:
- NAS-MM: The NAS protocol for MM functionality supports registration management functionality, connection management functionality and user plane connection activation and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling. 5G NAS protocol is defined in TS 24.501 [47]
... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.3 UE – SMF | The NAS-SM supports the handling of Session Management between the UE and the SMF.
The SM signalling message is handled, i.e. created and processed, in the NAS-SM layer of UE and the SMF. The content of the SM signalling message is not interpreted by the AMF.
The NAS-MM layer handles the SM signalling is as follows:
- ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3 Control Plane Protocol Stacks between the network functions in 5GC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3.1 The Control Plane Protocol Stack for the service based interface | The control plane protocol(s) for the service-based interfaces listed in clause 4.2.6 is defined in the TS 29.500 [49] |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3.2 The Control Plane protocol stack for the N4 interface between SMF and UPF | The control plane protocol for SMF-UPF (i.e. N4 reference point) is defined in TS 29.244 [65]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.4 Control Plane for untrusted non 3GPP Access | Figure 8.2.4-1: Control Plane before the signalling IPsec SA is established between UE and N3IWF
Figure 8.2.4-2: Control Plane after the signalling IPsec SA is established between UE and N3IWF
Large NAS messages may be fragmented by the "inner IP" layer or by TCP.
Figure 8.2.4-3: Control Plane for establishment of user... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.5 Control Plane for trusted non-3GPP Access | Figure 8.2.5-1: Control Plane before the NWt connection is established between UE and TNGF
Figure 8.2.5-2: Control Plane after the NWt connection is established between UE and TNGF
Large NAS messages may be fragmented by the "inner IP" layer or by TCP.
Figure 8.2.5-3: Control Plane for establishment of user-plane via T... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.6 Control Plane for W-5GAN Access | The control plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.7 Control Plane for Trusted WLAN Access for N5CW Device | Figure 8.2.7-1: Control Plane for trusted WLAN access for N5CW device
The EAP protocol applies only for performing EAP-based access authentication procedure to connect to a trusted WLAN access network. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3 User Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.1 User Plane Protocol Stack for a PDU Session | This clause illustrates the protocol stack for the User plane transport related with a PDU Session.
Legend:
- PDU layer: This layer corresponds to the PDU carried between the UE and the DN over the PDU Session. When the PDU Session Type is IPv4 or IPv6 or IPv4v6, it corresponds to IPv4 packets or IPv6 packets or both o... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.2 User Plane for untrusted non-3GPP Access | Figure 8.3.2-1: User Plane via N3IWF
Large GRE packets may be fragmented by the "inner IP" layer.
Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.3 User Plane for trusted non-3GPP Access | Figure 8.3.3-1: User Plane via TNGF
Large GRE packets may be fragmented by the "inner IP" layer.
Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.4 User Plane for W-5GAN Access | The user plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.5 User Plane for N19-based forwarding of a 5G VN group | Figure 8.3.5-1: User Plane for N19-based forwarding
Details about the PDU Layer, PDU Session User Plane Protocol Stack are included in clause 8.3.1 and clause 8.3.2. The N19 is based on a shared User Plane tunnel connecting two PSA UPFs of a single 5G VN group. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.6 User Plane for Trusted WLAN Access for N5CW Device | Legend: - Transport: this layer refers to the transport of PDUs between the N5CW device and TWIF (see clause 4.2.8.5.4). In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. Figure 8.2.8-1: User Plane for trusted WLAN access for N5CW device Annex A (informative): ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 1 Scope | The present document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 [2] and for the policy and charging control framework which is described in TS 23.503 [20]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3 Definitions, symbols and abbreviations | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [20] apply. A term defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the same term, if any, in any other specifications.
Multi-member AF session: A type of AF session ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [20] apply. An abbreviation defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the same abbreviation, if any, in any other specifications. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4 System procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.1 General | The clause 4 describes the procedures and Network Function services for the 5GS by end-to-end information flows and these information flows make use of NF service operations, defined in clause 5, for the communication within the 5GC Control Plane. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2 Connection, Registration and Mobility Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.1 General | The Connection Management is used to establish and release the Control Plane signalling connection between the UE and the AMF. The Registration Management is used to register or deregister a UE/user with the 5GS and establish the user context in the 5GS. The Mobility Management functions are used to keep track of the c... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2 Registration Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.1 General | The Registration and Deregistration procedures in clause 4.2.2 provides the required functionality to register or deregister a UE/user with the 5GS. Additional functionality to support Registration Management for non-3GPP access is defined in clause 4.12. Additional functionality to support Registration Management for ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2 Registration procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.1 General | A UE needs to register with the network to get authorized to receive services, to enable mobility tracking and to enable reachability. The UE initiates the Registration procedure using one of the following Registration types:
- Initial Registration to the 5GS;
- Mobility Registration Update upon changing to a new Track... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.2 General Registration | Figure 4.2.2.2.2-1: Registration procedure
1. UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, [last visited TAI (if available)], Security parameters, [Requested NSSAI], [Mapping Of Requested NSSAI], [Default Configured NSSAI Indication], [UE Radio Capability Upda... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.3 Registration with AMF re-allocation | When an AMF receives a Registration request, the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE. The Registration with AMF re-allocation procedure, described in figure 4.2.2.2.3-1, is used to reroute the NAS message of the UE to the ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.4 Registration with Onboarding SNPN | This clause specifies how a UE can register to an ON-SNPN for provisioning the UE with SO-SNPN credentials and other information to enable SNPN access as defined in clause 5.30.2.10 of TS 23.501 [2].
The Registration procedure for Onboarding SNPN over 3GPP access shall be supported as specified in clause 4.2.2.2.2 with... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3 Deregistration procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.1 General | The Deregistration procedure allows:
- the UE to inform the network that it does not want to access the 5GS any longer; and
- the network to inform the UE that it does not have access to the 5GS any longer; or
- the network to inform the UE that the UE's Registered PLMN is not allowed to operate at the UE location.
The... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.2 UE-initiated Deregistration | The UE uses this procedure to deregister from the registered PLMN as shown in Figure 4.2.2.3.2-1.
Figure 4.2.2.3.2-1: UE-initiated Deregistration
1. The UE sends NAS message Deregistration Request (5G-GUTI, Deregistration type (e.g. Switch off), Access Type, [Unavailability Period Duration], [NAS message container]) to... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.3 Network-initiated Deregistration | The procedure depicted in Figure 4.2.2.3.3-1 shows Network-initiated Deregistration procedure. The AMF can initiate this procedure for either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE or the UE's registered PLMN is not allowed to operate ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3 Service Request procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.1 General | The Service Request procedure is used by a UE in CM-IDLE state or the 5GC to request the establishment of a secure connection to an AMF. The Service Request procedure is also used both when the UE is in CM-IDLE and in CM-CONNECTED to activate a User Plane connection for an established PDU Session. The Service Request p... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.2 UE Triggered Service Request | The UE in CM-IDLE state initiates the Service Request procedure in order to send uplink signalling messages, user data, to request emergency services fallback, or as a response to a network paging request. The UE shall not initiate UE Triggered Service Request from CM-IDLE if there is a Service Gap timer running. After... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.3 Network Triggered Service Request | This procedure is used when the network needs to signal (e.g. N1 signalling to UE, Mobile-terminated SMS, User Plane connection activation for PDU Session(s) to deliver mobile terminating user data) with a UE. When the procedure is triggered by SMSF, PCF, LMF, GMLC, NEF, AMF or UDM, the SMF (and UPF, if applicable) in ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4 UE Configuration Update | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.1 General | UE configuration may be updated by the network at any time using UE Configuration Update procedure. UE configuration includes:
- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI (including ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.2 UE Configuration Update procedure for access and mobility management related parameters | This procedure is initiated by the AMF when the AMF wants to update access and mobility management related parameters in the UE configuration.
This procedure is also used to trigger UE to perform, based on network indication, either Mobility Registration Update procedure while the UE is in CM-CONNECTED state to modify ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.3 UE Configuration Update procedure for transparent UE Policy delivery | This procedure is initiated when the PCF wants to update UE policy information (i.e. UE policy) in the UE configuration. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PC... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5 Reachability procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.1 General | Elements of this procedure are used for UDM/NF initiated UE Reachability Notification requests, e.g. for "SMS over NAS".
The procedure applies to UEs that are in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states.
There are two procedures necessary for any service related entity that would need to be notified by the reach... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.2 UE Reachability Notification Request procedure | The UE Reachability Notification Request procedure is illustrated in figure 4.2.5.2-1.
Figure 4.2.5.2-1: UE Reachability Notification Request Procedure
1a. [Conditional] When a service-related entity requests the UDM to provide an indication regarding UE reachability, the UDM checks whether that service-related entity ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.3 UE Activity Notification procedure | The UE Activity Notification procedure is illustrated in figure 4.2.5.3-1.
Figure 4.2.5.3-1: UE Activity Procedure
0. Event has been subscribed in the AMF for UE reachability for DL traffic or for UE reachability status change.
1a. For a UE in CM-IDLE, the AMF receives (N1) NAS signalling implying UE is reachable for D... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.6 AN Release | This procedure is used to release the logical NG-AP signalling connection for the UE between the (R)AN and the AMF and the associated N3 User Plane connections and (R)AN signalling connection between the UE and the (R)AN and the associated (R)AN resources.
When the NG-AP signalling connection is lost due to (R)AN or AM... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7 N2 procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.1 N2 Configuration | At power up, restart and when modifications are applied, the 5G-AN node and AMF use non-UE related N2 signalling to exchange configuration data. Full details of this configuration data are specified in TS 38.413 [10], but the following highlights some aspects.
The AMF supplies the 5G-AN node with information about:
a) ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2 NGAP UE-TNLA-binding related procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.1 Creating NGAP UE-TNLA-bindings during Registration and Service Request | When a UE connects to the 5GC via a 5G-AN node without providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate to any of its connected AMFs, the following steps are performed:
1. The 5G-AN node selects an AMF as defined in clause 6.3.5 of ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.2 Creating NGAP UE-TNLA-bindings during handovers | During an Xn-based inter NG-RAN node handover, the following applies
- If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node supplies the target 5G-AN node with the corresponding TNL address of the AMF for the currently used TNL association.
- If the target 5G-AN does not have a TNL association towards the ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.3 Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release | If the AMF has released the NGAP UE-TNLA-binding in the 5G-AN node for a UE and the 5G-AN node needs to send an N2 message for this UE, the following applies:
- The 5G-AN node checks the GUAMI stored in the UE context and the associated AMF:
- If the GUAMI is available, 5G-AN selects the AMF which owns that GUAMI.
- If... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.4 NGAP UE-TNLA-binding update procedure | At any time the AMF may decide to re-bind the NGAP UE association to a new TNL association:
- by sending a UE-specific NGAP message on a new TNL association (triangular redirection), if:
- AMF responds to the 5G-AN node initiated NGAP message (i.e. triangular redirection) as described in clauses 4.2.7.2.1, 4.2.7.2.2 an... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.5 NGAP UE-TNLA-binding per UE Release procedure | At any time the AMF may decide to release the NGAP UE-TNLA binding while keeping the UE in CM-CONNECTED state while keeping the corresponding N3 interface. The AMF releases the NGAP UE-TNLA binding by sending a UE-specific NGAP UE-TNLA binding release message on the current TNL association.
If the AMF releases the NGAP... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.3 AMF Failure or Planned Maintenance handling procedure | For UE(s) in CM-CONNECTED state:
- If AMF failure is detected by 5G-AN, all NGAP UE TNLA binding for UEs served by that AMF are released.
- If AMF becomes unavailable due to planned maintenance, the AMF notifies the 5G-AN about the unavailable GUAMI(s) and provides optionally a target AMF Name corresponding to each una... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.4 Additional User Location Information with Mobile Base Station Relay (MBSR) | As described in clause 5.35A of TS 23.501 [2], when a UE is being served by an MBSR, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 parameters shall also include the additional ULI of this MBSR.
When the AMF provides user location information to other NFs (e.g. LMF as sp... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.5 Additional User Location Information with Mobile gNB with wireless access backhauling (MWAB) | When a UE is being served by an MWAB-gNB cell, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 message shall also include the Additional ULI as described in clause 5.49.4 of TS 23.501 [2]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.8 Void | 4.2.8a UE Capability Match Request procedure
If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3 of TS 23.501 [2]), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedur... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9 Network Slice-Specific Authentication and Authorization procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.1 General | The Network Slice-Specific Authentication and Authorization procedure is triggered for an S-NSSAI requiring Network Slice-Specific Authentication and Authorization with an AAA Server (AAA-S) which may be hosted by the H-PLMN operator or by a third party which has a business relationship with the H-PLMN, using the EAP f... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.2 Network Slice-Specific Authentication and Authorization | Figure 4.2.9.2-1: Network Slice-Specific Authentication and Authorization procedure
1. For S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization, based on change of subscription information, or triggered by the AAA-S, the AMF may trigger the start of the Network Slice Specific Authenticati... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.3 AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure | Figure 4.2.9.3-1: AAA Server initiated Network Slice-Specific Re-authentication and Re-authorization procedure
1. The AAA-S requests the re-authentication and re-authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Re-Auth Request message, for the UE identified by the GPSI in this message. T... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.4 AAA Server triggered Slice-Specific Authorization Revocation | Figure 4.2.9.4-1: AAA Server-initiated Network Slice-Specific Authorization Revocation procedure
1. The AAA-S requests the revocation of authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Revoke Auth Request message, for the UE identified by the GPSI in this message. This message is sent t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10 N3 data transfer establishment procedure when Control Plane CIoT 5GS Optimisation is enabled | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10.1 UE triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2 of TS 23.501 [2], then the UE may, e.g. based on the amount of data to be transferred in uplink, initiate N3 data transfer establish... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10.2 SMF triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may, e.g. based on the amount of data to be transferred or due to congestion, initiate N3 data transfer establishment ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11 Network Slice Admission Control Function (NSACF) procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.1 General | The Network Slice Admission Control Function procedures are performed for an S-NSSAI which is subject to Network Slice Admission Control (NSAC) as described in TS 23.501 [2]. If charging needs to be enabled, the NSACF may act as a NF (CTF) and interact with the CHF to support the Event based charging as defined in TS 3... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.2 Number of UEs per network slice availability check and update procedure | This clause applies to Non-Hierarchical and centralized NSAC architectures. The difference between the two architectures for the various steps, where applicable, is described at the end of the clause.
The number of UEs per network slice availability check and update procedure is to update (i.e. increase or decrease) th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.3 Configuration for Early Admission Control (EAC) update procedure | The configuration for Early Admission Control (EAC) update procedure indicates to the AMF the activation or the deactivation of the EAC mode for the S-NSSAI subject to NSAC. EAC mode means that the AMF is required to perform the number of UEs per network slice availability check and update procedure before the S-NSSAI ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.