Long, prolonged ago, in a far-off year 2019, a 4 (at a time) US carriers came together to announce a singular partnership. They would work together on a new Cross Carrier Messaging Initiative, or CCMI, that betrothed interoperability for an RCS Universal Profile-based messaging standard. Originally set to be launched in 2020, we hadn’t listened really most about it for some time. According to a new report, there’s a good reason for that: The CCMI is dead.
The news comes from Light Reading — It’s a blog we might not have listened of, yet a site’s research and reports of network happenings and 5G are roughly always spot-on, and we trust them implicitly. According to a report, a now 3 US carriers have deserted a RCS-based project.
Although a association doing a logistics behind a cross-carrier bid claims that it’s still “continuing to pierce brazen with preparations,” a Verizon orator told Light Reading that “the owners of a Cross Carrier Messaging Initiative motionless to finish a corner try effort.” We reached out to serve endorse these sum with a folks that rubbed a 2019 announcement, yet they did not immediately respond for comment. (Also, Sprint rubbed that, and they kind of don’t exist now, so we’ll see if they even answer.)
In box this all feels like a variety of word salad so far, we have a detailed explainer about RCS Messaging. But in short, there’s a messaging customary called RCS that allows for extended messaging — consider of it as a inheritor to SMS, that we’re still regulating a whole lot here in a US. It supports things like review receipts, aloft peculiarity media, and improved organisation conversations, yet it doesn’t usually work on a possess like a normal discuss app that connects to centralized servers. As it was designed, RCS allows for any conduit network to spin adult a possess somewhat opposite chronicle and interconnect them — during least, so prolonged as they’re all concordant with a Universal Profile standards. Before a CCMI, opposite carriers had their possess systems (which could be flattering insecure) and some didn’t work with others, so we usually got a advantages of RCS messaging in specific apps and when articulate to people inside your specific conduit network, that is flattering dumb.
The CCMI radically promised that a carriers would all make their implementations cross-compatible — during a time, by what sounded like a jointly grown app. That would have meant someone on ATT could spin adult an RCS-based organisation review with friends on T-Mobile and Verizon by this app and suffer all a advantages of a new messaging customary in inter-carrier communications. But, sad trombone noises, this latest change means those skeleton are dead.
RCS “Chat” messaging in a Google Messages app.
This might seem like bad news, yet things have altered given 2019. In a time given a CCMI was announced, Google leapfrogged a carrier’s greedy dithering and rolled out a possess RCS messaging resolution around a Messages app, all connected to a Jibe network (though it will use your conduit network if it’s Universal Profile-compatible). It’s a pierce that means business don’t have to wait on their carriers to start a work they should have finished 5 years ago. More recently, T-Mobile has essentially handed a reins for a whole network messaging resolution to Google by adopting Messages as a default SMS app for all T-Mobile phones, joining all a business to Google’s RCS network.
Given what has and hasn’t succeeded when it comes to RCS messaging, what we’d like to see is for Verizon and ATT to follow T-Mobile, give adult on their possess foolish standards, and simply adopt Google’s RCS Messaging — possibly by joining their discuss apps to Google’s Jibe network somehow or by adopting a Messages app as authorised solutions, as T-Mobile did. But in a meantime, there’s zero to forestall business on possibly network from usually installing a Messages app themselves and bypassing a conduit disaster altogether — generally given it sounds like a carriers have given adult on regulating it.