Google wants to make it easy for carriers to have interoperable RCS...

Google wants to make it easy for carriers to have interoperable RCS messaging

0 38

Last week Sprint and Rogers announced that users sending messages between the two carriers will be able to make use of RCS. RCS, of course, is the new standard to replace SMS that Google committed to back in 2015. So far each carrier seems to have its own idea for how RCS should work. But Google’s recent work in cross-carrier communication is a big step towards ubiquity, and thanks to the tech behind this latest interconnect other carriers can more easily get in on the RCS action.

We are deploying a “hub” model, so that carriers can interconnect to the hub once to get access to all other carriers connected to the hub.
— Nick Fox (@RealNickFox) June 5, 2017

Google’s Nick Fox followed up his announcement on the 1st with an answer to a question posed by our own Artem about how Google’s RCS interconnect works. Instead of requiring that carriers individually connect their networks in some capacity to one another to exchange RCS messages, the RCS standards used by Google and the GSMA make use of a hub-style interconnect.

Google’s hub-based implementation of RCS in the recent cross-carrier announcement isn’t a new technology, but it is cool. Back in 2013, the GSM Association published a white paper that detailed how RCS could work — and it’s very much worth a read if you are even mildly interested in the future of carrier messaging, RCS, or even just networking. The white paper showed a few different methods for RCS implementation, such as using a direct NNI (Network-Network Interface) decentralized network for each carrier interconnection. Unfortunately, that particular solution results in a quickly rising number of interconnects as the number of carriers increases (n(n – 1) / 2), which means for each additional carrier in the network a larger investment needs to be made

Article originally published at: Android Police