Cloud native train control system based on domain-driven design and implementation method thereof

Abstract

The invention discloses a cloud native train control system based on domain-driven design and an implementation method thereof. The train control system comprises a communication interface service layer; the application domain is connected with the communication interface service layer, the application domain comprises a plurality of function modules corresponding to specific entities in the train control system, and the application domain is used for preliminary logic processing in the train control system and information interaction with the communication interface service layer; the domain domain is connected with the application domain, the domain domain receives the information of the application domain, and the domain domain calculates and / or verifies the state information of the corresponding train according to different requests in the information of the application domain; and an infrastructure layer. According to the method, a traditional single train control system is decoupled and split into a multi-module train control system, so that the coupling degree between modules is reduced, upgrading iteration is facilitated, the fault range is controlled, and technical reference is provided for design of a cloud native train control system.

Description

Technical Field

[0001] The present invention relates to the field of rail transit technology, and in particular to a cloud-native train control system based on domain-driven design and an implementation method thereof. Background Art

[0002] With the rapid development of rail transit, the train operation control system, as its core system, plays the role of the train command brain. At present, the train control system is an embedded system architecture, and the application logic is tightly coupled with the underlying hardware, making it difficult to migrate between different underlying hardware platforms; different functions are tightly coupled, and system expansion is difficult. Every time a new line or station is built, new physical hardware equipment needs to be added, resulting in duplicate construction of computing resources and difficulty in expansion. The same train control equipment is severely coupled in different jurisdictions, and construction in a certain area will lead to the update and upgrade of the entire equipment.

[0003] The rapid development of cloud computing and virtualization technology can realize the decoupling of application logic and underlying hardware, facilitate the deployment and upgrade of train control systems, realize the effective reuse of computing resources, and reduce equipment investment costs. There have been many studies on train control virtualization and cloud train control. However, the current research on train control systems focuses on upgrading the existing train control hardware to the cloud, without changing the upper-layer application logic, lacking a cloud-native train control system design solution, and not combining domain-driven design technology. It has not played the real role of cloud computing. Its application model is still a simple upgrade of the current stand-alone train control system, computing resources cannot be fully reused, and the coupling between modules is tight, and there is no deeper integration with the latest virtualization technology and cloud technology. Summary of the invention

[0004] The purpose of the present invention is to provide a cloud-native train control system based on domain-driven design and its implementation method, aiming to solve the problems in the prior art that different jurisdictions of the same train control device in the train control system are severely coupled, the system is not convenient for iterative upgrades, and the existing train control system does not support virtualization solutions.

[0005] To achieve the above object, the present invention is implemented through the following technical solutions:

[0006] On the one hand, the present invention provides a cloud-native train control system based on domain-driven design, including:

[0007] Communication interface service layer;

[0008] An application domain, which is connected to the communication interface service layer, the application domain comprising: a plurality of functional modules corresponding to specific entities in the train control system, the application domain being used for preliminary logic processing in the train control system and information interaction with the communication interface service layer;

[0009] A domain domain, which is connected to the application domain, receives information from the application domain, calculates and / or verifies status information of the corresponding train according to different requests in the information of the application domain, and sends the calculated and / or verified train status information to the application domain;

[0010] The infrastructure layer is used for intra-domain communication in the train control system and for providing a virtualized container, wherein the application domain, the domain domain and the communication interface service layer are all arranged in a virtualized container.

[0011] Preferably, the application domain includes:

[0012] A train application domain, which includes a plurality of application entities. Each train corresponds to one application entity in the application domain. The train application domain is used to record specific entity data of a particular train.

[0013] The trackside signal application domain is used to send the current line switch, section, and signal machine status to the domain domain, and the domain domain calculates the locking status of the section and switch, and updates the line switch, section, and signal machine status according to the results returned by the domain domain.

[0014] The temporary speed limit command entity application service module uses the speed limit command as an entity and is responsible for the interface function of the speed limit command;

[0015] The external communication interface service module is connected to the communication interface service layer and sends the data information of the application domain to the communication interface service layer.

[0016] Preferably, the train application domain includes:

[0017] The train registration status application service module is responsible for the current train registration progress status of a specific train;

[0018] The train driving permission status entity service module is used to record the authorization status of the train and is used for preliminary driving permission services, as well as the unpacking and packaging of train-ground wireless message packets;

[0019] The train position report entity application service module is connected to the train registration status application service module and the train driving permit status entity service module respectively, and is used to receive train position report information, receive track circuit collection information, and exchange information with the train registration status application service module and the train driving permit status entity service module respectively. It is also used to make a preliminary legality judgment on the on-board position report and unpack and assemble the train-ground wireless message packets.

[0020] Preferably, the train registration progress status includes: determining whether the train has completed registration and the data interaction status of the intermediate steps in the train registration process.

[0021] Preferably, the preliminary legitimacy judgment of the vehicle-mounted location report includes: the relationship between the location report and the registration status, and the basic legitimacy check of the fields in the location report.

[0022] Preferably, the trackside signal application domain includes:

[0023] A turnout entity service module, used for receiving a turnout operation command and sending the turnout operation command to the communication interface service layer;

[0024] Track section entity service module, used to collect the status of trackside secondary detection equipment and receive commands related to the status of trackside secondary detection equipment in the section;

[0025] The signal machine entity service module is used to record the location and topological connection relationship of the signal machine;

[0026] The route entity service module is used to receive route commands and route status information transmitted externally, and send the route commands and route status information to the domain, and update the route command status according to the result returned by the domain.

[0027] Preferably, the domain includes:

[0028] The train driving permission calculation domain service module calculates the train authorization status according to the train position and trackside line status information obtained from the entity of the application domain, obtains the authorization information of each train, and sends the authorization information of each train to the application domain;

[0029] Line resource range calculation domain service module, which is used to calculate the range of line resources required by a certain train;

[0030] The train registration domain service module is used to receive the train registration and deregistration message packets, verify the legitimacy of the train registration and deregistration message packets, and update the train registration and deregistration message packets;

[0031] A train position calculation domain service module, which is used to receive the information of the application domain and determine the train position according to the train autonomous positioning and the status of the trackside secondary detection equipment in the information of the application domain;

[0032] A line resource management domain service module, which is used to judge the current station status data transmitted by the application domain, obtain updated station status data, and send the updated station status data to the application domain;

[0033] A temporary speed limit management domain service, which transfers the speed limit command status according to the speed limit command information transmitted by the application domain, and sends the updated speed limit information to the application domain;

[0034] The maintenance diagnosis service module is used to receive maintenance log data sent by other modules in the domain, and the maintenance diagnosis service module is used to provide general message parsing, human-machine display and log storage.

[0035] Preferably, the domain also includes:

[0036] The kilometer mark calculation service module is used to calculate the distance from a kilometer mark to a relative point on the route;

[0037] The electronic map domain service module is used to provide electronic map data in the current area.

[0038] Preferably, any module or a combination of several modules in the application domain, the domain domain and the communication interface service layer corresponds to a virtualized container, and the virtualized container is set in a cloud or a local server.

[0039] Preferably, each of the virtualized containers is implemented by two sub-containers with different architectures. The two sub-containers simultaneously run the requirements of the same domain. The domain codes in the two sub-containers are designed differently. When the results of domain calculations for the same purpose in the two sub-containers are inconsistent, they are directed to the security side for processing.

[0040] Preferably, the intra-domain communication of the train control system includes: communication with external Ethernet, communication with CAN, and communication with a serial bus.

[0041] On the other hand, the present invention also provides an implementation method of a cloud-native train control system based on domain-driven design, which is implemented using the above-mentioned cloud-native train control system based on domain-driven design. The method includes: according to traditional train control functions, dividing and sorting out the modules in the application domain and the domain domain to decouple the train control system.

[0042] Preferably, it also includes: aggregating and organizing each module in the application domain and each module in the domain domain according to the business field and / or data scope, and the aggregate organization includes: dividing each module in the application domain and each module in the domain domain according to function, so as to realize the aggregation of the temporary speed limit server of the train control system, the wireless block center, and the interlocking train control integrated equipment.

[0043] Compared with the prior art, the present invention has the following beneficial effects:

[0044] 1. The cloud-native train control system based on domain-driven design proposed in the present invention decouples the traditional single-body train control system and splits it into a multi-module train control system, which reduces the coupling between modules and facilitates upgrades and iterations;

[0045] 2. The cloud-native train control system based on domain-driven design proposed in the present invention supports the design of subsequent cloud train control systems, decouples the processing of persistent state preservation from state-independent logic processing, and can deploy different modules in different parts according to different characteristics. The boundary between cloud, edge and terminal is clearer, laying a foundation for further virtualization of the train control system and cloud migration;

[0046] 3. The cloud-native train control system based on domain-driven design proposed in the present invention is convenient for on-site deployment, can realize the replacement deployment of each subdomain, can realize the replacement of a certain application function without affecting the implementation of other functions, can realize the replacement of the entity of a certain area without affecting the operation of other areas, and after a fault occurs, the fault impact range is more controllable;

[0047] 4. The cloud-native train control system based on domain-driven design proposed in the present invention improves the overall availability and reliability of the train control system. A single entity failure or a single service failure in the train control system will not cause the overall failure of the train control system. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for the description. Obviously, the drawings described below are an embodiment of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work:

[0049] Figure 1 A system architecture diagram of a cloud-native train control system based on domain-driven design provided in one embodiment of the present invention;

[0050] Figure 2 A train registration flow chart of a cloud-native train control system based on domain-driven design provided by an embodiment of the present invention;

[0051] Figure 3 A schematic diagram of driving permission processing for a cloud-native train control system based on domain-driven design provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following is combined with Figure 1-3The cloud-native train control system based on domain-driven design and its implementation method proposed in the present invention are further described in detail with specific implementation methods. According to the following description, the advantages and features of the present invention will be clearer. It should be noted that the drawings are in a very simplified form and use non-precise proportions, which are only used to conveniently and clearly assist in explaining the purpose of the implementation methods of the present invention. In order to make the purposes, features and advantages of the present invention more obvious and easy to understand, please refer to the drawings. It should be noted that the structures, proportions, sizes, etc. illustrated in the drawings of this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the limiting conditions for the implementation of the present invention, so they have no technical substantive significance. Any structural modification, change in proportional relationship or adjustment of size, without affecting the effects that can be produced by the present invention and the purposes that can be achieved, should still fall within the scope of the technical content disclosed in the present invention.

[0053] In view of the problems in the prior art that different jurisdictions of the same train control device in the train control system are severely coupled internally, it is inconvenient for the iteration and upgrade of the system, and the existing train control system does not support virtualization solutions.

[0054] On the one hand, reference Figure 1 As shown, this embodiment provides a cloud-native train control system based on domain-driven design, including: a communication interface service layer; an application domain, which is connected to the communication interface service layer, and the application domain includes: a number of functional modules corresponding to specific entities in the train control system, and the application domain is used for preliminary logical processing in the train control system, and information interaction with the communication interface service layer; a domain domain, which is connected to the application domain, and the domain domain receives the information of the application domain. According to different requests in the information of the application domain, the domain domain calculates and / or verifies the status information of the corresponding train, and sends the calculated and / or verified train status information to the application domain; an infrastructure layer, which is used for intra-domain communication in the train control system and provides a virtualized container, and the application domain, the domain domain and the communication interface service layer are all set in a virtualized container. The intra-domain communication of the train control system includes: communication with an external Ethernet, communication with CAN (Controller Area Network, controller local area network), and communication with a serial bus.

[0055] The application domains include:

[0056] 1. Train application domain, which includes several application entities. Each train corresponds to an application entity in the application domain. The train application domain is used to record the specific entity data of a specific train. The specific entity data of a specific train includes: the train registration status, train position status (including on-board position report occupancy and section occupancy status) and train authorization status corresponding to a specific train. The only mark of the specific entity data of a specific train is the unique ID number of the train.

[0057] The train application domain includes: a train registration status application service module, a train position report entity application service module and a train MA (Movement Authority) status entity service module.

[0058] The train registration status application service module is responsible for the current train registration progress status of a specific train, which includes: judging whether the train has completed registration and the data interaction status of the intermediate steps in the train registration process. In order to prevent the anemia problem in DDD (Domain-Driven Design), the train registration status application service module has a simple registration message package check and reply function.

[0059] The train MA status entity service module is used to record the authorization status of the train and is used for preliminary driving permission services, as well as the unpacking and assembly of train-ground wireless message packets.

[0060] The train position report entity application service module is connected to the train registration status application service module and the train driving permit status entity service module respectively, and is used to receive train position report information, receive track circuit acquisition information, and exchange information with the train registration status application service module and the train driving permit status entity service module respectively. It is also used to perform preliminary legitimacy judgment on the on-board position report and unpack and assemble the train-ground wireless message packets. The preliminary legitimacy judgment on the on-board position report includes: the relationship between the position report and the registration status, and the basic legitimacy check of the fields in the position report.

[0061] 2. Trackside signal application domain, which is used to send the current line turnout, section, and signal machine status to the domain domain, and the domain domain calculates the locking status of the section and turnout, and updates the line turnout, section, and signal machine status according to the results returned by the domain domain. The trackside signal application domain includes: turnout entity service module, track section entity service module, signal machine entity service module and route entity service module. The trackside signal application domain includes the inherent attributes and current status of a specific trackside signal device.

[0062] The turnout entity service module includes: inherent attributes such as turnout speed limit, topological connection relationship, fixed and reverse position status, locked state, and blocked state; protection and driving related turnout status. The turnout entity service module is used to receive turnout operation commands, receive turnout operation commands from the communication interface service layer, and send turnout operation commands to the communication interface service layer (which can support hard-electric interface and OC-based communication interface). The turnout state can be changed according to a single turnout command. At the same time, it has preliminary logical judgment capabilities: when the local resources are in an allocated state, they will not be allocated to other devices again; it does not accept contradictory operations in which directional control and reverse control are established at the same time, etc.

[0063] The track section entity service module includes: inherent attribute information such as section slope, speed limit, station field topology, occupation and clearance status, locking status, blockade status, direction information, and the track section entity service module is used to collect the status of trackside secondary detection equipment (track circuit, axle counter) and receive commands related to the status of trackside secondary detection equipment in the section. It has the ability to handle section functions such as section allocation conflicts and the ability to handle single entity operation commands in the section.

[0064] The signal machine entity service module is used to record the location and topological connection relationship of the signal machine. The signal machine status includes information such as closed, on and off, and signal status. It also has the edge processing capability to guide the safety side according to the conflict of collected information such as filaments. The signal machine entity service module has the ability to correspond the signal machine collection drive code position with the signal machine display color.

[0065] The route entity service module includes: the relationship between the route and the signal, section, and turnout; the current status of the route; and route-related commands. The route entity service module is used to receive route commands and route status information transmitted from the outside, and send the route commands and route status information to the domain, and update the route command status according to the results returned by the domain. Specifically: receive route commands and status information from the outside, send them to the "Line Resource Management Domain Service", and update the route command status according to the "domain" results.

[0066] 3. The temporary speed limit command entity application service module takes the speed limit command as the entity, including: information about the temporary speed limit command itself (including location, time, command number, etc.); information about the current status of the temporary speed limit command; and information about the temporary speed limit initialization command. The temporary speed limit command entity application service module is responsible for the interface function of the speed limit command. The communication interface service layer receives the dispatch command from the dispatch device and the command execution result from this application domain. Send the latest speed limit information to the speed limit command service in the domain domain, and obtain the latest status update from the domain domain.

[0067] 4. External communication interface service module, which is connected to the communication interface service layer and sends the data information of the application domain to the communication interface service layer. It exchanges data with communication modules such as network communication and serial communication, and provides hardware access interface. It provides railway signal security communication protocol services such as subset037, RSSP1, RSSP2, and establishes corresponding link entities. And according to the link status, it triggers related events such as connection establishment and connection interruption. According to the input information, it searches for the application entity in the corresponding application domain and forwards the message to the corresponding entity. It receives the corresponding message from the entity in the application domain and forwards it to the corresponding communication module. When forwarding, the message can be forwarded to the subscribed entity through the subscription mechanism; and the data sent to the external system can be received from the relevant entity. For secure communication protocols, RSSP-II, RSSP-I, subset037, etc. can be designed into the application domain, and one link channel corresponds to one entity. When there is a general domain need, such as general national secret encryption service, the relevant encryption service can be deployed in the domain domain.

[0068] The work to be performed by the application domain includes: (a) sending the data required by the entity to the domain domain at an appropriate time, requesting the service of the domain domain, receiving service feedback from the "domain domain", and updating the local entity data. (b) maintaining the local entity state, maintaining the time validity of the entity state, and triggering the relevant guidance safety side operation when the entity data does not meet the requirements. The safety side operation includes interrupting the connection with the on-board equipment, triggering UEM (unconditional emergency stop message), closing the signal, etc. Periodically checking the entity data, and performing guidance safety side processing when problems with the legality and validity are found. (c) event management, including the update of the train position, the train operation status, external commands (dispatching commands (UEM commands, disaster area commands, section confirmation commands, etc.), platform screen door applications issued by trains, etc.), trackside signal entity status changes, etc., processing according to events and the latest messages, when the domain domain needs to participate, find the corresponding domain service, and request the corresponding service from the "domain domain", and perform corresponding processing according to the feedback results. At the same time, publish new entity information and events to the outside. (d) external interface processing. Interact with the corresponding communication interface service layer. Subscribe to relevant messages from the communication interface service layer, obtain external messages, and send application layer data to the communication interface service layer. The communication interface service layer is responsible for the processing of RSSP1, RSSP2, FSFB2 and other security communication protocols, including security verification and underlying TCP / IP, serial port and other processing.

[0069] The domains include:

[0070] 1) The train driving permit calculation domain service module calculates the train authorization status based on the train position and trackside line status information obtained from the entity of the application domain, obtains the authorization information of each train, and sends the authorization information of each train to the application domain.

[0071] 2) Line resource range calculation domain service module, which is used to calculate the range of line resources required by a certain train. The train entity in the train application domain can provide line attribute information to the train based on this range. The calculation service in the line resource range calculation domain service module can be divided into continuous calculation service and point range calculation service based on balise.

[0072] 3) A train registration domain service module, which is used to receive train registration and deregistration message packets, verify the legitimacy of the train registration and deregistration message packets, and update the train registration and deregistration message packets. In other embodiments, considering that the train registration process is relatively simple and the demand changes very little, this service module can also be deployed in the application domain and completed by each train entity. When the registration function in the scenario is simple, the registration service can be fully implemented by the train registration status application service module. The registration process is relatively simple, so according to the actual line configuration needs, when the line is relatively simple, this train registration domain service module can be flexibly merged with the train registration status application service module in the application domain.

[0073] 4) Train position calculation domain service module, which is used to receive the information of the application domain, and judge the train position according to the train autonomous positioning and the status of the secondary detection equipment on the trackside in the information of the application domain. The comprehensive position of the train is judged according to the train autonomous position report, and the area where the train may be located is judged, and the result is returned to the applicant entity. The train screening function can be implemented to determine whether there are other trains at the head and tail of the train. Occupancy check judgment is performed, and the occupancy check of the section is performed through CEM (Centralized Electronic Module), 3-point or 2-point inspection, etc., to determine whether the train position is already in a certain track section.

[0074] 5) Line resource management domain service module, which is used to judge the current station status data transmitted by the application domain, obtain updated station status data, and send the updated station status data to the application domain, wherein the station status data includes: locking information of switches and sections, signal status information, and switch and signal drive information.

[0075] 6) Temporary speed limit management domain service, according to the speed limit command information transmitted by the application domain, circulates the speed limit command status, and sends the updated speed limit information to the application domain. The circulated speed limit command status includes: illegal status identification, further promotion of legal status, status summary, etc.

[0076] 7) A maintenance diagnosis service module, which is used to receive maintenance log data (input and output interface data, internal operation log data, etc.) sent by other modules in the domain. The maintenance diagnosis service module is used to provide general message parsing, human-computer display and log storage.

[0077] 8) A kilometer mark calculation service module is used to calculate the distance between a kilometer mark and a relative point on the route. The input is the kilometer mark value and the output is the distance. The kilometer mark calculation service module can be provided for various domains including the domain domain.

[0078] 9) Electronic map domain service module is used to provide electronic map data in the current area. The electronic map domain service module can split the overall operation line and station into several sub-areas, and each sub-area provides a domain service to the outside world.

[0079] Any module or a combination of several modules in the application domain, the domain domain and the communication interface service layer corresponds to a virtualized container, and the virtualized container is set in a cloud or local server. Each virtualized container is implemented by two sub-containers with different architectures. The two sub-containers run the requirements of the same domain at the same time. The domain codes in the two sub-containers are designed differently. When the results of domain calculations with the same purpose in the two sub-containers are inconsistent, they are directed to the security side for processing.

[0080] On the other hand, this embodiment also provides a method for implementing a cloud-native train control system based on domain-driven design, which is implemented using the above-mentioned cloud-native train control system based on domain-driven design, and the method includes: dividing and combing the modules in the application domain and the domain domain according to traditional train control functions to decouple the train control system. According to the business field and / or data range, the modules in the application domain and the modules in the domain domain are aggregated and organized, and the aggregated organization includes: dividing the modules in the application domain and the modules in the domain domain according to function to realize the aggregation of the temporary speed limit server, wireless block center, and interlocking train control integrated equipment of the train control system.

[0081] The following is a further introduction to the above technical solution with specific application examples:

[0082] refer to Figure 2As shown, the train equipment initiates the communication connection of subset037, the local communication interface service layer processes the subset037 connection, and generates the corresponding entity to maintain this link. After the link is established, the link establishment event is triggered. When the train registration entity in the train application domain receives the event that a certain train link has been connected, it further prepares the registration process. The registration process is initiated by the on-board equipment, and the local RBC completes the registration process according to the protocol, updates the registration status of the on-board registration entity, and publishes this registration status. Figure 3 This state change event can be consumed by other services.

[0083] refer to Figure 3 As shown, the train regularly reports the onboard position report, and forwards the position report to the train position entity (train position report entity application service module) that has subscribed to the message through the communication interface service layer. The secondary detection equipment collects the track occupancy status information, obtains it through the collection drive service of the communication interface service layer, and sends this message to the track section entity that subscribes to this message. The track section entity pre-processes this collected information (forgiveness of light vehicle jumping, etc.) and publishes this section status. In this example, the route entity and the train position entity have subscribed to the section status information and will receive this information from the infrastructure layer. The route entity calculates the route based on the latest status of the section and turnout, and updates and publishes the route status. The train position entity and the MA entity (train MA status entity service module) have subscribed to the route status and can obtain this status. After obtaining information such as the route, section status, and train position report, the train position entity forwards the information to the train position calculation domain service module, combines various information, calculates the actual position of the train, maps it to the coordinate system inside the system, and returns this result to the train position entity. After detecting the registered status of a certain train, the MA entity starts to act and monitors the train position entity, route entity (route entity service module) and other related service statuses. (Note: This embodiment takes the calculation of MA core content as an example. Other non-core content, such as temporary speed limit retransmission timeout, etc., can be deduced from this specific implementation and will not be repeated here.) The MA entity sends the location, route status, etc. to the MA domain service, obtains the latest MA information from the domain service, and forms an MA message packet that meets the vehicle-ground protocol based on this information, and sends it to the external communication interface service module via the internal message queue. The external communication interface service module packages this information into the subset037 network protocol format and further forwards it to the on-board equipment. The train drives according to this MA information. Considering that any operation will use the electronic map data of the line, this function is obviously the most basic service. Therefore, Figure 3 Access to electronic map domain services is ignored.

[0084] In summary, this embodiment proposes a cloud-native train control system based on domain-driven design and its implementation method, decouples the traditional single-body train control system, splits it into a multi-module train control system, reduces the coupling between modules, and facilitates upgrades and iterations; supports the design of subsequent cloud train control systems, decouples the processing of persistent state preservation from state-independent logic processing, and can deploy different modules in different parts according to different characteristics, making the boundary between cloud, edge and end clearer, laying the foundation for further virtualization of the train control system and cloud migration; facilitates on-site deployment, can realize replacement deployment of each subdomain, can realize the replacement of a certain application function without affecting the implementation of other functions, and can replace the entity of a certain area without affecting the operation of other areas; provides the overall availability and reliability of the train control system. The failure of a single entity or a single service will not cause the overall failure of the train control system.

[0085] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0086] It should be noted that the devices and methods disclosed in the embodiments of this article can also be implemented in other ways. The device implementation described above is only schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of this article. In this regard, each box in the flowchart or block diagram can represent a part of a module, program or code, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented by a dedicated hardware-based system for performing a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0087] In addition, the functional modules in the various embodiments of this document may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0088] Although the content of the present invention has been described in detail through the above preferred embodiments, it should be appreciated that the above description should not be considered as a limitation of the present invention. After reading the above content, it will be apparent to those skilled in the art that various modifications and substitutions of the present invention will occur. Therefore, the protection scope of the present invention should be limited by the appended claims.

Claims

1. A cloud-native train control system based on domain-driven design, It is characterized in that include: Communication interface service layer; An application domain, which is connected to the communication interface service layer, the application domain comprising: a functional module corresponding to a specific entity in the train control system, the application domain being used for preliminary logic processing in the train control system and information interaction with the communication interface service layer; A domain domain, which is connected to the application domain, receives information from the application domain, calculates and / or verifies the corresponding train status information or station status data according to different requests in the information of the application domain, and sends the calculated and / or verified train status information or station status data to the application domain; The infrastructure layer is used for intra-domain communication in the train control system and for providing a virtualized container, wherein the application domain, the domain domain and the communication interface service layer are all arranged in a virtualized container.

2. The cloud-native train control system based on domain-driven design as claimed in claim 1, It is characterized in that The application domains include: A train application domain, which includes a plurality of application entities. Each train corresponds to one application entity in the application domain. The train application domain is used to record specific entity data of a particular train. The trackside signal application domain is used to send the current line switch, section, and signal machine status to the domain domain, and the domain domain calculates the locking status of the section and switch, and updates the line switch, section, and signal machine status according to the results returned by the domain domain. The temporary speed limit command entity application service module uses the speed limit command as an entity and is responsible for the interface function of the speed limit command; The external communication interface service module is connected to the communication interface service layer and sends the data information of the application domain to the communication interface service layer.

3. The cloud-native train control system based on domain-driven design as claimed in claim 2, It is characterized in that The train application domain includes: The train registration status application service module is responsible for the current train registration progress status of a specific train; The train driving permission status entity service module is used to record the authorization status of the train and is used for preliminary driving permission services, as well as the unpacking and packaging of train-ground wireless message packets; The train position report entity application service module is connected to the train registration status application service module and the train driving permit status entity service module respectively, and is used to receive train position report information, receive track circuit collection information, and exchange information with the train registration status application service module and the train driving permit status entity service module respectively. It is also used to make a preliminary legality judgment on the on-board position report and unpack and assemble the train-ground wireless message packets.

4. The cloud-native train control system based on domain-driven design as claimed in claim 3, It is characterized in that The train registration progress status includes: determining whether the train has completed registration and the data interaction status of the intermediate steps in the train registration process.

5. The cloud-native train control system based on domain-driven design as claimed in claim 3, It is characterized in that The preliminary legality judgment of the vehicle-mounted location report includes: the relationship between the location report and the registration status, and the basic legality check of the fields in the location report.

6. The cloud-native train control system based on domain-driven design as claimed in claim 2, It is characterized in that The trackside signal application domain includes: A turnout entity service module, used for receiving a turnout operation command and sending the turnout operation command to the communication interface service layer; Track section entity service module, used to collect the status of trackside secondary detection equipment and receive commands related to the status of trackside secondary detection equipment in the section; The signal machine entity service module is used to record the location and topological connection relationship of the signal machine; The route entity service module is used to receive route commands and route status information transmitted externally, and send the route commands and route status information to the domain, and update the route command status according to the result returned by the domain.

7. The cloud-native train control system based on domain-driven design according to claim 1, It is characterized in that The domains include: The train driving permission calculation domain service module calculates the train authorization status according to the train position and trackside line status information obtained from the entity of the application domain, obtains the authorization information of each train, and sends the authorization information of each train to the application domain; Line resource range calculation domain service module, which is used to calculate the range of line resources required by a certain train; The train registration domain service module is used to receive the train registration and deregistration message packets, verify the legitimacy of the train registration and deregistration message packets, and update the train registration and deregistration message packets; A train position calculation domain service module, which is used to receive the information of the application domain and determine the train position according to the train autonomous positioning and the status of the trackside secondary detection equipment in the information of the application domain; A line resource management domain service module, which is used to judge the current station status data transmitted by the application domain, obtain updated station status data, and send the updated station status data to the application domain; A temporary speed limit management domain service, which transfers the speed limit command status according to the speed limit command information transmitted by the application domain, and sends the updated speed limit information to the application domain; The maintenance diagnosis service module is used to receive maintenance log data sent by other modules in the domain, and provide general message parsing, human-computer display and log storage.

8. The cloud-native train control system based on domain-driven design according to claim 7, It is characterized in that The domain also includes: The kilometer mark calculation service module is used to calculate the distance from a kilometer mark to a relative point on the route; The electronic map domain service module is used to provide electronic map data in the current area.

9. The cloud-native train control system based on domain-driven design according to claim 1, It is characterized in that Any module or a combination of several modules in the application domain, the domain domain and the communication interface service layer corresponds to a virtualized container, and the virtualized container is set in a cloud or a local server.

10. The cloud-native train control system based on domain-driven design according to claim 9, It is characterized in that Each of the virtualized containers is implemented by two sub-containers with different architectures. The two sub-containers run the requirements of the same domain at the same time. The domain codes in the two sub-containers are designed differently. When the results of domain calculations for the same purpose in the two sub-containers are inconsistent, they are directed to the security side for processing.

11. The cloud-native train control system based on domain-driven design according to claim 1, It is characterized in that The intra-domain communication of the train control system includes: communication with external Ethernet, communication with CAN, and communication with a serial bus.

12. A method for implementing a cloud-native train control system based on domain-driven design. It is characterized in that It is implemented using a cloud-native train control system based on domain-driven design as described in any one of claims 1-11, and the method includes: dividing and sorting out the modules in the application domain and the domain domain according to traditional train control functions to decouple the train control system.

13. The method for implementing a cloud-native train control system based on domain-driven design according to claim 12, It is characterized in that Also includes: According to the business field and / or data scope, each module in the application domain and each module in the domain domain are aggregated and organized, and the aggregated organization includes: dividing each module in the application domain and each module in the domain domain according to function, so as to realize the aggregation of the temporary speed limit server of the train control system, the wireless block center, and the interlocking train control integrated equipment.

Images