Feature Description
This section describes the traffic policing and traffic shaping for individual subscribers.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the support of per subscriber Traffic Policing and Shaping feature on Cisco's Chassis and explains the commands and RADIUS attributes that are used to implement this feature. The product Administration Guides provide examples and procedures for configuration of basic services on the system. It is recommended that you select the configuration example that best meets your service model, and configure the required elements for that model, as described in the respective product Administration Guide, before using the procedures in this chapter.
Important |
Traffic Policing and Shaping is a licensed Cisco feature. A separate feature license may be required. Contact your Cisco account representative for detailed information on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide. |
The following topics are included:
This section describes the traffic policing and traffic shaping for individual subscribers.
Traffic policing enables bandwidth limitations on individual subscribers and/or APN of a particular traffic class in 3GPP/3GPP2 service.
Bandwidth enforcement is configured and enforced independently on the downlink and the uplink directions.
Traffic Shaping is a rate limiting method that provides a buffer facility for packets exceeded the configured limit. Once the packet that exceed the data rate, the packet queued inside the buffer to be delivered at a later time.
The bandwidth enforcement can be done in the downlink and uplink directions independently. If there is no more buffer space available for subscriber data the system can be configured to either drop the packets or transmit for the next scheduled traffic session.
Traffic Policing is configured on a per-subscriber basis. The subscribers can either be locally configured subscribers on the system or subscriber profiles configured on a remote RADIUS server.
In 3GPP service, traffic policing can be configured for subscribers through APN configuration as well.
Important |
In 3GPP service, the attributes received from the RADIUS server supersede the settings in the APN. |
Important |
Commands used in the configuration samples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands. |
Important |
Instructions for configuring RADIUS-based subscriber profiles are not provided in this document. Please refer to the documentation supplied with your server for further information. |
Step 1 |
Configure local subscriber profiles on the system to support Traffic Policing by applying the following example configurations: |
Step 2 |
Verify the subscriber profile configuration by applying the following example configuration:
|
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
This section provides information and instructions for configuring the APN template's QoS profile in support of Traffic Policing.
The profile information is sent to the SGSN(s) in response to the GTP Create/Update PDP Context Request messages. If the QoS profile requested by the SGSN is lower than the configured QoS profile, the profile requested by the SGSN is used. If the QoS profile requested by the SGSN is higher, the configured rates are used.
The values for the committed data rate and peak data rate parameters are exchanged in the GTP messages between the GGSN and the SGSN. Therefore, the values used may be lower than the configured values. When negotiating the rate with the SGSN(s), the system converts this rate to a value that is permitted by GTP as shown in the following table:
Value (bps) | Increment Granularity (bps) |
---|---|
From 1000 to 63,000 |
1,000 (for example, 1000, 2000, 3000, ... 63000) |
From 64,000 to 568,000 |
8,000 (for example, 64000, 72000, 80000, ... 568000) |
From 576,000 to 8,640,000 |
64,000 (for example, 576000, 640000, 704000, ... 86400000) |
From 8,700,000 to 16,000,000 |
100,000 bps (for example, 8700000, 8800000, 8900000, ... 16000000) |
Step 1 |
Set parameters by applying the following example configurations: |
Step 2 |
Verify that your APNs were configured properly by entering the following command:
|
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
Traffic Shaping is configured on a per-subscriber basis. The subscribers can either be locally configured subscribers on the system or subscriber profiles configured on a remote RADIUS server.
In 3GPP service Traffic policing can be configured for subscribers through APN configuration as well.
Important |
In 3GPP, service attributes received from the RADIUS server supersede the settings in the APN. |
Important |
Commands used in the configuration samples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands. |
This section provides information and instructions for configuring local subscriber profiles on the system to support Traffic Shaping.
Important |
Instructions for configuring RADIUS-based subscriber profiles are not provided in this document. Please refer to the documentation supplied with your server for further information. |
Step 1 |
Set parameters by applying the following example configurations:
|
||
Step 2 |
Verify the subscriber profile configuration by applying the following example configuration:
|
||
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
This section provides information and instructions for configuring the APN template's QoS profile in support of Traffic Shaping.
The profile information is sent to the SGSN(s) in response to the GTP Create/Update PDP Context Request messages. If the QoS profile requested by the SGSN is lower than the configured QoS profile, the profile requested by the SGSN is used. If the QoS profile requested by the SGSN is higher, the configured rates are used.
The values for the committed data rate and peak data rate parameters are exchanged in the GTP messages between the GGSN and the SGSN. Therefore, the values used may be lower than the configured values. When negotiating the rate with the SGSN(s), the system converts this rate to a value that is permitted by GTP as shown in the following table.
Value (bps) | Increment Granularity (bps) |
---|---|
From 1000 to 63,000 |
1,000 (for example, 1000, 2000, 3000, ... 63000) |
From 64,000 to 568,000 |
8,000 (for example, 64000, 72000, 80000, ... 568000) |
From 576,000 to 8,640,000 |
64,000 (for example, 576000, 640000, 704000, ... 86400000) |
From 8,700,000 to 16,000,000 |
100,000 bps (for example, 8700000, 8800000, 8900000, ... 16000000) |
Step 1 |
Set parameters by applying the following example configurations. |
Step 2 |
Verify that your APNs were configured properly by entering the following command:
|
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
This section provides information and instructions for configuring local subscriber profiles on the system to support Traffic Shaping.
Important |
Instructions for configuring RADIUS-based subscriber profiles are not provided in this document. Please refer to the documentation supplied with your server for further information. |
Step 1 |
Set parameters by applying the following example configurations:
|
||
Step 2 |
Verify the subscriber profile configuration by applying the following example configuration:
|
||
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
This section provides information and instructions for configuring the APN template's QoS profile in support of Traffic Shaping.
The profile information is sent to the SGSN(s) in response to the GTP Create/Update PDP Context Request messages. If the QoS profile requested by the SGSN is lower than the configured QoS profile, the profile requested by the SGSN is used. If the QoS profile requested by the SGSN is higher, the configured rates are used.
The values for the committed data rate and peak data rate parameters are exchanged in the GTP messages between the GGSN and the SGSN. Therefore, the values used may be lower than the configured values. When negotiating the rate with the SGSN(s), the system converts this rate to a value that is permitted by GTP as shown in the following table.
Value (bps) | Increment Granularity (bps) |
---|---|
From 1000 to 63,000 |
1,000 (for example, 1000, 2000, 3000, ... 63000) |
From 64,000 to 568,000 |
8,000 (for example, 64000, 72000, 80000, ... 568000) |
From 576,000 to 8,640,000 |
64,000 (for example, 576000, 640000, 704000, ... 86400000) |
From 8,700,000 to 16,000,000 |
100,000 bps (for example, 8700000, 8800000, 8900000, ... 16000000) |
Step 1 |
Set parameters by applying the following example configurations. |
Step 2 |
Verify that your APNs were configured properly by entering the following command:
|
Step 3 |
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference. |
Attribute | Description | ||
---|---|---|---|
SN-QoS-Tp-Dnlk (or SN1-QoS-Tp-Dnlk) |
Enable or disable traffic policing in the downlink direction. |
||
SN-Tp-Dnlk-Committed-Data-Rate (or SN1-Tp-Dnlk-Committed-Data-Rate) |
Specifies the downlink committed data rate in bps. |
||
SN-Tp-Dnlk-Peak-Data-Rate (or SN1-Tp-Dnlk-Committed-Data-Rate) |
Specifies the downlink peak data rate in bps. |
||
SN-Tp-Dnlk-Burst-Size (or SN1-Tp-Dnlk-Burst-Size) |
Specifies the downlink-burst-size in bytes. NOTE: This parameter must be configured to the greater of the following two values: 1) 3 times greater than packet MTU for the subscriber connection, OR 2) 3 seconds worth of token accumulation within the "bucket" for the configured peak data rate. |
||
SN-Tp-Dnlk-Exceed-Action (or SN1-Tp-Dnlk-Exceed-Action) |
Specifies the downlink exceed action to perform. |
||
SN-Tp-Dnlk-Violate-Action (or SN1-Tp-Dnlk-Violate-Action) |
Specifies the downlink violate action to perform. |
||
SN-QoS-Tp-Uplk (or SN1-QoS-Tp-Uplk) |
Enable/disable traffic policing in the downlink direction. |
||
SN-Tp-Uplk-Committed-Data-Rate (or SN1-Tp-Uplk-Committed-Data-Rate) |
Specifies the uplink committed data rate in bps. |
||
SN-Tp-Uplk-Peak-Data-Rate (or SN1-Tp-Uplk-Committed-Data-Rate) |
Specifies the uplink peak data rate in bps. |
||
SN-Tp-Uplk-Burst-Size (or SN1-Tp-Uplk-Burst-Size) |
Specifies the uplink burst size in bytes.
|
||
SN-Tp-Uplk-Exceed-Action (or SN1-Tp-Uplk-Exceed-Action) |
Specifies the uplink exceed action to perform. |
||
SN-Tp-Uplk-Violate-Action (or SN1-Tp-Uplk-Violate-Action) |
Specifies the uplink violate action to perform. |
The RADIUS attributes listed in the following table are used to configure Traffic Policing for UMTS subscribers configured on remote RADIUS servers. More information on these attributes can be found in the AAA Interface Administration and Reference.
Attribute | Description |
---|---|
SN-QoS-Conversation-Class (or SN1-QoS-Conversation-Class) |
Specifies the QOS Conversation Traffic Class. |
SN-QoS-Streaming-Class (or SN1-QoS-Streaming-Class) |
Specifies the QOS Streaming Traffic Class. |
SN-QoS-Interactive1-Class (or SN1-QoS-Interactive1-Class) |
Specifies the QOS Interactive Traffic Class. |
SN-QoS-Interactive2-Class (or SN1-QoS-Interactive2-Class) |
Specifies the QOS Interactive2 Traffic Class. |
SN-QoS-Interactive3-Class (or SN1-QoS-Interactive3-Class) |
Specifies the QOS Interactive3 Traffic Class. |
SN-QoS-Background-Class (or SN1-QoS-Background-Class) |
Specifies the QOS Background Traffic Class. |
SN-QoS-Traffic-Policy (or SN1-QoS-Traffic-Policy) |
This compound attribute simplifies sending QoS values for Traffic Class (the above attributes), Direction, Burst-Size, Committed-Data-Rate, Peak-Data-Rate, Exceed-Action, and Violate-Action from the RADIUS server. This attribute can be sent multiple times for different traffic classes. If Class is set to 0, it applies across all traffic classes. |