Foreword
This document is drafted in accordance with the provisions of GB/T 1.1-2020 "Standardization Work Guidelines Part 1 Structure and Drafting Rules for Standardization Documents".
This document replaces GB/T 28181-2016 "Public security video surveillance networking system information transmission, exchange, control technical requirements",Compared with GB/T 28181-2016, in addition to structural adjustments and editorial changes, the main technical changes are as follows.
Changed the scope of the standard (see Chapter 1 of the 2016 version of Chapter 1).
Deleted "networking system information", "digital access", "analog access", "analog-digital hybrid monitoring system" The terms and definitions of "digital monitoring system", "monitoring point" and "monitoring center" have been changed, and the term "SIP monitoring domain The terms and definitions of "SIP monitoring domain", "non-SIP monitoring city", "cascade" and "interconnection" are changed.
Added the acronym "PTZ" (see 3.2). Changed "SIP monitoring domain interconnection structure diagram" (see 4.1.1, 2016 version of 4.1.1) Changed "networking system communication protocol structure diagram", media flow channel added H, 265, G, 7221AAC (see 4.3.1, 2016
4.3.1 of the 2016 version). Added RTP time collection requirement for media stream data transmission (see 4.3.6). -Changed network transmission bandwidth requirements video ton rate requirements (see 5,4,5.6, 5.45.6 of 2016 version) Added support for H.265, AAC (see 6.2A.2.1.9, Appendix C Appendix F Appendix G) Changed references to SDP protocols (see 6.4 Appendix G Appendix F of 2016 version 64) Changed data exchange with other systems (see 6.9 Appendix A Appendix G of the 2016 Edition 69) Changed signaling character set requirements (see 6.10, Appendix 610 of the 2016 Edition)
Changed control requirements (see Chapter 7, 2016 Edition of 7).
Changed transmission, switching, and control security requirements (see Chapter 8, 2016 Edition of Chapter 8).
Changed basic requirements for registration and cancellation (see 9.1,1, 91.1 of the 2016 edition).
Added registration redirection (see 9.1.2.3).
Changed basic requirements and data types for device control and device configuration (see 9,3,1, A.2,1A.2,3, 1A,2.3.2) Added watchdog bit information query, cruise track list query, cruise track query, PTZ precise status query, memory card status query and answer command (see 9.5.3, A.2.4.10~A.2.4.14, A,2. 6.12~A.2.6.16). Added PTZ precision position change event subscription and notification (see 9.111, 9.11.2A2.13A2.6.15). -Added equipment software upgrade, image capture signaling process and protocol interface (see 9.139.14). Changed part of Appendix A. Added some data type definitions (see A.2.1, 2016 version of A.2.1) added some control commands and parameters (see A.2.3, 2016 version of A.2,3); added some query commands and parameters (see A.2.4, 2016 version of A.2.4): modified some notification commands and parameters (see A.2.5, 2016 version of A2.5 ); added modified some answer commands and parameters (see A.2.6.201 version of A.2.6); partially modified PTZ command examples (see A3.22016 version of A.3.2); added networked system extended applications (see A.4).
Changed Appendix B, added media playback command description (see Appendix B of the 2016 version)
Changed Appendix C to add H.265 package description (see Appendix C 2016 Edition Appendix C).
Changed Appendix D for TCP protocol-based video and audio media transmission requirements (see Appendix L of Appendix D 2016 Edition).
1 Scope
This document specifies the interconnection structure of the public security video surveillance system (hereinafter referred to as the "networking system"), the basic requirements for transmission, exchange, control and security requirements, as well as the control, transmission process and protocol interface and other technical requirements.
This document applies to the public security video surveillance networking system program design, system testing, acceptance and related equipment development and production. Other video surveillance networking systems can refer to the implementation
2 normative reference documents
The following documents constitute the essential provisions of this document through the normative references in the text. Among them, note the date of the referenced documents, only the date of the corresponding version applies to this document; do not note the date of the referenced documents, the latest version (including all the revision of the list) applies to this document.
GB/T 4754 National economy industry classification
GB/T 10114-2003 Rules for the preparation of administrative division codes below the county level
GB18030 Information technology Chinese coding character set
GB/T 25724 Public security video surveillance digital video and audio coding and decoding technical requirements
GB35114 Public security video surveillance networking information security technical requirements
GA/T 380 National public security organs code compilation rules
ISO/IEC 13818-1:2019 General coding of information technology motion picture and accompanying audio information Part 1: System
ISO/IEC 14496-2:2004 Coding of information technology audiovisual objects Part 2;Video
ISO/IEC 14496-2:2004/Amd2:2005 Coding of audiovisual objects for information technology part 2 video revision 2 new levels for simple grades
ISO/IEC 14496-3:2019 Coding of audiovisual objects for information technology Part 3: Audio
ISO/IEC 14496-4 Information technology audiovisual object codes Part 4: Conformance testing
ISO/IEC 14496-42004/AMD102005 Information technology audiovisual object codes Part 4:Conformance testing Revision 10
ISO/IEC 14496-5:2001 Coding of information technology audiovisual objects part 5 reference software
IETFRFC3261 Session Initiation Protocol
IETFRFC3550 Real-time transmission protocol
IETFRFC3551 RTP Description for Audio and Video Conferencing Minimum Control
IETFRFC3725 Current Best Implementation of Third Party Call Control (3PCC) in Session Initiation Protocol (SIP)
IETFRFC3984 RTP load format for H.264 video
IETFRFC4566:2006 Session Description Protocol
IETFRFC4571 Connection Oriented Transport Packet Rai Real Time Transport Protocol (RTP) and Real Time Transport Control Protocol (RTCP)
IETFRFC6665 Session Initiation Protocol (SIP) Event Notification
IETFRFC7798 High Efficiency Video Coding (HEVC) RTP payload format
3 Terms and Definitions, Abbreviations
3.1 Terminology and Definitions
The following terms and definitions apply to this document.
4 Interconnection Structure
4.1 SIP surveillance domain interconnection structure
4.1.1 Overview
The interconnection structure of SIP monitoring domains for information transmission, exchange and control of networked systems is shown in Figure 1. Figure 1 describes the connection relationship between functional entities in a single SIP monitoring domain, and between different SIP monitoring domains in two cases. The channel interconnection protocol between functional entities is divided into two types: session channel protocol and media stream (this document mainly refers to the video/audio amount) channel protocol. The session channel protocol is described in 4.3.2~4,3.4, and the media stream channel protocol is described in 4.3.5 and 4.3.
5 Transmission requirements
5.1 Network transmission protocol requirements
Network system network layer should support IP protocols, the transport layer should support TCP and UDP protocols 5.2 Media transmission protocol requirements
Video and audio streams should support RTP/RTCP protocols when transmitted on IP-based networks:The data encapsulation format of video and audio streams should meet the requirements of 4.3.6.
The video and audio stream should be extended to support TCP protocol when transmitted on IP-based networks protocol should be in accordance with the provisions of Appendix D
6 exchange requirements
6.1 Uniform encoding rules
6.1.1I unified coding rules
Networking system should be front-end equipment, monitoring center equipment, user terminal ID for unified coding, the code has global uniqueness. The code should be used in accordance with the coding rules specified in Appendix E E.1 (20 decimal digit character code). Communication between the management platform of the networked system, the management platform and other systems should be used to identify the equipment and users of the networked system with the unified code specified in this chapter.
7 control requirements
7.1 Registration to meet the following requirements .
a) should support the device or system into the networked system when the SIP server for registration of the work mode device or system registration should be extended to support the carrying of protocol version identification, protocol version identification should be consistent with the provisions of Appendix b)
c) If the device or system registration is not successful, it is appropriate to delay a certain random time after re-registration
d It is desirable to implement the registration redirection function to dynamically assign the access server to the device in order to cope with the load balancing and fault migration on the server side when the large-scale device is accessed.
e device or system registration of the session control process see 9.1.
8 transmission, switching and control security requirements
8.1 Device authentication
Device identity authentication meets the following requirements.
a) should support the unified coding of all devices in the access system, device coding specification see the provisions of 6.1; b access device authentication should use different authentication methods according to different circumstances. For non-standard SIP devices, it is appropriate to authenticate through the gateway.
Should support the use of password-based digital digest authentication for device authentication, the authentication process is described in Chapter 22 of 9.1 and IETFc) RFC3261.
d) It is desirable to support the authentication method of digital certificate.
8.2 Data encryption
It is desirable to use IPSec in the network layer or TLS in the transport layer to achieve hop-by-hop security encryption for SIP messages
9 Control, transmission process and protocol interface
9.1 Registration and cancellation
9.1.1 Basic requirements
Registration and deregistration meet the following basic requirements.
a) SIP clients, gateway SIP devices, networking systems and other SIP agents (SIPUA) shall use the REGISTER method defined in IETFRFC3261 for registration and deregistration. Registration and cancellation should be authenticated, the authentication method should support the digital digest authentication method, high security level is appropriate to support the authentication method of digital certificate.
b) b) After successful registration, the SIP proxy shall refresh the registration to the registration server before the registration expiration time comes, and the dramatic new registration message process shall be consistent with the process description of 9.1.2.1 and follow the provisions of IETFRFC3261 for refreshing the registration. If the registration fails, the SIP agent shall continue to initiate the registration process after a certain interval of time, and the interval of time between the last registration shall be adjustable and shall not be shorter than 605 under normal circumstances.
d) system device registration expiration time should be configurable, the default value is 86400s1 days) should send a refresh registration message before the registration expiration time arrives to reserve appropriate refresh registration processing time for the SIP server, the registration expiration time should not be shorter than 3600SIP agent registration success is considered SIP server for online state, registration failure is considered SIP server for offline state eSIP server is considered online after successful registration of SIP proxy SP proxy registration expiration is considered offline.
D For SIP proxy inside a router with Network Address Translation (NAT) enabled, it is appropriate to support the use of TCP to initiate SIP registration and keep the TCP connection open after successful registration, and the SP proxy and server send all requests and responses to SIP messages such as heartbeat refresh registration, video and audio on-demand, and control in the TCP channel. If the TCP channel is disconnected, the SIP proxy is considered to be abnormally disconnected and the SIP proxy shall re-initiate the registration after a certain time interval according to the aforementioned requirements.
9.1.2 Signaling Flow
9.1.2.1 Basic Registration
The basic registration means that the digital digest-based challenge-response security technique specified in IETFRFC3261 is used for registration, and the specific registration flow shall be in accordance with Figure 8.
Appendix A (normative) Monitoring and Alarm Networking System Control Description Protocol (MANSCDP) command set
Appendix B (normative) Monitoring Alarm Networking System Real-Time Streaming Protocol (MANSRTSP) command set
Appendix C (normative) RTP-based video and audio data encapsulation
Appendix D (normative) TCP protocol-based video and audio media transmission
Appendix E (normative) Unified Encoding Rules
Appendix F (normative) Technical requirements for video and audio encoding/decoding
Appendix G (normative) SDP definition
Appendix H (informative) technical requirements for camera and platform path selection
Appendix I (normative) protocol version identification
Appendix J (normative) directory query response instructions
Appendix K (informative) Media Streaming Preservation Mechanism
Appendix L (normative) Subject header city definition
Appendix M (normative) Multi-Response Messaging
Appendix N (normative) Inter-city Directory Subscription Notification
Appendix O (normative) Camera Capture Part Type Codes
Bibliography
