GSMA Advanced Messaging – RCS Universal Profile

Rich Communication Services (RCS) has been around for a couple of years without any major success (actually the number of RCS deployments has been declining). There were many reasons. From the technical point of view it was caused by very ambitious design at the times where there was a little experience with IP-based technologies in operators’ networks, along with the lack of good enough RCS clients. That has changed and in the November 2016 we got a new standard called RCS Universal Profile (RCS UP) created by GSMA.

It contains a set of Advanced Calling and Messaging features and agreed enablers – such as application to person messaging (chatbots) and conversational commerce (the seamless integration of transactions and messaging).

messaging-web-banner-650x320

To date 46 Mobile Network Operators and 12 manufacturers, covering a subscriber base of 4.7 billion people globally, have committed to supporting a single, standard implementation of the Universal Profile. That means that the profile will be implemented by most smartphones makers (similarly as in the case of VoLTE/VoWifi). They are Alcatel, ASUS, General Mobile, HTC, Intex Technologies, Lava International Ltd., LG Electronics, Lenovo/Motorola, Samsung Electronics and ZTE,. Moreover the standard is supported by mobile OS providers Google and Microsoft. Therefore the devices will be equipped (as from Q2 2017) with a built-in Advanced Messaging app, so consumers will be able to text, chat and share media without the need to download any special application. (However a usage of app is also an option supported by RCS Universal Profile.)

Update: We have got the first smartphone with RCS UP support – more here

It is worthwhile to mention that Google is playing an important role because it bought Jibe – one of a few useful RCS clients, and has developed a universal Android client based on the GSMA RCS UP. Google along with Sprint in US and Rogers in Canada announced that they’re rolling out with their RCS Messaging based on RCS UP at the end of the last year. Besides, as GSMA says, Google is offering a carrier hosted service for Operators to launch and manage Advanced Messaging services to their customers without deploying the RCS or even IMS infrastructure.

Continue reading

News: 2016 Summary

The year 2016 was in many ways the year of VoLTE and VoWifi. IP-based communication became an established standard and mobile operators are getting confident with the new technology. GSMA has just published the numbers for 2016.

IP deployments in 2016

IP deployments in 2016

One thing is the official announcement that an operator offers VoLTE/VoWifi, the other thing how much compliant it is and what services are really supported. We can see a big progress here as well. More and more operators are trying to interwork over IP, provide IP-based emergency services, IP voice and video mail, enhanced voice quality such as HD or EVS, support real multi-device feature or self-provisioning.

Operators are also trying to offer web-based access using WebRTC, which seems to be a must for enterprise integration and communication in context. RCS was not that popular in 2016, operators mostly use IPSMGW to provide SMS over IP. But seems it starts to change as can’t rely on SMS forever.

If the 2016 was about calling over IP, the 2017 can be about M2M (again). In the last 12 months we have seen many Sigfox and LoRaWAN deployments, and finally we got the log-awaited ‘so-called’ specification NB-IoT and we could see its first deployment. I planned to write a post about LPWANs, but then I read and article written by Nick Hunn, which is much better than anything I could put together: nb-iot is dead long live nb-iot.

Although we made a big step forward it doesn’t make our life any easier. In 2017 we can expect Artificial Intelligence everywhere, but I doubt it will allow us to relax either 🙂 Happy new year everyone!

 

News: Finally 4G?

IMS was designed in a very a general way. As a service network which is access independent, supports multiple identities and it is very expensive to implement. Sometimes less is more – at least in the beginning. That’s also why we have the VoLTE – a minimum IMS profile which reduces the scope into something manageable and more practical.

As the VoLTE has been around for a couple of years already and works fine, the early adopters are looking for more – HD Voice, EVS, WebRTC and other technologies. Recently T-Mobile USA (DIGITS) and AT&T (NumberSync) announced their solutions for multi-device feature. Not all the features are always successful or truly practical – but this time I’d think more operators will follow. Btw. with IoT to come I wonder when exactly we will see a first virtual entity (agent) seamlessly moving from one devices to another 🙂

News: Telco Monitoring

I always enjoy to visit telcos’ monitoring centres. One feels like to be in NASA. It’s a pity that mostly it is not allowed to take any pictures.

AT&T Monitoring

AT&T Monitoring

It is interesting that rarely there is just one vendor of this monitoring. Usually it is a mix of various applications, which inform about the most important KPIs and events. Often we can see open applications to be used. If you are working in support you probably know at least some of them – cacti, zabbix, nagios, observiumMRTG, munin, zenoss, etc. One of them is grafana.

Grafana

Grafana

I’ve recently seen a T1-operator monitoring based on Grafana. The nice thing about it is that it allows to include various data sources, analytics where we can easily combine charts with related events and it supports multi-tenancy. Just before Christmas we have got a new version 4.1 with a new alerting feature. The alert rules are easy to configure using existing graph panels and threshold levels can be set simply by dragging handles. The rules will continually be evaluated by grafana-server and notifications will be sent out when the rule conditions are met. Besides the altering there are many other improvements and enhancements.

Anyway whatever tool you use, happy NYE monitoring!

News: RCS Reborn?

There are mobile operators who have RCS in their network but practically no one really use it. The number of RCS deployments – in contrast to VoLTE or VoWifi is decreasing and more than once I’ve heard that RCS is a zombie. These days when it comes to texting over 4G we mostly still rely on the old good SMS, using IPSMGW. Of course, we can choose from plenty of OTT technologies as WeChat, WhatsApp, Line, etc. However SMS is still a must to have for all the mobile carriers, even though they are not making much money on it.

RCS standard is everything but simple and straightforward. The operators were that afraid, that they’ll become only connectivity providers that they created an omnipotent service which no one was able to implement. For many years we struggled during the integrations and to find a really working RCS client was close to impossible. One of the better clients was Jibe. Jibe was bought by Google the last year and many were wondering what is the Google up to..

Messanger

Messanger

Recently Google along with Sprint in US and Rogers in Canada announced that they’re rolling out with their RCS Messaging. More info in RCS Universal Profile post. Hard to predict how successful it will be this time, but chances are, we will see RCS around in 2017.

SCTP Introduction

When we talked about the Diameter protocol in Diameter Overview, we mentioned that it relies on transport level protocols – TCP or SCTP.

SIP and Diameter stacks

SIP and Diameter stacks

I guess most of people are familiar with TCP. But not everyone is familiar with SCTP protocol yet. And that’s a pity because the Stream Control Transmission Protocol (SCTP) was designed especially for telcos as TCP is burdened with some limitations. Let’s explore SCTP’s basic featurers today. Btw. we should remind that SCTP is a must also in legacy networks, because SCTP is a part of Sigtran stack (SS7 over IP).

SIP and Diameter in Wireshark

SIP and Diameter in Wireshark

And last but not least SCTP can also transport the SIP protocol (RFC 4168). It is not that common, but there are some operators benefiting from this option e.g. in case of  NNI.

Continue reading

Challenges of Automated Testing (for telcos)

Recently I have been asked for an advice regarding automated testing. I spent several years in R&D designing our test framework (for SMSC, MMSC, RCS, IPSMGW, ..), sometimes I felt like trying to break a wall, sometimes it was very rewarding (at least for me it is rewarding to find a bug 🙂 ). There are some lessons learnt I’ll remember for a long time. I’m afraid this post won’t be a short reading.

Fukushima Nuclear Power Plant

Continue reading