How it Works

AMF supports collision handling for the following UE-initiated procedures:

  • Initial Registration Request

  • Deregistration

While the initial registration procedure is running, collision can occur for UE-initiated deregistration, or for an extra initial registration that is triggered. In such cases, the current procedure will be waiting for any of the following cases:

  • Security mode complete message

  • Initial context setup response

  • AM policy establishment from PCF

In each of the above specified case, the AMF aborts the running procedure, clears up the corresponding messages, and proceeds with the new incoming procedure.

The UE-level procedure takes precedence over the PDU-level procedure, or aborts or suspends the PDU-level procedure depending on the call flow needs. All procedures have equal priority—Collision handling is provided for every combination.