A toll station multi-station integration system based on cloud edge collaboration, a control method, a terminal and a medium

Abstract

This invention discloses a cloud-edge collaborative multi-station toll station integration system, control method, terminal, and medium. The system includes: an equipment and operating system layer, a lane controller and edge computing layer, and a platform and toll service layer. The equipment and operating system layer consists of various electromechanical equipment at the toll station and their underlying drivers. The lane controller and edge computing layer includes lane controllers and Docker containers deployed on the lane controllers, with the lane controllers having a built-in edge computing subsystem. The platform and toll service layer includes: a hyper-converged edge cloud, a toll service system, a unified Meta management platform, and a remote monitoring and maintenance platform. This invention centrally carries station-level services through the edge cloud, provides unified access to electromechanical equipment through lane controllers, and deploys downgraded toll servers in large and small toll plazas, achieving centralized deployment of station-level services and further promoting the digital and intelligent upgrade of highway toll systems.

Description

Technical Field

[0001] This invention relates to the field of traffic information engineering technology, and in particular to a cloud-edge collaborative multi-station toll station integration system, control method, terminal and medium. Background Technology

[0002] Currently, most highway toll stations still use a "one station, one server room" model: each station independently configures servers, storage, and networks. Toll collection, monitoring, and auditing functions are often decentralized into multiple independent systems, forming a "siloed" architecture. This leads to problems such as difficulty in sharing data and business processes, inconsistent versions, and low resource utilization. Consequently, toll station operations heavily rely on local server rooms and manual management, requiring a large number of toll collection and maintenance personnel, as well as incurring high maintenance costs for equipment and electromechanical facilities inspection and repair. At the same time, the decentralized systems and lack of unified scheduling and emergency mechanisms mean that failures in local server rooms or critical equipment often rely on manual switching or simple measures, making it difficult to form a unified disaster recovery system across stations and road sections, resulting in insufficient business continuity and data security. Overall, toll stations generally suffer from decentralized construction, multiple coexisting systems, high maintenance costs, and weak disaster recovery capabilities.

[0003] Therefore, existing technologies still have shortcomings. Summary of the Invention

[0004] To address the aforementioned shortcomings of existing technologies, this invention provides a cloud-edge collaborative multi-station toll station integration system, control method, terminal, and medium. The technical solution adopted by this invention is as follows: In a first aspect, the present invention provides a cloud-edge collaborative multi-station toll station integration system, the system comprising: The equipment and operating system layer, the lane controller and edge computing layer, and the platform and toll collection service layer; The equipment and operating system layer consists of various electromechanical equipment at the toll station and their underlying drivers, which forms the basis for system perception and execution. The lane controller and edge computing layer are the hub for device access and edge collaboration, including the lane controller and Docker containers deployed on the lane controller, which has a built-in edge computing subsystem. The platform and billing service layer includes: hyperconverged edge cloud, billing service system, Meta unified management platform and remote monitoring and operation and maintenance platform, which are used to realize centralized deployment of billing services, multi-site integration and remote monitoring and operation and maintenance.

[0005] In one implementation, the equipment and electromechanical devices deployed at the toll station site in the operating system layer include any one or more of the following: inductive loop detectors, voice prompts, barrier gates, ETC (Electronic Toll Collection) devices, mobile payment devices, toll display screens, weighing devices, CPC card readers, vehicle-to-everything (V2X) roadside units, license plate recognition, and toll monitoring cameras.

[0006] In one implementation, the lane controller provides standard interfaces and a web configuration interface to the outside world in the form of a business plugin and an HTTP server.

[0007] In one implementation, the hyperconverged edge cloud integrates computing, storage, and virtualization capabilities in the form of an all-in-one machine, providing a unified operating environment for the primary charging system and the backup degraded charging system; The toll collection system includes a primary toll collection system and a backup degraded toll collection system. The primary toll collection system is deployed as a Web Server at the hyperconverged edge and is responsible for toll calculation, transaction processing and accounting management under normal conditions. The backup degraded toll collection system is an independent Web Server instance that shares some data with the primary toll collection system but is logically isolated. When cloud station anomalies or lane services are affected, it switches over in seconds with the coordination of the lane controller and takes over the necessary toll collection functions. The Meta Unified Management Platform serves as a unified operations management portal, aggregating lane data, equipment information, and operational statistics from various stations. It provides road companies with a unified operational view and decision support, and, combined with the resource monitoring of the hyperconverged edge cloud, enables centralized management of computing nodes, virtual machines, and application containers.

[0008] Secondly, embodiments of the present invention also provide a control method for a cloud-edge collaborative multi-station toll station system based on any of the above-described solutions, the method comprising: When a vehicle enters the lane, the vehicle detector detects the vehicle and sends a trigger signal to the lane controller. The lane controller then activates the lane toll collection process and drives the preset electromechanical equipment to collect data. The collected data is analyzed and combined with the toll collection results, and then the travel instructions are sent to the lane controller through the hyperconverged edge cloud. The lane controller, in conjunction with the barrier gate, executes the release command to allow the vehicle to exit the lane.

[0009] In one implementation, the preset electromechanical equipment is driven to collect data, including: The drive lane camera collects image data; Drive the license plate recognition equipment to identify license plate information; The vehicle-mounted electronic tag information is read through the roadside unit of the vehicle-to-everything (V2X) network.

[0010] In one implementation, the collected data is analyzed and combined with toll collection results. Then, a travel instruction is issued to the lane controller via a hyper-converged edge cloud, including: Determine if the vehicle is an ETC vehicle; if not, proceed to manual processing, complete manual toll collection, and issue a departure instruction after the toll collection is completed. If it is an ETC vehicle, determine whether the on-board electronic tag is normal, and if it is abnormal, switch to manual processing to complete manual toll collection, and issue a departure instruction after the toll collection is completed; If the vehicle electronic tag is normal, the validity of the vehicle electronic tag and ETC card is verified. If the verification fails, the process is transferred to manual processing to complete manual toll collection, and a departure instruction is issued after the toll collection is completed. If the verification passes, the amount due will be displayed on the fee display screen, and a payment instruction will be issued after the fee is collected.

[0011] In one implementation, the method further includes: When cloud station anomalies or lane operations are detected, the toll collection system will be switched.

[0012] Thirdly, embodiments of the present invention also provide a terminal, wherein the terminal includes a memory, a processor, and an entity extraction and processing program stored in the memory and executable on the processor. When the processor executes the entity extraction and processing program, it implements the steps of the control method of the cloud-edge collaborative toll station multi-station integration system described in any of the above schemes.

[0013] Fourthly, embodiments of the present invention also provide a computer-readable storage medium, wherein an entity extraction processing program is stored on the computer-readable storage medium, and the entity extraction processing program implements the steps of the control method of the cloud-edge collaborative toll station multi-station integration system described in any one of the above schemes on the computer-readable storage medium.

[0014] Beneficial Effects: Compared with existing technologies, this invention provides a cloud-edge collaborative multi-station toll station system, comprising: an equipment and operating system layer, a lane controller and edge computing layer, and a platform and toll collection service layer; wherein, the equipment and operating system layer consists of various electromechanical devices and their underlying drivers at the toll station site, which is the foundation for system perception and execution; the lane controller and edge computing layer is the hub for device access and edge collaboration, including the lane controller and Docker containers deployed on the lane controller, and the lane controller has a built-in edge computing subsystem; the platform and toll collection service layer includes: a hyper-converged edge cloud, a toll collection service system, a Meta unified management platform, and a remote monitoring and maintenance platform, used to realize centralized deployment of toll collection services, multi-station integration, and remote monitoring and maintenance.

[0015] This invention enables centralized deployment of station-level services through edge cloud and unified access of lane controllers to electromechanical equipment. It also deploys downgraded toll collection servers in the plazas of large and small stations, thereby achieving centralized deployment of station-level services and further promoting the digital and intelligent upgrade of the highway toll collection system. Attached Figure Description

[0016] Figure 1 This is an architecture diagram of the control system for a cloud-edge collaborative multi-station toll station integration system provided in an embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of the equipment composition of the lane controller in the control system of the cloud-edge collaborative toll station multi-station integration system provided in the embodiment of the present invention.

[0018] Figure 3 A flowchart of a preferred embodiment of the control method for a cloud-edge collaborative toll station multi-station integration system provided by the present invention.

[0019] Figure 4 The flowchart illustrates the specific application of the control method for a cloud-edge collaborative toll station multi-station integration system provided in this embodiment of the invention.

[0020] Figure 5 This invention describes the cloud-edge collaborative charging process for small stations and standard stations in a multi-station integration scenario.

[0021] Figure 6 A schematic diagram of a terminal provided in an embodiment of the present invention. Detailed Implementation

[0022] To make the objectives, technical solutions, and effects of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0023] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content, operations, or steps, nor does it require execution in the described order. For example, some operations or steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0024] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0025] It should be understood that, in order to clearly describe the technical solutions of the embodiments of the present invention, the terms "first" and "second" are used in the embodiments of the present invention to distinguish identical or similar items with essentially the same function and effect. For example, "first control information" and "second control information" are only used to distinguish different control information and do not limit their order.

[0026] Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or the order of execution, and that the words "first" and "second" do not necessarily imply that they are different.

[0027] It should also be understood that the term “and / or” as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0028] In recent years, new-generation information technologies such as cloud computing, big data, the Internet of Things, mobile internet, and artificial intelligence have been rapidly integrated into the transportation industry. "Internet + Transportation" has become an important tool for transformation and upgrading, and an independent, controllable, secure, and reliable information technology system has become a rigid requirement. Based on the principle of cloud-edge collaboration, this invention proposes a cloud-edge collaborative multi-station integration system for toll stations, realizing unified access and interconnection of toll station electromechanical equipment, supporting lightweight construction and centralized operation and maintenance, and solving engineering challenges such as multi-station integration and system integration.

[0029] This embodiment of the system is based on "cloud-edge collaboration": the provincial cloud platform deploys an edge node management system, the road segment-level hyper-converged edge cloud uniformly carries toll station operations, and the lane controllers on the lane side undertake local control and intelligent terminal functions. Through three-level collaboration between the provincial platform, the central edge cloud, and the lane controllers, an operating mode of "cloud-based unified management, edge aggregation, and lane autonomy" is formed. Specifically, the cloud is responsible for toll processing, accounting, and centralized operation and maintenance; the edge cloud is responsible for centralized deployment of multi-station operations and data aggregation; and the lane controllers are responsible for millisecond-level device driving and critical data caching. Combined with a primary / backup strategy and a degradation mechanism, the system can ensure business continuity under various failure scenarios.

[0030] In practical applications, this embodiment, considering traffic volume, existing electromechanical scale, and station location, divides toll stations into central stations (large stations) and small stations. A unified hyper-converged edge cloud platform is built at the central station to centrally deploy station-level transaction, station-level management, gantry services, and entrance overload control systems. Unified deployment and upgrades of nodes and applications are achieved through cloud-edge collaboration. Small stations only deploy lane controllers, retaining necessary network access. This migrates toll collection, monitoring, and other services originally scattered across various station server rooms to a centralized edge cloud platform, eliminating the need for individual stations to configure complete servers and storage facilities, thus achieving lightweighting and simplification of electromechanical equipment.

[0031] This embodiment of the cloud-edge collaborative toll station multi-station integration system is divided into three layers: the equipment and operating system layer, the lane controller and edge computing layer, and the platform and toll collection business layer. These three layers are decoupled using standardized interfaces. Through a hierarchical upward transition from the "equipment layer → control / edge layer → platform layer," unified access to lane electromechanical equipment, edge intelligent control, and centralized cloud-based toll collection and remote operation and maintenance are achieved. Figure 1 As shown, the bottom layer consists of various electromechanical equipment distributed across toll stations and lanes; the middle layer comprises lane controllers that uniformly access these devices and perform real-time control and preliminary data processing locally; the top layer consists of a road segment-level hyper-converged edge cloud, a unified Meta management platform, and a remote monitoring and maintenance platform, enabling centralized deployment of toll collection services, integration of multiple stations, and remote monitoring and maintenance. This three-layer collaborative architecture allows for the "abstraction" of station-level data centers into logical sites within the edge cloud without altering the essential processes of lane operations, forming a new model of "multiple stations sharing one cloud, cloud-edge collaborative operation."

[0032] Specifically, the equipment and operating system layer in this embodiment consists of various electromechanical devices and their underlying drivers at the toll station, forming the foundation for system perception and execution. Typical devices include any one or more of the following: inductive loop detectors, voice prompts, barrier gates, ETC (Electronic Toll Collection), mobile payment devices, toll display screens, weighing equipment, CPC card readers / writers, vehicle-to-everything (V2X) roadside units, license plate recognition, and toll monitoring cameras. To reduce the access complexity caused by devices from multiple vendors and using multiple protocols, a driver layer is introduced within the lane controller to manage these devices uniformly. Various devices connect via interfaces such as GPIO, UART, wired network cards, and USB. The driver management system (SO) provides a unified API, shielding hardware differences and allowing upper-layer services to focus only on functions such as vehicle detection, image acquisition, barrier gate control, and voice announcements, without needing to concern themselves with specific device models and communication details. This design facilitates centralized selection and batch deployment after multiple stations are integrated, and also reserves space for future equipment replacement and upgrades, thus reducing life-cycle maintenance costs.

[0033] Furthermore, the lane controller and edge computing layer serve as the hub for device access and edge collaboration. This includes the lane controller itself and Docker containers deployed on it. The lane controller incorporates an edge computing subsystem, using a "thing model" to uniformly abstract device status and attributes (such as online status, fault alarms, lane modes, etc.) and, based on this, carries lane business logic. In terms of software architecture, the lane controller provides standard interfaces and a web configuration interface externally in the form of business plugins and an HTTP server. Maintenance personnel can directly complete parameter configuration, device debugging, and local maintenance through a browser, reducing reliance on dedicated maintenance terminals and allowing for the expansion of new services as needed through plugins. Specifically, for example... Figure 2As shown in the figure, the device composition of the lane controller includes: perception and acquisition devices, vehicle-road communication devices, transaction payment devices, information release devices, safety warning devices, and ticket printing devices. On the one hand, the lane controller in this embodiment provides rich on-site interfaces and can access various electromechanical devices such as lane antennas, fare display screens, mobile payment terminals, vehicle detectors, license plate recognition devices, etc.; on the other hand, it provides standardized service interfaces externally through a unified software framework to achieve the unified access and management of devices from different manufacturers on the same controller. The controller has built-in edge computing capabilities, supports device status collection and preprocessing, local discrimination of key events, and can perform quick linkage control on devices such as license plate recognition devices and fare displays.

[0034] To enhance the scalability and resource isolation capabilities, Docker containers are deployed on the lane controller: the lane detection and control mirror integrates the device SDK, protocol adaptation library, and driver mapping to achieve the unified access and collaborative control of multi-vendor electromechanical devices; the camera streaming service mirror is responsible for video collection and forwarding to provide data for cloud or local video analysis. The overall control and edge computing functions are mounted on the IoT-Edge platform, and through it, local data aggregation, rule calculation, and two-way communication with the cloud Huawei IoT-Edge platform are completed: on the one hand, the lane operation and device health information are sent up as needed for operation and maintenance and management analysis; on the other hand, it supports the unified configuration and control instructions sent from the cloud to achieve unified policy control across stations and lanes.

[0035] In cloud-edge collaboration, the lane controller mainly plays three types of roles: (1) When the cloud station is normal, it is responsible for real-time device driving and data collection, and sends transaction and status information to the edge cloud toll collection system, and the cloud completes fare calculation, warehousing, and clearing; (2) When the edge cloud or cloud station fails, it cooperates with the local downgraded toll collection server to take over the core toll collection logic, and relies on local caching and simplified rules to ensure passage, realizing the second-level switching between the cloud station and the downgraded service; (3) When the communication link is unstable or interrupted for a short time, the transaction data is locally stored and resumed from the breakpoint, and automatically retransmitted after the network is restored to ensure the integrity and consistency of the accounting data.

[0036] In this embodiment, by introducing a self-controlled lane controller, while ensuring the real-time control of electromechanical devices, a collaborative mechanism of "cloud overall planning, edge concentration, and lane autonomy" is constructed, providing key support for the multi-station integration transformation and second-level disaster tolerance capabilities.

[0037] Furthermore, the platform and the toll collection business layer are located at the top layer of the architecture, mainly composed of a hyper-converged edge cloud platform, a toll collection business system, a Meta unified management platform, a remote monitoring and operation and maintenance platform, etc.

[0038] This embodiment's hyperconverged edge cloud integrates computing, storage, and virtualization capabilities in an all-in-one form, providing a unified operating environment for the primary toll collection system and the backup degraded toll collection system. The toll collection system includes a primary toll collection system and a backup degraded toll collection system. The primary toll collection system, deployed as a Web Server at the hyperconverged edge, is responsible for toll calculation, transaction processing, and accounting management under normal conditions. The backup degraded toll collection system, as an independent Web Server instance, shares some data with the primary toll collection system but is logically isolated. When cloud station anomalies or lane operations are detected, it switches over within seconds with the coordination of the lane controller, taking over necessary toll collection functions. The Meta unified management platform, serving as a unified operation management portal, aggregates lane data, equipment information, and operational statistics from various stations, providing road companies with a unified operational view and decision support. Combined with the resource monitoring of the hyperconverged edge cloud, it enables centralized management of computing nodes, virtual machines, and application containers.

[0039] This embodiment deploys the primary toll collection system, the backup degraded toll collection system, operation and maintenance components, and some data services on a hyperconverged edge cloud. Only a small number of edge cloud nodes need to be built for a road segment to support the business of multiple toll stations, realizing the integration of multiple stations and resource pooling. This reduces the number of traditional data centers and servers, and provides a physical foundation for cross-station disaster recovery and takeover.

[0040] Based on the above embodiments, the present invention also provides a control method for a cloud-edge collaborative multi-station toll station integration system. In specific implementation, the control method for this embodiment can be applied to a terminal, which includes intelligent product terminals such as computers. Specifically, for example... Figure 3 As shown in the figure, the control method of the cloud-edge collaborative toll station multi-station integration system in this embodiment includes the following steps: Step S100: When a vehicle enters the lane, the vehicle detector sends a trigger signal to the lane controller after detecting the vehicle. The lane controller then activates the lane toll collection process and drives the preset electromechanical equipment to collect data. Step S200: Analyze the collected data and combine it with the toll collection results, and issue a departure instruction to the lane controller through the hyper-converged edge cloud. In step S300, the lane controller, in conjunction with the barrier gate, executes the release command to allow the vehicle to leave the lane.

[0041] Specifically, after a vehicle enters the ETC lane at the toll station, the lane detector detects the vehicle's entry and triggers the lane toll collection process, while the passage indicator light turns red. Next, the lane controller drives the lane camera to collect image data; drives the license plate recognition device to recognize the license plate information; and reads the vehicle's electronic tag information through the vehicle-to-everything (V2X) roadside unit. The system first determines whether the vehicle is an ETC vehicle. If not, it switches to manual processing, completes manual toll collection, and issues a departure instruction after toll collection is completed. If it is an ETC vehicle, it checks whether the vehicle's electronic tag is normal. If not, it switches to manual processing, completes manual toll collection, and issues a departure instruction after toll collection is completed. If the vehicle's electronic tag is normal, it verifies the validity of the vehicle's electronic tag and ETC card. If the verification fails, it switches to manual processing, completes manual toll collection, and issues a departure instruction after toll collection is completed. If the verification passes, it displays the amount due on the toll display screen, completes toll collection, and issues a departure instruction after toll collection is completed.

[0042] Combination Figure 4 As shown, the control method of this embodiment includes the following steps in specific applications: Step 1: The vehicle enters the ETC lane of the toll station, triggering three operations simultaneously: Step 1.1: The ramp pre-transaction antenna establishes a chain with the OBU (On-Board Unit) and reads the OBU information; Step 1.2: The vehicle detector detects the vehicle entering, and the HarmonyOS lane controller wakes up the lane process; Step 1.3: The red traffic indicator light illuminates.

[0043] Step 2: After the HarmonyOS lane controller wakes up the lane process, it executes the following: vehicle camera captures images, and license plate recognition device recognizes license plates.

[0044] Step 3: Perform a judgment: Is it an ETC vehicle? Step 3.1: If the result is "No": Transfer to manual / ETC-MTC hybrid processing → Mobile payment intervention → Manual toll collection → Barrier gate opens to allow passage → Vehicle exits ETC lane; Step 3.2: If the result is "Yes": Proceed to the "Is OBU abnormal?" judgment step.

[0045] Step 4: Determine if the OBU is malfunctioning. Step 4.1: If the result is "Yes": The barrier gate is raised to allow passage → the toll display and voice prompt prompt the vehicle to pull over / manual processing → standard toll station edge cloud → the printer prints a receipt and uploads the record to the provincial transaction system → the vehicle exits the ETC lane; Step 4.2: If the result is "No": Proceed to the "Repeated transactions within 3 minutes?" judgment stage.

[0046] Step 5: Determine if there are duplicate transactions within 3 minutes. Step 5.1: If the result is "yes": Proceed directly to the judgment step of "Does the captured license plate match the OBU license plate?" Step 5.2: If the result is "No": Proceed to the "OBU and ETC card validity" judgment stage.

[0047] Step 6: Determine the validity of the OBU and ETC card: Step 6.1: If the result is "No": The barrier gate is raised to allow passage → the toll display and voice prompt prompt the vehicle to pull over / manual processing → standard toll station edge cloud → the printer prints a receipt and uploads the record to the provincial transaction system → the vehicle exits the ETC lane; Step 6.2: If the result is "yes": Proceed to the judgment step of "Does the captured license plate match the OBU license plate?"

[0048] Step 7: Determine if the captured license plate matches the OBU license plate: Step 7.1: If the result is "No": The toll display and voice prompt will prompt you to pull over / manual processing → Standard toll station edge cloud → Printer prints receipt record and uploads it to the provincial transaction system → Vehicle exits ETC lane; Step 7.2: If the result is "Yes": The toll display shows the toll amount → Transaction successful → The barrier gate opens to allow passage → The vehicle exits the ETC lane. Records of the transaction and special situation handling process can be uploaded to the standard toll station edge cloud / station-level system, and a receipt can be printed and kept if necessary.

[0049] In this embodiment, the electromechanical equipment controlled by the lane controller installed at the small station is consistent with that of the standard station. For example... Figure 5 As shown, after a vehicle enters the ETC lane of the small station, the lane controller collects toll-related information such as license plate / capture image and associates it with the monitoring video. It packages the "transaction data + image / video" and uploads it to the standard station cloud. After the cloud completes the reception and storage, the station-level toll system calculates the amount due, and the entrance overload control system verifies and audits it. It then generates a receipt containing the amount and processing instructions and sends it to the lane controller. The controller sends the amount to the toll display screen (which can be linked to control voice / traffic lights / barriers) to complete the deduction and release. The transaction result is then sent back to the cloud for archiving to form a closed loop.

[0050] In other implementations, this embodiment switches the toll collection system when a cloud station malfunction or lane service disruption is detected. The toll collection system includes a primary toll collection system and a backup degraded toll collection system. The primary toll collection system is deployed as a Web Server at the hyper-converged edge, responsible for toll calculation, transaction processing, and accounting management under normal conditions. The backup degraded toll collection system is an independent Web Server instance, sharing some data with the primary toll collection system but logically isolated. When a cloud station malfunction or lane service disruption is detected, it switches within seconds with the lane controller's coordination, taking over necessary toll collection functions. Therefore, in practical applications, under normal circumstances, lanes use the cloud station transaction service, i.e., the primary toll collection system, without any switching operation. When the cloud station transaction service is detected to be unavailable or in an abnormal state, inconsistent with the current working mode, the IoT controller determines that switching to the backup degraded toll collection system is necessary based on the principle of "prioritizing the cloud station," and a prompt appears on the toll collection interface: "Station-level transaction system unavailable, switch to plaza degraded system?" After the toll collector confirms, the system marks the current mode as "downgraded." The IoT master controller sends a switch command to the lane controller, and the field equipment switches to the backup downgraded toll collection system, initiating the plaza downgraded transaction service. The lane continues to collect tolls in downgraded mode. During downgraded operation, the system continuously monitors the status of the cloud station transaction service. When the station-level service is detected to have recovered and become stable and available, the IoT master controller pushes a prompt to the downgraded toll collection interface: "Cloud station transaction service has been restored. Do you want to switch to cloud station transaction service?" After the toll collector confirms again, the system completes the switchback from plaza downgrade to cloud station service, updates the current mode and the status of each WebUI, and restores the normal cloud station workflow; if no confirmation is made immediately, the existing mode is maintained and periodically re-evaluated.

[0051] In summary, this invention addresses the needs of multi-station consolidation and second-level disaster recovery at highway toll stations by constructing a cloud-edge collaborative multi-station consolidation system based on "hyper-converged edge cloud + lane controller." The system centrally hosts station-level business on the edge cloud, provides unified access to electromechanical equipment via lane controllers, and deploys degraded toll servers in the plazas of large and small toll stations, enabling centralized deployment of station-level business and rapid switching between cloud stations and degraded services. Experimental results show that the system meets design goals in terms of data consistency, business availability, and switching latency, significantly reducing the size of the data center and servers compared to traditional models, and significantly improving cross-site disaster recovery capabilities. Further development can add more edge intelligent applications to the existing architecture, further promoting the digital and intelligent upgrade of highway toll systems.

[0052] Based on the above embodiments, the present invention also provides a terminal, the principle block diagram of which can be as follows: Figure 6 As shown. The terminal may include one or more processors 100 ( Figure 6(Only one is shown in the image), memory 101, and computer program 102 stored in memory 101 and executable on one or more processors 100. For example, an entity extraction processing program. When one or more processors 100 execute computer program 102, they can implement the various steps in the control method embodiment of the cloud-edge collaborative toll station multi-station integration system. Alternatively, when one or more processors 100 execute computer program 102, they can implement the functions of various modules / units in the control system embodiment of the cloud-edge collaborative toll station multi-station integration system, which is not limited here.

[0053] In one embodiment, the processor 100 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0054] In one embodiment, memory 101 may be an internal storage unit of an electronic device, such as a hard drive or RAM. Memory 101 may also be an external storage device of the electronic device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital Card (SD), or Flash Card. Furthermore, memory 101 may include both internal and external storage units. Memory 101 is used to store computer programs and other programs and data required by the terminal. Memory 101 can also be used to temporarily store data that has been output or will be output.

[0055] Those skilled in the art will understand that Figure 6 The block diagram shown is merely a partial structural diagram related to the present invention and does not constitute a limitation on the terminal to which the present invention is applied. A specific terminal may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0056] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), direct memory bus RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0057] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A cloud-edge collaborative multi-station toll station integration system, characterized in that, The system includes: a device and operating system layer, a lane controller and edge computing layer, and a platform and toll collection service layer; The equipment and operating system layer consists of various electromechanical equipment at the toll station and their underlying drivers, which forms the basis for system perception and execution. The lane controller and edge computing layer are the hub for device access and edge collaboration, including the lane controller and Docker containers deployed on the lane controller, which has a built-in edge computing subsystem. The platform and billing service layer includes: hyperconverged edge cloud, billing service system, Meta unified management platform and remote monitoring and operation and maintenance platform, which are used to realize centralized deployment of billing services, multi-site integration and remote monitoring and operation and maintenance.

2. The cloud-edge collaborative multi-station toll station integration system according to claim 1, characterized in that, The electromechanical equipment deployed at the toll station site in the device and operating system layer includes any one or more of the following: inductive loop detectors, voice prompts, barrier gates, ETC, mobile payment devices, toll display screens, weighing equipment, CPC card readers, vehicle-to-everything (V2X) roadside units, license plate recognition, and toll monitoring cameras.

3. The cloud-edge collaborative multi-station toll station integration system according to claim 1, characterized in that, The lane controller provides standard interfaces and a web configuration interface to the outside world in the form of business plugins and an HTTP server.

4. The cloud-edge collaborative multi-station toll station integration system according to claim 1, characterized in that, The hyperconverged edge cloud integrates computing, storage, and virtualization capabilities in the form of an all-in-one machine, providing a unified operating environment for the primary charging system and the backup degraded charging system; The toll collection system includes a primary toll collection system and a backup degraded toll collection system. The primary toll collection system is deployed as a WebServer at the hyperconverged edge and is responsible for toll calculation, transaction processing and accounting management under normal conditions. The backup degraded toll collection system is an independent WebServer instance that shares some data with the primary toll collection system but is logically isolated. When cloud station anomalies or lane services are affected, it switches over in seconds with the coordination of the lane controller and takes over the necessary toll collection functions. The Meta Unified Management Platform serves as a unified operations management portal, aggregating lane data, equipment information, and operational statistics from various stations. It provides road companies with a unified operational view and decision support, and, combined with the resource monitoring of the hyperconverged edge cloud, enables centralized management of computing nodes, virtual machines, and application containers.

5. A control method for a cloud-edge collaborative multi-station toll station integration system based on any one of claims 1-4, characterized in that, The method includes: When a vehicle enters the lane, the vehicle detector detects the vehicle and sends a trigger signal to the lane controller. The lane controller then activates the lane toll collection process and drives the preset electromechanical equipment to collect data. The collected data is analyzed and combined with the toll collection results, and then the travel instructions are sent to the lane controller through the hyperconverged edge cloud. The lane controller, in conjunction with the barrier gate, executes the release command to allow the vehicle to exit the lane.

6. The control method for a multi-station integrated toll station system based on cloud-edge collaboration according to claim 5, characterized in that, The driver collects data from preset electromechanical equipment, including: The drive lane camera collects image data; Drive the license plate recognition equipment to identify license plate information; The vehicle-mounted electronic tag information is read through the roadside unit of the vehicle-to-everything (V2X) network.

7. The control method for a multi-station integrated toll station system based on cloud-edge collaboration according to claim 6, characterized in that, Based on the collected data analysis and combined with the toll collection results, the system issues travel instructions to the lane controller via a hyperconverged edge cloud, including: Determine if the vehicle is an ETC vehicle; if not, proceed to manual processing, complete manual toll collection, and issue a departure instruction after the toll collection is completed. If it is an ETC vehicle, determine whether the on-board electronic tag is normal, and if it is abnormal, switch to manual processing to complete manual toll collection, and issue a departure instruction after the toll collection is completed; If the vehicle electronic tag is normal, the validity of the vehicle electronic tag and ETC card is verified. If the verification fails, the process is transferred to manual processing to complete manual toll collection, and a departure instruction is issued after the toll collection is completed. If the verification passes, the amount due will be displayed on the fee display screen, and a payment instruction will be issued after the fee is collected.

8. The control method for a multi-station integrated toll station system based on cloud-edge collaboration according to claim 7, characterized in that, The method further includes: When cloud station anomalies or lane operations are detected, the toll collection system will be switched.

9. A terminal, characterized in that, The terminal includes a memory, a processor, and a control program for a cloud-edge collaborative toll station multi-station integration system stored in the memory and executable on the processor. When the processor executes the control program for the cloud-edge collaborative toll station multi-station integration system, it implements the steps of the control method for the cloud-edge collaborative toll station multi-station integration system as described in any one of claims 5-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a control program for a cloud-edge collaborative toll station multi-station integration system. The control program for the cloud-edge collaborative toll station multi-station integration system implements the steps of the control method for the cloud-edge collaborative toll station multi-station integration system as described in any one of claims 5-8 on the computer-readable storage medium.

Images