I like statistics. Sometimes it can be misleading or data can be hard to interpret. But it can help us when we struggle to see the forest for the trees.
The last two years the IP-based mobile technologies were booming. If you are working with 4G networks you know it well. This year however the number of new deployments decreased significantly (Sep 2017, source GSMA).
Well, there can be many reasons for that. Rather than guessing, let’s have a fun and take a look on how popular are some telco topics on Google in the last 3 years.
If you are interested in the WebRTC technology, you probably know what pain it was to define Mandatory To Implement (MTI) codecs. But compromise is not always the best solution. So the key players decided to form an Alliance for Open Media – an open-source project that plans to develop next-generation media formats, codecs and technologies. The Alliance’s founding members are Amazon, Cisco, Google, Intel Corporation, Microsoft, Mozilla and Netflix. The Alliance wants to come with an open-source common standard for media sharing. It is nice to see Google, Microsoft and Mozilla to work together on web standards 🙂 Along with the HTML5 this can push forward the development of real-time communication apps a lot. On the other hand there are still many other players, many different interests, so let’s wait for the first real outcomes.
I admit this news slipped my attention. I noticed only that Edge does support the getUserMedia and then I got a bit lost in what is the WebRTC 1.0, what 1.1 and what is the Next Version (NV) 🙂 There are also other news, e.g. Google introduced a new open-source tool for developers which tests network conditions, and if camera and microphone work properly. If you missed these information as I did, you can find a nice summary with many other updates in the following video
It is a part of nearly each IMS deployment. Session Border Controller. As the name indicates it sits on a border. A border between two networks. SBC is a controller so it controls all the traffic (both signalling and media) going through. So far so good. But what is really the SBC? What standards we can find? Where is some detail description of the SBC internal architecture? Sure, there are plenty of specs which are somehow describing the role of SBC. The basic one describing SBC is the RFC 5853.
The meaning of SBC has changed over the last 15 years significantly. We can say that SBCs are solving the problems which are not addressed by other IMS elements – problems with multiple access networks (e.g. IPv4 and IPv6, SIP normalization, VPNs..), security issues (DOS attacks, topology hiding, ..), legislative issues (emergency calls, legal intercept, interworking,..), media related problems (QoS, transcoding, media security,..). And of course, the number of these problems and issues which need to be solved is increasing. So what is the SBC now? As an SBC we understand a network element which is implementing following functionalities:
Malicious attacks such as a denial-of-service attack (DoS) or distributed DoS
Toll fraud via rogue media streams
Malformed packet protection
Encryption of signaling (via TLS and IPSec) and media (SRTP)