Subscription (PATCH) Call Flow

The NRF updates the subscription to notifications on NF instances to refresh the validity time, when the specified time is due to expire. The SMF can request a new validity time to the NRF. If the operation is successful, the NRF can assign and provide a new validity time to the NF.

Updating the "subscriptionID" resource, initiates the Subscription (PATCH) operation. The operation starts on issuing an HTTP PATCH request on the URI representing the individual resource.

The following figure illustrates the call flow for subscription to NF instances in the same PLMN.

Subscription (PATCH) Call Flow
Subscription (PATCH) Call Flow
StepDescription
1

The SMF sends a PATCH request to the resource URI identifying the individual subscription resource. The payload body of the PATCH request contains a "replace" operation on the "validityTime" attribute of the SubscriptionData structure. The request also contains a new suggested value for the "validityTime" attribute. This replace operation does not replace any other attribute of the resource.

2a

When a subscription is successful, the NRF sends a "204 No Content" response. This response indicates that the NRF accepts:

  • Extension of the subscription lifetime

  • Value of the "validityTime" attribute

2b

If the subscription fails due to errors in the JSON Patch object in the request body, the NRF returns a "400 Bad Request" status code with the problem details.

2c

If the subscription fails due to internal errors in the NRF, the NRF returns a "500 Internal Server Error" with the problem details.

Example:

PATCH .../subscriptions/2a58bf47 
Content-Type: application/json-patch+json 
[ 
{ "op": "replace", "path": "/validityTime", "value": "2018-12-30T23:20:50Z" }, 
]