1. International Telecommunication Union Chairman: Mr Chaesub Lee (ETRI, Korea, Rep. of) chae-sub.lee@ties.itu.int TSB: Ms Tatiana Kurakova Supported by Ms Gabrielle Regan SG13 – Future networks including mobile and NGN

2. CONTENTS 1. Mission and Mandates of SG 13 2. Management and Structures 3. Study Overview 4. Working Party Activities: from each WP Chairs 5. Meetings

3. 1. Mission and Mandates of SG 13 1. Mission and Mandates of SG 13 Leading Study Group roles of ITU-T SG13 Lead study group for Future Networks and NGN Lead study group on Mobility Management and Fixed-Mobile Convergence SG13 was NGN group Lead study group for NGN and Satellite SG13 covers ‘Future networks including mobile and NGN’ WTSA 2008 WTSA 2004

4. 1. Mission and Mandates of SG 13 Responsible for studies relating to the requirements, architecture, evolution and convergence of future networks. Also includes NGN project management coordination across study groups and release planning, implementation scenarios and deployment models, network and service capabilities, interoperability, impact of IPv6, NGN mobility and network convergence, public data network aspects and network aspects of IdM. Responsible for studies relating to network aspects of mobile telecommunication networks, including International Mobile Telecommunications (IMT), wireless Internet, convergence of mobile and fixed networks, mobility management, mobile multimedia network functions, internetworking, interoperability and enhancements to existing ITU ‑ T Recommendations on IMT. Responsibility of ITU-T SG13 (Res. 2)

5. 1. Mission and Mandates of SG 13 Mandated Scopes of ITU-T SG13 (Res. 2) Communication networks aspects: study for requirements, functional architectures and their capabilities of future networks including NGN according to a layered approach such as transport (access and core), transport control, service control and service/application support functions including support of mobility. Mobile aspects: studies relating to network aspects of mobile telecommunication networks, including International Mobile Telecommunications (IMT), wireless Internet, convergence of mobile and fixed networks, mobility management, mobile multimedia functions, internetworking, interoperability and enhancements to existing ITU-T Recommendations on IMT. This study will incorporate harmonization with relevant standards which will be developed in mobile related standard development organizations. Content distribution networks aspects: study for the requirements, functions and mechanisms to support distribution of contents which are requested by end users. This will include capabilities to support content finding/metadata, content distribution, rights management and media coding. This study will incorporate broadcasting and other standards integration within the context of future networks including NGN and mobile communication networks.

6. 1. Mission and Mandates of SG 13 Ad hoc networks aspects: study of requirements, functions and mechanisms needed to support configuration of ad-hoc networks used for identifying service discovery and activation, and context description/distribution including peer-to-peer networking. This study should be based on preliminary work in Study Group 13 and 19 performed during the previous study period. Common function aspects: study of functions and relevant capabilities including NGN-specific identity management functional architecture that supports value added identity services, the secure exchange of identity information and the application of bridging/interoperability between a diverse set of identity information formats. Also to be studied are any identity management threats within the NGN and the mechanisms to counter them. In addition Study Group will study the protection of personally identifiable information (PII) in the NGN to ensure that only authorized PII is disseminated within the NGN as well as future networks. Mandated Scopes of ITU-T SG13 (Res. 2)

7. 1. Mission and Mandates of New SG 13 Mandated Scopes of ITU-T SG13 (Res. 2) This study also will cover regulatory implications including telecommunications for disaster relief and emergency communications. In order to assist countries with economies in transition, developing countries, and especially least developed countries, in the application of IMT and related wireless technologies, consultations should be held with representatives of ITU ‑ D with a view to identifying how this might best be done through an appropriate activity conducted in conjunction with ITU ‑ D. Study Group 13 shall maintain strong cooperative relations with external SDOs and 3GPPs and develop a complementary programme. It shall proactively promote communications with external organizations to allow for normative referencing in ITU ‑ T Recommendations of mobile network specifications developed by those organizations. Study Group 13 will hold collocated meetings with Study Group 11.

8. 2. Questions and Structures Question #Question title 3/13 Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN 4/13 Requirements and frameworks for QoS enablement in the NGN 5/13 Principles and functional architecture for NGN (including ubiquitous networking) 7/13 Impact of IPv6 to an NGN 9/13 MM mechanisms supporting multi-connections for multiple access technologies 10/13 Identification of evolving IMT-2000 systems and beyond 12/13 Evolution towards integrated multi-service networks and interworking 15/13 Applying IMS and IMT in Developing Country mobile telecom networks 16/13 Security and identity management 17/13 Packet forwarding and deep packet inspection for multiple services in packet-based networks and NGN environment 19/13 Distributed services networking (DSN) 20/13 Public data networks 21/13 Future networks 22/13 Mobility management and Fixed Mobile Convergence 24/13 Service scenarios, deployment models and migration issues 25/13 Coordination, Planning, and Terminology

9. 2. Questions and Structures Structures of Working Parties WPTitleQuestions Chair Vice Chair 1 Coordination, planning and global outreach of NGN including mobile 10, 15, 25 Leo Lehman / Asok Chatterjee Simon Bugaba / Davoud D. Gorgeh 2 Service requirements, scenarios and evolution aspects 3, 12, 24 Liu Duo Konstantin Trofimov 3 Frameworks and functional architectures 5, 9, 22 Olivier Le Grand Mohammed Al Ramsi 4QoS and security4, 16, 17 Hui Lan Lu Haitham Chedyak 5Future networks7, 19, 20, 21 Naotaka Morita Maurice Ghazal

10. 3. Study Overview History of studies in SG13 ISDN IP-based Networks GII NGN IPTV IMT 2000 Future Networks I series Recommendations Y.100 series Recommendations Y.1000 series Recommendations Y.2000 series Rec Y.1900 series Rec Q.1700 Series Rec Not yet specified

11. 3. Study Overview  Requirements, architecture, evolution and convergence of future networks including IPv6 NGN and network aspects of IdM  IMT, wireless Internet, FMC, mobility management, mobile multimedia network functions, internetworking, interoperability and enhancements to existing ITU ‑ T Recommendations on IMT. Future Net- works

12. Future FMC Mobile Requirements Architectures QoS and Security Mobility Fixed NGN FMC IPTV Ubiquitous Networking USN/RFIDs Web based Open Environment Climate Change Future Networks Others Infrastructural Frameworks High level view of SG13 work scopes 3. Study Overview

13. Key efforts  NGN Capability Requirements: MM Communication Center, Charging & Accounting, IPTV-Net-CTRL, Service Integration & Delivery Environment, USN  NGN F&A: NACF, Content Delivery, FA on id-loc-split, IPTV- IDF, Open Service Environments  QoS & Security: RACF, Security Framework (NGN, Mobility, Certificate Mang., IdM, Mobile Financial), Deep Packet Inspection  New Features: IPv6 NGN (Ad-hoc, multi-homing, Object mapping etc.), Mobility Management (Control, VPN, Interworking, Service Stratum), Multi-Connection, IPTV Interworking, NGN-hn, Networked Vehicle, NGN-Web, Mobile VoIP, GHG monitoring service, Service Overlay Network, Distribute Service Networking, Public Telecommunication Data Network  Future Network: Vision, Requirements, Candidate technology (Virtualization etc.), Architecture etc.  Coordination and collaboration: Roadmap (NGN, IPTV), IMT 2000 related collaboration with mobile (e.g. 3GPP) 3. Study Overview

14. Status of NGN Developments 3. Study Overview SIDE OSE Y.2291

15. Assisting developing countries with Mobile, NGN others Cooperation with other SDOs and 3GPP In order to assist countries with economies in transition, developing countries, and especially least developed countries, in the application of IMT and related wireless technologies, consultations should be held with representatives of ITU ‑ D with a view to identifying how this might best be done through an appropriate activity conducted in conjunction with ITU ‑ D. Study Group 13 shall maintain strong cooperative relations with external SDOs and 3GPPs and develop a complementary programme. It shall proactively promote communications with external organizations to allow for normative referencing in ITU ‑ T Recommendations of mobile network specifications developed by those organizations. Support Developing regions (Mandates from Res. 2) 3. Study Overview

16. International Telecommunication Union 5. Meetings  12 - 23 January 2009, Geneva, SG 13  22 May 2009, Geneva, WPs 2,3 and 4/13  2 – 12 September 2009, Mar Del Plata, Argentina, SG 13  29 January 2010, Geneva, SG 13  19 – 30 April 2010, Geneva, SG 13  16 September 2010, Geneva, SG 13  17 – 28 January 2011, Geneva, SG 13  10 – 21 October 2011, Geneva, SG 13  4 – 15 June 2012, Geneva, SG 13

17. Working Party 1 Coordination, Planning, Global Outreach of NGN Including Mobile Leo Lehman, Asok Chatterjee WP 1/13 Co-Chairmen Orientation for New Attendees to SG 13 (Geneva, Switzerland, 17-28 January 2011) ‏

18. Working Party 1 of Study Group 13 Coordination, Planning, Global Outreach (WP1/13) ‏ QTitleRapporteurAssociate Rapporteur 25 Coordination, PlanningYoshinori GotoXin Chang and Terminology 10 Identification of Evolving IMT-2000 Systems and Beyond Nebojsa Dikic 15 Applying IMS and IMT in Developing Country Mobile Telecom Networks Simon Bugaba Co-Chairmen: Leo Lehman, Asok Chatterjee Vice chairmen: Simon Bugaba, Davoud Gordeh

19. Q.25 (Coordination, Planning and Terminology)

20. Role of Q25/13  Complex systems (such as NGN, IPTV) need robust program management  Q25 provides program management tool, and maintains ‘Road Map’ documents  Industry needs common language and unique terms for each concept, architectural element, protocol definition, etc. in order to guard against misunderstanding and confusion  Q25 collects, revises and publishes all relevant terms and definitions (related to NGN and future networks) in a dedicated ITU-T Recommendation

21. Q.10 (Identification of Evolving IMT- 2000 Systems and Beyond)

22. Role of Q10/13  IMT is perhaps the most recognized initiative spanning all three Sectors of ITU  IMT is developed by a number of globally recognized SDOs (at 3GPP and 3GPP2)  Q10/13 facilitates the recognition of these systems, and their adoption by the broader ITU community  Q10/13 produces Recommendations for IMT family members based on (1) GSM-evolved core with UTRAN/GERAN access, and (2) ANSI-41 evolved core with CDMA2000 access

23. Q.15 (Applying IMS and IMT in Developing Country Mobile Telecom Networks)

24. Role of Q15/13  There is a need to study requirements of telecom networks in developing countries with the increasing shift towards mobility and convergence  The work needs to be done in close cooperation between all three Sectors of ITU and relevant external organizations  Q15/13 develops scenarios and requirements, in terms of services and deployments, for applying IMT and IMS to mobile networks in developing countries

25. Working part 2 Service requirements, scenarios and evolution aspects Duo LIU WP 2/13 Chairlady CATR, China Introduction to new comers (Geneva, Switzerland, 17-28 January 2011) ‏

26. Future WP2 in SG 13 Requirements Architectures QoS and Security Q 10, 15, 25 & ITU-D, Mobile (3GPP) Overall Q 3, 12, 24 Q 5, 9, 22 Q 4, 16, 17 Q 7, 19, 20, 21 Classifications of Questions WP2

27. Questions and Management Team of WP2 Question Question titleRapporteur Associate Rapporteur 3/13 Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN Mr. Marco CARUGIMr. Tong WU 12/13 Evolution towards integrated multi-service networks and interworking Mr. Gyu Myoung LEE 24/13 Service scenarios, deployment models and migration issues Mr. Mingdong LI Mr. Heechang CHUNG Mr. Jiashun TU Mr. Hideaki YAMADA

28. Q3 Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN

29. Role of Q.3/13 Motivation Key requirements to be considered are ubiquitous support of: seamless end-to-end service operations, service access by mobile and wireline users, wireless/wireline technology independent service access, real time multimedia content delivery, unicast and multicast delivery technologies, SLAs and differentiated levels of quality of service, enhanced security, service mobility, service interworking, policy based capabilities, context based capabilities, user identification, authentication and authorization, service discovery, service routing, service brokering, service composition, and both IPv4 and IPv6 protocol technologies. Emerging services include IP multimedia telephony applications, IPTV applications, content delivery services, business/enterprise communications, ubiquitous sensor network based applications, identification based services, context aware services, third party services such as managed delivery services and others, applications of user networks (home networks), applications of grids and related enablers, VPNs and other network virtualization applications, managed peer to peer services, advanced data communication services, as well as other future applications and services based on composition of open service environment capabilities.

30. Role of Q.3/13 Tasks Development of Recommendations on emerging services in evolving next generation multi service network environments (requirements and capabilities, service and network architectures, implementation scenarios). Development of Recommendations on open service environment and SOA in evolving next generation multi-service network environments (including requirements for telecom SOA and telecom APIs, and capabilities and components of a SOA enabled open service environment). Completion of draft Recommendations currently under way. Revision of Y.2233 Maintenance and enhancement of the Recommendations for which the Question is responsible. Coordination with the NGN related Questions (in particular in the areas of NGN services and architectures). Coordination with standardization bodies, fora and consortia involved in standardization of SOA and application to network interface related aspects.

31. Recommendations in Q3/13 Y.1901Requirements for the support of IPTV services Y.2201Requirements and capabilities for ITU-T NGN Y.2201 Rev.2Requirements and capabilities for ITU-T NGN Y.2215 Requirements and framework for the support of VPN services in NGN including mobile environment Y.2216 NGN capability requirements to support multimedia communication centre (MCC) service Y.2221 Requirements for support of Ubiquitous Sensor Network (USN) applications and services in the NGN environment Y.2233 Rev.1 Requirements and framework allowing accounting and charging capabilities in NGN Y.2236Framework for NGN support of multicast-based services Y.2807MPLS-based mobility capabilities for NGN services

32. Documents under study in Q3/13 Y.iptv-netcontrol-fwIPTV network control framework Y.IPTV-Serv-Provision Framework for IPTV service provisioning using IPTV identifiers: concepts, use cases and requirements Y.miptv-reqFunctional requirements of Mobile IPTV Y.NGN-SIDE-Req Requirements for NGN service integration and delivery environment

33. Q12 Evolution towards integrated multi-service networks and interworking

34. Role of Q.12/13 Motivation The rapid growth and the embedded base of legacy telecommunications networks have necessitated a strategy of evolution towards integrated multi- service networks which connect to enterprise and home networks. Due to popularity of the IPTV and transformation of networks to NGN it has become necessary to include study of home networks. Thus the focus of this Question will include activities related to IP television (IPTV) and home networks. This Question will address items such as: determination of how best to carry narrow-band and broadband services of a fully integrated IP-based network across non-IP based networks (e.g. FR and ATM); description of interworking of services, including definition of protocol requirements; interworking of services between home network operator administered networks.

35. Role of Q.12/13 Tasks Creation of, maintenance and enhancement to the Recommendations in Y.1400 series Maintenance of Recommendations Y.2261, Y.2262 and Y.2271 Maintenance and enhancement to the Recommendations in I.500 series Maintenance and enhancement to Recommendations Q.933, Q.933bis, X.36, X.76, X.84, X.142, X.144, X.145, X.146, X.147, X.148, X.149, X.151 and X.272 and the development of new Recommendations as deemed necessary Completion of draft Recommendations already under discussion in Questions 12/13 Development of new Recommendations related to home network and their interworking aspects with the operator administered networks Development of new Recommendations related to interworking to support IPTV services

36. Documents in Q12/13 Y.1911 IPTV services and nomadism: scenarios and functional architecture for unicast delivery Y.2281Framework of networked vehicle using NGN Y.2291Framework for home network using NGN architecture Recommendations Documents under study Y.ipevInterworking between NGN and legacy IP-based networks Y.IPTVintwVoDIPTV interworking for VoD services Y.NGN-Web Functional requirements and architecture of Web service component in NGN Y.UbiNet-hnFramework of home network using ubiquitous networking Y.WoTFramework of Web of Things using NGN

37. Q24 Service scenarios, deployment models and migration issues

38. Role of Q.24/13 Motivation As NGN and Future Networks scope covers wide areas of network, a set of promising service scenarios and deployment models of NGN and Future Networks are very useful to accelerate the NGN and Future Networks deployment. All the scenarios should be initiated from the user point of views, which would be described as use cases. At the same time, operators of existing telecommunication networks have expressed concerns connected with the necessity of full replacement of their network equipment when migrating from traditional telecommunication networks to NGN and Future Networks. For Future Networks, more and more new technologies will be introduced, e.g. Cloud Computing, IoT, etc. The architecture and deployment of Future Networks will be probably largely different from the existing telecommunication networks. Foregoing requirements will be still available when existing telecommunication networks or NGN migrate to Future Networks.

39. Role of Q.24/13 Tasks Develop documents on NGN and Future Networks service scenarios including emerging services and converged services. Develop documents on NGN and Future Networks based IPTV service scenarios that converge traditional broadcasting services and telecommunication services over the NGN and Future Networks environment. Develop documents on service scenarios of use cases and 3rd party services for ubiquitous environments. Develop documents on migration scenarios to NGN and Future Networks. Develop documents on decision factors for selecting migration scenarios and migration criteria through analysis of the scenarios. Continue documents currently under way. Documents produced under this Question will normally be published as Supplements or will progress through, or in coordination with, other related Questions.

40. Recommendations in Q24/13 Y.2214 Service requirements and functional models for Customized Multimedia Ring services Y.2235 Converged web-browsing service scenarios in NGN Y.2237 Functional model, service scenarios and use cases for QoS enabled mobile VoIP service

41. Supplements in Q24/13 Supplement 13 to Y.2000-series (Y.NGN-ncescen) Scenarios for evolution of NGN to enhanced network capability Supplement 14 to Y.2000-series (Y.sof) Service scenarios over FMC

42. Documents under study in Q24/13 Y.gmsGHG monitoring service scenario on NGN Y.hapas Heterogeneous application profiles adaptation service scenario over NGN Y.iptvbsIPTV service brokering service scenarios Y.irasIT Risk analysis service over NGN Y.miptv-scen Supplement Service scenarios and use cases of mobile IPTV Y.passProfile based application adaptation service over NGN H.andbook on IMT-2000 (2nd Edition) The Handbook of evolving IMT-2000 Systems Y.son-ngnFunctional model of service overlay network using NGN

43. Working part 3 Frameworks and functional architectures Olivier LE GRAND WP 3/13 Chairman France Telecom Orange, France Introduction to new comers (Geneva, Switzerland, 17-28 January 2011) ‏

44. Future WP3 in SG 13 Requirements Architectures QoS and Security Q 10, 15, 25 & ITU-D, Mobile (3GPP) Overall Q 3, 12, 24 Q 5, 9, 22 Q 4, 16, 17 Q 7, 19, 20, 21 Classifications of Questions WP3

45. Questions and Management Team of WP3 QuestionQuestion titleRapporteur Associate Rapporteur 5/13 Principles and functional architecture for NGN (including ubiquitous networking) Mr. Keith KNIGHTSON (Industry Canada, Canada) Mr. Yoshinori GOTO (NTT, Japan) Mr. Yuan ZHANG (China Telecom, China) 9/13 MM mechanisms supporting multi-connections for multiple access technologies Mr. Yachen WANG (China Mobile, China) Mr. Oscar LOPEZ TORRES (Inter Digital, United States) 22/13 Mobility management and fixed mobile convergence Mr. Woo-jin CHOI (KT, Korea) Ning ZONG (Huawei, China)

46. Q5 Principles and functional architecture for NGN (including ubiquitous networking)

47. Role of Q.5/13 Motivation To establish a set of common principles and architectures for the convergence among services and networks Substantial studies and frameworks are required to: - ensure interoperability of networks and applications; - facilitate innovation in the use and application of industry capabilities; - facilitate best utilization of the existing telecommunications infrastructure; - facilitate mobility of users and devices.

48. Role of Q.5/13 Tasks General reference models of the NGN : identify the basic architectural compositions of the NGN, including support for ubiquitous networking. This will include development of models and functions taking consideration of various networking requirements for IPTV, RFID-based services, and connection to USN (ubiquitous sensor networks), home networks,… Functional requirements and architectures for ubiquitous networking via NGN: Identification of entities, their functions, and reference points, required to provide telecommunications services to support ubiquitous networking. Reference model and functions for customer manageable and home networks: Develop models and functions to allow customers to create, configure, customize, and otherwise customize the network services/resources allocated to them by the network provider, and to allow involvement of third parties in the development of network-supported applications. Implementation framework related to provision of emergency telecommunications in NGNs (including ubiquitous network environments)

49. Recommendations in Q5/13 Y.2001General overview of NGN Y.2002 Overview of ubiquitous networking and of its support in NGN Y.2011General principles and general reference model for NGN Y.2012Functional requirements and architecture of NGN Y.2014Network attachment control functions in NGN Y.2015General requirements for ID/locator separation in NGN Y.2016 Functional requirements and architecture of the NGN for applications and services using tag-based identification Y.2017Multicast functions in NGN Y.2018 Mobility management and control framework and architecture within the NGN transport stratum Y.2019Content delivery functional architecture in NGN Y.2021IMS for Next Generation Networks Y.2031PSTN/ISDN emulation architecture Y.2205 NGN - Emergency telecommunications - Technical considerations Y.1910IPTV functional architecture

50. Y.2012: NGN overview architecture

51. Y.1910: IPTV functional architecture

52. Documents under study in Q5/13 Supplement Y.iptv-ipmcast Guidelines on deployment of IP multicast for IPTV service delivery Y.2205 rev1 NGN - Emergency telecommunications - Technical considerations Y.FAid/locFunctional architecture of Id-Loc-split in NGN Y.IPTV-IDFService delivery information platform for IPTV Y.iptv-netcontrol-faFunctional architecture aspects of IPTV network control Y.MCC-arch Functional requirements and architecture for the NGN for Multimedia Communication Centre service Y.2014 rev2 Network attachment control functions in Next Generation Networks Y.OSE-archOpen Service Environment Functional Architecture for NGN Y.NGN-SIDE-archNGN SIDE functional architecture Y.USN-archUbiquitous Sensor Network (USN) functional architecture

53. Q9 MM mechanisms supporting multi-connections for multiple access technologies

54. Role of Q.9/13 Motivation Different types of network connections may provide users with different user experiences, such as broad bandwidth, low time delay, and high security. The main purpose of multi- connection is to federate all means of access technologies in order to access the network ubiquitously (from everywhere and at any time), benefit from different advantages of multiple access technologies, and help us to provide better user experience Users and operators may benefit from harmonization of multiple connections, such as efficient utilization of network resources, load balancing, reliability of connection and continuity of services, etc

55. Role of Q.9/13 Tasks Explore the scenarios and the policies for multiple connection harmonization in mobile networks utilizing fixed and mobile accesses Identify and study enhancements to existing Recommendations related to service requirements for the harmonization of multiple connections for multiple access technologies. Develop high-level network architecture enhancements to support the harmonization of multiple connections for multiple access technologies. Study Multi-connection Technical Issues: Routing mechanism 、 Multi- connection based services such as Streaming, conference etc 、 Study UE functions in multi-connection ， coordination among multiple connections. Identify which MM mechanisms are required to provide service continuity through multi connection in multiple access networks and at the same time their effect to provide unawareness of such functions to multimedia services. Identify which QoS mapping mechanisms among RATs need to be executed in multiple connection harmonization to provide networks with acceptable levels of quality of perception.

56. Documents in Q.9/13 Supplement 9 – Y.2000 series (Y.MC-SCEN) Supplement on multi-connection scenarios Documents approved Documents under study Y.MC-REQ Requirements of multi-connection Y.MC-ARCH Architecture of Multi-connection Y.MC-ID Identification and configuration of resources for Multi- Connection Y.MC- Streaming Streaming service based on MC architecture

57. Q22 Mobility management and fixed mobile convergence

58. Role of Q.22/13 Motivation Towards the ultimate migration to interoperable network, there is an industry requirement to provide global roaming and seamless mobility for the users of different access technologies and/or different operators. The work of Mobility Management and Fixed Mobile Convergence includes all aspects required in terminals, customer networks, access networks (both wired and wireless), core networks and application services.

59. Role of Q.22/13 Tasks Develop the functional requirements for mobility management capabilities for both IMT and NGN. Develop the architecture (interrelationship) and definition of the functional entities, information flows required to provide mobility management capabilities for both IMT and NGN. Allocate the functional entities to physical entities in order to determine which interfaces can use existing protocols or enhancements to existing protocols and which interfaces need protocol development for mobility management capabilities for both IMT and NGN. Identify and study the applicability of convergence related evolving IMT- standards in the context of the NGN architecture and FMC requirements and document these. Identify and study architectural and network interface issues relating to FMC specific functions in the overall NGN architecture, and document these.

60. Recommendations in Q22/13 Q.1706 / Y.2801Mobility management requirements for NGN Q.1707 / Y.2804Generic framework of mobility management for NGN Q.1708 / Y.2805Framework of Location Management for NGN Q.1709 / Y.2806Framework of Handover Control for NGN Q.1762 / Y.2802Fixed-mobile convergence general requirements Q.1763 / Y.2803 FMC service using legacy PSTN or ISDN as the fixed access network for mobile network users Y.2808FMC with a common IMS session control domain

61. Y.MM-VPNMobile VPN Framework for NGN Y.MM-WAU Mobility management for interworking between WiMax and UMTS Y.MM-WAW Mobility management for interworking between WiMAX and WLAN Y.MMC Mobility Management Framework for Multicast Communications in NGN Y.MMSMobility management control scenarios for NGN Y.MobileP2P Mobility supporting architecture for mobile P2P service in heterogeneous wireless networks Y.SMF Framework of Mobility Management in Service Stratum for NGN Documents under study in Q22/13

62. International Telecommunication Union Introduction to WP 4/13 on QoS and Security Hui-Lan Lu, Ph.D. (Alcatel-Lucent, USA) Vice Chairman of SG 13, Chairman of WP 4/13 huilan.lu@alcatel-lucent.com Newcomer Orientation ITU-T SG 13 Meeting, Geneva, 17-28 January 2011

63. Outline  Basic driver for QoS and security  Structure of WP 4/13  Work program of underlying Question  Q.4/13 on QoS  Q.16/13 on security and Identity Management (IdM)  Q.17/13 on Deep Packet Inspection (DPI)  Summary

64.  Applications have diverse bandwidth and performance needs  User devices have evolving and varied capabilities  Different access technologies are in use  Multiple providers and walled gardens are involved end- to-end  Networks and communications are vulnerable to attacks Motivation: Basal packet transport lacks inbuilt support for hard security and QoS NGN Core 802.xx Access 3G/LTE Cable DSL

65. Security may mean…  Limitation of data disclosure  Privacy  Anonymous communications  Prevention of changing data  Law enforcement  destruction of pirated content  tracking criminals  monitoring enemy’s communications

66. QoS may mean…  Satisfactory bandwidth or network performance (e.g., delay, jitter, packet error ratio, and packet loss ratio)  Satisfactory application performance, such as signal-to-noise ratio, lip sync, channel change delay, and post dialling delay  Carrier-grade network reliability  Robust communication security  Quality of experience  Collective effect of service performance which determines the degree of satisfaction of a user of the service (as defined in E.800)

67. Chairman: Hui-Lan Lu (Alcaltel-Lucent, USA) Vice Chairman: Haitham CHEDYAK (STE, Syrian Arab Republic )  Q.4/13 - Requirements & frameworks for QoS enablement in the NGN  Rapporteur: Taesang Choi (ETRI);  Associate Rapporteurs: Dong Sun (Alcatel-Lucent), Daoyan Yang (Huawei)  Q.16/13 - Security and identity management  Rapporteur: Igor Faynberg;  Associate Rapporteur: Igor Milashevskiy (Intervale)  Q.17/13 - Packet forwarding and deep packet inspection for multiple services in packet-based networks and NGN environment  Rapporteur - Meng Ji (Wuhan Fiberhome Networks) Working Party 4/13 QoS Security

68. Question 4/13 Work Program Y.2111 (RACF) Y.2171 Y.2112 Y.2113 Y.2173 Y.2172 Y.IPTV-TM ? Y.2121, Y.2122 admission priority restoration priority performance management resource authorization Resource and admission control Y.2174, Y.2175 Q.330x.x (SG 11) Ethernet-based IP access network Ethernet MPLS core network Protocol specifications Flow-aware transport Other related studies Y.QMFY.VNC +…

69. Resource and Admission Control Functions (RACF) Other Networks Service Control Functions Transport stratum Service stratum Management Functions ServiceUser Profiles Service User Profiles Transport User Profiles Control Media Management Application/Service Functions 3 rd Party Applications ANI End-User Functions Transport Control Functions Resource & Admission Control Functions Network Attachment Control Functions Network Attachment Control Functions Transport Functions NNI UNI (Ref.: ITU-T Rec. Y.2012) Resource and Admission Control Functions (RACF)  Provide application-driven, policy-based resource management to dynamically assure QoS and enforce network security measures  Address unicast/multicast, fixed/mobile, and CPE/CPN requirements

70. Policy Decision Functional Entity (PD-FE) Authorize resource requests based on policy Configure the transport to enforce policy Transport Resource Control Functional Entity (TRC-FE) Track resource use & network topology Make resource-based admission decision Policy Enforcement Functional Entity (PE-FE) Enforce policy for NAPT, gating, rate limiting, packet marking, etc. typically part of border transport elements (e.g., edge router and border gateway) service-facing, transport-independent service-independent, transport-dependent, segment-specific Resource and Admission Control Functions (RACF) Rs (Diameter) Rw (H.248, COPS, Diameter) Service Stratum Transport Functions (multicast-aware ) PD-FE TRC-FE RACF Transport Stratum Service Control Functions Rt (Diameter) Rd Rp (COPS) Rc (COPS, SNMP) Rn (Diameter) Ru Ri TRE-FEPE-FE Network Attachment Control Functions intra-domain inter-domain Other NGN s CPE/CPN Rh (Ref.: ITU-T Rec. Y.2111 Rev. 1, 11/2008)

71. Question 16/13 Work Program Mobility Security Framework in NGN Y.2740 Security Requirements for Mobile Financial Transactions in NGN Y.2741 Architecture for Secure Mobile Financial Transactions in NGN Y.2704 NGN Security Mechanisms NGN Certificate Management Y.2703 NGN AAA Y.2720 NGN IdM Framework Y.2722 NGN IdM Mechanisms Y.2701 Security Requirements for NGN Release 1 Y.2721 NGN IdM Requirements and Use Cases Y.2702 NGN Authentication and Authorization Requirements Determined draft Recommendation IdM and Security for Cloud Services Note: Recommendations produced by Q.16/13 are approved through the TAP.

72. NGN IdM Framework (ITU-T Rec. Y.2720, 1/2009) Users & Subscribers Organizations, Business Enterprises, Government Enterprises User Devices Network Elements and Objects Network and Service Providers Virtual Objects Entities Identity Lifecycle Management Correlation and Binding of Identity Information Authentication,Assurance, andAssertionof Identity Information DiscoveryandExchangeof Identity Information IdM Capabilities Identifiers (e.g., User ID, email address, telephone number, URI, IP address) Credentials (e.g., digital certificates, tokens, and biometrics) Attributes (e.g., roles, claims, context, privileges, location) Identity Information Federated Services Application Access Control (e.g., Multimedia and IPTV) Single Sign-on/Sign-off Role-based Access to Resources Protection of Personally-Identifiable Information Security Protection of Information and Network Infrastructure Business and Security Services Identity Management

73. Question 17/13 Work Program DPI Requirements (Y.dpireq) DPI Framework (Y.dpifr) Security Charging QoS Application Scenarios Q.16/13 Q.4/13 AnalysisEnforcement Rules TableDPI Scan

74. Summary  WP 4/13 is addressing QoS and security issues in NGN and beyond  A set of Recommendations has been developed  Y.2111 specifies RACF—the central enabler for NGN QoS  Y.2701 and Y.2702 set the basic security requirements for NGN  Y.2720 provides a holistic view of IdM in NGN and lays the foundation for further development  Ongoing studies include  IdM requirements and mechanisms, and securing mobile financial transactions (expected to be complete at this meeting)  Security requirements for DSN (jointly with Q.19/13)  Enhancements of RACF in support of mobility, and coordination with network performance management and CPN resource management  Deep packet inspection-enabled QoS and security control  An emerging focus is on resource management and security support for cloud services  Cooperation among related efforts in various SDOs (3GPP, ATIS, ETSI TISPAN, IETF, OMA, etc.) is essential for effective support of QoS and security end-to-end

75. Working party 5 – Future networks Naotaka Morita WP 5/13 Chairman NTT, Japan Introduction to new comers (Geneva in Switzerland, 19 January 2011) ‏

76. Working Party 5 of Study Group 13 Future Networks (WP5/13) ‏ QTitleRapporteurAssociate Rapporteur 7Impact of IPv6 on NGN Hyoung Jun KIM ETRI/SRC, Korea (Rep. of)‏ Sheng JIANG Huawei, China 19 Distributed services networking (DSN) Jin PENG China Mobile, China Shin-Gak KANG ETRI, Korea (Rep. of)‏ 20Public data networks Lintao JIANG CATR, China Kentaro OGAWA NTT, Japan & Jiguang CAO CATR, China 21Future networks Takashi EGAWA NEC, Japan & Myung-Ki SHIN ETRI, Korea (Rep. of)‏ Alojz HUDOBIVNIK Iskratel Slovenia Chairman: Naotaka Morita, NTT, Japan Vice chairman: Maurice Ghazal, Lebanon

77. Q.7 - Impact of IPv6 on NGN

78. Role of Q.7/13 Q7/13 studies the impact of IPv6 and how to apply IPv6 to NGN with alignment of the reference model and functional architecture of NGN. Given the concept of IPv6-based NGN, the extension of IPv6 issues might be necessary for supporting future network environments.  Q7/13 – Impact of IPv6 on NGN

79. Documents in Q.7/13  Recommendations  On going works Y.2051 General overview of IPv6-based NGN (Y.ipv6-ngn) ‏ Y.2052 Framework of multi-homing in IPv6-based NGN(Y.iptv6multi) ‏ Y.2053 Functional requirements for IPv6 migration in NGN(Y.ipv6transit) ‏ Y.2054Framework to support signalling for IPv6-based NGN(Y.ipv6sig) ‏ Y.ipv6-vmhFramework of Vertical Multi-homing in IPv6 based NGN Y.ipv6splitFramework of ID/LOC separation in IPv6-based NGN Y.ipv6-objectFramework of object mapping using IPv6 in NGN Y.ipv6naFunctional requirement for network access in IPv6 based NGN Y.ipv6migrationRoadmap for IPv6 Migration from NGN Operators’ Perspectives Y.ipv6-cvmhCognitive Vertical Multi-homing in IPv6-based NGN And more

80. Current work in Q.7/13 (1/2) ‏  Future works on NGNv6 (1/2) ‏  Interworking based on NGNv6 Within NGN: NGNv6  NGNv4 (RP 1b and 2b) ‏ With Non-NGN: NGNv6  IPv6 (RP 3a), NGNv6  IPv4 (3b) ‏ Specify Reference Points and Interworking Functions Service Features, Operation and Provision issues

81. Current work in Q.7/13 (2/2) ‏  Future works on NGNv6 (2/2) ‏  Advanced issues on NGNv6 Framework of ID and location separation on NGNv6 Framework of object mapping on NGNv6 Vertical multi-homing on NGNv6, etc. Converged Broadband (Fixed+Mobile) ‏ Managed IP IPv6 based IPv4 based VoiceFMCIPTVMMUSNFull-CARNet-Rob

82. Y.2055 (Y.ipv6-object) Framework of Object Mapping using IPv6 in NGN  This Recommendation describes requirements and mechanisms for object mapping using IPv6 in NGN.  Basic concept and requirements of object mapping using IPv6  Mapping architecture and relationships between identifiers  Mechanisms for object mapping using IPv6  Direct mapping vs. Indirect mapping  Direct mapping: An object at application layer is directly reachable to host entity at Point of Attachment (PoA) which IP is terminated.  Indirect mapping: An object at application layer is remotely reachable through non-IP interface to host entity at PoA which IP is terminated. An object is located outside of physical network attachment which IP is terminated.

83. Object identification through identity processing in IPv6-based NGN (Y.2055)

84. Major results of Q.7/13 in 1/2011 IPv6  Improved four ongoing drafts.  Consented draft Y.ipv6-object (Y.2055).  Prepared two drafts on migration and vertical multi-homing (vmh) targeted for consent in 5/2011.

85. Documentation for Q.7/13 in 1/2011 DocumentTitleResults TD138(WP5)Report for Q.7 TD168(PLEN)Y.ipv6-objectConsented TD129(WP5)Y.ipv6na TD128(WP5)Y.ipv6migrationTarget for 5/2011 TD127(WP5)Y.ipv6split TD120(WP5)Y.ipv6-vmhTarget for 5/2011

86. Q.19 - Distributed services networking (DSN)

87. 87 Scenarios of DSN - Leveraging peer-to-peer technology VoIP scenario: Core Nodes constitute a P2P overlay to locate users User Node can be selected as relay node to help NAT traverse and improve QoS Streaming scenario: Core Nodes constitute a P2P overlay to locate media resource Core Nodes and User Nodes constitute a tree or mesh to deliver media

88. 88 Capabilities of DSN 88 Transport connectivity Media resource management QoS Accounting and charging Numbering, naming and addressing Identification, authentication and authorization Mobility management Distributed technologies introduced Transport connectivity Media resource management Routing QoS Accounting and charging Numbering, naming and addressing Identification, authentication and authorization Mobility management Continuous service delivery Self adaptive load balance Bandwidth convergence Self organization Distributed resource storage Intelligent routing Dynamic resource scheduling Multi connection application layer enablement New mechanisms for numbering, naming and addressing added value

89. Documents in Q.19/13  Recommendations and Supplements  On going works Y.Suppl. 10 ITU-T Y Suppl.10: ITU-T Y.2000-series - Supplement on distributed service network (DSN) use cases Y.2206Requirements for distributed service network (DSN) Y.dsn_sec_reqSecurity Requirements for DSN Y.DsnarchArchitecture of DSN Y.dsntocfDSN Traffic optimization control function Y.DsnrfDSN Relay Function Y.dsnmmtelMultimedia Telephony over DSN Y.dsncdfDSN Content Delivery Function

90. Major results of Q.19/13 in 1/2011 Distributed Service Networking  Improved ongoing drafts.  Y.dsntocf (DSN Traffic Optimization Function)  Y.dsnrf (DSN Relay Function)  Y.dsn_sec_req (DSN Security Requirements)  Y.dsnmmtel (Multimedia Telephony over DSN)  Y.dsncdf (DSN Content Delivery Function)  Prepared draft Y.dsnarch targeted for consent in 5/2011  Planned Rapporteur meetings in April, May (GSI), July, and October (SG13).

91. Documentation for Q.19/13 in 1/2011 DocumentTitleNote TD119r1(WP5)Report for Q.19 TD118(WP5)Y.dsncdf TD117(WP5)Y.Dsnmmtel TD116(WP5)Y.dsn_sec_req TD115(WP5)Y.Dsnrf TD114(WP5)Y.Dsntocf TD113(WP5)Y.DsnarchTarget for 5/2011 TD174(PLEN)LS to SG17 on X.p2p Produced with Q.16/13

92. Q.20 - Public data networks

93. Role of Q.20/13 Question 20/13 – Public Data Networks (PDN) NGN services e.g., Voice telephony services (audio, fax, etc.) ‏ e.g., Data services (WWW, e-mail, etc.) ‏ e.g., Video services (TV, movie, etc.) ‏ CO-PS and CL-PS layer technologies PDN NGN transport PDN focuses on the topmost part of NGN transport stratum to meet the industry requirements for enhanced data communications, such as better scalability, throughput, reliability, multipoint to multipoint communication, QOS, etc.

94. Current work in Q.20/13 (1/2) ‏  Works on PDN candidates ——Y.2613:The general technical architecture for Public packet Telecom Data Network (PTDN) ‏ Architecture and reference model Data link layer Network layer Addressing & numbering Routing & switching OAM Interworking Security Performance

95. Current work in Q.20/13 (2/2) ‏  Works on iSCP (Independent Scalable Control Plane ） ——Y.iSCP-scen: Scenarios for independent scalable control plane in FPBN. ——Y.iSCP-req: Requirements of independent Scalable Control Plane (iSCP) in FPBN. ——Y.iSCP-arch: Architecture of independent Scalable Control Plane (iSCP) in FPBN. Control plane network

96. Documents in Q.20/13  Recommendations and Supplements  On going works Y.2601 Fundamental characteristics and requirements of future packet based networks Y.2611 High level architecture of future packet based networks Y.2612 Generic requirements and framework of FPBN addressing, routing and forwarding Y.2613 The general technical architecture for public packet telecommunication data network (PTDN) Y.Suppl. 11 Y.2600-series - Supplement on scenarios for independent scalable control plane (iSCP) in future packet based networks (FPBN) Y.PTDN-reliabilityThe network reliability in PTDN Y.PTDN-routingThe routing mechanism in PTDN Y.iSCP-reqRequirements of independent Scalable Control Plane (iSCP) Y.iSCP_ArchArchitecture of independent Scalable Control Plane (iSCP) Y.PTDN-M-IFInterface M between management element and PTDN nodes Y.PTDN-T-IF Interface T between address translator and edge device for address mapping/ translation

97. Major results of Q.20/13 in 1/2011 Packet Date Networks  Improved three ongoing drafts.  Initiated two new drafts on M- and T- interfaces  Interface M between management element and PTDN nodes  Interface T between address translator and edge device for address mapping/ translation  Prepared drafts Y.PTDN-reliability and Y.iSCP-req targeted for consent in 5/2011

98. Documentation for Q.20/13 in 1/2011 DocumentTitleNote TD126r1(WP5)Report for Q.20 TD125(WP5)Y.PTDN-M-IF TD124(WP5)Y.PTDN-T-IF TD123(WP5)Y.iSCP-reqTarget for 5/2011 TD122(WP5)Y.PTDN-reliabilityTarget for 5/2011 TD121(WP5)Y.PTDN-routing

99. Q.21 - Future Networks

100. Role of Q.21/13 Question 21/13 – Future networks Future network - A network able to provide revolutionary services, capabilities, and facilities that are hard to provide using existing network technologies (ITU-T Q.21/13 Jan. 2009 meeting report ).  FN is the network of the future: made using Clean-slate Design.  It should provide futuristic functionalities beyond the limitations of the current network including Internet (IP).  FN provides mechanisms that benefit every participant as much as they contribute.  Backward compatibility may or may not be required. [Note] : Clean-slate approach is understood as a design principle, not deployment aspect.

101. Focus group on Future Networks  The group was established in 2009. The objectives were to gather new ideas, identify potential study areas, describe vision with a targeted timeframe, and suggest future actions.  In 2009 and 2010, FG held eight meetings led by Mr. Takashi Egawa, NEC, Japan, and collocated with FN-related academic events. Project descriptions in 135 pages summarizes the research activities.  As a Future Networks vision, FG has found new requirements for networks, and identified four objectives (service-, data-, environment-, and social and economic awareness), and twelve design goals. It is assumed that the target date for trial services and phased deployment of FNs falls roughly between 2015 and 2020. The document becomes a good candidate for the first Recommendation (Y.3001) on Future Networks.  FG identified three technology areas likely to be used:  Network virtualization,  Energy-savings of networks, and  Identifiers and Identification processes.

102.  Definition of FN:  A network able to provide services, capabilities, and facilities difficult to provide using existing network technologies.  A Future Network is either:  Target Date: roughly 2015-2020 a)A new component network or an enhanced version of an existing one, or b)A heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network. Vision of Future Networks (Y.3001) 4 objectives and 12 design goals Service awareness Data awareness Social and economic awareness Environmental awareness Energy Consumption Optimization Service Universalization Economic Incentives Service Diversity Functional Flexibility Virtualization of Resources Network Management Mobility Reliability and Security Data Access Identification

103. Major results of Q.21/13 in 1/2011 Future Networks  Successfully received FG-FN outputs  Determined draft Y.FNvison (Y.3001) under TAP process  Initiated three drafts on network virtualization, energy saving, and IDs.  Initiated seeking collaboration with JTC1/SC6 via common mailing list  fncollaboration@lists.itu.int

104. Documentation for Q.21/13 in 1/2011 DocumentTitleNote TD131r1(WP5)Report for Q.21 TD137(WP5)Y.FNterm, Moved to Q.25 Target of the end of 2012 TD135(WP5)Y.FNidentifierTarget for the end of 2012 TD134(WP5)Draft on E-savingTarget for 10/2011 TD133(WP5)Draft on FNvirtTarget for 10/2011 TD182(PLEN)Y.3001Determined TD200(PLEN)6 LSs

105. Information about Cloud Computing

106. Current discussion in Focus Group on cloud computing  The focal point in ITU-T is FG-cloud.  http://www.itu.int/en/ITU- T/focusgroups/cloud/Pages/default.aspx  Definitions are being considered.  Cloud Computing: an emerging IT development, depl oyment and delivery model, enabling on- demand delivery of products, services and solutions over any network and for any devices (i.e., enabling Cloud Services)  Cloud Services: Services that are delivered and cons umed on demand at any time, through any access ne twork and using any connected devices using cloud c omputing technologies.

107. International Telecommunication Union Future plans

108.  All Questions under WP5 will join the next NGN-GSI in May 2011 in Geneva.  Q.19/13 will meet in April 2011, too. SunMonTueWedThusFriSat 891011121314 151617181920 SG13 21