ITU-T H 360-2004 An architecture for end-to-end QoS control and signalling SERIES H AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services C Quality of service arvi.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T H.360TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2004) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Quality of service architecture for audiovisual and multimedia services An architecture for end-to-end QoS co

2、ntrol and signalling ITU-T Recommendation H.360 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H.229 Systems aspects

3、H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359 Quality of service architecture fo

4、r audiovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile mul

5、timedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559 Mobile multimedia collaboration inter-working proced

6、ures H.560H.569 BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. H.360 (03/2004) i ITU-T Recommendation H.360 An architecture for end-to-end QoS control and signalling S

7、ummary End-to-end quality of service (QoS) and service priority require coordination of resources and quality control mechanisms at all points in a multimedia system. Procedures for achieving this entail a combination of information flows and functionality at various levels in the system. This Recom

8、mendation provides a reference architecture for defining and analysing mechanisms and procedures for achieving end-to-end QoS and service priority control. Source ITU-T Recommendation H.360 was approved on 15 March 2004 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure

9、. ii ITU-T Rec. H.360 (03/2004) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, ope

10、rating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn,

11、produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In

12、 this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g.

13、interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not sugge

14、st that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evide

15、nce, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which ma

16、y be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatso

17、ever, without the prior written permission of ITU. ITU-T Rec. H.360 (03/2004) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative reference . 1 3 Definitions 1 4 Abbreviations and acronyms . 2 5 Generic QoS architecture 3 5.1 Functional planes 3 5.2 Decomposition o

18、f MM systems into administrative domains 4 5.3 QoS classification at service, application and network levels 4 5.4 QoS budgets 6 5.5 Functional entities and reference points. 7 6 QoS control and signalling procedures. 9 6.1 General framework. 9 6.2 Classification of QoS signalling types . 10 6.3 QoS

19、 signalling procedures 13 ITU-T Rec. H.360 (03/2004) 1 ITU-T Recommendation H.360 An architecture for end-to-end QoS control and signalling 1 Scope This Recommendation contains a reference architecture for controlling the QoS and service priority of multimedia services in networks which are comprise

20、d of combinations of switched circuit and packet domains, wireless and wireline technologies, and conventional and packet-based terminals. The reference architecture is functionally defined. This Recommendation uses a domain-based approach which allows issues of administrative control and security a

21、lso to be considered. This Recommendation is concerned with end-to-end QoS control in multimedia systems made up of multiple and disparate administrative domains and QoS mechanisms. Detailed mechanisms for generic QoS control in individual networks are not described here but may be found in ITU-T Y-

22、series Recommendations. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other reference

23、s are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a

24、 document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 2.1 Normative references ITU-T Recommendation G.1010 (2001), End-user multimedia QoS categories. ITU-T Recommendation M.2301 (2002), Performance objectives and procedures for provisionin

25、g and maintenance of IP-based networks. ITU-T Recommendation Y.1540 (2002), Internet protocol data communication service IP packet transfer and availability performance parameters. ITU-T Recommendation Y.1541 (2002), Network performance objectives for IP-based services. 2.2 Informative reference IEE

26、E Standard 802.1D-1998, Information technology Telecommunications information exchange between systems Local and metropolitan area Common specifications: Media access control (MAC) bridges. 3 Definitions This Recommendation defines the following terms: 3.1 application service: A network-based servic

27、e involving the transmission and/or processing of multimedia information. 3.2 Application Service Provider (ASP): A Service Provider providing Application Services. NOTE The same business entity may act as both Network Operator and Application Service Provider. 3.3 end user: An entity employing Appl

28、ication Services. 2 ITU-T Rec. H.360 (03/2004) 3.4 End User Domain (EUD): A collection of physical or functional entities, including terminal equipment and network resources under the control of an End User. 3.5 Interconnect Function (ICF): A functional entity that interconnects Network Operator Dom

29、ains. It provides a policy and/or administrative boundary and may police authorized media flows between two Network Operator Domains to ensure they are consistent with the QoS policies of the Network Operator of that domain. 3.6 network operator: An administrative entity operating a network. 3.7 Net

30、work Operator Domain (NOD): A collection of network resources sharing a common set of policies, QoS mechanisms and technologies under the control of a Network Operator. 3.8 Network Policy Entity (NPE): A functional entity residing in a Network Operator Domain that maintains the policies of the Netwo

31、rk Operator. 3.9 Quality-of-Service Manager (QoSM): A functional entity residing in a Service Domain that mediates requests for end-to-end QoS in accordance with policies of the Application Service Provider controlling the Service Domain. It communicates with other QoSMs and with RMs to determine, e

32、stablish and control QoS. 3.10 Quality-of-Service Policy Entity (QoSPE): A functional entity residing in a Service Domain that manages the QoS policies of the Application Service Provider controlling the Service Domain. It provides authorization of permitted and default QoS levels. It receives reque

33、sts from and issues responses to QoSMs to establish the authorized end-to-end QoS levels. 3.11 Service Domain (SD): A collection of physical or functional entities offering Application Services under the control of an Application Service Provider which share a consistent set of policies and common t

34、echnologies. 3.12 Resource Manager (RM): A functional entity residing in a Network Operator Domain that applies a set of policies and mechanisms to transport resources within the domain to enable specified QoS levels to be achieved within the domain. 3.13 Transport Functionality (TF): A functional e

35、ntity representing the collection of transport resources within a Network Operator Domain. 3.14 User Equipment (UE): Equipment under the control of an End User. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations: ASP Application Service Provider COPS Common Open Policy

36、 Service DiffServ Differentiated Services EUD End User Domain ICF Interconnect Function IntServ Integrated Services MM MultiMedia MPLS Multi-Protocol Label Switching NOD Network Operator Domain NPE Network Policy Entity QoS Quality of Service ITU-T Rec. H.360 (03/2004) 3 QoSM Quality-of-Service Mana

37、ger QoSPE Quality-of-Service Policy Element QST QoS Signalling Type RM Resource Manager RSVP Resource ReSerVation Protocol SD Service Domain TF Transport Functionality UE User Equipment 5 Generic QoS architecture 5.1 Functional planes To achieve end-to-end QoS control in multimedia (MM) systems, the

38、 QoS mechanisms operating in the multimedia application must operate together with the QoS mechanisms operating in the packet-based network (e.g., RSVP, DiffServ, MPLS, etc.) which are generic and independent of the application. Furthermore, network management mechanisms may also be involved in cont

39、rolling and managing QoS. Figure 1 illustrates the relationship between a number of functional planes within which QoS mechanisms reside. Figure 1/H.360 Relationship between MM application, packet-based network, management, and circuit-switched planes 5.1.1 MM application plane Within this plane, Qo

40、S parameters specific to the MM application (e.g., QoS service class) are requested, authorized, signalled, monitored and controlled. 5.1.2 Packet-based network plane Within this plane, general non-application specific traffic parameters effecting QoS (e.g., end-to-end delay, delay variation (jitter

41、), packet loss, and bandwidth) must be controlled and accounted to achieve the QoS requirements requested by the MM application. This plane may be based on IP, MPLS, or other technologies. With connection-oriented MPLS networks, it may be possible to support some QoS services with greater efficienci

42、es than connectionless IP networks. 4 ITU-T Rec. H.360 (03/2004) 5.1.3 Circuit-switched plane Within this plane, every call receives the same level of quality. Circuit-switched networks only provide a choice of call acceptance or non-acceptance depending upon the requested and available capacities.

43、Once a call has been accepted, the capacity allocated is constant throughout the connection duration. Circuit-switched networks are engineered to provide acceptable quality levels for interactive communications. Transmission planning guidelines will determine the levels of quality achievable in circ

44、uit-switched environments. 5.1.4 Management plane Within this plane, QoS signalling statistics are exchanged with the MM Application Plane and Packet-Based Network Plane. This signalling will include call statistics, network utilization information, network configuration, performance monitoring, and

45、 network resource allocation. 5.2 Decomposition of MM systems into administrative domains An MM system will in the general case be made up of a number of separate Administrative Domains, each representing the domain of control of an MM End-User, Application Service Provider or Network Operator. 5.2.

46、1 End user domains An End User Domain is a collection of physical or functional entities, including terminal equipment and network resources under the control of an End User. The End User may be an individual or administrative entity employing Application Services. 5.2.2 Service domains A Service Do

47、main is a collection of physical or functional entities offering Application Services under the control of an Application Service Provider which share a consistent set of policies and common technologies. An MM system will in the general case be made up of a number of separate Service Domains. 5.2.3

48、 Network operator domains A Network Operator Domain is a collection of network resources sharing a common set of policies, QoS mechanisms and technologies under the control of a Network Operator. An MM system will, in general, be made up of a number of separate Network Operator Domains. Network Oper

49、ator Domains consist largely of transport-related functionality; this includes IP routers, ATM/MPLS switches; however, they may contain application-based elements such as NATs, firewalls, etc. Each Network Operator Domain may have its own QoS policies and/or differ from other domains in terms of administrative control (e.g., Network Operator), QoS mechanisms (RSVP/IntServ, DiffServ, MPLS, etc.), access, metering, addressing schemes (global, local), network protocol (IPv4 or IPv6), etc. 5.3 QoS classification at service, application and network l