{"id":16086,"date":"2019-10-30T12:21:31","date_gmt":"2019-10-30T11:21:31","guid":{"rendered":"https:\/\/www.sms77.io\/?p=16086"},"modified":"2023-02-16T14:07:11","modified_gmt":"2023-02-16T13:07:11","slug":"rcs-will-probably-become-more-complicated-again","status":"publish","type":"post","link":"https:\/\/www.seven.io\/en\/blog\/rcs-will-probably-become-more-complicated-again\/","title":{"rendered":"RCS will probably become more complicated again"},"content":{"rendered":"<section class=\"l-section wpb_row height_small\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row via_flex valign_top type_default stacking_default\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p><strong>Recently I <a href=\"https:\/\/seven.io\/en\/blog\/rcs-sms-meets-messenger-app\/\" rel=\"noopener\">reported in an article<\/a> about the current state of affairs regarding RCS (Rich Communication Services). I also mentioned how confused and disorganized it was in the past. And I have expressed the suspicion that the (no longer quite) new communication standard will get a much-needed unified organization through Google&#8217;s announcement to push the implementation itself now.\u00a0<\/strong><\/p>\n<p>Now, however, things became much more complicated, <a href=\"https:\/\/www.theverge.com\/2019\/10\/25\/20931699\/android-messaging-ccmi-rcs-mess-isis-google-fiascotastrophe\" rel=\"noopener\">according to the Verge<\/a> (among others). The <strong>four largest network operators<\/strong> in the US &#8211; AT&amp;T, T-Mobile, Verizon and Sprint &#8211; announced on 25 October 2019 that they are working on their <strong>own messaging app<\/strong> to use the standard. What&#8217;s particularly remarkable is that despite the statement that they are cooperating with Google on the implementation, Google&#8217;s reaction <strong>speaks a different language<\/strong>. Judging by the company&#8217;s significantly delayed response, the announcement came as much of a surprise to them as it did to the public.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section><section class=\"l-section wpb_row height_small\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row via_flex valign_top type_default stacking_default\"><div class=\"vc_col-sm-8 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><h2>Google apparently knew nothing about it<\/h2>\n<p>I have to explain that Google is the company that has been trying to push the implementation of RCS over the last few years. Initially, this task was <strong>assigned to the network operators<\/strong>. However, their efforts were so <strong>unmotivated and poorly organised<\/strong> that Google announced in June that it would now continue the project itself, independently of the network operators. To this end, a <strong>pilot project<\/strong> was launched in France and Great Britain, with other countries to follow &#8221; over the course of the year&#8221;. Then things became quiet, but the assumption was that Google would continue to work behind the scenes to make RCS available to a broader public as quickly as possible.<\/p>\n<p>And now the announcement of the American network operators. The initiative is a joint venture called the Cross Carrier Messaging Initiative (CCMI).\u00a0What has not been explained is why Google&#8217;s efforts are now <strong>being undermined<\/strong>. One assumption would be that network operators are <strong>afraid to relinquish control<\/strong> of RCS to Google. Also, CCMI did not explain how it might look with <strong>end-to-end encryption<\/strong> or whether Apple is now willing to work on <strong>compatibility for iMessage<\/strong>. These questions are indeed a <strong>general problem<\/strong> with RCS, but with a clear answer on them CCMI could have positioned itself as a trailblazer.<\/p>\n<h2>Back to square one<\/h2>\n<p>In short, just a few months after it looked like RCS could finally get the thoughtful and <strong>well-planned implementation<\/strong> it always needed, the four major network operators in the US have decided to make the map much more complicated again. Will we ever see RCS as a new communication standard, a <strong>successor to SMS<\/strong>? That remains to be seen.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"vc_col-sm-4 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"w-image align_center meta_simple\"><div class=\"w-image-h\"><img decoding=\"async\" width=\"371\" height=\"750\" src=\"https:\/\/www.seven.io\/wp-content\/uploads\/2019\/09\/RCS_Image_WIP_2-5.jpg\" class=\"attachment-full size-full\" alt=\"RCS sending of railway ticket\" loading=\"lazy\" srcset=\"https:\/\/www.seven.io\/wp-content\/uploads\/2019\/09\/RCS_Image_WIP_2-5.jpg 371w, https:\/\/www.seven.io\/wp-content\/uploads\/2019\/09\/RCS_Image_WIP_2-5-148x300.jpg 148w, https:\/\/www.seven.io\/wp-content\/uploads\/2019\/09\/RCS_Image_WIP_2-5-198x400.jpg 198w\" sizes=\"auto, (max-width: 371px) 100vw, 371px\" \/><\/div><div class=\"w-image-meta\"><div class=\"w-image-title\">RCS_Image_WIP_2<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section><section class=\"l-section wpb_row height_small\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row via_flex valign_top type_default stacking_default\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p style=\"text-align: center;\"><em>Header image by NicoElNino, image in phone by Halfpoint, both via iStock.com, edited.<\/em><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"Recently I reported in an article about the current state of affairs regarding RCS (Rich Communication Services). I also mentioned how confused and disorganized it was in the past. And I have expressed the suspicion that the (no longer quite) new communication standard will get a much-needed unified organization through Google&#8217;s announcement to push the...","protected":false},"author":1,"featured_media":16093,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[5,404],"tags":[271,5537,269],"class_list":["post-16086","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-updates","category-tech-trends","tag-rcs-en","tag-rich-business-messaging","tag-sms-en"],"_links":{"self":[{"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/posts\/16086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/comments?post=16086"}],"version-history":[{"count":6,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/posts\/16086\/revisions"}],"predecessor-version":[{"id":88238,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/posts\/16086\/revisions\/88238"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/media\/16093"}],"wp:attachment":[{"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/media?parent=16086"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/categories?post=16086"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.seven.io\/en\/wp-json\/wp\/v2\/tags?post=16086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}