Telecom software development: BSS, OSS, network APIs and the rules
Telecom software development is the work of building the systems that telecom operators, mobile virtual network operators (MVNOs), internet service providers and resellers use to sell, deliver, bill and support their services, and the software other businesses use to work with telecom networks. Telecommunication software development has its own vocabulary, its own standards and its own regulations. This guide explains the main system types, the open standards that connect them, the EU and US rules that shape them, and where custom software makes sense next to the platforms most operators buy.
The short version
- Telecom systems split into BSS (customer and business) and OSS (network and service operations).
- Most operators buy core billing and network systems and build what differentiates them: self-service, onboarding, partner tools and integrations.
- Build to open standards, mainly TM Forum Open APIs between business systems and CAMARA for network APIs.
- EU rules on contract information, switching and number porting are written into the customer journey, not only into the terms.
- Usage data is personal data with its own retention rules.
BSS and OSS: the two halves of telecom software
| Area | Systems | What they do |
|---|---|---|
| BSS: business support | Product catalogue, ordering, CRM, rating and billing, payments, self-service apps and portals, partner and reseller portals | Define what is sold, take the order, charge for it and support the customer |
| OSS: operations support | Service and resource inventory, provisioning and activation, number management, monitoring, fault and ticket handling | Deliver the service on the network, keep it running and fix it when it fails |
| Network and service platforms | Mobile core, voice and messaging platforms, broadband access, SIM and eSIM management | Carry the traffic and produce the usage records billing needs |
An order travels from the BSS to the OSS: the customer chooses a product, ordering checks it, the OSS provisions the line, the number or the connection, and the network starts producing usage. Usage records then travel back to rating and billing. Much of the cost and many of the failures in telecom software sit in those hand-offs between systems, which is why standards matter so much.
The standards that connect the systems
TM Forum Open APIs. TM Forum, the industry association for operators and their suppliers, publishes a set of standard REST interfaces for business functions. Its public repositories on GitHub list, among others, TMF620 Product Catalog, TMF622 Product Ordering, TMF629 Customer Management and TMF641 Service Ordering, published under the Apache 2.0 licence (read 11 November 2026). Systems that speak these interfaces can be connected or replaced without rewriting every integration, which is the most practical protection against being locked into one vendor.
CAMARA network APIs. CAMARA is a Linux Foundation project that defines common APIs for telecom network capabilities, so that an app team can use the same interface across operators. Its API list includes Number Verification, SIM Swap, Device Swap, Location Verification, Know Your Customer Match, Age Verification and Call Forwarding Signal (read 11 November 2026). These are among the most interesting areas of telecom software for companies outside telecom: a bank can check whether a customer's SIM was changed recently before approving a transfer, and an app can confirm a phone number silently instead of sending a one-time code.
EU rules that shape telecom software
The European Electronic Communications Code, Directive (EU) 2018/1972, sets end-user rights that the software has to deliver, not only the legal terms (read 11 November 2026):
- Contract information and summary (Article 102). Providers give consumers specified information before the contract, plus a contract summary. Recital 261 says the summary should ideally be no longer than one single-sided A4 page, or up to three pages for bundles. The ordering flow has to generate and record it.
- Switching internet access (Article 106(1)). Loss of service during switching shall not exceed one working day, and the receiving provider leads the process.
- Number portability (Article 106(5)). End-users who have agreed to port a number to a new provider shall have it activated within one working day from the agreed date. If porting fails, the transferring provider reactivates the number.
- Contract duration (Article 105). Termination conditions must not act as a disincentive to changing provider.
Porting and switching deadlines measured in working days mean the systems must be integrated end to end: the order, the national porting process, provisioning and billing have to move on the same day, with automatic fallbacks when one step fails.
Usage data. Article 6 of the ePrivacy Directive requires traffic data to be erased or made anonymous when no longer needed for transmitting a communication. Traffic data needed for billing and interconnection payments may be processed only until the end of the period during which the bill may lawfully be challenged or payment pursued (read 11 November 2026). Billing and analytics systems need retention rules built in, on top of the GDPR.
A note on the US: caller ID authentication
In the United States, the STIR/SHAKEN framework authenticates caller ID to fight spoofed robocalls. According to its Wikipedia summary, which cites the FCC, the FCC has required large carriers to use the protocols since 30 June 2021 (read 11 November 2026). Voice software that originates or carries traffic in the US network has to sign or verify calls accordingly, and the FCC's current rules should be checked for the provider's own category before launch.
Build or buy
Few operators should write their own rating and billing engine. It is complex, heavily regulated and offered by mature platforms. Custom telecom software pays in the places where operators actually compete with each other:
| Usually buy | Often build |
|---|---|
| Rating and billing engine | Self-service app and portal: plans, usage, top-ups, eSIM activation, support |
| Mobile core and network platforms | Online sales and onboarding, including identity checks and number porting requests |
| Payment processing | Partner, dealer and reseller portals with commissions |
| Standard CRM | Integrations between platforms, built on TM Forum Open APIs |
| Network monitoring tools | Dashboards that combine network, ordering and billing data for operations |
Products built on CAMARA network APIs, for fraud prevention or phone number verification, are usually custom work, because they sit inside the company's own sign-up and payment flows.
MVNOs and smaller providers often run on a host operator's or an enabler's platform. The custom layer on top, the customer app, onboarding and support tools, is where their brand lives and where they can move faster than the larger operators.
What makes telecom projects hard
- Many systems, one customer. Every customer action touches several systems; design the hand-offs and their failure cases first.
- Money at scale. Rating errors multiply across every subscriber; test with real usage patterns and reconcile billing against the network records.
- Fraud. SIM swap fraud, account takeover and subscription fraud target onboarding and self-service; build checks into those flows.
- Regulated journeys. Contract summaries, porting and switching have deadlines and content rules; log each step as evidence.
- Uptime. Self-service and activation are needed at all hours; plan for monitoring and on-duty support.
How we help
We build the customer-facing and integration layers of telecom products: self-service apps and portals, onboarding and porting flows, partner and reseller tools, dashboards and integrations between platforms, built to open interfaces where they exist, hosted in the EU, with the code in the client's own repository. See custom software development and app development. For connected devices and SIM-based products, see IoT software development; for payment and fraud checks, see fintech app development; and for an outside view of an existing platform, software consulting.
Questions people ask
What is telecom software development?
It is building the software that telecom operators, MVNOs, internet providers and resellers use to sell, deliver, bill and support their services, plus the software other companies use to work with telecom networks, such as network APIs for fraud checks. It covers business support systems (BSS), operations support systems (OSS) and the customer apps and portals on top.
What is the difference between BSS and OSS?
BSS faces the customer and the business: product catalogue, ordering, billing, customer management and self-service. OSS faces the network: service inventory, provisioning, activation, monitoring and fault handling. An order flows from BSS to OSS, and usage flows back from the network to billing.
Should a telecom company build or buy its BSS?
Most buy the core, such as rating and billing, from a specialist platform, because it is complex and heavily tested. Custom software pays where the company competes: self-service apps and portals, onboarding, partner and reseller tools, integrations between platforms and products that standard systems do not support.
What are TM Forum Open APIs?
A set of standard REST interfaces for telecom business functions, such as TMF620 Product Catalog, TMF622 Product Ordering, TMF629 Customer Management and TMF641 Service Ordering. TM Forum publishes them under the Apache 2.0 licence. Building to them makes it easier to replace or connect systems later.
What are CAMARA network APIs?
CAMARA is an open source project under the Linux Foundation that defines common APIs for telecom network capabilities, such as number verification, SIM swap checks and device location verification. A bank or app can use them, through operators that offer them, to check a user's phone number or detect a recent SIM change before a sensitive action.
Sources
- Directive (EU) 2018/1972, the European Electronic Communications Code, Articles 102, 105 and 106 and recital 261 (read 11 November 2026)
- Directive 2002/58/EC on privacy and electronic communications, Article 6 (read 11 November 2026)
- TM Forum Open APIs on GitHub (read 11 November 2026)
- CAMARA Project, Linux Foundation (read 11 November 2026)
- STIR/SHAKEN, Wikipedia (read 11 November 2026)