In the first of our three-part series on automating the complex task of IR.21 and IR.85 validation and implementation we consider the importance and imperative of automating this vital but resource-heavy and error-prone task.
Every month, you likely receive updates to your IR.21 and IR.85 documents from your roaming partners. You review the changes and implement them. So why do we need to automate this process? Because there are new opportunities emerging and you need to use your resources to target these. Read on for more.
The complexity implementing IR.21 and IR.85 changes
IR.21 is a document designed to contain and share data between operators, MNOs, and other network providers that’s required for roaming and internetworking services. These documents are key to your roaming partnerships, as they set out the conditions expected on different networks – and the experiences delivered.
It was introduced in 1991 and is one of the most activate documents in the GSMA-Networks Group. Release 18.0 was published in December 2025. Similarly, IR.85 is a modified version of IR.21 specifically relating to the efficient operation of roaming hubs to enable connectivity through other hub participants, such as national and international MNOs.
Both IR.21 and IR.85 cover technical data such as MCC/MNC codes, network capabilities and configurations, SMS/data routing, and service statuses for VoLTE, M2M, and 5G/LTE roaming. These changes are instructions from your partners, telling you how to reconfigure your network to support their customers when roaming.
Spreading this information can be done unilaterally – but the GSMA came up with a better way. That’s because the changes made by one MNO may need to be implemented by hundreds of others – all of the roaming partners that have a direct (IR.21) or indirect (IR.85) relationship with them.
The Roaming Agreement Exchange is a hub to which any subscribing MNO can post their updated agreements. As a result, it supports the global sharing of data if one party introduces a new version of its IR.21 specification and makes it automatically available to other partners in the hub. It facilitates information discovery and availability, but it does not implement the requisite changes in the networks, leaving a gap.
As you will likely already know, technical data can change hundreds of times each week, with every update requiring (potential) translation into a single format, parsing, validation, and comparison with previous partner data before being logged and distributed to internal teams.
The IR.21 and IR.85 problems
This process is slow and a significant drain on resources. When performed manually, it’s also prone to human error, which can have a significant impact on roaming functionality and operation, while degrading partner trust and leading to lost wholesale revenue.
Any changes can introduce significant complexity and demand heavy resources, as operators may have hundreds of such agreements in place. At We Are CORTEX, we call this the “IR problem”.
Each document consists of hundreds of pages, with every page containing multiple tables, which each outline the specific and unique parameters that roaming partners need to uphold.
The document specifies not just individual settings for network infrastructure, but also the different interfaces that must be supported in the appropriate domain and signalling entities. Issuing parties must also document and catalogue changes, so that receiving peers can manage their own governance procedures.
In addition, the landscape is changing. It’s not just classical inter-MNO agreements for 4G or 3G data, messaging and voice. Today, the introduction of the 5G service-based architecture (SBA), network slicing, URLLC (Ultra Reliable Low Latency Communication), millions of additional IoT devices, the proliferation of Non-Public Networks (NPNs), and Non-Public Networks (NPNs), among others, further adds to an already complex mix.
For example, Juniper Research[1] notes that IoT service revenue will also enjoy strong growth, reaching an estimated figure of $2 billion globally by 2028, equivalent to 10% of the global wholesale roaming market. That’s pretty exciting and shows how roaming is set to jump – surely it’s time to address legacy methodologies and take action?
Juniper also estimates that wholesale roaming revenue is, according to Juniper Research, set to double by 2029[2], driven by more complex services associated with 5G which will attract a premium over and above standard charges for consumer roaming access. So, it’s an issue that must be addressed – otherwise, you won’t be able to cope with new levels of change complexity.
Automation of IR.21 and IR.85 is the only viable option
Put simply, manual implementation of meeting IR.21 and IR.85 standards is untenable. In a rapidly evolving and complex network environment automation of the process is the only option to avoid reputational damage and compliance failures, and of course loss of customer QoS and QoE.
The We Are CORTEX Evolved Roaming Solution is a complete end-to-end automation and orchestration framework for implementing changes to IR.21 and IR.85 documents.
It condenses a process that previously would have taken weeks into just a few minutes, allowing engineers and operators to focus on alternative revenue-building and strategic tasks. It provides all the appropriate fail safes and safeguards.
Some of the benefits of CORTEX Roaming include:
- Protection of margins and increased profits
- Improved service reliability
- Reduced time to support partner configuration and hub changes
- Support for more partners and roaming services
- Eliminate human error
- Ensure compliance and transparency with an end-to-end audit trail
- Rapid iteration of process automation
- Less time focused on repetitive tasks
- More focus on service innovation and monetisation
The CORTEX Evolved Roaming solution can transform your roaming and wholesale business, by automating the entire process, which liberates teams to focus on new revenue streams and opportunities.
Find out why we need to address this challenge in our latest paper – “Automating IR.21 and IR.85 change implementation in your operations”.
[1] https://www.juniperresearch.com/press/operator-iot-roaming-revenue-to-break-2-billion-by-2029/
[2] https://www.juniperresearch.com/press/pressreleasesglobal-wholesale-roaming-revenue-to-double/
