hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.4.2 The UE is roaming and the selected N3IWF is in the home PLMN | Figure 4.9.2.4.2-1: Handover of a PDU Session procedure from 3GPP access to untrusted non-3GPP access with N3IWF in the HPLMN (home routed roaming)
1. If the UE is not registered via untrusted non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2. This includes the retrieval of the S... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.3 Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.3.0 General | The handover of a PDU Session between 3GPP access and trusted non-3GPP access shall be supported as specified in clause 4.9.2 for all types of handover of a PDU Session between 3GPP access and untrusted non-3GPP access, with the following modifications and clarifications:
- The untrusted non-3GPP access is substituted ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.10 NG-RAN Location reporting procedures | This procedure is used by an AMF to request the NG-RAN to report where the UE is currently located when the target UE is in CM-CONNECTED state. The need for the NG-RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends cancel indication to NG-RAN. This procedure may be used for services th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11 System interworking procedures with EPC | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.0 General | Clause 4.11 includes the following:
- Procedures for interworking with EPS based on N26 interface (clause 4.11.1) and interworking without N26 interface (clause 4.11.2);
- Handover procedures between EPS and 5GC-N3IWF (clause 4.11.3), handover procedures between EPS and 5GC-TNGF (clause 4.11.3a) and handover procedures... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1 N26 based Interworking Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.1 General | N26 interface is used to provide seamless session continuity for single registration mode UE.
Interworking between EPS and 5GS is supported with IP address preservation by assuming SSC mode 1. Interworking between EPS and 5GS is not supported for PDU Sessions with SSC mode 2 or SSC mode 3.
When the UE is served by the ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.2 Handover procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.2.1 5GS to EPS handover using N26 interface | Figure 4.11.1.2.1-1 describes the handover procedure from 5GS to EPS when N26 is supported.
In the case of handover to a shared EPS network, the source NG-RAN determines a PLMN to be used in the target network as specified by TS 23.501 [2]. The source NG-RAN shall indicate the selected PLMN ID to be used in the target ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.2.2 EPS to 5GS handover using N26 interface | 4.11.1.2.2.1 General
N26 interface is used to provide seamless session continuity for single registration mode.
The procedure involves a handover to 5GS and setup of QoS Flows in 5GS.
In the home routed roaming case, the PGW-C+ SMF in the HPLMN always receives the PDU Session ID from UE and provides PDN Connection asso... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.2.3 Handover Cancel | Instead of completing the handover procedure, the source RAN node (NG-RAN, E-UTRAN) may at any time, during the handover procedure, up to the time when a handover command message is sent to the UE, cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the sou... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.3 Idle Mode Mobility procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.3.1 General | When a UE moves from EPC to 5GC, the UE always performs Registration procedure.
When a UE moves from 5GC to EPC, the UE performs either Tracking Area Update or Initial Attach.
The UE performs Tracking Area Update procedure if
- Both the UE and the EPC support "attach without PDN connectivity", or
- The UE has at least ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.3.2 5GS to EPS Idle mode mobility using N26 interface | In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501 [2].
Clause 4.11.1.3.2 covers the case of idle mode mobility from 5GC to EPC. UE performs Tracking Area Update procedure in E-UTRA/EPS when it moves from NG-RAN/5GS to E-UTRA/EPS coverage area.
The procedure involve... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.3.3 EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface | Figure 4.11.1.3.3-1 describes the mobility registration procedure from EPS to 5GS when N26 is supported for idle and connected states.
Figure 4.11.1.3.3-1: EPS to 5GS mobility for single-registration mode with N26 interface
1. The Registration procedure is triggered, e.g. the UE moves into NG-RAN coverage. Step 2 to 9 ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.3.4 EPS to 5GS Mobility Registration Procedure (Idle) using N26 interface with AMF reallocation | During Idle state mobility registration procedure from EPS to 5GS, the initial AMF may select a new AMF based on S-NSSAIs associated with the established PDU Session, received in NAS Registration Request.
Figure 4.11.1.3.4-1: EPS to 5GS mobility with AMF re-allocation for single-registration mode and N26 interface conf... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.4 Procedures for EPS bearer ID allocation | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.4.1 EPS bearer ID allocation | Following procedures are updated to allocate EPS bearer ID(s) towards EPS bearer(s) mapped from QoS flow(s) and provide the EPS bearer ID(s) to the NG-RAN:
- UE requested PDU Session Establishment (Non-roaming and Roaming with Local Breakout (clause 4.3.2.2.1) including Request Types "Initial Request", "Existing PDU Se... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.4.2 EPS bearer ID transfer | Following procedures are updated to transfer EPS bearer ID(s) allocation information to target AMF.
- step 14d in figure 4.11.1.3.3-1 in EPS to 5GS Idle mode mobility with N26 (clause 4.11.1.3.3).
- step 7 in figure 4.11.1.2.2.2-1 in EPS to 5GS handover using N26 interface prepare phase (clause 4.11.1.2.2.2).
Figure 4.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.4.3 EPS bearer ID revocation | Following procedures are updated to revoke the EPS bearer ID(s) assigned to the QoS flow(s):
- UE or network requested PDU Session Release for Non-roaming and Roaming with Local Breakout (clause 4.3.4.2).
- UE or network requested PDU Session Release for Home-routed Roaming (clause 4.3.4.3).
- UE or network requested P... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5 Impacts to EPS Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.1 General | This clause captures changes to procedures in TS 23.401 [13] due to interworking with 5GS based on N26. The handover procedures between EPS and 5GS captured in clause 4.11.1.2 capture impacts to clause 5.5.1.2.2 of TS 23.401 [13] (S1-based handover, normal). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.2 E-UTRAN Initial Attach | The E-UTRAN Initial Attach Procedure specified in clause 5.3.2.1 of TS 23.401 [13] is impacted as shown in Figure 4.11.1.5.2-1 when interworking with 5GS using N26 interface is supported.
Figure 4.11.1.5.2-1: Impacts to E-UTRAN Initial Attach procedure
1. The UE sends an Attach Request message as specified in TS 23.401... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.3 Tracking Area Update | The following changes are applied to clause 5.3.3.1 (Tracking area update procedure with Serving GW change) in TS 23.401 [13]:
- Step 2: The UE shall in Access Stratum signalling include GUMMEI that is mapped from 5G-GUTI following the mapping rules specified in TS 23.501 [2] and the UE indicates it as a native GUMMEI ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.4 Session Management | 4.11.1.5.4.1 PDN Connection Request
The UE Requested PDN Connectivity Procedure specified in clause 5.10.2 of TS 23.401 [13] is impacted as shown in in Figure 4.11.1.5.4.1-1 when interworking with 5GS is supported.
Figure 4.11.1.5.4.1-1: Impacts to UE Requested PDN Connectivity Procedure
1. UE sends a PDN connectivity ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.5 5GS to EPS handover using N26 interface | In step 3 of clause 4.11.1.2.1, the Forward Relocation Request may include new information Return Preferred.
Return Preferred is an indication by the AMF of a preferred return of the UE to the last used 5GS PLMN at a later access change to a 5GS shared network.
RFSP Index in Use Validity Time is provided by the AMF to ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.6 UE triggered Service Request | The following changes are applied to clause 5.3.4.1 (UE triggered Service Request) in TS 23.401 [13]:
- Step 4: MME may steer the UE from EPC by rejecting the service request with an appropriate cause value. The MME should take into account availability of 5GC to the UE and the Preferred and Supported Network Behaviour... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.7 Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation | The following changes are applied to clause 5.3.4B.4 (Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation) in TS 23.401 [13]:
- Step 3: MME may steer the UE from EPC by rejecting the Control Plane Service Request with an appropriate cause value. The MME should take into account ava... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.5.8 Radio Resource Management functions and Information Storage | The following changes are applied to clause 4.3.6 (Radio Resource Management functions) in TS 23.401 [13]:
- At 5GS to EPS mobility or during inter-MME mobility, if RFSP Index in Use Validity Time is received from the AMF or the old MME, the new MME uses the received RFSP Index in use by the time indicated in RFSP Inde... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.1.6 EPS interworking information storing Procedure | Depending on the operator's configuration, the AMF serving the 3GPP access store DNN and SMF+PGW-C FQDN for S5/S8 interface in the UDM using Nudm_UECM_Update service operation when N26 is deployed. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2 Interworking procedures without N26 interface | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.1 General | Clause 4.11.2 defines the procedures to support interworking between 5GS and EPS without any N26 interface between AMF and MME.
Interworking between EPS and 5GS is supported with IP address preservation by assuming SSC mode 1. The UE shall not request handover to EPS of a PDU session with SSC mode 2 or SSC mode 3.
Duri... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.2 5GS to EPS Mobility | The following procedure is used by UEs in single-registration or dual registration mode on mobility from 5GS to EPS.
In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501 [2].
Figure 4.11.2.2-1: Mobility procedure from 5GS to EPS without N26 interface
The UE operating ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.3 EPS to 5GS Mobility | The following procedure is used by UEs in single-registration mode on mobility from EPS to 5GS.
In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501 [2].
This procedure is also used by UEs in dual-registration mode to perform registration in 5GS when the UE is also re... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.4 Impacts to EPS Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.4.1 E-UTRAN Attach | Impact on clause 5.3.2.1 of TS 23.401 [13] from adding support for the optional network functionality dual registration mode:
- Step 1:
The UE constructs the Attach Request message according to the following principles:
- If UE operates in single-registration mode, the UE indicates that it is moving from 5GC and provid... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.4.2 Session Management | 4.11.2.4.2.1 PDN Connection Request
Same procedure as specified in clause 4.11.1.5.4.1 is used with the following clarification:
Step 6. The relevant steps of the procedure as specified in the figure above are executed with the following modification:
- Additional condition to trigger Notify Request to HSS in step 15 o... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.2.4.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.3 Handover procedures between EPS and 5GC-N3IWF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.3.1 Handover from EPS to 5GC-N3IWF | Figure 4.11.3.1-1: Handover from EPS to 5GC-N3IWF
0. Initial status: one or more PDN connections have been established in EPC between the 5G capable UE and the PGW via E-UTRAN.
1. The UE initiates Registration procedure on untrusted non-3GPP access via N3IWF (with 5G-GUTI is available or SUCI if not) per clause 4.12.2.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.3.2 Handover from 5GC-N3IWF to EPS | Figure 4.11.3.2-1: Handover from 5GC-N3IWF to EPS
0. Initial status: one or more PDU Sessions have been established in 5GC between the UE and the SMF/UPF via untrusted non-3GPP access and N3IWF. During PDU Session setup and in addition to what is specified in clause 4.3.2.2.1 and clause 4.3.2.2.2, the AMF includes an i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4 Handover procedures between EPC/ePDG and 5GS | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.1 Handover from EPC/ePDG to 5GS | Figure 4.11.4.1-1: Handover from EPC/ePDG to 5GS
0. Initial status: one or more PDN Connections have been established between the UE and the EPC/ePDG via untrusted non-3GPP access as specified in clauses 7.2.4 and 7.6.3 of TS 23.402 [26] with modification described in clauses 4.11.4.3.3 and 4.11.4.3.5.
1. For the UE to... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.2 Handover from 5GS to EPC/ePDG | Figure 4.11.4.2-1 describes the procedure for handing over a PDU Session from 5GS to EPC/ePDG. The UE shall not request a handover of a PDU session with SSC mode 2 or SSC mode 3 to EPC/ePDG.
Figure 4.11.4.2-1: Handover from 5GS to EPC/ePDG
NOTE: In step 2, the UE can also trigger this procedure when 5G NAS (i.e. N1 mod... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3 Impacts to EPC/ePDG Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.1 General | This clause captures enhancements to procedures in TS 23.402 [26] to support interworking with 5GS. The architecture for interworking is shown in clause 4.3.4 of TS 23.501 [2]. with the ePDG connected to SMF+PGW-C and UPF+PGW-U using GTP based S2b. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.2 ePDG FQDN construction | Clause 4.5.4.2 of TS 23.402 [26] applies with the following modification:
- Tracking/Location Area Identity FQDN: When the 5GC NAS capable UE uses the Tracking Area of the NG-RAN when the UE is registered with the 5GC when constructing the Tracking Area Identity FQDN. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.3 Initial Attach with GTP on S2b | The procedure in clause 7.2.4 of TS 23.402 [26] applies with the following modifications:
- In Step A.1 IKEv2 tunnel establishment procedure, the 5GC NAS capable UE shall indicate its support of 5GC NAS in IKEv2. The UE allocates a PDU Session ID and also includes it in IKEv2 signalling sent to the ePDG. For 5GC NAS ca... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.4 Interaction with PCC | When interworking with 5GS is supported and a SMF+PGW-C is selected by the ePDG, policy interactions between PDN GW and PCRF specified in TS 23.402 [26] are replaced by equivalent interactions between SMF+PGW-C and PCF as captured in clause 4.11.0a.2.
If SMF+PGW-C is selected and interaction with PCF is required for a ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.5 UE initiated Connectivity to Additional PDN with GTP on S2b | The procedure in clause 7.6.3 of TS 23.402 [26] references the Initial Attach procedure with GTP on S2b. Impacts to the initial attach procedure with GTP on S2b are captured in clause 4.11.4.3.3 above. If the additional PDN connection is for emergency service, impact as captured in clause 4.11.4.3.3a applies. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.6 Use of N10 interface instead of S6b | This clause applies to scenarios when ePDG is connected to SMF+PGW-C and S6b in not used. It is applicable for procedures specified in TS 23.402 [26] including mobility between EPC/ePDG and EPC/EUTRAN and also for mobility between EPC/ePDG and 5GS.
When S6b, as specified in TS 23.402 [26], is not deployed between SMF+P... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.4.3.7 5GC NAS capability (re-)enabled and disabled | When 5G NAS (i.e. N1 mode) capability is (re-)enabled, the UE does not report the UE capability change to ePDG.
NOTE: The ePDG is not aware of the N1 mode Enabled / Disabled status at the UE. If a standalone PGW was previously selected, the ePDG is not able to initiate PDN disconnection with reactivation required for t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5 Impacts to 5GC Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.1 General | This clause captures impacts to 5GC procedures in other clauses of this specification to support interworking with EPS. These impacts are applicable to interworking based on N26 and interworking without N26 for PDU Session via 3GPP access and for PDU Session via non-3GPP access.
This clause also captures the impact to ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.2 Registration procedure | The following impacts are applicable to clause 4.2.2.2 (Registration procedure):
- Step 1: If the Registration type is set to "Initial Registration", the UE is not registered in EPS and the UE provides the 5G-GUTI mapped from EPS GUTI as the old GUTI, then the UE includes complete EPS Attach Request in the Registration... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.3 UE Requested PDU Session Establishment procedure | For PDU Session via 3GPP, the following impacts are applicable to clause 4.3.2.2 (UE Requested PDU Session Establishment procedure) to support interworking with EPS:
In clause 4.3.2.2.1 Non-roaming and Roaming with local breakout:
- Step 1: In PDU Session Establishment Request message, the UE includes also the UE capab... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.4 UE or Network Requested PDU Session Modification procedure | For PDU Session via 3GPP, the following impacts are applicable to clause 4.3.3.2 (UE or network requested PDU Session Modification (non-roaming and roaming with local breakout)) to support interworking with EPS:
- Step 1: In addition to the triggers listed in step 1 of clause 4.3.3.2, the procedure may be also triggere... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.5 Xn based inter NG-RAN handover | The following impacts are applicable to clause 4.9.1.2.1 (General) to support interworking with EPS:
- If there is Mapping between EBI(s) and QFI(s) for the UE in the source NG-RAN, the source NG-RAN sends the Mapping to target NG-RAN during handover. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.6 Inter NG-RAN node N2 based handover | The following impacts are applicable to clause 4.9.1.3.2 (Preparation phase) to support interworking with EPS:
- Step 7: If the PDU session supports EPS interworking, the N2 SM information contains the Mapping between EBI(s) and QFI(s). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.7 UE or Network Requested PDU Session Release procedure | The following impacts are applicable to clause 4.3.4.2 (UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout) to support interworking with EPS:
- Step 2b: If the released PDU Session used APN Rate Control in EPC then the PGW-U+UPF provides the APN Rate Control Status to the SMF if... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.8 Network Configuration | To avoid the need for identifier coordination between AMFs and MMEs, the AMF provides to the NG-RAN its served GUAMIs by separating the values between native AMF values and the values mapped from MME. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.9 Network Slice Admission Control | Support of NSAC in conjunction with interworking with EPC is described in clause 5.15.11.5 of TS 23.501 [2].
If EPS counting is required for a network slice, the SMF+PGW-C performs NSACF discovery that supports controlling the maximum number of PDU sessions per network slice as described in clause 6.3.22 of TS 23.501 [... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.10 UE Policy Association control | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.5.10.1 UE Policy Association Establishment for URSP delivery in EPS | The following impacts are applicable to clause 4.16.11 (UE Policy Association Establishment procedure) during initial registration or during UE registration with 5GS when the UE moves from EPS to 5GS:
In addition to step 3 in clause 4.16.11, if the indication about the support of provisioning of URSP rules in EPS is re... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.6 Interworking for common network exposure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.6.1 Subscription and Notification of availability or expected level of support of a service API | Figure 4.11.6.1 1 represent the information flow subscribing and notifying the availability or expected level of support of a service API.
For the subscription to Nnef_APISupportCapability service, the subscription request may include the Duration of Reporting. If the Duration of Reporting is expired, the SCEF+NEF dele... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.6.2 Unsubscribing to N11otification of availability or expected level of support of a service API | Figure 4.11.6.2 1 represent the information flow unsubscribing to Continuous report type subscription of the availability or expected level of support of a service API.
If the AF invokes Nnef_APISupportCapability_Subscribe service to SCEF+NEF node with the Duration of Reporting parameter for Continuous report type, the... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.11.6.3 Configuration of monitoring events for common network exposure | Figure 4.11.6.3-1 represent the information flow to configure monitoring events applicable to both EPC and 5GC using 5GC procedures towards UDM in scenarios where interworking between 5GS and EPC is possible.
Figure 4.11.6.3-1: Configuration of monitoring events for common network exposure
1. The AF configures a monito... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12 Procedures for Untrusted non-3GPP access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.1 General | Clause 4.12 defines the procedures to support Untrusted non-3GPP access by describing the differences compared to the defined procedures in other clauses. The procedures for Untrusted non-3GPP access are also used by a UE that accesses SNPN services via a PLMN over 3GPP access. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.2 Registration via Untrusted non-3GPP Access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.2.1 General | Clause 4.12.2 specifies how a UE can register to 5GC via an untrusted non-3GPP Access Network. It is based on the Registration procedure specified in clause 4.2.2.2.2 and it uses a vendor-specific EAP method called "EAP-5G". The EAP-5G packets utilize the "Expanded" EAP type and the existing 3GPP Vendor-Id registered w... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.2.2 Registration procedure for untrusted non-3GPP access | The signalling flow in Figure 4.12.2.2-1 does not show all the details of a registration procedure via untrusted non-3GPP access. It shows primarily the steps executed between the UE and N3IWF. All the details of a registration procedure, including interactions with UDM, etc. are specified in clause 4.2.2.2.2.
Figure 4... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.2.3 Emergency Registration for untrusted non-3GPP Access | Emergency Registration procedure is used by UEs requiring to perform emergency services but cannot gain normal services from the network. These UEs are in limited service state as defined in TS 23.122 [22].
The regular registration procedure described in clause 4.12.2 applies with the following differences:
- If the UE... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.3 Deregistration procedure for untrusted non-3gpp access | Figure 4.12.3-1: Deregistration procedure for untrusted non-3gpp access
1. The Deregistration procedure is triggered by one of the events:
1a. For UE-initiated Deregistration as in steps from 1 to 7 of Figures 4.2.2.3.2-1.
1b. For network initiated deregistration as in steps from 1 to 6 of Figure 4.2.2.3.3-1.
If the UE... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.4 N2 procedures via Untrusted non-3GPP Access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.4.1 Service Request procedures via Untrusted non-3GPP Access | The Service Request procedure via Untrusted non-3GPP Access shall be used by a UE in CM-IDLE state over non-3GPP access to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access.
The Service Req... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.4.2 Procedure for the UE context release in the N3IWF | This procedure is used to release the N2 signalling connection and the N3 User Plane connection. If the procedure is initiated by the AMF the IKEv2 SA for a UE is being released. The procedure will move the UE from CM-CONNECTED to CM-IDLE in AMF and all UE related context information is deleted in the N3IWF.
Both N3IWF... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.4.3 CN-initiated selective deactivation of UP connection of an existing PDU Session associated with Untrusted non-3GPP Access | The procedure described in clause 4.3.7 (CN-initiated selective deactivation of UP connection of an existing PDU Session) is used for CN-initiated selective deactivation of UP connection for an established PDU Session associated with non-3GPP Access of a UE in CM-CONNECTED state, with the following exceptions:
- The NG... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.5 UE Requested PDU Session Establishment via Untrusted non-3GPP Access | Clause 4.12.5 specifies how a UE can establish a PDU Session via an untrusted non-3GPP Access Network as well as to hand over an existing PDU Session between 3GPP access and non-3GPP access. The procedure applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios.
For non-roaming and LBO scena... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.6 UE or Network Requested PDU Session Modification via Untrusted non-3GPP access | The UE or network requested PDU Session Modification procedure via untrusted non-3GPP access is depicted in figure 4.12.6-1. The procedure applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios.
For non-roaming and LBO scenarios, the functional entities in the following procedures are loca... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.7 UE or network Requested PDU Session Release via Untrusted non-3GPP access | Clause 4.12.7 specifies how a UE or network can release a PDU Session via an untrusted non-3GPP Access Network. The UE requested PDU Session Release procedure via Untrusted non-3GPP access applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios.
For non-roaming and LBO scenarios, if the UE ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.12.8 Mobility from a non-geographically selected AMF to a geographically selected AMF | This procedure describes the AMF change that takes place when an UE initially served via non-3GPP access by an AMF selected based on non-geographical criteria (e.g. because the UE had no 3GPP access coverage or because only non-geographically selectable N3IWF are deployed) gets 3GPP access and is now to be served by an... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13 Specific services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.1 General | Clause 4.13 defines the additional procedures or additions to the existing procedures to support specific services such as SMS over NAS. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.2 Application Triggering | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.2.1 General | The AF invokes the Nnef_Trigger service to request that the network send an Application trigger to the UE. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.2.2 The procedure of "Application Triggering" Service | Figure 4.13.2.2-1: Device triggering procedure via Nnef
1. The AF determines the need to trigger the device. If the AF has no contact details for the NEF, it shall discover and select NEF services.
2. The AF invokes the Nnef_Trigger_Delivery request service.
3. The NEF checks that the AF is authorised to send trigger r... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3 SMS over NAS procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.1 Registration procedures for SMS over NAS | Figure 4.13.3.1-1: Registration procedure supporting SMS over NAS
1. During Registration procedure in 5GS defined in Figure 4.2.2.2.2-1, to enable SMS over NAS transporting, the UE includes an "SMS supported" indication in Registration Request in step 1-3 indicating the UE's capability for SMS over NAS transport. The "... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.2 Deregistration procedures for SMS over NAS | If UE indicates to AMF that it no longer wants to send and receive SMS over NAS (e.g. not including "SMS supported" indication in subsequent Registration Request message) or AMF considers that UE is deregistered on specific Access Type(s) or AMF receives Deregistration Notification from UDM for specific Access Type(s) ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.3 MO SMS over NAS in CM-IDLE (baseline) | Figure 4.13.3.3-1: MO SMS over NAS
1. The UE performs domain selection for UE originating SMS as defined in clause 5.16.3.8 of TS 23.501 [2] if SMS delivery via non 3GPP access is allowed and possible. If an UE under CM-IDLE state is going to send uplink SMS message, then UE and network perform the UE Triggered Service... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.4 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.5 MO SMS over NAS in CM-CONNECTED | MO SMS in CM-CONNECTED State procedure is specified by reusing the MO SMS in CM-IDLE State without the UE Triggered Service Request procedure. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.6 MT SMS over NAS in CM-IDLE state and RRC_INACTIVE with CN based MT communication state via 3GPP access | Figure 4.13.3.6-1: MT SMS over NAS in CM-IDLE and RRC_INACTIVE state via 3GPP access
1-3 MT SMS interaction between SC/SMS-GMSC/UDM follow the procedure as defined in TS 23.040 [7] or TS 23.540 [84]. If there are two AMFs serving the UE, one is for 3GPP access and another is for non-3GPP access, there are two SMSF addr... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.7 MT SMS over NAS in CM-CONNECTED state via 3GPP access | MT SMS in CM-CONNECTED procedure is specified by reusing the MT SMS in CM-IDLE state with the following modification:
- There is no need for the AMF to perform Paging of the UE and can immediate continue with a message to SMSF via N20 to allow the SMSF to start forward the MT SMS.
- When the AMF receives an MT-SMS from... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.8 MT SMS over NAS via non-3GPP access | MT SMS procedure via non-3GPP access is specified by reusing the MT SMS via 3GPP access in CM-CONNECTED state with the following modification:
- If the UE access to the network via both 3GPP and non-3GPP accesses and the AMF determines to deliver MT-SMS via non-3GPP access based on operator policy in step 4, the NAS me... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.3.9 Unsuccessful Mobile terminating SMS delivery re-attempt | The procedure of Unsuccessful Mobile terminating SMS delivery re-attempt is defined as follows:
- For SMS delivery, the SMSF and the UDM support the SMSF and UDM role as specified in TS 23.040 [7].
- If the UE is registered over both 3GPP access and non-3GPP access in the same AMF (i.e. the UE is registered in the same... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.13.4 Emergency Services |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.