How it Works

When a collision is detected, any of the following AMF collisions resolver-based procedures get activated:

  • Aborts an ongoing procedure and performs peer node cleanup when required.

  • Aborts an ongoing procedure and cleans locally without informing peer nodes.

  • Discards an incoming message without responding and paving a way for its timeout.

  • Allows both procedures to continue and execute one at a time in the FIFO manner.

Examples:

The following are a few examples:

  1. The AMF receives a note of the UE-initiated deregistration process, while the initial registration procedure activity is still in progress.

    In this case, the AMF aborts the initial registration procedure locally, without informing peer nodes such as UDM, PCF, and so on.

  2. The AMF receives a note of another initial registration process, while the current one is still in progress.

    In this case, the AMF aborts the older initial registration procedure, and performs the peer node cleanup activity, if required (such as the AMPolicyControl_Delete activity).