Skip to product information
1 of 12

PayPal, credit cards. Download editable-PDF and invoice in 1 second!

GB/T 28181-2022 English PDF (GBT28181-2022)

GB/T 28181-2022 English PDF (GBT28181-2022)

Regular price $2,330.00 USD
Regular price Sale price $2,330.00 USD
Sale Sold out
Shipping calculated at checkout.
Quotation: In 1-minute, 24-hr self-service. Click here GB/T 28181-2022 to get it for Purchase Approval, Bank TT...

GB/T 28181-2022: Technical requirements for information transmission,switch and control in video surveillance networking system for public security

This document specifies the peer-to-peer networking structure of the video surveillance networking system for public security (hereinafter referred to as and quot;surveillance networking system and quot;), the basic requirements and security requirements for transmission, exchange, and control, as well as the technical requirements for control, transmission process, and protocol interface. This document is applicable to the scheme design, system testing, acceptance and related device development and production of the video surveillance networking system for public security. Other video surveillance networking systems can be implemented by using this document as reference.
GB/T 28181-2022
GB
NATIONAL STANDARD OF THE
PEOPLE REPUBLIC OF CHINA
ICS 13.310
CCS A 91
Replacing GB/T 28181-2016
Technical requirements for information transmission, switch
and control in video surveillance networking system for
public security
ISSUED ON: DECEMBER 30, 2022
IMPLEMENTED ON: JULY 01, 2023
Issued by: State Administration for Market Regulation;
Standardization Administration of the People's Republic of China.
Table of Contents
Foreword ... 5
1 Scope ... 9
2 Normative references ... 9
3 Terms and definitions, abbreviations ... 11
3.1 Terms and definitions ... 11
3.2 Abbreviations ... 14
4 Peer-to-peer networking structure ... 15
4.1 Peer-to-peer networking structure of SIP surveillance realm ... 15
4.2 Peer-to-peer networking structure between SIP surveillance realm and non-SIP surveillance realm ... 18
4.3 Communication protocol structure of networking system ... 20
5 Transmission requirements ... 22
5.1 Requirements for network transmission protocol ... 22
5.2 Requirements for media transfer protocol ... 22
5.3 Information transmission delay time ... 22
5.4 Network transmission bandwidth ... 22
5.5 Network transmission quality ... 22
5.6 Video frame rate ... 23
6 Exchange requirements ... 23
6.1 Uniform encoding rules ... 23
6.2 Media encoding-decoding ... 24
6.3 Media storage encapsulation format ... 24
6.4 Definition of SDP ... 24
6.5 Conversion of network transmission protocol ... 24
6.6 Conversion of control protocol ... 24
6.7 Conversion of media transfer protocol ... 24
6.8 Conversion of media data format ... 24
6.9 Peer-to-peer networking with other systems ... 24
6.10 Signaling character set ... 25
6.11 Multipath cascaded networking structure ... 25
7 Control requirements ... 25
7.1 Registration ... 25
7.2 Real-time video and audio on demand ... 25
7.3 Control ... 26
7.4 Alarm event notification and distribution ... 26
7.5 Device information query ... 26
7.6 Status information submission ... 27
7.7 Retrieval of historical video and audio files ... 27
7.8 Playback of historical video and audio ... 27
7.9 Download of historical video and audio files ... 27
7.10 Network time calibration ... 28
7.11 Subscriptions and notifications ... 28
7.12 Voice broadcast and voice intercom ... 28
7.13 Device software upgrade ... 28
7.14 Image capture ... 28
8 Transmission, exchange, control security requirements ... 28
8.1 Device identity authentication ... 28
8.2 Data encryption ... 29
8.3 SIP signaling authentication ... 29
8.4 Data integrity protection ... 29
8.5 Access control ... 29
8.6 High security level requirements ... 30
9 Control, transmission process and protocol interface... 30
9.1 Registration and deregistration ... 30
9.2 Real-time video and audio on demand ... 34
9.3 Control ... 41
9.4 Alarm event notification and distribution ... 45
9.5 Network device information query ... 48
9.6 Status information submission ... 51
9.7 Device video and audio file retrieval ... 53
9.8 Playback of historical video and audio ... 54
9.9 Video and audio file download ... 64
9.10 Time calibration ... 72
9.11 Subscriptions and notifications ... 73
9.12 Voice broadcast and voice intercom ... 79
9.13 Device software upgrade ... 85
9.14 Image capture ... 88
Annex A (normative) Command set of monitoring and alarm networking system control description protocol (MANSCDP) ... 91
A.1 Command names and descriptions ... 91
A.2 Command definition ... 91
A.3 Front-end device control protocol ... 150
A.4 Extended application of networking system ... 154
Annex B (normative) Command set of monitoring and alarm networking system real- time streaming protocol (MANSRTSP) ... 155
B.1 Command name and description ... 155
B.2 Command definition ... 155
Annex C (normative) RTP-based video and audio data encapsulation ... 160 C.1 PS encapsulation of video and audio data based on RTP ... 160
C.2 RTP-based video and audio elementary stream encapsulation ... 161
Annex D (normative) Video and audio media transmission based on TCP protocol 165 Annex E (normative) Unicode rules ... 166
E.1 Encoding rules ... 166
E.2 Industry code comparison... 168
E.3 Rules for compilation of divisional codes below counties ... 169
Annex F (normative) Technical requirements for video and audio encoding/decoding ... 171
F.1 Basic requirements ... 171
F.2 Technical requirements for video encoding and decoding based on H.264 ... 171 F.3 Technical requirements for video encoding and decoding based on MPEG-4 ... 175 F.4 General requirements for audio coding and decoding ... 178
F.5 G.711 format ... 178
F.6 G.723.1 format ... 178
F.7 G.729 format ... 178
F.8 Technical requirements for SVAC video and SVAC audio encoding and decoding 179 F.9 Technical requirements for H.265 video encoding and decoding ... 179 F.10 AAC format ... 183
Annex G (normative) SDP definition ... 184
Annex H (informative) Technical requirements for camera and platform routing ... 191 H.1 Basic requirements ... 191
H.2 Processing logic ... 192
H.3 Definition of multipath SIP header extension ... 194
H.4 Path push and selection demonstration ... 195
Annex I (normative) Protocol version identification ... 198
Annex J (normative) Instructions for directory query responses ... 199
Annex K (normative) Keep-alive mechanism for media streams ... 205
Annex L (normative) Definition of the Subject header field ... 206
Annex M (normative) Multiple response messaging ... 207
Annex N (normative) Interdomain directory subscription notifications ... 208 N.1 Basic requirements ... 208
N.2 Application scenarios and processing logic ... 208
N.3 Signaling process ... 211
N.4 Protocol interface ... 214
Annex O (normative) The code of the acquisition part type of the camera ... 217 Bibliography ... 222
Technical requirements for information transmission, switch
and control in video surveillance networking system for
public security
1 Scope
This document specifies the peer-to-peer networking structure of the video surveillance networking system for public security (hereinafter referred to as "surveillance networking system"), the basic requirements and security requirements for transmission, exchange, and control, as well as the technical requirements for control, transmission process, and protocol interface.
This document is applicable to the scheme design, system testing, acceptance and related device development and production of the video surveillance networking system for public security. Other video surveillance networking systems can be implemented by using this document as reference.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. GB/T 4754, Industrial classification for national economic activities
GB/T 10114-2003, Rules for the code representation of administrative divisions under counties
GB 18030, Information technology - Chinese coded character set
GB/T 25724, Technical specifications for surveillance video and audio coding GB 35114, Technical requirements for information security of video surveillance network system for public security
GA/T 380, Coding rules for public security organs
ISO/IEC 13818-1:2019, Information technology - Generic coding of moving pictures and associated audio information - Part 1: Systems
ISO/IEC 14496-2:2004, Information technology ?€? Coding of audio-visual objects - 3.1.3 user terminal
A client device that is registered and authorized by a networking system and has operational requirements for data and/or devices within the system.
3.1.4 session initiation protocol; SIP
Developed by the Internet Engineering Task Force (IETF), it is a framework protocol for multi-party multimedia communication.
NOTE: Session initiation protocol is a text-based application layer control protocol, independent of the underlying transport protocol. It is used to establish, modify and terminate two-party or multi- party multimedia sessions on IP networks.
3.1.5 session control
The process of establishing, modifying or ending a communication between one or more participants.
3.1.6 SIP surveillance realm
A monitoring system consisting of front-end device, user terminals, servers, and networks conforming to the provisions of this document.
3.1.7 non-SIP surveillance realm
Surveillance systems that do not comply with the provisions of this document. 3.1.8 the third party controller
A SIP user agent (UA), capable of creating a session between two other user agents. NOTE: Third party controllers are generally implemented using back-to-back user agents (B2BUA). 3.1.9 the third party call control
The third party controller initiates, establishes, and releases sessions between two or more parties, and is responsible for the media negotiation between the parties. 3.1.10 user agent
SIP logical end entity specified by IETFRFC 3261. It is composed of user agent client (UAC) and user agent server (UAS). UAC is responsible for initiating calls, and UAS is responsible for receiving calls and responding.
3.1.11 proxy server
SIP logical entity specified by IETF RFC 3261. Through it, the request from the user agent client (UAC) is forwarded to the user agent server (UAS), and the response message of the UAS is forwarded back to the UAC.
3.1.12 register server
SIP logical entity specified by IETF RFC 3261, which has the function of receiving registration requests, saving the information carried in the requests, and providing location services within the domain.
3.1.13 redirect server
SIP logical entity specified by IETF RFC 3261. The server is responsible for planning SIP routing and telling the requester the obtained signaling next-hop address information, so that the requester can directly send a request to the next hop according to this address.
3.1.14 back to back user agent
SIP logical entity specified by IETF RFC 3261. It acts as a user agent server (UAS) to receive request messages and process the messages. At the same time, in order to decide how to respond to the request message, it also acts as a user agent client (UAC) to send the request message.
NOTE: A back to back user agent (B2BUA) differs from a proxy server in that a B2BUA needs to maintain a state of the conversations it creates.
3.1.15 functional entity
A collection of logic units that implement some specific functions.
NOTE: A physical device can consist of multiple functional entities. A functional entity may also consist of multiple physical devices.
3.1.16 source device
A device that actively initiates a service request.
3.1.17 target device
A device that finally responds to service requests.
3.1.18 SIP client
An entity that complies with the provisions of IETF RFC 3261 and has the functions of registration, establishment/termination of session connection, reception and playback of video and audio streams, etc. It mainly includes user interface, user agent (UA), media decoding module and media communication module.
3.1.19 SIP device
Peer-to-peer networked networking system platforms and devices shall not send application-independent messages to each other's SIP ports. Avoid application- independent messages from occupying SIP message processing resources of networking system platforms and devices.
This document is based on basic protocols such as IETF RFC 3261 and specifies the various business functions of monitoring and networking. If this document has special provisions for various functions, it shall follow this document, otherwise it shall follow the reference agreement such as IETF RFC 3261.
4.3.3 Session description protocol
The session negotiation and media negotiation of the session establishment process between devices in the networking system shall be described by the IETF RFC 4566 protocol. The main content includes session description, media information description, and time information description. Session negotiation and media negotiation information shall be carried and transmitted in the message body of the SIP message. 4.3.4 Control description protocol
Control commands related to front-end device control, alarm information, and device directory information of the networking system shall be described in MANSCDP and shall comply with the provisions of Annex A. Networking system control commands shall be carried and transmitted in the message body of the SIP message MESSAGE. 4.3.5 Media playback control protocol
The playback control command of historical video and audio shall use MANSRTSP. The protocol description shall comply with the provisions of Annex B. It shall realize the remote control of video and audio streams such as normal, fast, pause, stop, and random drag and play between devices between end-to-end. The historical media playback control command is carried and transmitted by the message body of the SIP message INFO.
4.3.6 Media transmission and media codec protocol
RTP transmission shall be supported when the media stream is transmitted on the IP network of the networking system. The media stream sending source shall support the function of controlling the peak value of media stream sending. The RTP load shall be in one of two formats: Video and audio data or video and audio elementary stream data based on PS encapsulation shall comply with the provisions of Annex C. The transmission of the media stream shall adopt the RTP protocol stipulated in IETF RFC 3550. Provide time stamp information in real-time data transmission and synchronization of each data stream. The RTP timestamps of all RTP packets encapsulated in the same frame of video and audio packets are the same, and different from the RTP timestamps of RTP packets of different frames of video and audio packets. The RTCP protocol stipulated in IETF RFC 3550 shall be adopted to provide reliable guarantee for the sequential transmission of data packets. Provide flow control and congestion control.
5 Transmission requirements
5.1 Requirements for network transmission protocol
The network layer of the networking system shall support the IP protocol. The transport layer shall support TCP and UDP protocols.
5.2 Requirements for media transfer protocol
Video and audio streams shall support RTP/RTCP protocol when transmitted on IP- based network. The data encapsulation format of video and audio streams shall meet the requirements of 4.3.6.
When video and audio streams are transmitted on an IP-based network, it is advisable to extend support for the TCP protocol. The protocol shall comply with the provisions of Annex D.
5.3 Information transmission delay time
When networking system information is transmitted via an IP network, the end-to-end information delay time (including the time elapsed during information collection, encoding, network transmission at the sending end, and information decoding and displaying at the receiving end) shall meet the following requirements: a) The end-to-end information delay time between the front-end device and the corresponding device directly connected to the monitoring center shall not be greater than 2 s.
b) The end-to-end information delay time between the front-end device and the user terminal device shall not be greater than 4 s.
5.4 Network transmission bandwidth
The network bandwidth design of the networking system shall be able to meet the bandwidth requirements of front-end device access to the monitoring center, peer-to- peer networking of monitoring center, and user terminal access to the monitoring center. There shall be allowance.
5.5 Network transmission quality
The transmission quality (such as transmission delay, packet loss rate, packet error rate, false packet rate, etc.) of the networking system IP network shall meet the following requirements:
6.2 Media encoding-decoding
Video codec in networking system shall adopt SVAC, H.264, H.265 or MPEG-4. SVAC is preferred. The audio encoding-decoding shall be G.711, G.722.1, G.723.1, G.729, SVAC or AAC. Relevant technical requirements shall comply with the provisions of Annex F.
6.3 Media storage encapsulation format
The storage and packaging format of media data such as video and audio in the networking system shall be PS format. See ISO/IEC 13818-1:2019 for the format. 6.4 Definition of SDP
The SDP content carried by the SIP message body in the networking system shall comply with the relevant requirements of IETF RFC 4566. The required fields shall comply with the provisions of Annex G.
6.5 Conversion of network transmission protocol
It shall support the two-way protocol conversion between the network transmission protocol of the non-SIP surveillance realm and the network transmission protocol specified in 5.1.
6.6 Conversion of control protocol
It shall support the two-way protocol conversion between the device control protocol in the non-SIP surveillance realm and the session initiation protocol, session description protocol, control description protocol and media playback control protocol specified in 4.3.
6.7 Conversion of media transfer protocol
It shall support the two-way protocol conversion between the media transmission protocol and data encapsulation format of the non-SIP surveillance realm and the media transmission protocol specified in 5.2 and the data encapsulation format specified in 4.3.6.
6.8 Conversion of media data format
It shall support the conversion of the media data in the non-SIP surveillance realm to the data in the media encoding format specified in 6.2.
6.9 Peer-to-peer networking with other systems
The peer-to-peer networking between the networking system and other systems shall comply with the requirements of Annex A and Annex E.
6.10 Signaling character set
The SIP signaling character set of networking systems and device shall adopt the encoding format in GB 18030.
6.11 Multipath cascaded networking structure
If some networking system management platforms have multiple upper-level platforms, the entire cascaded networking is not the tree structure shown in Figure 2 and Figure 3. There is a possibility that the upper-level platform accesses the target device of the lower-level platform through multiple paths. The management platform shall support this function according to the technical requirements in Annex H.
7 Control requirements
7.1 Registration
Registration meets the following requirements:
a) It shall support the working mode of registering with the SIP server when the device or system enters the networking system.
b) Device or system registration shall be extended to support carrying protocol version identification. The protocol version identification shall comply with the provisions of Annex I.
c) If the device or system registration is unsuccessful, it is advisable to re-register after a certain random time delay.
d) It is advisable to implement the registration redirection function. Dynamically assign access servers to devices, so as to cope with server-side load balancing and faul...

View full details