Professional Documents
Culture Documents
Media Power IPTV-Design Document
Media Power IPTV-Design Document
Contributors
The contributors to this document are noted here and may be contacted regarding any
changes or to discuss other aspects of the content.
Contact Information
Name
Organization
Email Address
Andre Mendes
Widevine
amendes@widewine.com
Karel Debrouwere
Scientific Atlanta
karel.debrouwere@sciatl.com
Kashif Rashid
Cisco Systems
krashid@cisco.com
Jim White
Jim.white@sciatl.com
Marco Bonomi
Minerva Networks
marcob@minervanetworks.com
Robert Giacomuzzi
Cisco/Scientific Atlanta
giacomr@cisco.com
Simone Arvigo
simone.arvigo@seachange.com
Venkataramanaiah R
Mannai
venkat@mannai.com.qa
Silju Pillai
Mannai
Silju.pillai@mannai.com.qa
Srihari Moningi
Mannai
Srihari.ramana@mannai.com.qa
Mannai
Jeby.mathew@mannai.com.qa
TPQ-GP55-DOC-0126
Version 0.7
Table of Contents
1. Introduction---------------------------------------------------------------------------------------- 5
2. Objective of this Project ------------------------------------------------------------------------- 5
3. Scope of Work (SoW) ----------------------------------------------------------------------------- 5
3.1 IPTV Logical Design -------------------------------------------------------------------------------------------- 6
TPQ-GP55-DOC-0126
Version 0.7
7. SeaChange ----------------------------------------------------------------------------------------- 44
7.1 Axiom Core Functions---------------------------------------------------------------------------------------- 45
7.2 VOD architecture: Axiom command centre and the VOD servers -------------------------------- 48
7.3 Features --------------------------------------------------------------------------------------------------------- 51
TPQ-GP55-DOC-0126
Version 0.7
1. Introduction
The purpose of this document is to provide a detailed design about the IPTV
implementation in Pearl Qatar Island, integrated with five various vendor components,
namely, Cisco, Scientific Atlanta, Minerva, Widevine, and SeaChange with a proven
ecosystem
1. Scientific Atlanta deals with the Head End System and IP STB
2. Minerva Networks deals with the Middleware
3. Widevine deals with Content Security (CAS)
4. SeaChange deals with Video on Demand (VoD)
This document details only the IPTV solution design. The design details that shall
support the IPTV solution will be provided in the Data Center and WAN Services Module
Detailed design document. The Network requirements for the IPTV solution are gathered
and documented in TPQ-GP55-DOC-0119 and hence is not discussed as well in this
document.
TPQ-GP55-DOC-0126
Version 0.7
Logical Diagram
A proven/tested ecosystem has been considered and built for the Pearl IPTV network.
The logical diagram for IPTV network is shown above. As per this diagram, the IPTV
Network is segregated into separate VLANs and discussed in the Networking Part of
IPTV.
TPQ-GP55-DOC-0126
Version 0.7
4. Scientific Atlanta
4.1 IPTV Head-End System Description
4.1.1 Sequential traffic flow from QSPK to IP Stream
1.
Receives L-band QPSK signal from Satellite using the Dishes installed at the
dish farm.
2.
LNBs connected to the dishes will convert these QSPK signal to IF and send to
Amplifiers for boosting the signal before splitting it and sending to multiple
devices.
3. IF splitters will split these signals to multiple IF feeds to feed IRD's, and to Pay
channel decoders using IF splitters and L-band test point.
4. The IRD will tune a particular transponder and pulls out the contents in ASI
format.
4.1
The ASI output from IRD goes to ASI splitter and further fed to main DCM
and redundant DCM.
4.1.1
DCM will further process the selected channel from the transponder to IP
format (MPEG2 transport) and send it to the distribution network.
4.2
4.2.1
DCM will process the selected channel from the transponder to IP format
and send it to the distribution network
5. Pay Channel decoder gets IF signal and is tuned to one channel according to the
smart card subscription from the channel provider, which is inserted in it.
5.1
Composite Video & analog audio signals from Pay Channel Decoders
goes to MPEG2 Encoder (D9022). And the ASI out of these is fed to
DCMs.
5.2
The DCM will process those selected channel from the pay channel
decoder fed through MPEG2 encoder to IP format and send it to the
distribution network.
TPQ-GP55-DOC-0126
Version 0.7
Satellite dish farm and 200 L Band signal feed for IPTV Head End system
2.
The Satellite dish farm consists of 6 dishes and will be located on the Roof top of the
BDC (Back up Data Centre). Three satellite dishes will receive and distribute L-Band
signals and for redundancy three more dishes shall serve as backup. Following are the
Satellites that are considered:
Hot Bird-13East,
Nile Sat 7 W.
The L-band feed from satellite Dish/LNB are fed to the Coaxial patch panel installed in
the standard rack located in BDC building data centre room. The equipment rack is
provided with Test Point for all the feeds, as well as TV monitor and DTH receiver to
monitor the live programs from each feed. To provide 200 L-Band feeds to IPTV head
end (12 Main feed + 12 Redundant feed) in the data centre room, we propose two 42 U
standard racks.
LNB: A low-noise block converter (LNB, for low-noise block, or sometimes LNC, for lownoise converter) The LNB is usually fixed on the satellite dish. As Microwave satellite
signals do not easily pass through walls, roofs or even glass windows, satellite antennas
are normally installed outdoors, and the signal needs to be passed indoors via cables.
The job of the LNB is to take a wide block (or band) of relatively high frequencies (Lband), amplify and convert them to similar signals carried at a much lower frequency
(called intermediate frequency or IF , frequency ranging from 950Mhz to 2150 Mhz).
Quattro universal LNB: A Quattro LNB has four fixed outputs and is used only in "head
end" I.F. distribution systems. The four outputs of the LNB are as follows.
Horizontal Polarization Low Band.
TPQ-GP55-DOC-0126
Version 0.7
The dielectric is surrounded by foil shield/s and/or copper braid/s which form the outer
conductor and also shield against electromagnetic interference (EMI). The outer
conductor/shield is encased in a PVC jacket. Most coaxial cables for video applications
have a nominal impedance of 75 ohms. Their differing electrical and physical
characteristics make it important to select the correct type of cable to suit the application.
All types of coax cables will lose signals. The extent of the loss will depend on the quality
of the cable. However, all coax cable will lose more signals at higher frequencies (2150
MHz+) than at lower frequencies (950 MHz).These losses are compensated by an IF
amplifier.
The L-band feed from satellite Dish/LNB ranging from 950 MHz to 2150 MHz with an
input signal level of -25dBm to -65dBm is fed to the coaxial patch panel. These virgin
signals are further splits and distributed to IRD and to Pay Channel decoders, with the
help of appropriate IF splitters. The required amount is 200 L-band signal feed carrying
different polarizations as per the required channel mapping.
TPQ-GP55-DOC-0126
Version 0.7
IF splitters:- A splitter is a small device that has one input (the 75 ohm load) and 2 or
more outputs, such as 2 ways, 3ways, 4 ways, 6way and 8 ways. Each ports driving a
separate 75ohm load. In TPQ, all these types of splitters as to attain the 200 nos of IF
signals.
Essentially they are transformers that split the power in the input signal to multiple
outputs, while maintaining the 75 ohm impedance. However, Every time you split an IF
signal with a splitter, you drastically decrease the signal's strength logic dictates that
splitting this signal in two with a "passive" device will result in two signals that each have-at most--half of the original signal's strength. To overcome these losses an IF amplifier
is used.
IF amplifier: - Boost the IF signal to get more mileage and compensate for the cable
loss in the distribution system. This is used to compensate for signal loss when the IF
signal is split into a number of IF signals (200 nos) by passive splitting. a set of two SAT
900 (IF amplifier), one set of main and another set is redundant amplifier. This design
ensures the availability of IF signal (950 MHz 2150 MHz) with relevant signal level that
ranges from -25dBm to -65dBm.
Three dishes are designed for redundant use, these dishes are tracked and tuned for the
same 3 satellites (Hot Bird-13East, Arab Sat-26 East & Nile Sat 7 W.) to ensure the
availability of IF signal always in case of failure from main dish feed..
The equipment rack is provided with Test Point for all the feeds, makes possible to
determine/ measure the signal level without interrupting the signal fed to the IRDs and
pay channel decoders.
A LCD monitors and a FTA satellite receiver (Free to Air) is provided and is connected
through a multi switch to monitor the programs from each satellite feed. (I.e. all the 12 IF
feed for Nilesat, Arabsat and Hotbird)
Multi switch: -
different dishes through one cable. This is done via a multiswitch distribution system.
DiSEqC (Digital Satellite Equipment Control) pronounced "Die-Sec" is a special
communication protocol for use between a satellite receiver and a device such as a
multi-dish switch or a small dish antenna rotor. A DiSEqC switch is a device which
TPQ-GP55-DOC-0126
Version 0.7
10
enables you to connect multiple LNBs to a satellite receiver; here this is used as we
have 3 dishes.
All the testing points and monitoring equipments will be in one rack, and second rack will
be equipped with all passive and active equipments for distributing the L-band signals,
carrying different polarizations as per the required channel mapping.
TPQ-GP55-DOC-0126
Version 0.7
11
Multiplexing
In Multiplexing part, we will have the Digital Content Manager which receives the
ASI input from the D9850s/D9022s and the Output for the DCMs will be Gigabit,
which will be fed to the Aggregation switch in the network. To ensure
redundancy, the DCMs will be connected in 1+1 configuration, ensuring
maximum availability for the system. There will be a total of 14 DCMs, which will
be used in the project with 7 as main DCMs and 7 as back up.
Monitoring
TPQ-GP55-DOC-0126
Version 0.7
12
For monitoring, we will be using the Copernicus MKIV server together with the
ROSA system software. For the complete system monitoring, interfacing will be
done with the 10/100 Base-T IP network and all the systems will be further
connected to the monitoring server with the help of the Ethernet cables.
The Acquisition/Encoding network will receive the input from the L-Band splitting
network for the satellite signal. At the Acquisition phase, we will be having 200
ASI outputs, which will further be going to the DCM. These 200 ASI outputs will
be in 1+1 configuration. This will provide fall-back procedure for the DCM in case
of any downtime on the primary/backup DCMs. These 200 streams have been
calculated as follows:
Out of the 100 D9850s in total, 70 D9850s Receivers are used for the
Free to Air channels. The output from these D9850s will be connected
directly to the DCM and there will be no interfacing equipment in between.
As every D9850 has only one ASI out and our requirement is to connect
the ASI inputs to both the primary and redundant DCM, we will be using
70 ASI splitters, which will be providing us with 70x2 ASI streams. The
output from the ASI splitters will be connected to both the main and
Backup DCM.
The output for the remaining 30 D9850s will be going into the Galaxy
System rack containing the Indus MKII Descrambler Cards. As the INDUS
has 2 outputs per card so both these outputs can be used for connecting
to the main and redundant DCMs. For these 30 Encrypted streams as we
will have 1+1 output for every stream so no ASI splitting is required and
we will have 30x2 ASI streams into the DCM.
The D9022s which will be used for the digital encoding will be having a
1+1 output at each output. So, one will be connected to the main DCM
and the other will be connected to the secondary DCM. This will give as
100x2 ASI streams at the input of the DCM.
All the 14 DCMs receive the 200x2 ASI input. Main DCM 1-6 will be having 30 ASI
inputs and the DCM 7 will be having only 20 ASI inputs. The same scheme will be used
for the redundant DCMs also.
TPQ-GP55-DOC-0126
Version 0.7
13
The detailed connectivity for all the HE components will further be given in the Rack
Layout and System Cabling diagrams. Refer TPQ-ITV-GP55-DWG-0001 drawing for
more details.
Designed to deliver high quality MPEG-2 video and supports ASI output. Control of the
encoder is supported via the front panel interface, an on-board web browser, and open
communication protocol (SNMP).
Features:
TPQ-GP55-DOC-0126
Version 0.7
14
Description:
The PowerVu Model D9850 receiver is designed for satellite content distribution
applications requiring 4:2:0 video decoding.
Features:
This has four L-band inputs and PowerVU conditional access. With Aspect ratio
conversion (4:3, 16:9 and 14:9) and Active Format Descriptor (AFD) control.
Specifications:
MPEG-2/ DVB Compatible system with Quadrature Phase Shift Keying (QPSK)
De-modulation process.
Variable Field Error Correction (FEC) (1/2, 2/3, 3/4, 5/6 OR 7/8).
Tuner frequency range 950MHz up to 2150MHz using C-band and KU-band
satellites frequencies. Input impedance of 75 and symbol rate range of 1.0 to
45Msymbols/s. RS-232 asynchronous data at rates up to 38.4 kb/s data outputs.
Power consumption of 50Wmax and voltage range of 100V to 240V AC.
Interface up to 40 ASI interfaces ports ( 30 ASI ports per ASI I/O card, having 3available
card slots and 1 card slot dedicated for IPTV ).Re-multiplexing of services and content
routing from any input to any output port.Transrating of single SD ( Standard Digital ) and
HD ( High Definition ) programs, ( recompression to lower bit rates.10 Gbps internal
processing throughput with 8 Gbps of I/O capability.
Specifications:
TPQ-GP55-DOC-0126
Version 0.7
15
This has 10 ports per ASI interface card, each port configurable as input and
output. Using a BNC-type connector and an output impedance of 75. Bit rate of
0.1 to 213 Mbps.
Power consumption of 250W fully loaded. Nominal input voltage 100-240V AC.
clear digital signal. The removable Common Interface Module allows the
operator to easily select the required CA System for transport stream descrambler.
Features:
Simultaneous descrambling of the selected services in a transport stream. Bays for two
DVB Common Interface Conditional Access Modules ( CAMs ). Descrambling capacity of
services depends on the used CAMS. It also supports all Common Interface compliant
CA systems. Provide ASI input and Dual ASI output and selection of Programs or
individual PIDs.
Specifications:
Having 1 main input and 2 outputs. Using a BNC-type of connector (on panel
board). Input impedance of 75. Maximum bit rate of 56Mbps. Having 2 CI slots
using PCMCIA connector type I and II.
Nominal power consumption is 10W.
The Galaxy Sub-Rack Concept is housed in a 3ru unit designed with a common power
and communication interface to all inserted modules. Physically consist of an interfacing
rear-card module and the application front-card module. The power supply can be either
single or dual power supply with a free choice of AC and DC.
Features:
TPQ-GP55-DOC-0126
Version 0.7
16
Holds up to 12 application cards of the Galaxy family in only 3RU. Multiple powering
possibilities with or without redundancy. Hot-swappable, easy accessible application
cards and low power consumption.
Specifications:
A relay contact type which has 2x25-pins female Sub D connector. Maximum
load of 60 VDC, 250 Ma, 5 VA. Communication port of 9-pins male Sub D
connector type RS-485. Capable of transmission speed up to 19200 bit/s. Power
supply of 100 to 240 VAC 10%, 47 TO 65 Hz.
TPQ-GP55-DOC-0126
Version 0.7
17
In the case of a Pearl network, which is built from the beginning, taking into account all
three major services (internet, voice and video), and the bandwidth engineering is
considered.
channels
via
encoders
for
TPQ-GP55-DOC-0126
Version 0.7
18
4.4.2 Scenarios
Satellite program is received and decoded by Scientific Atlantas D9850 Free to Air and
PowerKey Transport-Stream QPSK Satellite Receiver and fed directly to Scientific Atlantas
Digital Content Managers ASI Board.
2.
Satellite program is received and decoded by Scientific Atlantas D9850 Free to Air and
PowerKey Transport-Stream QPSK Satellite Receiver and fed to Scientific Atlantas
INDUS MKII Transport-Stream Descrambler. Each Descrambler Board carries two
CAM slots that can be used in cascade for multiple Descrambling capabilities of the
TPQ-GP55-DOC-0126
Version 0.7
19
same Transport Stream. The descrambled (Clear) Stream will be fed to Scientific Atlantas
Digital Content Managers ASI Board.
3. Proprietary Services like Show Time, Orbit, and ART and others where no
descrambling CAMs are available
Satellite Program will be received and decoded by the Service Providers Proprietary
Satellite Decoder. Since the output of the Decoder is Audio Video Base Band (AV BB), the
signal need to be re-encoded and converted to MPEG-2 Single Transport Stream
(STPS). This task will be performed by Scientific Atlantas D9022 MPEG-2 Encoder
and the encoded STPS will be fed to Scientific Atlantas Digital Content Managers ASI
Board.
Sl.No
1
DCM Pair
IP Address (Slot-1/Slot-2)
VLAN
Channels
192.168.120.101-104
120
FTA
192.168.120.105-108
120
FTA
192.168.120.109-112
120
FTA
192.168.120.113-116
120
FTA
192.168.120.117-120
120
FTA
192.168.120.121-124
120
FTA
192.168.125.101-104
125
Premium 1
192.168.125.105-108
125
Premium 1
192.168.125.109-112
125
Premium 1
192.168.125.113-116
125
Premium 1
192.168.127.101-104
127
Premium 2
192.168.127.105-108
127
Premium 2
192.168.127.109-112
127
Premium 2
192.168.127.113-116
127
Premium 2
TPQ-GP55-DOC-0126
Version 0.7
20
If the
TPQ-GP55-DOC-0126
Version 0.7
21
IPP430MC:
Same as IPP330 above, except that MPEG-2 HD is not supported (only MPEG-4 is
recommended for HD content for DVR models)
Includes fanless 160GB hard disk drive for DVR services, supports DVR trick mode,
speeds 2x, 15x, 50x and 300x
TPQ-GP55-DOC-0126
Version 0.7
22
5. Minnerwa Networks
This section of the document is an introduction to iTV Managers features, terms, and concepts.
Its meant to act as a primer for iTV Manager Administrators.
iTVManager 3.2 is a scalable enterprise solution that manages the distribution of video, television
and other data services over an IP Network. iTVManager offers true Video on Demand (VOD),
live television, and complete web integration. As the cornerstone of the IP television headend,
iTVManager is a scalable, interactive television management suite.
iTVManager is comprised of two major components:
1. the server software or BackOffice and
2. the set top box software, the Think application.
The BackOffice suite of software includes:
Subscribers
Channels
Asset management
Billing
EPG (Electronic Programming Guide) Loader that manages the data that is ingested from
an EPG provider and sent to the Set-Top Boxes (STB)
VOD (Video On Demand) Delivery System (VODDS) module that talks to VOD content
providers to automatically deliver to iTVManager the most up-to-date VOD assets
The Think application presents a UI that lets the television viewer see the EPG, purchase VOD
programs, search for titles in the EPG and VOD catalog and schedule recordings and program
TPQ-GP55-DOC-0126
Version 0.7
23
reminders. The user interface, through customization can be used to present custom branding
and layout design.
Services
Broadcast
Video
VOD streaming.
RTSP server for trick play functionality
(Pause, Fast Forward, Rewind).
VOD purchase.
VOD playback bookmarks.
Customer
Management
Invoice generation.
Flat-file "Billing Reports generation that can
be fed into the Telco's existing billing system
TPQ-GP55-DOC-0126
Version 0.7
24
Conditional
Access
Client UI and
Graphics
Other
Features
TPQ-GP55-DOC-0126
Version 0.7
25
The diagram below shows a high level picture of an iTVManager 3.2 system, with components
supplied by Minerva in green and components supplied by 3rd Parties in pink.
Mozilla
Think
X
Porting API (MvLayer)
Porting Library, HW/ OS
CA Client
STB
3rd Party
Admin
GUI
Admin
GUI
Admin
Applets
dhcp
VOD
CA
Servers Servers
Broadcast
Catcher
Network
Backoffice
SDK
(Enhydra)
Admin
Servlets
(Enhydra)
STB Unicast
Services
(Configuration,
Packages,
Transactions,
VOD, Apps)
Content
STB
Multicast
(Skins,
Apps,
Listings)
VOD
CA
Connector
APIs
Integration Managers
(VOD, CA, VODDS
etc.)
Server Middleware
Billing
Reports
EPG
Ingest
Guide Listing
Services
Data
TPQ-GP55-DOC-0126
Version 0.7
26
TPQ-GP55-DOC-0126
Version 0.7
27
Java Platform, Enterprise Edition (Java EE) is the industry standard for developing portable,
robust, scalable and secure server-side Java applications.
5.2.5 Swift MQ JMS
SwiftMQ is a micro-kernel based J(ava)M(essage)S(ystem) enterprise messaging platform.
There is some messaging within the server using JMS; however, this is not extensive and is only
used for some selected situations.
5.2.6 Swing
Swing is a GUI toolkit for Java. It is one part of the Java Foundation Classes. Swing includes
graphical user interface widgets such as text boxes, buttons, split-panes and tables. The admin
GUI is written using Swing.
TPQ-GP55-DOC-0126
Version 0.7
28
Coming to the software components of the platform and their distribution across multiple physical
machines, below is a description of the various supported implementations.
On the headend side, iTVManager is a suite of applications and processes that are spread across
two servers:
TPQ-GP55-DOC-0126
Version 0.7
29
TPQ-GP55-DOC-0126
Version 0.7
30
The Database Application is installed on one server, the BackOffice Server, the Application
Server, and the Boot Server installed on the second server. In this document, well focus on each
of these servers.
TPQ-GP55-DOC-0126
Version 0.7
31
These two BackOffice access methodsConsole and APIperform the same functions. For
example, if you want to add a customer, you can either open the BackOffice Consoles Customer
page, press the Add button, and fill out the customers data, or you can invoke the SDKs
md_cst.add_customer() procedure. The difference between the two methods is mostly a matter of
scale: If youre adding thousands of customers at a time, youll want to automate the task by
writing a script that invokes BackOffice SDK procedures. On the other hand, if you just want to
change the address of a single user, youll want to use the BackOffice Console.
Implicit in this description is that the BackOffice is an administrative tool. Its meant to be used by
an iTV Manager administrator who needs to modify, augment, or fine-tune some aspects of the
system. Of course, since almost all iTV Manager data and state are stored in the Database, it
means that the other iTV Manager processes, including the Think application running on an STB,
need to access the Database...but they do not use the BackOffice for this; instead, they either talk
to the Database directly, or they use the Data Service applications.
(VODDS) and
the
Video Server
respectively, ingest VOD metadata into the Database and download and store actual VOD
content (i.e. movies) on the third-party Video Server (such as those provided by Entone or
TPQ-GP55-DOC-0126
Version 0.7
32
Bitband). Other Boot Server processes include the interfaces to the Emergency Alert System,
Caller ID, and the Conditional Access system.
In the diagram mentioned below, there are the communications between STB and Minerva during
the "steady status" which happens once the box has already booted up and keeps the fingerpath
with the middleware through the Announcement Stream configurable (happening after the RunTime Stream and the Boot Stream).
All the main actions, such as Purchase Transactions, Edit Favorites, Play VOD, etc., are
summarized and described in the section User Actions, where there are all the choices that the
customer has from the STB side and that require a communication with the Application Server.
TPQ-GP55-DOC-0126
Version 0.7
33
6. Widevine Technologies
Widevine Cypher is the first and only session-based content security system for interactive TV
(IPTV).
TPQ-GP55-DOC-0126
Version 0.7
34
Widevine Cypher can protect content on set top boxes, personal computers, personal video
recorders, home media gateways, mobile phones, and a wide range of consumer electronics
devices.
The following details the benefits of utilizing Widevine and particularly Widevine Cypher to protect
Pearl Qatars video deployment.
broadcast television in the cable and satellite domain. The systems function by protecting content
only during transport. Decryption occurs when the transport session was terminated upon
reaching a set top box. This security architecture ensures that content is secured in transit from a
head-end to a receiving device. Since legacy CAS technologies only protect content during
transport, content stored on devices to accommodate for VOD is stored in the clear and is
susceptible to theft.
DRM systems are designed to protect files and are historically targeted at industries where
ownership is transferred, yet the rights of the new 'owner' to copy or distribute content are
restricted. DRM is based on the idea that there will be an electronic certificate of ownership
issued to someone or something as proof that rights have been assigned. Ideally, the certificate
cannot be copied or tampered and the item the certificate protects can only be used in
conjunction with the certificate itself. If the certificate is not present, the item cannot be used.
Encryption is applied at the file level at the point of encoding and rights are maintained by the
content copyright holder (i.e. a movie may be distributed as a file amongst many users but its
DRM properties require the owner to be paid each time a unique user attempts to watch the
movie).
DRM deals with the concept of ownership and is only appropriate for file-based content. CAS is
aimed more at permitting access without transfer of ownership and is only appropriate for
broadcasted content. However, todays IPTV deployments require a combination of both
technologies. Content is distributed in its digital file format and needs persistent encryption, while
TPQ-GP55-DOC-0126
Version 0.7
35
the access control is essential to the operators revenue. Therefore, the content security solution
of choice would ideally deliver both in a single system, giving service operators the ability to
deliver media in the most efficient, profitable manner.
Widevine has designed a comprehensive system that together delivers CAS to secure linear
broadcast and DRM to secure VOD. The value to Pearl Qatar is that a Widevine Cypher system
can be used for securing multimedia content delivered in multiple formats, platforms and content
types, including linear broadcast, VOD, streamed media, file downloads and progressive
downloads (Widevine owns the patent on encrypted session-based video delivery).
This multiplatform, multiformat approach ensures that IPTV Design in Pearl Qatar has the
flexibility to choose the video delivery infrastructure, video formats and consumer devices that
meet business and technical requirements today and tomorrow.
TPQ-GP55-DOC-0126
Version 0.7
36
is known as the digital hole the place content resides after decryption and before being display
on the screen.
Widevine developed digital copy protection to secure untrusted platforms such as PC-based
consumer devices that are highly vulnerable to piracy. This solution detects and responds to the
many utilities used to record and redistribute media. The technology is also applicable for
protecting STB and PVR devices.
TPQ-GP55-DOC-0126
Version 0.7
37
distribution but allows VOD ingestion, trick-play file creation and digital ad/program insertion in the
encrypted content. With application-level encryption, only the video data are encrypted, leaving
key aspects of the video stream such as the control and metadata in the clear. This method
enables trick-play ingestion and file creation without having to decrypt the entire video stream,
preventing points of vulnerability in the network. (Please see Figure 2 below for an illustration of
application-level encryption). Application-level encryption further enables persistent protection of
linear content (i.e. broadcast channels) even when used with network personal video recorder
(nPVR) and client (cPVR) applications.
TPQ-GP55-DOC-0126
Version 0.7
38
The below sections detail the components comprising the Widevine Cypher solution.
TPQ-GP55-DOC-0126
Version 0.7
39
to Widevine Secure devices, including set top boxes, PVRs, PCs, portable media players and
mobile devices.
Cypher CA is scalable to an unlimited number of subscribers and offers hot failover options
should an operator require them.
In order to dimension correctly, one must only dimension the bandwidth needed for the planned
live TV channels.
The following table has been used to determine the bandwidth, and thus Cypher Broadcast
dimensioning for PEARL-QATAR.
TPQ-GP55-DOC-0126
Version 0.7
40
Compression / Definition
MPEG 2
MPEG 4
Standard Definition
5 Mbits/s
3 Mbits/s
High Definition
18 Mbits/s
9 Mbits/s
Total of 720Mbits/sec initial bandwidth needed with an extra bandwidth of 180 Mbits/s
available. 1 Cypher Broadcast Unit is needed.
Cypher VOD encrypts/decrypts at 1 min/Gb for AES and 8:30/Gb for DVB-CSA
TPQ-GP55-DOC-0126
Version 0.7
41
(TVN
Entertainment customer source: Widevine encrypts a 2-hour movie in 1.5 min / NDS
encrypts a 2-hour movie in 45 minutes )
Knowing that, for security reasons, it is advised to re-encrypt a part (or all) of the VOD assets
every X time period, once the VOD vault becomes rather big, it may be interesting to expand the
Cypher VOD rack with 1 or 2 more units.
e.g. 1000 VOD assets at each 2 hours/asset = 1000 X max 4 min = 4.000 min of total VOD asset
re-encryption time
TPQ-GP55-DOC-0126
Version 0.7
42
Enhanced logging of Cypher appliances and Virtual SmartCard clients enables quick
troubleshooting of the entire system, including the status of entitlements delivery, device
connections, health status, service delivery and more.
A well defined MIB and the support for SNMP v1 and v2 traps offer the capability to seamlessly
integrate and communicate with third-party management systems. Designed for use in a
centralized head-end or in remote locations, access can be made using a secure, SSL-based
connection, so operators always know whats happening with Widevine Cypher.
Cypher Management Console allows users to:
View logs
TPQ-GP55-DOC-0126
Version 0.7
43
7. SeaChange
The features that will be employed at present and in the future for the Sea Change Video Server
for Pearl Qatar Project are described below.
Video Server will be integrated with other partner products (Minerva, Widewine, Scientific
Atlanta) to generate a modern and powerful IPTV system.
Figure 4: Cypher Management Console offers
at a glance status of the Cypher system.
Some important
features
supported
and in continuous implementation by SeaChange developers
Convenient
stop light
graphics
identify
Figure 5: Service status and SNMP traps can be
actionable
responses
are given
below:for fast troubleshooting.
easily accessed anytime, anywhere, reducing time to
identifying and troubleshooting potential problems.
SeaChange MediaServer
HDS Series
represents
1,600
hours of
VOD
programming
to
can reliably
thousands
offer
more
of subscribers from a
single cluster . The flexibility of the MediaServer HDS is marked by its ability to
provide a range of output types
including Gigabit
Ethernet for IP
transport
of MPEG, On2,
Contents Provider: SeaChange can provide a proposal for contents and metadata
production.
Asset Manager for VOD contents: Contents stored can be streamed free of charge
TPQ-GP55-DOC-0126
Version 0.7
44
or with price. Contents can be rented with various prices, mode and durations.
Multiuser Access: It is to possible to create more than one user on a single STB.
This can manage parental control and other types of filters.
from
the
same
user
can
be
viewed
on
different platforms (for example one content can be purchased on pc and viewed
in part on TV and other parts on 3G phone).
SeaChange
Video
Server
can
record
wide
for execution
at
be
specific
obtained
interactively,
or
can be
TPQ-GP55-DOC-0126
Version 0.7
45
automated.
Connection Manager Service mediates client requests, establishing the shortest path
between the client and the requested content. The Connection Manager ensures that content is
streamed from the closest storage location to the requesting client, delivering a high quality user
experience with minimal latency.
Asset Manager Service manages the life cycle of content stored on the system. Content is
typically created, uploaded, activated, deactivated and deleted by the Asset Manager in
accordance with business rules supplied by the operator. The Asset Manager provides full
visibility into the location and state of managed content through a browser-based GUI. recording
Service captures broadcast programs and publishes them as VOD content. The Recording
Service can simultaneously ingest multiple channels of broadcast content inreal time, which are
then distributed to the VOD system for on-demand viewing by clients. Capabilities in this service
include playout while record, enabling time-shifted viewing of broadcast TV programs.
Axiom fault-resiliency
To help ensure that the services running on the Command Center server remain available in the
event of server failure, the Command Center servers are typically paired together in twin-server
Command Center clusters running Legato Corporations CoStandbyServer. It provides a bidirectional failover mechanism so that, in the event of a hardware failure on one Command
Center cluster member, the surviving member (in addition to maintaining its own tasks)
automatically assumes the tasks and the identity of the failed member, permitting continuing
operation of all ITV services ordinarily provided by both members of the cluster.
To support the CoStandbyServer failover mechanism, both servers in a Command Center cluster
maintain identical Windows registry configurations and identical file sets on their respective C:\
drives. Each server maintains a dedicated, high-speed Ethernet link to its partner over which the
instances of CoStandbyServer software running on each machine communicate with each other
and continuously monitor the operational status of both systems.
Automatic Failover
When CoStandbyServer detects and verifies that a failure has occurred on one of the cluster
members, it automatically moves (fails over) the failed servers failover group from its home
server location to its away server location on the surviving cluster member which, in addition to
TPQ-GP55-DOC-0126
Version 0.7
46
its own tasks, begins performing the tasks of its failed companion.
For example, if a failure is detected on Server 1, the CoStandbyServer software running on
Server 2 automatically moves the Server 1 failover group to Server 2 and (while continuing to
process its own tasks) starts the services listed in Server 1s failover group on Server 2. After the
transplanted services have successfully completed their startup sequences, all services
ordinarily provided by both cluster members will be running on Server 2.
TPQ-GP55-DOC-0126
Version 0.7
47
drives, Windows Server 2003 operating software, high performance processors, switched PCI
buses and a range of standard network interfaces optimized for video.
7.2 VOD architecture: Axiom command centre and the VOD servers
AXIOM is the command center for the VOD: it has all the logic and the processes to ingest
content, generates trick files, propagate the content to the video server, order a VOD
server to start streaming etc.
The Video Server is the streamer: it sends the VOD mpeg stream to the STB.
The network communication conducted between and among the various component systems and
services that make up the VOD system is logically divided into the following categories:
TPQ-GP55-DOC-0126
Version 0.7
48
The management network, also called Server-to-Server network is used for the servers
to communicate together. The communication on the server-to-server network consists
primarily of control data, messaging, and other high-priority communication. So the
servers will be manageable from this interface usually using Mstsc (Microsoft Remote
Desktop).
The Propagation network is the network where the content is copied from the ingestion
point to the media cluster. In our example, this is very simplistic: it is just a link between
the Axiom command center and the video server. In a live deployment, this dedicated
network is key because the assets (mpeg files) are transiting through it.
The Client-to-Server network is where all the traffic between the set top boxes and the
servers flow. For the VOD, it mainly consists in control commands (DSMCC) and web
traffic generated by TV business when the subscriber browses the VOD catalog.
The Video Delivery network is the network that connects the media source (VOD server)
and the cable set-top boxes used by the subscriber. The first part between the VOD server
and the QAM is also called transport network (usually based on IP). The second part
between the QAM and the set top box is RF: the set top box tunes into an RF channel to
see the VOD. Please note that the VOD server REQUIRES an active Gigabit Ethernet
(GigE) port to stream.
TPQ-GP55-DOC-0126
Version 0.7
49
TPQ-GP55-DOC-0126
Version 0.7
50
The ADI service provides a method to transfer assets from a content provider to multiple Asset
Management Systems.
7.3 Features
Receives assets imported from a Content Receiver
Stores asset information (metadata) in the VOD master Directory database
Lets you configure VOD site information, such as the addresses of the Directory Server,
details about automatic import, and information about content providers
Lets you add and modify information about VOD applications (for example, Movies on
Demand)
Allows you to manually add or modify all asset information
TPQ-GP55-DOC-0126
Version 0.7
51
Allows you to pre-encrypt content files and generate the corresponding trick files
Allow you to view the status of assets within the VOD System, and manage the assets
(modify, remove, or move)
Lets you monitor work queues
Lets you inspect assets that have been loaded into the VOD MediaClusters, but have not
yet been made available to subscribers
AMPLUS workstation allows copying files to local sites
TPQ-GP55-DOC-0126
Version 0.7
52
TPQ-GP55-DOC-0126
Version 0.7
53
Sl.#
VLAN Name
Description
IP Range
Mask
NMS
Management
192.168.5.0
255.255.255.0
120
FTA
192.168.120.0 255.255.255.0
121
IPTVSBEN
192.168.121.0 255.255.255.0
122
IPTVSFEN
192.168.122.0 255.255.255.0
123
VoDDN
192.168.123.0 255.255.255.0
124
VoDPN
192.168.124.0 255.255.255.0
125
Premium1
Pay channels
192.168.125.0 255.255.255.0
126
Premium1 Enc
192.168.126.0 255.255.255.0
10
127
Premium2
Pay Channels
192.168.127.0 255.255.255.0
11
128
Premium2 Enc
192.168.128.0 255.255.255.0
Sl.#
1
2
3
4
5
6
7
Subnet Purpose
IPTV - DCM pair 1
IPTV - DCM pair 2
IPTV - DCM pair 3
IPTV - DCM pair 4
IPTV - DCM pair 5
IPTV - DCM pair 6
IPTV - DCM pair 7
TPQ-GP55-DOC-0126
Subnet
239.232.1.0
239.232.2.0
239.232.3.0
239.232.4.0
239.232.5.0
239.232.6.0
239.232.7.0
Version 0.7
Mask
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
255.255.0.0
54
BDC-DC2
Services
Server Name
Server IP address
DC-Switch Name
DC-Switch Port
IPTV
DCM1-1
192.168.120.101
BDC-DC2
Gi 10/25
IPTV
DCM2-1
192.168.120.109
BDC-DC2
Gi 10/26
IPTV
DCM3-1
192.168.120.117
BDC-DC2
Gi 10/27
IPTV
DCM4-1
192.168.125.101
BDC-DC2
Gi 10/28
IPTV
DCM5-1
192.168.125.109
BDC-DC2
Gi 11/29
IPTV
DCM6-1
192.168.127.101
BDC-DC2
Gi 11/30
IPTV
DCM7-1
192.168.127.109
BDC-DC2
Gi 11/31
IPTV
DCM1-2
192.168.120.105
BDC-DC2
Gi 10/32
IPTV
DCM2-2
192.168.120.113
BDC-DC2
Gi 10/33
IPTV
DCM3-2
192.168.120.121
BDC-DC2
Gi 10/34
IPTV
DCM4-2
192.168.125.105
BDC-DC2
Gi 10/35
IPTV
DCM5-2
192.168.125.113
BDC-DC2
Gi 10/36
IPTV
DCM6-2
192.168.127.105
BDC-DC2
Gi 10/37
IPTV
DCM7-2
192.168.127.113
BDC-DC2
Gi 10/38
SA
BDC-DC4
Service
Server Name
Server IP address
DC-Switch Name
DC-Switch Port
Axiom -AM
192.168.121.63
BDC-DC4
Gi 10/26
192.168.124.63
BDC-DC4
Gi 11/4
192.168.121.64
BDC-DC4
Gi 10/27
192.168.124.64
BDC-DC4
Gi 11/5
192.168.122.64
BDC-DC4
Gi 11/6
192.168.121.65
BDC-DC4
Gi 10/28
192.168.124.65
BDC-DC4
Gi 11/7
192.168.122.65
BDC-DC4
Gi 11/8
192.168.121.71
BDC-DC4
Gi10/29
192.168.123.71
BDC-DC4
Gi11/9
192.168.124.71
BDC-DC4
Gi 11/10
192.168.121.72
BDC-DC4
Gi 10/30
192.168.123.72
BDC-DC4
Gi11/11
192.168.124.72
BDC-DC4
Gi 11/12
192.168.121.73
BDC-DC4
Gi 10/31
192.168.123.73
BDC-DC4
Gi11/13
192.168.124.73
BDC-DC4
Gi 11/14
192.168.121.74
BDC-DC4
Gi 10/32
192.168.123.74
BDC-DC4
Gi11/15
192.168.124.74
BDC-DC4
Gi 11/16
Seachange
IPTV
IPTV
Axiom -DS
IPTV
IPTV
IPTV
IPTV
IPTV
Axiom -DS
Seachange Srv1
Seachange Srv2
Seachange Srv3
Seachange Srv4
SA
IPTV
DCM1-1
192.168.120.103
BDC-DC4
Gi 10/19
IPTV
DCM2-1
192.168.120.111
BDC-DC4
Gi 10/20
DCM3-1
192.168.120.119
BDC-DC4
Gi 10/21
TPQ-GP55-DOC-0126
Version 0.7
55
IPTV
DCM4-1
192.168.125.103
BDC-DC4
Gi 10/22
IPTV
DCM5-1
192.168.125.111
IPTV
Gi 10/23
IPTV
DCM6-1
192.168.127.103
BDC-DC4
Gi 10/24
IPTV
DCM7-1
192.168.127.111
BDC-DC4
Gi 10/25
IPTV
DCM1-2
192.168.120.107
BDC-DC4
Gi 10/12
IPTV
DCM2-2
192.168.120.115
BDC-DC4
Gi 10/13
IPTV
DCM3-2
192.168.120.123
BDC-DC4
Gi 10/14
IPTV
DCM4-2
192.168.125.107
BDC-DC4
Gi 10/15
IPTV
DCM5-2
192.168.125.115
BDC-DC4
Gi 10/16
IPTV
DCM6-2
192.168.127.107
BDC-DC4
Gi 10/17
IPTV
DCM7-2
192.168.127.115
BDC-DC4
Gi 10/18
IPTV
Boot/App/Admin Srv
192.168.121.11
BDC-DC4
Gi 10/33
192.168.123.11
BDC-DC4
Gi 10/34
IPTV
DB
192.168.121.12
BDC-DC4
Gi 10/35
192.168.121.47
BDC-DC4
Gi 10/36
192.168.125.47
BDC-DC4
Gi 10/37
192.168.126.47
BDC-DC4
Gi 10/38
192.168.121.46
BDC-DC4
Gi 10/39
192.168.127.46
BDC-DC4
Gi 10/40
192.168.128.46
BDC-DC4
Gi 10/41
192.168.121.45
BDC-DC4
Gi 10/42
192.168.124.45
BDC-DC4
Gi 11/17
192.168.121.42
BDC-DC4
Gi 10/43
192.168.122.42
BDC-DC4
Gi 10/44
Minerva
WideVine
IPTV
IPTV
IPTV
IPTV
IPTV
192.168.121.43
BDC-DC4
Gi 10/45
IPTV
192.168.121.44
BDC-DC4
Gi 10/46
192.168.122.44
BDC-DC4
Gi 10/47
With respect to the Networking part for IPTV, detail designing is described in the Data Center
Design Documentation, TPQ-GP55-DOC-0143 .
TPQ-GP55-DOC-0126
Version 0.7
56
9. Booting Process
STB initial process of proceeding for Booting up with various vendor components and their
respective versions
Sequential steps and the procedure for Booting Process and Renting an Asset
Flow during the Booting Process of STB
1. From the STB to the DHCP Server
The STB asks a DHCP address from the Data Center server
The STB with the assigned IP starts the client/communications with the CAS
The STB starts the communications with iTVManager to gather the info needed
TPQ-GP55-DOC-0126
Version 0.7
57
3. From the CAS to the STB and from the STB to the VOD server
10. References
1.
2.
3.
4.
5.
TPQ-GP55-DOC-0126
Version 0.7
58