The IuPS tab is used to define the radio and transport layers of the Iu-PS interface between the RNC and a 3G-SGSN SUT. The settings for the appropriate protocols are displayed based on your Protocol selection.
The IuCS tab is used to define the radio and transport layers of the Iu-CS interface between the RNC and MSC. The settings for the appropriate protocols are displayed based on your Protocol selection.
NOTE:
|
When you select the Mobility or Session Loading With Mobility test activity, a Mobility IuPS tab is added to the test case to define the interface for the handoff RNC.
Radio Access Network Application Part (RANAP) settings provide RNC link management and Radio Access Bearer (RAB) management for MNs, including RAB mobility management and signal integrity.
In HNB testing, the Iuh tab is used to define the radio and transport layers of the Iuh interface between the HNB and a HGW SUT. The settings for the appropriate protocols are displayed based on your UMTS Version selection.
In HNB testing, the Iu-PS tab is used to define the radio and transport layers of the Iu-PS interface between the RNC and a SGSN SUT. The settings for the appropriate protocols are displayed based on your UMTS Version selection.
n HNB testing, the Iu-CS tab is used to define the radio and transport layers of the Iu-CS interface between the RNC and a MSC SUT. The settings for the appropriate protocols are displayed based on your UMTS Version selection.
The RANAP settings, during HNB testing, provide Radio Access Bearer (RAB) management, RAN information management and location reporting for MS.
Location and Routing Information
RAN Information Management
Location Reporting Control
General
|
Measurements collected for IuPS radio and transport related processing are reported on the M3UA, MTP-3B, RANAP, and SCCP report tabs.
Measurements collected for Iuh interface in HNB testing, radio and transport related processing are reported on the RUA, HNBAP, RANAP, HNB Node and SCCP report tabs.
Use the checkbox to enable early RAB assignment during a Routing Area Update. This option is only available in Release 6 testing. Tcl Parameter: RanapEarlyRab_1
|
|||||||||||
Only available under UMTS version 8 and 3G Macro RNC Emulation is not selected. Use the checkbox to encode the IE "Source RNC To Target RNC" in release 7 format. Tcl Parameter: RanapSrc2TgtRncIeRel7En_1 |
|||||||||||
Select the Initiate Reset checkbox to allow the RNC to send a RANAP Reset Request and wait for the RANAP Reset Acknowledgement before sending any of the Attach Requests to SGSN. When you select the Initiate Reset checkbox, Max Retries and Reset Ack Timeout parameters are also enabled.
Tcl Parameters:
|
|||||||||||
In SGSN Node test case, Select to include the assigned maximum bit rate and define the associated maximum bandwidth for uplink and downlink IP packets. Tcl Parameter: RanapIncludeMaxBitRate_1
|
|||||||||||
Ignore Iu Release Request |
Available in SGSN and UMTS Node test cases. Select to ignore the IU RELEASE REQUEST message. As per specification 25.413, section 8.4.2 in release 15. Tcl Parameter: RanapIgnoreReleaseReqEn_1 |
||||||||||
Support for CN simulator (MSC Node or SGSN node) to initiate a CN RANAP Reset. Available in MSC and SGSN Node test cases. Select to include and enter a Global CN-ID. Global CN-ID - Range from 0 to 4095. Default = 0. Tcl Parameter: RanapCnIdEn_1 Tcl Parameter: RanapCnIdValue_1 |
|||||||||||
Select User Plane Mode. Options: Transparent (default), Support Predefined SDU Sizes Tcl Parameter: RanapUserPlaneMode_1 Enter User Plane Mode Versions Range: 0 (default) to 65535 Tcl Parameter: RanapUserPlaneModeVersions_1 |
|||||||||||
Only available in SGSN and MSC Node. Use the checkbox to encode the IE "Target RNC To Source RNC" in release 7 format. Tcl Parameter: RanapTgt2SrcRncIeRel7En_1 |
|||||||||||
In SGSN Node test case, define the maximum authorized traffic class for each Radio Access Bearer messages. Select the required Traffic Class ID and define the associated transport rate uplink and downlink traffic. Options: Conversational, Streaming, Interactive, Background Tcl Parameter: RanapTrafficClass_1
|
You can configure the test to assign the same Location Area Code (LAC) and Routing Area Code(RAC) to every MN or define a range of values that will be evenly distributed among the MNs. These values are used in both the RANAP and GMM layers.
During HNB testing, the HNB Location Information appears on the HNBAP tab, and is sent from the HNB to HNB-GW to provide information on the location of the HNB.
Enter the same value in the Start and End field to use that value for every MN. Enter the lowest value in the Start field and the highest value in the End field to define a range of values. When you define a range of LAC values, RAC values, or both, the value is incremented for each MN. Example:Example:
Assuming the following settings:
Number of MNs: 5
LAC range: 0— 2
RAC range: 0— 1
The MNs will be assigned LAC/RAC combinations in a round-robin manner:
MN 1: 0/0
MN 2: 1/1
MN 3: 2/0
MN 4: 0/1
MN 5: 1/0
NOTE: In UMTS testing, ensure that the LAC range defined on the Mobility IuPS tab does not overlap the range on the IuPS tab. Handoffs must be performed between different LAC/RAC combinations. |
Location Area Code Range
Range: 0 — 65,535
Default: 0
Tcl Parameter:
RanapLac_1 |
RanapLacEnd_1 |
Routing Area Code Range
Range: 0 — 255
Default: 0
Tcl Parameter:
RanapRac_1 |
RanapRacEnd_1 |
The following parameters define the remaining location and routing information elements for the RANAP layer.
Mobile Network Code
Range: 00 — 999 (2-3 digits; leading zeros are retained)
Default: 00
Tcl Parameter: RanapMnc_1
Mobile Country Code
Range: 000 — 999 (leading zeros are retained)
Default: 000
Tcl Parameter: RanapMcc_1
Service Area Code
Range: 0 — 65,535
Default: 0
Tcl Parameter: RanapSac_1
When you test with Release 6, you can include the RAN Information Send procedure in the test. RIM messages are sent, at the interval you define, to an RNC in another test case via the SGSN. The SGSN is responsible for routing the message to the correct RNC based on the destination ID, MCC, and MNC contained in the message.
Use the RIM Messages Sent checkbox to enable the procedure and define the timing and destination of the messages with the following parameters:
Tcl Parameter: RanapIncRim_1
RIM Timeout — The number of seconds between RIM messages.
Range: 1 second or greater
Default: 1
Tcl Parameter: RanapRimTimeout_1
Destination RNC ID
Range: N/A
Default: 0
Tcl Parameter: RanapRimRncId_1
Destination Mobile Country Code
Range: 000 — 999 (leading zeros are retained)
Default: 000
Tcl Parameter: RanapRimMcc_1
Destination Mobile Network Code
Range: 00 — 999 (2-3 digits; leading zeros are retained)
Default: 00
Tcl Parameter: RanapRimMnc_1
Use the RIM Multi-Report Timer (ms) checkbox to enter report timer in ms.
Range: 0 to 65535
Default: 10000
Tcl Parameter: RanapRimMultiReportTimer
Use the RIM Based Application Test Data File to System Information Messages checkbox to enter a Test Data File (TDF wizard is enabled) for system information messages per 3GPP TS 44.060.
See sample test data file: rimPsiMessages10_10.txt
The input test file usage guide:
1) All data is in HEX format
2) Support system information messages specified in 3GP TS 44.060
3) Each line with HEX data is for a system information message:
4) Multi-reports are supported, each report starts and ends with a line of "##############" string
5) Each report is limited to 8 messages (enough for NACC application)
6) Maximum 8 different reports are supported. If a RIM application needs more than 8 reports, the data feed with repeat automatically (reports 1,2, ..., 8, 1,2, ..., 8, ...)
Tcl Parameter: RanapRimCfgFileEn
By default, the RNC will respond to a Location Reporting Control message from the SGSN that requests Service Area Identifier location reporting. You can configure the response to a geographical area location report request with the settings in this pane.
NOTE: Different locations should be defined on the IuPS and Mobility IuPS tabs. |
Use the drop-down list to select whether Geographical Area reporting is supported and the type of information included in the Geographical Area IE of the Location Report message. The applicable parameters are enabled based on your selection.
Options:
Point
Point With Uncertainty
Polygon
Point With Uncertainty Ellipse
Point With Altitude
Point With Altitude and Uncertainty Ellipsoid
Ellipsoid Arc
Default: None
Tcl Parameter: RanapGeoAreaType_1
A single set of coordinates defines a point location, multiple sets of coordinates define the boundaries of a polygon.
Tcl Parameter:
Latitude Sign
Options: north or south
Default: north
Tcl Parameter: RanapLatitudeSign_1
Latitude
Range: 0 — 8388607
Default: 0
Tcl Parameter: RanapLatitude_1
Longitude
Range: -8388608 — 8388607
Default: 0
Tcl Parameter: RanapLongitude_1
Some of these settings are available when the location is defined by an Ellipsoid Arc or any of the choices that include an uncertainty qualifier.
Uncertainty Code
Range: 0 — 127
Default: 0
Tcl Parameter: RanapUncertaintyCode_1
Uncertainty Semi-Major
Range: 0 — 127
Default: 0
Tcl Parameter: RanapUncertaintySemiMajor_1
Uncertainty Semi-Minor
Range: 0 — 127
Default: 0
Tcl Parameter: RanapUncertaintySemiMinor_1
Orientation of Major
Range: 0 — 127
Default: 0
Tcl Parameter: RanapOrientationMajorAxis_1
Confidence
Range: 0 — 127
Default: 0
Tcl Parameter: RanapConfidence_1
Uncertainty Altitude
Range: 0 — 127
Default: 0
Tcl Parameter: RanapUncertaintyAltitude_1
Click the button to open the Polygon Points window and define up to 15 points on a polygon with point coordinates.
Direction of Altitude
Options: height or depth
Default: height
Tcl Parameter: RanapDirectionAltitude_1
Altitude
Range: 0 — 32767
Default: 0
Tcl Parameter: RanapAltitude_1
These settings are available when the location is defined by an Ellipsoid Arc.
Inner Radius
Range: 0 — 65535
Default: 0
Tcl Parameter: RanapInnerRadius_1
Offset Angle
Range: 0 — 179
Default: 0
Tcl Parameter: RanapOffsetAngle_1
Included Angle
Range: 0 — 179
Default: 0
Tcl Parameter: RanapIncludeAngle_1
Uncertainty Radius
Range: 0 — 127
Default: 0
Tcl Parameter: RanapUncertaintyRadius_1
Use these settings to set the type of report.
Request Type Report
Options: None, Geographical Area, Service Area
Default: None
Tcl Parameter: RanapRegRepArea_1
Request Type Event
Options: Direct or Change of Service Area
Default: Direct
Tcl Parameter: RanapReqEv_1
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. |
Tcl Parameter: RanapCfgFileEn_1
NOTES:
|