6.1.5 Notifications
29.5023GPP5G SystemRelease 16Session Management ServicesStage 3TS
6.1.5.1 General
This clause specifies the notifications provided by the Nsmf_PDUSession 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 |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
|
SM Context Status Notification |
{smContextStatusUri} (NF Service Consumer provided callback reference) |
POST |
Notify SM Context Status |
6.1.5.2 SM Context Status Notification
6.1.5.2.1 Description
If the NF Service Consumer (e.g AMF) has provided the callback URI for getting notified about change of SM context status, the SMF shall notify the NF Service Consumer when the SM context status information is updated.
6.1.5.2.2 Notification Definition
The POST method shall be used for SM context status notification and the URI shall be the callback reference provided by the NF Service Consumer during the subscription to this notification.
Callback URI: {smContextStatusUri}
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 |
|
SmContextStatusNotification |
M |
1 |
Representation of the SM context 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 |
Successful notification of the SM context status change |
||
|
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer 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 2) |
|
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer 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 2) |
|
NOTE 1: 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]). NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. |
||||
Table 6.1.5.2.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 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 notification is redirected |
Table 6.1.5.2.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 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 notification is redirected |