Skip to content

Updated RCS v3.1 now enhances voice message clarity by incorporating fresh codec support

GSMA moves to enhance user experience by focusing on various aspects of RCS development.

Update to RCS v3.1 improves voice message clarity through addition of new codec support
Update to RCS v3.1 improves voice message clarity through addition of new codec support

Updated RCS v3.1 now enhances voice message clarity by incorporating fresh codec support

The GSMA has announced the launch of the Universal Profile v3.1 update for RCS (Rich Communication Services) services, marking a significant step forward in improving audio quality and connection reliability.

This collaborative effort between global stakeholders aims to upgrade users' audio messaging capabilities, with the most notable enhancement being full support for the xHE-AAC audio codec. This codec allows for higher-quality voice notes and audio clips with more efficient compression, resulting in clearer and more natural sound even at lower bitrates[1][3][4].

In terms of reliability, Universal Profile 3.1 improves the client onboarding process and connectivity to mobile operator services by integrating closely with OS-level push notification services. This new mechanism makes it possible for RCS clients to stay inactive until awoken by push notifications, reducing battery drain and improving performance in areas with poor or inconsistent network coverage. Consequently, users experience fewer message failures and a smoother messaging setup[1][2][3][4].

Additional benefits include:

  • More stable and reliable messaging, especially under spotty signal conditions.
  • Better media quality and service flexibility enabling richer communication experiences.
  • Enhanced file transfer security, spam reporting, and deep link support to modernize the RCS ecosystem.
  • Builds on previous end-to-end encryption features introduced in Universal Profile 3.0[3].

It's worth noting that the GSMA, not Google, initially introduced the RCS standard without end-to-end encryption. However, Google was the first to implement end-to-end encryption for RCS as a feature later[1][4]. Apple, in its integration of RCS on iPhones with Android devices, did not initially include end-to-end encryption[1].

The update also brings in new mechanisms for connecting RCS clients to operator services, making the RCS experience more seamless and reliable, especially in challenging coverage zones[1].

The update was announced by Tom van Pelt via the GSMA blog[2]. This upgrade is a continuation of the GSMA's efforts to improve the RCS standard, building upon the advancements made in v3.0. The GSMA's Universal Profile 3.1 update sets a stronger foundation for widespread RCS adoption by addressing longstanding challenges of audio clarity and connectivity reliability, empowering operators and developers to offer more engaging and robust messaging services globally[1][2].

[1] GSMA (2022). GSMA announces Universal Profile v3.1 for RCS services [2] GSMA (2022). Tom van Pelt: Building on the success of RCS in 2022 and beyond [3] GSMA (2021). GSMA launches Universal Profile for RCS v3.0 [4] TechCrunch (2021). Google adds end-to-end encryption to RCS messaging, but it's not available on Android yet

Data-and-cloud-computing technologies play a crucial role in the implementation and enhancement of the Universal Profile v3.1 update for RCS services, as it involves advanced compression techniques like xHE-AAC audio codec for higher-quality voice notes and audio clips [3][4]. This update also integrates closely with OS-level push notification services, demonstrating the importance of technology in improving RCS connectivity and reducing battery drain [1][2][3][4].

Read also:

    Latest