Frameworks & Standards Overview
Navigate the frameworks, standards, reference architectures and industry initiatives that shape modern telecom BSS, OSS, networks and digital services.
Modern telecom architecture is shaped by several standards bodies and industry initiatives. They address different layers of the business, information, application, service and network landscape — and they overlap, borrow from each other, and occasionally compete. Use this reference to understand what each framework is, what it covers, how it relates to the others, and where it fits in a modern telecom architecture.
Organisations and ecosystems
TM Forum
Telecom architecture & operations
Open Digital Architecture • Business Process Framework • Information Framework • Functional Framework • Open APIs
GSMA
Mobile industry association & network-API initiatives
GSMA Open Gateway
Mplify (formerly MEF)
Service orchestration & NaaS standards
Lifecycle Service Orchestration • Network-as-a-Service (NaaS) standards
ETSI
ICT & telecom technical standards
ETSI NFV • ETSI ZSM
ITU-T
International telecommunications recommendations
ITU-T Recommendations
Find a framework, standard or initiative
Open Digital Architecture (ODA)
Lets operators and vendors describe, buy and assemble BSS/OSS as interchangeable components instead of monoliths, so that a system can be replaced without redesigning everything it touches.
Business Process Framework (eTOM)
Gives business, IT and vendors one process map to point at, so that a requirement, a system, a KPI or a gap can be located unambiguously.
Information Framework (SID)
Stops every system inventing its own meaning of "customer" or "service", so that data can flow between systems and be reconciled when it does not.
Functional Framework (formerly TAM)
Gives a product-neutral checklist of functions, so that portfolios can be rationalised and vendors compared by what they do rather than what they are called.
Open APIs
Makes BSS/OSS systems from different vendors interoperable at defined seams, so that integration is configuration against a known interface rather than a bespoke project every time.
GSMA Open Gateway
Turns network capabilities into a product developers can buy once and use globally, instead of integrating separately with every operator.
CAMARA APIs
Abstracts operator-specific network interfaces into developer-friendly APIs that behave identically on every network, so that an application does not need to know whose 5G core it is talking to.
3GPP specifications
Makes a phone from one vendor work on a network built from another's equipment, in any country, and lets operators build networks from multi-vendor components.
Lifecycle Service Orchestration (LSO)
Makes ordering, quoting and assuring a connectivity service between two carriers a machine-to-machine exchange instead of an email and a spreadsheet.
Network-as-a-Service (NaaS) standards
Gives enterprises and partners a consistent way to buy connectivity across many providers, and gives providers a repeatable product they can automate end to end.
ETSI NFV (MANO)
Lets network functions run as software on commodity infrastructure with a standard way to deploy, scale and heal them, instead of as fixed-function appliances.
ETSI ZSM (Zero-touch network & Service Management)
Sets the target for autonomous operations, so that vendors and operators build management domains that can be composed into closed-loop automation rather than islands of scripts.
ITU-T Recommendations
Makes networks in different countries and from different eras interconnect, by giving governments and operators one set of internationally agreed technical recommendations.