Non-UE N2 Messages Subscription Call Flow

This section describes the Non-UE N2 Messages Subscription call flow.

Handling of subscriptions from various peer nodes are identical, irrespective of the requesting entity a CBCF, an LMF, or a peer AMF. Handling of these subscriptions takes place as per message category.

Non-UE N2 Messages Subscription Call Flow
Non-UE N2 Messages Subscription Call Flow Description

Step

Description

1

The peer node sends a subscription request to the AMF, which reaches the REST-EP.

This message is either a PWS-BCAL (Broadcast Completed Area List or Broadcast Canceled Area List) or PWS-RF (Restart Indication or Failure Indication).

2

The REST-EP forwards this message to the AMF service.

3

The AMF service saves the subscription to the database and sends a success response to REST-EP. The saved subscription contains the URI of the remote node and the parameters for the subscriptions. The AMF creates a unique location URI for this subscription and includes it in the response.

4

The REST-EP responds with a 201 message to the peer node.

5

The AMF service forwards this information to the NGAP-EP.