NewNet Nimblevox Messaging VoltDelta

Archive for October, 2015

Google is not about to launch an iMessage clone

Posted on: October 27th, 2015 by Mobile Communications

Google has deployed a range of services such as Google Talk, Google Voice and Google Hangouts, yet they have not deployed an iMessage-like service despite having the technology and application framework to do so for years.  Those convinced that Google would ultimately deploy their own messaging solution fail to understand the very nature of Android’s open source origins.  There are several license agreements related to Android.  The first is for the base operating system, and the second is for Google Mobile Services.

The Android Operating System components are governed by the Apache License Version 2.0.  Google Mobile Services are under a completely “separate license” from Google, and comprise Gmail, Chrome, Google+, Google Maps, YouTube, Google Docs, Google Translate and Waze.   Google Mobile Services are proprietary and not open source. These applications must be licensed from Google by device makers, and can only be shipped on devices which meet its compatibility guidelines and other requirements.

If Google were to include an iMessage like service in the  Android operating system, device manufacturers (at the demand of their operator customers) would simply strip the service out of their customer specific builds, as permitted under the Apache license — something they cannot do with Apple’s products.  Under Android’s Open Source Platform policy, manufacturers and operators have complete discretion regarding the services and features that are included in their commercial implementations of Android.  Samsung’s version of Android has a different dialer and messaging app when compared to other vendors such as Sony’s version of Android.

Another option is for Google to incorporate the Jibe Client & back-end components into Google Hangouts and make it a part of the Google Mobile Services.  If they do this, they will risk completely alienating the operators and other industry players who have already filed petitions and complaints to the US Federal Trade Commission, EU Competition bureau , Canadian Competition Bureau, Indian Competition Commission, Russian Competition Bureau that Google manipulates their power and dominance within the market to push their Services to be used by phone manufacturers.  They might do this by asking these manufacturers to sign a contract stating that they must pre-install specific Google Mobile Services, in order to get the latest version of the open-source software ‘Android’.

Fundamentally let’s not read more into the press release than is there.  Google’s announcement was that it was including RCS in Android, not Google Mobile Services.

RCS is a fundamental technology change related to more than just ‘messaging’……… it is not an App. The technology needs to be properly integrated with the operating system to function as intended. It is my assessment that they will include RCS in the Android Operating System, and not as a function in Google Hangouts. This announcement gives operators an easy way to ‘opt-in’ to deploying RCS features.

Brent Newsome- Vice President Business Development

Google acquires Jibe and its impact on RCS

Posted on: October 19th, 2015 by Mobile Communications

The announcement that Google is Committing to RCS support in Android and acquiring Jibe Mobile in the process has sparked a huge industry debate, both online and in industry working groups. The Rich Communications Services (RCS) standard has been considered as something to be avoided in the last 18 months by many in the telco world despite the fact that quietly……… in telco labs, hundreds of engineering teams, vendors and device manufacturers are moving towards the all IP mobile network of the future. This is a network where VoLTE, Voice over WiFi, SMS over IP, IP Messaging and WebRTC all co-exist because of the IMS & RCS standards. Exactly what was envisioned from the standard’s very inception!

RCS is, and always has been, a set of detailed technical standards which can be used to launch innovative new service offerings by operators. The first example given by technical working groups in 2010 was as an IP-based messaging platform to replace SMS. This use case was created as the technical members of the various working groups could foresee the rise of what we now call OTT competition.

In the process of advocating for this solution, RCS became relegated as a messaging solution, which wasn’t nearly as feature complete as what the OTTs were rolling out. In fact, RCS is part of a broad standards initiative which includes technologies such as Voice over LTE, Voice over WiFi, SMS over IP, Video over LTE, WebRTC, Operator APIs and IP messaging. Furthermore it is extensible and can include many of the monetization features of OTT’s such as sticker stores.

‘RCS’ is not a product it’s a set of technical standards that are building blocks for future services, and as such ‘RCS’ is far from just messaging.

The shock that Google, which recently launched its innovative Google Fi Service, would throw its lot in with the RCS crowd, seems to have been too much for some traditional naysers who have now become illogical in their commentary. It is more important than ever that the RCS ecosystem (operators, vendors, pundits) base their thinking on facts.

First and Foremost let’s remember that “Don’t be evil” was the formal corporate motto of Google, more recently replaced by “Do the right thing.” Google has a long tradition of working with Telco’s, and not against them. With Google Fi they are demonstrating that they want to be a model for innovative services from which the Telco world can learn. By including RCS in Android, (this is what Google is doing) – indicates that they are working with their Telco partners, not against them. Their words support this as well… just read their press release: “We’re excited to team up with mobile operators, device makers and the rest of the Android ecosystem to support RCS standards and help accelerate their deployment in a more consistent way”.

Brent Newsome- Vice President Business Development