1 Scope
This Standard specifies the interconnection structure and communication protocols structure of information transport, switch and control and the basic requirements and security requirements for transport, switch and control and technical requirements for control, transport process and protocol interfacing etc.
This Standard is applicable to the scheme design, system testing, acceptance of security and protection video monitoring network s and urban monitor and control alarming network system and related equipment R&D and manufacture. Other information systems may adopt it by reference.
2. Normative References
The following documents are indispensable for the application of this Standard. For dated references, only the dated edition is applicable to this Document. For undated references, the latest edition (including all the amendments) applies.
GB/T 25724-2010 Technical Specification of Surveillance Video and Audio Coding
ISO/IEC 13818-1: 2000 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 - Part 2: Visual
ISO/IEC 14496-2: 2004/Amd.2: 2005 (Information Technology - Coding of Audio - Visual Objects - Part 2: Visual��Technical Corrigendum 2)
ISO/IEC 14496-4: 2004 Information Technology - Coding of Audio-visual Objects - Part 4: Conformance Testing (Available in English only)
ISO/IEC 14496-4: 2004/Amd.10: 2005 Information Technology - Coding of Audio-visual Objects - Part 4: Conformance Testing (available in English only��Technical Corrigendum 10)
ITU-T Rec.G.711-1988 Pulse Code Modulation (PCM) of Voice Frequencies
ITU-T Rec.G.723.1-1996 Dual Rate Speech Coder for Multimedia Communications Transmitting at 5.3 and 6.3 kbit/s
ITU-T Rec.G.729-1996 Coding of Speech at 8 kbit/S Using Conjugate Structure Algebraic - Code-excited Linear Prediction(CS-ACELP)
lTU-T Rec.H.264-2005 Advanced Video Coding for Generic Audiovisual Services
ITU-T Rec.H.264.1-2005 Conformance Specification For H.264 Advanced Video Coding
IETF RFC 2030 Simple Network Time Protocol (SNTP) Version 4 for IPv4,IPv6 and OSI)
IETF RFC 2326 (RTSP)Real Time Streaming Protocol
IETF RFC 2976 The SIP INFO Method
IETF RFC 3261 SIP: Session Initiation Protocol
IETF RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
IETF RFC 3428 Session Initiation Protocol (SIP) Extension for Instant Messaging
IETF RFC 3550 RTP: A Transport Protocol for Real - Time Application
IETF RFC 3725 Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)]
IETF RFC 4566 Session Description Protocol
3. Terms, Definitions and Abbreviations
3.1 Terminology and Definitions
For the purpose of this Standard, the following terms and definitions apply.
3.1.1 Security and protection video monitoring network system
It refers to the integrated network system which is able to fulfill the interconnection, interchange and compelling between different equipment and between systems and is equipped with such functions as information collection, transport, control, display, storage, treatment within urban and large-sized locations as for integrated application of such technologies as video and audio monitor and control, communication, computer network and system integration for purpose of security precautions.
3.1.2 Data of network system
It refers to the information transported, switched and controlled in network system, mainly including alarm information (analogue switch amount alarming and data protocol alarming), video information (simulation video signal and digital video signal), audio information (simulation audio signal and digital audio signal, equipment control information (serial port data and IP network data), equipment management information (serial port and IP network data) etc.
3.1.3 Front end device
It refers to the equipment of information collection, coding/treatment, storage, transport and safety control, installed at the site of monitor and control in network system.
3.1.4 Monitoring site
It refers to the location or places of front end device installation or monitor and control.
3.1.5 Monitoring center
It refers to the specific information collection, treatment and shared node in network system.
Note: monitor and control management personnel conduct centralized management and control on network system, apply and deal with the monitoring information.
3.1.6 User terminal
It refers to the client equipment with operation demand for data and/or equipment in the system and registered with network system and authorized.
3.1.7 Digital access
It refers to access mode with which front end device or regional monitor and control alarm system transports digital video and audio signal to the monitoring center through digital transmission channel.
3.1.8 Analog access
It refers to access mode with which front end device or regional monitor and control alarm system transports digital video and audio signal to the monitoring center through analogue transmission channel.
3.1.9 Analog-digital mixed monitoring system
It refers to the monitoring system with coexistence of simulation and digital signal control and treatment methods at the monitoring center.
3.1.10 Digital monitoring system
It refers to the monitoring system with the existence of digital signal control and treatment method at the monitoring center.
3.1.11 SIP: Session Initiation Protocol
It refers to the Framework Agreement for multi-party multimedia communication and formulated by IETF: Internet Engineering Task Force.
Note: it is an application layer control protocol based on text, and independent of bottom layer transport protocol and applicable to the establishment, modification and termination of bi-party or multi-party multimedia session on IP on-line.
3.1.12 Session control
It refers to the process of establishment, modification or completion of communication between one or multiple participants.
3.1.13 SIP monitoring realm
It refers to the monitoring network to support the communication protocols specified in this Standard and consists of SIP server and monitoring resources, user terminal and network etc. registered on SIP server.
3.1.14 Non-SIP monitoring realm
It refers to monitoring network composed of monitoring resources, user terminal and network etc. not supporting the communication protocols specified in this Standard. Non-SIP monitoring realm includes analog access device, digital access equipment not supporting the communication protocols not supporting the communication protocols specified in this Standard, analog-digital mixed monitoring system and digital monitoring system not supporting SIP protocols specified in this Standard.
3.1.15 The third party controller
It refers to a SIP user agent ( UA) and is able to create session between two user agents. The third party controller generally is realized adopting back-to-back user agent ( B2B UA).
3.1.16 The third party call control
The third party controller generally initiates and establish session and release session operation between additional two parties or more parties, and is responsible for media negotiation between session parties.
3.1.17 User agent
It is SIP logical terminal entity specified in IETF RFC 3261, composed of user agent client (UAC) and user agent server ( UAS) with UAC responsible for sending calls and UAS responsible for receiving calls and conducting response.
3.1.18 Proxy server
It refers to SIP logic entity specified in IETF RFC 3261, through which request from user agent client (UAC) is forwarded to user agent server (UAS ) and the response message from UAS is forwarded back to UAC.
One request message may be transported through a number of proxy servers and each proxy server determined routing independently; the response message is delivered along the reverse direction of request message.
3.1.19 Register server It refers to the SIP logic entity specified in IETF RFC 3261 and is the server with the functions such as receiving login request, storing information carried in the request and providing location service in the domain.
3.1.20 Redirect server
It refers to SIP logic entity specified in IETF RFC 1261 and is responsible for planning SIP call route. It informs the caller of the next trip address information of call received for the caller to send out request to next trip according to the address and the redirect server exit the calling process.
3.1.21 Back to back user agent
It refers to SIP logic entity specified in IETF RFC 3261, and receives request message and treats the message as user agent server ( UAS ) and meanwhile it send request message as user agent client (UAC) in order to judge how to respond to the request message.
Note: the difference between back-to-back user agent ( B2B UA) and proxy server is that B2B UA requires to maintain a session state it creates.