WO2020038447A1

WO2020038447A1 - Integrated network management method and apparatus for rail traffic system, and system

Info

Publication number: WO2020038447A1
Application number: PCT/CN2019/102064
Authority: WO
Inventors: 邓喜年
Original assignee: 比亚迪股份有限公司
Priority date: 2018-08-23
Filing date: 2019-08-22
Publication date: 2020-02-27
Also published as: CN110858850A; CN110858850B

Abstract

The present disclosure proposes an integrated network management method and apparatus for a rail traffic system, and an integrated network management system for rail traffic. Said method is used for data transmission management between subsystem network managers and a data processing center in a rail traffic system, and comprises: receiving data uploaded by subsystem network managers, and converting the data into normalized message data in a universal data schema; transmitting the normalized message data to a message queue middleware server; the message queue middleware server acquiring the topic of the normalized message data, and publishing the message data according to the topic; and according to a subscription topic of the data processing center, sending, to the data processing center, message data having the subscription topic in the message queue middleware server. The present invention reduces the direct coupling of data between the data processing center and subsystem network managers, ensures the stability of the whole integrated network management system, and ensures the integrity of data by using the high availability of the message queue middleware.

Description

Comprehensive network management method, device and system of rail transit system

Cross-reference to related applications

This application claims the priority of Chinese Patent Application No. “201810967894.X” filed by BYD Co., Ltd. on August 23, 2018 with the invention name “A Comprehensive Network Management Method, Device and System for Rail Transit System”.

Technical field

The present disclosure relates to the technical field of rail transit, and more particularly, to a method and device for integrated rail management of a rail transit integrated network management system, and a rail transit integrated network management system.

Background technique

The rail transit management system is the basis of rail transit operations. It is used to manage various subsystems and equipment in the rail transit system. Efficient and error-free operation is a basic requirement of the rail transit system. The rail transit system is a complex system, which includes numerous subsystems and a large number of system equipment, and each subsystem often includes its own subsystem network management. Therefore, the composition of the rail transit system is very complicated. Generally speaking, the rail transit management system can include an integrated network management system. The integrated network management system includes the components of the network management of each subsystem, the data processing center, and the integrated network management center. The integrated network management system performs unified management of the network management of each subsystem. This requires the integrated network management system to comprehensively grasp and centrally process the equipment status information and alarm information of each subsystem, and has high requirements for the communication and information processing capabilities of the integrated network management system.

In the related technical solution, the network management of each subsystem is directly connected to the data processing center of the integrated network management. The data processing center of the integrated network management is responsible for processing the acquired device data information and saving the final data to the storage device. In this way, it is possible to implement basic monitoring of the status of the equipment of each subsystem and storage of various information. However, when there are too many subsystems, or there are too many devices in the system, and a large amount of real-time data is concurrent, it is difficult to ensure that the system will not have data Lost, system reliability is difficult to guarantee.

Summary of the Invention

The present disclosure aims to solve at least one of the technical problems in the related art described above to a certain extent. Provided is a comprehensive network management method for a rail transit system that can ensure that data is processed and stored in a timely manner and will not be lost when the network management of multiple subsystems sends data.

In order to achieve the above object, according to an embodiment of the first aspect of the present disclosure, an integrated network management method for a rail transit system is provided, which is used for data transmission management between a subsystem network manager and a data processing center in the rail transit system, and includes:

The interface adapter module receives data uploaded by the subsystem network manager, and converts the data into standardized message data with a common data mode;

The interface adapter module transmits the normalized message data to a message queue middleware server;

Obtaining, by the message queue middleware server, the subject of the normalized message data, and publishing the message data according to the subject;

The message queue middleware server sends the message data having the subscription topic in the message queue middleware server to the data processing center according to the subscription topic of the data processing center.

In some embodiments, the receiving data uploaded by the network manager of the subsystem and converting the data into normalized message data with a common data mode includes:

Receiving the data uploaded by the network manager of the subsystem according to the first protocol, and analyzing and obtaining the parsed data according to the first protocol;

Converting the parsed data into normalized message data with a universal data pattern according to a second protocol;

The first protocol and the second protocol are different communication protocols.

In some embodiments, the transmitting the normalized message data to a message queue middleware server includes:

And transmitting the normalized message data to the message queue middleware server according to the sequence of the key values by using the identification identifier of the network management of each subsystem as a key value.

In some embodiments, the message queue middleware server obtaining the subject of the normalized message data and publishing the message data according to the subject includes:

Establishing a corresponding message queue on the message queue middleware server for each of the subsystem network managers,

Obtain a source subsystem network manager of the message data, and publish the message data to a message queue corresponding to the source subsystem network manager.

In some embodiments, the integrated network management method for a rail transit system further includes:

The message queue middleware server periodically checks the messages in the message queue middleware server, and clears messages that satisfy the preset discarding conditions from each message queue.

In some embodiments, after sending the message data having the subscription topic in the message queue middleware server to the data processing center according to the subscription topic of the data processing center, the method further includes:

The data processing center classifies and stores the message data, stores temporary data in the message data in a local database, and stores device monitoring data in a cloud database.

Through the comprehensive network management method of the rail transit system disclosed in the present disclosure, the direct coupling of data between the data processing center and the network management of each subsystem can be reduced by using a two-layer separated structure mode of the integrated network management data processing center and the message queue middleware server. Ensure the stability of the entire integrated network management system.

In order to achieve the above objective, an embodiment according to the second aspect of the present disclosure provides an integrated network management device for a rail transit system, which is used for data transmission management between a subsystem network manager and a data processing center in the rail transit system, and includes:

An interface adapter module, configured to receive data uploaded by a network management system of a subsystem, convert the data into normalized message data with a common data mode, and transmit the normalized message data to a message queue middleware server;

The message queue middleware server is configured to obtain the subject of the normalized message data, and publish message data according to the theme, and according to the subscription theme of the data processing center, the message queue middleware server has the subscription theme. The message data is sent to the data processing center.

In some embodiments, the interface adapter module receives data uploaded by a subsystem network manager, and converts the data into normalized message data with a common data mode, including:

In some embodiments, the interface adapter module transmitting the normalized message data to a message queue middleware server includes:

And transmitting the normalized message data to the middleware server in the order of the key values by using the identification identifier of the network management of each subsystem as a key value.

In some embodiments, the message queue middleware server is further configured to:

Periodically check the messages in the message queue middleware server, and clear the messages that meet the preset discard conditions from each message queue.

Through the integrated network management device of the rail transit system disclosed in the present disclosure, the use of a two-layer separated structure mode of the integrated network management data processing center and the message queue middleware server can reduce the direct coupling of data between the data processing center and the network management of each subsystem to ensure The stability of the entire integrated network management system.

In order to achieve the above object, an embodiment according to the third aspect of the present disclosure provides an integrated network management system for a rail transit system, which includes a plurality of subsystem network managers, a data processing center, a database, and an integrated network management center that are communicatively connected, and further includes: The integrated network management device for a rail transit system according to any one of the embodiments of the second aspect, the integrated network management device for the rail transit system is communicatively connected with the multiple subsystem network managers and the data processing center for the multiple subsystems Data transmission management between the network management and the data processing center.

In some embodiments, the data processing center is further configured to classify and store message data, store temporary data in the message data in a local database, and store device monitoring data in a cloud database;

The integrated network management center is further configured to obtain the device monitoring data from the cloud database, and perform device monitoring and fault statistical processing and big data analysis.

The integrated rail transit network management system according to the embodiment of the third aspect of the present disclosure has similar advantageous effects as the methods and devices of the first and second aspects, and will not be described again.

In order to achieve the above object, an embodiment according to the fourth aspect of the present disclosure provides an electronic device including a processor and a memory; wherein, the processor runs the program by reading executable program code stored in the memory. The program corresponding to the executable program code is described for implementing the integrated network management method of the rail transit system according to the embodiment of the first aspect.

In order to achieve the above object, an embodiment according to the fifth aspect of the present disclosure provides a non-transitory computer-readable storage medium on which a computer program is stored, characterized in that the program is implemented as the first aspect when executed by a processor. Comprehensive network management method for rail transit system according to the embodiment.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

Figure 1 is a schematic diagram of the working principle of a message queue based on the publish-subscribe mode;

2 is a structural block diagram of an integrated network management system of a rail transit system according to an embodiment of the present disclosure;

3 is a schematic flowchart of an integrated network management method for a rail transit system according to an embodiment of the present disclosure;

4 is a schematic diagram of a storage structure of a message queue according to an embodiment of the present disclosure;

5 is a structural block diagram of a rail transit integrated network management system according to another embodiment of the present disclosure;

6 is a structural block diagram of a message queue middleware server according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of an integrated network management work process of a rail transit system according to an embodiment of the present disclosure.

detailed description

Hereinafter, embodiments of the present disclosure will be described in detail. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary, and are intended to explain the present disclosure, and should not be construed as limiting the present disclosure.

One of the reasons for the various shortcomings in the related technology is that in this type of solution, the processing center is directly connected to the network management of each subsystem. It requires the data comprehensive network management processing center to have strong concurrent processing capabilities. When the data processing center receives a large amount of each subsystem, When real-time information about equipment status and alarm information, the integrated network management data processing center must not only match the data of each subsystem, but also quickly process and save the received data. If the data cannot be processed in time, a large amount of data is accumulated. In the server, it is easy to cause data loss.

In addition, after receiving the data, the integrated network management data processing center processes the data in a first-come, first-served manner. However, due to network transmission delays and other issues, the previous data of a device may be received late, resulting in the delayed data covering the latest Data, so that deviations occur in real-time monitoring of the device.

The main technical ideas of the present disclosure include: providing a message queue middleware server, the message queue middleware server is provided with the message queue middleware, and the data that each subsystem network manager needs to provide to the data processing center is relayed via the message queue middleware server, Thus decoupling the network management and data processing center of each subsystem. Specifically, the message data of the network management of each subsystem will not be directly sent to the data processing center, but will be sent to the message queue middleware server first; the message queue middleware server obtains the subject of the message data, and according to the message The topic of the data is published; after that, the message queue middleware server sends the message data in each message queue to the data center in turn according to the subscription information of the subsystem network management data processing center. That is, the data processing center does not directly obtain data from the subsystem network management interface, but obtains data from the message queue middleware server.

As a result, the use of a two-layered separation mode of the integrated network management data processing center and the message queue middleware server can reduce the direct coupling of data between the data processing center and the network management of each subsystem, and ensure the stability of the overall integrated network management system. Using the high availability of the message queue middleware to ensure the integrity of the data, it solves the problem of message loss under unreliable networks and performance bottlenecks under high concurrency, as well as the downstream integrated network management data when the subsystem network management message flood occurs. Flow shock caused by the processing center.

In order to facilitate the understanding of this disclosure, some basic concepts of the message queue technology and the working principle of the publish-subscribe model are briefly introduced first. It should be noted that, in the present disclosure, various concepts related to the message queue technology are subject to the general meanings in the art. The following introduction is only for the convenience of understanding of the present disclosure, and cannot be considered as the full meaning of each concept. Or extensions.

Message producer (producer): sends a message to the message queue.

Message consumer (consumer): Receive messages from the message queue.

Message queue: A first-in-first-out message storage area. Messages are sent and received in order. Once the message is consumed, the message is deleted from the queue.

Message (message) is a unit of data transmission in the message queue transmission mechanism. A message can be a piece of data. It can be understood by one or more applications and is the carrier of information passed between applications.

Topic: An identifier that can be considered a message. The message producer can add topics to the message and publish them to the message queue middleware according to the topic, and the message consumer subscribes to the required topic. In the art, sometimes the topic is used to represent the publish-subscribe model or such a working mode. Through the topic and publish-subscribe model of a message, you can support a mechanism to send a message to multiple subscribers.

Point-to-point message queue model: A producer sends messages to a specific queue, and a consumer receives messages from the queue. The producer and consumer of a message can not be running at the same time. Each successfully processed message is acknowledged by the message consumer. In this mode, each message is sent to a message consumer.

Publish-subscribe message model: In the publish-subscribe model, message producers can publish messages based on a specific message topic. A message consumer may be interested in receiving messages from a specific message topic, and can subscribe to topics of interest to get the corresponding messages under that topic. Each message can have one or more topics, and each topic may have 0, 1 or more subscribers. Under this model, publishers and subscribers can be decoupled from each other without knowing each other's existence.

Referring to FIG. 1, a working principle of a publish-subscribe mode of setting a queue according to a topic in a message queue is shown. A message producer generates a message with a subject and publishes the message to the message queue corresponding to the subject. The messages in the message queue will be sent to all message consumers subscribed to the message topic, such as message consumer 1 and message consumer 2. Thus, one message can be sent to multiple recipients.

The method and device of the embodiments of the present disclosure are described in detail below with reference to the drawings.

2 is a schematic structural diagram of an integrated network management system of a rail transit system according to an embodiment of the present disclosure. The integrated network management system 10 includes a plurality of subsystem network management systems 300, an integrated network management device 200, a data processing center 100, an integrated network management center 400, and a database 500. The various parts of the system are connected through wired or wireless communication. The data generated by the multiple subsystem network management device 300 is sent to the integrated network management device 200, and then processed by the integrated network management device 200 and sent to the data processing center.

First, with reference to FIG. 3, the integrated network management method of the rail transit system from the perspective of the integrated network management device 200 will be described. FIG. 3 is a schematic flowchart of an integrated network management method for a rail transit system according to an embodiment of the present disclosure.

Referring to FIG. 3, the integrated network management method for a rail transit system of the present disclosure is mainly used for data transmission management between a subsystem network manager and a data processing center in the rail transit system, and may include steps S110 to S140. In some embodiments, the integrated network management method of the rail transit system may further include steps S150 and S160.

S110: The interface adapter module receives data uploaded by the subsystem network manager, and converts the data into standardized message data with a common data mode.

Subsystem network management of the rail transit system may include clock system network management, FAS (fire alarm system) system network management, broadcast system network management, video monitoring system network management, passenger service system network management, and the like. The network management of each subsystem may use different protocols for communication, and the uploaded data also has different formats. Therefore, format conversion is needed to facilitate unified processing and storage in the data processing center.

For example, the interface adapter module may receive the data uploaded by the subsystem network manager according to the first protocol, and parse and obtain the parsed data according to the first protocol; convert the parsed data into a common data mode according to the second protocol Normalized message data. The first protocol and the second protocol may be different communication protocols. The first protocol is usually determined based on the type of network management of the subsystem, while the second protocol is based on the communication and data requirements of the data processing center.

S120: The interface adapter module transmits the normalized message data to a message queue middleware server.

The standardized message data has a common data mode of the integrated network management system, which facilitates operations in the subsequent data processing process. Aiming at the disorder of a large amount of data processing in the related technology, it may happen that the data received first is processed lagging, but the new data is overwritten by the lagging data, which leads to errors in the monitoring of equipment status and misleads network management personnel In order to make the data more orderly, the transmitting the normalized message data to the message queue middleware server may include sending the normalized message data to the sub-network management identifier of each subsystem as a key value in order. The middleware server can thereby ensure that the data of the network management of a single subsystem is sequentially consumed in accordance with the acquisition time sequence, and solves the problem that old data overwrites new data. Of course, it can also be sent to the middleware server in the other order, for example, in the order of receiving the message data.

S130. The message queue middleware server obtains a subject of the normalized message data, and publishes the message data according to the subject.

The message queue middleware works in a publish-subscribe mode. It can adopt various organizational forms such as setting up only one message queue or setting multiple message queues according to the theme.

In order to ensure that data of the same subsystem is sent and received in order, the message queue middleware server acquiring the subject of the normalized message data and publishing the message data according to the subject may include: in the message queue middleware The server establishes a corresponding message queue for each of the subsystem network managers, obtains the source subsystem network manager of the message data, and publishes the message data to a message queue corresponding to the source subsystem network manager.

4 is a schematic diagram of a storage structure of a message queue according to an embodiment of the present disclosure.

For example, in the rail transit integrated network management system, there are n subsystem network managers in total, and message queues M1, M2 to Mn are established for each subsystem network manager. Each message queue Mp is used to store message data from the subsystem network management p, p ∈ [1, n], p is a natural number. When new message data arrives at the message queue middleware server, it will be posted to the corresponding message queue according to its source (for ease of operation, the source subsystem of the message data can be used as a topic for the message). The system network management's identification (ID value, such as 1 to n) is issued in sequence. Of course, the identification of the subsystem network management may also be in other forms, for example, letters or a combination of letters and numbers. The purpose of this embodiment is only to use the identification identifier as a reference for the order of sending message data, and not to set priorities for corresponding subsystems. Therefore, the normalized message data may use the identification of the network management of each subsystem as a key value, and data transmission may be performed in a certain specified order according to the key value. There is no special requirement for the ordering relationship between the network management of each own system.

The length of each message queue can be different. For example, the message queue M1 includes message data M11 to M1i, and the topics of M11 to M1i are message data from the system network management 1. The message queue M2 includes message data M21 to M2j. The topics of M21 to M2j are message data from subsystem network manager 2. The message queue Mn includes message data Mn1 to Mnk, and the topics of Mn1 to Mnk are message data from subsystem network manager n.

Through the above-mentioned construction method of the message queue, it can be ensured that, for each message queue, each message data in the message queue is arranged in chronological order. Therefore, according to the working principle of the message queue, the message data in each message queue can be obtained by the data processing center in chronological order. It is guaranteed that the information and instructions of the same subsystem NMS are sent and received in order, while the messages and instructions of the NMS of different subsystems can be out of order.

Or alternatively, a corresponding message queue can be established according to the topic of the message data. This method is applicable to a scenario where the number of topic topics of the message data is relatively determined, and the data processing center has special needs for a certain type of topic. At this time, the priority can be sorted according to a preset subscription topic of the data processing center, for example, a topic corresponding to real-time data is given a higher priority. Correspondingly, when transmitting data to a data processing center, priority is given to data of a high priority topic.

In addition, since the data processing center selects the topics to be subscribed according to the needs, there may be cases where the data uploaded by the network manager of some subsystems is not subscribed. In order to prevent these unnecessary data from occupying system resources, periodic cleaning can be performed. For example, the message queue middleware server may periodically check the messages in the message queue middleware server, and clear the messages that satisfy the preset discard conditions from each message queue. For example, the preset discard condition may be that the topic of the message has not been subscribed, and the message exists in the message queue middleware server for longer than a preset duration threshold. For example, for temporary data exceeding 1 day or several days, non-temporary data exceeding One month or several months have not been subscribed by the data processing center, that is, cleared.

S140. The message queue middleware server sends the message data with the subscription topic in the message queue middleware server to the data processing center according to the subscription topic of the data processing center.

The message queue middleware server can be located in a geographically adjacent machine room to the data processing center, thereby reducing the transmission delay of message data. It can also be set separately, which is not required by this disclosure.

S150: The data processing center sorts and stores the message data, stores temporary data in the message data in a local database, and stores device monitoring data in a cloud database.

Temporary data does not need to be stored for a long time. It is stored in a local database to facilitate the processing of the data and is deleted periodically after processing. Does not take up too much resources. The device monitoring data may need to be stored for a long time, and other systems, such as the integrated network management center, may call the device monitoring data. Therefore, a cloud database exists to facilitate data sharing and save limited local storage resources.

S160: The integrated network management center obtains the device monitoring data from the cloud database, and performs device monitoring and fault statistical processing and big data analysis.

The integrated network management center can obtain the network management data of each subsystem from the cloud through the database access interface, and perform corresponding monitoring and troubleshooting according to the device monitoring data. With the increasing maturity of artificial intelligence and big data technologies, AI and big data methods can be used to further analyze equipment monitoring data to obtain further information about equipment operation and maintenance.

By adopting the integrated network management method of the rail transit system of the present disclosure, the data output by the network management of each subsystem is not directly transmitted to the integrated network management data processing center, but is first transmitted to the message queue middleware server, and the integrated network management data processing center is not directly from The system network management interface obtains data, but obtains data from the message queue middleware.

The use of a two-layered separation mode of the integrated network management data processing center and the message queue middleware server can reduce the direct coupling of data between the data processing center and the network management of each subsystem to ensure the stability of the overall integrated network management system. The high availability of the message queue middleware in the message queue server guarantees the integrity of the data, and it solves the problem of message loss under unreliable networks and performance bottlenecks in high concurrency situations, as well as the downstream integration of subsystem network management message floods. Traffic impact caused by the network management data processing center.

In order to implement the method in the embodiment of the first aspect, the embodiment of the second aspect of the present disclosure proposes an integrated network management device for a rail transit system.

The implementation of the apparatus may include one or more computing devices including a processor and a memory, and the memory stores an application program including computer program instructions executable on the processor. The application program can be divided into a plurality of program modules for corresponding functions of each component of the system. The division of program modules is logical rather than physical. Each program module can run on one or more computing devices, and one computing device can also run one or more program modules. Hereinafter, the system of the present disclosure will be described in detail according to the functional logic division of the program module.

Referring to FIG. 5, FIG. 5 is a structural block diagram of a rail transit integrated network management system according to an embodiment of the present disclosure. Similar to the embodiment of FIG. 3, the integrated network management system 20 includes a plurality of subsystem network management 300, integrated network management device 200, data processing center 100, integrated network management center 400, and database 500. The various parts of the system are connected through wired or wireless communication. The integrated network management device 200 is in communication connection with the multiple subsystem network management and the data processing center, and is used for data transmission management between the subsystem network management and the data processing center in the rail transit system. The data generated by the multiple subsystem network management 300 is sent to The integrated network management device 200 is processed by the integrated network management device 200 and sent to a data processing center. The integrated network management device 200 further includes an interface adapter 210 and a message queue middleware server 220.

The interface adapter module 210 is configured to receive data uploaded by a subsystem network manager, convert the data into standardized message data with a common data mode, and transmit the standardized message data to a message queue middleware server.

The interface adapter module receives the data uploaded by the subsystem network manager, and converts the data into standardized message data with a common data mode, which may include: receiving data uploaded by the subsystem network manager according to the first protocol, and according to the first protocol. The protocol is parsed to obtain parsed data; the parsed data is converted into standardized message data with a common data pattern according to a second protocol; wherein the first protocol and the second protocol are different communication protocols.

The transmitting, by the interface adapter module, the normalized message data to a message queue middleware server includes: using the identification identifier of each subsystem network management as the key value, and sending the normalized message data to the middleware in the order of the key values. server.

The message queue middleware server 220 is configured to obtain the subject of the normalized message data, and publish the message data according to the subject, and according to the subscription topic of the data processing center, the message queue middleware server has the subscription topic. The message data is sent to the data processing center.

The message queue middleware server obtaining the subject of the normalized message data and publishing the message data according to the theme may include: establishing a corresponding message in the message queue middleware server for each of the subsystem network managers A queue to obtain the source subsystem network manager of the message data, and publish the message data to a message queue corresponding to the source subsystem network manager.

In addition, the message queue middleware server is further configured to: periodically check messages in the message queue middleware server, and clear messages from each message queue that meet preset discard conditions.

FIG. 6 is a structural block diagram of a message queue middleware server according to an embodiment of the present disclosure. The message queue middleware 220 may further include a message receiving unit 221, a message queue configuration unit 222, a message queue storage unit 223, and a message sending unit 224.

The message receiving unit 221 is configured to receive normalized message data.

The message queue configuration unit 222 is configured to publish message data to a corresponding message queue according to a subject of the message data.

The message queue storage unit 223 is configured to store each message queue.

The message sending unit 224 is configured to send message data in each message queue to a data processing center according to the subscription information.

The message queue may adopt the storage structure shown in FIG. 4. Establish different message queues according to the subsystem network management to store corresponding message data.

After the data processing center 100 obtains the subscribed messages, the data processing center 100 may process the data and store the message data in the database 500. The database 500 may include a local database and a cloud database. The data processing center 100 may classify and store message data, store temporary data in the message data in a local database, and store device monitoring data in the cloud database.

The integrated network management center 400 may obtain the device monitoring data from the cloud database, and perform device monitoring and fault statistical processing and big data analysis, and obtain temporary data from a local database for data processing.

Referring to FIG. 7, FIG. 7 is a schematic diagram of an integrated network management work process of a rail transit system according to an embodiment of the present disclosure.

S201. The network management of each subsystem generates corresponding subsystem data. For example, n subsystems including clock system network management, broadcast system network management, and so on.

S202. The interface adapter module performs matching communication with the network management of each subsystem, and receives subsystem data, for example, using a first protocol.

S203: The received subsystem data is converted, converted into standardized message data, and sent to the message queue middleware server.

S204. In the message queue middleware server, n queues are respectively established according to n different subsystems, and message data from different subsystems are placed in corresponding queues.

S205. The data processing center subscribes to the message from the message queue middleware server by subscribing to the topic, and obtains the message from the message queue middleware when the topic message with the corresponding subscription arrives.

S206. Analyze and process the message. For example, the message data can be classified, and temporary data and equipment monitoring data can be separated.

S207: Store the message data in a database. For example, according to the classification of the data, temporary data can be stored in a local database, and device monitoring data can be stored in a cloud database.

S208: The integrated network management center obtains data from the database, and implements various integrated network management functions according to the obtained data.

For specific implementation of each component or module of the integrated network management device of the rail transit system of the present disclosure, reference may be made to corresponding method embodiments, and details are not described herein again.

In order to implement the above embodiments, the present disclosure also proposes an electronic device including a processor and a memory; wherein the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory for use in Implement the integrated network management method for a rail transit system as described in any of the foregoing embodiments.

In order to implement the above embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium having stored thereon a computer program that, when executed by a processor, implements an integrated network management system for a rail transit system as described in any of the foregoing embodiments. method.

It should be noted that, in the description of this specification, any process or method description in the flowchart or otherwise described herein may be understood to mean that it includes one or more steps for implementing a specific logical function or process. Modules, fragments or portions of the code of an executable instruction, and the scope of preferred embodiments of the present disclosure includes additional implementations, which may not be in the order shown or discussed, including in a substantially simultaneous manner according to the functions involved Or the functions are performed in the reverse order, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

Those of ordinary skill in the art may understand that all or part of the steps carried by the method for implementing the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer-readable storage medium. The program When executed, one or a combination of the steps of the method embodiments is included.

It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods may be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it may be implemented using any one or a combination of the following techniques known in the art: Discrete logic circuits, application-specific integrated circuits with suitable combinational logic gate circuits, programmable gate arrays (PGA), field programmable gate arrays (FPGA), etc.

In the description of this specification, the description with reference to the terms “one embodiment”, “some embodiments”, “examples”, “specific examples”, or “some examples” and the like means specific features described in conjunction with the embodiments or examples , Structure, material, or characteristic is included in at least one embodiment or example of the present disclosure. In this specification, the schematic expressions of the above terms are not necessarily directed to the same embodiment or example. Moreover, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. In addition, without any contradiction, those skilled in the art may combine and combine different embodiments or examples and features of the different embodiments or examples described in this specification.

In addition, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, the meaning of “plurality” is two or more, such as two, three, etc., unless it is specifically and specifically defined otherwise.

Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limitations on the present disclosure. Those skilled in the art can understand the above within the scope of the present disclosure. Embodiments are subject to change, modification, substitution, and modification.

Claims

An integrated network management method for a rail transit system, which is used for data transmission management between a subsystem network manager and a data processing center in a rail transit system, is characterized by:

The interface adapter module receives data uploaded by the subsystem network manager, and converts the data into standardized message data with a common data mode;

The interface adapter module transmits the normalized message data to a message queue middleware server;

Obtaining, by the message queue middleware server, the subject of the normalized message data, and publishing the message data according to the subject;

The message queue middleware server sends the message data having the subscription topic in the message queue middleware server to the data processing center according to the subscription topic of the data processing center.
The integrated network management method for a rail transit system according to claim 1, wherein the receiving data uploaded by the network management of the subsystem and converting the data into normalized message data with a universal data mode comprises:

Receiving the data uploaded by the network manager of the subsystem according to the first protocol, and analyzing and obtaining the parsed data according to the first protocol;

Converting the parsed data into normalized message data with a universal data pattern according to a second protocol;

The first protocol and the second protocol are different communication protocols.
The integrated network management method for a rail transit system according to claim 1 or 2, wherein the transmitting the standardized message data to a message queue middleware server comprises:

And transmitting the normalized message data to the message queue middleware server according to the sequence of the key values by using the identification identifier of the network management of each subsystem as a key value.
The integrated network management method for a rail transit system according to any one of claims 1 to 3, wherein the message queue middleware server obtains the subject of the standardized message data, and publishes the message data according to the subject, include:

Establishing a corresponding message queue in the message queue middleware server for each of the subsystem network managers;

Obtain a source subsystem network manager of the message data, and publish the message data to a message queue corresponding to the source subsystem network manager.
The integrated network management method for a rail transit system according to claim 4, further comprising:

The message queue middleware server periodically checks the messages in the message queue middleware server, and clears messages that satisfy the preset discarding conditions from each message queue.
The integrated network management method for a rail transit system according to any one of claims 1 to 5, characterized in that, according to the subscription topic of the data processing center, the message data of the message queue middleware server with the subscription topic is sent to After the data processing center, the method further includes:

The data processing center classifies and stores message data, stores temporary data in the message data in a local database, and stores device monitoring data in a cloud database.
An integrated network management device for a rail transit system is used for data transmission management between a subsystem network manager and a data processing center in a rail transit system, and is characterized in that it includes:

An interface adapter module, configured to receive data uploaded by a network management system of a subsystem, convert the data into normalized message data with a common data mode, and transmit the normalized message data to a message queue middleware server;

The message queue middleware server is configured to obtain the subject of the normalized message data, and publish message data according to the theme, and according to the subscription theme of the data processing center, the message queue middleware server has the subscription theme. The message data is sent to the data processing center.
The integrated network management device for a rail transit system according to claim 7, wherein the interface adapter module receives data uploaded by the subsystem network management and converts the data into standardized message data with a universal data mode, comprising:

Receiving the data uploaded by the network manager of the subsystem according to the first protocol, and analyzing and obtaining the parsed data according to the first protocol;

Converting the parsed data into normalized message data with a universal data pattern according to a second protocol;

The first protocol and the second protocol are different communication protocols.
The integrated network management device for a rail transit system according to claim 7 or 8, wherein the interface adapter module transmits the standardized message data to a message queue middleware server comprises:

And transmitting the normalized message data to the message queue middleware server according to the sequence of the key values by using the identification identifier of the network management of each subsystem as a key value.
The integrated network management device for a rail transit system according to any one of claims 7 to 9, characterized in that the message queue middleware server obtains a subject of the normalized message data, and issues message data according to the subject, include:

Establishing a corresponding message queue on the message queue middleware server for each of the subsystem network managers,

Obtain a source subsystem network manager of the message data, and publish the message data to a message queue corresponding to the source subsystem network manager.
The integrated network management device for a rail transit system according to claim 10, wherein the message queue middleware server is further configured to:

Periodically check the messages in the message queue middleware server, and clear the messages that meet the preset discard conditions from each message queue.
An integrated network management system for a rail transit system, which includes a plurality of subsystem network management, data processing centers, databases, and integrated network management centers that are communicatively connected, further comprising: the rail transit according to any one of claims 7-12 A system integrated network management device, the rail transportation system integrated network management device is in communication connection with the multiple subsystem network management and the data processing center, and is used for data transmission management between the multiple subsystem network management and the data processing center.
The integrated network management system for a rail transit system according to claim 12, characterized in that:

The data processing center is further configured to classify and store message data, store temporary data in the message data in a local database, and store device monitoring data in a cloud database;

The integrated network management center is further configured to obtain the device monitoring data from the cloud database, and perform device monitoring and fault statistical processing and big data analysis.
An electronic device, comprising a processor and a memory;

Wherein, the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the track according to any one of claims 1-6. Comprehensive network management method of transportation system.
A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that when the program is executed by a processor, the integrated network management method for a rail transit system according to any one of claims 1-6 is implemented.