Teleca White Papers

Solution area: e-MBMS in LTE

Increasing broadcast and multicast service capacity and quality using LTE and MBMS
W I T H T H E I N T R O D U C T I O N O F L O N G T E R M E V O L U T I O N ( LT E ) , T H E 4 G T E C H N O L O G Y G I A N T, M B M S H A S B E C O M E A N AT T R A C T I V E O P T I O N F O R O P E R ATO R S W H O WA N T TO I N C R E A S E B A N D W I D T H C A PA C I T Y A N D I M P R O V E S E RV I C E Q U A L I T Y W I T H O U T H AV I N G TO M A K E A C O S T LY I N V E S T M E N T I N R E C E I V E R H A R D WA R E O R N E T W O R K I N F R A S T R U C T U R E . I N T H I S W H I T E PA P E R , W E E X P L O R E T H E T E C H N O L O G Y A N D D E M O N S T R AT E WAY S I N W H I C H I T M E E T S T H E N E E D S O F TO D AY S B R O A D C A S T A N D M U LT I C A S T S E RV I C E P R O V I D E R S .

Introduction
Many operators have already launched mobile TV services to their subscribers for watching television on their mobile devices. Operators are currently using the streaming option over pointto-point connections for their mobile TV services. Unfortunately this point-to-point streaming option is limited when deploying any mass media services, including mobile TV, in a very large-scale market. This led both the 3rd Generation Partnership Project (3GPP) and the 3GPP2 working groups to kickstart the work item on Broadcast/Multicast technology. The 3GPP named the work item as MBMS (Multimedia Broadcast Multicast Services) and 3GPP2 named the work group as BCMCS (Broadcast Multicast Service) MBMS introduces point to multipoint communication where data packets are simultaneously transmitted from a single source to multiple destinations. The term Broadcast here refers to the normal transmission of content such as TV services and radio services. Multicast refers to transmission of content to a specific group of users: for example, a group of shareholders watching stock activity. A multicast-enabled network ensures that the content is solely distributed over those links that are serving receivers belonging to the corresponding multicast group. This makes MBMS a very resource-efficient way of delivering services to larger user groups.

Santhanaraj Muthusamy February 2011

TELECA WHITE PAPER

e - M B M S i n LT E

Why MBMS? At present, mobile TV services are delivered over point-to-point connections. As a consequence, a content server that delivers content to several users at a time must establish and maintain a separate point-to-point connection for each recipient. This approach works well for low to moderate numbers of subscribers, but does not scale well as the number of subscribers increases. Imagine, for instance, a popular ringtone service that synchronizes a list of top five ringtones in a users phone. Further, let us assume that 50,000 users subscribe to the service and each user connects at an average wireless link speed of 128Kbps, and that each music file is approximately 3MB in size. Each time a new title enters the top-five list it must be delivered to all 50,000 subscribers. Assuming the content server can handle only 1,000 parallel connections at a time, it will take more than 2.5 hours to deliver one ringtone to all 50,000 users. During this period, the server will generate continuous 128Mbps outgoing traffic. Note also that 50,000 subscribers is a relatively small number compared to the total market of potential subscribers per operator. Next consider how much capacity will be consumed by real-time services such as mobile TV. In this case, serializing will not work. Instead, a mobile TV service with 50,000 subscribers requires a server farm that can handle 50,000 simultaneous connections. Although this is technically possible, it is not an economical solution. Furthermore, the service would generate a tremendous amount of outbound traffic when many subscribers use it at the same time. Because spectrum is a limited and expensive resource, the radio access network in particular, the wireless link can also easily become a bottleneck if numerous recipients of the same service are located in the same cell. Imagine, for example, a soccer stadium where fans use their mobile phones to monitor parallel games, much the same way they currently use transistor radios. In this case, the use of point-to-point radio bearers would be very inefficient, if not prohibitive. Therefore, there is a clear need for new point-to-multipoint radio bearers that can support broadcast/multicast services more efficiently.

MBMS in GPRS/EDGE In GSM systems, MBMS uses GPRS and EDGE modulation and coding schemes (that is, CS1-4 and MCS1-9). MBMS also uses the GPRS and EDGE packet data channel (PDCH) for point-to-multipoint transmissions, and the Radio Link Control/Medium Access control (RLC/MAC) protocols on layer 2. As for point-to-point transmissions, MBMS also supports multi-slot operation. In this case, the radio network may use up to four timeslots per MBMS session. Early simulations have shown that the per-

TELECA WHITE PAPER

e - M B M S i n LT E

formance of a straightforward MBMS bearer implementation is not satisfactory. Therefore, to increase performance, two enhancements have been introduced: 1. RLC/MAC with automatic repeat request (ARQ): also called packet downlink Ack/Nack (PDAN) mode. In this mode, session feedback is provided from up to 16 terminals in a given cell. This way, the RLC data blocks that a terminal did not receive correctly are rebroadcasted over the MBMS radio bearer so that the terminal can use incremental redundancy techniques. 2. RLC/MAC without ARQ: also called blind repetition mode. In this mode, RLC blocks are repeated a pre-defined number of times, using an incremental redundancy technique, before the next RLC block is sent. MBMS terminals will probably be based on existing EDGE hardware, with a software update to support MBMS signaling procedures. In GSM, MBMS radio bearers can be multiplexed with GPRS/ EDGE data flows, even on the same timeslots. One deployment scenario might be to activate MBMS in dense areas where EDGE is deployed: in areas without EDGE, MBMS can be provided over pointto-point GPRS. One other deployment scenario might entail phasing in levels of functionality: for example, starting with MBMS broadcast and adding MBMS multicast. This would save capacity in cells that do not have users asking for the service.

MBMS in WCDMA In WCDMA, MBMS reuses existing logical and physical channels to the greatest possible extent. In fact, the implementation in WCDMA requires only three new logical channels and one new physical channel. The new logical channels are: An MBMS point-to-multipoint control channel (MCCH), which contains details concerning ongoing and upcoming MBMS sessions; An MBMS point-to-multipoint scheduling channel (MSCH), which provides information on data scheduled on MTCH; and An MBMS point-to-multipoint traffic channel (MTCH), which carries the actual MBMS application data. The new physical channel is the MBMS notification indicator channel (MICH) by which the network informs terminals of available MBMS information on MCCH. An important characteristic of MBMS in WCDMA is that the MBMS radio transmission cost is independent of the number of subscribers

TELECA WHITE PAPER

e - M B M S i n LT E

in the cell. With WCDMA MBMS technology (3GPP Rel-6), one 5MHz cell carrier can potentially support 16 point-to-multipoint MBMS channels at a user bit rate of 64Kbps per channel, for a singlereceive-antenna terminal. One important aspect of MBMS is flexibility. MBMS can be set to use only a portion of a cell carrier, leaving the rest for other services such as regular voice and data. The MBMS portion comprises a variable number of MBMS radio bearers. Moreover, each radio bearer can have a different bit rate. Although MBMS supports user bit rates of up to 256Kbps, given current handheld terminal display sizes and resolutions, 64Kbps is adequate for a news channel application and 128Kbps for a sports channel application.

Introduction of IMB Integrated Mobile Broadcast (IMB) is a part of 3GPPs Release 8 standard, providing capabilities for broadcast services similar to the broadcast element of MBMS in 3G TDD bands. In some markets, the demand for linear TV, video and other non-linear multimedia content is increasing rapidly. At the same time, most operators are seeing huge growth in wireless broadband, which will soon lead to congestion in their 3G networks. Because of this, mobile network operators are considering the deployment of a broadcast-capable mobile technology to alleviate emerging capacity constraints. IMB can be used to enable broadcast transmission using TDD spectrum allocations that are already held by many operators that have 3G licenses. IMB is a technology, defined as a part of the 3GPP Release 8 standard, which enables spectrally-efficient delivery of broadcast services using TDD radio techniques. This is achieved using technical specifications that are greatly aligned with existing FDD WCDMA unicast technology, which in turn allows for smooth handover between IMB delivery and unicast. One of the key advantages of IMB is that it can be deployed within unpaired TDD spectrum bands held by operators in some parts of the world. To date, TDD spectrum has been largely unused by these operators. IMB can offer capacity relief to the FDD channels by allowing TDD spectrum to be used for the deployment of broadcast applications. Support for existing Rel. 7 MBSFN and other TDD services has been incorporated within IMB through the reuse of the definitions of TDM pilots used in FDD MBMS frame and slot structure. This results in the increased spectral efficiency of MBMS services and a reduction in the functional complexity in the user terminal, which in turn will result in lower power consumption and extended terminal battery life. IMB may also serve as the basis for the standardisation of eMBMS an evolution of MBMS to be supported over Long Term Evolution (LTE) offering a smooth migration of IMB services towards LTE-based deployments. The key challenge for IMB is the support within

TELECA WHITE PAPER

e - M B M S i n LT E

handsets for both FDD and TDD frequencies, but this is expected to increase as these new services are deployed by operators.

e-MBMS MBMS in LTE Even though MBMS was introduced in Release 6 specifications of 3GPP, trials of MBMS services has been conducted by a small number of operators so far. However, with the introduction of LTE, the giant of 4G technology, MBMS is now an attractive option for operators who finally have enough bandwidth to cope with demand. After deploying LTE, the next logical step, according to most operators roadmaps, is to deploy e-MBMS in their network. An initial LTE design requirement was to support an enhanced version of MBMS compared to UMTS Release 6. The targets included cell-edge spectrum efficiency in an urban or suburban environment of 1 bps/Hz equivalent to the support of at least 16 Mobile TV channels at around 300Kbps per channel in a 5 MHz carrier. This is only achievable by exploiting the special features of the LTE OFDM air interface in a Single Frequency Network mode. It was also recognized that the user experience is not purely determined by the data rate achieved, but also by other factors, such as the interruption time when switching channels. This has implications for the design of the MBMS control signaling, which is also being extensively redesigned for LTE.

e-MBMS- SFN The feature in LTE to exploit the OFDM radio interface to transmit multicast or broadcast data as a multicell transmission over a single-frequency synchronized network is termed as MBSFN: Multimedia Broadcast Single Frequency Network. In MBSFN operation, MBMS data is transmitted simultaneously over the air from multiple, tightly time-synchronized cells. A UE receiver will therefore observe multiple versions of the signal with different delays, due to the multicell transmission. Provided that the transmissions from the multiple cells are sufficiently tightly synchronized for each to arrive at the UE within the cyclic prefix at the start of the symbol, there will be no Inter Symbol Interference (ISI). In effect, this makes the MBSFN transmission appear to a UE as a transmission from a single large cell, and the UE receiver may treat the multicell transmissions in the same way as multipath components of a single-cell transmission without incurring any additional complexity. The UE does not even need to know how many cells are transmitting the signal.

TELECA WHITE PAPER

e - M B M S i n LT E

This Single Frequency Network reception leads to significant improvements in spectral efficiency compared to UMTS Release 6 MBMS, as the MBSFN transmission greatly enhances the Signal to Interference Plus Noise Ratio (SINR). This is especially true at the cell edge, where transmissions which would otherwise have constituted inter-cell interference are translated into useful signal energy hence the received signal power is increased at the same time as the interference power being largely removed.

e-MBMS Definitions MBSFN Synchronization Area An area of the network where all eNodeBs can be synchronized and perform MBSFN transmissions. MBSFN Synchronization Areas are capable of supporting one or more MBSFN Areas. On a given frequency layer, an eNodeB can only belong to one MBSFN Synchronization Area. MBSFN Synchronization Areas are independent from the definition of MBMS Service Areas MBSFN Transmission or a transmission in MBSFN mode A multicast transmission technique realised by transmission of identical waveforms at the same time from multiple cells. An MBSFN transmission from multiple cells within the MBSFN Area is seen as a single transmission by a UE. MBSFN Area An MBSFN Area consists of a group of cells within an MBSFN Synchronization Area of a network, which are coordinated to achieve an MBSFN transmission. Except for the MBSFN Area Reserved Cells, all cells within an MBSFN Area contribute to the MBSFN Transmission and advertise its availability. The UE may only need to consider a subset of the MBSFN areas that are configured: i.e., when it knows which MBSFN area applies for the service(s) it is interested in receiving. MBSFN Area Reserved Cell A cell within a MBSFN Area that does not contribute to the MBSFN transmission. The cell may be allowed to transmit for other services, but only at restricted power on the resource allocated for the MBSFN transmission.

TELECA WHITE PAPER

e - M B M S i n LT E

MBSFN Area Synchronisation SequenceReserved Cell A cell within a MBSFN Area which does not contribute to the MBSFN Each synchronizationThe cell may be allowed to PDU) contains a timestamp that at restricted start Transmission. Protocol Data Unit (SYNC transmit for other services but indicates the power on the resource allocated for the MBSFN transmission. time of the synchronisation sequence. For an MBMS service, each synchronisation sequence has the same duration, which is configured in the BM-SC and the MCE. Synchronisation Sequence Each SYNC PDU contains a time stamp which indicates the start time of the synchronisation sequence. For an MBMS service, each synchronisation sequence has Synchronisation Period the same duration which is configured in the BM-SC and the MCE. The synchronisation period provides the time reference for the indication of the start time of each synSynchronisation Period chronisation sequence. The timestamp provided in each SYNC PDU is a relative value which refers to The synchronisation period provides the time reference for the indication of the start the start time of the synchronisationperiod. The duration ofstamp which is provided in configurable. time of each synchronisation sequence. The time the synchronisation period is each SYNC PDU is a relative value which refers to the start time of the synchronisation period. The duration of the synchronisation period is configurable.

MBMS Service Area

MBSFN Area MBSFN Area

MBSFN Area

MBSFN Area Reserved Cell

e-MBMS Architecture & Protocol The management of both MBMS content and resources will be performed through a Multicell/Multicast Coordination Entity (MCE), as shown in below mentioned MBMS Architecture & Protocol figure. This is a new node designed to coordinate the transmissions from multiple The management of both otherwise be difficult to achieve be performed through a Multicell/Multicells, which would MBMS content and resources will in the flat architecture of LTE. The role of the MCE includes allocating figure below. This is radio node designed by cast Coordination Entity (MCE), as shown in the the time/frequency a new resources usedto coordiall eNodeBs in the MBSFN area, ensuring that the same resource blocks are used nate the transmissions from multiple cells; an undertaking that wouldand decidingdifficult to achieve across the whole MBSFN area for a given service, otherwise be the radio in the configuration (modulation role ofcoding scheme). Thus forthe time/frequency radio flat architecture of LTE. The and the MCE includes allocating MBMS the radio scheduling and configuration roles which are normally the responsibility of the resources used by all eNodeBs in the MBSFN area, ensuring that the same resource blocks are used eNodeBs are instead centralized. across the whole MBSFN area for a given service, and deciding the radio configuration (modulation and coding scheme). Thus, for MBMS, the radio scheduling and configuration roles that are normally the responsibility of the eNodeBs are instead centralized.

5
TELECA WHITE PAPER 8

e - M B M S i n LT E

MME M3 MCE

MBMS GW

M1

M2 eNodeB

An additional logical entity called the MBMS Gateway (MBMS GW) is also defined. It receives userAn additional logical entity called the MBMS Gateway (MBMS GW) is also defined. plane MBMS trafficuser-plane MBMS traffic from the Centre (BM-SC), and, inService Centre It receives from the Broadcast/Multicast Service Broadcast/Multicast contrast to nonMBMS(BM-SC), and, in contrast to non-MBMS traffic, hosts the PDCP layer of the user traffic, hosts the PDCP layer of the user plane for header compression used by MBMS data plane for header compression for MBMS data packets for both multicell and singlepacketscell transmission. Theand single-cell transmission. The MBMS GW then forwardsto the including both multicell MBMS GW then forwards the user-plane traffic the eNodeBs. Each eNodeB hosts the RLC and MAC layers layers the protocol stack, user-plane traffic to the eNodeBs. Each eNodeB hosts the RLC and MAC of theofprotocol stack, including the segmentation and reassembly functions. The other functions which including the segmentation and reassembly functions. The other functions which remain to be hosted remain to be hosted by the eNodeB for MBMS mainly relate to single-cell MBMS by the eNodeB for MBMS mainly relate to single-cell MBMS operation. operation.

The interfaces between the MBMS logical network entities are as follows: M1 interface the MBMS logical eNodeB): A pure user plane The interfaces between (MBMS GW network entities are as follows: interface, no control plane application part is defined for this interface and IP multicast is used for pointto-multipoint delivery of user packets for both single cell and multicell transmission. The SYNC protocol is used to ensure that content control plane application part is M1 interface (MBMS GW eNodeB): A pure user plane interface, no is synchronized for multicell MBSFN transmission. This carries additional information which enables eNodeBs to definedidentify interface and IP multicast is and to detect packet loss.deliverystringent timing for this the radio frame timing used for point-to-multipoint The of user packets for requirements of the SYNC protocol would not is used eNodeBs which only both single-cell and multicell transmission. The SYNC protocol apply to ensure that content is syntransmit MBMS in single cell mode. chronized for multicell MBSFN transmission. This carries additional information which enables
eNodeBs tointerface (MCE frame timing andpure control-plane interface which conveys the M2 identify the radio eNodeB): A to detect packet loss. The stringent timing requirements session control signalling to to eNodeB, adding the necessary radio configuration of the SYNC protocol would not applythe eNodeBs, which only transmit MBMS in single-cell mode. data for multicell MBSFN transmission. This additional radio configuration data ensures that the RLC/MAC entities located in the eNodeB are configured appropriately and consistently in order to deliver synchronized content. The signalM2 interface (MCE eNodeB): A pure control-plane interface that conveys the session control SCTP protocol is used over the M3 interface to carry the application part. ing to the eNodeB, adding the necessary radio configuration data for multicell MBSFN transmission.

M3 interface (MCE MBMS GW): A pure control plane-interface that carries the This additional radio configuration data ensures that the RLC/MAC entities located in the eNodeB are session control signalling on the SAE bearer level, including MBMS Session Start configured appropriately and consistently in order to deliver synchronized content. The SCTP protocol and Session Stop messages. The Session Start message provides the information is used necessary for the service (including the part. over the M3 interface to carry the application service area over which to deliver the broadcast transmissions, and relevant QoS parameters). The SCTP protocol is used to carry the application part signalling.The MCE may be deployed as a separate
TELECA WHITE PAPER 9

e - M B M S i n LT E

M3 interface (MCE MBMS GW): A pure control-plane interface that carries the session control signaling on the SAE bearer level, including MBMS Session Start and Session Stop messages. The Session Start message provides the information necessary for the service (including the service area over which to deliver the broadcast transmissions, and relevant QoS parameters). The SCTP protocol is used to carry the application part signaling. The MCE may be deployed as a separate node: alternatively, the M3 interface may be terminated in eNodeBs, in which case the MCE would be considered to be part of an eNodeB and the M2 interface would not exist.

node, alternatively the M3 interface may be terminated in eNodeBs, in which case the MCE would be considered to be part of an eNodeB and the M2 interface would not exist. Deployment consideration
This type of deployment does not preclude the termination of an M3 interface in eNodeBs. In this Deployment consideration case, MCE is considered to be part of eNodeB. However, M2 should exist between the MCE and the It is not precluded that an M3 interface can be terminated in eNodeBs. In this case corresponding eNodeBs. The following figure depicts two potential deployment alternatives. In the MCE is considered as being part of eNodeB. However, M2 should exist between the scenario depicted on the left, MCE is deployed in aThe following In the scenario on theenvisaged is MCE and the corresponding eNodeBs. separate node. figure depicts two right, MCE part of deployment eNodeB. the QoS of alternatives. In the scenario depicted on the left MCE is deployed in a separate node. In the scenario on the right MCE is part of the QoS of eNodeB.

Contents Provider PDN Gateway BMSC

SGmb SG-imb MBMS UP

Contents Provider PDN Gateway BMSC

SGmb SG-imb MBMS UP

MBMS GW

MME

Sm

MBMS CP

MME

Sm

MBMS CP

M3
MCE
F4 F2

M1

M3

M1

M2
eNB eNB
MCE

eNB

MCE

eNB

MBMS Client MBMS Client on mobiles

on mobiles

User Operations The users actions to control MBMS services are defined as following operations UE Power on MBMS client on MBMS service on Broadcast service on Multicast service on MBMS service off TELECA WHITE PAPER Broadcast service off Multicast service off

10

e - M B M S i n LT E

User Operations The users actions to control MBMS services are defined as following operations UE power on MBMS client on MBMS service on Broadcast service on Multicast service on MBMS service off Broadcast service off Multicast service off MBMS client off UE power off

Each operation initiates specific protocol procedures, such as radio channel establishment and service activation, as portrayed in the following figure. Using the GUI of the MBMS client program, a user selects or de-selects a specific MBMS service. The multicast service activation and deactivation requires UE-Network signaling, whereas the broadcast service activation and deactivation needs intra-UE signaling only.

MBMS Control Signaling The 3GPP MBMS specifications do not include interactions between protocol entities in the UE. We design the inter-protocol interactions in the UE. The interactions are implemented with service primitives. The MBMS service primitives TELECA WHITE PAPER protocol entities have several parameters op-type, tmgi and rab-id, between which have values as following. The op-type indicates an MBMS operation, the

11

e - M B M S i n LT E

MBMS Control Signaling The 3GPP MBMS specifications do not include interactions between protocol entities in the UE. We must design the inter-protocol interactions in the UE. The interactions are implemented with service primitives. The MBMS service primitives between protocol entities have several parameters op-type, tmgi and rab-id, which have the following values: the op-type indicates an MBMS operation; the tmgi (temporary mobile group identity) indicates the corresponding MBMS service; and the rab-id indicates the MBMS bearer identifier. - Op-type = {mbms_on, mbms_off, broadcast_act, broadcast_deact, multicast_act, multicast_deact} - Tmgi = service_id + plmn_id - Rab-type = {pdp, mbms}

Service Announcement For a user to receive MBMS services, he or she needs to know in advance which MBMS services the network provides and how to receive them. This kind of information, which is described as as metadata, is structured as shown in the figure below, and is provided via the service announcement procedure. The service announcement can be realized in several ways, such as MBMS, cell broadcast service (CBS), or HTTP. We use an MBMS file download service for the service announcement. Using the MBMS download service, the metadata is broadcast over the entire network periodically. The multicast IP

Meta Data Envelope (*.xml)

User Service Bundle 1. User Service Description

Session Descripti on files

Meta Data Envelope

N.User Service Description

Session Descripti on files

Meta Data Envelope

When a user initiates the MBMS client program, a FLUTE process is created for receiving the service announcement (metadata files). The metadata files are TELECA WHITE PAPER downloaded with the service announcement and downlink packet rate during the

12

e - M B M S i n LT E

address and UDP port number for the service announcement should be predefined and may be broadcast over the network contained in RRC System Information Block (SIB) message. The IP address ff1e :: ff and UDP port 5000 are used in the service announcement. When a user initiates the MBMS client program, a File Delivery over Unidirectional Transport (FLUTE) process is created for receiving the service announcement (metadata files). The metadata files are downloaded with the service announcement and downlink packet rate during the service announcement. On receiving the metadata files, the FLUTE process stores them on the specified directory. The MBMS client program parses the stored metadata files and extracts service information (such as channel name, contents name, and service starting time) and then displays them to the user.

MBMS User Services An MBMS user service is provided with one or more MBMS bearer services. For simplicity, we will only consider an MBMS user service composed of one MBMS bearer service in our example. As the MBMS supports two service modes (multicast and broadcast) and two delivery types (streaming and file download), we compose four MBMS user services. The following table shows the parameters of the MBMS user services.

Service Id 1 2 3 4

Channel Name Multicast Download Multicast Streaming Broadcast Download Broadcast Streaming

IP Address IP...1 IP...2 IP...3 IP...4 ###1 ###2 ###3 ###4

Port

Video Streaming Service When a user selects a video streaming service, a VLC process is created with a multicast IP address and UDP ports specified in the corresponding metadata file. In the 3GPP specification, a maximum 384Kbps data rate is possible for the MBMS. In an operators test-bed, the video streaming service shows data rates of approximately 1Mbps as a result of using Ethernet instead of a radio network between UE and e-NodeB.

TELECA WHITE PAPER

13

e - M B M S i n LT E

File Download Service

File Download Service When a user selects a file download service, a FLUTE process is created with a Whenmulticast IP a file download service, a FLUTE process is created with a multicast IP address a user selects address and UDP ports specified in the corresponding metadata file. The downloaded file contains real-time data written in text, which is displayed on and UDP ports specified in the corresponding metadata file. The downloaded file contains real-time the MBMS client program GUI. The file download service which periodically data written in text, which isfiles periodically MBMS service area shows periodical peak in the broadcast same text displayed on the to the client program GUI. The file download service, packet data rate graph. which periodically broadcasts the same text files to the service area, shows a periodical peak in the packetConclusion: data rate graph.

Studies says that 3GPP e-MBMS is going to play a key role in mobile broadcast and multicast capabilities for mass-market deployment of broadcast like services.OMA standardizes the Broadcast /multicast service layer functions.e-MBMS reuses much of the existing radio and core network protocols. There are no major inclusions or CONCLUSION of new layers in the existing protocol stack. This plays a keyrole in the introduction implementation e-MBMS is going to play a for Mobile terminal vendors and network Studies says that 3GPP cost reduction strategies key role in mobile broadcast and multicast capabilioperators. There are several advantages when compared with non-mobile networks ties for mass-market deployment of broadcast andand additionalservices. The Open Mobile Alliance which require new receiver hardware broadcast-like investments into network infrastructure. Another important advantage is mobile operators can retain their (OMA) has done much to standardize the Broadcast /multicast service layer functions, enabling more business models because of the small size of e-MBMS cells they possess. The seamless communication between functions. The fact that e-MBMS reuses much with very fine radio operators can service customize the broadcasting of different content of the existing granularity in various group a areas. The introduction of e-MBMS will boost the and core network protocols makes forof particularly smooth integration, including no major inclusions capacity of existing services. Mobile broadcast also enables operators to offer or introduction of Internet, andthe existing protocol stack. These economies play a keycommon telephony, new layers in TV for mobile (small handheld) devices over a role in the service and network infrastructure. Finally the vendors MBMS based services implementation cost-reduction strategies for mobile terminal move toand network operators. should deliver a significant enhanced consumer experience both in terms of choice but also in terms of the overall quality of the user experience from fast channel switching through to much higher quality of streamed video. e-MBMS offers operators theapotential to boost the capacity of their existing services and improve
service delivery without making a costly investment. Unlike non-mobile networks, the implementaReferences: tion of 3GPP e-MBMS requires no new receiver hardware or additional investments into network 3GPP TS 36.300 LTE E-UTRAN Overall Description infrastructurea23.246 MBMS Architecture of cost and timeDescription 3GPP TS significant advantage in terms and functional savings. Another important advantage is that3GPP TS 25.346 can retain their business models in spite of the Multicast of e-MBMS cells mobile operators Introduction of the Multimedia Broadcast small size Service (MBMS) in the Radio Access Network they possess. TSaddition, operators canBroadcast Multicast Service (MBMS) in the GERAN fine 3GPP In 43.246 Multimedia customize the broadcasting of different content with very TeliaSonera, Mobile Broadcast/Multicast Service (MBMS), White Paper, August

10
TELECA WHITE PAPER 14

e - M B M S i n LT E

granularity to meet the needs of different sub-groups among their customers. Mobile broadcast also enables operators to offer telephony, Internet, and TV for mobile devices over a common service and network infrastructure. Finally, the move to MBMS-based services should deliver a significantly enhanced consumer experience, both in terms of choice and in terms of the overall quality of the user experience, including fast channel switching and a much higher quality of streamed video.

REFERENCES 3GPP TS 36.300 LTE E-UTRAN Overall Description 3GPP TS 23.246 MBMS Architecture and functional Description 3GPP TS 25.346 Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network 3GPP TS 43.246 Multimedia Broadcast Multicast Service (MBMS) in the GERAN TeliaSonera, Mobile Broadcast/Multicast Service (MBMS), White Paper, August 2004 J. Ogunbekun and A. Mendjeli, MBMS service provision and its challenges, Proc. of the 4th International Conference on 3G Mobile Communication Technologies, pp.128-133, June 2003. A. Boni, E. Launay, T. Mienville, and P. Stuckmann, Multimedia broadcast multicast service - technology overview and service aspects,Proc. of the 5th IEEE International Conference on 3G Mobile Communication Technologies, pp.634-638, 2004

ABBREVIATIONS 3GPP 4G ARQ BCMCS CBS CS EDGE FDD FLUTE GPRS 3 rd Generation Partnership project Fourth Generation Automatic Repeat request Broadcast Multicast service Cell Broadcast Service Coding Scheme Enhanced Data rate for GPRS Evolution Frequency Division Duplex File Delivery over Unidirectional Transport General packet Radio Service

TELECA WHITE PAPER

15

e - M B M S i n LT E

GSM GUI IMB ISI LTE MAC MBMS MBSFN MCE MCS MME OFDM OMA PDAN PDCH PDN QOS RLC SCTP TDD UMTS

Global system for Mobile communication Graphical user Interface Integrated Mobile Broadband Intersymbol Interference Long Term Evolution Medium Access Control Multimedia Broadcast multicast Service Multimedia Broadcast Single Frequency Network Multicast coordination Gateway Modulation and Coding Scheme Mobility Management Entity Orthogonal Frequency Division Multiple Access Open Mobile Alliance Packet data Ack/NAK Packet Data Channel Packet Data Network Quality of Service Radio link control Stream Control Transmission Protocol Time Division Duplex Universal Mobile Telecommunication system

WCDMA Wideband Code Division Multiple Access

TELECA WHITE PAPER

16