5.2.12 UDR Services
23.5023GPPProcedures for the 5G System (5GS)Release 18TS
5.2.12.1 General
The following Data Set Identifiers shall be considered in this release: Subscription Data, Policy Data, Application data and Data for Exposure. The corresponding Data Subset Identifiers and Data (Sub)Key(s) are defined in Table 5.2.12.2.1-1.
The set of Data Set Identifiers shall be extensible to cater for new identifiers as well as for operator specific identifiers and related data to be consumed.
The following table illustrates the UDR Services.
Table 5.2.12.1-1: NF services provided by UDR
|
NF service |
Service Operations |
Operation Semantics |
Example Consumer(s) |
|
Data Management (DM) |
Query |
Request/Response |
UDM, PCF, NEF |
|
Create |
Request/Response |
NEF |
|
|
Delete |
Request/Response |
NEF |
|
|
Update |
Request/Response |
UDM, PCF, NEF |
|
|
Subscribe |
Subscribe/Notify |
UDM, PCF, NEF |
|
|
Unsubscribe |
UDM, PCF, NEF |
||
|
Notify |
UDM, PCF, NEF |
||
|
GroupIDmap |
Query |
Request/Response |
NRF, SCP |
The following table shows the Exposure data that may be stored in the UDR along with a time stamp using Data Management (DM) Service:
NOTE: When the data in Table 5.2.12.1-2 need to be monitored in real time, they should be monitored directly at the originating NF (e.g. registration state changes may be monitored via the Namf_EventExposure service) and not use the stored information from UDR if it is not the latest. It is expected that such dynamically changing information (e.g. UE reachability status) is used for statistical purpose and analytics.
Table 5.2.12.1-2: Exposure data stored in the UDR
|
Category |
Information |
Description |
Data key |
Data Sub key |
|
Access and mobility information |
UE location |
Gives the Location or the last known location of a UE (e.g. Tai, Cell Id… both 3GPP and non-3GPP access location) |
SUPI or GPSI |
|
|
UE time zone |
Current time zone for the UE |
SUPI or GPSI |
||
|
UE Access type |
3GPP access or non-3GPP access |
SUPI or GPSI |
||
|
UE RAT type |
Determined as defined in clause 5.3.2.3 of TS 23.501 [2]. The values are defined in TS 29.571 [70] |
SUPI or GPSI |
||
|
UE registration state |
Registered or Deregistered |
SUPI or GPSI |
||
|
UE connectivity state |
IDLE or CONNECTED |
SUPI or GPSI |
||
|
UE reachability status |
It indicates if the UE is reachable for sending either SMS or downlink data to the UE, which is detected when the UE transitions to CM-CONNECTED state or when the UE will become reachable for paging, e.g. Periodic Registration Update timer |
SUPI or GPSI |
||
|
UE SMS over NAS service status |
SMS over NAS supported or not in the UE |
SUPI or GPSI |
||
|
UE Roaming status |
It indicates UE’s current roaming status (the serving PLMN and/or whether the UE is in its HPLMN) |
SUPI or GPSI |
||
|
UE Current PLMN |
Current PLMN for the UE |
SUPI or GPSI |
||
|
Session management |
UE IP address |
UE IP address |
SUPI or GPSI |
PDU session ID or DNN |
|
information |
PDU session status |
Active / released |
SUPI or GPSI |
PDU session ID or DNN or UE IP address |
|
DNAI |
DNAI |
SUPI or GPSI |
PDU session ID or DNN or UE IP address |
|
|
N6 traffic routing information |
N6 traffic routing information |
SUPI or GPSI |
PDU session ID or DNN or UE IP address |
5.2.12.2 Nudr_DataManagement (DM) service
5.2.12.2.1 General
The operations defined for Nudr_DM service use following set of parameters defined in this clause:
– Data Set Identifier: uniquely identifies the requested set of data within the UDR (see clause 4.2.5).
– Data Subset Identifier: it uniquely identifies the data subset within each Data Set Identifier. As specified in the procedures in clause 4, e.g. subscription data can consist of subsets particularised for specific procedures like mobility, session, etc.
– Data Keys defined in Table 5.2.12.2.1-1
For Nudr_DM_Subscribe and Nudr_DM_Notify operations:
– The Target of Event Reporting is made up of a Data Key and possibly a Data Sub Key both defined in Table 5.2.12.2.1-1. When a Data Sub Key is defined in the table but not present in the Nudr_DM_Subscribe this means that all values of the Data Sub Key are targeted.
– The Data Set Identifier plus (if present) the (set of) Data Subset Identifier(s) corresponds to a (set of) Event ID(s) as defined in clause 4.15.1
An NF Service Consumer may include an indicator when it invokes Nudr_DM Query/Create/Update service operation to subscribe the changes of the data, to avoid a separate Nudr_DM_Subscribe service operation.
Depending on the use case, it is possible to use a Data Key and/or one or multiple Data sub keys to further identify the corresponding data, as defined in Table 5.2.12.2.1-1 below.
Table 5.2.12.2.1-1: Data keys
|
Data Set |
Data Subset |
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 |
PDU Session ID or DNN |
|
|
Subscription Data (see clause 5.2.3.3.1) |
SMS Management Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
SMS Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
|
Session Management Subscription data |
SUPI |
S-NSSAI |
|
|
DNN |
|||
|
Serving PLMN ID and optionally NID |
|||
|
Slice Selection Subscription data |
SUPI |
Serving PLMN ID and optionally NID |
|
|
Group Data (NOTE 5) |
Internal Group Identifier or External Group Identifier |
– |
|
|
Identifier translation |
GPSI |
||
|
SUPI |
Application Port ID, MTC Provider Information, AF Identifier |
||
|
Intersystem continuity Context |
SUPI |
DNN |
|
|
LCS privacy |
SUPI |
– |
|
|
LCS mobile origination |
SUPI |
– |
|
|
UE reachability |
SUPI |
– |
|
|
Group Identifier Translation |
Internal Group Identifier or External Group Identifier |
– |
|
|
UE context in SMSF data |
SUPI |
– |
|
|
V2X Subscription data |
SUPI |
– |
|
|
ProSe Subscription data |
SUPI |
– |
|
|
User consent |
SUPI |
Purpose |
|
|
ECS Address Configuration Information (See Table 4.15.6.3d-1) |
SUPI, Internal group identifier or external group identifier or any UE |
DNN, S-NSSAI |
|
|
MBS Subscription data |
SUPI |
– |
|
|
Shared data |
Shared Data ID |
– |
|
|
Application data |
Packet Flow Descriptions (PFDs) |
Application Identifier |
– |
|
AF traffic influence request information |
AF transaction internal ID |
||
|
(See clause 5.6.7 and clause 6.3.7.2 of TS 23.501 [2]) |
S-NSSAI and DNN and/or Internal Group Identifier or SUPI or "any UE" indication (NOTE 4) |
||
|
Background Data Transfer (NOTE 3) |
Internal Group Identifier or SUPI |
||
|
Service specific information (See clause 4.15.6.7) |
S-NSSAI and DNN or Internal Group Identifier or SUPI or "any UE" indication (NOTE 4) |
||
|
EAS Deployment Information (See clause 7.1 of TS 23.548 [74]) |
DNN and/or S-NSSAI |
Application Identifier and/or Internal Group Identifier |
|
|
AM influence information (See clause 4.15.6.9.3) |
AF transaction internal ID |
||
|
S-NSSAI and DNN and/or Internal Group Identifier or SUPI or "any UE" indication (NOTE 4) |
|||
|
Policy Data |
UE context policy control data (See clause 6.2.1.3 of TS 23.503 [20]) |
SUPI |
|
|
PDU Session policy control data |
SUPI |
S-NSSAI |
|
|
(See clause 6.2.1.3 of TS 23.503 [20]) |
DNN |
||
|
Policy Set Entry data (See clause 6.2.1.3 of TS 23.503 [20]) |
SUPI (for the UDR in HPLMN) |
||
|
PLMN ID (for the UDR in VPLMN) |
|||
|
Remaining allowed Usage data |
SUPI |
S-NSSAI |
|
|
(See clause 6.2.1.3 of TS 23.503 [20]) |
DNN |
||
|
Sponsored data connectivity profiles (See clause 6.2.1.6 of TS 23.503 [20]) |
Sponsor Identity |
||
|
Background Data Transfer data (See clause 6.2.1.6 of TS 23.503 [20]) |
Background Data Transfer Reference ID. (NOTE 2) |
||
|
None. (NOTE 1) |
|||
|
Network Slice Specific Control Data (See clause 6.2.1.3 of TS 23.503 [20]) |
S-NSSAI |
||
|
Operator Specific Data |
SUPI or GPSI |
||
|
Exposure Data |
Access and Mobility Information |
SUPI or GPSI |
PDU Session ID or |
|
(see clause 5.2.12.1) |
Session Management information |
SUPI or GPSI |
UE IP address or DNN |
|
NOTE 1: Retrieval of the stored Background Data Transfer References for all ASP identifiers in the UDR requires Data Subset but no Data Key or Data Subkey(s). NOTE 2: Update of a Background Data Transfer Reference in the UDR requires a Data key to refer to a Background Data Transfer Reference as input data. NOTE 3: The Background Data Transfer includes the Background Data Reference ID and the ASP Identifier that requests to apply the Background Data Reference ID to the UE(s). Furthermore, the Background Data Transfer includes the relevant information received from the AF as defined in clause 6.1.2.4 of TS 23.503 [20]. NOTE 4: When the Data Key targets "any UE", then the request to UDR applies on Application data that applies on all subscribers of the PLMN. For encoding, see TS 29.519 [82]. NOTE 5: Group Data includes 5G VN group configuration and any other data related to a group stored in the UDR. |
|||
The content of the UDR storage for (Data Set Id= Application Data, Data Subset Id = AF TrafficInfluence request information) is specified in clause 5.6.7, Table 5.6.7-1 of TS 23.501 [2]. This information is written by the NEF and read by the PCF(s). PCF(s) may also subscribe to changes onto this information.
5.2.12.2.2 Nudr_DM_Query service operation
Service operation name: Nudr_DM_Query.
Description: NF service consumer requests a set of data from UDR.
Inputs, Required: Data Set Identifier, Data Key(s).
Inputs, Optional: Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required: Requested data.
Outputs, Optional: None.
5.2.12.2.3 Nudr_DM_Create service operation
Service operation name: Nudr_DM_Create.
Description: NF service consumer intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR.
Inputs, Required: Data Set Identifier, Data Key(s).
Inputs, Optional: Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required: Result.
Outputs, Optional: None.
5.2.12.2.4 Nudr_DM_Delete service operation
Service operation name: Nudr_DM_Delete.
Description: NF service consumer intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record.
Inputs, Required: Data Set Identifier, Data Key(s).
Inputs, Optional: Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required: Result.
Outputs, Optional: None.
5.2.12.2.5 Nudr_DM_Update service operation
Service operation name: Nudr_DM_Update.
Description: NF service consumer intends to update stored data in the UDR.
Inputs, Required: Data Set Identifier, Data Key(s), Data.
Inputs, Optional: Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required: Result.
Outputs, Optional: None.
5.2.12.2.6 Nudr_DM_Subscribe service operation
Service operation name: Nudr_DM_Subscribe.
Description: NF service consumer performs the subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required: Data Set Identifier as defined in clause 5.2.12.2.1, Notification Target Address (+ Notification Correlation ID), Event Reporting Information defined in Table 4.15.1-1.
Inputs, Optional: Target of Event Reporting as defined in clause 5.2.12.2.1, Data Subset Identifier(s) as defined in clause 5.2.12.2.1, Data Key(s), Subscription Correlation ID (in the case of modification of the event subscription).
Outputs, Required: When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional: None.
5.2.12.2.7 Nudr_DM_Unsubscribe service operation
Service operation name: Nudr_DM_Unsubscribe
Description: NF service consumer performs the un-subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
5.2.12.2.8 Nudr_DM_Notify service operation
Service operation name: Nudr_DM_Notify.
Description: UDR notifies NF service consumer(s) about modification of data, when data in the UDR is added, modified or deleted and an NF needs to be informed about this, due to a previous subscription to notifications procedure or due to a local configuration policy in the UDR.
Inputs, Required: Notification Correlation Information, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, Updated Data.
Inputs, Optional: Data Subset Identifier as defined in clause 5.2.12.2.1.
Outputs, Required: Result.
Outputs, Optional: None.
5.2.12.3 Nudr_GroupIDmap service
5.2.12.3.1 General
The Nudr_GroupIDmap service allows an NF consumer to retrieve a NF group ID corresponding to a subscriber identifier.
5.2.12.3.2 Nudr_GroupIDmap_query service operation
Service Operation name: Nudr_GroupIDmap_query
Description: Provides towards the invoking NF the NF Group ID corresponding to the supplied subscriber identifier.
Inputs, Required:
– NF Type (e.g. HSS).
– Subscriber Identifier.
– Subscriber Identifier Type (at least one of {IMPI, IMPU, SUPI, GPSI}).
Inputs, Optional: None.
Outputs, Required: NF Group ID.
Outputs, Optional: None.