Communication interoperability is vital to silo-free public safety comms

As we know, the concept of interoperability is multifaceted. At a basic engineering level, interoperability simply means that all elements of the communication network can communicate with each other. In other words, they are interoperable.

But in many cases, basic interoperability is not enough — more regulations and new policies are often needed to achieve full interoperability between systems and networks.

There are only two ways to achieve interoperability — open standards and gateways. If all communication elements adhere to the same open standard such as 3GPP MCX, for example, it means that all of those elements will communicate with each other directly. If, however, some of the elements are not standards-based, the only way to achieve interoperability is by using a gateway.

On the grand scheme of things, there is nothing wrong with gateways. Gateways provide connectivity between different types of communication technologies, such as PSTN and VoIP or LMR and MCX. Gateways have been around forever and will be around forever. When it comes to public safety operations, gateways are prolific and successful — think of RoIP gateways, for example.

But when an emergency happens, gateways don’t work. Ubiquitous broadband enables each agency to select their own proprietary communication technology, and then spend time and resources to address a specific interoperability use case with the gateway. However, emergencies don’t announce themselves in advance giving you time to prepare. If multiple agencies are responding, they have to be able to communicate, and when their core technologies differ, they can’t. You simply don’t have time to build gateways if agencies that need to cooperate on an emergency response use different technologies. The only way to be prepared for an emergency is by ensuring that one open, secure, reliable, interoperable communication technology is used by all. And this is why we have MCX.

An adoption of the open standard such as MCX can solve all interoperability issues of public safety communications. Now, the key word in the previous sentence is ‘adoption’. While MCX can solve interoperability issues, it first needs to be adopted by first responders — and that requires a significant effort.

I attended a number of ‘fire chat’ sessions on the subject of mission-critical voice during the recent FirstNet 5x5 event in Chicago. In the sessions, the users and public safety IT folks expressed their concern and frustration with the state of the MCX/MCPTT technology, poring over lots of user requirements that had not been addressed.

I was attending one of such sessions listening to the ‘unaddressed’ user requirements for MCPTT devices, such as the ability to control volume and channels (groups would be a proper MCPTT term), minimal UI, no need for the screen, sturdiness of the device and so on. Then at some point I simply raised my hand holding the L3Harris XL hybrid (dual-mode) radio, which answers all stated requirements.

It appears that many of the people in the audience — the people who deploy communication technology for first responders — didn’t even know that L3Harris devices are equipped with LTE capabilities and fully standard MCPTT client, and already deployed in the MCX networks.

So, there is hard (but critically necessary!) work required to achieve widespread adoption of MCX technology. And that in turn means that public safety professionals need to be educated on the benefits, value, capabilities and availability of MCX/MCPTT solutions — today, and in the future. Adoption and education should be critical work items for FirstNet — and any other public safety communications service provider.

When multiple agencies are covering the same event or responding to a given incident, all first responders should be able to communicate with each other. This is also called ‘interoperability’ — this is the word used in the US congress hearings, for example – and open standards offer the best and proper way to achieve it. Softil now wishes to take this terminology further and call interagency/first responder communications ‘communication interoperability’.

Anatoli Levine is Director of Products and Standards for Softil Ltd., responsible for developing strategy and product roadmap for Softil’s portfolio of enabling products for developers, including technologies such as Mission-Critical Communications (MCX) over LTE and 5G, WebRTC, VoLTE/ViLTE/RCS, SIP, IMS and many others. He actively participates in the development of open international communication standards at industry bodies such as 3GPP, ETSI, IETF and other SDOs.

Top image credit: iStock.com/Panuwat Srijantawong