Content for TS 24.502 Word version: 19.0.0

1… 4… 5… 5.3B… 6… 7… 7.2.5… 7.3… 7.3A… 7.4… 7.6… 7.9… 7.10… 8… 9… 9.3… 9.3.2… 9.3.2.2.3… 9.3.3…

7.9 Network-initiated liveness check procedure 7.9.1 General 7.9.2 Network-initiated liveness check procedure initiation 7.9.3 Network-initiated liveness check procedure completion 7.9.4 Abnormal cases
...

7.9 Network-initiated liveness check procedure p. 72

7.9.1 General p. 72

The network-initiated liveness check procedure enables the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access to detect whether the UE is alive.

7.9.2 Network-initiated liveness check procedure initiation p. 72

If the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access has not received any cryptographically protected IKEv2 or IPsec message for the duration of the timeout period for liveness check selected according to the local policy, the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access shall send an INFORMATIONAL request with no payloads RFC 7296.

7.9.3 Network-initiated liveness check procedure completion p. 72

The UE shall handle the INFORMATIONAL request with no payloads as per RFC 7296 and shall send an INFORMATIONAL response.

If an INFORMATIONAL response is received, the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access shall consider the liveness check procedure as successfully completed.

7.9.4 Abnormal cases p. 72

If an INFORMATIONAL response is not received, the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access shall deem the IKEv2 security association to have failed.

The N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access shall discard all states associated with the IKE SA and any child SAs that were negotiated using that IKE SA as specified in RFC 7296. In addition, the N3IWF for untrusted non-3GPP access and the TNGF for trusted non-3GPP access shall inform the AMF that the access stratum connection has been released.