A video surveillance system, method, medium, and device supporting multi-protocol access.

Abstract

This invention discloses a video surveillance system, method, medium, and device supporting multi-protocol access, belonging to the field of computer and communication technology. The system includes a client, a gateway, a service control module, a video transcoding module, a streaming media distribution module, a metadata storage module, and a target camera device. The service control module receives video playback requests from the client forwarded by the gateway, obtains the connection status with the metadata storage module, selects the corresponding system operating mode, obtains the device's access parameters, constructs an RTSP connection string, and sends it to the video transcoding module, enabling it to pull the video stream from the device and convert it in real time to a WebRTC-compatible format, then pushes it to the streaming media distribution module. The streaming media distribution module is used for signaling interaction and media negotiation with the client, encapsulating the compatible video stream, and distributing it to the client via a UDP multiplexed channel. This invention achieves low-latency video playback on the web and improves the system's disaster recovery capabilities.

Description

Technical Field

[0001] This invention relates to a video surveillance system, method, medium, and device that supports multi-protocol access, belonging to the field of computer and communication technology. Background Technology

[0002] Existing video surveillance systems playing on the web suffer from the following technical problems: browsers do not support the RTSP protocol; WebSocket-based streaming solutions rely on client-side software decoding, which can lead to frame backlog and latency exceeding seconds during prolonged playback, resulting in stuttering and screen tearing; HLS / FLV-based slicing solutions suffer from high physical latency due to their caching mechanisms, failing to meet the millisecond-level real-time requirements for PTZ control. At the system architecture level, device information is stored in relational databases such as MySQL and PostgreSQL. Service operation requires real-time database queries; if the database crashes, the network is interrupted, or the connection limit is exhausted, the video service will completely fail, even if the cameras are functioning normally, and it is difficult to quickly pinpoint whether the problem is with the database or the devices. In actual engineering deployments, video streaming services often involve complex port mapping and cross-domain resource sharing configurations. Existing technologies mostly employ manual configuration or simple monolithic deployments, lacking effective routing isolation mechanisms, leading to port conflicts between business streams and video streams, high maintenance costs, and susceptibility to service startup failures due to port conflicts.

[0003] Therefore, there is an urgent need for a video surveillance system that can achieve low-latency web-based playback and has adaptive degradation capabilities for database failures. Summary of the Invention

[0004] The purpose of this invention is to provide a video surveillance system, method, medium, and device that supports multi-protocol access. The system obtains the connection status with the metadata storage module in real time through the business control module and selects the corresponding operating mode to obtain the access parameters of the target camera device. Furthermore, the system pulls the RTSP stream through the video transcoding module, converts it into a WebRTC-compatible format, and pushes it. After being encapsulated by the streaming media distribution module and transmitted through a UDP multiplexed channel, the video stream is played with low latency on the Web.

[0005] To achieve the above objectives, the present invention is implemented using the following technical solution.

[0006] On the one hand, the present invention provides a video surveillance system that supports multi-protocol access, including a client, a gateway, a service control module, a video transcoding module, a streaming media distribution module, a metadata storage module, and a target camera device;

[0007] The business control module is used to receive client video playback requests forwarded by the gateway, obtain the connection status with the metadata storage module to select the corresponding system operation mode, obtain the access parameters of the target camera device in each mode, construct the RTSP connection string and send it to the video transcoding module; the business control module is also used to control the streaming media distribution module through the API interface and return the access address for WebRTC signaling interaction to the client.

[0008] The video transcoding module is used to construct and execute stream processing instructions based on the RTSP connection string, pull video streams from the target camera device and convert them in real time into a WebRTC-compatible streaming media format, and push them to the streaming media distribution module;

[0009] The streaming media distribution module is used to complete WebRTC signaling interaction with the client, perform media negotiation, encapsulate WebRTC-compatible video streams, and distribute them to the client through the negotiated UDP multiplexed channel.

[0010] Optionally, the business control module obtains the connection status with the metadata storage module to select the corresponding system operating mode, including:

[0011] Upon receiving a video playback request or during the service initialization phase, an attempt is made to establish a network connection with the metadata storage module;

[0012] If a connection rejection or timeout exception is received, the system will be switched to stateless operation mode; otherwise, the system will be switched to stateful operation mode.

[0013] Optionally, in each mode, the access parameters of the target camera device can be obtained, including:

[0014] When the system is in stateful operation mode, it queries the access parameters of the target camera device from the metadata storage module based on the device ID carried in the video playback request.

[0015] When the system is in stateless operation mode, it parses the payload parameters of the video playback request, extracts the access parameters of the target camera device, and verifies the completeness of the parameters. If the parameters contain the complete device IP address, port number, access credentials, and stream path, the verification passes, and the parameters are used directly to construct the RTSP connection string. If the parameters are missing, an error message is returned to the client.

[0016] Optionally, the video transcoding module constructs stream processing instructions, including:

[0017] Use the TCP protocol to perform an RTSP handshake;

[0018] Configure user agent parameters to simulate standard player behavior;

[0019] The Ultrafast encoding preset is used, and the Zerolatency tuning parameter is configured to disable the encoder's internal buffer.

[0020] Set a fixed keyframe interval and force keyframe insertion at regular intervals.

[0021] Optionally, the streaming media distribution module interacts with the client via WebRTC signaling to complete media negotiation, including:

[0022] Enable WebRTC port listening and ICE connection negotiation, write the host machine's physical IP address into the SDP session information, and complete the establishment of the UDP media transmission channel.

[0023] Optionally, the gateway is a reverse proxy gateway, which is configured with a first service listening port and a second service listening port;

[0024] The first service listening port corresponds to the video service plane, which is used to handle cross-network domain proxy forwarding of video playback requests and WebRTC related signaling. It is configured with cross-domain processing rules for directly responding to HTTP OPTIONS preflight requests, and retains Upgrade and Connection header information during the forwarding process to realize WebSocket protocol upgrade.

[0025] The second service listening port corresponds to the general business plane and is used to handle HTTPS encrypted transmission and forwarding of regular business logic.

[0026] In a second aspect, the present invention provides a video surveillance method supporting multi-protocol access, applied to the video surveillance system supporting multi-protocol access as described in the first aspect, comprising:

[0027] The gateway forwards client video playback requests to the business control module.

[0028] The business control module obtains the connection status between itself and the metadata storage module and selects the corresponding system operation mode. In each mode, the access parameters of the target camera device are obtained, an RTSP connection string is constructed, and the string is sent to the video transcoding module.

[0029] Using the video transcoding module, based on the RTSP connection string, a stream processing instruction is constructed and executed. The video stream is pulled from the target camera device via the RTSP protocol, converted in real time into a WebRTC-compatible streaming media format, and then pushed to the streaming media distribution module.

[0030] The business control module notifies the streaming media distribution module to start listening on the WebRTC port and returns the access address for WebRTC signaling interaction to the client. Based on the received access address, the client performs SDP exchange and ICE connection negotiation with the streaming media distribution module, and then establishes a UDP transmission channel.

[0031] The streaming media distribution module encapsulates WebRTC-compatible video streams and distributes them to clients through an established UDP multiplexed channel.

[0032] Optionally, the gateway is built using Nginx, and the video transcoding module integrates the FFmpeg tool.

[0033] Thirdly, the present invention provides a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implements the steps of the video surveillance method supporting multi-protocol access as described in any one of the second aspects.

[0034] Fourthly, the present invention provides a computer device, comprising:

[0035] Memory, used to store computer programs / instructions;

[0036] A processor for executing the computer program / instructions to implement the steps of the video surveillance method supporting multi-protocol access as described in any of the second aspects.

[0037] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0038] This invention uses a business control module to obtain the connection status with the metadata storage module in real time and adaptively selects the system operating mode based on the connection status. Even in the event of a database failure, it can still parse the payload parameters in the client's playback request to obtain access parameters, ensuring continuous availability of video services and improving the system's disaster recovery capabilities. A video transcoding module converts RTSP streams to WebRTC-compatible formats in real time and, combined with a streaming media distribution module, distributes them based on a UDP multiplexed channel, achieving low-latency, plugin-free playback on the web client. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of a video surveillance system architecture supporting multi-protocol access provided in an embodiment of the present invention;

[0040] Figure 2 This is a schematic diagram of a gateway architecture provided in an embodiment of the present invention. Detailed Implementation

[0041] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations thereof. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0042] Example 1

[0043] This embodiment describes a video surveillance system that supports multi-protocol access, such as... Figure 1 As shown, the solution specifically includes: a client, gateway, service control module, video transcoding module, streaming media distribution module, metadata storage module, and target camera equipment, which together constitute a complete video surveillance solution. The specific components are as follows:

[0044] Client: Runs in standard web browsers such as Chrome and Edge, without the need to install ActiveX or Flash plugins; The client sends control signals via HTTP / HTTPS protocol and receives video streams via WebRTC protocol (based on UDP), achieving plugin-free, low-latency native playback of video streams.

[0045] Reverse proxy gateway: The gateway is built using a lightweight, high-performance web server, such as Nginx, and deployed in a containerized environment.

[0046] Business control module: Built on the Python Flask framework, it is responsible for handling API requests, database connection acquisition, and fault degradation logic, which will be explained in detail later in this embodiment.

[0047] Video transcoding module: Integrates FFmpeg tools, responsible for pulling RTSP streams, real-time transcoding, and stream pushing.

[0048] Streaming media distribution module: It uses MediaMTX (or a similar streaming media service) as the WebRTC signaling server and media relay server, and supports UDP multiplexing.

[0049] The metadata storage module uses a relational database, specifically PostgreSQL, in this embodiment. It is used to store the configuration information (IP, port, channel number, account password, etc.) of the camera or network recorder.

[0050] The video equipment includes cameras and network recorders, which provide video streams to the outside world via the RTSP protocol.

[0051] The interaction process between the various modules of the system is explained in detail below:

[0052] The client sends a video playback request to the gateway via the HTTP protocol: / api / stream / start. The request payload is in JSON format and includes the device IP, port, username, password, and stream path.

[0053] After receiving a video playback request, the gateway performs route distribution;

[0054] The business control module performs database connection status acquisition during service initialization or upon receiving a request. Specifically, it determines the connection status of the metadata storage module by obtaining the operation error (OperationalError) or connection refused (ConnectionRefused) thrown by the database driver (such as SQLAlchemy / Psycopg2). Based on the connection status, it selects the corresponding system running mode, which is either stateful or stateless.

[0055] Stateful operation mode: The business control module queries the database table (such as the nepms_nvrs table) from the metadata storage module based on the device ID carried in the video playback request to obtain the complete access parameters.

[0056] Stateless Operation Mode: In this mode, the system skips all SQL query steps. Parameter injection validation is performed, specifically by parsing the JSON data of the video playback request payload. If the JSON data contains a complete IP address, port number, access credentials (username and password), and stream path, the system recognizes the request as legitimate and directly uses these parameters to construct the subsequent RTSP connection string. If parameters are missing, an error message "Service degradation and insufficient parameters" is returned to the client. Through this mechanism, even if the database server crashes or the network is interrupted, the video surveillance service can still operate normally as long as the client provides the parameters related to the physical device, ensuring business continuity.

[0057] The service control module constructs an RTSP connection string based on the acquired access parameters and sends it to the video transcoding module. Simultaneously, the service control module controls the streaming media distribution module via an API interface to prepare for video stream publishing, and also returns streaming media access credentials and the WebRTC signaling interaction address to the client.

[0058] The video transcoding module receives the RTSP connection string and dynamically constructs FFmpeg stream processing instructions based on the obtained device parameters. To achieve low latency, the key parameters are configured as follows:

[0059] Force the use of TCP protocol for RTSP streaming to prevent screen tearing or packet loss during network fluctuations;

[0060] Simulates standard media player behavior to prevent some cameras from being blocked by security policies;

[0061] : The ultra-fast preset using H.264 encoding achieves the fastest encoding speed with minimal compression.

[0062] : Core parameter. This parameter disables the encoder's internal buffer, allowing each frame of video to be output immediately after encoding, instead of waiting for B-frames or for the buffer to fill up.

[0063] Set the keyframe interval to 20, which is one frame per second, and force keyframes to be inserted periodically to achieve fast playback.

[0064] The video transcoding module pulls the raw video stream from the target camera device via the RTSP protocol, converts the video stream into a WebRTC-compatible streaming media format in real time, and then pushes it to the streaming media distribution module.

[0065] After receiving the API instruction from the business control module, the streaming media distribution module performs the following operations:

[0066] Initialize the WebRTC service, listen on a specific UDP port, and start the ICE negotiation service. Simultaneously, expose the WebRTC signaling interface for exchanging SDP session descriptions and verifying ICE candidate addresses with the client.

[0067] To address the issue of inconsistent internal and external network IPs in a Docker containerized deployment environment, which leads to ICE negotiation failure, this system sets the webrtcAdditionalHosts parameter in the configuration file. This forces the host machine's physical IP address to be written into the SDP session information, ensuring that the client browser can correctly address the media server.

[0068] After receiving the WebRTC signaling interaction address from the service control module, the client initiates signaling interaction and parameter negotiation with the streaming media distribution module through the gateway's video service plane proxy:

[0069] The client initiates a negotiation request, carrying an authentication request and an SDP session description;

[0070] After verifying the validity of the request, the streaming media distribution module returns an SDP response, completing the two-way media capability negotiation.

[0071] Both parties continued to exchange ICE candidate addresses and completed network connectivity verification and intranet penetration negotiation;

[0072] After the negotiation and verification are successful, both parties establish a WebRTC media transmission channel based on UDP and wait for the video stream data to be input.

[0073] The streaming media distribution module encapsulates the received video stream into SRTP (Secure Real-Time Transport Protocol) packets and distributes them to the client (browser) via a UDP multiplexed channel for decoding and playback.

[0074] If multiple browsers are accessing video from a single camera, there is still only one link to the camera. After the video is transcoded, it is distributed by a streaming media provider. Since the UDP protocol does not require TCP handshakes and retransmission confirmations, it greatly reduces transmission latency.

[0075] like Figure 2 As shown, to resolve port conflicts and cross-domain issues, this embodiment employs a dual-service configuration based on Nginx:

[0076] The video service plane Server1 listens on port 28080: it is used to handle video-related traffic; it is configured with the location / mediamtx / path to communicate with the streaming media service, implement WebRTC signaling forwarding, and support the Upgrade header to adapt to WebSocket long connections; it is configured with the Cross-Origin Resource Sharing (CORS) policy, which allows OPTIONS preflight requests to pass directly, enabling the frontend to call the video interface across domains; and it is configured with the location / api / path to communicate with the backend Python service.

[0077] The general business plane Server2 listens on port 443: it is used to handle regular HTTPS business requests; it is configured with SSL certificates and keys and enables HTTPS encrypted transmission; this plane mainly communicates with the backend Java business gateway or static resource server.

[0078] Through the above configuration, the system achieves physical port isolation between high-volume video data and regular control signaling data, facilitating independent bandwidth limiting and security policy deployment. In addition, with the help of automated deployment scripts, the IP address in the configuration file can be interactively replaced during deployment, and the container configuration can be automatically reloaded, dynamically modifying the IP address pointing to the backend service in the Nginx configuration, so that the same configuration can be quickly adapted to different network environments.

[0079] The system built based on this embodiment was tested in a laboratory environment. The test environment consisted of 10 1080P high-definition network cameras and a server configured with 4 cores and 8GB of RAM. Test results showed that the end-to-end latency from camera image capture to browser display remained stable between 200ms and 300ms, a significant performance improvement compared to the 1s-4s latency of the original WebSocket solution. After 48 hours of continuous operation, memory usage remained stable, with no video frame backlog or browser crashes. After manually disconnecting the database connection, the system successfully switched to stateless mode, and the video preview function remained unaffected.

[0080] Example 2

[0081] This embodiment describes a video surveillance method that supports multi-protocol access, applied to the video surveillance system that supports multi-protocol access as described in any one of Embodiment 1, and includes the following steps:

[0082] The gateway forwards client video playback requests to the business control module.

[0083] The business control module obtains the connection status between itself and the metadata storage module and selects the corresponding system operation mode. In each mode, the access parameters of the target camera device are obtained, an RTSP connection string is constructed, and the string is sent to the video transcoding module.

[0084] Using the video transcoding module, based on the RTSP connection string, a stream processing instruction is constructed and executed. The video stream is pulled from the target camera device via the RTSP protocol, converted in real time into a WebRTC-compatible streaming media format, and then pushed to the streaming media distribution module.

[0085] The business control module notifies the streaming media distribution module to start listening on the WebRTC port and returns the access address for WebRTC signaling interaction to the client. Based on the received access address, the client performs SDP exchange and ICE connection negotiation with the streaming media distribution module, and then establishes a UDP transmission channel.

[0086] The streaming media distribution module encapsulates WebRTC-compatible video streams and distributes them to clients through an established UDP multiplexed channel.

[0087] The gateway is built using Nginx, and the video transcoding module integrates the FFmpeg tool.

[0088] The specific steps for implementing the method have been described in detail in Example 1, and will not be repeated here.

[0089] Example 3

[0090] Based on the same inventive concept as other embodiments, this embodiment introduces a computer-readable storage medium storing a computer program / instructions thereon. When the computer program / instructions are executed by a processor, they implement the steps of the video surveillance method supporting multi-protocol access as described in any one of Embodiment 2. The steps of the method are not described in detail here.

[0091] Example 4

[0092] Based on the same inventive concept as other embodiments, this embodiment describes a computer device, including:

[0093] Memory, used to store computer programs / instructions;

[0094] A processor is used to execute the computer program / instructions to implement the steps of the video surveillance method supporting multi-protocol access as described in any one of Embodiment 2, the steps of which will not be elaborated here.

[0095] In summary, this invention uses a business control module to obtain the connection status with the metadata storage module in real time and adaptively selects the system operating mode based on the connection status. Even in the event of a database failure, it can still parse the payload parameters in the client's playback request to obtain access parameters, ensuring continuous availability of the video service and improving the system's disaster recovery capabilities. The video transcoding module converts the RTSP stream to a WebRTC-compatible format in real time and, combined with the streaming media distribution module, distributes it based on a UDP multiplexed channel, achieving low-latency, plugin-free playback on the web client.

[0096] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0097] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1A device that provides the functions specified in one or more boxes.

[0098] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0099] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0100] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A video surveillance system supporting multi-protocol access, characterized in that, This includes a client, gateway, business control module, video transcoding module, streaming media distribution module, metadata storage module, and target camera equipment; The business control module is used to receive client video playback requests forwarded by the gateway, obtain the connection status with the metadata storage module to select the corresponding system operation mode, obtain the access parameters of the target camera device in each mode, construct the RTSP connection string and send it to the video transcoding module; the business control module is also used to control the streaming media distribution module through the API interface and return the access address for WebRTC signaling interaction to the client. The video transcoding module is used to construct and execute stream processing instructions based on the RTSP connection string, pull video streams from the target camera device and convert them in real time into a WebRTC-compatible streaming media format, and push them to the streaming media distribution module; The streaming media distribution module is used to complete WebRTC signaling interaction with the client, perform media negotiation, encapsulate WebRTC-compatible video streams, and distribute them to the client through the negotiated UDP multiplexed channel.

2. The video surveillance system supporting multi-protocol access according to claim 1, characterized in that, The business control module obtains the connection status with the metadata storage module to select the corresponding system operating mode, including: Upon receiving a video playback request or during the service initialization phase, an attempt is made to establish a network connection with the metadata storage module; If a connection is refused or a timeout occurs, the system will be switched to stateless operation mode; otherwise, the system will be switched to stateful operation mode.

3. The video surveillance system supporting multi-protocol access according to claim 2, characterized in that, Obtain the access parameters of the target camera device in each mode, including: When the system is in stateful operation mode, it queries the access parameters of the target camera device from the metadata storage module based on the device ID carried in the video playback request. When the system is in stateless operation mode, it parses the payload parameters of the video playback request, extracts the access parameters of the target camera device, and verifies the completeness of the parameters. If the parameters contain the complete device IP address, port number, access credentials, and stream path, the verification passes, and the parameters are used directly to construct the RTSP connection string. If the parameters are missing, an error message is returned to the client.

4. The video surveillance system supporting multi-protocol access according to claim 1, characterized in that, The video transcoding module constructs stream processing instructions, including: Use the TCP protocol to perform an RTSP handshake; Configure user agent parameters to simulate standard player behavior; The Ultrafast encoding preset is used, and the Zerolatency tuning parameter is configured to disable the encoder's internal buffer. Set a fixed keyframe interval and force keyframe insertion at regular intervals.

5. The video surveillance system supporting multi-protocol access according to claim 1, characterized in that, The streaming media distribution module completes WebRTC signaling interaction with the client to achieve media negotiation, including: Enable WebRTC port listening and ICE connection negotiation, write the host machine's physical IP address into the SDP session information, and complete the establishment of the UDP media transmission channel.

6. The video surveillance system supporting multi-protocol access according to claim 1, characterized in that, The gateway is a reverse proxy gateway, which is configured with a first service listening port and a second service listening port; The first service listening port corresponds to the video service plane, which is used to handle cross-network domain proxy forwarding of video playback requests and WebRTC related signaling. It is configured with cross-domain processing rules for directly responding to HTTP OPTIONS preflight requests, and retains Upgrade and Connection header information during the forwarding process to realize WebSocket protocol upgrade. The second service listening port corresponds to the general business plane and is used to handle HTTPS encrypted transmission and forwarding of regular business logic.

7. A video surveillance method supporting multi-protocol access, applied to a video surveillance system supporting multi-protocol access as described in any one of claims 1-6, comprising: The gateway forwards client video playback requests to the business control module. The business control module obtains the connection status between itself and the metadata storage module and selects the corresponding system operation mode. In each mode, the access parameters of the target camera device are obtained, an RTSP connection string is constructed, and the string is sent to the video transcoding module. Using the video transcoding module, based on the RTSP connection string, a stream processing instruction is constructed and executed. The video stream is pulled from the target camera device via the RTSP protocol, converted in real time into a WebRTC-compatible streaming media format, and then pushed to the streaming media distribution module. The business control module notifies the streaming media distribution module to start listening on the WebRTC port and returns the access address for WebRTC signaling interaction to the client. Based on the received access address, the client performs SDP exchange and ICE connection negotiation with the streaming media distribution module, thereby establishing a UDP transmission channel; The streaming media distribution module encapsulates WebRTC-compatible video streams and distributes them to clients through an established UDP multiplexed channel.

8. The video surveillance method supporting multi-protocol access according to claim 7, characterized in that, The gateway is built using Nginx, and the video transcoding module integrates the FFmpeg tool.

9. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the video surveillance method supporting multi-protocol access as described in any one of claims 7 to 8.

10. A computer device, characterized in that, include: Memory, used to store computer programs / instructions; A processor for executing the computer program / instructions to implement the steps of the video surveillance method supporting multi-protocol access as described in any one of claims 7 to 8.

Images