Presentation on theme: "Future networks including mobile and NGN Chairman: Mr Chaesub Lee"— Presentation transcript:
1Future networks including mobile and NGN Chairman: Mr Chaesub Lee SG13 –Future networks including mobile and NGNChairman: Mr Chaesub Lee(ETRI, Korea, Rep. of)TSB: Ms Tatiana KurakovaSupported by Ms Gabrielle Regan1
2CONTENTSMission and Mandates of SG 13Management and StructuresStudy OverviewWorking Party Activities: from each WP ChairsMeetings
3Leading Study Group roles of ITU-T SG13 1. Mission and Mandates of SG 13Leading Study Group roles of ITU-T SG13SG13 was NGN groupSG13 covers ‘Future networks including mobile and NGN’WTSA 2008WTSA 2004Lead study group for NGN and SatelliteLead study group for Future Networks and NGNLead study group on Mobility Management and Fixed-Mobile Convergence
4Responsibility of ITU-T SG13 (Res. 2) 1. Mission and Mandates of SG 13Responsibility of ITU-T SG13 (Res. 2)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.
5Mandated Scopes of ITU-T SG13 (Res. 2) 1. Mission and Mandates of SG 13Mandated 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.
6Mandated Scopes of ITU-T SG13 (Res. 2) 1. Mission and Mandates of SG 13Mandated Scopes of ITU-T SG13 (Res. 2)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.
7Mandated Scopes of ITU-T SG13 (Res. 2) 1. Mission and Mandates of New SG 13Mandated 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.
82. Questions and Structures Question title3/13Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN4/13Requirements and frameworks for QoS enablement in the NGN5/13Principles and functional architecture for NGN (including ubiquitous networking)7/13Impact of IPv6 to an NGN9/13MM mechanisms supporting multi-connections for multiple access technologies 10/13Identification of evolving IMT-2000 systems and beyond12/13Evolution towards integrated multi-service networks and interworking15/13Applying IMS and IMT in Developing Country mobile telecom networks16/13Security and identity management17/13Packet forwarding and deep packet inspection for multiple services in packet-based networks and NGN environment19/13Distributed services networking (DSN)20/13Public data networks21/13Future networks22/13Mobility management and Fixed Mobile Convergence24/13Service scenarios, deployment models and migration issues25/13Coordination, Planning, and Terminology
92. Questions and Structures Structures of Working PartiesWPTitleQuestionsChairVice Chair1Coordination, planning and global outreach of NGN including mobile10, 15, 25Leo Lehman / Asok ChatterjeeSimon Bugaba / Davoud D. Gorgeh2Service requirements, scenarios and evolution aspects3, 12, 24Liu DuoKonstantin Trofimov3Frameworks and functional architectures5, 9, 22Olivier Le GrandMohammed Al Ramsi4QoS and security4, 16, 17Hui Lan LuHaitham Chedyak5Future networks7, 19, 20, 21Naotaka MoritaMaurice Ghazal
103. Study Overview History of studies in SG13 ISDN I series RecommendationsGIIY.100 series RecommendationsIP-based NetworksY.1000 series RecommendationsY.2000 series RecNGNY.1900 series RecIPTVIMT 2000Future NetworksQ.1700 Series RecNot yet specified
113. Study OverviewRequirements, architecture, evolution and convergence of future networks including IPv6 NGN and network aspects of IdMIMT, wireless Internet, FMC, mobility management, mobile multimedia network functions, internetworking, interoperability and enhancements to existing ITU‑T Recommendations on IMT.FutureNet-works
12High level view of SG13 work scopes 3. Study OverviewHigh level view of SG13 work scopesNGNFMCIPTVUbiquitous NetworkingUSN/RFIDsWeb basedOpen EnvironmentClimate ChangeFuture NetworksOthersRequirementsArchitecturesQoS and SecurityMobilityFutureFixedFMCMobileInfrastructural Frameworks
133. Study Overview Key efforts NGN Capability Requirements: MM Communication Center, Charging & Accounting, IPTV-Net-CTRL, Service Integration & Delivery Environment, USNNGN F&A: NACF, Content Delivery, FA on id-loc-split, IPTV-IDF, Open Service EnvironmentsQoS & Security: RACF, Security Framework (NGN, Mobility, Certificate Mang., IdM, Mobile Financial), Deep Packet InspectionNew 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 NetworkFuture Network: Vision, Requirements, Candidate technology (Virtualization etc.), Architecture etc.Coordination and collaboration: Roadmap (NGN, IPTV), IMT 2000 related collaboration with mobile (e.g. 3GPP)13
14Status of NGN Developments 3. Study OverviewStatus of NGN DevelopmentsSIDEOSEY.229114
153. Study Overview Support Developing regions (Mandates from Res. 2) 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.Assisting developing countries with Mobile, NGN othersCooperation with other SDOs and 3GPP
165. Meetings 12 - 23 January 2009, Geneva, SG 13 22 May 2009, Geneva, WPs 2,3 and 4/132 – 12 September 2009, Mar Del Plata, Argentina, SG 1329 January 2010, Geneva, SG 1319 – 30 April 2010, Geneva, SG 1316 September 2010, Geneva, SG 1317 – 28 January 2011, Geneva, SG 1310 – 21 October 2011, Geneva, SG 134 – 15 June 2012, Geneva, SG 13
17Leo Lehman, Asok Chatterjee WP 1/13 Co-Chairmen Orientation for New Attendees to SG 13 (Geneva, Switzerland, January 2011)Working Party 1Coordination, Planning, Global Outreach of NGN Including MobileLeo Lehman, Asok ChatterjeeWP 1/13 Co-Chairmen17
18Co-Chairmen: Leo Lehman, Asok Chatterjee Working Party 1 of Study Group 13 Coordination, Planning, Global Outreach (WP1/13)Co-Chairmen: Leo Lehman, Asok ChatterjeeVice chairmen: Simon Bugaba, Davoud GordehQTitleRapporteurAssociate Rapporteur25Coordination, PlanningYoshinori GotoXin Changand Terminology10Identification of Evolving IMT-2000 Systems and BeyondNebojsa Dikic15Applying IMS and IMT in Developing Country Mobile Telecom NetworksSimon Bugaba
20Role of Q25/13Complex systems (such as NGN, IPTV) need robust program managementQ25 provides program management tool, and maintains ‘Road Map’ documentsIndustry needs common language and unique terms for each concept, architectural element, protocol definition, etc. in order to guard against misunderstanding and confusionQ25 collects, revises and publishes all relevant terms and definitions (related to NGN and future networks) in a dedicated ITU-T Recommendation
21Q.10 (Identification of Evolving IMT-2000 Systems and Beyond)
22Role of Q10/13IMT is perhaps the most recognized initiative spanning all three Sectors of ITUIMT 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 communityQ10/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
23Q.15 (Applying IMS and IMT in Developing Country Mobile Telecom Networks)
24Role of Q15/13There is a need to study requirements of telecom networks in developing countries with the increasing shift towards mobility and convergenceThe work needs to be done in close cooperation between all three Sectors of ITU and relevant external organizationsQ15/13 develops scenarios and requirements, in terms of services and deployments, for applying IMT and IMS to mobile networks in developing countries
25Introduction to new comers (Geneva, Switzerland, 17-28 January 2011) Working part 2Service requirements, scenarios and evolution aspectsDuo LIUWP 2/13 ChairladyCATR, China25
26WP2 in SG 13 Classifications of Questions Requirements Architectures FutureOverallRequirementsWP2Q 3, 12, 24ArchitecturesQ 5, 9, 22QoS and SecurityQ 4, 16, 17Q 10, 15, 25 &ITU-D, Mobile (3GPP)Q 7, 19, 20, 21
27Questions and Management Team of WP2 Question titleRapporteurAssociate Rapporteur3/13Requirements and implementation scenarios for emerging services and capabilities in an evolving NGNMr. Marco CARUGIMr. Tong WU12/13Evolution towards integrated multi-service networks and interworkingMr. Gyu Myoung LEE24/13Service scenarios, deployment models and migration issuesMr. Mingdong LIMr. Heechang CHUNGMr. Jiashun TUMr. Hideaki YAMADA
28Q3Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN
29Role of Q.3/13MotivationKey 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.
30Role of Q.3/13TasksDevelopment 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.2233Maintenance 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.30
31Recommendations in Q3/13 Y.1901 Requirements for the support of IPTV servicesY.2201Requirements and capabilities for ITU-T NGNY.2201 Rev.2Y.2215Requirements and framework for the support of VPN services in NGN including mobile environmentY.2216NGN capability requirements to support multimedia communication centre (MCC) serviceY.2221Requirements for support of Ubiquitous Sensor Network (USN) applications and services in the NGN environmentY.2233 Rev.1Requirements and framework allowing accounting and charging capabilities in NGNY.2236Framework for NGN support of multicast-based servicesY.2807MPLS-based mobility capabilities for NGN services
32Y.IPTV-Serv-Provision Documents under study in Q3/13Y.iptv-netcontrol-fwIPTV network control frameworkY.IPTV-Serv-ProvisionFramework for IPTV service provisioning using IPTV identifiers: concepts, use cases and requirementsY.miptv-reqFunctional requirements of Mobile IPTVY.NGN-SIDE-ReqRequirements for NGN service integration and delivery environment
33Q12Evolution towards integrated multi-service networks and interworking
34Role of Q.12/13MotivationThe 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.
35Role of Q.12/13TasksCreation of, maintenance and enhancement to the Recommendations in Y.1400 seriesMaintenance of Recommendations Y.2261, Y.2262 and Y.2271Maintenance and enhancement to the Recommendations in I.500 seriesMaintenance 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 and X.272 and the development of new Recommendations as deemed necessaryCompletion of draft Recommendations already under discussion in Questions 12/13Development of new Recommendations related to home network and their interworking aspects with the operator administered networksDevelopment of new Recommendations related to interworking to support IPTV services35
36Documents in Q12/13 Recommendations Documents under study Y.1911 IPTV services and nomadism: scenarios and functional architecture for unicast deliveryY.2281Framework of networked vehicle using NGNY.2291Framework for home network using NGN architectureDocuments under studyY.ipevInterworking between NGN and legacy IP-based networksY.IPTVintwVoDIPTV interworking for VoD servicesY.NGN-WebFunctional requirements and architecture of Web service component in NGNY.UbiNet-hnFramework of home network using ubiquitous networkingY.WoTFramework of Web of Things using NGN
37Q24Service scenarios, deployment models and migration issues
38Role of Q.24/13MotivationAs 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.
39Role of Q.24/13TasksDevelop 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.39
40Converged web-browsing service scenarios in NGN Recommendations in Q24/13Y.2214Service requirements and functional models for Customized Multimedia Ring servicesY.2235Converged web-browsing service scenarios in NGNY.2237Functional model, service scenarios and use cases for QoS enabled mobile VoIP service
41Supplement 13 to Y.2000-series Supplement 14 to Y.2000-series Supplements in Q24/13Supplement 13 to Y.2000-series(Y.NGN-ncescen)Scenarios for evolution of NGN to enhanced network capabilitySupplement 14 to Y.2000-series(Y.sof)Service scenarios over FMC
42Y.miptv-scen Supplement H.andbook on IMT-2000 (2nd Edition) Documents under study in Q24/13Y.gmsGHG monitoring service scenario on NGNY.hapasHeterogeneous application profiles adaptation service scenario over NGNY.iptvbsIPTV service brokering service scenariosY.irasIT Risk analysis service over NGNY.miptv-scen SupplementService scenarios and use cases of mobile IPTVY.passProfile based application adaptation service over NGNH.andbook on IMT-2000 (2nd Edition)The Handbook of evolving IMT-2000 SystemsY.son-ngnFunctional model of service overlay network using NGN
43Working part 3 Olivier LE GRAND WP 3/13 Chairman Introduction to new comers (Geneva, Switzerland, January 2011)Working part 3Frameworks and functional architecturesOlivier LE GRANDWP 3/13 ChairmanFrance Telecom Orange, France43
44WP3 in SG 13 Classifications of Questions Requirements Q 3, 12, 24 FutureOverallRequirementsQ 3, 12, 24ArchitecturesWP3Q 5, 9, 22QoS and SecurityQ 4, 16, 17Q 10, 15, 25 &ITU-D, Mobile (3GPP)Q 7, 19, 20, 21
45Questions and Management Team of WP3 Question titleRapporteurAssociate Rapporteur5/13Principles 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/13MM mechanisms supporting multi-connections for multiple access technologiesMr. Yachen WANG (China Mobile, China)Mr. Oscar LOPEZ TORRES (Inter Digital, United States)22/13Mobility management and fixed mobile convergenceMr. Woo-jin CHOI (KT, Korea)Ning ZONG (Huawei, China)
46Q5Principles and functional architecture for NGN (including ubiquitous networking)
47Role of Q.5/13MotivationTo establish a set of common principles and architectures for the convergence among services and networksSubstantial 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.
48Role of Q.5/13TasksGeneral 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)48
49Recommendations in Q5/13 Y.2001 General overview of NGN Y.2002 Overview of ubiquitous networking and of its support in NGNY.2011General principles and general reference model for NGNY.2012Functional requirements and architecture of NGNY.2014Network attachment control functions in NGNY.2015General requirements for ID/locator separation in NGNY.2016Functional requirements and architecture of the NGN for applications and services using tag-based identificationY.2017Multicast functions in NGNY.2018Mobility management and control framework and architecture within the NGN transport stratumY.2019Content delivery functional architecture in NGNY.2021IMS for Next Generation NetworksY.2031PSTN/ISDN emulation architectureY.2205NGN - Emergency telecommunications - Technical considerationsY.1910IPTV functional architecture
52Documents under study in Q5/13 Supplement Y.iptv-ipmcastGuidelines on deployment of IP multicast for IPTV service deliveryY.2205 rev1NGN - Emergency telecommunications - Technical considerationsY.FAid/locFunctional architecture of Id-Loc-split in NGNY.IPTV-IDFService delivery information platform for IPTVY.iptv-netcontrol-faFunctional architecture aspects of IPTV network controlY.MCC-archFunctional requirements and architecture for the NGN for Multimedia Communication Centre serviceY.2014 rev2Network attachment control functions in Next Generation NetworksY.OSE-archOpen Service Environment Functional Architecture for NGNY.NGN-SIDE-archNGN SIDE functional architectureY.USN-archUbiquitous Sensor Network (USN) functional architecture
53Q9MM mechanisms supporting multi-connections for multiple access technologies53
54Role of Q.9/13MotivationDifferent 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 experienceUsers 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
55Role of Q.9/13TasksExplore the scenarios and the policies for multiple connection harmonization in mobile networks utilizing fixed and mobile accessesIdentify 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.55
56Supplement 9 – Y.2000 series (Y.MC-SCEN) Documents in Q.9/13Documents approvedSupplement 9 – Y.2000 series (Y.MC-SCEN)Supplement on multi-connection scenariosDocuments under studyY.MC-REQRequirements of multi-connectionY.MC-ARCHArchitecture of Multi-connectionY.MC-IDIdentification and configuration of resources for Multi- ConnectionY.MC-StreamingStreaming service based on MC architecture
57Mobility management and fixed mobile convergence Q22Mobility management and fixed mobile convergence57
58Role of Q.22/13MotivationTowards 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.
59Role of Q.22/13TasksDevelop 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.59
60Recommendations in Q22/13 Q.1706 / Y.2801 Mobility management requirements for NGNQ.1707 / Y.2804Generic framework of mobility management for NGNQ.1708 / Y.2805Framework of Location Management for NGNQ.1709 / Y.2806Framework of Handover Control for NGNQ.1762 / Y.2802Fixed-mobile convergence general requirementsQ.1763 / Y.2803FMC service using legacy PSTN or ISDN as the fixed access network for mobile network usersY.2808FMC with a common IMS session control domain
61Documents under study in Q22/13 Y.MM-VPNMobile VPN Framework for NGNY.MM-WAUMobility management for interworking between WiMax and UMTSY.MM-WAWMobility management for interworking between WiMAX and WLANY.MMCMobility Management Framework for Multicast Communications in NGNY.MMSMobility management control scenarios for NGNY.MobileP2PMobility supporting architecture for mobile P2P service in heterogeneous wireless networksY.SMFFramework of Mobility Management in Service Stratum for NGN
62Introduction to WP 4/13 on QoS and Security Newcomer Orientation ITU-T SG 13 Meeting, Geneva, January 2011Introduction to WP 4/13 on QoS and SecurityHui-Lan Lu, Ph.D. (Alcatel-Lucent, USA)Vice Chairman of SG 13, Chairman of WP 4/13
63Outline Basic driver for QoS and security Structure of WP 4/13 Work program of underlying QuestionQ.4/13 on QoSQ.16/13 on security and Identity Management (IdM)Q.17/13 on Deep Packet Inspection (DPI)Summary
64Motivation: Basal packet transport lacks inbuilt support for hard security and QoS NGN Core802.xxAccess3G/LTECableDSLApplications have diverse bandwidth and performance needsUser devices have evolving and varied capabilitiesDifferent access technologies are in useMultiple providers and walled gardens are involved end- to-endNetworks and communications are vulnerable to attacks
65Security may mean… Limitation of data disclosure Privacy Anonymous communicationsPrevention of changing dataLaw enforcementdestruction of pirated contenttracking criminalsmonitoring enemy’s communications
66QoS 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 delayCarrier-grade network reliabilityRobust communication securityQuality of experienceCollective effect of service performance which determines the degree of satisfaction of a user of the service (as defined in E.800)
67Working Party 4/13 QoS Security 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 NGNRapporteur: Taesang Choi (ETRI);Associate Rapporteurs: Dong Sun (Alcatel-Lucent), Daoyan Yang (Huawei)Q.16/13 - Security and identity managementRapporteur: 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 environmentRapporteur - Meng Ji (Wuhan Fiberhome Networks)
68Question 4/13 Work Program Y.2172Y.2171Y.2173restorationpriorityperformancemanagementadmissionpriorityFlow-awaretransportresourceauthorizationY.2121,Y.2122Y.2112Y.2111 (RACF)Ethernet-basedIP access networkResource and admission controlOther related studiesY.QMFY.VNCY.2113+…EthernetProtocol specificationsY.2174, Y.2175Y.IPTV-TM ?MPLS core networkQ.330x.x (SG 11)
69Resource and Admission Control Functions (RACF) MediaManagement(Ref.: ITU-T Rec. Y.2012)3rd Party ApplicationsANIApplication/Service FunctionsServiceService UserProfilesUserProfilesService ControlManagement FunctionsService stratumFunctionsTransport UserProfilesNetworkNetworkResource & AdmissionControl FunctionsAttachmentAttachmentControl FunctionsControl FunctionsTransport Control FunctionsEnd-UserFunctionsOtherNetworksTransport FunctionsUNINNITransport stratumResource and Admission Control Functions (RACF)Provide application-driven, policy-based resource management to dynamically assure QoS and enforce network security measuresAddress unicast/multicast, fixed/mobile, and CPE/CPN requirements
70Resource and Admission Control Functions (RACF) (Ref.: ITU-T Rec. Y.2111 Rev. 1, 11/2008)intra-domaininter-domainService Control FunctionsOther NGNsService StratumRs (Diameter)Transport Stratum(Diameter)RuRp (COPS)RdPD-FENetwork Attachment Control FunctionsTRC-FERiRt (Diameter)RACFRhRnRc (COPS, SNMP)Rw (H.248, COPS, Diameter)TransportFunctions (multicast-aware )CPE/CPNTRE-FEPE-FEPolicy Decision Functional Entity (PD-FE)Authorize resource requests based on policyConfigure the transport to enforce policyTransport Resource Control Functional Entity (TRC-FE)Track resource use & network topologyMake resource-based admission decisionPolicy Enforcement Functional Entity (PE-FE)Enforce policy for NAPT, gating, rate limiting, packet marking, etc.service-facing,transport-independentservice-independent, transport-dependent, segment-specifictypically part of border transport elements (e.g., edge router and border gateway)
71Question 16/13 Work Program Y.2740 Security Requirements for Mobile Financial Transactions in NGNY.2741 Architecture for Secure Mobile Financial Transactions in NGNMobility Security Framework in NGNIdM and Security for Cloud ServicesY.2701 Security Requirements for NGN Release 1Y.2720 NGN IdM FrameworkY NGN AAAY.2702 NGN Authentication and Authorization RequirementsY.2721 NGN IdM Requirements and Use CasesNGN Certificate ManagementY.2704 NGN Security MechanismsY.2722 NGN IdM MechanismsDetermined draft RecommendationNote: Recommendations produced by Q.16/13 are approved through the TAP.
72NGN IdM Framework (ITU-T Rec. Y.2720, 1/2009) Users &SubscribersOrganizations, Business Enterprises,Government EnterprisesUserDevicesNetworkElements andObjectsNetwork andService ProvidersVirtualEntitiesIdentity Lifecycle ManagementCorrelation and Binding of Identity InformationAuthentication,Assurance, andAssertionof Identity InformationDiscoveryandExchangeIdM CapabilitiesIdentifiers(e.g., User ID,address, telephone number,URI, IP address)Credentials(e.g., digital certificates,tokens, and biometrics)Attributes(e.g., roles, claims,context, privileges,location)IdentityInformationFederated ServicesApplication Access Control (e.g., Multimedia and IPTV)Single Sign-on/SignoffRolebased Access to ResourcesProtection of PersonallyIdentifiable InformationSecurity Protection of Information and Network InfrastructureBusiness and Security ServicesIdentity Management
73Question 17/13 Work Program DPI Requirements(Y.dpireq)DPI Framework(Y.dpifr)SecurityChargingQoSApplicationScenariosQ.16/13Q.4/13DPIRules TableAnalysisEnforcementScan73
74SummaryWP 4/13 is addressing QoS and security issues in NGN and beyondA set of Recommendations has been developedY.2111 specifies RACF—the central enabler for NGN QoSY.2701 and Y.2702 set the basic security requirements for NGNY.2720 provides a holistic view of IdM in NGN and lays the foundation for further developmentOngoing studies includeIdM 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 managementDeep packet inspection-enabled QoS and security controlAn emerging focus is on resource management and security support for cloud servicesCooperation 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
75Introduction to new comers (Geneva in Switzerland, 19 January 2011) Working party 5 –Future networksNaotaka MoritaWP 5/13 ChairmanNTT, Japan75
76Working Party 5 of Study Group 13 Future Networks (WP5/13) Chairman: Naotaka Morita, NTT, JapanVice chairman: Maurice Ghazal, LebanonQTitleRapporteurAssociate Rapporteur7Impact of IPv6 on NGNHyoung Jun KIM ETRI/SRC, Korea (Rep. of)Sheng JIANG Huawei, China19Distributed servicesnetworking (DSN)Jin PENG China Mobile, ChinaShin-Gak KANGETRI, Korea (Rep. of)20Public data networksLintao JIANG CATR, ChinaKentaro OGAWA NTT, Japan &Jiguang CAO CATR, China21Future networksTakashi EGAWA NEC, Japan &Myung-Ki SHIN ETRI, Korea (Rep. of)Alojz HUDOBIVNIKIskratelSlovenia
78Role of Q.7/13 Q7/13 – Impact of IPv6 on NGN 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.
79Documents in Q.7/13 Recommendations On going works Y.2051 General overview of IPv6-based NGN (Y.ipv6-ngn)Y.2052Framework of multi-homing in IPv6-based NGN(Y.iptv6multi)Y.2053Functional 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 NGNY.ipv6splitFramework of ID/LOC separation in IPv6-based NGNY.ipv6-objectFramework of object mapping using IPv6 in NGNY.ipv6naFunctional requirement for network access in IPv6 based NGNY.ipv6migrationRoadmap for IPv6 Migration from NGN Operators’ PerspectivesY.ipv6-cvmhCognitive Vertical Multi-homing in IPv6-based NGNAnd more
80Current work in Q.7/13 (1/2) Future works on NGNv6 (1/2) Interworking based on NGNv6Within NGN: NGNv6 NGNv4 (RP 1b and 2b)With Non-NGN: NGNv6 IPv6 (RP 3a), NGNv6 IPv4 (3b)Specify Reference Points and Interworking FunctionsService Features, Operation and Provision issues
81Converged Broadband (Fixed+Mobile) Current work in Q.7/13 (2/2)Future works on NGNv6 (2/2)Advanced issues on NGNv6Framework of ID and location separation on NGNv6Framework of object mapping on NGNv6Vertical multi-homing on NGNv6, etc.Converged Broadband (Fixed+Mobile)Managed IPIPv6 basedIPv4 basedVoiceFMCIPTVMMUSNFull-CARNet-Rob
82Y.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 IPv6Mapping architecture and relationships between identifiersMechanisms for object mapping using IPv6Direct mapping vs. Indirect mappingDirect 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.
83Object identification through identity processing in IPv6-based NGN (Y
84Major 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.
85Documentation for Q.7/13 in 1/2011 TitleResultsTD138(WP5)Report for Q.7TD168(PLEN)Y.ipv6-objectConsentedTD129(WP5)Y.ipv6naTD128(WP5)Y.ipv6migrationTarget for 5/2011TD127(WP5)Y.ipv6splitTD120(WP5)Y.ipv6-vmh
87Leveraging peer-to-peer technology Scenarios of DSN -Leveraging peer-to-peer technologyVoIP scenario:Core Nodes constitute a P2P overlay to locate usersUser Node can be selected as relay node to help NAT traverse and improve QoSStreaming scenario:Core Nodes constitute a P2P overlay to locate media resourceCore Nodes and User Nodes constitute a tree or mesh to deliver media87
88Capabilities of DSN added value Transport connectivity Media resource managementQoSAccounting and chargingNumbering, naming and addressingIdentification, authentication and authorizationMobility managementDistributed technologies introducedTransport connectivityMedia resource managementRoutingQoSAccounting and chargingNumbering, naming and addressingIdentification, authentication and authorizationMobility managementContinuous service deliverySelf adaptive load balanceBandwidth convergenceSelf organizationDistributed resource storageIntelligent routingDynamic resource schedulingMulti connection application layer enablementNew mechanisms for numbering, naming and addressingadded value8888
89Documents in Q.19/13 Recommendations and Supplements On going works Y.Suppl. 10ITU-T Y Suppl.10: ITU-T Y.2000-series - Supplement on distributed service network (DSN) use casesY.2206Requirements for distributed service network (DSN)Y.dsn_sec_reqSecurity Requirements for DSNY.DsnarchArchitecture of DSNY.dsntocfDSN Traffic optimization control functionY.DsnrfDSN Relay FunctionY.dsnmmtelMultimedia Telephony over DSNY.dsncdfDSN Content Delivery Function89
90Major 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/2011Planned Rapporteur meetings in April, May (GSI), July, and October (SG13).
91Documentation for Q.19/13 in 1/2011 TitleNoteTD119r1(WP5)Report for Q.19TD118(WP5)Y.dsncdfTD117(WP5)Y.DsnmmtelTD116(WP5)Y.dsn_sec_reqTD115(WP5)Y.DsnrfTD114(WP5)Y.DsntocfTD113(WP5)Y.DsnarchTarget for 5/2011TD174(PLEN)LS to SG17 on X.p2pProduced with Q.16/13
93Question 20/13 – Public Data Networks (PDN) Role of Q.20/13Question 20/13 – Public Data Networks (PDN)NGN servicese.g., Voice telephony services (audio, fax, etc.)e.g., Data services (WWW, , etc.)e.g., Video services (TV, movie, etc.)CO-PS and CL-PS layer technologiesPDNNGN transportPDN 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.
94Current 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 modelData link layerNetwork layerAddressing & numberingRouting & switchingOAMInterworkingSecurityPerformance
95Current 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
96Documents in Q.20/13 Recommendations and Supplements On going works Y.2601Fundamental characteristics and requirements of future packet based networksY.2611High level architecture of future packet based networksY.2612Generic requirements and framework of FPBN addressing, routing and forwardingY.2613The general technical architecture for public packet telecommunication data network (PTDN)Y.Suppl. 11Y.2600-series - Supplement on scenarios for independent scalable control plane (iSCP) in future packet based networks (FPBN)Y.PTDN-reliabilityThe network reliability in PTDNY.PTDN-routingThe routing mechanism in PTDNY.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 nodesY.PTDN-T-IFInterface T between address translator and edge device for address mapping/ translation96
97Major results of Q.20/13 in 1/2011 Packet Date Networks Improved three ongoing drafts.Initiated two new drafts on M- and T- interfacesInterface M between management element and PTDN nodesInterface T between address translator and edge device for address mapping/ translationPrepared drafts Y.PTDN-reliability and Y.iSCP-req targeted for consent in 5/2011
98Documentation for Q.20/13 in 1/2011 TitleNoteTD126r1(WP5)Report for Q.20TD125(WP5)Y.PTDN-M-IFTD124(WP5)Y.PTDN-T-IFTD123(WP5)Y.iSCP-reqTarget for5/2011TD122(WP5)Y.PTDN-reliabilityTD121(WP5)Y.PTDN-routing
100Role 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 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.
101Focus group on Future Networks The group was established in 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 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, andIdentifiers and Identification processes.
102Vision of Future Networks (Y.3001) 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: roughlyServiceawarenessDataawarenessa) A new component network or an enhanced version of an existing one, orb) A heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network.Service DiversityFunctional FlexibilityData AccessVirtualization of ResourcesNetwork ManagementIdentificationMobilityReliability and SecurityEnvironmental awarenessSocial and economic awarenessEnergy ConsumptionService UniversalizationOptimizationEconomic Incentives4 objectives and 12 design goals
103Major results of Q.21/13 in 1/2011 Future Networks Successfully received FG-FN outputsDetermined draft Y.FNvison (Y.3001) under TAP processInitiated three drafts on network virtualization, energy saving, and IDs.Initiated seeking collaboration with JTC1/SC6 via common mailing list
104Documentation for Q.21/13 in 1/2011 TitleNoteTD131r1(WP5)Report for Q.21TD137(WP5)Y.FNterm,Moved to Q.25Target of the end of 2012TD135(WP5)Y.FNidentifierTarget for the end of 2012TD134(WP5)Draft on E-savingTarget for10/2011TD133(WP5)Draft on FNvirtTD182(PLEN)Y.3001DeterminedTD200(PLEN)6 LSs
106Current discussion in Focus Group on cloud computing The focal point in ITU-T is FG-cloud.T/focusgroups/cloud/Pages/default.aspxDefinitions 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.
108Future plans Q.19/13 will meet in April 2011, too. All Questions under WP5 will join the next NGN-GSI in May 2011 in Geneva.Q.19/13 will meet in April 2011, too.SunMonTueWedThusFriSat891011121314151617181920SG1321