Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.502  Word version:  19.4.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   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…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.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.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H… 
4.19 Network Data Analytics  4.20 UE Parameters Update via UDM Control Plane Procedure  4.20.1 General  4.20.2 UE Parameters Update via UDM Control Plane Procedure  4.21 Secondary RAT Usage Data Reporting Procedure 
...

 

4.19  Network Data Analytics  p. 586

The system procedures for Network Data Analytics are defined in clause 6 of TS 23.288.

4.19.1  Void

4.19.2  Void

4.20  UE Parameters Update via UDM Control Plane Procedure  p. 586

4.20.1  General  p. 586

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 policies.
The UDM Update Data that the UDM delivers to the UE may contain:
  • one or more UE parameters including:
    • the updated Default Configured NSSAI (final consumer of the parameter is the ME);
    • the updated Routing Indicator Data (final consumer of the parameter is the USIM when the related credential is stored in the USIM, i.e. for PLMN or SNPN credentials; or final consumer of the parameter is the ME when the related credential is stored in the ME, i.e. for SNPN credentials);
    • indication of whether disaster roaming is enabled in the UE if UE MINT support indicator is received or UE is registered for Disaster Roaming service currently; and
    • indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' if UE MINT support indicator is received or UE is registered for Disaster Roaming service currently.
  • a "UE acknowledgement requested" indication.
  • a "re-registration requested" indication.
Up

4.20.2  UE Parameters Update via UDM Control Plane Procedure  p. 587

Reproduction of 3GPP TS 23.502, Fig. 4.20.2-1: UE Parameters Update via UDM Control Plane Procedure
Figure 4.20.2-1: UE Parameters Update via UDM Control Plane Procedure
Up
Step 1.
UDM decides to perform UE parameter update.
Step 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 service operation contains the UDM Update Data that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. The UDM Update Data includes:
  • The updated parameters to be delivered to the UE (see clause 4.20.1 for parameters possible to deliver).
  • whether the UE needs to send an ack to the UDM.
  • whether the UE needs to re-register after updating the data.
If the UE parameter update is performed due to "Routing Indicator update data" and the updated Routing Indicator value is not supported by the UDM where the AMF is currently registered and/or by the AUSF where the UE was authenticated, the UDM shall request the UE to re-register after updating the data.
Step 3.
From AMF to UDM: If AMF determines that the UE is not reachable, then AMF invokes the Nudm_SDM_Info service operation to UDM indicating that the transmission of UE Parameters Update data is not successful. The UDM considers the procedure as UE Parameters Update procedure as pending and subsequent steps from 4-7 are skipped.
Step 4.
From AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the transparent container received from the UDM.
The UE verifies based on mechanisms defined in TS 33.501 that the UDM Update Data is provided by HPLMN, SNPN, or CH; and:
  • If the security check on the UDM Update Data is successful, as defined in TS 33.501 the UE either stores the information and uses those parameters from that point onwards, or forwards the information to the USIM; and
  • If the security check on the UDM Update Data fails, the UE discards the contents of the UDM Update Data.
Step 5.
The UE to the AMF: If the UE has verified that the UDM Update Data is provided by HPLMN, SNPN, or CH and the UDM has requested the UE to send an ack to the UDM, the UE sends an UL NAS TRANSPORT message to the serving AMF with a transparent container including the UE acknowledgement.
Step 6.
The AMF to the UDM: If the AMF receives an UL NAS TRANSPORT message with a transparent container carrying a UE acknowledgement from the UE, the AMF sends a Nudm_SDM_Info request message including the transparent container to the UDM.
Step 6a.
If the UE parameter update is performed due to "Routing Indicator update data", the updated Routing Indicator value is also supported by the UDM where the AMF is currently registered and/or by the AUSF where the UE was authenticated and the UDM requests the UE to send an ack but does not request the UE to re-register, then upon reception of the transparent container indicating the acknowledgement of successful reception, the UDM shall trigger a Nudm_SDM_Notification service operation to update the UE Context in the AMF with the updated Routing Indicator Data (e.g. to avoid transmitting an outdated Routing Indicator on UE context transfer to another AMF).
Step 7.
If the UDM has requested the UE to re-register, the UE waits until it goes back to RRC_IDLE and initiates a Registration procedure as defined in TS 24.501.
Up

4.20.3  Void

4.21  Secondary RAT Usage Data Reporting Procedure  p. 588

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 Data from AMF towards the SMF. Optionally, it is used to report the Secondary RAT Usage Data from V-SMF to the H-SMF when the reporting to H-SMF is activated.
Reproduction of 3GPP TS 23.502, Fig. 4.21-1: RAN Secondary RAT Usage Data Reporting procedure
Figure 4.21-1: RAN Secondary RAT Usage Data Reporting procedure
Up
Step 1.
The NG-RAN, if it supports Dual Connectivity with Secondary RAT (using NR radio, E-UTRA radio, or unlicensed spectrum using NR or E-UTRA radio) and it is configured to report Secondary RAT Usage Data for the UE, depending on certain conditions documented in this specification, it shall send a RAN Usage Data Report message to the AMF including the Secondary RAT Usage Data for the UE. The NG-RAN node will send only one RAN Usage Report for a UE when the UE is subject to handover by RAN. The RAN Usage Data Report includes a Handover Flag to indicate when the message is sent triggered by a handover.
Reproduction of 3GPP TS 23.502, Fig. 4.21-2: SMF Secondary RAT Usage Data Reporting procedure
Figure 4.21-2: SMF Secondary RAT Usage Data Reporting procedure
Up
The NG-RAN, if it supports Dual Connectivity with Secondary RAT (using NR radio, E-UTRA radio, or unlicensed spectrum using NR or E-UTRA radio) and it is configured to report Secondary RAT usage data for the UE, it shall include the Secondary RAT usage data for the UE to the AMF in certain messages depending on certain conditions documented elsewhere in this TS.
Step 1.
The AMF forwards the N2 SM Information (Secondary RAT Usage Data) to the SMF in a Nsmf_PDUSession_UpdateSMContext Request.
Step 2.
The V-SMF sends the Nsmf_PDUSession_Update (Secondary RAT Usage Data) message to the H-SMF.
Step 3.
The H-SMF acknowledges receiving the Secondary RAT Usage data for the UE.
Step 4.
The V-SMF acknowledges receiving the Secondary RAT Usage data back to the AMF.
Up

Up   Top   ToC