Telecom Roaming - How Network API work together with TAP and BCE
How Network API work together with TAP and BCE for Telecom Roaming
Introduction
When we think about International Roaming, we usually think about a customer using her phone abroad and getting charged for data, voice, or SMS. Behind the scenes, this simple customer experience involves a complex ecosystem of network functions, BSS/OSS systems, and inter-operator settlement processes. For decades, the wholesale settlement part of this ecosystem has been handled by TAP, RAP, and more recently, BCE.
In parallel, the telecom industry has been working on a completely different set of capabilities: standardized Network APIs. These APIs, championed by the GSMA Open Gateway initiative and the CAMARA project, allow applications to access programmable network capabilities. One of these APIs is the Device Roaming Status API, which can tell an application whether a specific device is currently roaming or not.
The natural question that arises is: Can Network APIs replace TAP and BCE? The answer is no, and understanding why reveals an important architectural distinction in modern Telecom Roaming.
Network APIs do not replace TAP, RAP or BCE because they solve a different problem. CAMARA and GSMA Open Gateway expose network capabilities to applications in a standardised, API-driven manner, while TAP, RAP and BCE support wholesale roaming data exchange, charging, invoicing and settlement between operators. The important evolution is therefore not Network APIs replacing roaming settlement. It is the emergence of two complementary capabilities: programmable network access for application use cases, and modernised wholesale billing, charging and settlement through BCE alongside existing TAP-based processes.
![]() |
| Telecom Roaming Ecosystem: Network API and Wholesale Settlement Domains |
The Wholesale Settlement Domain: TAP, RAP, and BCE
Before we go further, let me clarify an important distinction that often gets blurred. Retail charging is what the subscriber pays according to their home operator's tariff. Wholesale settlement is what the operators pay each other. The Inter-Operator Tariff (IOT) is the wholesale rate between operators. It is not the subscriber's retail roaming tariff. TAP and BCE handle the wholesale side.
TAP (Transferred Account Procedure)
TAP is the GSMA standard used by roaming partners to exchange structured wholesale roaming usage and accounting records. The Visited Network generates TAP records from roaming usage, which are exchanged with the Home Network for validation, rating and wholesale settlement.
TAP has been the industry standard for over 30 years and is deeply integrated into the billing systems of virtually every operator. TAP 3.12 remains the latest TAP format generation, maintained through GSMA specifications TD.57 (Format Specification) and TD.58 (Implementation Handbook).
GSMA's strategic direction is toward BCE for newer wholesale roaming requirements, while TAP 3.12 continues to be maintained through revisions to the associated GSMA specifications and remains important during the transition.
RAP (Returned Account Procedure)
RAP is the GSMA standard, defined in TD.32, that provides the standardized mechanism for returning rejected TAP records and associated rejection information to the originating partner. When a Home Network validates TAP files against business rules and tariff agreements, errors are returned to the Visited Network via RAP. The Visited Network then corrects and resubmits these records.
BCE (Billing and Charging Evolution)
The core motivations for BCE are the new requirements of 5G SA, IoT, network slicing, and satellite connectivity. However, BCE is not limited to 5G. GSMA's current material explicitly states that BCE is designed to support both existing and future roaming services, including traditional cellular connectivity.
Aggregation: BCE supports aggregated usage reporting, while also allowing detailed records where the business case requires them. This is essential for IoT devices that generate millions of small data packets, and it allows usage to be mapped to specific services for correct tariff application.
Flexibility: BCE allows operators to negotiate and apply more flexible charging models, including event-based charging, flat fee charges, daily or monthly IMSI charges, and creative tier models such as back to first and step tiers.
Scalability: BCE is designed to handle the volume and complexity of 5G SA, IoT, network slicing, and NTN roaming. It supports operator groups, 5G SA traffic exchange, and invoice confidentiality.
Important note on TAP0 and migration: TAP0 provides a simplified TAP-based mechanism that can be used in BCE migration scenarios where roaming partners still require TAP-based exchange. It uses simplified TAP 3.12-based records, including zero-rated records, to support the exchange of selected usage information without carrying the full charging detail of conventional TAP records. This provides a transition path between existing TAP-based processes and newer BCE-based wholesale charging and settlement models.
From an architectural perspective, TAP and BCE should therefore be viewed as coexisting settlement mechanisms during the migration period. The applicable mechanism depends on the capabilities of the roaming partners, their bilateral agreements, the services being exchanged, and the wholesale charging and settlement model being used.
The important point is that BCE is not simply a new file format replacing TAP. It introduces a more flexible wholesale charging and settlement model that can support aggregated usage, different charging models, and newer service types, while existing TAP-based processes can continue to operate where required.
The Network API Domain: Programmable Network Capabilities
GSMA Open Gateway and CAMARA
The GSMA Open Gateway initiative provides a framework for exposing selected operator network capabilities through standardized Network APIs. The APIs are defined through the CAMARA project, an open-source initiative under the Linux Foundation, to make network capabilities accessible to applications through common and interoperable interfaces.
One of the APIs relevant to roaming is the Device Roaming Status API. It provides an application with the current or latest known roaming state of a device based on information available from the operator network.
The Device Roaming Status API
Consider an application that needs to know whether a customer's device is currently roaming. Instead of integrating directly with the operator's internal network systems, the application can invoke the Device Roaming Status API through the applicable Open Gateway deployment. The request contains a supported device identifier, and the API provider handles the required authentication, authorisation, policy and consent requirements according to the API and deployment model.
The response provides more context than a simple roaming = true/false indication. Depending on the API version and provider implementation, it can include the device's roaming status, the visited country when the device is roaming, and the lastStatusTime indicating when the reported status was last updated.
- Roaming status: Indicates whether the device is currently reported as roaming.
- Visited country: Provides country information when the device is reported as roaming, such as MCC and ISO country code.
- Last status time: Indicates when the reported roaming state was last updated.
The API should therefore not be interpreted as a location-tracking interface. It does not expose precise location such as GPS coordinates. The information is related to the device's roaming state and, where supported, the country in which the device is roaming.
There is also an important distinction around the term real-time. An API request can provide an application with the latest available roaming state at the time of the request, but this does not necessarily mean that the API performs a live interrogation of the visited network for every request. The lastStatusTime field provides an indication of the freshness of the reported state.
CAMARA also defines a Device Roaming Status subscription API. Instead of repeatedly querying the device status, an application can use the subscription model to receive notifications when the roaming state changes, subject to the supported API version and operator implementation.
Let me walk you through the request and response flow of the Device Roaming Status API.
![]() |
As you can see from the flow above, the API provides the application's current or latest known roaming state. The application sends a request using a supported device identifier, and the API provider applies the required authentication, authorisation, consent and policy controls according to the API and deployment model. The response can include the roaming status, visited country information when the device is roaming, and the lastStatusTime indicating the freshness of the reported status. The API invocation itself does not exchange TAP or BCE settlement files. Any separate wholesale roaming usage generated by the underlying connectivity continues through the applicable charging and settlement processes.
Deployment and roaming considerations: Depending on the Open Gateway deployment model, an application can integrate directly with an operator or access operator capabilities through an aggregation model. In roaming scenarios, the API functionality may also depend on coordination or federation between the home and visited operators, depending on where the required network data resides and how the particular API is implemented. GSMA's OPG.10 guidelines cover direct integration, aggregation, federation-related interactions, and the handling of API requests in roaming scenarios.
How Applications Use the Device Roaming Status API
Let me give you some practical examples:
Fraud detection: A bank can check whether a customer's phone is roaming when a transaction occurs. If a transaction appears to originate from a domestic location but the phone is roaming abroad, this could indicate fraud. The API can provide an additional signal for fraud detection and risk assessment.
Risk assessment: Financial institutions can use roaming status as one input to a risk score for online transactions.
Contextual services: A travel application could offer local connectivity options or travel information when it detects that a user has started roaming.
Cost optimization: Businesses can use roaming status information to trigger customer notifications, apply business rules, or establish appropriate data usage and routing policies.
The Two Domains Work Together
These are not sequential protocol layers in the OSI or 3GPP sense. They are two distinct functional domains that can coexist around the same underlying roaming connectivity and subscriber usage.
The important architectural distinction is that the Network API domain and the wholesale settlement domain have different responsibilities in the roaming ecosystem.
Domain 1: Programmable Network Capabilities (Network APIs). The Network API domain exposes selected network capabilities and current or latest known network state to applications. For example, the Device Roaming Status API can provide roaming status and, where available, visited country information. Applications can use this information for fraud detection, risk assessment, regulatory checks, or contextual services. It does not perform wholesale billing or settlement.
Domain 2: Wholesale Billing, Charging and Settlement (TAP, RAP, BCE). This domain supports the exchange, validation, rating, reconciliation and settlement of wholesale roaming usage between operators. TAP and RAP support established roaming settlement processes, while BCE provides a more flexible wholesale billing and charging process that can support different reporting and settlement models. The timing of these processes depends on the applicable agreement and process, and may be daily, monthly, quarterly, annually, or otherwise agreed.
Consider a scenario where a roaming subscriber makes a purchase from an online merchant while traveling abroad.
- The merchant's fraud detection system calls the Device Roaming Status API to determine whether the subscriber's device is roaming. The API returns the roaming status with available country information.
- The fraud detection system uses this information together with other signals to assess the risk of the transaction.
- Meanwhile, the subscriber's network usage continues to be processed by the operator's network and charging systems.
- For wholesale purposes, the applicable roaming settlement process exchanges the required usage or billing information using TAP or BCE according to the bilateral agreement and settlement model in use.
- The roaming partners validate, reconcile and settle the resulting wholesale charges according to the applicable process.
The fraud detection system used the Network API to obtain network context for an application-level decision. The operators used TAP or BCE for the wholesale charging and settlement process. The two domains therefore operate independently while supporting different aspects of the same roaming ecosystem.
Network API Requests in Roaming
Current State as of October 2026
TAP, RAP and BCE: TAP remains an established mechanism for wholesale roaming usage and settlement, while BCE provides an optional, more flexible settlement process for current and future roaming requirements. The two approaches can coexist during the migration and according to the capabilities and agreements of the roaming partners. GSMA continues to maintain the TAP 3.12 specifications, with TD.57 V37.0 and TD.58 V3.0 published in September 2026. GSMA also continues to maintain the BCE report and process specifications.
Network APIs: GSMA Open Gateway continues to expand its operator and ecosystem coverage. In 2026, GSMA reported more than 300 mobile networks representing more than 80% of global mobile connections participating in the initiative, with the channel and technology partner ecosystem continuing to grow.
The Device Roaming Status API is part of the current Open Gateway API portfolio. Its standardized definition supports synchronous retrieval of roaming status and, when the device is roaming, visited country information. The response can also include lastStatusTime to indicate when the reported status was last updated. CAMARA also defines a subscription API for receiving notifications when a device's roaming status changes.
Summary and What's Next
Network APIs and TAP/BCE address different responsibilities in the roaming ecosystem. TAP, RAP and BCE support wholesale usage exchange, billing, charging, reconciliation and settlement between roaming partners. Network APIs, such as the Device Roaming Status API, expose selected network capabilities and network state to applications for use cases such as fraud detection, risk assessment and contextual services.
The important architectural point is that these domains can coexist. A roaming subscriber's network usage can continue through the operator's normal charging and wholesale settlement processes while an application independently uses a Network API to obtain relevant network information. The API interaction does not replace or alter the underlying TAP/BCE settlement process.
My book provides a dedicated chapter on Roaming.
Get your copy on Amazon →Glossary
RAP: Returned Account Procedure - GSMA standard for returning rejected TAP records (TD.32)
BCE: Billing and Charging Evolution - GSMA's flexible wholesale billing, charging and settlement process for roaming and inter-operator services
TAP0: A BCE-related mechanism using simplified TAP 3.12-based records to support exchange and migration scenarios
GSMA: GSM Association - Industry body that develops standards, guidelines and frameworks for the mobile communications industry
CAMARA: Linux Foundation open-source project that develops standardized Network APIs for operator network capabilities
Open Gateway: GSMA initiative providing a standardized framework for exposing operator network capabilities through APIs
API: Application Programming Interface
IoT: Internet of Things
5G SA: 5G Standalone
NB-IoT: Narrowband Internet of Things
LTE-M: LTE for Machine-Type Communications
NTN: Non-Terrestrial Network
MNO: Mobile Network Operator
IMSI: International Mobile Subscriber Identity - Identifier associated with a mobile subscription
IOT: Inter-Operator Tariff - Wholesale rate agreed between roaming operators for applicable roaming usage
CDR: Call Detail Record - Structured usage record generated by a network or service platform for charging, billing, mediation or related processing
NAI: Network Access Identifier - An identifier used to identify a network access identity in applicable network and API contexts
MCC: Mobile Country Code - Code identifying the country or geographic area associated with a mobile network
lastStatusTime: Timestamp indicating when the reported device roaming status was last updated
Please use the CONTACT Form to reach out for training needs, consulting assignments, or other requirements.
You can also connect with me via LinkedIn.


Post a Comment