Руководство По Устранению Ошибки для Cisco Cisco Packet Data Gateway (PDG)
QoS Management
Network Controlled QoS (NCQoS) ▀
Cisco ASR 5000 Series Enhanced Feature Configuration Guide ▄
OL-22983-01
Network Controlled QoS (NCQoS)
Network-controlled QoS is the method by which the QoS for a PDP context (primary or secondary) is updated on the
request of the GGSN through Network Requested Update PDP Context (NRUPC) message. It can also activate a new
secondary PDP context on Network Requested Secondary PDP Context Activation (NRSPCA) message from the
GGSN.
request of the GGSN through Network Requested Update PDP Context (NRUPC) message. It can also activate a new
secondary PDP context on Network Requested Secondary PDP Context Activation (NRSPCA) message from the
GGSN.
How Network Controlled QoS (NCQoS) Works
The GGSN activates or modifies a bearer in case of a service flow matching a statically provisioned Policy and
Charging Control (PCC) rules. The network, based on QoS requirements of the application/service determines what
bearers are needed and either modifies an existing bearer or activates a new one.
Charging Control (PCC) rules. The network, based on QoS requirements of the application/service determines what
bearers are needed and either modifies an existing bearer or activates a new one.
Statically provisioned PCC rules, called Network Requested Operation (NRO) rules, are configured as charging rules in
Active Charging Service (ACS). As a part of charging action for such rules, QoS-needed and corresponding Traffic
Flow Template (TFT) packet filter is configured. QoS-needed mainly consists of QoS Class Identifier (QCI) and data
rates. Whereas, TFT mainly consists of uplink and downlink packet filter information.
Active Charging Service (ACS). As a part of charging action for such rules, QoS-needed and corresponding Traffic
Flow Template (TFT) packet filter is configured. QoS-needed mainly consists of QoS Class Identifier (QCI) and data
rates. Whereas, TFT mainly consists of uplink and downlink packet filter information.
W
ARNING
:
This feature does not work in conjunction with IMS-Authorization service.
When a packet arrives, Active Charging Service (ACS) analyzes it and proceeds for rule matching based on the priority
in the rulebase. If an NRO rule bound to the context on which the packet arrived matches, ACS applies the bandwidth
limit and gating. If an NRO rule bound to some other context matches, ACS discards the packet.
in the rulebase. If an NRO rule bound to the context on which the packet arrived matches, ACS applies the bandwidth
limit and gating. If an NRO rule bound to some other context matches, ACS discards the packet.
If an unbound NRO rule matches, ACS finds a context with the same QCI as the NRO rule, where context‘s Maximum
Bit Rate (MBR) and matched rule‘s MBR (context's MBR + matched rule's MBR) is less than the MBR for that QCI in
the APN. If such a context is found, NRUPC for that context is triggered. If the request succeeds, the rule will be bound
to that context.
Bit Rate (MBR) and matched rule‘s MBR (context's MBR + matched rule's MBR) is less than the MBR for that QCI in
the APN. If such a context is found, NRUPC for that context is triggered. If the request succeeds, the rule will be bound
to that context.
Important:
The packet that triggers the NRUPC request is discarded.
If no context satisfying the MBR limit is found, or if there is no context with the same QCI as the NRO rule, the system
triggers NRSPCA. If the request succeeds, the rule will be bound to that context.
triggers NRSPCA. If the request succeeds, the rule will be bound to that context.
Important:
The packet that triggers the NRSPCA request is discarded.
TFTs from the charging-action associated with the NRO rule are also sent as part of the NRUPC/NRSPCA request, and
sent back as part of Create PDP Context response.
sent back as part of Create PDP Context response.
Finally, if a non-NRO rule matches, ACS proceeds with the normal processing of that packet. Non-NRO charging-
actions can still do ―flow action‖ or ITC (limit-for-flow-type and limit-for-bandwidth).
actions can still do ―flow action‖ or ITC (limit-for-flow-type and limit-for-bandwidth).
ACS also takes care of following:
Before ACS makes an NRUPC/NRSPCA request, it checks if there is any outstanding request for the same QCI
for the same subscriber. If there is any, it will not make the new request, and it discards the packet.