6.1.5 Notifications
29.5033GPP5G SystemRelease 18Stage 3TSUnified Data Management Services
6.1.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.
Table 6.1.5.1-1: Notifications overview
|
Notification |
Resource URI |
HTTP method or custom operation |
Description (service operation) |
|
Data Change Notification |
{callbackReference} |
POST |
6.1.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.1.5.2-1.
Table 6.1.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.1.5.2-2 and of response data structures and response codes is specified in table 6.1.5.2-3.
Table 6.1.5.2-2: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
ModificationNotification |
M |
1 |
Table 6.1.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 resource located on an alternative service instance within the same NF or NF (service) set. 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 resource located on an alternative service instance within the same NF or NF (service) set. 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.1.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.1.5.2-4: Headers supported by the 307 Response Code on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
Location |
string |
M |
1 |
Contains the Callback URI of the target NF Service Consumer (e.g. AMF) to which the request is redirected |
|
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.5.2-5: Headers supported by the 308 Response Code on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
Location |
string |
M |
1 |
Contains the Callback URI of the target NF Service Consumer (e.g. AMF) to which the request is redirected |
|
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |