hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.10 CN-initiated selective deactivation of UP connection of an existing PDU Session involving I-SMF | For the CN-initiated selective deactivation of UP connection of an existing PDU Session procedure, if the PDU Session involved I-SMF, the procedure defined in clause 4.3.7 are impacted as following:
- The SMF and UPF in the procedure are replaced by the I-SMF and I-UPF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11 Xn based handover | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11.1 General | This clause describes the Xn based handover with the insertion, reallocation and removal of I-SMF.
To support the EAS session continuity upon UL CL relocation (allowing the UE to go on exchanging with the source EAS despite the fact that a new UL CL has been allocated to the PDU Session), the N9 forwarding tunnel betwe... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11.2 Xn based handover with insertion of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface (in this case the AMF is unchanged) and the AMF decides that insertion of a new intermediate I-SMF is needed. This procedure is used for non-roaming or local breakout roaming scenario.
The call flow is shown in figure 4.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11.3 Xn based handover with re-allocation of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface (in this case the AMF is unchanged) and the AMF decides that the intermediate SMF(I-SMF) is to be changed. This procedure is used for non-roaming or local breakout roaming scenario. In the case of home routed roaming sce... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11.4 Xn based handover with removal of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface(in this case the AMF is unchanged) and the AMF decides that removal of intermediate I-SMF is needed. This procedure is used for non-roaming or local breakout roaming scenario.
The call flow is shown in figure 4.23.11.4-1... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.11.5 Xn based handover without change of intermediate SMF | When both I-SMF and SMF are available for a PDU Session and no I-SMF change or removal is needed during Xn based handover procedure, compared to the procedure defined in clause 4.9.1.2.2 and clause 4.9.1.2.4 the SMF is replaced with the I-SMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12 N26 based Interworking Procedures with I-SMF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.1 General | When UE moves from EPS to 5GS, for a each PDU Session, the AMF determines whether I-SMF needs to be inserted based on UE location and service area of the SMF+PGW-C.
This clause describes the N26 based Interworking Procedures with I-SMF insertion when UE move from EPS to 5GS and removal when UE moves from 5GS to EPS. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.2 5GS to EPS Idle mode mobility using N26 interface with I-SMF removal | For 5GS to EPS Idle mode mobility using N26 with I-SMF removal, the procedure "5GS to EPS Idle mode mobility using N26 interface" defined in clause 4.11.1.3.2 for the home routed-roaming case are re-used, with the following change:
- The V-SMF is replaced by I-SMF, H-SMF is replaced by SMF and V-UPF is replaced by I-UP... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.3 EPS to 5GS mobility registration procedure (Idle and Connected State) using N26 interface with I-SMF insertion | For EPS to 5GS Mobility registration procedure using N26 with I-SMF insertion, the procedure "EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface" defined in clause 4.11.1.3.3 for the home routed-roaming case are re-used, with the following change:
- The V-SMF is replaced by I-SMF ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.4 Procedures for EPS bearer ID allocation | The EPS Bearer ID allocation procedure, EPS Bearer ID transfer procedure and EPS Bearer ID revocation procedure are perfomed as described for the home-routed roaming case in clause 4.11.1.4, with the following differences:
- H-SMF is replaced by SMF.
- V-SMF is replaced by I-SMF.
- In step 8 of clause 4.11.1.4.1, in ad... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.5 EPS to 5GS mobility registration procedure (Idle) using N26 interface with AMF reallocation and I-SMF insertion | For EPS to 5GS Mobility registration procedure using N26 with AMF reallocation and I-SMF insertion, the procedure "EPS to 5GS Mobility Registration Procedure (Idle) using N26 interface with AMF reallocation" defined in clause 4.11.1.3.4 are re-used, with the following change:
- The V-SMF is replaced by I-SMF and H-SMF ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.6 5GS to EPS handover using N26 interface with I-SMF removal | The procedure "5GS to EPS handover using N26 interface" in clause 4.11.1.2.1 for the home routed-roaming case is applied to handover from 5GS to EPS using N26 interface with I-SMF removal with the following changes:
- The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.7 EPS to 5GS handover using N26 interface with I-SMF insertion | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.7.1 Preparation phase | For handover from EPS to 5GS using N26 interface, if I-SMF needs to be inserted, the preparation procedure defined in clause 4.11.1.2.2.1 for the home routed-roaming case are re-used, with the following changes:
- The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF.
- The V-SMF selec... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.7.2 Execution phase | For handover from EPS to 5GS using N26 interface, if I-SMF needs to be inserted, the execution procedure defined in clause 4.11.1.2.2.2 for the home routed-roaming case are re-used, with the following change:
- The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF.
- The V-SMF selectio... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8 Impact to 5GC procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.1 General | This clause captures impact to 5GC procedures in other clauses of clause 4.23 to support interworking with N26. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.2 UE Triggered Service Request with I-SMF insertion/change/removal | The following impact is applicable for UE triggered Service Request with I-SMF insertion in clause 4.23.4.3:
- In step 8a, when an I-SMF is inserted, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tu... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.3 PDU Session establishment procedure | The following impact is applicable for PDU Session establishment in clause 4.23.5.1:
- If I-SMF is involved in the PDU Session establishment, after EBI has been successfully allocated, the SMF+PGW-C also prepares CN tunnel info for each EPS bearer and provides it to the I-SMF, see clause 4.23.12.4. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.4 PDU Session modification procedure | The following impact is applicable for PDU Session modification in clause 4.23.5.3:
- If I-SMF is involved in the PDU Session modification, if EBI needs to be allocated and the allocation is successful, the SMF+PGW-C also prepares CN tunnel info for each EPS bearer and provides it to the I-SMF, see clause 4.23.12.4. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.5 Inter NG-RAN node N2 based handover with I-SMF insertion/change/removal | The following impact is applicable for Inter NG-RAN node N2 based handover with I-SMF insertion in clause 4.23.7.3.2:
- In step 7c, at I-SMF insertion, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.12.8.6 Xn based handover with insertion of I-SMF | The following impact is applicable Xn based handover with insertion of I-SMF in clause 4.23.11.2:
- In step 6, at I-SMF insertion, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tunnel for each EPS b... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13 Non N26 based Interworking Procedures with I-SMF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13.1 General | When UE moves a PDU Session from EPS to 5GS, the AMF determines whether I-SMF needs to be inserted based on the UE location and the service area of the SMF+PGW-C.
This clause describes the non N26 based Interworking Procedures with I-SMF insertion when UE move a PDU Session from EPS to 5GS and I-SMF removal when UE mov... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13.2 Mobility procedure without N26 interface from EPS to 5GS | At Mobility procedure from EPS to 5GS without N26 interface the procedure described in Figure 4.11.2.3-1 takes place, with following difference:
- During step 9 of Figure 4.11.2.3-1 "UE requested PDU Session Establishment according to clause 4.3.2.2", the mechanisms described in clause 4.23.5.1 apply |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13.3 Mobility procedure without N26 interface from EPC/ePDG to 5GS | At Handover from EPC/ePDG to 5GS, the procedure described in Figure 4.11.4.1-1 takes place, with following difference:
- During step 2 of Figure 4.11.4.1-1 "UE requested PDU Session Establishment according to clause 4.3.2.2", the mechanisms described in clause 4.23.5.1 apply |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13.4 Mobility procedure without N26 interface from 5GS to EPS | At Mobility procedure from 5GS to EPS without N26 interface, the procedure described in Figure 4.11.2.2-1 takes place, with following difference:
- During step 14 of Figure 4.11.2.2-1 (SMF+PGW-C initiates release of the PDU Session(s) in 5GS transferred to EPS), if an I-SMF was involved in the PDU Session, the same mec... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.13.5 Mobility procedure without N26 interface from 5GS to EPC/ePDG | At Handover from 5GS to EPC/ePDG, the procedure described in Figure 4.11.4.2-1 takes place, with following difference:
- During step 3 of Figure 4.11.4.2-1 (5GC and NG-RAN resource release), if an I-SMF was involved in the PDU Session, the same mechanisms than in Home Routed roaming apply (Figure 4.3.4.3-1 steps 3a-16b... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.14 Pause of charging | When I-SMF is involved for a PDU Session, the procedure for pause of charging in home routed roaming case defined in clause 4.4.4 is applied by replacing the H-SMF with SMF and V-SMF with I-SMF.
When a Local UPF (PSA) is involved, the SMF stops or starts the usage reporting including usage reporting at the Local UPF (P... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.15 PDU Session mobility between 3GPP and non-3GPP access | In this Release of the specification, deployments topologies with specific SMF Service Areas apply only for 3GPP access.
At PDU Session mobility from 3GPP to non-3GPP access, an I-SMF may need to be removed because an I-SMF had been inserted when the PDU Session was served over 3GPP access.
At PDU Session mobility from... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.16 Handover of a PDU Session procedure between 3GPP and untrusted non-3GPP access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.16.1 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) | The following impacts are applicable to clause 4.9.2.1 when a PDU Session is handover from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout):
- Step2: The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.23.5.1 a... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.16.2 Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) | When a PDU Session is handover from 3GPP access with an I-SMF to untrusted non-3GPP access (non-roaming and roaming with local breakout), the following steps take place:
1) Step 1 of clause 4.9.2.2.
2) Step 2 of clause 4.9.2.2.
3) The step 3 in clause 4.9.2.4.2 is executed involving I-SMF instead of V-SMF, with followi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.16.3 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (home routed roaming) | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.16.3.1 The target AMF is in the PLMN of the N3IWF | The following impacts are applicable to clause 4.9.2.3.1 when a PDU Session is handover from untrusted non-3GPP to 3GPP access (home routed roaming) and target AMF is in the PLMN of the N3IWF:
- Step2: The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specif... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.17 Additional considerations for Home-routed roaming | As described in clause 4.23.1, the procedures in clause 4.23 apply for home-routed roaming scenarios with V-SMF insertion/removal/change (i.e. by replacing the I-SMF with V-SMF and SMF with H-SMF). Differences compared to the procedures for I-SMF are described below:
- The Registration procedure as defined in clause 4.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.24 Procedures for UPF Anchored Data Transport in Control Plane CIoT 5GS Optimisation | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.24.1 UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation | This clause describes the procedures for Mobile Originated Transport in Control Plane CIoT 5GS Optimisation where the PDU Session is terminated at a UPF.
Figure 4.24.1-1: UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation
1. If the UE is CM-CONNECTED it sends a NAS message carrying the... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.24.2 UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation | This clause describes the procedures for Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation where the PDU Session is terminated at a UPF.
Figure 4.24.2-1: Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation
1. Downlink data is received by the UPF. If buffering is configured in t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25 Procedures for NEF based Non-IP Data Delivery | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.1 General | Non-IP Data Delivery (NIDD) it is a means for delivering data via a PDU Sessions of type "Unstructured". The subsequent clauses describe the procedures necessary to support NEF based NIDD. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.2 SMF-NEF Connection Establishment | When the UE performs the PDU Session establishment with PDU Session type of "Unstructured" and the subscription information corresponding to the UE requested DNN includes the "NEF Identity for NIDD" (NEF ID), then the SMF initiates a SMF-NEF Connection establishment procedure towards the NEF corresponding to the "NEF I... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.3 NIDD Configuration | Figure 4.25.3-1 illustrates the procedure for configuring necessary information for data delivery via the NIDD API.
The NIDD Configuration procedure can be NEF initiated or AF triggered: in the former case the procedure starts at step 1, in the latter case it starts at step 2.
Figure 4.25.3-1: NIDD Configuration proced... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.4 NEF Anchored Mobile Originated Data Transport | Figure 4.25.4-1 illustrates the NEF Anchored Mobile Originated Data Transport procedure.
Figure 4.25.4-1: NEF Anchored Mobile Originated Data Transport procedure
1. The UE sends a NAS message with unstructured data according to steps 1-4 of the procedure for UPF anchored Mobile Originated Data Transport in Control Plan... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.5 NEF Anchored Mobile Terminated Data Transport | Figure 4.25.5-1 illustrates the procedure using which the AF sends unstructured data to a given user as identified via External Identifier or MSISDN.
Figure 4.25.5-1: NEF Anchored Mobile Terminated Data Transport
1a. If AF has already activated the NIDD service for a given UE and has downlink unstructured data to send ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.6 NIDD Authorization Update | Figure 4.25.6-1 illustrates the procedure for updating or revoking an existing NIDD Authorization.
The UDM may initiate the NIDD Authorization Update procedure with the NEF to send updated Authorization information to the NEF.
Figure 4.25.6-1: NIDD Authorization Update procedure
0. UDM provided a successful authorizati... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.7 SMF Initiated SMF-NEF Connection Release procedure | When the PDU Session Release is initiated and if a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.4.2, then the SMF initiates a SMF-NEF Connection Release procedure towards the NEF corresponding to the "NEF... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.8 NEF Initiated SMF-NEF Connection Release procedure | NEF initiates a SMF-NEF connection release procedure in the following cases:
- when a NIDD Authorization Update Request from the UDM indicates that the User is no longer authorized for NIDD, or
- failure of AF or failure of AF connection, or
- based on a request from the AF.
Figure 4.25.8-1 illustrates the NEF Initiate... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.25.9 NEF Anchored Group NIDD via NEF anchored unicast MT data | Figure 4.25.9-1 illustrates the procedure by which the AF can send a Group NIDD addressed to External Group Identifier. It is a pre-requisite assumption that the NEF has already resolved the mapping of External Group Identifier to individual SUPIs with the help of UDM during NIDD Configuration procedure as specified in... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26 Network Function/NF Service Context Transfer Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.1 General | Network Function/NF Service Context Transfer Procedures allow transfer of Service Context of a NF/NF Service from a Source NF/NF Service Instance to the Target NF/NF Service Instance, e.g. before the Source NF/NF Service can gracefully close its NF/NF Service. If SMF sets are deployed this applies from an SMF instance ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.2 NF/NF Service Context Transfer Push Procedure | Figure 4.26.2-1: NF/NF Service Context Push procedure
1. When triggered, the Source NF/NF Service acting as NF Service Consumer sends its Context (e.g. UE Context or SM context) to the Target NF/NF Service acting as NF Service producer. This may trigger several other procedures that ensure all necessary NF/NF Services ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.3 NF/NF Service Context Transfer Pull procedure | Figure 4.26.3-1: NF/NF Service Context Pull procedure
1. When triggered, the Target NF/NF Service as an NF Service Consumer requests a Context (e.g. UE context or SM context) from the Source NF as a NF Service Producer. This may trigger several other procedures that ensure all necessary NF/NF services are being updated... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.4 Context Transfer due to decommissioning | In the case of decommissioning, the Old NF may inform NRF that it is about to be decommissioned. NRF will in this case not include the NF profile of the Old NF in any discovery result from the NF/NF service discovery procedure. The NRF will also notify any consumers subscribed to changes to this resource. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.5 SMF Service Context Transfer procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.5.1 General | This clause lists the context-specific transfer procedures between different SMF Sets supporting the same DNN/S-NSSAI pair supported for SM Contexts (i.e. SMF contexts). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.5.2 I-SMF Context Transfer procedure | Old I-SMF triggered from O&M procedure sends Nsmf_PDUSession_SMContextStatusNotify (I-SMF transfer indication, New SMF ID or SMF set ID) to AMF.
Steps 2-25 in clause 4.23.4.3 follows, where in step 2 AMF selects the indicated I-SMF, or selects the I-SMF from the indicated SMF set. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.26.5.3 SMF Context Transfer procedure, LBO or no Roaming, no I-SMF | In the case of dynamic IP address assignment (IPv4 address and/or IPv6 prefix), the procedure in figure 4.26.4.1.1-1 assumes that, if the UE IP address is received from Old SMF, the control of the IP address(es) assigned by Old SMF is moved to New SMF by O&M procedures. New SMF is in full control of the concerned IP ad... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.27 Procedures for Enhanced Coverage Restriction Control via NEF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.27.1 General | The support for Enhanced Coverage Restriction Control via NEF enables AF to query status of Enhanced Coverage Restriction or enable/disable Enhanced Coverage Restriction per individual UEs. Figure 4.27.1-1 shows the procedure for Enhanced Coverage Restriction Control via NEF.
Figure 4.27.1-1: Enhanced Coverage Restrict... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28 Subscription-based distribution of timing information | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28.1 General | The distribution of 5G Clock (5G Access Stratum-based Time Distribution) and the (g)PTP domain synchronization ((g)PTP-based Time Distribution) may be controlled based on subscription data. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28.2 5G Access Stratum-based Time Distribution | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28.2.1 Control of access stratum time synchronization service without AF request | The control of 5G Access Stratum-based Time Distribution for a UE is performed by the AMF according to parameters retrieved in the Access and Mobility Subscription data.
Figure 4.28.2.1-1: Subscription-based control of 5G access stratum-based time distribution
1. The UE performs the registration procedure as described ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28.3 (g)PTP-based Time Distribution | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.28.3.1 Control of (g)PTP time synchronization service without AF request | The TSCTSF may use the subscription data to control the (g)PTP-based time distribution without AF request.
Figure 4.28.3.1-1: Subscription based control of (g)PTP time synchronization service without AF request
1. The UE performs the UE-requested PDU Session Establishment.
2. The PCF determines if the PDU Session is po... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.29 Energy consumption information collection and exposure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.29.0 General | This clause describes how EIF collects the energy consumption information and exposes the energy consumption information to the Consumer NF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.29.1 Energy Consumption information exposure | The procedure is used by the AF to subscribe to notifications and to explicitly cancel a previous subscription for Energy Consumption information exposure.
Figure 4.29.1-1: Energy consumption information exposure
1a. The untrusted AF (un)subscribes energy consumption event by invoking the Nnef_EventExposure_(Un)Subscri... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.29.2 Energy Consumption information collection | Figure 4.29.2-1 shows the procedure for EIF to collect the Energy consumption information.
Figure 4.29.2-1: Energy Consumption information collection
1. The Consumer NF (i.e. trusted AF or 5GC NF) subscribes to the energy consumption event with the EIF by using Neif_EventExposure_Subscribe service for the required gran... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5 Network Function Service procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.1 Network Function Service framework procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.1.1 Network Function Service Discovery | The network function (NF) within the core network may expose its capability as service via its service based interfaces, which can be re-used by other NFs. Unless the expected NF information is locally configured on requester NF, e.g. the expected NF is in the same PLMN, the NF service discovery is implemented via the ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2 Network Function services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.1 General | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2 AMF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.1 General | The following table shows the AMF Services and AMF Service Operations.
Table 5.2.2.1-1: List of AMF Services
Service Name
Service Operations
Operation
Semantic
Known Consumer(s)
Namf_Communication
UEContextTransfer
Request/Response
Peer AMF
CreateUEContext
Request/Response
Peer AMF
RelocateUEContext
Request/Response
Pe... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2 Namf_Communication service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.1 General | Service description: This service enables an NF to communicate with the UE through N1 NAS messages or with the AN (both UE and non UE specific). The service operations defined below allow the NF to communicate with the UE and the AN. The following are the key functionalities of this NF service.
- Provide service operat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.2 Namf_Communication_UEContextTransfer service operation | Service operation name: Namf_Communication_UEContextTransfer
Description: Provides the UE context to the consumer NF.
Input, Required: 5G-GUTI or SUPI, Access Type, Reason.
Input, Optional: Integrity protected message from the UE that triggers the context transfer.
Output, Required: The UE context of the identified UE ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.3 Namf_Communication_RegistrationStatusUpdate service operation | Service operation name: Namf_Communication_RegistrationStatusUpdate
Description: This service operation is used by the consumer NF to inform the AMF that a prior UE context transfer has resulted in the UE successfully registering with it. The UE context is marked inactive in the AMF.
Input, Required: 5G-GUTI, Status.
I... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.4 Namf_Communication_N1MessageNotify service operation | Service operation name: Namf_Communication_N1MessageNotify
Description: AMF notifies the N1 message received from the UE to a destination CN NF.
Input, Required: AMF ID (GUAMI), N1 Message(s)
Input, Optional: local time zone, UE's current location, AN access information (e.g. AN type AN N2 terminating point, CAG Identi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.5 Namf_Communication_N1N2MessageSubscribe service operation | Service operation name: Namf_Communication_N1N2MessageSubscribe.
Description: An NF can subscribe with the AMF to get notified of a particular N1 message type or a specific N2 information type about the UE.
Input, Required: CN NF ID, N1 Message Type
Input, Optional: SUPI.
Output, Required: None.
Output, Optional: None.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.6 Namf_Communication_N1N2MessageUnSubscribe service operation | Service operation name: Namf_Communication_N1N2MessageUnSubscribe.
Description: An NF can unsubscribe with the AMF to stop notifying a particular N1 message type or a specific N2 information type about the UE.
Input, Required: CN NF ID, N1 Message Type
Input, Optional: None.
Output, Required: None.
Output, Optional: No... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.7 Namf_Communication_N1N2MessageTransfer service operation | Service operation name: Namf_Communication_N1N2MessageTransfer.
Description: CN NF request to transfer downlink N1 and/or N2 message to the UE and/or AN through the AMF.
Input, Required: CN NF ID, Message type (N1 or N2 or both), Message Container (s) where at least one of the message containers (N1 or N2) is required.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.8 Namf_Communication_N2InfoSubscribe service operation | Service operation name: Namf_Communication_N2InfoSubscribe.
Description: An NF invokes this service operation to subscribe for the delivery of information contained in a specific N2 message type.
Input, Required: CN NF ID, N2 information type to be subscribed.
Input, Optional: None.
Output, Required: None.
Output, Opti... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.9 Namf_Communication_N2InfoUnsubscribe service operation | Service operation name: Namf_Communication_N2InfoUnSubscribe.
Description: An NF can invoke this service operation to unsubscribe for the delivery of information contained in a specific N2 message type.
Input, Required: CN NF ID, N2 information type to unsubscribe.
Input, Optional: None.
Output, Required: None.
Output,... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.10 Namf_Communication_N2InfoNotify service operation | Service operation name: Namf_Communication_N2InfoNotify.
Description: The AMF uses this service operation to notify a particular N2 message information towards the NFs that have subscribed (implicitly or explicitly) for the specific information. This service operation is also used to redirect the N2 message to the AMF ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.11 Namf_Communication_CreateUEContext service operation | Service operation name: Namf_Communication_CreateUEContext
Description: This service operation is used by a source AMF to create the UE context in a target AMF during handover procedures or an initial AMF to relocate the UE context to a target AMF during inter PLMN handover procedure.
Input, Required: 5G-GUTI, UE conte... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.12 Namf_Communication_ReleaseUEContext service operation | Service operation name: Namf_Communication_ReleaseUEContext
Description: This service operation is used by a source AMF to release the UE context in a target AMF during handover cancel procedures.
Input, Required: Handle of the UE context.
Input, Optional: None.
Output, Required: Cause.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.13 Namf_Communication_EBIAssignment service operation | Service operation name: Namf_Communication_EBIAssignment.
Description: The consumer NF uses this service operation to request a bunch of EPS Bearer IDs for a PDU Session and optionally indicate to the AMF the list of EBI(s) to be released.
Inputs, Required: SUPI, PDU Session ID, ARP list.
Input, Optional: Released EBI ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.14 Namf_Communication_AMFStatusChangeSubscribe service operation | Service operation name: Namf_Communication_AMFStatusChangeSubscribe
Description: This service operation is used by an NF to subscribe for AMF Status Change notification.
Input, Required: GUAMI(s).
Input, Optional: None.
Output, Required: None.
Output, Optional: None.
See clause 5.21.2.2 of TS 23.501 [2] for the example... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.15 Namf_Communication_AMFStatusChangeUnSubscribe service operation | Service operation name: Namf_Communication_AMFStatusChangeUnSubscribe
Description: This service operation is used by an NF to unsubscribe for AMF Status Change notification.
Input, Required: GUAMI(s).
Input, Optional: None.
Output, Required: None.
Output, Optional: None.
See clause 5.21.2.2 of TS 23.501 [2] for the exa... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.16 Namf_Communication_AMFStatusChangeNotify service operation | Service operation name: Namf_Communication_AMFStatusChangeNotify
Description: Report AMF Status change (e.g. AMF unavailable) notification to subscribed NFs.
Input, Required: GUAMI(s).
Input, Optional: Target AMF(s) Name associated with the indicated GUAMI.
Output, Required: None.
Output, Optional: None.
See clause 5.2... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.17 Namf_Communication_NonUeN2MessageTransfer service operation | Service operation name: Namf_Communication_NonUeN2MessageTransfer
Description: NF Service Consumer requests to transfer a non-UE specific message to NG-RAN node(s) via N2.
Input, Required: N2 Message Container.
Input, Optional: TAI List, RAT Selector (ng-eNB or gNB), Global RAN Node List, Send Write-Replace-Warning-Ind... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.18 Namf_Communication_NonUeN2InfoSubscribe service operation | Service operation name: Namf_Communication_NonUeN2InfoSubscribe
Description: The NF Service Consumer invokes this service operation to subscribe to the delivery of non-UE specific information from the NG-RAN node sent via N2 to the AMF.
Input, Required: Notification Target Address, Notification Correlation ID, N2 infor... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.19 Namf_Communication_NonUeN2InfoUnSubscribe service operation | Service operation name: Namf_Communication_NonUeN2InfoUnSubscribe
Description: The NF Service Consumer invokes this service operation to unsubscribe to stop notifying non-UE specific N2 information.
Input, Required: Subscription Correlation Id.
Input, Optional: None.
Output, Required: None.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.20 Namf_Communication_NonUeN2InfoNotify service operation | Service operation name: Namf_Communication_NonUeN2InfoNotify
Description: The AMF uses this service operation to notify a particular event towards the NF Service Consumer that has subscribed for the specific information. The AMF receives messages for such events from NG-RAN via N2.
Input, Required: Notification Correla... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.