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:
|