8 Notification Push to the Content Provider

29.1163GPPRelease 18Representational state transfer over xMB reference point between content provider and BM-SCTS

8.1 Introduction

The Content Provider configures the BM-SC with a push-notification-url and push-notification-configuration property as documented in clause 5.2.1.1, where the BM-SC can post the notifications to the Content Provider.

8.2 Notification Post

To send a notification to the Content Provider, the BM-SC shall use HTTP POST as follows:

– the request URI with the "path" part is set to: {push-notification-url} HTTP/1.1

– the Host field is set to the address of the Content Provider

– the Content-Type header field is set to “application/json”

– the body of the message is encoded in JSON format

The {push-notification-url} in the URI above is the push notification URL configured by the Content Provider when the Content Provider configures the service using procedures described in clause 5.2.1.2. The URL shall be an HTTPS URL.

The content body of the above POST request shall contain the notification that the BM-SC intends to send to the Content Provider. The representation of the notification is based on the JSON schema of notification resource as described in clause 5.2.4.1.

Upon receipt of HTTP POST from the BM-SC to notify the Content Provider about a notification, the Content Provider shall check whether the BM-SC is authenticated and authorized to send notifications to the Content Provider. If the authorization fails, the Content Provider shall send a 401 message to the BM-SC. If the authorization is successful, the Content Provider shall accept the notification request and respond to the BM-SC with a 200 OK message indicating that it has received the notification from the BM-SC. If the request cannot be fulfilled, the Content Provider shall send a 403 Forbidden message to the BM-SC.

The possible response messages from the Content Provider, depending on whether the notification request is accepted or not, are shown in Table 8.2-1.

Table 8.2-1: Response status code, message, and contents for notification request using HTTP POST

Status Code	Message	Contents
200 OK	The request has succeeded	None
401 Unauthorized	Request requires user authentication	In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8]
403 Forbidden	Request cannot be fulfilled	The Content Provider may include optional text to indicate why the request could not fulfilled
Note: In addition to the above response codes, the Content Provider can also send appropriate response codes described in IETF RFC 7231 [6] as applicable.