You are on page 1of 30

TUTORIAL: g Evolving Architectures for Mobile and Broadband…

Andy Sutton Principal Design Consultant Transport Network Design Orange UK 4th November 2008

COMPANY CONFIDENTIAL

Agenda: g
A question:
“We need sync over packet” - Why?

Surely we only require sync over p y y q y packet if we have a packet switched network… Therefore another question:
Why do we need a packet switched network?

Drivers for PSN - mobile Technologies and Migration steps What about fixed networks
Common core (Infrastructure FMC) Fixed broadband access

Triple Play and beyond…
COMPANY CONFIDENTIAL

Mobile Backhaul

COMPANY CONFIDENTIAL

? ll to date h h ? Answer: Scalability and TCO TCO… COMPANY CONFIDENTIAL .Question: E1s have served the industry well t d t so why change..

E1 Circuits E1 based DDF BTS/Node B Intermediate sites TN BSC AXC (Metro) RNC AXC (Core) SGSN TRAU Etc… COMPANY CONFIDENTIAL .

3 x E1 R99 & 5 x E1 HSPA) 44 x E1 COMPANY CONFIDENTIAL .DDF Cabling for chain of 4 sites (3 x E1 GSM.

8Mbps ( x E1s): (10 ) (20 ) TN serving 20 sites = 320 x E1 for 14.8Mbps TN serving 50 sites = 800 x E1 for 14.4 & 520 x E1 for 28.8Mbps Add some LTE: This requirement is on top of the above due to terminal distribution… COMPANY CONFIDENTIAL .E1 scaling for Mobile Broadband Evolution (GSM + R99 + HSPA) Assuming 11 x E1 per site then total E1 count arriving at TN: TN serving 20 sites = 220 x E1 TN serving 30 sites = 330 x E1 TN serving 40 sites = 440 x E1 TN serving 50 sites = 550 x E1 May be driven by pure capacity rather than 28.4 28.8… Lets now introduce 14.4 & 1040 x E1 for 28.4Mbps ( x E1s) and then 28.8Mbps TN serving 40 sites = 640 x E1 for 14.4 & 1300 x E1 for 28.8Mbps TN serving 30 sites = 480 x E1 for 14 4 & 780 x E1 for 28 8Mbps 14.

Iub backhaul evolution TDM Node B RNC Traditional TDM E1 IMA TDM RNC Node B PSN PWE3 G/W Hybrid backhaul ATM PWE3 for MAC-d flows MAC d PSN Node B PWE3 G/W RNC Full Iub over PSN ATM PWE3 for complete Iub PSN Node B RNC True IP based Iub 3GPP R5 25.933 COMPANY CONFIDENTIAL .

TDM DDF DDF DDF Note: This is a conceptual example UMTS R99 UMTS HSPA RJ45 RJ45 RJ45 GSM .TDM DDF UMTS R99 DDF IDU Microwave Link IDU DDF DDF UMTS HSPA RJ45 RJ45 RJ45 RJ45 IDU Microwave Link IDU GSM .TDM DDF UMTS R99 IDU Microwave Link IDU DDF DDF DDF DDF UMTS HSPA RJ45 RJ45 RJ45 RJ45 RJ45 IDU Microwave Link IDU 24 x E1 & 4 x FE 4 GSM .DDF & Ethernet Cabling for chain of 4 sites (3 x E1 GSM. 3 x E1 R99 & 1 x FE HSPA) GSM .TDM DDF UMTS R99 DDF COMPANY CONFIDENTIAL UMTS HSPA RJ45 RJ45 .

3 x E1 R99 & 1 x FE HSPA) 24 x E1 & 4 x FE 4 4 Use of X-Connect at Intermediate Sites COMPANY CONFIDENTIAL .DDF & Ethernet Cabling for chain of 4 sites (3 x E1 GSM.

DDF & Ethernet Cabling for chain of 4 sites (3 x E1 GSM.TDM DDF UMTS R99 DDF COMPANY CONFIDENTIAL UMTS HSPA RJ45 .TDM DDF UMTS R99 IDU Microwave Link IDU Internal X-Connect UMTS HSPA RJ45 RJ45 DDF IDU Microwave Link IDU GSM . 3 x E1 R99 & 1 x FE HSPA) Single IDU supporting 2 directions (2 x RFUs) GSM .TDM DDF UMTS R99 IDU Microwave Link Li k IDU Internal X-Connect UMTS HSPA RJ45 Single IDU supporting 2 directions (2 x RFUs) Single IDU supporting 2 directions (2 x RFUs) DDF IDU Microwave Link IDU Internal X-Connect 24 x E1 & 1 x FE 4 GSM .TDM DDF DDF Use of X-Connect and Ethernet Switching at Intermediate Sites UMTS R99 UMTS HSPA RJ45 GSM .

TDM DDF IDU RJ45 DDF Microwave Link IDU Internal X-Connect RJ45 UMTS R99 UMTS HSPA Microwave Link IDU IDU Full Iub over Ethernet (ATM PWE3 or IP tx) Use of X-Connect and Ethernet Switching at Intermediate Sites COMPANY CONFIDENTIAL GSM .TDM DDF DDF UMTS R99 RJ45 UMTS HSPA GSM .DDF & Ethernet Cabling for chain of 4 sites (3 x E1 GSM & 1 x FE R99 & HSPA) Single IDU supporting 2 directions (2 x RFUs) GSM .TDM DDF Microwave Link Single IDU supporting 2 directions (2 x RFUs) Single IDU supporting 2 directions (2 x RFUs) DDF 12 1 x E1 & 1 x FE (LAG or GE?) & UMTS R99 RJ45 IDU IDU Internal X-Connect UMTS HSPA Microwave Link IDU IDU Internal X-Connect GSM .TDM DDF DDF UMTS R99 RJ45 UMTS HSPA .

Assuming 3 x E1 per site and 1 x FE then total E1/FE count arriving at TN: TN serving 20 sites = 60 x E1 & 10 x FE TN serving 30 sites = 90 x E1 & 15 x FE TN serving 40 sites = 120 x E1 & 20 x FE TN serving 50 sites = 150 x E1 & 25 x FE Optimised Hybrid for Mobile Broadband Evolution Lets now introduce 14. again depends upon use and capabilities of Nodal radio and BSC equipment .4 & 150 x E1 & 25 x FE for 28.4Mbps and then 28.4 & 90 x E1 & 15 x FE for 28.8Mbps 28 8Mbps TN serving 50 sites = 150 x E1 & 25 x FE for 14.8Mbps Add some LTE LTE: This requirement is on top of the above due to terminal distribution… Note: Actual number of Ethernet connections depends upon aggregation/switching p p gg g g capability and use of Nodal radio systems.4 28.8Mbps: TN serving 20 sites = 60 x E1 & 10 x FE for 14 4 & 60 x E1 & 10 x FE for 28 8Mbps 14. maybe just 2 x GE per TN… COMPANY CONFIDENTIAL Note: GSM E1s may be presented as channelised (structured) STM-1 interface.4 & 120 x E1 & 20 x FE for 28.8Mbps TN serving 40 sites = 120 x E1 & 20 x FE for 14.8Mbps TN serving 30 sites = 90 x E1 & 15 x FE for 14.

DDF & Ethernet Cabling for chain of 4 sites (3 x E1 GSM (Ch-STM-1 aggregation at TN) & 1 x FE R99 & HSPA) 2 x Ch STM-1 & 2 x GE h E A Potential Scenario – Depends upon Nodal IDU Functionality… (GE & Ch STM-1) STM 1) COMPANY CONFIDENTIAL .

PDH .IP Transport Network Layer p y 3GPP Release 5 introduces the concept of IP Transport in p p UTRAN However. IP does not equal Ethernet IP can be carried over ATM .SDH R99 ATM based UTRAN can be carried over Ethernet ATM PWE3 GSM can be carried over Ethernet TDM PWE3 CESoPSN or SAToP Therefore careful consideration is required required… COMPANY CONFIDENTIAL .

transmission We know the end game is IP however even that’s not simple IP over what and how? This impacts the functionality we require on the backhaul network Transport Transmission COMPANY CONFIDENTIAL . abstraction and p .Transport.

Network functionality y Next-generation b kh l must N t ti backhaul t support legacy services What is the mechanism for this? Pseudo-wires Pseudo wires enable the transport of legacy protocols over Ethernet Are pseudo-wires a short term requirement? COMPANY CONFIDENTIAL .

? y p IETF RFC 3985 (One of many RFCs relating to pseudo-wires) Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture PWE3 is a mechanism that emulates the essential attributes of a telecommunications service ( (such as an E1 or ATM circuit) over a ) PSN PWE3 is intended to provide only the minimum necessary functionality to emulate the wire with the required degree of faithfulness for the given service definition Pseudo Wi P d Wire Attachment Circuit PSN t tunnel LSP l Termination point T i ti i t Attachment Circuit CE Native Service PE PE Native Service CE Emulated Service COMPANY CONFIDENTIAL ..What exactly is a pseudo-wire.

Creating p g pseudo-wire services What's needed to create a pseudo wire? Client signal termination points at the endpoints An IP routing protocol to establish reach-ability between endpoints A tunnelling protocol to establish a connection between the endpoints A signalling protocol to establish the pseudo wire connecting the pseudo-wire termination points through the tunnel Pseudo Wi P d Wire Attachment Circuit PSN t tunnel LSP l Termination point T i ti i t Attachment Circuit CE Native Service PE PE Native Service CE Emulated Service COMPANY CONFIDENTIAL .

Transport support p pp TDM GSM ATM R99 IP R5 Do D R5 N d B’ require Node B’s i pseudo-wires? Native IPoE TDM PWE3 ATM PWE3 ETH PWE3 IP PWE3 Possibly… Possibly Ethernet TDM GSM ATM R99 IP R5 Ethernet requires an underlying physical layer Microwave radio Optical fibre Copper TDM PWE3 ATM PWE3 ETH PWE3 IP PWE3 Native IPoE Ethernet Underlying Physical Layer U d l i Ph i l L COMPANY CONFIDENTIAL .

Ethernet makes sense however… Where do we place the support for pseudo-wires? Cell Site Gateway? Microwave System? Node B? COMPANY CONFIDENTIAL .

Common Core transmission/transport (Infrastructure FMC) COMPANY CONFIDENTIAL .

data centres. corporate offices and call centres PE P P MPLS VPNs Provide access to Internet transit Being re-engineered to p provide Classic P core Optical by-pass PE COMPANY CONFIDENTIAL PE P P Internet P P PE .GRN traffic flows Gigabit Router Network Core IP/MPLS network PE PE PE Traditional Mobile Broadband (Fixed & Mobile Connects all OUK switch sites.

Billing. Video. Corporate. Mobile and Residential Voice.OUK Core Network Overview (GRN) ( ) ‘High Availability’ Architecture and g y Features ‘Converged’ MPLS Network: Mobile & Residential Broadband Internet. etc. Based on RSVP LSPs with FRR protection (no optical protection) t ti ( ti l t ti ) Five QoS classes Redundant Internet Peering P i t R d d tI t t P i Points Optical by-pass not illustrated COMPANY CONFIDENTIAL . Gn & Gi backhaul.

VoIP .Fixed Broadband HSI .IPTV COMPANY CONFIDENTIAL .UMA .

ADSL2+ .G.Fixed broadband (ADSL .ADSL2 .Ethernet Inter-Working Function (IWF) Ethernet based backhaul Increasing use of IP/MPLS towards the unbundled DLE/LEX COMPANY CONFIDENTIAL .SHDSL) Different starting point Internet v’s Telco… Ethernet backhaul started to replace ATM due to TR-101 DSL Forum (Broadband Forum) Technical Report 101 Migration to Ethernet-Based DSL Aggregation S Introduction of the Ethernet DSLAM (sometimes called IP DSLAM) ADSL is still ATM though though… ATM .

End to End Encapsulation p Protocol Encapsulation COMPANY CONFIDENTIAL .

OUK IPTV End-to-End Architecture COMPANY CONFIDENTIAL .

EPC/SAE .IMS Already happening in fixed – DSL Forum (now Broadband Forum) TR-101 The correct solution and level of FMC will be a balance between cost. scalability and operational impact Therefore overall TCO… Sync over Packet will be critical to cost-optimised network evolution! COMPANY CONFIDENTIAL . technology.Summary y The evolution of mobile networks and the implications of mobile broadband demand a fundamental re-think of backhaul architecture A move to packet based backhaul is inevitable 3GPP R5 .LTE .

com COMPANY CONFIDENTIAL .sutton@orange-ftgroup.Thanks! Any Question? y andy.