Automating IR.21 and IR.85 and RAEX validation and implementation with CORTEX

The GSMA is actively pushing for MNOs to adopt RAEX for exchanging IR.21 and IR.85 documents.

The move is expected to help operators with the complexity of implementing roaming for 5G SA services. All of which may help operators – but it doesn’t help them to implement the required changes. Find out how CORTEX can automate the entire process – including implementation, so you can accelerate deployment of IR.21 and IR.85 changes – so you can focus on more strategic tasks. In this final blog in our three-part series on using automation to validate and implement constant and complex changes to IR.21 and IR.85, we will focus on the important process of RAEX (Roaming Agreement Exchange).

RAEX automates distribution of changes to IR.21 and IR.85 documents – but not to the network

Updates to these key documents can be frequent and may apply to hundreds of roaming partners, so it’s a resource-heavy, time-consuming task that, when delivered manually is prone to human error.

The documents share technical data such as MCC/MNC codes, network capabilities and configurations, SMS/data routing, and service statuses for VoLTE, M2M, and 5G/LTE roaming. They also impact SIM provisioning and billing, so have far-reaching consequences.

RAEX supports the sharing of changes to IR.21 and IR.85 between national and international roaming partners allowing them to update their own documents according to the changes made by one partner. IR.85 also identifies further data needed to enable roaming hubs to function smoothly.

In Q1, 2023, GSMA made it mandatory for MNOs to use RAEX, with most already publishing their IR.21 and IR.85 interconnection data sets through it. Operators capture the necessary data in a Word or Excel file, then the RAEX automatically converts the information into a standardised file format based, so it can be distributed securely and efficiently.

Changes to IR.21 and IR.85 impact the entire organisation and network

When changes are made to IR documents, it will likely lead to multiple changes that must be implemented across the entire organisation and network. The documents describe not only the performance requirements of roaming services, but also the parameters associated with each.

The GSMA now publishes RAEX data via APIs, that allows MNOs to both publish amendments to their own data directly and streamline the process of receiving updates from every other operator. Prior to these changes introduced by the GSMA, operators manually updated their systems with IR.21 and IR.85 data from PDFs, which could lead to keying errors.

Any errors — of this nature or otherwise — could mean that roaming customers cannot, for example, reach the number they require – in the case of emergency calls this could be catastrophic. In the case of failure to access data services, frustration and complaints from unhappy holidaymakers – or, worse, valuable business customers.

They can also lead to loss of service, lost revenue, reputational damage, and unnecessary rework for both the home network and the visited network of roaming partners.

Of course, RAEX offers multiple benefits:

• Electronic exchange of operational roaming data, from a central platform
• Standardised XML format to facilitate data import into other systems
• Consistent formats mean that operators can more easily interpret and parse the required changes, noting the differences with the current configurations
• Delivers a consistent audit trail to track changes and revisions to the network, aligned with other operational reporting goals

However, errors and omissions can creep in, through misreading or misunderstanding the presented data, or mis-keying the correct information during data entry. They can cause delays, or total loss, in issuing interconnection billing.

Automating IR.21 (and RAEX) and IR.85 workflows

That’s why many operators and MNOs want to go further and automate the entire IR.85 (and IR.21) implementation workflow. Manual validation and implementation of changes is simply not a viable option, as the complexity of changes and networks accelerates – and, with 5G SA roaming on the horizon, a new level of complexity will be reached.

In this context, automating the required changes is now imperative – not just to keep pace, but also to secure financial gains – from both reduced costs and better revenue management – as well as stronger security and improved customer satisfaction.

According to Analysys Mason, errors in IR.85 and IR.21 implementation can cost operators up to $5 million in annual revenue leakage from service errors and delays. At the same time, failure to maintain standards can lead to higher cyber risks from fragmented, inconsistent configurations, and service quality issues and disappointing customer experiences.

CORTEX intelligent automation platform enables the ingestion of IR.85 and IR.21 data in real time

The We Are CORTEX Evolved Roaming solution has been built specifically to enable service providers to implement changes to IR.21 and IR.85 documents quickly, efficiently, and with little risk.

It ensures that data is always accurately updated across all systems, with built-in compliance controls. As a result, it allows operators to maximise roaming revenues. It complements your existing RAEX ingestion processes and extends workflows to enable the efficient implementation of changes in your network and systems.

We Are CORTEX Evolved Roaming is a complete end-to-end automation and orchestration framework for automating changes to IR.21 and IR.85 documents. It condenses a process that previously would have taken weeks into just a few minutes

Find out more about how easy it is to move to fully automated RAEX change implementation with CORTEX and transform your roaming and wholesale business by getting in touch to discuss your requirements.

Or download our latest paper: “Automating IR.21 and IR.85 change implementation in your operations” – and take the essential next step for capitalising on new roaming opportunities, like 5G SA which is on your horizon.