1、 International Telecommunication Union ITU-T H.248.53TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2009) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Communication procedures Gateway control protocol: Traffic management packages Recommendation ITU-T H.248.
2、53 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 H.230H.239 Communication procedures H.240H.25
3、9 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 for audiovisual and multimedia services H.360H.
4、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 multimedia collaboration applications and servic
5、es 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.559Mobile multimedia collaboration inter-working procedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADV
6、ANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handl
7、ing H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to consumption H.770H.779 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.248.53 (03/2009) i Recommendation ITU-T H.248.53 Gateway control protocol
8、: Traffic management packages Summary H.248 media gateways may support interfaces with packet-switched networks (via ephemeral terminations). Such types of bearer connections could be subject of traffic control mechanisms. Recommendation ITU-T H.248.53 provides three H.248 packages addressing traffi
9、c management, traffic policing and packet size control. This Recommendation focuses on the traffic policing function. This revision contains an update to the traffic policing statistics package. The update adds new statistic elements and expands these packages procedures allowing the reporting of fi
10、ner-grained information regarding any violations of the policing parameters. Source Recommendation ITU-T H.248.53 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures. ii Rec. ITU-T H.248.53 (03/2009) FOREWORD The International Telecommunication
11、 Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questio
12、ns 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, produce Recommendations o
13、n 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 this Recommendation, the
14、 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., interoperability or appl
15、icability) 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 suggest that compliance with
16、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 evidence, validity or applica
17、bility 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 may be required to impleme
18、nt this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any mean
19、s whatsoever, without the prior written permission of ITU. Rec. ITU-T H.248.53 (03/2009) iii CONTENTS Page 1 Scope 1 1.1 Policy rules and policy enforcement behaviour . 1 1.2 Deriving policy enforcement point parameters 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms define
20、d in this Recommendation. 2 4 Abbreviations and acronyms 3 5 Conventions 4 6 Traffic management package 4 6.1 Properties 4 6.2 Events . 6 6.3 Signals 6 6.4 Statistics 6 6.5 Error codes 6 6.6 Procedures 6 7 Traffic policing statistics package 9 7.1 Properties 9 7.2 Events . 9 7.3 Signals 10 7.4 Stati
21、stics 10 7.5 Error codes 11 7.6 Procedures 11 8 Packet size package 13 8.1 Properties 14 8.2 Events . 14 8.3 Signals 14 8.4 Statistics 14 8.5 Error codes 15 8.6 Procedures 15 9 Deriving policy enforcement point parameters from parameters of traffic management and other packages 16 9.1 Motivation 16
22、9.2 ATM bearer traffic policing . 18 9.3 AAL2 bearer traffic policing 20 9.4 IP bearer traffic policing. 20 iv Rec. ITU-T H.248.53 (03/2009) Page Appendix I Derivation of policer configuration values Examples 24 I.1 Introduction 24 I.2 Examples 24 Appendix II TISPAN traffic management packages 29 II
23、.1 Traffic management package . 29 Bibliography. 32 Rec. ITU-T H.248.53 (03/2009) 1 Recommendation ITU-T H.248.53 Gateway control protocol: Traffic management packages 1 Scope This Recommendation provides three H.248 packages in the area of traffic control. The Traffic management package defines pro
24、perties to control the traffic policing enforcement of the incoming flow and performing admission control in the media gateway (MG). Traffic shaping is out of scope of the Traffic management package version 2. The Traffic policing statistics package defines statistics for traffic policers (as a comp
25、lementary protocol element for the Traffic management package). The Packet Size package allows a media gateway controller (MGC) to signal additional packet size based conditions for the traffic policer. 1.1 Policy rules and policy enforcement behaviour The tman and/or pacs packages in this Recommend
26、ation may be applied for traffic policing. If applied, the MG provides a “traffic policer“ function. Any policy rule is comprised by a set of conditions and a set of actions (see e.g., usage of filter/policy rules in b-ITU-T H.248.43). In the case of traffic policing, the set of actions could includ
27、e: 1) transparent packet forwarding, 2) packet tagging (Note 1), or 3) packet dropping. NOTE 1 At the date of approval of this Recommendation, this function is not supported by ITU-T H.248.53. The number of packets that do not conform to the traffic policing parameters, as well as the number of pack
28、ets that are dropped due to such violations, may be recorded in H.248 statistics. The statistic being employed depends on the condition that was violated: Packets that do not conform to traffic parameters are recorded by statistics of the tmanr package (see clause 7.4). Packets that do not conform t
29、o packet size limitations are recorded by statistics of the pacs package (see clause 8.4). NOTE 2 These statistics may complement other statistics relating to traffic control, e.g., gm/dp (see b-ITU-T H.248.43). All statistics combined provide an overview of the various reasons leading to packets be
30、ing dropped. 1.2 Deriving policy enforcement point parameters The packages define generic traffic parameters, which may be used for specific traffic policers. The mapping between the H.248 signalling elements and specific, bearer-dependent policy enforcement point (PEP) policing algorithms is the su
31、bject of clause 9. Such an algorithm may consider tman properties only (i.e., traffic policer conditions on the bitrate and/or delay variation parameters only), the pacs properties only (i.e., traffic policer conditions on the PDU size parameters), or the properties of both packages. 2 References Th
32、e 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 references are subject to revision; users of thi
33、s 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 2 Rec. ITU-T H.248.53 (03/2009) currently valid ITU-T Recommendations is regularly published. The reference to a docume
34、nt within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.248.1 Recommendation ITU-T H.248.1 (2005), Gateway control protocol: version 3. ITU-T I.371 Recommendation ITU-T I.371 (2004), Traffic control and congestion control in B-ISDN. ITU-T I.
35、378 Recommendation ITU-T I.378 (2002), Traffic control and congestion control at the ATM Adaptation Layer type 2. ITU-T Y.1221 Recommendation ITU-T Y.1221 (2002), Traffic control and congestion control in IP-based networks. ITU-T Y.1291 Recommendation ITU-T Y.1291 (2004), An architectural framework
36、for support of Quality of Service in packet networks. ATM-F AF-TM-0121 ATM Forum (ATM-F) AF-TM-0121.000 (1999), Traffic Management Specification, Version 4.1. IETF RFC 2216 IETF RFC 2216 (1997), Network Element Service Specification Template. 3 Definitions 3.1 Terms defined elsewhere This Recommenda
37、tion uses the following terms defined elsewhere: 3.1.1 traffic policing ITU-T Y.1291: Traffic policing deals with the determination of whether the traffic being presented (i.e., the ingress H.248 stream in a H.248 ephemeral termination) is (on a hop-by-hop basis) compliant with pre-negotiated polici
38、es or contracts. Traffic policing is e.g., according to clause 7.1.3 of ITU-T Y.1221 (called “parameter control“) for IP, or clause 7.2.3 of ITU-T I.371 (called “Usage Parameter Control (UPC) and Network Parameter Control (NPC)“) for ATM. 3.1.2 traffic scheduling (queuing and scheduling) ITU-T Y.129
39、1: This mechanism controls which packets to select for transmission on an outgoing link. Scheduling is e.g., further detailed for IP in clause 7.1.6 of ITU-T Y.1221 on packet scheduling, for ATM in clause 7.2.6 of ITU-T I.371 on cell scheduling, or for AAL2 in clause 7.2.5 of ITU-T I.378 on packet s
40、cheduling. 3.1.3 traffic shaping ITU-T Y.1291: A mechanism that alters the traffic characteristics of the traffic leaving a node (i.e., the egress H.248 stream from an H.248 ephemeral termination). Traffic is shaped e.g., according to clause 7.1.5 of ITU-T Y.1221 for IP, clause 7.2.7 of ITU-T I.371
41、for ATM, or clause 7.2.4 of ITU-T I.378 for AAL2. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 policer: A functional or physical entity that enforces pre-negotiated policies or contracts. 3.2.2 shaper: A functional or physical entity that modifies t
42、he characteristics of data leaving the entity. 3.2.3 scheduler: A functional or physical entity that controls which packets to select for transmission. Rec. ITU-T H.248.53 (03/2009) 3 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AAL2 ATM Adaptation
43、Layer type 2 ATM Asynchronous Transfer Mode ATM-F ATM Forum B Bucket size of a token bucket Bp Bucket size of peak token bucket Bs Bucket size of sustainable token bucket CLP Cell Loss Priority CPS Common Part Sublayer GBRA Generic Byte Rate Algorithm GCRA Generic Cell Rate Algorithm GoS Grade of Se
44、rvice IETF Internet Engineering Task Force INI Inter-Network Interface IP Internet Protocol LD Local Descriptor M Maximum allowed packet size MG Media Gateway MGC Media Gateway Controller MPLS Multiprotocol Label Switching N Size (in byte) of an IP packet NPC Network Parameter Control OAM Operations
45、, Administration, Maintenance PCI Protocol Control Information PCR Peak Cell Rate PDP Policy Decision Point PDU Protocol Data Unit PEP Policy Enforcement Point QoS Quality of Service R Rate of a token bucket Rp Rate of peak token bucket Rs Rate of sustainable token bucket RTCP RTP Control Protocol R
46、TP Real-time Transport Protocol SCR Sustainable Cell Rate SDP Session Description Protocol 4 Rec. ITU-T H.248.53 (03/2009) TB Token Bucket UDPTL User Datagram Protocol Transport Layer Protocol UNI User Network Interface UPC Usage Parameter Control 5 Conventions The term packet is used in a broader s
47、ense in this Recommendation related to every bearer technology for packet-switched networks. A packet could be e.g., an IP datagram, an ATM cell, an AAL type 2 CPS-PDU, a MPLS packet, etc. 6 Traffic management package Package name: Traffic management package Package ID: tman (0x008d) Description: Th
48、is package allows traffic descriptors to be defined for a stream and allows policing to be explicitly enabled. Version 1 is defined for a single traffic flow per H.248 stream. Version 2 supports multiple traffic flows per H.248 stream. Version: 2 Extends: None. 6.1 Properties 6.1.1 Peak data rate Pr
49、operty name: Peak data rate Property ID: pdr (0x0001) Description: This property defines the peak data rate in bytes per second that is permitted for the stream. Type: Sub-list of Integer The type represents a list of one or more integer values. A list with one item only relates to traffic policing on a stream level, a list with multiple items relates to traffic policing on a flow level. Flow level policing is only applicable in case of multi-flow stream structures (see also clause 6.6). The s
