Rich Communication Services

Last updated

Rich Communication Services
Google Messages RCS share.jpg
A thread of conversation and media in the Google Messages application on Android
Developer GSMA
Type Instant messaging
Launch dateSeptember 15, 2008;15 years ago (2008-09-15)
Platform(s) various Android smartphones, iPhone in 2024
Operating system(s) Android 5 and later, iOS in 2024
StatusActive
Website www.gsma.com/futurenetworks/rcs/

Rich Communication Services (RCS) is a communication protocol between mobile telephone carriers and between phone and carrier, aiming at replacing SMS messages with a text-message system that is richer, provides phonebook polling (for service discovery), and can transmit in-call multimedia. It is part of the broader IP Multimedia Subsystem. Google has added support for end-to-end encryption for all chats using RCS in their own app, Google Messages. End-to-end encryption is not a feature of RCS specified by GSMA, instead deferring to the individual messaging clients to establish encryption. [1] [2] [3] [4]

Contents

It is also marketed as Advanced Messaging, [5] and was marketed as chat features, [6] joyn, SMSoIP, [7] Message+, and SMS+. [8]

In early 2020, it was estimated that RCS was available from 88 operators in 59 countries with approximately 390 million users per month. [9] By November 2020, RCS was available globally in Google Messages on Android, provided directly by Google if the operator does not provide RCS. [10] By 2023, there were 800 million active RCS users on Google's platform and 1.2 billion handsets worldwide supporting RCS. [11]

History

The Rich Communication Suite industry initiative [12] was formed by a group of industry promoters in 2007. In February 2008 the GSM Association (GSMA) officially became the project home of RCS and an RCS steering committee was established by the organization, officially announced as Rich Communications Suite on September 15, 2008. [13]

The steering committee specified the definition, testing, and integration of the services in the application suite known as RCS. [14] [15] [16] Three years later, the RCS project released a new specification – RCS-e (e = "enhanced"), which included various iterations of the original RCS specifications. The GSMA program is now called Rich Communication Services. [17]

The GSMA published the Universal Profile in November 2016. [18] The Universal Profile is a single GSMA specification for advanced communications. Carriers that deploy the Universal Profile guarantee interconnection with other carriers. As of early 2017, there were 47 mobile network operators, 11 manufacturers, and 2 OS providers (Google and Microsoft) that had announced their support of the Universal Profile. [19] Google's Jibe Cloud platform is an implementation of the RCS Universal Profile, designed to help carriers launch RCS quickly and scale easily. [20]

Samsung was one of the first major device original equipment manufacturers (OEMs) to support RCS. Samsung RCS capable devices have been commercially launched in Europe since 2012 and in the United States since 2015.

Google supports RCS on Android devices with its Android SMS app Google Messages, beginning with Lollipop across Android devices. [21] [22] In April 2018, it was reported that Google would be transferring the team that was working on its Google Allo messaging service to work on a wider RCS implementation. [23] [24] [25] In June 2019, Google announced that it would begin to deploy RCS on an opt-in basis via the Messages app, with service compliant with the Universal Profile and hosted by Google rather than the user's carrier, if the carrier does not provide RCS. The rollout of this functionality began in France and the United Kingdom. [23] [24] [26]

In response to concerns over the lack of end-to-end encryption in RCS, Google stated that it would only retain message data in transit until it is delivered to the recipient. [27] In November 2020, Google later announced that it would begin to roll out end-to-end encryption for one-on-one conversations between Messages users, using RCS but not part of the GSMA's RCS specifications, beginning with the beta version of the app. [28] In December 2020, Samsung updated its One UI Messages app to also allow users to opt into RCS. [29] Google added end-to-end encryption to their Messages app using the Signal Protocol as the default option for one-on-one RCS conversations starting in June 2021. Google stated it would like to collaborate with other companies to make end to end encryption over RCS compatible with other apps. [30] [31] [1] [32] In December 2022, end-to-end encryption was added to group chats in the Google Messages app for beta users and was made available to all users in August 2023. Additionally, Google enabled RCS in Messages by default to encourage end-to-end encryption adoption. [3] [4] [33]

In October 2019, the four major U.S. carriers announced an agreement to form the Cross-Carrier Messaging Initiative to jointly implement RCS using a newly developed app. This service was to be compatible with the Universal Profile. [34] However, this carrier-made app never came to fruition. And later, both T-Mobile and AT&T signed deals with Google to adopt Google's Messages app. [35] [36] [37]

In September 2022, Apple CEO Tim Cook said the company had no plans to support RCS on its devices or any interoperability with iMessage. [38] However, in November 2023, an Apple spokesperson announced that Apple plans to introduce RCS support in 2024. The decision came after the Ministry of Industry and Information Technology proposed new regulation which could have required Apple to support RCS. [39] [40] Apple stated it will not support Google's end-to-end encryption extension over RCS, but would work with GSMA to create an RCS encryption standard. [40]

RCS specifications

RCS Universal Profile

The GSMA's Universal Profile is a globally agreed-upon standard for implementing RCS. The profile allows subscribers of different carriers and nations to communicate with each other. [41] Universal Profile became the dominant RCS specification since its introduction.

Version 1.0 (November 2016) [42]
Includes core features such as capability discovery which will be interoperable between regions, chat, group chat, file transfer, audio messaging, video share, multi-device, enriched calling, location share and live sketching.
Version 2.0 (July 2017) [42]
Includes Messaging as a Platform, APIs, plug-in integration and improved authentication and app security.
Version 2.1 (December 2017) [42]
Version 2.2 (May 2018) [42]
Version 2.3 (December 2018) [42]
Version 2.4 (October 2019) [42]
Removes plug-in integration and includes integrated seamless web-view.

Historical RCS Specifications

Before Universal Profile RCS, there was a variety of proprietary RCS specifications that did not allow RCS messaging between carriers. [43] RCS combines different services defined by 3GPP and Open Mobile Alliance (OMA) with an enhanced phonebook. Another phone's capabilities and presence information can be discovered and displayed by a mobile phone. RCS reuses 3GPP specified IMS core system as the underlying service platform taking care of issues such as authentication, authorization, registration, charging and routing.

Release 1 Version 1.0 (December 15, 2008)

Offered the first definitions for the enrichment of voice and chat with content sharing, driven from an RCS enhanced address book (EAB).

Release 2 Version 1.0 (August 31, 2009)

Added broadband access to RCS features: enhancing the messaging and enabling sharing of files.

Release 3 Version 1.0 (February 25, 2010)

Focused on the broadband device as a primary device.

Release 4 Version 1.0 (February 14, 2011)

Included support for LTE.

Release 5 Version 1.0 (April 19, 2012)

RCS 5.0 was completely backwards-compatible with RCS-e V1.2 specifications and also includes features from RCS 4 and new features such as IP video call, IP voice call and Geo-location exchange. RCS5.0 supported both OMA CPM and OMA SIMPLE IM. RCS 5.0 included the following features.
  • Standalone Messaging
  • 1-2-1 Chat
  • Group Chat
  • File Transfer
  • Content Sharing
  • Social Presence Information
  • IP Voice call (IR.92 and IR.58)
  • IP Video call (IR.94)
  • Geolocation Exchange
  • Capability Exchange based on Presence or SIP OPTIONS

Release 5.1

5.1 was completely backwards compatible with the RCS-e V1.2 and RCS 5.0 specifications. It introduced additional new features such as Group Chat Store & Forward, File Transfer in Group Chat, File Transfer Store & Forward, and Best Effort Voice Call, as well as lessons-learnt and bug fixes from the V1.2 interoperability testing efforts. RCS 5.1 supported both OMA CPM and OMA SIMPLE IM.
  • Version 1.0 (August 13, 2012)
  • Version 2.0 (May 3, 2013)
  • Version 3.0 (September 09, 2013)
  • Version 4.0 (November 28, 2013)

Release 5.2 Version 5.0 (May 7, 2014)

Improved central message store and introduced service extension tags into the specification. It also introduced a number of incremental improvements and bug fixes to RCS 5.1 V4.0 that improved the user experience and resolve issues that were noticed in deployed RCS networks.

Release 5.3 Version 6.0 (February 28, 2015)

Release 6.0 Version 7.0 (March 21, 2016)

Support for Visual Voice Mail and more

Release 7.0 Version 8.0 (June 28, 2017)

Support for Chatbots, SMS fallback features and more

Release 8.0 Version 9.0 (May 16, 2018)

Support for additional Chatbots features and vCard 4.0

RCS-e (enhanced)

Joyn

The GSMA defined a series of specific implementations of the RCS specifications. The RCS specifications often defined a number of options for implementing individual communications features, resulting in challenges in delivering interoperable services between carriers. The RCS specifications aimed to define a more specific implementation that promotes standardization and simplify interconnection between carriers.

RCS Business Messaging

RCS Business Messaging (RBM) is the B2C (A2P in telecoms terminology) version of RCS. This is supposed to be an answer to third-party messaging apps (or OTTs) absorbing mobile operators' messaging traffic and associated revenues. While RCS is designed to win back Person-to-Person (P2P) traffic, RBM is intended to retain and grow this A2P traffic. [48] [49] RCS offers "rich" features similar to those of messaging apps, but delivered (in theory) via the preloaded SMS messaging app - for example Google Messages or Samsung Messages. By making these features available in a B2C setting, RBM is expected to attract marketing and customer service spend from enterprises, thanks to improved customer engagement and interactive features that facilitate new use cases. [50] [51] This was the primary reason for the development of RCS by the GSMA.

RBM includes features not available to ordinary users, including predefined quick-reply suggestions, rich cards, carousels, and branding. This last feature is intended to increase consumer confidence and reduce fraud through the implementation of a verified sender system. [52] These additional features are only available with the use of a messaging-as-a-platform (MaaP) server integrated with the operator's network. The MaaP controls the verified sender details, unlocking RBM features, while also segregating P2P and A2P RCS messages, aiding monetisation of the latter (SMS currently suffers from grey routes, where A2P messages are sent over P2P connections, which are cheaper or often free). [53]

Status

According to GSMA PR in 2012, Rich Communication Services (RCS) carriers from around the globe supporting the RCS standard included AT&T, Bell Mobility, Bharti Airtel, Deutsche Telekom, Jio, KPN, KT Corporation, LG U+, Orange, Orascom Telecom, Rogers Communications, SFR, SK Telecom, Telecom Italia, Telefónica, Telia Company, Telus, Verizon and Vodafone. [54]

Universal Profile is currently backed by "a large and growing ecosystem" (68 supporters in 2019). Universal Profile support is optional in 4G, but mandatory in 5G networks and devices. [55]

RCS launches [57]
OperatorCountryLaunch dateNote
Movistar Flag of Spain.svg  Spain June 2012 [58] Branded as joyn.
MetroPCS Flag of the United States.svg  United States November 2012 [58] Branded as joyn.
KT Flag of South Korea.svg  South Korea December 2012 [58] [59] Branded as joyn. Discontinued in 2016.
LG U+ Flag of South Korea.svg  South Korea December 2012 [58] [59] Branded as joyn. Discontinued in 2016.
SK Telecom Flag of South Korea.svg  South Korea December 2012 [58] [59] Branded as joyn.
Deutsche Telekom Flag of Germany.svg  Germany February 2013 [58] Branded as Message+ [60]
Telcel Flag of Mexico.svg  Mexico February 2013 [58] Branded as joyn.
Claro Multiple marketsMay 2013 [58] Branded as joyn.
Sprint Flag of the United States.svg  United States October 2013Launched as a separate application
U.S. Cellular Flag of the United States.svg  United States October 2018Universal Profile [61]
Telekom Flag of Romania.svg  Romania June 2014 [62] [63] Branded as joyn.
Slovak Telekom Flag of Slovakia.svg  Slovakia June 2014 [62] [63] Branded as joyn.
O2 Flag of Germany.svg  Germany 2015 [64] Branded as Message+Call.
SFR Flag of France.svg  France May 2015 [65] [66] Initially branded as joyn, now RCS. [67]
T-Mobile US Flag of the United States.svg  United States July 2015 - September 2023 [68] Branded as Advanced Messaging. In June 2023, T-Mobile US converted to Google Jibe for RCS services. [69]
AT&T Flag of the United States.svg  United States November 2015 - June 2023Branded as Advanced Messaging and Video Call. [70] [71] In June 2023, AT&T converted to Google Jibe for RCS services. [72]
MTS Flag of Russia.svg  Russia December 2015 [73] Branded as MTS Connect.
Airtel Flag of India.svg  India February 2016
Jio Flag of India.svg  India September 2016 [74] Branded as Jio4GVoice.
Rogers Wireless Flag of Canada (Pantone).svg  Canada December 2016Universal Profile.
Fido Solutions Flag of Canada (Pantone).svg  Canada December 2016Universal Profile.
Telenor Multiple marketsFebruary 2017Universal Profile. [75]
Celcom Flag of Malaysia.svg  Malaysia May 2017Universal Profile.
Vodafone Multiple markets2012-2017 [76] Universal Profile. [77]

[58] [78] [79] [80] [81] First Branded as joyn. Since November 2013 Message+.

Telstra Flag of Australia (converted).svg  Australia October 2017Branded as Telstra Messaging. [82] Universal Profile v2. [83]
Telia Company Flag of Sweden.svg  Sweden December 2017Branded as SMS+. [84]
Telia Company Flag of Norway.svg  Norway February 2018Branded as SMS+. [84]
Globe Telecom Flag of the Philippines.svg  Philippines February 2018Universal Profile
NTT Docomo Flag of Japan.svg  Japan May 2018Branded as +Message. [85]
KDDI Flag of Japan.svg  Japan May 2018Branded as +Message. [85]
SoftBank Corp. Flag of Japan.svg  Japan May 2018Branded as +Message. [85]
Rakuten Mobile Flag of Japan.svg  Japan April 2020As part of Link application. [86]
Freedom Mobile Flag of Canada (Pantone).svg  Canada October 2018Universal Profile.
Verizon Flag of the United States.svg  United States December 2018Branded as Chat and launched as part of Android's default Messenger app with initial rollout for Pixel 3 phones. By 2022, Google's Messages app with RCS became the default messaging app for Android phones on Verizon. [87] In February 2024, Verizon announced a conversion to Google Jibe for RCS services. [88]
Google Fi Wireless Flag of the United States.svg  United States January 2019Universal Profile.
Google (Note: Not a carrier)🌐 GlobalNovember 2019In Google's Messages app, if a carrier does not provide Universal Profile RCS, Google provides RCS. [10]
Telekom Albania Flag of Albania.svg  Albania Universal Profile.
Bell Flag of Canada (Pantone).svg  Canada Universal Profile.
China Mobile Flag of the People's Republic of China.svg  China Universal Profile.
Orange Multiple markets2012-2019 [89] Branded as Chat Messages in Romania, [90] joyn elsewhere. [58] [62] [63]

[91] Since July 2018 branded as Chat - Universal profile in Slovakia.

[92] Service in France was interrupted as of 14 November 2017.

Boost Flag of the United States.svg  United States Universal Profile.
COSMOTE Flag of Greece.svg  Greece Branded as Message+ [93]
Telekom Flag of Hungary.svg  Hungary Universal Profile.
Vodacom Flag of South Africa.svg  South Africa Universal Profile.
Telkom Mobile Flag of South Africa.svg  South Africa Universal Profile. [94]
Illinois Valley CellularFlag of the United States.svg  United States Universal Profile.
Tiercel WirelessFlag of the United States.svg  United States Universal Profile.
TracFone Wireless Flag of the United States.svg  United States Universal Profile.
T-Mobile US Flag of the United States.svg  United States May 2020Universal Profile [95]
Swisscom Flag of Switzerland (Pantone).svg   Switzerland April 2020Branded as Message+ [96] Discontinued in 2023.
Proximus Flag of Belgium (civil).svg  Belgium August 2020 [97]
MTS Flag of Russia.svg  Russia October 2020Only for Samsung smartphones and only for Moscow customers, [98] MTS Connect still works for all MTS customers
Base Flag of Belgium (civil).svg  Belgium February 2021 [89]

Interconnect and hubs

Like SMS, RCS requires national and international interconnects to enable roaming. As with SMS, this will be accomplished with hubbing - where third-party providers complete agreements with individual operators to interwork their systems. Each subsequent operator that connects to a hub is therefore connected automatically to all other connected operators. This eliminates the need to each operator to connect to all the others to which they may need to send messages. [99] RCS hubs are provided by stakeholders with a vested interest in increasing RCS use. These include traditional SMS hub providers (e.g. Global Message Services and Sinch), software and hardware vendors (e.g. Interop Technologies, Mavenir, and ZTE), and also Google via its Jibe Cloud platform. [100]

Accreditation

The RCS interop and testing (IOT) accreditation process [101] was started by the GSMA in order to improve the quality of testing, increase transparency, drive scale, minimize complexity and accelerate time-to-market (TTM) of joyn services. Companies need to undertake the IOT process from the GSMA to apply for a license to use the service mark joyn.

"Accredited" means that the device, client or network has undertaken a series of test cases (150 to 300) in a specific set of conditions, provided test results and traces that have been analysed by the GSMA RCS IOT team and any IOT issues arising resolved with the submitter. [102]

"Accreditation Ready" is the designation awarded to a hosted RCS service that has undertaken the same series of test cases as the mobile network operator, provided test results and traces that have been analysed by the GSMA RCS IOT team and any IoT issues arising resolved with the submitter. [102]

A list of RCS AS providers and their GSMA RCS Accreditation status can be found here: [103]

Reception

In 2018, Amnesty International researcher Joe Westby criticized RCS for not allowing end-to-end encryption, because it is treated as a service of carriers and thus subject to lawful interception. [104] [105]

The Verge in 2019 criticized the inconsistent support of RCS in the United States, with carriers not supporting RCS in all markets, not certifying service on all phones, or not yet supporting the Universal Profile. Concerns were shown over Google's decision to run its own RCS service due to the possibility of antitrust scrutiny, but it was acknowledged that Google had to do so in order to bypass the carriers' inconsistent support of RCS, as it wanted to have a service more comparable to Apple's iMessage service available on Android. [27] [106]

Ars Technica in 2019 criticized Google's move to launch a direct-to-consumer RCS service, considering it a contradiction of RCS being native to the carrier to provide features reminiscent of messaging apps, counting it as being among various past and unsuccessful attempts by Google to develop an in-house messaging service (including Google Talk, Google+ Messenger, Hangouts, and Allo), and noting limitations: such as its dependencies on phone numbers as the identity (whereas email-based accounts are telco-agnostic), not being capable of being readily synchronized between multiple devices, and the aforementioned lack of end-to-end encryption. [107]

See also

Related Research Articles

<span class="mw-page-title-main">Instant messaging</span> Form of communication over the internet

Instant messaging (IM) technology is a type of online chat allowing immediate transmission of messages over the Internet or another computer network. Messages are typically transmitted between two or more parties, when each user inputs text and triggers a transmission to the recipient(s), who are all connected on a common network. It differs from email in that conversations over instant messaging happen in real-time. Most modern IM applications use push technology and also add other features such as emojis, file transfer, chatbots, voice over IP, or video chat capabilities.

The landscape for instant messaging involves cross-platform instant messaging clients that can handle one or multiple protocols. Clients that use the same protocol can typically federate and talk to one another. The following table compares general and technical information for cross-platform instant messaging clients in active development, each of which have their own article that provide further information.

<span class="mw-page-title-main">Google Talk</span> Instant messaging service

Google Talk was an instant messaging service that provided both text and voice communication. The instant messaging service was variously referred to colloquially as Gchat, Gtalk, or Gmessage among its users.

This is a comparison of voice over IP (VoIP) software used to conduct telephone-like voice conversations across Internet Protocol (IP) based networks. For residential markets, voice over IP phone service is often cheaper than traditional public switched telephone network (PSTN) service and can remove geographic restrictions to telephone numbers, e.g., have a PSTN phone number in a New York area code ring in Tokyo.

eBuddy Instant messaging software

eBuddy is a privately held Dutch software company that offers instant messaging services. As of 2011, eBuddy reported 100 million downloads. The company's flagship service is XMS, a proprietary cross-platform instant messaging service. After some changes of ownership, the company is now again owned by its original founders, Onno Bakker and Jan-Joost Rueb.

<span class="mw-page-title-main">WhatsApp</span> Messaging and VoIP service owned by Meta Platforms

WhatsApp is an instant messaging (IM) and voice-over-IP (VoIP) service owned by technology conglomerate Meta. It allows users to send text, voice messages and video messages, make voice and video calls, and share images, documents, user locations, and other content. WhatsApp's client application runs on mobile devices, and can be accessed from computers. The service requires a cellular mobile telephone number to sign up. In January 2018, WhatsApp released a standalone business app called WhatsApp Business which can communicate with the standard WhatsApp client.

iMessage Instant messaging service by Apple

iMessage is an instant messaging service developed by Apple Inc. and launched in 2011. iMessage functions exclusively on Apple platforms – including macOS, iOS, iPadOS, and watchOS – as part of Apple's broader strategic approach to inter device integration, sometimes referred to as the Apple Eco-System.

<span class="mw-page-title-main">Messenger (software)</span> American instant messaging app

Messenger, also known as Facebook Messenger, is an American proprietary instant messaging app and platform developed by Meta Platforms. Originally developed as Facebook Chat in 2008, the company revamped its messaging service in 2010, released standalone iOS and Android apps in 2011, and released standalone Facebook Portal hardware for Messenger calling in 2018. In April 2015, Facebook launched a dedicated website interface, Messenger.com, and separated the messaging functionality from the main Facebook app, allowing users to use the web interface or download one of the standalone apps. In April 2020, Facebook released a Messenger desktop app for Windows and macOS.

<span class="mw-page-title-main">Google Hangouts</span> Communication software by Google

Google Hangouts was a cross-platform instant messaging service developed by Google. It originally was a feature of Google+, becoming a standalone product in 2013, when Google also began integrating features from Google+ Messenger and Google Talk into Hangouts. Google then began integrating features of Google Voice, its Internet telephony product, into Hangouts, stating that Hangouts was designed to be "the future" of Voice.

TextSecure was an encrypted messaging application for Android that was developed from 2010 to 2015. It was a predecessor to Signal and the first application to use the Signal Protocol, which has since been implemented into WhatsApp and other applications. TextSecure used end-to-end encryption to secure the transmission of text messages, group messages, attachments and media messages to other TextSecure users.

<span class="mw-page-title-main">Windows 10 Mobile</span> Mobile operating system developed by Microsoft

Windows 10 Mobile was a mobile operating system developed by Microsoft. First released in 2015, it is a successor to Windows Phone 8.1, but was marketed by Microsoft as being an edition of its PC operating system Windows 10.

<span class="mw-page-title-main">Signal (messaging app)</span> Privacy-focused encrypted messaging app

Signal is an encrypted messaging service for instant messaging, voice, and video calls. The instant messaging function includes sending text, voice notes, images, videos, and other files. Communication may be one-to-one between users or may involve group messaging.

eSIM Programmable SIM card embedded into a device

An eSIM (embedded-SIM) is a form of SIM card that is embedded directly into a device. Instead of an integrated circuit located on a removable SIM card, typically made of PVC, an eSIM consists of software installed onto an eUICC chip permanently attached to a device. If the eSIM is eUICC-compatible, it can be re-programmed with new SIM information. Otherwise, the eSIM is programmed with its ICCID/IMSI and other information at the time it is manufactured, and cannot be changed. Different mobile telephones may not support an eSIM, may have a permanently programmed, unchangeable one, or one that can be reprogrammed for any carrier that supports the technology. Phones may support physical SIMs only, eSIM only, or both.

<span class="mw-page-title-main">Google Allo</span> Instant messaging app by Google

Google Allo was an instant messaging mobile app by Google for the Android and iOS mobile operating systems, with a web client available in some web browsers. It closed on March 12, 2019.

The Signal Protocol is a non-federated cryptographic protocol that provides end-to-end encryption for voice and instant messaging conversations. The protocol was developed by Open Whisper Systems in 2013 and was first introduced in the open-source TextSecure app, which later became Signal. Several closed-source applications have implemented the protocol, such as WhatsApp, which is said to encrypt the conversations of "more than a billion people worldwide" or Google who provides end-to-end encryption by default to all RCS-based conversations between users of their Google Messages app for one-to-one conversations. Facebook Messenger also say they offer the protocol for optional Secret Conversations, as does Skype for its Private Conversations.

<span class="mw-page-title-main">Element (software)</span> Decentralized encrypted chat and collaboration software powered by the Matrix protocol

Element is a free and open-source software instant messaging client implementing the Matrix protocol.

<span class="mw-page-title-main">Google Messages</span> Messaging application developed by Google

Google Messages is a text messaging software application developed by Google for its Android and Wear OS mobile operating systems, while it's also available via the Web.

Comparison of user features of messaging platforms refers to a comparison of all the various user features of various electronic instant messaging platforms. This includes a wide variety of resources; it includes standalone apps, platforms within websites, computer software, and various internal functions available on specific devices, such as iMessage for iPhones.

Beeper Inc. is an American software company that develops the instant messaging applications Beeper Cloud and Beeper Mini. The company is located in Palo Alto, California.

References

  1. 1 2 Bohn, Dieter (19 November 2020). "Google is rolling out end-to-end encryption for RCS in Android Messages beta". The Verge. Vox Media, Inc. Retrieved 28 November 2020.
  2. Omara, Emad (June 2021). Technical Paper: Messages End-to-End Encryption Overview - (PDF). gstatic.com (Report). 1.1.
  3. 1 2 "Google Messages Gets End-to-End Encryption for Group Chats on Android". PCMAG. Retrieved 2 December 2022.
  4. 1 2 Li, Abner (2 December 2022). "Google Messages starts rolling out end-to-end encryption (E2EE) for group chats in beta". 9to5Google . Retrieved 2 December 2022.
  5. "Advanced Messaging". T-Mobile Support. Retrieved 29 February 2024.
  6. Friedman, Alan (23 February 2023). "Google drops "Chat" for "RCS" on Android". Phone Arena. Retrieved 26 February 2023.
  7. "About joyn". GSMA. Archived from the original on 29 January 2013. Retrieved 7 March 2013.
  8. "SMS+ - Telia.se". Telia.se (in Swedish). Retrieved 20 April 2018.
  9. "RCS Set to Revolutionize Mobile Messaging Ecosystem". Forest Interactive. Retrieved 18 November 2020.
  10. 1 2 "Helping you connect around the world with Messages". Google. 19 November 2020. Retrieved 26 November 2023.
  11. MEF (21 November 2023). "RCS Business Messaging Takes Center Stage: Takeaways from RCS World 2023 - Blog". MEF. Retrieved 27 November 2023.
  12. PALOU, NACHO (12 June 2012). "Joyn, un servicio de mensajería instantánea limitado a las operadoras móviles". RTVE.es.
  13. "GSMA To Take Rich Communication Suite Forwards" . Retrieved 20 November 2023.
  14. "Rich Communications". GSMA. Retrieved 7 March 2013.
  15. "Strategic Rationale". GSMA. Archived from the original on 3 March 2014. Retrieved 7 March 2013.
  16. "Operators, Ecosystem & Hosted Solutions | Network 2020". Archived from the original on 2 October 2015.
  17. "Rich Communications – past, present & future". GSMA. Archived from the original on 23 May 2012. Retrieved 18 October 2012.
  18. "Universal Profile FAQs" (PDF). GSMA. 17 November 2016. Archived from the original (PDF) on 30 January 2017. Retrieved 24 February 2017.
  19. "Universal profile - Network 2020". GSM Association (GSMA) . Archived from the original on 27 January 2017. Retrieved 25 February 2017.
  20. "Jibe Platform". jibe.google.com. Retrieved 24 February 2017.
  21. Wanjala, Alvin. "How to Check if Your Android Phone Has RCS" . Retrieved 20 November 2023.
  22. Kuczynski, Kyle. "What is RCS Messaging? Rich Communication Services Guide" . Retrieved 20 November 2023.
  23. 1 2 "Google gives up on Google Allo, hopes carriers will sort out RCS messaging". Ars Technica. Retrieved 20 April 2018.
  24. 1 2 "Exclusive: Chat is Google's next big fix for Android's messaging mess". The Verge. Retrieved 20 April 2018.
  25. "Google is 'pausing investment' in Allo". The Verge. 19 April 2018.
  26. Bohn, Dieter (17 June 2019). "Google is finally taking charge of the RCS rollout". The Verge. Retrieved 24 November 2023.
  27. 1 2 Bohn, Dieter (17 June 2019). "Google is finally taking charge of the RCS rollout". The Verge. Retrieved 18 June 2019.
  28. Bohn, Dieter (19 November 2020). "Google is rolling out end-to-end encryption for RCS in Android Messages beta". The Verge. Retrieved 19 November 2020.
  29. "Samsung Messages starts adding support for Google RCS Chat". Android Police. 16 December 2020. Retrieved 17 December 2020.
  30. Amadeo, Ron (16 June 2021). "Google enables end-to-end encryption for Android's default SMS/RCS app". Ars Technica.
  31. Clark, Mitchell (15 June 2021). "Google adds E2E RCS encryption to Messages, emoji mashup suggests, and more for Android". The Verge.
  32. Omara, Emad (June 2021). Technical Paper: Messages End-to-End Encryption Overview - (PDF). gstatic.com (Report). 1.1.
  33. "Your RCS conversations are now fully end-to-end encrypted - Google Messages Community". support.google.com. Retrieved 30 November 2023.
  34. Bohn, Dieter (24 October 2019). "AT&T, Verizon, Sprint, and T-Mobile have finally agreed to replace SMS with a new RCS standard". The Verge. Retrieved 25 October 2019.
  35. Bohn, Dieter (29 March 2021). "T-Mobile is betting big on Google's Android services: RCS, YouTube TV, Pixel, and more". The Verge. Retrieved 15 July 2021.
  36. Bohn, Dieter (30 June 2021). "AT&T joins T-Mobile in switching all Android cellular communication devices to Google's 'Messages' app for RCS". The Verge. Retrieved 15 July 2021.
  37. "Android Fans Just got a Texting Upgrade. T-Mobile and Google Join Forces to Expand Rich Messaging (RCS) | T-Mobile Newsroom". T-Mobile Newsroom. Retrieved 15 July 2021.
  38. Roth, Emma (7 September 2022). "Tim Cook says "buy your mom an iPhone, if you want to end green bubbles."". The Verge. Retrieved 8 September 2022.
  39. 1 2 Miller, Chance (16 November 2023). "Apple announces that RCS support is coming to iPhone next year". 9to5Mac. Retrieved 16 November 2023.
  40. 1 2 John Gruber (16 November 2023). "The European Commission Had Nothing to Do With Apple's Reversal on Supporting RCS". Daring Fireball. Retrieved 16 February 2024.
  41. "Universal Profile". Future Networks. Retrieved 22 November 2023.
  42. 1 2 3 4 5 6 "Universal Profile - Thank You". Future Networks. Retrieved 23 November 2023.
  43. "Everything You Need to Know About RCS Universal Profile". Gadget Hacks. 5 November 2016. Retrieved 22 November 2023.
  44. "V1.2 joyn Hot Fixes, User Experience Guidelines". GSMA. 15 July 2013. Retrieved 26 November 2023.
  45. "joyn Blackbird Drop 1 accreditation guidelines 1.0" (PDF). GSMA. 19 June 2013. Retrieved 26 November 2023.
  46. "joyn Blackbird Product Definition Document Version 2.0" (PDF). GSMA. 26 September 2013. Retrieved 26 November 2023.
  47. "joyn Crane Product Definition Document Version 2.0" (PDF). GSMA. 18 August 2015. Retrieved 26 November 2023.
  48. "RCS Business Messaging". GSMA - Future Networks. Retrieved 6 February 2020.
  49. Aragon, Carlos (15 July 2019). "BRINGING MESSAGING BACK TO THE CARRIERS". Mavenir. Retrieved 6 February 2020.
  50. "Will Rich Communication Services (RCS) revolutionize business messaging?". MarTech Today. 29 August 2019. Retrieved 6 February 2020.
  51. Debris, Virginie (30 October 2019). "GMS' Chief Product Officer Virginie Debris on the real value of RBM". gms-worldwide.com. Retrieved 6 February 2020.
  52. MEF (25 October 2018). "Fraud-free RCS business messaging: Is it possible? - Blog". MEF. Retrieved 6 February 2020.
  53. GSMA Future Networks (August 2019). "Enabling your Network for RCS Business Messaging" (PDF). GSMA. Retrieved 6 February 2020.
  54. "Mobile Operators Show Increased Momentum in Rich Communications". PR Newswire. 27 February 2012.
  55. "Universal profile". GSMA. Retrieved 19 October 2021.
  56. Goldstein, Phil (5 March 2015). "Jibe Mobile CEO says RCS isn't dead, points to native IP messaging embedded on smartphones". Fierce Wireless. Retrieved 27 August 2022.
  57. "Global Launches - Future Networks" . Retrieved 14 February 2019.
  58. 1 2 3 4 5 6 7 8 9 10 "RCS Fact October 2013" (PDF). GSMA. 29 October 2013. Retrieved 9 March 2014.
  59. 1 2 3 "Korean operators launch joyn service". Telecompaper. 27 December 2012. Retrieved 27 December 2012.
  60. "Deine Telefon- und Nachrichten-Funktionen können jetzt noch mehr!". Deutsche Telekom. Archived from the original on 12 September 2017. Retrieved 15 October 2015.
  61. "Get More Out ofTexting". US Cellular. n.d. Retrieved 28 October 2018.
  62. 1 2 3 "Jibe Mobile powers Deutsche Telekom joyn expansion in Romania and Slovakia" Fierce Wireless. 2014-06-30. Retrieved 2014-07-02.
  63. 1 2 3 "Cosmote Romania, Slovak Telekom launch Joyn apps". Telecompaper. 30 June 2014. Retrieved 30 June 2014.
  64. "Die neue O2 Message+Call App: Jetzt mit dem Smartphone im WLAN telefonieren" (in German). o2 Germany. 11 August 2015. Archived from the original on 11 September 2018. Retrieved 26 November 2015.
  65. "SFR Launches RCS Native Messaging for Samsung and Sony Mobile Smartphones — powered by Jibe's Communications Cloud". 3 July 2015. Retrieved 20 November 2020.
  66. "Network Interconnection of Rich Communication Services between Orange France and SFR". 21 May 2015. Retrieved 20 November 2020.
  67. "Messagerie enrichie RCS - SFR" . Retrieved 20 November 2020.
  68. "Announcing Advanced Messaging. Only at T-Mobile". T-Mobile. Retrieved 22 July 2015.
  69. Li, Abner (21 September 2023). "T-Mobile switching to Google's Jibe for RCS in Messages app". 9to5Google . Retrieved 27 November 2023.
  70. "AT&T Launches Video Calling and Advanced Messaging". AT&T. Retrieved 3 October 2016.
  71. "Advanced Messaging". AT&T. Retrieved 3 October 2016.
  72. "AT&T starts using Google's Jibe platform for RCS messages". Engadget. 11 June 2023. Retrieved 27 November 2023.
  73. "MTS Connect". MTS. Archived from the original on 27 September 2020. Retrieved 25 December 2015.
  74. "RCS launches" (PDF). GSMA. Retrieved 28 April 2018.
  75. "Partnering with Telenor to launch RCS messaging in Europe and Asia". Google. 16 February 2017. Retrieved 25 February 2017.
  76. "Global Launches - Future Networks". GSMA . Retrieved 10 November 2017.
  77. "Delivering RCS messaging to Android users worldwide". Google. 24 February 2017. Retrieved 25 February 2017.
  78. "WhatsApp-Konkurrent: Vodafone startet mit Message+" (in German). teltarif. 8 November 2013. Retrieved 28 April 2014.
  79. "Vodafone Albania introduces monthly bundle, Message+". Telecompaper. 28 April 2014. Retrieved 28 April 2014.
  80. "Understanding Message+ and RCS: Why we're giving you the future of texting before anyone else". Vodafone UK. 10 September 2014. Archived from the original on 24 July 2019. Retrieved 18 August 2016.
  81. "Your texts and chat messages - all in one place". Vodafone UK. Retrieved 18 August 2016.
  82. "Telstra Messaging FAQs - Telstra Crowdsupport - 713814". crowdsupport.telstra.com.au. Retrieved 26 October 2017.
  83. "Telstra RCS Support on Messages - Telstra". Whirlpool.net.au.
  84. 1 2 "Telia Company partners with Google for Improved Messaging Service". www.teliacompany.com. Retrieved 14 December 2017.
  85. 1 2 3 田中聡 (10 April 2018). "SMSやキャリアメールとの違いは? 「+メッセージ」でできること、できないこと". ITmedia mobile (in Japanese). ITmedia Inc. Retrieved 20 April 2018.
  86. "Mavenir Cloud-Native RCS Solution Launches as Part of Rakuten Mobile Communication Platform, Rakuten Link". www.businesswire.com. Retrieved 7 April 2020.
  87. Bohn, Dieter (20 July 2021). "Verizon is also switching to Android Messages as default for RCS". The Verge. Retrieved 27 November 2023.
  88. Lawler, Richard (2 February 2024). "Verizon will switch to Google's Jibe platform to support RCS messaging on Android". The Verge. Retrieved 3 February 2024.
  89. 1 2 Sanchez, Laurent Redondo (1 February 2021). "Le RCS débarque chez BASE, après Orange et Proximus". BeMobile (in French). Retrieved 27 August 2022.
  90. "Orange anunţă Chat Messages, serviciu bazat pe standardul RCS". Orange.ro. 16 October 2017. Retrieved 16 October 2017.
  91. Živé.sk. "Orange podporuje Chat v Androide. Konkurenciu pre Viber či Messenger (Slovak)". Živé.sk. Retrieved 1 August 2018.
  92. "Le service joyn n'est plus disponible". Orange. Archived from the original on 7 February 2018. Retrieved 21 April 2018.
  93. "Message+". www.cosmotemessageplus.gr. Retrieved 16 April 2022.
  94. "Rich Communication Service (RCS):Taking RCS to the South African Market" (PDF).
  95. Kastrenakes, Jacob (26 May 2020). "T-Mobile now supports cross-carrier RCS messaging". The Verge. Retrieved 8 July 2020.
  96. "RCS: introducing the future of SMS – Message+". community.swisscom.ch. 17 April 2020.
  97. "Le SMS 2.0 débarque chez Proximus". Geeko (in French). Retrieved 27 August 2022.
  98. "RCS – чат и SMS в одном приложении | Услуги частным клиентам | Официальный сайт МТС - Москва и Московская область". moskva.mts.ru. Retrieved 8 March 2021.
  99. Flynn, Ray (2013). "RCS Hub White Paper" (PDF). GSMA. Retrieved 4 February 2020.
  100. "The RCS Ecosystem". GSMA Future Networks. Retrieved 4 February 2020.
  101. "Accreditation and Certification". 14 November 2017.
  102. 1 2 "GSMA RCS Interop and Testing". GSMA. Archived from the original on 12 October 2012. Retrieved 18 October 2012.
  103. https://www.gsma.com/futurenetworks/wp-content/uploads/2020/05/List-of-current-accreditations-for-Hosted-Solutions-Providers-v6.pdf [ bare URL PDF ]
  104. "Google's new Chat service shows total contempt for Android users' privacy". Amnesty International. 20 April 2018. Retrieved 24 April 2018.
  105. "Google's new chat service won't be secure like iMessage and WhatsApp: Amnesty International". The Indian Express. 22 April 2018. Retrieved 24 April 2018.
  106. Bohn, Dieter (9 May 2019). "With the Pixel 3A, T-Mobile just proved how broken the RCS Chat rollout has become". The Verge. Retrieved 18 June 2019.
  107. Amadeo, Ron (18 June 2019). "Google's ninth attempt at a messaging service will be based on RCS". Ars Technica. Retrieved 19 June 2019.