The Billing sub-tab is available on the Ga tab of the CGF Nodal, GGSN Nodal, UMTS, and LTE test cases if the test system is licensed for the appropriate features. The settings allow you to configure the emulated SGSN or GGSN nodes to generate CDRs for the MN Data Traffic processed during the test. When used in conjunction with the CGF Node test case, you can validate the G-CDRs, M-CDRs, or S-CDRs generated by the SUTs against LDRs generated by the nodes.
The physical Ga interface for all nodes is defined on the GTP' tab.
Primary Context APN Assignments (CGF Nodal)
|
|||
GTP Version 1 (CGF Nodal)
|
|||
Quality of Service (CGF Nodal)
|
|
||
| GTP' | |||
Billing |
|||
Charging Data Records (For Back-to-Back Testing only) SGSN / GGSN
QOS Change Record Closure CGI-SAI Change DT Establishment TAI Change Tariff Change eCGI Change DT Removal RAI Change User Location Change
|
QOS Change Record Closure CGI-SAI Change DT Establishment TAI Change Tariff Change eCGI Change DT Removal RAI Change User Location Change
DCCA Time Threshold QoS Change CGI-SAI Change DCCA Volume Threshold SGSN Change RAI Change DCCA Service Specific Threshold SGSN PLMN ID Change Record Closure DCCA Time Exhausted Tariff Change Time Limit DCCA Volume Exhausted PDP Context Release Volume Limit DCCA Validity Timeout RAT Change Envelope Closure DCCA Re-authorization Request Service Idled Out eCGI Change DCCA Continue Session Configuration Change TAI Change DCCA Retry & Terminate Session Service Stop DCCA Terminate Session Service Specific Unit Limit DCCA Service Specific Unit Exhausted User Location Change |
||
Measurements collected for CDR-related processing, the Ga interface, and the GTP' node are reported on the Billing, GTP', and GTP' Node report tabs.
| Data Record Type | Use the drop-down list to select the type of CDR that the GTP' node will generate. Options:
Default: Landslide SGSN or Landslide GGSN Tcl Parameter: CgfType
|
| Per-Flow Billing Type | If the test will be performing vendor-specific Per-Flow Validation with the CGF Node test case, select Landslide from the drop-down list to include per-flow attributes in the LDRs. Additional options are available in the DMF parameters for Per-Flow Validation. Options: None or Landslide Default: None Tcl Parameter: CgfBillType
|
| Charging Data Records | For Back-to-Back Testing only The Charging Data Records (CDRs) pane allows you to emulate change in charging conditions where the Nodes have reached the maximum number of the imposed limit of charging conditions and the node generates/sends a CDR/eG-CDR containing all the stored changes to a CGF node. You can indicate the Change Conditions and set up the CDRs to be generated with these conditions for a specified interval or CDR cycle. In GGSN Node test case and in the CGF Nodal (when GGSN Billing Client is selected), the List of Service Data pane is available when Data Record Type is EGSN. You can set up eG-CDRs to be generated with these conditions for a specified interval or CDR cycle.
In CGF Nodal test case, you have the option to select SGSN or GGSN as the billing client. Select Emulate Change Conditions, When SGSN is selected, the Change Conditions Pane is available. When GGSN is selected, the List of Traffic Volumes/ and List of Service Data are enabled. |
| Transport | Use the radio buttons to select the GTP' transport protocol. When UDP is used in Active Initiate mode, a Node Alive message is always sent to the CGF when the test begins. If you select TCP, you can suppress the message by clearing the Node Alive checkbox. Options: UDP or TCP Default: UDP Tcl Parameter: CgfNodeAlive
|
||
|
|
The GTP' Node can initiate the connection with the CGF in Active mode (the method used depends on the Transport selected) or wait for the CGF to initiate the connection in Passive mode. Options: Active or Passive Default: Active Tcl Parameter: CgfInitiateMode When you select Passive, you can use the checkbox to enable the Validate SUT option. With this option, the node will only accept messages from the selected CGF Node. |
||
Use the drop-down list to select the CGF that will receive the Data Records generated by the GTP' node. If you are using a CGF Node test case, it will be treated as a SUT and must be added to the SUT database. Options: The list contains all defined SUTs. Default: N/A |
|||
Validates the SUT that will receive the Data Records generated by the GTP' node. If you are using a CGF Node test case, it will be treated as a SUT to validate that the messages are from the selected SUT and must be added to the SUT database. Tcl Parameter:CgfPassiveUseSut Destination PortThe CGF's GTP' port. Range: N/A Default: N/A (the default GTP' port is 3386) Tcl Parameter: SutCgfNodeAddrPort
|
|||
Use the drop-down list to select the CGF that will receive the Data Records generated by the GTP' node. If you are using a CGF Node test case, it will be treated as a SUT and must be added to the SUT database. Options: The list contains all defined SUTs. Default: N/A |
|||
The CGF's GTP' port. Range: N/A Default: N/A (the default GTP' port is 3386) |
|||
Use the checkbox to send periodic Echo Request messages to the CGF, Define the number of seconds between messages in the field provided. Range: 5 — 900 Default: 5 Tcl Parameter:
|
|||
Tcl Parameter:
See Retries |
|||
If you selected SGSN (GGSN Nodal) or GGSN (UMTS) as the CDR Type, you can use the drop-down list to select the latest GTP' version supported by the CGF. If a CGF requests an earlier version, the SGSN CGF node will revert to that version. Range: 0 — 2 Default: 1 Tcl Parameter: CgfGtpVersion Related Measurements |
|||
Use the radio buttons to select the GTP' header length that will be used in the test. You can only choose a length that is valid for the selected GTP' version. Options: 6-octet or 20-octet Default: 6-octet |
|||
Enter the maximum CDR Size you need for encoding/decoding CDRs and allocating buffer size of the billing record repository. Range: 1 - 50000 Default: 1500. Tcl Parameter: CgfMaxCdrSize |
|||
Use the checkbox to test with one GTP' node interface that is shared by all SGSN nodes (checked) or to test with a separate GTP' node for each SGSN node (cleared). When the box is cleared, the IP Address on the GTP' Node sub-tab is used as a starting address and incremented for each node. |
Use the APN pane to define the APN values assigned to PDP/bearer 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 incremented values during test execution, or use a combination of both methods.
During GPRS testing, In the APN Primary Context Assignments pane, you can choose to use the same APN configuration for all contexts or define an APN configuration by primary context by selecting Summary or Individual radio buttons. When you select Individual, an APN sub-tab is displayed for each primary context. For example, the APNs defined in the P0 sub-tab are used with every MN's first primary context, the APNs defined in the P1 sub-tab are used with every MN's second primary context, and so on. The Number of individual primary contexts sub-tabs depend on the Number of Primary PDP Contexts value selected on the CGF Nodal Test Configuration tab.
| Case Sensitive APNs | Select to indicate that APN Name are case Sensitive. |
| APN 0 to APN 10 | Enter APN values. Range: 0 to 10 Default: 1 Tcl Parameter: Apn0 to Apn10
|
Charging Characteristics |
The type of charging the PDP context is liable for, selected from one of 16 charging profiles that may be configured on the GSN. Range: 0 - 16 Default: 16 (indicates that it is not used) Tcl Parameter: ChargeCharacteristics |
||||||
Include MS Time Zone |
Use the Include MS Time Zone to enables calculation of the MN's local time. Time Zone specifies the difference, in quarter-hour increments, between the local time and GMT. Bit 3 defines the algebraic sign of the difference (0 = positive, 1 = negative). The upper 4 bits (4 through 7) and the lower 3 (0 through 2) bits define the time difference. Range: 0 — 255 Default: 0 Daylight Saving Time defines the adjustment for daylight savings time, if any, in the current time zone. Range: 0 — 255
Default: 0 |
||||||
Include RAT Type |
Use the checkbox to include Radio Access Technology Type information element, which identifies the RAT type used by the SGSN. When enabled, enter the RAT type in the field provided. Range: 0 — 255
Default: 1 |
||||||
Select to include the User Location Information. Enter Geographic Type, Mobile Country Code, Mobile Network Code, Location Area Code and Cell ID or Service Area Code.
Tcl Parameter:
|