How it Works
This section describes how this feature works.
Heartbeat Request
The cnSGW-C or UPF sends the Heartbeat Request on a path to the peer node to find out if the node is alive. The Heartbeat Request messages are sent for each peer with which a PFCP control association is established. cnSGW-C or UPF is prepared to receive the Heartbeat Request and it responds with a Heartbeat Response. The Heartbeat Request starts with the peer when a new session is established with the peer and it’s stopped when the last session is released from the peer.
cnSGW-C and UPF send the Heartbeat Request based on the configured interval. If the peer doesn’t respond, the message is retried for the configured number of times within the retry interval. After the response is received the defined action is taken for the calls associated with the corresponding peer.
Recovery Time Stamp is the IE which contains the start time of the peer node. The Heartbeat Request contains the selfrecovery timestamp value sent to the peer.
Note | The heartbeat request is stopped only when the peer is deleted. |
Heartbeat Response
The Heartbeat Response message is sent as a response to a received Heartbeat Request.
Recovery Timestamp is the IE which contains the start time of the node. Heartbeat Response contains the peer's Recovery Timestamp value.