Get Adobe Flash player
OTT Monitoring Keeping it simple and useful by Rolf Ollmar, BRIDGE Technologies O TT is generally understood to mean a technique where the transmission of video to the subscriber is based on the same underlying methods as those currently being used to serve out web pages on the internet today. The Over-the-Top name refers to the potential of this technology for bypassing existing traditional television distribution methods by piggybacking itself on top of existing broadband internet connections. The key difference to traditional television delivery is the provision for a two-way IP pipe to the subscriber. The two-way pipe uses TCP to handle data loss through packet re-transmission. Further protocol layers allow for a seamless change of gears between different bandwidth profiles in order to adapt to the average bandwidth capacity of the broadband link. For this reason OTT is also often referred to as adaptive bitrate streaming. Over-the-Top delivery promises television quality across un-managed internet infrastructure. Whether this matches the quality we have come to expect from our television depends on how well the service is implemented and monitored from studio to subscriber. There is currently a large amount of activity in the OTT area. In many ways it is comparable to the way digital television and MPEG was prior to its standardization in the early 90s. 66 | TV-BAY MAGAZINE Four major flavours of OTT technology are being applied as of today: • Microsoft™ Smoothstream(tm) • Apple™ HLS • Adobe™ HDS/Flash • MPEG-DASH The three first ones are vendor driven implementations whereas the fourth is an MPEG standardisation effort. The OTT infrastructure A typical OTT architecture consists of an ingress head-end, multi-profile encoders, segmentation servers, the content delivery networks (CDNs), local ISP’s where the end-customers get their broadband connection from and finally the end user viewing the service from devices such as tablets, OTT-enabled set-top boxes or smart phones. To uphold television delivery quality some form of monitoring throughout this chain is recommended. Natural monitoring points are where the areas of economic responsibility meet - the demarcation points. Below is a list of suitable monitoring points in any OTT deployment: • Output of Origin / segmentation server • At strategic points throughout the CDN • At ingress points to local ISP’s subscribing to the OTT service • Inside end client devices • Active OTT monitoring The implementation below shows how OTT can be actively monitored at any point in the delivery chain. The screenshot shows two feeds being actively tested by emulating the behaviour of a player client attempting to access the material. The first content piece is called VoD and is stored content on a server. This could be recorded television or movies. The format is Apple HLS in this particular case. The second service being monitored is a live OTT feed called Olympics LIVE. In this particular case the format is Adobe HDS. The stream has been expanded for more measurement details. The only large difference between Live and Stored content is that in the live case the sequence numbers of the chunks are updating whereas for the stored material the sequence numbers are static. The only configuration needed to enable monitoring is the URL of the OTT stream. In addition an alarm template is defined to say when to alarm in case of faults. A chunk is downloaded for each available profile for the service. The download duration is checked against a configurable percentage value. For example - if the download duration is larger than 80% of the actual (real time) chunk duration of 10 seconds then an alarm is generated. The colour of the measurement is green, yellow or orange depending on the severity of the alarm. The last 120 minutes of measurements are logged as colour bars in order to easily visualise profile health over time. We see from the picture that the largest profile of 3.66Mbps is currently experiencing download issues. We