5.2.3 UDM Services
23.5023GPPProcedures for the 5G System (5GS)Release 18TS
5.2.3.1 General
The following table illustrates the UDM Services and Service Operations.
Table 5.2.3.1-1: NF services provided by UDM
|
NF service |
Service Operations |
Operation Semantics |
Example Consumer(s) |
|
Subscriber Data |
Get |
Request/Response |
AMF, SMF, SMSF, NEF, 5G DDNMF, TSCTSF |
|
Management |
Subscribe |
Subscribe/Notify |
AMF, SMF, SMSF, NEF, 5G DDNMF |
|
(SDM) |
Unsubscribe |
Subscribe/Notify |
AMF, SMF, SMSF, NEF, 5G DDNMF |
|
Notification |
Subscribe/Notify |
AMF, SMF, SMSF, NEF, GMLC, 5G DDNMF |
|
|
ModifySubscription |
Subscribe/Notify |
AMF, SMF, SMSF, NEF, 5G DDNMF |
|
|
Info |
Request/Response |
AMF, NEF |
|
|
UE Context |
Registration |
Request/Response |
AMF, SMF, SMSF |
|
Management |
DeregistrationNotification |
Subscribe/Notify |
AMF |
|
(UECM) |
Deregistration |
Request/Response |
AMF, SMF, SMSF |
|
Get |
Request/Response |
NEF, SMSF, GMLC, NWDAF, SMF |
|
|
Update |
Request/Response |
AMF, SMF |
|
|
PCscfRestoration |
Subscribe/Notify |
AMF, SMF |
|
|
SendRoutingInfoForSM |
Request/Response |
SMS-GMSC |
|
|
UE |
Get |
Request/Response |
AUSF |
|
Authentication |
ResultConfirmation |
Request/Response |
AUSF |
|
EventExposure |
Subscribe |
Subscribe/Notify |
NEF (NOTE), NWDAF, SMS-GMSC |
|
Unsubscribe |
NEF (NOTE), NWDAF, SMS-GMSC |
||
|
Notify |
NEF (NOTE), NWDAF, SMS-GMSC |
||
|
ModifySubscription |
NEF (NOTE), NWDAF, SMS-GMSC |
||
|
Parameter |
Update |
Request/Response |
NEF, AMF |
|
Provision |
Create |
Request/Response |
NEF |
|
Delete |
Request/Response |
NEF |
|
|
Get |
Request/Response |
NEF |
|
|
NIDDAuthorisation |
Get |
Request/Response |
NEF |
|
UpdateNotify |
Subscribe/Notify |
NEF |
|
|
ServiceSpecificAuthorisation |
Create |
Request/Response |
NEF |
|
UpdateNotify |
Subscribe/Notify |
NEF |
|
|
ReportSMDeliveryStatus |
Request |
Request/Response |
SMS-GMSC |
|
NOTE: Other NFs are allowed to consume the service based on roaming agreement or operator policy. |
|||
5.2.3.2 Nudm_UECM (UECM) service
5.2.3.2.1 Nudm_UECM_Registration service operation
Service operation name: Nudm_UECM_Registration
Description: Register UE’s serving NF (if NF Type is AMF, SMSF, or NWDAF) or Session’s serving NF (if NF Type is SMF) on the UDM. This operation implies the following:
– The authorization, if applicable, to register the NF service consumer in UDM for the UE (e.g. based on UE roaming/RAT restrictions applicable when NF type is AMF). If this is successful, the NF service consumer is set as a serving NF for the corresponding UE/Session context.
– When the consumer is AMF or SMF, it is implicitly subscribed to be notified when it is deregistered in UDM. This notification is done by means of Nudm_UECM_DeregistrationNotification operation.
– When the consumer is AMF or SMF, it may optionally use this operation to subscribe to be notified of the need for P-CSCF Restoration. This notification is done by means of Nudm_UECM_PCscfRestoration operation. For more information regarding P-CSCF restoration procedures see TS 23.380 [38].
Inputs, Required: NF ID, SUPI, NF Type, Access Type (if NF Type is AMF, SMSF), RAT Type and GUAMI (if NF Type is AMF), PDU Session ID (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF). If NF Type is SMF: DNN or Indication of Emergency Services, S-NSSAI, SMF+PGW-C FQDN for S5/S8 if the PDU Session supports EPS interworking, Serving Node PLMN ID. If NF type is AMF and Access Type is 3GPP access: Registration type. If NF type is SMSF: SMSF MAP address and/or Diameter address, Serving PLMN ID.
NOTE: The GUAMI includes the MNC+MCC of the serving PLMN. In home routed roaming, the H-SMF provides the PLMN ID of the HPLMN as Serving Node PLMN ID. In LBO roaming, the SMF in the VPLMN provides the PLMN ID of the serving PLMN in the VPLMN as Serving Node PLMN ID.
Inputs, Optional: PEI (conditional, condition stated below), P-CSCF Restoration notification information, NID (e.g. if NF Type is AMF; see clause 5.18 of TS 23.501 [2]), backup AMF(s) (if NF Type is AMF), "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE SRVCC capability (if NF Type is AMF), indication that access is from ePDG (shall be sent if NF Type is SMF and PDU Session is setup via S2b), VGMLC ID (if NF type is AMF and information is available in AMF). Backup AMF(s) sent only once by the AMF to the UDM in its first interaction with the UDM, indication of no event exposure subscription information available (if NF Type is AMF). PCF ID selected for the PDN connection/PDU Session (If NF type is SMF), UE MINT support indicator, Disaster Roaming indicator indicating that Disaster Roaming service is applied.
Outputs, Required: Result indication.
Outputs, Optional: None.
If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm_UECM_Registration in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association.
See step 14a of clause 4.2.2.2.2 for an example usage of this service operation.
5.2.3.2.2 Nudm_UECM_DeregistrationNotification service operation
Service operation name: Nudm_UECM_DeregistrationNotification.
Description: UDM notifies the NF consumer which has previously registered (using Nudm_UECM_Registration operation) has been deregistered in the UDM. As a result, the consumer is no longer registered in UDM as a serving NF for that UE.
NOTE: This notification corresponds to an implicit subscription.
Inputs, Required: SUPI, Access Type, PDU Session ID, serving NF deregistration reason.
Inputs, Optional: NF ID in the case of SM Context Transfer.
Outputs, Required: None.
Outputs, Optional: None.
See step 14d of clauses 4.2.2.2.2 and 4.26.5.3 for an example usage of this service operation. The serving NF deregistration reason tells the reason for sending the deregistration notification to the consumer NF.
The reason for AMF deregistration can be one of the following:
– UE Initial Registration.
– UE Registration area change.
– Subscription Withdrawn.
– 5GS to EPS Mobility.
The reason for SMF deregistration can be one of the following:
– SMF Context Transfer.
5.2.3.2.3 Nudm_UECM_Deregistration service operation
Service operation name: Nudm_UECM_Deregistration.
Description: The NF consumer requests the UDM to delete the information related to the NF in the UE context. When the consumer is AMF, this implies that the subscriptions to be notified when the NF is deregistered in UDM (i.e. Nudm_UECM_DeregistrationNotification) are also removed.
Inputs, Required: SUPI, NF type, Access Type, PDU Session Id (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF).
– Access Type is included only when the NF type indicates AMF or SMSF.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None.
5.2.3.2.4 Nudm_UECM_Get service operation
Service operation name: Nudm_UECM_Get.
Description: The NF consumer requests the UDM to get the NF ID or SMS address of the NF serving the UE.
Inputs, Required: UE ID, NF Type.
Inputs, Optional: Access Type, Analytics ID(s) (if NF Type is NWDAF), indication to retrieve PDU Session ID information.
– Access Type is included when the NF type indicates SMSF.
Outputs, Required: NF ID or SMS address of the NF corresponding to the NF type requested by NF consumer. If the NF Type requested by NF consumer is AMF, the Access Type corresponding to the AMF is also included. Analytics ID(s), if NF Type is NWDAF.
Outputs, Optional: SUPI or GPSI or both, PDU Session ID(s) already registered in the UDM for the UE.
For more information on retrieving PDU Session information, refer to clause 4.11.0a.5.
5.2.3.2.5 Nudm_UECM_Update service operation
Service operation name: Nudm_UECM_Update.
Description: Consumer updates some UE related information (e.g. UE capabilities, Intersystem continuity context, SMF+PGW-C FQDN for S5/S8 interface, Analytics ID(s) in the case of NWDAF).
Inputs, Required: NF ID, SUPI, NF type, UE context information.
Inputs, Optional: "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE MINT support indicator (if NF Type is AMF), SMF+PGW-C FQDN for S5/S8 interface (if NF Type is SMF).
Outputs, Required: Result Indication.
Outputs, Optional: None.
5.2.3.2.6 Nudm_UECM_PCscfRestoration service operation
Service operation name: Nudm_UECM_PCscfRestoration.
Description: UDM notifies the AMF and/or SMF(s) which indicated during registration in UDM to be notified of the need for P-CSCF Restoration.
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
5.2.3.2.7 Nudm_UECM_SendRoutingInfoForSM service operation
Service operation name: Nudm_UECM_SendRoutingInfoForSM.
Description: This service operation is used to get SMS Routing Info for MT SMS.
Inputs, Required: GPSI.
Inputs, Optional: None.
Outputs, Required: Result indication, SMS Routing Info.
Outputs, Optional: None.
5.2.3.3 Nudm_SubscriberDataManagement (SDM) Service
5.2.3.3.1 General
Subscription data types used in the Nudm_SubscriberDataManagement Service are defined in Table 5.2.3.3.1-1 below.
Table 5.2.3.3.1-1: UE Subscription data types
|
Subscription data type |
Field |
Description |
|---|---|---|
|
Access and Mobility Subscription data (data needed for UE |
GPSI List |
List of the GPSI (Generic Public Subscription Identifier) used both inside and outside of the 3GPP system to address a 3GPP subscription (see NOTE 9). |
|
Registration and Mobility Management) |
Internal Group ID-list |
List of the subscribed internal group(s) that the UE belongs to. |
|
Subscribed UE-AMBR |
The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR QoS Flows according to the subscription of the user. |
|
|
Subscribed UE-Slice-MBR(s) |
List of maximum aggregated uplink and downlink MBRs to be shared across all GBR and Non-GBR QoS Flows related to the same S-NSSAI according to the subscription of the user. There is a single uplink and a single downlink value per S-NSSAI. |
|
|
Subscribed S-NSSAIs |
The Network Slices that the UE subscribes to. In the roaming case, it indicates the subscribed Network Slices applicable to the Serving PLMN (NOTE 11). |
|
|
Default S-NSSAIs |
The Subscribed S-NSSAIs marked as default S-NSSAI. In the roaming case, only those applicable to the Serving PLMN (NOTE 12). |
|
|
S-NSSAIs subject to Network Slice-Specific Authentication and Authorization |
The Subscribed S-NSSAIs marked as subject to NSSAA. When present, the GPSI list shall include at least one GPSI. |
|
|
Network Slice Simultaneous Registration Group Information |
Optionally, for each S-NSSAI in the Subscribed S-NSSAIs, one or more value of Network Slice Simultaneous Registration Group(s) (NOTE 11) associated with the S-NSSAI. |
|
|
UE Usage Type |
As defined in clause 5.15.7.2 of TS 23.501 [2]. |
|
|
RAT restriction |
3GPP Radio Access Technology(ies) not allowed the UE to access. |
|
|
Forbidden area |
Defines areas in which the UE is not permitted to initiate any communication with the network. |
|
|
Service Area Restriction |
Indicates Allowed Areas in which the UE is permitted to initiate communication with the network and Non-allowed areas in which the UE and the network are not allowed to initiate Service Request or SM signalling to obtain user services. |
|
|
Core Network type restriction |
Defines whether UE is allowed to connect to 5GC and/or EPC for this PLMN. |
|
|
CAG information |
The CAG information includes Allowed CAG list and, optionally an indication whether the UE is only allowed to access 5GS via CAG cells as defined in clause 5.30.3 of TS 23.501 [2]. |
|
|
CAG information Subscription Change Indication |
When present, indicates to the serving AMF that the CAG information in the subscription data changed and the UE must be updated. |
|
|
RFSP Index |
An index to specific RRM configuration in the NG-RAN. |
|
|
Subscribed Periodic Registration Timer |
Indicates a subscribed Periodic Registration Timer value, which may be influenced by e.g. network configuration parameter as specified in clause 4.15.6.3a. |
|
|
Subscribed Active Time |
Indicates a subscribed active time value, which may be influenced by e.g. network configuration parameter as specified in clause 4.15.6.3a. |
|
|
MPS priority |
Indicates the user is subscribed to MPS as indicated in clause 5.16.5 of TS 23.501 [2]. |
|
|
MCX priority |
Indicates the user is subscribed to MCX as indicated in clause 5.16.6 of TS 23.501 [2]. |
|
|
AMF-Associated Expected UE Behaviour parameters |
Information on expected UE movement and communication characteristics. See clause 4.15.6.3 |
|
|
Steering of Roaming |
List of preferred PLMN/access technology combinations and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs or HPLMN/Credentials Holder indication that no change of the above list(s) stored in the UE is needed (see NOTE 3). Optionally includes an indication that the UDM requests an acknowledgement of the reception of this information from the UE. |
|
|
SoR Update Indicator for Initial Registration |
An indication whether the UDM requests the AMF to retrieve SoR information when the UE performs Registration with NAS Registration Type "Initial Registration". |
|
|
SoR Update Indicator for Emergency Registration |
An indication whether the UDM requests the AMF to retrieve SoR information when the UE performs Registration with NAS Registration Type "Emergency Registration". |
|
|
Network Slicing Subscription Change Indicator |
When present, indicates to the serving AMF that the subscription data for network slicing changed and the UE configuration must be updated. |
|
|
Provide the UE with the full set of subscribed S-NSSAIs |
Indicates the AMF to provide the UE with the full set of subscribed S-NSSAIs even if they do not share a common NSSRG. |
|
|
Tracing Requirements |
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421 [39]. |
|
|
Inclusion of NSSAI in RRC Connection Establishment Allowed |
When present, it is used to indicate that the UE is allowed to include NSSAI in the RRC connection Establishment in clear text for 3GPP access. |
|
|
Service Gap Time |
Used to set the Service Gap timer for Service Gap Control (see clause 5.31.16 of TS 23.501 [2]). |
|
|
Subscribed DNN list |
List of the subscribed DNNs for the UE (NOTE 1). Used to determine the list of LADN available to the UE as defined in clause 5.6.5 of TS 23.501 [2]. |
|
|
UDM Update Data |
Includes a set of parameters see clause 4.20.1 for parameters possible to deliver) to be delivered from UDM to the UE via NAS signalling as defined in clause 4.20 (NOTE 3). Optionally includes an indication that the UDM requests an acknowledgement of the reception of this information from the UE and an indication for the UE to re-register. |
|
|
NB-IoT UE priority |
Numerical value used by the NG-RAN to prioritise between UEs accessing via NB-IoT. |
|
|
Enhanced Coverage Restriction |
Specifies whether CE mode B is restricted for the UE, or both CE mode A and CE mode B are restricted for the UE, or both CE mode A and CE mode B are not restricted for the UE. |
|
|
NB-IoT Enhanced Coverage Restriction |
Indicates whether Enhanced Coverage for NB-IoT UEs is restricted or not. |
|
|
IAB-Operation allowed |
Indicates that the subscriber is allowed for IAB-operation as specified in clause 5.35.2 of TS 23.501 [2]. |
|
|
Charging Characteristics |
It contains the Charging Characteristics as defined in Annex A of TS 32.256 [71]. This information, when provided, shall override any corresponding predefined information at the AMF. |
|
|
Extended idle mode DRX cycle length |
Indicates a subscribed extended idle mode DRX cycle length value. |
|
|
PCF Selection Assistance info |
list of combination of DNN and S-NSSAI that indicates that the same PCF needs to be selected for AM Policy Control and SM Policy Control (NOTE 10). |
|
|
AerialUESubscriptionInfo |
Aerial UE Subscription Information. It contains an Indication on whether Aerial service for the UE is allowed or not. |
|
|
Routing Indicator |
Routing Indicator assigned to the SUPI. |
|
|
Slice Selection Subscription data (data needed for |
Subscribed S-NSSAIs |
The Network Slices that the UE subscribes to. In roaming case, it indicates the subscribed network slices applicable to the serving PLMN (NOTE 11). |
|
Slice Selection as described in clause 4.2.2.2.3 and |
Default S-NSSAIs |
The Subscribed S-NSSAIs marked as default S-NSSAI. In the roaming case, only those applicable to the Serving PLMN (NOTE 12). |
|
in clause 4.11.0a.5) |
S-NSSAIs subject to Network Slice-Specific Authentication and Authorization |
The Subscribed S-NSSAIs marked as subject to NSSAA. |
|
Network Slice Simultaneous Registration Group (NSSRG) Information |
Optionally, for each S-NSSAI in the Subscribed S-NSSAIs, the one or more value of Network Slice Simultaneous Registration Group(s) (NOTE 11) associated with the S-NSSAI. |
|
|
SMF Selection |
SUPI |
Key |
|
Subscription data (data needed for SMF |
SMF Selection Subscription data contains one or more S-NSSAI level subscription data: |
|
|
Selection as described |
S-NSSAI |
Indicates the value of the S-NSSAI. |
|
in clause 6.3.2 of |
Subscribed DNN list |
List of the subscribed DNNs for the UE (NOTE 1). |
|
TS 23.501 [2]) |
Default DNN |
The default DNN if the UE does not provide a DNN (NOTE 2). |
|
DNN(s) subject to aerial services |
List of DNNs that are used for aerial services (e.g. UAS operations or C2, etc.) as described in TS 23.256 [80]. (see NOTE 13). |
|
|
LBO Roaming Information |
Indicates whether LBO roaming is allowed per DNN, or per (S-NSSAI, subscribed DNN). (NOTE 16) |
|
|
HR-SBO allowed indication |
Indicates whether Session Breakout for HR Session using ULCL/BP in VPLMN is allowed per DNN, or per (S-NSSAI, subscribed DNN). (NOTE 17) |
|
|
Interworking with EPS indication list |
Indicates whether EPS interworking is supported per (S-NSSAI, subscribed DNN). |
|
|
Same SMF for Multiple PDU Sessions to the same DNN and S-NSSAI |
Indication whether the same SMF for multiple PDU Sessions to the same DNN and S-NSSAI is required. |
|
|
Invoke NEF indication |
When present, indicates, per S-NSSAI and per DNN, that NEF based infrequent small data transfer shall be used for the PDU Session (see NOTE 8). |
|
|
SMF information for static IP address/prefix |
When static IP address/prefix is used, this may be used to indicate the associated SMF information per (S-NSSAI, DNN). |
|
|
UE context in SMF |
SUPI |
Key. |
|
data |
PDU Session Id(s) |
List of PDU Session Id(s) for the UE. |
|
For emergency PDU Session Id: |
||
|
Emergency Information |
The SMF+PGW-C FQDN for emergency session used for interworking with EPC. |
|
|
For each non-emergency PDU Session Id: |
||
|
DNN |
DNN for the PDU Session. |
|
|
SMF |
Allocated SMF for the PDU Session. Includes SMF IP Address and SMF NF Id. |
|
|
SMF+PGW-C FQDN |
The S5/S8 SMF+PGW-C FQDN used for interworking with EPS (see NOTE 5). |
|
|
PCF ID |
The PCF ID serving the PDU Session/PDN Connection. |
|
|
SMS Management Subscription data (data needed by |
SMS parameters |
Indicates SMS parameters subscribed for SMS service such as SMS teleservice, SMS barring list |
|
SMSF for SMSF Registration) |
Trace Requirements |
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421 [39]. This information is only sent to a SMSF in HPLMN. |
|
Routing Indicator |
Routing Indicator assigned to the SUPI. |
|
|
SMS Subscription data |
SMS Subscription |
Indicates subscription to any SMS delivery service over NAS irrespective of access type. |
|
(data needed in AMF) |
||
|
UE Context in SMSF data |
SMSF Information |
Indicates SMSF allocated for the UE, including SMSF address and SMSF NF ID. |
|
Access Type |
3GPP or non-3GPP access through this SMSF |
|
|
Session Management Subscription data (data needed for PDU |
GPSI List |
List of the GPSI (Generic Public Subscription Identifier) used both inside and outside of the 3GPP system to address a 3GPP subscription. |
|
Session Establishment) |
Internal Group ID-list |
List of the subscribed internal group(s) that the UE belongs to. |
|
Trace Requirements |
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc…) is defined in TS 32.421 [39]. This information is only sent to a SMF in the HPLMN or one of its equivalent PLMN(s). |
|
|
Routing Indicator |
Routing Indicator assigned to the SUPI. |
|
|
Session Management Subscription data contains one or more S-NSSAI level subscription data: |
||
|
S-NSSAI |
Indicates the value of the S-NSSAI. |
|
|
Subscribed DNN list |
List of the subscribed DNNs for the S-NSSAI (NOTE 1). |
|
|
For each DNN in S-NSSAI level subscription data: |
||
|
DNN |
DNN for the PDU Session. |
|
|
Aerial service indication |
Indicates whether the DNN is used for aerial services (e.g. UAS operations or C2, etc.) as described in TS 23.256 [80]. |
|
|
Framed Route information |
Set of Framed Routes. A Framed Route refers to a range of IPv4 addresses / IPv6 Prefixes to associate with a PDU Session established on this (DNN, S-NSSAI). See NOTE 4. |
|
|
IP Index information |
Information used for selecting how the UE IP address is to be allocated (see clause 5.8.2.2.1 in TS 23.501 [2]). |
|
|
Allowed PDU Session Types |
Indicates the allowed PDU Session Types (IPv4, IPv6, IPv4v6, Ethernet and Unstructured) for the DNN, S-NSSAI. See NOTE 6. |
|
|
Default PDU Session Type |
Indicates the default PDU Session Type for the DNN, S-NSSAI. |
|
|
Allowed SSC modes |
Indicates the allowed SSC modes for the DNN, S-NSSAI. |
|
|
Default SSC mode |
Indicate the default SSC mode for the DNN, S-NSSAI. |
|
|
Interworking with EPS indication |
Indicates whether interworking with EPS is supported for this DNN and S-NSSAI. |
|
|
5GS Subscribed QoS profile |
The QoS Flow level QoS parameter values (5QI and ARP) for the DNN, S-NSSAI (see clause 5.7.2.7 of TS 23.501 [2]). |
|
|
Charging Characteristics |
It contains Charging Characteristics as defined in Annex A clause A.1 of TS 32.255 [45]. This information, when provided, shall override any corresponding predefined information at the SMF. |
|
|
Subscribed-Session-AMBR |
The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR QoS Flows in each PDU Session, which are established for the DNN, S-NSSAI. |
|
|
Static IP address/prefix |
Indicate the static IP address/prefix for the DNN, S-NSSAI. |
|
|
User Plane Security Policy |
Indicates the security policy for integrity protection and encryption for the user plane. |
|
|
PDU Session continuity at inter RAT mobility |
Provides for this DDN, S-NSSAI how to handle a PDU Session when UE the moves to or from NB-IoT. Possible values are: maintain the PDU session; disconnect the PDU session with a reactivation request; disconnect PDU session without reactivation request; or to leave it to local VPLMN policy. |
|
|
NEF Identity for NIDD |
When present, indicates, per S-NSSAI and per DNN, the identity of the NEF to anchor Unstructured PDU Session. When not present for the S-NSSAI and DNN, the PDU session terminates in UPF (see NOTE 8). |
|
|
NIDD information |
Information such as External Group Identifier, External Identifier, MSISDN, or AF Identifier used for SMF-NEF Connection. |
|
|
SMF-Associated Expected UE Behaviour parameters |
Parameters on expected characteristics of a PDU Session their corresponding validity times as specified in clause 4.15.6.3. |
|
|
Suggested number of downlink packets |
Parameters on expected PDU session characteristics as specified in clauses 4.15.3.2.3b and 4.15.6.3a. |
|
|
ATSSS information |
Indicates whether MA PDU session establishment is allowed. |
|
|
Secondary authentication indication |
Indicates that whether the Secondary authentication/authorization (as defined in clause 5.6 of TS 23.501 [2]) is required for PDU Session Establishment or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2. (see NOTE 14) |
|
|
DN-AAA Server UE IP address allocation indication |
Indicates that whether the SMF is required to request the UE IP address from the DN-AAA Server (as defined in clause 5.6 of TS 23.501 [2]) for PDU Session Establishment or or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2. |
|
|
DN-AAA Server addressing information |
If at least one of secondary DN-AAA authentication, DN-AAA authorization or DN-AAA UE IP address allocation is required by subscription data, the subscription data may also contain DN-AAA Server addressing information. |
|
|
Edge Configuration Server Address Configuration Information |
Consists of one or more ECS Configuration Information as defined in clause 8.3.2.1 of TS 23.558 [83]. |
|
|
API based secondary authentication indication |
Indicates that whether the API based Secondary authentication/authorization (as defined in clause 5.2.3 of TS 23.256 [80]) is required for PDU Session Establishment or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2. (see NOTE 14). |
|
|
UE authorization for EAS discovery via EASDF |
Indicates whether the UE is authorized to use 5GC assisted EAS discovery via EASDF (as defined in TS 23.548 [74]). |
|
|
Identifier translation |
SUPI |
Corresponding SUPI for input GPSI. |
|
(Optional) MSISDN |
Corresponding GPSI (MSISDN) for input GPSI (External Identifier). This is optionally provided for legacy SMS infrastructure not supporting MSISDN-less SMS. The presence of an MSISDN should be interpreted as an indication to the NEF that MSISDN shall be used to identify the UE when sending the SMS to the SMS-SC via T4. |
|
|
GPSI |
Corresponding GPSI for input SUPI and associated application information (e.g. Application Port ID) (NOTE 15). |
|
|
Intersystem continuity Context |
(DNN, PGW FQDN) list |
For each DNN, indicates the SMF+PGW-C which support interworking with EPC. |
|
LCS privacy (data needed by GMLC) |
LCS privacy profile data |
Provides information for LCS privacy classes and Location Privacy Indication (LPI) as defined in clause 5.4.2 in TS 23.273 [51] |
|
LCS mobile origination (data needed by AMF) |
LCS Mobile Originated Data |
When present, indicates to the serving AMF which LCS mobile originated services are subscribed as defined in clause 7.1 in TS 23.273 [51]. |
|
User consent (see TS 23.288 [50]) |
User consent for UE data collection |
Indicates whether the user has given consent for collecting, distributing and analysing UE related data. User consent is provided per purpose (e.g. analytics, model training). |
|
UE reachability |
UE reachability information |
Provides, per PLMN, the list of NF IDs or the list of NF sets or the list of NF types authorized to request notification for UE’s reachability (NOTE 7). |
|
V2X Subscription data (see TS 23.287 [73]) |
NR V2X Services Authorization |
Indicates whether the UE is authorized to use the NR sidelink for V2X services as Vehicle UE, Pedestrian UE, or both. |
|
LTE V2X Services Authorization |
Indicates whether the UE is authorized to use the LTE sidelink for V2X services as Vehicle UE, Pedestrian UE, or both. |
|
|
NR UE-PC5-AMBR |
AMBR of UE’s NR sidelink (i.e. PC5) communication for V2X services. |
|
|
LTE UE-PC5-AMBR |
AMBR of UE’s LTE sidelink (i.e. PC5) communication for V2X services. |
|
|
ProSe Subscription data (see TS 23.304 [77]) |
ProSe Service Authorization |
Indicates whether the UE is authorized to use ProSe Direct Discovery, ProSe Direct Communication, or both and whether the UE is authorized to use or serve as a ProSe UE-to-Network Relay. |
|
ProSe NR UE-PC5-AMBR |
AMBR of UE’s NR sidelink (i.e. PC5) communication for ProSe services. |
|
|
MBS Subscription data (see TS 23.247 [78]) |
MBS Service Authorization |
Indicates whether the UE is authorized to use Multicast MBS service. May also indicate the multicast MBS Session which the UE is allowed to join if the UE is authorized to use multicast MBS Service. |
|
NOTE 1: The Subscribed DNN list can include a wildcard DNN. NOTE 2: The default DNN shall not be a wildcard DNN. NOTE 3: The Steering of Roaming information and UDM Update Data are protected using the mechanisms defined in TS 33.501 [15]. NOTE 4: Framed Route information and Framed Route(s) are defined in TS 23.501 [2]. NOTE 5: Depending on the scenario PGW-C FQDN may be for S5/S8, or for S2b (ePDG case). NOTE 6: The Allowed PDU Session Types configured for a DNN which supports interworking with EPC should contain only the PDU Session Type corresponding to the PDN Type configured in the APN that corresponds to the DNN. NOTE 7: Providing a list of NF types or a list of NF sets may be more appropriate for some deployments, e.g. in highly dynamic NF lifecycle management deployments. NOTE 8: For a S-NSSAI and a DNN, the "Invoke NEF Indication" shall be present in the SMF selection subscription data if and only if the "NEF Identity for NIDD" Session Management Subscription Data includes a NEF Identity. When the "NEF Identity for NIDD" Session Management Subscription Data includes a NEF Identity for a S-NSSAI and DNN, the "Control Plane Only Indicator" will always be set for PDU Sessions to this S-NSSAI and DNN (see clause 5.31.4.1 of TS 23.501 [2]). NOTE 9: When multiple GPSIs are included in the GPSI list, any GPSI in the list can be used in NSSAA procedures. NOTE 10: The same PCF can be selected to serve the UE and to serve one or multiple PDU sessions, each of them is indicated in the list of S-NSSAI, DNN combinations in the PCF Selection Assistance Info. Providing one combination of DNN and S-NSSAI in the PCF Selection Assistance Info is assumed if interworking with EPS is needed. In case multiple PDU sessions to one DNN, S-NSSAI are established in EPS, it is appropriate to select same PCF by configuration or by using existing method, e.g. same PCF selection in usage monitoring. NOTE 11: If Network Slice Simultaneous Registration Group information is present and the VPLMN does not support the subscription-based restrictions to simultaneous registration of network slices, the subset of the Subscribed S-NSSAIs defined in clause 5.15.12 of TS 23.501 [2], are included, without providing the NSSRG information. NOTE 12: The Default S-NSSAIs (if more than one is present) are associated with common NSSRG values if NSSRG information is present. At least one Default S-NSSAI shall be present in a subscription including NSSRG information. NOTE 13: When UUAA is performed in the AMF (as in clause 5.2.2 of TS 23.256 [80]) and UUAA-MM status is FAILED or PENDING, the AMF shall reject PDU session establishment requests from the UE for a DNN that is subject to aerial services. NOTE 14: For a DNN in S-NSSAI either a DN-AAA based secondary authentication, or an API based secondary authentication can be configured. When API based authentication of the PDU session is required, Secondary authentication indication shall not be present. NOTE 15: A GPSI may be associated with Application Port ID, MTC Provider Information and/or AF Identifier. NOTE 16: For non-roaming UE (e.g. accessing SNPN with CH credentials), LBO roaming information does not apply. NOTE 17: For non-roaming UE, HR-SBO allowed indication does not apply. |
||
Editor’s note: For supporting the local traffic routing in VPLMN for home routed roaming session, it is FFS whether to add 1) HR-SBO authorization indication or 2) HR-SBO authorization information in Session Management Subscription data.
Table 5.2.3.3.1-2: Group Subscription data types
|
Subscription data type |
Field |
Description |
|---|---|---|
|
Group Identifier translation |
External Group Identifier |
Identifies external group of UEs that the UE belongs to as defined in TS 23.682 [23]. |
|
Internal Group Identifier |
Identifies internal group of UEs that the UE belongs to as defined in TS 23.501 [2]. |
|
|
SUPI list |
Corresponding SUPI list for input External Group Identifier. |
|
|
Group Data (NOTE 1) |
Internal Group Identifier |
Internal identifiers of the group of UEs that the Group Data belongs to. |
|
Group data |
In the case of 5G VN related groups the content of this information is defined in clause 4.15.6.3b. |
|
|
NOTE 1: Group Data within Group Subscription Data can be managed using the Shared Data feature defined in TS 29.503 [52]. In that case, Shared Data is identified using Shared Data identifier and can contain additional information than the one defined in this table. |
||
At least a mandatory key is required for each Subscription Data Type to identify the corresponding data. Depending on the use case, for some Subscription Data Types it is possible to use one or multiple sub keys to further identify the corresponding data, as defined in Tables 5.2.3.3.1-3 and 5.2.3.3.1-4 below.
Table 5.2.3.3.1-3: UE Subscription data types keys
|
Subscription Data Types |
Data Key |
Data Sub Key |
|
Access and Mobility Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
SMF Selection Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
UE context in SMF data |
SUPI |
S-NSSAI |
|
SMS Management Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
SMS Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
UE Context in SMSF data |
SUPI |
– |
|
Session Management Subscription data |
SUPI |
S-NSSAI |
|
DNN |
||
|
Serving PLMN ID and optionally NID |
||
|
Identifier translation |
GPSI |
– |
|
SUPI |
Application Port ID, MTC Provider Information, AF Identifier |
|
|
Slice Selection Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
Intersystem continuity Context |
SUPI |
DNN |
|
LCS privacy |
SUPI |
– |
|
LCS mobile origination |
SUPI |
– |
|
User consent |
SUPI |
Purpose |
|
UE reachability |
SUPI |
– |
|
V2X Subscription data |
SUPI |
– |
|
ProSe Subscription data |
SUPI |
– |
|
MBS Subscription data |
SUPI |
– |
Table 5.2.3.3.1-4: Group Subscription data types keys
|
Subscription Data Types |
Data Key |
Data Sub Key |
|
Group Identifier translation |
External Group Identifier |
– |
|
Internal Group Identifier |
– |
|
|
Group Data |
Internal Group Identifier |
– |
Wireline access specific subscription data parameters are specified in TS 23.316 [53].
5.2.3.3.2 Nudm_SDM_Get service operation
Service Operation name: Nudm_SDM_Get
Description: Consumer NF gets the subscription data indicated by the subscription data type input from UDM. The UDM shall check the requested consumer is authorized to get the specific subscription data requested. In the case of NF consumer is SMF, the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP, Subscribed S-NSSAI(s).
Inputs, Required: NF ID, Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: Data Sub Key(s), SoR Update Indicator, AF Identifier (for AF authorisation by the UDM), Disaster Roaming Indicator indicating that Disaster Roaming service is applied, Serving PLMN ID.
NOTE: Some subscription data subsets can be specific to the Serving PLMN where the UE is registered (e.g. access and mobility subscription data) as defined in clause 5.2.12.2.1. If the corresponding NF consumer does not include the Serving PLMN ID, the UDM provides the subscription data for the SUPI associated to the HPLMN.
If the AMF already has subscription data for the UE but the SoR Update Indicator in the UE context requires the AMF to retrieve SoR information depending on the NAS Registration Type ("Initial Registration" or "Emergency Registration"), the AMF shall include SoR update indicator in the Nudm_SDM_Get depending on the NAS Registration type.
Outputs, Required: The consumer NF gets the requested subscription data.
Outputs, Optional: None.
5.2.3.3.3 Nudm_SDM_Notification service operation
Service or service operation name: Nudm_SDM_Notification
Description: The UDM notifies NF consumer of the updates of Subscription Data indicated by the "subscription data Type" input and additional UDM-related parameters.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: None.
Outputs, Required: Result Indication.
The UDM invokes this service operation under the following cases:
– When the subscription data is updated at the UDM, the updated subscription information is notified to the serving NF that has subscribed for the specific subscription data type to be notified.
– When the UDM needs to deliver Steering of Roaming information to a UE.
– When the UDM needs to deliver UDM Update Data to a UE (e.g. a new Routing Indicator or Default Configured NSSAI to the UE).
If the updated subscription information is related to session management the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP.
Outputs, Optional: Redirection information.
If the NF consumer is AMF and if the result of the service operation fails, AMF shall set corresponding cause value in result indication which can be used by the UDM for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the UDM to resend UE related message to the AMF that serves the UE.
5.2.3.3.4 Nudm_SDM_Subscribe service operation
Service operation name: Nudm_SDM_Subscribe
Description: The NF consumer subscribes for updates to Subscription Data indicated by the ‘subscription data type’ input. The UDM shall check the requested consumer is authorized to subscribe to requested updates.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: Data Sub Key(s), Immediate Report Indication, Disaster Roaming Indicator indicating that Disaster Roaming service is applied.
Outputs, Required: None.
Outputs, Optional: Subscription Data.
5.2.3.3.5 Nudm_SDM_Unsubscribe service operation
Service operation name: Nudm_SDM_Unsubscribe
Description: The NF consumer unsubscribes from updates to Subscription Data indicated by the ‘subscription data type input.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: If the NF type is SMF: DNN, S-NSSAI.
Outputs, Required: None.
Outputs, Optional: None.
5.2.3.3.6 Nudm_SDM_Info service operation
Service Operation name: Nudm_SDM_Info
Description: Consumer NF provides UDM with information about the status of the subscription data management procedures. This service operation is used for:
– providing acknowledgement from the UE to UDM about successful delivery of Steering of Roaming information via the AMF as defined in TS 23.122 [22].
– providing acknowledgement from the UE to UDM about successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF.
– providing acknowledgement from the UE to UDM about successful delivery of UDM Update Data via the AMF as defined in clause 4.20.
– providing acknowledgement from the AMF to UDM that the delivery of the UDM Update Data has failed as defined in clause 4.20.
Inputs, Required: SUPI, Info (e.g. UE acknowledgment of SoR information from UDM via AMF, UE acknowledgement of successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF, UE acknowledgment of UDM Update Data from UDM via AMF, failed transmission of UDM Update Data from UDM via AMF, failed transmission of SoR information from UDM via AMF).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
5.2.3.3.7 Void
5.2.3.3.8 Nudm_SDM_ModifySubscription service operation
Service operation name: Nudm_SDM_ModifySubscription
Description: The NF consumer requests to modify an existing subscription to notifications of data changes.
Inputs, Required: Subscription Correlation ID, SUPI.
Inputs, Optional: Expiry time, Monitored resource URIs.
Outputs, Required: None.
Outputs, Optional: Subscription Data.
5.2.3.4 Nudm_UEAuthentication Service
5.2.3.4.1 General
This service is used by the requester NF to get authentication data and provide UDM with the result of the authentication procedure success. In the case of SNPN, this service may be used to instruct the AUSF to execute authentication towards AAA-S.
5.2.3.4.2 Nudm_UEAuthentication_Get service operation
See TS 33.501 [15].
5.2.3.4.3 Nudm_UEAuthentication_ResultConfirmation service operation
See TS 33.501 [15].
5.2.3.5 Nudm_EventExposure service
5.2.3.5.1 General
See clause 4.15.3.1.
5.2.3.5.2 Nudm_EventExposure_Subscribe service operation
Service operation name: Nudm_EventExposure_Subscribe
Description: The NF consumer subscribes to receive an event.
NF Consumers: NEF, SMS-GMSC.
Inputs, Required: Target of Event Reporting: UE(s) ID (SUPI or GPSI, Internal Group Identifier or External Group Identifier, or indication that any UE is targeted), Event filter containing the Event Id(s) (see clause 4.15.3.1) and Event Reporting Information defined in Table 4.15.1-1.
Inputs, Optional: Expiry time, DNN, S-NSSAI, traffic descriptor identifying the source of the downlink IP or Ethernet traffic (for Availability after DDN Failure and downlink data delivery status events), MTC Provider Information, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested).
For configuration of monitoring events applicable to both EPC and 5GC, a combined SCEF+NEF indicates that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC) and may include a SCEF address (i.e. if the event needs to be configured in a serving node in the EPC and the corresponding notification needs to be sent directly to the SCEF).
Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator’s policy).
Outputs, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1), Number of UE if the External Group Identifier and Maximum Number of Reports are included in the inputs.
Number of UEs indicates the number of UEs within the group identified by the External Group Identifier. The NEF uses this value to determine whether the monitoring event has been reported for all group member UEs.
5.2.3.5.3 Nudm_EventExposure_Unsubscribe service operation
Service operation name: Nudm_EventExposure_Unsubscribe
Description: the consumer deletes the subscription of an event if already defined in UDM.
Inputs, Required: Subscription Correlation ID.
Outputs, Required: Operation execution result indication.
5.2.3.5.4 Nudm_EventExposure_Notify service operation
Service operation name: Nudm_EventExposure_Notify
Description: UDM reports the event to the consumer that has previously subscribed.
Inputs, Required: Event ID, Notification Correlation Information, time stamp.
Inputs, Optional: Event specific parameters list, Event Removal Indication, list of group member UE(s) whose subscription to event notification(s) are removed from a group-based event notification subscription, UE(s) added/removed to/from the group.
Outputs, Required: None.
5.2.3.5.5 Nudm_EventExposure_ModifySubscription service operation
Service operation name: Nudm_EventExposure_ModifySubscription
Description: The NF consumer requests to modify an existing subscription to event notifications.
NF Consumers: NEF, SMS-GMSC.
Inputs, Required: UE(s) ID (SUPI or GPSI, Internal Group Identifier or External Group Identifier, or any UE), Subscription Correlation ID, Modifications to the Event Subscription.
Inputs, Optional:
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
5.2.3.6 Nudm_ParameterProvision service
5.2.3.6.1 General
This service is for allowing NEF to provision of information which can be used for the UE in 5GS.
Parameter Provision data types used in the Nudm_ParameterProvision Service are defined in Table 5.2.3.6.1-1 below.
Table 5.2.3.6.1-1: Parameter Provision data types
|
Parameter Provision data type |
Description |
|
Expected UE Behaviour parameters |
See clause 4.15.6.3 |
|
Network Configuration parameters |
See clause 4.15.6.3a |
|
5G VN group configuration data |
5G VN Group Data and 5G VN Group membership management parameters for the 5G VN Group. See clause 4.15.6.3b and clause 4.15.6.3c. |
|
Location Privacy Indication parameters |
Location Privacy Indication parameters of the "LCS privacy" Data Subset of the Subscription Data. See clause 5.2.3.3.1 and clause 7.1 of TS 23.273 [51]. |
|
Enhanced Coverage Restriction Information |
See clause 4.27.1 and clause 5.31.12 of TS 23.501 [2]. |
|
ECS Address Configuration Information |
See clause 4.15.6.3d. |
|
Multicast MBS group membership management parameters |
See clause 7.2.9 of TS 23.247 [78]. |
|
MBS Session Authorization information |
See clause 7.2.9 of TS 23.247 [78]. |
At least a mandatory key is required for each Parameter Provision Data Type to identify the corresponding data as defined in Table 5.2.3.6.1-2.
Table 5.2.3.6.1-2: Parameter Provision data types keys
|
Parameter Provision Data Types |
Data Key |
Data Sub Key |
|
Expected UE Behaviour parameters |
GPSI or External Group ID |
– |
|
Network Configuration parameters |
GPSI |
– |
|
5G VN group data |
External Group Identifier |
– |
|
5G VN group membership management parameters |
External Group Identifier |
– |
|
Location Privacy Indication parameters. |
GPSI |
– |
|
Enhanced Coverage Restriction Information |
GPSI |
– |
|
ECS Address Configuration Information |
GPSI or External Group ID or any UE |
– |
|
Multicast MBS group membership management parameters |
External Group Identifier |
– |
|
MBS Session Authorization information |
External Group ID |
– |
5.2.3.6.2 Nudm_ParameterProvision_Update service operation
Service operation name: Nudm_ParameterProvision_Update.
Description: The consumer updates the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters, Location Privacy Indication parameters, Enhanced Coverage Restriction Information, ECS Address Configuration Information), 5G VN group related information (5G VN group data, 5G VN membership management), or Multicast MBS group related information (MBS Session Authorization, Multicast MBS group membership management).
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI or SUPI, External Group ID, at least one of the Expected UE Behaviour parameters or at least one of the Network Configuration parameters or 5G VN group related information, MTC Provider Information, Validity Time or Location Privacy Indication parameters or Enhanced Coverage Restriction Information or ECS Address Configuration Information, or Multicast MBS group related information.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: Transaction specific parameters, if available.
For Multicast MBS group related information, refer to TS 23.247 [78].
5.2.3.6.3 Nudm_ParameterProvision_Create service operation
Service operation name: Nudm_ParameterProvision_Create
Description: The consumer creates a Network Configuration with one or more parameters, a 5G VN group related information (e.g. 5G VN group data, 5G VN membership management), or Multicast MBS group related information.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI, External Group ID, one or multiple Network Configuration parameters, or ECS Address Configuration Information, or for 5G VN group creation, External Group ID and 5G VN group related information, MTC Provider Information, or for Multicast MBS group creation and related information.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: Transaction specific parameters, if available; Internal Group ID if the inputs include a new 5G VN configuration.
For Multicast MBS group related information, refer to TS 23.247 [78].
5.2.3.6.4 Nudm_ParameterProvision_Delete service operation
Service operation name: Nudm_ParameterProvision_Delete
Description: The consumer deletes one or more previously created Network Configuration parameters, or a 5G VN group, or ECS Address Configuration Information.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI, External Group ID, for 5G VN group deletion or for Multicast MBS group deletion or Network Configuration of Parameters.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: None.
5.2.3.6.5 Nudm_ParameterProvision_Get service operation
Service operation name: Nudm_ParameterProvision_Get
Description: The consumer gets the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters).
Inputs, Required: GPSI, AF Identifier, requested information (e.g. Expected UE Behaviour, Network Configuration parameters).
Inputs, Optional: None.
Outputs, Required: Requested data, Operation execution result indication.
Outputs, Optional: None.
5.2.3.7 Nudm_NIDDAuthorisation service
5.2.3.7.1 General
See clause 4.25.3.
5.2.3.7.2 Nudm_NIDDAuthorisation_Get service operation
Service operation name: Nudm_NIDDAuthorisation_Get
Description: The consumer requests authorisation for NIDD Configuration.
Inputs, Required: GPSI or External Group Identifier, DNN, S-NSSAI, MTC Provider Information, Update Notification Address.
Inputs, Optional: NIDD Duration.
Outputs, Required: Single value or list of (SUPI, GPSI), Result.
Outputs, Optional: NIDD Duration.
5.2.3.7.3 Nudm_NIDDAuthorisation_UpdateNotify service operation
Service operation name: Nudm_NIDDAuthorisation_UpdateNotify
Description: This service operation is used by the UDM to notify the NIDD Authorization Update to NF consumer.
Inputs, Required: SUPI, GPSI, DNN, S-NSSAI, Result.
Inputs, Optional: Cause (e.g. subscription withdrawal, DNN used for NIDD service is removed from the UE subscription), NIDD Duration.
Outputs, Required: None.
5.2.3.7.4 Void
5.2.3.7.5 Void
5.2.3.8 Nudm_ServiceSpecificAuthorisation service
5.2.3.8.1 General
Service description: This service is for authorisation of a specific service configuration.
5.2.3.8.2 Nudm_ServiceSpecificAuthorisation_Create service operation
Service operation name: Nudm_ServiceSpecificAuthorisation_Create
Description: The consumer requests authorisation for a specific service configuration.
Inputs, Required: GPSI or External Group Id, DNN, S-NSSAI, Service Type (e.g. AF guidance for URSP), Update Notification address.
Inputs, Optional: MTC Provider Information, AF ID.
Outputs, Required: Authorisation result indication, SUPI or Internal Group Id, Service Specific Authorization Id.
Outputs, Optional: None.
5.2.3.8.3 Nudm_ServiceSpecificAuthorisation_UpdateNotify service operation
Service operation name: Nudm_ServiceSpecificAuthorisation_UpdateNotify
Description: This service operation is used by the UDM to notify a Service Specific Authorisation Update to NF consumer.
Inputs, Required: GPSI or External Group Id, SUPI or Internal Group Id, Status, Cause (e.g. subscription withdrawal, DNN associated to the authorization is removed from UE subscription).
Inputs, Optional: DNN, S-NSSAI, Service Type (e.g. AF guidance for URSP), MTC Provider Information, AF ID.
Outputs, Required: None.
5.2.3.8.4 Nudm_ServiceSpecificAuthorisation_Remove service operation
Service operation name: Nudm_ServiceSpecificAuthorisation_Remove
Description: The consumer requests the removal of the authorisation for a specific service configuration.
Inputs, Required: Service Specific Authorisation Id.
Outputs, Required: None.
5.2.3.9 Nudm_ReportSMDeliveryStatus service
5.2.3.9.1 General
Service description: This service is to report the SM-Delivery Status to UDM.
5.2.3.9.2 Nudm_ReportSMDeliveryStatus_Request service operation
Service operation name: Nudm_ReportSMDeliveryStatus_Request
Description: Reports the SM-Delivery Status to UDM.
Inputs, Required: GPSI, SM-Delivery status.
Inputs, Optional: None.
Outputs, Required: Report SM-Delivery status result.
Outputs, Optional: None.