Use the following configuration to activate the local-policy rule within service scheme based on the configured RAI or TAI range of subscribers.

configure  
   local-policy-service  local_policy_service_name 
      actiondef  actiondef_name 
         action priority  priority activate-lp-rule name  lprule_name 
      end  

Notes:

• activate-lp-rule lprule_name : This keyword activates a local-policy rule within service scheme when a subscriber is in the configured RAI or TAI range. lprule_name must be an existing local-policy rule within the service scheme expressed as an alphanumeric string of 1 through 63 characters.

  When the subscriber moves out of the configured RAI or TAI range, the local-policy rule is deactivated.

• Local-Policy can support up to 7 lp-rules to be activated for a given session.

Use the following configuration to suppress the CRA for event triggers enabled in local policy configurations.

configure  
   local-policy-service  local_policy_service_name 
      suppress-cra event-triggers { ecgi-change | tai-change | uli-change } +  
      end  

Notes:

• suppress-cra event-triggers { ecgi-change | tai-change | uli-change } : This keyword restricts sending of CRA towards MME depending on the ECGI-Change, TAI-Change and ULI-Change event triggers configured in local-policy service.

• Use the no suppress-cra command to configure the default behavior. By default, the CRA notification is sent to MME if one or a combination of these event triggers is installed.

Use the following configuration to install ECGI Change, TAI-Change and/or ULI-Change event triggers from local policy.

configure  
   local-policy-service  service_name 
      actiondef  actiondef_name 
      	action priority priority event-triggers { ecgi-change | tai-change | uli-change }  
    	exit  
	   eventbase  default 
          rule priority  priority event new-call ruledef  ruledef_name actiondef  actiondef_name [ continue ]  
          end  

Notes:

• priority priority : Specifies a priority for the specified action. priority must be unique and an integer from 1 to 2048.

• event-triggers { ecgi-change | tai-change | uli-change } : This keyword specifies to install ECGI-Change, TAI-Change and/or ULI-Change event triggers. If enabled, the respective event triggers are installed from local policy.

• This CLI command is configured in local-policy if operator wants to enable the respective change notification in MME by sending a CRA value.

Use the following configuration to enable TAI-Change detection and take specific action for TAI-CHANGE event reported by MME.

configure  
   local-policy-service  service_name 
      eventbase  eventbase_name 
      	rule priority  priority event tai-change ruledef  ruledef_name actiondef  actiondef_name [ continue ]  
   	end  

Notes:

• priority priority : Specifies a priority for the specified rule. priority must be unique and an integer from 1 to 2048.

• ruledef ruledef_name : Associates the rule with a specific ruledef. ruledef_name must be an existing ruledef within this local QoS policy service.

• actiondef actiondef_name : Associates the rule with a specific actiondef. actiondef_name must be an existing actiondef within this local QoS policy service expressed as an alphanumeric string of 1 through 63 characters.

• tai-change : Enables a new event to detect TAI-Change and applies specific action for the TAI-Change event as defined in actiondef configuration.

• continue : Subsequent rules are also matched; otherwise, rule evaluation is terminated on first match.

Use the following configuration to apply rules based on the values of ECGI, 3G-ULI, and TAI received in event notification by MME.

configure  
   local-policy-service  service_name 
      ruledef  ruledef_name 
      	condition priority  priority ecgi mcc  mcc_num mnc  mnc_num eci { eq | ge | gt | le | lt | match | ne | nomatch } regex |  string_value |  int_value | set }  
          condition priority  priority tai mcc  mcc_num mnc  mnc_num tac { eq | ge | gt | le | lt | match | ne | nomatch } regex |  string_value |  int_value | set }  
          condition priority  priority 3g-uli mcc  mcc_num mnc  mnc_num lac { eq | ge | gt | le | lt | match | ne | nomatch } regex |  string_value |  int_value | set }  
   	exit  

Notes:

• priority priority : Specifies a priority for the specified condition. priority must be unique and an integer from 1 to 2048.

• ecgi mcc mcc_num mnc mnc_num eci : Configures ECGI with values for MCC, MNC and ECI.

  • mcc_num : MCC is a three digit number from 001 to 999. It is a string of size 3 to 3.

  • mnc_num : MNC is two/three digit number from 01 to 999. It is a string of size 2 to 3.

  • eci : ECI is a hexadecimal number from 0x1 to 0xfffffff. It is a string of size 1 to 7.

• tai mcc mcc_num mnc mnc_num tac : Configures TAI with values for MCC, MNC and TAC.

  • mcc_num : MCC is a three digit number from 001 to 999. It is a string of size 3 to 3.

  • mnc_num : MNC is two/three digit number from 01 to 999. It is a string of size 2 to 3.

  • tac : TAC is a 4 byte field. It is a string of 4 hexadecimal values from 0x1 to 0xffff.

• 3g-uli mcc mcc_num mnc mnc_num lac : Configures 3G-ULI parameter with values for MCC, MNC and LAC.

  • mcc_num : MCC is a three digit number from 001 to 999. It is a string of size 3 to 3.

  • mnc_num : MNC is two/three digit number from 01 to 999. It is a string of size 2 to 3.

  • lac : LAC is a 4 byte field. It is a string of 4 hexadecimal values from 0x1 to 0xffff.

• This CLI command is configured in local-policy if operator wants to take specific action based on certain event parameter value received in Change event notification by MME.

Use the following configuration to enable QoS override based on subscriber location.

configure  
    active-charging service  service_name 
        trigger-action  trigaction_name 
            [ no ] throttle-suppress  
        exit  

Notes:

• throttle-suppress : This keyword allows operators to suppress the throttling when the subscriber is in a particular LAC or TAC location.

• Use the no throttle-suppress CLI command to disable this feature for the subscriber.

Use the following configuration to specify the local-policy rule within ECS for enabling trigger condition.

configure  
    active-charging service  service_name 
        trigger-condition  trigcond_name 
            [ no ] local-policy-rule =  lprule_name 
        exit  

Notes:

• local-policy-rule : This keyword allows operators to suppress the throttling when the subscriber is in a particular LAC or TAC location and hits the specified local-policy rule. The local-policy-rule contains either a list, range, or index of LAC and/or TAC entries.

• lprule_name : Specifies the local-policy rule name. lprule_name must be an existing local-policy rule within the service scheme expressed as an alphanumeric string of 1 through 63 characters.

• Use the no local-policy-rule CLI command to disable this feature for the subscriber.

Use the following command to verify the configuration status of this feature.

show configuration  

This command displays all the configurations that are enabled within the chassis for the subscriber. This display can be used to verify if the Location based QoS Override feature is enabled or disabled.

This is an example configuration to enable this feature for a subscriber on a particular rulebase rb1, for a particular local-policy-rule for zone A.

configure  
active-charging service s1  
    trigger-action ta1  
         throttle-suppress  
    exit  
    trigger-condition tc1  
      local-policy-rule = zone_A   
    exit  
    service-scheme ss1  
      trigger loc-update  
        priority 1 trigger-condition tc1 trigger-action ta1  
      exit  
    subs-class sc1  
      rulebase = rb1  
    exit  
    subscriber-base sb1  
      priority 1 subs-class sc1 bind service-scheme ss1  
    exit