PDN Contexts
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

PDN Contexts

The PDN Context tab is used to define multiple Subscriber Groups, PDN Contexts and QoS Profiles to provision each Subscriber Group with unique APN/PDN Contexts.

PDN Contexts

Context Tab

Quality of Service

       
 

Related Measurements

Measurements collected for HSS related processing are reported on the HSS Node report tab.

NOTE: When PDN Contexts is used  to define PDN Contexts and QoS Profiles in the SMS-HLR Interface (from SMS Network test case), the TCL variables with have a prefix of "SmsHlr" in palce of "HssSrv".
Subscriber Groups and APN/Context Assignment

Specify the number of Subscriber Groups to provision multiple sets of IMSIs, each with unique APN/PDN Contexts. You may define a maximum of 100 Subscriber groups.

Tcl Parameter: HssSrvPdnApnSubscriberGroupCount

NOTE: Each Subscriber group can be assigned a maximum of 32 PDN Contexts/APNs.

Subscribers in Group

Define Subscribers in Group to provision unique APN/PDN Contexts. Enter the range of Subscribers that should include unique APNs/Contexts (1 to the maximum subscribers)

Tcl Parameter:

HssSrvPdnApnSubscriberGroup[n]Start   start of subgroup n

HssSrvPdnApnSubscriberGroup[n]End   end of subsgroup n
PDN Contexts/APN

For example, If you configure PDN Context 1/APN 1 with subscribers ID Range 1-100, 300-500, 900-1000, then the 1/APN 1 is included only for the subscribers starting from 1 to 100,  300 to 500, and 900-1000.

Tcl Parameter: HssSrvPdnApnSubscriberGroup1Apns

(HssSrvPdnApnSubscriberGroup[n]Apns  { ... } - assigned PDN Context Indexes to subgroup n)

NOTE: When Subscribers in Groups are defined, the APN/PDN Contexts are  provisioned for all subscribers.

^ Back to Top

Contexts

Max APN Mode via TDF

Select to define a maximum of 300 PDN Contexts. When you select this option, you may define only one APN in the GUI and use the TDF to apply the parameter values to the rest of the APNs. Include TDF as required.

NOTE: Max APN allows you to define up to 300 Contexts, made unique via TDF and APN Name auto-incrementing. When not using APN Mode, you can define up to 30 Contexts via the GUI. Click  next to APN to use the Auto-Increment Format Wizard.

 

Tcl Parameter: HssSrvPdnMaxModeEn
Number of Contexts

Use the drop-down list to select the Number of contexts to be established for the HSS Server.

Options:  1— 30

Default: 1

Tcl Parameter: HssSrvNumContexts

NOTE: The number of Context tabs depend on the value you select in the Number of contexts checkbox.
IMPORTANT: When you configure a lot of information (for example, configure 8 PDN Contexts), the outgoing data becomes too big to fit in a single SCCP message and as a result, data will be subdivided and delivered as multiple SCCP messages. In such cases, you are required to include IMSI in SCCP routing information to assist the receivers of multiple SCCP messages to merge the received data.

 
Allow Dynamic VPLMN

Use the checkbox to allow the PDN context to derive a PDN GW identity from the visited PLMN. This parameter is available only if PDN Contexts is greater than 0.

Tcl Parameter: HssSrvDynamicVplmn

Values: 0 or 1 (0 = disabled, 1=enabled)
Context Tab

APN

Enter the APN value assigned to PDP context. Enter up to 50 characters. "." and "-" are allowed. 

Click to use the Auto-Increment Format Wizard. Available when Max APN Mode via TDF is not enabled.

Tcl Parameter: HssSrvPdnApn_1

APN Network Identifier

Enter the APN Network Identifier.

Tcl Parameter: HssSrvPdnNtwkId_1

PDN Type

Use the dropdown list to select the address type of PDN. When you select the IPv4 or IPv6 option, the V4 and V6 radio buttons become available and V4 is selected by default.

Options: IPv4, IPv6, IPv4 and IPv6, IPv4 or IPv6 and Non-IP

Default: IPv4

Tcl Parameter: HssSrvPdnType_1

Include Operator APN Identifier

Select Include Operator APN Identifier and configure the Operator Identifier.

Type: True/False

Default: False

Tcl Parameter:

HssSrvPdnOperatorApnIdEn_1

HssSrvPdnOperatorApnId_1

Range: 1 - 127 characters

Default: APN ID<1-based tab suffix>

QOS Class

Select to assign the QoS Profile Index to the PDN Contexts (references to the QOS Profile Index via the QosClass_[PDN Index] ).

Tcl parameter: HssSrvPdnQosClass_1

(HssSrvPdnQosClass_[PDN_INDEX])

You may also change the assigned QOS Profile/Class Runtime.

3GPPCharging Characteristics

Use this checkbox to enable the type of charging for which the PDN context is liable. Select from one of 16 charging profiles that may be configured on the SGSN. You can either use the same charging characteristics for all PDN contexts or enter a different charging profile for each context.

See table of Charging Profiles.

Range: 0 - 65535

Default: 0 (indicates that it is not used)

Tcl Parameter:

HssSrvPdnChgCharacteristicsEn

HssSrvPdnChgCharacteristics

PDN-GW Address

Select PDN-GW Address and enter the relevant IP address for the PDN context.

Tcl Parameter: HssSrvPdnPgwAddrEn_1

Starting Served-Party Address

Holds the PDN IP Address of the user.

Select the Served Party Address checkbox to enter the relevant IP address for the PDN context.

NOTE: In HSS Node test, the Starting Served-Party Address is used to indicate either static or dynamic allocation of UE IP.

Tcl Parameter: HssSrvPdnSpAddrEn_1

IPv4/IPv6 Address

Enter valid IP addresses for the PDN context. You can either use the same IP address for all PDN contexts or enter a different address for each context. The address available depends on the PDN Type you selected.

Tcl Parameter:

HssSrvPdnSpV4Addr_1

HssSrvPdnPgwV4Addr_1

HssSrvPdnSpV6Addr_1

 HssSrvPdnPgwV6Addr_1

Aggregate Maximum Bit Rate: UL,  DL in Bps

Select the checkbox to define different Aggregate Maximum Bit Rate for each IP context. Enter the appropriate Class ID and define the IP flow Aggregate Maximum Bit Rate for UL and DL traffic in bps.

Range = 0 to 4294967295

Default value = 0

Tcl Parameter:

HssSrvPdnAmbrEn_1

HssSrvPdnAmbrMaxDlBps_1

HssSrvPdnAmbrMaxUlBps_1

PDN-GW ID

Select the PDN GW ID and enter the origin host and realm of the PDN context. You can either use the same host and realm for all PDN contexts or enter a different address for each context.

  • Host: Depending on whether the node emulates originating or destination point, Host identifies the endpoint that originated the PDN context or Identity of the destination host.

  • Realm: Depending on whether the node emulates originating or destination point, Realm identifies the realm of the originator of any PDN context or the realm the message is to be routed to.

Tcl Parameter:

HssSrvPdnPgwIdEn_1

HssSrvPdnPgwOriginHost_1

HssSrvPdnOgworiginRealm_1

PDN Gateway Allocation Type

Indicates whether the allocated PDN-GW Address is Dynamic or Static. Select as required.

Tcl Parameter: HssSrvPdnPgwGwAllocType_1

Non-IP Data Delivery Mechanism

Available if PDN-Type = Non-IP.

Options: SGi Based Data Delivery

Tcl Parameter: HssSrvPdnNonIpMechType_1

Include Interworking 5GS Indicator

Select to include the Interworking 5GS indicator, Select Subscribed or Not Subscribed. Currently not supported in SMS Network test case under SMS-HLR interface.

HssSrvPdnItwk5gsIndEn_1

HssSrvPdnItwk5gsInd_1

 

Include Wildcard

Select to Enable Wildcard APN. The default wildcard value will depend on the PDN Context number. This will include the wildcard value per 3GPP TS 23.003 (3) (9.1.2) and 3GPP TS 23.008 (30) (2.13.6).

All APNs and associated PGW-ID pairs stored in the HSS not associated with an explicit APN subscription, (i.e. The access to that APN has been authorized as a consequence of having Wildcard APN in the user subscription), shall be included by the HSS inside the APN Context of the wildcard APN, as multiple instances of the Specific-APN-Info AVP.

Currently not supported in SMS Network test case under SMS-HLR interface.

Tcl Parameter:

HssSrvPdnWildcardEn_1

HssSrvPdnWildcard_1

Specify Subscribers

Select Specify Subscribers to provision multiple sets of IMSIs, each with unique APN. Enter the range of Subscribers that should include unique APNs (1 to the maximum subscribers)

For example, If you configure APN Context 1 with subscribers ID Range 1-100, 300-500, 900-1000, then the APN Context 1 is included only for the subscribers starting from 1 to 100,  300 to 500, and 900-1000.

NOTE: When Specify Subscribers is not selected, the APN is provisioned for all subscribers.

 

^ Back to Top

QoS Classes

The MME/SGSN needs the QOS information PDN Context basis for IP packet Uplink and Downlink. The MME/SGSN ensures that the granted QOS does not exceed the Authorized QoS per IP flow. The authorized bit rate/sec is defined separately for Uplink and Downlink packet flow.

Number of QoS Classes

Indicates the number of QoS Profiles defined. You may define a maximum of 15 QOS Profiles. The number of QoS Class tabs displayed depends on the Number of QoS Classes value you select.

The QoS Profile defined is assigned and referenced by the PDN Contexts (references a QOS profile by index).

Tcl Parameter: HssSrvPdnQosCount

Class n

NOTE: QOS variable names are suffixed by their QOS Profile index.
Include QoS Class ID

Available only when Number of Contexts is > 0. Select to enable and enter the QOS Class ID that defines the maximum authorized traffic class for the IP-CAN bearer or service flow.  You may also select and define the associated ARP value.  

Select QoS Class ID and enter the required QOS Class ID  

Valid Options: 0 - 255

Default: 1

Tcl Parameter:

HssSrvPdnQosEn_1

HssSrvPdnQci_1

Type: True/False
ARP Value

Available when select QoS Class ID. Use the ARP (Allocation and Retention Priority) to determine the relative priority level during admission and congestion processes. You may also select Pre-emption Capability and Vulnerability.

Valid Options: 1 - 15

Default: 1

Tcl Parameter:

HssSrvPdnArpEn_1

HssSrvPdnArpValue_1

  • Pre-emption Capability: Select to indicate that the PDN Context may preempt other context with a lower ARP value when resource limitations are reached.

  • Pre-emption Vulnerability: Select to indicate that a context is vulnerable to being dropped when resource limitations have been reached and there is a context with a higher ARP value in service.

QoS Profile is available irrespective of the Number of Contexts and QoS Class ID selection. Currently not supported in SMS Network test case under SMS-HLR interface.

See also QoS ProfileQoS Profile

 

Reliability Class

Range: 0 — 7

Default: 1

Tcl ParameterTcl Parameter: QosReliability_1

Where applicable, 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 Parameter: QosDelay_1

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 Parameter: QosPeakThruput_1

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 Parameter: QosMeanThruput_1

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 Parameter: DeliveryOrder_1

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 Parameter: QosTransferDelay_1

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 Parameter: QosTrafficPriority_1

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 Parameter: QosGuaranteedBitrateUplink_1

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 Parameter: QosGuaranteedBitrateDownlink_1

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 Parameter: QosErrorSdu_1

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 Parameter: QosAllocPriority_1

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 Parameter: QosSduRatioError_

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 Parameter: QosResidualBer_

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 Parameter: QosResidualBer_1

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 Parameter: TrafficClass_1

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 Parameter: MaxSduSize_1

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 Parameter: MaxBitrateUplink_1

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 Parameter: MaxBitrateDownlink_1

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 Parameter: QosSourceStatisticsDescriptor_1

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 Parameter: QosSignallingIndication_1

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 Parameter: QosMaxBitrateDownlinkExt_1

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 Parameter: QosGuaranteedBitrateDownlinkExt_1

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

QosIncGbrdMbrdExt_1

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 Parameter: QosMaxBitrateUplinkExt_1

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 Parameter: QosGuaranteedBitrateUplinkExt_1

QosGuaranteedBitrateUplinkExt_0_0
Gtp2QosGuaranteedBitrateUplinkExt_0_0

 
Apply Test Data File to Context File

The parameter is avaialble only when you select Max APN Mode via TDF. You can provision explicit values for each PDN Context/APN by using a Test Data File.

See Applying Parameter ValuesApplying Parameter Values.

See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). 

For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: 

Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.

TIP: When including large files, please be aware of memory limitations, since the TDF Editor shares memory with the Client.

NOTE: The available TDF options vary. on the L3-7 | IPSec tab > IKE with RSA Settings you may only select the Certificate TDF from TAS (these are non-CSV TDFs).

In addition, where applicable, any rules for defining TDFs are included in specific Test Cases. (For example, In MME Node test case, see MME Node - Provisioning TDF.)

From the DMF Window, press Shift+Alt+A to display the  Save DMF as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

 

Select/Create a new TDF-CSV

Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists.

Click to open the Select Existing or Create window.

  • Navigate to the relevant library/folder,

  • Enter the name of the file:

  • If the file name already exists, the file is selected and applied in the test case.

  • If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched.

    • Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV.

    • Click No to select a different file

NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file.
TIP: You may also navigate to the relevant library/folder and select file, and click OK.

 

Upload a New TDF to TAS

Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin).

  • Navigate to the file on your local folder and select.
  • Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.  

View Edit Selected TDF in TDF-CSV Editor

Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case).

Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required.

NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name.

The only options available are Save As and Cancel.

Open Selected TDF in Standalone TDF-CSV Editor

Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.

Generate Stub TDF-CSV

TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)

 

Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.

 

Launch Standalone TDF-CSV Editor

Click to open a blank TDF-CSV Editor.

The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor.  You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

 

Tcl Parameter: HssSrvPdnContextCfgFile  

 

 

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.