Skip to content
WorkspaceLet's simulate→
CortexSim/Industries/TelecommunicationsReference model
Telecommunications

Keep the session.
Account for the usage.

Subscriber state, session events, quota reservations and charging results must agree across the service chain—even when events arrive late or twice.

Design your evaluation
01Session identity across dependencies02Quota and reservation consistency03Usage-to-charge reconciliation
The session boundary
Account for the quota through the session lifecycle. — Session activeThe illustration separates consumed units from the outstanding reservation. The original grant remains the accounting boundary.ONE SUBSCRIBER / ONE SESSIONUsage boundaryCONSUMED + RESERVEDSESSION IDENTITYConsumedReservedILLUSTRATIVE ALLOCATIONPreserve the original grant
Interactive industry illustration · authored examples, not live operations
01/ 03
Session active

The illustration separates consumed units from the outstanding reservation. The original grant remains the accounting boundary.

Authored units illustrate session accounting. They do not represent measured network throughput or certified charging compatibility.
Subscriber, session and charging continuity

Every unit of usage needs a consistent service story.

A subscriber session is not a single request. It is a sequence of reservations, usage updates, quota decisions and final charges moving across independently timed services.

Events can arrive late, be replayed or cross a tariff change. Charging may recover before session state does. A service can appear healthy while consumed units, outstanding reservations and billed amounts no longer reconcile.

WHERE TO APPLY SIMULATION

Charging evolution

A product or tariff change alters the rules behind a familiar interface.

THE EXPERIMENT

Compare reviewed charging profiles with explicit quota, tariff and event-time assumptions.

THE EVIDENCE

Versioned charging decisions and independently expected outcomes.

CONNECTED TO YOUR REALITY

Connect subscriber context to the charging boundary.

Keep the systems you depend on. Bring a reviewed slice of their records, interfaces and dependencies into an isolated evaluation.

EXPLORE THE CONNECTION MODEL
01Your existing estate

Select a system to inspect its proposed mapping.

02Reviewed boundary

Reviewed data

Read-only source profile

Approved scopeVersioned sourceTraceable lineage
CORTEXSIM

Versioned industry twin

Records + rules + dependencies

03Isolated experiments

Challenge the candidate

Replay, interrupt, migrate and change assumptions against a retained baseline.

Review the evidence

Inspect differences, unresolved assertions and source provenance before accepting a change.

Explore MCP connectivity
SELECTED SOURCE

Subscriber management

Approved source view

Example input scope

Subscriber reference, service status and product version.

What enters the model

Bind each session to an explicit subscriber and product state.

Bring a minimized, versioned view of the records needed for the question. Review field mapping, freshness and provenance before promoting a model.

The source remains authoritative. Credentials and source-specific enforcement stay with the customer.

Approved fieldsSource snapshotVersioned mapping

These are evaluation architecture patterns, not a catalog of certified native vendor connectors. Source access, field mappings and interface behavior must be qualified for your environment.

THE SCENARIO LAB

Inspect the service chain when events stop arriving in order.

Will a charging or service change preserve the relationship between usage and outcome?

CHOOSE A SCENARIO

Six starting points. Each exposes a different dependency, assumption or recovery boundary.

THE EXPERIMENT

Charging-service recovery

The charging dependency stops responding during an active session.

ReservationQuota reservationThis scenario challenges this boundary.
ASSERTION TO VERIFY

Reservation and consumption remain reconciled across recovery.

DECISION IT SUPPORTS

Compare service continuity assumptions and unresolved charge states.

Illustrative evaluation brief

Restarting charging while subscriber sessions remain active.

An illustrative operator introduces a charging-service update. Sessions may continue sending usage while the dependency restarts, and the final termination event may arrive after recovery.

01

The decision to investigate

Replay a bounded subscriber and product profile with explicit event ordering. Compare grants, consumption, release and final charge references across the restart boundary.

02

The evidence to take into review

Correlated session events, tariff version, reservation changes, duplicate-event handling and usage-to-charge reconciliation.

Scope a similar evaluation
DOMAIN DEPTH

Reconcile the session, not just the message count.

Reconcile delivered usage and authored charges without repeated effects.

A TRACEABLE BUSINESS JOURNEY

Follow the identity through every handoff.

REVIEW AT THIS BOUNDARY

Subscriber

Correlate each usage event to a declared session.

Pin the source version, expected state and permitted transition. Retain a lineage reference so a reviewer can trace the result back to the input.

BUSINESS RULES TO PRESERVE
01

Correlate each usage event to a declared session.

02

Retain the tariff and allowance version used in the result.

03

Replayed events must preserve quota and charge identity.

04

Reconcile reservation, consumption and release independently.

ONE MODEL. DIFFERENT REVIEW RESPONSIBILITIES.

Charging operations

Inspect session exceptions and unmatched usage.

BSS / OSS architecture

Review interfaces and service dependencies.

Revenue assurance

Challenge usage and charge reconciliation.

Network engineering

Evaluate declared failure domains and recovery paths.

FROM EXPLORATION TO EVIDENCE

Build a focused first evaluation.

Choose the scenarios that matter to your team. Take a concrete scope into an architecture and domain review.

INCLUDE IN YOUR EVALUATION BRIEF
02/ 06

Scenarios selected

One session profile, one tariff and one charging interruption.

A local JSON brief with system mappings, selected scenarios and acceptance questions.

01

Define the boundary

One session profile, one tariff and one charging interruption.

Architecture & domain owners
02

Establish the baseline

Correlated synthetic session, usage, reservation and charge examples.

Source & model owners
03

Challenge the candidate

Run the selected scenarios in an isolated, version-pinned environment. Preserve failures and unresolved assertions.

Simulation & engineering teams
04

Review acceptance

Usage-to-charge comparisons, quota assertions and restart evidence for the declared profile.

Independent reviewers

Reference behavior covers declared authored and source-backed profiles. Native vendor compatibility, regulatory acceptance and production deployment require separate qualification.

QUESTIONS FOR YOUR REVIEW

Make the scope explicit.

A credible evaluation names its assumptions, its evidence and the decisions that remain with your team.

Read the evaluation playbook ↗
Does this emulate every network protocol or vendor charging stack?

No. Model fidelity depends on the declared interface, reference profile and reviewed examples. Vendor-specific behavior requires its own compatibility evidence.

Can network and charging dependencies be examined together?

An evaluation can connect authored service dependencies to the session workflow. The relationship must be declared and tested; a diagram alone does not establish physical-network fidelity.

How are tariff changes evaluated?

Pin the original and proposed rules, retain the session inputs, and compare results against independent expected usage and charge assertions.

Telecommunications

Bring your hardest handoff. Start there.

One session profile, one tariff and one charging interruption.

Design your evaluation Explore MCP connectivity