6.1.5 Notifications
32.2913GPP5G system, charging serviceCharging managementRelease 17Stage 3Telecommunication managementTS
6.1.5.1 General
Notifications shall comply to subclause 6.2 of 3GPP TS 29.500 [299] and subclause 4.6.2.3 of 3GPP TS 29.501 [300].
6.1.5.2 Event Notification
6.1.5.2.1 Description
The Notification is used by the CHF to notify NF consumers , which implements the Nchf_ ConvergedCharging_Notify operation defined in 3GPP TS 32.290 [58].
6.1.5.2.2 Target URI
The Notification URI "{notifyUri}" shall be used with the resource URI variables defined in table 6.1.5.2.2-1.
Table 6.1.5.2.2-1: Resource URI variables for this resource
Name |
Definition |
notifyUri |
String formatted as URI with the Notification URI is provided by the SMF during the creation and can be provided in update of the Charging Data resource and within the ChargingData type, as defined in subclause 6.1.6. |
6.1.5.2.3 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 on this resource
Data type |
P |
Cardinality |
Description |
ChargingNotifyRequest |
M |
1 |
Provides Information about active Charging events. ChargingNotifyRequest data type is defined in subclause 6.1.6. |
Table 6.1.5.2.3.1-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ChargingNotifyResponse |
O |
0..1 |
200 |
The receipt of the notification acknowledged, with information. Dependent on support of NotifyInfoResponse |
n/a |
204 No Content |
The receipt of the notification is acknowledged, without information. |
||
n/a |
307 Temporary Redirect |
Dependent on support of ES3XX (NOTE 2) |
||
n/a |
308 Permanent Redirect |
Dependent on support of ES3XX (NOTE 2) |
||
ProblemDetails |
O |
0..1 |
400 Bad Request |
Dependent on support of NotifyInfoResponse (NOTE 2) |
ChargingNotifyResponse |
O |
0..1 |
400 Bad Request |
Dependent on support of NotifyInfoResponse (NOTE 2) |
NOTE 1: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [299] for the POST method also apply. NOTE 2: Failure cases are described in clause 6.1.7. |
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 |
An alternative URI of the resource located in an alternative NF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance 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 |
An alternative URI of the resource located in an alternative NF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected |