RP Tab Parameters
The RP tab is used to define the RP interface between the PCF nodes and a PDSN SUT in CDMA test cases. During eHRPD testing, the RP tab defines the RP interface between ePCF node and HSGW SUT.
When you use a mobility test activity, a second tab, Target RP, displays to define the PCF/ePCF/Target ePCF nodes and associated RP interface that is used for the handoffs.
The RP tab is available in the following test cases:
Parameter Index
|
General Settings |
|
|
|
Open RP Settings |
|
|
|
Flow Control |
|
|
|
Close RP Settings |
|
|
|
Service Instance Settings |
|
|
|
NVSE
|
|
|
|
Quality of Service
|
|
|
| eHRPD Settings | ||
|
Service Instance APN Assignments
|
|
|
Related Measurements
Measurements collected for RP related processing are reported on the Open RP report tab.
| RP Type | The RP Type radio button selects the RP protocol that is used in the test. The options available are Open and Closed RP. | ||||
| SUT Port Number |
The port number used for the RP interface on the SUT. Range: N/A Default: 699 Tcl Parameter: SutFaPort |
||||
| Node Port |
The port number used for the PCF Node address. Range: N/A Default: 699 Tcl Parameter: PcfNodeAddrPort |
||||
| Session ID Version |
Use the radio buttons to select the Session ID Version the PCF node requests that the PDSN uses. An equal or earlier (lower) version should be returned. If a later (higher) version is returned, the test will continue but the error counter will be incremented. Options: 0 or 1 Default: 0 Tcl Parameter: OpenRpPcfSessionId Related Measurements |
||||
| Starting PCF Session ID |
The starting PCF session ID to be used in establishing RP connections. This ID is incremented to provide a unique PCF Session ID for each service instance. Range: 1 — 65535 Default: 1 |
||||
| MS ID |
From the MS ID dropdown list, select the MS ID Type Options: IMSI (maximum 15 digits), MIN (maximum 10 digits) Default: IMSI Enter the Mobile Subscriber ID to be used in establishing RP sessions. The number of digits allowed is based on MS ID type (IMSI or MIN). Range: N/A Default: 300000 Tcl Parameter:
|
||||
| BS ID |
The Base Station ID to be used in establishing RP sessions. Range: N/A Default: bsid12 Tcl Parameter: RpBsid |
||||
| Open RP SPI |
The Security Parameter Index identifies a security context between two peers.
Range: N/A Default: 1000 (0 255 are reserved) Tcl Parameter: OpenRpSpi
|
||||
| Open RP Secret |
The password used to establish an RP tunnel. Range: N/A Default: secret Tcl Parameter: OpenRpSecret |
||||
| Lifetime |
The maximum number of seconds that a service instance is maintained without a re-registration request. 65535 indicates that the lifetime will not expire. Range: 1— 65535 Default: 65535 Tcl Parameter: OpenRpLifetime Related Measurements |
||||
| Redirection |
Select to allow the PDSN to specify an alternate PDSN within the Unknown PDSN response message. A registration request can be redirected to an alternate PDSN because the requested PDSN was in an overload condition. Redirection is indicated by a registration reply message with an error code of 136 (Unknown PDSN) that also provides an alternate PDSN IP address. On receipt, the PCF node attempts to register with the alternate PDSN using the IP address provided in the reply. Tcl Parameter: OpenRpRedirect Related Measurements |
||||
| Registration Timeout, Retries, Retry Interval, and Max Retry Interval |
Tcl Parameter:
See Retries. |
||||
| Re-registration Time |
The number of seconds prior to the expiration of the lifetime timer that a re-registration request is sent. Enter 0 to disable re-registrations. Range: 0 — 100 Default: 20 Tcl Parameter: RpRegistrationTime |
||||
| Protocol Type |
Use the radio buttons to select the type of link layer protocol/network layer protocol used by the MN Options: PPP(0x880b), Unstructured(0x8881) Default: Unstructured(0x8881)
|
||||
| Dormancy |
Use the checkbox to enable dormant session processing. In HSGW Nodal test case, Dormancy is not available when you select Partial Context Handoff HSGW Nodal Test Configuration tab (dormant handoff is not supported with partial context handoff).
Tcl Parameters:
When Dormancy is enabled, the following parameters are also available:
Range: 1 — 1000 Default: 300
Related Measurements |
||||
| ESN |
Use the checkbox to include the Electronic Serial Number, a unique identifier for the MN, in the message. Either ESN or MEID must be included. When enabled, the ESN field and the Enabled Fixed ESN checkbox are available. The ESN value that you enter will be incremented for every MN session unless you check the Enabled Fixed ESN box. Range: Up to 15 hexadecimal digits (do not enter "0x") Default: 0 Tcl Parameter:
|
||||
| MEID |
Use the checkbox to include the Mobile Equipment Identifier, a unique identifier for the MN, in the message. Either MEID, ESN, or both may be included. When enabled, the MEID field and the Fixed MEID checkbox are available. The MEID value that you enter will be incremented for every MN session unless you check the Fixed MEID box. Range: Up to 14 hexadecimal digits (do not enter "0x") Default: 0 |
||||
| Proprietary Extensions | See Proprietary Extension Settings. |
Flow Control
The Flow Control attribute is included at the GRE layer and is used by the PCF to notify the PDSN of the MN's ability to receive bearer plane traffic on a given service instance. The PCF sends an XOFF indicator to request that the PDSN suspend transmission of forward traffic or an XON indicator to request that the PDSN resume forward traffic. If the PCF determines that the condition is temporary, it can request that the PDSN buffer forward traffic until communications can be resumed.
Use the checkbox to include a cycle of Flow Control messages in your test. You can define a repeating cycle of XOFF and XON messages and specify the number of messages sent as well as the start and timing of the cycle. The Duration Indicator for XOFF messages is always "temporary" (0).
|
NOTES:
|
| Start Delay |
The number of seconds the test will wait, after a service instance is successfully established, before sending the first XOFF message. Range: 0 — 255 Default: 0 Tcl Parameter: OpenRpFcStartDelay |
| Duration |
The number of seconds from the time an XOFF is sent until the associated XON is sent. Range: 1 — 65535 Default: 1 Tcl Parameter: OpenRpFcDuration
|
| Cycle Delay |
The number of seconds from the time an XON is sent until the next XOFF is sent. Range: 1 — 65535 Default: 1 Tcl Parameter: OpenRpFcCycleDelay
|
| Number of consecutive XOFFs | In addition to the XOFF duration and the delay between cycles, you can specify the number of XOFF and XON messages that will be sent for each service instance. If you select multiple messages, you can define the number of messages and their spacing by message type. |
| Number of Consecutive XOFFs |
Use the radio buttons to select either a Single XOFF per service instance per cycle, or consecutive Multiple XOFFs. If you select multiple messages, define the number of messages in the field provided. Range: 2 — 255 Default: 2 Tcl Parameter: OpenRpFcXoffRep
|
| XOFF Delay |
The number of milliseconds between each XOFF message when Multiple XOFFs is selected. Range: 1 — 65535 Default: 1000 Tcl Parameter: OpenRpFcXoffDelay
|
| Number of Consecutive XONs |
Use the radio buttons to select either a Single XON per service instance per cycle, or consecutive Multiple XONs. If you select multiple messages, define the number of messages in the field provided. Range: 2 — 255 Default: 2 Tcl Parameter: OpenRpFcXonRep
|
| XON Delay |
The number of milliseconds between each XON message when Multiple XONs is selected. Range: 1 — 65535 Default: 1000 Tcl Parameter: OpenRpFcXonDelay
|
Related Measurements
Service Instance Settings
The Active Start Airlink Parameters, requested QOS, and some NVSE and TFT settings can be defined differently for each of an MS's service instances, and some values must be different for each service instance associated with one MS. When you include auxiliary service instances per subscriber in the test, you can either use common settings for all services instances by selecting the Summary button or customize the settings for each service instance by selecting the Individual button.
When you select Individual, one sub-tab is provided for MS's Main service instance, sub-tabs are provided for the number of auxiliary service instanced defined (Aux-n), and Fill Session Reference is enabled. For individual settings, the same values are used for every MS's main service instance, for every MS's first auxiliary service instance, and so on.
| NOTE: The number of Aux tabs defined corresponds to the value you select in Auxiliary Service Instances per Subscriber on the Mobile Subscriber pane of the Test Configuration tab. |
| TIP: The Main tab is responsible for creating the default PDN connection and GRE Key Information Service Option value of SO59 is responsible for creating additional PDN connections. |
When you select Summary, the identifiers that must be unique among MS's service instances are automatically incremented by the test.
| Fill Session References | When Individual settings for each service instance are selected, you can click Fill Session References to automatically provision MN Session Reference Number with a unique value in each sub-tab. |
|
Active Start Airlink Parameters You can define the following parameter values that will be sent in the Active Start Airlink record. The RN generates an Active Start Airlink Record over RP interface when the MS has connected to the associated over-the air service instance. |
|
|
The reference ID of the service instance. This value must be unique for each service instance. You can automatically provision the values in Individual settings with Fill Session Reference. Range: 0 — 255 Default: 1 |
|
| User Zone |
The unique identification number for the User Zone, which is made up of the User Zone ID and User Zone System ID. User Zone ID is used over the air interface to identify the zone to the network and the MN, and the System ID provides the System Identifier (SID) associated with the zone. Range: The least significant 16 bits of the 32-bit field are the User Zone ID, the next significant 15 bits are the SID, and the most significant bit is 0. Default: 0 |
| DCCH Frame Size |
The Dedicated Control Channel frame size. Range:
Default: 0 |
| Air Link QOS |
The Air Link Priority associated with the MN for packet data service. Range: The least significant bits of the 32-bit field hold the priority. Default: 0 |
| Forward MUX Option |
Forward multiplex option. Range: N/A Default: 1 |
|
Fund Frame Size |
Specifies the Fundamental Channel Frame Size Range:
Default: 2 |
|
Forward Fund RC |
The format and structure of the radio channel in the forward Fundamental Channel. A set of forward transmission formats that are characterized by data rates, modulation characterized, and spreading rates. Range: N/A Default: 1 |
|
Reverse FUND RC |
The format and structure of the radio channel in the reverse Fundamental Channel. A set of reverse transmission formats that are characterized by data rates, modulation characterized, and spreading rates. Range: N/A Default: 1 |
|
Forward Traffic Type
|
Forward direction traffic type – either Primary or Secondary. Range: 0 — Primary 1 — Secondary Default: 1 |
|
Reverse MUX Option |
Reverse multiplex option. Range: N/A Default: 1 |
|
Reverse Traffic Type |
Reverse direction traffic type – either Primary or Secondary. Range:
Default: 1 |
|
Service Option |
Service option as received from the RN. Range: N/A Default: 33 |
|
Forward PDCH RC |
The Radio Configuration of the Forward Packet Data Channel. (This parameter can be used as an indication that the MS is 1xEV DV capable.) Tcl Parameter: OpenRpFpdchRc2_1 |
|
Reserve PDCH RC |
The Radio Configuration of the Reverse Packet Data Channel. (This parameter can be used as an indication that the MS is 1xEV DV capable.) Tcl Parameter: OpenRpRdcchRc2_1 |
|
Forward DCCH Mux Option |
Forward Dedicated Control Channel multiplex option Tcl Parameter: OpenRpFdcchMo2_1 |
|
Reverse DCCH Mux Option |
ReverseDedicated Control Channel multiplex option Tcl Parameter: OpenRpRdcchMo2_1 |
|
Forward DCCH RC |
The format and structure of the radio channel in the forward Dedicated Control Channel. A set of forward transmission formats that are characterized by data rates, modulation characterized, and spreading rates. Tcl Parameter: OpenRpFdcchRc2_1 |
|
Reserve DCCH RC |
The format and structure of the radio channel in the reverse Dedicated Control Channel. A set of reverse transmission formats that are characterized by data rates, modulation characterized, and spreading rates. Tcl Parameter: OpenRpRdcchRc2_1 |
NVSE Settings
| Include NVSE Service Option | Use the checkbox to include the Service Option NVSE in RRQ messages. This element is mandatory whenever auxiliary service instances per subscriber are included in the test. | ||||||
| NVSE QOS Mode |
Use the checkbox to include the QOS Mode Session Parameter NVSE in RRQ messages, and enter the value in the field provided. A value of 0 indicates that QOS is disabled and 1 indicates that QOS is enabled. Range: 0 — 255 Default: 1 |
||||||
| GRE Segmentation Enabled |
Use the checkbox to include the GRE Segmentation Enabled in RRQ messages. Tcl Parameters:
|
Requested QOS Settings
You can define the RAN QOS resources requested by the MN for its service instances.
| Flow ID |
The identifier of the packet filter for the service instance's TFT. The PDSN will use the identifier supplied by the MN. Range: 0 — 255 Default: 255 |
| Flow Priority |
The priority requested for the IP flow, which is validated against the mobile subscriber's profile. Range: 0 (lowest) — 255 (highest) Default: 15 |
| DSCP |
Use the checkbox to include the Differentiated Service Code Point (DSCP) requested for differentiated services marking. The PDSN must ensure that the MN only uses valid DSCP values based on the mobile subscriber's profile or on network policy, and may re-mark packets with inappropriate DSCP values. Enter 0 for Default Forwarding (best effort) or see the IANA DSCP Registry for Class Selection, Assured Forwarding, and Expedited Forwarding pool values. Range: 0 — 63 Default: 0 |
| Profile ID |
The application that will be using the IP flow. Range:
Default: 1 |
APN Assignments
The Service Instance APN Assignments settings is associated with that in Service Instance Settings. That is, they correspond to each other on one-to-one basis.
-
See Setting Up a HSGW Nodal Test for details one-to-one mapping of auxiliary connections on the Service Instance Settings pane and PDN connections on the Service Instance APN Settings pane.
|
Total APNs |
The maximum number of APN values that will be generated for the contexts, including both incrementing values and manually-defined values. Range: Variable (total APNs >= Number of Default Bearers) Default: 1 Tcl Parameter: OpenRpApnTotalApns_0 |
|
| Starting Auto-Incrementable APN |
The format used to generate incrementing APN values. See the Auto-Increment section in Parameter Types and Features for more information incrementing formats and methods. Range: N/A Default: ssenoauth146 Tcl Parameter: OpenRpApn_0
|
|
| Retries |
The number of times the PDP context will attempt to be activated if the first attempt did not succeed. When you enable Retries, each retry attempt will use the next APN value in the list if you have defined multiple APN values. Range: Variable (limited by the maximum number of PDP contexts) Default: 0 (retries are disabled) Tcl Parameter: OpenRpApnRetries_0 Related Measurements |
|
| Manually Specify First |
Use the drop-down list to select the number of APN values that you will manually define. The appropriate number of value fields (APN 0 — APN 10) are enabled based on your selection. The values that you define in these fields will always be used first when you select Round Robin mode. Tcl Parameter: OpenRpApnNumSpecifiedApns_0
|
|
| Round Robin |
Select to enable round-robin APN assignment. When you define multiple APN values, the first value in the list is assigned to the first context, the second value is assigned to the second context, and so on. Manually-defined values are always selected first and when that list is exhausted, incrementing values are used. After the test has cycled through the total number of APNs, the next context is assigned the first APN value in the list. A context will use the same APN through the life of the test as long as the context can be successfully established using that APN. In a Session Loading test, for example, a new APN is not obtained every time the context is re-established. NOTE: Round Robin is not available on GTPv2 tab for all LTE Nodal and Node test cases (MME, SGW, PGW, and HSGW).
Tcl Parameter: OpenRpApnRoundRobin_0
|
|
| PDP Type |
Indicates the requested packet data protocol type. Available when the GRE Key Information Service Option in the eHRPD Setting panel is SO59. Tcl Parameter: OpenRpApnPdnType_0
|
Protocol Configuration Options
Protocol Configuration Options (PCO) is transferred via GTP tunnels. The sending entity copies the value part of the PCO into the Value field of the PCO IE. The protocol configuration options information element is used to:
-
Transfer external network protocol options associated with a PDP context activation, and
-
Transfer additional (protocol) data (e.g. configuration parameters, error codes or messages/events) associated with an external protocol or an application.
|
NOTE: The PGW Node test case, you may select IP Control Protocol and enter the Primary/Secondary DNS addresses. |
The Protocol Configuration Options in all LTE test cases support configuration of username/password for authentication to the PGW. Use the radio buttons to select an authentication method.
Options: No Authentication, PAP Authentication, CHAP Authentication
Default: No Authentication
When you select Include PAP Authentication, you can define the password and peer ID.
|
NOTE: These values must be configured to match the PAP Peer ID and Password expected by the PDN GW/GGSN. |
-
Password defines the password to be used for PAP authentication. This may be the subscriber's password.
Range: N/A
Default: Secret
-
Peer ID defines the peer to be used for PAP authentication. A unique ID can be supplied for each context by using the Auto-Increment feature. This value may be the subscriber's user name, and the GGSN may or may not use a DNS or AAA server to validate this field.
Range: N/A
Default: Secret
Tcl Parameters:
|
Gtp2PcoPapPassword |
Gtp2PcoPapPeerId |
Gtp2IncPcoOpt |
When you select Include CHAP Authentication, you can define the fields that are used to build the CHAP ID field. The field is coded as a CHAP response, and is not checked by the GGSN. The GGSN sends this value to a RADIUS server in an Access Request message.
|
NOTE: This must be configured to match the expected CHAP ID at the RADIUS server. |
-
Identifier defines the CHAP identifier to be used for CHAP authentication.
Range: 0 — 255
Default: 0
-
Name defines the subscriber's user name to be used for CHAP authentication. A unique name can be supplied for each PDP context by using the Auto-Increment feature.
-
Range: N/A
Tcl Parameter: MSName
-
Secret defines the secret used by both the client and server in the MD5 calculation.
Range: N/A
Default: secret
-
CHAP Challenge Value defines the CHAP value, in hex, to be used for CHAP authentication.
Range: 0-F characters
Default: ABCD
Tcl Parameter:
Gtp2PcoChapId
Gtp2PcoChapName
Gtp2PcoChapSecret
Gtp2PcoChapChallengeValue
Related Measurements
IP Control Protocol
During HSGW, SGW, and PGW Nodal testing, select IP Control Protocol to include the protocol configuration options (PCO) IEs in the Create PDP Context Request. In PGW Node test case, only IP Control Protocol is available for selection.
-
-
NOTE: Multiple protocol configurations are included in a single PCO. Tcl Parameter: Gtp2PcoIpcpEn
Type: True/False
Default: False
Select IP Control Protocol and then enter IPCP IP Address, primary and secondary addresses for WINS and DNS servers. You may enter IPv4 or IPv6 addresses, as required.
-
NOTE: In PGW Node test case, enter only IP Control Protocol Primary and Secondary DNS address.
Type: True/False
Default: False
Tcl Parameters:
|
Gtp2PcoIpcpIpAddrEn |
Gtp2PcoIpcpIpAddr |
|
Gtp2PcoIpcpPrimDnsEn |
Gtp2PcoIpcpPrimDnsAddr |
|
Gtp2PcoIpcpPrimWinsEn |
Gtp2PcoIpcpPrimWinsAddr |
|
Gtp2PcoIpcpSecDnsEn |
Gtp2PcoIpcpSecDnsAddr |
|
Gtp2PcoIpcpSecWinsEn |
Gtp2PcoIpcpSecWinsAddr |
Additional Parameters
Selecting Additional Parameters allows you to further select P-CSCF IP Address request, DNS address request, DHCP address allocation request, IM CN flag request, MSISDN request, etc as part of PCO IE.
Type: True/False
Default: False
Tcl Parameter: PcoAddEn
Tcl Parameter: NasAddEn
Tcl Parameter: Gtp2PcoAddEn
|
NOTE: The P-CSCF is the entry point to the IMS domain and serves as the outbound proxy server for the UE. The UE attaches to the P-CSCF prior to performing IMS registrations and initiating SIP sessions. The P-CSCF may be in the home domain of the IMS operator, or it may be in the visiting domain, where the UE is currently roaming. For attachment to a given P-CSCF, the UE performs the P-CSCF discovery procedures. Attachment to the P-CSCF is necessary for the UE for initiating IMS registrations and sessions. In these procedures, the UE first establishes the IP connectivity access network (IP-CAN) bearer. Then, the UE sends a query to the DHCP server for retrieving the IP addresses and FQDN (Fully Qualified Domain Name) of the P-CSCF. After the DHCP query, the UE performs a DNS query on the FQDN received from the DHCP server. In response to the DNS query, the IP address of the P-CSCF is returned (referred as the DHCP-DNS procedure for P-CSCF discovery). If the FQDN of the P-CSCF is pre-configured in the UE, the UE can directly query the DNS server and get the IP address of the P-CSCF. |
The following are enabled only when you select Additional Parameters:
|
P-CSCF IPv4 Address Request |
Select to indicate that UE requests a P-CSCF IPv4/IPv6 address(es). |
|
|
P-CSCF IPv6 Address Request |
||
|
DNS Server IPv4 Address Request |
Select to indicate that the UE performs a DNS query to retrieve a list of P-CSCF(s) IPv4/IPv6 addresses. |
|
|
DNS Server IPv6 Address Request |
||
|
IPv4 Address Allocation Request via NAS Signaling |
Applicable in HSGW, MME, PGW and SGW Nodal test cases. Select to indicate dedicated signalling PDP context for NAS signalling. If not selected, the network considers the PDP context as a general purpose PDP context. |
|
|
IPv4 Address Allocation Request via DHCPv4 |
Select to indicate that the UE requests a DHCP server IPv4 address allocation. |
|
|
IM CN Subsystem Signalling Flag Request |
Select to indicate the dedicated signalling PDP context for IMS signalling. If UE does not include the IM CN subsystem Signalling flag, the network will consider the PDP context as a general purpose PDP context. |
|
|
MSISDN Request |
Select to indicate request user MSISDN. |
|
|
IPv4 Link MTU Request |
Select to indicate request for IPv4 Link MTU. Only applicable to PDU/PDN type IPv4 or IPv4v6. |
|
|
MS Support of Network Requested Bearer Control Indicator |
Select to indicate that the UE supports network requested bearer control, e.g. network initiated QoS. |
|
|
MS Support of Local Address in TFT Indicator |
Select to indicate support of local address in TFT on the UE side. |
|
|
QoS Rules with Length of Two Octets Support Indicator |
Select to indicate support of QoS rules with the length of two octets on the UE side. |
|
|
QoS Flow Descriptions with Length of Two Octets Support Indicator |
Select to indicate support of QoS Flow Descriptions with the length of two octets on the UE side. |
|
|
DNS Server IPv4 Address |
Select to enter the DNS Server IPv4 address. |
|
|
DNS Server IPv6 Address |
Select to enter the DNS Server IPv6 address. |
|
|
P-CSCF IPv4 Address |
Select to enter the P-CSCF IPv4 address. Used in PGW/SGW Node stand alone tests. If selected, PGW Node will send this IP address to UE in even Number restoration events (e.g. 2nd, 4th, etc.) |
|
|
P-CSCF IPv6 Address |
Select to enter the P-CSCF IPv6 address. Used in PGW/SGW Node stand alone tests. If selected, PGW Node will send this IP address to UE in even Number restoration events (e.g. 2nd, 4th, etc.) |
|
|
Secondary P-CSCF IPv4 Address |
Enabled if P-CSCF IPv4 Address is enabled. Select to support a secondary P-CSCF V4 Address. Supported in PGW Node/GGSN Node. |
|
|
Secondary P-CSCF IPv6 Address |
Enabled if P-CSCF IPv6 Address is enabled. Select to support a secondary P-CSCF V6 Address. Supported in PGW Node/GGSN Node. |
|
|
Restoration P-CSCF V4 Address |
Enabled if P-CSCF IPv4 Address is enabled. Select to support P-CSCF Restoration Procedure. Enter Address. If selected, PGW Node will send this IP address to UE in odd Number restoration events (e.g. 1st, 3rd, etc.) |
|
|
Restoration P-CSCF V6 Address |
Enabled if P-CSCF IPv6 Address is enabled. Select to support P-CSCF Restoration Procedure. Enter Address. If selected, PGW Node will send this IP address to UE in odd Number restoration events (e.g. 1st, 3rd, etc.) |
|
|
P-CSCF Reselection Support |
Applicable in MME Nodal test cases. If selected, UE will include P-CSCF Restoration Support flag along with P-CSCF IPv4 or P-CSCF IPv6 in PCO-PDN Connectivity Request Message.
|
|
|
PDU Session ID |
Applicable in MME Nodal test case when NAS Version >= 15.5.0. If selected, the PDU Session Id will be included in PCO or ePCO IE for Attach and PDN Connectivity procedures. Enter the PDU Session Id. Range : 1 to 15. Default : 5 |
Tcl Parameters:
|
PcoAddCscfv4ReqEn |
PcoAddDnsv4ReqEn |
PcoAddImcnFlgReqEn |
|
PcoAddCscfv6ReqEn |
PcoAddDnsv6ReqEn |
PcoAddMsisdnReqEn |
|
PcoAddCscfv6ReqEn |
PcoAddIpAllDhcpv4En |
PcoAddIpAllNasEn |
|
Gtp2PcoAddCscfv4ReqEn |
Gtp2PcoAddDnsv4ReqEn |
Gtp2PcoAddImcnFlgReqEn |
|
Gtp2PcoAddCscfv6ReqEn |
Gtp2PcoAddDnsv6ReqEn |
Gtp2PcoAddMsisdnReqEn |
|
Gtp2PcoAddCscfv6ReqEn |
Gtp2PcoAddIpAllDhcpv4En |
Gtp2PcoAddIpAllNasEn |
|
Gtp2PcoAddDnsv4 |
Gtp2PcoAddDnsv6 |
Gtp2PcoAddCscfv4 |
|
Gtp2PcoAddCscfv6 |
Gtp2PcoAddRestoreCscfv4 |
Gtp2PcoAddRestoreCscfv6 |
|
Gtp2PcoAddSecCscfv4En |
Gtp2PcoAddSecCscfv4 |
|
|
Gtp2PcoAddSecCscfv6En |
Gtp2PcoAddSecCscfv6 |
|
|
NasPcoAddCscfv4ReqEn |
NasPcoAddDnsv4ReqEn |
NasPcoAddImcnFlgReqEn |
|
NasPcoAddCscfv6ReqEn |
NasPcoAddDnsv6ReqEn |
NasPcoAddMsisdnReqEn |
|
NasPcoAddCscfv6ReqEn |
NasPcoAddIpAllDhcpv4En |
NasPcoAddIpAllNasEn |
|
NasPcoAddCscfReselectEn |
NasPcoPduSessionIdEn_1 |
NasPcoPduSessionId_1 |
|
NasPcoAddDnsv4 |
NasPcoAddDnsv6 |
NasPcoAddCscfv4 |
|
NasPcoAddCscfv6 |
NasPcoAddRestoreCscfv4 |
NasPcoAddRestoreCscfv6 |
In MME Nodal, SGW Nodal, and UMTS test cases, the Protocol Configuration Options > Additional Parameters are available for both client and server settings depending on your selection on the Test Configuration tab. Also, the individual parameters available on the server address pane depends on the corresponding address you select on the client address pane.
|
Test Case |
Client Address Parameters (Protocol Configuration Options > Additional Parameters) |
Server Address Parameters (Protocol Configuration Options > Additional Parameters) |
Tcl Parameter Prefix |
|
GGSN Nodal |
Gn | IPv4 Protocol Configuration Options > Additional Parameters |
N/A |
No Prefix |
|
HSGW Nodal |
RP | RP Protocol Configuration Options > Additional Parameters |
N/A |
Prefixec with Ppp |
|
PGW Nodal |
S5/S8 | GTPv2 Protocol Configuration Options > Additional Parameters |
N/A |
Prefixed with Gtp2 |
|
MME Nodal
|
S1-MME | NAS > Protocol Configuration Options > Additional Parameters |
Only when you select SGW/PGW Node Emulation on the MME Nodal Test Configuration tab: S11 | GTPv2 > Protocol Configuration Options > Additional Parameters are visible when you enable the associated checkbox on the S1-MME>NAS>Per Bearer APN/PCO Settings>Protocol Configuration Oprtions>Additional Parameters panel. |
Prefixed with Nas |
|
Tgt Iu-PS/Gb | SM > Protocol Configuration Options > Additional Parameters |
N/A |
No Prefix |
|
|
Gn to GGSN | IPv4 > Protocol Configuration Options > Additional Parameters |
N/A |
No Prefix |
|
|
SGW Nodal |
S11 | GTPv2 > S11 Protocol Configuration Options > Additional Parameters |
Only when you select PGW Node Emulation on the SGW Nodal Test Configuration tab: S11/S5 | GTPv2 > S5 Protocol Configuration Options >Additional Parameters are visible |
Prefixed with Gtp2 |
|
Gn | IPv4 > S11 Protocol Configuration Options > Additional Parameters |
N/A |
No Prefix |
|
|
UMTS |
Iu-PS/Gb | SM Protocol Configuration Options > Additional Parameters |
Only when you select GGSN Node Emulation on the UMTS Test Configuration tab: Gn | GTP > Protocol Configuration Options > Additional Parameters are visible |
No Prefix |
eHRPD Settings
Closed RP Settings
Tunnel Name
The Host Name AVP used during tunnel establishment. It is included in the SCCRP sent from a Security Gateway to a SUT (CDMA2000 and GPRS test cases).
Tcl Parameter: ClosedRpTunnelName
Tunnel Connect Rate
The rate, in tunnels per second, at which the test will attempt to establish tunnels.
Tcl Parameter: TunnelConnectRate
Tunnel Disconnect Rate
The rate, in tunnels per second, at which the test will attempt to tear down established tunnels.
Tcl Parameter: TunnelDisconnectRate
Receive Window Size
The Receive Window Size AVP used during Close RP tunnel establishment, indicating the number of control messages that a peer may send before waiting for an acknowledgment. It is included in the SCCRP sent from a Security Gateway to a SUT (CDMA2000 and GPRS test cases).
Tcl Parameter: RcvWindowSize
Hello Timeout (s)
The number of times a "hello" message is sent without receiving any response before the number of timer expires.
Tcl Parameter: RpHelloTimeout
Restart Retry Timer
Select this checkbox to enable restarting the retry time.
Tcl Parameter: RpRestartRetry
Apply Parameters from Test Data File
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.
|
||
|
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).
|
||
|
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.
|
||
|
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 |
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. |
View TDF Actions/Options Menu)