Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   4.11.2   4.11.3…   4.12…   4.12.6…   4.12a   4.12b   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.4…   4.16…   4.16.4…   4.16.8…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24   4.25   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   A…   E…   F…

 

4.9.2  Handover of a PDU Session procedure between 3GPP and untrusted non-3GPP access
4.9.2.0  General [R16]
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 allowed by policy or AN rejected resource setup, etc., the network should not release the PDU Session.
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.
Up
Step 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.
Step 2.
The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.1 (PDU Session Establishment for Non-roaming and Roaming with Local Breakout).
Step 3.
If the User Plane of the PDU Session is activated in non-3GPP access, the V-SMF executes the release of resources in non-3GPP access by performing steps 4 to 7 specified in clause 4.12.7, followed by step 7a specified in clause 4.3.4.2 in order to release the resources over the source non-3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 4 and 7 of clause 4.12.7 as well as in step 7a of clause 4.3.4.2, the messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 7b of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained.
If the User Plane of the PDU Session is deactivated in non-3GPP access, this step is skipped.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access.
Up
4.9.2.2  Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout)Word-p. 182
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.
Up
Step 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.
Step 2.
The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5.
Step 3.
If the User Plane of the PDU Session is activated in 3GPP access, the V-SMF executes the release of resource in 3GPP by performing step 3b, then steps 4 to 7a specified in clause 4.3.4.2 (UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout) in order to release the resources over the source 3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 3b, 4, 6 and 7a of clause 4.3.4.2, messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 7b of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained.
If the User Plane of the PDU Session is deactivated in 3GPP access, this step is skipped.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access
Up
4.9.2.3  Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (home routed roaming)
4.9.2.3.1  The target AMF is in the PLMN of the N3IWF
Up
Step 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.
Step 2.
The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.2 (PDU Session Establishment for Home Routed Roaming). The AMF selects the same V-SMF as the one used via non-3GPP access.
Step 3.
If the User Plane of the PDU Session is activated in non-3GPP access, the V-SMF executes the release of resource in non-3GPP access by performing steps 4 to 7 specified in clause 4.12.7, followed by step 7 specified in clause 4.3.4.2 in order to release the resources over the source non-3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 4 and 7 of clause 4.12.7 as well as in step 7a of clause 4.3.4.2, the messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 7b of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained.
If the User Plane of the PDU Session is deactivated in non-3GPP access, this step is skipped.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access.
Up
4.9.2.3.2  The target AMF is not in the PLMN of the N3IWF (i.e. N3IWF in HPLMN)Word-p. 183
Up
Step 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 corresponding to each of the PDU Sessions.
Step 2.
The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.2 (PDU Session Establishment for Home Routed Roaming).
Step 3.
The H-SMF executes the release of resources in non-3GPP AN by performing steps 3-12 specified in clause 4.12.7 with the following exceptions:
  • the H-SMF interfaces the source AMF (in the home PLMN). The H-SMF shall not send the N1 SM Container (PDU Session Release Command) to the UE;
  • The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed.
  • Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the H-SMF to the source AMF indicates the PDU Session is moved to different access.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access.
Up
4.9.2.4  Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (home routed roaming)Word-p. 184
4.9.2.4.1  The selected N3IWF is in the registered PLMN
Up
Step 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 access.
Step 2.
The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5. The AMF selects the same V-SMF as the one used via 3GPP access.
Step 3.
If the User Plane of the PDU Session is activated in 3GPP access, the V-SMF executes the release of resources in 3GPP access by performing step 5c to 10 specified in clause 4.3.4.3 (UE or network requested PDU Session Release for Home Routed Roaming) in order to release the resources over the source 3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 5c, 6, 8 and 9 of clause 4.3.4.3, the messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 7b of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained.
If the User Plane of the PDU Session is deactivated in 3GPP access, this step is skipped.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access.
Up
4.9.2.4.2  The UE is roaming and the selected N3IWF is in the home PLMN
Up
Step 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 SMF-IDs corresponding to each of the PDU Sessions.
Step 2.
The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5.
Step 3.
The H-SMF executes the release of resources in source V-SMF, V-UPF, V-AMF and 3GPP AN by performing steps 3a, 5c to 16b specified in clause 4.3.4.3 with the following exceptions:
  • the H-SMF indicates in the Nsmf_PDUSession_Update Request that the UE shall not be notified. This shall result in the V-SMF not sending the N1 Container (PDU Session Release Command) to the UE;
  • Nsmf_PDUSession_StatusNotify service operation invoked by H-SMF to V-SMF indicates PDU Session is moved to different access;
  • Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the V-SMF to the AMF indicates the PDU Session is moved to different access;
  • The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed.
The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access.
Up
4.10  NG-RAN Location reporting proceduresWord-p. 185
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 that require accurate cell identification (e.g. emergency services, lawful intercept, charging), or for subscription to the service by other NFs. When Dual Connectivity is activated, PSCell information is only reported if requested by the AMF.
Up
Step 1.
AMF to NG-RAN: Location Reporting Control (Reporting Type, Location Reporting Level, (Area Of Interest, Request Reference ID)).
The AMF sends a Location Reporting Control message to the NG-RAN. The Location Reporting Control message shall identify the UE for which reports are requested and shall include Reporting Type and Location Reporting Level. The Location Reporting Control message may also include Area Of Interest and Request Reference ID. Location Reporting Level could be TAI+ Cell Identity. Reporting Type indicates whether the message is intended to trigger a single standalone report about the current Cell Identity serving the UE or start the NG-RAN to report whenever the UE changes cell, or ask the NG-RAN to report whenever the UE moves out or into the Area Of Interest. If the Reporting Type indicates to report whenever the UE changes cell and if PScell reporting is requested and Dual Connectivity is in use, the Master RAN node shall also report to the AMF whenever the PSCell changes. If the Reporting Type indicates to start the NG-RAN to report when UE moves out of or into the Area Of Interest, the AMF also provides the requested Area Of Interest information in the Location Reporting Control message. The AMF may include a Request Reference ID in the Location Report Control message to identify the request of reporting for an Area Of Interest. If multiple Areas Of Interest are included in the message, the Request Reference ID identifies each Area of Interest.
NOTE 1:
Requesting reports whenever the UE changes cell can increase signalling load on multiple interfaces. Requesting reports for all changes in PSCell ID can further increase signalling load. Hence it is recommended that any such reporting is only applied for a limited number of subscribers,
Up

Step 2.
NG-RAN to AMF: Location Report (UE Location, UE Presence in Area Of Interest, Request Reference ID, Timestamp).
The NG-RAN sends a Location Report message informing the AMF about the location of the UE which shall be represented as the requested Location Reporting Level. If PSCell reporting is requested and Dual Connectivity is activated, then the Master NG-RAN node shall also include the PSCell ID.
When UE is in CM-CONNECTED with RRC Inactive state, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type indicating single stand-alone report, the NG-RAN shall perform NG-RAN paging before reporting the location to the AMF. The NG-RAN should send the Location Report promptly and shall not wait to attempt to create a Dual Connectivity configuration. However, if PSCell reporting is requested and the PSCell ID is known to the Master RAN node, then it shall be included in the Location Report.
When UE is in CM-CONNECTED with RRC Inactive state, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type indicating continuous reporting whenever the UE changes cell, the NG-RAN shall send a Location Report message to the AMF including the UE's last known location with time stamp. If the UE was using Dual Connectivity immediately before entering CM-CONNECTED with RRC Inactive state and PSCell reporting is requested, then the Location Report shall also include the PSCell ID.
When UE is in CM-CONNECTED, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type of Area Of Interest based reporting, the NG-RAN shall track the UE presence in Area Of Interest and send a Location Report message to AMF including the UE Presence in the Area Of Interest (i.e., IN, OUT, or UNKNOWN) as described in clause D.2 and the UE's current location (including the PSCell ID if PSCell reporting is requested and Dual Connectivity is activated) when the UE is in RRC Connected state, or, when the UE is in RRC Inactive state, the UE's last known location (including the PSCell ID if PSCell reporting is requested and the UE was using Dual Connectivity immediately before entering CM-CONNECTED with RRC Inactive state) with time stamp if the NG-RAN perceives that the UE presence in the Area Of Interest is different from the last one reported. When the NG-RAN detects that the UE has moved out of or into multiple areas of interest, it sends multiple pairs of UE Presence in the Area Of Interest and the Request Reference ID in one Location Report message to AMF. If UE transitions from RRC Inactive state to RRC Connected state, NG-RAN shall check the latest location (including the PSCell ID if PSCell reporting is requested and Dual Connectivity is activated) of UE and follow the rules when UE is in RRC Connected.
The AMF stores the latest received PSCell ID with its associated timestamp. The AMF stores the latest received PSCell ID with its associated timestamp, when available.
Up

Step 3.
AMF to NG-RAN: Cancel Location Report (Reporting Type, Request Reference ID).
The AMF can send a Cancel Location Reporting message to inform the NG-RAN that it should terminate the location reporting for a given UE corresponding to the Reporting Type or the location reporting for Area Of Interest indicated by Request Reference ID. This message is needed when the reporting type was requested for continuously reporting or for the Area Of Interest. The AMF may include the Request Reference ID which indicates the requested Location Reporting Control for the Area Of Interest, so that the NG-RAN should terminate the location reporting for the Area Of Interest.
NOTE 2:
Location reporting related information of the source NG-RAN node is transferred to the target NG-RAN node during Xn handover.
Up

In this release the location reporting procedure is applicable only to 3GPP access.
Up

Up   Top   ToC