Mobility, 3G and Beyond and NGN Tatiana Kurakova, Telecommunication Standardization Sector Engineer 24 June 2004, Victoria Falls, Zimbabwe

A View of Terminal Mobility Versus Personal Mobility must carry a wireless terminal must be within radio coverage Network wireless Personal mobility need not carry a terminal must have a personal number Network wireline A View of Terminal Mobility Versus Personal Mobility

Definitions Mobility is the ability to provide services irrespective of environment changes that may occur by mobile user/terminal/network's activities. Personal mobility is the ability of a user to access telecommunication services at any terminal on the basis of a personal identifier, and the capability of the network to provide those services delineated in the user's service profile. Terminal mobility is the ability of a terminal to access telecommunication services from different locations and while in motion, and the capability of the network to identify and locate that terminal.

Data Subscriber Growth Wireless Applications Growth Wireless Internet Source: Strategis Group, World Cellular / PCS Markets, May 1998. (“Other Digital” refers to PDC and PHS.) Source: The Yankee Group, Nortel Networks Subscriber Growth Data Subscriber Growth Data Traffic Growth Voice 96% Data 4% Voice 30% Data 70% Wireless Applications Growth

Group on IMT-2000 and Beyond Why mobile studies are so important? growth of wireless access outstripping traditional access soon will be over 50% of all subscribers already the case in some markets explosive growth of the Internet strong correlation between wireless access and internet usage leads to “Wireless Internet” multiple forums working on 3G systems need to promote harmonization and convergence rapidly increasing importance of globalization

Questions under study (1 of 3) 1) Service and Network capability requirements and network architecture      establish a clear vision for future mobile services and network capability requirements for “beyond IMT-2000 systems”   2) NNI mobility management protocol (Stage 3) define new mobility management signalling application protocols, or enhancements to existing protocols, needed to support IMT-2000 services to enable global roaming between different IMT-2000 family systems.   3) Identification of existing and evolving IMT-2000 Systems     identify architectures, detailed specifications and releases which have been and will be produced by recognized SDO’s which make up existing and evolving IMT-2000 systems.

Questions under study (2 of 3) 4) Interworking functions to be used with existing and evolving IMT-2000 systems identify (and define if not done elsewhere) interworking functions to facilitate appropriate interworking between existing and evolving IMT-2000 family members, PSTN/ISDN and Packet Data Networks 5) Preparation of a Handbook on IMT-2000 work with the D- and R-sectors, coordinate T sector input for a handbook on IMT-2000 to assist developed and developing countries

Questions under study (3 of 3) 6) Harmonization of evolving IMT-2000 Systems define interface requirements and network architectures for harmonization of existing and evolving IMT-2000 systems to provide seamless global roaming for IMT-2000 future Capability Sets (that include high speed packet data, multimedia, and IP-based services) 7) Convergence of fixed and existing IMT-2000 systems - describe the principles and requirements for the convergence of fixed and IMT-2000 networks - describe the architectural requirements for a converged core network to support IMT-2000 capabilities accessible from various wireless and wireline access technologies to support current and evolving IMT-2000 capabilities  

The three-stage process for interface specification Services/Features Stage 1 Service definition Functional architecture Physical architecture Information flows Stage 2 Signaling requirements SDL diagrams Stage 3 Protocol specification Interfaces SDL – System Description Language The three-stage process for interface specification

ITU-T Recommendations developed by SSG (1 of 3) Q.1702 (06/02) - Long-Term Vision of Network Aspects for Systems Beyond IMT-2000 Q.1703 (05/04) – Service and Network Capabilities Framework of Network Aspects for Systems Beyond IMT-2000 Q.1741.1 (04/02) - IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access network   Q.1741.2 (12/02) - IMT-2000 references to release 4 of GSM evolved UMTS core network with UTRAN access network  

ITU-T Recommendations developed by SSG (2 of 3) Q.1741.3 (09/03) - IMT-2000 References to Release 5 of GSM evolved UMTS Core Network Q.1742.1 (12/02) - IMT-2000 references to ANSI-41 evolved core network with cdma2000 access network   Q.1742.2 (07/03) - IMT-2000 references (approved as of 11 July 2002) to ANSI-41 evolved core network with cdma2000 access network  

ITU-T Recommendations developed by SSG (3 of 3) Q.1742.3 (01/04) - IMT-2000 references (approved as of 30 June 2003) to ANSI-41 evolved core network with cdma2000 access network Handbook “Deployment of IMT-2000 Systems” (11/02) Q.1761 (01/04) - Principles and requirements for convergence of fixed and existing IMT-2000 systems Supplement 47 (11/03) - Emergency services for IMT-2000 Networks - Requirements for harmonization and convergence  

Questions for further study 1) Service and Network capability requirements and network architecture 2) Mobility Management 3) Identification of existing and evolving IMT-2000 Systems 4) Preparation of a handbook on IMT-2000 5) Convergence of evolving IMT-2000 networks with evolving fixed networks

Foreseen deliverables (1 of 5) 2004: Technical Report, Q.TRMMR: Mobility Management (MM) Requirements for Systems Beyond IMT-2000 New Recommendation Q.1741.4: “GSM evolved UMTS core network” (References to Release 6) New Recommendation Q.1742.4: “ANSI-41 evolved core network with cdma2000 access network”

Foreseen deliverables (2 of 5) 2004: New Recommendation Q.FMCstg2: Network architecture and interface requirements facilitating evolution of existing public fixed networks towards converged core network, supporting IMT-2000 capabilities Technical Report: Lawful interception requirements for the converged and the harmonized networks

Foreseen deliverables (3 of 5) 2005: New Recommendation Q.FNAB: Long-term high-level network architecture for beyond IMT-2000 systems New Recommendation Q.FIFB: Long-term high-level network functional information flows for beyond IMT-2000 systems Technical Report, Q.MMF: MM Framework and Functional Architecture for Systems Beyond IMT-2000

Foreseen deliverables (4 of 5) 2005: Handbook on IMT-2000 deployment, 2nd edition, Core Network Aspects New Recommendation: Access network interface requirements for utilizing IMT-2000 radio access technologies as FWA with existing public fixed networks

Foreseen deliverables (5 of 5) 2006: Technical Report: MM Functional Information Flows and Protocol Development New Recommendation: Architectural and network interface requirements for converged core network to facilitate services transparency to users across different access arrangements, including migration path for network convergence

Mobility Management Mobility Management requirements based on Vision, Harmonization, and Fixed/Mobile Convergence studies Technical Report nearing completion assessing protocol candidates based on: compatibility with emerging IP-based Core Networks re-use of existing specifications from IETF, partner SDOs of 3GPPs, IEEE, others smooth migration to longer term requirements

Where ITU-T can add value in global IMT-2000 and beyond standardization • Leadership through coordination, consensus building, and collaborative working arrangements – with 3GPPs, OMA, SDOs, other relevant fora • Facilitating adoption of appropriate external specifications as ITU-T Recommendations – act as a single source for IMT-2000 and related standards • Development of requirements and architectural framework Recommendations as needed and appropriate – provide context and structure for IMT-2000 related specifications • Identifying emerging industry needs for global standards – propose efficient and coordinated work planning and sharing arrangements with external forums to meet needs • Facilitating interoperability and interworking between IMT-2000 family members for global roaming, seamless service delivery – provide interworking specifications if not done elsewhere

Envisaged Network Environment Around the Year 2010 (1 of 2) Market trends High-speed data connection is a norm Core network is fully IP-based Digital TV with data service capability Existence of many complementary wireless networks Users are computer proficient Users move internationally wanting their services anytime anywhere Services are the driver

Envisaged Network Environment Around the Year 2010 (2 of 2) Technology trends Software radio technology becomes a main element in the wireless infrastructure Mobility management will be supporting higher speed objects such as vehicles Concept of seamless services will be extended beyond handover and roaming services Security environment around the year 2010

NGN in ITU-T Main study groups addressing NGN: SG 11 SG 13 SSG Network Signalling and Control functional architectures in emerging NGN environments Signalling and control requirements and protocols to support user attachment in NGN environments SG 13 Functional requirements, services and architectures SSG Vision for IMT-2000 Mobility Management Convergence of Fixed and Mobile SG16 has developed MM Services specifications directly applicable to NGN with the H.323 system, H.248 gateway control protocol, QoS, Security, Services & Applications N.B: all SGs have an “NGN” aspect to their work

ITU-T NGN Project Joint ITU-T SG13-SSG session on NGN, 5 Nov 02 NGN-2004 Project description http://www.itu.int/ITU-T/ studygroups/com13/ngn2004/index.html Definition of NGN Workshop on "Next Generation Networks: What, When and How?" Geneva, 9-10 July 2003 Joint Rapporteurs Group on NGN (JRG-NGN)

Joint Rapporteurs Group on NGN (JRG-NGN) 4 meetings held in last 10 months - last meeting in June 04 11 Recommendations under development 2 mailing lists open to non-ITU-T members

What is NGN ? A full (carrier class and business class) service network Telephony and other Legacy (including Internet access) services Data, including High speed access to Internet and its applications Video (VOD, Streaming) Digital TV Broadcast, Multimedia (combining all of the above) Mobility and Nomadism. Interworking with Legacy services for Human and Machine users (including RFIDs machines) Network features and technical characteristics Packet-based (IP, MPLS, ATM, Ethernet) transport IP and service intelligence, in an IP-managed network Distributed, transport-resource-session-service independent control Using IP-friendly (well defined profile) protocols

The Transformed Network Always on Anytime, anywhere and in any form Voice and multimedia Self service, intuitive Simple for the end user Secure, trusted and reliable So - what’s a transformed network all about? This is a spec. And this is actually very different from today’s network. Looks a lot the same, very different. Dramatically lower in cost and that’s going to happen because the technology is going to keep moving, just like it has for PCs. “Always-on.” Networks aren’t always on today. Be reached anytime, anywhere, in any form. So we have voice mobility today, we need to be able to take our work and our play with us. Voice + Multimedia. Inherently voice + multimedia. So some people say ‘why do you put voice in there because multimedia includes voice?’ Yes, but let’s make the point. Voice is just another applications but it’s a very stringent application that requires demanding things of the network. And right now, voice is on a separate network and if you want to have a multimedia experience, you, the user, are coordinating the voice bridge with a bunch of digits to dial, the desktop with a bunch of applications to figure out how to use. And we have the capability now to do that as simply as dialling a phone. So the technology exists, we just need to roll it out in the network. Self-Serve and Intuitive: the networks need to be self-serve. Everybody, whether they’re an enterprise or a carrier, tells me everyday ‘the networks cost too much to operate.’ And the long run solution over that is make them self-serve. So, as in the example I mentioned, use IMS so that I can configure my communications configuration, not cause the carrier to have to pick up the phone and I’m going to ask him to run these three numbers to one voicemail. One. Then they have to have people to take the order. And if you go back far enough, you get John’s work order when the cord-boards were around. So just as that couldn’t survive, the carrier having to take the order for these things today can’t survive, the network’s got to be self-service. It needs to be simpler for the end user. It needs to be secure, trusted and reliable. And it’s not in a lot of place, a lot of the network we use today is best efforts. And the voice network is pretty secure, trusted and reliable, a lot of the networks are not. And it needs in fact to be a platform for services creation, it needs to be more sophisticated itself, the network has to have services in it itself.

When is NGN coming in ? Some (pre-NGN) pieces are already there: PSTN (VoIP, VoATM) trunking, some VoIP offers Private/corporate network solutions (Centrex IP, IP VPN…) A long way to the 21st Network. Convergence of Telephony and Data (IT, Internet) approaches: PSTN/ISDN evolving towards NGN oriented platforms Replacement of obsolete PSTN/ISDN network elements: 2005 onwards Packet Data networks evolution (Fixed-Internet convergence) Evolving from the current High Speed Internet access (ADSL, WLAN …) platforms To offer new generation Services: 2005 onwards Mobile convergence (IMS): 2006 onwards

How will NGN be developed and deployed ? Replacing progressively legacy PSTN elements/areas Only when becoming obsolete (too little OPEX/CAPEX gain, particularly in Core) Migration of PSTN->NGN might accelerate after 2010 (PSTN lines moved to DSLAMs -> VoIP) Green field deployment (today) Overlay deployment, building over xDSL and Fiber-based access to Internet ADSL is being deployed fast, with huge investments Opportunity to provide new (audio-data-video) services Convergence between Fixed-Mobile and Internet services/applications Nomadicity (Mobility Management for Roaming) Mobility through Fixed WLAN (spectrum from Fixed ->Nomadic->Mobile) Harmonizing/Converging with Mobile IMS and IP-Cable

Recommended follow-up Actions Define Services Framework Generic service Building blocks (or Capabilities) Harmonized with Mobile and Cable/Broadcast Define reference Architecture Built upon IMS, adapted to accommodate xDSL access Identify Scenarios and Evolution Steps Identify Interfaces subject to standardization Prioritise Standardization areas and requirements Select protocols and specify their profile(s) Interact (and share) with relevant SDOs (IETF, 3GPP) and Fora (e.g. DSL, MSF …)

Focus Group on NGN (1 of 2) Addresses the market needs for NGN standards Created on 7 May 2004 to tackle NGN studies Goal – to produce global standards for NGN Lifetime till mid 2005 Reports to TSB Director Inherits ~ 11 draft Recommendations from JRG NGN Operates in compliance with Recommendation A.7 Inaugural meeting 23-25 June 2004 Web site http://www.itu.int/ITU-T/ngn/ Mailing list fgngn@itu.int Paperless meetings First meeting documents are public available

Focus Group on NGN (2of 2) Terms of Reference Nomadicity architecture supporting broadband xDSL access NGN activities on QoS Signalling IP QoS Signalling requirements Authentication Security

For more information please visit our web site http://www.itu.int: SSG web page http://www.itu.int/ITU-T/ssg/index.html and IMT-2000 web pages: 1. Network aspects http://www.itu.int/ITU-T/imt-2000/network.html 2. Radio aspects http://www.itu.int/ITU-R/study-groups/rsg8/rwp8f/index.asp NGN Project: http://www.itu.int/ITU-T/studygroups/com13/ngn2004/index.html Focus Group: http://www.itu.int/ITU-T/ngn/fgngn/index.html

Thank you for your attention!