hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.1 General | NOTE: The PFDF service is functionality within the NEF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.2 PFD management via NEF (PFDF) | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.2.1 PFD management triggered by AF | Figure 4.18.2.1-1: Procedure for PFD management via NEF (PFDF) triggered by AF
1. The AF invokes the Nnef_PFDManagement_Create/Update/Delete service. The Allowed Delay is an optional parameter. If the Allowed Delay is included, it indicates that the list of PFDs in this request should be provisioned within the time int... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.2.2 PFD management based on PFD Determination analytics | Figure 4.18.2.2-1 shows the procedure that NEF (PFDF) determines the PFD information for the known Application Identifier(s), based on the PFD Determination analytics information notified/responded from the subscribed/requested NWDAF. The procedure enables the NEF (PFDF) to determine whether to create/update/delete PFD... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.3 PFD management in the SMF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.3.1 PFD Retrieval by the SMF | This procedure enables the SMF to retrieve PFDs for an Application Identifier from the NEF (PFDF) when a PCC rule with this Application Identifier is provided/activated and PFDs provided by the NEF (PFDF) are not available at the SMF.
In addition, this procedure enables the SMF to retrieve PFDs from the NEF (PFDF)when ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.18.3.2 Management of PFDs in the SMF | This procedure enables the provisioning, modification or removal of PFDs associated with an application identifier in the SMF. Either the complete list of all PFDs of all application identifiers, the complete list of all PFDs of one or more application identifiers or a subset of PFDs for individual application identifi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.19 Network Data Analytics | The system procedures for Network Data Analytics are defined in clause 6 of TS 23.288 [50]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.19.1 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.19.2 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.20 UE Parameters Update via UDM Control Plane Procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.20.1 General | The purpose of the control plane solution for update of UE parameters is to allow the HPLMN, SNPN, or CH to update the UE with a specific set of parameters, generated and stored in the UDM, by delivering protected UDM Update Data via NAS signalling. The HPLMN, SNPN, or CH updates such parameters based on the operator p... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.20.2 UE Parameters Update via UDM Control Plane Procedure | Figure 4.20.2-1: UE Parameters Update via UDM Control Plane Procedure
1. UDM decides to perform UE parameter update.
2. From UDM to the AMF: The UDM notifies the changes of the information related to the UE to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification s... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.20.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.21 Secondary RAT Usage Data Reporting Procedure | The procedure in Figure 4.21-1 may be used to report Secondary RAT Usage Data from NG-RAN node to the AMF. It is executed by the NG-RAN node to report the Secondary RAT Usage Data information towards AMF which is then reported towards SMF.
The procedure in Figure 4.21-2 may be used to report the Secondary RAT Usage Dat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22 ATSSS Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.1 General | This clause specifies the procedures that enable the support of Access Traffic Steering, Switching and Splitting (ATSSS), as defined in clause 5.32 of TS 23.501 [2]. These procedures can be applied only by ATSSS-capable UEs and 5GC networks.
The key enabler of ATSSS is the Multi Access-PDU (MA PDU) Session. As specifie... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2 UE Requested MA PDU Session Establishment | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.0 Overview | Clauses 4.22.2.1 and 4.22.2.2 specify the MA PDU Session establishment procedures with both 3GPP access and non-3GPP access connected to 5GC. Clause 4.22.2.3 specifies the MA PDU Session establishment procedure with 3GPP access connected to EPC and non-3GPP access connected to 5GC. Clause 4.22.2.4 specifies the MA PDU ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.1 Non-roaming and Roaming with Local Breakout | The signalling flow for a MA PDU Session establishment when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.2.2.1-1 with the following differences and clarifications:
- The PDU Session Establishment Request message ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.2 Home-routed Roaming | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.2.1 Home-routed Roaming - UE registered to the same PLMN | When the UE is registered to the same VPLMN over 3GPP access and non-3GPP access, the MA PDU Session is established as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") with the differences and clarifications:
- The PDU Session Establishment Request message may... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.2.2 Home-routed Roaming - UE registered to different PLMNs | When the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the MA PDU Session is established first over one access as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") and then over the other access with the following differences and cla... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.3 MA PDU Session establishment with 3GPP access connected to EPC and non-3GPP access connected to 5GC | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.3.1 General | This clause applies to the case where, for a PDU Session, multi-access connectivity via both EPC (over 3GPP access) and 5GC (over non-3GPP access) is supported and allowed in the UE and network. In this case, multi-access connectivity using ATSSS via both 3GPP access to EPC and non-3GPP access to 5GC may be provided as... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.3.2 PDN Connections and Multi Access PDU Sessions | When the UE wants to request a new PDN Connection in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session:
- The UE requests establishment of a new PDN Connection when the UE is registered via 3GPP access in EPS using PDN Connection Establishment procedure. The UE provides vi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.3.3 QoS Support | The general principles for QoS support with ATSSS as described in clause 5.32.4 of TS 23.501 [2], apply, with the clarifications provided in this clause.
With an MA PDU Session associated to a PDN Connection on EPS there may be separate user-plane tunnels between the AN and the PGW-U+UPF, one associated with 3GPP acces... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.4 MA PDU Session establishment with non-3GPP access connected to EPC and 3GPP access connected to 5GC | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.4.1 General | This clause applies to the case where, for a PDU Session, multi-access connectivity via both EPC (over non-3GPP access) and 5GC (over 3GPP access) is supported and allowed in the UE and network. In this case, multi-access connectivity using ATSSS via both non-3GPP access to EPC and 3GPP access to 5GC may be provided as... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.4.2 PDN Connections and Multi Access PDU Sessions | When the UE wants to request a new PDN Connection in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session:
- The UE requests establishment of a new PDN Connection when the UE is registered via non-3GPP access in EPS using PDN Connection Establishment procedure. The UE provide... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.2.4.3 QoS Support | The general principles for QoS support with ATSSS as described in clause 4.22.2.3.3 apply, with the clarifications below:
- With an MA PDU Session associated to a PDN Connection on EPS there may be separate user-plane tunnels between the AN and the PGW-U+UPF, one associated with non-3GPP access in EPC and one associate... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.3 UE Requested PDU Session Establishment with Network Modification to MA PDU Session | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.3.1 Overview | When an ATSSS-capable UE requests to establish a single-access PDU Session, but no policy in the UE and no local restrictions mandate a single access, the 5GC network may decide to modify it to a Multi-Access PDU (MA PDU) Session. This decision may be taken when e.g. the SMF wants to offload some traffic of the request... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.3.2 Non-roaming or roaming with local breakout | In the case of non-roaming or roaming with local breakout, the procedure for establishing a MA PDU Session when the UE requests a single-access PDU Session is the same with the procedure specified in clause 4.22.2.1.1, with the following clarifications and modifications:
- In step 1, the UE sets Request Type to initial... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.3.3 Home-routed, the UE registered to the same VPLMN over both access | In the case of home-routed roaming, when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access, the procedure for establishing a MA PDU Session when the VPLMN is ATSSS capable and the UE requests a single-access PDU Session but no policy in the UE and no local restrictions mandate a single access,... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.3.4 Home-routed, the UE registered to different PLMNs over both access | In the case of home-routed roaming, when the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the procedure for establishing a MA PDU Session when the UE requests a single-access PDU Session in an ATSSS capable PLMN but no policy in the UE and no local restrictions mandate a single access, is t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.4 Access Network Performance Measurements | The PMF of UE side or/and UPF side should be able to correlate the measurement packets with the corresponding access type in order to get the accurate measurement result for each access. The PMF of UE side correlates the sent measurement request and received measurement response messages via the same access type and th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.5 Reporting of Access Availability | After the MA PDU session is established, if Reporting of Access Availability is required by network, the UE performs detection of the unavailability and availability of an access as described in clause 5.32.5.3 of TS 23.501 [2]. To report the availability/unavailability of the access, the UE sends the PMF-Access Report... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6 EPS Interworking | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.1 General | This clause includes mobility procedures for interworking with EPS. MA PDU Session establishment procedures with user plane resources in EPS are described in clause 4.22.2.3 and clause 4.22.2.4. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2 Impacts to EPS interworking procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2.1 5GS to EPS handover using N26 interface | Based on the signalling flow in Figure 4.11.1.2.1-1, the procedure is performed with the following differences and modifications:
- Step 2 is also performed with all the SMF+PGW-Cs corresponding to MA PDU Sessions with allocated EBI(s).
- In step 12e, the AMF requests the release of the 3GPP access of the MA PDU Sessio... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2.2 5GS to EPS idle mode mobility using N26 interface | Based on the signalling flow in Figure 4.11.1.3.2-1, the procedure is performed with the following differences and modifications:
- Step 5a is also performed with all the SMF+PGW-Cs corresponding to the MA PDU Sessions with allocated EBI(s).
- In step 12, if the MA PDU Session is established in both 3GPP and non-3GPP a... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2.3 EPS bearer ID allocation | Based on the signalling flow in Figure 4.11.1.4.1-1, additionally for the MA PDU Session, with the following differences and clarifications:
- In step 1, the following procedures and relevant steps are also initiated during the UE Requested MA PDU Session Establishment, the UE Requested PDU Session Establishment with N... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2.4 EPS bearer ID revocation | Based on the clause 4.11.1.4.3, additionally the following procedures are updated to revoke the EPS bearer ID(s) assigned to the QoS Flow(s) in the MA PDU Session:
- UE or network requested MA PDU Session Release (non-roaming and roaming with local breakout) in clause 4.22.10.2.
- UE or network requested MA PDU Session... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.2.5 5GS to EPS mobility without N26 interface | Based on the signalling flow in Figure 4.11.2.2-1, the procedure is performed with the following differences and modifications:
- In step 10 (and step 13 in clause 4.11.2.4.1), if the MA PDU Session is established in both 3GPP and non-3GPP accesses and the MA PDU Session is moved to EPS and if the UE and the network do... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.6.3 Network Modification to MA PDU Session after a UE moving from EPC | Figure 4.22.6.3-1 describes procedure for Network Modification to MA PDU Session after a UE is moving from EPS.
Figure 4.22.6.3-1: Network Modification to MA PDU Session after a UE moving from EPS
1. When the network supports interworking with N26 interface, a PDN Connection can be moved from EPS to 5GS as described in... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.7 Adding / Re-activating / De-activating User-Plane Resources | If the UE has established a MA PDU Session but the user-plane resources over one access of the MA PDU Session have not been established, then:
- If the UE wants to add user-plane resources over this access, the UE shall initiate the UE Requested PDU Session Establishment procedure over this access, as specified in clau... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.8 UE or network requested MA PDU Session Modification | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.8.1 General | This procedure is triggered in the following cases:
- QoS Flow creation / modification (including GBR QoS Flow movement).
- Update of ATSSS rules and/or N4 rules. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.8.2 UE or network requested MA PDU Session Modification (non-roaming and roaming with local breakout) | The signalling flow for a MA PDU Session Modification when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.3.2-1 with the following differences and clarifications:
- In step 1b, the SMF may decide to update ATSSS ru... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.8.3 UE or network requested MA PDU Session Modification (home-routed roaming) | The signalling flow for a MA PDU Session Modification when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on the signalling flow in Figure 4.3.3.3-1 with the following differences and clarifications:
- In step 1b, the H-SMF ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9 Connection, Registration and Mobility Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9.1 Registration procedures | Support for using the Registration procedures for non-3GPP access path switching is described in clause 4.22.9.5.
The signalling flow for a Registration is based on the signalling flow in Figure 4.2.2.2.2-1 with the following differences and clarifications:
- In step 1, if the UE wants to re-activate the user plane of ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9.2 UE Triggered Service Request | The signalling flow for a UE Triggered Service Request is based on the signalling flow in Figure 4.2.3.2-1 with the following differences and clarifications:
- In step 1, if the UE wants to re-activate the user plane of the MA PDU Session(s) over the access the Service Request message is sent to, the UE indicates PDU S... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9.3 N2 based handover | Inter NG-RAN node N2 based handover, as described in clauses 4.9.1.3.2 and 4.9.1.3.3, is supported for the 3GPP access with the differences and clarifications described below.
- In step 2 of clause 4.9.1.3.2, the S-AMF determines whether or not the T-AMF supports ATSSS based on the supported features of the T-AMF provi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9.4 Network Triggered Service Request | The signalling flow for a Network Triggered Service Request is based on the signalling flow in Figure 4.2.3.3-1 with the following differences and clarifications:
- In step 2a, the SMF determines over which access (3GPP access or non-3GPP access or both accesses) the user plane resources need to be activated for the MA... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.9.5 Registration procedures for non-3GPP access path switching | If the UE supports non-3GPP access path switching and the AMF indicates that the network supports non-3GPP access path switching as described in clause 4.22.2, the UE may trigger a Mobility Registration Update via a new non-3GPP access to switch traffic from an old non-3GPP access (i.e. TNGF or N3IWF) to the new non-3G... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.10 MA PDU Session Release | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.10.1 General | The MA PDU Session Release procedure is used to release the MA PDU Session, or release the MA PDU Session over a single access. The MA PDU Session Release over a single access may be triggered by the network due to e.g. when the UE is deregistered over an access or when the S-NSSAI of the MA PDU Session is no longer in... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.10.2 UE or network requested MA PDU Session Release (non-roaming and roaming with local breakout) | The signalling flow for a MA PDU Session Release when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.4.2-1 with the following differences and clarifications:
- In step 1, if the AMF needs to release the MA PDU Sess... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.22.10.3 UE or network requested MA PDU Session Release (home-routed roaming) | The signalling flow for a MA PDU Session Release when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on the signalling flow in Figure 4.3.4.3-1 with the following differences and clarifications:
- In step 1, if the V-AMF nee... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23 Support of deployments topologies with specific SMF Service Areas | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.1 General | This clause captures changes to 5GC procedures in other clauses of this specification and new procedures to support deployments topologies with specific SMF Service Areas that are defined in clause 5.34 of TS 23.501 [2].
In the case of roaming for a Home Routed PDU Session the following cases may occur:
- A UE moves ou... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.2 I-SMF selection | For non-roaming or LBO roaming case, the AMF selects an SMF serving the PDU Session as described in clause 4.3.2.2.3. If the service area of the selected SMF does not control UPF that can serve the UE location, the AMF selects an I-SMF as described in clause 5.34.3 of TS 23.501 [2]. Additionally, if Local Offloading Ma... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.3 Registration procedure | The following impacts are applicable to clause 4.2.2.2 (Registration procedure) when the UE has established PDU Session(s):
- Step 5: The UE context transferred from old AMF includes SMF information. If I-SMF is available for the PDU Session(s), the received SMF information includes I-SMF information and SMF informatio... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.4 Service Request procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.4.1 General | The following two scenarios are considered:
- The I-SMF is available for the PDU Session and I-SMF is not changed or removed during the service request procedure. The procedure to support this scenario is described in clause 4.23.4.2.
- The I-SMF is inserted, changed or removed during service request procedure. The pro... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.4.2 UE Triggered Service Request without I-SMF change/removal | When both I-SMF and SMF are available for a PDU session and no I-SMF change or removal is needed during the service request procedure, the procedure in this clause is used. Compared to the procedure in clause 4.2.3.2, the SMF is replaced with the I-SMF and the impacted intermediate UPF(s) are UPFs that are controlled b... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.4.3 UE Triggered Service Request with I-SMF insertion/change/removal | When Local Offloading Management specified in TS 23.548 [74] is not applied, as part of a UE Triggered Service Request, I-SMF is to be inserted, changed or removed, the procedure in this clause is used. It includes the following cases:
- the UE moves from SMF service area to new I-SMF service area, a new I-SMF is inser... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.4.4 Network Triggered Service Request | For network triggered service request procedure, if the procedure is triggered by downlink packet, the procedure in clause 4.2.3.3 are impacted as following:
- if the I-SMF is available for the PDU Session, the procedure is triggered by I-SMF. Correspondingly, the SMF in that procedure is replaced by the I-SMF.
- The r... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.5 PDU Session Management procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.5.1 PDU Session establishment procedure | For non roaming or LBO roaming, it includes the following cases:
- If the service area of the selected SMF includes the current UE location and if the Local Offloading Management specified in TS 23.548 [74] is not applied, the UE requested PDU Session Establishment procedure is same as described in clause 4.3.2.2.1.
NO... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.5.2 PDU Session Release procedure | For the non roaming or LBO roaming case, the procedure defined in clause 4.3.4.3 (UE or network requested PDU Session Release for Home-routed Roaming) is used to release the PDU Session, with the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. Also if t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.5.3 PDU Session modification procedure | For the non-roaming or LBO roaming case, the procedure defined in clause 4.3.3.3 (UE or network requested PDU Session Modification for Home-routed Roaming) is used to modify the PDU Session, with the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively.
If th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.5.4 SMF triggered I-SMF selection or removal | Figure 4.23.5.4-1: SMF triggered I-SMF selection or removal
1. The PCF sends to the SMF PCC rule(s) which may include DNAI(s) for the PDU sessions by invoking Npcf_SMPolicyControl_UpdateNotify service operation.
Based on the received DNAI(s), the SMF may subscribe to UE mobility event notification from the AMF (e.g. UE... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.6 I-SMF Related Procedures with PCF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.6.1 General | This clause provides PCC related details for scenarios including an I-SMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.6.2 Policy Update Procedures with I-SMF | Figure 4.23.6-1 shows procedures related to provisioning of PCC rules containing traffic steering information related to an I-SMF.
Figure 4.23.6-1: Policy Update procedure
In cases where step 1a in figure 4.23.6-1 is triggered in response to PCF receiving AF request, below steps 3 and 4 are applicable, in addition to t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.6.3 Reporting UP path change to the AF | Figure 4.23.6.3-1 shows procedures related Reporting UP path change to the AF.
Figure 4.23.6.3-1: Reporting UP path change to the AF
1a. I-SMF indicates that UP path change may occur for the PDU Session via Nsmf_PDUSession_Update Request as described in clause 4.23.9; the SMF responds to the I-SMF.
2. If early notifica... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7 Inter NG-RAN node N2 based handover | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.1 General | The following two scenarios are considered:
- The I-SMF is available for the PDU Session and I-SMF is not changed or removed during the inter NG-RAN node N2 based handover procedure. The procedure to support this scenario is described in clause 4.23.7.2.
- The I-SMF is inserted, changed or removed during inter NG-RAN n... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.2 Inter NG-RAN node N2 based handover without I-SMF change/removal | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.2.1 General | When both I-SMF and SMF are available for a PDU Session and no I-SMF change or removal is needed during inter NG-RAN node N2 handover procedure, the procedure defined in clause 4.9.1.3.2, 4.9.1.3.3 are used with the following differences. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.2.2 Preparation phase | Compared to the procedure in clause 4.9.1.3.2, the SMF interacting with the S-UPF, T-UPF, S-AMF and T-AMF is the I-SMF. The difference is following:
- Step 3: The N14 context exchanged between S-AMF and T-AMF contains the SM Context ID at I-SMF, or SM Context ID at SMF if I-SMF is not applicable before.
- Step 4: The T... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.2.3 Execution phase | Compared to the procedure for execution phase in 4.9.1.3.3, the SMF interacting with the S-UPF, T-UPF, S-AMF and T-AMF is the I-SMF. The difference is as following:
- Step 10a: If I-SMF is available for a PDU Session and the existing intermediate S-UPF is re-allocated, i.e. a new T-UPF is selected, the I-SMF invokes an... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.2.4 Handover Cancel | The home routed roaming procedure defined in clause 4.9.1.4 is applied, with V-SMF replaced by I-SMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.3 Inter NG-RAN node N2 based handover with I-SMF insertion/change/removal | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.3.1 General | When I-SMF is inserted or changed or removed during inter NG-RAN node N2 handover, the procedures defined in this clause are used.
To support the EAS session continuity upon UL CL relocation, a N9 forwarding tunnel to support the EAS session continuity is established and released between the Source UL CL and Target UL ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.3.2 Preparation phase | Figure 4.23.7.3.2-1: Inter NG-RAN node N2 based handover, preparation phase, with I-SMF insertion/change/removal
1. Steps 1-3 in clause 4.9.1.3.2 are performed.
2. For PDU sessions in the UE context, the Target AMF determines whether a (new) Target I-SMF needs to be selected based on Target UE location and service area... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.3.3 Execution phase | Figure 4.23.7.3.3-1: Inter NG-RAN node N2 based handover, execution phase, with I-SMF insertion/change/removal
1. Steps 1-6 in clause 4.9.1.3.3 are performed with the following change:
Step 6a: For PDU sessions in the UE context, if the I-SMF is either to be changed, or to be removed, the T-AMF includes an indication i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.7.3.4 Handover Cancel | Figure 4.23.7.3.4-1: Handover Cancel procedure
1. Step 1~3 in clause 4.11.1.2.3 are performed.
Case: I-SMF Change, step 4~9 are skipped for I-SMF Insertion case and I-SMF Removal case.
4. T-AMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication).
The target AMF invokes Nsmf_PDUSessio... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.8 AN Release procedure involving I-SMF | For the AN release procedure, if the PDU Session involves an I-SMF, the procedure defined in clause 4.2.6 applies with:
- The SMF and UPF in the procedure replaced by the I-SMF and I-UPF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9 Branching Point or UL CL controlled by I-SMF | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.0 Overview | The procedures in this clause describe the Addition, Removal and Change of PDU Session Anchor (PSA2), Branching Point or UL CL controlled by I-SMF. They all rely on following principles:
1. When a (new) I-SMF is inserted (e.g. as described in clause 4.23.7, clause 4.23.11 or clause 6.10 of TS 23.548 [74]), the I-SMF pr... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.1 Addition of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF | This clause describes a procedure to add a PDU Session Anchor and Branching Point or UL CL controlled by I-SMF.
Figure 4.23.9.1-1: Addition of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF
1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1, which is controlled by SM... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.2 Removal of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF | This clause describes a procedure to remove a PDU Session Anchor and Branching Point or UL CL controlled by I-SMF.
Figure 4. 23.9.2-1: Removal of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF
1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1 (controlled by SMF) and... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.3 Change of PDU Session Anchor for IPv6 multi-homing or UL CL controlled by I-SMF | This clause describes a change of UL-CL/BP function, e.g. addition of a new PDU Session Anchor (i.e. PSA2) and release of the existing additional PDU Session Anchor (i.e. PSA0), via modifying IPv6 multi-homing or UL CL rule in the same Branching Point or UL CL under controlled by the same I-SMF.
Figure 4.23.9.3-1: Chan... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.4 Simultaneous change of Branching Point or UL CL and additional PSA controlled by I-SMF | This clause describes simultaneous change of UL-CL/BP function and additional PSA, e.g. addition of a new UL CL/BP and PDU Session Anchor (i.e. PSA2) and release of the existing UL CL/BP and additional PDU Session Anchor (i.e. PSA0), with target UPF(s) and source UPF(s) are all controlled by I-SMF.
This procedure may b... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.23.9.5 Simultaneous change of Branching Points or UL CLs controlled by different I-SMFs | This clause describes simultaneous change of UL-CL/BP function and additional PSA, e.g. addition of a new UL CL/BP and PDU Session Anchor (i.e. PSA2) and release of the existing UL CL/BP and PDU Session Anchor (i.e. PSA0), with target UPF(s) and source UPF(s) are all controlled by different I-SMF(s).
This procedure may... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.