3GPP is the partnership that specifies the mobile network itself — the radio, the core, and the interfaces between them, from 3G through 5G and beyond. For API work the relevant surface is network exposure: the Network Exposure Function (NEF) and its predecessor SCEF, which define how capabilities inside the mobile core are made available to applications outside it.
3GPP
3GPP is the layer everything else in telecom stands on. Its specifications are the reason a phone works in a country its owner has never visited, and they are published openly and in enormous volume.
- Network exposure - NEF in 5G and SCEF in 4G are the standardised doors through which an application reaches core-network capability; CAMARA APIs are ultimately fronting these.
- Published in the open - The specification corpus is free to download, and the API-shaped subset is substantial: 116 machine-readable definitions were harvested for The State of Telecom APIs.
- Release-based - Capability arrives in numbered releases the whole industry plans against.
- Below the commercial layer - 3GPP defines what is technically possible; whether any of it is purchasable by a developer is decided several layers higher.
3GPP is the clearest illustration of the sector’s central paradox. The organizations that specify telecom publish the most machine-readable material in it and sell nothing, while the operators who could sell it publish the least. Half the machine-readable telecom estate belongs to bodies with nothing to sell.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Telecom APIs
116 machine-readable definitions harvested — part of the 351 freely downloadable contracts published by six bodies that sell nothing.
