How it Works

This section describes how this feature works.

When the AMF detects changes in the Relative AMF Capacity configurations, it performs the following actions:
  • The AMF triggers the configuration updates toward all the gNBs and each request has a timeout value of 30 seconds, which is a hardcoded value.

  • The AMF waits for all the responses and timeout to occur for all the requests toward gNBs.

  • The AMF consolidates the completed list of gNBs from which failure is received with TimeToWait IE from gNB. The IE indicates the minimum time, for which the AMF must wait before retransmitting.

  • The AMF calculates the maximum value of TimeToWait, received across all the failure responses as the waiting time, before it retransmits to all the failed gNBs.

  • The AMF retransmits only to those gNBs which have sent TimeToWait IE and retransmission will be done only once. No further action will be taken on further failure responses.

  • If there are new configuration changes and if there is already an AMF configuration update procedure in progress, then the ongoing configuration is prioritized. The AMF handles the new configuration changes, only after the completion of the ongoing AMF configuration update procedure.

Clear Sub

Operators can clear the existing sessions at specific rate by issuing clear sub all command along with the rate option.