QOS Profile

Click here to see this page in full context

QOS Profile

You can define the QOS settings requested by the MS/MN in the GPRS, UMTS, and LTE test cases. In GPRS and UMTS testing, when you select the QOS Update Test, you can define new profiles that will be requested for PDP contexts. In the GGSN Node test case, you can define the QOS settings and timing for GGSN-initiated PDP context updates.

GGSN Nodal Test Case
GGSN Node Test Case
CGF Nodal Test Case
UMTS Test Case
MME Nodal Test Case
HSS Node test Case

Where applicable, you can choose to use the same QOS profile for all PDP/bearer contexts or you can define different profiles for each context. Use the Quality of Service radio buttons to select either Summary (all contexts use the same profile) or Individual (different profiles can be defined). If you select Individual, each QOS profile is defined in a separate sub-tab. The sub-tabs are initially provisioned with the Summary settings and are labeled by context.

For example, when 3 primary contexts and 2 secondary contexts are used, the sub-tabs labeled P0 — P2 contain the 3 primary context profiles. Secondary contexts are labeled with both the primary and secondary context identifiers (Pn-Sn). For example, P2-S1 identifies the second secondary context (S1) that is associated with the third primary context (P2).

All of the uplink and downlink rate attributes include a wizard that converts kbps to the correct attribute code. Click the "..." button, enter the rate in kbps in the dialog box, click OK, and the converted code is displayed in the parameter field. You can also directly enter the code in the field.

GPRS Testing

Quality of Service is defined on the GTP tab. The parameters that are enabled depend on which GTP version is selected. With the Inter-SGSN or Session Loading With Mobility tests, you can define profiles that will be requested when the PDP context is handed off when you check the Use Alternate QOS Values on Handoff checkbox.

In GGSN Nodal testing, when Test Activity is Command Mode, you can configure 5 additional sets (Set 2 to Set 6) of QOS Update profile that will be included in the Update PDP Context Request messages.

In CGF Nodal Testing, in GTP' Tab in Ga Interface for Billing.

UMTS Testing

Quality of Service is defined in the SM tab. Only the QOS attributes that can be requested by an MN are available in the UMTS test case. Defaults for all fields are 0 in the UMTS test case.

Parameter Index

Reliability Class
Delay Class
Peak Throughput
Mean Throughput
Delivery Order
Transfer Delay

Delivery of Erroneous SDUs
Guaranteed Bit Rate Uplink
Guaranteed Bit Rate Downlink
Max Bit Rate for Uplink
Max Bit Rate for Downlink
Allocation/Retention Priority

Residual BER
Traffic Class
Max SDU Size
Traffic Handling Priority
SDU Error Ratio
Precedence Class

Include Source Statistics Descriptor

Source Statistics Descriptor
Signalling Indicator

Include Max/Guaranteed Bit Rate Downlink

Max Bit rate for Downlink (extended)
Guaranteed Bit rate Downlink (extended)

Include Max/Guaranteed Bit Rate Uplink

Reliability Class

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosReliability_0_0

Gtp2QosReliability_0_0

Value	Description
0	Subscribed reliability class
1	Unused (treated as 2)
2	Unacknowledged GTP; Acknowledged LLC and RLC, Protected Data
3	Unacknowledged GTP and LLC; Acknowledged RLC, Protected Data
4	Unacknowledged GTP, LLC and RLC, Protected Data
5	Unacknowledged GTP, LLC and RLC, Unprotected Data
6	Unused
7	Reserved

Delay Class

The relative importance for the handling of all SDUs (R97/98).

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosDelay_0_0

Gtp2QosDelay_0_0

Value	Description
0	Subscribed delay class
1	Delay class 1
2	Delay class 2
3	Delay class 3
4	Delay class 4 (best effort)
5	Unused
6	Unused
7	Reserved

Peak Throughput

The maximum throughput allowed for a PDP context.

Range: 0 — 15

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosPeakThruput_0_0

Gtp2QosPeakThruput_0_0

Value	Description
0	Subscribed peak throughput
1	Up to 1,000 octets/sec
2	Up to 2,000 octets/sec
3	Up to 4,000 octets/sec
4	Up to 8,000 octets/sec
5	Up to 16,000 octets/sec
6	Up to 32,000 octets/sec
7	Up to 64,000 octets/sec
8	Up to 128,000 octets/sec
9	Up to 256,000 octets/sec
10 — 14	Unused
15	Reserved

Mean Throughput

The average throughput allowed for a PDP context.

Range: 0— 31

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosMeanThruput_0_0

Gtp2QosMeanThruput_0_0

Value	Description
0	Subscribed mean throughput
1	Up to 100 octets/sec
2	Up to 200 octets/sec
3	Up to 500 octets/sec
4	Up to 1,000 octets/sec
5	Up to 2,000 octets/sec
6	Up to 5,000 octets/sec
7	Up to 10,000 octets/sec
8	Up to 20,000 octets/sec
9	Up to 50,000 octets/sec
10	Up to 100,000 octets/sec
11	Up to 200,000 octets/sec
12	Up to 500,000 octets/sec
13	Up to 1,000,000 octets/sec
14	Up to 2,000,000 octets/sec
15	Up to 5,000,000 octets/sec
16	Up to 10,000,000 octets/sec
17	Up to 20,000,000 octets/sec
18	Up to 50,000,000 octets/sec
19 — 29	Unused
30	Reserved
31	Best effort

Delivery Order

Indicates whether in-sequence SDU delivery is used (R99).

Range: 0 — 3

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

DeliveryOrder_0_0

Gtp2DeliveryOrder_0_0

Value	Description
0	Subscribed delivery order
1	With delivery order
2	Without delivery order
3	Reserved

Transfer Delay

Indicates the maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU to its delivery.

Range: 0 — 63

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosTransferDelay_0_0

Gtp2QosTransferDelay_0_0

Value	Description
0	Subscribed transfer delay
1— 15	Transfer delay in 10ms increments (10ms — 150ms)
16— 31	Transfer delay in 50ms increments (200ms — 950ms) calculated as (200ms + (value - 16) * 50ms)).
32— 62	Transfer delay in 100ms increments (1,000ms — 4,000ms) calculated as (1000ms + (value - 32) * 100ms)).
63	Reserved

Traffic Handling Priority

The relative importance for the handling of all SDUs (R99).

Range: 0 — 3

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosTrafficPriority_0_0

Gtp2QosTrafficPriority_0_0

Value	Description
0	Subscribed traffic handling priority
1	Priority level 1
2	Priority level 2
3	Priority level 3

Guaranteed bit rate uplink

Range: 0 — 255 (Use the conversion wizard or see Standard Values... for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosGuaranteedBitrateUplink_0_0

Gtp2QosGuaranteedBitrateUplink_0_0

Value	Description
0	Subscribed bit rate
1— 63	Maximum bit rate in 1 kbps increments (1 — 63 kbps)
64— 127	Maximum bit rate in 8 kbps increments (64 — 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)).
128— 254	Maximum bit rate in 64 kbps increments (576 — 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)).
255	0 kbps

Guaranteed bit rate downlink

Range: 0 — 255 (Use the conversion wizard or see Standard Values... for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosGuaranteedBitrateDownlink_0_0

Gtp2QosGuaranteedBitrateDownlink_0_0

Value	Description
0	Subscribed bit rate
1— 63	Maximum bit rate in 1 kbps increments (1 — 63 kbps)
64— 127	Maximum bit rate in 8 kbps increments (64 — 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)).
128— 254	Maximum bit rate in 64 kbps increments (576 — 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)).
255	0 kbps

Delivery of Erroneous SDUs

Indicates whether SDUs detected as erroneous will be delivered or discarded (R99).

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosErrorSdu_0_0

Gtp2QosErrorSdu_0_0

Value	Description
0	Subscribed delivery of erroneous SDUs
1	No detect
2	Erroneous SDUs are delivered
3	Erroneous SDUs are not delivered
4 — 7	Reserved

Allocation/Retention Priority

The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control (R99).

Range: 0 — 255

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosAllocPriority_0_0

Gtp2QosAllocPriority_0_0

SDU Error Ratio

The fraction of SDUs lost or detected as erroneous (R99).

Range: 0 — 15

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosSduRatioError_0_0

Gtp2QosSduRatioError_0_0

Value	Description
0	Subscribed SDU error ratio
1	1 * 10-2
2	7 * 10-3
3	1 * 10-3
4	1 * 10-4
5	1 * 10-5
6	1 * 10-6
7	1 * 10-1
8 — 15	Reserved

Residual BER

The undetected bit error ratio in the delivered SDUs. If error detection is not requested, this indicates the BER in the delivered SDUs (R99).

Range: 0 — 15

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosResidualBer_0_0

Gtp2QosResidualBer_0_0

Value	Description
0	Subscribed residual BER
1	5 * 10-2
2	1 * 10-2
3	5 * 10-3
4	4 * 10-3
5	1 * 10-3
6	1 * 10-4
7	1 * 10-5
8	1 * 10-6
9	6 * 10-8
10 — 15	Reserved

Precedence Class

The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control (R97/98).

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosResidualBer_0_0

Gtp2QosResidualBer_0_0

Value	Description
0	Subscribed precedence
1	High priority
2	Normal priority
3	Low priority
4	Unused
5	Unused
6	Unused
7	Reserved

Traffic Class

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

TrafficClass_0_0

Gtp2TrafficClass_0_0

Value	Description
0	Subscribed traffic class
1	Conversational class
2	Streaming class
3	Interactive class
4	Background class
5 — 7	Reserved

Max SDU Size

The maximum SDU size for which the network will satisfy the negotiated QOS.

Range: 0 — 255

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

MaxSduSize_0_0

Gtp2MaxSduSize_0_0

Value	Description
0	Subscribed maximum SDU size
1— 150	Maximum SDU size in 10-octet increments (10 — 1500 octets)
151	1502 octets
152	1510 octets
153	1520 octets
154+	Reserved

Max Bit Rate for Uplink

Range: 0 — 255 (Use the conversion wizard or see Standard Values... for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

MaxBitrateUplink_0_0

Gtp2MaxBitrateUplink_0_0

Value	Description
0	Subscribed bit rate
1— 63	Maximum bit rate in 1 kbps increments (1 — 63 kbps)
64— 127	Maximum bit rate in 8 kbps increments (64 — 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)).
128— 254	Maximum bit rate in 64 kbps increments (576 — 8,640 kbps) calculated as (576 kbps + ((value - 128 kbps) * 64 kbps)).
255	0 kbps

Max Bit Rate for Downlink

Range: 0 — 255 (Use the conversion wizard or see Standard Values... for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

MaxBitrateDownlink_0_0

Gtp2MaxBitrateDownlink_0_0

Value	Description
0	Subscribed bit rate
1— 63	Maximum bit rate in 1 kbps increments (1 — 63 kbps)
64— 127	Maximum bit rate in 8 kbps increments (64 — 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)).
128— 254	Maximum bit rate in 64 kbps increments (576 — 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)).
255	0 kbps

Include Source Statistics Descriptor

Use the checkbox to include octets 14 — 16 in the QOS Information Element. When enabled, you can define the following attributes.

Source Statistics Descriptor — Indicates the source type.

Range: 0 — 15 (0 = unknown, 1 = speech)

Default: 0

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosSourceStatisticsDescriptor_0_0

Gtp2QosSourceStatisticsDescriptor_0_0

Signalling Indication — Indicates whether the PDP context is optimized for signalling traffic.

Range: 0 (not optimized) — 1 (optimized)

Default: 0

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosSignallingIndication_0_0

Gtp2QosSignallingIndication_0_0

Include Max/Guaranteed Bit Rate Downlink

Use the checkbox to include octets 15 and 16 when a downlink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 — 256,000 kbps) as (8600 kbps + (value * 100 kbps)).

The extended Max/Guaranteed Bit Rate Downlink fields will completely override the Max/Guaranteed Bit rate downlink/uplink, if they are set to anything other than 0.

Max Bit Rate for Downlink (extended)

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosMaxBitrateDownlinkExt_0_0

Gtp2QosMaxBitrateDownlinkExt_0_0

Guaranteed Bit Rate Downlink (extended)

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosGuaranteedBitrateDownlinkExt_0_0

Gtp2QosGuaranteedBitrateDownlinkExt_0_0

Related Measurements

Poorly Formed — The GGSN may reject a request with a 201 cause value when either or both extended bit rates are present but the corresponding non-extended bit rates are not 8,640 (254 parameter values).

Include Max/Guaranteed Bit Rate Uplink

Use the checkbox to include octets 17 and 18 when a uplink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 — 256,000 kbps) as (8600 kbps + (value * 100 kbps)).

Tcl Parameter: QosIncGbrdMbrdExt_0_0

Range: True or False

Default: False

The extended Max/Guaranteed Bit Rate Uplink fields will completely override the Max/Guaranteed Bit rate Uplink, if they are set to anything other than 0.

NOTE: If only the Downlink Extended QOS is Enabled, then the Uplink info is not sent in the messages. If only the Uplink Extended QOS is Enabled, both Uplink and Downlink QOS info are included in the message, with the Downlink values set to 0.

Max Bit Rate for Uplink (extended)

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosMaxBitrateUplinkExt_0_0

Gtp2QosMaxBitrateUplinkExt_0_0

Guaranteed Bit Rate Uplink (extended)

Range: 0 — 255 (Use the conversion wizard for rate/value conversion.)

Default: 1

Tcl ParameterTcl Parameter:

The Tcl Variable names for the QOS parameters are suffixed based on the Summary vs Individual setting and the number of context in a test.

With summary settings, everything is suffixed with _0_0.
With Individual, there are multiple tabs of parameters, each tab would have suffixes based on Primary/Secondary Context: _Primary_Secondary. For example,if there were 3 primarys and 2 secondary per primary, there would be:

_0_0 (Primary), _0_1 (secondary), _0_2 (secondary), _1_0, _1_1, _1_2, _2_0, _2_1, and _2_2.

QosGuaranteedBitrateUplinkExt_0_0

Gtp2QosGuaranteedBitrateUplinkExt_0_0