Tellabs Integratedmobile Primer

8/10/2019 Tellabs Integratedmobile Primer

1/36

Tellabs

IntegratedMobileSM

Solution: 2G and 3G MobileSolutions for ETSI Markets

tellabs.com


2/36

2 Tellabs IntegratedMobileSM Solution 2G and 3G ETSI Solutions Primer

www.tellabs.com/solutions/integratedmobile/

Foreword ......................................................................................... 3

Executive Summary..........................................................................4

The Evolving Mobile Market ..............................................................4

Evolution of Mobile Data Services .....................................................5

Evolution of the Mobile Network ....................................................... 6

3GPP R99 ................................................................................ 7

3GPP R4....................................................................................8

3GPP R5....................................................................................8

3GPP Future Releases and LTE ................................................... 9

Challenges for Mobile Operators ..................................................... 10

Enabling Cost Reduction by Converging 2G/3G Transport

from Cell Sites to the Core ........................................................ 11

Cell Site Requirements ............................................................. 12

Aggregation Site Requirements .................................................12

RNC Site Requirements ............................................................ 15

Mobile Core Requirements ........................................................ 16

Enabling Cost Savings with Ethernet ......................................... 16

Enabling Microwave Transport Optimization ............................... 18

Enabling Hybrid Transport for Smooth,

Cost-Effective 2G to 3G Migration ............................................. 19

Enabling Technology: A Single End-to-End

Management System for 2G and 3G ..........................................20

Enabling a Forward-Looking RAN for All-IP R6 and LTE .............. 21

Tellabs Mobile Data Network Solutions ............................................22

Service Provisioning and Monitoring with

the Tellabs 8000 Network Manager ..............................................23

Tellabs IntegratedMobileSM Solution Product Portfolio .................... 24

Tellabs 8800 Multiservice Router (MSR) Series ............................. 24

Tellabs 8860 Multiservice Router (MSR) .................................. 25

Tellabs 8840 Multiservice Router ............................................25

Tellabs 8830 Multiservice Router ............................................25

Tellabs 8600 System ...................................................................26

Tellabs 8660 Switch ...............................................................26

Tellabs 8630 Access Switch ................................................... 28

Tellabs 8620 Switch ...............................................................28

Tellabs 8605 Switch ...............................................................29

Tellabs 8100 Managed Access System ..........................................30

Tellabs 6300 Managed Transport System ......................................30

The Tellabs 6325 Edge Node ..................................................30

Tellabs 6340 Switch Node ...................................................... 31



Glossary ....................................................................................... 32


3/36

Foreword

Over the past two decades, mobile service has become one

of the biggest technological success stories in history. That

success can be measured in terms of customers: Today, nearly2.5 billion people worldwide are considered active users of

mobile networks, with more than 2 billion on networks that usethe Global Standard for Mobile communications (GSM) familyof technologies. In some countries, such as Algeria, Argentina,

India, Kenya and Norway, wireless users far outnumberwireline customers, according to the International

Telecommunication Union.1

Third-Generation (3G) wireless is continuing this success. Bythe end of 2006, approximately 167 million people worldwidewill be customers of 3G networks, according to Strategy

Analytics2, an independent research firm. By 2010, the 3Guser base will top 1 billion, the firm forecasts.

3G also is successful from a business perspective. Although

3G users will account for only one-third of all mobile customersby 2010, they will drive more than half of all wireless revenue,according to Strategy Analytics.The firms outlook is based

partly on the upcoming launches of 3G in major markets suchas Brazil, China, India, Pakistan and Russia.

Tellabs IntegratedMobileSM

Solution:2G and 3G Mobile Solutions for ETSI Markets

However, these trends have created challenges for mobile

operators, including fierce competition and margin pressure.These challenges typically are reflected in metrics such asAverage Revenue Per User (ARPU), percentage of customer

turnover (churn) and net additions to the user base (netadds). Mobile operators, investors, press and analysts all

focus on these metrics when assessing the operatorscompetitive position and outlook.

In order to optimize these metrics and improve both theirprofit margins and competitive positions, mobile operators

are increasingly focusing their attention in three areas:

Reduce Capital and Operational Expenses (CapEx and OpEx).

By reducing these overhead costs, operators are betterable to price their products and services competitively yetprofitably. Reduced costs also free up capital to invest in

developing new, market-differentiating products and services.

Improve service quality.High Quality of Service (QoS) isimportant regardless of the target market or demographics,but it is particularly important if the operator targets

enterprises and individual business users. QoS also affectsoverhead costs because when it is poor, the operator hasto spend more to attract and retain customers.

Develop new products and services including a wider range

of content, such as multimedia.A wide range of products

and services, including innovative offerings that rivals cantmatch, positions an operator to compete on something other

than price. Another benefit is that the more ways customershave to communicate, the more they are likely to spend more further improving the operators bottom line.

In addition to these three trends, mobile operators increasinglyare focused on transport, largely because its costs representup to 25 percent of their leased-line OpEx according to a March

2006 report by Heavy Reading,3an independent analyst firm.One way to minimize transport costs while increasing networkflexibility is to use 3G build-outs as an opportunity to build their

own infrastructure and avoid leased-line expenses. At the same

Foreword bySteve McCarthy,Senior Executive Vice President, Tellabs

1www.itu.int/ITU-D/icteye/Reporting/ShowReport.aspx?ReportName=%2FWTI%2FCellularSubscribersPublic&RP_intYear=2005&RP_intLanguageID=1&ShowReport=true

2 www.strategyanalytics.net/default.aspx?mod=ReportAbstractViewer&a0=30553 www.heavyreading.com/details.asp?sku_id=999&skuitem_itemid=880&promo_code=&aff_

code=&next_url=%2Fdefault%2Easp%3F

Tellabs IntegratedMobileSM Solution 2G and 3G ETSI Solutions Primer 3



4/36



time, operators can prepare for migration to a packet-basedarchitecture, which achieves bandwidth savings through

statistical aggregation of non-voice data services.

This migration can be accomplished as slowly or as quickly asthe operator desires. For example, some operators may wish tobegin an aggressive transition to a network based on Internet

Protocol/Multiprotocol Label Switching (IP/MPLS) technology.With IP/MPLS, wireless operators can significantly reduce theirtransport costs and thus improve both their competitive position

and profitability. Other operators may prefer a grow-into-itstrategy where their first step is to establish an infrastructure

of their own to save the leased-line cost and then transition to apacket-centric architecture.

The TellabsIntegratedMobileSMSolution provides operatorswith the flexibility to choose the migration model that best

fits their needs. The Tellabs IntegratedMobile solution alsolets operators leverage Tellabs industry leadership in the

development of IP/MPLS network technology, as well asthe companys 30-plus years of carrier network design,implementation and support experience. Tellabs customer

base shows that the company is widely perceived as a leaderin telecom throughout the world. Customers include Cingular,Verizon Wireless, Vodafone Hungary, Vodacom South Africa,

China Mobile and TeliaSonera.

This primer is designed to educate readers on mobile network

evolution and the challenges mobile operators face, as well asprovide a comprehensive overview of the Tellabs full-servicemobile portfolio. This primer will also illustrate how easilyhigher margins can be realized, how quickly revolutionary new

revenue-generating services can be introduced, and the keybenefits and differentiators of the Tellabs IntegratedMobile solu-tion. Lastly, well demonstrate how the Tellabs IntegratedMobile

solution can empower mobile operators to expand the scope oftheir network while reducing the number and complexity of

network elements and the corresponding OpEx and CapExthat negatively impact profits.

Executive Summary

For mobile operators, the evolution to 3G brings challenges andopportunities. Universal Mobile Telecommunications System

(UMTS), High Speed Downlink Packet Access (HSDPA) andHigh Speed Uplink Packet Access (HSUPA) enable an almost

limitless range of new voice, data and multimedia services,providing operators with additional revenue streams, newmarket differentiators and the opportunity to compete on

services rather than on price alone.

But the evolution to 3G also means increased spending ontransport to accommodate new bandwidth-intensive services.

The evolution also includes a period of at least a few yearswhen operators must support both 2G and 3G customers,services and infrastructure simultaneously. That overlap

increases cost and complexity, which make it difficult formobile operators to price their 2G and 3G servicescompetitively yet profitably.

But savvy mobile operators recognize that these challenges

can be turned into opportunities. For example, by using3G evolution as the opportunity to redesign networks

around a packet-oriented architecture, mobile operatorscan begin reducing overhead costs today while setting the

stage for tomorrows technologies, including IP MultimediaSubsystem (IMS).

The Tellabs IntegratedMobile solution meets these and otherchallenges with a full-service portfolio of products and servicesspecifically designed for the mobile market. This solution

empowers mobile operators to reduce OpEx and CapEx,improve service quality and develop alternative products and

services to deliver exciting new revenue-generating content.The Tellabs Integrated Mobile solution includes industry-leadinghardware, software, engineering and support services that

have been validated time and again in some of the largest carriernetworks in the world. With major deployments in more than

150 mobile networks worldwide, along with strong cooperation

and joint development with leading mobile infrastructurevendors, Tellabs is a leader in the development of mobile

communication technology.

The Evolving Mobile Market

GSM is a dominant, worldwide standard. As of August 2006,more than 2 billion people 29% of the worlds population were customers of GSM-based networks, including UMTS,

according to the GSM Association.4That is approximately 82%of all mobile users, making the GSM family of technologies the

worlds de facto wireless standard.

GSMs customer growth has significantly increased over the

past few years. Although GSM took 12 years to amass 1 billioncustomers by early 2004, it took only 30 months to pass 2

billion by mid-2006.

One drawback to this growth rate and penetration is that somemarkets are becoming saturated. For example, wireless pen-

etration is 91% in Australia and 96% in Germany, according toITU research.5In some countries, such as Singapore, Israel andthe United Kingdom, penetration has hit 100% (see Figure 1).

4www.gsmworld.com/news/statistics/index.shtml5www.itu.int/ITU-D/icteye/Reporting/ShowReport.aspx?ReportName=%2FWTI%2FCellular

SubscribersPublic&RP_intYear=2005&RP_intLanguageID=1&ShowReport=true


5/36



140

120

100

80

60

40

20

0

Penetration%

Country

CAGR% (20002005) 2005 Penetration Rate(Per 100 Inhabitants)

Australia

16

.

6

91

.

39

Singapore

9.

8

103

.

41

HongKong

9.

8

123

.

47

Bahrain

29

.

5

103

.

04

Israel

12

.

0

112

.

42

Germany

10

.

4

95

.

78

UK

8.

9

102

.

16

CzechRepublic

22

.

1

115

.22

Figure 1. Global mobile penetration rates.Source: ITU, 2005.

$180,000

$160,000

$140,000

$120,000

$100,000

$80,000

$60,000

$40,000

$20,000

0

Mi

llions(USD)

Multimedia EntertainmentInformation

201020062005 2007 2008 2009

Figure 2. Worldwide data-oriented mobile revenue.Source: Ovum, 2007.

As a result of this saturation, mobile operators in many parts

of Asia-Pacific, Latin America and Western Europe faceincreasingly fierce competition for existing wireless users.

This competition is exerting significant pressure on key metrics

such as ARPU, churn and net-adds. All else equal, the marketwill trend toward zero growth in ARPU and net-adds, while

churn will grow exponentially.

To escape that situation, mobile operators must reduceoverhead expenses such as transport costs in order toimprove their profitability even as pricing pressure increases.

They also must leverage 3G in order to offer a wider rangeof market-differentiating services and develop new revenue

streams. In fact, technologies such as UMTS could not comeat a better time because by enabling a variety of broadbandservices, 3G gives operators a way to escape the

commoditization of voice.

Evolution of Mobile Data Services

In order to improve both their competitive positions and bottomlines, mobile operators are increasingly focusing development

efforts on applications and services such as real-time multime-dia, full-motion video, high-quality audio, Web browsing, e-mailand instant messaging. These offerings have four key benefits:

Enable new revenue streams and thus offset voice

commoditization

Drive additional revenue, increasing ARPU and

helping make the operator more attractive to investors

Position operators to compete on services ratherthan price alone, thus reducing pressure on margins

Help reduce churn, especially if the applicationsand services are unique or exclusive

Forecasts from analyst firms such as Ovum show a consistent

increase in non-voice mobile revenue, illustrated (see Figure 2).

A key difference between 2G and 3G is that technologiessuch as UMTS and HSDPA enable data services that have amuch larger potential customer base. Speed is one reason for

this difference. For example, traditional data services such asInternet access have not been as popular as hoped because2G and 2.5G technologies such as circuit-switched GSM and

General Packet Radio Service (GPRS) support average speedsof 14.4-57.6 Kbps and peak rates of 115 Kbps. As a result,

these services do not deliver a satisfactory experience in theeyes of many consumers and business users, especially forbandwidth-intensive applications such as large file transfers.

Enhanced Data rates for GSM Evolution (EDGE), a 2G evolu-tion technology, improves the user experience somewhat byproviding peak rates of 473 Kbps,6but its average speeds

of 100 Kbps-130 Kbps7often dont meet the expectationsof todays wireless users.

6 http://3gamericas.org/pdfs/white_papers/2006_Rysavy_Data_Paper_FINAL_09.15.06.pdf7 http://3gamericas.org/pdfs/white_papers/2006_Rysavy_Data_Paper_FINAL_09.15.06.pdf


6/36

36

35

34

33

32

31

30

29

28

27

26

Billion$

Total RAN infrastructure excluding North America

2005 2006 2007 2008 2009 2010

Figure 4. RAN infrastructure investment, excluding North America.Source: Heavy Reading, June 2006.

6 Tellabs IntegratedMobile Solution 2G and 3G ETSI Solutions Primer


Evolution of the Mobile Network

Deploying a 3G Radio Access Network (RAN) is a significantcost. Figure 4 illustrates the increasing investment in RANinfrastructure.

3G RAN deployment directly affects transport requirements,

both in terms of standards and network architecture. Table 1illustrates the evolution of 3GPP transport standards. During

this evolution, which typically lasts several years, dependingon the operator, legacy technologies such as Time DivisionMultiplexing (TDM) and Asynchronous Transfer Mode (ATM)

coexist with IP. For both operators and the 3GPP standards,the evolution culminates with an all-IP mobile network.

Table 1. 3GPP transport specification evolution.

R4 March 2001 2005 ATM/IP packet switchednetwork backbone

R99 March 2000 2003 UTRAN introductionATM aggregation

R5 June 2002 2008 All-IP in RAN and backbone networks all the way to the handset

R6 March 2005 2010 All-IP applications in multi-accessconverged network

Transport Network ImpactTarget VendorAvailability

Date

FreezeDate

3GRelease

14,400

Download&Messagi

ng

WebBrowsi

ng

Vi

deo/Audi

o

Streami

ng

Real-time

Multi

medi

a

2048

DatarateKbps

HSDPA

EV-DO Rev.A

UMTS

EV-DO

3GPP

3GPP2

EDGE

1XRTT

GPRS

18-96

HSC SD

GSM

768

Key

Peak

Typical

384

128

64

28.814.4

2G

9.6

Applicat

ion bandw

idth requ

irements

2.5G

3G

Figure 3. Service and application data for evolving mobile technology.Source: Tellabs, 2007.

8 http://3gamericas.org/pdfs/white_papers/2006_Rysavy_Data_Paper_FINAL_09.15.06.pdf9www.3gpp.org

By comparison, UMTS and HSDPA support average download

speeds of 550 Kbps-800 Kbps8and theoretical peak rates of14.4 Mbps, depending on network configurations. Those rates

enable a good user experience even with bandwidth-intensive

applications such as streaming multimedia, large file transfersand videoconferencing. As a result, 3G lets operators capitalize

on the pent-up demand for mobile broadband services.

Figure 3 illustrates the data rates for each of the ThirdGeneration Partnership Project (3GPP)9network technologies,along with examples of the services they enable.

However, in order to capitalize on the demand for mobile

broadband services, operators must be aware of the expen-ditures required to enable them. Some of these expenses are

obvious, such as UMTS base stations and the mobile packetcore (Serving GPRS Support Node SGSN, Gateway GPRSSupport Node GGSN). Others are less obvious but still have

a major impact, such as deploying a 3G network alongsidethe existing 2G network during an evolution that, for manyoperators, typically lasts several years. The cost of parallel

2G and 3G networks along with the huge increase in 3Gbackhauling capacity compared to 2G requirements can

eat into the profit margins from 3G services. As a result,operators should consider developing and executing a 3Gevolution strategy based on a single, converged network.

This network must be capable of handling both voice anddata, and should be cost-efficient to sustain high-capacity

transport requirements for 3G.


7/36

Tellabs IntegratedMobile Solution 2G and 3G ETSI Solutions Primer 7


BSC

BTS

BTS

BSC

FR

SGSN

GGSN

IP

TDM:E-1

TDMATMIPFR

TDM:Microwave

TDMAccess

Packet-Switched Backbone

Circuit-Switched Network

Base StationSubsystem (BSS)

PSTN/ISDN/PLMN

TDM

TDM

MSCMSC

PublicInternet

CorporateIntranets

Cell

Cell

MediaGateway

MediaGateway

3GPP R99

Initial 3G deployments based on 3GPP Release 99 (R99)

accommodate growth in data services and traffic by replacingthe TDM-based 2G aggregation network with ATM, as illustrated

in Figures 5 and 6. The connection towards the packet corenetwork that were Frame Relay (FR) in 2G are also migratingto ATM under 3G R99 specifications. This change requires

operators to invest in a parallel transport network for 3G.

During the migration to 3G, the biggest changes take placein the RAN, where TDM E-1 connections migrate to ATM E-1connections (see Figure 6). To gain efficiency with ATM traffic,

mobile operators often implement the multiple E-1s from basestations as an Inverse Multiplexing over ATM (IMA) group.

Figure 5. 2G GSM/GPRS network architecture with Frame Relay and TDM.

During the evolution from 2G to 3G R99, some of the network

elements also change in terms of name and function, whileothers are added. Examples include:

The Base Station Subsystem (BSS) becomes the UMTSTerrestrial Radio Access Network (UTRAN), or RAN

The BTS becomes the Node B

The Base Station Controller (BSC) becomes the Radio

Network Controller (RNC)

RNC

Node B

Node B

RNC

ATM

3G-SGSN

GGSN

IP

ATM:nxE-1 IMA

TDMATMIP

ATM:Microwave

ATMAccess


Circuit-Switched Backbone

UTRAN

PSTN/ISDN/PLMN

TDM

ATM

3G-MSC3G-MSC

PublicInternet

CorporateIntranets

Cell

Cell

MediaGateway

MediaGateway

Figure 6. 3GPP R99 network architecture with ATM.


8/36



RNC

Node B

Node B

RNC

IP/ATM

3G-SGSN

GGSN

IP

ATM:nxE-1 IMA

TDMATMIP

ATM:Microwave

ATMAccess


Circuit-Switched Backbone

UTRAN

PSTN/ISDN/PLMN

TDM

ATM

MGWMGW

MSC-SMSC-S

PublicInternet

CorporateIntranets

Cell

Cell

MediaGateway

MediaGateway

applications. This is a major step for the RAN, where multiple

technologies TDM, Frame Relay, ATM and IP mustcoexist. This diversity challenges operators to either build anoverlay network for the Node B-to-RNC connectivity or select

a platform that can handle all the requirements of the evolution.

In the core network, a converged backbone for all mobileservices (IMS) becomes an alternative for operators. Figure 8

illustrates this architecture.

Application servers, defined at the service plane, connect tothe framework through an interface to the control plane. Atthe control plane, the Call Session Control Function (CSCF)

controls session setup, modification and release throughSession Initiation Protocol (SIP). Supporting services at

the control plane include the Media Resource Function(MRF), Media Gateway Control Function (MGCF) and HomeSubscriber Server (HSS). The MRF, composed of a Media

Resource Function Controller (MRFC) and Media ResourceFunction Processor (MRFP), is responsible for defining andcontrolling media stream bearers. The MGCF controls all

signaling functions for external network connectivitythrough the MGW.

Figure 7. 3GPP R4 network architecture.

3GPP R4

3G R99 is followed by 3GPP Release 4 (R4), which begins

to incorporate more IP in the mobile network backbone, asillustrated (see Figure 7). In R4, the RAN remains ATM-centric.

In the R4 network, the traditional Mobile Switching Center(MSC) functions are separated and allocated to the MSC

Server (MSC-S) and the Media Gateway (MGW). The MSC-Sassumes responsibility for all call signaling and control func-

tions, while the MGW performs call transmission and mediaadaptation. In general, the interfaces connecting the MSC-Sand MGW to the mobile network are equivalent to those of the

traditional, monolithic MSC.

3GPP R5

The next iteration, 3GPP Release 5 (R5), also offers an

option of IP in both the access and core network, providinga single converged network for voice and data services and


9/36



TDMATMIP

IP Access

3G-SGSNTDM

GGSN MGW

OperatorsIP Backbone

Mobile Cells

UTRAN

IMS

SIP

SIP

ISUP PSTN/PLMN

PublicInternet

SIP Terminals

CorporateIntranets

Laptop

PDA

Laptop

PDA

Node B

Node B

RNCIP

RNC

Application Environment

MGCFCSCF

Figure 8. 3GPP R5 network architecture.

The HSS maintains the subscriber Home Location Register

(HLR), along with Domain Name System (DNS), security andnetwork access databases. At the core network transportplane, devices such as the MGW, routers and GGSN facilitate

access to the Public Switched Telephone Network (PSTN),core packet backbone and RAN, respectively.

In general, the objective of IMS is to provide a common

framework within the mobile network for enabling andextending multimedia applications to the user in the mostefficient, cost-effective manner possible. The IMS architecture

broadly assumes that all applications and services will beIP-based, including video, audio and any real-time dataapplications. Referred to as IP multimedia applications,

these applications comprise sessions that may be addedor dropped in real time using SIP.

Defined by the transport area working group of the Internet

Engineering Task Force (IETF), SIP has been selected asthe primary signaling protocol for the IMS architecture for itsflexible syntax. Ultimately, SIP, coupled with open settlement

processes, will drive the interconnection and arbitrationbetween mobile and fixed IP networks.

3GPP Future Releases and LTE

Beyond R5, full integration with other wireless technologies

such as WLAN (IEEE 802.11 Wi-Fi), WiMAX (based onIEEE 802.16d and 802.16e) and Mobile Adhoc Networking(MANET)10 will drive future generations of the integrated

mobile network. Some wireline services also will be integratedas part of fixed-mobile convergence, where a common core

handles all types of traffic. Figure 9 illustrates how the topologyof this type of converged networks might look.

3GPP evolution is followed by Long-Term Evolution (LTE),which uses advanced air interface technologies such as

Orthogonal Frequency Division Multiple Access (OFDMA) andSingle Carrier Frequency Division Multiple Access (SC-FDMA)

to peak download rates that are expected to be approximately100 Mbps. LTE generally is considered a 4G technologybecause of its data rates, which meet the ITUs current

definition for 4G, and because it represents a majorevolutionary step beyond 3G technologies such asHSDPA/HSUPA.

10 www.ietf.org/html.charters/manet-charter.html


10/36



LTE currently is under development in standards bodies, withanticipated commercial deployments after 2010. The increasedthroughput will lead to the development of advanced, band-width-intensive services that significantly impact both the RAN

and core network. For example, in LTE, RNC functions aredistributed to the Node Bs. The 3GPP also is considering

bypassing the SGSN in order to eliminate data bottlenecksthere. Figure 10 illustrates LTE logical architecture.

The mobile evolution that is taking place today and throughthe rest of this decade creates several challenges for operators

implementing the transport platform for 3G. The coexistenceof several technologies TDM and Frame Relay for 2G, ATMfor R99 and R4 and the R5-based IP requirement forces

operators to invest in parallel platforms or seek solutions thatsupport all of these technologies simultaneously. The IP-centric

releases R5 and R6 and the bandwidth demands of LTE willcreate additional requirements for transport platforms.

Challenges for Mobile OperatorsThe RAN is an ideal place for mobile operators to reduceoverhead costs. Backhaul/transport spending on leased linesrepresents up to 25 percent of mobile operators OpEx,

according to a March 2006 report by Heavy Reading,11anindependent analyst firm. By building their own infrastructure fully or in partly instead of just leasing capacity, mobile

operators may drastically reduce their OpEx. With a whollyowned end-to-end RAN, network operators need only maintain

their network and not leased lines. Even with a partially ownedsolution in which operators still rely on some leased capacity,introducing aggregation in the packet domain before transport

through the leased capacity may reduce OpEx substantially.

This is especially true as non-voice traffic grows and becomesthe dominating element. In either case, mobile operators can

significantly reduce their transport costs and thus improveboth their competitive positions and profitability.

Based on discussions with mobile operators, Tellabs

estimates that operators outside of North America currentlyspend about 420 Euros ()per month to lease a single E-1 line.A major mobile operator typically has at least 30,000 base

stations, and with most sites currently requiring one to fourE-1s, an operator may spend well over 151 million annuallyon transport leases.

Figure 9. Diversity of access methods in future mobile networks architecture.

MobileTerminals

WLAN

WiMAX etc.

UMTS

IPSGSN GGSN

UTRAN

GERAN

GPRS

IP

IP

IP

OperatorsIP Backbone

Common

IP Network

Operator

Infrastructure

IMS

MobilityServers

ApplicationServers

Call

Servers

ISDNPSTN

GSM

SGSN GGSN

PublicInternet/

Corporate

Intranet

Others

Application

Infrastructure

11 www.heavyreading.com/details.asp?sku_id=999&skuitem_itemid=880&promo_code=&aff_code=&next_url=%2Fdefault%2Easp%3F


11/36



3G LTE E-Node B

Radio Control Featuresembedded in Node B

MMEUPE

3GPP Anchor SAE Anchor

Evolved Packet Core(IP/MPLS)

SGSN 3G HLR/Radius

Database

GW Node

Single E-UTRAN Architecture Application Domain

End-to-End E-UTRAN QoS

Packet-based + CoS aware E-UTRAN

Backhaul Protocols to be Optimised

IMS

Rel 99-R6

Node B

Maximum

100 Mbps

2G BTS

GERAN

UTRAN

Evolved UTRANAll IP

Figure 10. LTE architecture.

However, its important to note that because 3G enablesbandwidth-intensive applications such as streaming multime-dia, mobile operators transport requirements and expenses also will increase over the next few years. If an operator has

to add two or more E-1 lines to each cell site to accommodatedemand for 3G services, transport costs could double or

quadruple.

It is important to note that the addition of one or two E-1 lines isa conservative estimate. According to Heavy Readings report,Carriers are typically basing their initial HSDPA/Evolution Data

Optimised (EV-DO) deployment plans around four T-1/E-1transport circuits per cell site; but as capacity expands, theyare talking about having to support as many as ten such

circuits. So for an operator with 10,000 3G base stations,each served by up to 10 E-1 lines, monthly transport costs

could approach 42 million.

What all these numbers add up to is pressure on profit margins.The following sections discuss mobile operators options forreducing that pressure by leveraging new technologies and

solutions such as the Tellabs IntegratedMobile solution.

Enabling Cost Reduction by Converging 2G/3G Transportfrom Cell Sites to the Core

In 2G and 2.5G, the capacity of a single E-1 always exceededthe capacity of any single radio transceiver, regardless ofwhether it was running GSM or GPRS. With the arrival of 3G

radio technologies such as HSDPA, each Node B transceivercan now support peak subscriber data rates in excess of

3.6 Mbps and eventually more than 10 Mbps. Both are wellbeyond the 2 Mbps capacity of an E-1 line.

Depending on the air interface technologies used, diversetransport technologies may be required. For example, a

GSM-based RAN uses TDM circuits (typically E-1 links), whilea 3GPP R99- and/or R4-based RAN uses ATM. The use ofATM for bandwidth flexibility does not, however, imply any

changes to the fact that transport is still mainly based onnxE-1, now just with ATM cells inside. The Node B is still

equipped with a physical E-1 interface(s), and in the nearfuture an Ethernet interface. Another 3GPP evolutionarystep is support for IP-based transport technologies once

R5, R6 and R7 become available, and the physical transportwill indeed become all-Ethernet based. Eventually Ethernetand IP transport will reduce transport costs and will better

accommodate Ethernet-attached devices should the operatoroffer WLAN or WiMAX services co-located with the Node Bs.


12/36



To accommodate all of these requirements, operators mustconsider a transport network that can accommodate not

only the increased capacity and multiple protocols of 2Gand 3G, but also the unique scalability needs of each partof the network. Connectivity requirements and infrastructure

cost points vary according to the location of the node in thenetwork. To reflect that situation, this chapter divides theRAN into four parts cell sites, aggregation sites, RNC

sites andcore sites and examines the connectivity andfunctionality requirements of each.

Cell Site Requirements

Given the typical distribution of traffic in a mobile network,transport links are frequently underutilized. As a result, leased-

line OpEx is unnecessarily elevated as the operator pays forbandwidth that lays fallow rather than producing revenue.Naturally, if the last mile part of the network belongs to the

operator, the issue is how to most efficiently use that resource.

On the positive side, 3G evolution is an opportunity for wirelessoperators to change their transport technologies and businessmodels. Figure 11 shows one example of how an operator can

use transport consolidation and grooming to reduce the costand complexity of transport for both 2G and 3G networks.

Side A of Figure 11 shows a migration from dedicated E-1sfor 2G and 3G to an optimized and shared E-1 infrastructure.

These changes save either leased-line costs or capacity in

operator-owned networks. Side B of the figure shows theevolution toward Ethernet-based infrastructure, first at thetransport side of the network and later toward the Node Bs.

Provided the operator has got their own fiber all the way to thecell site, the simplest approach is to aggregate the E-1s coming

from both 2G and 3G and backhaul them together. Alternatively,a cell-site node that converts separate traffic types into a com-mon uplink that can be implemented (e.g., with pseudowires)

over a common Layer 2 or Layer 3 (L2/L3) protocol such asATM, Ethernet or IP/MPLS will optimize traffic by eliminating

idle or unused channels, or optionally by overbooking datatraffic. Bandwidth can then be dynamically shared across thetransport between different RAN technologies. This process of

statistically multiplexing the RAN traffic transport significantlyreduces the wireless operators leased-line OpEx.

Operators with 2G networks that continue to have solid growthin terms of customers and revenue should not assume that

they have no immediate need to plan for 3G. Instead, theyshould begin investing in a single platform that will allow them

to accommodate growth or changes in their 2G requirementsand their eventual migration to 3G. For operators with theirown fiber, the simplest way is to add Ethernet interfaces

towards the Node B and carry both 2G and 3G traffic.The ideal long-term platform should support 2G transportoptimization, Abis optimization and 3G transport in a single

device. Over the long term, this strategy provides flexibility

and helps minimize overhead costs.

In summary, mobile operators should look for a cell-siteplatform that provides the following features and benefits:

Service consolidation at the cell site into a single uplink.This approach should:

Support TDM, ATM and Ethernet

Reduce idle traffic to minimize the use of expensive leased lines

Delay capacity upgrades for operator-owned transport

infrastructure, leased lines or radios

Combine 2G and 3G traffic into a single uplink

Decouple the mobile infrastructure from the transport network,

enabling a single transport for multi-vendor environments

Support Abis optimization for 2G traffic together with3G transport requirements to avoid short-term tactical

investments for 2G

Ethernet-based transport

xDSL-based transport

Radio resource sharing

Network management extension all the way to the cell site

in order to simplify operations and provide IP-level accesscontrol

Figure 12 illustrates this architecture.

Aggregation Site Requirements

The cost of transport between Node Bs and RNCs is oftenthe largest portion of the leased line OpEx. There are two mainmethods to optimize your network: build your own network

to eliminate leased-line OpEx completely or apply statisticalaggregation of packet traffic in order to better exploit transportcapacity. An operator can also do a combination of both

methods.

One way to optimize is simply to stop leasing capacity andestablish a transport network of your own, the advantage being

that you are decoupling capacity from cost. This means thereis no longer a need to pay a monthly fee, often proportionalto the bandwidth requested (e.g., the equivalent number of

E-1 leased lines). Scalability then becomes more a matter

of upgrading either the line rate of a Next-Generation Syn-chronous Digital Hierarchy (NG-SDH) transport network oradding another lambda in case of a Wave Division Multiplexing(xWDM)-based solution. As long as the transport solution is

raw bit transport without sophisticated traffic processing orvoice compression techniques, this approach may prove to bevery cost competitive, even if not all capacity is utilized at any

point in time. Aggregation in this case is left to the RNC orRNC front-end device in a centralized aggregation scenario.

This scenario is described in figure 13.


13/36

TellabsIntegratedMobileSMSolution 2G and 3G ETSI Solutions Primer 13


Ethernet

STM-1

Controllers

Controllers

4xE-1

4xE-1

4xE-1

2xE-12G

3G

2G

3G

2G

3G

2G

2xE-1

8605

Controllers

Ethernet

4xE-1

2xE-1

3G

8605

Controllers

Ethernet

2xE-1

2G

3G

8605

Controllers

STM-1

4xE-1

2xE-1

Controllers

Ethernet

Ethernet

Ethernet

2xE-1

2G

3G

A.E-1 Evolution B.Ethernet Evolution

63256325

Figure 11: RAN transport evolution.

Figure 12. Optimized cell-site architecture.

SDH, DWDM, FiberEthernet

IP/MPLSService Core

RNC

SGSN

BSC

PWE3,TE LSP

86608630

8630

ATMBRAS

8660

SDH, DWDM, Fiberthernet

IP/MPLSService Core

RNC

SGSN

PWE3,TE LSP

8660

TMBRAS

8605

8605

8605

8605

8605

8605

Leased lines

Microwave radios

DSL transport

Ethernet

E-1/T-1E-1/T-1

with ATM/IMA

8630


14/36

14 TellabsIntegratedMobileSMSolution 2G and 3G ETSI Solutions Primer


Figure 14. Packet aggregation/hub optimization architecture.

SDH, DWDM, FiberEthernet

IP/MPLSService Core

RNC

SGSN

BSC

PWE3,TE LSP

ATMBRAS

IP/MPLSService Core

RNC

BSC

TMBRAS

86608630

8630

8630

8660

Figure 13. NG-SDH aggregation optimization architecture.

IP/MPLSService Core

RNC

SGSN

BSC

ATMBRAS

E-1/Ethernet backhaul overNG-SDH/CWDM

IP/MPLSService Core

RN

GSN

BSC

RA

6325

6325

6325

6325

8660

Handles IMA offload before the RNCs in order to optimize

RNC utilization and reduce transport needs

Achieves savings in transport with switching and statistical

gain that reduce the transported capacity over leased linksor L1/L2 network

Creates the opportunity to select the optimal transportsolution based on cost and availability, as well as enables:

Enhanced utilization of existing SDH or Ethernet over SDH

(EoSDH) infrastructure

New leased-line alternatives with optimized E-1s, Ethernet

and xDSL transport

The opportunity to use dark fiber

The opportunity to optimize radio infrastructure with statistical

gain and Ethernet support

Enhanced scalability for new broadband services, such as

HSDPA, with packet handling before L1 transport

Another way to optimize these monthly costs, as well as

transport network utilization, is to do packet aggregationcloser to the network edge before the traffic arrives to centrallocations such as RNC sites (see Figure 14). In this approach,

leased or owned transport capacity is made more efficient by

exploiting the fact that most of the packet traffic in 3G is delaytolerant. This results in more efficient bandwidth sharing thanjust adding bandwidth to accommodate peak rates of trafficpotentially generated in each Node B. This approach essen-

tially is a distributed aggregation scenario in which the job ofoptimizing the capacity is done at the network edge.

Distributed aggregation or hub-site strategy architectureprovides several key benefits to operators:

Enhances scalability at the RNC site by moving thelow-capacity port termination away from these crowded

central sites


15/36



New carrier-class protection scenarios, such as Operations

and Maintenance (OAM)-based Label Switched Path (LSP)

1+1 traffic priorities

Common transport infrastructure for all mobile releases

Efficient network operations and management via

end-to-end Network-Management Systems (NMS)

Network convergence with additional services such

as Wi-Fi, WiMAX and IP Television (IPTV) that canbe terminated to a common transport already at

lower parts of the network hierarchy

Figure 14 illustrates this type of aggregation architecture,which optimizes the high-capacity RAN transport.

RNC Site Requirements

The connectivity and functionality requirements of RNC sites

pose several challenges during the migration to 3G. Fortunately,there are many similarities between the existing 2G transport

needs next to the BSC and the new requirements of the RNCfor 3G. For example, mobile operators must overcome RNCunderutilization, enhance scalability and optimize port costs,

an issue that was solved with the TDM cross-connects locatednext to BSCs in 2G.

New challenges brought on by 3G include:

Parallel support of Iub interface optimization between NodeBs and RNCs, and Abis interface optimization between 2Gbase stations and BSCs

Support for ATM switching and IMA offload from RNCs tothe transport elements to increase the number of Node Bs

per RNC

Better scaling for multiple co-located RNCs

At the same time, operators also should be able to optimize the

costs related to the RNCs. For example, to improve scalabilityand lower costs, operators can choose unchannelized STM-1ATM interfaces instead of more expensive channelized STM-1

in RNCs. A common way to overcome these challenges is toallocate an ATM switch or in a design that is more forward-

looking a Multiservice Router (MSR) next to the RNC toadd scalability and optimize the total cost of transport.

The ideal RNC site transmission solution should also be fu-

ture-proof and flexible, support easy operations/maintenance,enable network scalability, support carrier-class protectionscenarios such as MSP 1+1 or Subnetwork Connection

Protection (SNCP) and have the ability to accommodatetraffic between core edge RNC-MGW, SGSN-GGSN, DataCommunication Network (DCN) and core Provider Edge

(PE) routers. Finally, the RNC solution should provide mobileoperators with the ability to optimize costs by choosing thebest transport option, such as expansion of existing SDH

or EoSDH network, metro Ethernet, fiber, Digital SubscriberLine Access Multiplexer (DSLAM) or microwave.

Figure 15 illustrates this type of RNC access architecture.

Operators that prefer a more forward-looking architecture alsoshould consider the technology migration related to 3G whenselecting platforms for RNC sites. In these cases, supportfor future network connectivity has a key role when defining

an RNC site transport solution. The platform should not onlyhandle ATM or E-1 transport requirements, but also help theoperator with a smooth migration toward Ethernet connectivity

and all-IP standards.

IP/MPLSService Core

RNC

SGSN

BSC

ATMBRAS

8660

Backhaul AlternativesLL

2G/3G TDM

MW2G TDM3G ATM

NG-SDH2G TDM

3G TDM/Ethernet

DSL/Ethernet2G TDM/Ethernet3G ATM/Ethernet

New Infra xWDM2G TDM/Ethernet3G ATM/Ethernet

Figure 15. RNC site architecture.


16/36

all-IP network because operators can accommodate legacy

and IP technologies cost-effectively. This approach significantlylowers the operational cost of the core network by collapsing

multiple network elements into one multifunctional platform.It can provide a smooth migration required as the backbonenetworks change from TDM and Frame Relay to ATM and,

ultimately, to IP/MPLS.

Enabling Cost Savings with Ethernet

The growing availability of Ethernet-based transport services

creates a major opportunity for mobile operators to reducetransmission expenses. For example, mobile operators canbuild their own Ethernet backhaul network, or they may

leverage the fact that metro Ethernet networks are already

widely deployed, so mobile operators increasingly have theoption of leasing Ethernet private lines instead of traditionalleased lines. Ethernet interfaces in base station radios allowoperators to allocate bandwidth more flexibly and fully utilize

features such as adaptive modulation. At the same time,Ethernet interfaces are emerging in Node Bs and eventuallyin RNCs.

Mobile Core RequirementsAt the mobile core, all traffic is disaggregated and switched to

the appropriate destination. To perform these functions, a wideselection of network elements is required including, but notlimited to, ATM switches, IP routers and SDH switches. Voice

traffic is directed to the circuit-switched network, while datatraffic is directed to the packet-switched network.

Due to the number of different network interfaces required,

mobile operators may be faced with the relatively high costsassociated with interconnecting the transport, circuit-switched,and packet-switched networks. These costs can be exacerbated

by the high costs of channelized optical facilities and IP-over-ATM core network elements typically found only in a

combination of high-cost routers. The amount of individualhigh-cost network elements can be significantly reduced byusing MSRs, as shown in Figure 16.

By using an MSR that combines the functions of a high-

performance IP/MPLS router and ATM switch, operators canconsolidate multiple network overlays within the core networkto effectively reduce the number of network elements required

to run full-service ATM, Frame Relay and IP networks. Thisflexibility is a major asset during the migration to 3G and an

8830

IP/MPLSBackbone with

IP/MPLS/ATM Tunnels

Operator ApplicationInfrastructure

PublicInternet

Corporate Intranets

MSR

MSR MSR

MSR8840

2G SGSN

3G SGSN

2G MSC

3G MSC-S

TDMATMIP

8860

Network Management Mobility Servers Call Servers HLR Application Servers

8840

Figure 16. Mobile data center and backbone network.




17/36

As a transport technology, Ethernet is expected to have aper-Megabit cost 25-50 percent lower than E-1 lines. However,

many Ethernet transport services currently do not meet thestrict QoS parameters for jitter and latency required by somelegacy RAN technologies. To meet those requirements,

Ethernet transport services must support deterministic QoS.

RAN technologies require TDM-like performance across thetransport network. This performance level can be deliveredusing ATM technology via per session QoS mechanisms that

meet the requirements for service guarantees. ATM providesbandwidth reservation and guarantees delivery of each

session with regard to latency, jitter and availability. Ethernetservices must be able to match these service levels before

mobile operators will adopt them on a widespread basis.

By developing a transport strategy that leverages carrier-

class Ethernet and MPLS, mobile operators can significantlyreduce their overhead costs by reducing their reliance on E-1

lines. By deploying managed, QoS-aware systems betweenNode Bs and RNCs, the transport infrastructure can beoptimized via Ethernet interfaces. Available bandwidth can

be utilized in a more efficient way by allowing overbookingfor data services. Ethernet interfaces can be used to enablenew metro Ethernet services and Ethernet leased lines for

transport. This use of Ethernet transport can further lowerthe RANs total cost by using a single transport network that

carries both fixed and mobile traffic.

The ideal managed edge solution should address synchroniza-tion and service quality management. These abilities are criticalfor making low-cost Ethernet a carrier-class transport alternative

because metro Ethernet deployments typically lack the requiredQoS capabilities, and thus require extensive over-provisioning.

For example, synchronization plays an important role in mobilenetworks because the base stations must be well-synchronized

in order to ensure good voice quality and manage call hand-overs. GSM and Wideband Code Division Multiple Access

(WCDMA) networks typically obtain synchronization with thecell site from the E-1 or T-1 leased line or the microwave linkto which they are connected. When the connectivity is TDM,

synchronization is not an issue. However, when Ethernet isused, timing extraction could be challenging because traditionalEthernet networks do not have the ability to provide a clock-

based signal to a cell site. With NG-SDH based solutions, thisis not an issue since the Ethernet being embedded in a TDM

structure will ensure synchronization throughout the network.

For pure packet networks, standardization bodies are addressingthis issue. Existing options include the IEEEs 1588 Precision

Time Protocol (PTP) and synchronous Ethernet. Optimally,mobile operators should look for a vendor that integratessynchronization standards into their equipments support for

synchronous Ethernet. For example, with Tellabs, synchroniza-tion can be relayed to the cell site by means of adaptive timing,where a TDM interface in the transmission element can obtain

synchronization through a TDM pseudowire. In fact, thetransmission elements are part of the synchronization network,

so it can distribute the clock to other elements in the network.

When a legacy packet network prevents Primary ReferenceClock (PRC) distribution via line signals, packet-based clock

recovery methods must be used. The commonly used methodis adaptive timing, which is typically based on the frequency ofthe received packets. Mobile operators can use adaptive timingover the legacy asynchronous Ethernet network, while in new

parts of the network, synchronous Ethernet can be utilized toconvey the timing reference.

Adaptive timing recovery can be used to provide timing that

is fully compliant with the G.823/G.824 jitter and wanderspecifications. Adaptive timing recovery methods may bevulnerable to any low-frequency components in the Packet-

Switched Network (PSN) packet delay variation, potentiallyresulting from protection switching or extremely slow time scaleload variation in the course of the day. The adaptive clock

recovery method used in the transmission elements can bedesigned to improve wander performance in the presence of

low-frequency components in PSN packet delay variation.




18/36



Adaptive timingfor timing

emulated TDMinterface separately

PRC

8600

AsynchronousMetro Ethernet

8600

8600

8600

8600

As these tables show, the migration from E-1 to Ethernet-based

transport enables operators to either add more capacity to theirnetwork with steady costs or lower the total cost of transportremarkably. This type of cost reduction, which is tied to the

capacity increase generated by 3G data traffic, is a keycomponent in a profitable 3G deployment.

Ethernet support is rapidly becoming a key component of RAN

infrastructure. For example, weve seen an emergence of thefirst Node Bs on the market that have Ethernet interfaces.Meanwhile, in 2007 and 2008, most infrastructure vendors

will add Ethernet support to Node Bs and later to other partsof their product portfolios, such as RNCs. These changes giveoperators more opportunities to begin leveraging Ethernet

throughout their 3G migration.

Figure 17. Adaptive timing recovered for each emulated TDM inter face.

Enabling Microwave Transport Optimization

Most mobile operators use microwave to collect last-mile trafficfrom BTSs. As a result, microwave optimization is an importantrequirement for mobile operators as they migrate to 3G. Like

wired transport technologies, microwave must be scalable inorder to accommodate the bandwidth demands of 3G and, in

the future, LTE.

Figure 17 shows an example of adaptive timing from TDM inter-faces and Figure 18 shows timing distribution via pseudowire.

Once the synchronization problems are solved operators can

fully utilize the cost benefits that Ethernet transport provides.Tables 2, 3 and 4 illustrate the OpEx savings that are achievedwhen E-1 leased lines are converted to Ethernet leased lines.

Table 2 indicates how the cost per bit varies for E-1 andEthernet leased lines while Tables 3 and 4 show the savingsper individual cell sites.

15,000

12,000

3,000

3x E-1 rental

10M Ethernet

1styear savings

25,000

12,000

13,000

5x E-1 rental

10M Ethernet

1styear savings

Table 2. Ethernet and E-1 pricing.

Table 3. Ethernet savings vs. 3 E-1s. Table 4. Ethernet savings vs. 5 E-1s.

Price per Mbit/s/Y

2,500 (100%)

1,200 (48%)

150 (6%)

Annual Rental

5,000

12,000

15,000

Example Pricing

Per E-1 leased line

10M Ethernet line

100M Ethernet line

Solution for

2G+3G

2G+3G

2G+3G


19/36



PRC

Recovered timinginjected to

TDM line signal

8600

SynchronizationPseudowire

AsynchronousMetro Ethernet

8600

8600

8600

8600

Adaptive timingused for timingrecovery from

synchronizationpseudowire

Figure 18. Adaptive timing recovered from synchronization pseudowire.

For example, HSDPAs last-mile capacity requirements will growsteadily through the rest of this decade, from approximately 4Mbps in 2006 to 8 Mbps in 2007 and eventually tens of Mbps.

At the same time, large microwave branches collect traffic from

several Node Bs. With HSDPAs maximum rate of 14.4 Mbps,hops of 126 Mbps are likely, thus requiring significant microwaveoptimization or additional investments to deliver this bandwidth.One way to optimize the radio infrastructure is to use transmission

nodes in large branch sites. This ensures that the capacityrequirements of the radios can be dimensioned based onstatistically multiplexed traffic that takes QoS into account

rather than receiving the full payload for best-effort datafrom each site.

Another way to save CapEx is to use such cell-site aggregatorsin front of the microwave that support both E-1s and Ethernet.

This allows the continued use of E-1 radios that are capableof providing the link capacity necessary to support optimizedtraffic even when the number of best effort E-1s go beyond the

radio link capacity. E-1 radios also can be used when the NodeB is Ethernet by using E-1 uplinks and Multilink Point-to-PointProtocol (MLPPP) toward the radio side and Ethernet toward

the Node B. Similarly, if more capacity is needed at the radio,it can be upgraded to Ethernet even if the Node B side is

E-1-based. For example, pseudowires can be used in thistype of design.

Another consideration is QoS. This can be addressed via

techniques such as adaptive modulation, which adjusts the linkcapacity based on weather and other line-of-sight conditions.For example, during a storm, the link might provide 2 Mbps,but when the weather is clear, adaptive modulation increases

throughput to 10 Mbps. QoS on microwave links is particularlyimportant for voice to ensure that it always has the capacity it

requires to provide a good user experience. Using the stormexample, the network would give voice priority access to the2 Mbps available. Once the weather has cleared and the full

10 Mbps link is available, non-voice traffic is allocated morebandwidth.

Enabling Hybrid Transport for Smooth, Cost-Effective

2G to 3G Migration

Except for greenfield deployments, few mobile operators canmake a business case for replacing their existing transport

network at the beginning of their migration to 3G. Instead, thetransition from legacy transport technologies to an all-IP RAN

may take several years. During this period, the mobile operatormay choose to separate HSDPA and R99 voice traffic at thecell site. The voice traffic can be transported over the legacy

TDM transport network, while HSDPA is routed over a DSLnetwork. One of the existing transport alternatives for data isxDSL, which currently is used primarily for residential data

services.

Many mobile operators are considering or implementing DSLtransport. One example is T-Mobile U.K., which said at a

December 2006 conference:12Everyone is evaluating DSL.Its widely available, and the performance is improving andcan lead to OpEx expansion costs that are up to 80 percent

cheaper [than leased lines].

12www.lightreading.com/document.asp?doc_id=112739


20/36



A hybrid strategy, illustrated in Figure 19, provides mobileoperators with the flexibility necessary to remain competitive

during their migration to 3G. For example, a hybrid strategyallows operators to leverage excess capacity in existing E-1infrastructure for 3G voice traffic while also taking advantage

of the fact that DSL is a viable, highly cost-effective transportsolution for 3G data traffic such as HSDPA.

Table 5 highlights the business case for using xDSL as atransport technology. The savings achieved are critical foroperators because they reduce overhead costs and in turn

improve the operators ability to price its services competitivelyyet profitability. These savings are particularly important for

operators in price-sensitive markets.

Enabling Technology: A Single End-to-End Management

System for 2G and 3G

Integrated provisioning and management simplify day-to-day

operations of a multiservice network. For example, wirelessoperators should seek solutions that provide an end-to-end

view of not only each transport circuit, but also the servicesusing that link. If a transport connection experiences anoutage, the operators Network Operations Center (NOC) can

quickly and easily determine the service impact. For instance,the NOC can view all of the alarms for everything associatedwith that outage from a single vantage point and pull up all

related circuits.

Speed is important because an outage typically has a rippleeffect, forcing neighboring cell sites to pick up traffic usually

handled by the base station that lost its transport link. So

the faster the NOC can identify and resolve the problem, thefewer calls and data sessions that will be dropped or blocked.

This directly improves overall network quality and customersatisfaction. It also can help reduce overhead costs becausethe operator doesnt have to staff its call centers to field calls

about frequent service problems.

Table 5. TDM and DSL transport savings.

300

4

0

420

0

504.000

6.048.000

0

0%

RAN over DSLRAN over E-1

# Cell sites for mid-size city

# 3G E-1s required per cell site

# Ethernet interfaces per cell site

Cost per E-1 per month

DSL transport cost per month (6M equiv)

Monthly cost

Yearly cost

Savings per annum

RAN over packet cost advantage

300

1

1

420

30

135.000

1.620.000

4.428.000

73%

Mobile operators should also look for a single, end-to-endmanagement system that covers both their 2G and 3G net-

works, which significantly reduces complexity and overheadcosts. For example, when an operator has to maintain only asingle management system, time and training costs are saved

as the NOC staff does not have to learn multiple management

consoles and tools. With that complexity out of the way, staffcan focus more of their attention on maintaining high-quality

2G and 3G networks.

The ideal end-to-end management system should also feature:

A central database that documents the entire network

and every element, reducing a need for a separateinventory system

Support for packet- and circuit-loop testing and testreports, ensuring that SLA requirements are met

The ability to manage all transport technologies witha single management system, including ATM, Ethernet,

Frame Relay, IP/MPLS and TDM Low integration cost due to well-documented and

open interfaces toward other software tools

A Graphical User Interface (GUI), ensuring easyprocess flow and minimized mistakes in everydaytasks such as provisioning

Figure 19. TDM and DSL transport.

E-1

RNC

R99 voice over

TDM

HSDPA data over

xDSLEthernet

8605

8660


21/36



IMS

PSTN

Radio Access Network Mobile Core

Ethernet, Fiber, NG-SDH

Ethernet, TDM

NG-SDH

IP/MPLS

Tellabs8000 Network Manager

6325

6325

8860

8100

8630

8605

8620

xDSL

6350

8660 8860

Internet

Figure 20. Tellabs IntegratedMobile solution for ETSI markets.

To accommodate LTEs mesh requirements, mobile operators

should choose MSRs that can support TDM, ATM and FrameRelay pseudowires. This design supports 2G and 3G transport,Ethernet pseudowires, RFC 2547 IP VPNs and hierarchical IP

VPNs, thus providing an ideal migration path for LTE and theall-IP RAN.

LTE will require a significant increase in transport capacity in

order to accommodate the technologys access capabilities of100 Mbps peak downlinks and 50 Mbps peak uplinks. As aresult, mobile operators should choose solutions that feature

pseudowire technology, which leverages both the economicsof packet transport equipment and Ethernet microwave, metroEthernet and DSL services. This approach decouples band-

width from cost.

The bottom line is that although most operators are unlikely todeploy LTE before 2010, they should begin planning now to

ensure that transport CapEx investments made today will nothave to be replaced in order to support LTE.

Enabling a Forward-Looking RAN for All-IP R6 and LTE

Based on the 3GPP standardization process, R6 require an IP

transport network. This IP-based design establishes the RANslong-term requirements. For example, to maximize investmentin network elements purchased today, mobile operators should

choose MSRs and switches rather than ATM switches. That isbecause MSRs and switches are capable of supporting both

the requirements of todays TDM, ATM and Frame Relaynetworks and the needs of R6. As a result, MSRs andswitches are an ideal choice during the migration to R6.

MSRs and switches will also help mobile operators

accommodate LTE, which requires RNC functionality to bedistributed to the Node Bs. This design, which eliminates theRNC as a data bottleneck, requires additional features from the

RAN. For example, LTE requires Node Bs to be fully meshed.

If a call starts on a Node B (the anchor Node B) then movesacross the country (such as when the user is driving) fromNode B to Node B, the new Node B will need to communicatewith the anchor Node B for tasks such as billing. It also will

need to communicate with the previous and next Node Bs inorder to facilitate call handoff. IP Virtual Private Networks (VPN)are likely to be the best solution for this type of meshing.


22/36



Tellabs Mobile Data Network Solutions

In the mobile market, the only constant is change. In some

regions, such as Western Europe, operators must competefor subscribers in markets that are approaching saturation orhave already surpassed 100% wireless penetration. In other

regions, such as China, India and Latin America, operatorsmust develop services that can be sold into price-sensitive

markets. In all regions, operators also face three commonchallenges:

Maintain or reduce OpEx and CapEx

Enhance overall service quality

Increase revenue through alternative products and servicesthat offer access to compelling new content

The Tellabs IntegratedMobile solution gives operators in allmarkets a powerful, flexible and cost-effective way to overcomethese challenges. With Tellabs portfolio of IP/MPLS-enablednetwork solutions, mobile operators can deploy a single

converged network to transport voice and data services withdifferentiated levels of service quality. Tellabs empowers the

operator with a network that is flexible and adaptable to theendless, unpredictable demands of the subscriber base andmarketplace.

Ultimately, the Tellabs IntegratedMobile solution can help the

mobile operator maintain OpEx and CapEx, increase overallservice quality and provide a foundation for the developmentof innovative, high-margin products and services.

Figure 20. NMS/Element Management System (EMS) integration under OSS umbrella.

NetworkManagementSystem

ElementManagementSystem

NetworkElements

BusinessSupportSystem

Billing Ordering Accounting

OperationalSupportSystem

Operational Umbrella FMS Provisioning

NMS X NMS Y

EMSEMS EMS

Mediation and Brokering Middleware

Tellabs intelligent access, transport, edge and aggregationplatforms are ideal for integrating voice and data for transport

between the base station network and the main switchingcenters. They support all of the major data and voice

transmission technologies and provide MPLS encapsulationand switching to enable all types of traffic to be tunneledacross the access and aggregation network.

Tellabs platforms are managed by a single, standards-based

NMS, which provides network and connectivity managementincluding provisioning and monitoring. It provides flexibleand open interfaces and can be integrated with the leading

Operational Support System (OSS)/Business Support System(BSS) platforms used by mobile operators for provisioning,

monitoring and billing.

This section provides an overview of Tellabs mobile data net-work solutions, including how the solutions operators evolve tomeet the challenges of todays and tomorrows wireless market.

Figure 20 illustrates the Tellabs IntegratedMobile solution for

E-1 markets, including the locations of key network elementssupporting the multiservice core, scalable RNC and edgeaggregation, transport optimization with hub applications and

cell-site aggregation. The features and benefits of each Tellabselement are discussed in the following sections.


23/36



Element Management

Tellabs network elements

Tellabs

8000 opendatabase

Other network elements

CORBA

NBI

Network Management

Service Management

Operational Support System

8000

6300 8600 88008100

SN

MP

CLI

Figure 21. Tellabs8000 Network Manager.

Service Provisioning and Monitoring with theTellabs8000 Network Manager

As with any service delivery network, the mobile data networksolution must be able to participate in, and be activelymanaged by, the mobile operators existing OSS and BSS.

The Telecommunications Management Network (TMN)

provides a framework to achieve interconnectivity andcommunication across various operating systems and

telecommunications networks. Within the TMN framework,the OSS controls and manages the Network Elements (NE).The TMN refers to this interface as the Southbound Interface

(SBI). Similarly, the interface between the NMS and theumbrella OSS is known as the Northbound Interface (NBI).The TMN framework specifies the use of CORBA for

implementing the NBI, as shown in Figure 21.

The Tellabs8000 manager provides a combination ofelement management, network management and service

provisioning that enables mobile operators to quickly deployand monitor new services, as shown in Figure 22 .

In addition to providing full graphical element, fault andperformance management for the Tellabs8600 Managed

Edge System, the Tellabs8100 Managed Access System,the Tellabs6300 Managed Transport System and the Tellabs

8800 Multiservice Router (MSR) Series, the Tellabs 8000manager provides end-to-end set-up, testing and monitoringof TDM or ATM circuits, VPNs, Pseudowire Emulation Edge

to Edge (PWE3) MPLS tunnels and other connectivity

needed in mobile networks.

Provisioning a circuit, pseudowire or VPN that includes QoScharacteristics governed by an SLA is a complicated task,

involving many steps and requiring up-to-date knowledge ofthe network type and resource allocation. If done manually

by accessing each associated network element using theCommand Line Interface (CLI) commands, this task canbecome both labor and cost intensive.

By contrast, the Tellabs 8000 manager automates these steps

and provides an umbrella interface for the process. End-to-endmanagement of the entire lifecycle of the connection is achievedwith reduced time, cost and probability of errors.

Instead of manually configuring each network element along

the path of the connection, the end points are highlighted ona graphical network map. The Tellabs 8000 manager software

issues the appropriate configuration commands automaticallyto all the network elements along the path of the connection.Similarly, QoS properties such as bandwidth requirements,

latency and jitter can be specified for the connectionand auto-matically applied to each network element in the path. Finally,fault reporting and monitoring are reported for the connection

rather than for the individual network elements/links, makingthe operators view of the network much easier to understand.

In summary, for mobile operators, the advantages of the

Tellabs 8000 manager are:

Improved operator efficiency and time to market. The

automated tasks and service templates save significant

time over the command-line configuration approach andreduce the number of operator errors.


24/36



Adaptive network capabilities.Changes in bandwidthusage caused by unpredicted use of new data services

can be quickly flagged and analyzed at the service levelso that appropriate actions can be taken.

Network modeling and optimization.Elements, physicaland virtual links can be visualized without physical imple-mentation. This enables different network planning options

to be modeled and analyzed prior to implementation.

A single NMS.NMS should operate and integrate all

technologies in evolving mobile networks.

TellabsIntegratedMobileSMSolution Product Portfolio

Tellabs offers a full-service portfolio of network solutions

designed for mobile voice and data service delivery. Eachis modular and scalable, so that they can be extended andoptimised to suit a mobile operators particular networkrequirements. This end-to-end capability is shown in

Figure 20 and includes:

The Tellabs8800 Multiservice Router (MSR) Seriesseries

is designed for the network core edge to enable the deliveryof TDM, Frame Relay, ATM and Ethernet services, as well

as new IP/MPLS-based VPN services. The Tellabs8800MSR series high density and capacity enables mobileoperators to aggregate hundreds of cell sites at the central

offices and to interconnect multiple mobile switchingoffices over an IP/MPLS network.

The Tellabs8600 Managed Edge Systemprovidesaggregation and transport of TDM, ATM, Frame Relay,IP and Ethernet services using MPLS PWE3 encapsulation

technology. The Tellabs8600 system includes a variety ofhighly scalable and versatile devices that enable the mobile

operator to efficiently extend fully managed packet-basedservices throughout the RAN.

The Tellabs8100 Managed Access Systemprovidesflexible, integrated delivery of multiple services acrossa highly scalable TDM platform. The Tellabs8100 system

includes a full range of cell site access, hubbing andaggregation elements that empower the mobile operator

with exceptional control of network resources. The Tellabs6300 Managed Transport Systemis a next-

generation SDH transport and grooming platform withhigh-bandwidth granularity for aggregating mobile voiceand data traffic over a next-generation SDH network.

Tellabs8800 Multiservice Router (MSR) Series

The Tellabs8800 MSR series is designed to aggregate a

large number of cell sites, BSCs, MGWs, call servers and othernodes in a mobile switching office. In addition, the Tellabs

8800 MSR series can interconnect multiple intra-city, regionaland national switching offices over new IP/MPLS backbones,as well as legacy ATM backbones.

Table 6. Tellabs 8800 MSR series specifications.

160 Gbps

10 Gbps

3

16/64

35 in/889 mm x21.6 in/549 mm x29.5 in/749 mm

2

Tellabs 8840 MSRTellabs 8860 MSR

Switchingcapacity(full duplex)

Bandwidthper slot(full duplex)

No. of SCCs

per chassis

No. ofULCs/PLMs

Mechanicaldimensions(W x D x H)

No. of chassisper ETSI rack

120 Gbps

10 Gbps

3

12/48

35 in/889 mm x17.3 in/439 mm x

29 in/737 mm

2

Tellabs 8830 MSR

40 Gbps

10 Gbps

2

4/16

14 in/356 mm x17.5 in/444 mm x23.5 in/597 mm

6

The Tellabs 8800 MSR series supports any-to-any Layer 2network interworking and provides mobile operators with a

seamless path to migrate their networks from TDM, FrameRelay and ATM to Ethernet/IP/MPLS. The Tellabs 8800 MSRseries enables connection-oriented network characteristics

such as QoS and security with powerful MPLS trafficengineering capabilities, while maintaining the superiorscalability and flexibility of pure IP networks in mobile core

networks. The Tellabs 8800 MSR series supports carrier-classreliability and the TellabsServiceAssuredupgrades, thus

ensuring that mobile traffic is always transported even whenthere network failures and system upgrades.

Each MSR features a wide range of interfaces to provide

unmatched service flexibility (see Table 6). The Tellabs 8800MSR series enables service providers to converge networksat their own pace while simultaneously supporting ATM,

Frame Relay and TDM/private leased-line networks at speedsfrom DS-1/E-1 to OC-192c/STM-64 and Ethernet interfacesfrom 10 Mbps to 10 Gbps. All of the Tellabs 8800 MSR series

network elements are based on the same hardware andsoftware technologies and share a common CLI and NMS, thusenabling mobile operators seamless operation of the network.

Tellabs8860 Multiservice Router (MSR)

The Tellabs8860 MSR is a 160 Gbps (full duplex), high-performance networking platform that supports carrier-class

IP, Frame Relay, ATM, Ethernet and TDM interfaces. This

scalable platform can help mobile operators reduce theirCapEx and OpEx with a broad range of new services and

with fewer network elements. The Tellabs 8860 MSR can


25/36



Figure 25. Tellabs8830Multiservice Router (MSR).

aggregate hundreds of cell sites, BSCs, MGWs, call serversand other devices present in a mobile operator switchingoffice. In addition, the Tellabs 8860 MSR can interconnect

multiple intra-city, regional and national switching officesover new IP/MPLS networks as well as legacy ATM networks.

The Tellabs 8860 MSR can accommodate up to 64hot-swappable Physical Line Modules (PLM).

The Tellabs 8860 MSR combines both IP-routing and time-tested ATM-based QoS levels with the efficiencies of MPLS

traffic engineering. State-of-the-art, custom ASIC technologyprovides 10 Gbps line rate packet forwarding and switching

while performing complex lookup and filtering tasks. It enablesmobile operators to support their existing 2G revenue-generat-ing services, while facilitating the migration to new data-rich,

higher-revenue-generating 3G services.


The Tellabs8840 MSR provides the same features and

functions as the Tellabs 8860 MSR but with 120 Gbps (fullduplex) of capacity in a 19 inch rack-mountable shelf. Justlike the larger Tellabs 8860 MSR, the Tellabs 8840 MSR is

a high-performance networking platform offering carrier-class IP, Frame Relay, ATM, Ethernet and TDM/private lineservices. The Tellabs 8840 MSR can accommodate up to

48 hot-swappable PLMs.


Based on the same design as the larger MSRs, the 40 Gbps

(full duplex) Tellabs8830 MSR is a high-performance net-working platform that delivers carrier-class IP, Frame Relay,

ATM, Ethernet and TDM/private line services at the edge ofan IP/MPLS network. The Tellabs 8830 MSR offers a lowentry price-point for architecting a powerful IP/MPLS network

that can operate at the PE or as an aggregation device thatfeeds into the edge of a large IP/MPLS backbone. The Tellabs8830 MSR can accommodate up to 16 hot-swappable PLMs.



OC-192c/STM-64

ChannelizedOC-48/STM-16(down to DS-3/E-3)

OC-48c/STM-16c

ChannelizedOC-12/STM-4(down to DS-3/E-3)

OC-12c/STM-4c

OC-3c/STM-1c

ChannelizedOC-3/STM-1(down to DS-0)

ChannelizedOC-3/STM-1 IMA(down to T-1/E-1)

DS-3/E-3

Channelized

DS-3/E-3 (3/1/0)(down to DS-0)

10 GigE

GigE

10/100BaseT

Portsper shelf/ETSI rack

12/24

48/96

48/96

192/384

192/384

192/384

96/192

96/192

288/576

288/576

12/24

192/384

1152/2304


4/24

16/96

16/96

64/384

64/384

64/384

32/192

24/144

96/576

96/576

4/24

64/384

384/2304

16/32

64/128

64/128

256/512

256/512

256/512

128/256

128/256

384/768

384/768

16/32

256/512

1536/3072


1/1

1/4

1/4

4/16

4/16

4/16

2/8

2/8

6/24

6/24

1/1

4/16

24/96

ModulePorts

per shelf/ETSI rack

PLM/ULC 8860 8840 8830

Table 7. Tellabs 8800 series por t densities.


26/36



42 Gbps

3.5 Gbps

12

600 mm x440 mm x300 mm

3

3.5 Gbps

3.5 Gbps

1

88 mm x440 mm x280 mm

25

300 Mbps

300 Mbps

Fixed ports

44 mm x440 mm x280 mm

50

14 Gpbs

3.5 Gbps

4

222 mm x440 mm x286 mm

9

Tellabs 8630

switch

Tellabs 8660

switch

Switching capacity(full duplex)

Bandwidth per slot

Number of IFMsper chassis

Mechanicaldimensions(W x D x H)

Number of chassisper ETSI rack

Tellabs 8605

switch

Tellabs 8620

switch

Table 8. Tellabs8600 Managed Edge System specifications. Figure 26. Tellabs8660 Edge Switch.

Tellabs

8600 Managed Edge SystemThe Tellabs8600 system comprises several network elementsand an integrated, service-oriented NMS. The network elements

can be located either in the access network close to cell sitesor within the regional network for traffic aggregation and

service provision.

Access equipment typically has less capacity than aggregationnodes deployed in the regional network. The Tellabs8620Access Switch and the Tellabs8630 Access Switch are

primarily designed for small hub sites, while the Tellabs8660Edge Switch is more suited to deployment in the regionalnetwork for aggregating traffic from the RAN network tothe RNC site. Compact and cost-efficient, the Tellabs8605

Access Switch is optimized for cell-site aggregation. All ofthe network elements are based on the same technology

platform which guarantees interoperability and provides/hasfeatures required in large-scale access network deployments.

Tellabs8660 Edge Switch

The Tellabs8660 switch is the largest and highest capacity

network element in the Tellabs 8600 system. This elementtypically resides in large hub sites or next to an RNC within

a mobile operator network. However, due to its intelligenthardware architecture, the element can also be cost efficientlydeployed in smaller sites. Typically, these are sites that have

high reliability requirements and growth expectations; theycan operate with only a fraction of the platforms maximumcapacity, giving excellent growth potential.

The physical dimensions of the Tellabs

Tellabs Integratedmobile Primer

Documents

Transcript of Tellabs Integratedmobile Primer