Configuring the N11 Timers

The N11 timer configuration is invoked when AMF rejects the N1N2 message transfer with the "Temporary reject registration ongoing" or "Temporary reject handover ongoing" cause code. Then, SMF considers the timer and reattempts the message transfer. When the timer expires, the transfer is reattempted based on the configured retry count.

To configure an N11 timer, use the following sample configuration:

config 
   profile failure-handling failure_handling_name 
      interface [ gtpc | N11 ] message message_type 
         cause-code [ temp-reject-register | temp-reject-handover ]   
            action [ retry { timeout timeout_duration | 
            max-retry retry_count } | clear | terminate ] 
            end 

NOTES:

  • profile failure-handling failure_handling_name —Enter the name of the profile for failure handling.

  • interface [ gtpc | N11 ] —Configure the interface over which the message transfer must happen.

  • message message_type —Configure the message type to be transferred over the interface. The N11 interface supports the message type as N1N2Transfer.

  • cause-code [ temp-reject-register | temp-reject-handover ] —Configure the HTTP cause code. You can configure multiple cause code values for a message.

  • action [ retry | clear | terminate ] —Configure the action to perform when the message transfer is not successful.

  • action [ retry { max-retry retry_count | timeout timeout_duration } —Specify the number of times the message transfer must be reattempted and the time interval between the consecutive attempts.