Feature Configuration

To configure this feature, use the following configuration:

config 
    call-control-policy ccp_name 
        authenticate registration-request type { frequency frequency_count | periodicity duration } 
        no authenticate registration registration-request 
        authenticate service-request type { frequency frequency_count | periodicity duration } 
        no authenticate registration service-request 
        authenticate all-events { frequency frequency_count | periodicity duration } 
        no authenticate all-events 
        guti-reallocation type { frequency frequency_count | periodicity duration } 
        no guti-reallocation 
        end 

NOTES:

  • call-control-policy ccp_name —Specify the UE-specific name for call control policy. Must be a string.

  • authenticate registration-request { normal | periodic | inter-rat | intra-rat } —Specify the required option to authenticate the registration process.

  • registration-type normal —Specify the initial registration details with locally allocated GUTI.

  • authenticate service-request { data | signaling } —Specify the option to authenticate the service type for the service request.

  • authenticate all-events —Specify the option to authenticate all events. It’s also the default or the fallback authentication option, when the configuration doesn’t present for any type.

  • guti-reallocation { periodic-registration | service-request } —Specify the options to authenticate the GUTI reallocation process.

  • no authenticate { [ registration-request ] | [ service-request ] | [ all-events ] | [ guti-reallocation ] } —Specify the option for which the authentication isn’t required.

  • frequency frequency_count —Specify the required frequency duration or count for authenticating each option. The frequency range is 0–256. The disabled value is 0.

  • periodicity duration —Specify the time, period, or duration for authenticating the selected option. The periodicity duration range is 0–10800 (minutes). The disabled value is 0.

Note
  • The AMF does not maintain periodicity and frequency after the context is deleted. If UE context is not available, the frequency and periodicity triggers doesn't work.

    For example, if the mobile identifier in the NAS Attach is a foreign GUTI, the AMF doesn't trigger authentication/GUTI reallocation for the subscriber based on frequency/periodicity.

  • Inter-rat ReAuth/SelectiveAuth is supported for frequency 1 and periodicity 0 only.

  • If the GUTI reallocation and reauthentication need to be configured on the basis of only frequency or only periodicity, then the non-used or disabled configuration parameter (such as periodicity or frequency) must be set as 0.

  • The periodicity values in minutes indicate that Amf ReAuth or ReAllocateGuti time difference between the two successive requests is more than the defined values.

  • The periodicity timer configured for any procedure starts on the first occurrence of that procedure.

  • The defined frequency value indicates that Amf ReAuth or ReAllocateGuti for every subscriber.

  • When the AMF resets both frequency and periodicity, it indicates the expired value for either frequency or periodicity.

  • The default GUTI reallocation is enabled for periodic-registration . The following commands are used to disable or enable this option.

    config 
        amf-global call-control-policy ccp-name 
        guti-reallocation periodic-registration disabled 
        end 
    
    config 
        amf-global call-control-policy ccp-name 
        no guti-reallocation periodic-registration disabled 
        guti-reallocation periodic-registration { frequency count | periodicity duration  }
        end