dsTest supports both server emulation and client simulation for the Diameter Credit-Control Application (DCCA) CC Interface application. Test PDN Gateway (PGW) Credit-Control (CC) functions with our Online Charging System (OCS) Emulator. Use the PGW’s Policy and Charging Enforcement Function (PCEF) simulation with the CC Interface application to test the capacity and performance of an OCS. Use the OCS Emulator and the CC Interface application in tandem to test Diameter Routing Agents (DRA), Diameter Proxies, Relay Agents, and Redirect Agents.
The CC Interface application supports methods for:
- Quota management
- Simple Debit/Credit
- Balance checks
- Price inquiries
- Failure Procedures
Both session-based and event-based charging scenarios are supported. A complete set of events that can be generated with the CC interface can be found here. Use the Diameter Dictionary to validate your messages and CC test scenario.
PGW/PCEF Testing (Server Emulation)
The OCS Emulator executes DCCA procedures based on configurable subscriber profiles, credit pools, and tariffs, responding to charging events from PGWs and eliminating the need to dedicate a production server to lab activities. You can reconfigure credit balances in real-time, simulating the expiration of credit and testing a PGW’s compliance with network credit policies.
The OCS Emulator provides mobile subscriber credit control services for the CC interface—all of the functionality required by a PGW plus all of the benefits of an emulator.
Configurable services, quota allocation rules, credit pools, tariffs, and subscriber profiles give you the flexibility to fully test charging strategies for new prepaid services before they are deployed in a live network.
- Test a PCEF’s usage reporting;
- Reconfigure credit balances with run-time commands to simulate the expiration of credit, testing a PCEF’s termination behavior;
- Control interface to change the emulator’s behavior;
- Reconfigure your emulator in seconds by simply loading a new configuration file;
- Simulate a non-responsive server by pausing the emulator or simulate intermittent issues by pausing and resuming;
- Disable individual subscribers during the test run, generating unknown subscriber errors.
One OCS Emulator can support any mixture of interfaces, up to 1000 client connections. Multiple OCS Emulators can be instantiated on a single server. In this mode each emulator can support multiple interfaces, up to an aggregate of 1000 client connections across all emulators. The emulators are fully independent and their subscriber databases may also be independent, overlap, or be duplicated.
OCS Testing (Client Simulation)
The CC Interface application can be used to simulate a PGW’s charging functionality to determine the impact of new charging strategies or OCS features and standards before they are deployed in a network. The CC Interface application allows users to validate OCS performance and capacity in a realistic network environment, replicating the deployment configuration.
Execute timed chains of test events with a run-time command or during an automated test to generate Credit Control Requests (CCRs) towards the OCS. Verify that the OCS sends the correct answers (CCAs) to the gateway.
- Construct session-based charging event cycles – initiate the session with reserve unit requests, generate combined debit unit and reserve unit requests to simulate ongoing resource usage, and generate final debit unit requests when the session ends or when credit expires
- Generate debit unit requests to simulate event-based charging events
Multiple PGW/PCEF simulators can be instantiated on a single server, each with scalable subscriber loads and transaction rates. In this mode, up to 1000 independent nodes may be simultaneously simulated. The nodes are fully independent and their subscriber configurations may also be independent, overlap, or be duplicated.
Advanced Testing Features
SmartEvents — Alter application behavior or coordinate multiple interface applications with SmartEvents. Our programmable, subscriber-level state machine gives you the ability to define handlers for specified application events that can then cause an event in another application to be executed. You can also configure handlers to modify subscriber information during run-time, introduce timers, or randomize subscriber behavior based on configurable probabilities to name a few of the many options in one of dsTest’s most powerful features.
SmartMessageElement — Insert, delete, or replace elements in Diameter, RADIUS, MAP, LDAP, GTP, REST or SOAP messages with our SmartMessageElement solution. Define proprietary signaling or corrupt elements to facilitate negative testing. You can specify when your elements are used with SmartEvents.
Traffic Profile — Draw the shape of your test actions across time with Traffic Profile. You can define the rate for any action as a static rate or reference a Traffic Profile configuration, which also means that multiple Traffic Profiles can be running currently. Use Traffic Profile in conjunction with the randomizing features in SmartEvents to design a test that more truly simulates real-world network activity.
Diameter Dictionary — Define a set of message templates against which all messages will be validated with our Diameter Dictionary. Whether you’re load testing or testing functionality all messages are validated.
dsTest provides rich sets of measurements for the CC Interface application:
- Transaction and transport layer attempts, successes, and failures
- Transaction duration, transactions-per-second, and round-trip delay
- Message and byte counters
- Errors encountered and error indications received in messages
You can read more about the reporting features offered with dsTest and dsClient here.