Rich communication services is a protocol between both
mobile operators and phones. The overall aim of RCS is for it to eventually
replace SMS and MMS messaging, the formats we're all familiar with as they have
been around for years. RCS was first formed in 2007 and was taken over by the GSM
Association (GSMA), the industry trade body that represents mobile operators
worldwide, in 2008. In 2016, the GSMA agreed on a Universal Profile - a set of
standards that all mobile operators, phone manufacturers and software providers
can use to help implement RCS on devices. RCS messaging is very much like WhatsApp, where live chat
can take place, including multi-media support, with everything handled via the
data network. It's seen as a rival to Apple's iMessage service, although
there are some subtle differences between how these services operate. What's the current status of RCS messaging?
For a number of years, RCS has been widely supported by
mobile phone networks, software and devices. It's supported by the stock Google
Messages app available on Android. The problem has been that mobile phone
networks have been handed responsibility for support and few have moved on it. There are probably a number of reasons for that - dropping
SMS or MMS tariffs and working on cross-network functions are likely to have
seen RCS as low priority. However, in June 2019, Google took the reins back. This has
seen RCS messaging supported on Android devices and using Google's servers
rather than the mobile phone network's servers. Google has said, however, that
if a network supports RCS, its own servers can be used for transfer of
messages. That got the system off the ground, bringing a new messaging
platform to Android users - but Google only targeted France and the UK
initially. In the UK, the service went live on 28 June 2019 for some users;
there was wider roll-out in the US in December 2019. In the US the major US carriers - Verizon, AT&T, Sprint
and T-Mobile - agreed a cross-carrier solution for RCS in a programme called
CCMI - Cross-Carrier Messaging Initiative. This will bring RCS to the US from
2020, adhering to the Universal Profile outlined by the GSMA, but using its own
app. The details aren't fully clear, but there's confirmation that the CCMI
will work to interface with Google Messages and Samsung's app too. Whether this
gives a seamless result remains to be seen and more information will be
revealed in the future. Subsequently, T-Mobile has confirmed a partnership with
Google to allow T-Mo customers to use RCS with people on other networks. This
will work using the Google Messages app, so you just need to make sure they're
on the same Messages app on their end and that their network supports Universal
Profile too. What does RCS messaging do?
The biggest advantage RCS Messaging has over SMS - and the
reason it will be implemented in the first place - is that it will enable users
to send rich, verified messages. This means messages will be able to carry more
information, so users can send things like photos, videos and audio messages to
one another. They will be able to carry out video calls with one another
from directly within the messaging app, rather than having to rely on
third-party software. Group messages are possible, and little things such as
read receipts and indicators to show other users are typing a message will be
included as well. RCS messages will also do away with the 160 character limit
currently found in SMS messages. Businesses will be able to use RCS Messaging to send things
like boarding passes for airlines, package delivery notifications and credit
card fraud alerts. They're features that Apple iMessage, WhatsApp and Facebook
Messenger have offered for some time, but Android phones have gone without in a
default messaging application. For many, having one app to handle everything
will be key - and whether the new CCMI in the US will just let people use the
Google app remains to be seen. Are RCS messages secure?
RCS messages rely on data in order to be sent between users,
and so messages are sent with client-to-server encryption. The protocol should
also prevent spam messages from reaching your device, as for a company to be
able to send a message via RCS, they have to go through a brand verification
process. RCS messages received from companies will have the company's
name in the sender info, rather than just a mobile phone number. However, at the moment there's no universal support for
end-to-end encryption. As the initial roll-out will use Google's servers - and
potentially the network's own if supported - it means there's a couple of
places where your messages could potentially be intercepted. Encryption will
only be in place for the transmission of the messages. This might change, following the discovery of code relating
to end-to-end encryption in an unreleased version of Google Messages. As this
app is in the final stages of testing, it might be that encryption is going to
arrive soon on the Google's RCS service. Who is supporting RCS Messaging?
Many companies, including operators, manufacturers and
software providers have pledged their support for RCS Messaging, but by far and
away the biggest supporter is Google. The technology giant has been trying to increase the
adoption of RCS messaging in recent years, as it wants to implement it in all
Android phones. Google is rolling out the new features afforded by RCS as
"chat" and it is part the existing Android Messages app - alongside
SMS and MMS.
0 Comments