Feature Configuration

To configure this feature, use the following sample configuration:

config 
profile access access_profile_name 
    n2 trigger { ho-in-progress | temp-not-reachable } { guard-timeout timeout | max-retry retry_count | value retry_count_range } 
    n2 trigger ue-not-reachable value notreachable_count_range 
    end 

NOTES:

  • profile access access_profile_name —Specify a name for the access profile.

  • n2 trigger —Specify the N2 trigger type. Trigger can be the traffic type. Must be one of the following:

    • ho-in-progress —Specify the handover-in-progress trigger configuration list of cause-codes.

    • temp-not-reachable —Specify the temporary not reachable trigger configuration list of cause-codes.

    • ue-not-reachable —Specify the UE not reachable trigger configuration list of cause-codes.

  • guard-timeout timeout —Specify the Handover in progress guard timeout in milliseconds, within the range of 500-30000 milliseconds. The default value is 10000 milliseconds.

  • max-retry retry_count —Specify the maximum retry count value for the handover in progress or temporary not reachable options, within the range of 0-64. The default value is 0.

  • value { notreachable_count_range } | { retry_count_range } —The numbered value in the range of counts for UE not reachable or the maximum retry range.

Note

The defined configurations are used to match the received unsuccessful transfer (radio network standard and customized) causing the code to decide the RRC inactive action. It has the following scenarios:

  • The PCF-initiated modification gets rejected in the case of ue-not-reachable , ho-in-progress , and temp-not-reachable cases. It gets suspended and resumes back after the xn-handover activities in the AN release.

  • The Guard Timer gets started, when the RRC inactive action is either in the ho-in-progress or the temp-not-reachable trigger profile. It waits for the ongoing PCF-initiated modification to suspend. It restarts the xn-handover activities in the AN release within the given time. If this action fails, then the PCF-initiated modification gets rejected. As a result, this action reported as the rule failure note to the PCF.

  • The maximum retry allows the maximum continuous reattempt after the first attempt gets failed. It's a result of receiving the same trigger category cause code repeatedly for each and every attempt. If this action fails, the PCF-initiated modification gets rejected. As a result, this action reported as the rule failure note to the PCF, after reaching the maximum retry attempt.

  • This feature gets activated for the standard RRC inactive cause codes with a default guard timeout and zero maximum-retry.