Distributed streaming media cross-segment access method based on SIP protocol for video surveillance system

Abstract

A distributed streaming media cross-segment access method for a video surveillance system based on the SIP protocol realizes access by video clients in different network segments by finding the IP address of a distributed load-balanced streaming media service in the same network segment as the main SIP signaling proxy service. This effectively solves the access restriction that the video client and the load-balanced streaming media service end are not in the same network segment, and the configuration-free method shortens the debugging and deployment cycle and improves engineering efficiency.

Description

Technical Field

[0001] The patented technology of this invention belongs to the field of computer multimedia technology, and specifically relates to a distributed deployment streaming media cross-segment access method for a video surveillance system based on the SIP protocol. Background Art

[0002] SIP (Session Initiation Protocol) is a multimedia communication protocol developed by IETF (Internet Engineering Task Force) to initialize, maintain and destroy real-time sessions between multimedia devices or applications. As a real-time video application, video surveillance systems are increasingly using the SIP protocol to establish the publishing and browsing of real-time audio and video streams through SIP communication between cameras, servers and SIP video clients.

[0003] The video surveillance system must not only meet the video surveillance needs of intranet users, but also meet the video communication between the external network proxy extended video client and the distributed streaming media service based on load balancing in different network segments from the intranet.

[0004] In the national standard "Technical requirements for information transmission, exchange and control of security video surveillance network systems"

[0005] (GB / T28181-2011) and the enterprise standard "Grid Video Surveillance System and Interface" issued by the State Grid Corporation of China both elaborate on the specific methods of using the SIP protocol to build a video surveillance system. In the above two standards, both mention that the video resources of the system can be accessed through the INVITE method to achieve the purpose of remote monitoring and control. Both propose to use streaming media services to distribute the data streams of video devices, so as to save bandwidth during concurrent access. However, how to establish the SIP signaling process between video clients, proxy services, distributed streaming media services and video surveillance devices in different network segments is not specified in the standards and specifications. Summary of the invention

[0006] In order to solve the deficiencies in the prior art, the present invention provides a distributed streaming media cross-segment access method based on the SIP protocol for a video surveillance system. The distributed streaming media cross-segment access method based on the SIP protocol provided by the present invention realizes the access of video clients in different network segments by searching for the IP address of a distributed load balancing streaming media service in the same network segment as the main SIP signaling proxy service.

[0007] The present invention specifically adopts the following technical solutions:

[0008] The distributed streaming media cross-segment access method of the video surveillance system based on the SIP protocol specifically includes the following steps:

[0009] Step 1, the main SIP signaling proxy service saves all network segment IP addresses and SIP listening port information of the main SIP signaling proxy server;

[0010] Step 2: The video client sends a login request containing the user code to the NGINX proxy server via the HTTP protocol;

[0011] Step 3: The NGINX proxy server forwards the video client login request to the main HTTP service;

[0012] Step 4: The main HTTP service parses the video client IP address through the HTTP request header, saves the correspondence between the user code and the server IP address received by the main HTTP service, and searches for the main SIP signaling proxy service IP address and port information in the same network segment as the server IP address received by the main HTTP service;

[0013] Step 5: The main HTTP service returns the resolved video client IP address and the main SIP signaling proxy service IP address and port found in step 4 to the video client via the NGINX proxy service;

[0014] Step 6: The video client sends an INVITE request carrying an SDP message body to the primary SIP signaling proxy service, where the SDP message body includes the IP address and port of the video client; wherein SDP is a protocol for session description;

[0015] Step 7: After receiving the INVITE request signaling in step 6, the primary SIP signaling proxy service forwards it to the target streaming media service assigned by the streaming media load balancing strategy through the intranet message bus;

[0016] Step 8, the streaming media service searches for the media server IP address and port information in the same network segment as the IP address corresponding to the received user code saved by the HTTP service in step 4, and returns it to the main SIP signaling service through the intranet message bus;

[0017] Step 9: The main SIP signaling proxy service fills the target media server IP address found in step 8 into the SDP and returns it to the video client;

[0018] Step 10: The video client returns an ACK signaling, and the streaming media service sends the audio and video stream to the video client according to the address IP and port corresponding to the video client in the SDP message body of the INVITE request signaling in step 7;

[0019] The SIP protocol refers to the Session Initiation Protocol.

[0020] Preferably, in step 2 and step 3, the NGINX proxy server configures the proxy HTTP service into a master-slave mode. When the video client accesses the backend server, the request is first obtained by NGINX and then forwarded to the backend master HTTP server by NGINX.

[0021] Preferably, in step 5, the main HTTP server may choose to transmit the data to the video client through the NGINX proxy server, or may directly transmit the data to the video client.

[0022] Preferably, in step 6, the video client may send the original request signaling to the primary SIP signaling proxy service via the transmission control protocol or the user datagram protocol.

[0023] Preferably, in step 8, the streaming media service searches for the media server IP address and real-time transport control protocol RTCP port information in the same network segment as the IP address corresponding to the received user code saved by the main HTTP service in step 4, and returns it to the main SIP signaling service through the intranet message bus.

[0024] Preferably, in step 9, the primary SIP signaling proxy service fills the media server IP address found in step 8 into the SDP and returns 200OK to the video client.

[0025] Preferably, in step 10, the video client of the video surveillance system replies with an ACK confirmation message, and the streaming media server transmits the audio and video stream to the video client via RTP and RTCP based on UDP or TCP (RTP is used to transmit audio and video data; RTCP is used to transmit quality control data) according to the IP address and port of the video client in the SDP message body in the INVITE request signaling in step 7, thereby completing cross-segment access with the distributed streaming media service.

[0026] The beneficial effect of the present invention is that, compared with the prior art, the purpose of the present invention is to realize the process of video clients accessing load-balanced streaming media services across network segments in a video surveillance system. In the video surveillance system, there is no need to configure the IP address of the streaming media service that responds to the video clients of the video surveillance system deployed in different network segments to realize signaling interaction and video communication. The access restriction that the video client and the load-balanced streaming media service end are not in the same network segment is effectively solved, and the configuration-free method shortens the debugging and deployment cycle and improves the engineering efficiency. In addition, the soft scalability of this system (no additional hardware is required under the condition that the server performance meets the expansion requirements) also provides technical guarantees for coping with various complex on-site actual environments and saves costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1It is a schematic diagram of a distributed streaming media cross-network segment access method based on the SIP protocol of a video monitoring system of the present invention.

[0028] Figure 2 The present invention is a flow chart of a distributed streaming media cross-network segment access method based on the SIP protocol of a video monitoring system. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical scheme and advantages of the present invention clearer, the technical scheme of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. The embodiments described in this application are only part of the embodiments of the present invention, not all of them. Based on the spirit of the present invention, other embodiments obtained by ordinary technicians in this field without creative work are all within the scope of protection of the present invention.

[0030] The method of the present invention is described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0031] Figure 1 It is a schematic diagram of a distributed streaming media cross-segment access method based on the SIP protocol in a video monitoring system of the present invention; Figure 2 Flow chart of the distributed streaming media cross-segment access method based on SIP protocol of the present invention, such as Figure 1 , Figure 2 As shown, the video surveillance system includes a video client, an NGINX proxy server, a SIP signaling proxy server, and a distributed load balancing streaming media server; characterized in that the access method includes the following steps:

[0032] Step 1: The main SIP signaling proxy service saves all network segment IP addresses and SIP listening port information of this server;

[0033] Specifically, for example: primary SIP signaling proxy server

[0034] IP1: 192.168.1.102

[0035] IP2: 172.20.102 (intranet)

[0036] Subnet mask: 255.255.255.0

[0037] Default Gateway: 192.168.1.254

[0038] SIP listening port: 5060

[0039] For example: Standby SIP signaling proxy server

[0040] IP1: 192.168.1.202

[0041] IP2: 172.20.202 (intranet)

[0042] Subnet mask: 255.255.255.0

[0043] Default Gateway: 192.168.1.254

[0044] SIP listening port: 5060

[0045] Step 2: The video client sends a login request containing the user code to the NGINX proxy server via the HTTP protocol;

[0046] Specifically,

[0047] For example: Video client

[0048] IP: 10.1.1.1

[0049] Subnet mask: 255.255.255.0

[0050] Default Gateway: 10.1.1.254

[0051] User ID: 1001

[0052] Video stream receiving port: 40000

[0053] Example: NGINX server

[0054] IP: 192.168.1.100

[0055] Subnet mask: 255.255.255.0

[0056] Default Gateway: 192.168.1.254

[0057] HTTP listening port: 8080

[0058] Step 3: The NGINX proxy server forwards the video client login request to the main HTTP service;

[0059] For example: Main HTTP server

[0060] IP: 192.168.1.101

[0061] Subnet mask: 255.255.255.0

[0062] Default Gateway: 192.168.1.254

[0063] HTTP listening port: 8080

[0064] For example: HTTP server

[0065] IP: 192.168.1.201

[0066] Subnet mask: 255.255.255.0

[0067] Default Gateway: 192.168.1.254

[0068] HTTP listening port: 8080

[0069] In steps 2 and 3, the NGINX proxy server (IP: 192.168.1.100) configures the proxy HTTP service to active-standby mode. When the video client accesses the backend server, it does not directly request the backend server, but first obtains the request by NGINX, and then forwards it to the backend primary HTTP server (IP: 192.168.1.101).

[0070] Step 4, the main HTTP service parses the video client IP address (IP: 10.1.1.1) through the HTTP request header, saves the correspondence between the user code (1001) and the main HTTP service IP address (IP: 192.168.1.101) (the correspondence between the user code 1001 and IP: 192.168.1.101), and searches for the main SIP signaling proxy service IP address (IP: 192.168.1.102) and port (5060) information in the same network segment as the server IP address (IP: 192.168.1.101) received by the main HTTP service;

[0071] Step 5: The main HTTP service returns the resolved video client IP address (IP: 10.1.1.1) and the main SIP signaling proxy service IP address (IP1: 192.168.1.102) and port (5060) found in step 4 to the video client (IP: 10.1.1.1) via the NGINX proxy service.

[0072] Specifically, in step 5, the main HTTP server can choose to transmit data to the video client through the NGINX proxy server, or it can directly transmit the data to the video client.

[0073] Step 6, the video client sends an INVITE request carrying an SDP message body to the primary SIP signaling proxy service, wherein the SDP message body includes the IP address (IP: 10.1.1.1) and port (40000) of the video client; preferably, the video client can send the original request signaling to the primary SIP signaling proxy service via TCP (Transmission Control Protocol, hereinafter referred to as TCP) or UDP (User Datagram Protocol, hereinafter referred to as UDP) protocol, wherein SDP is a protocol for session description;

[0074] Step 7: After receiving the INVITE request signaling in step 6, the main SIP signaling proxy service determines whether the target video device in the request signaling is a video device resource of the video surveillance system. When the target device in the request signaling is a video device resource of the system, it is forwarded to the target streaming media server 2 (IP1: 192.168.1.302) assigned by the streaming media load balancing strategy through the intranet (IP2: 172.20.1.XXX) message bus; if the target device in the request signaling is not a video device resource of the system, it returns that the requested target resource is wrong. Specifically,

[0075] For example: Streaming Server 1

[0076] IP1: 192.168.1.301

[0077] IP2: 172.20.1.301 (intranet)

[0078] Subnet mask: 255.255.255.0

[0079] Default Gateway: 192.168.1.254

[0080] For example: Streaming Server 2

[0081] IP1: 192.168.1.302

[0082] IP2: 172.20.1.302 (intranet)

[0083] Subnet mask: 255.255.255.0

[0084] Default Gateway: 192.168.1.254

[0085] For example: streaming media server

[0086] IP1: 192.168.1.30N

[0087] IP2: 172.20.1.30N (intranet)

[0088] Subnet mask: 255.255.255.0

[0089] Default Gateway: 192.168.1.254

[0090] Step 8, the streaming media service searches for the media server IP address and port information in the same network segment as the IP address corresponding to the received user code saved by the main HTTP service in step 4, and returns it to the main SIP signaling service through the intranet message bus;

[0091] Specifically, the streaming media service 1 searches for the media server IP address (IP1:192.168.1.302) and RTCP port information in the same network segment as the IP address (IP:192.168.1.101) corresponding to the received user code (1001) saved by the main HTTP service (IP:192.168.1.101) in step 4, and returns it to the main SIP signaling service (IP2:172.20.1.102) through the intranet (IP2:172.20.1.XXX) message bus;

[0092] Step 9, the main SIP signaling proxy service fills the target media server 2 IP address (IP1:192.168.1.302) found in step 8 into the SDP and returns it to the video client;

[0093] Specifically, the primary SIP signaling proxy service fills the media server 2 IP address (IP1:192.168.1.302) into the SDP and returns 200OK to the video client;

[0094] Step 10, streaming media server 2 (IP1: 192.168.1.302) sends the audio and video stream to the video client according to the address IP (IP: 10.1.1.1) and port (40000) corresponding to the video client in the SDP message body of the INVITE request signaling in step 7.

[0095] Specifically, the video client of the video surveillance system replies with an ACK confirmation message, and the streaming media server 2 (IP1: 192.168.1.302) transmits the audio and video stream to the video client via UDP or TCP RTP and RTCP according to the IP address (IP: 10.1.1.1) and port (40000) of the video client in the SDP message body of the INVITE request signaling in step 7, thereby completing cross-segment access with the distributed streaming media service.

[0096] Preferably, in the present invention, the request signaling sent by the video client and the signaling returned by the streaming media server are both SIP (Session Initiation Protocol) signaling.

[0097] The present invention effectively solves the access restriction that a video client and a streaming media server are not in the same network segment in a video monitoring system.

[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents, and any modifications or equivalent replacements that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A distributed streaming media cross-segment access method for a video surveillance system based on the SIP protocol, characterized in that: The specific steps include: Step 1, the main SIP signaling proxy service saves all network segment IP addresses and SIP listening port information of the main SIP signaling proxy server; Step 2: The video client sends a login request containing the user code to the NGINX proxy server via the HTTP protocol; Step 3: The NGINX proxy server forwards the video client login request to the main HTTP service; Step 4: The main HTTP service parses the video client IP address through the HTTP request header, saves the correspondence between the user code and the server IP address received by the main HTTP service, and searches for the main SIP signaling proxy service IP address and port information in the same network segment as the server IP address received by the main HTTP service; Step 5: The main HTTP service returns the resolved video client IP address and the main SIP signaling proxy service IP address and port found in step 4 to the video client via the NGINX proxy service; Step 6: The video client sends an INVITE request carrying an SDP message body to the primary SIP signaling proxy service, where the SDP message body includes the IP address and port of the video client; wherein SDP is a protocol for session description; Step 7: After receiving the INVITE request signaling in step 6, the primary SIP signaling proxy service forwards it to the target streaming media service assigned by the streaming media load balancing strategy through the intranet message bus; Step 8, the streaming media service searches for the media server IP address and port information in the same network segment as the IP address corresponding to the received user code saved by the HTTP service in step 4, and returns it to the main SIP signaling proxy service through the intranet message bus; Step 9: The main SIP signaling proxy service fills the target media server IP address found in step 8 into the SDP and returns it to the video client; Step 10: The video client returns an ACK signaling, and the streaming media service sends the audio and video streams to the video client according to the address IP and port corresponding to the video client in the SDP message body of the INVITE request signaling in step 7; The SIP protocol refers to the Session Initiation Protocol.

2. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In steps 2 and 3, the NGINX proxy server configures the proxy HTTP service into active / standby mode. When the video client accesses the backend server, NGINX first obtains the request and then forwards it to the backend primary HTTP server.

3. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In step 5, the main HTTP server can choose to transmit data to the video client through the NGINX proxy server, or directly transmit the data to the video client.

4. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In step 6, the video client may send an original request signaling to the primary SIP signaling proxy service via the transmission control protocol or the user datagram protocol.

5. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In step 8, the streaming media service searches for the media server IP address and real-time transport control protocol RTCP port information in the same network segment as the IP address corresponding to the received user code saved by the main HTTP service in step 4, and returns it to the main SIP signaling service through the intranet message bus.

6. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In step 9, the primary SIP signaling proxy service fills the media server IP address found in step 8 into the SDP and returns 200 OK to the video client.

7. The distributed streaming media cross-segment access method based on the SIP protocol of the video surveillance system according to claim 1 is characterized by: In step 10, the video surveillance system video client replies with an ACK confirmation message, and the streaming media server transmits the audio and video stream to the video client through the real-time transport protocol RTP and real-time transport control protocol RTCP based on UDP or TCP according to the IP address and port of the video client in the SDP message body in the INVITE request signaling in step 7, where RTP is used to transmit audio and video data, and RTCP is used to transmit quality control data.

Images