1、 International Telecommunication Union ITU-T H.248.69TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2009) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Communication procedures Gateway control protocol: Packages for interworking between MSRP and H.248 Recomm
2、endation ITU-T H.248.69 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
3、 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 for audiovisual and multim
4、edia 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 ap
5、plications 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 procedures H.560H.569 BROADBAN
6、D, TRIPLE-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 a
7、pplication 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.69 (03/2009) i Recommendation ITU-T H.248.69 Ga
8、teway control protocol: Packages for interworking between MSRP and H.248 Summary Recommendation ITU-T H.248.69 defines packages and procedures to enable the message session relay protocol (MSRP) to be sent and received on a H.248 controlled media gateway (MG). It further allows communication between
9、 an MGC and MG regarding the messaging policy, messaging statistics and message protocol connection state. Source Recommendation ITU-T H.248.69 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.69 (03/2009) FOREWORD The I
10、nternational 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
11、, operating 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 t
12、urn, 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. NO
13、TE In 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
14、e.g. 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
15、suggest 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
16、evidence, 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, whi
17、ch may be required 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 m
18、ay be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.248.69 (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 2 6
19、 Messaging streams 2 6.1 Session establishment. 2 6.2 Connection establishment. 2 6.3 Recording messages . 4 6.4 Playing messages 4 6.5 Deleting messages 4 6.6 Connection removal 4 7 Message conferencing 4 8 MSRP Statistics Package 4 8.1 Properties 5 8.2 Events . 5 8.3 Signals 11 8.4 Statistics 11 8
20、.5 Error codes 12 8.6 Procedures 12 9 MSRP Connection Status Package . 13 9.1 Properties 13 9.2 Events . 13 9.3 Signals 13 9.4 Statistics 14 9.5 Error codes 14 9.6 Procedures 14 10 Play Message Package 14 10.1 Properties 14 10.2 Events . 14 10.3 Signals 15 10.4 Statistics 17 10.5 Error codes 17 10.6
21、 Procedures 17 iv Rec. ITU-T H.248.69 (03/2009) Page 11 Delete Stored Message Package . 18 11.1 Properties 18 11.2 Events . 18 11.3 Signals 18 11.4 Statistics 19 11.5 Error Codes. 19 11.6 Procedures 19 12 Messaging Session Information Package . 19 12.1 Properties 19 12.2 Events . 20 12.3 Signals 20
22、12.4 Statistics 20 12.5 Error codes 20 12.6 Procedures 21 13 Messaging Filtering Package 21 13.1 Properties 21 13.2 Events . 22 13.3 Signals 24 13.4 Statistics 24 13.5 Error codes 24 13.6 Procedures 25 14 Stored Message Information Package 27 14.1 Properties 27 14.2 Events . 27 14.3 Signals 27 14.4
23、Statistics 30 14.5 Error codes 30 14.6 Procedures 30 15 Record Message Package . 30 15.1 Properties 30 15.2 Events . 30 15.3 Signals 31 15.4 Statistics 32 15.5 Error codes 32 15.6 Procedures 32 Rec. ITU-T H.248.69 (03/2009) 1 Recommendation ITU-T H.248.69 Gateway control protocol: Packages for inter
24、working between MSRP and H.248 1 Scope This Recommendation defines packages and procedures to enable the message session relay protocol (MSRP) to be sent and received on a H.248 controlled media gateway (MG). It further allows communication between an MGC and MG regarding the messaging policy, messa
25、ging statistics and message protocol connection state. It is assumed that the MG contains the MSRP switch functionality. NOTE The use of MSRP over TLS is for further study. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text,
26、 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 the possibility of applying the most recent edition of
27、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 a Recommendation. ITU-T H.248.1 Recommendation ITU-T H.
28、248.1 (2005), Gateway control protocol: Version 3. ITU-T H.248.7 Recommendation ITU-T H.248.7 (2004), Gateway control protocol: Generic announcement package. ITU-T H.248.9 Recommendation ITU-T H.248.9 (2005), Gateway control protocol: Advanced media server packages. ITU-T H.248.19 Recommendation ITU
29、-T H.248.19 (2004), Gateway control protocol: Decomposed multipoint control unit, audio, video and data conferencing packages. ITU-T H.248.43 Recommendation ITU-T H.248.43 (2008), Gateway control protocol: Packages for gate management and gate control. ITU-T H.248.47 Recommendation ITU-T H.248.47 (2
30、008), Gateway control protocol: Statistic conditional reporting package. IETF RFC 2822 IETF RFC 2822 (2001), Internet Message Format. IETF RFC 3339 IETF RFC 3339 (2002), Date and Time on the Internet: Timestamps. IETF RFC 3860 IETF RFC 3860 (2004), Common Profile for Instant Messaging (CPIM). IETF R
31、FC 3862 IETF RFC 3862 (2004), Common Presence and Instant Messaging (CPIM): Message format. IETF RFC 3986 IETF RFC 3986 (2005), Uniform Resource Identifier (URI): Generic Syntax. IETF RFC 4021 IETF RFC 4021 (2005), Registration of Mail and MIME Header Fields. IETF RFC 4975 IETF RFC 4975 (2007), The
32、Message Session Relay Protocol (MSRP). IETF RFC 4976 IETF RFC 4976 (2007), Relay Extensions for the Message Session Relay Protocol (MSRP). IETF RFC 5228 IETF RFC 5228 (2008), Sieve: An Email Filtering Language. 2 Rec. ITU-T H.248.69 (03/2009) 3 Definitions 3.1 Terms defined elsewhere This Recommenda
33、tion uses the following term defined elsewhere: 3.1.1 sieve IETF RFC 5228: An Email Filtering Language. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 message identity: Used between the MGC and MG in order to uniquely identify a particular message for
34、 H.248 procedural purposes. It may be the MSRP message identity but may be any valid identifier. 3.2.2 messaging stream: A H.248 stream that contains SDP indicating that the connection media type format is related to messaging. 3.2.3 MSRP switch: A media level entity that receives MSRP messages and
35、delivers them to the other conference participants. An MSRP switch has a similar role to a conference mixer with the exception that an MSRP switch does not actually “mix“ together different input media streams; it merely relays the messages between participants. 4 Abbreviations and acronyms This Rec
36、ommendation uses the following abbreviations and acronyms: MG Media Gateway MGC Media Gateway Controller MSRP Message Session Relay Protocol SDP Session Description Protocol 5 Conventions None. 6 Messaging streams 6.1 Session establishment The MGC is responsible for determining the filtering criteri
37、a, based on subscriber information and any local policy. The filtering is enforced in two ways. Firstly, through the modification of the session requests received from users before the session description/configuration is provided to an MG. Secondly, filtering may occur within the messaging session
38、with different actions being applied to messages received by a users termination. 6.2 Connection establishment In order for a MG to send and receive messages, a H.248 stream is created on a Termination in addition to any other streams, i.e., audio/video streams. The MCG shall assign a new StreamID f
39、or the stream. The characteristics of sent messaging may be set in the Local Descriptor and the characteristics of received messaging may be set in the Remote Descriptor. The addressing information for the messaging stream may be set via a session description protocol (SDP) connection “c=“ line. Rec
40、. ITU-T H.248.69 (03/2009) 3 The MGC shall indicate that the stream is for messaging through the use of a SDP media “m=“ line. See clause 8.1 of IETF RFC 4975 for details on how to set the components of this line. The MGC may indicate or request the allowed media types and formats through the use of
41、 the SDP “accept-types“ attribute (see clause 8.6 of IETF RFC 4975). Messages received with message media types and formats not included in attribute are discarded by the MG. The MGC may indicate or request the maximum message size through the SDP “max-size“ attribute (see clause 8.6 of IETF RFC 497
42、5). The MGC may also set message level filters in order to request the MG to perform certain actions based on different message characteristics. Session level filtering (i.e., that is described in SDP) related to message media types, media formats and maximum message size is applied to messages ente
43、ring the termination from an MG external direction. Message level filtering is typically applied to messages received on a termination from other terminations in the associated context. Additional characteristics of the messaging session may be set via the “Message Session Information“ (msi) package
44、 (see clause 12). In addition to providing information regarding the allowed messages, the MGC may set quotas for the sending and reception of messages on a termination/stream. See clause 8.6.1 for more details. Once the message characteristics have been negotiated with the end user (see IETF RFC 49
45、75 for an example on how this is achieved) and the SDP related to the message stream has been set, then the MG shall wait for a MSRP connection request from the peer. If the MGC sends the “Establish MSRP Connection“ (msrpstat/conn) signal, then the MG shall be responsible for initiating the MSRP con
46、nection. Once the connection is established, the MG shall then be responsible for MSRP signalling according to IETF RFC 4975. NOTE Clause 4 of IETF RFC 4975 indicates that MSRP nodes may support multiple sessions over a single MSRP connection. In this case, multiple H.248 Streams are used for each s
47、ession; however, the connection information will remain the same (see clause 8.1 of IETF RFC 4975). The MG shall then relay the MSRP messages between terminations containing the same StreamID. If a message is relayed to a termination that has message level filtering applied to it, the filter shall b
48、e applied before sending the message to the user represented by the termination. See clause 13 for more information. When sending MSRP “SEND Requests“, the MG should follow the chunk size recommendations in clause 7.1.1 of IETF RFC 4975; however the chunk size may be altered via provisioning. Clause
49、 8.9 of IETF RFC 4975 describes the relationship between the SDP Direction Attribute and MSRP. ITU-T H.248.1 contains the StreamMode property in the Local Control descriptor. The StreamMode property shall take precedence over the SDP Direction Attribute. The effect of the StreamMode property values shall be the same as described in clause 8.9 of IETF RFC 4975. Clause 5.4 of IETF RFC 4975 describes the MSRP Connection model. In order for the MGC to be aware of the status of the connection, it should se
