Huawei IPTV Solution

Technical Proposal
Huawei Tech. Co., Ltd.

All Rights Reserved By Huawei.

 Table of Contents

1 Executive Summary.........................................................................................................................4
1.1 Huawei unique value to OPERATOR.............................................................................4
1.2 Benefit of work with Huawei.............................................................................................4
2 Scope of Work..................................................................................................................................6
2.1 Overview..............................................................................................................................6
2.2 Precondition of delivery.....................................................................................................6
2.3 Solution architecture and work boundary......................................................................7
2.4 Service deploy suggestion................................................................................................9
3 Huawei IPTV Services...................................................................................................................11
3.1 Overview............................................................................................................................11
3.2 Live TV (BTV)....................................................................................................................11
3.3 VOD....................................................................................................................................13
3.4 Start Again (TSTV)...........................................................................................................15
3.5 Catch-up TV (TVOD).......................................................................................................15
3.6 cPVR..................................................................................................................................16
3.7 PC Client............................................................................................................................17
3.8 Advertising.........................................................................................................................18
3.9 Multi-Profile.......................................................................................................................19
3.10 PIP....................................................................................................................................19
3.11 OTT...................................................................................................................................20
3.12 Recommend Engine......................................................................................................22
3.13 Search Engine................................................................................................................23
3.14 FCC..................................................................................................................................23
4 Huawei IPTV Solution...................................................................................................................24
4.1 Architecture overview......................................................................................................24
4.2 Highlights of Huawei IPTV solution...............................................................................26
4.3 Middleware System..........................................................................................................27
4.4 VoD System(Huawei MDN)............................................................................................33
4.5 Element Management System(I2000)..........................................................................37
4.6 Terminal Management System......................................................................................40
4.7 OTT Integration Solution.................................................................................................43
4.8 Service Quality Management Solution.........................................................................44
4.9 Backup and Restore Solution........................................................................................47
4.10 Digital Home Solution....................................................................................................51
4.11 Proposed Hardware.......................................................................................................53
5 Integration with existing system....................................................................................................55
5.1 The integration with existing CRM/Billing.....................................................................55
5.2 The integration with existing IMS CORE......................................................................56
5.3 The integration with existing upper-layer OSS............................................................57
6 IP Network Requirements..............................................................................................................59
6.1 Bearer Network Requirements......................................................................................59
7 Acronyms and Abbreviations.........................................................................................................61
 1 Executive Summary

“This chapter is very important, and must be customized by product manager of this
project based on this project background information and competition strategy.”
Huawei is pleased to submit this proposal to XXX for End-to-end IPTV solution. The
objective of this proposal is to introduce our capabilities, as well as our proposed IPTV
solution to XXX for the planned IPTV ecosystem. Huawei will provide the best integrated
solution and services for this project.
Huawei is an IPTV and IP network expert and possesses rich and practice
experiences in IPTV system integration. Huawei has the depth of capabilities, proven
experience and commitment to assist XXX to ensure the End-to-end IPTV system
successful launch.

1.1 Huawei unique value to XXX

 Most complete IPTV solutions with Huawei own developed products. Huge
installed base and strong growing TV subscriber numbers even in the long
term ensures ongoing innovative TV values features from Huawei.
 Huawei as No1 in fixed network has clear commitment to fixed network and
mobile networks, i.e. Huawei is the long term strategic key player with broad
portfolio in fixed and mobile networks.
 Broad digital home portfolio which enables another growth segment for
converged and fixed network operators.

1.2 Benefit of work with Huawei

Good telecom business understanding and experience allows Huawei to be a true
business partner with XXX and a Prime Contractor in complex multi-vendor deployment
and integration projects.
1. Mature system and fully match with XXX requirements to enable quick
deployment
a) Huawei is the vendor who has launched IPTV solution.
b) Huawei solution almost matches all the key requirements of RFP.
c) Huawei would like to customize an innovation EPG for XXX based on
understanding of OPERATOR TV customers’ look & feel.
2. Huawei owns complete hybrid XXX solution
a) Huawei is ongoing heavily investing in development of own TV products which
enables Huawei to deploy very competitive TV solution today and in future on
standard roadmap, and re-act very agile on new market opportunities and be
most committed to project customization needs.
3. Strong project delivery experience in complex Telco solution including IPTV
system.
a) Huawei has local project team dedicated for XXX IPTV project plus resource
such as sub-contractors, logistics.
b) Huawei has rich IPTV integration experiences which were proven in Guangdong
Telecom (more than 1M subscribers), UAE Etisalat, Saudi STC, Telekom
Malaysia, and Morocco Telecom IPTV project.

And also Huawei IPTV solution leverages cost-effective technology, open

architecture, easy operation and easy maintenance, smoothly evolution to help
carrier reduce the CAPEX and OPEX. The specific key points are shown as below:

1． Transforming the business model from traditional one-time equipment business to

Revenue Share business model, Huawei is willing to realize a Win-Win partner
relationship with XXX and help XXX reduce the CAPEX and OPEX.
2． Customization to quick response and delivery to accelerate positive.
3． Self-provisioning solution, with Zero touch, reduces OPEX.
4． Advantaged CDN technology and suitable local storage to save up to 80% bandwidth
of IP backbone.
5． Easy maintenance solution to save OPEX and CAPEX
1) End-to-end built-in Service Quality Management (SQM) solution to reduce
CAPEX & OPEX of monitoring & customer support.
2) Huawei unified network management solution, automatically routine check
(iCheck) tools and automatically signaling tracing (iTrace) tools enable operators
work efficiency to reduce the OPEX.
6． Huawei is leading SDP solution provider who is awarded Best Service Delivery
Platform in Barcelona, February 16, 2010. Huawei IPTV platform is based on SDP
architecture and can be easily integrated into Telcos existing SDP structure which
enables rich value added service introduction in a most efficient way
7． Huawei IPTV can seamlessly evolve to IMS architecture. And so far, Huawei IPTV
platform has integrated with Huawei IMS core to offer blended innovation service.
 2 Scope of Work

2.1 Overview
This chapter summarized the project scope for Huawei recommended IPTV solution
according to XXX requirements and needs.
The scope of work is based on standard integration interfaces and assumptions
further described in technical proposal. Any aspect of the customer’s environment that
may offer variation in the scope will require to discussing between XXX and Huawei to
decide on whether it is in or out of the work scope.
It is possible that XXX can ask for additional requirements out of this scope, and
based on the negotiation between XXX and Huawei, Huawei will update a new
suggestion and quotation to XXX.

2.2 Precondition of delivery

The proposed solution is based on the functional and dimensioning requirements
from XXX in the RFP document which have been understood by Huawei.
Our aim of this chapter is to provide XXX with a detail description about how and
what the precondition and considerations while designing the IPTV platform for XXX.
The following assumptions/considerations have been made when designing the
system:
1) All the IP bearer network equipments such as DNS/DHCP, Access Network,
BRAS, Core Network, AAA, and so on will be provided by XXX.
2) In the home network, the Home Gateway will be provided by XXX and match
the TV service requirements.
3) The IP bearer network can comply with the requirement of VOD service via IP.
That means the bearer network benchmark is:
 Maximum network delay: 400 ms;
 Maximum jitter: 50 ms;
 Maximum packet loss ratio: 1/1000
4) XXX provides the power supply system for platform, and assumes the power
supply is DC.
5) All of the equipment room and air conditions and other system will be provided
by XXX.
6) The Rack or cabinet which is used for the equipment excluded in Huawei
 quotation will be provided by XXX.
7) Huawei will offer the Ethernet switches and necessary firewalls which are used
for internal connection in Huawei IPTV platform.
More detailed Scope of Work, Please refer to the responsibility matrix.

2.3 Solution architecture and work boundary

The following figure is the high-level description to describe the work boundary
between Huawei IPTV platform and XXX existing system. The emphasis components are
provided by Huawei and strong partners. The other component will be provided by XXX,
including CRM/Billing, OSS, ACS, CAS, DNS/DHCP server, AAA, IP core network, metro
network, access network, head-end, STB, Home GW, and PC.

Figure 2-1 work boundary

Components Partners Remarks and Description
Headend GV The head-end system is responsible for the production of live
programs in the IPTV system.
Middleware Huawei The Media Entertainment Middleware (hereinafter named MEM)
is a core component of IPTV solution and can integrates with the
CMS, CRM/Billing, VOD Server, and other components in a fast
way.
VOD Server Huawei The Media Delivery Network (MDN) act as the VOD Server in
HUAWEI IPTV system. It distributes and stores media content.
The MDN dynamically routes content requests of subscribers and
provides subscribers with streaming services.
CA System Verimatrix Huawei proposed reusing the Verimatrix CA system to provide
the per-integrated solution.
Advertisement Huawei Through the IPTV Ad Platform, advertisement agencies and
platform advertisers can easily present advertisements to promote different
types of products on different advertisement presentation
platforms, such as EPG, VOD, Target Ads, and so on
Report system Huawei The iWeb report system can collect data from the data sources of
the IPTV system and collect statistics to provide accurate and
statistics reports.
SQM Huawei Huawei IPTV SQM (Service Quality Management) support
embedded probe which can deploy with the media server or STB
provided by Huawei to reduce the TCO. Meanwhile, Huawei
SQM solution can also support independent probe deployment to
monitor IP bear network equipment provided by Huawei or other
vendors.
EMS Huawei iManager 2000 (I2000) EMS is the device management platform,
provides the functions such as managing topology, faults,
performance, and configuration, and monitoring hosts, and also
can integrate with existing OSS system.
TMS Huawei As the management of IPTV STBs that supports the TR069
protocol, the terminal management system (TMS) follows the
B/S structure.
OTT Enabler Huawei The Huawei OTT enabler is based on Mashup technologies. The
(mashup based) Mashup engine is going to get metadata and video entry (which
can be configurable by the admin) about internet content from
ISPs’ platform.
Network Huawei Huawei propose S93 Series and S53 series switch for IPTV
Equipment internal connection.
STB Huawei Huawei Proposed EC2108S and EC2118S.

2.4 Service deploy suggestion

The following is the brief scenario and simple description of the proposed services in
different phases, Magyar Telekom can check with the suggestion. In addition, Huawei will
provide standard, open and well documented interfaces for integration with existing CRM,
billing, OSS and ACS. In order to reduce the time-to-market, the interactive EPG
template and sample will also be provided. Any modification could be discussed with
Huawei, and Huawei will update the project plan and commercial offer based on the
discussion conclusion between XXX and Huawei.

Description Remark
Phase I Lab environment The Bidder shall provide opportunity for
at Bidder Customer staff to test and evaluate the
main features of the proposed system.

Phase II Pilot test at The Bidder shall provide pilot system at

Customer T0 + 4 Customer site as a proof of concept. The
pilot shall start with a restricted service set
agreed between Customer and Bidder.
The Bidder shall specify in the offer which
services are available in pilot and what are
the prerequisites on Customer side.
The pilot test shall start from T0 +3
months.

Friendly user test The Bidder shall support phased launch of

the new system. The phase 1 will be
defined as friendly user test with
approximately 100 users.
The FUT shall start T0 +6 months.
Full commercial The Bidder shall provide the turnkey
launch system ready for full commercial launch
T0 +7 months.

S/N Services Phase Phase Roadmap Quotation Remark

Customer facing services
1 Live TV
2 VOD
3 TSTV
4 Catch up TV
5 cPVR
6 PC client
7 Advertising
Integrate with existing system
8 Integrate with
CRM/Billing
9 Integrate with OSS
HUAWEI Recommend Feature in this project
10 Multi-profile(Account)
11 Bookmark
12 PIP
I II
X Quoted
X Quoted
X Quoted
X Quoted
X Quoted
X Not
Quoted
X Quoted
X Quoted
X Quoted
X Quoted
X Quoted
X Quoted
13 Forward error correction X Quoted
14 Re-Transmission X Quoted
Optional Feature in this project
15 OTT X Optional
16 Recommend engine X Optional
17 Search engine X Optional
18 Fast channel change X Optional

3 Huawei IPTV Services

3.1 Overview
There are certain enhanced IPTV services that have gained traction over the last
couple of years. Some of these services have been simply replicated from the legacy TV
services, while some are IPTV specific. However in order to effectively compete with the
legacy pay-TV providers it is incumbent to replicate all the enhanced features that
subscribers currently enjoy. These include Live TV, VOD, TSTV, TVOD, interactive
services (such as advertising, OTT, search engine, etc), multi-profile, some limited TV
commerce experience etc.

3.2 Live TV (BTV)

3.2.1 Definition
The operator can create and publish live TV services.
End users can browse EPG and select a channel to watch. If the channel has not
been ordered, they can preview the channel for a short time (configurable). However, in a
day the end user can preview it only once.
End users can also watch a channel by press the channel number or up and down
navigation on the remote control.
End users can view the channels classified as follows:
1. All channels
2. Subscribed channels
3. All favorite channels
4. ~ 13. Self defined favorite channel name (For example, My Favorite Sports)
Middleware should support self-defined favorite channel list.
The channel browsing should be limited to the selected category.
Middleware should support displaying audio channel and video channel separately.
There are three options: audio and video, audio only, video only. For the first option,
audio channels will be displayed on the top the channel list. For last two options, just
audio/video channels will be displayed. Regarding display orders, first ordered by the
type, audio or video, then by the channel numbers, from small number to big number.
Middleware should support multiple subtitles. When a live TV channel contains
multiple subtitles on streams, subscriber can be able to select preferred subtitle
language.
Middleware should support multi audio stream. When a live TV channel contains
multi-lingual audio streams, subscriber can be able to select preferred audio language.
Middleware should support both encrypted and unencrypted streams.
Middleware should support vertical display on BTV guide page. Channel list and
program list to each channel will be displayed vertically. The program guide contains live
TV program and catch up TV program.
The BTV channels can be defined into several packages with different prices. End
users can order the packages monthly through operator OSS/BSS in offline mode.
The BTV channels support to be ordered online for a month or 24 hours. When end
users watch an unsubscribed channel, there will be four options:
1. Order the package (monthly) to which this channel belongs. The package might
contain several other channels. If the channel belongs to several packages, there will be
a package list displayed for end users to select.
2. Order this channel for one month
3. Order this channel for 24 hours
The operator can define different prices for the options above. To each channel, it
has two prices, one is for a month, and the other is for 24 hours. To each package, it only
has the price for a month.
For charging the subscribers for BTV Services, CDR will be generated by IPTV
platform for the option number 3 above, operator BSS should support getting and
processing the CDR files form IPTV server. Regarding the option number 1 and 2,
operator should provide API development in BSS system if online mode should be
supported.
 Figure 1.1 The page of the Program Guide

3.3 VOD
3.3.1 Definition
The operator can publish VOD (Video on Demand) programs in the system.
End Users can play movies or TV series that interest them in the IPTV program
library.
Middleware should support trick play. (Trick play means end users can play, pause,
stop, fast rewind, fast forward and direct jump to a particular part of a movie. Speed: 2x
4x 8x 16x 32x.)
The IPTV system provides the chapter experience similar to the experience of using
a DVD player. That is, after a user selects a VOD, multiple chapters of the VOD are
displayed on the detailed information page of the VOD. The system can display a
maximum of nine chapters for a VOD. Then the user can choose to play from a specified
chapter. An end user can access the multi-chapter play page from the detailed
information page of a VOD. The multi-chapter page displays information such as posters
of chapters, start time, and chapter number in thumbnails. After clicking the start button of
a chapter, the VOD service will be started from the beginning of this chapter.
Middleware should support bookmark function. When end users set a bookmark to a
movie, they can start playing the program from the bookmark next time.
Middleware should support trailer. The trailer can be published and be bound with a
movie, end users can preview before watching the VOD.
Middleware should support favorite list. End users can add a movie to favorite list,
Middleware should support download function. End users can download the
downloadable VOD to local inner hard disk, if the volume of hard disk is not sufficient or
there is no inner hard disk, the message carrying the error information will be popped up.
End users can watch the VOD when downloading.
Middleware should support Free VOD feature. End users can watch these movies
freely on specified date without ordering. The operators can add/modify/delete the
parameters regarding the free VOD.
Middleware should support multiple subtitles. When a VOD contains multiple
subtitles on streams, subscriber can be able to select preferred subtitle language.
Middleware should support multi audio stream. When a VOD service contains multi-
lingual audio streams, subscriber can be able to select preferred audio language.
Middleware should support both encrypted and unencrypted VOD.
Middleware should support parental control. When the users’ parental control value
is lower than parental control value of VOD, the password are required to input for
protecting the children.
Middleware should support VOD PPV (Pay-Per-View). The rental period is 24 hours
which means pay for a movie once and watch the movie freely in 24 hours. After 24
hours, end user should pay again before watching the same movie. The default value of
rental period is 24 hours, and it can be configured up to 7 days.
For charging the subscriber for VOD services, CDR will be generated by IPTV
platform, operator BSS should support getting and processing the CDR files form IPTV
server. To Free VOD, the field of charge in CDR file will be empty or 0.

Figure 1.2 The page of the VOD

3.4 Start Again (TSTV)

3.4.1 Definition
When watching a Live TV program, end users can go back to picture they have just
missed. That is they can trick-play the live program. Pause and fast rewind function can
be used. When the program is behind the Live TV actual content, fast forward function
can be used to catch up the current Live TV stream.
Also End Users can be able to re-start a TV program which is already running/
started for some duration. When end users chose “Start Again”, the program playing will
go back to beginning of this program.
The length of time shift is 4 hours for every “Start Again/TSTV” channel.

Figure 1.3 The page of TSTV

3.5 Catch-up TV (TVOD)

3.5.1 Definition
After a live TV channel is distributed successfully, an operator can enable the catch-
up TV service on the channel.
TVOD: TV on-demand. It’s a kind of on-demand program service in IPTV.
The IPTV system records BTV programs in real time and stores the recorded
programs in files.
By selecting the TV program from the TV program list on the EPG, End users can
watch the programs that have been played recently. When watching TVOD programs,
End users can pause, fast rewind, and fast forward the TVOD programs.
The length of TVOD is 7 days of every channel.
If End users have ordered the channel, the TVOD belongs to this channel can be
watched freely.
End users can watch TVOD by PPV (Pay-Per-View) mode without ordering the
whole channel.
For charging the subscriber for TVOD Services, CDR will be generated by IPTV
platform, operator BSS should support getting and processing the CDR files form IPTV
server.

Figure 1.4 The page of TVOD playbill

3.6 cPVR
3.6.1 Definition
Channel can be recorded by End users into the Hard Disk Storage available within
the STB.
Middleware should support both encrypted and unencrypted streams for recording.
Schedule recording must also start when STB is in standby mode.
Middleware should support schedule recording (recording of future program). In case
of a failed schedule recording, middleware should display the failed info on the cPVR
management page.
There are four statuses to cPVR program: Completed, Recording, Scheduled, and
Failed.
End users can access and play recorded content on the management page. Also
End users can delete or clear the recorded content. Middleware should display the
duration of recorded content.
The recorded content can be watched immediately after recording.
The cPVR function is disabled when the corresponding channel isn’t ordered by the
end user.
The operation of recording will be terminated automatically when inner hard disk
space is full.
 Figure 1.5 The page of adding local record

3.7 PC Client
3.7.1 Definition
Middleware should support PC Client function.
PC Client is supposed to be the replacement of STB and TV Set.
The services supported by PC Client list as follow:
Encrypted VOD
Scrambled BTV
cPVR
PC Client software can be obtained both by downloading from operator webpage
and by CD and the PC Client version can be upgraded online

3.8 Advertising
3.8.1 Definition
System should support the following three types of advertisement:
1. Banner AD (EPG AD). Following is the sample.
 2. Scroll Message AD (By TVMS). Following is the sample.

3. BTV logo-AD. Following is the sample.

Different AD can be published to end users in different group or area.

Banner AD should support format: jpg.

BTV logo-AD should support format: jpg, gif.

Scroll Message should support both text and picture style.

Banner AD in PC client and WAP portal will be supported in Phase 3. Scroll
Message AD and BTV logo-AD will not be supported by PC client and WAP portal.

3.9 Multi-Profile
3.9.1 Definition
End users can set the default profile. If the system has set the default profile, and the
default profile does not have a password.
The master account can add, delete, and modify subaccount’s information and
channel/category permission.
 The master account can reset subaccount’s passwords as blank.
The master account can define the credit of a subaccount.
A subaccount can only modify its own basic information, including the icon, name,
supporting TVMS or not, introduction, and passwords
A subaccount cannot modify the credit or channel/category permission.
A subaccount can purchase the content based on the credit provided.
The maximum number of subaccounts is 4, that is altogether 5 accounts including
the master account.

Figure 1.6 The page of the Profile login

3.10 PIP
3.10.1 Definition
Middleware should support PIP feature.
When a channel is highlighted in the channel list, the EPG PIP screen (small
window) should display the video and audio of the channel at the same time.
All IPTV channel are supposed to contain PIP small stream.
The small channel should be unscrambled streams/non-encrypted streams.
End users can switch between the small screen channel and the big screen channel
through the remote control.
For a non-subscribed channel, the PIP small screen will display “unsubscribed”, and
users can preview the channel on the big screen for one time per day (the number of
preview times is configurable).
For the small screen channel, the channel number is displayed at the upper-right
corner.
 Figure 1.7 The page of the PIP

3.11 OTT
3.11.1 Definition
Middleware should support OTT (Over the Top) services. End users can browse and
play content from the following internet websites through STB.
YouTube
Yahoo News
Weather forecast
Picasa album
 Figure 1.8 The page of OTT homepage

Figure 1.9 The page of OTT newspaper

3.12 Recommend Engine

3.12.1 Definition
With rapid development of IPTV services, subscribers can receive more and more
TV programs. As a result of this development trend, subscribers are happy with the
increasing diverse TV programs. The subscribers, however, fail to quickly and accurately
locate their favorite programs among numerous programs due to the large amount of
program information and the small number of retrieving methods.
To solve the problem about "overload" of program information, Huawei IPTV solution
proposes and implements the personalized recommendation feature targeting TV
programs, which is, recommending to subscribers their favorite TV programs according
to their hobbies and preferences.
The principles of personalized recommendation are as follows:The personalized
recommendation engine searches for program information that matches with subscriber
models, and then recommends the program information to the subscribers. Alternatively,
it searches for subscriber groups in which subscribers have similar preference for
programs, and then recommends browsed program information to the subscribers in the
groups. Personalized recommendation is a service model in which program information is
actively pushed to subscribers who require it.

Figure 1.10 The page of Recommended

3.13 Search Engine

3.13.1 Definition
The search function will only support for searching content in the live program,
TVOD, and VOD, not included the Interactive contents.
End users can put in the keywords and set the search field of content, like
Title
Actors
 Genres
All (including the above three fields)
Middleware should support global search (TVOD, VOD, and Live Program).
Middleware should support English and Arabic language searching.

Figure 1.11 The page of the VOD Search

3.14 FCC
3.14.1 Definition
The FCC server provides the FCC function.
When a subscriber switches between live channels, the FCC server accelerates the
delivery of the cached media stream to the terminal to shorten the time for channel
switching.
FCC will take about 20% bandwidth consumption additionally. And about 5%
bandwidth added totally according to the concurrent subscriber visit in statistic.
After sending the request by STB, the arrival of first package of TV stream from FCC
server should be in 1s.
 4 Huawei IPTV Solution

4.1 Architecture overview

Huawei provide a complete end-to-end IPTV solution based on open architecture
which is easy to integrate with existing system. The key component includes Huawei
middleware, VOD platform, CMI, BMS, EMS, report server, backup and restore system,
CPE portal, OTT enabler, SQM (optional), recommendation engine (optional) and search
engine (optional). The high-level architecture of Huawei solution is shown as below:

Figure 1.12 High-level architecture of Huawei IPTV solution

The Huawei solution is a comprehensive end-to-end IPTV solution.
 As shown in figure 3-1, with the core Huawei IPTV middleware, the Huawei offered
solution is not only easy integration with existing system to support hybrid IPTV
solution, multiple operator scenario, but also support to seamlessly integration with
existing IMS system to provide rich blended service.
 Self-made VOD server support comprehensive service that can help carrier win the
market based on the enhanced TV service. The services involve Live TV, VOD, PVR,
 TSTV, Catch up TV, download and progressive download.
 An attractive CPE portal (EPG) is a key component for offering great end user
experience and strengthens the TV service provider brand. Huawei offer a browser
based EPG with many fantastic technology through which the interactive services
are accessed and activated.
 Thanks to Huawei OTT solution, it is providing an open API for 3rd party to quickly
integrate with internet application such as RSS feed and OTT application.
 The Huawei Home network solution is based on DLNA to connect the home device
including PC, STB and mobile device which supports DLNA. It will enable the
content to easy share in the home.
 Huawei fully consideration to reduce the OPEX, so Huawei offered solution provides
the unified Elemental management system, backup, restore system and report
server which help customer easy management and maintenance the IPTV
component.
 Furthermore, bringing the successful IPTV experience in worldwide, Huawei also
recommend some key features and solution for carrier, for example, the IPTV SQM
solution, to help carrier to monitor and localize the IPTV problem quickly and sharply
reduce the maintenance cost and enhance the user experience; the FEC and RET
feature, the recommendation engine and search engine are also included in the
Huawei optional offer.

4.2 Highlights of Huawei IPTV solution

Openness, customizable, and evolution solution

 Providing standard interface for 3rd party integration to construction a
comprehensive eco-system and shorten the time-to-market of new services.
 Browse based EPG is a highly customizable portal that can be completely
match the operator’s requirement.
 Full compliance with TISPAN and OIPF to assure seamless evolution to IMS.

Focusing on subscriber experience

 Abundant service and feature to fully match requirements.
 Offering rich interactive service to make customers enjoy the personalized TV
 Customized innovation EPG to assuring easy-to-use and attractive portal for
customers.

Meeting for complex and changeable business requirements

 Quick response market requirement with an separate, customizable IPTV
business management system
 Develop new margin area with innovation technology such as strong Ad
platform, Mashup technology and so on
  Supporting wholesale and public business model in a unified platform

High availability and reliable

 Adopting unified ATAE with nature 99.95% reliability
 A proven high available system, all of the key components are equipped with
redundancy technologies such as dual-node backup, cluster, load balance and
so on

4.3 Middleware System

4.3.1 Overview
The following figure illustrates the Huawei middleware architecture. Huawei
middleware system is comprised of MEM (Media Entertainment Middleware), CMI
(content management interface), BMS (Business management system), Report, Mashup
Engine, Search Engine, and Recommendation Engine.

Figure 1.13 IPTV Middleware architecture

The Huawei middleware is openness, all-service, evolutionary middleware, designed
to meet the carrier interactive TV service requirement.
 Openness
As Huawei is the member of Open IPTV Forum, ITU-T, IETF, DVB, ETSI and OMA,
so the middleware architecture and interface is based on standard and easy to
interoperability with 3rd party system.
 All-service
Huawei middleware support abundant TV service to help carrier succeed the competition
and increase the ARPU. The following figure collects the services supported by Huawei
middleware.

Figure 1.14 IPTV Middleware service portfolio

 Evolutionary
Huawei middleware can be fully compliance with industry standard such as TISPAN
and OIPF. Huawei IPTV platform can support flexible deployment. The team “flexible”
means Huawei IPTV platform support work well independently and work together with
IMS core. When the IMS eco-system is material, Huawei middleware can smoothly
evolve from traditional architecture to IMS based architecture. If implement in an IMS
environment, Huawei middleware allows the carrier to offer additional differentiating
features such as call notification, message sending and receiving, video call termination,
IPTV presence information, chatting (IM) and share-TV.

4.3.2 Key components

1. MEM
The Media Entertainment Middleware (MEM) is a core component of the middleware
system. It is the center that implements all of the business logics for the IPTV service. It
is also the connection point for integrating the other component in the IPTV solution. The
MEM includes a browser based, highly customizable portal (EPG) that can be completely
adapted to the carrier requirements when it comes to branding and look and feel as well
as easily being expanded with new services.
The MEM mainly provides the following functions: managing subscriber profile,
managing service profile, maintaining content, implement subscriber requests for
services, providing the EPG, managing CDR, etc.
The MEM consists of the EDS, ACS, EPG, and SMS/DB.
 EDS - EPG Distributing Server
The EDS distribute STB requests to appropriate EPG servers to implement load
balancing between EPG servers.
 ACS - Application Control Server
The ACS controls subscriber access to implement the authenticating and authorizing
functionality. And also the ACS generates CDR for service consumption of subscribers.
 EPG – Electronic Program Guide
An EPG server enables subscribers to view program information, browse
information, and perform service operations on friendly pages. When subscribers perform
service operations, the EPG server checks local service authorization information and
parental control levels, and provides self-services including changing passwords,
changing parental control levels, querying bills, and saving programs to the Favorites list.
On EPG pages, subscribers can view program trailers, popular programs, program
ranking list, and latest programs. Through the interactions between an EPG server and
other components, subscribers can also browse, subscribe to, and play programs.

2. CMS
The CMS is a content management interface system for the IPTV. The CMS
provides functions such as content injection and content management. At present, the
content managed by the CMI includes the VOD content, EPG metadata, TV series, Live
TV recorded, NVOD content, program list, and value-added service.
The CMS manages content in browser/server (B/S) mode.
The software structure of the CMS consists of the CMS application and the
database, as shown in following figure.
CMS Application Software
GUI Layer

Business Layer Interface Adapter

DAO Layer

CMS Database

Figure 1.15 IPTV CMS architecture

The modules of the CMI mainly provide the following functions:
 The GUI layer provides GUI management.
 The business layer provides basic content management. For example, life cycle
management of media content.
 The interface adapter enables the communication between the CMI and
external systems.
 The DAO layer converts service information to data in the database and
controlling the storage of database data.
 The database stores data of the CMI.
2. BMS
 The BMS is business management system, it is the adaptive component between
middleware and carrier unified BSS. The BMS can manage services independently and
can also interconnect with the existing carrier’s BSS to provide complete and unified
service operation and management functions.
The software structure of the BMS consists of the BMS application server and the
database. The following figure shows the software structure of the BMS.

Figure 1.16 IPTV BMS architecture

XML Extensible Markup Language JMS Java Messaging Service
HTTP Hypertext Transfer Protocol RMI Remote Method Invocation
IIOP Internet Inter-ORB Protocol JDBC Java Database Connectivity
SOAP Simple Object Access Protocol FTP File Transfer Protocol
OSS Operations Support System MEM Media Entertainment Management
The BMS consists of the following functional systems:
 Partner Management
Partner management mainly involves managing CPs or SPs. The main functions of
partner management are as follows:
 Creating partners
 Approving partners
 Suspending partners
 Deregistering partners
 Activating partners
 Authorizing services
 Managing partner types
 Service Management
Service management mainly involves managing content, services, and products.
The main functions of service management are as follows:
 Managing content.
  Managing services
 Managing products
The system administrator can set flexible product packages and preferential policies
to provide diversified product sales policies in time. During operation, carriers can flexibly
change product information and package policies in time without affecting subscriber
experience.
 Business Management
Business management mainly involves managing service information about users.
The main functions of business management is registering users, changing user
information, ordering products, canceling ordered products, activating user accounts,
suspending user accounts, pre-deregistering users, and deregistering users. And alos
include of device management that is unbinding users from STBs when STBs fail or
users want to change STBs.
 Customer Service
 Managing customer information
 Querying ordering information
 Querying consumption records
 Querying history bills
3. TV Message System
With the development of IPTV services, an increasing number of subscribers hope to
experience the brand new services brought by IPTV. As an additional feature of IPTV, the
IPTV TVMS has the following advantages:
 Initiating quiz and voting activities through the IPTV TVMS to interact with
subscribers through TV programs
 Sending shopping information of manufacturers through the IPTV TVMS to TV
subscribers to implement message interaction between manufacturers and
subscribers
TV Message system supports scrolling message and page message.
 Scrolling Messages
Messages scrolled at specific positions on a screen. Normally, such messages
cannot be closed or edited. Scrolling messages are generally used as emergency
messages or messages that subscribers are forced to receive.
 Page messages
Page messages are displayed on a screen in complicated forms. This is similar to an
EPG page. Subscribers can interact with this page, or choose to close this page.
According to the complexity of the page, the page messages are divided into two types:
static page messages and interactive page messages.
Static page message is simple without complicated interaction. This page is normally
a simple HTML page. Static page messages have better presentation effects than
scrolling messages.
Interactive Page Message contains certain interactive content. Such a page requires
an auxiliary background service system. Subscribers can fully interact with this page.

4. Report server
 Huawei pre-integrate the iWeb report system act as IPTV report system. During the
running of the IPTV system, the report system collects data from the data sources of the
IPTV system and generates statistics. It therefore completes the process from original
data collection to final report generation. The report system provides accurate and visual
statistics reports for carriers.
The report system offers some basic report templates for carriers and also supports
to customize more report template to meet the operation requirements.
The report system is B/S structure system and supports generating manual reports
and schedule reports.

Figure 1.17 IPTV report server

4.4 VoD System(Huawei MDN)

4.4.1 Overview
The Media Delivery Network (MDN) is the VOD Platform of the IPTV system. It
distributes and stores media content, dynamically routes subscriber requests for content,
and provides subscribers with streaming services.
 Figure 1.18 MDN architecture
1. Streaming Service
 All Service
 Support various streaming services such as Live TV, HDTV, VOD, TSTV,
TVOD, nPVR, VOD download and progressive download.
 Support streaming service in CA scramble mode.
 Media Relay Functionality / Fast channel change.
 Packet Retransmission in the case of packet loss.
 Support streaming service in IMS network architecture.
 Trick mode
 Support trick mode during the service experiencing, for example, fast
forwarding, fast rewinding, pausing, stopping, and seeking a program.
 Supporting the speeds of 2x, 4x, 8x, 16x, and 32x for playback control.
 Bearer and Transmission
 Video compression: H.264; Media containers: MPEG2 TS over UDP
 Encapsulating the TS through the RTP
 Supporting network-wide multicast, multicast relay, and network-wide uni-
cast for the live service
2. Content Distribution Functionality
Huawei MDN support content distribution mechanism. Content distribution is to
properly distribute media content to POP node in different areas to serve the customer
requirement nearly and save the bandwidth for IP core network. The MDN provides
multiple modes for distributing content, including push, pull, and secondary distribution.
 Push
 After receiving a content distribution task, the MDN actively triggers the content
distribution instruction and distributes media content to VOD server at different layers.
 Pull
When a piece of requested media content is not stored on an VOD server at an edge
POP and the number of requests for the content counted by the distribution sub-system
exceeds the threshold, the MDN requests the edge VOD server to fetch the content from
an upper-layer POP. Therefore, the VOD server can provide services for nearby users.
 Secondary distribution
Through the dynamic adjustment of media content at POP, the distribution of the
media content on different VOD server at the same POP can be optimized to meet the
requirements for watching programs. When a user requests media content from the VOD
server, the distribution sub-system automatically counts the number of request times of
the content. If the number of request times reaches a threshold, the distribution sub-
system distributes the content to other VOD server at the same POP.

4.4.2 Key components

1. Streaming sub-system
 MRF/FEC
The MRF (Media Relay Functionality) is a component that provides the conversion
function for the live media stream. The MRF mainly implements the functions of relaying
and forwarding the live media stream, encapsulating the RTP header into the TS,
converting between the uni-cast stream and multicast stream, and shaping the media
stream.
MRF also has FEC (Forward error correct) functionality that is embedded the FEC
functionality into MRF component. Then, the MRF can implement streaming convert and
add error correct packet simultaneously.
 FCC/RET
Usually, based on the traditional multicast zapping mechanism, the channel zapping
time is about 2-3 seconds. In order to reduce the zapping time, Huawei develop the Fast
channel change (FCC) solution. The FCC server support to receive and analyze the live
streaming. When the STB start to change channel and send IGMP leave. The FCC
server will burst the uni-cast streaming to STB directly. That uni-cast streaming will make
the STB join new channel as soon as possible.
In addition, FCC server also has live TV streaming RET (re-transmission)
functionality. An FCC server can check and parse RTCP RET messages and retransmit
requested RTP packets to the STB based on the sequence numbers of the RTP packets.
The formats of RET messages comply with RFC4585. The RET functionality can make
sure the picture quality during the network has problem.
 HMS/RET
HMS is Huawei media server that inter-works with STB to support on demand
service. HMS support various streaming services such as Live TV, HDTV, VOD, TSTV,
TVOD, nPVR, VOD download and progressive download. In addition, HMS also support
trick mode during the service experiencing, for example, fast forwarding, fast rewinding,
pausing, stopping, and seeking a program, and the speeds of 2x, 4x, 8x, 16x, and 32x for
playback control.
In addition, FCC server also has on demand streaming RET (re-transmission)
functionality. An FCC server can check and parse RTCP RET messages and retransmit
requested RTP packets to the STB based on the sequence numbers of the RTP packets.
The formats of RET messages comply with RFC4585. The RET functionality can make
sure the picture quality during the network has problem.

2. Management sub-system
 UM
As the local authentication agent on the MDN, the UM provides the HMS with local
authentication results and controls subscriber access based on authentication results.
When a subscriber requests the HMS to provide a streaming service, the MS sends
a request for local authentication to the UM. If the subscriber is successfully
authenticated, the MS provides the service for the subscriber.
 CMI
The CMI connection point between the MEM and MDN and imports all media
content to the MDN. The main functions of the CMI are as follows:
 Provide an interface for SP management: The CIS manages SP accounts,
SP rights, and SP resources through this interface.
 Provide an interface for content management: The CIS adds, deletes,
queries, modifies, and censors content through this interface.
 MC
The MC provides the external EMS with an interface for managing devices. The
main functions of the MC are as follows:
 Provide information such as performance, alarms, and logs of the MDN to
the external NMS
 Enable the external NMS to manage configurations and monitor
performance of MDN devices

3. Distribution sub-system
 MM
The MM on the MDN manages content. After receiving content management
instructions (for example, instructions for adding, deleting, and querying for media
content) from the CMI, the MM performs the relevant content management tasks, for
example, publishing, adding, deleting, and querying for content.
The main functions of the MM are as follows:
 After receiving a content publication instruction from the CMI, the MM
instructs the relevant MS to download media content from the content
source at proper time according to the distributing policy.
 When an MS sends a request for downloading content, the MM allocates a
content source to the MS according to the content distribution status on the
entire network, and instructs the MS to download the content from the
 content source.
 Every time a subscriber requests a piece of content from an MS on a POP,
the MS counts the number of times that the content has been requested.
When the number reaches or exceeds a threshold, the MS requests the
MM to distribute the content again. The MM then distributes the content to
another MS on the same POP.
 CC/CDNC
The CDNC and a CC provides similar functions. The CDNC is deployed on the
central node of the MDN and is responsible for global routing and management. A CC is
deployed on each POP of the MDN. It manages the HMS on the local POP, receives
subscriber requests from the CDNC, and routes the requests to the HMS on the POP.
The main functions of the CDNC are described as follows:
 Obtaining the information about the distribution of media content on the
MDN from the MM in real time.
 Monitoring the health status of CCs on lower-level POP in real time.
 Routing subscriber requests to appropriate CCs to implement global load
balancing.
 Collecting statistics about content popularity and reporting the statistics.
The main functions of a CC are described as follows:
 Obtaining the information about the distribution of media content on the
MDN from the MM in real time.
 Monitoring the health status of each HMS on the local POP in real time.
 Routing each subscriber request forwarded by the CDNC to an appropriate
HMS on the local POP.
 Collecting statistics about the popularity of content on the local POP and
reporting the statistics to the CDNC.

4.5 Element Management System(I2000)

4.5.1 Overview
Located at the element management layer of the Telecommunication Management
Network (TMN) model, I2000 acts as element management system (EMS) of IPTV
platform provides overall management. The management functions I2000 include:
topology management, configuration management, fault management, performance
management, and security management. I2000 provides standard external interfaces
(alarm SNMP interface and performance file interface), which help users to integrate
I2000 with the existing network management system (NMS) quickly.
 Figure 1.19 I2000 position in TMN model

4.5.2 Key features

1. Topology Management
The I2000 displays status and information of all management nodes, providing a
clear picture of management environment for customer. By right-clicking the mouse on
NEs, users can find a shortcut menu for the operations of common I2000 applications.
Customer benefits:
Product development brings about more network devices on the network, resulting in
an increasing complex network structure. That being the case, it is difficult to find out
causes when an error occurs, which substantially reduces work efficiency. Therefore, it is
necessary to provide users with a clear topology view so that users can know the NE
deployment and monitor NE status.

Figure 1.20 Main topology management functions

2. Configuration Management
Configuration management includes the functions of querying and updating service
operation parameters. The I2000 provides the IPTV system with the iCnfg Integrated
Configuration System (I2000 iCnfg for short). The I2000 iCnfg enables users to configure
distributed IPTV components, helping users to perform centralized management and
save the configuration maintenance cost.
The configuration management function is used to query, add, modify, and delete NE
data and service data. The configuration management function provides the device view
and service view.

3. Fault Management
Alarms are categorized into fault alarms and event alarms. A fault alarm is generated
when the system deviates from the normal running status, and is defined as "the physical
or algorithmic cause of a malfunction" in X.733. An event alarm is a notification sent while
the system is running, and is defined as "this is a generic term for any type of occurrence
within a network entity" in 3GPP 32.111-1. Event alarms can only be acknowledged, but
cannot be cleared.
When a fault occurs on a managed NE, an active alarm is generated and reported to
the I2000. After receiving the alarm, I2000 displays it on I2000 GUIs in real time.
I2000 stores alarm information into databases six months by default. It also allows
operators to export alarm information manually to .csv files.
4. Performance Management
One counter maps one performance measurement item on an NE. After an NE is
started, the default counter is loaded and activated (deactivation is not allowed). After the
NE receives a service request, the counter starts to count the values of involved
performance items.
A measurement task is a set of performance items. Each performance items
contained in a performance measurement task corresponds to a counter. After a
managed NE is connected to I2000, operators can active some performance
measurement tasks on the NE. Then the NE reports the performance items result of
these active tasks to I2000 periodically. Operators can deactivate some measurement
tasks.
I2000 supports displaying near-real-time performance data and generating
performance threshold alarms function for operators to monitor performance and predict
faults.
I2000 can store performance data in the database for a default three months. It also
allows users to export performance data to .csv files.
5. Security Management
I2000 provides role-based user group management and right management for O&M
personnel. I2000 has the following default roles:
 Super administrator group: By default, this group is provided by the system and
must be the only one. Members in this group can manage all NEs and run all
I2000 applications except the security management.
 Security administrator group: By default, this group is provided by the system
and must be the only one. Members in this group have security management
rights, for example, creating a user/user group, and assigning rights to a
user/user group.
 Operator group: Multiple user groups are allowed, and their rights are assigned
by the security administrator. Users can customize various operator groups as
required. Each group may have different rights. An operator group can be
assigned a set of certain operation rights or managed NE objects. For example,
a certain operator group can query various data; other groups can perform
various operations or manage a certain type of devices.

4.6 Terminal Management System

4.6.1 Overview
Huawei adopts Works OneMS ACS system as the STB unified management system.
OneMS ACS is a STB management solution which can handle STB provisioning,
monitoring, maintenance and reporting, and all these can be integrated with higher level
systems, such as Network Management System (NMS) or OSS/BMS systems.

4.6.2 Key features

1. Remote Monitoring
The TMS provides status monitoring and performance monitoring by setting
parameter attributes.
 Status monitoring
If the report attribute of the STB is set to the active status, when the status or
parameter values of the STB change, the STB can actively report the change to the TMS.
The TMS can determine whether to update the TMS information or overwrite the STB
information with the TMS information according to the settings for its behaviors.
 Performance monitoring
 After the TMS is configured with the performance monitoring parameters of the STB,
maintenance personnel can check the status of media playback performance of the STB
on the TMS. Maintenance personnel can understand the running status of the STB in a
timely manner according to the performance status of the STB.
2. Remote Diagnosis
To achieve the purpose of diagnosis and troubleshooting, the TMS provides the
diagnosis function for the administrator to solve problems about connectivity. Three
diagnosis methods are as follows:
 IP Ping diagnosis
IP Ping is a computer network tool that is usually used to test whether data packets
can be successfully transmitted to a specified host on an IP network. Through the IP Ping
diagnosis, maintenance personnel can properly detect the status of network connections
between the STB and other subsystems of the IPTV, for example, the status of network
connection between the STB and EPG server.
 Trace Route diagnosis
Trace Route is a computer network tool that is usually used to test the information
such as routing and hop count on an IP network. Through the Trace Route diagnosis,
maintenance personnel can properly detect the status of network connections between
the STB and other subsystems of the IPTV, for example, the status of network connection
between the STB and EPG server.
3. Remote Maintenance
The TMS provides the remote maintenance function, through which maintenance
personnel can maintain devices remotely. Remote maintenance includes:
 Remote restart
In certain scenarios or services, maintenance personnel must restart STBs. In this
case, they can restart the STBs through remote restart.
 Remote restoration of factory settings
In this case, maintenance personnel can restore the data of the STB to the factory
status through remote restoration of factory settings, and then reset the data of the STB.
 Firmware upgrade
When the software of STBs needs to be upgraded, maintenance personnel can
upgrade STBs in batches so that subscribers can better use IPTV services. There are
two upgrade modes:
− Group upgrade based on the upgrade policy.
Maintenance personnel upgrade the STBs falling within a specified range of IP
addresses or MAC addresses according to the configured upgrade policy.
− Upgrade of the specified STBs.
Maintenance personnel actively upgrade and control an STB or a group of STBs.
 Backup and recovery
Maintenance personnel upload the configuration files of STBs to the system. When
STBs are faulty, maintenance personnel can restore the STBs by using these
configuration files so that the STBs can function properly.
 Log files reporting
Maintenance personnel upload the log files of STBs to the system. When STBs are
faulty, maintenance personnel can identify the faults and troubleshoot the STBs by using
these log files so that subscribers can use IPTV services properly.
4. Device Configuration
The TMS provides the functions of checking and configuring device information,
including:
 Network configuration
Network configuration covers the IP address, address type, subnet mask, default
gateway, DNS server, and MAC address of the STB.
 Time setting
Time setting includes configuring the STB NTP server, and checking the current time
and time zone of the STB.
 Authentication configuration
Authentication configuration covers the IPTV account, IPTV password, PPPoE
account, PPPoE password, and URL of the authentication server.
 Performance statistics configuration
Performance statistics configuration covers the URL of the log server, the period for
reporting the statistics result, and the statistics recording period.
 Alarm configuration
Alarm configuration covers the alarm switch, alarm reporting level, CPU alarm
threshold, memory alarm threshold, disk space alarm threshold, and bandwidth alarm
threshold.
 TR-069 parameter setting
TR-069 parameter setting covers the URL, user name, password, and upgrade
management.
 SQM configuration
SQM configuration covers the SQM listening port and SQM serving port.
5. Statistics Collection
To help subscribers check the statistics, the TMS provides the statistics reporting
function. The statistics cover four parts:
 Device deployment statistics
Counts the number of STBs that have been deployed (have been registered and
have not been registered) in an area.
 Device registration statistics
Counts the number of STBs that have been registered in an area and compares the
number of registered STBs in different time intervals.
 Device software version statistics
Counts the number of all types and the number of each type of STB software
versions in an area.
 Device pre-configuration statistics
Counts the number of STBs that have been successfully pre-configured or fail to be
pre-configured in an area.
4.7 OTT Integration Solution
4.7.1 Overview

Figure 1.21 OTT service architecture

The Huawei OTT enabler is based on Mashup technologies. The Mashup engine is
going to get metadata and video entry (which can be configurable by the admin) about
internet content from ISPs’ platform. The metadata include txt, picture, etc. At same time,
the operator/admin uses EPG customization tool to make out EPG template according UI
design and predefined service logics, e.g. which services should be Mashuped in one
EPG page. When STB send a request to access OTT application, Huawei EPG server
will mix the metadata and video entry from different ISP on one EPG page, and response
it to STB. In this way, STB can access the news by text or picture without the direct
connection with ISP site. If subscriber requires watching OTT video, STB will use the
video entry on EPG to connect ISP site directly. Currently, the video format should be
encapsulated by flv and the codec should be H.264.

4.7.2 Key features

 No additional requirements for STB capability
 Best layout and user experience for TV screen
 Browsing via TV remote control is simpler
 The OTT content can be fully controlled by operator
4.7.3 OTT service work flow

Figure 1.22 OTT service flow

4.8 Service Quality Management Solution

Huawei IPTV SQM (Service Quality Management) support embedded probe which
can deploy with the media server or STB provided by Huawei to reduce the TCO.
Meanwhile, Huawei SQM solution can also support independent probe deployment to
monitor IP bear network equipment provided by Huawei or other vendors.

4.8.1 Overview
IPTV service requires an all-round media quality monitoring system, which can
measure all indexes of IPTV QoS and QoE at all stages in the lifecycles of IPTV devices
and networks to constantly enhance device performance, quickly diagnose and correct
network faults, and improve network performance, thus improving the QoE of IPTV
subscribers. The Huawei Service Quality Management (SQM) system is a monitoring
system that meets the preceding requirements.
Huawei provide an end to end SQM solution, including MQMC and probes. There
have two types of probe:
Media servers probe: It is a joint probe which based on HMU media server, deployed
in POP node
STB probe: It is a software client should be installed in STB.
 MQMC: SQM solution management system.
 Locating Faults
When subscribers report faults, maintenance personnel need to quickly locate the
faults and take corrective measures.
Maintenance personnel can use the SQM system to analyze the indicator values of
media stream monitored by all monitoring points on the network. In this way, they can
determine the health status of the system side or network side. Fault locating is triggered
as per subscriber.
 Monitoring Network Quality
Monitoring network quality is monitoring the quality of media streams of a specified
type transmitted over a segment of a network. You can use the SQM system to determine
whether HD or SD uni-cast or multicast media streams can be properly transmitted on a
specified network. Network quality monitoring is triggered as per uni-cast or multicast
link.
 Monitoring Live Channels
Live channel monitoring focuses on the transmission quality of video stream of a HD
or SD live on the network in real time. Live channel monitoring is triggered as per
channel.

4.8.2 Highlights
Huawei service quality monitoring solution is an end to end solution. It can monitor
the solution from the service side through network to the end users. The high lights of this
solution are showing as below.
 End to End Solution
Huawei service quality monitoring solution can deploy probes inside the service
platform, in Huawei network devices and on other vendor network devices, in the service
terminal such as STB. It is a real end to end solution. This may help the operators to
monitor the services status and troubleshoot easily and precisely.
 Easy to be Maintained
Obviously, a module within a device is easier to maintain than an external one. In
that these devices can share the network management path with the built-in module.
 High system reliability
Built-in modules can interconnecting with the motherboard or even share data Trans
path with normal service transmission, so it do not need connection in physical line. This
can avoid disturbs introduced by these physical connections.
 Accurate service quality measuring
The service monitoring solution inspects the real service streams, and measures
them using standard algorithm. This can get more accurate results comparing to the
"emulated streams".
 External probe support other vendor device
Huawei service quality monitoring solution also support external probe, to be easier
to deploy on a multi-vendor networks. The external probe can connect with other vendor
devices to monitor the service streams through them.
  Multi-Dimensional service analysis
The MQMC analyzes the statistics of the simulated test indicators for NEs, networks,
and services in a multi-dimensional manner, generates alarms in time to prevent the
performance from potentially worsening, and rapidly identifies the worsening source.
Customers can improve the service quality in advance to meet users' satisfaction so as to
improve the competitiveness of network operation and easily realize the active operation
and maintenance.
 High-precision data measurement to ensure accuracy of KPI data
In network performance tests, the precision and algorithms of time are of vital
importance to the test results. The MQMC Solution features the precise built-in time
Model and hardware time stamping for IP packet headers, thus avoiding the error in the
time consumed by the software system. The external probe adds time information to the
header of the IP packet received. Thus, the time precision is greatly enhanced. The
probes provide high-precision time synchronization for NTP (precise to seconds).

4.8.3 Key components

 MQMC (Media Quality Monitor Center)
MQMC manages and configures the topology relationship for all of the probes. And
also collects the monitoring data reported by probes and implement monitoring task
based on different service scenario such as uni-cast link, multicast link, and live link.
 Server probe
Serve probe means the probe can embedded into streaming server. Server probe
can monitor various modules such as NIC monitoring, signaling collection, media
sending, media receiving, media processing, and SQM analysis. Monitors can create and
delete links according to the instructions delivered by the MQMC. Server probe collect
data from monitored devices based on the instructions delivered by the MQMC, analyze
video quality, and report analysis results to the MQMC.
 STB probe
STB probe means the probe can embedded into STB. The STB integrates the SQM
analysis module. When subscribers experience failure during use of IPTV services, the
MQMC creates fault locating links. The STB receives the instructions delivered by the
MQMC to collect data and analyzes the received media streams. Then the STB reports
the result of analyzing the video quality to the MQMC. After the fault is located, the
MQMC requests the STB to stop the monitoring.

4.9 Backup and Restore Solution

4.9.1 Backup system overview
 Why Backup
 It is one of the most important system construction issues how to properly protect the
data stored in the computer system, ensure the reliable operation of the system, and
provide fast and reliable access to the service system. And one of the key elements
guaranteeing the reliable operation of the system is to protect the data stored in the
computer.
Though the development of computer technology greatly conveniences our daily life,
the data in the computer can get lost because of operational errors committed by
humans, the defects of system or application software, damage to hardware, the attack
of computer viruses and hackers, natural disasters, etc., and such loss can do
inestimable damage to an enterprise. To protect the key service data on the business
system, we must perform an effective backup of such data that supports fast recovery.
All data backups are prepared for recovery in case of a disaster. The standards for
judging the advantages or disadvantages of an automatic backup system relate not only
to its backup mode/backup speed, but also to its recovery capability, another important
element deserving careful consideration. For recoverability, there are two decisive
factors: the recovery speed and operational simplicity.
 Backup Principles
Data backup is performed to maintain the consistency and integrity of data, and free
the user and operator of worry over the data. Different application environments require
different backup solutions. Usually, a perfect backup system needs to meet the following
principles:
 Stability
The main purpose of a backup product is to provide the system with a data
protection method, so the stability and reliability of the product is one of the most
important aspects. First of all, its backup software must be 100% compatible with the
operating system. Second, it is capable of fast and effective data recovery in the event of
an accident.
 Recoverability
The purpose of data backup is to recover the data. A backup system is meaningless
if its success of backup is unforeseeable or it cannot guarantee that system data can be
recovered within an appropriate period of time. If the hardware or software of the backup
system fails, very likely the system cannot be recovered quickly if there is a recovery
process that has never been practiced before or if there is no such process at all. This
will deteriorate the availability of the application system.
 Automatic
For their operational nature, many systems pose certain limits on when the backup
starts and how long the backup takes. Midnight is the suitable time for backup thanks to
the low traffic of the service system. But this would increase the workload of the system
administrator, and, for such reasons as mental fatigue, expose data backup to hidden
danger. Therefore, the backup solution should provide regular automatic backups, and
use such techniques as the tape library for automatic tape change. In the process of an
automatic backup, the log function is required, and an automatic alarm message should
be issued in case of abnormality.
 High performance
 With the growth of business, data keeps increasing and is updated more and more
frequently. So you will not have enough time for backing up so much data when you are
off work, and if you do such backup during your work hours, it will affect the performance
of the system. For this reason, the backup design should take into account, as much as
possible, the improvement of the data backup speed, for example, by operating a number
of tape machines concurrently.
 Operational simplicity
Since data backup applies to various fields, the operators performing data backups
are at different levels. This requires an intuitive graphic user interface (GUI) easy to
operate so as to shorten the time for the operator to learn, alleviate the work pressure on
the operator, and facilitate the setting and completion of data backup.

4.9.2 Proposal backup solution

The centralized backup system’s network topology is as shown below:

Figure 1.23 Backup topology

We suggest that set up centralized backup system for all the service systems which
need to be backup. The remote terminal can be put in network management center, and
it is responsible for managing and maintaining data backup system for the IPTV system.
 Features and Security Performance
Standalone data backup network
A dedicated storage network for data backup independent of the service network is
set up to ensure that data backup will not have any impact on the service network.
 Backup server
 This is the server end of the backup software, responsible for centralized
management and monitoring of data backup, media management, and so on.
 Tape library
The specific backup strategy is followed to determine the duration for keeping the
stored backup data for database level 0 backup, the operating system, application
system, call ticket documents, and so on. The tape library is mainly used for storing long-
term data for the archive purpose.
 Parallel design
A parallel structure is designed for this solution, which supports the concurrent
performance of multiple data backups. The speed for a single data backup/recovery can
be 30MB/S or above.
 Centralized management
A remote maintenance terminal can be deployed if needs arise. It is only responsible
for monitoring the data backup for every service system (the administration authority can
be increased if necessary). A local maintenance terminal can also be set up in the
maintenance room of each service system, responsible for managing and maintaining the
data backup in the system.
 Implementation and training
Huawei shall be responsible for implementing the whole solution, and providing on-
site training for the operation & maintenance personnel.

4.9.3 Backup Strategy

 Routine operation
The backup window is between 0:00-7:00 in the early morning.
Data backups can be performed in all the service systems concurrently.
Target of Backup Backup Keep
Name
backup window period period

File full 0~7:00

1 week 3 months
backup
MEM
Database 0~7:00
1 day 1 month
full backup

Database 0~7:00
1 day 1 month
full backup
i2000
File full 0~7:00
1 week 3 months
backup

Database 0~7:00
MDN(central 1 day 1 month
full backup
node)
File full 0~7:00
1 week 3 months
backup
BMS Database 0~7:00 1 day 1 month
full backup
 File full 0~7:00
1 week 3 months
backup
Note:
1. The database’s log backup is performed in continuous automatic mode, and is compatible

with Oracle/DB2. In case of Oracle, the backup needs to be performed in archive log mode.

2. To ensure the rapidity and correctness of database recovery, Huawei recommends level 0

backup for databases.

3. The regular backup of the file system and the operating system is to safeguard system files

against accidents and unauthorized modifications.

 Important operations
Important operations include system upgrade, software patching, service
adjustment, and system separation. Prior to performing any of these important
operations, it is necessary to get carefully prepared for data backup.
First, perform a level 0 backup before each important operation.
It is necessary to perform a full backup for the application system before any
important operation relating to the application system, and keep the backup for a period
of three months.
It is necessary to perform a full backup for the application system before any
important operation relating to the operating system, and keep the backup for one year.
Please perform a specific operation according to the relevant upgrade and cutover
guide.
Note:
While performing a backup for an important operation, the operator needs to perform the

backup manually on the backup server because the time is uncertain and irregular.

 Major festivals and holidays

Major festivals and holidays: New Year’s Day, Christmas, and so on.
During festivals and holidays when service traffic is at its peak, it is particularly
necessary to guarantee data security. Therefore, it is necessary to enhance the
monitoring of the backup. You can consider improving the backup frequency, for
example, changing the original one full backup everyday to several backups every day.
Note:
The strategy adjustment made during a major festival and holiday is temporary one, and need

be restored to the normal strategy when the festival or holiday is over.

4.10 Digital Home Solution
4.10.1 Overview
Huawei digital home solution is shown as below, it supports multiple STBs in home,
PC client and mobile device connection. All of these devices connected should be
compliant with DLNA standard.

Figure 1.24 Digital home solution overview

4.10.2 Digital home scenarios description

1. Scenario 1: Content sharing between home storage and other home devices
The home storage should be support DLNA DMS and DMC, the other home devices
at least support DLNA DMP. The other home devices can play the content saved in the
home storage.
For example, at primary STB, it can play the content storage in the PC hard disk.
Currently, Huawei STB supports this scenario.
2. Scenario 2: Content sharing between primary STB and other home devices
The primary STB will have a embedded or external Hard disk, it can recoding the
content form the IPTV platform. The primary STB should support DMS and DMC, and the
other devices should support DMP, the other home devices can play the content on the
primary STB including the live TV. This scenario will be supported in the future huawei
release
3. Scenario 3: Interactive between primary STB and other home devices
The end-user can shift the playing content to PC client or mobile and resume
watching the content continuously. Or the end-user can shift the content from PC to TV
set. Meanwhile, the end-use can set the bookmark, favorite in any device and share
these bookmark and favorites in any other devices. This scenario will be support in the
future huawei release
4. Scenario 4: Remote controlling the STB through mobile devices or PC
The end-use can set the nPVR recording schedule through the Mobile device or PC.
And also the end-use can check the recording status and new movie. This scenario will
be support in the future huawei release

4.10.3 Home network engineering suggestion

To easy connect the home devices, Huawei suggest using the WiFi technologies,
here are the suggestion for WiFi device:

Interfac distanc Wireless

Solution Protocol Scenario
e e penetrability
TCP uni-cast and UDP multicast
HUAWEI
WiFi 15 supported
HG531/HG532+WS3 RJ45 2 walls
802.11n meters Suitable for 2-3 SD channels or 1
11
HD channel
TCP uni-cast and UDP multicast
RUCKUS WiFi 20 supported
RJ45 2 walls
VF7811+VF7111 802.11n meters Suitable for 5-6 SD channels or 2
HD channel
TCP uni-cast and UDP multicast
RUCKUS WiFi 20 supported
RJ45 2 walls
VF2825+VF2111 802.11g meters Suitable for 3-4 SD channels or 1
HD channel
Standard AP+USBWiFi 10 Only TCP uni-cast supported
USB 1 wall or less
WiFi adaptor 802.11g meters Suitable for 1 SD channel
4.11 Proposed Hardware

Figure 1.25 ATAE illustration

The all the components which self designed by Huawei sub-system are based on
Huawei ATAE blade servers, the following is a simple introduction of Huawei ATAE
servers, for the detail information, please refer to the ATAE product description
documents provided by Huawei.
The ATAE provides a complete service platform solution, including dense service
processing blades, storage devices, USM, and network devices.
The ATAE uses the modularization technique to separate resources, such as
computing, input/output (I/O) ports, and storage, from each other, and to separate the
management and services, thus ensuring the high availability of the system. The ATAE
system integrates multiple techniques concerning with the server, storage, network
switching and connection, and heterogeneous intelligent management. The high
performance enables the ATAE system to meet the future requirement for service
development. The ATAE supports the current devices and meanwhile is highly extensible.
It is a good choice for extending the applications.
The ATAE functions as a telecommunications server of high availability, high
reliability, and high performance, and provides an open, standard, and universal service
processing platform. The ATAE is intended for the following applications: server
applications, powerful processing capability, and powerful backplane switching capability.
This section describes the ATAE features such as reliability and extensibility.
 Diversified Server Blades
The various server blades and flexible I/O modules (including the RTMs and
daughter cards) are applicable to different services or to different scenarios of the same
service.
 Modular Design and Dense Configuration
 The ATAE uses the standard modular design, that is, different function processing
units can be implemented through different independent modules. Therefore, the loose
coupling between system modules is implemented. The ATAE product has the features of
high density and energy saving. One shelf contains up to 12 server blades.
 High Reliability
The ATAE uses the redundancy design to provide services of high reliability.
 Flexible Extensibility
The ATAE provides flexible extensibility. It can take full advantage of current devices
and meanwhile is convenient for the extension of the current system to meet the
requirement of the future service development.
 Management and Maintenance Tools
The ATAE provides powerful management and maintenance tools to perform
centralized management on the computing resource, storage resource, network process
resource and interface resource.
 Fault Recovery
The ATAE provides the fast fault recovery. Therefore, you can locate and rectify
faults quickly, thus enhancing the secure running capability of the system.
 Energy Saving Design
The ATAE features energy saving, thus meeting your requirements for effectively
using energy, reducing power consumption, and reducing environment influence.
More detailed information for Huawei ATAE hardware platform, please refer to Huawei
ATAE hardware platform production description.

5 Equipment Dimensioning

5.1 List of Service Requirement and Traffic Data

Huawei collected the Service Requirement and Traffic Data from the RFP/RFQ/RFI. The data are
shown in the following table:

List of Service Requirements in RFP/RFQ/RFI

SN Service Name Item Data Unit
1 Network Structure Network Structure Two Level Level
2 IPTV Total registered IPTV Total registered Subs. 50 K Sub.
Subs. Qty. (K)
3 Ratio of Online Subs. Ratio of Online Subs. 50% %
4 Ratio of Unicast %
Subs. Ratio of Unicast Subs. 10%
5 Ratio of FCC Subs. Ratio of FCC Subs. 5% %
6 SD Unicast %
Concurrent Ratio SD Unicast Concurrent Ratio 90%
7 HD Unicast HD Unicast Concurrent %
Concurrent Ratio Ratio 10%
8 Central Node Central Node registered 50 K Sub.
registered Subs. Subs.(K)
Edge Node registered Edge Node registered Subs. 50 K Sub.
Subs. (K)
SD Live Channel SD Live Channel Qty. 50 Channel
SD TVOD Channel SD TVOD Channel Qty. 50 Channel
SD TVOD Hours SD TVOD Hours（H） 168 Hour
SD TSTV Channel SD TSTV Channel Qty. 50 Channel
SD TSTV Hours SD TSTV Hours（H） 3 Hour
SD VOD Content SD VOD Content 1600 Hour
Hours Hours（H）
SD Coding Rate SD Coding Rate（ Mbps） 2.5 Mbps
HD Live Channel HD Live Channel Qty. 12 Channel
Qty.
HD TVOD Channel HD TVOD Channel Qty. 12 Channel
Qty.
HD TVOD Hours HD TVOD Hours 168 Hour
HD TSTV Channel HD TSTV Channel Qty. 12 Channel
Qty.
HD TSTV HD TSTV Hours（H） 3 Hour
Hours（H）
HD VOD Content HD VOD Content Hours 400 Hour
Hours
HD Coding Rate HD Coding Rate （Mbps） 8.0 Mbps
（Mbps）
NVOD Channel Qty. NVOD Channel Qty. 2 Channel
 NPVR NPVR calculate mode TVOD -
Rate
Period of Reserved Period of Reserved NPVR 30 Day
NPVR Programs Programs(Days)
… … … … …
Based on the project requirements, the network overall architecture is below:

Figure 1.26 Physical architecture of the proposed solution

SchematicDiagram
Logic Network Diagram

5.2 Calculation Process

5.2.1 IPTV Platform Central Node

Besides the data listed in the RFP/RFQ/RFI document. Huawei also provides the necessary
assumption of service traffic data to calculate the configuration. The data are shown here:

1.1.1.1.1.a.1 List: Service Traffic Data assumed by vendor

SN Service Name Item Data Unit
1 EPG EPG Online subscriber 25000 Sub.
2 FCC FCC Input Channel 221 Mbps
 SN Service Name Item Data Unit
Bandwidth(Mbps)
FCC Output Broadcast Mbps
3 FCC
Bandwidths(Mbps) 3050
MRF Broadcast Mbps
4 MRF
Bandwidths(Mbps) 221
HMS(TVOD/ HMS Need Read Mbps
5
TSTV/ VOD) Bandwidths(Mbps) 15250
HMS(TVOD/ HMS Need Write Mbps
6
TSTV/ VOD) Bandwidths(Mbps) 221
NVoD Output Broadcast Mbps
7 NVoD
Bandwidth(Mbps) 5
IPTV Platform Central Node is calculated as below:
 EPG Online subscriber = Central Node registered Subs.(K) * 1000 /
Ratio of Online Subs.
 FCC Input Channel Bandwidth(Mbps) = SD Live Channel Qty.* SD
Coding Rate（ Mbps）+ HD Live Channel Qty. * HD Coding Rate
（Mbps）
 FCC Output Broadcast Bandwidths(Mbps) = Central Node registered
Subs.(K) * 1000 * (Ratio of Online Subs. - Ratio of Unicast Subs.) *
Ratio of FCC Subs. * IF (SD Live Channel Qty.+ HD Live Channel
Qty.>0, SD Unicast Concurrent Ratio* SD Coding Rate（ Mbps）+ HD
Unicast Concurrent Ratio* HD Coding Rate （Mbps）, 0 )
 MRF Broadcast Bandwidths(Mbps) = SD Live Channel Qty.* SD
Coding Rate（ Mbps）+ HD Live Channel Qty.* HD Coding Rate
（Mbps）
 HMS Need Read Bandwidths(Mbps) = Central Node registered Subs.
(K)* 1000 * Ratio of Unicast Subs.* (SD Unicast Concurrent Ratio* SD
Coding Rate（ Mbps） + HD Unicast Concurrent Ratio* HD Coding
Rate （Mbps） )
 HMS Need Write Bandwidths(Mbps) = MAX (SD TVOD Channel Qty.,
SD TSTV Channel Qty.) * SD Coding Rate（ Mbps）+ MAX (HD
TVOD Channel Qty., HD TSTV Channel Qty.) * HD Coding Rate
（Mbps）
 NVoD Output Broadcast Bandwidth(Mbps) = NVOD Channel Qty.* SD
Coding Rate（ Mbps）
5.2.2 IPTV Platform Edge Node
List: Service Traffic Data assumed by vendor
Service Name Item Data Unit
EPG EPG Online subscriber(K) 25000 Sub.
FCC Input Channel Mbps
221
FCC Bandwidth(Mbps)

FCC Output Broadcast Mbps

3565
FCC Bandwidths(Mbps)

HMS Need Read Mbps

15250
HMS Bandwidths(Mbps)

HMS Need Write Mbps

221
HMS Bandwidths(Mbps)

IPTV Platform Edge Node is calculated as below:

 EPG Online subscriber = Edge Node registered Subs.(K) * 1000 / Ratio
of Online Subs.
 FCC Input Channel Bandwidth(Mbps) = IF(Edge Node registered Subs.
(K) > 0, SD Live Channel Qty.* SD Coding Rate（ Mbps）+ HD Live
Channel Qty. * HD Coding Rate （Mbps）, 0)
 FCC Output Broadcast Bandwidths(Mbps) = Edge Node registered Subs.
(K) * 1000 * (Ratio of Online Subs. - Ratio of Unicast Subs.) * Ratio of
FCC Subs. * IF (SD Live Channel Qty.+ HD Live Channel Qty.>0, SD
Unicast Concurrent Ratio* SD Coding Rate（ Mbps）+ HD Unicast
Concurrent Ratio* HD Coding Rate （Mbps）, 0 )
 HMS Need Read Bandwidths(Mbps) =IF( Edge Node registered Subs.
(K)<>0 , Edge Node registered Subs.(K) * 1000 * Ratio of Unicast
Subs.* (SD Unicast Concurrent Ratio* SD Coding Rate（ Mbps） + HD
Unicast Concurrent Ratio* HD Coding Rate （Mbps） ) , 0)
 HMS Need Write Bandwidths(Mbps) = IF( Edge Node registered Subs.
(K)<>0 , MAX (SD TVOD Channel Qty., SD TSTV Channel Qty.) *
SD Coding Rate（ Mbps）+ MAX (HD TVOD Channel Qty., HD TSTV
Channel Qty.) * HD Coding Rate （Mbps） , 0)

5.2.3 Storage Configuration

List: Service Traffic Data assumed by vendor
Service Name Item Data Unit
VOD VOD Storage(G) 3164 GB
SD TVOD SD TVOD Storage(G) 9229 GB
 Service Name Item Data Unit
SD TSTV SD TSTV Storage(G) 165 GB
HD TVOD HD TVOD Storage(G) 7088 GB
HD TSTV HD TSTV Storage(G) 127 GB
NPVR Storage NPVR Storage(G) 6993 GB
Storage Requirement(G) Storage Requirement(G) 19480 GB

IPTV Platform Edge Node is calculated as below:

 VOD Storage(G) = (SD VOD Content Hours（H）* SD Coding
Rate（ Mbps）+ HD VOD Content Hours* HD Coding Rate
（Mbps） ) *3600/8/1024
 SD TVOD Storage(G) = SD TVOD Channel Qty. * SD TVOD
Hours（H）* SD Coding Rate（ Mbps）*3600/8/1024
 SD TSTV Storage(G) = SD TSTV Channel Qty. * SD TSTV
Hours（H）* SD Coding Rate（ Mbps）*3600/8/1024
 HD TVOD Storage(G) = HD TVOD Channel Qty. * HD TVOD Hours
* HD Coding Rate （Mbps）*3600/8/1024
 HD TSTV Storage(G) =HD TSTV Channel Qty. * HD TSTV
Hours（H） * HD Coding Rate （Mbps）*3600/8/1024
 NPVR Storage(G) = IF (NPVR calculate mode="TVOD Rate", Period
of Reserved NPVR Programs(Days)* (MAX(SD TVOD Channel Qty.,
SD TSTV Channel Qty.)* SD Coding Rate（ Mbps）+MAX(HD TVOD
Channel Qty., HD TSTV Channel Qty.)* HD Coding Rate （Mbps）)
*24*3600 /8/1024,0)
Storage Requirement(G) =SUM(VOD Storage(G) , MAX(SD TVOD Storage(G), SD
TSTV Storage(G) ) , MAX (HD TVOD Storage(G), HD TSTV Storage(G) ) , NPVR
Storage(G) )

5.3 Calculation Result

5.3.1 IPTV Platform Central Node

The result of IPTV Platform Central Node calculation is as below:

List: Service Traffic Data assumed by vendor
Service
SN Item Dimension Calculation Result
Name
1 EPG EPG Online subscriber 25000 Sub. [Calculation Result]
 Service
SN Item Dimension Calculation Result
Name

FCC Input Channel

2 FCC [Calculation Result]
Bandwidth(Mbps) 221 Mbps
FCC Output Broadcast
3 FCC [Calculation Result]
Bandwidths(Mbps) 3050 Mbps
MRF Broadcast
4 MRF [Calculation Result]
Bandwidths(Mbps) 221 Mbps
HMS(TVOD
5 / TSTV/ HMS Need Read [Calculation Result]
VOD) Bandwidths(Mbps) 15250 Mbps
HMS(TVOD
6 / TSTV/ HMS Need Write [Calculation Result]
VOD) Bandwidths(Mbps) 221 Mbps
NVoD Output Broadcast
7 NVoD [Calculation Result]
Bandwidth(Mbps) 5 Mbps
IPTV Platform Central Node is calculated as below:
 EPG Online subscriber = Central Node registered Subs.(K) * 1000 /
Ratio of Online Subs.
 FCC Input Channel Bandwidth(Mbps) = SD Live Channel Qty.* SD
Coding Rate（ Mbps）+ HD Live Channel Qty. * HD Coding Rate
（Mbps）
 FCC Output Broadcast Bandwidths(Mbps) = Central Node registered
Subs.(K) * 1000 * (Ratio of Online Subs. - Ratio of Unicast Subs.) *
Ratio of FCC Subs. * IF (SD Live Channel Qty.+ HD Live Channel
Qty.>0, SD Unicast Concurrent Ratio* SD Coding Rate（ Mbps）+ HD
Unicast Concurrent Ratio* HD Coding Rate （Mbps）, 0 )
 MRF Broadcast Bandwidths(Mbps) = SD Live Channel Qty.* SD
Coding Rate（ Mbps）+ HD Live Channel Qty.* HD Coding Rate
（Mbps）
 HMS Need Read Bandwidths(Mbps) = Central Node registered Subs.
(K)* 1000 * Ratio of Unicast Subs.* (SD Unicast Concurrent Ratio* SD
Coding Rate（ Mbps） + HD Unicast Concurrent Ratio* HD Coding
Rate （Mbps） )
 HMS Need Write Bandwidths(Mbps) = MAX (SD TVOD Channel Qty.,
SD TSTV Channel Qty.) * SD Coding Rate（ Mbps）+ MAX (HD
TVOD Channel Qty., HD TSTV Channel Qty.) * HD Coding Rate
（Mbps）
 NVoD Output Broadcast Bandwidth(Mbps) = NVOD Channel Qty.* SD
Coding Rate（ Mbps）
5.3.2 IPTV Platform Edge Node
List: Service Traffic Data assumed by vendor
Dimensi Calculation
Service Name Item
on Result
25000 [Calculation
EPG EPG Online subscriber(K) Sub. Result]
FCC Input Channel 221 [Calculation
FCC Bandwidth(Mbps) Mbps Result]
FCC Output Broadcast 3565 [Calculation
FCC Bandwidths(Mbps) Mbps Result]
HMS Need Read 15250 [Calculation
HMS Bandwidths(Mbps) Mbps Result]
HMS Need Write 221 [Calculation
HMS Bandwidths(Mbps) Mbps Result]

IPTV Platform Edge Node is calculated as below:

 EPG Online subscriber = Edge Node registered Subs.(K) * 1000 / Ratio
of Online Subs.
 FCC Input Channel Bandwidth(Mbps) = IF(Edge Node registered Subs.
(K) > 0, SD Live Channel Qty.* SD Coding Rate（ Mbps）+ HD Live
Channel Qty. * HD Coding Rate （Mbps）, 0)
 FCC Output Broadcast Bandwidths(Mbps) = Edge Node registered Subs.
(K) * 1000 * (Ratio of Online Subs. - Ratio of Unicast Subs.) * Ratio of
FCC Subs. * IF (SD Live Channel Qty.+ HD Live Channel Qty.>0, SD
Unicast Concurrent Ratio* SD Coding Rate（ Mbps）+ HD Unicast
Concurrent Ratio* HD Coding Rate （Mbps）, 0 )
 HMS Need Read Bandwidths(Mbps) =IF( Edge Node registered Subs.
(K)<>0 , Edge Node registered Subs.(K) * 1000 * Ratio of Unicast
Subs.* (SD Unicast Concurrent Ratio* SD Coding Rate（ Mbps） + HD
Unicast Concurrent Ratio* HD Coding Rate （Mbps） ) , 0)
 HMS Need Write Bandwidths(Mbps) = IF( Edge Node registered Subs.
(K)<>0 , MAX (SD TVOD Channel Qty., SD TSTV Channel Qty.) *
SD Coding Rate（ Mbps）+ MAX (HD TVOD Channel Qty., HD TSTV
Channel Qty.) * HD Coding Rate （Mbps） , 0)
5.3.3 Storage Configuration
List: Service Traffic Data assumed by vendor
Dimensi Calculation
Service Name Item
on Result
[Calculation
3164 GB
VOD VOD Storage(G) Result]
[Calculation
9229 GB
SD TVOD SD TVOD Storage(G) Result]
[Calculation
165 GB
SD TSTV SD TSTV Storage(G) Result]
[Calculation
7088 GB
HD TVOD HD TVOD Storage(G) Result]
[Calculation
127 GB
HD TSTV HD TSTV Storage(G) Result]
[Calculation
6993 GB
NPVR Storage NPVR Storage(G) Result]
19480 [Calculation
Storage Requirement(G) Storage Requirement(G) GB Result]

IPTV Platform Edge Node is calculated as below:

 VOD Storage(G) = (SD VOD Content Hours（H）* SD Coding
Rate（ Mbps）+ HD VOD Content Hours* HD Coding Rate
（Mbps） ) *3600/8/1024
 SD TVOD Storage(G) = SD TVOD Channel Qty. * SD TVOD
Hours（H）* SD Coding Rate（ Mbps）*3600/8/1024
 SD TSTV Storage(G) = SD TSTV Channel Qty. * SD TSTV
Hours（H）* SD Coding Rate（ Mbps）*3600/8/1024
 HD TVOD Storage(G) = HD TVOD Channel Qty. * HD TVOD Hours
* HD Coding Rate （Mbps）*3600/8/1024
 HD TSTV Storage(G) =HD TSTV Channel Qty. * HD TSTV
Hours（H） * HD Coding Rate （Mbps）*3600/8/1024
 NPVR Storage(G) = IF (NPVR calculate mode="TVOD Rate", Period
of Reserved NPVR Programs(Days)* (MAX(SD TVOD Channel Qty.,
SD TSTV Channel Qty.)* SD Coding Rate（ Mbps）+MAX(HD TVOD
Channel Qty., HD TSTV Channel Qty.)* HD Coding Rate （Mbps）)
*24*3600 /8/1024,0)
 Storage Requirement(G) =SUM(VOD Storage(G) , MAX(SD
TVOD Storage(G), SD TSTV Storage(G) ) , MAX (HD TVOD
Storage(G), HD TSTV Storage(G) ) , NPVR Storage(G) )
5.4 System Configuration

5.4.1 Configuration detail of Central Node

MEM:
Item Qty. Description Remark
IPTV,TV08MNTU8,Management
Unit,04C-6 Rear GE&2
MGMT/DB/NTP Server Qty. 2 Loopback FC
IPTV,TV08MNTU8,Management
ACS/EDS Server Qty. 4 Unit,04C-2 Rear GE&2 Rear FC
IPTV,TV08EPG16,EPG
EPG Server Qty. 4 Unit,04C-2 Rear GE&2 Rear FC
IPTV,TV08MNTU8,Management
UPG Server Qty. 2 Unit,04C-2 Rear GE&2 Rear FC
300GB According to different
model of Storage,
means S2300(4G) or
MEM DB Storage(Disks Qty.) 4 S2300(8G) or DX80

MDN:
Item Qty. Description Remark
ATAE,GS38DB8,Database
Process Cell,04C-6 Rear GE&2
MC/UoA/DBU Server Qty. 2 Loopback FC
IPTV,TV08MNTU8,Managemen
t Unit,04C-2 Rear GE&2 Rear
MMU Server Qty. 2 FC
IPTV,TV08MNTU8,Managemen
t Unit,04C-2 Rear GE&2 Rear
CDNC/CC Server Qty. 2 FC
IPTV,TV08MNTU8,Managemen
t Unit,04C-2 Rear GE&2 Rear
UMU Server Qty. 2 FC
IPTV,TV08MSU16,MS
NVOD Server Qty. 2 Unit,04C-6GE&Rear 2FC
IPTV,TV08MSU16,MS
FCC 2 Unit,04C-8GE
 IPTV,TV08MSU16,MS
MRF 2 Unit,04C-8GE
IPTV,TV08MSU16,MS
HMU 7 Unit,04C-6GE&Rear 2FC
300GB According to different
MDN DB Storage(Disks Qty.)
model of Storage,
4 means S2300(4G) or
S2300(8G) or DX80

S2300(4G) 　

S2300 Storage Rack(24

Harddisks) Qty. -

S2300 Storage Rack(48Harddisks)

Qty. -

S2300 Storage Rack(72

Harddisks) Qty. -

S2300 Storage Rack(96

Harddisks) Qty. -

S2300(8G) 　

Disk
HMS Hard Disk Rack Qty.(24 Array,S2300,24*300G,Dual-
Controller(8GB CaChe),AC,With
Harddisks) 4
Management Software,Without
Service
HMS Hard Disk Rack Qty.(48
Harddisks) -

DX80 　

HMS Hard Disk Rack Qty.(12

Harddisks) -

HMS Hard Disk Rack Qty.(24

Harddisks) -

HMS Hard Disk Rack Qty.(36

Harddisks) -

HMS Hard Disk Rack Qty.(48

Harddisks) -

HMS Hard Disk Rack Qty.(60

Harddisks) -

HMS Hard Disk Rack Qty.(72

Harddisks) -

HMS Hard Disk Rack Qty.(84

Harddisks) -
HMS Hard Disk Rack Qty.(96
Harddisks) -

CMS:
Item Qty. Description Remark
IPTV,TV08MNTU8,Managemen
t Unit,04C-6 Rear GE&2
2
CMS/FTP server Qty. Loopback FC
300GB According to different
model of Storage,
CMS/FTP DB Storage hard disk means S2300(4G) or
quantity (300G) 2 S2300(8G) or DX80

BMS:
Item Qty. Description Remark
IPTV,TV08MNTU8,Managemen
t Unit,04C-6 Rear GE&2
4
CMS/FTP server Qty. Loopback FC
300GB According to different
model of Storage,
CMS/FTP DB Storage hard disk means S2300(4G) or
quantity (300G) 4 S2300(8G) or DX80

Report:
Item Qty. Description Remark
IPTV,TV08MNTU8,Managemen
t Unit,04C-6 Rear GE&2
2
CMS/FTP server Qty. Loopback FC
300GB According to different
model of Storage,
CMS/FTP DB Storage hard disk means S2300(4G) or
quantity (300G) 6 S2300(8G) or DX80

I2000:
Item Qty. Description Remark
CMS/FTP server Qty. iManager
2 I2000,IM07OM8,Operation
 Maintenance Process Cell,04C-
Loopback FC
300GB According to different
model of Storage,
CMS/FTP DB Storage hard disk means S2300(4G) or
quantity (300G) 2 S2300(8G) or DX80

STB TMS:
Item Qty. Description Remark
IPTV,TV08MNTU8,Managemen
t Unit,04C-6 Rear GE&2
BMC/DB/Balance Server Qty. 2 Loopback FC
IPTV,TV08MNTU8,Managemen
t Unit,04C-2 Rear GE&2 Rear
APU server Qty. 2 FC
300GB According to different
model of Storage,
TMS DB hard disk quantity (300G)
2 means S2300(4G) or
S2300(8G) or DX80

TVMS:
Item Qty. Description Remark
IPTV,TV08MNTU8,Managemen Share with CMS
t Unit,04C-6 Rear GE&2 server
TVMS MGMT/DB server Qty. - Loopback FC
IPTV,TV08MNTU8,Managemen
Message Gateway server/Web t Unit,04C-2 Rear GE&2 Rear
server Qty. 2 FC
300GB According to different
model of Storage,
TVMS DB hard disk quantity means S2300(4G) or
(300G) 2 S2300(8G) or DX80

DHCP&SQM:
Item Qty. Description Remark

DHCP server Qty. -

IPTV,TV08MNTU8,Managemen
t Unit,04C-6 Rear GE&2
MQMC server Qty. 2 Loopback FC
 300GB According to different
model of Storage,
MQMC DB hard disk quantity means S2300(4G) or
(300G) 2 S2300(8G) or DX80

Irdeto CA (or Verimatrix with different equipments according to the requirement):

Item Qty. Description Remark
PC Server,IBM X3550M2,Xeon
quad-core5504 2.0GHz or
above,4G(2*2G),No
HDD(2.5"SAS),No
FDD,DVDRW,4*Integrated TOE
1000M NIC,Integrated
ServeRaid M5014 Raidcard,Rack
Model,Eng.
Doc,3Y5*8,100V~240VAC,2*67
Pisys server Qty. 4 5W(1+1),No KVM
Irdeto PIsys Head End Basal Basal Package
Package(0-20000) including 2 Encryptior
Encryptor Qty. 2

Irdeto IPTV Scrambler

Scramblers Qty. 2

Irdeto Pre-encryption Double

Pre-encryption server Qty. 1 Servers
PC Server,IBM X3550M2,Xeon
quad-core5504 2.0GHz or
above,4G(2*2G),No
HDD(2.5"SAS),No
FDD,DVDRW,4*Integrated TOE
1000M NIC,Integrated
ServeRaid M5014 Raidcard,Rack
Model,Eng.
Doc,3Y5*8,100V~240VAC,2*67
SSS Server Qty. 4 5W(1+1),No KVM
PC Server,IBM X3550M2,Xeon
quad-core5504 2.0GHz or
above,4G(2*2G),No
HDD(2.5"SAS),No
FDD,DVDRW,4*Integrated TOE
1000M NIC,Integrated
ServeRaid M5014 Raidcard,Rack
Model,Eng.
Doc,3Y5*8,100V~240VAC,2*67
SPS Serverr Qty. 2 5W(1+1),No KVM

Headend:
Item Qty. Description Remark
 Provided by other
configuration
SD/HD IRD Qty. - document
Provided by other
configuration
Mosaic Qty. - document
Provided by other
configuration
document
Audio Encoder Qty. -

Provided by other
configuration
SD encoder server Qty. - document
Provided by other
configuration
HD encoder server Qty. - document

IPTV DB Storage:
Item Qty. Description Remark
S2300(4G)
300GB According to different
model of Storage,
MEM/MDN/CMS/BMS/Inrpt/I2000/T means S2300(4G) or
MS/TVMS/SQM DB Storage 30 DX80
Disk
Array,S2300,24*300G,Dual-
Controller(4GB Cache),DC,with
S2300 Storage Rack(24 Management Software,Without
Harddisks) Qty. 2 Service
S2300 Storage Rack(48Harddisks)
Qty. -

DX80
MEM/MDN/CMS/BMS/Inrpt/I2000/T
MS/TVMS/SQM DB Storage
DB sharing Data Rack Qty.(12
disks Rack)
DB sharing Data Rack Qty.(24
disks Rack)
300GB According to different
model of Storage,
means S2300(4G) or
- DX80
Disk Array,FUJITSU
DX80,2*300G(15K
SAS)/Increased to 12
Disks,4*4Gb hostinterface with
-
4*5m LC Cable,dual
Controller(4Gb Cache),110/220V
AC,Without Service
-
-
DB sharing Data Rack Qty.(36 -
disks Rack) -

5.4.2 Configuration detail of Edge Node

Item Qty. Description Remark

IPTV,TV08EPG16,EPG
EPG 4 Unit,04C-2 Rear GE&2 Rear FC
IPTV,TV08MSU16,MS
HMU 7 Unit,04C-6GE&Rear 2FC
IPTV,TV08MSU16,MS
FCC 2 Unit,04C-8GE

HMU Storage S2300(4G)

S2300 Storage Rack(24

Harddisks) Qty. -

S2300 Storage Rack(48Harddisks)

Qty. -

S2300 Storage Rack(72

Harddisks) Qty. -

S2300 Storage Rack(96

Harddisks) Qty. -

S2300(4G)

S2300 Storage Rack(24

Harddisks) Qty. -

S2300 Storage Rack(48Harddisks)

Qty. -

S2300 Storage Rack(72

Harddisks) Qty. -

S2300 Storage Rack(96

Harddisks) Qty. -

S2300(8G)

HMS Hard Disk Rack Qty.(24 Disk

Harddisks) 4 Array,S2300,24*300G,Dual-
Controller(8GB CaChe),AC,With
Management Software,Without
 Service

HMS Hard Disk Rack Qty.(48
Harddisks)
Disk
Array,S2300,48*300G,Dual-
Controller(8GB CaChe),AC,With
-
Management Software,Without
Service

DX80 　

HMS Hard Disk Rack Qty.(12
Harddisks)
HMS Hard Disk Rack Qty.(24
Harddisks)
Disk Array,FUJITSU
DX80,2*300G(15K
SAS)/Increased to 12
Disks,4*4Gb hostinterface with
-
4*5m LC Cable,dual
Controller(4Gb Cache),110/220V
AC,Without Service
-
-

HMS Hard Disk Rack Qty.(36

-
Harddisks) -

HMS Hard Disk Rack Qty.(48

-
Harddisks) -

HMS Hard Disk Rack Qty.(60

-
Harddisks) -

HMS Hard Disk Rack Qty.(72

-
Harddisks) -

HMS Hard Disk Rack Qty.(84

-
Harddisks) -

HMS Hard Disk Rack Qty.(96

-
Harddisks) -

5.5 Physical Parameter of Hardware

Heat
Depth Width Height Power dissipation Noise Weight
Item
(mm) (mm) (mm) (W) (BTU/Hour (bels) (Kg)
)
N68E-22 Rack 1000 600 2200 N/A N/A N/A 120
(AC Power
 Heat
Depth Width Height Power dissipation Noise Weight
Item
(mm) (mm) (mm) (W) (BTU/Hour (bels) (Kg)
)
Supply)

N610E-22 Rack
(AC Power 800 600 2200 N/A N/A N/A 180
Supply)
Note: N610E-22 Rack is used for special equipment and the IBM X3550M2
servervs of Irdeto CA.

5.6 Rack layout and footprint

Depth Width Height

Item Qty.
(mm) (mm) (mm)
AC rack X 1000 600 2200
AC rack X 800 600 2200
DC rack X 800 600 2200
Here are some examples of rack layout, please adjust according to the BOQ.

ATAE basic rack (N68E-22)

PDB 2U

Empty Frame 1U
5624 1U
Cable Slot 1U
5624 1U
Cable Slot 1U

S2300 3U

Empty Frame 1U
Empty Frame 1U

S2300 3U

Empty Frame 1U
 Empty Frame 1U
DiskTape 1U

USM 2U

Empty Frame 2U

PDB 2U

Empty Frame 1U
KVM 1U
MRMU 1U
Empty Frame 1U

ATAE 14U

Empty Frame 1U

Empty Frame 2U

Empty Frame 1U

ATAE extend rack (N68E-22)

PDB 2U
Empty Frame 2U

Empty Frame 2U

ATAE 14U

Empty Frame 2U

PDB 2U

Empty Frame 1U
KVM 1U
MRMU 1U
Empty Frame 1U
ATAE 14U
 Empty Frame 2U

Empty Frame 2U

Storage rack (N68E-22)

PDB 2U

Empty Frame 1U
Empty Frame 1U
Empty Frame 1U

S2300 3U

Empty Frame 1U

S2300 3U

Empty Frame 1U

S2300 3U

Empty Frame 1U

S2300 3U

Empty Frame 2U

PDB 2U

Empty Frame 1U
 Empty Frame 1U

S2300 3U

Empty Frame 1U
Empty Frame 1U

S2300 3U

Empty Frame 1U
Empty Frame 1U

S2300 3U

Empty Frame 1U
Empty Frame 1U

S2300 3U

Empty Frame 1U
Empty Frame 1U

Network equipment rack (N68E-22)

PDB 2U

Firewall 3U

Cable Slot 1U

Firewall 3U

Cable Slot 1U
S9303 4U

Cable Slot 1U

S9303 4U

Empty Frame 1U

F5/Lanswitch/Router 3U

Empty Frame 1U

F5/Lanswitch/Router 3U

Empty Frame 1U

F5/Lanswitch/Router 3U

Cable Slot 2U

F5/Lanswitch/Router 3U

Empty Frame 1U

F5/Lanswitch/Router 3U

Empty Frame 1U

F5/Lanswitch/Router 3U
 Empty Frame 1U
Empty Frame 1U

PC server Rack (N610E-22)

blank panel 1U

power distribution
3U
frame

LAN switch 1U
cabling slot 1U
LAN switch 1U
cabling slot 1U

Scramblers Server 3U

cabling slot 1U

Scramblers Server 3U

cabling slot 1U
Encryptor 1U

blank panel 1U

Encryptor 1U

blank panel 1U

Pre-encryption 1U
server
blank panel 1U

Pre-encryption 1U
server
blank panel 1U
KVM switch 1U
KVM 1U
blank panel 1U
Pisys server 1U
blank panel 1U
Pisys server 1U
blank panel 1U
SSS Server 1U
blank panel 1U
SSS Server 1U
blank panel 1U
SPS Server 1U
blank panel 1U
SPS Server 1U

blank panel 4U

Assembling Slide 2U

blank panel 1U
Root support 1U
 6 Integration with existing
system

6.1 The integration with existing CRM/Billing

The BMS (Business Management System) is the component in IPTV platform for
IPTV service management and business logical controlling, will provide interface to
integrate with existing CRM/Billing.
Here now, we assume the following precondition:
 Interface protocol
 The protocol used by the interface is based on the SOAP protocol.
 Responsibility under Magyar Telekom CRM/Billing
 Providing provisioning function for IPTV service
 Providing charging function for IPTV service
 Processing CDR and providing bill of IPTV service
The following figure illustrates the interface between operator’s existing CRM/Billing
to Huawei IPTV Platform.

Figure 1.27 The interface between IPTV platform and CRM/Billing

According the diagram shown above, the blocks in red are the components of BOSS
or OSS provided by Magyar Telekom. The blocks in blue are Huawei IPTV components.
The table below summaries the function of integration of legacy BOSS and IPTV
platform:

Function Systems Interface Description

Type
Product BOSS→ SOAP  Add product
Synchronization IPTV  Modify product
 Del product
 Suspend
product
 Resume
product
Subscriber BOSS → SOAP  Add user
Synchronization IPTV  Del user
 Modify user
info
 Suspend user
 Resume user

Billing BOSS← FTP User settlement

Transaction IPTV bill send to BOSS
Balance Inquiry BOSS ↔ SOAP  For pre-paid
IPTV service
 User financial
balance
synchronization

6.2 The integration with existing IMS CORE

Huawei IPTV can seamlessly evolve to IMS architecture. And so far, Huawei IPTV
platform has integrated with Huawei IMS core to offer blended innovation service.
Huawei IPTV platform is an open architecture which can be fully compliance with
industry standard such as TISPAN and OIPF. All or the external interface to integrate with
IMS core are compliance with the definition of TISPAN.
Meanwhile, to address your concern about close couple with IMS system, Huawei
IPTV platform can support flexible deployment. The team “flexible” means Huawei IPTV
platform support work well independently and work together with IMS core.
 Figure 1.28 Interface between Huawei IPTV and IMS core
The interface between Huawei IPTV platform and IMS core are:
Function Systems Interface Description
Type
Signaling router IMS core  ISC Session and
SCF/SDF(IPTV (SIP/SDP) service controlling
middleware)
User profile IMS core  Sh
synchronization SCF/SDF(IPTV (Diameter)
BMS)
Signaling router IMS core Y2 (SIP/SDP) Session and
MCF(MDN) service controlling
Signaling router IMS core Gm(SIP/SDP) Session and
UE service controlling

6.3 The integration with existing upper-layer

OSS
Huawei EMS (I2000) supports northbound interface to integrate with upper-layer
OSS. It provides data about alarms information to realize one-screen-management. To
integrate with upper-layer OSS, it can be through the following protocols: SNMP, MML,
DB, and FTP.
 The table below briefly introduces the protocols:
Interface Function
SNMP alarm interface Supports the SNMPV1, V2C, and V3 protocols and provides
the following functions:
 Forwarding alarms in real time
 Synchronizing alarms
 Supporting the superior NMS to query for the currently
active fault alarms on the I2000. The currently active fault
alarms refer to the alarms of the following types:
unacknowledged and uncleared, acknowledged and
uncleared.
 Setting the conditions for filtering alarms at different levels.
 Heartbeat mechanism
The SNMP interfaces can monitor the communication
links. The external system can query for and set the
heartbeat period. The I2000 regularly sends heartbeat
messages to the external system.
MML interface Through a database and a man-machine language (MML)
interface, the I2000 provides external systems with
configuration management, performance management, and
fault management.
 The superior NMS can remotely connect with the I2000
database to access the configuration data and
performance data of the I2000.
 Through an MML interface, external systems can obtain
the real-time alarm information forwarded by the I2000,
and query for history alarms and current alarms.
Database interface The superior NMS connects to the I2000 database through the
database interface to obtain the data of the configuration and
performance of the I2000.
FTP interface It is used to transfer the performance data.
 7 IP Network Requirements

7.1 Bearer Network Requirements

7.1.1 Overview
The successful deployment of the IPTV system cannot do without the bearer
network. Furthermore, the audio and video quality of IPTV services relies heavily on the
bearer network. This section mainly lists the service indexes and function requirements
essential for deploying the IPTV system on the bearer network successfully and ensuring
the normal operation of IPTV services; Also the document describes that how to evaluate
and optimize the IP bear network.
The bearer network is required to support IPTV services. To deploy the IPTV system
on the existing bearer network, you need to evaluate the functions, performance, and
indexes of the bearer network.
As the main service provided by the IPTV system, the video service is real-time and
bandwidth-sensitive. Therefore, before deploying the IPTV system, check whether the
existing bearer network meets related requirements. Then deploy the IPTV system based
on the check results. To check whether the bearer network meets the requirements for
deploying the IPTV system, you need to mainly take into account the following aspects:
 QoS
This index is the most basic one for the application of the video service. The index
involves each component of the bearer network, from the core network to the broadband
access devices. It is an index of the service application level. The index is to ensure the
quality of the video service, the main service of the IPTV system, and ensure subscriber
experience.
 Reliability
This index is an advanced service index. As the architecture of the bearer network
becomes more and more complicated, the reliability of the bearer network directly
determines the availability of services. It is risky to deploy the IPTV system on a bearer
network that is unreliable. One cause is that the end-to-end connection cannot be
guaranteed.
 Security
In view of the features of the IPTV system, that is, a large number of IPTV
subscribers, high online rate, and long online duration, you need to assign IP addresses
reasonably and make proper policies during deployment. As one kind of multi-play
service, IPTV services are generally deployed on the same bearer network along with the
high-speed Internet (HSI) and voice over Internet Protocol (VOIP) networks. Therefore,
you need to consider the isolation of the three service networks.
 Performance
This index is mainly used to evaluate the bearer network when you want to deploy
the IPTV system for commercial use. The commercial deployment of the IPTV system
requires high performance of the key components on the bear network to support a large
number of subscribers, channels, and services.
 Function
This index is to measure whether the existing bearer network can meet the
requirements for the basic applications of the IPTV service. It is a mandatory index, and
other indexes are based on this index.

7.1.2 Network QOS Requirements of IPTV

The following table lists the requirements for the bearer network.
Index Category Description Requirement Mandatory Remarks
or not
QoS Bandwidth Standard 2-3 Mbit/s M
definition
High definition 6-8 Mbit/s M

Delay < 400 ms M

Jitter < 50 ms M

Packet loss ratio < 1/1000 M

Packet error ratio < 1/10000 M

Remarks:
M: Mandatory
O: Optional
R: Recommend
 8 Acronyms and Abbreviations

A
AAA Authentication, Authorization, Accounting
AAC Advanced Audio Coding

ACS Application Control Service

AD Advertisement

API Application Program Interface

ARPU Average Revenue Per Subscriber

ASI Asynchronous Serial Interface

ASP Advanced Simple profile

AVC Audio Visual Communication

Ant Antenna

A/D Analogue and Digital Converter

B
BMS Business Support System

BRAS Broadband Remote Access Server

C
CA Conditional Access

CBR Constant Bit Rate

CDN Content Delivery Network

CIS Content Ingestion Service

CMS Content Management System

CP Content Provider;

CSA Canadian Standards Association

D
DAS Direct Attached Storage

Demod Demodulator
DHCP Dynamic Host Configuration Protocol

DNS Domain Name services

DRM Digital Rights Management

DSA Digital Signature Algorithm

DSLAM Digital Subscriber Line Access Multiplexer

DVB Digital Video Broadcasting

DVB-C Digital Video Broadcasting-Cable

DVB-S Digital Video Broadcasting-Satellite

DVB-T Digital video Broadcasting-Terrestrial

E
ECM Entitlement Control Message

ECS Encryption Control Signal

EDS EPG distribute Server

EMC Electromagnetic Compatibility

EMI Electro Magnetic Interference

EMM Entitlement Management Message

EPG Electronic Program Guide

F
FC Fiber Channel

FCC Fast Channel Change

FEC Forward Error Correction

FTP File Transfer Protocol

G
GB Gigabyte

GE Gigabit Ethernet

GPS Global Positioning System

H
HDLC High level Data Link Control

HMS HUAWEI Media Server

HTML Hypertext Markup Language

HTTP Hyper Text Transport Protocol

I
ICMP Internet Control Message Protocol

ICP Internet Content Provider

IDC Internet Data Center

IEC International Electrotechnical Commission

IGMP Internet Group Management Protocol

IP Internet Protocol

IPTV Internet Protocol Television

IRD Integrated Receiver/Descrambler

ISMA Internet Streaming Media Alliance

ISO International Organization for Standardization

J
J2EE Java 2 Platform Enterprise Edition

JPEG Joint Photographic Experts Group

M
MAM Media Assets Management

MDN Media Delivery Network

MIB Management Information Base

MM Media Manager

MPEG Motion Picture Expert Group

MPTS Multi-program transport stream

N
NTP Network Time Protocol

NVOD Near Video on Demand

O
OMC Operation and Maintenance Center

OSS Operation Support System

P
PAL Phase Alternate Line

PES Packetized Elementary Stream

PGM Pragmatic General Multicast

PLTV Pause live TV

PLVOD Pause live VOD

PMS Product Management Service

PPP Point-to-Point Protocol

PPPoE PPP over Ethernet

PS Program Stream

Q
QOS Quality of Service

R
RADIUS Remote Authentication Dial in Subscriber Service

RF Raido Frequency

RFC Request for Comments

RFI Request for Information

RRS Request Routing Server

RTP Real-time Transport Protocol

RTS Real-time Transfer Protocol

RTSP Real-Time Streaming Protocol

S
SCSI Small Computer System Interface

SDI Serial Digital Interface

SDK Software Development Kit

SDH Synchronous Digital Hierarchy

SM Streaming Media

SMS Subscriber Management Service

SNMP Simple Network Management Protocol

SOAP Simple Object Access Protocol

SP Service Provider

STB Set Top Box

Sync Synchronization

T
TCP Transfer Control Protocol

TS Transport Stream

TVOD TV Video On Demand

U
UDP Subscriber Datagram Protocol

UM Usage Mediation

URL Universal Resource Locator

V
VBR Variable Bit Rate

VCDN Virtual Content Delivery Network

VOD Video On Demand

W
W3C World Wide Web Consortium

X
XML Extensible Markup Language