7 Usage of Nudr_DataRepository Service API for Structured Data for Exposure
29.5193GPP5G SystemRelease 18Stage 3TSUsage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure
7.1 Introduction
The following clauses specify the usage of Nudr_DataRepository service for exposure data. The principles specified in 3GPP TS 29.504 [6] are followed unless explicitly specified otherwise in the following clauses.
7.2 Resources
7.2.1 Overview
This clause specifies the resources for the usage of the Unified Data Repository service for Structured Data for Exposure.
7.2.2 Resource Structure
This clause describes the structure for the Resource URIs and the resources and methods used for the service.
Figure 7.2.2-1 depicts the resource URIs structure for the Nudr_DataRepository API for exposure data data.
Figure 7.2.2-1: Resource URI structure of the Nudr_DataRepository API for exposure data
Table 7.2.2-1 provides an overview of the resources and applicable HTTP methods.
Table 7.2.2-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method |
Description |
AccessAndMobilityData |
/exposure-data/{ueId}/ |
PUT |
Create and update the access and mobility exposure data for a UE |
PATCH |
Update the access and mobility exposure data for a UE. |
||
GET |
Retrieve the access and mobility exposure data for a UE |
||
DELETE |
Delete the access and mobility exposure data for a UE |
||
PduSessionManagementData |
/exposure-data/{ueId}/ |
PUT |
Create and update the session management data for a UE and for an individual PDU session |
GET |
Retrieve the session management data for a UE and for an individual PDU session |
||
DELETE |
Delete the session management data for a UE and for an individual PDU session |
||
ExposureDataSubscriptions |
/exposure-data/subs-to-notify |
POST |
Create a subscription to receive notifications on exposure data changes. |
IndividuaExposureDataSubscription |
/exposure-data/subs-to-notify/ |
PUT |
Modify a subscription to receive notifications on exposure data changes. |
DELETE |
Delete a subscription identified by {subId}. |
7.2.3 Resource: AccessAndMobilityData
7.2.3.1 Description
This resource represents the exposure data related to access and mobility.
7.2.3.2 Resource definition
Resource URI: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/{ueId}/access-and-mobility-data
This resource shall support the resource URI variables defined in table 7.2.3.2-1.
Table 7.2.3.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See 3GPP TS 29.504 [6] clause 6.1.1. |
ueId |
VarUeId |
Represents the SUPI or GPSI. Data type VarUeId is defined in 3GPP TS 29.571 [7]. |
7.2.3.3 Resource Standard Methods
7.2.3.3.1 PUT
This method shall support the URI query parameters specified in table 7.2.3.3.1-1.
Table 7.2.3.3.1-1: URI query parameters supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.3.3.1-2 and the response data structures and response codes specified in table 7.2.3.3.1-3.
Table 7.2.3.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
AccessAndMobilityData |
M |
1 |
Access and mobility data for the UE is created or updated. |
Table 7.2.3.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
AccessAndMobilityData |
M |
1 |
201 Created |
Successful case. The resource has been successfully created and a response body containing a representation of the access and mobility data shall be returned. |
AccessAndMobilityData |
M |
1 |
200 OK |
Successful case. The resource has been successfully updated and a response body containing a representation of the access and mobility data shall be returned. |
n/a |
204 No Content |
Successful case. The resource has been successfully updated and no additional content is to be sent in the response message. |
||
NOTE: The HTTP status code for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
Table 7.2.3.3.1-4: Headers supported by the 201 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
Contains the URI of the newly created resource, according to the structure: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/{ueId}/access-and-mobility-data |
7.2.3.3.2 GET
This method shall support the URI query parameters specified in table 7.2.3.3.2-1.
Table 7.2.3.3.2-1: URI query parameters supported by the GET method on this resource
Name |
Data type |
P |
Cardinality |
Description |
supp-feat |
SupportedFeatures |
O |
0..1 |
The features supported by the NF service consumer. See 3GPP TS 29.500 [4] clause 6.6.2 and 3GPP TS 29.571 [7]. |
This method shall support the request data structures specified in table 7.2.3.3.2-2 and the response data structures and response codes specified in table 7.2.3.3.2-3.
Table 7.2.3.3.2-2: Data structures supported by the GET Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 7.2.3.3.2-3: Data structures supported by the GET Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
AccessAndMobilityData |
M |
1 |
200 OK |
The response body contains the access and mobility data. |
NOTE: The HTTP status code for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.3.3.3 DELETE
This method shall support the URI query parameters specified in table 7.2.3.3.3-1.
Table 7.2.3.3.3-1: URI query parameters supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.3.3.3-2 and the response data structures and response codes specified in table 7.2.3.3.3-3.
Table 7.2.3.3.3-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 7.2.3.3.3-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Upon success, an empty response body shall be returned. |
||
NOTE: The HTTP status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.3.3.4 PATCH
This method shall support the URI query parameters specified in table 7.2.3.3.4-1.
Table 7.2.3.3.4-1: URI query parameters supported by the PATCH method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.3.3.4-2 and the response data structures and response codes specified in table 7.2.3.3.4-3.
Table 7.2.3.3.4-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
AccessAndMobilityData |
M |
1 |
Access and mobility data for the UE. |
Table 7.2.3.3.4-3: Data structures supported by the PATCH Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Upon successful modification there is no body in the response message. |
||
NOTE: The HTTP status code for the PATCH method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.4 Resource: PduSessionManagementData
7.2.4.1 Description
This resource represents the exposure data related to session and management data for a given subscriber and a given PDU session.
7.2.4.2 Resource definition
Resource URI: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/{ueId}/session-management-data/{pduSessionId}
This resource shall support the resource URI variables defined in table 7.2.4.2-1.
Table 7.2.4.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See 3GPP TS 29.504 [6] clause 6.1.1. |
ueId |
VarUeId |
Represents the SUPI or GPSI. Data type VarUeId is defined in 3GPP TS 29.571 [7]. |
pduSessionId |
PduSessionId |
Identifies an individual PDU session. Data type PduSessionId is defined in 3GPP TS 29.571 [7]. |
7.2.4.3 Resource Standard Methods
7.2.4.3.1 PUT
This method shall support the URI query parameters specified in table 7.2.4.3.1-1.
Table 7.2.4.3.1-1: URI query parameters supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.4.3.1-2 and the response data structures and response codes specified in table 7.2.4.3.1-3.
Table 7.2.4.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
PduSessionManagementData |
M |
1 |
Session management data for a UE and a PDU session is created or updated. |
Table 7.2.4.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response Codes |
Description |
PduSessionManagementData |
M |
1 |
201 Created |
Successful case. The resource has been successfully created and a response body containing a representation of the session management data shall be returned. |
PduSessionManagementData |
M |
1 |
200 OK |
Successful case. The resource has been successfully updated and a response body containing a representation of the session management data shall be returned. |
n/a |
204 No Content |
Successful case. The resource has been successfully updated and no additional content is to be sent in the response message. |
||
NOTE: The HTTP status code for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
Table 7.2.4.3.1-4: Headers supported by the 201 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
Contains the URI of the newly created resource, according to the structure: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/{ueId}/session-management-data/{pduSessionId} |
7.2.4.3.2 GET
This method shall support the URI query parameters specified in table 7.2.4.3.2-1.
Table 7.2.4.3.2-1: URI query parameters supported by the GET method on this resource
Name |
Data type |
P |
Cardinality |
Description |
ipv4-addr |
Ipv4Addr |
O |
0..1 |
UE IPv4 address. |
ipv6-prefix |
Ipv6Prefix |
O |
0..1 |
UE IPv6 prefix. |
dnn |
Dnn |
O |
0..1 |
Identifies a DNN. |
fields |
array(string) |
C |
1..N |
When the NF consumer only retrieves a subset of the resource, the "fields" query parameter shall be included. The "fields" query parameter contains the pointers of the attribute(s) to be retrieved. |
supp-feat |
SupportedFeatures |
O |
0..1 |
The features supported by the NF service consumer. See 3GPP TS 29.500 [4] clause 6.6.2 and 3GPP TS 29.571 [7]. |
This method shall support the request data structures specified in table 7.2.4.3.2-2 and the response data structures and response codes specified in table 7.2.4.3.2-3.
Table 7.2.4.3.2-2: Data structures supported by the GET Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 7.2.4.3.2-3: Data structures supported by the GET Response Body on this resource
Data type |
P |
Cardinality |
Response Codes |
Description |
PduSessionManagementData |
M |
1 |
200 OK |
The response body contains the session management data. |
NOTE: The HTTP status code for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.4.3.3 DELETE
This method shall support the URI query parameters specified in table 7.2.4.3.3-1.
Table 7.2.4.3.3-1: URI query parameters supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.4.3.3-2 and the response data structures and response codes specified in table 7.2.4.3.3-3.
Table 7.2.4.3.3-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 7.2.4.3.3-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Upon success, an empty response body shall be returned. |
||
NOTE: The HTTP status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.5 Resource: ExposureDataSubscriptions
7.2.5.1 Description
This resource is used to represent subscriptions to notifications of exposure data modifications.
7.2.5.2 Resource Definition
Resource URI: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/subs-to-notify
This resource shall support the resource URI variables defined in table 7.2.5.2-1.
Table 7.2.5.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See 3GPP TS 29.504 [6] clause 6.1.1. |
7.2.5.3 Resource Standard Methods
7.2.5.3.1 POST
This method shall support the URI query parameters specified in table 7.2.5.3.1-1.
Table 7.2.5.3.1-1: URI query parameters supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.5.3.1-2 and the response data structures and response codes specified in table 7.2.5.3.1-3.
Table 7.2.5.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ExposureDataSubscription |
M |
1 |
Identifies an individual subscription to notifications of exposure data modifications. |
Table 7.2.5.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ExposureDataSubscription |
M |
1 |
201 Created |
Upon success, a response body containing a representation of the Individual subscription resource shall be returned. The HTTP response shall include a "Location" HTTP header that contains the resource URI of the created resource. |
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
Table 7.2.5.3.1-4: Headers supported by the 201 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
Contains the URI of the newly created resource, according to the structure: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/subs-to-notify/{subId} |
7.2.6 Resource: IndividualExposureDataSubscription
7.2.6.1 Description
This resource represents an individual subscription to notifications of exposure data modifications.
7.2.6.2 Resource Definition
Resource URI: {apiRoot}/nudr-dr/<apiVersion>/exposure-data/subs-to-notify/{subId}
This resource shall support the resource URI variables defined in table 7.2.6.2-1.
Table 7.2.6.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See 3GPP TS 29.504 [6] clause 6.1.1. |
subId |
string |
Identifies an individual subscription to notifications. The value is allocated by the UDR during creation of the IndividualExposureDataSubscription resource. |
7.2.6.3 Resource Standard Methods
7.2.6.3.1 PUT
This method shall support the URI query parameters specified in table 7.2.6.3.1-1.
Table 7.2.6.3.1-1: URI query parameters supported by the PUT method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.6.3.1-2 and the response data structures and response codes specified in table 7.2.6.3.1-3.
Table 7.2.6.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
ExposureDataSubscription |
M |
1 |
Identifies an individual subscription to notifications of exposure data modifications. |
Table 7.2.6.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ExposureDataSubscription |
M |
1 |
200 OK |
The individual subscription resource was updated successfully and a body with the modified subscription to notifications about exposure data is returned. |
n/a |
204 No Content |
The individual subscription resource was successfully modified. |
||
NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.2.6.3.2 DELETE
This method shall support the URI query parameters specified in table 7.2.6.3.2-1.
Table 7.2.6.3.1-1: URI query parameters supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 7.2.6.3.2-2 and the response data structures and response codes specified in table 7.2.6.3.2-3.
Table 7.2.6.3.2-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
The request body shall be empty. |
Table 7.2.6.3.2-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Upon success, an empty response body shall be returned. |
||
NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
7.3 Data Model
7.3.1 General
This clause specifies the application data model supported by the API.
Table 7.3.1-1 specifies the data types defined for the Nudr_DataRepository for Exposure Data service based interface protocol.
Table 7.3.1-1: Nudr_DataRepository specific Data Types for Exposure Data
Data type |
Section defined |
Description |
Applicability |
AccessAndMobilityData |
7.3.2.2 |
||
ExposureDataChangeNotification |
7.3.2.5 |
Contains changed exposure data for one UE for which Notification was requested. |
|
ExposureDataSubscription |
7.3.2.4 |
Subscription to Notifications about Exposure Data. |
|
PduSessionManagementData |
7.3.2.3 |
||
PduSessionStatus |
7.3.3.3 |
Represents the state of the PDU session, i.e. active or released. |
Table 7.3.1-2 specifies data types re-used by the Nudr_DataRepository for Exposure Data service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nudr_DataRepository for Exposure Data service based interface.
Table 7.3.1-2: Nudr_DataRepository re-used Data Types for Exposure Data
Data type |
Reference |
Comments |
Applicability |
AccessType |
3GPP TS 29.571 [7] |
Identifies the access type, i.e. 3GPP access or Non-3GPP access. |
|
CmInfo |
3GPP TS 29.518 [10] |
Describes the connectivity management state of a UE. |
|
DateTime |
3GPP TS 29.571 [7] |
||
Dnai |
3GPP TS 29.571 [7] |
Identifies a Data network access identifier. |
|
Dnn |
3GPP TS 29.571 [7] |
Identifies a Data Network Name. (NOTE) |
|
Ipv4Addr |
3GPP TS 29.571 [7] |
The IPv4 Address. |
|
Ipv6Addr |
3GPP TS 29.571 [7] |
The Ipv6 Address. |
|
Ipv6Prefix |
3GPP TS 29.571 [7] |
The Ipv6 Address Prefix. |
|
PduSessionId |
3GPP TS 29.571 [7] |
PDU Session Identifier |
|
PduSessionType |
3GPP TS 29.571 [7] |
PDU Session type. |
|
PlmnId |
3GPP TS 29.571 [7] |
Identifies a PLMN. |
|
RatType |
3GPP TS 29.571 [7] |
Identifies a RAT type. |
|
RmInfo |
3GPP TS 29.518 [10] |
Describes the registration management state of a UE. |
|
RouteToLocation |
3GPP TS 29.571 [7] |
A traffic route to/from a DNAI. |
|
TimeZone |
3GPP TS 29.571 [7] |
Identifies a time zone. |
|
SmsSupport |
3GPP TS 29.518 [10] |
Indicates the supported SMS delivery of a UE. |
|
SupportedFeatures |
3GPP TS 29.571 [7] |
Used to negotiate the applicability of the optional features. |
|
UeReachability |
3GPP TS 29.518 [10] |
Describes the reachability of the UE. |
|
Uri |
3GPP TS 29.571 [7] |
||
UserLocation |
3GPP TS 29.571 [7] |
Identifies the user location. |
|
VarUeId |
3GPP TS 29.571 [7] |
String represents the SUPI or GPSI. |
|
NOTE: The UDR uses the DNN as received from the NF service consumer without applying any transformation. To successfully perform DNN matching, a DNN shall always be encoded either with the full DNN (e.g., because there are multiple Operator Identifiers for a Network Identifier) or the DNN Network Identifier only. |
7.3.2 Structured data types
7.3.2.1 Introduction
This clause defines the structures to be used in resource representations.
7.3.2.2 Type AccessAndMobilityData
Table 7.3.2.2-1: Definition of type AccessAndMobilityData
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
location |
UserLocation |
O |
0..1 |
Current location for the UE, which can be a combination of E-UTRA, NR and non-3GPP access location. |
|
locationTs |
DateTime |
O |
0..1 |
Indicates when the location was last updated. |
|
timeZone |
TimeZone |
O |
0..1 |
Current time zone for the UE. |
|
timeZoneTs |
DateTime |
O |
0..1 |
Indicates when the timeZone was last updated. |
|
accessType |
AccessType |
O |
0..1 |
Current access type for the UE (3GPP access or non-3GPP access). |
|
accessTypeTs |
DateTime |
O |
0..1 |
Indicates when the accessType was last updated. |
|
regStates |
array(RmInfo) |
O |
1..N |
Describes the registration management state of the UE. |
|
regStatesTs |
DateTime |
O |
0..1 |
Indicates when the regStates were last updated. |
|
connStates |
array(CmInfo) |
O |
1..N |
Describes the connectivity management state of the UE. |
|
connStatesTs |
DateTime |
O |
0..1 |
Indicates when the connStates were last updated. |
|
reachabilityStatus |
UeReachability |
O |
0..1 |
Describes the reachability of the UE. |
|
reachabilityStatusTs |
DateTime |
O |
0..1 |
Indicates when the reachabilityStatus was last updated. |
|
smsOverNasStatus |
SmsSupport |
O |
0..1 |
Indicates the supported SMS delivery of the UE. |
|
smsOverNasStatusTs |
DateTime |
O |
0..1 |
Indicates when thesmsOverNasStatus was last updated. |
|
roamingStatus |
boolean |
O |
0..1 |
True: The serving PLMN of the UE is different from the HPLMN of the UE; |
|
roamingStatusTs |
DateTime |
O |
0..1 |
Indicates when the roamingStatus was last updated. |
|
currentPlmn |
PlmnId |
O |
0..1 |
The identity of the PLMN serving the UE. |
|
currentPlmnTs |
DateTime |
O |
0..1 |
Indicates when the currentPlmn was last updated. |
|
ratTypes |
array(RatType) |
O |
1..N |
RAT type(s) |
|
ratTypesTs |
DateTime |
O |
0..1 |
Indicates when the ratTypes was last updated. |
|
suppFeat |
SupportedFeatures |
C |
0..1 |
This IE represents a list of Supported features used as described in clause 7.5. Shall be present in the HTTP PUT request/response; or in the HTTP GET response if the "supp-feat" attribute query parameter is included in the HTTP GET request. (NOTE) |
|
resetIds |
array(string) |
O |
1..N |
This IE uniquely identifies a part of temporary data in UDR that contains the created resource. This attribute may be provided in the response of successful resource creation. |
|
NOTE: In the HTTP request, it represents the set of features supported by the NF service consumer. In the HTTP response, it represents the set of features supported by both the NF service consumer and the UDR. |
7.3.2.3 Type PduSessionManagementData
Table 7.3.2.3-1: Definition of type PduSessionManagementData
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
pduSessionStatus |
PduSessionStatus |
O |
0..1 |
Status of the PDU session. |
|
pduSessionStatusTs |
DateTime |
O |
0..1 |
Indicates when the pduSessionStatus was last updated. |
|
dnai |
Dnai |
O |
0..1 |
DNAI |
|
dnaiTs |
DateTime |
O |
0..1 |
Indicates when the dnai was last updated. |
|
n6TrafficRoutingInfo |
array(RouteToLocation) |
O |
1..N |
N6 traffic routing information. |
|
n6TrafficRoutingInfoTs |
DateTime |
O |
0..1 |
Indicates when the n6TrafficRoutingInfo was last updated. |
|
ipv4Addr |
Ipv4Addr |
O |
0..1 |
UE IPv4 address. |
|
ipv6Prefix |
array(Ipv6Prefix) |
O |
1..N |
UE IPv6 prefix. |
|
ipv6Addrs |
array(Ipv6Addr) |
O |
1..N |
IPv6 addresses. |
|
pduSessType |
PduSessionType |
O |
0..1 |
PDU session type. |
|
ipAddrTs |
DateTime |
O |
0..1 |
Indicates when the ipv4Addr and Ipv6Prefix were last updated. |
|
dnn |
Dnn |
O |
0..1 |
DNN |
|
pduSessionId |
PduSessionId |
O |
0..1 |
The identifier of a PduSessionManagement resource. (NOTE 1). |
ResourceNotificationExposureDataFix |
suppFeat |
SupportedFeatures |
C |
0..1 |
This IE represents a list of Supported features used as described in clause 7.5. Shall be present in the HTTP PUT request/response; or in the HTTP GET response if the "supp-feat" attribute query parameter is included in the HTTP GET request. (NOTE 2) |
|
resetIds |
array(string) |
O |
1..N |
This IE uniquely identifies a part of temporary data in UDR that contains the created resource. This attribute may be provided in the response of successful resource creation. |
|
NOTE 1: The "pduSessionId" attribute shall be present when the ResourceNotificationExposureDataFix is supported. NOTE 2: In the HTTP request, it represents the set of features supported by the NF service consumer. In the HTTP response, it represents the set of features supported by both the NF service consumer and the UDR. |
7.3.2.4 Type ExposureDataSubscription
Table 7.3.2.4-1: Definition of type ExposureDataSubscription
Attribute name |
Data type |
P |
Cardinality |
Description |
notificationUri |
Uri |
M |
1 |
URI provided by the NF service consumer indicating where to receive to subscribed notifications from the UDR. |
monitoredResourceUris |
array(Uri) |
M |
1..N |
A set of URIs that identify the resources for which a modification triggers a notification. |
expiry |
DateTime |
C |
0..1 |
This IE shall be included in a subscription response if, based on operator policy and taking into account the expiry time included in the request, the UDR needs to include an expiry time. This IE may be included in a subscription request. When present, this IE shall represent the time after which the subscription becomes invalid. The absence of this attribute in the subscription response means the subscription to be valid without an expiry time. |
supportedFeatures |
SupportedFeatures |
C |
0..1 |
Used to negotiate the applicability of the optional features. This attribute shall be provided in the POST request and in the response of successful resource creation. |
resetIds |
array(string) |
O |
1..N |
This IE uniquely identifies a part of temporary data in UDR that contains the created resource. This attribute may be provided in the response of successful resource creation. |
7.3.2.5 Type ExposureDataChangeNotification
Table 7.3.2.5-1: Definition of type ExposureDataChangeNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
ueId |
VarUeId |
O |
0..1 |
User identity of modified data. |
|
accessAndMobilityData |
AccessAndMobilityData |
O |
0..1 |
Access and Mobility Data for the UE. |
|
pduSessionManagementData |
array(PduSessionManagementData) |
O |
1..N |
PDU Session Management Data for one or several PDU sessions of the UE. |
|
delResources |
array(Uri) |
O |
1..N |
The resources, as defined in table 7.2.2-1, if removed from UDR and notification on resource data change was requested. It may be present when the ResourceNotificationExposureDataFix is supported (NOTE). |
|
NOTE: When the "delResources" attribute is present, the attributes that correspond with the values included in the "delResources" attribute shall be omitted. I.e., when the "delResources" attribute includes the value "../{ueId}/access-and-mobility-data" the attribute "accessAndMobilityData" shall be omitted, and when the "delResources" attribute includes all the existing "../{ueId}/session-management-data/{pduSessionId}" resource URIs, the attribute "pduSessionManagementData" shall be omitted. |
7.3.3 Simple data types and enumerations
7.3.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
7.3.3.2 Simple data types
The simple data types defined in table 7.3.3.2-1 shall be supported.
Table 7.3.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
7.3.3.3 Enumeration: PduSessionStatus
Table 7.3.3.3-1: Enumeration PduSessionStatus
Enumeration value |
Description |
Applicability |
"ACTIVE" |
The PDU session is active. |
|
"RELEASED" |
The PDU session is released. |
7.4 Error handling
7.4.1 General
For the Nudr_DataRepository service API for Exposure Data, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].
In addition, the requirements in the following clauses are applicable for the Nudr_DataRepository service API for Exposure Data.
7.4.2 Protocol Errors
No specific procedures for the Nudr_DataRepository service API for Exposure Data are specified.
7.4.3 Application Errors
The application errors defined for the Nudr_DataRepository service API for Exposure Data are listed in table 7.4.3-1.
Table 7.4.3-1: Application errors
Application Error |
HTTP status code |
Description |
The application error handling shall follow 3GPP TS 29.504 [6] clause 6.1.6 unless explicitly specified in this document.
7.5 Feature negotiation
The optional features in table 6.1.8-1 of 3GPP TS 29.504 [6] are defined for the Nudr_DataRepository API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
7.6 Notifications
7.6.1 General
Notifications shall comply with clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5].
This clause describes the resources to provide Notification to NF service consumers which have subscribed to be notified when exposure data is changed.
Table 7.6.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
Exposure Data Change Notification |
{notificationUri} |
POST |
Exposure Data Change Notification |
7.6.2 Exposure Data Change Notification
The POST method shall be used for Data Change Notifications and the URI shall be as provided during the subscription procedure.
Callback URI: {notificationUri}
Support of URI query parameters is specified in table 7.6.2-1.
Table 7.6.2-1: URI query parameters supported by the POST method
Name |
Data type |
P |
Cardinality |
Description |
n/a |
Support of request data structures is specified in table 7.6.2-2 and of response data structures and response codes is specified in table 7.6.2-3.
Table 7.6.2-2: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
array(ExposureDataChangeNotification) |
M |
1..N |
Each element in the array provides the changed exposure data for one user. |
Table 7.6.2-3: Data structures supported by the POST Response Body
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Upon success, an empty response body shall be returned. |
||
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |
Annex A (normative):
OpenAPI specification