CDF App

• All (Acct-Interim-Interval)

• ACA Delay (s)

• Starting Subscriber ID

• APN Assignments

• Monitoring

• ACR Database

All (Acct-Interim-Interval)

The Acc-Interim-Interval AVP (AII) set to a non-zero value indicates the desired intermediate charging interval.

Use to include intermediate charging interval in seconds. The OFCS expects to receive either a ACR (Accounting-Request Interim) or ACR (Accounting-Request Stop) AVP within this time-out value.

An instance of the interval Timer starts at the beginning of the accounting session, reset on the receipt of an ACR [Interim] and stops when ACR [Stop] is received. After the specified timer expires, the CDF stops the accounting session with the appropriate error indication.

Indicates a delay in sending ACA after receiving ACR (to simulate a traffic/server load).

• If the delay value is = 0, ACA is sent immediately after receiving the ACR.
• If the delay value is > 0 then ACA will be sent after the delay period expires.

Option: 0 - 30 Seconds

Default: 0 (no delay)

Tcl Parameter: DiaSrvAcaDelay

Starting Subscriber ID

In OFCS testing, the Starting Subscriber ID indicates the first Subscriber ID used in the OFCS test case. You can use the radio buttons to select either IMSI (the default) or MS ISDN.

Tcl Parameter: DiaSrvSubscriberIdType

• IMSI: The Starting International Mobile Subscriber Identifier included as part of the OFCS CDF Subscriber ID.

Range: 5 - 15 digits

Default: 222101000001056

Tcl Parameter: DiaSrvStartingImsi  

• MS ISDN: The starting ISDN directory number for the mobile subscriber. This value is incremented for each mobile subscriber.

Range: Maximum 16 digits

Default: 17962480141

Tcl Parameter: DiaSrvStartingMsIsdn  

APN Assignments

Use the APN pane to define the APN values assigned to bearer contexts. You can define one APN for all contexts or a different APN for every context.

The number of APNs available for input depends on the Default Bearers per Session you selected on the Mobile Subscriber pane of the Emulator Configuration tab. The APN requires a range of  2 - 50 characters and each APN must be unique.

Tcl Parameter: DiaSrvApn0 — DiaSrvApn10

Case Sensitive APNs

Use checkbox to indicate APN Names are case sensitive.

Tcl Parameter: DiaSrvApnCaseSenseEn

Starting Auto-Incrementable APN

Enable to use the Auto Increment Wizard for APNs.  Use the Auto-Increment feature to provision a unique name for each APN.

Default: #(N0)spirent.apn.com

Tcl Parameter: DiaSrvStartingApn

Tcl Parameter: DiaSrvStartingApnEn

Select to specify different profiles for PGW and SGW SUTs on the available tabs. Define Multiple SUT Profiles is available only when you select Multiple SUT Types on the Emulator Configuration tab.

Not selecting Define Multiple SUT Profiles allows you to enter only the SGW SUT Profiles.

Select to enable database creation of received ACR (Accounting Request) by OFCS Node. Once checked , all other related configurations will be enabled.

Tcl Parameter: DiaSrvAcrDatabaseEn  

Default = False

Tcl Parameter: DiaSrvAcrMaxRecords

Range from 1 to 2048

Default = 100

Tcl Parameter: DiaSrvAcrHexEn

Default = False

Tcl Parameter: DiaSrvAcrSubsEn

Default = False

Tcl Parameter: DiaSrvAcrSubsStart

Range from 1 to 1500000

Default = 1

Tcl Parameter: DiaSrvAcrSubsEnd

Range from 1 to 1500000

Default = 1

The resultant database ( <tc_Id>_accouting_records.db will be uploaded by the TAS from test servers /home/spcoast/<s_id>/<ts_id> to result page.

OFCS Node collects the information from the accounting request from SGW and PGW.  SGW and PGW requests can be distinguished by AVP: Node-Functionality (862), which is part of IMS-Information AVP group.  The values are as follows.

    S_GW   = 8,    P_GW   = 9,

Accounting request, Diameter Command Code 271 constitute of so many fields, out of which Landslide should be able to create a SQLite db by the pre configured fields. Since accounting request occurs in every pre configured “interim interval, only the accounting request contains service parameters are logged in to the database.

Service parameters are included in Traffic volumes, AVP code 2046 (in the case of SGW) and in Service Data Container, AVP Code 2040 (in the case of PGW). This way we can reduce the database operation required.

The proposed database tables are shown below. Additionally we provide GUI level configuration to pick and choose which of these fields should be in the Database. The actual number of columns of the Database depends upon the GUI configuration.

Main Table of ACR: Record Hex Dump is for dump everything in hex for the whole diameter message. This is optional, and it is useful if the user want to catch all the information in the ACR messages. The content will be in hex, and may be imported into Wireshark for viewing.

The multiple Traffic volumes or service data container from an ACR is reported under a separate table. Service/Traffic-Data-Table: Each row corresponds to either traffic data volume or service Data container within a single ACR.

Session Id and Accounting Request Number are joint columns between these two tables.

Service Data/Traffic Volume Sequence Number is an internal auto-incremented number to identify individual instance of Service Dat Container/Traffic Volume AVP groups in a single ACR message.

The rest of the columns correspond to what is chosen from GUI:

If all the Check boxes in the GUI are configured, both tables of the DB look as follows.

Accounting Request Table

Service Information Table: