quality of service related recommendations

Table of contents

Mobile Related Recommendations.............................................................................. 9 NGN ................................................................................................................ 9 Numbering ................................................................................................................................................................................................................................12 Satellite communication................................................................................................................................................................................................................18 Recommendations for Multi-media....................................................................................................................................................................................................19 Related Multi-media Recommendations..............................................................................................................................................................................................25 Signalling related Recommendations .................................................................................................................................................................................................26 TMN related Recommendations........................................................................................................................................................................................................27 Security related Recommendations...................................................................................................................................................................................................28 Quality of Service related Recommendations .......................................................................................................................................................................................30

• Recommendation Q.1701 (03/99) - Framework for IMT-2000 networks This Recommendation sets out the "family" of systems concept which provides the basis for the development of IMT-2000 standards including the set of signaling requirements for IMT-2000. It also contains a description of the interfaces in the system which may need to be standardized by the ITU. It has been agreed that the development of IMT-2000 requirements will be performed in Capability Sets and this Recommendation sets out the contents of Capability Set 1 and the vision for subsequent Capability Sets.

• Recommendation Q.1702 (06/02) - Long-Term Vision of Network Aspects for Systems Beyond IMT-2000This Recommendation addresses the envisaged network environment, network design objectives, and architecture concepts of Systems Beyond IMT-2000.This Recommendation, together with a draft ITU-R Recommendation which covers the radio aspects, form the ITU long-term vision for Systems Beyond IMT-2000.

• Recommendation Q.1703 (05/04) – Service and Network Capabilities Framework of Network Aspects for Systems Beyond IMT-2000 This Recommendation specifies the service and network capability framework for Systems

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Q.1701





Beyond IMT-2000, from the network aspects, in order to attend the high level end-user needs delineated in the ITU long-term vision for Systems Beyond IMT 2000, as specified in ITU T Recommendations Q.1701 and Q.1702 and ITU-R Recommendation M.1645.

It is expected that various advanced services can be offered via the combination of radio aspect of service capabilities and network aspect of service capabilities, the ones described herein. This recommendation follows the vision described in ITU-R (Recommendation M.1645) and ITU-T (Recommendation Q.1702). To fulfill the vision and accomplish the objectives for Systems Beyond IMT-2000, this recommendation identifies the general capabilities and/or requirements framework. These capabilities and/or requirements framework can be studied in order to develop the detailed capabilities and/or requirements for Systems Beyond IMT-2000.

• Recommendation Q.1706 /Y.2801 (11/06) – Mobility Management Requirements for Next Generation NetworksThis Recommendation describes the requirements for mobility management (MM) for Next Generation Networks (NGN). For this purpose, this Recommendation describes the considerations for mobility management in the NGN, classifies the types of mobility management for NGN environment, and identifies a set of the MM requirements for NGN.

• Recommendation Q.1711 (03/99) - Network functional model for IMT-2000 This Recommendation identifies network and terminal functions that are specific for the support of IMT-2000 services, as specified in the Recommendation on the Framework for IMT-2000 Networks (ITU-T Recommendation Q.1701). These functions together with other, more conventional network functions are then grouped into functional entities in a generic functional model. In the functional model, the relationships among functional entities and groups are shown. The functional model is mapped onto a generic network reference model to illustrate possible groupings of functional entities into physical collections of entities. Based on the functional model, global roaming requirements and network interconnection scenarios are described. This Recommendation forms the basis for the development of information flows and the definition of functional entity actions and the development of signaling requirements for the various interfaces identified in ITU-T Recommendation Q.1701.

• Recommendation Q.1721 (06/00) - Information Flows for IMT-2000 Capability Set-1 This recommendation specifies Stage 2 information flow procedures for the support of end-to-end inter-family and inter-system IMT-2000 Capability Set 1 (CS-1) services and network capabilities. The areas covered are mobility management, call and bearer control, services control, and over-the-air authorization services. The description of information flows contains the list of information elements that are exchanged between the interacting functional entities.

• Recommendation Q.1731 (06/00) - Radio Technology Independent Requirements for IMT-2000 Layer 2 Radio Interface This Recommendation defines requirements for common services, functions and primitives for the radio technology independent parts of the Layer 2 of the IMT-2000 radio interface, to ensure maximum commonalty between IMT-2000 family members.

• Recommendation Q.1741.1 (04/02) – IMT-2000 References to Release 1999 of GSM evolved UMTS Core Network with UTRAN Access Network This Recommendation identifies the IMT-2000 Family Member, "GSM evolved UMTS Core Network with UTRAN Access Network". This release of the Family Member is known to the

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Q.1741.1






http://www.itu.int/rec/T-REC-Q.1706/en

http://www.itu.int/rec/T-REC-Q.1706/en

Standards Development Organizations (i.e. ARIB, ETSI, T1, TTA, TTC) as the "3GPP Release 1999".

• Recommendation Q.1741.2 (12/02) – IMT-2000 References to Release 4 of GSM evolved UMTS Core Network with UTRAN Access NetworkThis Recommendation identifies a release of the IMT-2000 Family Member, "GSM evolved UMTS Core Network with UTRAN Access Network". This release of the Family Member is known to the Standards Development Organisations (i.e. ARIB, CWTS, ETSI, T1, TTA, TTC) as the "3GPP Release 4". An earlier release, known as "3GPP Release 99", of this Family Member is specified in the Recommendation Q.1741.1, while other IMT-2000 Family Members are specified in other Recommendations in the Q.174x series.

This Recommendation combines and associates the relevant standards from a number of Standards Development Organisations for the core network for this IMT-2000 Family Member into a global Recommendation.



• Recommendation Q.1741.3 (09/03) - IMT-2000 References to Release 5 of GSM evolved UMTS Core Network This Recommendation identifies a release of the IMT-2000 Family Member, "GSM evolved UMTS Core Network". This release of the Family Member is known to the Standards Development Organisations (i.e. ARIB, CWTS, ETSI, T1, TTA, TTC) as the "3GPP Release 5". Earlier releases, known as "3GPP Release 99" and "3GPP Release-4", of this Family Member are specified in the Recommendation Q.1741.1 and Q.1741.2, respectively, while other IMT-2000 Family Members are specified in other Recommendations in the Q.174x series.

This Recommendation combines and associates the relevant standards from a number of Standards Development Organizations for the core network for this IMT-2000 Family Member into a global Recommendation.

• Recommendation Q.1741.4 (10/05) - IMT-2000 References to Release 6 of GSM evolved UMTS Core NetworkThis Recommendation identifies a release of the IMT-2000 Family Member, “GSM evolved UMTS Core Network”. This release of the Family Member is known to the Standards Development Organisations (i.e. ARIB, CCSA, ETSI, ATIS, TTA, TTC) as the “3GPP Release 6”. Earlier releases, known as “3GPP Release 99”, “3GPP Release 4”, and “3GPP Release 5”, of this Family Member are specified in the Recommendation Q.1741.1, Q.1741.2, and Q.1741.3, respectively, while other IMT-2000 Family Members are specified in other Recommendations in the Q.174x series.

This Recommendation combines and associates the relevant standards from a number of Standards Development Organizations for the core network for this IMT-2000 Family Member into a global Recommendation.

• Recommendation Q.1742.1 (12/02) – IMT-2000 References to ANSI-41 evolved Core Network with cdma2000 Access Network This Recommendation associates the published core network standards from standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 17 July 2001 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network."

3GPP2 specifications that were approved as of July 2002 will be associated with published core network standards in future ITU-T Recommendation Q1742.2. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R M.1457. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x series.

This Recommendation combines and associates the relevant core network standards from a number of standards development organizations for this IMT-2000 Family Member into a global Recommendation.

• Recommendation Q.1742.2 (07/03) - IMT-2000 references (approved as of 11 July 2002) to ANSI-41 evolved core network with cdma2000 access network This Recommendation associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 11 July 2002 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network."

3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in





http://www.itu.int/rec/T-REC-Q.1741.4/en




ITU-T Q.1742.1. 3GPP2 specifications that are approved as of July 2003 will be associated with published core network standards in future ITU-T Recommendation Q1742.3. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R M.1457. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x series.

This Recommendation combines and associates the regional standards for the core network of this IMT-2000 Family Member into a global recommendation.

• Recommendation Q.1742.3 (01/04) - IMT-2000 References (approved as of 30 June 2003) to ANSI-41 evolved Core Network with cmda2000 Access Network This Recommendation associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 30 June 2003 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network."

3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.2. 3GPP2 specifications that are approved as of July 2004 will be associated with published core network standards in future ITU-T Recommendation Q1742.4. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R M.1457. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x series.


• Recommendation Q.1742.4 (04/05) - IMT-2000 References (approved as of 30 June 2004) to ANSI-41 evolved Core Network with cmda2000 Access NetworkThis Recommendation associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 30 June 2004 for the IMT-2000 Family Member "ANSI-41 evolved Core Network with cdma2000 Access Network."

3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.2. 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.3. 3GPP2 specifications that are approved as of 30 June 2005 will be associated with published core network standards in future ITU-T Recommendation Q1742.5.

The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R M.1457. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x series.






• Recommendation Q.1742.5 ( 09/06) – IMT 2000 references (approved as of 31 December 2005) to ANSI-41 evolved core network with cdma2000 access networkThis Recommendation associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 31 December 2005 for the IMT-2000 Family Member “ANSI-41 evolved Core Network with cdma2000 Access Network.”

3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.2. 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.3. 3GPP2 specifications that were approved as of 30 June 2004 were associated with the published core network standards from the regional standards development organizations in ITU-T Q.1742.4. 3GPP2 specifications that are approved as of 31 December 2006 will be associated with published core network standards in future ITU-T Recommendation Q1742.6. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R M.1457. The associations for other IMT-2000 Family Members are identified in the ITU-T Q.174x series.


• Recommendation Q.1751 (06/00) - Internetwork Signaling Requirements for IMT-2000 Capability Set 1 This recommendation document contains signaling requirements for the Network to Network Interface (NNI) protocol. The requirements are to support the capabilities that are recommended in the IMT-2000 Framework document and specified as Capability Set 1 (CS-1). This document covers requirements for five communication groups of the NNI: Call and Bearer Control; Mobility Management; Virtual Home Environment (VHE) and Intelligent Network (IN) Services Control; Packet Data Services and Internet Access Control; and Inter-network Security. The requirements specified in this document are non-information flow related, and they should be viewed as complementary to the information flows of Recommendation Q.1721. They include general NNI protocol requirements, NNI functional models, NNI reference points, state models for selective functional entities, and the choice of various protocol suites.

• Recommendation Q.1761 (01/04)- Principles and Requirements for Convergence of Fixed and Existing IMT-2000 Systems This Recommendation describes requirements for the use of fixed networks in the role of fixed access networks for IMT-2000 networks. This convergence of fixed networks and IMT-2000 networks enables mobile users to roam outside the serving area of their IMT-2000 network and still have access to the same set of services outside their IMT-2000 network boundaries as they do within those boundaries. This recommendation also describes the framework for fixed mobile convergence and the capability requirements for enhanced fixed terminals that may be utilized to enhance the roaming IMT-2000 user’s experience. This Recommendation also details the mobility management functional requirements in fixed networks in support of roaming IMT-2000 subscribers.

The evolution of individual core network technologies towards common Internet Protocol (IP) based solutions provides long term opportunities for the convergence of diverse







network technologies. This convergence provides, in turn, opportunities for extending the reach and scope of services that a user of one of these networks may obtain beyond what could be supported in a pre-converged environment.

As these long term convergence opportunities emerge and stabilize, there are opportunities in the near to medium term that may be enabled by providing capabilities to enable IMT-2000 roamers to access their basic and enhanced services, possibly excluding terminal mobility, in environments where IMT-2000 is not yet deployed.

This Recommendation describes the requirements for supporting a mobile IMT-2000 user roaming to a fixed network such that the IMT-2000 user may obtain basic services plus access to the user’s services per the subscription profile. A number of service level scenarios are possible. This situation provides personal mobility among fixed network users and may exclude terminal mobility.

• Supplement 30 (12/00) to Series Q Recommendations - Framework for IMT-2000 Networks - Roadmap to IMT-2000 Recommendations, Standards and Technical Specifications This Supplement is an "information" document and is intended as a roadmap and a source of references for documents related to IMT-2000 specifications from ITU-T as well as from sources outside the ITU (e.g.,3GPPs and SDOs.) The list of documents contained in this Supplement should therefore be treated as "bibliographic" references. The scope includes any relevant standards that are targeted toward the specification of IMT-2000 systems.

• Supplement 47 to ITU-T Q-series Recommendations (11/03) - Emergency Services for IMT-2000 Networks - Requirements for Harmonization and Convergence This Supplement is an "information" document and is intended to outline the requirements and provisions for Emergency Services for IMT-2000 systems. This is a compilation from sources outside the ITU (e.g., administrations, Standards Development Organizations, and the Third Generation Partnership Projects (3GPP and 3GPP2)). The scope includes any relevant discussion concerning the provisioning of Emergency Services specifically addressing the IMT-2000 systems during Harmonization and Convergence periods.

ITU-T Recommendation Q.1701 provides the framework for IMT-2000 networks and defines the IMT-2000 Family of Systems concept. This Recommendation identified the following Emergency call capabilities to be supported on IMT-2000 systems:

Identification of emergency call Emergency call handling Emergency caller location

This Supplement to the Q-series of Recommendations identifies and discusses the requirements and provisioning of Emergency Services in IMT-2000 systems. For the purposes of this Supplement, Emergency Services includes supporting national emergency calls and the International Emergency Preference Scheme (IEPS), as found in ITU-T Recommendation E.106.

• Supplement 52 to ITU-T Q-series Recommendations (12/04) - Technical report on NNI mobility management requirements for systems beyond IMT-2000 This Supplement identifies the mobility management requirements for Systems Beyond IMT-2000, based on ITU-T Recommendations Q.1702 [7] and Q.1703 [8] and ITU-R Recommendation M.1645 [23]. A number of mobility management protocols are reviewed and analysed according to the identified requirements.

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Q.Sup52







• Recommendation Y.1281 (09/03) - Mobile IP services over MPLS This Recommendation defines service definition and requirements to support mobile IP services through the MPLS network. It also describes the service architecture and application procedures to provide the mobility service over the MPLS network.

The scope of this Recommendation covers: Service requirements and definitions for mobile IPv4 and mobile IPv6 services over

MPLS; Service architecture to support mobile IP service over MPLS; LSP tunnelling scenarios to support the mobile IP services over MPLS; Application procedures to support the mobile IP services over MPLS.

• Recommendation Q.FNAB on Functional Network Architecture for Systems Beyond IMT-2000The scope of this Recommendation is to provide a long-term high-level network architecture for beyond IMT 2000 systems, including definition of functional entities (FEs), allocation of functional capabilities to FEs, and interfaces model among FEs for systems around the year 2010, as specified by ITU-R Recommendation M.1645 and ITU-T Recommendation Q.1702.

The purpose of this Recommendation is to identify high-level network functions which are specific to Beyond IMT-2000 Systems and to define a Functional Model which will form the basis for the development of information flows and the definition of functional entity actions.

Expected completion – 04/2007

• Recommendation Q.FIFB on Long-term high-level network functional information flows for beyond IMT-2000 systemsThis Recommendation will define how the information should flow among the functional entities in a system beyond IMT-2000, according to the functional network architecture model described in Q.FNAB.

Expected completion – to be decided

• Recommendation Q.MMF- Generic Framework of Mobility Management for NGNThis Recommendation is purposed to describe a generic framework of Mobility Management (MM) for Next Generation Networks (NGN). This Recommendation describes the followings: o Design considerations;o Conceptual framework of MM;

o Mobility Managers; ando Generic MM procedures.

This Recommendation describes a generic framework of MM for NGN. Based on this Recommendation, the specific and more detailed frameworks and functional information flows for location management and handover management will be developed in the draft Recommendations, LMF (Location Management Framework) and HMF (Handover Management Framework), respectively.

Expected completion – 3Q/2007

• Recommendation Q.LMF on Framework of Location Management for NGNThis Recommendation is purposed to provide the framework of location management for

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Y.1281

NGN. To design the framework of location management for NGN, this Recommendation describes the followings: o Design considerations and basic functions for location management;o Reference functional architecture for location management;o Functional information flows of location management; ando Application of candidate protocols for location management.

This work on Location Management Framework has been made based on the ITU-T Recommendations: Mobility Management Requirements (Q.1706/Y.2801) and Mobility Management Framework (MMF).


• Recommendation Q.HMF on Framework of Handover Management for Next Generation NetworksThis Recommendation is purposed to provide the framework of handover management for Next Generation Networks (NGN). This Recommendation describes the followings: o Design considerations for handover management;

o Classification of handover management schemes; o Reference functional architectures; o Functional information flows; ando Candidate schemes for handover management.

This Handover Management Framework (HMF) has so far been made based on the other companion ITU-T Recommendations Mobility Management Requirements (Q.1706/Y.2801), Mobility Management Framework (MMF), and Location Management Framework (LMF).


• Recommendation Q.1741.5 on architecture and specifications of Release 7 of IMT-2000 Family Member "GSM evolved UMTS Core Network "

Expected completion – 2008

• Recommendation Q.1742.6 on architecture and specifications of next Release of IMT-2000 Family Member "ANSI-41 evolved Core Network with cmda2000 Access Network"


• Handbook "Deployment of IMT-2000 Systems" is a Handbook to assist countries in the deployment of existing and evolving IMT-2000 systems

Expected completion of 2nd Edition – 1Q/2008

• Handbook "Deployment of IMT-2000 Systems" Edition 2003

• Recommendation Q.FMC Req - FMC General RequirementsThis Recommendation is intended to help and to be used as general requirement document to lead of the development of recommendations, standards and implementation guidelines for the realization of FMC. This is to ensure that all elements required for interoperability and network capabilities to support applications globally across FMC are adequately addressed by

http://www.itu.int/opb/publications.aspx?lang=en&parent=T-HDB-MOB.01-2003

ITU-T standardization activities.

The scope of this Recommendation is to give FMC principles, high level service requirements and capabilities. More specifically, this Recommendation identifies the fundamental characteristics, requirements and capabilities that an FMC should be able to support. And the term “IMS” without any prefix in this recommendation refers to the IMS concept in Y.2021.


• Recommendation FMC IMS - Fixed Mobile Convergence with a common IMS session control domainThis Recommendation describes principles and requirements for convergence of fixed and mobile networks (“fixed-mobile convergence, (FMC)”). This convergence of fixed and mobile networks enables mobile users to roam outside the serving area of their mobile networks and still have access to the same set of services outside their network boundaries as they do within those boundaries, subject to the constraints of physical access and commercial agreements. This Recommendation also describes the general framework for fixed-mobile convergence and the mobility management functional requirements that must be satisfied in fixed networks to achieve this convergence.

This Recommendation is focused on future IMS-based Networks, although some legacy fixed network requirements are also addressed.


• Recommendation FMC PAU - FMC service scenario by using PSTN as the fixed Access network for UMTS network

This Recommendation describes the service scenario of the fixed-mobile service, proposes the service feature, network architecture, capability requirement based on the legacy PSTN network and GSM/UMTS network, and discusses the signalling requirement on PSTN and GSM/UMTS mobile network.


Mobile related Recommendations

NGN

• Recommendation Y.2001 (12/04) - General overview of NGN The concept of an NGN (Next Generation Network) has been introduced to take into consideration the new realities in the telecommunications industry, characterized by factors such as: competition among operators due to ongoing deregulation of markets, explosion of digital traffic, e.g., increasing use of "the Internet", increasing demand for new multimedia services, increasing demand for a general mobility, convergence of networks and services, etc.

The target of NGN is to ensure that all elements required for interoperability and network capabilities support applications globally across the NGN while maintaining the concept of separation between transport, services and applications.

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Y.2001

The scope of this Recommendation is to give a general overview of what constitutes and defines a Next Generation Network (NGN). More specifically, this Recommendation identifies the fundamental characteristics and capabilities that an NGN should be able to support. This Recommendation is intended to be used as background information to assist the development of Recommendations, standards and of implementation guidelines for the realization of Next Generation Networks.

• Recommendation Y.2011 (10/04) - General principles and general reference model for Next Generation NetworksThis Recommendation specifies general principles and a general reference model for Next Generation Networks.

• Supplement 1 to the Y .2000-series Recommendations (07/06) - NGN Release 1 Scope This Supplement to ITU-T Y.2000-series Recommendations on the scope of release 1 of the Next Generation Networks (NGN) provides the release 1 environment, release 1 services, descriptions and use cases.

• Recommendation Y.2012 (09/06) - Functional Requirements and Architecture of the NGN of Release 1The objective of this Recommendation is to describe the functional requirements and architecture of the Next Generation Network (NGN) for release 1, as described in Recommendation Y.2201 (NGN release 1 requirements) and the Supplement 1 to Y.2000-series Recommendations (NGN release 1 scope). The functional architecture provided in this Recommendation allows a clear distinction between the definition and specification aspects of services provided by the NGN and the actual specification of the network technologies used to support those services. In line with Y.2011 principles, an implementation-independent approach is adopted.

• Recommendation Y.2021 (09/06) - IMS for Next Generation Networks The IP Multimedia Subsystem (IMS) as specified by the 3rd Generation Partnership Project (3GPP) and the 3rd Generation Partnership Project 2 (3GPP2) has been adopted to support session and other Session Initiation Protocol (SIP) based services This recommendation describes how the IMS can be used in the NGN context following the fundamental principles described in Y.2001 and Y.2011. This document identifies the IMS for use in NGN and describes the use of IMS in providing the IP Multimedia Service component of the NGN functional architecture and its relationships to other service components. It further identifies those IMS architecture documents that are relevant in the context of NGN. For more detail refer to ITU-T Recommendation Y.2012, NGN functional architecture.

• Recommendation Y.ngn-rtconv – IMS based Real-time Conversational Multimedia Services over NGN The scope of this Recommendation document is to define the service requirements, service features, service architecture, and implementation scenarios of IMS based real-time conversational multimedia services.


• Recommendation Y.mpls-mob - MPLS-based Mobility and QoS capabilities for NGN services.The scope of this Recommendation covers:

• Service Requirements for MPLS-based mobility and QoS capabilities for NGN services

http://www.itu.int/rec/T-REC-Y.2012/en

http://www.itu.int/rec/T-REC-Y.2012/en

http://www.itu.int/rec/T-REC-Y.2000SerSup1/en

http://web/rec/T-REC-Y.2011/en

http://web/rec/T-REC-Y.2011/en

• Service functional architecture for MPLS-based mobility and QoS capabilities for NGN services

• Service scenarios for MPLS-based mobility and QoS capabilities for NGN services • Protocol procedures l for MPLS-based mobility and QoS capabilities for NGN services


• Recommendation Y.ngn-vpn - VPN Service Capabilities in NGN mobile environmentProvisioning of a multiplicity of VPN applications in NGN mobile environment will require dynamic management of application flows and service features. To support the related additional service capabilities for VPN services in NGN mobile environment, the following work items will be addressed in this draft recommendation:

● Service Requirements for VPN services in NGN mobile environment ● Functional Requirements for VPN services in NGN mobile environment ● Service functional architecture for VPN services in NGN mobile environment● VPN implementation scenarios in NGN mobile environment


• Recommendation Y.ngn-mcast - NGN Multicast service capabilities with MPLS-based QoS supportThe scope of this Recommendation covers:

o Requirements for NGN multicast services with MPLS-based QoS support o Reference model for NGN multicast service architecture

o Functional architecture for NGN multicast services with MPLS-based QoS support o Functional scenarios and procedures for NGN multicast services with MPLS-based QoS

support o Implementation scenarios for NGN multicast services with MPLS-based QoS support


• Recommendation Y.NGN-R1- NGN Release 1 descriptionITU-T has adopted a release-based approach for the production of NGN recommendations, with the scope of each release clearly defined and with clear deadlines for completion. The objective is to aid project management, and to ensure concentration of effort on a smaller set of deliverables to be achieved in a shorter timescale, thus achieving feasible deliverables in a timely manner. The present document gives a description of Release 1 of an anticipated series of releases within ITU-T in terms of the overall requirements and high level overview of the functional features to be addressed. In order to fulfil the general objectives and principles of an NGN identified in Recommendations Y.2001 and Y.2011, the present document focuses on key initial capabilities whilst ensuring the general and long term architectural direction of the NGN is maintained as flexible as possible to allow future enhancements and releases.


• Recommendation Y.2201 - NGN release 1 requirementsThis ITU-T Y-Series Recommendation provides high level requirements for services and

capabilities of Next Generation Network (NGN) Release 1.


• Recommendation Y.NGN-R2-Reqts - Requirements and capabilities for ITU-T NGN Release 2This ITU-T Y-Series Recommendation provides high level requirements for services and capabilities of Next Generation Network (NGN) Release 2.


Numbering

• Recommendation E.164 (02/05) - The international public telecommunication numbering planThis Recommendation provides the number structure and functionality for the four categories of numbers used for international public telecommunication: geographic areas, global services, Networks and Groups of Countries (GoC). For each of the categories, it details the components of the numbering structure and the digit analysis required to successfully route the calls. Annex A provides additional information on the structure and function of international public telecommunication numbers (hereafter referred to as "international E.164-numbers"). Annex B provides information on network identification, service parameters, calling/connected line identity, dialling procedures and addressing for geographic-based ISDN calls. Specific E.164-based applications, which differ in usage, are defined in separate Recommendations. In addition, this Recommendation describes a resource that enables the conduct of trials of potential new international public correspondence services. Specific E.164-based applications, which differ in usage, are defined in separate Recommendations, e.g., ITU-T Rec. E.168 – Application of E.164 numbering plan for UPT.

• Recommendation E.156 (05/06) - Guidelines for ITU-T action on reported misuse of E.164 number resourcesThis recommendation outlines the procedures that the TSB Director, should undertake when he has received reports of alleged misuse from members, including methods to address and counter any alleged misuse when such reports are brought to his attention.

• Recommendation E.164 Supplement 2 - Number PortabilityThis Supplement defines standard terminology for a common understanding of the different aspects of number portability within an E.164 numbering scheme. It identifies numbering and addressing formats, call flows, network architectures and routing approaches that will provide alternative methods of implementation. It also proposes some examples of the administrative and operational processes required for the successful implementation of number portability.


• Recommendation E.118 (05/06) - The international telecommunication charge card Telecommunication charge cards may be issued by Operating Agencies (OAs) to allow customers to use their card in connection with various international services at appropriate charges for each transaction and have the charges billed to their account in the country where the OA issued the charge card. Cards issued by OAs in accordance with this

http://www.itu.int/rec/T-REC-E.118/en



http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-E.164


Recommendation conform to the appropriate ISO standards.

This Recommendation has been revised to allow alternative, application-specific standards for IC cards where unique form factors require such alternatives.

• Recommendation E.190 (05/97) - Principles and responsibilities for the management, assignment and reclamation of E-Series international numbering resources This Recommendation contains the principles and responsibilities used in the management, assignment and reclamation of E-Series international numbering resources, e.g. Recommendations E.164 and E.212, under the auspices of the appropriate ITU-T Study Group.

• Recommendation E.212 (05/04) - The international identification plan for mobile terminals and mobile users A plan for unique international identification of mobile terminals and mobile users is required in order to enable these terminals and users to roam among public networks which offer mobility services. International Mobile Subscriber Identity (IMSI) is required so that a visited network can identify a roaming mobile terminal or mobile user, e.g. in order to query a subscriber's home network for subscription and billing information.

Recommendation E.190 describes the general principles to be utilized in the assignment of ITU-T E-series international numbering resources. The procedures in this Recommendation, E.212, were developed in accordance with the principles contained in Recommendation E.190, and the statements contained in Recommendation E.190 take precedence over Recommendation E.212.

• Annexes to E.212 - Annexes C, D and E to The international identification plan for mobile terminals and mobile users The ITU-TSB assigns and reclaims E.212 Mobile Country Codes (MCCs) for countries and shared MCCs for Networks according to ITU-T Rec. E.212. The ITU-TSB is also responsible for the assignment and reclamation of Mobile Network Codes (MNCs) for shared MCCs. Mobile Subscriber Identification Numbers (MSINs) are administered by the MNC assignee.

Annexes contain guidelines and procedures for the assignment of MNC.s

Expected completion - 2007

• Recommendation E.106 (10/03) - International Emergency Preference Scheme for Disaster Relief Operations (IEPS)This Recommendation describes an international preference scheme for the use of public telecommunications by national authorities for emergency and disaster relief operations. The International Emergency Preference Scheme for Disaster Relief Operations (IEPS) is needed when there is a crisis situation causing an increased demand for telecommunications when use of the International Telephone Service may be restricted due to damage, reduced capacity, congestion or faults. In crisis situations there is a requirement for IEPS users of public telecommunications to have preferential treatment.

In a crisis situation, there is a need for telecommunications among IEPS users of public telecommunications networks, such as the PSTN, ISDN or PLMN. These communications, which are regarded as essential, will be needed at the same time as the public will be attempting an increased number of calls during the period when the telecommunications networks may be restricted due to damage, congestion or faults.

Many countries have, or are developing, national preference schemes to allow preferential



http://web/md/T05-SG02-060503-TD-PLEN-0021/en





treatment for such national traffic. However, it is important for an international support scheme during a crisis to allow communications between the IEPS users in one country and their correspondents in another. The International Emergency Preference Scheme for Disaster Relief Operations (IEPS) addresses this international support scheme.

This preference scheme is only intended for use by IEPS users to be able to place calls with preference. Public emergency services on the other hand are intended for use by members of the general public to request services such as fire, police, and medical. They are often invoked by a short access code.

• Recommendation E.751 (02/96) - Reference connections for traffic engineering of land mobile networks This Recommendation provides some reference architectures for existing and future public land mobile telecommunication networks (PLMN) and also provides a high level reference connection for Future Public Land Mobile Telecommunication Systems (FPLMTS) call/connection setup. The primary purpose of the reference connection is to provide a basis for developing traffic Grade of Service (GOS) Recommendations for networks supporting mobile services. The underlying FPLMTS call flow model in the reference connection should be used as a basis for more implementation-specific configurations for detailed performance analysis and GOS target setting.

• Recommendation E.760 (03/00) - Terminal mobility traffic modeling Terminal mobility traffic modeling for land terrestrial or satellite-based mobile systems (including cellular, cordless, paging and IMT-2000) presented in this Recommendation is intended to characterize the mobile user traffic demand associated with mobile services. This demand has significance for both the user and the signaling plane.

• Recommendation E.771 (10/96) - Network grade of service parameters and target values for circuit-switched land mobile services This Recommendation proposes network Grade of Service (GOS) parameters for current and evolving land mobile services. These parameters are defined, and their target values specified, assuming that the network and the network components are operating in their normal mode (i.e. are fully operational). Further, the parameters and their target values assume normal (as opposed to distress or emergency) traffic.

• Recommendation F.116 (03/00) - Service features and operational provisions in IMT-2000

IMT-2000 systems are third generation mobile systems, which may be terrestrial, or satellite-based and may be characterized as networks in terms of service provision. This Recommendation describes Service Feature and Operational Provisions that apply to IMT-2000 systems. It defines a set of service features and capabilities to standardize service presentation and to facilitate global mobility for users across network boundaries. Some of these services features and capabilities are essential whilst others are optional.

• Recommendation E.418 (05/03) – Framework for network management of IMT-2000 networks This Recommendation lays down a framework for supporting and defining the role of network management for IMT-2000 networks. IMT-2000 networks consist of various network elements and telecommunication technologies such as wireless and IP-based services. It is intended to give some guidance to identify data that is needed to check the status/performance of networks, especially IMT-2000 networks.

Network management requires real-time monitoring of current network status and



http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-F.116






performance and the ability to take prompt action to control the performance and resources of the network when necessary. It should be noted that the complete range of network status and performance parameters are not necessary for the introduction of a network management capability.

The scope of this KPI (Key Performance Indicators) Recommendation is to find areas where meaningful measures can be identified and correlated to the broader business objectives.

Often measurements are taken because they are available not because they are meaningful. It is envisaged that the model in this Recommendation will assist carriers to direct operations areas to play a more key role in supporting the business.

Network management requires real-time monitoring of current network status and performance and the ability to take prompt action to control the performance and resources of the network and services when necessary. It should be noted that the complete range of network status and performance parameters are not necessary for the introduction of a network management capability.

• Annex A to Recommendation E.217 (05/02) - Telephone/ISDN numbering plan for the mobile-satellite services of Inmarsat The purpose of this annex is to specify a telephone/ISDN numbering plan for mobile earth stations in systems operated by Inmarsat. Such systems may include maritime, land-based and aeronautical satellite systems. In the future, the range of mobile satellite systems may also include satellite systems for other applications.

(Previous version was in Rec. E.215: 05/97)

• Recommendation E.470 (02/05) – Operational considerations for QoS of voice over IP- based networks with PSTN-IP-PSTN architecture It is recognized that IP-based networks are increasingly used to deliver voice services to customers. These networks can impact the end-to-end service quality perceived by users. In order to maintain network performance required to deliver the desired service quality, several operational issues have to be considered. These issues include defining network performance measures and their objectives, Inter-Working issues between networks employing a variety of technologies, network measurement points, information to be exchanged between network operators, etc.

ITU-T SG 13 on "Next-generation networks" has defined four key scenarios to be considered in their IP framework document:

(Scenario a) A voice call from an IP terminal connected to an IP-based network to a PSTN phone

(Scenario b) A voice call from PSTN phone to an IP terminal connected to an IP-based network

(Scenario c) A voice call from a PSTN phone to another PSTN phone via an IP-based network

(Scenario d) A voice call from an IP terminal connected to an IP-based network to another IP terminal connected to an IP-based network via PSTN

This Recommendation focuses only on Scenario c. In Scenario c both ends are PSTN (telephone) terminals and connected to PSTN at least as a local access (PSTN-IP-PSTN architecture).This network architecture is employed/or planned to be employed by many ROAs all over the world. In this case, the user may not be aware of the changes in the






underlying technology and the QoS expectations may be expected to remain the same.

This recommendation is for providing the general aspects of voice services in PSTN-IP-PSTN architecture, especially, for providing information whether or not the existing ITU-T recommendations could be applicable to PSTN-IP-PSTN voice architecture. Also, it covers the general impacts of IP networks to voice services and provides an overview of the performance measurement/management scope.

• Recommendation E.480 (09/06) - Framework for Service Management Operational requirements Service ManagementService Management (SM) is a new operational discipline being introduced to manage the increasing complexity associated with services built up from multiple interconnected networks delivering content from multiple sources. This Recommendation is intended to support and define the role of service management. It explains the service management principles and functions. The major part of this Recommendation provides a definition of service management and provides a framework for further analysis of the operational activities associated with service management.

• Recommendation E.861 (0 2/06) - Defining Operations Competency metrics Improving network and service operations quality and efficiency to significantly reduce cost has become a business imperative for telecommunications service providers worldwide. However, one needs objective metrics by which to measure operations quality and efficiency and to facilitate comparison of them among service providers. This Recommendation describes a set of metrics called Total Operations Competency (TOC) metrics that are designed to cover a comprehensive view of network and services operations. Although each metric is useful on its own, metrics can also be combined to construct quantitative indicators for high-level business objectives. These indicators, in conjunction with cost functions for metrics improvements, can be used to formulate a rich set of optimization problems pertinent to operations.

• Recommendation E.861 Revised - Defining Operations Competency metrics


• Recommendation E.802 - Framework and methodologies for the determination and application of QoS parametersThis document provides frameworks and methodologies for the identification of QoS criteria relevant to users and guidelines for conversion of these criteria into QoS parameters that can be used to evaluate the QoS of telecommunication services.

Guidelines are also given to obtain user's QoS requirements and to prioritize the criteria or parameters. All these may be applied to services supported by the terrestrial and wireless legacy networks as well as services supported by the emerging IP network.


• Recommendation E.107 - Emergency Telecommunications Service (ETS) and Interconnection Framework for National Implementations of ETSThere is a potential for bilateral/multi-lateral agreement between cooperating countries/Administrations to link their respective Emergency Telecommunications Service (ETS) systems. This Recommendation provides guidance that will enable telecommunications between one ETS National Implementation (ENI) and another ENI, in addition to providing a





description of ETS.


• Recommendation E.772 – Network grade of service parameters and target values for packet-switched public land mobile services This Recommendation applies to terrestrial based land mobile systems. Focused on packet-switched services, the goal of the Recommendation is to provide targets for GOS parameters to be used in dimensioning the radio transmission resources, the fixed infrastructure of the radio access network, and the core network hosting the switching and mobility support functionality. Recognizing that second and third generation systems will coexist over a significant period of time, the scope of this Recommendation covers teletraffic aspects related to both system generations.

This Recommendation proposes network Grade of Service (GOS) parameters for current and evolving land mobile services, i. e. those supported by evolving second generation systems and the implementation of the members in the IMT-2000 family. These parameters are defined, and their target values specified, assuming that the network and the network components are operating in their normal mode (i.e. are fully operational). Further, the parameters and their target values assume normal (as opposed to distress or emergency) traffic.

In general, the target values specified for evolved second generation systems should be considered as minimum requirements to third generation systems (where applicable), i.e. the target GOS for third generation systems should be equal to, if not more stringent than, the targets specified in this Recommendation for evolved second generation systems.

The scope of this Recommendation is delimited with reference to the following dimensions: addressed plane, connection phase, spanned network segment, medium individuality in multimedia connections, and interoperation between evolved second generation systems and IMT-2000. In particular, this Recommendation

is concerned with both the user and the control plane; introduces GOS parameters classified according to whether they relate to the call

set-up, the information transfer, or the call clear down phase of a connection; proposes, where possible, separate GOS target values associated with the radio

resources, the radio access network and the core network of mobile systems; leaves for further study the consideration of the individual mediums comprising a

multimedia connection; leaves for further study the teletraffic aspects related to interoperation between

evolved second generation systems and IMT-2000.


• Recommendation E.790 - Traffic measurement requirements for networks supporting Personal Communication Services


• Recommendation E.780 - Dimensioning methods for Public Land Mobile Systems This Recommendation applies to terrestrial based land mobile systems. Its goal is to provide a guidance for dimensioning the radio transmission resources, the fixed infrastructure of the

radio access network, and the core network hosting the switching and mobility support functionality. Recognizing that second and third generation systems will coexist over a significant period of time, the scope of this Recommendation covers teletraffic aspects related to both system generations. In particular, the Recommendation is intended to address both circuit and packet switched service.

Traffic engineering methods for public land mobile systems presented in this Recommendation are intended to help:

dimensioning the radio (transmission) resources so as to cost-effectively meet specified service quality targets while accounting for the specifics of the radio environment, in particular the dependence of the channel quality on terminal mobility characteristics, propagation environment, activity of traffic sources, and transmission activity on the traffic and signaling channels;

dimensioning the fixed infrastructure of mobile systems including the cost effective coverage of the service area, the transmission resources between BS and MSC (or related functionality), the transmission resources between MSCs, the processing capacity of BSs and MSCs and the related signaling implications;

dimensioning the transmission resources and processing capacity for the interconnection between the land mobile systems and other systems, considering the related signaling implications.

This Recommendation considers both circuit-switched and packet-switched services in terrestrial based systems. Satellite based systems are for further study.

It is recognized that circuit and packet switched services are supported at a different degree by different mobile systems. In particular so-called "second generation" systems, such as GSM, are designed to basically support circuit switched services, whereas so-called "third generation" systems, i. e.IMT-2000 and the related family of radio interfaces, are designed for a flexible allocation of the transmission resources and hence are inherently oriented towards packet switching. Further, second generation based systems and third generation systems will coexist over a significant period of time with traffic interactions associated with coverage and capacity reasons. This coexistence scenario has teletraffic implications that are in the scope of this Recommendation.

So far as practicable, this Recommendation provides guidelines which are independent of the radio access technology (e.g. whether TDMA or CDMA). However, it is recognized that the radio access technology has to be reflected in the engineering methods of specific network segments in the mobile domain. In the cases where such a distinction is necessary, this Recommendation will give separate indications.


Satellite communication

• Recommendation M.1140 (10/92) - Maritime mobile telecommunication services via satelliteThe purpose of this Recommendation is to describe general maintenance aspects of satellite maritime mobile systems and define interrelationship and interworking issues of such systems with terrestrial voice and data networks taking into consideration criteria, procedures and

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-M.1140


facility standards specified in the M- and O-Series Recommendations.

This Recommendation is predominantly based on the maintenance requirements of the INMARSAT-A maritime satellite system which is the prevailing operational maritime service. Other maritime systems such as the digital INMARSAT-C, -B and -M will be addressed in Recommendations, specific to each type. However, the following sections are equally relevant to other INMARSAT maritime systems.

• Recommendation M.1150 (04/97) - Maintenance aspects of maritime/land mobile telecommunication store-and-forward services (packet mode) via satelliteThis Recommendation describes special maintenance procedures for maritime and land mobile-satellite messaging systems predominantly based on Inmarsat-C maintenance requirements.

• Recommendation M.1160 (04/97) - Maintenance aspects of aeronautical mobile telecommunication service via satelliteThe purpose of this Recommendation is to describe the special maintenance procedures and facilities that are required for the maintenance of the Inmarsat aeronautical mobile telecommunication system via satellite, and to define interrelationship and interworking issues of such systems with terrestrial voice and data public/private networks. Wherever possible, the standard maintenance procedures and facilities specified in the M- and O-Series Recommendations, and appropriate X Series Recommendations for data should be followed for the maintenance of these systems.

• Recommendation M.1170 (04/97) - Maintenance aspects of mobile digital telecommunication service via satelliteThe purpose of this Recommendation is to describe general maintenance procedures and facilities that are required for the maintenance of the mobile digital telecommunication system via satellite (INMARSAT-M and INMARSAT-B, denoted as INMARSAT-M/B hereafter) and define interrelationship and interworking issues of such systems with terrestrial voice and data networks. Wherever possible, the standard maintenance procedures and facilities specified in the M- and O-Series Recommendations, and appropriate X-Series Recommendations for data should be followed for the maintenance of these systems.

Recommendations for Multi-media

• Recommendation H.323 ( 06/06)- Packet-based multimedia communications systems This Recommendation covers the technical requirements for multimedia communications systems in those situations where the underlying transport is a Packet Based Network (PBN) which may not provide a guaranteed Quality of Service (QOS). These packet based networks may include Local Area Networks, Enterprise Area Networks, Metropolitan Area Networks, Intra-Networks, and Inter-Networks (including the Internet). They also include dial up connections or point-to-point connections over the GSTN or ISDN which use an underlying packet based transport such as PPP. These networks may consist of a single network segment, or they may have complex topologies which incorporate many network segments interconnected by other communications links.

This Recommendation describes the components of an H.323 system. This includes Terminals, Gateways, Gatekeepers, Multipoint Controllers, Multipoint Processors, and Multipoint Control

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-H.323







Units. Control messages and procedures within this Recommendation define how these components communicate.

This Recommendation describes terminals and other entities that provide multimedia communications services over Packet Based Networks (PBN) which may not provide a guaranteed Quality of Service. H.323 entities may provide real-time audio, video and/or data communications. Support for audio is mandatory, while data and video are optional, but if supported, the ability to use a specified common mode of operation is required, so that all terminals supporting that media type can interwork.

The packet based network over which H.323 entities communicate may be a point-to-point connection, a single network segment, or an internetwork having multiple segments with complex topologies.

H.323 entities may be used in point-to-point, multipoint, or broadcast (as described in ITU-T Rec. H.332) configurations. They may interwork with H.310 terminals on B-ISDN, H.320 terminals on N-ISDN, H.321 terminals on B-ISDN, H.322 terminals on Guaranteed Quality of Service LANs, H.324 terminals on GSTN and wireless networks, V.70 terminals on GSTN, and voice terminals on GSTN or ISDN through the use of Gateways.

• Recommendation H.mmho - Multimedia Architecture. Specification of Handover Scenarios in H.323 Systems


• Recommendation H.mmsm - End to end Open Services Architectural Framework. Specification of service mobility requirements with regard to Multimedia Architectures


• Annex I to Recommendation H.323 - Packet based MM telephony over error prone channels


• Recommendation H.223 (07/01) – Multiplexing Protocol for Low Bit Rate Multimedia Communication This Recommendation specifies the frame structure, format of fields and procedures of the packet multiplexing protocol for low bit rate multimedia communication. This protocol can be used between two low bit rate multimedia terminals, or between a low bit rate multimedia terminal and a Multipoint Control Unit (MCU) or an InterWorking adapter (IWA).

The protocol allows the transfer of any combination of digital voice/audio, digital video/image and data information over a single communication link. This protocol provides low delay and low overhead by using segmentation and reassembly and by combining information from different logical channels in a single packet. The control procedures necessary to implement this multiplexing protocol are specified in Recommendation H.245.

In this Recommendation communication between different protocol layers is modeled as a set of abstract primitives, which represent a logical exchange of information. The decomposition of functionality into (sub)layers, as well as the description of the primitives, do not imply a particular method of implementation. In particular, layers may exchange the



contents of a logical unit (an SDU) in a "streaming" mode where information exchange may start before the transferring layer has the complete unit in its possession.

• Recommendation H.246 (05/06) – Interworking of H-series multimedia terminals with H- series multimedia terminals and voice/voiceband terminals on GSTN and ISDNThis revision of H.246 incorporates the separately published text of Amendment 1 (Usage of H.243 multipoint control messages and support for Unicode characters in H.320 systems), Annex E1 (Mobile Application Part and H.225.0 interworking), Annex E2 (ANSI-41 (Americas) Mobile Application Part and H.225.0 interworking), Annex C (Annex C:ISDN User Part function – H.225.0 interworking, and Annex F (H.323-H.324 interworking), along with some changes of editorial nature. It also incorporates the technical and editorial corrections from the H.323 System Implementors’ Guide (09/2005).

• Recommendation H.501 (03/02) - Protocol for mobility management and intra/inter- domain communication in multimedia systems The purpose of this Recommendation is to define messages and procedures for mobility management and for communication within and between domains of a mobile or non-mobile multimedia environment for the purpose of address resolution, user authentication, service data exchange, access authorization, call validation and usage reporting.

This Recommendation describes a protocol for communication between logical elements of a multimedia packet network to allow the completion of calls to and from users managed by such logical elements. This protocol can be used in mobile and non-mobile environments for the purpose of address resolution, user authentication, service data exchange, access authorization, call validation and usage reporting. These capabilities enable the protocol to be used for mobility management in mobile environments.

The general procedure is for logical elements to exchange information regarding the location of users or endpoints, in the form of addresses each administrative domain can resolve. Addresses can be specified in a general manner or in an increasingly specific manner. Additional information allows elements within an administrative domain to determine the most appropriate administrative domain to serve as the destination for the call. Logical elements may control access to their exposed addresses, and require reports on the usage made during calls to those addresses.

• Recommendation H.510 (03/02) - Mobility for H.323 multimedia systems and services The purpose of this Recommendation is to define services and procedures for the support of mobility in H.323 multimedia systems.

This Recommendation deals with mobility aspects for H.323 systems above the transport layer. H.510 applies new functions defined in support of mobility management to H.323-compliant systems.

The main focus is on the support of terminal mobility, although support of user mobility in the context of H.323 is covered as well. This version of this Recommendation does not cover handover procedures where active calls can be maintained during location changes.

Interworking with other networks to support mobility across networks of different types is outside the scope of this Recommendation.

• Recommendation H.530 (03/02) - Symmetric security procedures for H.323 mobility in H.510 The purpose of this Recommendation is to describe security procedures for an H.323






http://www.itu.int/rec/T-REC-H.246/en


multimedia mobility environment. This Recommendation provides the details about the security procedures for H.510.

So far, the signalling capabilities of ITU-T Rec. H.235 in its versions 1 and 2 [4] are designed to handle security in mostly static H.323 [5] environments. Those environments and multimedia systems can achieve some limited mobility within gatekeeper zones; ITU-T Rec. H.323 [5] in general and ITU-T Rec. H.235 [4] specifically provide only very little support for secure roaming of mobile users and terminals across different domains with many involved entities in a mobility, distributed environment for example.

The H.323 mobility scenarios depicted in ITU-T Rec. H.510 [6] regarding terminal mobility pose a new situation with their flexible and dynamic character also from a security point of view. Roaming H.323 users and mobile terminals have to be authenticated by a foreign, visited domain. Likewise, the mobile user would like to obtain evidence about the true identity of the visited domain. In addition to that, it may be also useful to obtain evidence about the identity of the terminals complementing user authentication. Thus, these requirements demand for mutual authentication of the user and the visited domain and optionally also of the identity of the terminal.

As the mobile user is usually known only to the home domain where the user is subscribed and assigned a password, the visited domain initially does not know the mobile user. As such, the visited domain does not share any established security relationship with the mobile user and the mobile terminal. In order to let the visited domain achieve the authentication and authorization assurance for the mobile user and for the mobile terminal, the visited domain would relay certain security tasks such as authorization checks or key management to the home domain through intermediate network and service entities. This requires securing the communication and key management between the visited domain and the home domain too.

While, in principle, mobility H.323 environments are more open than closed H.323 networks, there is of course also need to appropriately secure the key management tasks. It is also true that communication within and across the mobility domains deserves protection against malicious tampering.

In summary, this Recommendation describes a generic security concept for mobility among domains for multimedia applications and multimedia services. The technical details describe the deployment for H.323 and for H.510 in particular, but are considered potentially open to other environments.

• Recommendation G.728 (09/92) - Coding of speech at 16 kbit/s using low-delay code excited linear prediction This Recommendation contains the description of an algorithm for the coding of speech signals at 16 kbit/s using low-delay code excited linear prediction (LD-CELP).

Under further study is the future incorporation of three additional appendices (to be published separately) consisting of LD-CELP network aspects, LD-CELP fixed-point implementation description, and LD-CELP fixed-point verification procedures.

• G.728 (1992) Amendment 1 (05/06) - revised Annex J - Variable bit rate operation of LD- CELP mainly for voiceband-data applications in DCMEAnnex J to ITU-T Rec. G.728 defines a 40 kbit/s extension optimized for voiceband data signals of the existing Annex G/G.728 – 16 kbit/s fixed point specification. The main difference between the codec described hereby and the codec described in Annex G/G.728 is the application of a Trellis-Coded Quantization (TCQ) approach to codebook search. The TCQ

http://web/rec/T-REC-G.728/recommendation.asp?lang=en&parent=T-REC-G.728-200605-I!Amd1

http://www.itu.int/rec/recommendation.asp?type=items&lang=e&parent=T-REC-G.728-199209-I

http://www.itu.int/rec/recommendation.asp?type=items&lang=e&parent=T-REC-G.728-199209-I

approach replaces the analysis-by-synthesis approach to codebook search of ITU-T Rec. G.728 only in voiceband data (VBD) mode.

The backward adaptation of the predictor achieved in VBD mode is almost identical to the backward adaptation achieved in speech mode (ITU-T Rec. G.728). Additionally, the same adaptation cycle is used for both speech mode (ITU-T Rec. G.728) and VBD mode. In speech mode, the 40 kbit/s reverts to the LD-CELP of ITU-T Rec. G.728.

This annex includes an electronic attachment containing test vectors for implementation verification of Annex J/G.728.

• Recommendation G.729 (03/96) and its Annexes – Coding of speech at 8kbit/s using CS- ACELP (conjugate – structure, algebraic-code- excited liner prediction) This Recommendation contains the description of an algorithm for the coding of speech signals at 8 kbit/s using Conjugate-Structure Algebraic-Code-Excited Linear-Prediction (CS-ACELP).

This coder is designed to operate with a digital signal obtained by first performing telephone bandwidth filtering (Recommendation G.712) of the analogue input signal, then sampling it at 8000 Hz, followed by conversion to 16-bit linear PCM for the input to the encoder. The output of the decoder should be converted back to an analogue signal by similar means.

• Recommendation G.729 Revised - Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)ITU-T Rec. G.729 contains the description of an algorithm for the coding of speech signals using Conjugate-Structure Algebraic-Code-Excited Linear-Prediction (CS-ACELP) operating at the basic bit rate of 8 kbit/s using fixed point arithmetic. Additional modules include: reduced complexity implementation at 8kbit/s; operation at 6.4 and 11.8 kbit/s; silence removal (voice activity detection, discontinuous transmission and comfort noise generation); floating point arithmetic implementation; and 8-32 kbit/s scalable wideband speech and audio coding extension.

This revision incorporates and integrates in a single body of text the corrections and clarifications previously identified in various corrigenda and Implementors’ Guides. The C source code is also repackaged and has been reviewed for greater consistency and ease-of-use.

The revised G.729 Release 2 ANSI C-source code and test vectors are available as an attachment to the main full under approval.


• Recommendation G.729.1 (0 5/06) – G.729 based Embedded Variable bit-rate coder: An 8-32 kbit/s scalable wideband coder bitstream interoperable with G.729G.729.1 describes an 8-32 kbit/s scalable wideband (50-7000Hz) audio/speech coding algorithm extension to the ITU-T G.729 speech coder/ G.729.1 can encode wideband signals at bitrates of 14 to 32 kbit/s. The produced embedded bitstream has granularity steps of 2 kbit/s allowing graceful quality improvements. G.729.1 can also be used as a narrowband codec to encode 50-4000 Hz signals at bit rates of 8 and 12 kbit/s. At 8 kbit/s, the bitstream is compliant with the G.729 bitstream format. This allows full interoperability with G.729, G.729 Annex A and G.729 Annex B. Hence an efficient deployment in existing G.729 based VoIP infrastructures is foreseen. Frame size (20 ms), delay (48.9375 ms), complexity (35.8

http://www.itu.int/rec/T-REC-G.729.1

http://www.itu.int/rec/T-REC-G.729.1

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-G.729

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-G.729

WMOPS) and quality in various conditions are all compliant with the requirements set and suitable for the targeted applications.

• Recommendation G.722.2 (07/03) – Wideband coding of speech at around 16 kbit/s using adaptive multi-rate Wideband (AMR-WB) This Recommendation describes the high quality Adaptive Multi-Rate Wideband (AMR-WB) encoder and decoder that is primarily intended for 7 kHz bandwidth speech signals. AMR-WB operates at a multitude of bit rates ranging from 6.6 kbit/s to 23.85 kbit/s. The bit rate may be changed at any 20 ms frame boundary.

G.722.2 AMR-WB is the same codec as the 3GPP AMR-WB. The corresponding 3GPP specifications are TS.26.190 for the speech codec and TS 26.194 for the Voice Activity Detector.

• Recommendation H.263 (01/05) - Video coding for low bit rate communication This Recommendation specifies a coded representation that can be used for compressing the moving picture component of audio-visual services at low bit rates. The basic configuration of the video source coding algorithm is based on Recommendation H.261 and is a hybrid of inter-picture prediction to utilize temporal redundancy and transform coding of the remaining signal to reduce spatial redundancy. The source coder can operate on five standardized video source formats: sub-QCIF, QCIF, CIF, 4CIF and 16CIF, and can also operate using a broad range of custom video formats.

The decoder has motion compensation capability, allowing optional incorporation of this technique in the coder. Half pixel precision is used for the motion compensation, as opposed to Recommendation H.261 where full pixel precision and a loopfilter are used. Variable length coding is used for the symbols to be transmitted.

In addition to the basic video source coding algorithm, eighteen negotiable coding options are included for improved compression performance and the support of additional capabilities. Additional supplemental information may also be included in the bitstream for enhanced display capability and for external usage.

• Recommendation H.264 (03/05) - Advanced video coding for generic audiovisual services As the costs for both processing power and memory have reduced, network support for coded video data has diversified, and advances in video coding technology have progressed, the need has arisen for an industry standard for compressed video representation with substantially increased coding efficiency and enhanced robustness to network environments.

This Recommendation | International Standard was developed in response to the growing need for higher compression of moving pictures for various applications such as videoconferencing, digital storage media, television broadcasting, internet streaming, and communication. It is also designed to enable the use of the coded video representation in a flexible manner for a wide variety of network environments. The use of this Recommendation | International Standard allows motion video to be manipulated as a form of computer data and to be stored on various storage media, transmitted and received over existing and future networks and distributed on existing and future broadcasting channels.

• Recommendation H.264 Amendment 2 - Revision of H.264, including 4:4:4 and scalable video coding extensions




http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-G.722.2

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-G.722.2

Related Multi-Media Recommendations

• Recommendation H.450 series – Generic functional protocol for the support of supplementary services in Recommendation H.323 These Recommendations define the signaling protocol between H.323 entities for the control of supplementary services. Detailed procedures applicable to individual supplementary services are specified by other Recommendations of the H.450.x-Series and by individual manufacturers for proprietary services using the capabilities defined in this Recommendation.

• Recommendation H.245 ( 05/06) (version 13) – Control protocol for multimedia communicationThis Recommendation specifies syntax and semantics of terminal information messages as well as procedures to use them for in-band negotiation at the start of or during communication. The messages cover receiving and transmitting capabilities as well as mode preference from the receiving end, logical channel signalling, and Control & Indication. Acknowledged signalling procedures are specified to ensure reliable audiovisual and data communication.

Products claiming compliance with Version 13 of H.245 shall comply with all of the mandatory requirements of this Recommendation. Version 13 products can be identified by H.245 TerminalCapabilitySet messages containing a protocolIdentifier value of {itu-t (0) recommendation (0) h (8) 245 version (0) 13}.

This revision added ASN.1 syntax and semantics for H.361 and H.249 OID descriptions. It also introduced some minor corrections.

• Recommendation H.332 (09/98) – H.323 extended for loosely coupled conferences This Recommendation covers highly scalable conferencing on packet-based networks involving hundreds and thousands of participants. This type of conference is defined in Recommendation H.323 as broadcast and broadcast-panel conferences.

• H.235.x Sub-series of Recommendations (09/05) This Recommendation describes enhancements within the framework of the H.3xx-series Recommendations to incorporate security services such as Authentication and Privacy (data encryption). The proposed scheme is applicable to both simple point-to-point and multipoint conferences for any terminals which utilize ITU-T Rec. H.246 as a control protocol; also to H.323 systems that use the H.225.0 RAS and/or Call Signaling Protocol.

For example, H.323 systems operate over packet-based networks which do not provide a guaranteed quality of service. For the same technical reasons that the base network does not provide QOS, the network does not provide a secure service. Secure real-time communication over insecure networks generally involves two major areas of concern – authentication and privacy.

This Recommendation describes the security infrastructure and specific privacy techniques to be employed by the H.3xx-series of multimedia systems. This Recommendation will cover areas of concern for interactive conferencing. These areas include, but are not strictly limited to, authentication and privacy of all real-time media streams that are exchanged in the conference. This Recommendation provides the protocol and algorithms needed between the H.323 entities.

http://www.itu.int/rec/T-REC-H.235.0/en


http://www.itu.int/rec/T-REC-H.245

http://www.itu.int/rec/T-REC-H.245

http://www.itu.int/rec/recommendation.asp?type=products&lang=e&parent=T-REC-H

http://www.itu.int/rec/recommendation.asp?type=products&lang=e&parent=T-REC-H

This Recommendation utilizes the general facilities supported in ITU-T Rec. H.245 and as such, any standard which operates in conjunction with this control protocol may use this security framework. It is expected that, wherever possible, other H-series terminals may interoperate and directly utilize the methods described in this Recommendation. This Recommendation will not initially provide for complete implementation in all areas, and will specifically highlight endpoint authentication and media privacy.

This Recommendation includes the ability to negotiate services and functionality in a generic manner, and to be selective concerning cryptographic techniques and capabilities utilized. The specific manner in which they are used relates to systems capabilities, application requirements and specific security policy constraints. This Recommendation supports varies cryptographic algorithms, with varies options appropriate for different purposes; e.g., key lengths. Certain cryptographic algorithms may be allocated to specific security services (e.g., on e for fast media stream encryption and another for signaling encryption).

It should also be noted that some of the available cryptographic algorithms or mechanisms may be reserved for export or other national issues (e.g., with restricted key lengths). This Recommendation supports signaling of well-known algorithms in addition to signaling non-standardized or proprietary cryptographic algorithms. There are no specifically mandated algorithms; however, it is strongly suggested that endpoints support as many of the applicable algorithms as possible in order to achieve interoperability. This parallels the concept that the support of ITU-T Rec. H.245 does not guarantee the interoperability between two entities’ codecs.

Version 4 of ITU-T Rec. H.235 breaks up the former ITU-T Rec. H.235v3 into a suite of H.235.x subseries Recommendations, and restructures the subseries. New ITU-T Recs H.235.8 and H.235.9 have been added to the suite; other subseries Recommendations have been extended with new functionality (ITU-T Recs H.235.3, H.235.5). ITU-T Rec. H.235.0 holds the H.323 security framework with common text and useful general information for all H.235.x subseries Recommendations.

New H.235.0 Appendices IV, V, and VI provide a mapping of text, figures and tables from ITU-T Rec. H.235 version 3 (2003), including the subsequent Corrigendum 1 and amendments, to the new structure.

• Recommendation H.361 (05/06) – End-to-End Quality of Service (QoS) and Service Priority Control and Signaling in H.323 SystemsThis Recommendation provides the enhancements to the H.323 signaling to allow a call to establish end-to-end QoS and service priority. Then enhancements described here enable a call to acquire QoS even when a call traverses multiple service and network operator domains. While these enhancements are optional, the H.323 entities are required to ignore and not fail abruptly on the receipt of the new objects.

Signalling related Recommendations

• Recommendation Q.NGN-nacf-mob – Signalling Requirement and Architecture of Access Mobility Control in NACF This ITU-T Q-Series Recommendation provides the signalling requirements and architecture of Access Mobility Function in NACF (Network Attachment Control Functions).




TMN related Recommendations

• Recommendation M.3200 (04/97) - TMN management services and telecommunications managed areas: overview This Recommendation is intended to provide an overview of Telecommunications Management Network (TMN) Management Services and Telecommunications Managed Areas. It provides the framework for the specification of protocols, messages, management information, etc. for TMN interfaces. The TMN Management Services are described from the TMN users perspective and are independent of the protocols, messages and information models chosen. They will therefore assist in the smooth transition from a non-TMN to a TMN environment.

It should be noted that flexibility will be required in the definition of TMN Management Services to enable additional requirements to be accommodated as they are identified.

To avoid discrepancies and duplications, this Recommendation establishes the structuring principles (e.g.numbering, naming, etc.) for the M.3200-Series of Recommendations.

• Recommendation M.3210.1 (01/01) - TMN management services for IMT-2000 security management This recommendation is one of the series of M.3200 TMN Management Service recommendations that provide description of management services, goals and context for management aspects of IMT2000 networks. This recommendation provides a profile for fraud management in an IMT2000 mobile network. This is done by existing and defining new function sets, functions and parameters and adding additional semantics and restrictions.

This Recommendation provides requirements and analysis of the security management (administration) of IMT-2000. The emphasis is on the X interface between two service providers and the management services needed between the two service providers to detect and prevent fraud. The methodology used in this Recommendation is based on ITU-T M.3020.

This Recommendation describes a subset of security management services, identified in ITU-T M.3200 as a TMN managed area, for IMT-2000 management. It describes the requirements and analysis of operating the Fraud Information Gathering System (FIGS) between service providers. FIGS provides the means for the wireless service provider to monitor a defined set of subscriber activities. The aim is to enable service providers/network operators to use FIGS to limit their financial exposure to large unpaid bills produced on subscriber accounts whilst the subscriber is roaming outside their home areas.

Verification of the authenticity of the Home Network-FDS and the Visited Service Provider is beyond the scope of this management service.

The Recommendation M.3060 - Principles for the Management of the Next Generation Networks (03/06) and M.3016-series on TMN security are also applicable.

Security related Recommendations

http://www.itu.int/rec/T-REC-M/e

http://www.itu.int/rec/T-REC-M.3060/en

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-M.3210.1

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-M.3210.1



• Recommendation X.509 (08/05) - Information Technology - Open Systems Interconnection - The Directory: Public-key and Attribute Certificate Frameworks ISO – International Organization for StandardizationIEC – International Electrotechnical Commission

This revised Recommendation | International Standard also defines a framework for public-key certificates and attribute certificates. These frameworks may be used by other standards bodies to profile their application to Public Key Infrastructures (PKI) and Privilege Management Infrastructures (PMI). Also, this Recommendation | International Standard defines a framework for the provision of authentication services by Directory to its users. It describes two levels of authentication: simple authentication, using a password as a verification of claimed identity; and strong authentication, involving credentials formed using cryptographic techniques. While simple authentication offers some limited protection against unauthorized access, only strong authentication should be used as the basis for providing secure services.

• Recommendation X.841 (10/00) - Information technology - Security techniques - Security information objects for access control This new Recommendation | International Standard provides object definitions that are commonly needed in security standards to avoid multiple and different definitions of the same functionality. Precision in these definitions is achieved by use of the Abstract Syntax Notation One (ASN.1).

This new Recommendation | International Standard covers only static aspects of Security Information Objects (SIOs).

• Recommendation X.842 (10/00) - Information technology - Security techniques - Guidelines on the use and management of Trusted Third Party Services This new Recommendation | Technical Report provides guidance for the use and management of Trusted Third Party (TTP) services, a clear definition of the basic duties and services provided, their description and their purpose, and the roles and liabilities of TTPs and entities using their services.

This new Recommendation | Technical Report identifies different major categories of TTP services including time stamping, non-repudiation, key management, certificate management, and electronic notary public.

• Recommendation X.843 (10/00) - Information technology - Security techniques - Specification of TTP Services to support the Application of Digital Signatures The goal of this new Recommendation | International Standard is to define the services required to support the application of digital signatures for non repudiation of creation of a document. Since this implies integrity of the document and authenticity of the creator, the services described in this draft new Recommendation | International Standard can also be combined to implement integrity and authenticity services.

• Recommendation X.1121 (04/04) – Framework of security technologies for mobile end-to- end data communicationsThis recommendation describes security threat for mobile end-to-end data communication and security requirements from the point of view of mobile user and ASP. In addition, this recommendation categorizes security technologies by security functions that satisfy above security requirements and by the place to which the security technology applies on models of mobile end-to-end data communication.

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-X.1121






http://www.itu.int/rec/recommendation.asp?type=folders<=e&parent=T-REC-X.841

http://www.itu.int/rec/recommendation.asp?type=folders<=e&parent=T-REC-X.841



This recommendation provides security requirements, which are from the point of view of mobile user and application service provider in upper layer in OSI Reference Model, for mobile end-to-end data communication between mobile terminal in mobile network and application server in open network.

This recommendation provides a framework of security technologies for mobile end-to-end data communication.

This recommendation does not provide the details of mobile network except for that provides wireless network access to mobile terminal and is connected to open network.

• Amendment 1 to Recommendation X.1121 - Security technologies for mobile end-to-end data communication, enhancements


• Recommendation X.1122 (04/04) – Guideline for implementing secure mobile systems based on Public Key Infrastructure (PKI) Although PKI technology is very useful security technology to realize many security functions (encipherment, digital signature, data integrity, and so on) to mobile end-to-end data communication, PKI technology should be adapted for mobile end-to-end data communication. However, the method to construct and manage secure mobile systems based on PKI technology has not been established yet. This recommendation shows the guideline when constructing secure mobile systems based on PKI technology.

This document shows the guideline when constructing secure mobile systems based on PKI technology. The range of applications of this document shall be as follows:

Its subject shall be the control of Certificates in the mobile in general. However, defining a method of mobile settlement as a settlement model shall be

excluded from the area of application of this document.

• Amendment 1 to Recommendation X.1122- Guideline for implementing secure mobile systems based on PKI, enhancements


• Recommendation X.msec-3 - General security service (policy) for secure mobile end to end data communication This baseline document of x.msec-3 describes general security service for secure mobile communication. The investigation of general security service is important for both service providers and users. The service providers can use the general security service to overcome limits of mobile network and satisfy different users and applications with different degree of security. The users can easily enjoy secure communication under the general security service. The general security service is realized by security policy with three layers. One layer is super security policy as value added service that safeguards mobile communication with sensitive information. The second layer is baseline security policy as prevalent service which satisfies essential mobile communication without sensitive information. The last layer is no security policy defined as the policy under which mobile terminal and application service provider have no security-related function.

Security policy is owned by mobile network operator. The security levels are provided by mobile network operator. The negotiation happens between mobile terminal and security







gateway.


• Recommendation X.msec-4 Authentication architecture in mobile end-to-end data communicationThis draft Recommendation describes a generic authentication mechanism in mobile end to end data communication between mobile users and all kinds of service providers in the network.

This specification applies to the mobile terminals based on different mobile communication standardizations, and application server in all kinds of open network, including mobile user, mobile terminal, service provider, application server.


• Recommendation X.e2emp-w - End-to-end multicast protocol over wireless network


• Recommendation X.crs - Correlative reacting system in mobile data communication This draft Recommendation describes an open architecture of Correlative Reacting System against potential security threats from unsafe mobile terminals in end-to-end data communications in mobile networks. The architecture provides for an operator network the security enhancement capabilities of both network access control and application service restrictions, which results in a mechanism that prevents virus or worms from rapid spreading through the operator network.


• Recommendation X.mrmcp-1 – Mobile relayed multicast protocol: Framework


• Recommendation X.mrmcp-2 – Mobile relayed multicast protocol: Specification for simplex group applications


Quality of Service related Recommendations

• Recommendation P.313 Revised – Transmission characteristics and measurement methods for cordless and mobile hands-free terminals


• Recommendation P.CARHF – Hands-free Communication in Vehicles


• Recommendation Y.PM - Performance Measurement in IP Networks


_____________

quality of service related recommendations

Business