A lane special situation handling system and method based on OpenHarmony

Abstract

The application discloses a lane special situation handling system and method based on OpenHarmony, and the system comprises a user login management module, which is used for verifying whether a logged user account is legal, and binding a highway toll lane to the legal logged user account; a special situation data acquisition module, which is used for establishing a WebSocket long connection with a highway toll system by using OpenHarmony technology when the user account is in a working state, and acquiring special situation data existing in the bound highway toll lane through a subscribed WebSocket event; a lane special situation verification module, which is used for displaying the special situation data and collected video images of the bound highway toll lane for the user to verify the lane special situation when the special situation data is received; and a lane device operation module, which is used for establishing communication with different lane devices by using OpenHarmony technology, and receiving lane device operation instructions issued by the user to complete the operation of the lane device in the lane special situation verification process. The application can realize that personnel can move to verify and effectively control numerous lane manufacturer model devices when a special situation occurs in the lane.

Description

Technical Field

[0001] This application relates to the field of highway toll collection technology, specifically to a lane emergency handling system and method based on OpenHarmony. Background Technology

[0002] Toll collection is one of the core tasks of highway operation and management. The toll collection system is an information tool for toll collectors to complete their work. However, many special situations may arise during the process that require handling (such as: vehicle-card mismatch, abnormal vehicle type, green / preferential vehicles, lost toll cards, no cards, damaged cards, timeouts, etc.). Only after verification by toll collectors, toll station managers, and drivers, and after the situation is clarified, will toll collection be processed and the vehicle released. Especially against the backdrop of the complete elimination of provincial border toll stations on highways, toll collectors may even need to go to the lanes to verify information and control the complex related equipment. They must collect tolls effectively, avoid traffic congestion and impair traffic efficiency, and, most importantly, prioritize their own safety to prevent accidents.

[0003] Therefore, it is necessary to develop a mobile emergency response system for toll collectors that can effectively manage numerous vehicle models from various manufacturers within the toll lanes. This system would serve as an effective supplement to the toll collection system, enabling better, faster, and more efficient toll collection. OpenHarmony operating system is a domestically developed next-generation operating system with features and advantages such as distributed soft bus, distributed task scheduling, device virtualization, and a hierarchical security architecture. It can be used to develop products adaptable to multiple terminals, allowing for one-time development and multi-terminal deployment, achieving integrated hardware and software capabilities. Combining the features and advantages of OpenHarmony's ArkUI development framework, providing toll collectors with a handheld, multi-terminal emergency response system will effectively improve their work efficiency. Summary of the Invention

[0004] To enable personnel to move around and effectively manage equipment from numerous manufacturers and models in highway toll lanes during special circumstances, this application provides a lane emergency handling system and method based on OpenHarmony.

[0005] Firstly, this application provides a lane emergency response system based on OpenHarmony, comprising:

[0006] The user login management module is used to verify the legitimacy of logged-in user accounts using OpenHarmony's ATM permission management technology, bind legitimate logged-in user accounts to highway toll lanes, and display that the currently logged-in user account is in working status.

[0007] The special incident data acquisition module is used to create a WebSocket using OpenHarmony when the user account is in working status, establish a long WebSocket connection with the highway toll system, and obtain special incident data of the highway toll lane bound to the user account sent by the highway toll system through subscribed WebSocket events; the special incident data refers to the vehicle data and ETC card association data under special circumstances.

[0008] The lane emergency verification module is used to obtain the video image of the bound highway toll lane when emergency data is received; it uses the UI framework components of OpenHarmony to design and display the emergency data and the video image of the bound highway toll lane, and provides a button for users to click to provide feedback on whether the lane emergency verification is successful or not; it sends the result of the lane emergency verification feedback by the user through the button to the highway toll system through a created WebSocket;

[0009] The lane device operation module is used to communicate with lane devices that support the IoT standard using the MQTT or IoT gateway's ModBus protocol; for lane devices that do not support the IoT standard, it uses the OpenHarmony NDK framework to communicate with the lane devices according to their native protocol; and it uses OpenHarmony's UI framework components to design independent operation buttons for each lane device. During lane special situation verification, it receives lane device operation commands issued by the user using the operation buttons to complete the operation of the lane device.

[0010] By adopting the above solution, compared to the complex, data-intensive, and computationally demanding highway toll collection system hosted on a mainframe, the solution utilizes OpenHarmony technology to establish a special situation data acquisition module that can communicate bidirectionally with the highway toll collection system and obtain lane special situation data in a timely manner, and a lane special situation verification module that can display special situation data. This allows the solution to be mounted on a portable handheld terminal for easy on-site verification by staff, while also providing feedback on the authenticity of special situations to the toll collection system. Furthermore, OpenHarmony technology enables communication with different lane devices, allowing for effective control of multiple different models of lane devices based on user-issued operation commands.

[0011] Preferably, the special situation data acquisition module is further used to establish communication with the highway toll system using the HTTP module of OpenHarmony and adopting the HTTP request / response interaction mode to acquire special situation verification auxiliary data; the special situation verification auxiliary data includes: vehicle flow data, gantry flow data, and trajectory data.

[0012] By adopting the above solution, considering the complex lane special situations, staff may need to obtain more information related to lane special situations. They can use OpenHarmon's HTTP module to obtain more detailed vehicle trajectory data, past payment records, and basic vehicle information, and even the current lane's vehicle queuing status and congestion status, to assist logged-in users in further judging and deciding how to handle the special situation.

[0013] Preferably, it also includes: a work handover module, used to locate the handheld terminal device of the personnel to be on duty using OpenHarmony's distributed soft bus, interconnect the handheld terminal device of the current personnel on duty with the handheld terminal device of the personnel to be on duty using OpenHarmony's unified device networking and topology management technology, and synchronize the special situation data and lane equipment status data stored in the distributed memory database of OpenHarmony on the handheld terminal device of the current personnel on duty to the terminal device of the personnel to be on duty; the handheld terminal device of the current personnel on duty refers to the handheld terminal device logged in corresponding to the account currently in working status; the terminal device of the personnel to be on duty refers to the handheld terminal device logged in corresponding to the user account whose bound target is the same as the highway toll lane bound to the account currently in working status and which has issued a login request.

[0014] By adopting the above solution and leveraging OpenHarmony's distributed technology, data synchronization can be achieved across multiple handheld terminal devices equipped with the lane emergency response system. This enables data sharing and collaborative work, allowing the real-time transfer of any unfinished tasks and subsequent data from the current shift personnel to the next shift, thus achieving rapid shift handover and ensuring timely handling of lane emergencies.

[0015] Preferably, acquiring the video image of the bound toll lane specifically includes: establishing communication with the bound highway toll lane video image acquisition device based on the RTSP protocol to acquire the real-time video image data of the bound highway toll lane; and rendering and displaying the video image using the XComponent component of OpenHarmony.

[0016] By adopting the above scheme, considering that lane camera devices generally support the RTSP protocol, the RTSP protocol is selected to establish communication with the bound toll lane video image acquisition device to ensure timely acquisition of lane video images. The acquired lane video images are then rendered and displayed to enhance the recognizability of the lane video images, thereby assisting staff in verifying and judging special situations.

[0017] Preferably, the lane emergency verification module is further configured to set an emergency data session confirmation button via the OpenHarmony UI framework component. When the user's click on the emergency data session confirmation button is detected,

[0018] Use OpenHarmony's CALL module to call toll booths or drivers.

[0019] By adopting the above solution, and considering some complex and special situations where it is necessary to call toll station managers or drivers to request assistance or verify issues, the OpenHarmony CALL module is used to realize automated call management functions.

[0020] Preferably, the lane special situation verification module is further configured to set lane image management buttons through the UI framework components of OpenHarmony. The lane image management buttons include a lane image playback button and a lane image screenshot button. When a user clicks the lane image playback button, the module manages the playback of real-time video images through OpenHarmony's AVPlayer. When a user clicks the lane image screenshot button, the module takes a screenshot of the video image through OpenHarmony's screenshot interface, converts it to JPEG format, and transmits the screenshot to the highway toll collection system using the POST method via OpenHarmony's HTTP module.

[0021] By adopting the above solution, and considering that staff can use OpenHarmony's technology to manage video playback by speeding up or pausing the video images during special situation verification, and capture or record video images as evidence for special situation verification and feed them back to the toll system when necessary, the solution ensures timely feedback on verified issues.

[0022] Preferably, the special situation data acquisition module is further configured to add an SM2 signature from the OpenHarmony algorithm library to the HTTP header of each request sent to the highway toll system so that the highway toll system can verify the signature based on the SM2 signature in the HTTP header.

[0023] By adopting the above scheme, and considering that emergency handling involves financial transactions, a security mechanism of header signature verification is added to ensure the security of data transmission and processing.

[0024] Secondly, this application provides a lane emergency handling method based on OpenHarmony, including:

[0025] The system utilizes OpenHarmony's ATM access control technology to verify the legitimacy of logged-in user accounts, binds legitimate user accounts to highway toll lanes, and displays that the currently logged-in user account is in an active working state.

[0026] When the user account is in working status, a WebSocket is created using OpenHarmony, and a long WebSocket connection is established between the created WebSocket and the highway toll system. The special situation data of the highway toll lane bound to the user account is obtained by subscribing to the WebSocket events.

[0027] Upon receiving emergency data, the system acquires the video image of the associated highway toll lane; it uses OpenHarmony's UI framework components to design and display the emergency data and the associated highway toll lane video image, and provides a button for users to click to provide feedback on whether the lane emergency verification has passed; it then uses a created WebSocket to send the result of the user's feedback on whether the lane emergency verification has passed to the highway toll system.

[0028] By utilizing the UI framework components of OpenHarmony, an independent operation button is designed for each lane device. During the lane special situation verification process, the operation button is used to receive the lane device operation command issued by the user to complete the operation of the lane device.

[0029] By adopting the above scheme, OpenHarmony technology is used to achieve mutual communication with the highway toll collection system, obtain special situation data of the highway toll lane for verification, and feed back the verification results to the highway toll collection system. During the verification process, OpenHarmony technology is used to achieve communication with equipment in different lanes, complete the operation control of different lanes, and complete the handling of special situations.

[0030] Thirdly, this application provides a computer-readable storage medium including a stored computer program, wherein the computer program, when running, controls the device where the computer-readable storage medium is located to perform the method described above.

[0031] Fourthly, this application provides a computer device, the computer device including a memory, a processor and a program stored in the memory and executable thereon, the program being executed by the processor to implement the steps of the method described above.

[0032] In summary, this application has the following beneficial effects:

[0033] 1. Based on the high performance and low latency characteristics of OpenHarmony technology, a special situation data acquisition module and a lane special situation verification module are designed to enable bidirectional communication with the highway toll collection system and timely acquisition of lane special situation data. The module design, which does not require a large amount of storage space, can be mounted on a mobile handheld terminal, making it convenient for staff to complete on-site verification based on the displayed special situation data. At the same time, during the lane special situation verification process, OpenHarmony's support and flexibility for multiple device types are utilized to achieve stable communication with different lane devices and effective control of multiple different models of lane devices. This improves the accuracy, convenience, and real-time performance of lane special situation handling, enhances the work efficiency of toll collectors, and avoids dangerous operations on the lanes, ensuring their personal safety.

[0034] 2. Utilizing OpenHarmony's distributed technology, communication connections are established between terminal devices mounted on multiple handheld lane emergency response systems to achieve data sharing and collaborative work. This ensures that any unfinished situations and subsequent data from staff leaving their shifts are transferred to the next staff in real time, enabling rapid shift handover and ensuring timely handling of lane emergencies.

[0035] 3. Utilize OpenHarmony to provide multiple security mechanisms to ensure the security of lane emergency data transmission and lane emergency handling involving financial transactions. Attached Figure Description

[0036] Figure 1 This is a schematic diagram of the lane emergency response system based on OpenHarmony described in a specific embodiment;

[0037] Figure 2 This is a diagram illustrating the communication between the OpenHarmony-based lane emergency handling system, the highway toll collection system, the toll lane video image acquisition device, and the equipment in different lanes, as described in a specific embodiment.

[0038] Figure 3 This is a flowchart of the lane emergency handling method based on OpenHarmony described in a specific embodiment. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0040] like Figure 1As shown in the figure, this application discloses a lane emergency handling system based on OpenHarmony, specifically including: a user login management module 1, an emergency data acquisition module 2, a lane emergency verification module 3, and a lane equipment operation module 4, all mounted on a handheld terminal device (such as a smartphone, tablet, etc.). The specific module design is as follows:

[0041] Considering the monetary issues involved in handling special situations in highway toll lanes, the lane emergency response system design must ensure the legitimacy and compliance of system login users (generally highway toll lane staff). Therefore, a user login management module 1 is set up to verify the legitimacy of logged-in user accounts using OpenHarmony's ATM permission management technology, bind legitimate logged-in user accounts to highway toll lanes, and display that the currently logged-in user account is on duty. It is also used to design user login and logout buttons using OpenHarmony's UI framework components.

[0042] Specifically, OpenHarmony's ATM access control technology is used for TokenID verification to confirm the login user's employee ID, password, application APL level, and other information. Besides user account security verification, accurate time is also a crucial technical factor for correct toll collection. Therefore, the user login management module 1 also uses OpenHarmony's RTC real-time clock to synchronize the time after successful user login, ensuring accuracy. Each logged-in user account is bound to the highway toll lane number according to scheduling requirements.

[0043] The special situation data acquisition module 2 is used to create a WebSocket using OpenHarmony when the user account is in working status, establish a long WebSocket connection between the created WebSocket and the highway toll system, and obtain special situation data of the highway toll lane bound to the user account sent by the highway toll system through subscribed WebSocket events.

[0044] Specifically, using the highway toll collection system as the server, it subscribes to WebSocket events such as open, message, close, and error. Through the subscribed message event, it obtains special situation data in JSON format sent by the highway toll collection system and bound to the highway toll lane. This special situation data refers to the association data between vehicle data (such as license plate number, vehicle model, vehicle type, number of axles, vehicle weight, etc.) and the ETC card (card type, balance, billing information, etc.) under special circumstances. Special circumstances include no license plate, no vehicle model, inconsistent vehicle model, vehicle already transacted, exceeding limits (e.g., weight), ETC card and OBU vehicle mismatch, invalid ETC card entry, insufficient ETC card balance, and ETC card billing failure.

[0045] The lane emergency verification module 3 is used to obtain the video image of the bound highway toll lane when receiving emergency data; to design and display the emergency data and the video image of the bound highway toll lane using the UI framework components of OpenHarmony, and to provide a button for users to click to provide feedback on whether the lane emergency verification is successful or not; and to send the result of the lane emergency verification feedback provided by the user through the button to the highway toll system through the created WebSocket.

[0046] Specifically, acquiring the video images of the bound toll lane includes: establishing communication with the bound highway toll lane video image acquisition device based on the RTSP protocol, acquiring the real-time video image data of the bound highway toll lane, and using the XComponent component of OpenHarmony to construct a surface to render and display the video images in order to enhance the recognition of the real-time video image data of the highway toll lane.

[0047] The UI framework components of OpenHarmony are used to design and display special situation data and the associated video images of the highway toll lane. A button is provided for users to click and provide feedback on whether the special situation has been verified. Specifically, a display window is created using OpenHarmony's UI framework components. The window is divided into three areas: the first area displays the special situation type (the specific special situation) and the operation button (the operation button for verification); the second area is a video intercom area, used to display the associated video image data of the highway toll lane; the third area displays the special situation data, specifically including license plate number, vehicle type, vehicle category, card type, number of axles, vehicle weight, weight limit, etc.

[0048] The process of sending the lane emergency verification result (whether it passed or failed) to the highway toll collection system via a created WebSocket involves the following steps: After the user verifies the special situation in the toll lane against the displayed lane emergency data and video images, the user sends the verification result via the WebSocket's `send` method to the highway toll collection system. The toll collection system records this information and sends an ACK confirmation message back to the lane emergency verification module, forming a closed loop for emergency handling. For example, if, after verification by the logged-in user, a vehicle without a license plate is indeed found in the toll lane, the verification is considered successful, and the verification information is sent back to the toll collection system.

[0049] During special situation verification, staff need to control lane equipment from different manufacturers, such as barrier gates, toll displays, weighing platforms, license plate recognition devices, and vehicle model recognition devices, to assist in completing highway lane toll collection. To achieve effective control of multiple devices, the system design needs to be functionally divided into a two-layer architecture. The first layer is the device access layer, which establishes communication connections with different devices. The second layer is the business interaction layer, which issues control commands to control the devices based on special circumstances. Therefore, a lane equipment operation module 4 is set up. For lane equipment supporting the IoT standard, it communicates with the lane equipment using MQTT or the ModBus protocol of the IoT gateway. For lane equipment not supporting the IoT standard, it uses the OpenHarmony NDK framework to communicate with the lane equipment according to the lane equipment's native protocol. This enables communication reporting, subscription, and distribution, establishes connections with different lane equipment, and acquires or sends data in real time. The lane equipment operation module 4 also uses the OpenHarmony UI framework components to design independent operation buttons for each lane equipment. During lane special situation verification, it receives lane equipment operation commands issued by the user using these buttons to complete the operation of the lane equipment. Specifically, the UI framework ArkUI, provided by OpenHarmony, is used to construct the graphical representation of each lane device. Different operation buttons are created for each lane device graphic for toll collectors to operate. The system receives operation commands from users using these buttons to complete the operation of the lane devices. Event handling functions bind the operation actions to the communication and interaction with the device hardware, updating the interface display when the state changes, providing toll collectors with a real-time, immersive operating experience.

[0050] In this system, user-issued lane device operation commands via operation buttons are triggered by button events, which then send the corresponding commands to the lane devices through established communication. To facilitate the specific invocation process for different devices, lane device operation module 4 utilizes the service componentization technology of the OpenHarmony microservice framework to design independent logical service units for the control of each lane device, enabling each device to perform specific business functions (such as raising and lowering the barrier gate and displaying tickets). These service components are dynamically configured, managed, and loaded through configuration files, eliminating the need to redeploy the entire application system.

[0051] In one specific embodiment, for some complex special situations, toll collectors may need vehicle passage flow data, gantry flow data, trajectory data, etc., to support their decision-making in special situations. The special situation data acquisition module 2 in the system is also used to establish communication with the highway toll system using the OpenHarmony HTTP module (@ohos.net.http module) in an HTTP request / response interaction mode, and to obtain special situation verification auxiliary data through the GET method. Each HTTP request includes parameters such as license plate number, time range, highway mileage marker, and toll station number as query conditions. The special situation verification auxiliary data includes: vehicle passage flow data, gantry flow data, and trajectory data.

[0052] To ensure the security of the interaction process, a security mechanism needs to be added during the HTTP session. The special situation data acquisition module is also used to add the SM2 signature from the OpenHarmony algorithm library to the HTTP header of each request sent to the highway toll system so that the highway toll system can verify the signature based on the SM2 signature in the HTTP header.

[0053] In one specific embodiment, to ensure the handover of work, the system further includes:

[0054] The work handover module 5 is used to locate the handheld terminal devices of personnel awaiting duty using OpenHarmony's distributed soft bus, and to interconnect the handheld terminal devices of the currently on-duty personnel and the personnel awaiting duty using OpenHarmony's unified device networking and topology management technology. It also synchronizes data such as special situation data, lane equipment status data, on-duty personnel information, and system configuration parameters stored in OpenHarmony's distributed memory database on the currently on-duty personnel's handheld terminal device to the personnel awaiting duty's terminal device. The currently on-duty personnel's handheld terminal device refers to the handheld terminal device logged in by the account currently in working status; the personnel awaiting duty's terminal device refers to the handheld terminal device logged in by a user account whose binding target is the same as the highway toll lane bound to the currently working account and which has issued a login request.

[0055] Specifically, synchronizing the special situation data, lane equipment status data, duty personnel information, system configuration parameters, and other data stored in the OpenHarmony distributed memory database on the handheld terminal device of the current duty personnel to the terminal device of the personnel to be on duty involves: using the @ohos.data.distributedDataObject module to add the special situation data, lane equipment status data, duty personnel information, system configuration parameters, and other data stored in the OpenHarmony distributed memory database on the handheld terminal device of the current duty personnel to the synchronization network, changing the monitoring object data to the terminal device of the personnel to be on duty, and finally achieving data synchronization.

[0056] In one specific embodiment, in order to better handle complex special situations, users (toll station staff) often need to communicate with toll stations or drivers. The lane special situation verification module 3 in the system is also used to set a special situation data session confirmation button through the UI framework component of OpenHarmony. When the operation of the user clicking the special situation data session confirmation button is detected, the toll station or driver is dialed through the CALL module of OpenHarmony.

[0057] In one specific embodiment, a user may need to carefully examine the video images of the toll lane to complete emergency verification and operational decisions. The lane emergency verification module 3 in the system is also used to set several lane image management buttons (including lane image playback buttons, lane image screenshot buttons, etc.) through the UI framework components of OpenHarmony. When the user clicks the lane image playback button, the system manages the playback of the video image in real time through OpenHarmony's AVPlayer. When the user clicks the lane image screenshot button, the system takes a screenshot of the video image through OpenHarmony's screenshot interface, converts it to JPEG format, and uses OpenHarmony's HTTP module to send the screenshot of the video image to the highway toll system using the POST method.

[0058] like Figure 2 As shown, during the handling of special situations, the system communicates with the highway toll collection system to complete the acquisition of special situation data and the feedback of special situation data verification results; the system communicates with the bound toll lane video image acquisition device to complete the acquisition of video image data and the control of video image playback operation; the system communicates with several different lane devices to complete the acquisition of lane device status data and the control of lane devices.

[0059] like Figure 3 As shown in the figure, this application discloses a lane emergency handling method based on OpenHarmony, the specific steps of which include:

[0060] S1. Detect the legitimacy of user login and bind a specific highway toll lane to the legitimate login user.

[0061] Specifically, OpenHarmony's ATM access control technology is used to verify the legitimacy of logged-in user accounts, bind legitimate user accounts to specific highway toll lanes, and display that the user account is in working status.

[0062] S2. When the user account is in working status, obtain the special situation data of the toll lane of the highway.

[0063] Specifically, after logging in with a user account, a WebSocket is created using OpenHarmony. The created WebSocket establishes a long WebSocket connection with the highway toll collection system. The system obtains the special data sent by the highway toll collection system and bound to the highway toll lane through the message event in the subscribed WebSocket event.

[0064] S3. Display special situation data, obtain the user's verification results of lane special situations, and feed back the verification results to the highway toll collection system.

[0065] Specifically, upon receiving emergency data, the system acquires the video image of the associated highway toll lane; it uses OpenHarmony's UI framework components to design and display the emergency data and the associated highway toll lane video image, and provides a button for users to click to provide feedback on whether the lane emergency verification has passed; and it uses a created WebSocket to send the result of the user's feedback on whether the lane emergency verification has passed to the highway toll system.

[0066] S4. During the lane special situation verification process, obtain the lane equipment operation instructions issued by the user to complete the operation of the lane equipment.

[0067] During the lane emergency verification process, communication is established with the lane equipment, and operation instructions issued by the user are received to complete the operation of the lane equipment.

[0068] To ensure the timeliness of emergency response and avoid interruptions due to toll collectors leaving get off work, the method further includes:

[0069] S5. When the user leaves work, complete the synchronous interaction of special situation data and lane equipment status data when handing over to the user on duty.

[0070] Specifically, when a user clicks the logout button to leave work, OpenHarmony's distributed soft bus is used to locate the handheld terminal device of the person waiting to be on duty. OpenHarmony's unified device networking and topology management technology is used to interconnect the handheld terminal device of the currently on duty person with the handheld terminal device of the person waiting to be on duty. Data such as special situation data, lane equipment status data, on-duty personnel information, and system configuration parameters stored in OpenHarmony's distributed memory database on the currently on duty person's handheld terminal device are synchronized to the terminal device of the person waiting to be on duty.

[0071] This application also discloses a computer-readable storage medium.

[0072] Specifically, the computer-readable storage medium stores a computer program that can be loaded by a processor and executed, such as the lane emergency handling method based on OpenHarmony described above. The computer-readable storage medium includes, for example, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0073] This application also discloses a computer device.

[0074] Specifically, the computer device includes a memory and a processor, with the memory storing a computer program that can be loaded by the processor and executed to perform the aforementioned lane emergency handling method based on OpenHarmony.

[0075] The above are all preferred embodiments of this application and are not intended to limit the scope of protection of this application. Any feature disclosed in this specification (including the abstract and drawings) may be replaced by other equivalent or similar features unless specifically stated otherwise. That is, unless specifically stated otherwise, each feature is only one example of a series of equivalent or similar features.

Claims

1. A lane emergency response system based on OpenHarmony, characterized in that, include: The user login management module is used to verify the legitimacy of logged-in user accounts using OpenHarmony's ATM permission management technology, bind legitimate logged-in user accounts to highway toll lanes, and display that the currently logged-in user account is in working status. The special incident data acquisition module is used to create a WebSocket using OpenHarmony when the user account is in working status, establish a long WebSocket connection with the highway toll system, and obtain special incident data of the highway toll lane bound to the user account sent by the highway toll system through subscribed WebSocket events; the special incident data refers to the vehicle data and ETC card association data under special circumstances. The lane emergency verification module is used to obtain the video image of the bound highway toll lane when emergency data is received; it uses the UI framework components of OpenHarmony to design and display the emergency data and the video image of the bound highway toll lane, and provides a button for users to click to provide feedback on whether the lane emergency verification is successful or not; it sends the result of the lane emergency verification feedback by the user through the button to the highway toll system through a created WebSocket; The lane device operation module is used to communicate with lane devices that support the IoT standard using the MQTT or IoT gateway's ModBus protocol; for lane devices that do not support the IoT standard, it uses the OpenHarmony NDK framework to communicate with the lane devices according to their native protocol; and it uses OpenHarmony's UI framework components to design independent operation buttons for each lane device. During lane special situation verification, it receives lane device operation commands issued by the user using the operation buttons to complete the operation of the lane device.

2. The lane emergency response system based on OpenHarmony according to claim 1, characterized in that, The special situation data acquisition module is also used to establish communication with the highway toll system using the HTTP request / response interaction mode of OpenHarmony's HTTP module to obtain special situation verification auxiliary data; The auxiliary data for verifying special situations includes: vehicle flow data, gantry flow data, and trajectory data.

3. The lane emergency response system based on OpenHarmony according to claim 1, characterized in that, Also includes: The work handover module is used to locate the handheld terminal devices of personnel awaiting shifts using OpenHarmony's distributed soft bus, and to interconnect the handheld terminal devices of the currently on-duty personnel and the personnel awaiting shifts using OpenHarmony's unified device networking and topology management technology. It also synchronizes the special situation data and lane equipment status data stored in OpenHarmony's distributed memory database on the currently on-duty personnel's handheld terminal device to the personnel awaiting shifts' terminal devices. The currently on-duty personnel's handheld terminal device refers to the handheld terminal device logged into by the account currently in working status. The personnel awaiting shifts' terminal devices refer to the handheld terminal devices logged into by user accounts whose binding target is the same as the highway toll lane bound to the currently on-duty account and which have issued login requests.

4. The lane emergency response system based on OpenHarmony according to claim 1, characterized in that, The acquisition of video images of the bound toll lane specifically includes: establishing communication with the bound highway toll lane video image acquisition device based on the RTSP protocol to acquire real-time video image data of the bound highway toll lane; and rendering and displaying the video images using the XComponent component of OpenHarmony.

5. The lane emergency response system based on OpenHarmony according to claim 1, characterized in that, The lane emergency verification module is also used to set an emergency data session confirmation button through the UI framework component of OpenHarmony. When the operation of clicking the emergency data session confirmation button by the user is detected, the toll station or driver's phone is dialed through the CALL module of OpenHarmony.

6. The lane emergency response system based on OpenHarmony according to claim 1, characterized in that, The lane emergency verification module is also used to set lane image management buttons through the UI framework components of OpenHarmony. The lane image management buttons include a lane image playback button and a lane image screenshot button. When the user clicks the lane image playback button, the real-time video image playback is managed through OpenHarmony's AVPlayer. When the user clicks the lane image screenshot button, the video image is captured and converted into JPEG format through OpenHarmony's screenshot interface. The video image screenshot is then transmitted to the highway toll system using the POST method via OpenHarmony's HTTP module.

7. The lane emergency response system based on OpenHarmony according to claim 2, characterized in that, The special situation data acquisition module is also used to add an SM2 signature from the OpenHarmony algorithm library to the HTTP header of each request sent to the highway toll system so that the highway toll system can verify the signature based on the SM2 signature in the HTTP header.

8. A method for handling lane emergency situations using the system described in any one of claims 1 to 7, characterized in that, include: The system utilizes OpenHarmony's ATM access control technology to verify the legitimacy of logged-in user accounts, binds legitimate user accounts to highway toll lanes, and displays that the currently logged-in user account is in an active working state. When the user account is in working status, a WebSocket is created using OpenHarmony, and a long WebSocket connection is established between the created WebSocket and the highway toll system. The special situation data of the highway toll lane bound to the user account is obtained by subscribing to the WebSocket events. Upon receiving emergency data, the system acquires the video image of the associated highway toll lane; it uses OpenHarmony's UI framework components to design and display the emergency data and the associated highway toll lane video image, and provides a button for users to click to provide feedback on whether the lane emergency verification has passed; it then uses a created WebSocket to send the result of the user's feedback on whether the lane emergency verification has passed to the highway toll system. By utilizing the UI framework components of OpenHarmony, an independent operation button is designed for each lane device. During the lane special situation verification process, the operation button is used to receive the lane device operation command issued by the user to complete the operation of the lane device.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the method as described in claim 8.

10. A computer device, characterized in that, The computer device includes a memory, a processor, and a program stored in and executable on the memory, the program being executed by the processor to implement the steps of the method as described in claim 8.

Images