NF subscribes to UDM notifications of UE and/or Group Subscription data updates.
The NF can subscribe to Group Subscription data from UDM in this step and be notified of Group Subscription data updates in step 7 using the Shared Data feature defined in TS 29.503
[Conditional, on using NWDAF-assisted values] The AF may subscribe to NWDAF via NEF in order to learn the UE mobility analytics and/or UE Communication analytics for a UE or group of UEs by applying the procedure specified in TS 23.288, clause 126.96.36.199
. The Analytics Id is set to any of the values specified in TS 23.288, clause 6.7.1
[Conditional, on using NWDAF-assisted values] AF validates the received data and derives any of the Expected UE behaviour parameters defined in clause 188.8.131.52
for a UE or group of UEs.
The AF provides one or more parameter(s) to be created or updated in a Nnef_ParameterProvision_Create
Request to the NEF.
The GPSI identifies the UE and the Transaction Reference ID identifies the transaction request between NEF and AF. For the case of Nnef_ParameterProvision_Create
, The NEF assigns a Transaction Reference ID to the Nnef_ParameterProvision_Create
NEF checks whether the requestor is allowed to perform the requested service operation by checking requestor's identifier (i.e. AF ID).
For a Create request associated with a 5G VN group, the External Group ID identifies the 5G VN Group.
The payload of the Nnef_ParameterProvision_Update
Request includes one or more of the following parameters:
The AF may request to delete 5G VN configuration by sending Nnef_ParameterProvision_Delete
to the NEF.
If the AF is authorised by the NEF to provision the parameters, the NEF requests to create, update and store, or delete the provisioned parameters as part of the subscriber data via Nudm_ParameterProvision_Create
Request message, the message includes the provisioned data and NEF reference ID.
If the AF is not authorised to provision the parameters, then the NEF continues in step 6 indicating the reason to failure in Nnef_ParameterProvision_Create
/Update/Delete Response message. Step 7 does not apply in this case.
For non-roaming case and no authorisation or validation by the UDM required and if the request is not associated with a 5G VN group, the NEF can directly forward the external parameter to the UDR via Nudr_DM_Update Request message. And in this case, the UDR responds to NEF via Nudr_DM_Update Response message.
UDM may read from UDR, by means of Nudr_DM_Query, corresponding subscription information in order to validate required data updates and authorize these changes for this subscriber or Group for the corresponding AF.
If the AF is authorised by the UDM to provision the parameters for this subscriber, the UDM resolves the GPSI to SUPI, and requests to create, update or delete the provisioned parameters as part of the subscriber data via Nudr_DM_Create
/Update/Delete Request message, the message includes the provisioned data.
If a new 5G VN group is created, the UDM shall assign a unique Internal Group ID for the 5G VN group and include the newly assigned Internal Group ID in the Nudr_DM_Create
Request message. If the list of 5G VN group members is changed or if 5G VN group data has changed, the UDM updates the UE and/or Group subscription data according to the AF/NEF request.
UDR stores the provisioned data as part of the UE and/or Group subscription data and responds with Nudr_DM_Create
/Update/Delete Response message.
When the 5G VN group data (as described in clause 184.108.40.206b
) is updated, the UDR notifies to the subscribed PCF by sending Nudr_DM_Notify
as defined in clause 220.127.116.11
If the AF is not authorised to provision the parameters, then the UDM continues in step 5 indicating the reason to failure in Nudm_ParameterProvision_Update
Response message and step 7 is not executed.
The UDM classifies the received parameters (i.e. Expected UE Behaviour parameters or the Network Configuration parameters or the 5G VN configuration parameters or Location Privacy Indication parameters), into AMF-Associated and SMF-Associated parameters. The UDM may use the AF ID received from the NEF in step 2 to relate the received parameter with a particular subscribed DNN and/or S-NSSAI. The UDM stores the SMF-Associated parameters under corresponding Session Management Subscription data type.
Each parameter or parameter set may be associated with a validity time. The validity time is stored at the UDM/UDR and in each of the NFs, to which parameters are provisioned (e.g. in AMF or SMF). Upon expiration of the validity time, each node deletes the parameters autonomously without explicit signalling.
UDM responds the request with Nudm_ParameterProvision_Create/Update/Delete Response. If the procedure failed, the cause value indicates the reason.
NEF responds the request with Nnef_ParameterProvision_Create/Update/Delete Response. If the procedure failed, the cause value indicates the reason.
[Conditional this step occurs only after successful step 4] UDM notifies the subscribed Network Function (e.g., AMF) of the updated UE and/or Group subscription data via Nudm_SDM_Notification
If the NF is AMF, the UDM performs Nudm_SDM_Notification (SUPI or Internal Group Identifier, AMF-Associated parameters, etc.) service operation. The AMF identifies whether there are overlapping parameter set(s) and merges the parameter set(s) in the Expected UE Behaviour, if necessary. The AMF uses the received AMF-Associated parameters to derive the appropriate UE configuration of the NAS parameters and to derive Core Network assisted RAN parameters. The AMF may determine a Registration area based on parameters Stationary indication or Expected UE Moving Trajectory.
If the NF is SMF, the UDM performs Nudm_SDM_Notification (SUPI or Internal Group Identifier, SMF-Associated parameter set, DNN/S-NSSAI, etc.) service operation.
The SMF stores the received SMF-Associated parameters and associates them with a PDU Session based on the DNN and S-NSSAI included in the message from UDM. The SMF identifies whether there are overlapping parameter set(s) in the Expected UE behaviour and merges the parameter set(s), if necessary. The SMF may use the SMF-Associated parameters as follows:
SMF configures the UPF accordingly. The SMF can use the Scheduled Communication Type parameter or Suggested Number of Downlink Packets parameter to configure the UPF with how many downlink packets to buffer. The SMF may use the parameter Communication duration time to determine to deactivate UP connection and to perform CN-initiated selective deactivation of UP connection of an existing PDU Session.
The SMF may derive SMF derived CN assisted RAN information for the PDU Session. The SMF provides the SMF derived CN assisted RAN information to the AMF as described in PDU Session establishment procedure or PDU Session modification procedure.
The NEF (in NOTE 1) or the UDM (in step 3) can also update the corresponding UDR data via Nudr_DM_Create/Delete as appropriate.