InternationalTelecommunicationUnion
Chairman: Mr Chaesub Lee(ETRI, Korea, Rep. of)[email protected]
TSB: Ms Tatiana KurakovaSupported by Ms Gabrielle Regan
SG13 – Future networks including
mobile and NGN
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
1. Mission and Mandates of SG 131. 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
• 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
Lead study group for NGN and Satellite
SG13 covers ‘Future networks including mobile and NGN’
WTSA 2008
WTSA 2004
1. Mission and Mandates of SG 131. 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)
1. Mission and Mandates of SG 131. 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.
1. Mission and Mandates of SG 131. 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)
1. Mission and Mandates of New SG 131. 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.
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.
2. Questions and Structures2. 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 Convergence24/13 Service scenarios, deployment models and migration issues
25/13 Coordination, Planning, and Terminology
2. Questions and Structures2. Questions and StructuresStructures of Working Parties
WP Title QuestionsChair
Vice Chair
1Coordination, planning and global outreach of NGN including mobile
10, 15, 25Leo Lehman / Asok Chatterjee
Simon Bugaba / Davoud D. Gorgeh
2Service requirements, scenarios and evolution aspects
3, 12, 24Liu Duo
Konstantin Trofimov
3Frameworks and functional architectures
5, 9, 22Olivier Le Grand
Mohammed Al Ramsi
4 QoS and security 4, 16, 17Hui Lan Lu
Haitham Chedyak
5 Future networks 7, 19, 20, 21Naotaka MoritaMaurice Ghazal
3. Study OverviewHistory of studies in SG13
ISDN
IP-based Networks
GII
NGN
IPTV IMT 2000Future
Networks
I series Recommendations
Y.100 series Recommendations
Y.1000 series Recommendations
Y.2000series Rec
Y.1900series Rec
Q.1700 SeriesRec
Not yet specified
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.
FutureNet-works
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
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
Status of NGN Developments3. Study Overview
Service Stratum
Transport Stratum
Transport Functions
Transport Control Functions
Service Control and Content Delivery Functions
Applications
Application Support Functions and Service Support Functions
Service Control Functions
Content Delivery Functions
Network Attachment and Control Functions
Resource and
Admission control
Functions
Mobility Management and Control Functions
End-User Functions
Functions from Other
Networks
Functionsfrom other
Service Providers
ANI
NNI
SNI
UNI
Service User Profiles
Transport User Profiles
IdM Functions
Man
agem
ent F
unct
ions
Control
Media
Management
IdM
SIDE OSE
Y.2291
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
InternationalTelecommunicationUnion
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
Working Party 1 Coordination, Planning, Global Outreach of NGN Coordination, Planning, Global Outreach of NGN
Including MobileIncluding Mobile
Leo Lehman, Asok ChatterjeeWP 1/13 Co-Chairmen
Orientation for New Attendees to SG 13 (Geneva, Switzerland, 17-28 January 2011)
Working Party 1 of Study Group 13 Coordination, Planning, Global Outreach
(WP1/13)
Q Title Rapporteur Associate Rapporteur
25 Coordination, Planning
Yoshinori Goto Xin Chang
and Terminology
10Identification 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 ChatterjeeVice chairmen: Simon Bugaba, Davoud Gordeh
Q.25 (Coordination, Planning and Terminology)
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
Q.10 (Identification of Evolving IMT-2000 Systems and Beyond)
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
Q.15 (Applying IMS and IMT in Developing Country Mobile Telecom
Networks)
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
Working part 2Service requirements, scenarios and evolution aspects
Duo LIUWP 2/13 Chairlady
CATR, China
Introduction to new comers (Geneva, Switzerland, 17-28 January 2011)
Future
WP2 in SG 13WP2 in SG 13
RequirementsRequirements
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
Questions and Management Team of WP2
Question Question title Rapporteur AssociateRapporteur
3/13 Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN
Mr. Marco CARUGI Mr. 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
Role of Q.3/13
MotivationKey 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.
Role of Q.3/13
TasksDevelopment 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.
Recommendations in Q3/13
Y.1901 Requirements for the support of IPTV services
Y.2201 Requirements and capabilities for ITU-T NGN
Y.2201 Rev.2 Requirements and capabilities for ITU-T NGN
Y.2215Requirements and framework for the support of VPN services in NGN including
mobile environment
Y.2216NGN capability requirements to support multimedia communication centre
(MCC) service
Y.2221Requirements for support of Ubiquitous Sensor Network (USN) applications and
services in the NGN environment
Y.2233 Rev.1Requirements and framework allowing accounting and charging capabilities in
NGN
Y.2236 Framework for NGN support of multicast-based services
Y.2807 MPLS-based mobility capabilities for NGN services
Documents under study in Q3/13
Y.iptv-netcontrol-fw IPTV network control framework
Y.IPTV-Serv-ProvisionFramework for IPTV service provisioning using IPTV
identifiers: concepts, use cases and requirements
Y.miptv-req Functional requirements of Mobile IPTV
Y.NGN-SIDE-ReqRequirements for NGN service integration and delivery
environment
Role of Q.12/13
MotivationThe 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.
Role of Q.12/13
TasksCreation 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
Documents in Q12/13
Y.1911IPTV services and nomadism: scenarios and functional architecture
for unicast delivery
Y.2281 Framework of networked vehicle using NGN
Y.2291 Framework for home network using NGN architecture
Recommendations
Documents under study
Y.ipev Interworking between NGN and legacy IP-based networks
Y.IPTVintwVoD IPTV interworking for VoD services
Y.NGN-WebFunctional requirements and architecture of Web service component
in NGN
Y.UbiNet-hn Framework of home network using ubiquitous networking
Y.WoT Framework of Web of Things using NGN
Role of Q.24/13
MotivationAs 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.
Role of Q.24/13
TasksDevelop 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.
Recommendations in Q24/13
Y.2214Service requirements and functional models for
Customized Multimedia Ring services
Y.2235 Converged web-browsing service scenarios in NGN
Y.2237Functional model, service scenarios and use cases for
QoS enabled mobile VoIP service
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
Documents under study in Q24/13
Y.gms GHG monitoring service scenario on NGN
Y.hapasHeterogeneous application profiles adaptation service scenario
over NGN
Y.iptvbs IPTV service brokering service scenarios
Y.iras IT Risk analysis service over NGN
Y.miptv-scen Supplement
Service scenarios and use cases of mobile IPTV
Y.pass Profile based application adaptation service over NGN
H.andbook on IMT-2000
(2nd Edition)The Handbook of evolving IMT-2000 Systems
Y.son-ngn Functional model of service overlay network using NGN
Working part 3Frameworks and functional architectures
Olivier LE GRANDWP 3/13 Chairman
France Telecom Orange, France
Introduction to new comers (Geneva, Switzerland, 17-28 January 2011)
Future
WP3 in SG 13WP3 in SG 13
RequirementsRequirements
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
Questions and Management Team of WP3
Question Question title Rapporteur AssociateRapporteur
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)
Q5
Principles and functional architecture for NGN
(including ubiquitous networking)
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.
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)
Recommendations in Q5/13
Y.2001 General overview of NGN
Y.2002Overview of ubiquitous networking and of its support in
NGN Y.2011 General principles and general reference model for NGNY.2012 Functional requirements and architecture of NGNY.2014 Network attachment control functions in NGNY.2015 General requirements for ID/locator separation in NGN
Y.2016Functional requirements and architecture of the NGN for applications and services using tag-based identification
Y.2017 Multicast functions in NGN
Y.2018Mobility management and control framework and
architecture within the NGN transport stratum Y.2019 Content delivery functional architecture in NGN Y.2021 IMS for Next Generation Networks Y.2031 PSTN/ISDN emulation architecture
Y.2205NGN - Emergency telecommunications - Technical
considerations Y.1910 IPTV functional architecture
Y.2012: NGN overview architecture
Service Stratum
Transport Stratum
Transport Functions
Transport Control Functions
Service Control and Content Delivery Functions
Applications
Application Support Functions and Service Support Functions
Service Control Functions
Content Delivery Functions
Network Attachment and Control Functions
Resource and
Admission control
Functions
Mobility Management and Control Functions
End-User Functions
Functions from Other
Networks
Functionsfrom other
Service Providers
ANI
NNI
SNI
UNI
Service User Profiles
Transport User Profiles
IdM Functions
Man
agem
ent F
unct
ions
Control
Media
Management
IdM
Y.1910: IPTV functional architecture
Content Delivery Functions
ManagementFunctions
Application Functions
Service Control Functions
End-UserFunctions
ContentProvider
Functions
IPTV Terminal
Functions
HomeNetwork
Functions
Network Functions
Core TransportFunctions
Content Delivery & Storage Functions
Application Profile Functional Block
Content Delivery Client Functions
Access NetworkFunctions
Delivery NetworkGateway
Functional Block
Authentication &Configuration Protocol
Resource Control Functional Block
Authentication &IP Allocation
Functional Block
ContentPreparation Functions
TransportManagement
Functional Block
Content DeliveryManagement
Functional Block
Application Management
Functional Block
EdgeFunctions
Service User Profile
Functional Block
Control Client Functional Block
IPTV Service Control Functional
Block
Transaction ProtocolApplication
Client Functions
IPTV Application Functions
Content Distribution & Location Control
Functions
Content & Metadata
Delivery Protocols
Service ControlManagement
Functional Block
Control
SCP Functions
Metadata
SCP Client Functions
Content & MetadataSources
End-User Device Management
Functional Block
Content
Content & Control
Multicast Delivery Control Protocol
Transport Functions
Documents under study in Q5/13
Supplement Y.iptv-ipmcast
Guidelines on deployment of IP multicast for IPTV service delivery
Y.2205 rev1NGN - Emergency telecommunications - Technical
considerationsY.FAid/loc Functional architecture of Id-Loc-split in NGN
Y.IPTV-IDF Service delivery information platform for IPTV
Y.iptv-netcontrol-fa Functional architecture aspects of IPTV network control
Y.MCC-archFunctional requirements and architecture for the NGN for
Multimedia Communication Centre service
Y.2014 rev2Network attachment control functions in Next Generation
Networks Y.OSE-arch Open Service Environment Functional Architecture for NGN
Y.NGN-SIDE-arch NGN SIDE functional architecture
Y.USN-arch Ubiquitous Sensor Network (USN) functional architecture
Q9
MM mechanisms supporting multi-connections for multiple access
technologies
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
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.
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-IDIdentification and configuration of resources for Multi-
Connection Y.MC-
StreamingStreaming service based on MC architecture
Q22
Mobility management and fixed mobile convergence
Role of Q.22/13
MotivationTowards 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.
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.
Recommendations in Q22/13
Q.1706 / Y.2801 Mobility management requirements for NGN
Q.1707 / Y.2804 Generic framework of mobility management for NGN
Q.1708 / Y.2805 Framework of Location Management for NGN
Q.1709 / Y.2806 Framework of Handover Control for NGN
Q.1762 / Y.2802 Fixed-mobile convergence general requirements
Q.1763 / Y.2803FMC service using legacy PSTN or ISDN as the fixed
access network for mobile network users
Y.2808 FMC with a common IMS session control domain
Y.MM-VPN Mobile VPN Framework for NGN
Y.MM-WAUMobility management for interworking between
WiMax and UMTS
Y.MM-WAWMobility management for interworking between
WiMAX and WLAN
Y.MMCMobility Management Framework for Multicast
Communications in NGN
Y.MMS Mobility management control scenarios for NGN
Y.MobileP2PMobility supporting architecture for mobile P2P
service in heterogeneous wireless networks
Y.SMFFramework of Mobility Management in Service
Stratum for NGN
Documents under study in Q22/13
InternationalTelecommunicationUnion
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
Newcomer Orientation ITU-T SG 13 Meeting, Geneva, 17-28 January 2011
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
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 NGN Core
802.xxAccess
3G/LTE
Cable
DSL
Security may mean…
Limitation of data disclosure Privacy Anonymous communications Prevention of changing data Law enforcement
destruction of pirated contenttracking criminalsmonitoring enemy’s communications
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)
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
Question 4/13 Work Program
Y.2111 (RACF)
Y.2171
Y.2112
Y.2113
Y.2173Y.2172
Y.IPTV-TM ?
Y.2121,Y.2122
admission priority
restoration priority
performancemanagement
resource
authorization
Resource and admission control
Y.2174, Y.2175
Q.330x.x (SG 11)
Ethernet-basedIP access network
Ethernet
MPLS core network
Protocol specifications
Flow-awaretransport
Other related studies
Y.QMF
Y.VNC
+ …
Resource and Admission Control Functions (RACF)
OtherNetworks
Service ControlFunctions
Transport stratum
Service stratum
Man
ag
em
en
t Fu
ncti
on
s
Service UserProfiles
Service UserProfiles
Transport UserProfiles
ControlMedia
Management
Application/Service Functions
3rd Party Applications
ANI
End-UserFunctions
Transport Control Functions
Resource & Admission
Control Functions
Network Attachment
Control Functions
Network Attachment
Control Functions
Transport Functions
NNIUNI
(Ref.: ITU-T Rec. Y.2012)(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
Policy Decision Functional Entity (PD-FE)Authorize resource requests based on policyConfigure the transport to enforce policy
Transport Resource Control Functional Entity (TRC-FE)Track resource use & network topologyMake 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-FEPD-FE
TRC-FETRC-FERACF
Transport Stratum
Service Control FunctionsService Control Functions
Rt (Diameter)
RdRp (COPS)
Rc (COPS, SNMP)Rn
(Diameter)
RuRi
TRE-FETRE-FE PE-FEPE-FE
Network Attachment Control Functions
intra-domain
inter-domain
Oth
er NG
Ns
CPE/CPN
Rh
(Ref.: ITU-T Rec. Y.2111 Rev. 1, 11/2008)(Ref.: ITU-T Rec. Y.2111 Rev. 1, 11/2008)
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 Mechanism
s
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.
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 ManagementCorrelation and Binding of Identity Information
Authentication, Assurance, and Assertionof Identity Information Discoveryand Exchangeof 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 ServicesApplication Access Control (e.g., Multimedia and IPTV)
Single Sign-on/Sign-offRole-based Access to Resources
Protection of Personally-Identifiable InformationSecurity Protection of Information and Network Infrastructure
Business and Security Services
Iden
tity
Man
ag
em
en
t
Question 17/13 Work Program
DPI Requirements(Y.dpireq)
DPI Framework(Y.dpifr)
Security
Charging
QoS
ApplicationScenarios
Q.16/13
Q.4/13
Analysis Enforcement
Rules Table
DPI
Scan
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
Working party 5 –Future networks
Naotaka MoritaWP 5/13 Chairman
NTT, Japan
Introduction to new comers (Geneva in Switzerland, 19 January 2011)
Working Party 5 of Study Group 13 Future Networks (WP5/13)
Q Title Rapporteur Associate Rapporteur
7 Impact of IPv6 on NGN Hyoung Jun KIMETRI/SRC, Korea (Rep. of)
Sheng JIANGHuawei, China
19 Distributed services networking (DSN)
Jin PENGChina Mobile, China
Shin-Gak KANGETRI, Korea (Rep. of)
20 Public data networks Lintao JIANGCATR, China
Kentaro OGAWANTT, Japan &Jiguang CAOCATR, China
21 Future networks
Takashi EGAWANEC, Japan &Myung-Ki SHINETRI, Korea (Rep. of)
Alojz HUDOBIVNIKIskratel Slovenia
Chairman: Naotaka Morita, NTT, JapanVice chairman: Maurice Ghazal, Lebanon
Q.7 - Impact of IPv6 on NGN
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.
Core Network
Application
IPv6-based IP Connectivity
IPv6-based service/applicationIPv6-based service/application
IPv6EnabledEnd-UserFunctions
Fiber Access
xDSL Access
Mobile Access
Wireless Access(WiMAX)
Service Stratum
Transport Stratum
IPv6En-
abledProce-ssing
IPv6En-
abledProce-ssing
Q7/13 – Impact of IPv6 on NGN
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.2054 Framework to support signalling for IPv6-based NGN(Y.ipv6sig)
Y.ipv6-vmh Framework of Vertical Multi-homing in IPv6 based NGN
Y.ipv6split Framework of ID/LOC separation in IPv6-based NGN
Y.ipv6-object Framework of object mapping using IPv6 in NGN
Y.ipv6na Functional requirement for network access in IPv6 based NGN
Y.ipv6migration Roadmap for IPv6 Migration from NGN Operators’ Perspectives
Y.ipv6-cvmh Cognitive Vertical Multi-homing in IPv6-based NGN
And more
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
NGN1
IPv6-based
IPv6-based
IPv4-based
IPv4-based
NGN2
IPv6-based
IPv4-based
Non-NGN
IPv4-based
IPv6-based
IPv6-based
3a
1c
1b
1a
2a
2b
2c
IPv6-based
3c3b
4a
4b
IPv4-based
4c
Intra-NGN Communication
Interworking between Non-NGN
Inter-NGN Communication
Group 1
Group 4
Interworking with Non-NGN
Group
Group
2
3
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
Voice FMC IPTV MM USN Full-CAR Net-Rob
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.
Object identification through identity processing
in IPv6-based NGN (Y.2055)
Applications(Person, Objects)
Services(Service stratum)
Networks(Transport stratum)
User/Object Identities
Object IDs
IPv6 address
Name (Attributes)
Identification/Authorization
Mapping/Binding
Device ID, Content ID,
Telephone number,URL/URI, etc
Session/Protocol ID, IPv6 Address,
MAC Address, etc
ScopeLayered Architecture Identity Processing
Identity Management
Object Mapping
ID/LOC Separation
IPv6-based NGN
Major results of Q.7/13 in 1/2011IPv6
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.
Documentation for Q.7/13 in 1/2011
Document Title Results
TD138(WP5) Report for Q.7
TD168(PLEN) Y.ipv6-object Consented
TD129(WP5) Y.ipv6na
TD128(WP5) Y.ipv6migration Target for 5/2011
TD127(WP5) Y.ipv6split
TD120(WP5) Y.ipv6-vmh Target for 5/2011
Q.19 - Distributed services networking (DSN)
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
8888
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
Documents 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 cases
Y.2206 Requirements for distributed service network (DSN)
Y.dsn_sec_req Security Requirements for DSN
Y.Dsnarch Architecture of DSN
Y.dsntocf DSN Traffic optimization control function
Y.Dsnrf DSN Relay Function
Y.dsnmmtel Multimedia Telephony over DSN
Y.dsncdf DSN Content Delivery Function
Major results of Q.19/13 in 1/2011Distributed 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).
Documentation for Q.19/13in 1/2011
Document Title Note
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.Dsnarch Target for 5/2011
TD174(PLEN) LS to SG17 on X.p2p
Produced with Q.16/13
Q.20 - Public data networks
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
PDNNGN 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.
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
FPBN C
FPBN D
FPBN B
FPBN A
Core Transport Network
Access
Transport Network
User Network
Access
Transport Network
Core
Transport Network
Access Transport Network
User Net-work
I-NNI I-NNI
Reference Point in FPBN
a
b
c d
Service Stratum
Core Transport
Network
I-NNI E-NNI
f
c b a
a
Cloud
b
Other TN
d
User Net-work
Ma
na
ge
men
t fu
nc
tio
ns
e
Current work in Q.20/13 (2/2)
Works on iSCP (Independent Scalable Control Plan
e )
——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.
CE CE SCE SCE
FE FE SFE SFE
Data Plane
VNE
Control Plane
ME
Management Plane
CEiSCP
SCE
FE
SFE
FE
FE
SFE
Data-plane network
Control plane network
Documents in Q.20/13
Recommendations and Supplements
On going works
Y.2601Fundamental characteristics and requirements of future packet based networks
Y.2611 High level architecture of future packet based networks
Y.2612Generic requirements and framework of FPBN addressing, routing and forwarding
Y.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-reliability The network reliability in PTDN
Y.PTDN-routing The routing mechanism in PTDN
Y.iSCP-req Requirements of independent Scalable Control Plane (iSCP)
Y.iSCP_Arch Architecture of independent Scalable Control Plane (iSCP)
Y.PTDN-M-IF Interface M between management element and PTDN nodes
Y.PTDN-T-IFInterface T between address translator and edge device for address mapping/ translation
Major results of Q.20/13 in 1/2011Packet 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
Documentation for Q.20/13 in 1/2011
Document Title Note
TD126r1(WP5) Report for Q.20
TD125(WP5) Y.PTDN-M-IF
TD124(WP5) Y.PTDN-T-IF
TD123(WP5) Y.iSCP-req Target for
5/2011
TD122(WP5) Y.PTDN-reliability Target for
5/2011
TD121(WP5) Y.PTDN-routing
Q.21 - Future Networks
Role of Q.21/13
Question 21/13 – Future networksFuture 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.
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.
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: roughly2015-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 and12 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
Major results of Q.21/13 in 1/2011Future 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 [email protected]
Documentation for Q.21/13 in 1/2011
Document Title Note
TD131r1(WP5) Report for Q.21
TD137(WP5) Y.FNterm,
Moved to Q.25
Target of the end of 2012
TD135(WP5) Y.FNidentifier Target for the end of 2012
TD134(WP5) Draft on E-saving Target for
10/2011
TD133(WP5) Draft on FNvirt Target for
10/2011
TD182(PLEN) Y.3001 Determined
TD200(PLEN) 6 LSs
Information aboutCloud Computing
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, deployment 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 consumed on demand at any time, through any access network and using any connected devices using cloud computing technologies.
InternationalTelecommunicationUnion
Future plans
Future plans
All Questions under WP5 will join the next NGN-GSI in May 2011 in Geneva.
Q.19/13 will meet in April 2011, too.
Sun Mon Tue Wed Thus Fri Sat
8 9 10 11 12 13 14
15 16 17 18 19 20SG13
21