GSMA

Official Document BA.40 – Roaming Guide

Roaming Guide
Version 8.0
3 January 2024

Security Classification: Confidential

Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is subject to
copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be
disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without
the prior written approval of the Association.

Copyright Notice
Copyright © 2024 GSM Association

Disclaimer
The GSMA makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and
hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained
in this document may be subject to change without prior notice.

Compliance Notice
The information contain herein is in full compliance with the GSMA Antitrust Compliance Policy.

This Permanent Reference Document has been developed and is maintained by GSMA in accordance with the provisions set out in GSMA AA.34
- Policy and Procedures for Official Documents.

V8.0 Page 1 of 37
GSMA
Official Document BA.40 – Roaming Guide

Table of Contents
1 Introduction
1.1 Overview
1.2 Scope
1.3 Definitions and Abbreviations
1.4 References
2 Roaming and Interworking
2.1 What is Roaming?
2.2 What is Interworking?
3 Strategy for Roaming
3.1 The Roaming Functions in a typical MNO
3.1.1 Roaming Commercial Team, Carrier Services, Roaming Operations
3.1.2 IREG (Network) Testing
3.1.3 Finance
3.1.4 Fraud
3.1.5 Roaming Customer Care
3.2 Choosing Roaming Partners
3.2.1 Creating the Roll Out Plan
3.2.2 Receiving Invitations
3.3 Types of Roaming Solutions
3.3.1 Standard Bi-Lateral Roaming
3.3.2 Multi- IMSI Solutions
3.3.3 Roaming Hubbing
3.3.4 Network Extensions (NE/ International NE)
3.3.5 Non-Terrestrial Roaming
3.3.6 Machine to Machine (M2M) or Mobile Internet of Things (MIoT)
3.4 Services
3.4.1 Basic Agreements Voice & SMS
3.4.2 SMS and MMS Interworking
3.4.3 GPRS, EDGE, 3G PS data
3.4.4 CAMEL
3.4.5 Long Term Evolution (LTE)
3.4.6 5G Roaming

V8.0 Page 2 of 37
GSMA
Official Document BA.40 – Roaming Guide
4 Setting up for delivering Roaming
4.1 Billing Configuration
4.1.1 Transferred Account Procedure (TAP)
4.1.2 Returned Account Procedure (RAP)
4.1.3 Billing and Charging Evolution (BCE)
4.1.4 Data Clearing
4.1.5 BCE Agent
4.1.6 Invoicing and Financial Settlement
4.2 International Signalling
4.2.1 SCCP
4.2.2 IPX/GRX
4.3 Roaming Commercials
4.3.1 IOT Negotiations
4.3.2 Roaming Regulations
4.4 Steering of Roaming (SoR)
4.5 Fraud
4.6 Near Real Time Roaming Data Exchange (NRTRDE)
5 Delivering Roaming
5.1 Roaming Agreements
5.1.1 Confidentiality and Anti-Trust
5.1.2 MNO to MNO Agreements
5.1.3 Hubbing Agreements
5.1.4 RAEX IOT and RAEX Op Data
5.2 RAEX IR.21
5.3 SIM Exchange
5.3.1 Supply and Co-ordination
5.3.2 Auditing
5.3.3 Monitoring usage of test SIM Cards
5.4 Network (IREG) Testing
5.5 Billing (TADIG) Testing
5.5.1 TAP Testing Toolkit (TTT)
5.5.2 TAP Testing Completion Certificate (TCC)
5.6 Launching Agreements
5.6.1 Commercial Launch Letters

V8.0 Page 3 of 37
GSMA
Official Document BA.40 – Roaming Guide
5.7 Network Closure
5.8 Invoicing and Settlement
5.9 Disputes
5.10 Quality of Service
6 GSM Association
6.1 Working Groups
6.2 Member Gateway
6.2.1 Finding and Downloading Documents
6.2.2 Searching for GSMA Members
6.2.3 Roaming Gateway
6.2.4 Roaming Tab
Annex A Simple Process Flow
A.1 Negotiation
A.2 Test Preparation
A.3 Network (IREG) Testing
A.4 Billing (TADIG) Testing
A.5 Launch
A.6 On-going
Annex B Document Management
B.1 Document History
B.2 Other Information

V8.0 Page 4 of 37
GSMA
Official Document BA.40 – Roaming Guide

1 Introduction

1.1 Overview
The Roaming Handbook is intended to be an introduction and central entry point to
Roaming processes and where to find more detailed rules and procedures.

This handbook enables Roaming individuals to become familiarized quickly, minimizing the
background research needed to get started.

1.2 Scope
The scope of the Roaming Handbook is to introduce the reader to Roaming as defined in the
Permanent Reference Documents (PRDs) of the GSMA. It can be used as a starting point
from which the users can explore these PRDs.

Note: This handbook provides additional help and explanations, but does not replace the
GSMA PRDs.

1.3 Definitions and Abbreviations

All Terms & Abbreviations used in this PRD are defined in WA.03 Definitions and
Abbreviations.

1.4 References
Ref Doc Number Title
[1] AA.12 International Roaming Agreement
[2] AA.13 International Roaming Agreement – Common Annexes
AA.19 Addendum to the International GSM Roaming Agreement SMS
[3]
Interworking Agreement
[4] AA.34 Policy and Procedures for Official Documents
[5] AA.35 Procedures for Industry Specifications
AA.40 Addendum to the International Roaming Agreement Multimedia
[6]
Messaging Service Interworking Agreement
[7] AA.69 Template Agreement for Interworking
[8] AA.70 Agreement for International MMS Interworking Services
[9] AA.71 Agreement for International SMS Hubbing Services
[10] AA.73 Roaming Hubbing Client to Provider Agreement
[11] AA.74 Roaming Hub-to-Hub Agreement
[12] AA.102 Operator to Operator IOT Discount Addendum to AA.12 [1]
[13] AA.103 Group to Group IOT Framework Agreement
[14] AD.08 Working Group Operating Procedures
[15] BA.08 Timescales for Data Transfer
[16] BA.12 Transfer Account Procedure and Billing Information
[17] BA.13 Returned Account Procedure

V8.0 Page 5 of 37
GSMA
Official Document BA.40 – Roaming Guide

Ref Doc Number Title

[18] BA.19 RAEX Op Data Business Requirements
[19] BA.20 Fraud Prevention Procedures
[20] BA.21 Network Extension Principles
[21] BA.23 Outbound Roaming Solutions Handbook
[22] BA.27 Charging Principles
BA.29 RAEX IOT Business Requirements and IOT Rules and
[23]
Procedures
[24] BA.30 Steering of Roaming
[25] BA.35 Financial Clearing Agent Migration
[26] BA.36 Invoices – Creation and Content
[27] BA.37 Financial Clearing and Settlement Handbook
[28] BA.38 Payment Notification Report Requirements
[29] BA.46 Non-Terrestrial Roaming Principles
[30] BA.48 M2M Roaming Principles
[31] BA.50 Technology Neutral Agreements Handbook
[32] BA.51 Roaming Service Level Agreement Guidelines
[33] BA.60 Roaming Hubbing Handbook
[34] BA.62 Roaming Hubbing Business Requirements Commercial Model
[35] BA.64 SMS Interworking
[36] BA.65 LTE, VoLTE and 5G NSA Roaming Implementation Handbook
FF.18 NRTRDE (Near Real Time Roaming Data Exchange) Business
[37]
Requirements
[38] FF.19 NRTRDE Commercial Implementation Handbook
[39] FF.21 Fraud Manual
IR.21 GSMA Association Roaming Database, Structure and Updating
[40]
Procedures
IR.24 End-to-End Functional Capability Specification for Inter-PLMN
[41]
Roaming (Stage 4 Testing)
[42] IR.25 VoLTE Roaming Testing
IR.26 End-to-End Functional Capability Specification for Inter-PLMN
[43] Roaming (Stage 4 Testing). Addendum for Phase 2
Supplementary Services and Operator Determined Barring

[44] IR.27 Functional Capability Test Specification for Inter-PLMN Roaming

(Stage 4 Testing). Phase 1 Data Services, Fax Services
IR.31 End-to-End Functional Capability Specification for Associate-
[45]
PLMN SMS-Roaming
IR.32 End-to-End Functional Capability Specification for Inter-PLMN
[46]
CAMEL-Roaming (CAMEL Phase 1, Phase 2 and Phase 3)
[47] IR.33 GPRS Roaming Guidelines
IR.35 End – to – End Functional Capability Test Specification for Inter-
[48]
PLMN GPRS Roaming

V8.0 Page 6 of 37
GSMA
Official Document BA.40 – Roaming Guide

Ref Doc Number Title

[49] IR.38 LTE and EPC Roaming Testing
[50] IR.50 2G 2.5G 3G Roaming
[51] IR.53 MMS Inter-working Tests
[52] IR.59 Description of Anti-Steering of Roaming mechanisms
[53] IR.60 Prepaid Service Roaming Test
[54] IR.65 IMS Roaming and Interworking Guidelines
[55] IR.73 Steering of Roaming Implementation Guidelines
IR.85 Roaming Hubbing Provider Data, Structure and Updating
[56]
Procedures
[57] IR.88 EPC Roaming Guidelines
[58] IR.89 Guide to Identifying Anti-Steering of Roaming
[59] SG.07 Potential Misuse and a Threat Analysis of the GSM System
[60] SG.16 GPRS Security Guide for Users
[61] TD.13 TADIG Code Naming Conventions
[62] TD.28 File Transfer Methods
[63] TD.32 RAP Format Specification
[64] TD.35 NRTRDE Format Specification
[65] TD.36 Data Clearing Procedures
[66] TD.41 Testing the Transferred Account Procedures (TAP)
[67] TD.43 TAP Test Cases (TTC) for GSM Phase 1 Services
[68] TD.47 TAP Test Cases (TTC) for GPRS Services
[69] TD.50 TAP Test Cases (TTC) for VoLTE Roaming Testing
[70] TD.51 TAP Test Cases (TTC) for LTE and EPC Roaming Testing
[71] TD.53 Financial Outstanding Issues Report (FOIR)
[72] TD.54 NRTRDE Agent Migration Process
[73] TD.55 Data Clearing House Migration Process
[74] TD.56 Inter-NRDRTE Agent Operational Procedures
[75] TD.57 TAP3 Format Specification
[76] TD.95 PNR Format Specification
[77] TD.201 Common Billing and Charging Processes
[78] TD.202 Billing and Charging Evolution Reports
[79] TD.204 Reject Dispute Reporting
[80] TD.205 BCE Sample Files
[81] TD.206 Detail Data Records
[82] TD.207 Billing and Charging Evolution (BCE) Testing
[83] TS.25 Network Codes and Names (has replaced SE.13 [6970])
[84] WA.01 Best Practises for Roaming Technology Life
[85] WA.05 Technology Handbook

V8.0 Page 7 of 37
GSMA
Official Document BA.40 – Roaming Guide

Ref Doc Number Title

[86] WA.50 5G Agreement Template
[87] WA.51 5G SA Implementation Guidelines
[88] WA.200 BCE Tariff Management Agreement Template
[89] WA.201 Future Billing and Settlement Requirements

2 Roaming and Interworking

2.1 What is Roaming?
(International) Roaming enables the customers of one MNO to use the network of another
MNO.

Note: The GSMA defines rules and procedures for international roaming only. National
roaming is out of scope for this PRD. MNOs however may choose to use the GSMA
international roaming rules and procedures, also for national roaming.,

In most cases Roaming involves Bi-lateral, two-way (inbound and outbound) Roaming,
however in some cases Unilateral or one way Roaming takes place either for technical or
commercial reasons.

2.2 What is Interworking?

Interworking is defined as the entirety of technical, commercial and operational means
necessary to join the Service platforms of two MNOs including all parties in the chain, in
order to enable a minimum of two end users to use a specific service offered by both MNOs
across their network boundaries.

3 Strategy for Roaming

3.1 The Roaming Functions in a typical MNO
The following functions are common within MNOs who have launched Roaming. This
handbook describes the functions and key roles only, and does not depict the departments
within the individual companies.

3.1.1 Roaming Commercial Team, Carrier Services, Roaming Operations

This function can be organised in several ways. In some companies, the functions of
Roaming and Interworking are contained in the same department, while in others Roaming
and Interworking are separate functions handled by separate departments. However, all
functions that are not strictly related to Roaming are outside the scope of this handbook.

3.1.1.1 The Roaming Manager

The Roaming Manager is normally responsible for the overall coordination between various
functions and strategy.

The Roaming Department may also have responsibility for managing outbound Roaming
which may include pricing, marketing, and promotions.

This role can also be referred to as The Wholesale Roaming Manager as the person in such
a position would be responsible for the Wholesale side of the roaming business.

V8.0 Page 8 of 37
GSMA
Official Document BA.40 – Roaming Guide
3.1.1.2 The Roaming Coordinator
Usually within the Roaming Department, there is a “Roaming Coordinator” who is in charge
of agreements.

As the Roaming Department often has to interface with every department within the
company and have overall visibility of the status of Roaming, the Roaming Coordinator is a
vital member of the Roaming Department.

3.1.1.3 The Roaming Assistant

The most common role to find in this department is the “Roaming Assistant”. This person
has most of the day-to-day contact with the Roaming Partners.

3.1.1.4 Commercial Roaming Manager

MNOs may split the Roaming function between operational Roaming and commercial
Roaming.

Typically one group will look after the implementation and ongoing management whilst the
other will focus on strategy, pricing, commercial inter-Operator activities etc. Sometimes,
both are within the same group, and they can be divided between different departments.

Currently it is easier to find a Roaming Commercial Manager who may be responsible for the
IOT (Inter Operator Tariff) alongside the Roaming (Wholesale) Manager and who deal with
IOT negotiations with preferred Roaming Partners to that MNO.

3.1.1.5 Marketing
The role of the Marketing team within Roaming is normally to design effective promotional
initiatives that create incentives that will increase the usage among the roamers, both
Inbound (visiting roamers) and Outbound (own roaming customers). They can also be
responsible for maintaining all the company updates with the latest Roaming information.

3.1.1.6 Test SIM Card Administrator

The person responsible for the test SIM (Subscriber Identity Module) cards is usually a
representative from Customer Services or the Network Department; however, it can often be
the responsibility of the Roaming Department and may sit with either the Roaming
Coordinator or Roaming Assistant.

The role requires providing all Roaming Partners with their requested amount of test SIM
cards, and upon confirmation of receipt of the test SIMs will activate them accordingly. This
can also apply to the use of eSIM, but the eSIM is not physically mailed to the partner.

These activities might also be covered by the Roaming Coordinator and/or assistant.

3.1.2 IREG (Network) Testing

This person or group performs the Roaming tests, and trouble shoots for network problems.
They will be responsible for ordering the signalling links and opening the network to testing,
and later to commercial Roaming. This function also undertakes periodical Roaming tests
and troubleshooting after the commercial Roaming is in place.

V8.0 Page 9 of 37
GSMA
Official Document BA.40 – Roaming Guide
Signalling is a prerequisite to testing, as it is the basis for the communication between the
two networks. Generally, the signalling transmission or transport part is an outsourced
service provided.

IREG testing activities can also be outsourced partially or completely to a vendor.

3.1.2.1 IREG Manager

The IREG Manager is an important part of the Roaming team and may or may not sit directly
under the management team responsible for Roaming.

3.1.2.2 IREG Tester/Assistant/Engineer

The network (IREG) Tester is the person responsible for performing the tests, contacting the
other MNO’s IREG team and coordinates and troubleshoots the tests until testing is deemed
successful. Depending on the structure of the company they may also be responsible for
inserting the other MNO’s technical details on the switch. They can also be responsible for
the signalling configuration and/or coordination with the signalling provider.

3.1.2.3 TADIG Tester/Assistant/Analyst

The billing (TADIG) Tester is an important link between IREG and the launch of the Roaming
Agreement. This person will validate the IREG tests against the billing records, issue and
sign the Tap Completion Certificate (TCC) and give the final approval for the Roaming
Coordinator to schedule the launch date with the partner.

This function will (on the basis of the data produced when performing the technical Roaming
testing) perform billing tests. They will be responsible for Transferred Account Procedure
(TAP) and Billing and Charging Evolution (BCE) formats, liaison with Data Clearing House
(DCH) and BCE Agents (if used) and managing the TAP and BCE file flows between
networks on a daily basis. Please note that BCE file transfers might be done on a monthly
basis or a longer basis based on the agreement.

TADIG testing activities can also be outsourced partially or completely to a vendor.

3.1.3 Finance
The functions of the Finance department can be divided into two areas regarding Roaming.

One area is to produce invoices (based on TAP or BCE file data) for the inbound traffic
generated in the network by the customer of a Roaming Partner.

The other requirement is to ensure that the invoices are received from the Roaming Partners
for any outbound traffic that customers have generated in their network.

The final responsibility will be to ensure payment and collection for all the invoices. Many
MNOs use the services of a Financial Clearing Agent (FCA) for parts or all of this process.

3.1.4 Fraud
This function assumes responsibility for the creation of Near Real Time Roaming Data
Exchange (NRTRDE) records and the analysis of potential Fraud cases that may arise from
NRTRDE records received. They are responsible for supplying data in the event of an

V8.0 Page 10 of 37
GSMA
Official Document BA.40 – Roaming Guide
actual fraud case. Many Operators contract a NRTRDE Agent or buy a system that manages
parts, or all of this process.

3.1.5 Roaming Customer Care

Customer care can be divided in two parts, a responsibility for assisting inter-Operator
issues and the responsibility for assisting in Roaming customer queries.

For each of these functions, it is suggested that there is one member of staff who is
designated as a contact point. This group should meet on a regular basis to ensure that all
aspects of Roaming are being addressed and updated.

3.2 Choosing Roaming Partners

3.2.1 Creating the Roll Out Plan

Within a typical Roaming Operations team, it is likely that the Roaming (Wholesale) Manager
or Roaming Coordinator will set a roll out plan for what partners they would like to introduce
over the course of a financial or calendar year.

The roll out plan may include the following information to allow for the Roaming Operations
team to understand the priority of the work within the roll out plan:

 The country, name, TADIG Code of the MNO.

 The direction of Roaming required, Inbound, Outbound or both.
 The service required.
 The speculative annual value to the Operator of bringing on this service with this
Roaming Partner.
 Any understanding of the typical timescales for delivery the Roaming Partner uses.

3.2.2 Receiving Invitations

The value of the targets on the roll out plan may have been ascertained by some research
into the background of the Roaming Partner:
 Their market share within their country
 Their market share broken down by service type
 The services they can offer, including phase of service.
 The quantity of their customers that roam
 The type of customer, post-pay, pre-pay
 The Roaming Partner’s coverage by country coverage and population, for example
75% of the country, 97% of the population.
 Potential inbound traffic to the Roaming Partner’s country.
This criteria can also be used to review invitations by Roaming Partners for Roaming
agreements. Using the above data allows the MNO to decide if there is real value in the
Roaming invitation and whether it should be incorporated into their roll out plan.

By asking the above questions, the MNO is also able to ascertain quickly how serious the
intentions are of the Roaming Partner to deliver their own roll out plan.

V8.0 Page 11 of 37
GSMA
Official Document BA.40 – Roaming Guide
3.3 Types of Roaming Solutions

3.3.1 Standard Bi-Lateral Roaming

This section defines the common bilateral relationship between two MNOs with standard
International Roaming Agreement (IRA) and testing procedures.

3.3.2 Multi- IMSI Solutions

Multi-IMSI (International Mobile Subscriber Identity) is an option/solution that allows for MNO
A to use MNO B’s IMSI range and get access to MNO B’s Roaming Partners for Outbound
coverage, however this does not affect the Inbound coverage.

The benefit of the solution is to rapidly provide global coverage to MNO A’s customers. It
demands technical implementations and investment, and is commonly offered by Roaming
vendors with different options.

More details on outbound Roaming solutions can be found within BA.23 [21].

3.3.3 Roaming Hubbing

Roaming Hubbing rules and procedures are defined within BA.62 [34] and explained in
BA.60 [33].

The concept is to have many Operators connected to a Roaming Hub (either directly or via
peering agreements between the hubs) which then handles the Roaming testing and
maintenance between the Operators.

3.3.4 Network Extensions (NE/ International NE)

There are different forms of network extensions, all of them defined and addressed within
BA.21 [20], including its impacts and requirements for implementation.

The benefit of a NE is to extend the inbound coverage of a MNO by using another MNO’s
network. MNO B will extend its inbound coverage on MNO C territory, meaning that a
customer from MNO A that has an agreement with MNO B will roam onto MNO C’s network,
even without any Agreement with MNO C.

BA.21 [20] offers additional guidance to MNOs when considering Network Extensions.

3.3.5 Non-Terrestrial Roaming

A Non-Terrestrial Operator (Aeronatical, Maritime or Satellite Network) supplies services in
International zones however may also have a license/ authorisation for which includes
national zones.

The rules for Non-Terrestrial Roaming are defined within BA.46 [29], and provides the ability
for a “normal” GSM Operator to have a Roaming Agreement with a Non-Terrestrial Operator.

3.3.6 Machine to Machine (M2M) or Mobile Internet of Things (MIoT)

Machine to Machine (M2M) or MIoT refers to a family of devices and services that use wide-
area mobile network technologies to enable communications between machine to machine
and also with individuals.

V8.0 Page 12 of 37
GSMA
Official Document BA.40 – Roaming Guide
Currently M2M services are more prominent, but not limited to, specific industries:
 Automotive / Transport
 Consumer electronics
 m-Health
 Utilities
M2M Transparency Rules for Roaming are found within BA.48 [30] and notified via AA.13 [2]
C.13 and the IR.21 [40].

3.4 Services

3.4.1 Basic Agreements Voice & SMS

As a basic principle, in order for a HPMN customer to use a service while roaming, it first
needs to be provisioned for that service in the HPMN network. Please note that many
operators are now reallocating the spectrum they are using for their circuit switched
networks in favor of the newer technology. So basic voice and SMS services may not be a
possibility to test based on the VPMNs decision for their spectrum.

Not all services provided by the HPMN to its customers will be available to them when
Roaming, but there are a number of basic services that are normally (but not always)
mandatory in order for two MNOs to launch Roaming. The basic services are the ability for a
roamer to originate and receive calls and originate and receive SMS while visiting the
VPMN. There are also a few basic GSM features (supplementary services) that the VPMN
has to prove will work while the HPMN customer is Roaming on the VPMN, for example
various types of barring and call forwarding.

The document that the MNOs exchange to validate the technical configurations on both
sides for these services and features is the testing book IR.24 [41]. More information of this
and other testing documentation is provided within section 5.4.

The calls performed during this phase will later be validated on the TADIG test for its billing
perspective, comparing the rates applied to the rates published on the VPMN IOT. More
information on TADIG testing can be found within section 5.5.

BCE testing is different than TAP testing based on the aggregated reports in BCE. TD.207
[82] is the Billing and Charging Evolution (BCE) Testing PRD. But testing needs to be done
over a certain amount of time rather than at an individual record basis.

Once IR.24 [41] testing has been successfully performed and validated by the TADIG teams,
the two MNOs will agree on a date and sign the Commercial Launch Letter (CLL) for GSM
services between them. More information on the launch procedure can be found within
section 5.6.

3.4.2 SMS and MMS Interworking

SMS/MMS Interworking means that a customer from one MNO (HPMN A) can send a
SMS/MMS to a customer that belongs to another MNO (HPMN B).

The basic requirement for SMS/MMS Interworking is a signalling connection between the
MNOs, which is what the Roaming set-up will provide.

V8.0 Page 13 of 37
GSMA
Official Document BA.40 – Roaming Guide
If the two MNOs decide to charge each other for these services, for example when the traffic
is unbalanced, they will need to have the SMS/MMS interworking relationship regulated by a
contract; either as an addendum to the existing IRA, or as a standalone contract. The
templates for the addenda can be found in AA.19 [3] for SMS and AA.40 [6] for MMS, and
the templates for the standalone contracts can be found in AA.69 [7].

Different to the Roaming settlement, the billing does not happen through TAP files, therefore
the relationship between the MNOs can be managed by a SMS/MMS Hubbing Provider that
can take a fee to provide services, including settlement and reporting for SMS/MMS
interworking relations. In this case, the agreements templates to be used are AA.70 [8] for
MMS interworking relations through a Hubbing Provider and AA.71 [9] for SMS interworking
relationships through a Hubbing Provider.

NOTE: AA.40 [6] and AA.70 [8] are no longer maintained by the GSMA as they are not
commonly used in the industry.

More details on SMS/MMS Interworking can be found within BA.64 [35], BA.50 [31], IR.31
[45] and IR.53 [51].

3.4.3 GPRS, EDGE, 3G PS data

After successfully launching Roaming of GSM services, the HPMN and VPMN can move to
test other services. The second most common service to be tested is the data service,
meaning the ability of a HPMN customer to use the VPMN data network.

GPRS is the basic solution for providing IP (Internet Protocol) communication between
mobile stations and IP networks over other external packet data networks such as the
Internet. EDGE (Enhanced Data for Global Evolution) is an enhanced version of GPRS,
therefore GPRS Roaming tests are valid for EDGE networks, as they are also valid for 3G
Packet Switched (PS) data services.

Before the testing phase, it is necessary to confirm that the International Roaming
Agreement signed between HPMN and VPMN covers data Roaming. Instructions on
technology neutral agreements can be found within BA.50 [31].

Furthermore, to enable data Roaming, both the HPMN and VPMN need to be connected to a
GPRS Roaming Exchange (GRX) or Internet Protocol Exchange (IPX) Provider that will
guarantee that their IP traffic can be exchanged.

The same process as for the basic services will apply to the launch of data services, going
through a testing document (IR.35 [48]) and further validation by the TADIG teams – please
refer to section 5.6. Once the validations are exchanged both MNOs agree on a launch date
for data services and sign a new Commercial Launch Letter.

More information on data Roaming can be found in the documents IR.33 [47], WA.05 [85],
SG.07 [59], SG.16 [60] and TD.47 [68].

3.4.4 CAMEL
Customized Application for Mobile network Enhanced Logic (CAMEL) is a network solution
which allows the functionality of Intelligent Network (IN) services for roamers. It is commonly
associated with pre-paid Roaming, as it allows real-time billing and call supervision, but it is

V8.0 Page 14 of 37
GSMA
Official Document BA.40 – Roaming Guide
not limited to pre-paid services. With the advance of its technology MNO have been using
CAMEL for post-paid and advanced services as it provides more control on the billing and
services provided to the HPMN customer while Roaming at a VPMN with a CAMEL
agreement.

There are different phases of CAMEL (1, 2 and 3 being the most common) and each phase
provides a different level of service. The CAMEL phase needs to be available on both
networks in order for both MNOs to be able to use it.

The same process for the basic services will apply to the launch of CAMEL, going through a
testing document (IR.32 [46] / IR.60 [53]) and further validation by the TADIG teams –
please refer to section 5.6. Once the validations are exchanged both MNOs agree on a
launch date for CAMEL and sign a new Commercial Launch Letter. The HPMN controls the
CAMEL subscriber and the VPMN needs to allow CAMEL triggers to allow CAMEL roaming
therefore it is possible for CAMEL subscribers of the HPMN to roam on the VPMN network,
even if a CLL has not been signed. The VPMN network has the right to charge for these
services as the connection was allowed and enabled by the HPMN. (See GSMA PRD BA.27
[22]) CAMEL roaming should also include the TAP CAMEL fields, however not all parties
have updated the billing systems to include this.

More information on CAMEL Roaming can be found within WA.05 [85].

3.4.5 Long Term Evolution (LTE)

LTE bridges the different mobile telecommunication technologies worldwide into one
common high-speed all-IP broadband technology.

There is a specific handbook on LTE, VoLTE and 5G NSA, BA.65 [36] that contains much
more complete information. This section provides for a short overview.

3.4.5.1 Roaming Agreements

The standard Roaming agreement templates, AA.12 [1] and AA.13 [2], were already updated
in 2003 to be technology-neutral; hence no updates or new agreements will be required in
most cases. If there are MNOs with Roaming agreements based on templates that are not
technology-neutral, they will need to be updated to be using the latest templates.

MNOs need to exchange LTE specific Commercial Launch Letters.

3.4.5.2 RAEX IOT

RAEX IOT is used to state how the underlying bearer is charged.

The RAEX IR.21 [40] and IR.85 [56] PRDs support data over LTE including Voice over LTE
(VoLTE) and including multiple PDP contexts.

3.4.5.3 LTE on Clearing, Invoicing and Settlement

Since TAP files can be used for LTE, there is minimum impact on existing data clearing,
invoicing, financial clearing and settlement processes. Most likely the impacts is on the level
of reporting needed/offered.

The Roaming Traffic Data Report (RTDR) format supports LTE events.

V8.0 Page 15 of 37
GSMA
Official Document BA.40 – Roaming Guide
As an alternative charging approach BCE aggregated records can be used to bill for LTE
data records.

3.4.5.4 Impacts on Wholesale Charging

Full TAP support for VoLTE Roaming using local breakout is implemented in TAP3.12.

One of the possibilities with LTE is that the VPMN could use call records from the Serving
GPRS Support Node (SGSN) and Serving Gateway (SGW) for home-routed access and
additionally from the Packet Gateway (PGW) for local-breakout sessions. New recording
entity type codes for SGW and PGW, and new Cause for Termination values are available in
TAP.

Figure 1: LTE environments

3.4.5.5 Impact on Fraud-Related Issues and NRTRDE

TD.35 [64] supports LTE data Roaming. As the home network has full visibility of any
VoLTE usage, it is not a part of NRTRDE.

3.4.5.6 Testing
Data over LTE testing is defined in IR.38 [49] and TD.51 [70] and VoLTE roaming testing is
defined in IR.25 [42] and TD.50 [69].

V8.0 Page 16 of 37
GSMA
Official Document BA.40 – Roaming Guide
For more technical details on LTE and LTE Roaming, please refer to IR.88 [57] and IR.65
[54].

3.4.5.7 Value Added Services (VAS)

A significant amount of Roaming Value Added Services (VAS) are based on SS7 (Signalling
System 7) signalling procedures. With LTE, the interfaces are based on Diameter, which will
replace the SS7 signalling. Providers will need to evolve the ecosystem to accommodate
Diameter as the main source of information for VAS.

3.4.6 5G Roaming
In 5G technology, there are two types of deployment architectures:

 5G Non Stand-Alone (NSA)

 This deployment model consists of the new 5G radio (NR) deployed as a secondary
Radio Access Type (RAT), while the primary Access Type and core network (EPC) is
the 4G or LTE technology.
 5G Stand-Alone (SA)
 This deployment model consists of the 5G radio (NR) and the 5G network core
(5GC). Combined, this architecture is referred to as the 5G System or 5GS.
These two types of 5G network architectures have different roaming deployment models and
will be described separately. This PRD will focus on 5G SA roaming. Additional information
regarding 5G NSA roaming can be found in GSMA PRD BA.65[36].

There is a specific handbook for 5GSA WA.51 [87].

3.4.6.1 Roaming Agreements

For launching of 5GSA Roaming MNO’s can utilize an existing IRA and the new annexes .
An operator without an existing IRA can utilize the template agreement and annexes found
in GSMA PRD WA.50 [86].

3.4.6.2 RAEX Op Data/IOT/IR.21

The RAEX IR.21 [40] and IR.85 [56] PRDs support data over 5GNSA including Voice over
New Radio (VoNR) and including multiple PDP contexts.

For 5GSA you will need to use the new BCE Agreement Template WA.200 [88] to agree
your tariffs.

3.4.6.3 5G on Clearing, Invoicing and Settlement

Since TAP files can be used for 5GNSA, there is minimum impact on existing data clearing,
invoicing, financial clearing and settlement processes. Most likely the impacts is on the level
of reporting needed/offered.

BCE aggregated records need to be used to bill for 5GSA data records.

3.4.6.4 Impact on Fraud-Related Issues and NRTRDE

As the home network has full visibility of voice over IMS usage. NRTRDE is not needed.

V8.0 Page 17 of 37
GSMA
Official Document BA.40 – Roaming Guide
3.4.6.5 Testing
Data over 5GNSA testing is defined in IR.38 [49]. Further testing procedures are still to be
defined by NG.

3.4.6.6 Value Added Services (VAS)

Signalling for 5GSA will be based on HTTP2. HTTP2 will eventually replace diameter
signaling. Providers will need to evolve the ecosystem to accommodate HTTP2 as the main
source of information for VAS.

4 Setting up for delivering Roaming

4.1 Billing Configuration

Current billing processes available are TAP and BCE. In TAP billing you send your partner
MNO individual billing records. Those records contain enough information that could be
used by the partner MNO to bill their retail subscribers. Although they don’t need to be used
if the billing system is set up to use home records instead of TAP.

BCE on the other hand aggregates the usage and makes it impossible for the HPMN to bill
their retail subscribers from a BCE report. BCE is meant for wholesale settlement only.

4.1.1 Transferred Account Procedure (TAP)

TAP is the process of enabling serving parties to invoice their commercial partner and for
those partners to onward charge their customers in a timely manner and is usually billed in
Special Drawing Rights (SDRs). TAP provides a standardized format that allows for all call
information to be exchanged between different Operators and systems. SDR is a universally
accepted currency maintained by the International Monetary Fund (IMF) that is then
converted to the individual country’s currency.

The TAP formatting and rules are defined in TD.57 [75]. It defines the logical and physical
data that must be transferred between PMNs under TAP. It additionally contains the
maximum amount of validation rules that can be applied to a TAP file. Validation rules not
defined in TD.57 [75] can only be performed after bilateral agreement between the two
roaming partners, however such agreements are very unusual.

The transfer mechanism for TAP files is discussed in TD.28 [62].

The primary commercial requirement for TAP data to be transferred is defined in BA.12 [16].

4.1.2 Returned Account Procedure (RAP)

The RAP Rejects and Returns process formatting and rules are defined in BA.13 [17] and
TD.32 [63]. This process allows for an automated notification of fatal errors and/or missing
files, including the return of call event details containing severe errors.

The HPMN Operator will validate incoming TAP transfers and skip or ‘reject’ call event
details that do not conform to the TAP standard or to the terms of the Roaming Agreement.
The incorrect call event details will be returned to the VPMN so that they can be corrected
and resubmitted. The purpose of the rejects and returns process is to:

V8.0 Page 18 of 37
GSMA
Official Document BA.40 – Roaming Guide
 Reject invalid call event details/files so as not to impact the HPMN billing system
processing
 Allow the HPMN to bill its customers in a timely manner
 Allow the VPMN to correct and resubmit previously transmitted or rejected call event
details/files
 Assist in automated accounting in the invoicing and/or settlement process
 Minimise the need to resort to the disputes process.
Note: Whilst TD.32 [63] only specifies RAP standard usage, the process and interface is
also designed to be able to support non-standard validation checks that have been bilaterally
agreed between Roaming Partners.

4.1.3 Billing and Charging Evolution (BCE)

An alternative approach to TAP Wholesale settlement BCE is set up to charge on a bulk or
aggregated basis. This has been created to help lower the costs of TAP clearing in a MNOs
billing system. One of the examples as to why this is needed is because of the low tariffs
and low data usage are causing manual processing of settlements between operators.

The BCE reports and requirements are in the following GSMA PRDs. WA.201 [89] is the
requirements document. This document is maintained by WAS group. Any new
requirements to the BCE process or reports needs to be initiated in the WAS group. Annex
A of WA.201 [88] contains the form used to initiate a requirements discussion within WAS.
TD.201 [77] is the process flow document. It is set up to explain the procedures and flows of
the BCE reports including the high level dispute process. TD.202 [78] is the format
specification in XML. It defines the structure and the syntax for reporting wholesale records
through the BCE processes. TD.204 [79] is the Dispute process and how to initiate disputes.
As there is no longer RAP reporting in BCE this is needed in case something is not correct in
the reports. TD.205 [80] contain sample files in XML. This document is to help your
developers to create the BCE reports. TD.206 [81] contains the format specification for the
Detailed Data Records in case of a dispute or in the case where an operator may need the
detailed records from their roaming partner. BA.50 [31] has an annex for a Comercial
Launch Letter for BCE for when you are ready to go live with a roaming partner. WA.200
[88] is the BCE Tarriff Management document. It is set up so that the commercial terms can
be discussed and agreed upon and put into a form that simplifies and standardizes the setup
of the BCE tariff.

4.1.4 Data Clearing

To recover Roaming revenue, MNOs need to exchange billing information between each
other in TAP or BCE files. This needs to be carried out in accordance to timescales set out
in BA.08 [15]. It is possible to do this on a peer-to-peer basis, however most MNOs choose
to exchange TAP files via Data Clearing Houses (DCHs) and BCE Reports through the BCE
Agents. The DCH and the BCE Agent do not need to be the same entity.

4.1.4.1 Data Clearing Houses (DCH)

Data Clearing House services may be employed by a MNO to act as its agent. Data
Clearing Houses can provide a single point of contact to send and distribute files to and from
Roaming Partners. Data Clearing Houses, where employed, are (subject to the contract

V8.0 Page 19 of 37
GSMA
Official Document BA.40 – Roaming Guide
between the DCH and the MNO) responsible to their customer for the error free transfer of
TAP files between the Roaming Partners.

In addition to data clearing other services can be offered, for example:

 File validation
 File creation
 File conversion
 Fraud detection
 Tariff (IOT) check
 IOT and retail re-rating
Note: The GSMA does not define rules for agreements between MNOs and their vendors.

Mandatory rules and procedures for how a MNO changes DCH are found in TD.55 [73].

Operational procedures for interworking between DCHs are found in TD.36 [65].

4.1.5 BCE Agent

The BCE Agent may be employed by a MNO to support all functions of the BCE process.
The BCE agent does not need to be a DCH or FCA. The scope of the work of a BCE agent
depends on the need of the MNO. An agent can do everything for the MNO in regards to
BCE or can do specific functions of the BCE process based on the contract. An MNO can
use one or more BCE agents, however, there needs to be a Default agent selected for use
on the Public Interface as the MNO’s partners need to have a defined entity to exchange
their reports with over the public interface. The BCE agent may combine the functions of the
DCH and FCA entities.

Some of the services that can be offered by the BCE agent are as follows:

 Report validation
 Report creation
 Invoice creation
 Report transfer
 Reconciliation
 Charging model validation
 Dispute process handling
 DDR csv creation

4.1.6 Invoicing and Financial Settlement

In order to recover Roaming revenue MNOs need to invoice each other for the traffic used in
their respective networks. This needs to be carried out in accordance to chosen settlement
option and timescales agreed to in the Roaming agreement common annexes (AA.13 [2])
and as per the rules of BA.36 [26]. It is possible to do this on a peer-to-peer basis, however
many MNOs choose to use the services of a Financial Clearing Agent (FCA) to produce,
exchange and clear invoices.

Payments need to be accompanied by a Payment Notification Report (PNR) as per the rules
in BA.38 [28] and according to the format defined in TD.95 [76].

V8.0 Page 20 of 37
GSMA
Official Document BA.40 – Roaming Guide
4.1.6.1 Financial Clearing Agents (FCA)
Based on the billing information they receive from the MNO (Roaming Traffic Data Reports
(RTDRs) from Data Clearing Houses where employed), the Financial Clearing Agent
performs some or all of the following functions:

 Produce and distribute invoices on behalf of the MNO;

 Provide collection and payment of funds and monitor credit issues
 Reclaim Foreign VAT
 Provide bilateral or multilateral settlements

Mandatory rules and procedures for how a MNO migrates from one FCA to another are
found in BA.35 [25] including the Financial Outstanding Issues Reports. The formats for
these reports are found in TD.53 [71].

4.2 International Signalling

Signalling also known as Signalling System 7 or SS7 is a prerequisite in order to connect
two PMNs together and allow 2G and 3G Roaming.

The SS7 signalling is used between SS7 Elements grouped into a SS7 Network to allow to:

 Make a phone call (ISUP)

 Translate a number (INAP)
 Roam (MAP)
 Send a SMS (MAP)
 Maintain the SS7 Network (SNMP)
 By the exchange of Message Signal Units (MSU).
Either the IREG tester or the International Roaming Coordinator could be responsible for
ordering the SS7 international links and opening the network to testing, and later to
commercial Roaming.

This order will be based on the information of the IR.21 [40] of the other PMN.

The setup of SS7 International links is normally an outsourced service provided by one of
many third parties, more commonly named Signalling and Connection Control Part (SCCP)
provider.

4.2.1 SCCP
The SCCP is a transport layer protocol which provides extended routing, flow control,
segmentation, connection-orientation, and error correction facilities in a SS7
Telecommunications Networks.

Most MNOs use a SCCP vendor to connect to its partners. Depending on the volume and/or
price per MSU, it is possible to have two or three vendors with direct connections to the main
Roaming Partners. This could help to reduce SCCP costs and optimize SS7 routing.

4.2.2 IPX/GRX
IPX/GRX is a centralised IP routing network that provides routing, interconnecting and some
additional services of customers’ data traffic via Central Exchange Points (CEPs). The

V8.0 Page 21 of 37
GSMA
Official Document BA.40 – Roaming Guide
CEPs consist of high-capacity routers, switches and servers, including Domain Name
System (DNS) servers. Generally used for data Roaming, MMS interworking and Wi-Fi
Roaming.

IPX/GRX is a secure inter-Operator packet data network that interconnects Operators

around the world and supports global Roaming coverage.

IPX/GRX providers are essentially international data carriers offering a secure, closed,
private network.

IPX/GRX providers connect to each other via peering interfaces. These peering interfaces
may be direct connections or may pass through a common peering point. IPX/GRX
Providers should have Service Level Agreements (SLAs) with other IPX/GRX Providers.

In practice, each MNO will interconnect its data equipment to a given IPX/GRX provider.
The SGSN of the VPMNs will thus be able to communicate with the GGSN of the HPMNs.

4.3 Roaming Commercials

4.3.1 IOT Negotiations

The TAP IOT rules are defined in BA.29 [23], according to which MNOs have the freedom to
set the level of their IOT (Freedom of Tariffing) without restrictions. TAP IOT rates are
notified in RAEX IOT.

BCE IOT rules are agreed as part of WA.200 [88] and are notified using the BCE IOT tariff
template in Annex A.

In order to help operators with their discount negotiations, contract signing and settlement
procedures, a number of documents are available:

 AA.102 [12], template of an operator to operator TAP IOT discount addendum to the
AA.12 [1] for those that would like to keep the IOT discount agreement as an
Addendum to the IRA as explained above.
 AA.103 [13], template of a group to group TAP IOT framework agreement introducing
a new concept of signing an indefinite Framework Agreement and definite discount
letters. Once the discount letter expires, then one would only need to replace the
discount letter. In the case where discount periods are not consecutive, a new
discount letter would be enough on the basis of the indefinite nature of the
Framework agreement.
 BA.37 [27], provides information and examples on the relevant components of IOT
discount settlement.
 WA.200 [88] for BCE Tariff Agreement

4.3.2 Roaming Regulations

Since 2007, an increasing number of Operators and Roaming relationships are being
affected by government imposed regulation. The most publicized region affected by such
regulation is Europe. The European Commission has created rules and caps for retail and
wholesale rates that an Operator can charge its customer and its Roaming Partners.

V8.0 Page 22 of 37
GSMA
Official Document BA.40 – Roaming Guide
Regulators world-wide outside of the EU have also discussed and implemented regulation
on Roaming tariffs.

4.4 Steering of Roaming (SoR)

Steering of Roaming is the ability for a MNO to steer its Outbound Roaming traffic to a
preferred MNO(s). It is achieved through various methods but is mainly through SIM based
or signalling based solutions; or a combination of both.

It is important to note that application of Anti-Steering is strictly prohibited by the GSMA, as

defined in BA.30 [24]. BA.30 [24] also contains a reporting template to be used by a MNO to
report the identification of another MNO using Anti Steering of Roaming Mechanisms.

More details on SoR can be obtained in BA.30 [24], IR.59 [52] (Operator only), IR.73 [55]
and IR.89 [58].

4.5 Fraud
Many Operators suffer losses due to fraud from usage generated in their own network. The
home network is able to manage the problem through a combination of controls on new
subscriptions and their real time visibility of usage generated on their network. Typically
networks deploy a Fraud Management System (FMS) to detect, alert and in some cases
automatically terminate cases of fraudulent usage.

Historically fraudulent usage has been a problem associated with Roaming. This is due to a
significant time delay between usage being generated by a customer and the HPMN being
aware of such usage.

Roaming fraud prevention procedures are detailed in BA.20 [19] and FF.18 [37]. Fraud
considerations in general are discussed in FF.21 [39].

The Fraud And Security Group (FASG) manages the distribution of confidential fraud alerts
amongst its membership. All members are encouraged to submit reports which are a
valuable source of fraud intelligence. To submit an alert you should complete the fraud alert
template see GSMA PRD BA.20[19].

The FASG also manages a database of phone numbers that have featured as B-Numbers in
cases of fraud. Hot B-Numbers reported to the GSMA by Fraud and Security group
members, CFCA and TUFF (other industry fraud bodies outside of the GSMA) are published
in the database. All members are encouraged to use this database and to input any B-
Numbers they have identified from their own fraud cases.

4.6 Near Real Time Roaming Data Exchange (NRTRDE)

NRTRDE involves the transfer of individual records from the VPMN to the HPMN within 4
hours of the usage being generated. There are no thresholds to consider and the records
are not rated. The prompt receipt of detailed customer usage allows the HPMN to rapidly
detect fraud. The HPMN will be able to integrate the NRTRDE into their Fraud Management
System allowing for automated error free detection of Roaming fraud.

FF.18 [37] details the NRTRDE business requirements and FF.19 [38] is a handbook to
assist Operators implementing NRTRDE. The format specification is contained within TD.35
[64].

V8.0 Page 23 of 37
GSMA
Official Document BA.40 – Roaming Guide
The process for migrating NRTRDE providers is found in TD.54 [72]. The process on how
NRTRDE agents should inter-operate between each other is found in TD.56 [74].

5 Delivering Roaming

5.1 Roaming Agreements

This section contains a brief overview of the various roaming agreement templates that are
available. More information can be found in BA.50 [31].

5.1.1 Confidentiality and Anti-Trust

It is important to note that once a MNO becomes a GSMA member and it signs a roaming
agreement with another MNO, it becomes responsible for ensuring confidentiality and anti-
trust rules are followed.

MNOs have to be very careful when using mailing lists to reach out to multiple MNOs at the
same time. No individual MNO’s information, of any nature, should be shared with other
MNOs or third-parties without prior written consent. For more information on confidentiality
rules please refer to the signed AA.12 [1] and AA.13 [2] between the MNOs involved, and
the GSMA Anti Trust Policy available from GSMA.com.

Sharing certain information with competitors can constitute anti-competitive behaviour and
may be unlawful under applicable antitrust law. Such behaviour may arise, by way of
example only, where two or more competitors exchange or allow to exchange data which
enables them to fix prices or align pricing policies. For further information please refer to the
GSMA Anti-Trust Policy.

5.1.2 MNO to MNO Agreements

Note: BA.50 [31] contain all the information on Agreement Templates.

AA.12 [1], in conjunction with AA.13 [2] and RAEX Op Data and RAEX IOT, comprises of the
GSM Associations standard International Roaming Agreement for parties who wish to make
Unilateral/Bilateral Agreement for the establishment of international Roaming services. The
basic legal framework set out in AA.12 [1] covers areas such as scope, confidentiality
provisions, data privacy, liability, fraud prevention, duration, suspension of services and
termination.

AA.13 [2] Common Annexes contain the practical principles and procedures the parties
agree on to implement International Roaming. These annexes forms part of the basis of
day-to-day Roaming operations and procedures.

The Individual Annexes (RAEX Op Data and RAEX IOT) serves as a source of information
and guidance for both parties in a Roaming Partnershipand are distributed to Roaming
Partners via the RAEX Tool.

AA.19 [3] is the SMS Inter-working Bilateral Addendum which allows an Operator to charge
for the termination of SMS on their network.

AA.40 [6] is the Multimedia Messaging Interworking Bilateral Addendum which allows an
Operator to charge for the termination of MMS on its network.

V8.0 Page 24 of 37
GSMA
Official Document BA.40 – Roaming Guide
AA.69 [7] is the template Agreement that allows Inter-working between two Operators,
normally used where no roaming agreement is in place.

5.1.3 Hubbing Agreements

AA.73 [10] contains a template for the Roaming Hubbing Agreement between a Roaming
Hub Provider and a Client Operator.

AA.74 [11] contains a template for the agreement between Roaming Hubbing Providers.

The RAEX IOT and RAEX Op Data is used in conjunction with AA.73 [10] and AA.74 [11] to
exchange individual annex information.

5.1.4 RAEX IOT and RAEX Op Data

RAEX IOT is the process for the exchange of the IOT data, which forms part of the
applicable agreement (AA.12 [1], AA.73 [10] or AA.74 [11] as applicable). This process is
defined in BA.29 [23].

The remainder of the individual annexes of the applicable agreement (AA.12 [1]/AA.13 [2],
AA.73 [10] or AA.74 [11]), excluding the IOT, is exchanged using the RAEX Op Data
process. This process is defined in BA.19 [18].

The purpose of the RAEX IOT process is to define standardised TAP IOT data and
operational exchange process requirements which support the validation of the TAP IOT
data integrity and provide exchange integrity. This will, in turn, support accurate validation of
charges contained within TAP files which will result in fewer revenue impacting disputes and
facilitate better cash flow between contracted parties.

The purpose of the RAEX Op Data process is to allow automatic processing and extraction
of all the operational Roaming Agreement information.

The TAP IOT has been separated out from the operational information, as the rules for the
exchange of the TAP IOT are strict and well defined, whereas the rules for the exchange of
the operational information are very flexible and according to the needs of the sender.

Both RAEX TAP IOT and RAEX Op Data are bilateral and need to be exchanged separately
for each Roaming relation.

The RAEX IOT and Op Data applications provided by the GSMA supports both the creation
and distribution of RAEX IOTs and RAEX Op Data. By using distribution lists, the system
supports Operators who have the same IOT and/or Op Data for many Roaming relations.

See section 6.2.3 for how to find additional RAEX information on the GSMA Member
Gateway.

5.2 RAEX IR.21

The RAEX IR.21 Tool is used to exchange all necessary technical information between
Roaming Partners

RAEX IR.21 [40] contains all the data that needs to be defined in any network in order to set
a commercial Roaming or Interworking agreement of any kind, including all supported

V8.0 Page 25 of 37
GSMA
Official Document BA.40 – Roaming Guide
services and technologies. RAEX IR.21 [40] is exchanged whenever one MNO makes an
upgrade of any of this information. Please note that there are timelines specified and agreed
on how long it should take a MNO to implement any one of the fields once they’ve been
updated.

The contact points should be involved in the whole process that is, commercial aspects,
configuration, testing and troubleshooting. These contact points can include the name of the
person or/and department, phone and fax numbers and email address. A 24x7 number is
considered best practice.

5.3 SIM Exchange

In order to perform Bilateral Roaming tests, both Operators need to exchange test SIM
cards. The number of test SIM cards to issue should be stated in the AA.13 [2] annex C.5.1
or in a separate bilateral agreement.

5.3.1 Supply and Co-ordination

Test SIM cards need to be provided with all the basic and advanced services that the HPMN
want to offer to its customers while Roaming on the VPMN.

For security and anti-fraud purposes, it is important to ensure that the test SIM cards cannot
be used until the VPMN sends confirmation of receipt of the SIMs. Best practice is to assign
the test SIM cards to the Roaming Partner on the HPMN system as inactive until the
confirmation is received; and once received, request for SIM activation within the appropriate
department.

Another critical point on this co-ordination is to ensure that the Roaming Partner receives all
the SIM details so the configuration can be done on its network for Roaming.

It is also advisable to separate the SIM cards from their details, so that the PIN code is not
sent in the same pack as the SIM card.

Testing SIM Card supply chain and activation is one of the common bottle necks on the
Roaming process, so creating a process with the different departments involved and
documenting it internally is very important.

Sending the SIM Card through a well-known courier and constantly tracking the “package”
through the Air Waybill (AWB) is also recommended.

5.3.2 Auditing
As the number of partners increase, MNO exposure to fraud with test SIM cards increases.
It is recommended that at least once a year the MNO runs an SIM audit on all SIMs received
and sent to the partners and if it cannot be located, or confirmed with a Roaming Partner, it
should be de-activated as soon as possible to avoid fraud.

In order to be able to control and audit the usage of the test SIM cards it is imperative that
the SIM details of the SIMs received and sent are kept in good order.

V8.0 Page 26 of 37
GSMA
Official Document BA.40 – Roaming Guide
5.3.3 Monitoring usage of test SIM Cards
Because the VPMN has no visibility to usage of a lost or stolen SIM card, it is highly
recommended that all HPMNs monitor test SIMs for fraud, high usage or usage on networks
other than the VPMN’s network. One option to improve and monitor fraud or exceptional
usage of test SIM cards is to create NRTRDE files specific to test SIMs.

5.4 Network (IREG) Testing

The listing of Network Testing PRDs is as follows:

 IR.24 [41] is to test basic GSM test cases and is oriented to test all traffic cases
before opening a GSM agreement between two Roaming Partners. It is mainly used
for 2G/3G technology.
 IR.25 [42] is to test VoLTE roaming test cases.
 IR.26 [43] is to test Phase 2 Supplementary Services.
 IR.27 [44] is to test VideoCall Service and is oriented to cover every case in order to
assure a correct Service. It will be used for 3G technology only.
 The main objective of IR.32 [46] is to go through every signal operation that can occur
if a CAMEL service is used. It is not limited to prepaid only but any other service that
can be based on CAMEL.
 IR.35 [48] is to test Packet traffic and is oriented to test all traffic cases before
opening a GPRS Agreement between two Roaming Partners. It can be used for
either 2G or 3G technologies.
 IR.38 [49] is to test data roaming LTE and EPC test cases.
 IR.60 [53] is to test Prepaid Service and it is scarcely used by the Operators due to
most of them maintaining their own test documents. It is mainly used for 2G
technology.
5.5 Billing (TADIG) Testing
Billing (TADIG) Testing is performed once the relevant network (IREG) tests (for example
IR.24 [41]) have been successfully performed by the VPMN and the completed documents
issued to the HPMN. The TAP billing records are sent from the VPMN in a Test file to the
HPMN (directly or via a DCH).

It is not recommended to issue a TAP Testing Completion Certificate (TCC) directly from an
e-mailed copy of the TAP file but e-mailed copies can be used for checking whilst waiting for
the original file to be received.

Test cases for new services after commercial launch can be sent either in a live TAP file or a
Test TAP file. If the test calls are included in a live TAP file then they are chargeable up to
the amount agreed to in the AA.13 [2]. If the charge exceeds the agreed amount, the HPMN
can issue a debit note for the amount exceeding the agreed amount.

When CAMEL is used for post-paid services, there is specific information, for example the
dialled digits, CAMEL destination number and CAMEL service keys, that needs to be
provided to the customer and is important that it comes correctly populated on the TAP file.
There are Operators that cannot provide this, so it is recommended to check this point
clearly before starting the test.

V8.0 Page 27 of 37
GSMA
Official Document BA.40 – Roaming Guide
Problems identified during TADIG testing need to be reported back to the VPMN TADIG
team for investigation. This may result in re-tests which will be captured in new IREG and
TADIG test files. Minor issues can be noted in the Comments Section of the TCC if
bilaterally agreed by both parties thereby allowing the launch to progress.

BCE testing needs to be done based on the recommendations in TD.207 [82]. BCE testing
requires the submission of UDRs and based on the certain criteria and timing, you cannot
reconcile UDRs for a single day, so longer testing periods are required to get actual
validation for BCE testing.

For more detailed information of the billing (TADIG) testing process read documents TD.41
[66] and for the TAP format specification and rules, TD.57 [75].

5.5.1 TAP Testing Toolkit (TTT)

The TTT is a user-friendly interactive windows application developed and continuously
maintained by the GSMA to support the execution of the applicable TAP and RAP Testing
Procedures as defined in the relevant IDS PRDs.

The TTT is available for download from the GSMA Member Gateway Roaming Tab. It is a
tool which is utilised to read and process/validate the TAP files. The TTT contains templates
relating to basic scenarios of the IREG PRDs and the corresponding TAP records expected
from the TADIG PRDs such as TD.43 [67].

For example, if a Test GSM TAP file is loaded into the TTT, the scenarios mentioned in
TD.43 [67] can be selected as an option which can then be used to validate the IREG tests
performed. Once all test scenarios are successfully validated a TCC can be issued.

For further information about the TTT, contact directly the GSMA or visit the TTT page on
Member Gateway under the Roaming Tab.

5.5.2 TAP Testing Completion Certificate (TCC)

The TAP Testing Completion Certificate (TCC) must be exchanged to certify the successful
execution of the applicable TAP Testing Procedure.

It shall be provided by the HPMN to the VPMN after successful tests have been completed.
The recommended form is given in TD.41 [66] which illustrates the basic information
required. However, the form can be customised by adding the company logo and/or other
information.

It is recommended that the TCCs are checked by the individual issuing/signing the
Commercial Launch Letter in case caveats are required to be captured.

5.6 Launching Agreements

Following the successful completion of the relevant network (IREG) and billing (TADIG)
tests, and once Testing Completion Certificates (TCCs) has been exchanged, both parties
will need to agree a launch date and sign a Commercial Launch Letter (CLL). The CLL
should state the effective starting date for the agreement and must be signed by both
parties. The exchange of the CLL can take place electronically.

Templates to all CLLs are located within BA.50 [31] for easy reference.

V8.0 Page 28 of 37
GSMA
Official Document BA.40 – Roaming Guide
5.6.1 Commercial Launch Letters
Templates for Commercial Launch Letters (CLL) for various services can be found in BA.50
[31].

Once the CLL is agreed, notification of launch must then be sent to:

 All relevant internal departments (billing, engineering/network, finance, fraud,

marketing, etc.)
 The function within company responsible for GSMA Member Gateway updates (for
example the Membership Information Manager (MIM)).
 The Data Clearing House.
 The Financial Clearing Agent.

5.7 Network Closure

Information in relation to Network Closures and action required to be taken place by the
MNO is contained in WA.01 [84] Best Practises for Roaming Technology Life Cycle.

5.8 Invoicing and Settlement

Rules for invoicing are defined in BA.36 [26], and for payments in BA.38 [28]. Additional
help can be found in the Financial Clearing and Settlement Handbook BA.37 [27].

5.9 Disputes
Any disputes between Roaming Partners need to be handled as per the relevant agreement
and the general rules defined in GSMA PRDs.

5.10 Quality of Service

How to implement roaming quality measurements can be found in GSMA PRD. BA.51 [32]
Roaming Service Agreement Guidelines.

As the objective of the Service Level Agreement is to maintain and improve roaming quality,
MNOs should ensure that when acting as the VPMN, network conditions of service shall not
differ substantially from those provided to their own customers as stipulated in their roaming
agreements, (AA.12 [1] Section 6). For example, the VPMN, shall not impose any limitation
of offered data speeds by way of throttling roaming customers on their network compared to
what is provided to its own customers.

6 GSM Association
As explained on the GSMA public website (www.gsma.com), the GSMA represents the
interests of Mobile Operators worldwide. Spanning over 200 countries, the GSMA unites
nearly all of the world’s Mobile Operators, as well as a large number of other companies in
the broader mobile ecosystem, including for example DCHs, FCAs, handset makers,
software companies, equipment providers, Internet companies, and media and
entertainment organisations.

6.1 Working Groups

GSMA Working Groups that are involved in defining rules for international roaming include:

V8.0 Page 29 of 37
GSMA
Official Document BA.40 – Roaming Guide
 Wholesale Agreements and Solutions group (WAS)
 Networks Group (NG)
 Interoperability, Data specifications and Settlement group (IDS)
 Fraud And Security Group (FASG)
The operating procedures for the Working Groups can be found in AD.08 [14]. AA.34 [4] &
AA.35 [5] contains rules for the approval of documentation.

For more information on Working Groups and their subgroups please refer to the Groups
Directory Listing on Member Gateway
(https://membergateway.sharepoint.com/sites/wg/SitePages/Home.aspx).

6.2 Member Gateway

Members of the GSMA have exclusive access to the Member Gateway
(https://membergateway.sharepoint.com/sites/Home), which is a very useful knowledge
source on all topics related to the GSM family of wireless communications.

Through the Member Gateway the community is able to keep up-to-date on the current
GSMA topics such as Working Groups, meetings, knowledge bases, PRDs, contact details
of Roaming Partners and more.

To access Member Gateway, members must request accessvia their MIM (Member
Information Manager). Every GSMA member company has a defined MIM assigned to
them.

Below is the layout of the Member Gateway homesite:

Figure 2: Member Gateway Home Site

6.2.1 Finding and Downloading Documents

All Official Documents (Permanent Reference Documents - PRDs) edited and approved by
the GSMA are stored on the GSMA Member Gateway.

V8.0 Page 30 of 37
GSMA
Official Document BA.40 – Roaming Guide
At the top of the home page, there is a button “Official Documents” that will lead to the
following page:

Figure 3: Official Documents

Each column can be filtered to assist in finding the PRDrequired.

6.2.2 Searching for GSMA Members

From the Member Gateway Directory you can search for GSMA Members by organisation
name or individual.

V8.0 Page 31 of 37
GSMA
Official Document BA.40 – Roaming Guide
Figure 4: Member Gateway Directory

6.2.3 Roaming Gateway

Via the Member Gateway Home site you can click through to Roaming Gateway
(https://www.raextools.com/raextools/). Depending on the Roaming Gateway roles assigned
by your MIM on Roaming Gateway you can view the TS.25 [83] and TD.13[61] databases
access and manage RAEX files and manage Roaming Partner & Distribution lists.

Figure 5: Roaming Gateway

6.2.4 Roaming Tab

The roaming tab on Member Gateway (see figure below) holds the following information:

 GSER Access
 RAEX: Contains training material and documentation in relation to RAEX IOT / Op
Data and RAEX IR.21 [40].
 BID Database
 IDS Release Pages: Contains overviews of products managed by IDS (TADIG) and
related documentation. This can be used to see for example what version of TD.57
[75] is applicable to a given TAP version.
 Tap Testing Toolkit (TTT)
 Information on BCE (Billing & Charging Evolution
 Escalation Contacts: Contains DCH, FCA and NRTRDE Agent contact listings.

V8.0 Page 32 of 37
GSMA
Official Document BA.40 – Roaming Guide

Figure 6: Member Gateway Roaming Tab

V8.0 Page 33 of 37
GSMA
Official Document BA.40 – Roaming Guide

Annex A Simple Process Flow

Network Billing
Test
Negotiation (IREG) (TADIG) Launch On-going
Preparation
Testing Testing

Figure 7: Simple Process Diagram

A.1 Negotiation
 Roaming Department
o Negotiate deviations and conditions of the agreement
o Exchange individual documents

A.2 Test Preparation

 Roaming Department
o Exchange SIM cards
o Distribute documents internally (RAEX IR.21 [40], IR.24 [41], IR.25[42], IR.35
[48], IR.38[49], IR.50[50], RAEX Op Data, RAEX IOT, etc.)
 IREG Team
o Load IR.21 [40]
o Schedule tests with other IREG team
o Request SS7 and GRX/IPX connection where applicable

A.3 Network (IREG) Testing

 IREG Team
o Complete IR.21 [40], IR.24 [41], IR.25 [42], IR.35 [48], IR.38 [49], IR.50 [50],etc.
and pass it to TADIG Team
o Support the other operator on completing own IR.21 [40], IR.24 [41], IR.25[42],
IR.35 [48], IR.38 [49], IR.50 [50],
o Support TADIG Team with re-tests
o Receive own IR.21 [40], IR.24 [41], IR.25 [42], IR.35 [48], IR.38 [49], IR.50 [50]

V8.0 Page 34 of 37
GSMA
Official Document BA.40 – Roaming Guide
 Roaming Department
o Escalate test problems with other operator

A.4 Billing (TADIG) Testing

 TADIG Team
o Find IR.21 [40], IR.24 [41], IR.25 [42], IR.35 [48], IR.38 [49], IR.50 [50],calls on its
own TAP files
o Validate own TAP before sending to the other operator
o Validate TAP file received and issue TCC
o Support the other operator on issuing TCC
o Receive TCC
 Roaming Department
o Escalate test problems with other operator

A.5 Launch
 Roaming Department
o Agree on best launch date
o Inform internal areas, DCH and FCH of the agreed launch date
o Prepare and sign CLL

A.6 On-going
 Roaming Department
 IREG Team
 TADIG Team
 Marketing
 Fraud / Business Risk
 Finance
 Carrier Services

V8.0 Page 35 of 37
GSMA
Official Document BA.40 – Roaming Guide

Annex B Document Management

B.1 Document History

Version Date Brief Description of Change Approval Editor / Company
Authority
Sibel Gazozcu /
3.0.0 Dec 2003 New Non-Binding PRD Avea Iletisim
Hizmetleri A.S.
Updated with information on Sibel Gazozcu /
3.1.0 Nov 2004 Packet Roaming (CR 001 to BARG #64 Avea Iletisim
BA.40BARG 64_068Rev1) Hizmetleri A.S.
Sibel Gazozcu /
Updated with information on
Omani Qatari
3.2 Oct 2005 CAMEL Section (CR 002 to BA.40 BARG #66
Telecommunications
BARG 66_33)
SAOC
Sibel Gazozcu /
Updated with information on Fraud
Omani Qatari
3.3 Feb 2006 section (CR 003 to BA.40 BARG BARG #67
Telecommunications
67_046)
SAOC
Procedure for introducing Sibel Gazozcu /
SMS/MMS Interworking prior to Omani Qatari
4.0 Aug 2006 AGREE #31
Roaming (CR 003 to BA.40 Telecommunications
AGREE 31_003) SAOC
Deletion of the Services
Alexandre Pereira /
4.1 Sep 2006 Description and moved to the
Digicel Group
Roaming Handbook
Complete re-draft of the document Alexandre Pereira /
5.0 Mar 2008
with updated information Digicel Group
CR 007 (BARG Doc 72_029)
Change ‘Subscriber’ to ‘Customer’
CR 008 (BARG Doc 72_092) Alexandre Pereira /
5.1 Aug 2008 BARG #72
Quality Review References to Digicel Group
BA.60 and post-paid CAMEL
testing included
CR 009 (BARG Doc 74_030)
Update including paragraph about Alexandre Pereira /
5.2 Oct 2009 BARG #74
updating information duplicated in Digicel Group
different documents.
CR 010 (BARG Doc 76_034)
20 Oct Update including paragraph about Alexandre Pereira /
5.3 BARG #76
2010 AA.60 and minor lay-out fixes on Syniverse
the PRD table
10 May CR 011 (BARG Doc 79_033) BARG #79 & Alexandre Pereira /
6.0
2012 General Update EMC #102 Syniverse
31 May Editorial update to correct LTE Alexandre Pereira /
6.1 N/A
2012 diagram Syniverse

V8.0 Page 36 of 37
GSMA
Official Document BA.40 – Roaming Guide
Converted to .docx, Infocentre
section, updated with new Alexandre Pereira /
N/A Apr 2013 N/A
screenshots and other Editorial Syniverse
corrections
Added section 5.2.8 on
Alexandre Pereira /
6.2 Feb 2014 Confidentiality and Anti-Trust RING eVote
Syniverse
Rules
Transfer of PRD from BARG to
6 Jan WAS (same as v6.2) David Chong /
6.3 N/A
2015 CR 1002 had to be deleted and GSMA
recreated as CR 1003
4 Feb CR 1003 Rewrite to bring up to Christer Gullstrand /
7.0 WAS eVote
2015 date Syniverse
Editorial update to remove
17 June
7.0 reference to BA.01 and change N/A Sunil Joshi / EE
2016
AA.60 to AA.69
15 Aug Editorial updates by editor and
7.1 reference to WA.03 for definitions WAGREE Sunil Joshi / EE
2016
and abbreviations
14 March Addition of CR 1005 Network Randy Peterson
7.2 WAGREE
2017 Closures (Union)
23 March CR 1006 Addition of Quality Randy Peterson
7.3 WAS eVote
2018 section (Union)
12 July CR 1007 Updating document to Randy Peterson
7.4 WAS eVote
2019 include BCE (Union)
22 March Editorial update - IR.88 change of Randy Peterson
7.4 N/A
2021 name (Union)
27
CR1009 Editor Annual Review and Randy Peterson
8.0 September WAS eVote
Update (Comfone)
2022
3 January Move to new GSMA Template and Randy Peterson
8.0 change from Infocentre to Member N/A
2024 (Comfone)
Gateway & Roaming Gateway

B.2 Other Information

Type Description
Document Owner WAS
Editor / Company Randy Peterson (Comfone)

It is our intention to provide a quality product for your use. If you find any errors or omissions,
please contact us with your comments. You may notify us at [email protected]

Your comments or suggestions & questions are always welcome.

V8.0 Page 37 of 37