CGF Node Emulator Configuration

Emulator Options

• Server Mode

• Release

• Run-Time CDR Logging

• Per-Flow Validation

• Max Data Records

• Silently Discard Records Exceeding Max

• Maximum Flows per Bearer

• Ga Profile Monitoring

• Max CDR Size

• CDR Timer (s)

• LDR Timer (S)

Failover Simulation

Redirection Simulation

Use the drop-down list to select the type of CDR processing performed by the CGF node.

• Learn more about CDR Collection and Validation

Options:

• Collection — The node collects G-CDRs, M-CDRs, S-CDRs, G-LDRs, and S-LDRs received during the test, consolidates partial CDRs, and includes the Data Records in the test results.

• Validation — The node compares LDRs with the CDRs received during the test and validates the accuracy of the CDRs based on the CDR Validation settings.

• Both — The node performs both Collection and Validation processing.

• Statistics Only — The node simply responds to the messages received during the test without retaining or validating CDRs and reports the number and type of messages sent and received.

Default: Both

Tcl Parameter: CgfMode

Use the drop-down list to select the LTE release used by the EGSNs, SGSNs, GGSNs, PGW, and SGW.

Options: R97 — R99 and R4 — R11

Default: R11

Tcl Parameter: CgfRelease

The result of the Runtime CDR Logging depends whether you select the parameter or not.

• Runtime CDR Logging not selected: Each validated CDR is counted as an active Billing Record and decreases the number of Free Billing Records.
• Runtime CDR Logging selected: Validated CDRs are no longer pegged as active and this leaves the number of Free Billing Records unchanged (original number).

Tcl Parameter: CgfRuntimeLoggingEn

If you purchased the Per-Flow Validation features, you can validate the Uplink bytes, Downlink bytes, and duration by specifying them on the Validation tab. The validation attributes will be included in the CDR Validation Attributes settings.  

Select Per-Flow Validation and specify the maximum flows per bearer supported

Tcl Parameter: CgfPerFlowEn

The maximum number of Billing Records that will be maintained by the CGF node. When partial CDRs are received, they are consolidated into one Billing Record. One Billing Record should be established for every PDP context that is successfully activated. In a Capacity test, for example, one record is established for each PDP context but in a Session Loading Test, a new record is established for each PDP context every time it is activated.

When the maximum number of records is reached, an error indication is sent to the GSN if any CDRs or LDRs are received for a PDP context that does not have an established Billing Record. If you are not interested in collecting or validating records, you can check the Silently Discard Records Exceeding Max box and the node will ignore the excess Data Records .

Range: Variable1

Default: 1

1 Maximum rates, number of sessions, and number of emulated nodes vary depending on the test application and the test system's licensed capacity.

Related Measurements

• Error Indications Sent

• Free Billing Records

Tcl Parameter: CgfSessions

Tcl Parameter: CgfSilentDiscardEn

Enter the maximum number of Flows per bearer.

Option: 0 - 128

Tcl Parameter: CfgMaxFlowsperBearer

Select to configure the Profiles information used to validate whether SUT correctly records number of changes in charging conditions by analyzing the received Data Record request. (The CGF Node collects information form the accounting request from SGW and PGW, and when the record closure criteria is met, validates the records, and reports).

Configure monitoring profiles information on the Ga | Profiles tab.

Tcl Parameter: CfgGaProfilesEn

Enter the maximum CDR Size you need for encoding/decoding CDRs and allocating buffer size of the billing record repository.

Range: 1 - 9000

Default: 1500.

Tcl Parameter: CgfMaxCdrSize

Configure the amount of time to wait for a final Data Record. If the record is not received, an error is reported.

CDR Timer

The number of seconds to wait for the final CDR for a PDP context after the final LDR for the context has been received.

Range: N/A

Default: 30

Tcl Parameter: CgfCdrTimer

Related Measurements

• CDR Time Failed

LDR Timer

The number of seconds to wait for the final LDR for a PDP context after the final CDR for the context has been received.

Range: N/A

Default: 30

Tcl Parameter: CgfLdrTimer

Related Measurements

• LDR Time Failed

Use the checkbox to send periodic Echo Request messages to the GSNs. Define the number of seconds between messages in the field provided.

Range: 5 — 900

Default: 5

See Retries

Indicates the CDR packet transfer scenarios that trigger failover simulation. Select an option other that the default Normal CDR Packet Transfer to specify the failover simulation settings.

Options:

• Normal CDR Packet Transfer
• Connection Breaks Before a Successful CDR Reception
• Connection Breaks After a Successful CDR Reception

Default: Normal CDR Packet Transfer

Tcl Parameter: CgfFailoverScenario

Indicates how often the failover scenario is simulated. Select the appropriate radio button.

• One-Time (0)
• Periodic (1)

Values:   0 or 1

Default: One-time (0)

Tcl Parameter: CgfFailoverPeriodicity

Indicates the cause of failover.

• Transport Loss

Values: Transport Loss, Negative Response

• Negative Response

Values: No Resourses, System Failure

• Negative Response Cause: No Resources, System Failure

Tcl Parameter:

The Start Method indicates when the failover procedure starts, either a specified time after connection or after a specified number of CDRs are received.

Tcl Parameter: CgfFailoverStartType

Default: Time After Connection in sec

Options:

• Time After Connection in sec
• After number of CDRs Rcvd

Values: Tx, Nx

Select and enter an appropriate value.

Indicates the length for time for which the failover simulation process is active. After the specified time expires, the failover simulation process stops.

Tcl Parameter: CgfFailoverTy

Selecting the Simulate Redirection checkbox allows you simulate the redirection mechanism by specifying  the start method and cause of redirection request. A Redirection Response message always sends as a response of a received Redirection Request.

Value: true/false

Default false.

Tcl Parameter: CgfRedirectEn

Use Advertise a Redirection CGF to include forwarding CGF Node IP Address in the Redirect Request Message.

Selecting just Simulate Redirection, does not advertise redirection CGF IP address. Advertising the node address in the Redirection message requires you to first select Advertise a Redirection CGF and then select the node address from the Advertise Redirection CGF dropdown list on the Network Devices tab.  

Type: True, False

Default: False

Tcl Parameter: CgfRedirectSutEn

The Start Method indicates when the Redirection procedure starts, either a specified time after connection or after a specified number of CDRs are received. Use the radio button to select your option and enter the appropriate value.

Default: Time After Connection in sec

Options:

• Time After Connection in sec (Tx)
• After number of CDRs Rcvd (Nx)

Values: Tx, Nx

The Cause dropdown list provides you a list of reasons for triggering redirection included into the Redirection Request.

Options:

• This node is about to go down (0)
• Another node is about to go down (1)
• System failure (2)
• Receive buffers becoming full (3)
• Send buffer becoming full (4)

Values: 0, 1, 2, 3, 4

Default: 0 (This node is about to go down)

Tcl Parameter: CgfRedirectCause