6 API Definitions
29.5633GPP5G SystemHome Subscriber Server (HSS) services for interworking with Unified Data Management (UDM)Release 18Stage 3TS
6.1 Nhss_UEAuthentication Service API
6.1.1 Introduction
The Nhss_UEAuthentication service shall use the Nhss_UEAuthentication API.
The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
– The <apiName> shall be "nhss-ueau".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.
6.1.2 Usage of HTTP
6.1.2.1 General
HTTP/2, as defined in IETF RFC 7540 [9], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
HTTP messages and bodies for the Nhss_UEAuthentication service shall comply with the OpenAPI [10] specification contained in Annex A.
6.1.2.2 HTTP standard headers
6.1.2.2.1 General
The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
6.1.2.2.2 Content type
The following content types shall be supported:
– JSON, as defined in IETF RFC 8259 [11], signalled by the content type "application/json".
– The Problem Details JSON Object (IETF RFC 7807 [12] signalled by the content type "application/problem+json".
6.1.2.3 HTTP custom headers
6.1.2.3.1 General
In this release of the specification, no specific custom headers are defined for the Nhss_UEAuthentication service.
For 3GPP specific HTTP custom headers used across all service based interfaces, see clause 5.2.3 of 3GPP TS 29.500 [4].
6.1.3 Resources
6.1.3.1 Overview
Figure 6.1.3.1-1: Resource URI structure of the nhss-ueau API
Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.1.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
n/a |
generate-av |
generate-av (POST) |
Generate Authentication Vector |
6.1.4 Custom Operations without associated resources
6.1.4.1 Overview
Table 6.1.4.1-1: Custom operations without associated resources
Custom operation URI |
Mapped HTTP method |
Description |
{apiRoot}/nhss-ueau/<apiVersion>/generate-av |
POST |
The HSS calculates a fresh Authentication Vector taking into account the received information (imsi, serving network name, authentication method) |
6.1.4.2 Operation: Generate AV
6.1.4.2.1 Description
This custom operation is used by the NF service consumer (UDM) to request calculation of an authentication vector for the provided imsi.
6.1.4.2.2 Operation Definition
This operation shall support the response data structures and response codes specified in tables 6.1.4.2.2-1 and 6.1.4.2.2-2.
Table 6.1.4.2.2-1: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
AvGenerationRequest |
M |
1 |
Contains input parameters for Authentication Vector calculation |
Table 6.1.4.2.2-2: Data structures supported by the POST Response Body
Data type |
P |
Cardinality |
Response codes |
Description |
AvGenerationResponse |
M |
1 |
200 OK |
Upon success, a response body containing the generated authentication vector shall be returned |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
403 Forbidden |
The "cause" attribute may be used to indicate one of the following application errors: – AUTHENTICATION_REJECTED |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND |
Table 6.1.4.2.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.1.4.2.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.1.5 Notifications
In this release of this specification, no notifications are defined for the Nhss_UEAuthentication Service.
6.1.6 Data Model
6.1.6.1 General
This clause specifies the application data model supported by the API.
Table 6.1.6.1-1 specifies the data types defined for the Nhss service based interface protocol.
Table 6.1.6.1-1: Nhss specific Data Types
Data type |
Clause defined |
Description |
Applicability |
AvGenerationRequest |
6.1.6.2.2 |
Contains imsi, authentication method, serving network name, resynchronization info |
|
AvGenerationResponse |
6.1.6.2.3 |
Contains the calculated Authentication Vector |
Table 6.1.6.1-2 specifies data types re-used by the Nhss 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 Nhss service based interface.
Table 6.1.6.1-2: Nhss re-used Data Types
Data type |
Reference |
Comments |
Applicability |
AuthType |
3GPP TS 29.503 [13] |
||
ServingNetworkName |
3GPP TS 29.503 [13] |
||
ResynchronizationInfo |
3GPP TS 29.503 [13] |
||
AvEapAkaPrime |
3GPP TS 29.503 [13] |
||
Av5GHeAka |
3GPP TS 29.503 [13] |
||
ProblemDetails |
3GPP TS 29.571 [7] |
Response body of error response messages. |
|
RedirectResponse |
3GPP TS 29.571 [7] |
Response body of redirect response messages. |
6.1.6.2 Structured data types
6.1.6.2.1 Introduction
This clause defines the structures to be used in resource representations.
6.1.6.2.2 Type: AvGenerationRequest
Table 6.1.6.2.2-1: Definition of type AvGenerationRequest
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
imsi |
string |
M |
1 |
pattern: "[0-9]{5,15}" |
|
authType |
AuthType |
M |
1 |
Indicates the authentication method; "EAP_AKA_PRIME" or "5G_AKA" |
|
servingNetworkName |
ServingNetworkName |
M |
1 |
||
resynchronizationInfo |
ResynchronizationInfo |
O |
0..1 |
6.1.6.2.3 Type: AvGenerationResponse
Table 6.1.6.2.3-1: Definition of type AvGenerationResponse
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
avEapAkaPrime |
AvEapAkaPrime |
C |
0..1 |
shall be present if av5GHeAka is absent, otherwise shall be absent. |
|
av5GHeAka |
Av5GHeAka |
C |
0..1 |
shall be present if avEapAkaPrime is absent, otherwise shall be absent. |
6.1.6.3 Simple data types and enumerations
6.1.6.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.1.6.3.2 Simple data types
The simple data types defined in table 6.1.6.3.2-1 shall be supported.
Table 6.1.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
6.1.7 Error Handling
6.1.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.1.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.1.7.3 Application Errors
The application errors defined for the Nhss_UEAuthentication service are listed in table 6.1.7.3-1.
Table 6.1.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
AUTHENTICATION_REJECTED |
403 Forbidden |
The user cannot be authenticated |
USER_NOT_FOUND |
404 Not Found |
The user does not exist in the HPLMN |
6.1.8 Feature negotiation
The optional features in table 6.1.8-1 are defined for the Nhss_UEAuthentication API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.1.8-1: Supported Features
Feature number |
Feature Name |
Description |
6.2 Nhss_SubscriberDataManagement Service API
6.2.1 API URI
The Nhss_SubscriberDataManagement service shall use the Nhss_SubscriberDataManagement API.
The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
– The <apiName> shall be "nhss-sdm".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.2.3.
6.2.2 Usage of HTTP
6.2.2.1 General
HTTP/2, as defined in IETF RFC 7540 [9], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
HTTP messages and bodies for the Nhss_SubscriberDataManagement service shall comply with the OpenAPI [10] specification contained in Annex A.
6.2.2.2 HTTP standard headers
6.2.2.2.1 General
The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
6.2.2.2.2 Content type
The following content types shall be supported:
– JSON, as defined in IETF RFC 8259 [11], signalled by the content type "application/json".
– The Problem Details JSON Object (IETF RFC 7807 [12] signalled by the content type "application/problem+json".
6.2.2.3 HTTP custom headers
6.2.2.3.1 General
In this release of the specification, no specific custom headers are defined for the Nhss_SubscriberDataManagement service.
For 3GPP specific HTTP custom headers used across all service-based interfaces, see clause 5.2.3 of 3GPP TS 29.500 [4].
6.2.3 Resources
6.2.3.1 Overview
Figure 6.2.3.1-1: Resource URI structure of the nhss-sdm API
Table 6.2.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.2.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
UeContextInPgwData |
/{ueId}/ue-context-in-pgw-data |
GET |
Retrieve the UE’s Context in PGW Data |
Subscriptions (Collection) |
/{ueId}/subscriptions |
POST |
Create a subscription |
Individual Subscription (Document) |
/{ueId}/subscriptions/{subscriptionId} |
DELETE |
Delete the subscription identified by {subscriptionId}, i.e. unsubscribe |
PATCH |
Modify the subscription identified by {subscriptionId} |
6.2.3.2 Resource: UeContextInPgwData
6.2.3.2.1 Description
This resource represents the allocated PGWs for the UE.
6.2.3.2.2 Resource Definition
Resource URI: {apiRoot}/nhss-sdm/<apiVersion>/{ueId}/ue-context-in-pgw-data
This resource shall support the resource URI variables defined in table 6.2.3.2.2-1.
Table 6.2.3.2.2-1: Resource URI variables for this resource
Name |
Definition |
apiRoot |
See clause 6.2.1 |
apiVersion |
See clause 6.2.1 |
ueId |
Represents the UE identifier with type IMSI. pattern: "^(imsi-[0-9]{5,15}|.+)$" |
6.2.3.2.3 Resource Standard Methods
6.2.3.2.3.1 GET
This method shall support the URI query parameters specified in table 6.2.3.2.3.1-1.
Table 6.2.3.2.3.3-1: URI query parameters supported by the GET method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 6.2.3.2.3.1-2 and the response data structures and response codes specified in table 6.2.3.2.3.1-3.
Table 6.2.3.2.3.1-2: Data structures supported by the GET Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.2.3.2.3.1-3: Data structures supported by the GET Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
UeContextInPgwData |
M |
1 |
200 OK |
A response body containing the UeContextInPgwData shall be returned. |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – DATA_NOT_FOUND |
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.2.3.2.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.2.3.2.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.2.3.3 Resource: Subscriptions
6.2.3.3.1 Description
This resource is used to represent subscriptions to notifications.
6.2.3.3.2 Resource Definition
Resource URI: {apiRoot}/nhss-sdm/<apiVersion>/{ueId}/subscriptions
This resource shall support the resource URI variables defined in table 6.2.3.3.2-1.
Table 6.2.3.3.2-1: Resource URI variables for this resource
Name |
Definition |
apiRoot |
See clause 6.1.1 |
apiVersion |
See clause 6.1.1 |
ueId |
Represents the IMSI of the subscriber. |
6.2.3.3.3 Resource Standard Methods
6.2.3.3.3.1 POST
This method shall support the URI query parameters specified in table 6.2.3.3.3.1-1.
Table 6.2.3.3.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 6.2.3.3.3.1-2 and the response data structures and response codes specified in table 6.2.3.3.3.1-3.
Table 6.2.3.3.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
SubscriptionData |
M |
1 |
The subscription that is to be created. |
Table 6.2.3.3.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
SubscriptionData |
M |
1 |
201 Created |
Upon success, a response body containing a representation of the created Individual subscription resource shall be returned. The HTTP response shall include a "Location" HTTP header that contains the resource URI of the created resource. |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND |
ProblemDetails |
O |
0..1 |
501 Not Implemented |
The "cause" attribute may be used to indicate one of the following application errors: – UNSUPPORTED_RESOURCE_URI This response shall not be cached. |
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.2.3.3.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.2.3.3.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.2.3.4 Resource: Individual subscription
6.2.3.4.1 Description
This resource is used to represent an individual subscription to notifications.
6.2.3.4.2 Resource Definition
Resource URI: {apiRoot}/nhss-sdm/<apiVersion>/{ueId}/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.2.3.4.2-1.
Table 6.2.3.4.2-1: Resource URI variables for this resource
Name |
Definition |
apiRoot |
See clause 6.1.1 |
apiVersion |
See clause 6.1.1 |
ueId |
Represents the IMSI of the subscriber |
subscriptionId |
The subscriptionId identifies an individual subscription to notifications. |
6.2.3.4.3 Resource Standard Methods
6.2.3.4.3.1 DELETE
This method shall support the URI query parameters specified in table 6.2.3.4.3.1-1.
Table 6.2.3.4.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 6.2.3.4.3.1-2 and the response data structures and response codes specified in table 6.2.3.4.3.1-3.
Table 6.2.3.4.3.1-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 6.2.3.4.3.1-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. |
|||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
|
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
|
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – SUBSCRIPTION_NOT_FOUND (see 3GPP TS 29.500 [4] table 5.2.7.2-1) |
|
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.2.3.4.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.2.3.4.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.2.3.4.3.2 PATCH
This method shall support the URI query parameters specified in table 6.2.3.4.3.2-1.
Table 6.2.3.4.3.2-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 6.2.3.4.3.2-2 and the response data structures and response codes specified in table 6.2.3.4.3.2-3.
Table 6.2.3.4.3.2-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
array(PatchItem) |
M |
1 |
It contains the list of changes to be made to the resource representing the individual subscription, according to the JSON PATCH format specified in IETF RFC 6902 [13]. |
Table 6.2.3.4.3.2-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 success, a response with no content is returned. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – SUBSCRIPTION_NOT_FOUND (see 3GPP TS 29.500 [4] table 5.2.7.2-1) |
ProblemDetails |
O |
0..1 |
403 Forbidden |
One or more attributes are not allowed to be modified. The "cause" attribute may be used to indicate one of the following application errors: – MODIFICATION_NOT_ALLOWED (see 3GPP TS 29.500 [4] table 5.2.7.2-1) |
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.2.3.4.3.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.2.3.4.3.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.2.4 Custom Operations without associated resources
In this release of this specification, no custom operations without associated resources are defined for the Nhss_SubscriberDataManagement Service.
6.2.5 Notifications
6.2.5.1 General
This clause specifies the use of notifications and corresponding protocol details.
6.2.5.2 Data Change Notification
The POST method shall be used for Data Change Notifications and the URI shall be as provided during the subscription procedure.
Resource URI: {callbackReference}
Support of URI query parameters is specified in table 6.2.5.2-1.
Table 6.2.5.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 6.2.5.2-2 and of response data structures and response codes is specified in table 6.2.5.2-3.
Table 6.2.5.2-2: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
ModificationNotification |
M |
1 |
Table 6.2.5.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. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the notification endpoint of the subscribing NF Service Consumer. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the notification endpoint of the subscribing NF Service Consumer. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – CONTEXT_NOT_FOUND See table 6.2.7.3-1 for the description of this error. |
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.2.5.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.2.5.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.2.6 Data Model
6.2.6.1 General
This clause specifies the application data model supported by the API.
Table 6.2.6.1-1 specifies the data types defined for the Nhss_SubscriberDataManagement service API.
Table 6.2.6.1-1: Nhss_SubscriberDataManagement specific Data Types
Data type |
Clause defined |
Description |
UeContextInPgwData |
6.2.6.2.2 |
|
SubscriptionData |
6.2.6.2.3 |
Subscription Data |
SubscriptionDataSets |
6.2.6.2.4 |
UE Subscription Data Sets |
Table 6.2.6.1-2 specifies data types re-used by the Nhss_SubscriberDataManagement service API from other APIs, including a reference and when needed, a short description of their use within the Nhss_SubscriberDataManagement service API.
Table 6.2.6.1-2: Nhss_SubscriberDataManagement re-used Data Types
Data type |
Reference |
Comments |
PgwInfo |
3GPP TS 29.503 [13] |
|
ModificationNotification |
3GPP TS 29.503 [13] |
|
NfInstanceId |
3GPP TS 29.571 [7] |
Network Function Instance Identifier |
Uri |
3GPP TS 29.571 [7] |
Uniform Resource Identifier |
DateTime |
3GPP TS 29.571 [7] |
|
ProblemDetails |
3GPP TS 29.571 [7] |
Response body of error response messages. |
RedirectResponse |
3GPP TS 29.571 [7] |
Response body of redirect response messages. |
Fqdn |
3GPP TS 29.571 [7] |
Fully Qualified Domain Name |
6.2.6.2 Structured data types
6.2.6.2.1 Introduction
This clause defines the data structures to be used in resource representations.
6.2.6.2.2 Type: UeContextInPgwData
Table 6.2.6.2.2-1: Definition of type UeContextInPgwData
Attribute name |
Data type |
P |
Cardinality |
Description |
pgwInfo |
array(PgwInfo) |
O |
1..N |
Information about the APNs and PGW-C+SMF FQDNs used in interworking with UDM |
emergencyFqdn |
Fqdn |
O |
0..1 |
PGW-C+SMF FQDN for emergency session |
emergencyPlmnId |
PlmnId |
O |
0..1 |
PLMN where the PGW-C+SMF for emergency session is located |
emergencyIpAddr |
IpAddress |
O |
0..1 |
IP address of the PGW-C+SMF for emergency session |
emergencyRegistrationTime |
DateTime |
O |
0..1 |
Time of PGW-C+SMF for emergency session Registration. |
Note: At least one of pgwInfo and emergencyFqdn/emergencyIPAddr shall be present. The format of PGW-C+SMF FQDN is specified in clause 5.12.3.2, 3GPP TS 29.303 [16]. |
6.2.6.2.3 Type: SubscriptionData
Table 6.2.6.2.3-1: Definition of type SubscriptionData
Attribute name |
Data type |
P |
Cardinality |
Description |
nfInstanceId |
NfInstanceId |
M |
1 |
Identity of the NF Instance creating the subscription. |
callbackReference |
Uri |
M |
1 |
URI provided by the NF service consumer to receive notifications |
monitoredResourceUris |
array(Uri) |
M |
1..N |
A set of URIs that identify the resources for which a change triggers a notification. The URI shall take the form of either an absolute URI or an absolute-path reference as defined in IETF RFC 3986 [31]. See NOTE 1. |
expires |
DateTime |
O |
0..1 |
If present in a POST request, it indicates the point in time at which the subscription expires. Within a POST request the proposed expiry time is conveyed whereas in a POST response or PATCH response the confirmed expiry time is returned. |
immediateReport |
boolean |
O |
0..1 |
This IE indicates whether immediate report is needed or not. When present, this IE shall be set as following: – true: immediate report is required – false (default) immediate report is not required |
report |
SubscriptionDataSets |
C |
0..1 |
This IE shall be present in Subscribe response, if the immediateReport attribute is set to "true" in Subscribe request. When present, this IE shall contain the representation of subscription data sets that to be monitored, i.e. listed in monitoredResourceUris attribute. |
NOTE 1: The HSS should handle only the relative-path part (apiSpecificResourceUriPart, see 3GPP TS 29.501 [5] clause 4.4.1) and ignore possible inconsistencies (caused by e.g. an SCP) in the base URI part. |
6.2.6.2.4 Type: SubscriptionDataSets
Table 6.2.6.2.4-1: Definition of type SusbcriptionDataSets
Attribute name |
Data type |
P |
Cardinality |
Description |
ueContextInPgwData |
UeContextInPgwData |
O |
0..1 |
UE Context in PGW Data |
6.2.6.3 Simple data types and enumerations
6.2.6.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.2.6.3.2 Simple data types
The simple data types defined in table 6.2.6.3.2-1 shall be supported.
Table 6.2.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
6.2.7 Error Handling
6.2.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.2.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.2.7.3 Application Errors
The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [4] may also be used for the Nhss_SubscriberDataManagement service. The following application errors listed in Table 6.2.7.3-1 are specific for the Nhss_SubscriberDataManagement service.
Table 6.2.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
USER_NOT_FOUND |
404 Not Found |
The user does not exist. |
DATA_NOT_FOUND |
404 Not Found |
The requested data is not found/does not exist. |
CONTEXT_NOT_FOUND |
404 Not Found |
It is used during the modification of an existing subscription when no corresponding context exists. |
6.2.8 Feature Negotiation
The optional features in table 6.2.8-1 are defined for the Nhss_SubscriberDataManagement API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.2.8-1: Supported Features
Feature number |
Feature Name |
Description |
6.3 Nhss_UEContextManagement Service API
6.3.1 Introduction
The Nhss_UEContextManagement service shall use the Nhss_UEContextManagement API.
The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
– The <apiName> shall be "nhss-uecm".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.
6.3.2 Usage of HTTP
6.3.2.1 General
HTTP/2, as defined in IETF RFC 7540 [9], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
HTTP messages and bodies for the Nhss_UEContextManagement service shall comply with the OpenAPI [10] specification contained in Annex A.
6.3.2.2 HTTP standard headers
6.3.2.2.1 General
The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
6.3.2.2.2 Content type
The following content types shall be supported:
– JSON, as defined in IETF RFC 8259 [11], signalled by the content type "application/json".
– The Problem Details JSON Object (IETF RFC 7807 [12] signalled by the content type "application/problem+json".
6.3.2.3 HTTP custom headers
6.3.2.3.1 General
In this release of the specification, no specific custom headers are defined for the Nhss_UEContextManagement service.
For 3GPP specific HTTP custom headers used across all service-based interfaces, see clause 5.2.3 of 3GPP TS 29.500 [4].
6.3.3 Resources
6.3.3.1 Overview
Figure 6.3.3.1-1: Resource URI structure of the nhss-uecm API
Table 6.3.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.3.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
n/a |
deregister-sn |
deregister-sn (POST) |
Requesting MME/SGSN deregistration |
n/a |
imei-update |
imei-update (POST) |
Requests the update of the IMEI of the UE stored in HSS |
n/a |
roaming-status-update |
roaming-status-update (POST) |
Requests the update of the roaming status of the UE stored in HSS |
6.3.4 Custom Operations without associated resources
6.3.4.1 Overview
Table 6.3.4.1-1: Custom operations without associated resources
Custom operation URI |
Mapped HTTP method |
Description |
{apiRoot}/nhss-uecm/<apiVersion>/deregister-sn |
POST |
Requesting MME/SGSN deregistration. |
6.3.4.2 Operation: deregister-sn
6.3.4.2.1 Description
This custom operation is used by the NF service consumer (UDM) to request MME/SGSN deregistration.
6.3.4.2.2 Operation Definition
This operation shall support the data structures and response codes specified in tables 6.3.4.2.2-1 and 6.3.4.2.2-2.
Table 6.3.4.2.2-1: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
DeregistrationRequest |
M |
1 |
Table 6.3.4.2.2-2: 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. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND |
Table 6.3.4.2.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.3.4.2.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.3.4.3 Operation: imei-update
6.3.4.3.1 Description
This custom operation is used by the NF service consumer (UDM) to request the update of the IMEI of the UE.
6.3.4.3.2 Operation Definition
This operation shall support the data structures and response codes specified in tables 6.3.4.3.2-1 and 6.3.4.3.2-2.
Table 6.3.4.3.2-1: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
ImeiUpdateInfo |
M |
1 |
Table 6.3.4.3.2-2: Data structures supported by the POST Response Body
Data type |
P |
Cardinality |
Response codes |
Description |
ImeiUpdateResponse |
M |
1 |
200 OK |
Upon success, a response body containing the IMEI(SV) stored previously in HSS shall be returned. |
n/a |
204 No Content |
Upon success, if the HSS does not have any IMEI(SV) values stored for the UE, an empty response body shall be returned. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – CONTEXT_NOT_FOUND |
Table 6.3.4.3.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.3.4.3.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.3.4.4 Operation: roaming-status-update
6.3.4.4.1 Description
This custom operation is used by the NF service consumer (UDM) to request the update of the roaming status of the UE.
6.3.4.4.2 Operation Definition
This operation shall support the data structures and response codes specified in tables 6.3.4.4.2-1 and 6.3.4.4.2-2.
Table 6.3.4.4.2-1: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
RoamingStatusUpdateInfo |
M |
1 |
Table 6.3.4.4.2-2: 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. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – CONTEXT_NOT_FOUND |
Table 6.3.4.4.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.3.4.4.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.3.5 Notifications
In this release of this specification, no notifications are defined for the Nhss_UEContextManagement Service.
6.3.6 Data Model
6.3.6.1 General
This clause specifies the application data model supported by the API.
Table 6.3.6.1-1 specifies the structured data types defined for the Nhss_UECM service API.
Table 6.3.6.1-1: Nhss_UECM specific Data Types
Data type |
Clause defined |
Description |
Applicability |
DeregistrationRequest |
6.3.6.2.2 |
Contains IMSI, deregistration reason |
|
ImeiUpdateInfo |
6.3.6.2.3 |
Contains IMSI, new IMEI(SV) |
|
ImeiUpdateResponse |
6.3.6.2.4 |
Contains the previous IMEI(SV) stored in HSS |
|
RoamingStatusUpdateInfo |
6.3.6.2.5 |
Contains PLMN-ID where the UE is located |
Table 6.3.6.1-2 specifies data types re-used by the Nhss_UECM service API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nhss_UECM service API.
Table 6.3.6.1-2: Nhss_UECM re-used Data Types
Data type |
Reference |
Comments |
Applicability |
Guami |
3GPP TS 29.571 [7] |
||
ProblemDetails |
3GPP TS 29.571 [7] |
Response body of error response messages. |
|
RedirectResponse |
3GPP TS 29.571 [7] |
Response body of redirect response messages. |
|
PlmnId |
3GPP TS 29.571 [7] |
6.3.6.2 Structured data types
6.3.6.2.1 Introduction
This clause defines the structures to be used in resource representations.
6.3.6.2.2 Type: DeregistrationRequest
Table 6.3.6.2.2-1: Definition of type DeregistrationRequest
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
imsi |
string |
M |
1 |
pattern: "^[0-9]{5,15}$" |
|
deregReason |
DeregistrationReason |
M |
1 |
String, see clause 6.3.6.3.3 |
|
guami |
Guami |
O |
0..1 |
The GUAMI identifying the AMF where the UE is registered. May be used by the HSS based on operator policy to decide whether a registered VLR shall be cancelled. |
6.3.6.2.3 Type: ImeiUpdateInfo
Table 6.3.6.2.3-1: Definition of type ImeiUpdateInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
imsi |
string |
M |
1 |
IMSI of the subscriber. pattern: "^[0-9]{5,15}$" |
imei |
string |
C |
0..1 |
IMEI of the UE as described in 3GPP TS 23.003 [15], clause 6.2.1; it shall not include the Check Digit. pattern: "^[0-9]{14}$" |
imeisv |
string |
C |
0..1 |
IMEISV of the UE as described in 3GPP TS 23.003 [15], clause 6.2.2. pattern: "^[0-9]{16}$" |
NOTE: Exactly one of attributes "imei" or "imeisv" shall be present. |
6.3.6.2.4 Type: ImeiUpdateResponse
Table 6.3.6.2.4-1: Definition of type ImeiUpdateResponse
Attribute name |
Data type |
P |
Cardinality |
Description |
previousImei |
string |
C |
0..1 |
Previous IMEI of the UE as described in 3GPP TS 23.003 [15], clause 6.2.1; it shall not include the Check Digit. It shall be included if the HSS has an IMEI value stored for the UE. pattern: "^[0-9]{14}$" |
previousImeisv |
string |
C |
0..1 |
IMEISV of the UE as described in 3GPP TS 23.003 [15], clause 6.2.2. It shall be included if the HSS has an IMEISV value stored for the UE. pattern: "^[0-9]{16}$" |
NOTE: At least one of attributes "previousImei" or "previousImeisv" shall be present. |
6.3.6.2.5 Type: RoamingStatusUpdateInfo
Table 6.3.6.2.5-1: Definition of type ImeiUpdateInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
imsi |
string |
M |
1 |
IMSI of the subscriber. pattern: "^[0-9]{5,15}$" |
plmnId |
PlmnId |
M |
1 |
PLMN-ID where the UE is located. |
6.3.6.3 Simple data types and enumerations
6.3.6.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.3.6.3.2 Simple data types
The simple data types defined in table 6.3.6.3.2-1 shall be supported.
Table 6.3.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
6.3.6.3.3 Enumeration: DeregistrationReason
Table 6.3.6.3.3-1: Enumeration DeregistrationReason
Enumeration value |
Description |
"UE_INITIAL_AND_SINGLE_REGISTRATION" |
This value is used when the UDM needs to indicate to HSS that the MME/SGSN, if any, shall be cancelled due to an initial registration for single registration. |
"UE_INITIAL_AND_DUAL_REGISTRATION" |
This value is used when the UDM needs to indicate to HSS that an SGSN shall be cancelled (due to initial registration), but the MME shall not be cancelled (due to dual registration). |
"EPS_TO_5GS_MOBILITY" |
This value is used when the UDM needs to indicate to HSS that the MME/SGSN, if any, shall be cancelled due to a mobility event (i.e. for single registration which is not an initial registration). |
6.3.7 Error Handling
6.3.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.3.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.3.7.3 Application Errors
The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [4] may also be used for the Nudm_UEContextManagement service. The application errors defined for the Nhss_UEContextManagement service are listed in Table 6.3.7.3-1.
Table 6.3.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
USER_NOT_FOUND |
404 Not Found |
The user does not exist. |
CONTEXT_NOT_FOUND |
404 Not Found |
It is used when no corresponding UE context exists. |
6.3.8 Feature Negotiation
The optional features in table 6.3.8-1 are defined for the Nhss_UEContextManagement API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.3.8-1: Supported Features
Feature number |
Feature Name |
Description |
6.4 Nhss_EventExposure Service API
6.4.1 API URI
URIs of this API shall have the following root:
{apiRoot}/<apiName>/<apiVersion>/
where "apiRoot" is defined in clause 4.4.1 of 3GPP TS 29.501 [5], the "apiName" shall be set to "nhss-ee" and the "apiVersion" shall be set to "v1" for the current version of this specification.
6.4.2 Usage of HTTP
6.4.2.1 General
HTTP/2, as defined in IETF RFC 7540 [13], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
HTTP messages and bodies for the Nhss_EE service shall comply with the OpenAPI [14] specification contained in Annex A5.
6.4.2.2 HTTP standard headers
6.4.2.2.1 General
The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
6.4.2.2.2 Content type
The following content types shall be supported:
JSON, as defined in IETF RFC 8259 [15], signalled by the content type "application/json".
The Problem Details JSON Object (IETF RFC 7807 [16] signalled by the content type "application/problem+json"
JSON Patch (IETF RFC 6902 [41]). The use of the JSON Patch format in a HTTP request body shall be signalled by the content type "application/json-patch+json".
6.4.2.3 HTTP custom headers
6.4.2.3.1 General
The usage of HTTP custom headers shall be supported as specified in clause 5.2.3 of 3GPP TS 29.500 [4].
6.4.3 Resources
6.4.3.1 Overview
Figure 6.4.3.1-1: Resource URI structure of the Nhss_EE API
Table 6.4.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.4.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
EeSubscriptions |
/{ueId}/ee-subscriptions |
POST |
Create a subscription |
Individual subscription |
/{ueId}/ee-subscriptions/{subscriptionId} |
PATCH |
Update the subscription identified by {subscriptionId} |
DELETE |
Delete the subscription identified by {subscriptionId}, i.e. unsubscribe |
6.4.3.2 Resource: EeSubscriptions (Collection)
6.4.3.2.1 Description
This resource is used to represent subscriptions to notifications.
6.4.3.2.2 Resource Definition
Resource URI: {apiRoot}/nhss-ee/<apiVersion>/{ueId}/ee-subscriptions
This resource shall support the resource URI variables defined in table 6.4.3.2.2-1.
Table 6.4.3.2.2-1: Resource URI variables for this resource
Name |
Definition |
apiRoot |
See clause 6.4.1 |
ueId |
Represents the identity of the UE in the HSS (IMSI) or the identity of a group of UEs. – If representing a single UE, this parameter shall contain the IMSI of the UE. pattern: See type Imsi in clause 6.4.6.3.2 of this document. – If representing a group of UEs, this parameter shall contain the External Group Id. pattern: "^extgroupid-[^@]+@[^@]+$" (NOTE) |
NOTE: If the HSS supports GBEE feature, the ueId can contain the External Group Id, or ueId can only contain IMSI of the UE. |
6.4.3.2.3 Resource Standard Methods
6.4.3.2.3.1 POST
This method shall support the URI query parameters specified in table 6.4.3.2.3.1-1.
Table 6.4.3.2.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 6.4.3.2.3.1-2 and the response data structures and response codes specified in table 6.4.3.2.3.1-3.
Table 6.4.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
EeSubscription |
M |
1 |
The subscription that is to be created |
Table 6.4.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
CreatedEeSubscription |
M |
1 |
201 Created |
Upon success, a response body containing a representation of the created Individual subscription resource shall be returned, along with event reports that might be immediately available at the HSS. The HTTP response shall include a "Location" HTTP header that contains the resource URI of the created resource. |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
403 Forbidden |
The "cause" attribute may be used to indicate one of the following application errors: – MONITORING_NOT_ALLOWED – MAXIMUM_RESOURCES_EXCEEDED – MTC_PROVIDER_NOT_ALLOWED |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND |
ProblemDetails |
O |
0..1 |
501 Not Implemented |
The "cause" attribute may be used to indicate one of the following application errors: – UNSUPPORTED_MONITORING_EVENT_TYPE – UNSUPPORTED_MONITORING_REPORT_OPTIONS This response shall not be cached. |
Table 6.4.3.2.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.4.3.2.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.4.3.3 Resource: Individual subscription (Document)
6.4.3.3.1 Resource Definition
Resource URI: {apiRoot}/nhss-ee/<apiVersion>/{ueId}/ee-subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.4.3.3.1-1.
Table 6.4.3.3.1-1: Resource URI variables for this resource
Name |
Definition |
apiRoot |
See clause 6.4.1 |
ueId |
Represents the identity of the UE in the HSS (IMSI) pattern: See type Imsi in clause 6.4.6.3.2 of this document. |
subscriptionId |
The subscriptionId identifies an individual subscription to notifications The type is string. |
6.4.3.3.2 Resource Standard Methods
6.4.3.3.2.1 DELETE
This method shall support the URI query parameters specified in table 6.4.3.3.2.1-1.
Table 6.4.3.3.1.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 6.4.3.3.2.1-2 and the response data structures and response codes specified in table 6.4.3.3.2.1-3.
Table 6.4.3.3.2.1-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 6.4.3.3.2.1-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. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – SUBSCRIPTION_NOT_FOUND, see 3GPP TS 29.500 [4] table 5.2.7.2-1. |
Table 6.4.3.3.2.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.4.3.3.2.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.4.3.3.2.2 PATCH
This method shall support the URI query parameters specified in table 6.4.3.3.2.2-1.
Table 6.4.3.3.2.2-1: URI query parameters supported by the PATCH method on this resource
Name |
Data type |
P |
Cardinality |
Description |
supported-features |
SupportedFeatures |
O |
0..1 |
see 3GPP TS 29.500 [4] clause 6.6 |
This method shall support the request data structures specified in table 6.4.3.3.2.2-2 and the response data structures and response codes specified in table 6.4.3.3.2.2-3.
Table 6.4.3.3.2.2-2: Data structures supported by the PATCH Request Body on this resource
Data type |
P |
Cardinality |
Description |
array(PatchItem) |
M |
1..N |
Items describe the modifications to the Event Subscription |
Table 6.4.3.3.2.2-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 success, an empty response body shall be returned. |
||
PatchResult |
M |
1 |
200 OK |
Upon success, the execution report is returned. |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same HSS (service) set. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – USER_NOT_FOUND – SUBSCRIPTION_NOT_FOUND, see 3GPP TS 29.500 [4] table 5.2.7.2-1. |
ProblemDetails |
O |
0..1 |
403 Forbidden |
One or more attributes are not allowed to be modified. The "cause" attribute may be used to indicate one of the following application errors: – MODIFICATION_NOT_ALLOWED, see 3GPP TS 29.500 [4] table 5.2.7.2-1. |
Table 6.4.3.3.2.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.4.3.3.2.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same HSS (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.4.4 Custom Operations without associated resources
In this release of this specification, no custom operations without associated resources are defined for the Nhss_EventExposure Service.
6.4.5 Notifications
6.4.5.1 General
This clause will specify the use of notifications and corresponding protocol details if required for the specific service. When notifications are supported by the API, it will include a reference to the general description of notifications support over the 5G SBIs specified in TS 29.500 / TS 29.501.
6.4.5.2 Event Occurrence Notification
The POST method shall be used for Event Occurrence Notifications and the URI shall be as provided during the subscription procedure.
Resource URI: {callbackReference}
Support of URI query parameters is specified in table 6.4.5.2-1.
Table 6.4.5.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 6.4.5.2-2 and of response data structures and response codes is specified in table 6.4.5.2-3.
Table 6.4.5.2-2: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
array(MonitoringReport) |
M |
1..N |
A list of MonitoringReports each of which contains information regarding the occurred event |
Table 6.4.5.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. |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the notification endpoint of the subscribing NF Service Consumer. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the notification endpoint of the subscribing NF Service Consumer. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
ProblemDetails |
O |
0..1 |
404 Not Found |
The "cause" attribute may be used to indicate one of the following application errors: – CONTEXT_NOT_FOUND |
NOTE: In addition, common data structures as listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] are supported. |
Table 6.4.5.2-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
Table 6.4.5.2-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected. |
6.4.6 Data Model
6.4.6.1 General
This clause specifies the application data model supported by the API.
Table 6.4.6.1-1 specifies the data types defined for the Nhss_EE service API.
Table 6.4.6.1-1: Nhss_EE specific Data Types
Data type |
Clause defined |
Description |
EeSubscription |
6.4.6.2.2 |
A subscription to Notifications |
CreatedEeSubscription |
6.4.6.2.3 |
|
MonitoringConfiguration |
6.4.6.2.4 |
Monitoring Configuration |
MonitoringReport |
6.4.6.2.5 |
Monitoring Report |
Report |
6.4.6.2.6 |
|
ReportingOptions |
6.4.6.2.7 |
|
LocationReportingConfiguration |
6.4.6.2.8 |
|
ReachabilityForSmsReport |
6.4.6.2.9 |
|
LossConnectivityConfiguration |
6.4.6.2.10 |
|
ReachabilityForDataConfiguration |
6.4.6.2.11 |
|
PduSessionStatusCfg |
6.4.6.2.12 |
Reporting configuration for events related to PDN connectivity Status |
ReachabilityForDataReport |
6.4.6.2.13 |
Report of "UE_REACHABILITY_FOR_DATA" event |
FailedMonitoringConfiguration |
6.4.6.2.14 |
Failed Monitoring Configuration in the EE subscription |
EventType |
6.4.6.3.3 |
|
LocationAccuracy |
6.4.6.3.4 |
|
FailedCause |
6.4.6.3.5 |
Failed cause of the failed Monitoring Configuration in the EE subscription |
Table 6.4.6.1-2 specifies data types re-used by the Nhss_EE service API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nhss_EE service API.
Table 6.4.6.1-2: Nhss_EE re-used Data Types
Data type |
Reference |
Comments |
Uri |
3GPP TS 29.571 [7] |
Uniform Resource Identifier |
SupportedFeatures |
3GPP TS 29.571 [7] |
See 3GPP TS 29.500 [4] clause 6.6 |
DateTime |
3GPP TS 29.571 [7] |
|
PatchResult |
3GPP TS 29.571 [7] |
|
DurationSec |
3GPP TS 29.571 [7] |
|
DiameterIdentity |
3GPP TS 29.571 [7] |
|
Dnn |
3GPP TS 29.571 [7] |
Data Network Name with Network Identifier only. |
ProblemDetails |
3GPP TS 29.571 [7] |
Response body of error response messages. |
RedirectResponse |
3GPP TS 29.571 [7] |
Response body of redirect response messages. |
MtcProviderInformation |
3GPP TS 29.571 [7] |
MTC Provider Information |
DiameterIdentity |
3GPP TS 29.571 [7] |
Diameter Identify (FQDN) |
LossConnectivityReport |
3GPP TS 29.503 [13] |
Report of "LOSS_OF_CONNECTIVITY" event |
LocationReport |
3GPP TS 29.503 [13] |
Report of "LOCATION_REPORTING" event |
PdnConnectivityStatReport |
3GPP TS 29.503 [13] |
Report of "PDN_CONNECTIVITY_STATUS" event |
6.4.6.2 Structured data types
6.4.6.2.1 Introduction
This clause defines the data structures to be used in resource representations.
6.4.6.2.2 Type: EeSubscription
Table 6.4.6.2.2-1: Definition of type EeSubscription
Attribute name |
Data type |
P |
Cardinality |
Description |
callbackReference |
Uri |
M |
1 |
URI provided by the NF service consumer to receive notifications |
monitoringConfigurations |
map(MonitoringConfiguration) |
O |
1..N |
A map (list of key-value pairs where referenceId converted from integer to string serves as key) of MonitoringConfigurations |
scefId |
DiameterIdentity |
O |
0..1 |
Diameter Identify (FQDN) of the SCEF |
scefDiamRealm |
DiameterIdentity |
O |
0..1 |
When present, It contains the Diameter realm of the SCEF to which the monitered reports may be sent in EPC. |
supportedFeatures |
SupportedFeatures |
O |
0..1 |
See clause 6.4.8 |
reportingOptions |
ReportingOptions |
O |
0..1 |
This IE may be included if the NF service consumer wants to describe how the reports of the event are to be generated. If this attribute is not present in the request, it means that the NF service consumer does not specify any maximum number of reports or any expiry time for the subscription; still, the NF service producer (HSS) may set an expiry time in the response to the subscription creation (see clause 6.4.6.2.7). |
mtcProviderInformation |
MtcProviderInformation |
O |
0..1 |
Indicates MTC provider information for Monitoring Configuration authorization. |
externalIdentifier |
string |
O |
0..1 |
Represents a single external Identifier or a group of external Identifiers: – If representing a single external identifier: – If representing a group of external identifiers: |
6.4.6.2.3 Type: CreatedEeSubscription
Table 6.4.6.2.3-1: Definition of type CreatedEeSubscription
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eeSubscription |
EeSubscription |
M |
1 |
This IE shall contain the representation of the created event subscription. |
|
eventReports |
array(MonitoringReport) |
O |
1..N |
This IE may be included when the NF consumer has indicated supporting of ERIR feature in the subscription creation request (see clause 6.4.8). This IE when present, shall contain the status of events that are requested for immediate reporting as well, if those events are available at the time of subscription. |
ERIR |
failedMonitoringConfigs |
map(FailedMonitoringConfiguration) |
O |
1..N |
A map (list of key-value pairs where ReferenceId converted from integer to string serves as key; see clause 6.4.6.3.2) of FailedMonitoringConfiguration; see clause 6.4.6.2.14. This IE is used to indicate the failed subscriptions of event monitoring configuration and the failed cause for them. |
|
supportedFeatures |
SupportedFeatures |
O |
0..1 |
See clause 6.4.8 |
6.4.6.2.4 Type: MonitoringConfiguration
Table 6.4.6.2.4-1: Definition of type MonitoringConfiguration
Attribute name |
Data type |
P |
Cardinality |
Description |
eventType |
EventType |
M |
1 |
Event type |
immediateFlag |
boolean |
O |
0..1 |
Indicates if an immediate event report in the subscription response indicating current value / status of the event is required, if available. If the flag is not present, then immediate reporting may be skipped. |
locationReportingConfiguration |
LocationReportingConfiguration |
C |
0..1 |
Shall be present if eventType is "LOCATION_REPORTING" |
lossConnectivityConfiguration |
LossConnectivityConfiguration |
O |
0..1 |
May be present if eventType is "LOSS_OF_CONNECTIVITY". |
reachabilityForDataConfiguration |
ReachabilityForDataConfiguration |
O |
0..1 |
May be present if eventType is "UE_REACHABILITY_FOR_DATA" |
pduSessionStatusCfg |
PduSessionStatusCfg |
O |
0..1 |
may be present if eventType is "PDN_CONNECTIVITY_STATUS" |
idleStatusInd |
boolean |
O |
0..1 |
Idle Status Indication request. May be present if eventType is "UE_REACHABILITY_FOR_DATA" or "AVAILABILITY_AFTER_DDN_FAILURE" When present, this IE shall be set as following: – true: Idle status indication is requested – false (default): Idle status indication is not requested |
6.4.6.2.5 Type: MonitoringReport
Table 6.4.6.2.5-1: Definition of type MonitoringReport
Attribute name |
Data type |
P |
Cardinality |
Description |
referenceId |
ReferenceId |
M |
1 |
Shall contain the Reference ID which was provided as the key of the associated monitoring configuration in subscription request. The consumer can use this IE to uniquely associate the report with the corresponding event that was requested to be monitored. |
eventType |
EventType |
M |
1 |
String; see clause 6.4.6.3.3 only the following values are allowed: "UE_REACHABILITY_FOR_SMS" "UE_REACHABILITY_FOR_DATA" "LOSS_OF_CONNECTIVITY" "LOCATION_REPORTING" "PDN_CONNECTIVITY_STATUS" |
timeStamp |
DateTime |
M |
1 |
Point in time at which the event occured |
report |
Report |
O |
0..1 |
Shall be present if eventType is "UE_REACHABILITY_FOR_SMS" "UE_REACHABILITY_FOR_DATA" "LOSS_OF_CONNECTIVITY" "LOCATION_REPORTING" "PDN_CONNECTIVITY_STATUS" |
6.4.6.2.6 Type: Report
Table 6.4.6.2.6-1: Definition of type Report
Attribute name |
Data type |
P |
Cardinality |
Description |
reachabilityForSmsReport |
ReachabilityForSmsReport |
O |
0..1 |
Reports the UE reachacbility for SMS |
reachabilityForDataReport |
ReachabilityForDataReport |
O |
0..1 |
Reports the UE reachacbility for Data |
lossConnectivityReport |
LossConnectivityReport |
O |
0..1 |
Reports the Loss of Connectivity |
locationReport |
LocationReport |
O |
0..1 |
Reports the UE Location |
pdnConnectivityStatReport |
PdnConnectivityStatReport |
O |
0..1 |
Reports the PDN Connectivity Status |
6.4.6.2.7 Type: ReportingOptions
Table 6.4.6.2.7-1: Definition of type ReportingOptions
Attribute name |
Data type |
P |
Cardinality |
Description |
maxNumOfReports |
MaxNumOfReports |
O |
0..1 |
Maximum number of reports. If not present, the NF service consumer does not specify any maximum number of reports to be received. (NOTE) |
expiry |
DateTime |
C |
0..1 |
This IE shall be included in an event subscription response, if, based on operator policy, the HSS needs to include an expiry time, and may be included in an event subscription request. When present, this IE shall represent the time at which monitoring shall cease and the subscription becomes invalid. If the maxNumOfReports included in an event subscription response is 1 and if an event report is included in the subscription response then the value of the expiry included in the response shall be an immediate timestamp. (NOTE) |
reportPeriod |
DurationSec |
C |
0..1 |
Indicates the interval time between which the event notification is reported, may be present if event type is "LOCATION_REPORTING" |
NOTE: If parameter "maxNumOfReports" and "expiry" are included at the same time, the subscription will expire as soon as one of the conditions is met. |
6.4.6.2.8 Type: LocationReportingConfiguration
Table 6.4.6.2.8-1: Definition of type LocationReportingConfiguration
Attribute name |
Data type |
P |
Cardinality |
Description |
currentLocation |
boolean |
M |
1 |
true: Indicates that current location is requested. false: Indicates that last known location is requested. |
accuracy |
LocationAccuracy |
C |
0..1 |
Indicates whether Cell-level or TA-level accuracy is requested. Shall be present when current location is requested. |
6.4.6.2.9 Type: ReachabilityForSmsReport
Table 6.4.6.2.9-1: Definition of type ReachabilityForSmsReport
Attribute name |
Data type |
P |
Cardinality |
Description |
reachabilitySmsStatus |
boolean |
M |
1 |
true: UE is reachable for SMS false: UE is not reachable for SMS |
maxAvailabilityTime |
DateTime |
O |
0..1 |
Indicates the time (in UTC) until which the UE is expected to be reachable. This information may be used by the SMS Service Center to prioritize the retransmission of pending Mobile Terminated Short Message to UEs using a power saving mechanism (eDRX, PSM etc.). |
6.4.6.2.10 Type: LossConnectivityConfiguration
Table 6.4.6.2.10-1: Definition of type LossConnectivityConfiguration
Attribute name |
Data type |
P |
Cardinality |
Description |
maxDetectionTime |
DurationSec |
O |
0..1 |
When present, it indicates the configured Maximum Detection Time |
6.4.6.2.11 Type: ReachabilityForDataConfiguration
Table 6.4.6.2.11-1: Definition of type ReachabilityForDataConfiguration
Attribute name |
Data type |
P |
Cardinality |
Description |
maximumLatency |
DurationSec |
O |
0..1 |
When present, it indicates the configured Maximum Latency. (NOTE) |
maximumResponseTime |
DurationSec |
O |
0..1 |
When present, it indicates the configured Maximum Response Time. (NOTE) |
suggestedPacketNumDl |
integer |
O |
0..1 |
When present, it indicates the configured Suggested number of downlink packets. (NOTE) |
NOTE: At least one of maximumLatency, maximumResponseTime or suggestedPacketNumDl shall be present |
6.4.6.2.12 Type: PduSessionStatusCfg
Table 6.4.6.2.12-1: Definition of type PduSessionStatusCfg
Attribute name |
Data type |
P |
Cardinality |
Description |
apn |
Dnn |
O |
0..1 |
When present, it indicates the APN for which the event is monitored. |
6.4.6.2.13 Type: ReachabilityForDataReport
Table 6.4.6.2.13-1: Definition of type ReachabilityForDataReport
Attribute name |
Data type |
P |
Cardinality |
Description |
reachabilityDataStatus |
boolean |
M |
1 |
true: UE is reachable for Data false: UE is not reachable for Data |
maxAvailabilityTime |
DateTime |
O |
0..1 |
Indicates the time (in UTC) until which the UE is expected to be reachable. This information may be used by the SMS Service Center to prioritize the retransmission of pending Mobile Terminated Short Message to UEs using a power saving mechanism (eDRX, PSM etc.). |
6.4.6.2.14 Type: FailedMonitoringConfiguration
Table 6.4.6.2.14-1: Definition of type FailedMonitoringConfiguration
Attribute name |
Data type |
P |
Cardinality |
Description |
eventType |
EventType |
M |
1 |
Contains the Event type, see clause 6.4.6.3.3 |
failedCause |
FailedCause |
M |
1 |
Contains the failed cause of the subscription of the event monitoring. |
6.4.6.3 Simple data types and enumerations
6.4.6.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.4.6.3.2 Simple data types
The simple data types defined in table 6.4.6.3.2-1 shall be supported.
Table 6.4.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
ReferenceId |
integer |
ReferenceId is used as key in a map of MonitoringConfigurations; see clause 6.4.6.2.4. ReferenceId is used as key in a map of FailedMonitoringConfiguration; see clause 6.4.6.2.3. The numeric value should not be higher than 2^64-1 (i.e. it should be possible to convey it in an unsigned 64 integer Information Element, used in other protocols), if interworking with the Event Exposure framework in EPC is required. |
Imsi |
string |
IMSI pattern: ‘^(imsi-[0-9]{5,15})$’ |
UeIdOrGroupId |
string |
Contains the UE identifier or the Group Identifier of the UE. pattern: ‘^(imsi-[0-9]{5,15}|extgroupid-[^@]+@[^@]+|.+$)’ |
MaxNumOfReports |
integer |
Maximum number of reports. Minimum: 1 |
6.4.6.3.3 Enumeration: EventType
Table 6.4.6.3.3-1: Enumeration EventType
Enumeration value |
Description |
"LOSS_OF_CONNECTIVITY" |
Loss of connectivity event |
"UE_REACHABILITY_FOR_DATA" |
UE reachability for Data, implements the "UE Reachability for Data" event as specified in 3GPP TS 23.682 [18]. When this event is subscribed by an NF service consumer, the HSS shall send an Insert Subscriber Data Request message to the MME/SGSN for the UE with the Monitoring-Type AVP set to the value UE_REACHABILITY and the Reachability-Information AVP set to the value REACHABLE_FOR_DATA, see clause 5.2.2.1.3 of 3GPP TS 29.272 [17]. |
"UE_REACHABILITY_FOR_SMS" |
UE reachability for SMS, implements the "UE Reachability for SMS Delivery" event as specified in 3GPP TS 23.682 [18]. This event only supports One-Time reporting. |
"LOCATION_REPORTING" |
Location Reporting event |
"COMMUNICATION_FAILURE" |
Communication Failure event |
"AVAILABILITY_AFTER_DDN_FAILURE" |
Availability after DDN failure event |
"PDN_CONNECTIVITY_STATUS" |
PDN Connectivity Status event |
6.4.6.3.4 Enumeration: LocationAccuracy
Table 6.4.6.3.4-1: Enumeration LocationAccuracy
Enumeration value |
Description |
"CELL_LEVEL" |
Change of cell shall be reported, equivalent to the value "CGI-ECGI (0)" of Accuracy IE of HSS Diameter interface as specified in clause 8.4.17 of 3GPP TS 29.336 [21]. |
"RAN_NODE_LEVEL" |
change of serving RAN node shall be reported, equivalent to the value "eNB (1)" of Accuracy IE of HSS Diameter interface as specified in clause 8.4.17 of 3GPP TS 29.336 [21]. |
"TA_LEVEL" |
Change of TA shall be reported, equivalent to the value " LA-TA-RA (2)" of Accuracy IE of HSS Diameter interface as specified in clause 8.4.17 of 3GPP TS 29.336 [21]. |
6.4.6.3.5 Enumeration: FailedCause
Table 6.4.6.3.5-1: Enumeration FailedCause
Enumeration value |
Description |
"MTC_PROVIDER_NOT_ALLOWED" |
MTC Provider is now allowed to perform monitoring for the requested event type. |
"MONITORING_NOT_ALLOWED" |
The subscriber does not have the necessary subscription for monitoring with the requested Event Type. |
"UNSUPPORTED_MONITORING_EVENT_TYPE" |
The required event type is unsupported. |
"UNSUPPORTED_MONITORING_REPORT_OPTIONS" |
The monitoring configuration for the required event type contains unsupported report options. |
"UNSPECIFIED" |
The failed cause is unspecified. |
6.4.7 Error Handling
6.4.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.4.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.4.7.3 Application Errors
The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [4] may also be used for the Nhss_EventExposure service. The following application errors listed in Table 6.4.7.3-1 are specific for the Nhss_EventExposure service.
Table 6.4.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
MONITORING_NOT_ALLOWED |
403 Forbidden |
The subscriber does not have the necessary subscription for monitoring with the requested Event Type. |
MTC_PROVIDER_NOT_ALLOWED |
403 Forbidden |
MTC Provider not authorized to perform monitoring configuration. |
USER_NOT_FOUND |
404 Not Found |
The user does not exist |
CONTEXT_NOT_FOUND |
404 Not Found |
It is used when no corresponding context exists. |
UNSUPPORTED_MONITORING_EVENT_TYPE |
501 Not Implemented |
The monitoring configuration contains unsupported event type. |
UNSUPPORTED_MONITORING_REPORT_OPTIONS |
501 Not Implemented |
The monitoring configuration contains unsupported report options. |
6.4.8 Feature Negotiation
The optional features in table 6.4.8-1 are defined for the Nhss_EE API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.4.8-1: Supported Features
Feature number |
Feature Name |
Description |
1 |
ERIR |
Event Reports in Response An NF consumer supporting this feature shall be able to handle the event reports within the Event Subscription Create Response, as specified in clause 5.5.2.2.2. |
2 |
GBEE |
Support of Group-based Event Exposure. This feature bit indicates whether the Nhss_EventExposure Service support Group-based Event Exposure or not. |
6.4.9 Security
As indicated in 3GPP TS 33.501 [6] and 3GPP TS 29.500 [4], the access to the Nhss_EE API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [18]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [19]) plays the role of the authorization server.
If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nhss_EE API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [19], clause 5.4.2.2.
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nhss_EE service.
The Nhss_EE API defines a single scope "nhss-ee" for OAuth2 authorization (as specified in 3GPP TS 33.501 [6]) for the entire API, and it does not define any additional scopes at resource or operation level.
Annex A (normative):
OpenAPI specification