1、 International Telecommunication Union ITU-T H.248.65TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2009) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Communication procedures Gateway control protocol: Support of the resource reservation protocol Recommenda
2、tion ITU-T H.248.65 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 pro
3、cedures 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 for audiovisual and multimedia
4、 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 multimedia collaboration applic
5、ations 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.559Mobile multimedia collaboration inter-working procedures H.560H.569 BROADBAND, TR
6、IPLE-PLAY AND ADVANCED 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 applic
7、ation event handling 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.65 (03/2009) i Recommendation ITU-T H.248.65 Gateway
8、 control protocol: Support of the resource reservation protocol Summary Recommendation ITU-T H.248.65 provides an ITU-T H.248 package for the support of the resource reservation protocol (RSVP). The protocol capabilities are tightly coupled with the pull mode defined in Recommendation ITU-T H.248.55
9、. The RSVP extension package complements the generic pull mode package by providing additional capabilities for the specific path-coupled QoS/resource control protocol RSVP. This package allows the ITU-T H.248 entities to make the resource reservation, i.e., set up the bearer path with the desired Q
10、oS. Based on this package, the MGC and the MG are able to initiate/terminate the RSVP messages. Source Recommendation ITU-T H.248.65 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.65 (03/2009) FOREWORD The Internationa
11、l Telecommunication 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
12、 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, produc
13、e 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 this
14、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. intero
15、perability 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 suggest tha
16、t 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 evidence, v
17、alidity 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 may be r
18、equired to implement 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 repro
19、duced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.248.65 (03/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 RSVP exten
20、sion package 3 6.1 Properties 3 6.2 Events . 3 6.3 Signals 11 6.4 Statistics 15 6.5 Error codes 15 6.6 Procedures 15 Rec. ITU-T H.248.65 (03/2009) 1 Recommendation ITU-T H.248.65 Gateway control protocol: Support of the resource reservation protocol 1 Scope ITU-T H.248.55 provides a generic package
21、(as base package) for pull mode support. Such a capability is, for instance, required for bearer/media path-coupled QoS control protocols, like the resource reservation protocol (RSVP) according to IETF RFC 2205. This extension package describes the RSVP-specific procedures and enables the ITU-T H.2
22、48 entities to support an RSVP mechanism, which includes the initiation/termination of RSVP messages. This package provides a means of resource reservation, by which the MGC and the MG are able to set up the bearer path with the desired QoS. IETF RFC 2205 defines several RSVP message types. In addit
23、ion to the two fundamental types: (Path and Resv), there are also teardown messages (PathTear and ResvTear), error messages (PathErr and ResvErr) and a confirm message (ResvConf). This Recommendation introduces a generic method for the MGC and the MG to deal with these above messages to support RSVP
24、. The ITU-T H.248 media gateway acts as an RSVP-aware policy enforcement point (PEP) when processing RSVP messages. The ITU-T H.248 MGC acts as an RSVP-aware policy decision point (PDP), it is the MGC that determines when to send the RSVP messages. On reception of incoming RSVP messages, the MG repo
25、rts the related events to the MGC for its resource policy decision. As such, the packages in this Recommendation allow the support of the functionality outlined by the application/RSVP interface (clause 3.11.1 of IETF RFC 2205). 2 References The following ITU-T Recommendations and other references c
26、ontain 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 this Recommendation are therefore encouraged to investigate
27、 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 document within this Recommendation does not give it, as a stand-alone document, the status of
28、 a Recommendation. ITU-T H.248.1 Recommendation ITU-T H.248.1 (2005), Gateway control protocol: Version 3; Amendment 1 (2008). ITU-T H.248.55 Recommendation ITU-T H.248.55 (2008), Gateway control protocol: Generic pull mode package. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2006), Resource and admis
29、sion control functions in Next Generation Networks. IETF RFC 2205 IETF RFC 2205 (1997), Resource ReSerVation Protocol (RSVP) Version 1 Functional Specification. IETF RFC 2210 IETF RFC 2210 (1997), The Use of RSVP with IETF Integrated Services. IETF RFC 2750 IETF RFC 2750 (2000), RSVP Extensions for
30、Policy Control. IETF RFC 3182 IETF RFC 3182 (2001), Identity Representation for RSVP. IETF RFC 3520 IETF RFC 3520 (2003), Session Authorization Policy Element. 2 Rec. ITU-T H.248.65 (03/2009) IETF RFC 3521 IETF RFC 3521 (2003), Framework for Session Set-up with Media Authorization. 3 Definitions 3.1
31、 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 ADSPEC: An object of a RSVP message, defined in Appendix A “Object Definitions“ of IETF RFC 2205, “Carries OPWA data, in a Path message“; see also its detailed format in clause 3.3 “RSVP ADSPEC Object“ of
32、IETF RFC 2210. 3.1.2 ERROR_SPEC: An object of a RSVP message, defined in Appendix A of IETF RFC 2205, “Specifies an error in a PathErr, ResvErr, or a confirmation in a ResvConf message“. 3.1.3 FILTER_SPEC: An object of a RSVP message, defined in Appendix A of IETF RFC 2205, “Defines a subset of sess
33、ion data packets that should receive the desired QoS (specified by a FLOWSPEC object), in a Resv message“. 3.1.4 POLICY_DATA: An object of a RSVP message, defined in Appendix A of IETF RFC 2205, “Carries information that will allow a local policy module to decide whether an associated reservation is
34、 administratively permitted. It may appear in Path, Resv, PathErr, or ResvErr message“. 3.1.5 FLOWSPEC: An object of a RSVP message, defined in Appendix A of IETF RFC 2205, “Defines a desired QoS, in a Resv message“; see also its detailed format in clause 3.2 “RSVP FLOWSPEC Object“ of IETF RFC 2210.
35、 3.1.6 SENDER_TSPEC: An object of a RSVP message, defined in Appendix A of IETF RFC 2205, “Defines the traffic characteristics of a senders data flow“; see also its detailed format in clause 3.1 “RSVP SENDER_TSPEC Object“ of IETF RFC 2210. 3.1.7 SESSION: An object of a RSVP message, defined in Appen
36、dix A of IETF RFC 2205, “Contains the IP destination address (DestAddress), the IP protocol id, and some form of generalized destination port, to define a specific session for the other objects that follow. It is required in every RSVP message“. 3.2 Terms defined in this Recommendation None. 4 Abbre
37、viations and acronyms This Recommendation uses the following abbreviations: IP Internet Protocol MG Media Gateway MGC Media Gateway Controller PDP Policy Decision Point PEP Policy Enforcement Point QoS Quality of Service RSVP Resource ReSerVation Protocol SIP Session Initiation Protocol Rec. ITU-T H
38、.248.65 (03/2009) 3 TTL Time to Live 5 Conventions None. 6 RSVP extension package Package Name: RSVP extension package Package ID: rsvp (0x00d2) Description: This package complements the generic pull mode package by providing additional capabilities for the specific path-coupled QoS/resource control
39、 protocol RSVP IETF RFC 2205. This package allows the ITU-T H.248 entities to make the resource reservation, i.e., set up the bearer path with the desired QoS. Based on this package, the MGC and the MG are able to initiate/terminate the RSVP messages. Version: 1 Extends: Generic pull mode package (p
40、lm) version 1 ITU-T H.248.55. 6.1 Properties None. 6.2 Events 6.2.1 Path Received Event Name: Path Received Event ID: pathr (0x0004) Description: This event enables the MGC to be notified when the first RSVP Path message is received by the MG, or if the path state is changed by later Path messages.
41、The parameters are related to RSVP information elements contained in the received message. This event shall be applied to the Root termination or to ephemeral terminations only. 6.2.1.1 EventDescriptor Parameters None. 6.2.1.2 ObservedEventsDescriptor Parameters 6.2.1.2.1 Session ID Parameter Name:
42、Session ID Parameter ID: session (0x0001) Description: This parameter relates to RSVP object “SESSION“. Type: Octet String Optional: No Possible values: A sequence of octets Default: None 4 Rec. ITU-T H.248.65 (03/2009) 6.2.1.2.2 Sender TSpec Parameter Name: Sender TSpec Parameter ID: stspec (0x0002
43、) Description: This parameter relates to RSVP object “SENDER_TSPEC“. Type: Octet String Optional: Yes Possible values: A sequence of octets Default: None 6.2.1.2.3 Ad Spec Parameter Name: Ad Spec Parameter ID: adspec (0x0003) Description: This parameter relates to RSVP object “ADSPEC“. Type: Octet S
44、tring Optional: Yes Possible values: A sequence of octets Default: None 6.2.1.2.4 Policy Data Parameter Name: Policy Data Parameter ID: policy (0x0004) Description: This parameter relates to RSVP object “POLICY_DATA“. Type: Octet String Optional: Yes Possible values: A sequence of octets Default: No
45、ne 6.2.2 Resv Received Event Name: Resv Received Event ID: resvr (0x0005) Description: This event enables the MGC to be notified when the first RSVP Resv message is received by the MG, or if the reservation state is changed by later Resv messages. The parameters are related to RSVP information eleme
46、nts contained in the received message. This event shall be applied to the Root termination or to ephemeral terminations only. 6.2.2.1 EventDescriptor Parameters None. Rec. ITU-T H.248.65 (03/2009) 5 6.2.2.2 ObservedEventsDescriptor Parameters 6.2.2.2.1 Session ID Parameter Name: Session ID Parameter
47、 ID: session (0x0001) Description: This parameter relates to RSVP object “SESSION“. Type: Octet String Optional: No Possible values: A sequence of octets Default: None 6.2.2.2.2 Style Parameter Name: Style Parameter ID: style (0x0002) Description: This parameter represents the reservation style. Typ
48、e: Enumeration Optional: No Possible values: “FF“ (0x0001) Fixed-Filter “SE“ (0x0002) Shared-Explicit “WF“ (0x0003) Wildcard-Filter Default: None 6.2.2.2.3 Flow Spec Parameter Name: Flow Spec Parameter ID: flowspec (0x0003) Description: This parameter relates to RSVP object “FLOWSPEC“. It is reporte
49、d if contained in the received message. Type: Octet String Optional: Yes Possible values: A sequence of octets Default: None 6.2.2.2.4 Filter Spec Parameter Name: Filter Spec Parameter ID: filterspec (0x0004) Description: This parameter relates to RSVP object “FILTER_SPEC“. It is reported if contained in the received message. Type: Octet String Optional: Yes Possible values: A sequence of octets Default: None 6 Rec. ITU-T H.248.65 (03/2009) 6.2.2.2.5 Pol
