CN116620367B - Cloud-edge cooperative track control system - Google Patents
Cloud-edge cooperative track control system Download PDFInfo
- Publication number
- CN116620367B CN116620367B CN202310903736.9A CN202310903736A CN116620367B CN 116620367 B CN116620367 B CN 116620367B CN 202310903736 A CN202310903736 A CN 202310903736A CN 116620367 B CN116620367 B CN 116620367B
- Authority
- CN
- China
- Prior art keywords
- edge
- data
- central
- service
- station
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012545 processing Methods 0.000 claims description 46
- 230000006854 communication Effects 0.000 claims description 39
- 238000004891 communication Methods 0.000 claims description 39
- 238000012544 monitoring process Methods 0.000 claims description 18
- 238000000034 method Methods 0.000 claims description 17
- 230000002159 abnormal effect Effects 0.000 claims description 12
- 230000003993 interaction Effects 0.000 claims description 11
- 238000007726 management method Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 11
- 238000013523 data management Methods 0.000 claims description 8
- 238000012546 transfer Methods 0.000 claims description 7
- 238000013480 data collection Methods 0.000 claims description 6
- 230000008859 change Effects 0.000 claims description 5
- 238000004422 calculation algorithm Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 25
- 238000010586 diagram Methods 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 7
- 238000013461 design Methods 0.000 description 7
- 238000010276 construction Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000013500 data storage Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 238000013508 migration Methods 0.000 description 4
- 230000005012 migration Effects 0.000 description 4
- 230000002457 bidirectional effect Effects 0.000 description 3
- 230000015556 catabolic process Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000006731 degradation reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000005192 partition Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 239000000306 component Substances 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 238000005469 granulation Methods 0.000 description 1
- 230000003179 granulation Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B61—RAILWAYS
- B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
- B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
- B61L27/30—Trackside multiple control systems, e.g. switch-over between different systems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B61—RAILWAYS
- B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
- B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
- B61L27/70—Details of trackside communication
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Mechanical Engineering (AREA)
- Train Traffic Observation, Control, And Security (AREA)
Abstract
The application discloses a cloud-edge cooperative track control system. Wherein, this system includes: the center end is deployed at the cloud end of the network and is used for remotely managing the vehicle and the platform at the cloud end and cooperatively managing the vehicle and the platform with the edge equipment; and the plurality of edge devices are deployed at the station, and each edge device is connected with the central terminal based on Kafka and is used for locally managing the vehicles and the stations at the edge side and cooperatively managing the vehicles and the stations with the central terminal. The application solves the technical problem of low control efficiency caused by relative independence of the center end of the track system and the equipment at the platform side in the related art, realizes weak centering, and ensures the reliability and stability of line operation to the greatest extent.
Description
Technical Field
The application relates to the field of track control, in particular to a cloud-edge cooperative track control system.
Background
In the related art, along with the slowing of rail traffic, rail traffic modes of a low traffic system are discussed in succession in a plurality of places, the low traffic becomes the primary choice of a first-line city junction line and a second-third city trunk line, a multi-level and diversified travel mode is provided for passengers, and a city traffic system structure is optimized.
Compared with subways and light rails, the low-traffic market with lower investment, faster construction and easier approval has better development potential. The intelligent rail express system (intelligent rail for short) not only has the safety and the comfort of rail transit, but also has the flexibility of public transport operation. Meanwhile, no special rail is required to be built, the construction cost is low, and the period is short. Has obvious advantages in various systems with low traffic. Compared with systems such as subway systems, urban area fast rails and the like, the intelligent rail (belonging to an electronic guide rubber wheel system) has small platform scale and limited equipment resources. According to the operation condition of current intelligent rail circuit, whole system mainly includes: comprehensive dispatch systems, platform door systems, broadcast systems, passenger information systems, video monitoring systems, power monitoring systems, transmission systems, wireless systems, and the like. The system basically adopts discrete setting and lacks a unified platform foundation; the bottom layer equipment directly interacts with the center, and the key data has a certain time delay. When the platform side is out of connection with the center, the equipment at the platform side does not have automatic feedback and intelligent decision making capability, and most service functions are affected, so that the normal operation of the platform side is affected.
In the related art, the intelligent rail system design mainly comprises two modes: one is a system discrete design; the other is a centralized cloud computing mode. The two modes adopt a direct interaction mode of bottom equipment and a center, and the mode mainly comprises the following problems: in terms of system architecture, the station is unable to analyze and process data in real time or near real time. In the process of transmitting the data back to the center for processing, the transmission delay of the sensitive data is higher; meanwhile, many data are original useless data, cannot be properly processed, unnecessary waste is caused to bandwidth, and the requirement on central resources is increased. In addition, after the platform side is out of connection with the center, the platform side equipment does not have automatic feedback and intelligent decision making capability, and most of the business at the platform side cannot normally run, so that the normal operation of the line is affected. In the aspect of platform construction, each subsystem is separated, a unified data acquisition, service comprehensive processing and other platform foundation is lacked, system functions and line management are not easy to expand, a center is relatively independent from platform side equipment, and vertical integration of resources and services of each professional equipment is lacked. Meanwhile, as the service nodes are more, the operation and maintenance pressure and difficulty are higher.
In view of the above problems in the related art, an effective solution has not been found.
Disclosure of Invention
The application provides a cloud-edge cooperative track control system.
According to an aspect of the embodiment of the present application, there is provided a cloud-edge cooperative track control system, the system including: the center end is deployed at the cloud end of the network and is used for remotely managing the vehicle and the platform at the cloud end and cooperatively managing the vehicle and the platform with the edge equipment; and the plurality of edge devices are deployed at the station, and each edge device is connected with the central terminal based on Kafka and is used for locally managing the vehicles and the stations at the edge side and cooperatively managing the vehicles and the stations with the central terminal.
Further, the edge device includes: the shift operation management module is used for carrying out station pre-reporting and station reporting before the vehicle enters the station, and managing shift schedule, station side business linkage and shift operation process record; the data processing center module is used for performing redundancy switching of edge side fault nodes, station equipment interaction, real-time data management, historical data management, equipment linkage and program operation monitoring; and the edge side system upgrading service module is used for remotely upgrading the application service and the configuration file of the edge equipment from the central terminal.
Further, a message channel is arranged between the central end and each edge device, and the edge device sends a heartbeat state and a platform side service linkage execution state to the central end through the message channel; the central terminal sends a change message of a line operation schedule, an edge side station reporting linkage message, an edge side system platform software service upgrading message and a configuration information updating message to each edge device through the message channel.
Further, the system includes a data collaboration subsystem, the data collaboration subsystem including: the system comprises a central data acquisition platform arranged at a central end and edge data processing modules arranged at each edge device, wherein the central data acquisition platform is a client end, the edge data processing modules are server ends, and Modbus TCP protocol is adopted for direct interaction.
Further, each edge data processing module is used for collecting equipment information of a plurality of stations, the edge data processing modules are used for receiving Modbus inquiry requests from the central data acquisition platform, judging whether the Modbus inquiry requests are primary edge data processing modules of the stations, returning service data to the central data acquisition platform if the Modbus inquiry requests are primary edge data processing modules, and returning fault codes to the central data acquisition platform if the Modbus inquiry requests are not primary edge data processing modules, wherein each station corresponds to the primary edge data processing modules and the standby edge data processing modules.
Further, the system includes a service collaboration subsystem, the service collaboration subsystem including: the system comprises a central control module arranged at the central end and edge control modules arranged at each edge device, wherein the central control module is used for acquiring the operation state of a target vehicle, monitoring the communication state of the target vehicle if the target vehicle is in a shift operation state, reporting a stop of the target vehicle if the communication state of the target vehicle is normal, and lowering shift stop reporting authority to the edge control module if the communication state of the target vehicle is abnormal, and the edge control module is used for reporting a stop of the target vehicle after receiving the shift stop reporting authority lowered by the central control module.
Further, the central end is further configured to: and monitoring the communication state of each edge device, if the first edge device is in a communication abnormal state, searching a preset configuration table for second edge devices with the first edge devices being redundant, and sending a take-over instruction to the second edge devices, wherein the take-over instruction is used for indicating the second edge devices to take over the first station service of the first edge devices.
Further, the central end is further configured to: and if the first edge equipment and the second edge equipment are in abnormal communication states, taking over the first station service of the first edge equipment and the second station service of the second edge equipment.
Further, the central end is further configured to: and after sending a take-over instruction to the second edge equipment, monitoring the communication state of the first edge equipment, and if the first edge equipment is restored to the normal communication state, sending a take-over stopping instruction to the second edge equipment.
Further, the edge device is further configured to: determining the data type of cooperative data to be interacted with the central terminal; if the cooperative data is dynamic information, encrypting the cooperative data by adopting a SM4 symmetric encryption algorithm of the national cipher, acquiring the configuration information from the central terminal through a secure file transfer protocol SFTP if the cooperative data is configuration information, and acquiring the basic information from the central terminal through a secure hypertext transfer protocol HTTPS based on the secure information if the cooperative data is basic information, wherein the basic information comprises at least one of the following: point list information and device information.
According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program that, when executed, performs the steps in the above-described system.
According to another aspect of the embodiment of the present application, there is also provided an electronic device including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus; wherein: a memory for storing a computer program; and a processor for executing the steps of the method by running a program stored on the memory.
Embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps of the above method.
According to the application, the central end is deployed at the cloud end of the network and is used for remotely managing vehicles and platforms at the cloud end and cooperatively managing the vehicles and the platforms with the edge equipment, the plurality of edge equipment is deployed at the stations, each edge end is respectively connected with the central end based on Kafka and is used for locally managing the vehicles and the platforms at the edge side and cooperatively managing the vehicles and the platforms with the central end, a cloud edge end cooperative track control system is provided, the edge nodes have offline autonomous and fault node service migration capability under the addition of the cooperative capability of the central end and each edge equipment, the robustness of the whole system is comprehensively improved, the technical problem that the control efficiency is low due to the fact that the central end of a track system and the equipment at the station side are relatively independent in the related art is solved, weak centering is realized, and the reliability and stability of line operation are ensured to the greatest extent.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a block diagram of a cloud-edge coordinated track control system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of the cooperation of the center and edge data according to the embodiment of the present application;
FIG. 3 is a schematic diagram of service collaboration in accordance with an embodiment of the present application;
FIG. 4 is a second schematic diagram of service collaboration in accordance with an embodiment of the present application;
FIG. 5 is a flow chart of a hub redundancy switch in an embodiment of the present application;
FIG. 6 is a flow chart of edge side redundancy switching in an embodiment of the present application;
fig. 7 is a system network configuration diagram of an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
Example 1
In this embodiment, a cloud-edge cooperative track control system is provided, and fig. 1 is a block diagram of a cloud-edge cooperative track control system according to an embodiment of the present application, as shown in fig. 1, where the system includes:
the central end 10 is deployed at the cloud end of the network and is used for remotely managing vehicles and platforms at the cloud end and cooperatively managing the vehicles and the platforms with the edge equipment;
the station in this embodiment is station equipment, including: display apparatus, gate apparatus, platform door apparatus, image pickup apparatus, power supply apparatus, platform communication apparatus, broadcasting apparatus, and the like. The scheme of the embodiment not only can be applied to rail transit on the low-traffic rubber wheel road surface, but also can be applied to urban public transport system construction, such as intelligent rails (electronic guide rubber wheels), guide buses (guide rail rubber wheels), BRT (bus bar traffic) and the like.
A plurality of edge devices 12 deployed at the station, each edge being connected to the central terminal based on Kafka, for locally managing vehicles and stations at the edge side, and managing vehicles and stations in cooperation with the central terminal, respectively.
Through the system, the central end is deployed at the network cloud end and is used for remotely managing vehicles and platforms at the cloud end and cooperatively managing the vehicles and the platforms with the edge equipment, the plurality of edge equipment is deployed at the stations, each edge end is connected with the central end based on Kafka and is used for locally managing the vehicles and the platforms at the edge side and cooperatively managing the vehicles and the platforms with the central end, the cloud edge end cooperative track control system is provided, the edge nodes are provided with offline autonomous and fault node service migration capability under the addition of the cooperative capability of the central end and each edge equipment, the robustness of the whole system is comprehensively improved, the technical problem that the control efficiency is low due to the fact that the central end of the track system and the equipment at the station side are relatively independent in the related art is solved, weak centering is achieved, and the reliability and stability of line operation are guaranteed to the greatest extent.
In the central system software architecture of the central terminal of the embodiment, the Nginx service is used as the reverse proxy service of the central IIS server, so that the load balance and high availability of IIS service requests are realized. The nminix service achieves high availability through keepalive. The client and other requests go through the Nginx reverse proxy to IIS service, and then call the storage layer to perform operations such as data reading, insertion and the like.
In the aspect of data storage, real-time data, alarms, events, logs and configuration data are respectively stored through a Redis cache service and a MySQL cluster database service. The client can read and configure data from the micro service layer to the storage service. The real-time database is connected with the drive acquisition service through OPC UA protocol to collect and store data. The micro service cluster can read the historical data in the real-time library through an API mode.
The equipment or external system data realize data acquisition through a unified data driving and collecting platform, and the data driving and collecting platform uploads the data to a micro-service layer through a RESTful interface in a position-changing and uploading mode, so that the data of the types of DI events, SOE, alarms and the like are stored in a MySQL cluster database; the real-time data is stored into a Redis cache cluster service. Meanwhile, the real-time data is pushed to the client by a Kafka message queue mode.
DNS is a domain name server for the entire architecture, and domain names are used for service address configuration within the architecture. The domain name resolution is completed through a domain name server.
The system adopts a Kafka cluster as a message bus, and three nodes are all adopted. The transmission of real-time data and business data between the bearing center and each station and between the bearing center and each professional is realized by the excellent throughput capacity. The Kafka cluster realizes data separation by creating different topics and provides a dedicated channel for data transmission among the modules of the system. The Kafka cluster adopts a ZooKeeper to realize load balancing so as to ensure the robustness of the system.
Redis clusters implement a high availability solution for cache database clusters by employing a multi-sentinel mode through three service nodes. The sentinel is a process program which runs independently of Redis service and has the functions of cluster monitoring, message notification, fault transfer and the like. The sentinel interacts with the Redis master-slave service through commands, so that the Redis server returns to monitor the running state of the Redis server. When the sentry detects that the master is down, the slave is automatically switched to the master, and then other slave servers are notified through a publish-subscribe mode, and the configuration files are modified to switch the slave to the master. The cache database is mainly used as a real-time point location data storage database and a login authorization authentication information storage database. The login verification and the query and storage of real-time data are realized by Redis with high performance and high throughput.
MySQL is used as a central service data storage database, a mutual primary and backup design is adopted, the bidirectional synchronization of the databases is realized through MySQL Replication, and a keepalive is adopted to realize a high-availability architecture of a central database cluster. The application service connects to the database cluster through VIP (Virtual IP Address ). VIP achieves failover through keepalive high availability software. If the database cluster has an abnormal termination of the database service in one node or an accident that the network cannot communicate, the VIP address is automatically transferred to another master node. The service database realizes the creation of the partition of the alarm data storage according to the day by an event mode, and the partition table of the next day is built in the early morning of the timing event. To ensure the storage query efficiency of a large amount of data. The log is a monthly partition, and the database is built after initial building. The log data and the alarm data are stored for 90 days by a timing task mode.
In one implementation of this embodiment, the edge device includes: the shift operation management module is used for carrying out station pre-reporting and station reporting before the vehicle enters the station, and managing shift schedule, station side business linkage and shift operation process record; the data processing center module is used for performing redundancy switching of edge side fault nodes, station equipment interaction, real-time data management, historical data management, equipment linkage and program operation monitoring; and the edge side system upgrading service module is used for remotely upgrading the application service and the configuration file of the edge equipment from the central terminal.
Optionally, a message channel is included between the central end and each edge device, and the edge device sends a heartbeat state and a platform side service linkage execution state to the central end through the message channel; the central terminal sends a change message of a line operation schedule, an edge side station reporting linkage message, an edge side system platform software service upgrading message and a configuration information updating message to each edge device through the message channel.
In the edge side software system architecture of the edge device, the central end and each edge hardware platform device construct a unified, exclusive, shared and bidirectional message channel based on Kafka, so that the transmission of service messages is realized. Each edge hardware platform device can send a heartbeat state, a platform side business linkage execution state (such as vehicle station entering door, platform side station reporting linkage and the like) and the like to the center through the message channel; the center sends a change message of a line operation schedule, an edge side station reporting linkage message, an edge side system platform software service upgrading message, a configuration information updating message and the like to each edge hardware platform device through the message channel. The edge side system adopts an SQLite file type database to ensure isolation and decoupling among different services, and the system uses three files of history data, configuration data and scheduling data to store respectively.
The system function aspect of the edge side mainly comprises a single module, namely: the system comprises a shift operation management module, a data processing center module and an edge side system upgrade service module. The shift operation management module mainly realizes functions of forecasting stations and station reporting before a vehicle enters a station, and functions of shift schedule management, platform side business linkage, shift operation process recording and the like. The data processing center module mainly realizes the functions of redundancy switching of fault nodes at the edge side, station equipment interaction, real-time data management, historical data management, equipment linkage, program operation monitoring and the like. After the program is started, a shift operation management module and a heartbeat monitoring thread are started, then an event processing loop is entered, messages sent to the program and broadcasted are received, and the messages are sequentially processed. The edge side system upgrading service module mainly realizes the remote automatic upgrading of application services, configuration files and the like of the edge side system from the center.
In the embodiment, a central end and each station edge hardware platform device form a ring network, a distributed publishing and subscribing message system is built based on kafka, and a collaborative framework between the center and each edge node and between the edge nodes is built. Under the framework, each edge hardware platform device can stand for independent operation and intelligent decision in a global view, so that from the operation scheduling angle, the core service function realizes cloud-edge two-stage management, and degradation service is not reduced. The center cloud and the edge side bear different service capacities according to the characteristics of the center cloud and the edge side, comprehensively allocate computing power and storage resource requirements of cloud edge two stages, and can maximally embody the advantages and characteristics of the framework by cooperation of the center cloud and the edge side, and comprise the following steps: data collaboration, service collaboration, application management collaboration, security collaboration.
In a data collaboration implementation scenario, the system includes a data collaboration subsystem, the data collaboration subsystem including: the system comprises a central data acquisition platform arranged at a central end and edge data processing modules arranged at each edge device, wherein the central data acquisition platform is a client end, the edge data processing modules are server ends, and Modbus TCP protocol is adopted for direct interaction.
In one example, each edge data processing module is configured to collect device information of a plurality of stations, where the edge data processing modules are configured to receive a Modbus query request from the central data collection platform, determine whether the device is a primary edge data processing module of the station, if so, return service data to the central data collection platform, and if not, return a fault code to the central data collection platform, where each station corresponds to the primary edge data processing module and the standby edge data processing module.
If most systems employ underlying devices to interact directly with the center, the platform measurement cannot analyze and process the data in real time or near real time. In the process of transmitting the data back to the center for processing, the transmission delay of the sensitive data is higher; meanwhile, many data are original useless data, cannot be properly processed, unnecessary waste is caused to bandwidth, and the requirement on central resources is increased. The edge side of the embodiment performs unified data acquisition and service linkage on various heterogeneous devices, and after the edge side is simplified and integrated, the heterogeneous devices are uploaded to a center to realize cloud edge data collaboration while unifying cloud edge interface standards.
In order to improve the software execution efficiency and reduce the computing load of the edge side, the central data acquisition platform and the data acquisition processing central module of the edge side data processing layer directly interact by adopting a Modbus TCP protocol. The edge data processing modules are Server ends, ports are defaulted to 5020, the central driving software is Client ends, and the main and standby double services are adopted, so that each edge data processing module supports 2 clients to access concurrently.
Each edge data processing module may support equipment for collecting multiple stations. The Device ID in the Modbus TCP protocol is used as the Device ID for each station. In order to ensure redundancy, the equipment of each station is subjected to data acquisition by two edge data processing modules, one serving as a main use and the other serving as a standby use. When the data processing module receives a Modbus inquiry request sent by the driving software, firstly judging whether the data processing module is a main acquisition end of the station or not, and if so, normally returning data; if not, the function code is added by 0x80 according to the Modbus protocol, and the fault state is returned. This functionality can be extended to support multiple Device IDs with reference to existing code for electromechanical field services. Fig. 2 is a schematic diagram of the cooperation of the center and edge data according to the embodiment of the present application.
The data processing module stores real-time data for Modbus registers using arrays that are fully identical to those registers. When a query from the flooding software is received, the corresponding register value is obtained from the array and returned. And the data processing module directly writes the data acquired by the data processing module through the Modbus protocol into the array to realize real-time data update. And writing the array by the data processing module for data transmitted to the data processing module by other modules through the Modubes TCP protocol. Regardless of the manner in which the real-time data of the registers is updated, it is necessary to ensure that only one source can update the data at the same time, and a mutual exclusion lock is used when necessary.
In a service collaboration implementation scenario, the system includes a service collaboration subsystem, the service collaboration subsystem comprising: the system comprises a central control module arranged at the central end and edge control modules arranged at each edge device, wherein the central control module is used for acquiring the operation state of a target vehicle, monitoring the communication state of the target vehicle if the target vehicle is in a shift operation state, reporting a stop of the target vehicle if the communication state of the target vehicle is normal, and lowering shift stop reporting authority to the edge control module if the communication state of the target vehicle is abnormal, and the edge control module is used for reporting a stop of the target vehicle after receiving the shift stop reporting authority lowered by the central control module.
When the central schedule is changed, schedule change information is sent to each edge side system through a cloud-edge exclusive message channel, and after the edge side receives the message, platform side service execution is completed according to the latest departure plan. FIG. 3 is a schematic diagram of service coordination according to an embodiment of the present application, in which an edge side message processing flow is shown in FIG. 3, when a communication of a certain intelligent rail vehicle is abnormal, the system will degrade a platform side service linkage triggering right to an edge side, so as to keep a platform side core service to a maximum extent for normal operation; and after the vehicle communication is recovered, the platform side service linkage triggering right is recovered to the center.
For a certain vehicle, it is classified into a shift operation state and a non-shift operation state. When the vehicle is in a non-shift operation state, the platform side does not need to pre-report the station and report the station linkage of the vehicle, but the station door linkage function is reserved. The operating shift is divided into center control and edge control according to whether the communication is normal or not. The central control shift, the pre-report station and report station function are completely notified by the center, and the edge side does not do logic processing. As shown in table 1:
TABLE 1
FIG. 4 is a schematic diagram of service coordination according to an embodiment of the present application, wherein the functions of the pre-report station and the report station are calculated by the edge side according to the departure time.
In an implementation scenario of application management collaboration, the central side is further configured to: and monitoring the communication state of each edge device, if the first edge device is in a communication abnormal state, searching a preset configuration table for second edge devices with the first edge devices being redundant, and sending a take-over instruction to the second edge devices, wherein the take-over instruction is used for indicating the second edge devices to take over the first station service of the first edge devices.
Optionally, the central end is further configured to: and if the first edge equipment and the second edge equipment are in abnormal communication states, taking over the first station service of the first edge equipment and the second station service of the second edge equipment.
Optionally, the central end is further configured to: and after sending a take-over instruction to the second edge equipment, monitoring the communication state of the first edge equipment, and if the first edge equipment is restored to the normal communication state, sending a take-over stopping instruction to the second edge equipment.
The center and each edge device carry out a real-time communication detection mechanism, and when the center identifies that the communication of one edge device is abnormal, the system can take over the edge device which is redundant with the service of the disconnection edge device. When the edge side devices in a redundant relation are all out of connection, the center can take over the platform service which is responsible for the two edge side devices. Fig. 5 is a flowchart of a central redundancy switch in an embodiment of the present application, and the specific flow is shown in fig. 5.
After the communication state between the failed edge hardware platform device a and the center is recovered, the center issues a message instruction to the edge hardware platform device B temporarily taking over the failed node according to the edge node redundancy configuration relationship, the edge hardware platform device B stops taking over the terminal device and the service of the edge hardware platform device a, and at the same time, the edge hardware platform device a will recover taking over the service of the device and the platform side, and fig. 6 is an edge side redundancy switching flowchart in the embodiment of the application, where the flow is shown in fig. 6.
In a security collaboration implementation scenario, the edge device is further configured to: determining the data type of cooperative data to be interacted with the central terminal; if the cooperative data is dynamic information, encrypting the cooperative data by adopting a SM4 symmetric encryption algorithm of the national cipher, acquiring the configuration information from the central terminal through a secure file transfer protocol SFTP if the cooperative data is configuration information, and acquiring the basic information from the central terminal through a secure hypertext transfer protocol HTTPS based on the secure information if the cooperative data is basic information, wherein the basic information comprises at least one of the following: point list information and device information.
The system of the embodiment adopts three-level equivalent protection requirements for design and construction, and the interaction of cloud edge dynamic messages adopts a national secret SM4 symmetric encryption algorithm. In terms of service interaction, the edge side acquires relevant configuration information from the center through an SFTP protocol, and updating of the edge side configuration information is completed; in the aspect of acquiring basic information, such as point table information, equipment information and the like, the edge side acquires relevant basic information from the center through an HTTPS protocol.
The scheme is used for carrying out innovative design on a system architecture aiming at the low-traffic system of the intelligent track express system, and adopting cloud computing, edge computing and other technologies to construct a brand new system architecture based on cloud edge end cooperation.
In the aspect of a central terminal, based on the super-fusion intelligent hardware platform, unified integration of hardware resource requirements of all specialized computing, memory, exchange, storage and the like is realized, and the hardware resource requirements are reduced. The central system platform modularizes and atomizes each professional software function or service through the micro-service architecture and vertically integrates each professional software function, so that the standardization and unification of basic functions such as calculation, information perception, service processing, data acquisition and the like are realized. The software utilization efficiency is improved, the system-level interfaces are reduced, and the requirements of system function upgrading, operation line expanding and the like are facilitated. Meanwhile, through the high-availability design of the core component, the robustness of the whole system is comprehensively improved.
In the aspect of edge side (platform side, edge equipment), edge calculation is introduced, and a brand new edge side system platform is created from the perspective of improving the high availability of the circuit operation core function through lightweight edge hardware platform equipment. The center and each edge hardware platform device realize bidirectional information interaction and information sharing of the center and the edge devices through exclusive and shared information channels, so that each edge hardware platform device can stand at a global view to independently operate and has the capability of intelligent decision. And simultaneously, under the support of a central and edge side cooperative frame, core service functions (such as a platform side door opening and closing, a linkage station reporting and the like) and a cloud edge end framework are deeply fused, so that degradation service is not reduced, weak centering is realized through enabling an edge side, and the platform side independent operation capability and the abnormality handling capability are enhanced. In addition, the edge side node has stronger heterogeneous resource integration capability through rich hardware interfaces, and the edge hardware platform equipment can realize single-station deployment and cross-station deployment modes, so that the flexibility and adaptability of the whole system deployment strategy are improved. Through the high cooperative capability of the center and each edge side node, the edge node has the service migration capability of the offline autonomous and fault nodes. From the platform construction angle, guarantee system safety, reliable operation.
The software in the embodiment adopts a micro-service technology, establishes a unified fusion architecture, establishes a unified comprehensive automatic system platform, replaces the traditional integrated monitoring, communication, signal, automatic ticket selling, platform door and other split systems in weak current, solves the problem of real-time data sharing in the rail transit industry, and provides support for realizing intelligent urban rails.
Through standardization, standardization and unification of data and interfaces, the coupling relation between software and hardware is relieved, and free combination of modularization and granulation functions according to requirements is realized so as to meet the personalized requirements of specific businesses of clients.
Through the open data interface and the development component, a third party can perform standardized extension development on the comprehensive automation system platform, so that rail traffic application service ecology is established, the problems of monopoly development of traditional platform service and limited function update are solved, further, a guarantee is provided for the independent selection of update function service of a customer, and the benign cyclic development of urban rail industry is promoted.
Fig. 7 is a system network structure diagram of an embodiment of the present application, where each station or field section constructs a three-layer ring network with a center through an edge hardware platform device, each station divides different VLANs according to a specialty, prevents risks such as a network storm, and realizes data interview between different VLANs by using a routing function of a three-layer switching module. The network has redundancy capability, and the edge hardware platform equipment of the station or the field section can realize bidirectional communication capability with the center. And the trolley-bus vehicle-mounted equipment realizes wireless communication and data transmission with the center through an LTE network.
By adopting the scheme of the embodiment, through a brand new system architecture of cloud side end cooperation, the core service functions (such as platform side report stations and the like) and the cloud side end architecture are deeply integrated, degradation service is not reduced, weak centralization is realized, and the reliability and stability of line operation are ensured to the greatest extent. Under the addition of the coordination capability of the center and each edge side node, the edge node has the service migration capability of offline autonomous and fault nodes, and the robustness of the whole system is comprehensively improved. Resources are reasonably allocated, so that balance points are found on the use of computing power, bandwidth and storage of the center cloud and the edge side, and the reliability, stability, robustness and adaptability of the system are comprehensively improved. Through intensive and platform design, the requirements of various professional software and hardware resources are integrated, and the resource utilization efficiency is improved, so that the cost reduction and synergy are realized. The edge side nodes have stronger heterogeneous resource integration capability through rich hardware interfaces, and the edge hardware platform equipment can realize single-station deployment and cross-station deployment modes, so that the flexibility and adaptability of the whole system deployment strategy are improved.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.
It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.
In the several embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, such as the division of the units, is merely a logical function division, and may be implemented in another manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application, which are intended to be comprehended within the scope of the present application.
Claims (8)
1. A cloud-edge coordinated track control system, the system comprising:
the center end is deployed at the cloud end of the network and is used for remotely managing the vehicle and the platform at the cloud end and cooperatively managing the vehicle and the platform with the edge equipment;
the edge equipment is deployed at the station, and each edge end is connected with the central end based on Kafka and is used for locally managing vehicles and stations at the edge side and cooperatively managing the vehicles and the stations with the central end;
wherein the system comprises a service collaboration subsystem, the service collaboration subsystem comprising: the system comprises a central control module and edge control modules, wherein the central control module is arranged at the central end and each edge device and is used for acquiring the operation state of a target vehicle, monitoring the communication state of the target vehicle if the target vehicle is in a shift operation state, reporting a stop of the target vehicle if the communication state of the target vehicle is normal, and lowering shift stop reporting authority to the edge control module if the communication state of the target vehicle is abnormal, wherein the edge control module is used for reporting the stop of the target vehicle after receiving the shift stop reporting authority lowered by the central control module;
wherein the central end is further configured to: and monitoring the communication state of each edge device, if the first edge device is in a communication abnormal state, searching a preset configuration table for second edge devices with the first edge devices being redundant, and sending a take-over instruction to the second edge devices, wherein the take-over instruction is used for indicating the second edge devices to take over the first station service of the first edge devices.
2. The system of claim 1, wherein the edge device comprises:
the shift operation management module is used for carrying out station pre-reporting and station reporting before the vehicle enters the station, and managing shift schedule, station side business linkage and shift operation process record;
the data processing center module is used for performing redundancy switching of edge side fault nodes, station equipment interaction, real-time data management, historical data management, equipment linkage and program operation monitoring;
and the edge side system upgrading service module is used for remotely upgrading the application service and the configuration file of the edge equipment from the central terminal.
3. The system according to claim 1, wherein a message channel is included between the central end and each edge device, and the edge device sends a heartbeat state and a platform side service linkage execution state to the central end through the message channel; the central terminal sends a change message of a line operation schedule, an edge side station reporting linkage message, an edge side system platform software service upgrading message and a configuration information updating message to each edge device through the message channel.
4. The system of claim 1, wherein the system comprises a data collaboration subsystem, the data collaboration subsystem comprising: the system comprises a central data acquisition platform arranged at a central end and edge data processing modules arranged at each edge device, wherein the central data acquisition platform is a client end, the edge data processing modules are server ends, and Modbus TCP protocol is adopted for direct interaction.
5. The system of claim 4, wherein each edge data processing module is configured to collect equipment information of a plurality of stations, and the edge data processing modules are configured to receive a Modbus query request from the central data collection platform, determine whether the module is a primary edge data processing module of the station, if the module is the primary edge data processing module, return service data to the central data collection platform, and if the module is not the primary edge data processing module, return a fault code to the central data collection platform, where each station corresponds to the primary edge data processing module and the standby edge data processing module.
6. The system of claim 1, wherein the central end is further configured to: and if the first edge equipment and the second edge equipment are in abnormal communication states, taking over the first station service of the first edge equipment and the second station service of the second edge equipment.
7. The system of claim 1, wherein the central end is further configured to: and after sending a take-over instruction to the second edge equipment, monitoring the communication state of the first edge equipment, and if the first edge equipment is restored to the normal communication state, sending a take-over stopping instruction to the second edge equipment.
8. The system of claim 1, wherein the edge device is further configured to: determining the data type of cooperative data to be interacted with the central terminal; if the cooperative data is dynamic information, encrypting the cooperative data by adopting a SM4 symmetric encryption algorithm of the national cipher, acquiring the configuration information from the central terminal through a secure file transfer protocol SFTP if the cooperative data is configuration information, and acquiring the basic information from the central terminal through a secure hypertext transfer protocol HTTPS based on the secure information if the cooperative data is basic information, wherein the basic information comprises at least one of the following: point list information and device information.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310903736.9A CN116620367B (en) | 2023-07-24 | 2023-07-24 | Cloud-edge cooperative track control system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310903736.9A CN116620367B (en) | 2023-07-24 | 2023-07-24 | Cloud-edge cooperative track control system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN116620367A CN116620367A (en) | 2023-08-22 |
CN116620367B true CN116620367B (en) | 2023-10-24 |
Family
ID=87610208
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202310903736.9A Active CN116620367B (en) | 2023-07-24 | 2023-07-24 | Cloud-edge cooperative track control system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116620367B (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109767171A (en) * | 2019-03-08 | 2019-05-17 | 郭军伟 | A kind of city intelligent track express system |
CN110901693A (en) * | 2019-10-15 | 2020-03-24 | 北京交通大学 | Train operation control system based on 5G and cloud computing technology |
CN112046557A (en) * | 2020-09-14 | 2020-12-08 | 重庆交通大学 | Control method of unmanned train control system |
CN112084030A (en) * | 2020-09-14 | 2020-12-15 | 重庆交通大学 | Unmanned train control system based on cloud edge coordination and control method thereof |
CN112511586A (en) * | 2020-10-21 | 2021-03-16 | 中国铁道科学研究院集团有限公司通信信号研究所 | High-speed railway intelligent traffic scheduling safety card control system based on cloud edge cooperation |
CN113327442A (en) * | 2021-04-30 | 2021-08-31 | 广州中国科学院软件应用技术研究所 | Cooperative control system and method based on end cloud fusion |
CN114786152A (en) * | 2022-04-28 | 2022-07-22 | 北京交通大学 | Credible collaborative computing system for intelligent rail transit |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3798945A1 (en) * | 2019-09-30 | 2021-03-31 | Siemens Mobility S.A.S. | System, apparatus and method for remotely managing operation of rail vehicles |
-
2023
- 2023-07-24 CN CN202310903736.9A patent/CN116620367B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109767171A (en) * | 2019-03-08 | 2019-05-17 | 郭军伟 | A kind of city intelligent track express system |
CN110901693A (en) * | 2019-10-15 | 2020-03-24 | 北京交通大学 | Train operation control system based on 5G and cloud computing technology |
CN112046557A (en) * | 2020-09-14 | 2020-12-08 | 重庆交通大学 | Control method of unmanned train control system |
CN112084030A (en) * | 2020-09-14 | 2020-12-15 | 重庆交通大学 | Unmanned train control system based on cloud edge coordination and control method thereof |
CN112511586A (en) * | 2020-10-21 | 2021-03-16 | 中国铁道科学研究院集团有限公司通信信号研究所 | High-speed railway intelligent traffic scheduling safety card control system based on cloud edge cooperation |
CN113327442A (en) * | 2021-04-30 | 2021-08-31 | 广州中国科学院软件应用技术研究所 | Cooperative control system and method based on end cloud fusion |
CN114786152A (en) * | 2022-04-28 | 2022-07-22 | 北京交通大学 | Credible collaborative computing system for intelligent rail transit |
Also Published As
Publication number | Publication date |
---|---|
CN116620367A (en) | 2023-08-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101217402B (en) | A method to enhance the reliability of the cluster and a high reliability communication node | |
CN110083662B (en) | Double-living framework construction method based on platform system | |
US20130344802A1 (en) | System and method for multi-tier automatic transit system updating | |
CN113037560B (en) | Service flow switching method and device, storage medium and electronic equipment | |
CN102664750B (en) | Method, system and device for hot backup of multi-machine | |
CN102088490B (en) | Data storage method, device and system | |
CN108860223B (en) | Data processing system and method | |
CN102625339A (en) | Monitoring system for using state of integrated wireless communication equipment of railway locomotive | |
CN103595973A (en) | Real-time vehicle audio/video monitoring system and method | |
CN103036719A (en) | Cross-regional service disaster method and device based on main cluster servers | |
CN106945691A (en) | The real-time hot standby switch device of server multicenter of automatic train monitor | |
CN110535924B (en) | Rail transit server communication method and system | |
CN108116456A (en) | For the storage system of remote backup train operation monitoring device data | |
CN114024826A (en) | Application multi-active system based on service grid technology and used in distributed ESB scene | |
CN110348826A (en) | Strange land disaster recovery method, system, equipment and readable storage medium storing program for executing mostly living | |
CN108769215B (en) | Transportation information integration system | |
CN102412990A (en) | Remote sensing satellite raw data recording system with centralized management and real-time transmission functions | |
CN105872024A (en) | Disaster recovery device, system and method | |
CN210804735U (en) | Intelligent electric meter | |
CN112637277A (en) | Station center system based on cloud platform and control method | |
CN116620367B (en) | Cloud-edge cooperative track control system | |
CN113127499B (en) | Block chain-based micro-service method, equipment and medium | |
CN116633977A (en) | Vehicle comprehensive dispatching system suitable for rubber wheel ground system | |
CN115037769A (en) | SOA-based air traffic control automation system and implementation method thereof | |
CN102571310B (en) | The disaster recovery method of Voice Mail Service and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |