6.1.5 Notifications
29.5183GPP5G SystemAccess and Mobility Management ServicesRelease 18Stage 3TS
6.1.5.1 General
The notifications provided by the Namf_Communication service are specified in this clause.
Table 6.1.5.1-1: Callback overview
|
Notification |
Resource URI |
HTTP method or custom operation |
Description (service operation) |
|
AMF Status Change Notification |
{amfStatusUri} |
POST |
|
|
Non UE N2 Information Notification |
{n2NotifyCallbackUri} |
POST |
|
|
N1 Message Notification |
{n1NotifyCallbackUri} |
POST |
|
|
UE Specific N2 Information Notification |
{n2NotifyCallbackUri} |
POST |
|
|
N1N2 Transfer Failure Notification |
{n1n2FailureTxfNotifURI} |
POST |
6.1.5.2 AMF Status Change Notification
6.1.5.2.1 Description
If a NF service consumer (e.g. SMF) has subscribed to AMF Status Change on Namf_Communication Service, when AMF aware of a change of its own status, AMF shall create a notification including the current state, and shall deliver the notification to the call-back URI, following Subscribe/Notify mechanism defined in 3GPP TS 29.501 [5].
6.1.5.2.2 Notification Definition
Call-back URI: {amfStatusUri}
Call-back URI is provided by NF Service Consumer during creation of the subscription.
6.1.5.2.3 Notification Standard Methods
6.1.5.2.3.1 POST
This method shall support the request data structures specified in table 6.1.5.2.3.1-1 and the response data structures and response codes specified in table 6.1.5.2.3.1-2.
Table 6.1.5.2.3.1-1: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
AmfStatusChangeNotification |
M |
1 |
Representation of the AMF status change notification. |
Table 6.1.5.2.3.1-2: 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 AMF 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. |
|
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. |
|
ProblemDetails |
O |
0..1 |
404 Not Found |
When context of the notification is not found,the "cause" attribute shall be set to: – CONTEXT_NOT_FOUND |
|
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.2.3.1-3: 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.1.5.2.3.1-4: 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.1.5.3 Non UE N2 Information Notification
6.1.5.3.1 Description
This resource represents the callback reference provided by the NF Service Consumer (e.g. LMF, CBCF/PWS-IWF) to receive notifications about N2 information that are not related to a UE.
6.1.5.3.2 Notification Definition
Callback URI: {n2NotifyCallbackUri}
This notification shall support the callback URI variables defined in table 6.1.5.2.2-1.
Table 6.1.5.3.2-1: Callback URI variables for this notification
|
Name |
Definition |
|
n2NotifyCallbackUri |
Callback reference provided by the NF Service Consumer during the subscription to this notification. |
6.1.5.3.3 Notification Standard Methods
6.1.5.3.3.1 POST
This method sends an N2 information notification to the NF Service Consumer (e.g. LMF, CBCF/PWS-IWF).
This method shall support the request data structures specified in table 6.1.5.3.3.1-2 and the response data structures and response codes specified in table 6.1.5.3.3.1-3.
Table 6.1.5.3.3.1-2: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
N2InformationNotification |
M |
1 |
Representation of the N2 information notification. |
Table 6.1.5.3.3.1-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 N2 information to the NF service consumer. |
||
|
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. |
|
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: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.3.3.1-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.1.5.3.3.1-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.1.5.4 N1 Message Notification
6.1.5.4.1 Description
This resource represents the callback reference provided by the NF Service Consumer (e.g. LMF) to receive notifications about N1 message from the UE (e.g. LPP messages).
6.1.5.4.2 Notification Definition
Callback URI: { n1NotifyCallbackUri }
Callback URI is provided by the NF Service Consumer during the subscription to this notification. . The callback URI for N1 message notification may also be obtained from the NRF, if the NF Service Consumer has registered it in the NF Profile with the NRF.
6.1.5.4.3 Notification Standard Methods
6.1.5.4.3.1 POST
This method sends an N1 message notification to the NF Service Consumer (e.g. LMF).
This method shall support the request data structures specified in table 6.1.5.4.3.1-2 and the response data structures and response codes specified in table 6.1.5.4.3.1-3.
Table 6.1.5.4.3.1-2: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
N1MessageNotification |
M |
1 |
Representation of the N1 message notification. |
Table 6.1.5.4.3.1-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 N1 message to the NF service consumer. |
||
|
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. |
|
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. |
|
ProblemDetails |
O |
0..1 |
403 Forbidden |
This case represents, the NF service consumer failing to accept the processing of the notified N1 message. The detailed information shall be provided in the ProblemDetails structure. |
|
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.4.3.1-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.1.5.4.3.1-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.1.5.5 UE Specific N2 Information Notification
6.1.5.5.1 Description
This resource represents the callback reference provided by the NF Service Consumer (e.g. LMF) to receive notifications about UE specific N2 information.
6.1.5.5.2 Notification Definition
Callback URI: {n2NotifyCallbackUri}
Callback URI is provided by the NF Service Consumer during the subscription to this notification.
6.1.5.5.3 Notification Standard Methods
6.1.5.5.3.1 POST
This method sends an N2 information notification to the NF Service Consumer (e.g. LMF).
This method shall support the request data structures specified in table 6.1.5.5.3.1-2 and the response data structures and response codes specified in table 6.1.5.5.3.1-3.
Table 6.1.5.5.3.1-2: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
N2InformationNotification |
M |
1 |
Representation of the N2 information notification. |
Table 6.1.5.5.3.1-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 N2 information to the NF service consumer. |
||
|
N2InfoNotificationRspData |
M |
1 |
200 OK |
This case represents a successful notification of the N2 information to the NF service consumer when information needs to be returned in the response. |
|
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. |
|
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: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.5.3.1-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.1.5.5.3.1-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.1.5.6 N1N2 Transfer Failure Notification
6.1.5.6.1 Description
This resource represents the callback reference provided by the NF Service Consumer (e.g. SMF) to receive notifications about failure to deliver N1 / N2 message.
6.1.5.6.2 Notification Definition
Callback URI: {n1n2FailureTxfNotifURI}
Callback URI is provided by the NF Service Consumer during the UE specific N1N2MessageTransfer operation (see clause 6.1.3.5.3.1.
6.1.5.6.3 Notification Standard Methods
6.1.5.6.3.1 POST
This method sends an N1/N2 message transfer failure notification to the NF Service Consumer (e.g. SMF).
This method shall support the request data structures specified in table 6.1.5.6.3.1-1 and the response data structures and response codes specified in table 6.1.5.6.3.1-3.
Table 6.1.5.6.3.1-1: Data structures supported by the POST Request Body
|
Data type |
P |
Cardinality |
Description |
|
N1N2MsgTxfrFailureNotification |
M |
1 |
Representation of the N1/N2 message transfer failure notification. The "cause" attribute shall be set to one of following cause value s (see clause 6.1.6.3.6): – UE_NOT_RESPONDING – UE_NOT_REACHABLE_FOR_SESSION – TEMPORARY_REJECT_REGISTRATION_ONGOING – TEMPORARY_REJECT_HANDOVER_ONGOING – REJECTION_DUE_TO_PAGING_RESTRICTION – AN_NOT_RESPONDING – FAILURE_CAUSE_UNSPECIFIED The AMF may additionally provide the “retryAfter” IE in order for the NF service consumer to throttle sending further N1/N2 Message Transfer request for a short period, e.g. when UE is not responding to paging. |
Table 6.1.5.6.3.1-2: 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 N1 / N2 message transfer to the NF service consumer. |
||
|
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. |
|
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: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
||||
Table 6.1.5.6.3.1-3: 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.1.5.6.3.1-4: 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 |