Access-independent Core Networks: Converging towards all-IP

1. Access-independent Core Networks:Converging towards all-IP Andy JonesHead of Transmission & InterconnectivityVodafone GroupBBWF Madrid5th October 2005

2. Agenda • Fixed/Mobile Convergence requires a Core Network able to support any type of access • Mobile operator’s perspective on architectural convergence • Identify the main evolution steps towards an all-IP architecture • Transport Layer evolution • Evolution of Control, Switching and Service Layers • Role of IP Multimedia Subsystem (IMS) for fixed and mobile • Compare and contrast fixed and mobile drivers for network evolution

3. Where do we want to go? Today Single-service Vertical Networks Tomorrow Multi-service Integrated Network Services Fixed Network GSM UMTS GPRS Access Access Access Transport, Switching & Access Networks Where are we? and ... Servers Content Content Communication Control Media Gateways Media Gateways IP Backbone Network

4. Service Plane Service Domain Control Plane Control Control User Plane Gateway Gateway Access Networks Bearer Transport Plane Transport Scope of Multi-service Core Scope: the Reference Core Network Architecture • Move from Monolithic to Layered structure for the Core Network • efficient and specialized platforms • modular and scaleable

5. Transport layer – Converged Packet Network IP Backbone Network • All services converge on one IP multi-service backbone – including voice • MPLS selected as future-proof convergent technology – cap ATM investment in Core • MPLS first deployed in Vodafone in 2000 • Early driver - Layer 3 VPN for GPRS virtualisation and corporate access • Then deployed Layer 2 transport for 3G (3GPP Release 99) - ATM over MPLS • Collapse of multiple overlayed IP backbones onto one network (enterprise + SP) • Maximise OPEX efficiencies by eliminating duplicated transport infrastructures Vodafone Converged Packet Network • CPN is a global project within Vodafone’s global business integration programme: One Vodafone • Already deployed in several major Vodafone properties – Group-wide rollout in 05/06

6. Group A Group F Group E Group B Group G Group C Group D Transport Architecture: Open & Hierarchical Vodafone Converged Packet Network Architecture (Release 2) • De-risking interoperability • Simplifying OSS integration • Stimulating competition

7. Call servers Media Gateways Media Gateways IP Backbone Network Mobile Core Network - the evolution path • 3GPP Release 4 is currently being deployed by Mobile Operators • Release 4 is a natural evolution of the Core Network • Modular call servers and media gateways replace large monolithic switches • Optical/SDH transport layer rationalised • TDM tandems removed • Overall, a dramatic simplification with significant OPEX benefits • However, IMS is about to create a disruptive revolution • Why deploy Release 4 and IMS? Sounds like duplication…rather than convergence! • Key architectural challenge for Mobile Operators: • To map an evolution path for the entire architecture, optimised both for new and existing services

8. Target Architecture for Access-independent Core Network UTRAN Access Network Other Access NWs (e.g. WLAN) I/W-Domain IP Transport Network IP MM End-Point Services & Apps. IMS Domain Other SIP networks PSTN Internet PS-Domain SGSN GGSN MGC MGW ASs G/W CSCFs (SIP) • Looking ahead, the long-term goal is an all-IP network architecture • All domains are IP-based, end-to-end • core • access • air interface • terminal • services • This all-IP vision requires significant architectural development • currently in progress in 3GPP Release 7 standardisation • beyond the 3 year planning horizon of R4 and IMS introduction

9. Core Network evolution - steps towards an all-IP target • However, R4 and IMS are important steps towards the all-IP target • Vodafone’s strategy for R4 is to move rapidly to IP transport in the core for voice and video, leveraging IP/MPLS Converged Packet Network • IMS enables homogenous service framework, initially for non-real time multimedia services – air interface and RAN evolution required before CS bearer can be retired • R4 and IMS are initially autonomous (R4 for voice and videotelephony, IMS for new multimedia applications) • R4/IMS combinational services – link control of packet and circuit bearers for real-time multimedia • 3GPP Release 7 enables efficient use of the UMTS packet bearer for real-time traffic • Start to see convergence of all mobile services on IMS-enabled packet core • IMS is the target for Mobile and Fixed operators – but they have different drivers and priorities for its deployment R4/IMS combinational services – rich voice enhanced with multi-media R4 deployment IMS roadmap 2007 2008 2009 2005 2006 2010 3GPP Release 7 standards frozen (for real time packet bearer in access and core) Release 7 products general availability Final step in all-IP evolution: IMS-enabled real time services Non-real time services on IMS (3GPP Release 5)

10. All-IP Evolution Plan requires Industry push • IMS is the common target, but Mobile & Fixed Operators have: • different drivers • different priorities • and therefore, different roadmaps • Mobile & Fixed operators share a common responsibility to drive the industry • Vodafone continues to contribute and drive the Standards (3GPP, OMA, ETSI etc) • Unacceptable lag between standardisation and real interoperable solutions • In 2004, Vodafone joined the MultiService Forum (MSF) www.msforum.org • to promote open standards and architecture • to accelerate interop for next generation infrastructure • interoperability agreements for key R4 and IMS interfaces Through MSF, Vodafone is accelerating the arrival of the all-IP network

11. Thank You!