Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.502  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
6.1.4 Custom Operations without associated resources  6.1.5 Notifications  6.1.5.1 General  6.1.5.2 SM Context Status Notification  6.1.5.2.1 Description  6.1.5.2.2 Notification Definition 
...

 

6.1.4  Custom Operations without associated resources  p. 129

None.

6.1.5  Notifications  p. 129

6.1.5.1  General  p. 129

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 TS 29.500 for Server-initiated communication.
Notification Callback URI HTTP method or custom operation Description
(service operation)
SM Context Status Notification{smContextStatusUri} (NF Service Consumer provided callback reference)POSTNotify SM Context Status
Up

6.1.5.2  SM Context Status Notification  p. 130

6.1.5.2.1  Description  p. 130
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  p. 130
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.
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.2-3.
Data type P Cardinality Description
SmContextStatusNotificationM1Representation of the SM context status notification.
Data type P Cardinality Response codes Description
n/a204 No ContentSuccessful notification of the SM context status change
RedirectResponseO0..1307 Temporary RedirectTemporary redirection. (NOTE 2)
RedirectResponseO0..1308 Permanent RedirectPermanent redirection. (NOTE 2)
NOTE 1:
The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of TS 29.500 other than those specified in the Table above also apply, with a ProblemDetails data type (see clause 5.2.7 of TS 29.500).
NOTE 2:
RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of TS 29.500.
Name Data type P Cardinality Description
LocationstringM1A URI pointing to the endpoint of NF service consumer to which the notification should be sent. For the case when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in TS 29.500.
3gpp-Sbi-Target-Nf-IdstringO0..1Identifier of the target NF (service) instance ID towards which the notification is redirected.
Name Data type P Cardinality Description
LocationstringM1A URI pointing to the endpoint of NF service consumer to which the notification should be sent. For the case when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in TS 29.500.
3gpp-Sbi-Target-Nf-IdstringO0..1Identifier of the target NF (service) instance ID towards which the notification is redirected.
Up

Up   Top   ToC