A visual special situation processing method and system based on a remote frame buffer protocol

Abstract

The present application belongs to the intelligent traffic technical field, and particularly relates to a visual special situation processing method and system based on a remote frame buffer protocol. The method comprises the following steps: installing and starting a VNC server based on the RFB protocol at a lane end, providing a remote desktop, integrating a LibVNCClient in a lane special situation processing system, and realizing real-time control and visual access to the remote desktop; installing a lane camera at the lane end, starting an RTSP live protocol of the lane camera, providing an RTSP live stream address, integrating an FFMPEG in the lane special situation processing system, connecting the live stream address, and decoding a video stream captured by the lane camera in real time; and establishing a communication link between the lane end and the special situation processing system by using an Ethernet. The system comprises a remote desktop module, a camera video playing module, and a communication link establishing module. The present application provides flexible and changeable expressway lane special situation processing requirements, realizes seamless integration of toll business and remote video monitoring resources, and optimizes the passing efficiency of unattended lanes.

Description

Technical Field

[0001] This invention belongs to the field of intelligent transportation technology, specifically relating to a visual special situation handling method and system based on a remote frame buffer protocol. Background Technology

[0002] On-site lane toll collection systems refer to automated toll collection facilities installed at the entrances and exits of highways, bridges, tunnels, etc. They integrate vehicle identification (such as ETC and license plate recognition), toll calculation, and payment processing functions to achieve fast and efficient toll collection. This system typically includes hardware such as lane controllers, automatic barriers, vehicle detectors, high-definition cameras, and toll displays, as well as corresponding software management systems.

[0003] The remote emergency response system is designed to handle special situations (emergencies) that cannot be resolved automatically on-site, such as ETC recognition errors, vehicle type disputes, and toll evasion detection. This system is typically located in the management center and connects to the toll collection systems of each lane via a network to receive real-time information, analyze it, make judgments, and issue processing instructions.

[0004] The on-site lane toll collection system and the remote emergency response system are closely connected via a data communication network. When an emergency is detected at the lane end, an alarm is automatically triggered or manually by the toll collector, uploading relevant images, videos, transaction data, and other information to the backend. Upon receiving the information, the backend staff analyzes and judges it according to policies and rules, and sends processing instructions to the lane end, such as re-identification, manual input of toll amount, releasing or stopping the vehicle, etc. Because remote emergency response primarily relies on command interaction and does not directly display the user interface at the lane end, backend staff may not be able to intuitively understand the overall situation, affecting the accuracy and timeliness of their judgments. For example, they cannot directly observe the specific condition of the driver and vehicle, making it difficult to effectively identify any violations or special circumstances. To handle emergencies more effectively, the backend needs to be able to view real-time video footage of the lane involved in the emergency, including but not limited to high-definition videos of the vehicle's front and sides, as well as possible videos from inside the toll booth, to confirm whether vehicle information, driver behavior, and toll collector operations are compliant.

[0005] Currently, many toll collection systems still rely on traditional lane alarm methods, requiring on-site intervention by staff. While some systems have advanced to the point of automatically reporting emergencies and transmitting operational instructions to toll booths or on-site management positions via video intercom, several challenges remain: network transmission latency impacts communication efficiency, seamless integration with remote emergency response systems is difficult, there is a lack of functionality supporting direct intervention by remote operators, and the system suffers from insufficient compatibility and stability. These are all issues that urgently need to be addressed. Specifically, they may lead to the following problems:

[0006] 1. The problems caused by delays in video streaming transmission should not be underestimated. They disrupt the continuity of video playback and severely impact the smoothness of real-time communication between the back-end and the scene. In emergencies, such as when urgently needing to open a green channel for ambulances, such delays can lead to sluggish decision-making and hinder rapid response.

[0007] 2. The user interface designs provided by existing video providers are cumbersome and lack intuitiveness, which is extremely inconvenient for applications that want to be integrated into remote special situation handling systems, and seriously hinders the improvement of work efficiency.

[0008] 3. Existing remote visualization operation tools have limitations. They are independent of the billing business system and have poor scalability, making it difficult to adapt to flexible and ever-changing needs. This inevitably causes great trouble for users.

[0009] 4. Most existing interface software is tied to a specific operating system, which is not conducive to the future migration and promotion to domestic operating system platforms, and constitutes a significant obstacle to the process of localization of information technology. Summary of the Invention

[0010] This invention addresses the problems of existing lane toll collection systems, such as network transmission delays affecting communication efficiency, difficulty in seamless integration with remote emergency response systems, and lack of support for direct intervention by remote operators. It proposes a visualized emergency handling method and system based on a remote frame buffer protocol to solve the above problems.

[0011] The technical solution claimed by this invention is as follows:

[0012] A method for visualizing special situations based on a remote frame buffer protocol includes the following steps:

[0013] S1: The lane end installs and starts the VNC server based on the RFB protocol to provide a remote desktop. The lane emergency handling system integrates LibVNCClient to establish a connection with the VNC server port number corresponding to the lane end, so as to realize real-time control and visual access to the remote desktop.

[0014] S2: Install lane cameras at the lane end, configure the network environment of lane cameras based on the router, enable the RTSP live streaming protocol for lane cameras and provide RTSP live streaming address, and integrate FFMPEG to connect to the live streaming address to decode the video stream captured in real time by lane cameras.

[0015] S3: Use Ethernet to establish a communication link between the lane end and the emergency handling system.

[0016] Preferably, the lane emergency handling system uses a QT-developed graphical user interface to provide interface controls for remote desktop and live video display.

[0017] Preferably, S1 specifically includes the following steps:

[0018] S11: Install and start the VNC server on the lane side; integrate LibVNCClient into the lane emergency handling system.

[0019] S12: The lane emergency handling system is based on the integrated LibVNCClient and connects to the VN at the lane end. C Server port;

[0020] S13: The lane emergency handling system obtains frame buffer data from the remote desktop and generates an image;

[0021] S14: Display the generated image on the interface control;

[0022] S15: The interface controls listen for mouse and keyboard events on the remote desktop and send feedback to the VNC server.

[0023] Preferably, S2 specifically includes the following steps:

[0024] S21: Install lane cameras at the lane end and configure the network environment of the lane cameras based on the router;

[0025] S22: The lane camera enables the RTSP live streaming protocol and tests the availability of the live streaming protocol using VLC-related software.

[0026] S23: The video decoder provided by FFMPEG decodes the video stream generated by the lane camera;

[0027] S24: The lane emergency handling system acquires the frame buffer data of the lane camera video in the decoder and generates an image;

[0028] S25: Display the generated image on the interface control.

[0029] Preferably, the specific process of S3 is as follows: a communication link for the lane emergency handling system is established using Ethernet. The lane emergency handling system acts as the server. After startup, it listens to the communication port and waits for the client to connect. The lane end acts as the client and actively initiates a TCP connection request to the server for the communication port. After the TCP connection is established, the server and the client can communicate normally.

[0030] Preferably, the server and client exchange information via message messages. Each message is sent as a single message, without being split into packets. Unless otherwise specified, the message receiver must confirm the message processing result with the sender via a message within the response timeout period. If the message sender does not receive a response from the receiver within the response timeout period, the receiver is considered to have failed to process the message.

[0031] The present invention also provides a visual emergency handling system based on a remote frame buffer protocol, comprising a remote desktop module, a camera video playback module, and a communication link establishment module connected in sequence.

[0032] The remote desktop module is used to provide a lane-based remote desktop and enable the lane emergency handling system to control and visualize the remote desktop in real time.

[0033] The camera video playback module is used to enable the lane emergency handling system to play the video stream collected by the lane camera in real time.

[0034] The communication link establishment module is used to establish a communication link between the lane end and the lane emergency handling system.

[0035] Preferably, the lane-end system installs and starts a VNC server based on the RFB protocol to provide a remote desktop; the lane emergency handling system integrates LibVNCClient to realize real-time control and visual access to the remote desktop.

[0036] Preferably, a lane camera is installed at the lane end, the network environment of the lane camera is configured based on the router, the lane camera enables the RTSP live streaming protocol and provides the RTSP live stream address, and the lane special situation handling system integrates FFMPEG to connect to the live stream address and decodes the video stream captured in real time by the lane camera.

[0037] Preferably, the lane emergency handling system uses a QT-developed graphical user interface to provide interface controls for image display.

[0038] Beneficial effects

[0039] This invention provides a visual emergency handling method and system based on the remote frame buffer protocol. The lane-side terminal installs and starts a VNC server based on the RFB protocol, providing a remote desktop. The lane emergency handling system integrates LibVNCClient, establishing a connection with the VNC server port number corresponding to the lane-side terminal, enabling real-time control and visual access to the remote desktop. The lane emergency handling system can directly control and visually access the lane-side terminal, overcoming the limitations of traditional monitoring emergency handling programs that cannot proactively access emergency events. It enables the handling of most emergency events in the background, solving the problems of existing lane toll collection systems' difficulty in seamless integration with remote emergency handling systems and lack of support for remote operators. The system addresses the issue of direct intervention by personnel by installing lane cameras at the lane end, configuring the network environment of the lane cameras based on routers, enabling the lane cameras to use the RTSP live streaming protocol and providing RTSP live stream addresses. The lane emergency handling system integrates FFMPEG to connect to the live stream addresses and decodes the video streams captured in real time by the lane cameras. The RTSP live streaming protocol is highly versatile and can solve the problems of cross-platform implementation of audio and video and the compatibility of audio and video live streaming protocols. FFMPEG can achieve low-latency live video display and provides millisecond-level disconnection recovery to ensure communication effectiveness. Audio and video can be quickly restored after a disconnection, solving the problem of network transmission latency affecting communication efficiency in existing lane toll collection systems.

[0040] The lane emergency handling system uses a graphical user interface developed with QT, providing interface controls for image display. Using QT to develop a graphical user interface allows it to run in almost all system environments, making it highly versatile and solving the problem of cross-platform implementation of desktop interfaces.

[0041] The method and system provided by this invention offer flexible solutions for handling special situations in highway lanes, enabling seamless integration of toll collection services and remote video surveillance resources, while optimizing the traffic efficiency of unattended lanes.

[0042] This invention, a remote desktop and video control system based on VNC and FFMPEG, addresses the challenges posed by the surge in demand for remote processing and collaboration, the growing difficulties faced by traditional VNC technology, and the powerful capabilities of FFMPEG in multimedia processing. It follows the trend of technological convergence, innovatively solving multimedia processing problems in remote desktop applications and providing a more efficient, high-quality, and multifunctional remote emergency handling solution. FFMPEG enables low-latency live video display and provides millisecond-level disconnection recovery to ensure communication effectiveness. It selects the most commonly used video protocols and remote technologies in current business scenarios, encapsulating them for easy integration with existing services. It overcomes the limitations of traditional monitoring emergency handling programs in actively accessing emergency events, enabling the handling of most emergency events in the background. Based on IP network interaction and fully open-source C++ dependencies, it uses QT to develop a graphical user interface, ensuring compatibility with almost all system environments. Attached Figure Description

[0043] Figure 1 This is a flowchart of a visualization-based special situation handling method based on a remote frame buffer protocol in an embodiment of the present invention.

[0044] Figure 2 This is a schematic diagram of the communication data field in an embodiment of the present invention.

[0045] Figure 3 This is a flowchart illustrating the process of establishing a remote desktop in an embodiment of the present invention.

[0046] Figure 4 This is a flowchart illustrating the video playback process of the lane camera in an embodiment of the present invention.

[0047] Figure 5 This is a schematic diagram of the data frame format in an embodiment of the present invention. Specific implementation methods

[0048] To make the objectives, technical solutions, and advantages of the present invention clearer, the technical solutions will be further described clearly and completely below with reference to the accompanying drawings.

[0049] Example 1: A Visualized Special Situation Handling Method Based on Remote Frame Buffer Protocol

[0050] This embodiment provides a visual special situation handling method based on a remote frame buffer protocol, such as... Figure 1 As shown, it includes the following steps:

[0051] S1: The lane-side VNC server is installed and started based on the RFB protocol, providing a remote desktop. The lane emergency handling system integrates LibVNCClient to establish a connection with the VNC server port number corresponding to the lane-side, enabling real-time control and visual access to the remote desktop; such as Figure 3 As shown, the specific steps include the following:

[0052] S11: Install and activate VN at the lane end. C On the server side, the lane emergency handling system integrates LibVNCClient. In a specific embodiment of this invention, the machine to be controlled (i.e., the lane end) needs to have the VNC server installed and started. To achieve effective control and management of the lane end, the first step is to ensure that the VNC (Virtual Network Computing) server software is installed and successfully started on the lane end. This step is crucial because it builds a visual bridge from the control end to the controlled end, enabling administrators or users to cross network boundaries and view and operate the desktop environment of the controlled machine in real time. Ensuring successful service startup and stable operation can be verified by checking the service status or by directly attempting to connect from another computer.

[0053] S12: The lane emergency handling system connects to the VNC server port on the lane side based on the integrated LibVNCClient. In a specific embodiment of the invention, the lane emergency handling system integrates LibVNCClient (an open-source C library for VNC) to connect to the VNC server port number. LibVNCClient, as a powerful VNC client library, has its core function of establishing a robust connection with a remote VNC server, enabling real-time control and visual access to the remote desktop. One of the key steps in this process is accurately specifying the VNC server port number. The port number ensures that LibVNCClient can accurately find and access the target VNC service, whether it is the standard 5900 port or a custom-configured port. By carefully configuring the connection parameters, the flexibility and efficiency of LibVNCClient can be fully utilized to seamlessly connect to VNC servers worldwide, transcending network boundaries.

[0054] S13: The lane emergency handling system obtains frame buffer data from the remote desktop and generates an image; In a specific embodiment of the present invention, the lane emergency handling system obtains remote frame buffer data from the remote desktop and generates an image to be displayed on a cross-platform interface. Specifically, it obtains remote screen data through the RFB protocol, generates high-definition images, and ensures that these images can be seamlessly integrated and displayed in real time in various cross-platform interface applications. Whether it is Windows, macOS, or Linux operating systems, it can provide users with a smooth and consistent visual experience.

[0055] S14: Display the generated image on the interface control;

[0056] S15: The interface control listens to mouse and keyboard events on the remote desktop and feeds them back to the VCN server, enabling remote control rather than just viewing the screen. In specific embodiments of this invention, the VNC server can generally be installed on various systems with interfaces, such as Linux and Windows. Cross-platform interface listening transmits keyboard and mouse events via the RFB protocol. Using the QT cross-platform application development framework, we can efficiently achieve unified processing of keyboard and mouse events across different operating systems. The core of the conversion mechanism lies in mapping the captured diverse keyboard key presses and mouse actions, such as clicks, scrolling, and dragging, into a standardized event format that the RFB protocol can recognize and transmit through a series of carefully designed algorithms.

[0057] In a specific embodiment of the present invention, a VNC server is installed at the lane end, sharing the screen of the controlled host and passively controlled by the VNC Client. The emergency handling system integrates LibVNCClient (an open-source C library for developing VNC) to allow remote users to display and control the functions of the local computer through the VNC client, supporting multiple operating system platforms. The specific steps are as follows:

[0058] (1) Initialize the rfbClient connection object. ① Create an rfbClient object using rfbGetClient(8,3,4). ② Bind the GetPassword password writing and MallocFrameBuffer frame buffer screen image data processing methods to rfbClient. ③ Initialize timers containing functions such as WaitForMessage and HandleRFBServerMessage to handle screen updates, keyboard and mouse events, or other types of VNC server notifications.

[0059] (2) Connect to the rfbServer. ① Establish an asynchronous thread to handle connection operations and avoid freezing the interface. ② Set the password object; the GetPassword callback function handles the password object conversion and requires the format. ③ Set the address and port to connect to the server using ConnectToRFBServer and InitialiseRFBConnection. ④ After successful connection, allocate the framebuffer space of the rfbClient and modify the connection status to normal.

[0060] (3) Mouse and keyboard event sending and frame buffer screen image data processing. ① Received Qt key events are converted into RFB protocol keyboard key enumerations and sent via SendKeyEvent. ② Received Qt mouse events are converted into RFB protocol mouse key enumerations and sent via SendPointerEvent with the specified event and relative coordinates. ③ The frame buffer screen image data is used to iterate through each relevant area to generate an updated image, and the interface refresh function is called to refresh the updated image to the interface display area.

[0061] (4) Release rfbClient. ① The asynchronous thread waits to stop. ② Close the communication link using rfbCloseSocket. ③ Release the frameBuffer. ④ Release the remaining memory space of rfbClient using rfbClientCleanup.

[0062] In addition, regarding the synchronous waiting issue when connecting to rfbServer, it was found that there was an error in setting the synchronous / asynchronous flag in LibVNCClient. After modifying the source code of the sock_set_nonblocking function, it worked normally.

[0063] S2: Install lane cameras at the lane end, configure the network environment of the lane cameras based on the router, enable the RTSP live streaming protocol for the lane cameras and provide RTSP live stream addresses, the lane emergency handling system integrates FFMPEG to connect to the live stream address, and decodes the video stream captured in real time by the lane cameras; such as Figure 4 As shown, the specific steps include the following:

[0064] S21: A lane camera is installed at the lane end and the network environment of the lane camera is configured based on the router; In a specific embodiment of the present invention, the lane end configures the network environment of the lane camera based on the router and verifies the configured network environment.

[0065] S22: The lane camera enables the RTSP live streaming protocol and tests whether the live streaming protocol is available using VLC-related software. If it is not available, check the camera configuration and network. In a specific embodiment of the present invention, the lane camera operates normally and provides an RTSP live streaming address. It can be directly tested by playing the live stream from another computer using VLC or other players.

[0066] S23: The video decoder provided by FFMPEG decodes the video stream generated by the lane camera. In a specific embodiment of the present invention, the lane emergency handling system integrates the FFMPEG connection live stream address and utilizes FFMPEG's powerful transcoding capabilities to perform timely transcoding operations on the original live stream according to the needs of the target platform or device, such as adjusting the resolution, bitrate, or encoding / decoding format to adapt to different network environments and playback terminals. In a specific embodiment of the present invention, the target platform or device refers to the operating system with the lane emergency handling system software installed, such as a small-screen system or a system with poor network connectivity.

[0067] S24: The lane emergency handling system acquires frame buffer data from the lane camera video in the decoder to generate an image; in a specific embodiment of the invention, acquiring the remote frame buffer of the camera video in the video decoder to generate an image for display on the cross-platform interface specifically involves: the video decoder efficiently extracting the real-time video stream captured by the camera, processing it through advanced frame buffering technology to ensure high quality and low latency for each frame. Subsequently, these refined video frames are converted into clear and detailed images, making the image display on the QT cross-platform interface both fast and smooth.

[0068] S25: Display the generated image on the interface control.

[0069] In a specific embodiment of the present invention, after the lane camera is successfully deployed, a live stream similar to the RTSP protocol is provided for verification. Then, FFMPEG is used for efficient video decoding and playback (such as H.264, HEVC, etc.), reducing bandwidth consumption and improving adaptability to network environment fluctuations.

[0070] (1) Creating the video display area. ① Create an area component for display. ② Create a QLabel within it for display and set a default background image. ③ Create a decoding thread and assign it the live stream address.

[0071] (2) Parsing of Threaded Video and Audio Streams. ① Set the transmission mode and timeout in the RTSP protocol using av_dict_set. ② Open the live stream address using avformat_open_input. ③ Obtain the stream from the opened address using avformat_find_stream_info. ④ Obtain the video stream from the stream and decode it, generating the corresponding format from a frame and providing it to the interface controls for display.

[0072] (3) Destroy the thread and release memory space of the internal QLabel display.

[0073] S3: An Ethernet communication link is established between the lane-side and the emergency handling system. In a specific embodiment of the invention, an Ethernet communication link is established between the background emergency handling system and the client. The background emergency handling system acts as the server. After the server starts, it listens on the communication port and waits for the client (i.e., the lane-side) to connect. The client actively initiates a TCP connection request to the server for the communication port. After the TCP connection is established, the server and the client can communicate normally. The server and the client exchange information via message packets. Each message is sent as a single packet, without packetization. Unless otherwise specified, the message receiver must confirm the message processing result with the sender within the response timeout period. If the message sender does not receive a response from the receiver within the response timeout period, the receiver's processing is considered to have failed.

[0074] TCP communication consists of eight parts: start-of-frame marker, protocol version number, frame sequence number, message body length, message content, and CRC checksum.

[0075] 1. Data frame format as follows Figure 5 As shown.

[0076] 2. Description of each data field in the data frame as follows: Figure 2 As shown. Unless otherwise specified, all data uses unsigned integer encoding. Data represented in bytes is in big-endian format, with the most significant byte first and the least significant byte last. Undefined or reserved parameters are filled with the default value 0x00.

[0077] 3. The message body DATA field uses a JSON string for sending and receiving messages. The message body DATA field is in string format. Data transmission and sending are based on six parts: "Message Category, Message Code, Timestamp, GUID, Response Required, and Message Content." The message code content is as follows:

[0078] 2000 is for retrieving the lane list.

[0079] 2001 is the listening lane.

[0080] 2002 was used to close special operations.

[0081] 2003 for obtaining lane status information

[0082] 2004 was used to query basic information on toll stations nationwide.

[0083] 2005 is the login interface

[0084] After obtaining the lane list information, you can get the remote connection information related to that lane and the camera information that needs to be displayed.

[0085] In a specific embodiment of the present invention, a highway emergency handling software in a certain province currently employs the method provided by the present invention to achieve remote monitoring and emergency handling functions for highway lane software. The emergency handling software is coded using the Qt Creator development tool. Qt is a cross-platform C++ framework (C++ library) primarily used to develop graphical user interface (GUI) programs, and can also develop command-line user interface (CUI) programs without a user interface. The emergency handling software uses FFMPEG to implement RTSP live video processing. FFMPEG is a powerful open-source cross-platform multimedia framework mainly used for processing audio and video content, including but not limited to encoding, decoding, transcoding, multiplexing, demultiplexing, streaming, filtering, and playback. RTSP (Real Time Streaming Protocol) is an application layer protocol used to control the transmission of real-time data, especially multimedia data such as audio and video streams. Most camera equipment used in the transportation field supports this protocol, requiring no additional development. The special monitoring software uses VNC (Virtual Network Computing) for remote monitoring. VNC is a widely used remote desktop sharing system that allows users to remotely access and control another computer's desktop environment via a network connection. VNC is based on the RFB (Remote Framebuffer) protocol, which is used to transmit the content displayed on the remote computer's screen, as well as mouse and keyboard events. The software uses LibVNCClient to provide the ability for the VNC server to establish connections and communicate, allowing developers to build their own VNC client applications. FFMPEG is a powerful open-source computer program suite for processing multimedia data, including video, audio, and other types of media files. It can not only record, convert, and stream audio and video, but also supports a wide range of codecs and file formats, covering almost all known media types.

[0086] Example 2: Visualized Situation Handling System Based on Remote Frame Buffer Protocol

[0087] This embodiment provides a visual emergency handling system based on a remote frame buffer protocol, including a remote desktop module, a camera video playback module, and a communication link establishment module connected in sequence.

[0088] The remote desktop module provides a lane-based remote desktop and enables the lane emergency handling system to control and visualize the remote desktop in real time. Considering cross-platform compatibility and universality, RFB is chosen as the underlying protocol for the remote desktop module. In a specific embodiment of the invention, the lane-based system installs and starts a VNC server based on the RFB protocol to provide the remote desktop. The lane emergency handling system integrates LibVNCClient to enable real-time control and visualization of the remote desktop.

[0089] The camera video playback module is used to enable the lane emergency handling system to play the video stream captured by the lane camera in real time. Considering the universality of the live streams from various cameras, the camera video playback module adopts the relatively common RTSP for live stream transmission. In a specific embodiment of the present invention, a lane camera is installed at the lane end, and the network environment of the lane camera is configured based on the router. The lane camera enables the RTSP live streaming protocol and provides an RTSP live stream address. The lane emergency handling system integrates FFMPEG to connect to the live stream address and decodes the video stream captured in real time by the lane camera.

[0090] The communication link establishment module is used to establish a communication link between the lane end and the lane emergency handling system; the interface display uses QT as a graphical user interface development tool; in a specific embodiment of the present invention, the lane emergency handling system uses QT to develop a graphical user interface and provides interface controls for image display.

[0091] The above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail through the above preferred embodiments, those skilled in the art should understand that various changes can be made to it in form and detail without departing from the scope defined by the claims of the present invention.

Claims

1. A method for visualizing special situations based on a remote frame buffer protocol, characterized in that, Includes the following steps: S1: The lane end installs and starts the VNC server based on the RFB protocol to provide a remote desktop. The lane emergency handling system integrates LibVNCClient to establish a connection with the VNC server port number corresponding to the lane end, so as to realize real-time control and visual access to the remote desktop. S2: Install lane cameras at the lane end, configure the network environment of lane cameras based on the router, enable the RTSP live streaming protocol for lane cameras and provide RTSP live streaming address, and integrate FFMPEG to connect to the live streaming address to decode the video stream captured in real time by lane cameras. S3: Use Ethernet to establish a communication link between the lane end and the emergency handling system.

2. The visual emergency handling method based on the remote frame buffer protocol according to claim 1, characterized in that, The lane emergency handling system uses a QT-developed graphical user interface, providing interface controls for remote desktop and live video display.

3. The visualization-based special situation handling method based on the remote frame buffer protocol according to claim 2, characterized in that, S1 specifically includes the following steps: S11: Install and start the VNC server on the lane side; integrate LibVNCClient into the lane emergency handling system. S12: The lane emergency handling system connects to the VNC server port at the lane end based on the integrated LibVNCClient; S13: The lane emergency handling system obtains frame buffer data from the remote desktop and generates an image; S14: Display the generated image on the interface control; S15: The interface controls listen for mouse and keyboard events on the remote desktop and send feedback to the VNC server.

4. The visualization-based special situation handling method based on the remote frame buffer protocol according to claim 2 or 3, characterized in that, S2 specifically includes the following steps: S21: Install lane cameras at the lane end and configure the network environment of the lane cameras based on the router; S22: The lane camera enables the RTSP live streaming protocol and tests the availability of the live streaming protocol using VLC-related software. S23: The video decoder provided by FFMPEG decodes the video stream generated by the lane camera; S24: The lane emergency handling system acquires the frame buffer data of the lane camera video in the decoder and generates an image; S25: Display the generated image on the interface control.

5. The visualization-based special situation handling method based on the remote frame buffer protocol according to claim 4, characterized in that, The specific process of S3 is as follows: A communication link for the lane emergency handling system is established using Ethernet. The lane emergency handling system acts as the server. After startup, it listens to the communication port and waits for client connections. The lane end acts as the client and actively initiates a TCP connection request to the server for the communication port. After the TCP connection is established, the server and the client can communicate normally.

6. The visualization-based special situation handling method based on the remote frame buffer protocol according to claim 5, characterized in that, The server and client exchange information via message messages. Each message is sent as a single message, without being split into packets. Unless otherwise specified, the message receiver must acknowledge the message processing result to the sender via a message within the response timeout period. If the message sender does not receive a response from the receiver within the response timeout period, the receiver is considered to have failed to process the message.

7. A visual emergency handling system based on a remote frame buffer protocol, characterized in that, It includes a remote desktop module, a camera video playback module, and a communication link establishment module connected in sequence; The remote desktop module is used to provide a lane-based remote desktop and enable the lane emergency handling system to control and visualize the remote desktop in real time. The camera video playback module is used to enable the lane emergency handling system to play the video stream collected by the lane camera in real time. The communication link establishment module is used to establish a communication link between the lane end and the lane emergency handling system.

8. The visualization-based special situation handling system based on the remote frame buffer protocol according to claim 7, characterized in that, The lane-end system installs and starts a VNC server based on the RFB protocol to provide a remote desktop; the lane emergency handling system integrates LibVNCClient to realize real-time control and visual access to the remote desktop.

9. The visualization-based special situation handling system based on the remote frame buffer protocol according to claim 7, characterized in that, Lane cameras are installed at the lane end. The network environment of the lane cameras is configured based on the router. The lane cameras enable the RTSP live streaming protocol and provide RTSP live stream addresses. The lane emergency handling system integrates FFMPEG to connect to the live stream address and decodes the video stream captured in real time by the lane cameras.

10. The visualization-based special situation handling system based on the remote frame buffer protocol according to claim 7, characterized in that, The lane emergency handling system uses a graphical user interface developed with QT, providing interface controls for image display.

Images