Rail transit data management method and system, electronic equipment and storage medium

Abstract

The invention discloses a rail transit data management method and system, electronic equipment and a storage medium, the management system comprises a central end and a plurality of station nodes, and the central end and the station nodes are each provided with an event channel, an agent module and a message queue; data synchronization is carried out between the station nodes and the central end through event channels, agent modules and message queues; after receiving the subscription request of the client, the central end determines a target node in the station nodes based on the subscription request; the client is a station node in an external system or a management system; and the central end obtains service data corresponding to the subscription request from the target node and sends the service data to the client. When the client is an external system, the central end interacts with the station nodes in the management system to obtain service data, and when the client is an internal station node, the central end interacts with other station nodes to obtain service data, and data transmission is carried out through the central end in a unified manner. And the complexity and the cost of integration are also reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of data distribution, and in particular to a rail transit data management method, system, electronic device and storage medium. Background Art

[0002] Modern rail transit systems include multiple station nodes, such as train control nodes, station management nodes, signal nodes, ticketing nodes, passenger information nodes, etc. These station nodes are responsible for different functional modules, but they are highly dependent on each other. In order to ensure the coordinated work and efficient operation of the system, data between different station nodes must be transmitted in a timely and reliable manner. The following problems mainly exist in the data transmission process:

[0003] 1) Currently, the data push service exists in multiple station nodes. Each station node has a separate publish-subscribe method. The data message format of each station node is different. The business call needs to subscribe to the publish-subscribe service of multiple station nodes, and it is impossible to unify the standardization and management of station nodes;

[0004] 2) When multiple systems need to be integrated, a large amount of adaptation code must be written, which increases the complexity and cost of integration. Summary of the invention

[0005] In order to solve the above technical problems, the present invention provides a rail transit data management method.

[0006] In a first aspect, the present invention provides a rail transit data management method, which is applied to a management system, wherein the management system includes a central end and multiple station nodes, wherein the central end and the station nodes are both deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes and the central end through the event channels, proxy modules and message queues;

[0007] The method comprises:

[0008] The central end receives a subscription request sent by a client, where the client is an external system or the station node in the management system;

[0009] The central end determines a target node among the station nodes based on the subscription request; the subscription request includes a service identifier;

[0010] The central end obtains the service data corresponding to the subscription request from the target node and sends it to the client.

[0011] In a second aspect, the present invention provides a management system, the management system comprising a central end and a plurality of station nodes, the central end and the station nodes are both deployed with an event channel, an agent module and a message queue; the station nodes and the central end perform data synchronization through the event channel, the agent module and the message queue;

[0012] The central end is used to receive a subscription request sent by a client, where the client is an external system or the station node in the management system;

[0013] The central end is used to determine the target node in the station node based on the subscription request; the subscription request includes a service identifier;

[0014] The central end is used to obtain the service data corresponding to the subscription request from the target node and send it to the client.

[0015] In a third aspect, the present invention provides an electronic device, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the rail transit data management method described in the first aspect of the present invention.

[0019] In a fourth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to implement the rail transit data management method described in the first aspect of the present invention when executed by a processor.

[0020] The rail transit data management method provided by the embodiment of the present invention is applied to a management system, which includes a central end and multiple station nodes, and the central end and the station nodes are all deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes and the central end through event channels, proxy modules and message queues; after receiving the subscription request from the client, the central end determines the target node in the station node based on the subscription request; the subscription request includes a service identifier; the client is an external system or a station node in the management system; the central end obtains the service data corresponding to the subscription request from the target node and sends it to the client. When the client is an external system, it interacts with the station node in the management system through the central end to obtain business data and send it to the external system. When the client is an internal station node, it also interacts with other station nodes through the central end to obtain business data and feed it back to the station node. If data is sent uniformly through the central end, you only need to write adaptation code for the station node, external system and central end, which greatly reduces the code writing task and also reduces the complexity and cost of integration. Each station node interacts with the central end for data. When the client is an external system, the external system does not need to interact directly with the station node, that is, the external system does not need to subscribe to the publish-subscribe services of multiple station nodes for business calls; each station node interacts with the central end for data, so the station nodes can be uniformly standardized and managed.

[0021] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 It is a structural diagram of a management system provided by an embodiment of the present invention;

[0024] Figure 2 is a flow chart of a rail transit data management method provided by an embodiment of the present invention;

[0025] Figure 3 It is a schematic diagram of the content of a configuration page of a central terminal provided by an embodiment of the present invention;

[0026] Figure 4 It is a distributed flow chart of a rail transit data interaction process provided by an embodiment of the present invention;

[0027] Figure 5 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] In one embodiment of the present invention, a rail transit data management method is provided, and the rail transit data management method is applied to a rail transit data management system, such as Figure 1 The structure diagram of a rail transit data management system shown in the figure, the management system includes a central terminal 10 and multiple station nodes 20, both of which are deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes 20 and the central terminal 10 through event channels, proxy modules and message queues. It should be noted that Figure 1 Only two station nodes are used as an example. In actual applications, there are multiple station nodes.

[0030] In the same unit (referring to the central end and the station node), the message queue sends messages to the event channel, and the agent module and the message queue send messages to each other. In different units, the event channel of unit A sends messages to the message queue of unit B.

[0031] like Figure 2 A rail transit data management method is shown, the rail transit data management method comprising:

[0032] S201. The central end receives a subscription request sent by a client, where the client is an external system or a station node in the management system.

[0033] That is to say, both the external system and the station node within the management system can send subscription requests to the central end, that is, both the external system and the station node can act as consumers of business data, and in the present invention, the station nodes are producers that provide business data.

[0034] S202. The central end determines a target node in the station node based on the subscription request; the subscription request includes a service identifier.

[0035] Station nodes may include train control nodes, station management nodes, signal nodes, ticketing nodes, passenger information nodes, etc. Each station node is responsible for different business types, and the business data produced is different. The central end pre-stores the business type of each station node. The business type can be stored in the central end in the form of a business identifier. The client's subscription request includes a business identifier, and the central end can determine the target node from multiple station nodes based on the business identifier in the subscription request.

[0036] It should also be noted that a station node may have multiple business types.

[0037] S203: The central end obtains the service data corresponding to the subscription request from the target node and sends it to the client.

[0038] After the target node is determined, the business data corresponding to the subscription request of the target node is usually obtained and sent to the client. The business data is usually the full data of the target node and / or incremental data. Full data refers to the complete data set, that is, the entire content of the entire data set. Incremental data refers to the part of the data that has been added or changed since the last processing.

[0039] In this embodiment, both the external system and the station node can serve as consumers of business data, and both the station node can serve as producers of business data.

[0040] The data interaction process that can be formed includes the following two situations: 1.

[0041] Case 1:

[0042] Subscription request sending and forwarding: external system → central terminal → station node;

[0043] Business data feedback: station node → central terminal → external system.

[0044] Case 2:

[0045] Subscription request sending and forwarding: station node A → central terminal → station node B;

[0046] Business data feedback: station node B → central end → station node A.

[0047] The central system (central end) of the line is prone to performance bottlenecks when processing data under high concurrency. By inventing a cloud-edge collaborative deployment architecture solution, the proxy module and event channel are deployed to the designated station node, and the data is pre-processed at the station node, effectively reducing the pressure on the central system. Multiple central addresses are configured at the station node. The station node will only process the data in a unified manner, and the central end will forward the data. For example, other external systems can subscribe through the central end and configure it at the central end. The central end plays the role of gateway and agent for external systems; data interaction between stations is also carried out through the central end.

[0048] The rail transit data management method provided by the embodiment of the present invention is applied to a management system, which includes a central end and multiple station nodes, and the central end and the station nodes are all deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes and the central end through event channels, proxy modules and message queues; after receiving the subscription request from the client, the central end determines the target node in the station node based on the subscription request; the subscription request includes a service identifier; the client is an external system or a station node in the management system; the central end obtains the service data corresponding to the subscription request from the target node and sends it to the client. When the client is an external system, it interacts with the station node in the management system through the central end to obtain business data and send it to the external system. When the client is an internal station node, it also interacts with other station nodes through the central end to obtain business data and feed it back to the station node. If data is sent uniformly through the central end, you only need to write adaptation code for the station node, external system and central end, which greatly reduces the code writing task and also reduces the complexity and cost of integration. Each station node interacts with the central end for data. When the client is an external system, the external system does not need to interact directly with the station node, that is, the external system does not need to subscribe to the publish-subscribe services of multiple station nodes for business calls; each station node interacts with the central end for data, so the station nodes can be uniformly standardized and managed.

[0049] In an optional embodiment of the present invention, when the central end and the station node are synchronizing data, the one that sends data is regarded as the sender, and the one that receives data is regarded as the receiver. The data interaction process between the sender and the receiver includes: the sender's agent module sends the data to the sending message queue; the sender's event channel transfers the data in the sender's message queue to the receiver's message queue; the receiver's agent module obtains data from the receiver's message queue.

[0050] In an example, when the data of station node A needs to be synchronized to station node B, station node B can subscribe to messages from station node A through the central end. The agent module of station node A sends the data to the message queue of station node A, and then sends it to the message queue of the central end through the event channel of station node A. The central end sends the data in the message queue to the message queue of station node B through its own internal event channel, and the agent module of station node B can obtain the data from its own internal message queue.

[0051] In another example, when the data of station node A needs to be synchronized to an external system, the external system can subscribe to messages from station node A through the central end. The agent module of station node A sends the data to the message queue of station node A, and then sends it to the message queue of the central end through the event channel of station node A. The agent module of the central end sends the data in the message queue to the external system.

[0052] In an optional embodiment, the subscription request also includes a business data range, and the business data range includes incremental data and full data. A database is provided in the proxy module of the central end, and the configuration information of the client is stored in the database.

[0053] The central end obtains the business data corresponding to the subscription request from the target node and sends it to the client, including: the central end determines the business data range according to the subscription request; the proxy module of the central end obtains the full data corresponding to the business identifier from the target node as the business data; and sends the business data to the client according to the configuration information; when the business data range includes incremental data, the proxy module of the central end obtains the incremental data corresponding to the business identifier from the target node as the business data; and sends the business data to the client according to the configuration information.

[0054] In an optional example, the configuration parameters include a sending method, a service IP address, a service port and a URL, and the proxy module of the central end sends the business data to the client according to the configuration information, including: the central end sends the business data to the space pointed to by the service IP address, service port and URL in the sending method, so as to send the business data to the client.

[0055] Specifically, the identity ID of each client (external system or station node) is unique, so fixed configuration parameters can be set for each client, and the configuration parameters of each client are set in the configuration page. After the configuration is completed, the configuration parameters can be stored in the local storage space of the central end. Then, when the client sends a subscription request, the subscription request may not carry configuration parameters. When the central end receives the subscription request, the subscription request usually also includes the identity ID of the client, and the central end can obtain the parameter configuration corresponding to the identity ID from the local match. Of course, the configuration parameters can also be carried by the subscription request sent by the client, and the central end reads the client's configuration parameters from the subscription request.

[0056] Figure 3 A schematic diagram of the contents of a central configuration page, such as Figure 3 As shown, the configuration parameters include the sending method, service IP address, service port and URL, and can also include the subscription topic name, subscription content, request type, business data range ( Figure 3 The corresponding sliding buttons for incremental and full in the text box. The sending method can be websocket, http, etc. By changing the data range parameters (full + incremental, incremental only) and other configuration parameters in the configuration file through the visualization page, the subscription method can be dynamically updated and take effect in real time. It supports dynamic switching of subscription methods on the subscription configuration page without restarting the system, solving the problem that the system must be restarted to take effect when switching subscription methods during operation.

[0057] In addition, the central end may also include a data publishing page, through which the content of published data may be viewed in real time.

[0058] In an optional embodiment of the present invention, when the service data range includes incremental data, after the proxy module of the central end subscribes to the topic of the message queue of the central end, the method further includes:

[0059] When the proxy module of the central end monitors that the central end is disconnected from the client, it sends a stop push instruction to the internal message queue; the central end synchronizes the stop push instruction to the message queue in the target node through the internal event channel; when the proxy module of the target node obtains the stop push instruction from the message queue of the target node, it stops pushing incremental data to the message queue of the target node.

[0060] When the central end is disconnected from the client, it means that the communication channel between the two is disconnected. At this time, the client cannot receive the data sent by the central end. Therefore, the central end interacts with the target node to control the target node to stop pushing incremental data to prevent the central end from continuously receiving redundant data.

[0061] In order to clearly illustrate the rail transit data management method of the present invention, Figure 4 And the following example to illustrate, Figure 4 It is a distributed flow chart of the rail transit data interaction process. Figure 4 In this example, WS stands for websocket and MQ stands for message queue. Figure 4 As shown in the figure, the rail transit data interaction process is as follows:

[0062] 1.1. The client sends a subscription request with a service identifier to the central proxy module, requesting the WS subscription interface;

[0063] 1.2. The central proxy module reads the business data range of the subscription request in the local configuration file.

[0064] The specific business data range includes incremental only, full data + incremental;

[0065] When the business data range is full + incremental, first execute steps 1.3-1.5, then execute steps 2.1-2.3;

[0066] When the business data range is incremental only, execute 1.6 first, and then directly execute steps 2.1-2.3;

[0067] 1.3. The proxy module at the central end requests the target node (sends business data) according to the configuration parameters;

[0068] 1.4. Return all data;

[0069] Specifically, the target node (station node) sends the full data to the MQ at the central end, and the agent module at the central end obtains the full data from the MQ;

[0070] 1.5. The central proxy module pushes all data to the client through WS;

[0071] 1.6. The central agent module asynchronously sends a message to the MQ topic to notify the target node to start pushing incremental data;

[0072] At this time, the central MQ continuously receives incremental data pushed by the target node;

[0073] 2.1. The central agent module subscribes to the MQ topic and monitors the subsequent incremental data;

[0074] 2.2. The central agent module receives the data from MQ, which is the incremental data;

[0075] 2.3. The central proxy module pushes incremental data to the client through WS;

[0076] 3.1. The proxy module at the central end monitors the disconnection event of WS;

[0077] 3.2. After WS is disconnected, the (central end proxy module) asynchronously sends a message to the (central end) MQ topic to notify the target node to stop pushing incremental data.

[0078] This time, the central proxy module includes a database. When the proxy module receives a subscription request from the client, it can also store the current client information and subscribed topics, and support viewing client connections, subscribed topics, and query data in the platform's management interface.

[0079] In an optional embodiment of the present invention, the communication message protocol between the client and the management system and the communication message protocol within the management system are both preset universal message protocols. In the prior art, message conversion between different formats takes time, resulting in delays in information transmission, affecting the real-time performance and responsiveness of the system. This embodiment adopts a universal message protocol, which can reduce the delay in information transmission and improve the real-time performance and responsiveness of the system.

[0080] Information Protocol is a protocol used in computer networks to specify the format, content and rules of data transmission. It defines how data is organized, encoded, transmitted and decoded to ensure that data can be correctly and efficiently transmitted and processed between different systems.

[0081] In this embodiment, the communication message protocol defines the message attributes that must be included in the message data when the message data is transmitted, specifically including the following message attributes:

[0082] 1. ID

[0083] Type: string;

[0084] Description: Identifies an event. Producers must ensure that source+id is unique for each individual event. If a duplicate event is resent (e.g. due to a network error), it may have the same id. Consumers may consider events with the same source and id to be duplicates.

[0085] Constraints: 1. Message attributes that must be included; 2. Must be a non-empty string; 3. Must be unique within the producer scope.

[0086] Examples: 1. Event counter maintained by the producer; 2. UUID

[0087] 2. source

[0088] Type: URI-reference;

[0089] Description: Identifies the context in which the event occurred. Typically includes information such as the type of event source, the organization that published the event, or the process that produced the event. The exact syntax and semantics behind the data encoded in the URI are defined by the event producer. The producer must ensure that the source+id is unique for each independent event. Applications can assign a unique source to each independent producer, which makes it easy to generate unique IDs because no other producer will have the same source. Applications can use UUIDs, URNs, DNS authorities, or application-specific schemes to create unique source identifiers. A source can also include multiple producers. In this case, producers must cooperate to ensure that the source+id is unique for each independent event.

[0090] Constraints: 1. Message attributes must be included; 2. Must be a non-empty URI-reference; 3. Absolute URI is recommended

[0091] Example: A unique URI on the entire network with DNS authority

[0092] 3. Specversion

[0093] Type: string;

[0094] Description: The version of the CloudEvents specification used by the event. This version can be used to interpret the context.

[0095] Constraints: 1. Message attributes that must be included; 2. Must be a non-empty string; 3. Must be unique within the producer scope.

[0096] 4. type

[0097] Type: string;

[0098] Description: This attribute contains a value describing the event type associated with the originating event. This attribute is typically used for routing, monitoring, policy enforcement, etc. The format of this attribute is defined by the producer.

[0099] Constraints: 1. Must contain message attributes; 2. Must be a non-empty string; 3. Should be prefixed with a reversed DNS name. The prefix field determines the organization that defines the semantics of this event type.

[0100] 5. Data

[0101] Type: string;

[0102] Description: Message content.

[0103] In a specific example, the message attributes included in the message data are as follows:

[0104]

[0105]

[0106] In addition, the management system of the present invention can also disclose standardized interfaces and docking processes to external systems to improve docking performance and efficiency.

[0107] Table 1 shows an example of a unified data publishing interface:

[0108] Table 1. Unified data publishing interface content

[0109]

[0110] The following is an example of a unified data subscription interface:

[0111] Table 2. Unified data subscription interface content

[0112]

[0113] In Table 1 and Table 2, Event-Broker is the proxy module at the central end.

[0114] In general, the present invention discloses a publishing and subscription platform based on a visual page, which can view the data content of publishing or subscription in real time, perform unified format verification on the published content, and dynamically configure the subscription method and subscribed data content on the page. The push of data is integrated and unified. It provides unified data publishing and subscription, and pushes data services for other business systems to call. It supports general message definition and realizes real-time data synchronization between systems. Compared with the prior art, the differences and advantages of the technical solution of the present invention are mainly:

[0115] 1) Visual data presentation and interactive design, based on the publishing and subscription platform of the visualization page, can view the published or subscribed data content in real time, perform unified format verification on the published content, and dynamically configure the subscription method and subscribed data content on the page. The push of data is integrated and unified. Provide unified data publishing and subscription, and push data services for other business systems to call.

[0116] 2) Reduce development complexity: Developers do not need to write a dedicated parser or conversion tool for each different message format. They only need to develop once to adapt to all messages. The unified format and interface specifications make development and maintenance easier and reduce duplication of work.

[0117] 3) Improve data consistency and controllability: A unified message format can ensure the standardization of message content, so that all parties have consistent interpretations of the message, reducing ambiguity and misunderstanding. It is easier to check the validity of the message to ensure that the data is complete and accurate. For example, you can add a check field or protocol header to the format to facilitate troubleshooting.

[0118] 4) Improve performance and efficiency: Since developers only need to implement and optimize one format processing logic, a unified format helps optimize code execution efficiency and reduce performance loss. A unified format also facilitates optimization of message compression, caching, and transmission efficiency, making the overall system operation more efficient.

[0119] Corresponding to the rail transit data management method in the present invention, the present invention also provides a management system, such as Figure 1 As shown, the management system includes a central end and multiple station nodes, and both the central end and the station nodes are deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes and the central end through the event channels, proxy modules and message queues;

[0120] The central end is used to receive a subscription request sent by a client, where the client is an external system or the station node in the management system;

[0121] The central end is used to determine the target node in the station node based on the subscription request; the subscription request includes a service identifier;

[0122] The central end is used to obtain the service data corresponding to the subscription request from the target node and send it to the client.

[0123] Optionally, when the central end and the station node perform data synchronization, the one that sends data is used as the sender, and the one that receives data is used as the receiver. The data interaction process between the sender and the receiver includes:

[0124] The proxy module of the sender is used to send data to the message queue in the sender;

[0125] The event channel of the sender is used to transfer the data in the message queue of the sender to the message queue of the receiver;

[0126] The agent module of the receiver is used to obtain data from the message queue of the receiver.

[0127] Optionally, the subscription request further includes a service data range, and the proxy module of the central end is provided with a database, and the configuration information of the client is stored in the database;

[0128] The central end is used to determine the service data range according to the subscription request;

[0129] When the service data range includes full data, the proxy module of the central end is used to obtain the full data corresponding to the service identifier from the target node as the service data; and send the service data to the client according to the configuration information;

[0130] When the service data range includes incremental data, the proxy module of the central end is used to obtain the incremental data corresponding to the service identifier from the target node as service data; and send the service data to the client according to the configuration information.

[0131] Optionally, the configuration parameters include sending method, service IP address, service port and URL,

[0132] The central end is used to send the business data to the space pointed to by the service IP address, service port and URL in the sending manner, so as to send the business data to the client.

[0133] Optionally, when the business data range includes incremental data, the proxy module of the central end is used to send the subscription request to the message queue of the central end, and send it to the message queue of the target node through the event channel of the central end;

[0134] The proxy module of the target node is used to obtain the subscription request in the message queue of the target node, and feed back the incremental data corresponding to the service identifier in the subscription request to the internal message queue;

[0135] The incremental data in the message queue of the target node is synchronized to the message queue of the central end through the event channel inside the target node;

[0136] The proxy module of the central end is used to subscribe to the topic of the message queue of the central end, and obtain incremental data from the message queue of the central end as business data.

[0137] Optionally, the proxy module of the central end is further used to send a stop push instruction to an internal message queue when monitoring that the central end is disconnected from the client;

[0138] The central end is used to synchronize the stop push instruction to the message queue in the target node through an internal event channel;

[0139] The proxy module of the target node is used to stop sending incremental data to the message queue of the target node when obtaining the stop push instruction from the message queue of the target node.

[0140] Optionally, the communication message protocol between the client and the management system and the communication message protocol within the management system are both preset universal message protocols.

[0141] The management system provided by the embodiment of the present invention can execute the rail transit data management method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0142] Figure 5 A schematic diagram of the structure of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0143] like Figure 5 As shown, the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 to the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0144] A number of components in the electronic device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0145] The processor 41 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 executes the various methods and processes described above, such as the rail transit data management method.

[0146] In some embodiments, the rail transit data management method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 40 via the ROM 42 and / or the communication unit 49. When the computer program is loaded into the RAM 43 and executed by the processor 41, one or more steps of the rail transit data management method described above may be performed. Alternatively, in other embodiments, the processor 41 may be configured to execute the rail transit data management method in any other appropriate manner (e.g., by means of firmware).

[0147] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0148] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0149] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0150] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0151] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0152] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0153] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0154] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A rail transit data management method, characterized in that: Applied to a management system, the management system includes a central terminal and multiple station nodes, the central terminal and the station nodes are both deployed with event channels, proxy modules and message queues; Data synchronization is performed between the station node and the central end through event channels, proxy modules and message queues; The method comprises: The central end receives a subscription request sent by a client, where the client is an external system or the station node in the management system; The central end determines a target node among the station nodes based on the subscription request; the subscription request includes a service identifier; The central end obtains the service data corresponding to the subscription request from the target node and sends it to the client.

2. The method according to claim 1, characterized in that When the central end and the station node perform data synchronization, the one that sends data is regarded as the sender, and the one that receives data is regarded as the receiver. The data interaction process between the sender and the receiver includes: The agent module of the sender sends the data to the message queue in the sender; The event channel of the sender transmits the data in the message queue of the sender to the message queue of the receiver; The agent module of the receiver obtains data from the message queue of the receiver.

3. The method according to claim 1, characterized in that The subscription request also includes a service data range, and the proxy module of the central end is provided with a database, and the configuration information of the client is stored in the database; The central end obtains the service data corresponding to the subscription request from the target node and sends the service data to the client, including: The central end determines the service data scope according to the subscription request; When the service data range includes full data, the proxy module of the central end obtains the full data corresponding to the service identifier from the target node as service data; and sends the service data to the client according to the configuration information; When the service data range includes incremental data, the proxy module of the central end obtains the incremental data corresponding to the service identifier from the target node as service data; and sends the service data to the client according to the configuration information.

4. The method according to claim 3, characterized in that The configuration parameters include a sending method, a service IP address, a service port and a URL, and the proxy module of the central end sends the service data to the client according to the configuration information, including: The central end sends the business data to the space pointed to by the service IP address, service port and URL in the sending manner, so as to send the business data to the client.

5. The method according to claim 3, characterized in that When the service data range includes incremental data, the proxy module of the central end obtains the incremental data corresponding to the service identifier from the target node as the service data, including: When the service data range includes incremental data, the proxy module of the central end sends the subscription request to the message queue of the central end, and sends it to the message queue of the target node through the event channel of the central end; The proxy module of the target node obtains the subscription request in the message queue of the target node, and feeds back the incremental data corresponding to the service identifier in the subscription request to the internal message queue; The incremental data in the message queue of the target node is synchronized to the message queue of the central end through the event channel inside the target node; The proxy module of the central end subscribes to the topic of the message queue of the central end, and obtains incremental data from the message queue of the central end as business data.

6. The method according to claim 5, characterized in that Also includes: When the proxy module of the central end detects that the central end is disconnected from the client, the proxy module of the central end sends a stop push instruction to the internal message queue; The central end synchronizes the stop push instruction to the message queue in the target node through an internal event channel; When the proxy module of the target node obtains the stop push instruction from the message queue of the target node, it stops sending incremental data to the message queue of the target node.

7. The method according to any one of claims 1 to 6, characterized in that: The communication message protocol between the client and the management system and the communication message protocol within the management system are both preset universal message protocols.

8. A management system, characterized in that: The management system includes a central terminal and multiple station nodes, and both the central terminal and the station nodes are deployed with event channels, proxy modules and message queues; data synchronization is performed between the station nodes and the central terminal through the event channels, proxy modules and message queues; The central end is used to receive a subscription request sent by a client, where the client is an external system or the station node in the management system; The central end is used to determine a target node among the station nodes based on the subscription request; The subscription request includes a service identifier; The central end is used to obtain the service data corresponding to the subscription request from the target node and send it to the client.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the rail transit data management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the rail transit data management method according to any one of claims 1 to 7 when executed.

Images