• Initial QoS

• Service Detection

• Classification of Application Traffic

• Quality of Service Renegotiation

• Before making an NRUPC/NRSPCA Request, ACS checks if there is any outstanding request for the same QCI for the same subscriber. If there is, it will not process the new request and discards the packet.

• After a context is terminated, ACS unbinds all the rules bound to that context. Such a rule can later be bound to some other context when a packet matches that rule.

  Important:

  The packet that triggered the NRUPC/NRSPCA request is discarded.

configure
     context <context_name>
          ip access-list <acl_name>
               permit { tcp | udp } ........ treatment { background | conversational | interactive-1 | interactive-2 | interactive-3 | streaming }
               end

• context_name must be the name of the destination context in which you want to configure the ACL. The same context must be used for APN configuration.
• For information on configuring the rules that comprise the ACL, refer to Access Control Lists.

configure
     active-charging service <service_name>
          charging-action <charging_action_name> -noconfirm
               qos-renegotiate traffic-class streaming
               flow action discard
               flow limit-for-bandwidth direction downlink peak-data-rate <bps> peak-burst-size <bytes> violate-action lower-ip-precedence
               end

• A maximum of eight packet filters can be configured per charging action.

• The flow limit-for-bandwidth command contains other option than the example shown here. See ACS Charging Action Configuration Mode Commands in the Command Line Interface Reference for more information on this command.

configure
     active-charging service <service_name>
          rulebase <rulebase_name> [ -noconfirm ]
               qos-renegotiate timeout <timeout>
               end

configure
     context <context_name>
          apn <apn_name>
               ip access-group <acl_name> [ in | out ]
               end

• context_name must be the name of the destination context in which you have already configured the ACL, and want to configure the APN template.
• <acl_name> must be the name of the ACL that you have already configured in the context.
• If the optional in or out keywords are not specified in the ip access-group command (APN Configuration Mode), the ACL will be applied to all inbound and outbound packets.

configure
     active-charging service <service_name>
          packet-filter <filter_name> [ -noconfirm ]
               ip local-port { = <port_num> | range <start_port_num> to <end_port_num> }
               ip protocol { = <proto_num> | range <start_proto_num> to <end_proto_num> }
               ip remote-address { = { <ip_address> | <ip_address/mask> } | { range { <ip_address> | <ip_address/mask> } to { <ip_address> | <ip_address/mask> } }
               ip remote-port { = <port_num> | range <start_port_num> to <end_port_num> }
               direction { bi-directional | download | upload }
               priority <priority>
               end

configure
     active-charging service <service_name>
          charging-action <charging_action_name> [ -noconfirm ]
               qos-class-identifier <identifier>
               flow action discard [ downlink | uplink ]
               tft packet-filter <filter_name>
               flow limit-for-bandwidth direction { downlink | uplink } peak-data-rate <bps> peak-burst-size <bytes> violate-action { discard | lower-ip-precedence }
               end

• A number of optional keywords and variable are available for the flow limit-for-bandwidth direction command. Refer to the ACS Charging Action Configuration Mode Commands section of the Command Line Interface Reference for more information regarding this command.

configure
     context <context_name>
          apn <apn_name>
               bearer-control-mode [ mixed | ms-only | none ]
               end

• To enable NCQoS, bearer-control-mode in the APN Configuration Mode must be configured with mixed mode.