6.1.5 Notifications
29.5103GPP5G SystemNetwork function repository servicesRelease 18Stage 3TS
6.1.5.1 General
This clause specifies the notifications provided by the Nnrf_NFManagement service.
The delivery of notifications shall be supported as specified in clause 6.2 of 3GPP TS 29.500 [4] for Server-initiated communication.
Table 6.1.5.1-1: Notifications overview
|
Notification |
Resource URI |
HTTP method or custom operation |
Description (service operation) |
|
NF Instance Status Notification |
{nfStatusNotificationUri} (NF Service Consumer provided callback reference) |
POST |
Notify about registrations / deregistrations or profile changes of NF Instances |
6.1.5.2 NF Instance Status Notification
6.1.5.2.1 Description
The NF Service Consumer provides a callback URI for getting notified about NF Instances status events, the NRF shall notify the NF Service Consumer, when the conditions specified in the subscription are met.
6.1.5.2.2 Notification Definition
The POST method shall be used for NF Instance Status notification and the URI shall be the callback reference provided by the NF Service Consumer during the subscription to this notification.
Resource URI: {nfStatusNotificationUri}
Support of URI query parameters is specified in table 6.1.5.2.2-1.
Table 6.1.5.2.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-2, and support of response data structures and response codes is specified in table 6.1.5.2-3.
Table 6.1.5.2.2-2: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
NotificationData |
M |
1 |
Representation of the NF Instance status notification. |
Table 6.1.5.2.2-3: Data structures supported by the POST Response Body
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
N/A |
204 No Content |
This case represents a successful notification of the NF Instance status event. |
||
|
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF Service Consumer instance to which the notification should be sent. 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 |
The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF Service Consumer instance to which the notification should be sent. 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. |
|
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] other than those specified in the table above also apply, with a ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.2.2-4: Headers supported by the 307 Response Code on this endpoint
|
Name |
Data type |
P |
Cardinality |
Description |
|
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer instance to which the request should be sent |
Table 6.1.5.2.2-5: Headers supported by the 308 Response Code on this endpoint
|
Name |
Data type |
P |
Cardinality |
Description |
|
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer instance to which the request should be sent |