
πΆ Telecom Β· Data Flow
How network usage becomes a customer bill: call detail records, mediation, rating against the plan, billing and invoicing.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagramβ¦
Data flow for telecom billing: network elements (switches, packet core, SMSC) produce CDRs; mediation collects, validates, de-duplicates and normalises them; the rating engine prices each record using the customer's plan from the product catalog and applies allowances; at cycle end billing applies discounts and taxes (GST), produces invoices and posts them to the customer's account and the general ledger; disputes come back as adjustments. Number the processes.
flowchart LR
subgraph EXT ["External entities"]
ne["Network Elements (Switches, Packet Core, SMSC)"]
cust["Customer"]
gl["General Ledger System"]
end
subgraph PROC ["Processes"]
p1("1.0 Collect and Validate CDRs")
p2("2.0 Rate Usage Records")
p3("3.0 Apply Discounts and Taxes")
p4("4.0 Generate and Post Invoices")
p5("5.0 Process Billing Disputes")
end
subgraph STORE ["Data stores"]
d1[("D1 Raw and Normalized CDRs")]
d2[("D2 Product Catalog")]
d3[("D3 Customer Account and Allowance Data")]
d4[("D4 Rated CDRs")]
d5[("D5 Billing and Invoice Data")]
d6[("D6 Dispute and Adjustment Data")]
end
ne -->|"Raw CDRs"| p1
p1 -->|"Validated and Normalized CDRs"| d1
d1 -->|"Normalized CDRs"| p2
d2 -->|"Customer Plan Details"| p2
d3 -->|"Allowance Data"| p2
p2 -->|"Updated Allowance Balances"| d3
p2 -->|"Rated CDRs"| d4
d4 -->|"Rated CDRs"| p3
p3 -->|"Discounted and Taxed (GST) CDRs"| d5
d5 -->|"Cycle-End Billing Details"| p4
p4 -->|"Invoice and Account Details"| cust
p4 -->|"General Ledger Entries"| gl
cust -->|"Billing Dispute Details"| p5
p5 -->|"Dispute Records"| d6
p5 -->|"Account Adjustment Data"| d3
p5 -->|"Invoice Adjustments"| d5
d5 -->|"Dispute History Context"| p5A data flow diagram with 8 processes and outside parties, 6 data stores and 17 data flows.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
A simplified 5G standalone network: phones and radio sites, the 5G core network functions, and the connection out to the internet.
The states a mobile SIM goes through, from stock in the warehouse to active service, suspension, porting out and deactivation.
The IT stack of a mobile operator: business support systems (CRM, billing, orders) and operations support systems (inventory, provisioning, assurance).
How a subscriber moves their number to another operator: porting code, request through the clearing house, donor approval and cutover.
What happens when a customer recharges a prepaid mobile: plan selection, payment, balance update in the charging system and confirmation.
A schema for subscriber data: customers, accounts, subscriptions (numbers), plans, SIMs and bills.