EMBMS Solution V100R001C00 Feature Description

4
eMBMS Solution
V100R001C00
Feature Description

Issue V1.0
Date 2012-03-23

HUAWEI TECHNOLOGIES CO., LTD.

Issue V1.0 (2012-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.
No part of this document may be reproduced or transported in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not
be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all
statements, information, and recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

eMBMS Solution
Feature Description Content

ii

Content
1 Basic Features ................................................................................................................................. 1
1.1 eMBMS Session Establishment ....................................................................................................................... 1
1.2 eMBMS Session Release ................................................................................................................................. 4
1.3 MBSFN Synchronous Transmission ................................................................................................................ 7
1.4 Service Area-Specific Broadcast ...................................................................................................................... 9
1.5 Live TV and Channel-Based Program Subscription ........................................................................................ 9
1.6 Push VOD Recording Services for Home Application and Program-Based Subscription ............................. 15
2 Optional Features ........................................................................................................................ 21
2.1 Live Broadcast for Unencrypted DVB-S Media Flow ................................................................................... 21
2.2 STB Management ........................................................................................................................................... 22
2.3 QoS Monitoring on the STB .......................................................................................................................... 24
3 Acronyms and Abbreviations ................................................................................................... 26

eMBMS Solution
Feature Description 1 Basic Features

1

1 Basic Features
This document describes the features of the evolved multimedia broadcast multicast service
(eMBMS) V100R001C00. This is the first pre-commercial release at solution level.
Table 1-1 lists the relevant products for eMBMS solution V100R001C00.
Table 1-1 Products for eMBMS solution V100R001C00
NE Product
IPTV IPTV Solution
BM-SC UBMC
HSS SAE-HSS
S/P-GW UGW9811
MBMS GW UGW9811
MME USN9810
MCE MCE
eNodeB DBS3900 TD-LTE
Outdoor CPE B222s

An IPTV system involves the following network elements (NEs): business management system (BMS),
content management system (CMS), media delivery network (MDN), Media Entertainment Middleware
(MEM), electronic program guide (EPG), Certificate Authority (CA), Head-end and set-top box (STB).
1.1 eMBMS Session Establishment
Availability
This feature is introduced as of eMBMS V100R001C00, and involves the following NEs:
broadcast/multicast service center (BM-SC), Multimedia Broadcast Multicast Service
gateway (MBMS GW), Media Entertainment Middleware (MME), Multi-cell/multicast
eMBMS Solution

2

Coordination Entity (MCE), E-UTRAN NodeB (eNodeB) and customer premises equipment
(CPE).
Summary
The eMBMS Session establishment is initiated by the BM-SC. The control signaling is
transported to the eNodeB through MBMS GW, MME and MCE in sequence. The data flow
is transported from the BM-SC to the eNodeB through the MBMS GW.
When the eMBMS Session is established, the broadcast data can be transported to the CPE
over the air interface. With this feature, telecom operator's network supports broadcast and
multicast services, easing the tightness of unicast resources required by terminals.
Benefits
This feature enables the eMBMS Session on the existing band of a radio network, helping the
telecom operator to develop multimedia services and improve the network resource usage.
This feature supports eMBMS Session establishment on multiple bands and bandwidth
sharing between multicast and unicast services. This enables dynamic bandwidth adjustment,
reduces the network deployment cost and hence improves spectrum efficiency.
Description
Figure 1-1 shows the Session Start procedure.
eMBMS Solution

3

Figure 1-1 Session Start procedure
1
3
3
4
4
5
5
7
7
8
9
1
11
Session Start
Request
RAR
RAA
Session Start
Response
Session Start
Request
Session Start
Response
Session Start
Request
Session Start
Response
IGMP Report
Scheduling Info
Scheduling Info
Response
MBMS Data
BM-SC MBMS GW MME MCE eNodeB UE
MBSFN Area
Configuration
MBMS Data,
Sync Header
IP Multicast
Package
10
6
2
IGMP Report

The Session Start procedure is as follows:
1. The BM-SC sends a Re-Auth-Request message to the related MBMS GW (which is
confirmed based on the MBMS GW List), and the MBMS GW sends a Re-Auth-Answer
eMBMS Solution

4

message back to the BM-SC. The session is established. The
MBMS-StartStop-Indication contained in the Re-Auth-Request message is "Start."
2. The MBMS GW joins the multicast group using the IGMP report message.
3. The MBMS GW confirms the related MME based on the SAI, and then the session
between the MBMS GW and MME is completed with the Session Start Request and
Session Start Response. The Session Start Request message contains transport network
layer (TNL) information, such as the M1 IP multicast address, GTP-U C-TEID and M1
SSM IP.
4. The MME confirms the related MCE based on the SAI, and then the session between the
MME and MCE is completed with the Session Start Request and Session Start Response.
5. The MCE allocates the physical multicast channels (PMCHs) and logical channel
identifiers (LCIDs), and sends a Session Start Request to the eNodeB (confirmed based
on the SAI). The eNodeB sends Session Start Response back to the MCE. The session is
therefore complete.
6. The eNodeB joins the multicast group by using the IGMP report message.
7. The MCE sends a Scheduling Info message to the related eNodeB (which is confirmed
based on the SAI), and then the eNodeB sends a Scheduling Info Response message
back to the MCE to complete the procedure for reserving air interface resources.
8. The eNodeB sends an MBSFN Area Configuration message to the UE through the
multicast control channel (MCCH) to complete the MBSFN service area configuration
for the UE.
9. After a specified time for delay, the BM-SC encapsulates and sends the MBMS Data and
Sync Header to the MBMS GW.
10. The MBMS GW encapsulates the data sent from the BM-SC into IP multicast packets,
and sends these packets to the eNodeB. The IP multicast packets consist of MBMS Data,
Sync, L4 UDP data and Multicast IP.
11. The eNodeB decapsulates the IP multicast packets, and caches the MBMS Data. It
eventually performs dynamic scheduling based on the Sync information before an MCH
scheduling period (MSP).
Enhancement
None.
Dependency
None.
1.2 eMBMS Session Release
Availability
BM-SC, MBMS GW, MME, MCE, eNodeB and CPE.
eMBMS Solution

5

Summary
The eMBMS Session release is initiated by the BM-SC, and the control signaling is
transported from the BM-SC to the eNodeB through MBMS GW, MME and MCE.
Afterwards the sessions between the BM-SC, MBMS GW and eNodeB will be released.
Benefits
This feature enables the release of the eMBMS Session to save network resources such as
Internet services.
Description
Figure 1-2 shows the Session Stop procedure.
eMBMS Solution

6

Figure 1-2 Session Stop procedure
1
3
3
4
4
7
7
5
5
6
1
Session Stop
Request
RAR
RAA
Session Stop
Response
Session Stop
Request
Session Stop
Response
Session Stop
Request
Session Stop
Response
IGMP Leave
Scheduling Info
Scheduling Info
Response
BM-SC MBMS GW MME MCE eNodeB UE
MBSFN Area
Configuration
8
2
IGMP Leave

The Session Stop procedure is as follows:
1. The BM-SC sends a Re-Auth-Request message to the related MBMS GW (which is
confirmed based on the MBMS GW List), and the MBMS GW sends a Re-Auth-Answer
message back to the BM-SC. The session is then released. The
MBMS-StartStop-Indication contained in the Re-Auth-Request message is "Stop."
2. The MBMS GW quits the multicast group using the IGMP Leave message.
eMBMS Solution

7

3. The MBMS GW sends a Session Stop Request message to the related MME (which is
confirmed based on the SAI), and then the MME sends a Session Stop Response
message back to the MBMS GW. The session is released.
4. The MME sends a Session Stop Request message to the related MCE (confirmed based
on the SAI), and the MCE sends a Session Stop Response message back to the MME.
The session is released.
5. The MCE sends a Scheduling Info message to the related eNodeB (which is confirmed
based on the SAI), and then the eNodeB sends a Scheduling Info Response message
back to the MCE. The procedure for releasing air interface resources is complete.
6. The eNodeB sends an MBSFN Area Configuration message to the UE through the
MCCH to delete the MBSFN service area configuration on the UE.
7. The MCE sends a Session Stop Request to the eNodeB (confirmed based on the SAI),
and the eNodeB sends a Session Stop Response message back to the MCE. The M1
interface is released.
8. The eNodeB quits the multicast group using the IGMP Leave message.
Enhancement
None.
Dependency
None.
1.3 MBSFN Synchronous Transmission
Availability
BM-SC, MCE and eNodeB.
Summary
The BM-SC adds a timestamp into a data packet, and then conveys the packet to the eNodeB
to achieve MBSFN synchronous transmission.
According to the timestamp within the received packet, cells of all MBSFN eNodeBs in a
specific service area send the identical radio signal simultaneously. In this case, the MBSFN
signals from different cells combine naturally over the air interface.
Benefits
This feature supports MBSFN signals combination at multiple cell edges, which improves the
SINR at cell edges and the spectrum efficiency, and helps the telecom operators to develop
eMBMS services and increase profits.
eMBMS Solution

8

Description
With MBSFN synchronous transmission technology, different cells may send identical radio
signal simultaneously, and the natural combination of signals helps to enhance the signal to
interference plus noise ratio (SINR) at cell edge and improves the spectrum efficiency.
In Huaweis eMBMS solution, MBSFN synchronous transmission is achieved through the
synchronization of NEs, resources and content.
NE Synchronization
The eNodeB, MCE and BM-SC are synchronized to achieve the following goals:
The synchronization among eNodeBs ensures the time and frequency synchronization
based on the requirements of an LTE TDD system, so that the radio frames between
eNodeBs in the same MBSFN Area are synchronous.
The synchronization between the eNodeB and the MCE ensures the consistency of
MCCH update time, reducing the radio interference during MCCH updating. The
eNodeB obtains the clock signal from GPS, and the MCE obtains the clock signal from
the NTP.
The synchronization between the eNodeB and the BM-SC ensures the consistency of
BM-SC timestamp. The BM-SC obtains the clock signal from the NTP.
Resource Synchronization
Resource synchronization means that the MBMS service data, after being processed in the
same way by layer 1 and layer 2 on the side of the eNodeBs in the MBSFN Area, is mapped
into identical time and frequency resources.
Based on the synchronization among eNodeBs, the MCE synchronizes the resources of the
PMCH level or higher levels, such as MBSFN subframes, modulation and coding scheme
(MCSs), MBSFN Area Ids; the eNodeB synchronizes the resources for sessions in the PMCH.
Content Synchronization
The content synchronization means that the same MBMS service contents are sent by
eNodeBs in the MBSFN Area simultaneously.
The content synchronization is achieved in compliance with the Sync protocol, which ensures
that the eNodeB and the BM-SC have the consistency of the Sync Period and Sync Sequence.
The Sync protocol applies between the BM-SC and eNodeB. The BM-SC give a Timestamp
for each packet, and the eNodeB schedules the packets according to the Timestamp on them
to ensure that the same packets are distributed simultaneously.
Enhancement
None.
Dependency
None.
eMBMS Solution

9

1.4 Service Area-Specific Broadcast
Availability
This feature is introduced in eMBMS V100R001C00, and involves the following NEs:
BM-SC, MBMS GW, MME, MCE and eNodeB.
Summary
An eMBMS Session can be defined for a unique service area (SA), and an SA has a unique
service area identifier (SAI) list. The data broadcast in one SA and another SA could be
different. Therefore thesubscribers in different SAs can enjoy data services of different
contents and then the differentiated data service among SAs are able to meet.
Benefits
This feature enables the telecom operators to provide different content in different SAs to
meet various requirements of subscribers. Therefore, the telecom operators can attract more
subscribers and extend their market shares.
Description
The entire network coverage area is divided into several MBMS SAs, each identified by an
MBMS service area identifier (SAI). The service area-specific broadcast is achieved by
configuring the mappings between parameters on the BM-SC, MME, MCE and eNodeB, for
instance, the mapping between the MBMS SAI and the MBMS GW List, MME, and cell or
eNodeB.
When publishing services, the operation and maintenance (O&M) personnel selects MBMS
service areas using MBMS SAIs to specify the range for eMBMS broadcasting services.
Enhancement
None.
Dependency
None.
1.5 Live TV and Channel-Based Program Subscription
Availability
IPTV system, eMBMS bearer and STB.
Summary
Live TV is a type of service implemented by data transmission over the eMBMS bearer. The
service data is transported end to end from the IPTV system to the STB.
eMBMS Solution

10

This feature supports program subscription based on channels where the charging can be
handled as per time or PPV (Pay Per View)
Benefits
This feature supports charging per time and PPV, which helps telecom operators to attract
more IPTV service subscribers and hence increase revenue.
Description
The signaling procedure of the IPTV Live TV service is shown in Figure 1-3. This
section will elaborate the procedures of channel publishing, eMBMS Session start, STB
startup and program-watching.
Figure 1-3 Flowchart of the Live TV service
IPTV STB CPE MME SGW/ PGW MBMS GW BM-SC
CPE access authentication
1. Channel
publishing
2. IPTV data transmission over the eMBMS bearer
3. STB startup
4. Program playing

The CPE access authentication involves the following procedure:
The CPE with an international mobile subscriber identity (IMSI) attaches to the LTE-EPC
network, and then the home subscriber server (HSS) and MME attempt to authenticate it. On
the network side, the CPE can be bound to a UMTS subscriber identity module (USIM) card
to prevent other terminals from accessing the network using this USIM.
The Live TV channel publishing procedure is shown in Figure 1-4.
eMBMS Solution

11

Figure 1-4 Live TV channel publishing flowchart
CMS
MEM MDN
1
Create and submit the
channel metadata.
2
Synchronize the
channel metadata.
3
Store the channel
metadata.
4
Instruct the MDN to create and
distribute the description file.
5
Instruct the HMS to obtain
the multicast data.
6
Query the distribution result.
7
Synchronize the
distribution result.
8
Activate the channel.
9
Synchronize the status of
the channel to be activated.
10
Update the
channel status.

The procedure of Live TV channel publishing is described below:
1. The service operator creates and submits the channel metadata in the CMS.
2. The CMS synchronizes the channel metadata on the MEM.
3. The MEM stores the channel metadata in the database. If channel encryption is required,
the MEM requests CA to encrypt the channel.
4. The CMS instructs the MDN to create and distribute the description file for a live TV
channel.
5. The MDN creates the channel description file, and then instructs the Huawei Media
Server (HMS) to obtain the multicast data.
6. The CMS queries the distribution result on the MDN to obtain the live TV channel
uniform resource locator (URL).
7. The CMS synchronizes the live TV channel URL to the MEM.
8. Service operators submit the command for activating the channel in the CMS.
9. The CMS synchronizes the status of the channel to be activated to the MEM.
10. The MEM activates the channel and updates the channel status.
eMBMS Solution

12

The HMS is used for retransmission (RET).
The procedure of IPTV data transmission over the eMBMS bearer is shown in Figure 1-5.
Figure 1-5 IPTV data transmission over the eMBMS bearer
MME MCE BM-SC MBMS GW CPE eNodeB
3
2
4
Session
completes.
Transfer
multicast data.
Transfer
multicast data.
Transfer
multicast data.
1

The procedure of IPTV data transmission over the eMBMS bearer is as follows:
1. The BM-SC initiates the eMBMS bearer establishment, and the sessions between the
NEs are completed. The NEs include MBMS GW, MME, MCE and eNodeB.
2. After a times expires, the BM-SC obtains the IPTV multicast data flow based on the
multicast address of the channel. Then, the BM-SC sends the data flow to the MBMS
GW.
3. The MBMS GW transfers the multicast data sent from the BM-SC to eNodeBs.
4. The eNodeBs transfer the multicast data sent from the MBMS GW to the CPE, and the
CPE receives all the eMBMS multicast data and waits for the data requests from the
STB.
The STB startup procedure is shown in Figure 1-6.
eMBMS Solution

13

Figure 1-6 STB startup procedure
MEM-ACS EPG MEM-EDS STB CPE
Response
5
5
Response
Request
Authorization
4
Request
Authorization
4
Challenge
3
Login Response
3
Login Request
2
EPG Response
2
EPG Request
1
DHCP Request
1
DHCP Offer
5

The STB startup procedure is described as follows:
1. After being powered on, the STB obtains an address from the CPE using the DHCP
mechanism. (The STB is explicitly connected to the CPE).
2. The STB connects to the MEM-EDS to obtain the electronic program guide (EPG)
address.
3. The STB logs on to the EPG authentication page using an account and password.
4. The EPG sends a Challenge to the STB. The STB receives the Challenge and requests
authentication from the EPG.
eMBMS Solution

14

5. The EPG sends the authentication request to the MEM-ACS, and then returns the
authentication result to the STB. After that, the EPG home page is shown to the
subscribers.
The procedure for playing a program is shown in Figure 1-7.
Figure 1-7 Procedure for playing a program
1
Get channel list
1
Response
2
IGMP Join
2
Multicast data transfer
STB CPE EPG

The procedure of program playing is as follows:
1. The STB is powered on and authenticated, and then requests the channel list from the
EPG.
2. The STB checks the multicast address returned by the EPG. Then the STB sends an
IGMP v2 request to the CPE, joins the CPE multicast, and obtains the source multicast
data of the program. The CPE obtains all the multicast data through the eMBMS air
interface, and sends only the data of one channel to the STB based on its request.
Enhancement
None.
Dependency
This feature depends on the features described in section 1.1 eMBMS Session Establishment",
section 1.2 "eMBMS Session Release", section 1.3 "MBSFN Synchronous Transmission" and
section 1.4 "Service Area-Specific Broadcast".
This feature also depends on the Live TV feature of the IPTV solution and the CPE's
capability in supporting eMBMS multicast flow transmission.
eMBMS Solution

15

1.6 Push VOD Recording Services for Home Application
and Program-Based Subscription
Availability
IPTV system, eMBMS bearer and STB.
Summary
Push VOD is a type of service implemented by data transmission over the eMBMS bearer.
The service data is transported from the IPTV system to the STB through the eMBMS bearer.
The STB receives and records the service data, and then decrypts the data into a TV program
for subscribers to watch.
With this feature, the subscriber can pay the program by time or by view times. . For instance,
after a successful subscription, the program will be free to view by the subscriber within
defined duration. However if the time expires, the subscriber has to re-subscribe it.

Benefits
This feature enables program pushing and recording. With this feature, subscribers can enjoy
high-definition videos that cannot be supported by the LTE network bandwidth, and the
telecom operators can utilize radio resources more efficiently by reducing the resources used
for subscribing VOD programs. In addition, this feature supports multiple charging patterns,
bringing larger profits for the telecom operators.
With this feature, subscribers can watch a recorded VOD program anytime, and they can also
pause, fast forward, and fast rewind the program, and jump to any desired point during the
progress.
Description
The telecom operator provides the NVOD channel for local program recording. The STB
records a program on the NVOD program list, and shows the recorded program to the
subscriber. The subscriber can order and watch it. The program, if not successfully recorded,
can be recorded for the next time via NVOD channel.
The procedure of the IPTV Push VOD service carried on the eMBMS bearer is shown in
Figure 1-8.
eMBMS Solution

16

Figure 1-8 Procedure of the IPTV Push VOD service
IPTV STB CPE MME SGW/ PGW MBMS GW BM-SC
CPE access authentication
1. Channel
publishing
2. IPTV data transmission over the eMBMS bearer
3. STB startup
4. Program recording
5. Program playing

The IPTV data transmission over the eMBMS bearer and the STB startup for the IPTV Push
VOD and IPTV Live TV services are almost the same. This section elaborates the procedures
of channel publishing, program recording and program playing.
The procedure of channel publishing is shown in Figure 1-9.
eMBMS Solution

17

Figure 1-9 Procedure of channel publishing
CMS
MEM MDN
1 Create NVOD channel metadata.
1
Synchronize NVOD channel metadata.
1
Store the metadata
in the database.
2
Instruct the MDN to define
the NVOD channel.
3
Transmit the program list
description file.
4
Query the URL of the NVOD channel.
3
Distribute the program list
description file to the HMS.
5
Synchronize the querying result.
Initiate the NVOD channel.
Instruct the MDN to initiate
the NVOD channel.
6 Initiate the NVOD channel.
Activate the NVOD channel.
Instruct the MEM to activate
the NVOD channel.
Activate the NVOD channel.
6
6
7
7
7

The procedure of channel publishing is as follows:
eMBMS Solution

18

1. The operator creates and submits the NVOD channel metadata and the default program
list in the CMS. The CME synchronizes the NVOD channel metadata on the MEM, and
then the MEM stores the metadata in the database.
2. The CMS sends the MDN a command to define the NVOD channel.
3. The MDN obtains the program list description file from the CMS using the FTP
mechanism, generates the channel description file based on NVOD channel metadata,
and then distributes channel information to the specified edge HMS.
4. The CMS sends the MDN a message to query the distribution result, and obtains the
URL of the NVOD channel.
5. The CMS synchronizes the distribution result on the MEM.
6. The operator initiates the NVOD channel in the CMS, and the CMS instructs the MDN
to initiate the NVOD channel. The CMS cannot use encrypted VOD contents as NVOD
content source.
The MDN informs the HMS to send the unicast program media flow to the NVOD server,
and the NVOD server transforms the unicast flow to the multicast flow and sends the
multicast flow to the Media Relay Function (MRF) server. Then, the MRF server
encapsulates the data into RTP format and sends the RTP packets to the IPTV network.
7. The telecom operator activates the NVOD channel in the CMS, and the CMS instructs
the MEM to activate the NVOD channel. The MEM activates the channel, updates the
channel status and instructs the EPG to update the program list in a timely manner.
The procedure of program recording is shown in Figure 1-10.
Figure 1-10 Program recording procedure
STB
CPE EPG
5
4
3
3
2
1
1
Periodically request the
NVOD program list.
Return the NVOD program list.
Select and record the program.
IGMP Join
Multicast data transfer
Store the recorded program.
Report the recording result.

The procedure of program recording is as follows:
1. The STB periodically requests the NVOD program list from the EPG.
eMBMS Solution

19

2. The STB creates the appointments for recording programs in a sequence based on the
program list.
3. At an appointment time expires, the STB joins the CPE multicast group, receives the
NVOD data from the CPE, and starts to record the program.
4. The recorded contents are stored locally.
5. After the recording is complete, the STB reports the recording result to the EPG.
The procedure of program playing is shown in Figure 1-11.
Figure 1-11 Program playing
STB
EPG MEM
6
5
5
4
4
4
3
2
1
1
Request the play page of the
recorded program.
Return the play page of
the recorded program.
Select the program and
request authentication.
Authentication
Request for ordering.
Return the program list.
Display the ordering page.
Send an ordering request.
Ordering response
Decrypt and play
the program.

The procedure of program playing is as follows:
1. The STB requests the play page of the recorded program from the EPG which displays
the programs that are successfully recorded and are within the valid duration.
2. The subscriber selects the desired program from the list of recorded programs, and the
STB requests authentication from the EPG.
3. The EPG checks whether the subscriber has the rights to play the selected program. If the
subscriber has the rights, go to step 6; otherwise go to step 4.
eMBMS Solution

20

4. The request cannot be authenticated, and the EPG triggers the ordering request. The
MEM returns a program list, and the STB displays the subsciption page.
5. The STB sends an subscription request, and the MEM returns an subscription response.
Then the subscriber confirms the subscription. The subscriber can choose to pay for all
VOD programs for a month or a year, or buy VOD programs in PPV mode.
6. STB decrypts the program locally and plays the program.
Enhancement
None.
Dependency
This feature depends on the features described in section 1.1 "eMBMS Session
Establishment", section 1.2 "eMBMS Session Release", section 1.3 "MBSFN Synchronous
Transmission", and section 1.4 "Service Area-Specific Broadcast".
This feature also depends on the Push VOD feature of the IPTV solution and the CPE's
capability in supporting eMBMS multicast flow transmission.
eMBMS Solution
Feature Description 2 Optional Features

21

2 Optional Features
2.1 Live Broadcast for Unencrypted DVB-S Media Flow
Availability
This feature is introduced as of eMBMS V100R001C00, and only applicable to the STB.
Summary
It is an STB feature.
Benefits
This feature supports multiple DVB-S services, helping the telecom operators to absorb more
subscribers.
Subscribers can use an STB to switch between satellite programs and IPTV programs,
enjoying better experience.
Description
The STB with this function can receive Digital Video Broadcasting-Satellite (DVB-S)
programs, and play the unencrypted live broadcast programs for subscribers to watch. This
feature also supports the switch between satellite mode and IPTV mode.
Enhancement
None.
Dependency
This feature depends on the STB's capability in receiving and playing DVB-S programs.
eMBMS Solution

22

2.2 STB Management
Availability
Summary
This feature helps the telecom operators to manage home-applied STBs remotely using the
terminal management system (TMS), such as monitoring, diagnosing, maintaining,
configuring and collecting statistics for STBs.
Benefits
This feature helps the telecom operators in implementing remote, automatic, and batch
upgrade and management of STBs, and implementing remote analysis, locating and
troubleshooting of STBs.
This feature also helps subscribers in upgrading STBs in real time, troubleshooting STBs in a
timely and effective manner, and experiencing better IPTV services.
Description
This feature supports STB management by the TMS.
The TMS has features such as large management capacity, high security and reliability, high
performance, and powerful integration and extension capability.
Table 2-1 provides the functional specification of the TMS.
Table 2-1 Functional specification of the TMS
Function Description
Monitoring STB
remotely
The operator can monitor STBs remotely on the TMS,
including status monitoring and performance monitoring.

Status monitoring
If the report attribute of the STB is set to the active state, the
STB can actively report the change of its status or parameter
settings 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, the operator can check the status of
media playback performance of the STB on the TMS. The
operator can also be aware of the running status of the STB in a
timely manner according to the performance status of the STB.
Diagnosing STB
remotely
The operator can diagnose STBs remotely on the TMS as
follows:

IP Ping diagnosis
eMBMS Solution

23

IP Ping is a computer network tool used to test whether data
packets can be successfully transported to a specified host on
an IP network. Through the IP Ping diagnosis, the operator can
properly detect the status of network connections between the
STB and other subsystems of the IPTV.

Trace Route diagnosis
Trace Route is a computer network tool used to verify the
message 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.

Broadcast test
The operator obtains the current status of an STB by using the
broadcast test function of the TMS. The operator can position
STB faults in a timely manner based on this status.
Maintaining STBs
remotely
The operatator can maintain STBs remotely by viewing the
real-time logs and log files on the TMS. The remote
maintenance mainly includes the following items:

Remote restart

Remote restoration of factory settings

Firmware upgrade

Backup and recovery
Configuring STBs You can view and configure the following STB information:

Network configuration
Network configuration covers the IP address, address type,
subnet mask, default gateway, DNS server and MAC address
of the STB.
NOTE
The network configuration information should be read only.

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, bandwidth alarm threshold and packet
loss threshold.
eMBMS Solution

24


TR069 parameter setting
TR069 parameter setting covers the URL, user name, password
and upgrade management.

SQM configuration
SQM configuration covers the SQM listening port and SQM
serving port.
Collecting statistics on
STBs
The operator can generate reports on the STBs in an area on
the TMS. The TMS collects statistics on the following items:

Device deployment statistics

Device registration statistics

Device software version statistics

Device pre-configuration statistics

For details, see IPTV Solution TMS Feature Description-(V100R003C28_01).
Enhancement
None.
Dependency
This feature depends on TMS feature deployment of the IPTV solution, and the CPE's
capability on supporting TR111 PART2 and NAT traversal.
2.3 QoS Monitoring on the STB
Availability
Summary
This feature helps the telecom operators to monitor the STB quality of service (QoS) using the
service quality management (SQM).
By deploying probes for STBs, the SQM supports measurement of QoS and QoE indicators in
each phase of the IPTV lifecycle. Therefore, the device performance can be enhanced
continuously, network accidents can be diagnosed quickly, and faults can be rectified in a
timely manner, which is improving network performance and user experience.
Benefits
This feature enables the telecom operators to:
eMBMS Solution

25

Use quantification to display a subscriber's experience and feeling for video services
through the QoS-QoE association analysis.
Quickly position faults related to video play quality that are reported by subscribers and
find the fault point.
Monitor live TV sources, network links, and the video-play quality of STBs in real time
to detect faults in advance, including even the potential faults.
Monitor the number of subscribers carried by STBs on the entire network in real time
and view real-time status of STBs.
With this feature, the subscribers can:
Enjoy high-quality video with few faults.
Quick response and solution to the reported fault.
Description
The IPTV service depends on the network transmission. HUAWEI SQM monitors the quality
of video transmission over the network and dig out video quality fault.
The SQM deploys probes to collect data, monitor video quality, and isolate faults.
Table 2-2 describes main function of the SQM.
Table 2-2 Main function of the SQM
Monitoring live TV
quality
When creating a live TV quality monitoring task, the operator can
monitor quality of live TV sources across the IPTV network.
Monitoring network
quality
When creating a network quality monitoring task, the operator
can monitor unicast and multicast streams transferred in the IPTV
network.
Monitoring STBs
across the IPTV
network
On the STB monitoring page, the operator can monitor content
quality played by STBs across the network.
Positioning video
faults
If the video faults occur, the SQM can position faults effectively.

For details, see IPTV Solution SQM User Guide-(V100R001C23patch).
Enhancement
None.
Dependency
This feature depends on SQM feature deployment for the IPTV solution, and the CPE's
capability to support UPnP IGD and NAT traversal.
eMBMS Solution
Feature Description 3 Acronyms and Abbreviations

26

3 Acronyms and Abbreviations
A
ACS Auto-Configuration Server
AP Access Point

B
BM-SC Broadcast/Multicast Service Center
BMS Business Management System
BSS Business Support System
BWA Broadband Wireless Access

C
CA Certificate Authority
CAS Conditional Access System
CDN Content Delivery Network
CDR Charging Data Record
CMS Content Management System
CPE Customer Premises Equipment
CRS Cell Reference Signal
C-TEID Common Tunnel End-point IDentifier

D
DHCP Dynamic Host Configuration Protocol
DL DownLink
eMBMS Solution

27

DVB-S Digital Video Broadcasting-Satellite

E
E2E End to End
EDS Electronic program guide Distributing Server
eMBMS Evolved Multimedia Broadcast Multicast Service
eNodeB E-UTRAN NodeB
EPC Evolved Packet Core
EPG Electronic Program Guide
EPS Evolved Packet System
eRAN E-UTRAN RAN

F
FDD Frequency Division Duplex
FTP File Transfer Protocol

G
GTP-U User plane part of GPRS Tunneling Protocol
GW GateWay

H
HMS Huawei Media Server
HSS Home Subscriber Server

I
IMSI International Mobile Subscriber Identity
IGMP Internet Group Management Protocol
IP Internet Protocol
IPsec IP Security
IPTV Internet Protocol TeleVision

L
LCID Logical Channel IDentifier
eMBMS Solution

28

LTE Long Term Evolution

M
M2AP M2 Application Protocol
M3AP M3 Application Protocol
M3AP-ID M3 Application Identifier
MBMS Multimedia Broadcast Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MCCH Multicast Control CHannel
MCE Multi-cell/multicast Coordination Entity
MCH Multicast CHannel
MCS Modulation and Coding Scheme
MDN Media Delivery Network
MEM Media Entertainment Middleware
MME Mobility management entity
MSP MCH Scheduling Period

N
NE Network Element
NAT Network Address Translation
NTP Network Time Protocol
NVOD Near Video On Demand

P
PC Personal Computer
PIM Protocol Independent Multicast
PMCH Physical Multicast CHannel
PPV Pay Per View

R
RB Resource Block
RET RETransmission
eMBMS Solution

29

RSRP Reference Signal Received Power

S
SA Service Area
SAE System Architecture Evolution
SAI Service Area Identifier
SCTP Stream Control Transmission Protocol
SNR Signal-to-Noise Ratio
SSM Source-Specific Multicast
STB Set-Top Box

T
TCP Transmission Control Protocol
TDD Time Division Duplex
TEID Tunnel Endpoint IDentifier
TNL Transport Network Layer
TV TeleVision

U
UDP User Datagram Protocol
UE User Equipment
UGW Unified GateWay
UPnP IGD Universal Plug and Play Internet Gateway Device
URL Uniform Resource Locator
USIM UMTS Subscriber Identity Module

V
VOD Video On Demand

EMBMS Solution V100R001C00 Feature Description

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

EMBMS Solution V100R001C00 Feature Description

Hochgeladen von

Copyright:

Verfügbare Formate

4

Das könnte Ihnen auch gefallen