1、 International Telecommunication Union ITU-T H.627TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2012) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSBroadband, triple-play and advanced multimedia services Advanced multimedia services and applicationsSignalling and protocols for visual surveillanc
2、e Recommendation ITU-T H.627 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 Communic
3、ation 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 m
4、ultimedia 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 collaborati
5、on 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 procedures H.560H.569 BRO
6、ADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629Ubiquitous sensor network applications and Internet of Things H.640H.649 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects
7、H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application 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 Digital Signage H.780H.789 For further details, please refe
8、r to the list of ITU-T Recommendations. Rec. ITU-T H.627 (06/2012) i Recommendation ITU-T H.627 Signalling and protocols for visual surveillance Summary Recommendation ITU-T H.627 describes the detailed specifications of reference points, signalling and control methods, and overall protocols of a vi
9、sual surveillance system, based on the requirements described in Recommendation ITU-T F.743 and the functional architecture described in Recommendation ITU-T H.626. For the reference points between different functional entities relevant protocols are identified, such as protocols between the premise
10、s unit (PU) and service platform, the customer unit (CU) and service platform, and the PU and CU. For reference points in the same functional entity, the internal signalling is described, including the signalling flow or information elements relevant for each reference point, such as the signalling
11、for the service control flow, and the media distribution flow in the service platform. Message formats and message text which relate to existing protocols (such as SIP, RTP, RTSP, HTTP) used in this Recommendation, are also provided. History Edition Recommendation Approval Study Group 1.0 ITU-T H.62
12、7 2012-06-29 16 Keywords Control protocols, signalling, visual surveillance. ii Rec. ITU-T H.627 (06/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU
13、Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardizat
14、ion Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, 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 techno
15、logy which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Complianc
16、e with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, 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 obliga
17、tory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not 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
18、 of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of t
19、he date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which 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 c
20、onsult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2013 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.627 (06/2012) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definit
21、ions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations 2 5 Introduction to VS functional architecture and related reference points 2 6 Signalling flows and relevant protocol exchanges . 3 6.1 Service management . 3 6.2 Alarm and linkage action 6 6.3 Video/a
22、udio acquisition 6 6.4 Instant image snapshot . 8 6.5 Recording and playback . 9 6.6 Voice (audio) communication 14 6.7 Far-end camera control . 17 Rec. ITU-T H.627 (06/2012) 1 Recommendation ITU-T H.627 Signalling and protocols for visual surveillance 1 Scope As defined in ITU-T H.626, the visual s
23、urveillance service is a telecommunication service focusing on video (but also including audio) application technology, which is used to remotely capture multimedia (such as audio, video, image and alarm signals) and present them to the end user in a user-friendly manner, based on a managed broadban
24、d network with ensured quality, security and reliability. The objective of this document is to describe the detailed specifications of reference points, signalling and control methods, and overall protocols of a visual surveillance system based on the functional architecture defined in ITU-T H.626.
25、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 references are subject to revisio
26、n; 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 document within this Re
27、commendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T F.743 Recommendation ITU-T F.743 (2009), Requirements and service description for visual surveillance. ITU-T H.626 Recommendation ITU-T H.626 (2011), Architectural requirements for visual surveillance. IT
28、U-T Y.101 Recommendation ITU-T Y.101 (2000), Global Information Infrastructure terminology: Terms and definitions. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2010), Functional requirements and architecture of next generation networks. IETF RFC 2326 IETF RFC 2326 (1998), Real Time Streaming Protocol (
29、RTSP). IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 3261 IETF RFC 3261 (2002), SIP: Session Initiation Protocol. IETF RFC 3550 IETF RFC 3550 (2003), RTP: A Transport Protocol for Real-Time Applications. 3 Definitions 3.1 Terms defined elsewhere This Recommendati
30、on uses the following terms defined elsewhere: 3.1.1 interface ITU-T Y.101: A shared boundary between two functional units. NOTE 1 An interface is defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges and other characteristics, as appropriate. 2
31、Rec. ITU-T H.627 (06/2012) 3.1.2 reference point ITU-T Y.2012: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. NOTE 2 A reference point may correspond to one or more physi
32、cal interfaces between pieces of equipment. 3.2 Terms defined in this Recommendation None. 4 Abbreviations This Recommendation uses the following abbreviations: CMU Centre Management Unit CPU Central Processing Unit CU Customer Unit FECC Far-End Camera Control HTTP Hypertext Transfer Protocol ID Ide
33、ntity IIS Instant Image Snapshot MDU Media Distribution Unit MSU Media Storage Unit PTZ Pan/Tilt/Zoom PU Premises Unit RTCP Real-time Transport Control Protocol RTP Real-time Transport Protocol RTSP Real-time Streaming Protocol SCU Service Control Unit SDP Session Description Protocol SIP Session In
34、itiation Protocol SOAP Simple Object Access Protocol VS Visual Surveillance XML Extensible Markup Language 5 Introduction to VS functional architecture and related reference points ITU-T H.626 describes the functional architecture framework of visual surveillance (VS), illustrated in Figure 5-1, and
35、 introduces the reference points of VS architecture. The present Recommendation provides a more detailed description of these reference points and introduces some new reference points. Rec. ITU-T H.627 (06/2012) 3 H.627(12)_F5-1PUPdPcPcCdMcMDU MSUDsMpPsCmCsSmScSCUSdSdDmCMUMcMedia ControlManagementCU
36、Pm DmDsCdFigure 5-1 Decomposition of VS 6 Signalling flows and relevant protocol exchanges The following are illustrative items: the SIP message format should comply with the definition in IETF RFC 3261 the RTSP message format should comply with the definition in IETF RFC 2326 the HTTP message forma
37、t should comply with HTTP1.1 defined in IETF RFC 2616 the RTP/RTCP signalling and message refer to IETF RFC 3550. 6.1 Service management 6.1.1 PU registration PU registration uses the SIP protocol IETF RFC 3261. The request message-header uses the standard REGISTER method, and the CMU returns a resp
38、onse with a “401 unauthorized“ or “200 OK“ message. The related signalling flows are shown in Figure 6-1 and the steps are described underneath. PU CMU1. Register2. 401 Unauthorized3. Register4. 200 OKH.627(12)_F6-1Figure 6-1 PU registration 4 Rec. ITU-T H.627 (06/2012) Step 1: The PU uses the SIP R
39、EGISTER method to implement registration to the CMU, the message header (SIP header) contains “From, To, Contract“ fields to show the addresses of the PU and CMU. Step 2: The CMU returns a response with an SIP 401 message and requests the PU to send the authentication information. Step 3: The PU add
40、s the authentication information and re-sends an SIP REGISTER message to the CMU. Step 4: The CMU returns an SIP 200 OK message or other error code to finish the registration. 6.1.2 CU registration CU registration has the same procedural flow and uses the same protocols as PU registration, see Figur
41、e 6-2. CU CMU1. Register2. 401 Unauthorized3. Register4. 200 OKH.627(12)_F6-2Figure 6-2 CU registration 6.1.3 Obtaining the PU list As illustrated in Figure 6-3, after the CU and PU have been registered to the service platform, the CU needs to request from the SCU in the service platform, the PU lis
42、t information, in order to provide that list to the end users. The PU list information includes user information, static list information and dynamic list information of PUs. The following steps describe the process. H.627(12)_F6-3CU SCU CMU1. HTTP: GET (UserInfo)4. HTTP: 200 OK5. HTTP: GET (StaticL
43、istInfo)6. HTTP: 200 OK7. HTTP: GET (DynamicListInfo)8. HTTP: 200 OK9. SIP: MESSAGE10. SIP: 200 OK2. Authentication3. ResponseFigure 6-3 Obtaining the PU list Rec. ITU-T H.627 (06/2012) 5 Step 1: The CU sends an HTTP GET message with the Request-URI “UserInfo“ to the SCU to request user information.
44、 Steps 2, 3: The SCU needs to check the authentication information from the CMU. The CMU returns a response to the SCU. Step 4: The SCU returns an HTTP 200 OK message with the user information to the CU. Steps 5, 6: The CU sends an HTTP GET message with the Request-URI “StaticListInfo“ to the SCU to
45、 request the static PU list information. The SCU returns an HTTP 200 OK message with the static PU list information to the CU. Steps 7, 8: The CU sends an HTTP GET message with the Request-URI “DynamicListInfo“ to the SCU to request the dynamic PU list information. The SCU needs to get the latest st
46、atus of the PUs and returns an HTTP 200 OK message as a response to the CU. Steps 9, 10: The SCU sends an SIP MESSAGE with the updated PU list information to the CU when the SCU gets the relevant status changes event. 6.1.4 PU-related parameters query The related parameters of PUs include: 1) Serial
47、 port parameters, including serial port numbers, baud rate, data bit rate, parity bit, flow control parameters, PTZ decoder type, PTZ decoder address, etc. 2) Input parameters for switching, including channel number, channel state for input and output, etc. 3) Clock parameter in the PU, used by the
48、PU for clock drift correction. 4) Video parameters, including video channel ID, encoding mode, encoding type, picture quality level, bit rate, frame rate, video resolution, I-frame interval, etc. 5) Video display parameters, including contrast ratio, brightness, chromaticity, saturation. 6) Subtitle
49、s parameters, including position of text (bitmap X/Y), text content, position of time stamp, etc. 7) Alarm configuration parameters, including alarm type, alarm level, parameters for instant image snapshot, etc. 8) PTZ control parameters, including PTZ ID, preset point index, preset point name, track number, PTZ velocity, etc. 9) PU status parameters, including CPU utilization, channel status, alarm status, etc. 10) PU logs parameters, including type of log, query method, query time, etc.
