1 / 25

Migration to All-IP Networks: Directions and Deployment

Customers’ Event Crete, May 2007. Migration to All-IP Networks: Directions and Deployment. Presented by: Dr. Yuri Gittik Chief Strategy Officer. Outline. All-IP” Networks: The Approach IP Transformation Focus on Access and Metro

tamra
Download Presentation

Migration to All-IP Networks: Directions and Deployment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Customers’ Event Crete, May 2007 Migration to All-IP Networks: Directions and Deployment Presented by: Dr. Yuri Gittik Chief Strategy Officer

  2. Outline • All-IP” Networks: The Approach • IP Transformation • Focus on Access and Metro • Incremental Deployment – Leveraging Existing Infrastructures

  3. Towards “All-IP” Networks • IP traffic prevails the applications– IP for voice and data services • VoIP and soft-switches for voice services • Internet access and IP VPN services • Pseudowire solutions for Ethernet and legacy Layer 1/2 services • New IP-based services: IPTV, N-play • Fixed-mobile convergence • “Access-agnostic” services for wireline and mobile customers • IMS SIP-based services (“push-to-x”) • IP/MPLS infrastructure • IP DSLAMs, PSN backhaul, metro and core networks • It’s all about money: €conomy- not technology! • Reduced opex with high economy of scale • Reduce the number of different networks and infrastructures • Flexibility with existing and new services

  4. BT’s 21CN Network Evolution • From multi-networks to a multi-service network • Fewer network elements • Simpler service management • Rapid implementation

  5. More for Less Drivers for the 21st Century Network Power to Customers –increased flexibility and greater reliability Speed to Market - innovative services Investing now for future £1B annual cash savings Cost Transformation - significant reduction in operating costs

  6. Migration to “All-IP” Networks:Still Open Issues • IP transformation • Maintain legacy traffic (mainly business and mobile) • Focus on access and metro • From DSLAM to MSAN • Ethernet metro • Incremental deployment – leveraging existing infrastructures • First of all, SDH infrastructure • And many others…

  7. Outline • All-IP” Networks: The Approach • IP Transformation • Focus on Access and Metro • Incremental Deployment – Leveraging Existing Infrastructures

  8. IP Transformation: Legacy over PSN Network Core Access/Backhaul Services/CPE Legacy Services Existing Equipment • Maintain legacy traffic over new packet-switched infrastructures • TDM, ATM, voice, … • A broad traffic range: residential and business services, 2G/3G mobile traffic • Domestic and international coverage ATM DSLAM 2G BTS 3G NodeB Legacy Networks SDH, ATM New Services and Equipment New Packet-Switched Networks GbE, MPLS, IP IP RAN 4G NodeB IP DSLAM

  9. "Classic" Edge-to-Edge Pseudowires • Emulation of native Layer 1/Layer 2 services, such as TDM, Frame Relay, ATM or Ethernet, over a packet-switched core network (IP/MPLS) • Enables transport of a native service over IP/MPLS tunnels • Emulation is performed by provider edge devices (PE) • The individual service emulations in this approach are termed pseudowires • RAD pioneered “pre-pseudowire” TDMoIP in 1999 and leads the pseudowire standardization and implementation PW Encapsulation Function PW Encapsulation Function Customer Premises Customer Premises PE PE IP/MPLS CPE CPE Attachment Circuit Native Service Attachment Circuit Native Service PW PW

  10. “Classic” Pseudowires Extended Pseudowires/Emulation Broadening the Pseudowire Approach Network Segment Access Core IP/MPLS Infrastructure Platforms Ethernet IAD+DSLAM (MSAN) Note:Metro segment could be considered as a part of the access network, or, alternatively, associated with the core network

  11. 3GPP Development: More IP/MPLS RAN Core

  12. Mobile Backhauling:Towards IP-centric Infrastructure Milestone 1. Legacy (TDM and ATM-based) cellular voice+data traffic over PSN infrastructure including backhauling • Pseudowire solutions with optional clock recovery • Incremental migration to “all-IP” and IMS solutions • Mainly in the core, not backhaul infrastructure, yet with some impact on backhauling Milestone 2. IP-based cellular voice+data traffic over PSN infrastructure including backhauling • Regular IP solutions with some cellular-specific implementations • IMS solutions are expanding into the multi-technology access • TISPAN is adding functional sub-system for enhanced control of network resources “Grey area”

  13. Backhaul Evolution Towards IP  • Evolution steps • Pre-provisioned (w/o control plane) traffic-agnostic transport (TDM, ATM) • Pre-provisioned (w/o control plane) traffic-aware transport • Abis optimization, data compression, … • [Traffic-aware] transport with control plane • Network control plane (IP/MPLS-based), optionally service-aware • Service control plane (IP/IMS-based) • Next steps? • Access “collapsing” when controller nodes (not entities!) are eliminated • From Backhaul (radio sites-controller)+ Aggregation (controllers-edge node) to Access (radio sites-edge/core node)  ? ? ? ?

  14. Outline • All-IP” Networks: The Approach • IP Transformation • Focus on Access and Metro • Incremental Deployment – Leveraging Existing Infrastructures

  15. 21CN Network Architecture • CMSAN – Copper MSAN • FMSAN – Fiber MSAN

  16. ngDSLAM/MSAN: Typical Deployment Scenario • Initial Stage: DSLAM platform with strong focus on residential services (and optional PSTN migration) • Use standard commodity IAD and CPE • Low importance of fiber access • Basic services (voice, Internet access) • Next Stage: Broadening the focus • More focus on business customers • Access over DSL and fiber • Maintaining traditional services (leased lines, ATM) • Dedicated smart NTU and multiservice CLE for new and traditional services • Cellular backhaul applications • And now adding IPTV services…

  17. To Ensure Really Multiservice MSAN Customer Premises Single/multiple Copper Fiber IAD • Adding a range of smart NTU/CLE products to the MSAN platform • Access over xDSL and fiber links • Optional pseudowire technologies to support legacy traffic • More focus on direct (fiber) access to Metro Ethernet • Point-to-point and point-to-multipoint (GPON) PBX CO/POP 3G NodeB Ethernet Metro IP/MPLS ATM Access Gateway Single/multiple Copper ngDSLAM MSAN TDM 2G BTS Customer Premises Radio Site NTU/CLE Fiber PBX

  18. Ethernet Metro: Too Many Options? • Ethernet over legacy networks (SDH, ATM) • MPLS-based Ethernet metro • New alternative [emerging] technologies • Transport MPLS (T-MPLS) – Alcatel, more? • PBB-TE (former PBT) – Nortel, BT, NSN, (RAD?) • Yet a clear consensus on the requirements for end-to-end Ethernet services • Smart termination and service demarcation are essential • Ethernet OAM, traffic handling, protection, … E-NTU

  19. Outline • All-IP” Networks: The Approach • IP Transformation • Focus on Access and Metro • Incremental Deployment – Leveraging Existing Infrastructures

  20. Leveraging Existing Infrastructure Network Core Access/Backhaul Services/CPE Legacy Services Existing Equipment • How to take advantage of existing infrastructures? • Ethernet/IP services over: • SDH: Ethernet over SDH (DTAG, Telenor, …) • ATM: Ethernet over ATM (FT, DTAG, …) ATM DSLAM 2G BTS 3G NodeB Legacy Networks SDH, ATM New Services and Equipment New Packet-Switched Networks GbE, MPLS, IP IP RAN 4G NodeB IP DSLAM

  21. T-COM: Bottom Up from SDH

  22. Core router Distribution router DSLAM or Ethernet switch ngSDH node Telenor: “All-IP 2010” Network Distribution Ethernet/ngSDH Core IP/MPLS • Higher capacity • Fewer technologies • Seamless services • IP-based service platform with open standards and common interfaces • Common service edge • Ethernet interfaces • All access types SDH Point-to-point radio or fiber Areas with late IP/MPLS distribution rollout 80x nodes Base Station Ethernet CWDM DSL Distribution FTTP Fiber VDSL2 New build areas ADSL ADSL2+ SHDSL High capacity DSL areas Access

  23. Ethernet over SDH: Options • Ethernet traffic (services) over pure SDH infrastructure • ngSDH, MSPP (Multi-Service Provisioning Platform) • “Old generation” SDH with external Ethernet-over-SDH capabilities • GFP, Virtual concatenation for “fat pipes”, LCAS, etc. • Ethernet traffic over combined SDH & PSN infrastructures • How to bridge two worlds in a most efficient way? Egate Channelized STM-1 Ethernet IP/MPLS SDH Metro GbE

  24. Summary • Variety of “All-IP” networks implementation: “One size does not fit all” • Increasing importance of intelligent multiservice access over diverse media • More technological alternatives are under way… driven by economics

  25. Thank you for your attention Yuri Gittik yuri_g@rad.com www.rad.com

More Related