CN110708312A - Method and system for message transmission in ATS and ATS - Google Patents
Method and system for message transmission in ATS and ATS Download PDFInfo
- Publication number
- CN110708312A CN110708312A CN201910941847.2A CN201910941847A CN110708312A CN 110708312 A CN110708312 A CN 110708312A CN 201910941847 A CN201910941847 A CN 201910941847A CN 110708312 A CN110708312 A CN 110708312A
- Authority
- CN
- China
- Prior art keywords
- message
- middleware
- software
- center
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 23
- 238000000034 method Methods 0.000 title claims description 48
- 238000007726 management method Methods 0.000 claims description 30
- 238000012545 processing Methods 0.000 claims description 25
- 238000004891 communication Methods 0.000 claims description 21
- 230000006978 adaptation Effects 0.000 claims description 11
- 230000008878 coupling Effects 0.000 abstract description 15
- 238000010168 coupling process Methods 0.000 abstract description 15
- 238000005859 coupling reaction Methods 0.000 abstract description 15
- 230000004048 modification Effects 0.000 abstract description 7
- 238000012986 modification Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 10
- 230000003993 interaction Effects 0.000 description 9
- 230000001131 transforming effect Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
On one hand, in the software of the ATS, first messages generated by all functional modules are stored in a first message center through first message middleware. And each functional module acquires the required second message from the first message center. Information transmission is not carried out among the functional modules, and the coupling degree among the functional modules is reduced. On the other hand, the third message generated by each software is stored in the second message center through the second message middleware. Each software obtains the fourth message it needs from the second message center. Information transmission is not carried out among the software, and the coupling degree among the software is reduced. The damage or upgrading modification of a certain functional module cannot influence the normal operation of software, and the damage or upgrading modification of certain software cannot influence the normal operation of the ATS, so that the robustness of the ATS is enhanced, and the difficulty in modifying and upgrading is reduced.
Description
Technical Field
The invention relates to the technical field of rail transit, in particular to a method and a system for message transmission in an ATS (automatic train maintenance) and the ATS.
Background
The characteristics of high speed, density, diversification, networking and intellectualization of urban rail transit are increasingly shown. An ATS (Automatic Train monitoring System) subsystem provides a monitoring platform for all Train operations on a whole line as a part of a CBTC (communication based Train Control System) System. Through the automatic means, can alleviate operation personnel operation burden, improve subway operation's efficiency and service level. The ATS is a typical distributed system, and mainly consists of a central application server, station extensions, a gateway computer, a communication front-end processor, and numerous front-end software. Due to the difference of different subway lines in requirements, functions and display styles and the difference of operation modes, the ATS needs to be continuously researched and developed and continuously expanded, and meanwhile, the research and development of each software of the ATS are performed after the span of many years.
At present, the bottleneck which troubles the ATS development appears, and the main reasons are that the coupling degree between system software is too high, and the coupling degree between each module in the software is too high. This results in that, in the process of opening a new subway line, once a module is modified, the whole system software needs to be reissued, unpredictable problems frequently occur, and the difficulty of finding problems is increased in geometric level.
In the practical application process, the inventor finds that the existing ATS has higher coupling degree no matter each functional module in software or among software, the damage of any function may influence the normal operation of the system, and the difficulty of transforming and upgrading the ATS is increased.
Disclosure of Invention
The embodiment of the invention provides a method and a system for message transmission in an ATS (automatic transfer system) and the ATS, which are used for solving the problems that the normal operation of the system can be influenced by the damage of any function and the difficulty in the transformation and the upgrade of the ATS is increased no matter each function module in software or the software has higher coupling degree.
In view of the above technical problems, in a first aspect, an embodiment of the present invention provides a method for message delivery in an ATS, including:
for any software of the ATS, any functional module in the software sends the generated first message to the first message center by calling the first message middleware, and/or the functional module acquires a second message from the first message center by calling the first message middleware;
and/or the presence of a gas in the gas,
and the software calls the second message middleware to send the generated third message to the second message center, and/or the software calls the second message middleware to acquire a fourth message from the second message center.
Optionally, the acquiring, by the functional module, a second message from the first message center by invoking the first message middleware includes: the function module determines a message theme and a message structure body corresponding to the message to be acquired, and acquires the message conforming to the determined message theme and message structure body from the first message center by calling the first message middleware to serve as the second message;
the software acquires a fourth message from the second message center by calling the second message middleware, and the method comprises the following steps: the software determines a message theme and a message structure body corresponding to the message to be acquired, and acquires the message conforming to the determined message theme and message structure body from the second message center by calling the second message middleware to serve as the fourth message;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
Optionally, the acquiring, by the functional module, a second message from the first message center by invoking the first message middleware includes:
the function module determines a message theme and a message structure body corresponding to a message to be acquired, and registers first message consumption information in the first message center by calling the first message middleware; the first message consumption information comprises a determined message subject and a message structure, and the time when the first message center pushes a message to the function module;
the first message center pushes a second message which accords with the first message consumption information to the functional module according to the first message consumption information by calling the first message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
Optionally, the software acquires a fourth message from the second message center by invoking the second message middleware, including:
the software determines a message theme and a message structure body corresponding to the message to be acquired, and registers second message consumption information in the second message center by calling the second message middleware; the second message consumption information comprises a determined message subject and a message structure, and the time when the second message center pushes a message to the software;
the second message center pushes a fourth message which accords with the second message consumption information to the software according to the second message consumption information by calling the second message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
Optionally, before any functional module in the software sends the generated first message to the first message center by calling the first message middleware, the method further includes: the function module creates first registration information in the first message center by calling the first message middleware; the first registration information comprises a message theme and a message structure body corresponding to the first message generated by the functional module;
the software calls the second message middleware to send the generated third message to the second message center, and before the third message is sent to the second message center, the software further comprises: the software creates second registration information in the second message center by calling the second message middleware; the second registration information comprises a message subject and a message structure corresponding to the third message generated by the software.
Optionally, the first registration information further includes first identification information of the functional module as a message producer generating the first message and/or as a message consumer acquiring the second message;
the second registration information further includes second identification information of the software as a message producer for generating the third message and/or as a message consumer for obtaining the fourth message.
Optionally, before the function module obtains the second message from the first message center by invoking the first message middleware, the method further includes: the first message middleware encrypts the second message;
or,
before the software acquires a fourth message from the second message center by calling the second message middleware, the method further comprises the following steps: the second message middleware encrypts the fourth message.
In a second aspect, the present invention provides a system for message delivery in an ATS, comprising a first message middleware and a first message center for implementing intra-software message delivery of the ATS, and/or a second message middleware and a second message center for implementing inter-software message delivery of the ATS;
for any software of the ATS, any functional module in the software sends the generated first message to the first message center by calling the first message middleware, and/or the functional module acquires a second message from the first message center by calling the first message middleware;
and the software calls the second message middleware to send the generated third message to the second message center, and/or the software calls the second message middleware to acquire a fourth message from the second message center.
Optionally, the first message middleware and the second message middleware each include an application support module, a message management and task adaptation module, a configuration management module, a data processing module, and a communication support module;
in the first message middleware, an application support module is used for providing an interface for a function module to call the first message middleware; in the second message middleware, an application support module is used for providing an interface for software to call the second message middleware;
in the first message middleware, a message management and task adaptation module is used for processing a task of acquiring a second message from the first message center; in the second message middleware, a message management and task adaptation module is used for processing a task of acquiring a fourth message from the second message center;
in the first message middleware, a configuration management module is used for managing first registration information created in the first message center and a first message sent to the first message center by a functional module by calling the first message middleware; in the second message middleware, the configuration management module is used for managing second registration information created in a second message center and a third message sent to the second message center by software by calling the second message middleware;
in the first message middleware, the data processing module is used for encrypting a second message sent to the functional module; in the second message middleware, the data processing module is used for encrypting a fourth message sent to the software;
in the first message middleware, the communication support module is used for managing message passing between the first middleware and the first message center as well as between the first middleware and each functional module; in the second message middleware, the communication support module is used for managing the second middleware and the second message center, and message transmission between the second middleware and each piece of software.
In a third aspect, the present invention provides an ATS comprising a system for message delivery in the ATS of any one of claims 8-9.
On one hand, in the software of the ATS, first messages generated by all functional modules are stored in a first message center through first message middleware. And each functional module acquires the required second message from the first message center through the first message middleware. Information transmission is not carried out among the functional modules, and the coupling degree among the functional modules is reduced. On the other hand, the third message generated by each software is stored in the second message center through the second message middleware. And each software acquires the fourth message required by the software from the second message center through the second message middleware. Information transmission is not carried out among the software, and the coupling degree among the software is reduced. The damage or upgrading modification of a certain functional module cannot influence the normal operation of software, and the damage or upgrading modification of certain software cannot influence the normal operation of the ATS, so that the robustness of the ATS is enhanced, and the difficulty in modifying and upgrading is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description will be given below of the drawings required for the embodiments or the technical solutions in the prior art, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating the principle of inter-functional module messaging within software provided by one embodiment of the present invention;
fig. 2 is a schematic diagram illustrating a message passing principle between software of the ATS according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of a message transport mechanism provided by another embodiment of the present invention;
FIG. 4 is a diagram illustrating the existence of messages in a message center according to another embodiment of the present invention;
FIG. 5 is a schematic diagram of a functional module and a message broker provided in accordance with another embodiment of the present invention as a whole;
FIG. 6 is a timing diagram of the operation of message middleware provided by another embodiment of the present invention;
fig. 7 is a schematic diagram of a functional module and a message middleware according to another embodiment of the present invention;
fig. 8 is a schematic structural diagram of message middleware provided in another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the method for message passing in the ATS provided by this embodiment, on one hand, the message passing between different functional modules in each software of the ATS is improved, and the coupling degree between different functional modules in each software is reduced. On the other hand, the message transmission among all the software of the ATS is improved, and the coupling degree among all the software of the ATS is reduced, so that the robustness of the whole ATS is improved, the complexity of the ATS is reduced, the normal working state of the ATS can be maintained for a long time, and the difficulty of upgrading and transforming the ATS is reduced.
Fig. 1 is a schematic diagram of a message passing principle between functional modules in software according to this embodiment, referring to fig. 1, in the method for message passing in an ATS, for any software 101 of the ATS, any functional module 1011 in the software sends a generated first message to a first message center 1013 by calling a first message middleware 1012, and/or the functional module 1011 acquires a second message from the first message center 1013 by calling the first message middleware 1012;
or,
fig. 2 is a schematic diagram of a message passing principle between software of the ATS provided in this embodiment, referring to fig. 2, in an ATS100, the software 101 sends a generated third message to a second message center 103 by invoking a second message middleware 102, and/or the software 101 obtains a fourth message from the second message center 103 by invoking the second message middleware 102;
the first message middleware 1012 is a module in the software 101, so that each functional module 1011 and the first message center 1013 perform message interaction; the second message middleware 102 is a module for enabling each software 101 and the second message center 103 to perform message interaction.
It should be noted that, in this embodiment, the message interaction between the functional modules of the software in the ATS may be improved only according to the principle shown in fig. 1, the message interaction between the software in the ATS may be improved only according to the principle shown in fig. 2, and the message interaction between the functional modules of the software in the ATS may also be improved as well as the message interaction between the software in the ATS, which is not limited in this embodiment.
For the functional module in the software, if the functional module is used as a producer of the message, the first message generated is sent to the first message center by calling the first message middleware, and if the functional module is used as a consumer of the message, the second message is acquired from the first message by calling the first message middleware.
And for the software in the ATS, if the software is used as a producer of the message, the generated third message is sent to the second message center by calling the second message middleware, and if the software is used as a consumer of the message, the fourth message is acquired from the second message by calling the second message middleware.
On one hand, in the software of the ATS, first messages generated by each functional module are stored in a first message center through first message middleware. And each functional module acquires the required second message from the first message center through the first message middleware. Information transmission is not carried out among the functional modules, and the coupling degree among the functional modules is reduced. On the other hand, the third message generated by each software is stored in the second message center through the second message middleware. And each software acquires the fourth message required by the software from the second message center through the second message middleware. Information transmission is not carried out among the software, and the coupling degree among the software is reduced. The damage or upgrading modification of a certain functional module cannot influence the normal operation of software, and the damage or upgrading modification of certain software cannot influence the normal operation of the ATS, so that the robustness of the ATS is enhanced, and the difficulty in modifying and upgrading is reduced.
Fig. 3 is a schematic diagram of a message transmission mechanism provided in this embodiment, and referring to fig. 3, a functional module or software is used as a message producer to send a produced message to a message center, and the message center stores messages according to message topics. The functional module or software is used as a message consumer to obtain messages from the message center according to message subjects. The message subject can be a set of a type of message or a set of a type of associated message. Messages of a message topic are managed by the same queue. The message producer is responsible for creating the message, does not care who consumes the message, and obtains or subscribes the message of the relevant message topic by the message consumer according to the message topic. The producer and the consumer do not care how the two parties interact with each other.
After each functional module or software sends the produced message to the message center, the message center manages the message according to the message theme. Fig. 4 is a schematic diagram of a message existence form in a message center provided in this embodiment, as shown in fig. 4, the message center receives messages of various message topics (for example, messages of message topic 1, message topic 2, and message topic 3 in fig. 4), which are from different systems, and for example, the messages include a system command message, a customized command message, and a general message. The messages are managed through queues according to the topics in the message center (for example, a topic queue 1 corresponding to a message topic 1, a topic queue 2 corresponding to a message topic 2, and a topic queue 3 corresponding to a message topic 3).
There are two methods for a message consumer to obtain a message of a certain message subject from a message center, one is a pull mode method, and the other is a push mode method. The pull mode (periodic consumer to queue area for message getting a message of a specified topic) method is described as follows:
further, on the basis of the foregoing embodiment, the acquiring, by the functional module, a second message from the first message center by invoking the first message middleware includes: the function module determines a message theme and a message structure body corresponding to the message to be acquired, acquires the message conforming to the determined message theme and message structure body from the first message center by calling the first message middleware, and takes the message as the second message
The software acquires a fourth message from the second message center by calling the second message middleware, and the method comprises the following steps: the software determines a message theme and a message structure body corresponding to the message to be acquired, and acquires the message conforming to the determined message theme and message structure body from the second message center by calling the second message middleware to serve as the fourth message;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
In the pull mode, a functional module is used as a message consumer to determine a message theme and a message structure required by the message consumer, for example, a message theme required by a certain functional module is an alarm message theme, and a message structure capable of being analyzed is determined according to self configuration. And requesting the first message middleware for the required messages according to the information, and sending second messages which are in accordance with the message subject and the message structure in the first message center to the functional module through the first message middleware. The function module realizes the acquisition of the required information without interacting with other function modules. Wherein the message structure specifies the format in which each data in the message exists.
Similarly, in the pull mode, the software is used as a message subject and a message structure body required by the message consumer to be determined, for example, the message subject required by a certain software is a train running data subject, and the message structure body capable of being analyzed is determined according to the configuration of the software. And requesting the second message middleware for the required messages according to the information, and sending fourth messages which are in accordance with the message subject and the message structure in the second message center to the software through the second message middleware. The software realizes the acquisition of the required information without interaction with other software.
The following introduces the push model (the message service center is responsible for pushing messages to consumers bound with corresponding topics, the consumers register processing functions to the message service center, and the message service center calls the processing functions) method:
further, on the basis of the foregoing embodiments, the acquiring, by the functional module, a second message from the first message center by invoking the first message middleware includes:
the function module determines a message theme and a message structure body corresponding to a message to be acquired, and registers first message consumption information in the first message center by calling the first message middleware; the first message consumption information comprises a determined message subject and a message structure, and the time when the first message center pushes a message to the function module;
the first message center pushes a second message which accords with the first message consumption information to the functional module according to the first message consumption information by calling the first message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
In the push mode, the function module registers the first message consumption information through the first message middleware, and after the registration is successful, the first message middleware pushes the message which accords with the determined message theme and message structure to the function module according to the message pushing time specified in the first message consumption information.
Further, on the basis of the foregoing embodiments, the acquiring, by the software, a fourth message from the second message center by invoking the second message middleware includes:
the software determines a message theme and a message structure body corresponding to the message to be acquired, and registers second message consumption information in the second message center by calling the second message middleware; the second message consumption information comprises a determined message subject and a message structure, and the time when the second message center pushes a message to the software;
the second message center pushes a fourth message which accords with the second message consumption information to the software according to the second message consumption information by calling the second message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
In the push mode, the software registers second message consumption information through a second message middleware, and after the registration is successful, the second message middleware pushes the message which accords with the determined message theme and message structure to the software according to the message pushing time specified in the second message consumption information.
It is understood that, when the functional module and the software register the message consumption information as the message consumer, the message subject included in the message consumption information should be the message subject already existing in the message, that is, the message subject already registered by the message producer. When it is detected that the message center does not have a message topic in certain message consumption information, the message consumer needs to register the message consumption confidence again according to the message topic currently existing in the message center.
The following describes a case where there is no message topic in the message consumption information in the message center:
further, when the functional module registers first message consumption information in the first message center by calling the first message middleware, if the first message middleware judges that no message conforming to the first message consumption information exists in the first registration information registered in the first message center, a prompt that no message conforming to the first message consumption information exists is sent to the functional module;
the functional module acquires first registration information registered by each functional module in the first message center through the first message middleware, regenerates first message consumption information according to the first registration information registered by each functional module, and registers the regenerated first message consumption information in the first message center by calling the first message middleware.
Further, when the software registers second message consumption information in the second message center by calling the second message middleware, if the second message middleware judges that no message conforming to the second message consumption information exists in the second registration information registered in the second message center, sending a prompt that no message conforming to the second message consumption information exists to the software;
the software acquires second registration information registered by each software in the second message center through the second message middleware, regenerates second message consumption information according to the second registration information registered by each software, and registers the regenerated second message consumption information in the second message center by calling the second message middleware.
The following describes the process of registering functional modules and software as message producers in a message center:
further, on the basis of the foregoing embodiments, before any functional module in the software calls the first message middleware to send the generated first message to the first message center, the method further includes: the function module creates first registration information in the first message center by calling the first message middleware; the first registration information comprises a message theme and a message structure body corresponding to the first message generated by the functional module;
or,
the software calls the second message middleware to send the generated third message to the second message center, and before the third message is sent to the second message center, the software further comprises: the software creates second registration information in the second message center by calling the second message middleware; the second registration information comprises a message subject and a message structure corresponding to the third message generated by the software.
Before sending a produced message to a message center, a message producer needs to register in the message center, and registers information such as a message theme and a message structure body to which the produced message belongs in the message center, so that the message is managed according to the message theme.
Further, on the basis of the foregoing embodiments, the first registration information further includes first identification information of the functional module as a message producer for generating the first message, and/or as a message consumer for acquiring the second message;
the second registration information further includes second identification information of the software as a message producer for generating the third message and/or as a message consumer for obtaining the fourth message.
According to the first registration information of the functional module in the first message center and the first message consumption information of the functional module registered in the first message center, a virtual corresponding relation of message transmission among the modules is actually established, and message forwarding is realized through the virtual corresponding relation.
The first registration information of the function module may be used as external description information of the function module, fig. 5 is an external schematic diagram of the function module and the message intermediate provided in this embodiment as a whole, as shown in fig. 5, the function module and the first message intermediate may be regarded as a unit, and a message is acquired from the unit through the external description information. Specifically, the unit body is composed of independent functional modules and message middleware. The functional module is responsible for processing the service. The message middleware is responsible for putting the generated external messages into a resource network formed by the large middleware and receiving the information needing to be processed. The external message description comprises a subject list of the message of the current function module, identifications of the consumer and the producer, a message structure body and the like.
Further, on the basis of the foregoing embodiments, before the function module acquires the second message from the first message center by invoking the first message middleware, the method further includes: the first message middleware encrypts the second message;
or,
before the software acquires a fourth message from the second message center by calling the second message middleware, the method further comprises the following steps: the second message middleware encrypts the fourth message.
The message middleware can also encrypt the message to ensure the security of data transmission.
Fig. 6 is a timing diagram of the operation of the message middleware provided in this embodiment, and the following description is made in conjunction with fig. 6 for a process in which a message producer and a message consumer register in a message center through the message middleware and implement information delivery:
the registration process comprises the following steps:
(1) when the message producer and the message consumer create the message, the IP address of the message center needs to be specified, and the key words of the message center need to be specified in the program, so that the registration in the message center is completed.
(2) The message center establishes a virtual corresponding relation in the message center according to the registration of the message producer and the message consumer, and the message center is responsible for forwarding the message.
(3) The message consumer specifies the manner in which the message is to be obtained, i.e., pull mode or push mode.
The process of modifying the software by the method comprises the following steps:
modifying each module, removing the coupling relation among the modules, sending messages by using a message middleware, establishing a virtual link relation among the modules, and carrying out information interaction through the message middleware, wherein the method comprises the following steps:
(1) removing the dynamic library reference relation among the functional modules;
(2) summarizing the message types externally provided by the current functional module, and creating a message description file;
(3) and integrating message middleware, creating a message consumer object and a message producer object, wherein the message consumer object is responsible for receiving messages from the outside, and the message producer is responsible for generating message types provided by the function module to the outside. Binding message subjects, setting an acquisition mode (pull mode or push mode) of the messages, realizing a message processing function, and binding a message processing function of a user command.
(4) And an IPlug plug-in interface is realized, and a uniform initialization interface function of the plug-in is provided for the outside.
Currently, each software in the ATS is divided into a plurality of function modules, such as an alarm module unit, an operation module unit, an equipment module unit, a group analysis module unit, a logic layer module unit, a yard graph module unit, a running graph module unit, a shift dispatching module unit, a train tracking module unit, a log module unit, a communication module unit, a database module unit, and the like, and a functional corresponding relationship diagram of these function modules and a message middleware is shown in fig. 7.
On the other hand, since the ATS is a typical distributed system, it is composed of a plurality of software, and is divided into central software and station software. The central software comprises: application center server software, gateway computer software and scheduling foreground software; the station software comprises: station extension, local workstation, TDT interface machine, etc. The software component message interaction usually adopts a UDP or TCP mode, and simultaneously utilizes a security protocol to carry out encryption transmission, wherein the security protocol comprises an RSSP-1 protocol, an RSSR-2 protocol, an SFP protocol and an RP protocol. Generally, each software integration package analysis module and a communication module, to package the content to be sent into bit stream data, and the upper application module interacts with the communication module and the package analysis module to obtain the corresponding data content. The software and the software are directly connected, a large number of communication lists need to be configured, a huge data interface file needs to be maintained, once a small point is changed, package analysis and an equipment communication list need to be modified, and meanwhile, the problem that the communication layer, the safety protocol layer or the package analysis is difficult to judge is encountered.
In order to solve the above problems, the following describes a process of modifying software by the above method:
the link layer of the message middleware realizes communication adaptation of message forwarding based on the inside of the RP protocol and the UDP protocol, and the message application layer does not need to care about the communication realization of the lower layer.
And establishing a plurality of message centers by using the message middleware, taking charge of unified management of messages, and simultaneously performing redundant hot standby and resource load on the plurality of message centers.
By utilizing the convention that the message description file carries out information transmission on a plurality of software components, at the beginning of establishing connection with the message center, the software serving as a message producer transmits the version of the message description file to the message center, meanwhile, when the consumer software establishes connection with the message center, whether the version of the message description file of a subscribed producer is consistent with the version of the message description file of the consumer software needs to be compared, and if the version of the message description file is not consistent with the version of the message description file of the subscribed producer, the latest message description file needs to be downloaded from the message center.
The producer software is responsible for generating messages and transmitting the messages to the message center; the consumer software is responsible for subscribing to messages from a producer and to topics that it needs.
In this way, the device list information still needs to be maintained between the software, but the lack of the single device information does not affect the operation of the whole system, and meanwhile, new software devices can be dynamically added without affecting the operation of the system.
Therefore, the message middleware provided by the embodiment is a part of the program, and has the following characteristics: the method only exchanges messages, is not responsible for storing the messages and detecting whether the messages are transmitted to a destination or not, has a self-detection function and self-recovery capability, limits the maximum byte number by caching, performs a broadcast detection and handshake mechanism, and can be responsible for encrypting the messages.
The embodiment provides a system for message delivery in an ATS, which includes a first message middleware and a first message center for implementing intra-software message delivery of the ATS, and/or a second message middleware and a second message center for implementing inter-software message delivery of the ATS;
for any software of the ATS, any functional module in the software sends the generated first message to the first message center by calling the first message middleware, and/or the functional module acquires a second message from the first message center by calling the first message middleware;
and the software calls the second message middleware to send the generated third message to the second message center, and/or the software calls the second message middleware to acquire a fourth message from the second message center.
Further, on the basis of the above embodiment, the first message middleware and the second message middleware each include an application support module, a message management and task adaptation module, a configuration management module, a data processing module, and a communication support module;
in the first message middleware, an application support module is used for providing an interface for a function module to call the first message middleware; in the second message middleware, an application support module is used for providing an interface for software to call the second message middleware;
in the first message middleware, a message management and task adaptation module is used for processing a task of acquiring a second message from the first message center; in the second message middleware, a message management and task adaptation module is used for processing a task of acquiring a fourth message from the second message center;
in the first message middleware, a configuration management module is used for managing first registration information created in the first message center and a first message sent to the first message center by a functional module by calling the first message middleware; in the second message middleware, the configuration management module is used for managing second registration information created in a second message center and a third message sent to the second message center by software by calling the second message middleware;
in the first message middleware, the data processing module is used for encrypting a second message sent to the functional module; in the second message middleware, the data processing module is used for encrypting a fourth message sent to the software;
in the first message middleware, the communication support module is used for managing message passing between the first middleware and the first message center as well as between the first middleware and each functional module; in the second message middleware, the communication support module is used for managing the second middleware and the second message center, and message transmission between the second middleware and each piece of software.
Fig. 8 is a schematic structural diagram of a message middleware provided in this embodiment, and specifically, as shown in fig. 8, functions of each module are as follows:
a communication support module: detecting the similar message middleware and the handshake function of the message middleware; the functions of establishing communication channels in the process, between the processes and between the systems and message transmission management are provided.
A configuration management module: the message middleware self-describes the configuration management and allows the access to the message middleware type configuration.
The data processing module comprises: data encryption/decryption management, message passing frame header packaging/unpacking management and task data domain management.
The message management and task adaptation module: message format definition, message management, task driven engine setup/management functions.
An application support module: and an external interface providing module.
If the message middleware is divided into a consumer role, a message service center role, a message producer role, a linker role and a configuration management role according to the roles. The role of the message middleware of each role in message delivery is described as follows:
the role of the linker is to establish link connection between the service center and the consumer and the producer.
The configuration management role is to load the basic configuration of the server center, the consumer and the producer in the initialization process of the middleware, describe the basic configuration with the xml file format and also specify the basic configuration by codes.
The service center exists as a routing node of the message and is responsible for the persistence work of the message.
The producer is the generation unit of the message, and the upper application creates various messages by calling the producer object and transmits the messages to the service center.
The consumer is a processing unit of the message, the upper layer application subscribes a related subject according to the self requirement, and specifies a routing mode, which can be a push mode or a pull mode, but the consumer in the message middleware is not responsible for message processing and only takes the role of obtaining the message, and the specific processing is provided with a processing function by the upper layer application.
Finally, the present implementation provides a system for an ATS including messaging in any one of the above ATS. Specifically, the message transmission is carried out in each software and among the software of the ATS by the message transmission method in the ATS, and the message transmission method greatly reduces the coupling degree among the functional modules in the software and the coupling degree among the software, enhances the system stability and robustness of the ATS and reduces the difficulty in upgrading and transforming the ATS.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present invention, and are not limited thereto; although embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method of messaging in an ATS, comprising:
for any software of the ATS, any functional module in the software sends the generated first message to the first message center by calling the first message middleware, and/or the functional module acquires a second message from the first message center by calling the first message middleware;
and/or the presence of a gas in the gas,
and the software calls the second message middleware to send the generated third message to the second message center, and/or the software calls the second message middleware to acquire a fourth message from the second message center.
2. The method of messaging in an ATS according to claim 1,
the function module acquires a second message from the first message center by calling the first message middleware, and the method comprises the following steps: the function module determines a message theme and a message structure body corresponding to the message to be acquired, and acquires the message conforming to the determined message theme and message structure body from the first message center by calling the first message middleware to serve as the second message;
the software acquires a fourth message from the second message center by calling the second message middleware, and the method comprises the following steps: the software determines a message theme and a message structure body corresponding to the message to be acquired, and acquires the message conforming to the determined message theme and message structure body from the second message center by calling the second message middleware to serve as the fourth message;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
3. The method of message delivery in an ATS of claim 1, wherein the function module obtains a second message from the first message center by invoking the first message middleware, comprising:
the function module determines a message theme and a message structure body corresponding to a message to be acquired, and registers first message consumption information in the first message center by calling the first message middleware; the first message consumption information comprises a determined message subject and a message structure, and the time when the first message center pushes a message to the function module;
the first message center pushes a second message which accords with the first message consumption information to the functional module according to the first message consumption information by calling the first message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
4. The method of message delivery in an ATS of claim 1, wherein the software obtains a fourth message from the second message center by invoking the second message middleware, comprising:
the software determines a message theme and a message structure body corresponding to the message to be acquired, and registers second message consumption information in the second message center by calling the second message middleware; the second message consumption information comprises a determined message subject and a message structure, and the time when the second message center pushes a message to the software;
the second message center pushes a fourth message which accords with the second message consumption information to the software according to the second message consumption information by calling the second message middleware;
the message theme is an alarm message theme, a train running data theme, a trackside data theme or a vehicle data theme.
5. The method of messaging in an ATS according to claim 1,
before any functional module in the software calls the first message middleware to send the generated first message to the first message center, the method further comprises the following steps: the function module creates first registration information in the first message center by calling the first message middleware; the first registration information comprises a message theme and a message structure body corresponding to the first message generated by the functional module;
the software calls the second message middleware to send the generated third message to the second message center, and before the third message is sent to the second message center, the software further comprises: the software creates second registration information in the second message center by calling the second message middleware; the second registration information comprises a message subject and a message structure corresponding to the third message generated by the software.
6. The method of messaging in an ATS according to claim 5,
the first registration information further comprises first identification information of the functional module, wherein the functional module is used as a message producer for generating the first message and/or is used as a message consumer for acquiring the second message;
the second registration information further includes second identification information of the software as a message producer for generating the third message and/or as a message consumer for obtaining the fourth message.
7. The method of messaging in an ATS according to claim 1,
before the function module obtains the second message from the first message center by calling the first message middleware, the method further includes: the first message middleware encrypts the second message;
or,
before the software acquires a fourth message from the second message center by calling the second message middleware, the method further comprises the following steps: the second message middleware encrypts the fourth message.
8. A system for messaging in an ATS, comprising first message middleware and a first message center for implementing intra-software messaging for the ATS, and/or second message middleware and a second message center for implementing inter-software messaging for the ATS;
for any software of the ATS, any functional module in the software sends the generated first message to the first message center by calling the first message middleware, and/or the functional module acquires a second message from the first message center by calling the first message middleware;
and the software calls the second message middleware to send the generated third message to the second message center, and/or the software calls the second message middleware to acquire a fourth message from the second message center.
9. The system for message delivery in an ATS of claim 8 wherein the first message middleware and the second message middleware each include an application support module, a message management and task adaptation module, a configuration management module, a data processing module, and a communication support module;
in the first message middleware, an application support module is used for providing an interface for a function module to call the first message middleware; in the second message middleware, an application support module is used for providing an interface for software to call the second message middleware;
in the first message middleware, a message management and task adaptation module is used for processing a task of acquiring a second message from the first message center; in the second message middleware, a message management and task adaptation module is used for processing a task of acquiring a fourth message from the second message center;
in the first message middleware, a configuration management module is used for managing first registration information created in the first message center and a first message sent to the first message center by a functional module by calling the first message middleware; in the second message middleware, the configuration management module is used for managing second registration information created in a second message center and a third message sent to the second message center by software by calling the second message middleware;
in the first message middleware, the data processing module is used for encrypting a second message sent to the functional module; in the second message middleware, the data processing module is used for encrypting a fourth message sent to the software;
in the first message middleware, the communication support module is used for managing message passing between the first middleware and the first message center as well as between the first middleware and each functional module; in the second message middleware, the communication support module is used for managing the second middleware and the second message center, and message transmission between the second middleware and each piece of software.
10. An ATS comprising a system for message delivery in the ATS of claim 8 or 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910941847.2A CN110708312A (en) | 2019-09-30 | 2019-09-30 | Method and system for message transmission in ATS and ATS |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910941847.2A CN110708312A (en) | 2019-09-30 | 2019-09-30 | Method and system for message transmission in ATS and ATS |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110708312A true CN110708312A (en) | 2020-01-17 |
Family
ID=69198164
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910941847.2A Pending CN110708312A (en) | 2019-09-30 | 2019-09-30 | Method and system for message transmission in ATS and ATS |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110708312A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115082216A (en) * | 2022-06-27 | 2022-09-20 | 中国工商银行股份有限公司 | Interactive method, device, electronic equipment and medium between systems |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101668031A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Message processing method and message processing system |
| CN101674257A (en) * | 2008-09-10 | 2010-03-17 | 阿里巴巴集团控股有限公司 | A method and device for storing message and a message processing system |
| CN105338061A (en) * | 2015-09-29 | 2016-02-17 | 华中科技大学 | Lightweight message oriented middleware realization method and system |
| CN105871959A (en) * | 2015-01-22 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Message delivery method, system and device |
| CN106878415A (en) * | 2017-02-15 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The load-balancing method and device of data consumption |
| CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| US20180067846A1 (en) * | 2015-09-29 | 2018-03-08 | International Business Machines Corporation | Apparatus and method for expanding the scope of systems management applications by runtime independence |
| CN108134746A (en) * | 2017-12-19 | 2018-06-08 | 深圳交控科技有限公司 | The processing method and processing device of rail traffic data |
| CN108134745A (en) * | 2017-12-19 | 2018-06-08 | 深圳交控科技有限公司 | Distribution type data collection method and device |
| CN109412821A (en) * | 2017-08-16 | 2019-03-01 | 阿里巴巴集团控股有限公司 | Message treatment method and device and electronic equipment |
| CN109677465A (en) * | 2018-12-29 | 2019-04-26 | 卡斯柯信号有限公司 | Distributed real-time systems framework for track traffic synthetic monitoring system |
-
2019
- 2019-09-30 CN CN201910941847.2A patent/CN110708312A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101668031A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Message processing method and message processing system |
| CN101674257A (en) * | 2008-09-10 | 2010-03-17 | 阿里巴巴集团控股有限公司 | A method and device for storing message and a message processing system |
| CN105871959A (en) * | 2015-01-22 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Message delivery method, system and device |
| CN105338061A (en) * | 2015-09-29 | 2016-02-17 | 华中科技大学 | Lightweight message oriented middleware realization method and system |
| US20180067846A1 (en) * | 2015-09-29 | 2018-03-08 | International Business Machines Corporation | Apparatus and method for expanding the scope of systems management applications by runtime independence |
| CN106878415A (en) * | 2017-02-15 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The load-balancing method and device of data consumption |
| CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| CN109412821A (en) * | 2017-08-16 | 2019-03-01 | 阿里巴巴集团控股有限公司 | Message treatment method and device and electronic equipment |
| CN108134746A (en) * | 2017-12-19 | 2018-06-08 | 深圳交控科技有限公司 | The processing method and processing device of rail traffic data |
| CN108134745A (en) * | 2017-12-19 | 2018-06-08 | 深圳交控科技有限公司 | Distribution type data collection method and device |
| CN109677465A (en) * | 2018-12-29 | 2019-04-26 | 卡斯柯信号有限公司 | Distributed real-time systems framework for track traffic synthetic monitoring system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115082216A (en) * | 2022-06-27 | 2022-09-20 | 中国工商银行股份有限公司 | Interactive method, device, electronic equipment and medium between systems |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111787066B (en) | Internet of things data platform based on big data and AI | |
| CN107645562B (en) | Data transmission processing method, device, equipment and system | |
| CN112488679B (en) | Cross-link contract analysis method of blockchain, relay chain and cross-link system | |
| CN103562882B (en) | For providing the system and method for messaging application interface | |
| CN112511218B (en) | Satellite ground station monitoring system based on microservice | |
| CN112511586B (en) | Cloud edge cooperation-based intelligent driving scheduling safety card control system for high-speed railway | |
| CN102761864A (en) | Data transmission method, system and device | |
| CN103684963A (en) | Framework system and implementation method of middleware applied to car networking | |
| CN106230806A (en) | Blended data custom protocol communication system under tertiary-structure network environment and method | |
| CN104753817A (en) | Local analogy method and local analogy system for cloud computing message queue service | |
| CN103220292A (en) | Cross-safe-area data transmission method and system | |
| US8478714B2 (en) | Integrated distribution management system channel adapter | |
| CN101466109B (en) | Communication system and method for WiMAX network management | |
| CN107222530A (en) | Service asynchronous exchange method, equipment, system and computer-readable recording medium | |
| CN111294235B (en) | Data processing method, device, gateway and readable storage medium | |
| EP2429150A1 (en) | Apparatus, web service component and method based on web service | |
| CN101567861B (en) | Data synchronization method and application system between heterogeneous application systems | |
| CN104317661A (en) | Intersystem communication method and device of dual embedded systems | |
| CN106027534A (en) | System for implementing financial message processing based on Netty | |
| CN114189274A (en) | Satellite ground station monitoring system based on microservice | |
| CN111901308B (en) | Information interaction method | |
| US20040037315A1 (en) | Method for transmitting a mobile agent in a network, associated transmitter, receiver and mobile agent | |
| CN101227470A (en) | System and method of business management | |
| CN110708312A (en) | Method and system for message transmission in ATS and ATS | |
| CN103595695A (en) | Method and system for providing services by service bus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200117 |
|
| RJ01 | Rejection of invention patent application after publication |