GMM Tab
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

GMM Tab

The GMM tab is used to define the system layer of the Iu-PS interface (GMM and SM) between the RNC and the SGSN SUT. The parameters define Routing Area Update options and the attributes used in GMM messages.

Retries and Timers

 

Ciphering Algorithm IE

 

DRX Parameter IE

 

 

 

Authentication

 

 

 

 

 

 

 

 

MS Radio Access Capability IE

 

Attach Type IE

 

 

Local Area Identification IE Codes

 

Mobile Identity IE

 

MS Network Capability IE

 

General

Related Measurements

Measurements collected for IuPS GMM related processing are reported on the GMM report tab.

General

The following parameters define the number of PDP contexts for each MN (when PDP contexts are used) and the delay time for the MN attaches.

Number of Primary PDP Contexts per MS

Use the drop-down list to select the number of primary PDP contexts to be established for each mobile subscriber.

Options:  1— 11

Default: 1

Number of Secondary PDP Contexts per Primary

Use the drop-down list to select the number of secondary contexts to create for each primary context. Select 0 to disable secondary contexts.

Options: 0 — 10

Default: 0

IMPORTANT:

  • The total number of PDP contexts (MN sessions) that will be attempted during the test is the result of Number of Mobile Nodes multiplied by the total number of PDP contexts per subscriber. When secondary PDP contexts are used, Number of Primary PDP Contexts per MS + (Number of Primary PDP Contexts per MS * Number of Secondary PDP Contexts per Primary) determines the total number of PDP contexts.

  • The total number of primary and secondary contexts for each mobile subscriber cannot exceed 11. The number of secondary PDP contexts that you can select depends on the number of primary contexts selected. ExampleExample:

    If 3 primary contexts are specified in Number of Primary PDP Context per MS, no more than 2 secondary contexts can be created:  3 primary contexts + (3 x 2) secondary contexts = 9 total contexts.

    If 5 primary contexts are specified, only 1 secondary context can be created (5 primary + 5 secondary = 10 total contexts.

  • When you include Data Traffic in the test, the total number of PDP contexts that can be defined depends on the number of Data Message Flows added to the test. The total contexts available is reduced by each DMF added to the test. If you use multiple contexts per MN, you must also map the contexts to DMFs.

GMM Attach Start Delay

The number of milliseconds that the test will wait, after all RNC links are established, before beginning to perform GMM attaches for the MNs.

NOTE: The GMM Attach Start Delay is used only during the initial MN activations. This delay is not necessary during session loading, because the links are not brought down.

Range: 0 — 65535

Default: 0

GMM Detach Start Delay

The number of milliseconds after the last RNC link is deactivated that the test will wait before attempting to detach the MN.

Range: 1 —2147483647

Default: 0

PDP Context Activate Delay

The number of milliseconds that the test will wait, after an MN has successfully attached, before beginning to activate the MN's PDP contexts. When you define a delay time and clear the Follow On checkbox, the SGSN may perform an Iu Release due to inactivity. If the connection is released, the MN will send a Service Request to restore the connection before attempting to activate PDP contexts.

NOTE: The PDP Context Activate Delay is used for all MN activations, not just the initial activation. This delay is applied during session loading, because both GMM and SM sessions are brought down.

Range: 0 — 65535

Default: 0

^ Back to Top

Retries and Timers

Number of Retries

The number of times the test will re-transmit a message if a response is not received before the Retry Timer expires. Enter 0 to disable retries.

Range: 0 — 255

Default: 0

Tcl Parameter: GmmRetryCnt

Retry Timer

The number of seconds the test will wait for a response.

Range: 0 — 255

Default: 15

Tcl Parameter: GmmRetryTmr

Periodic Routing Area Updates

Use the Perform Periodic Routing Area Updates checkbox to generate a Routing Area Update Request from the MN to the SGSN according to the timed cycle you define.

Time

The number of seconds to wait before generating a request.

Range: 1 — 65534

Default: 3240

Tcl Parameter: GmmRauTime

Detach Request Time(s)

Use the Detach Request Time(s) to initiate a detach request at the specified time. When the RNC sends a Attach Request to the same SGSN, the SGSN will send a Attach Accept back with a Null-NRI. The Null-NRI will trigger the RNC to send a RAU request for the MN to the next available SGSN.

Range: 0 – 1000 seconds

Default: 0

Tcl Parameter: GmmDetachRequestDelay

^ Back to Top

Attach Type IE

Attach Type IE

Use the drop-down list to select the type of Attach message to send.

Options: GPRS attach (0x01), GPRS attach while IMSI attached (0x02), or Combined GPRS/IMSI attach (0x03)

Default: GPRS attach (0x01)

Tcl Parameter: GmmAttachType

Follow On

Use the checkbox to set the Follow-on request bit in the Attach Type IE, indicating that the MN wishes to activate a PDP context when the attach is complete.

Tcl Parameter: GmmFollowOn

Detach Start Delay

The number of milliseconds after the last PDP context is deactivated that the test will wait before attempting to detach the MN.

Range: 1 — 2147483647

Default: 0

^ Back to Top

Location Area Identification IE

See RAI Attributes.

^ Back to Top

Mobile Identity IE

Select the type of MN identifier that will be used in the initial and subsequent GMM Attach Requests and define the values used.

Attach With

Use the drop-down list to select the type of information the IE will contain.

Options: IMEI, IMSI, IMEISV, or P-TMSI

Default: IMEI

Tcl Parameter: GmmMIe

NOTES:
  • IMEI and IMEISV are not available on the Target IuPS > GMM tab when Initial Network is Target on the Test Configuration tab (4G does not support Attach With IMEI and Attach with IMEISV).
  • Only IMSI is supported for Mobility test activities (Session Loading with Mobility/Intra-HNB GW Mobility) for test case HNB GW Nodal.

 
P-TMSI

An invalid P-TMSI that will be used in every MN's initial Attach Request. When the MN is re-attached in a Session Loading test, either the valid P-TMSI obtained during a previous attach or a random P-TMSI is used in the request depending on the Use SGSN Assigned P-TMSI setting.

Range: Up to 32 decimal digits. Hex format is also acceptable if "0x" prefix is used.

Default: 0

Tcl Parameter: GmmPtmsi

 
Software Version

The version value is combined with the IMEI when IMEISV identity type is used. The same value is used for all MNs and it is a fixed length of 2 digits.

Range: 00 — 99

Default: 00

Tcl Parameter: GmmSwVersion

 
Starting IMEI

The International Mobile Equipment Identity that will be used for the first MN. This value will be incremented for each MN.

Range: 14 digits

Default: N/A

Tcl Parameter: GmmImei

 
Starting IMSI

The International Mobile Subscriber Identifier that will be used for the first MN. This value is incremented for each MN. A combination of this value and the NSAPI uniquely identifies a PDP context.

Range: 5 — 15 digits

Default: N/A

Tcl Parameter: GmmImsi

 
Use SGSN Assigned P-TMSI

Use the checkbox to specify that the P-TMSI received from the SGSN is used in any re-attach attempts. When the checkbox is cleared, a random P-TMSI is generated and used for the attach attempt.

Tcl Parameter: GmmUseAssignedPtmsi

 
Use Random TLLI

Select Use Random TLLI to generate random TLLI messages, available for UMTS or GPRS protocols.

Type: True/False

Default: False

Tcl Parameter: GmmUseRandomTLLI

NOTE: Normally, the TLLI in Attach Request messages is based on the session number. For Port reservation, since the sessions in both the test cases have the same number, a the duplicate TLLI message may be generated.

Related Measurements

 

^ Back to Top

Ciphering Algorithm IE

Defines the encryption capabilities of the MNs.

GPRS Encryption Algorithm

Simulate MNs that can support any combination of the GEA/1 through GEA/7 algorithms by checking the respective boxes.

Tcl Parameter:

GmmGprs1

GmmGprs2

GmmGprs3

GmmGprs4

GmmGprs5

GmmGprs6

GmmGprs7

GmmPfp

Packet Flow Procedures

Use the checkbox to indicate that the MNs can support the BSS packet flow procedure.

Use the Hard-Coded key

Select the check box and enter the Cipher Key value to be used.

Tcl Parameter:

GmmCipherKeyEn

GmmCipherKey

^ Back to Top

MS Network Capability IE

Defines the UMTS capabilities of the MSs.

Use the radio buttons to select the 3GPP revision level supported by the MNs.

Options: pre-R99 or R99 or later

Default: R99 or later

Use these checkboxes to indicate that the MNs can support Short Messaging Service.

Tcl Parameter:

GmmSmg

GmmSmd
NOTE: The following selections are available only when UMTS Version is >= 8 on the Test Configuration tab (during  HNB GW Nodal, MME Node, MME Nodal, SGSN Node, and UMTS testing).

Tcl Parameter:

GmmIratToUtranIuEn

GmmIratToEutranS1En

GmmEmmCombinedProcEn

GmmSrvccToGeranUtranEn

Select to indicate that the MNs are capable of Support of Localized Service Area. SoLSA provides the mechanisms to support LSA services related to the radio resources, and it can be used to provide special set of service features for certain subscribers within a regionally restricted area or areas.

Tcl Parameter: GmmSolsa

Tcl Parameter: GmmUcs2

GmmIsrEn

GmmEpcEn

^ Back to Top

DRX Parameter IE

Defines the Discontinued Reception mode used by the MNs.

Split PG Cycle Code

Indicates the Split PG Cycle used by the MNs. Enter 0 to indicate that the MNs do not use DRX.

Range: 0 — 255

Default: 0

Tcl Parameter: GmmPgcc

DRX Cycle Length Coefficient

The DRX cycle length coefficient requested by the MNs. Enter 0 to indicate that the CN domain-specific DRX cycle length should be used.

Range: 0 — 15

Default: 0

Tcl Parameter: GmmClco

Non-DRX Timer

Use the drop-down list to select the maximum number of seconds that the MN can stay in the non-DRX mode after a transfer.

Options: No non-DRX mode or a maximum of 1, 2, 4, 8, 16, 32, or 64 seconds

Default: No non-DRX mode

Tcl Parameter: GmmNdrxt

Split PG Cycle on CCCH

Use the checkbox to indicate that split PG cycle on CCCH is supported by the MNs.

Tcl Parameter: GmmCcch

^ Back to Top

MS Radio Access Capability IE

See MS Radio Access Capability Attributes

^ Back to Top

Authentication

Defines the authentication keys used by the MNs.

Secret Key

The MN's text or hexadecimal key that is associated with its IMSI and is used to derive the UMTS ciphering key.

Tcl Parameter: GmmSecretKey

RES Length (bytes)

Per 3GPP (33.102) specified RES Length of 4-16 octets. Range: 4 to 8, Default : 8

Tcl Parameter: GmmAuthResLen

GSM Security

Select to enable GSM Authentication.

Tcl Parameter: GmmGsmSecurityEn

Use Hard Coded Auth Value

Use the checkbox to specify a hard-coded response and enter the RES value, in hexadecimal format, in the field provided. With this option, Secret Key and Operator Variant are not used. MAC verification will be by-passed and the exact number of bytes (up to 16) configured in the hard-coded value.

Tcl Parameter:

GmmAuthValueEn

GmmAuthValue

Operator Variant Algorithm Configuration Field

The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network.

Range: Up to 32 hex characters, excluding "0x."

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Tcl Parameter: GmmOpVar

Related Measurements

^ Back to Top

Apply Parameter Values from Test Data Files (GMM)

See About Applying Parameter ValuesAbout Applying 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.

 

NOTE: GMM file settings include UMTS Version.

^ Back to Top

 

© 2024 Spirent Communications Inc. All Rights Reserved.