SM Tab

Measurements collected for Iuh interface in HNB testing, radio and transport related processing are reported on the SM, RUA, HNBAP, RANAP, HNB Node and SCCP report tabs.

General

Defines attributes used in PDP context requests sent from the MNs to the SGSN.

Starting NSAPI

The starting Network Service Access Point Identifier. A combination of this value and the IMSI uniquely identifies a PDP context. This value increments for each primary and secondary PDP context associated with a given mobile subscriber.

Range: 5 — 15 (0 — 4 are reserved for GGSN error handling)

Default: 5

Tcl Parameter: SmNsapi

PDP Type

Select the Packet Data Protocol type that is requested by the MNs.

Options: IPv4 or IPv6

Default: IPv4

Tcl Parameter: PdpType

Signalling Connection

Use the drop-down list to define whether the Iu signalling connection is maintained after PDP context activation. If Keep Active is not selected, the RNC will send a Release Request at the time specified. The MN will initiate the Service Request procedure to re-establish the connection when necessary.

NOTE: Signalling Connection is not available when Test Activity is Command Mode.

Options: Keep Active, Tear Down Upon Context Active, or Tear Down After Delay

Default: Keep Active

Tcl Parameter: SmKeepSigActive

If you select Tear Down After Delay, you can enter the number of seconds to wait, after context activation, before sending the release in the Delay field.

Tcl Parameter: SmSigConnTearDnDly

Related Measurements

Teardown Indicator

Available on MME Nodal (Iu-PS) and UMTS test cases. Per TS 24.008 section 9.5.14.1. Select to Tear Down indicator in "GSM A-I/F DTPA - Deactivate PDP Context request". This IE is included in the message in order to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated. Tcl Parameter: SmTeardownIndEn

PDP Context Update

Update Interval

Use to configure the SGSN Node to send periodic Update PDP Context messages. Enter the Update Interval in seconds. Range from 0 to 10000. Default = 5. Tcl Parameter: PdpContextUpdate Tcl Parameter: PdpContextUpdateInterval

Activate PDP Response

Available in MME Node when Mobility = Inter-Tech or Command Mode and Interface = Target Iu-Ps or Target Gb. Select to configure the "Activate PDP Response" with one of the possible options:

Options: Respond with Requested Type (default), Respond with IPv4 Address Only, Respond with IPv4 Address Only.

Tcl Parameter: SmPdpResponseType

Deactivate PDP

Deactivate Interval
Continuous Deactivate PDP

In SGSN Node test case, select Deactivate PDP and enter the Deactivate Interval to periodically send a Deactivate PDP Context (with cause code: reactivation required) after the PDP context is Activated. You may configure to Deactivate once or select Continuous Deactivate PDP.

Tcl Parameter: DeactivatePdpEn

Tcl Parameter: DeactivatePdpInterval Tcl Parameter: DeactivatePdpContinousEn

^ Back to Top

Primary Context APN Assignments

Access Point Name	Use the APN sub-tab to define the APN values assigned to PDP contexts. You can define one APN for all contexts, a different APN for every context, or a set of APNs that are distributed among all contexts. With the retry capability, you can also configure alternate APNs that will be used if a context cannot be established using the preferred APN. You can manually define different APN values, generate incrementing values during test execution, or use a combination of both methods. You can choose to use the same APN configuration for all contexts (Summary) or define an APN configuration by primary context (Individual). Select Individual and the number of tab depends on the number of Default Bearer per Session you selected on the Test Configuration Tab \| Mobile Subscriber pane. For example, if you selected 4 Default Bearer per Session, APN P0, P1, P2, and P3 sub-tabs displays for each primary context assignments.
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: SmApn_0
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 9) are enabled based your selection. The values that you define in these fields will always be used first when you select Round Robin mode. Tcl Parameter: SmApnNumSpecifiedApns_0
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 (limited by the maximum number of PDP contexts) Default: 1 Tcl Parameter: SmApnTotalApns_0
Round Robin	Use the checkbox 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. Tcl Parameter: SmApnRoundRobin_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: SmApnRetries_0 Related Measurements APN Retries

^ Back to Top

Quality of Service

The Quality of Service pane allows you to specify the QoS parameters for a primary PDP context. The GGSN/SGSN needs the QoS information for IP packet Uplink and Downlink. The GGSN/SGSG SUT 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.

Summary/Individual

You can define one QOS for all Primary PDP contexts or a different QOS for each Primary PDP context.

Select the Summary radio button to use the same QOS configuration for all bearers in the Summary tab
Select the Individual radio button to define individual QOS for each bearer per subscriber by selecting the radio buttons.

When you select Individual, a Primary Context eg; P0) sub-tab is displayed for each Primary Context per subscriber (selected on the Mobile Subscriber pane on the Test Configuration tab). the number of tab depends on the number of Default Bearer per Session you selected on the Test Configuration Tab | Mobile Subscriber pane.

For example, if Default Bearer per Session is 3, the Primary Context QoS tabs displayed are Default, P0, P1, and P2.

R97 Only

In UMTS and GPRS testing, select the R97 Only checkbox to send only 4-byte R97 QoS attributes (2G specification).

NOTE: When R97 Only checkbox is not selected, R99/3G QoS attributes are sent regardless of which version UMTS Version (4 through 8) is selected (on the Test Configuration tab).

See GTP QOS Profile.

^ Back to Top

Modified Quality Of Service

The Modified Quality of Service pane allows you to specify the QoS parameters for secondary PDP context. In MME Nodal test case, the Mobile Quality of Service pane is available on the Target Iu-PS | SM tab and Target Gb | SM tab when Handoff Protocol is UMTS (IuPS over IP) or GPRS respectively, and Test Activity is Sequencer or Command Mode (MME Nodal Test Configuration).

You may define ten sets of Quality profile

See GTP QOS Profile for parameter description.

^ Back to Top

Protocol Configuration Options

Select the required authentication method.

Options: No Authentication, Include PAP Authentication, or Include CHAP Authentication

Default: No Authentication

PAP Authentication

When you select 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 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:

PcoPapPassword

PcoPapPeerId

IncPcoOpt

CHAP Authentication

When you select 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

Default: 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 Parameters:

PcoChapId

PcoChapName

PcoChapSecret

PcoChapChallengeValue

Related Measurements

User Authentication Failure

IP Control Protocol

During GGSN Nodal, MME Nodal, MME Node with PGW Emulation. SGW Nodal and UMTS testing, select IP Control Protocol to include the protocol configuration options (PCO) IEs in the Create PDP Context Request.

NOTE: Multiple protocol configurations are included in a single PCO.

Tcl Parameter: PcoIpcpEn

Type: True/False

Default: False

NOTE: During MME Nodal testing, the IP Control Protocol Tcl parameters on Gn | IPv4 tab is prefixed with Sgsn. During MME Node testing, the IP Control Protocol Tcl parameters on S1-MME | NAS Tab are prefixed with Nas.

Selecting IP Control Protocol allows you to further select and enter IPCP IP Address, primary and secondary addresses for WINS and DNS servers. You may enter IPv4 or IPv6 addresses, as required.

Type: True/False

Default: False

Tcl Parameters:

PcoIpcpIpAddrEn	PcoIpcpIpAddr
PcoIpcpPrimDnsEn	PcoIpcpPrimDnsAddr
PcoIpcpPrimWinsEn	PcoIpcpPrimWinsAddr
PcoIpcpSecDnsEn	PcoIpcpSecDnsAddr
PcoIpcpSecWinsEn	PcoIpcpSecWinsAddr

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.

NOTE: If Default Bearers per UE is 2 or more, "Per Bearer APN/PCO Settings" should use "Individual" mode in order to include P-CSCF IPV4/6 Address Request and P-CSCF Reselection support only in PCO for VoLTE PDN Connection.

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
SGW Nodal	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

^ Back to Top

Apply Parameter Values from Test Data Files (SM)

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: SmCfgFileEn

NOTE: SM file settings include UMTS Version and Activate PDP Contexts upon GMM Attach.

^ Back to Top