Migration Roadmap to Ambient Networks Nick Papadoglou, Vodafone; Philip Eardley, BT; Bryan Busropan, TNO; Peter Karlsson, TeliaSonera; Helena Flygare,TeliaSonera; WilfriedSpeltacker, Lucent; David Moro, Telefonica
Overview Introduction to Ambient Networks (AN) Migration and Deployment Issues Migration Principles Migration Roadmap Phases Overlay vs. Interworking in Phase 1 and 2 Conclusion
The Ambient Networks Project EU 6th Framework Integrated Project Phase I, Establishing the Ambient Networks Concept and its Feasibility, started Jan 2004 Aims at an innovative, industrially exploitable mobile network solution in particular for systems beyond 3G Brings together a strong industry led consortium of leading operators, vendors, and research organisations Part of Wireless World Initiative (WWI) Many partners! Ericsson AB (project co-ordinator), Sweden Alcatel SEL AG, Germany British Telecommunications plc, UK Budapest University Of Technology And Economics, Hungary Concordia University, Canada Consorzio Ferrara Ricercha, Italy Critical Software S.A., Portugal DaimlerChrysler AG, Germany DoCoMo Communications Laboratories Europe GmbH, Germany Elisa Corporation, Finland Ericsson Eurolab Deutschland GmbH, Germany Ericsson Magyarorszag Kommunikacios Renszerek K.F.T., Hungary France Telecom SA, France Fraunhofer Gesellschaft Zur Foerderung Der Angewandten Forschung e. V., Germany Instituto De Engenharia De Sistemas E Computadores Do Porto, Portugal Kungliga Tekniska Högskolan, Sweden Lucent Technologies Network Systems GmbH, Germany Lucent Technologies Network Systems UK Limited, UK Motorola Japan, Japan National ICT Australia (University Of New South Wales), Australia NEC Europe ltd, UK Nokia Corporation, Finland Oy LM Ericsson AB, Finland Panasonic European Laboratories GmbH, Germany Rheinisch-Westfaelische Technische Hochschule Aachen, Germany Siemens AG, Germany Siemens AG Oesterreich, Austria Siemens Mobile Communications SPA, Italy Swedish Institute Of Computer Science AB, Sweden Technical Research Centre Of Finland, Finland Technische Universitaet Berlin, Germany Telecom Italia SPA, Italy Telefonica Investigacion Y Desarrollo SA Unipersonal, Spain Telenor Communication AS, Norway TeliaSonera AB, Sweden TNO - Netherlands Organisation For Applied Scientific Research, Netherlands University Of Surrey, UK Universidad De Cantabria, Spain University College London, UK University Of Ottawa, Canada Vodafone Group Services Limited, UK
What is an AN? Ambient Service Interface ASI Scalable & Affordable networking supporting the dynamics of Overlay Context Media Support Layer Provisioning Mgmt. Delivery wireless access Ambient Provide rich & easy to Routing Group Connectivity Naming Mobility Security Information use communication Ambient Ambient Network services for all in a Multi Radio Network Connectivity Agreement Interface Domain Resource Mgmt. Interface Controller Establishm. Management cost effective manner Traffic Multiaccess Engineering Ambient Increase competition Resource ARI Interface and dynamic cooperation of various Standardised common control players plane, called the Ambient Allow incremental Control Space (ACS) supporting market introduction of heterogeneous networks and new technologies seamless interoperation IST - WWI - Ambient Networks ANI
What is AN Providing Hide network complexity from the user AN is all about the control layer Standardize the control space to unify the heterogeneous network environment. Better end-to-end security and QoS control, Radio Resource Management (HO support), context info exchange, etc. Not about the physical layer or application layer!
Migration and Deployment Issues Migration and Deployment issues part of the concept just as much as the target architecture Migration Aspects The Ambient Control Space is an Overlay to existing networks The Control Space operates on an abstracted view of the network resources The AN Concept will become functional even in partial deployment scenarios Not all resources of an Ambient Network have to be AmbNet aware to participate in AN Deployment Aspects We assume the innovation to start from the network edges
Migration Principles Migration requires some time Interim solutions may accelerate the migration process (incremental migration) The migration strategy must follow economic rules and not only technological visions Advantages for the various stakeholders involved must be evident both from a technological and business perspective in all phases Sufficient deployment with AN-capable systems must be reached within a reasonable time from time of conception, standardisation until realisation
Four Migration Phases Four possible phases identified for smooth migration Overlay 1a: Immediate use of existing Layer 2 or 3 bearer of the legacy network Overlay 1b: Implementation of an abstraction layer, adopting the ARI to the legacy network on both the user and control plane 2a: Installation of Inter-Working Functions (IWFs) to emulate an AN behaviour in the legacy network 2b: Add AN functionality in a stepwise fashion to the legacy network to become a real AN with all ACS capabilities 0 2 4 7 10 AN Standardization Legacy standards adopted AN AN Islands Growing AN Infrastructure N ative A N Infrastructure Time Note: Phases can co-exist Backward C o m patible 1a: L2/L3 Bearer 1b: A R I Abstraction 2a: IW F (AN Emulation) 2b: Full A N Deployment
Draft AN standardisation Roadmap 2004 2005 2006 Phase II 2007 2008 2009 Ambient Networks Project Partial aspects of concepts and interfaces ANI aspects ASI aspects System interfaces ARI ANI ASI Protocol specifications Interoperability Specifications IETF/IRTF (NSIS, HIP, ) 3GPP (SAE, IMS, RAN, ) IEEE (802.21, ) OMA (MWS)
Overlay Phase 1a Application ACS Ambient control messages Application ACS legacy data AN terminal Data Legacy Network, no AN functionality legacy data AN terminal
Overlay Phase 1b Application ACS ARI Adaptation layer legacy data AN terminal Ambient control messages Messages to control legacy network s resources Control Data User Data Legacy Network, with resource control Application ACS Adaptation layer legacy data AN terminal ARI
Interworking Phase 2a Application ACS Ambient data AN terminal Ambient control messages Ambient network ACS Ambient data I W F Legacy control legacy data InterWorking Unit Legacy control messages Legacy network Application Legacy control legacy data Legacy terminal
Native AN Phase 2b Application ACS Ambient data AN terminal Ambient control messages Ambient network Application ACS Ambient data AN terminal
Overlay vs. Interworking Migration phases will depend on the business strategy of the stakeholder and adoption rate by the wider consumer community Overlay (Phase 1) more economical and lower risk to introduce AN functionality, although adds complexity and terminal costs, increasing subsidisation Interworking (Phase 2) adds complexity only at the edges of the network (i.e. Gateway) but becomes obsolete when migration finishes
Example of AN migration A likely migration scenario starts with terminals being upgraded with AN functionality for instance a Personal Area Network to become an AN end system. One reason why terminals are a likely starting point is that their innovation and replacement cycle is typically a couple of years. PANs with AN functionality could compose with (similarly enhanced) Body Area Networks via a direct connection, or with someone else s PAN over a legacy network (Phase 1a: overlay). Later operators running WLAN hotspot networks may exploit the fact that many of its customers are AN end systems and upgrade its network to AN. In order to support both AN enabled and legacy terminals, an IWF (Phase 2a) can be introduced. As the terminal population becomes dominated by ANs, the NO or service provider (SP) can decide to upgrade its network to a Native AN (Phase 2b: full AN deployment).
Conclusion Incremental migration depending on both technological and business strategic issues Four migration phases identified considering all possible aspects Migration phases can co-exist without any interoperability problems
Acknowledgement This document is a byproduct of the Ambient Networks Project, partially funded by the European Commission under its Sixth Framework Programme. It is provided as is and without any express or implied warranties, including, without limitation, the implied warranties of fitness for a particular purpose. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the Ambient Networks Project or the European Commission. Questions?
Network Composition Media Delivery Mobility Domain Management Network A Ambient Connectivity Multiaccess Context Provisioning Security Connectivity Controller Network A+B Media Delivery Mobility Domain Management Network B Ambient Connectivity Multiaccess Context Provisioning Security Connectivity Controller Ambient Network Interface When ANs meet, they may whish to co-operate on the control layer composition Composition leads to a rearrangement of the control layer functionality Various levels of composition will exist depending on the business model