Technology & Communications
Telecommunications
Comprehensive guide to telecom systems including BSS, OSS, billing, network management, and 5G technologies.
$1.8T
Global Revenue
1.2B+
India Subscribers
250+
5G Networks
400EB
Data Traffic
What Engineers Miss When They First Enter Telecommunications
Telecom is, at its core, a billing company with a network attached. This is not a dismissive description — it is the insight that explains most of the hard engineering problems in the sector. The network generates events continuously: calls, SMS, data sessions, roaming connections. Each event has to be collected as a CDR (Call Detail Record), transmitted to the mediation system, rated against the subscriber's plan and applicable tariff rules, aggregated into the billing cycle, and eventually converted into an invoice that the customer accepts as correct. The chain of systems that does this is where the money is and where the complexity lives.
India's telecom market is defined by scale that makes other industries look small. Jio alone has 450 million subscribers, each of whom generates multiple CDRs per day. The mediation platform that processes these records must handle billions of events daily, each with sub-second latency targets for prepaid real-time charging. Airtel and Jio both run 5G networks, which means the BSS/OSS stack must handle a new generation of events — from network slices, from IoT devices, from fixed wireless access subscribers — on top of the existing 4G base. The engineering teams that have built and operated these systems have worked at a scale that translates directly to high-demand skills across any large-scale systems role.
The 5G transition has created a specific set of engineering problems that did not exist in earlier network generations. Network slicing — the ability to create virtual dedicated network segments for enterprise customers with guaranteed QoS — requires real-time orchestration between OSS and the network's SDN controller layer. Charging for 5G services involves new parameters (network slice identifier, QoS class) that the billing system has to understand. The TM Forum Open API programme and 3GPP standards define how these systems should interoperate, and operators who have implemented these standards are ahead of those who built proprietary interfaces.
What Teams Actually Do Day To Day
- 1Operate the mediation platform that collects CDRs from hundreds of network elements across different generations and vendors, normalises heterogeneous event formats into a common schema, detects and repairs gaps (missing CDRs from a node that was offline), and feeds rated records into the billing engine within the required latency window.
- 2Maintain the real-time rating engine for prepaid subscribers — the system that deducts from a subscriber's balance in real time as they make a call or use data, applies the correct rate based on time of day, destination number, and active plan, and sends the network a stop-signal when the balance is exhausted.
- 3Build and maintain the BSS customer management and self-service stack: the CRM that holds subscriber records, the plan catalog that defines every available offer, the self-service app where customers manage their account, the care agent console that customer support uses, and the API layer that connects them all.
- 4Manage OSS provisioning flows that translate customer service orders — activating a new SIM, porting a number from another operator, adding an enterprise VPN service — into network configuration changes executed across multiple network elements with the correct sequencing and rollback handling.
- 5Support regulatory and roaming compliance: interconnect billing with other operators for calls that cross networks, roaming CDR exchange with international partners in TAP (Transferred Account Procedures) format, TRAI reporting submissions, and the lawful interception interfaces that operators are required to maintain.
One End-to-End Flow: A Prepaid Subscriber Makes a Data-Intensive Day on Their 5G Plan
A prepaid subscriber streaming video, making calls, and checking social media generates dozens of CDRs across voice and data sessions. This walkthrough follows the charging and balance management path for a single day.
Subscriber activates a data session
When the subscriber's device connects to the network for a data session, the PCRF (Policy and Charging Rules Function) in 4G — or the PCF in 5G — receives the session start. For prepaid subscribers, it checks the balance and active plan via the OCS (Online Charging System) and authorises the session with a credit quota — a specific number of megabytes the session can use before it must report back for a balance update.
Systems Involved
RAN (Radio Access Network), Core network (PCRF/PCF), OCS, subscriber balance store
Where It Usually Breaks
The credit quota size is a design trade-off. Too small a quota means many round-trips to the OCS, increasing latency. Too large a quota means the subscriber can over-consume by nearly a full quota worth of data after their balance is exhausted if the stop signal arrives late.
Usage reporting triggers balance deductions
As the subscriber uses data, the PCRF/PCF receives usage reports at defined intervals or when the credit quota is consumed. Each usage report triggers an OCS deduction from the subscriber's balance. The OCS checks for applicable free allowances (daily data top-up, night pack) and applies them before touching the main balance.
Systems Involved
PCRF/PCF, OCS, plan allowance management, subscriber balance ledger
Where It Usually Breaks
Allowance application order matters and is a frequent source of billing disputes. If the OCS deducts from the main balance before checking a free-data allowance that should have been consumed first, the subscriber's effective data benefit is less than advertised.
CDRs are generated and collected by the mediation system
At session close (or at periodic intervals for long sessions), the network element generates a CDR containing session start/end times, bytes uploaded/downloaded, subscriber IMSI, cell IDs visited, and APN. The mediation system collects these files from network elements on a schedule, validates format, checks for gaps in sequence numbers, and normalises the CDR into a standard internal format.
Systems Involved
Network element CDR generation, SFTP collection job, mediation platform, CDR validation
Where It Usually Breaks
Network element CDR files delivered out of order (a file from 2am arriving after a file from 3am) must be handled by event-time ordering, not arrival-time ordering. Mediation systems that use arrival time can post charges to the wrong billing period.
CDRs are rated and aggregated for the billing cycle
The rating engine applies the subscriber's plan rates to the CDR's usage parameters. For an all-you-can-use plan, this is straightforward. For a plan with tiered pricing (first 2GB at full speed, then throttled), the rating engine must track cumulative usage within the billing cycle. Rated CDRs are aggregated into the billing account.
Systems Involved
Rating engine, tariff catalog, billing account aggregation
Where It Usually Breaks
Tariff catalog updates that go live mid-billing-cycle without a clear effective-date logic cause some CDRs to be rated at the old rate and some at the new rate in ways that customers cannot reconcile with their statement.
Bill is generated and presented to the subscriber
At billing cycle close, the billing engine generates the invoice showing data usage, voice charges, SMS, value-added services, taxes, and the final amount due (for postpaid) or a statement of usage against the prepaid recharge (for prepaid). The bill is delivered via the self-service app and SMS summary.
Systems Involved
Billing engine, invoice generation, self-service app, SMS notification
Where It Usually Breaks
Subscribers who consumed data on roaming or who had services activated mid-cycle often cannot reconcile their bill without a detailed usage download. Bills that show aggregate charges without line-item detail generate the highest call volume to customer care.
Technology Architecture — How Telecommunications Platforms Are Built
The diagram below reflects how production Telecommunications systems are structured at scale — nine layers from client channels through edge security, API gateway, domain microservices, polyglot data stores, async event streaming, analytics, external partners, and cloud infrastructure. Solid arrows show synchronous REST/gRPC calls; dashed arrows show async event flows via Kafka or a message queue.
Industry Players & Real Applications
🇮🇳 Indian Companies
Reliance Jio
Telecom Operator
Oracle, Custom 5G Stack
India's largest by subscribers, 5G leader
Bharti Airtel
Telecom Operator
Ericsson, Amdocs
Second largest, strong enterprise business
Vodafone Idea
Telecom Operator
Mixed (merger)
Third largest, turnaround in progress
BSNL
State-owned Telecom
TCS, C-DOT
Government operator, 4G rollout
Tata Communications
Enterprise Telecom
Custom, Global Network
Global network and enterprise services
ACT Fibernet
Broadband ISP
Custom Platform
Major fiber broadband provider
🌍 Global Companies
AT&T
USATelecom Giant
Amdocs, Ericsson
Largest US carrier
Verizon
USATelecom Operator
Custom, Ericsson
US 5G leader
Deutsche Telekom
GermanyTelecom Operator
Huawei, Custom
Europe's largest telco
China Mobile
ChinaTelecom Giant
Huawei, ZTE
World's largest by subscribers
Vodafone Group
UKGlobal Telecom
Mixed, Amdocs
Operating in 20+ countries
Orange
FranceTelecom Operator
Custom, Nokia
Major European operator
Singtel
SingaporeTelecom
Amdocs, Custom
Largest in Southeast Asia
🛠️ Enterprise Platform Vendors
Amdocs
Amdocs CES, Billing, CRM, Catalog
Largest BSS vendor globally
Ericsson
BSS, OSS, Network Equipment
Network and software leader
Nokia
NetCracker, Network Management
Network equipment and OSS
Huawei
BSS, OSS, Network Equipment
Major vendor in Asia/EMEA
Oracle Communications
BRM, ASAP, Network Charging
Billing and revenue management
Netcracker (NEC)
Digital BSS/OSS
Full-stack BSS/OSS
CSG International
Singleview, Billing, Revenue Mgmt
Convergent billing specialist
Tecnotree
Digital BSS, Charging
Growing BSS vendor
Real World Use Cases
Business Support Systems
Customer management, billing, revenue
Coming SoonOperations Support Systems
Network management, provisioning, assurance
Coming Soon5G & Network Technology
5G core, RAN, edge computing
Coming SoonEnterprise & IoT
B2B services, IoT connectivity
Coming SoonCore Systems
These are the foundational systems that power Telecommunications operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What Telecommunications Teams Actually Use. Every technology choice in Telecommunicationsis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across Telecommunications is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Telecommunicationsplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java/J2EE
Core BSS applications, billing, CRM
C/C++
Real-time systems, mediation, network protocols
Golang
High-performance microservices, cloud-native BSS
Python
Automation, analytics, ML models
🖥️ frontend
React/Angular
Customer portals, agent desktops
React Native
Customer self-care mobile apps
🗄️ database
Oracle DB
Core billing, CRM, enterprise data
PostgreSQL
Modern BSS applications
TimeScaleDB
Network performance metrics time-series
Redis
Session cache, real-time balance
Apache Kafka
Event streaming, CDR processing
Cassandra
CDR storage, high-volume data
🔗 integration
Diameter Stack
Real-time charging integration
SS7/SIGTRAN
Legacy network integration
TMF Open APIs
Industry-standard REST APIs
Apache Camel
Integration framework
☁️ cloud
Kubernetes
Container orchestration for cloud-native
OpenStack
Telco cloud, NFV infrastructure
AWS/Azure
Public cloud for BSS workloads
Interview Questions
Q1.Explain the difference between BSS and OSS in telecom.
BSS (Business Support Systems) handles customer-facing and revenue operations: CRM, billing, order management, product catalog, revenue assurance. OSS (Operations Support Systems) manages network operations: fault management, performance monitoring, provisioning, inventory, configuration management. BSS deals with 'business' aspects (customer, money), OSS deals with 'network' aspects (elements, services). Modern architectures integrate both through common data platforms and APIs.
Q2.How does real-time charging work for prepaid subscribers?
Real-time charging uses Diameter protocol (Ro interface). When subscriber makes a call, network sends CCR-Initial to OCS (Online Charging System) to reserve balance. OCS checks balance, applies rating, reserves amount for granted quota (e.g., 60 seconds). Periodic CCR-Update requests extend the session. On call end, CCR-Terminate reports final usage. OCS deducts actual usage, releases unused reservation. This ensures no overcharging and immediate balance reflection.
Q3.What is the role of mediation in telecom billing?
Mediation sits between network elements and billing. It collects CDRs (Call Detail Records) from switches, routers, and other elements. Functions: normalization (different formats to standard), enrichment (add customer/product info), validation (check mandatory fields), duplicate detection, error handling, aggregation. Output goes to rating/billing engine. Critical for accuracy - any issue means revenue leakage or billing errors.
Q4.Explain the TMForum Frameworx and Open APIs.
TMForum is telecom industry consortium. Frameworx includes: eTOM (business process framework), SID (information framework - data model), TAM (application map), and TM Forum Open APIs. Open APIs are REST-based APIs standardized for BSS/OSS integration. Examples: TMF620 (Product Catalog), TMF622 (Product Order), TMF678 (Customer Bill). Using TMF APIs enables vendor interoperability and reduces integration costs.
Q5.How do you handle high-volume CDR processing?
Design for scale: Use distributed processing (Kafka for streaming, Spark for batch). Implement parallel processing with partitioning by MSISDN or time. Use in-memory processing for real-time needs. Implement idempotency to handle reprocessing. Use columnar storage (Parquet) for analytics. Set up dead-letter queues for errors. Monitor throughput, latency, and error rates. Typical scale: billions of CDRs/day, sub-second processing latency for online charging.
Q6.What are the key considerations in BSS transformation?
Migration strategy: big-bang vs phased vs parallel run. Data migration is critical - customer data, balances, usage history. API-first approach for gradual modernization. Consider business continuity - billing cannot stop. Training for operations team. Testing: regression, performance, billing accuracy. Typical approach: new digital stack for new products, gradual migration of base. Cloud-native architecture for agility. Cost: BSS transformation is multi-year, $50M+ investment for large operators.
Glossary & Key Terms
BSS
Business Support Systems - CRM, billing, order management systems
OSS
Operations Support Systems - network management, provisioning systems
CDR
Call Detail Record - record of voice/data usage event
HLR/HSS
Home Location Register/Home Subscriber Server - subscriber database
OCS
Online Charging System - real-time prepaid charging
MSISDN
Mobile Station International Subscriber Directory Number - phone number
IMSI
International Mobile Subscriber Identity - SIM card identifier
VAS
Value Added Services - SMS, MMS, content services
MVNO
Mobile Virtual Network Operator - uses another operator's network
NRA
Number Range Allocation - managing phone number pools
Diameter
AAA protocol for charging, policy, authentication in LTE/5G
TMF
TM Forum - telecom industry standards organization