hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.4 Number of PDU Sessions per network slice availability check and update procedure | This clause applies to Non-Hierarchical NSAC and centralized NSAC architectures. The difference between the two architectures for the various steps, where applicable, is described at the end of the clause.
The number of PDU Sessions per network slice availability check and update procedure is to update (i.e. increase o... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.5 Network Slice Admission Control Support for Roaming | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.5.1 Network Slice Admission Control Support for Roaming by VPLMN | This clause describes the case of VPLMN NSAC admission mode.
For NSAC for roaming UEs, a maximum number of allowed UEs per mapped S-NSSAI in HPLMN and/or a maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI in HPLMN is allocated to the VPLMN for each S-NSSAI in HPLMN and stored in one NSCAF in the VP... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.5.2 Network Slice Admission Control Support for Roaming by HPLMN | 4.2.11.5.2.1 General
For maximum number of UEs in roaming case, there are two types of NSAC admission modes requiring interaction with HPLMN for inbound roamers; VPLMN with HPLMN assistance NSAC admission mode or HPLMN NSAC admission mode.
For PDU sessions in the home-routed roaming case, the SMF in HPLMN performs NSAC... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.6 Update of local maximum number in Hierarchical NSAC Architecture | Figure 4.2.11.6-1: Update of local maximum number in hierarchical NSAC architecture
At any time the Primary NSACF may update the allocated local Maximum number of UE and/or PDU sessions configured at the NSACFs as follow:
1. The Primary NSACF decides to update the local maximum number of UE or PDU session values at the... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3 Session Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.1 General | Clause 4.3 defines the Session Management related procedures. It refers to clause 4.4 for the N4 interactions.
As defined in clause 5.6.3 of TS 23.501 [2], considering the case of Home Routed PDU Session, the NAS SM information processing by SMF considers following kind of NAS SM information:
- Information that both th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2 PDU Session Establishment | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.1 General | A PDU Session establishment may correspond to:
- a UE initiated PDU Session Establishment procedure.
- a UE initiated PDU Session handover between 3GPP and non-3GPP.
- a UE initiated PDU Session handover from EPS to 5GS.
- a Network triggered PDU Session Establishment procedure. In this case the network sends the devic... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.2 UE Requested PDU Session Establishment | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.2.1 Non-roaming and Roaming with Local Breakout | Clause 4.3.2.2.1 specifies PDU Session establishment in the non-roaming and roaming with local breakout cases. The procedure is used to:
- Establish a new PDU Session;
- Handover a PDN Connection in EPS to PDU Session in 5GS without N26 interface;
- Switching an existing PDU Session between non-3GPP access and 3GPP acc... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.2.2 Home-routed Roaming | This procedure is used in the case of home-routed roaming scenarios.
Figure 4.3.2.2.2-1: UE-requested PDU Session Establishment for home-routed roaming scenarios
1. This step is the same as step 1 in clause 4.3.2.2.1.
2. For NR satellite access, the AMF may decide to verify the UE location as described in clause 5.4.11... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.2.3 SMF selection | 4.3.2.2.3.1 General
The SMF selection function, as described in clause 6.3.2 of TS 23.501 [2], is supported by the AMF and is used to allocate an SMF that manages the PDU Session.
The SMF selection function described in this clause does not apply to the selection of an SMF for Emergency services. For SMF selection for ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.2.4 Multiple PDU Sessions towards the same DNN and S-NSSAI | A UE may establish multiple PDU Sessions associated with the same DNN and S-NSSAI and the AMF may select the same SMF or different SMFs as specified in clause 6.3.2 of TS 23.501 [2].
During PDU Session establishment, the AMF checks if the SMF selection subscription data indicates that the same SMF is required for multi... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.3 Secondary authorization/authentication by an DN-AAA Server during the PDU Session establishment | The PDU Session establishment authentication/authorization is optionally triggered by the SMF during a PDU Session establishment and performed transparently via a UPF or directly with the DN-AAA Server without involving the UPF if the DN-AAA Server is located in the 5GC and reachable directly, as described in clause 5.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.2.4 Support of L2TP | L2TP may be used between UPF and the DN via N6 to carry traffic of a PDU Session, as defined in TS 23.501 [2]. The corresponding high level end to end signalling flow is described in this clause and further refined in TS 29.561 [63]. For the procedure described below, it is a prerequisite that the UE is already registe... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.3 PDU Session Modification | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.3.1 General | The procedure is used when one or several of the QoS parameters exchanged between the UE and the network are modified and/or to send updated ECS Address Configuration Information as defined in clause 6.5.2 of TS 23.548 [74] to the UE and/or to send the updated DNS server address as defined in clause 6.2.3.2.3 of TS 23.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.3.2 UE or network requested PDU Session Modification (non-roaming and roaming with local breakout) | The UE or network requested PDU Session Modification procedure (non-roaming and roaming with local breakout scenario) is depicted in figure 4.3.3.2-1.
Figure 4.3.3.2-1: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout)
1. The procedure may be triggered by following event... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.3.3 UE or network requested PDU Session Modification (home-routed roaming) | The UE or network requested PDU Session Modification procedure (home-routed roaming scenario) is depicted in figure 4.3.3.3-1.
Figure 4.3.3.3-1: UE or network requested PDU Session Modification (for home-routed roaming scenario)
1. The procedure is triggered by one of the following events:
1a. (UE or serving network re... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.4 PDU Session Release | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.4.1 General | The PDU Session Release procedure is used to release all the resources associated with a PDU Session, including:
- The IP address/Prefixes allocated for an IP-based PDU Session; this may include the release of multiple Prefixes in the case of Multi-homing (as defined in TS 23.501 [2]).
- Any UPF resource (including N3/... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.4.2 UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout | Figure 4.3.4.2-1 captures both the UE Requested PDU Session Release procedure and the network requested PDU Session Release procedure. The procedure allows the UE to request the release of one PDU Session. The procedure also allows the AMF, the SMF or the PCF to initiate the release of a PDU Session. In the case of LBO... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.4.3 UE or network requested PDU Session Release for Home-routed Roaming | This procedure is used in the case of home-routed roaming scenarios.
Figure 4.3.4.3-1: UE or network requested PDU Session Release for home-routed roaming
1. The procedure is triggered by one of the following events:
1a. (UE initiated release) As in step 1a of clause 4.3.4.2 with the addition that:
- the V-SMF initiate... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5 Session continuity, service continuity and UP path management | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.1 Change of SSC mode 2 PDU Session Anchor with different PDU Sessions | The following procedure is triggered by SMF in order to change the PDU Session Anchor serving a PDU Session of SSC mode 2 for a UE when neither multi-homing nor UL CL applies to the PDU Session. This procedure releases the existing PDU Session associated with an old PDU Session Anchor (i.e. UPF1 in figure 4.3.5.1-1) an... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.2 Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions | The following procedure is triggered by SMF in order to change the PDU Session Anchor serving a PDU Session of SSC mode 3 for a UE. This procedure releases the existing PDU Session associated with an old PDU Session Anchor (i.e. UPF1 in figure 4.3.5.2-1) after having established a new PDU Session to the same DN with a ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.3 Change of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session | Clause 4.3.5.3 describes a procedure for service continuity with SSC mode 3 that uses the multi-homed PDU Session described in clause 5.6.4.3 of TS 23.501 [2]. In this case the SMF prepares a new PDU Session Anchor first and then notifies the UE of the existence of a new IP prefix, as depicted in figure 4.3.5.3-1. This... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.4 Addition of additional PDU Session Anchor and Branching Point or UL CL | Clause 4.3.5.4 describes a procedure to add a PDU Session Anchor and a Branching Point or UL CL for an established PDU Session.
Figure 4.3.5.4-1: Addition of additional PDU Session Anchor and Branching Point or UL CL
1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1 (PSA1 in Figure 4.3.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.5 Removal of additional PDU Session Anchor and Branching Point or UL CL | Clause 4.3.5.5 describes a procedure to remove a PDU Session Anchor and (optionally) remove Branching Point or UL CL for an established PDU Session.
Figure 4.3.5.5-1: Removal of additional PDU Session Anchor and Branching Point or UL CL
1. UE has an established PDU Session with a UPF including the Branching Point or UL... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.6 Change of additional PDU Session Anchor for IPv6 multi-homing or UL CL | The following procedure is triggered by an SMF when the SMF needs to modify IPv6 multi-homing or UL CL rule (i.e. traffic filter in the Branching Point or the UL CL) in order to move the some or whole traffic flows of the existing additional PDU Session Anchor which was established by the IPv6 multi-homing or the UL CL... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.7 Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session | Simultaneous change of UL CL or Branching Point and additional PSA can be performed after Xn based handover, N2 based handover and Service Request procedures.
The following procedure is triggered by SMF in order to change the Branching Point or the UL CL and additional PSA serving a PDU Session for a UE.
Figure 4.3.5.7... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.5.8 Ethernet PDU Session Anchor Relocation | This procedure allows for Ethernet PDU Sessions to change the PDU Session Anchor (PSA) while the session remains set up. Originally the Ethernet PDU Session goes via the Source UPF acting as the PSA. The Ethernet context which contains all Ethernet specific information including the MAC address of the UE and possibly i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6 Application Function influence on traffic routing, service function chaining and handling of payload headers | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.1 General | Clause 4.3.6 describes the procedures between an Application Function and the SMF to maintain an efficient user plane path and/or to provide N6-LAN service function chaining and/or to perform Handling of Payload Headers for Application Functions that require it.
As described in clauses 5.6.7, 5.6.16 and 5.6.17 of TS 23... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.2 Processing AF requests to influence traffic routing and/or Service Function Chaining and/or for Handling of Payload Headers for Sessions not identified by an UE address | Figure 4.3.6.2-1: Processing AF requests to influence traffic routing and/or Service Function Chaining for Sessions not identified by an UE address
NOTE 1: The 5GC functions used in this scenario are assumed to all belong to the same PLMN (HPLMN in non-roaming case or VPLMN in the case of a PDU Session in LBO mode).
0.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.3 Notification of User Plane Management Events | The SMF may send a notification to the AF if the AF had subscribed to user plane management event notifications as described in clauses 4.3.6.2 and 4.3.6.4 and in clause 5.6.7 of TS 23.501 [2]. The following are the examples of such events:
- A PDU Session Anchor identified in the AF subscription request has been estab... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.4 Transferring an AF request targeting an individual UE address to the relevant PCF | Figure 4.3.6.4-1: Handling an AF request targeting an individual UE address to the relevant PCF
Depending on the AF deployment (see clause 6.2.10 of TS 23.501 [2]), the AF may send the AF request to PCF directly, in which case step 1 is skipped, or via the NEF.
1. [Conditional] If the AF sends the AF request via NEF, t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5 Processing AF requests to influence traffic routing for HR-SBO session | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5.1 General | Processing an AF requests to influence traffic routing for HR-SBO session are based on procedure described in clauses 4.3.6.5.2 - 4.3.6.5.5. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5.2 AF traffic influence request includes HPLMN DNN, HPLMN S-NSSAI | Figure 4.3.6.5.2-1: Processing an AF request to influence traffic routing for HR-SBO session when AF provides HPLMN DNN and HPLMN S-NSSAI
0a. AF subscribes to H-SMF regarding the change of serving PLMN change event and is notified after V-SMF insertion/inter-PLMN V-SMF change as described in clause 6.7.2.6 of TS 23.548... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5.3 AF traffic influence request without HPLMN DNN, S-NSSAI information for a single UE, with private IP address or public IP address owned by VPLMN | Figure 4.3.6.5.3-1 Processing AF requests in VPLMN to influence traffic of a HR-SBO PDU Session
1. During HR-SBO PDU Session establishment procedure, the V-SMF provides an indication that the UE PDU session is working in HR-SBO mode, SUPI of the UE and the HPLMN DNN and HPLMN S-NSSAI of the PDU session to UPF (i.e. L-P... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5.4 AF traffic influence request without HPLMN DNN, S-NSSAI information for a single UE, with UE IP address owned and assigned by HPLMN | Figure 4.3.6.5.4-1: Processing AF requests in VPLMN to influence traffic of a HR-SBO PDU Session
1. If HR-SBO applies to the PDU Session, the H-SMF may provide an indication that the PDU Session is working in HR-SBO mode, SUPI, HPLMN DNN and S-NSSAI of the PDU session to UPF.
2. V-SMF subscribes to Traffic Influence da... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.6.5.5 AF traffic influence request for GPSI or any UE | If target is GPSI, the NEF determines PLMN owning the GPSI (i.e. HPLMN of the UE). If the PLMN owning the GPSI is not the serving PLMN of the NEF, the NEF determines that HR-SBO applies for the PDU session. Then the NEF in VPLMN contacts NEF of the PLMN owning the GPSI by invoking Nnef_UEId_Get service, and the NEF of ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.7 CN-initiated selective deactivation of UP connection of an existing PDU Session | The following procedure is used to deactivate UP connection (i.e. data radio bearer and N3 tunnel) for an established PDU Session of a UE in CM-CONNECTED state.
For an always-on PDU Session, the SMF should not configure the UPF to report inactivity.
Figure 4.3.7-1: CN-initiated deactivation of UP connection for an esta... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.3.8 Change of Network Slice instance for PDU Sessions | When a Network Slice instance for the existing PDU Session is required to be changed as described in clause 5.15.5.3 of TS 23.501 [2], the AMF deletes the old NSI ID corresponding to the Network Slice instance that is congested or no longer available and informs the SMF of the PDU Session(s) which is selected by using ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4 SMF and UPF interactions | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.1 N4 session management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.1.1 General | N4 session management procedures are used to control the functionality of the UPF. The SMF can create, update and remove the N4 session context in the UPF, which is described in clause 5.8.2 of TS 23.501 [2].
The following N4 session management procedures exist: N4 Session Establishment procedure, N4 session Modificati... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.1.2 N4 Session Establishment procedure | The N4 Session Establishment procedure is used to create the initial N4 session context for a PDU Session at the UPF. The SMF assigns a new N4 Session ID and provides it to the UPF. The N4 Session ID is stored by both entities and used to identify the N4 session context during their interaction. The SMF also stores the... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.1.3 N4 Session Modification procedure | The N4 Session Modification procedure is used to update the N4 session context of an existing PDU Session at the UPF, which is executed between SMF and UPF whenever PDU Session related parameters have to be modified.
Figure 4.4.1.3-1: N4 Session Modification procedure
1. SMF receives the trigger to modify the existing ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.1.4 N4 Session Release procedure | The N4 session release procedure is used to remove the N4 session context of an existing PDU Session at the UPF.
Figure 4.4.1.4-1: N4 Session Release procedure
1. SMF receives the trigger to remove the N4 session context for the PDU Session.
2. The SMF sends an N4 session release request message to the UPF.
3. The UPF ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.2 N4 Reporting Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.2.1 General | The N4 reporting procedure is used by the UPF to report events to the SMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.2.2 N4 Session Level Reporting Procedure | This procedure is used by the UPF to report events related to an N4 session for an individual PDU Session. The triggers for event reporting were configured on the UPF during N4 Session Establishment/Modification procedures by the SMF.
Figure 4.4.2.2-1: N4 Session Level Reporting procedure
1. The UPF detects that an eve... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3 N4 Node Level Procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3.1 N4 Association Setup Procedure | The N4 Association Setup procedure is used to setup an N4 association between the SMF and the UPF, to enable the SMF to use the resources of the UPF subsequently to establish N4 Sessions. The SMF and UPF may exchange the supported functionalities on each side during these procedures.
The setup of an N4 association is i... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3.2 N4 Association Update Procedure | The N4 Association Update procedure shall be used to modify an existing N4 association between the SMF and the UPF. It may be initiated by the UPF or by the SMF to update the supported features or available resources of the UP function.
N4 Association Update procedure can be used by the SMF to update the provisioning o... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3.3 N4 Association Release Procedure | The N4 Association Release procedure shall be used to terminate the N4 association between the SMF and the UPF due to e.g. OAM reasons. The N4 Association Release Request may be initiated by the SMF or UPF.
Figure 4.4.3.3-1: SMF initiated N4 association release procedure
Figure 4.4.3.3-2: UPF initiated N4 association r... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3.4 N4 Report Procedure | The N4 Report procedure shall be used by the UPF to report information to the SMF which is not related to a specific N4 session, e.g. to report a user plane path failure affecting all the N4 sessions towards a remote GTP-U peer.
N4 Report procedure can be used by the UPF to report the clock drift between the external t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.3.5 N4 PFD management Procedure | This N4 procedure is used by the SMF to provision or remove all PFD(s) belonging to an Application Identifier in the UPF. PFD sets belonging to different Application Identifiers can be managed with the same PFD management request message.
The N4 PFD management procedure is a node level procedure, i.e. independent of an... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.4.4 SMF Pause of Charging procedure | The SMF Pause of Charging procedure aims for the SMF charging and usage monitoring data to more accurately reflect the downlink traffic actually sent to the AN.
The following are example triggers for the SMF to enable the pause of charging
- Operator specified criteria/threshold (e.g. number/fraction of packets/bytes d... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.5 User Profile management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.5.1 Subscriber Data Update Notification to AMF | Whenever the user profile is changed for a user in the UDM/UDR and the changes affect the user profile in the AMF, the UDM shall notify these changes to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. Then the AMF adds or modifies the user profile.
The Nudm_SDM_Notification service op... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.5.2 Session Management Subscriber Data Update Notification to SMF | Whenever the session management subscriber data is changed for a user in the UDM/UDR and if the SMF subscribed for the update of the session management subscriber data to be notified, the UDM shall notify these changes to the affected SMF by the means of invoking Nudm_SDM_Notification service operation. Then the SMF mo... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.5.3 Purge of subscriber data in AMF | An AMF may, as an implementation option, purge the subscriber data and MM context of a UE after the implicit or explicit Deregistration of the UE. In this case, the AMF shall unsubscribe and deregister from the UDM, where UDM may further do corresponding operation from UDR, by the means of following "Purge of subscribe... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.6 Security procedures | Security procedures for the 5GS are specified in 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.7 ME Identity check procedure | The AMF initiates Mobile Equipment Identity Check procedure by invoking the N5g-eir_MEIdentityCheck_Get service operation as defined in clause 5.2.4.2.2. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8 RAN-CN interactions | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.1 Connection Inactive and Suspend procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.1.1 Connection Inactive procedure | This procedure may be initiated by the serving NG-RAN node when the UE is in CM-CONNECTED with RRC_CONNECTED state and has received the "RRC Inactive Assistance Information" from the AMF as defined in clause 5.3.3.2.5 of TS 23.501 [2]. NG-RAN initiates the transition to RRC_INACTIVE state as defined in TS 38.300 [9].
4... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.1.2 Connection Suspend procedure | This procedure may be initiated by the serving NG-RAN node when the UE is in CM-CONNECTED and has at least one PDU session with active user plane connection and NG-eNB has received indication from the AMF that User Plane CIoT 5GS Optimisation, as defined in clause 5.31.18 of TS 23.501 [2], is supported for the UE.
Figu... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.2 Connection Resume procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.2.1 General | The Connection Resume procedure is used by a UE to request the establishment of a secure connection between a UE and the network when the UE is in CM-CONNECTED with RRC_INACTIVE state, or in CM-IDLE with Suspend indicator for the UE supporting User Plane CIoT 5GS Optimisation. The UE initiates the procedure when upper ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.2.2 UE Triggered Connection Resume in RRC_INACTIVE procedure | The Connection Resume procedure is used by the UE in RRC_INACTIVE state, e.g. to transition to RRC_CONNECTED state or for Small Data Transmission while in RRC_INACTIVE as specified in TS 38.300 [9]. Triggers for the UE to initiate this procedure are defined in clause 5.3.3.2.5 of TS 23.501 [2].
Figure 4.8.2.2-1: Connec... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.2.3 Connection Resume in CM-IDLE with Suspend procedure | For the UE supporting User Plane CIoT 5GS Optimisation, the Connection Resume procedure is used by the UE to perform RRC_IDLE with Suspend to RRC_CONNECTED state transition. Triggers for the UE to initiate this procedure are defined in clause 5.31.18 of TS 23.501 [2].
Figure 4.8.2.3-1: Connection Resume in CM-IDLE with... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.2.4 Connection Resume in CM-IDLE with Suspend and MO EDT procedure | The Connection Resume with Early Data Transmission procedure is used by the UE to optimise sending user data in a single uplink packet and single uplink followed by single downlink packet cases for a UE in CM-IDLE with Suspend.
Figure 4.8.2.4-1: Connection Resume in RRC_IDLE with Suspend with EDT
1. UE to NG-eNB: RRC m... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.8.3 N2 Notification procedure | This procedure is used by an AMF to request the NG-RAN to report RRC state information, when the target UE is in CM-CONNECTED state. When AMF has requested reporting of subsequent state changes, the need for the NG-RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends a cancel indication.... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9 Handover procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1 Handover procedures in 3GPP access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.1 General | These procedures are used to hand over a UE from a source NG-RAN node to a target NG-RAN node using the Xn or N2 reference points. This can be triggered, for example, due to new radio conditions, load balancing or due to specific service e.g. in the presence of QoS Flow for voice, the source NG-RAN node being NR may tr... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.2 Xn based inter NG-RAN handover | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.2.1 General | Clause 4.9.1.2 includes details regarding the Xn based inter NG-RAN handover with and without UPF re-allocation.
Xn handovers are only supported for intra-AMF mobility. New AMF can be selected by the target NG-RAN node as specified in clause 5.21.2 of TS 23.501 [2].
The handover preparation and execution phases are per... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.2.2 Xn based inter NG-RAN handover without User Plane function re-allocation | This procedure is used to hand over a UE from a source NG-RAN to Target NG-RAN using Xn when the AMF is unchanged and the SMF decides to keep the existing UPF. The UPF referred in this clause 4.9.1.2.2 is the UPF which terminates N3 interface in the 5GC for non-roaming or local breakout roaming scenario, V-UPF which te... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.2.3 Xn based inter NG-RAN handover with insertion of intermediate UPF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn when the AMF is unchanged and the SMF decides that insertion of a new additional intermediate UPF is needed. If redundant transmission is performed for one or more QoS Flows of a PDU Session to be switched to the Target NG-RAN, th... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.2.4 Xn based inter NG-RAN handover with re-allocation of intermediate UPF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn when the AMF is unchanged and the SMF decides that the intermediate UPF (I-UPF) is to be changed. In the case of using UL CL, the I-UPF can be regarded as UL CL and additional PSA provides local access to a DN, the simultaneous ch... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.3 Inter NG-RAN node N2 based handover | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.3.1 General | Clause 4.9.1.3 includes details regarding the inter NG-RAN node N2 based handover without Xn interface.
The source NG-RAN decides to initiate an N2-based handover to the target NG-RAN. This can be triggered, for example, due to new radio conditions or load balancing, if there is no Xn connectivity to the target NG-RAN,... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.3.2 Preparation phase | Figure 4.9.1.3.2-1: Inter NG-RAN node N2 based handover, Preparation phase
1. S-RAN to S-AMF: Handover Required (Target ID, Source to Target transparent container, SM N2 info list, PDU Session IDs, intra system handover indication).
NOTE 1: When applicable the message includes the selected NID, see TS 38.413 [10] for t... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.3.3 Execution phase | Figure 4.9.1.3.3-1: inter NG-RAN node N2 based handover, execution phase
NOTE 1: Registration of serving AMF with the UDM is not shown in the figure for brevity.
1. S-AMF to S-RAN: Handover Command (Target to Source transparent container, List Of PDU Sessions to be handed-over with N2 SM information containing informat... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.1.4 Inter NG-RAN node N2 based handover, Cancel | Prior to sending a Handover Command to the UE, the source NG-RAN node may attempt cancellation of handover during the handover procedure. The reason for cancellation may include timer expiration, internal failure within the source NG-RAN node or UE returned to source cell etc. The handover cancellation is initiated by ... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2 Handover of a PDU Session procedure between 3GPP and untrusted non-3GPP access | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.0 General | The procedures in this clause are used to hand over a PDU Session between 3GPP access and non-3GPP access. This can be triggered, for example, due to radio conditions, user interaction, etc. When the UE triggers handover of a PDU Session between 3GPP access and non-3GPP access and the procedure fails due to e.g. not al... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.1 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) | Clause 4.9.2.1 specifies how to hand over a UE from a source Untrusted non-3GPP access to a target 3GPP access and how a UE can handover a PDU Session from untrusted non-3GPP access to 3GPP access. It is based on the PDU Session Establishment procedure for 3GPP access as specified in clause 4.3.2.
Figure 4.9.2.1-1: Han... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.2 Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) | Clause 4.9.2.2 specifies how to hand over a UE from a source 3GPP access to a target Untrusted non-3GPP access and how a UE can handover a PDU Session from 3GPP access to untrusted non-3GPP access. It is based on the PDU Session Establishment procedure for non-3GPP access as specified in clause 4.12.5.
Figure 4.9.2.2-1... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.3 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (home routed roaming) | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.3.1 The target AMF is in the PLMN of the N3IWF | Figure 4.9.2.3.1 -1: Handover of a PDU Session procedure from untrusted non-3GPP access to 3GPP access (home routed roaming)
1. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. The NG-RAN selects the same AMF as the one used via non-3GPP access.
2... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.3.2 The target AMF is not in the PLMN of the N3IWF (i.e. N3IWF in HPLMN) | Figure 4.9.2.3.2-1: Handover of a PDU Session procedure from untrusted non-3GPP access with N3IWF in the HPLMN to 3GPP access (home routed roaming)
1. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. This includes the retrieval of the SMF-IDs corr... |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.4 Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (home routed roaming) | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.9.2.4.1 The selected N3IWF is in the registered PLMN | Figure 4.9.2.4.1-1: Handover of a PDU Session procedure from 3GPP access to untrusted non-3GPP access (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. The N3IWF selects the same AMF as the one used via 3GPP acce... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.