CN109741229B - Management system and method applied to rail transit - Google Patents
Management system and method applied to rail transit Download PDFInfo
- Publication number
- CN109741229B CN109741229B CN201811366435.2A CN201811366435A CN109741229B CN 109741229 B CN109741229 B CN 109741229B CN 201811366435 A CN201811366435 A CN 201811366435A CN 109741229 B CN109741229 B CN 109741229B
- Authority
- CN
- China
- Prior art keywords
- service
- module
- target
- management
- rail transit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a management system and a method applied to rail transit, wherein the system comprises the following steps: the method comprises the following steps that a plurality of service modules are registered in a registration module, the types of services provided by the service modules are different, the service modules are independently deployed and operated, the services provided by the service modules jointly form a service, and an application terminal receives a service request related to rail transit; the API hosting module is used for determining a target service module corresponding to the service request from registration information prestored in the registration module, generating a target calling interface and calling the target service module through the target calling interface so as to enable the target service module to provide target service; and a target service module in the service modules acquires target service data corresponding to the target service and generates a response message of the service request according to the target service data. The invention can reduce the coupling of the system, make the system easier to maintain and expand new functions, and improve the maintenance and expansion efficiency of the system.
Description
Technical Field
The invention relates to the technical field of rail transit, in particular to a management system and a management method applied to rail transit.
Background
In an automatic ticket selling and checking system corresponding to rail transit, a management system applied to rail transit bears important and complex service functions of rail transit.
In the related art, a management system applied to rail transit is a single framework based on an MVC (Model View Controller, Model-View-Controller) three-layer framework system, in this framework, the coupling of the management system applied to rail transit is high, with the continuous change of rail transit system services, the continuous increase of required functions, the single framework is more and more difficult to meet the requirement of rapid service change, the change of any requirement requires a very long delivery cycle, the system is difficult to maintain and expand new functions, and the maintenance and expansion efficiency is low.
Disclosure of Invention
The present invention is directed to solving, at least to some extent, one of the technical problems in the related art.
Therefore, an object of the present invention is to provide a management system and method for rail transit, which can reduce the coupling of the system, make the system easier to maintain and expand new functions, and improve the maintenance and expansion efficiency of the system.
In order to achieve the above object, a management system for rail transit according to an embodiment of a first aspect of the present invention includes: the system comprises an application terminal, a plurality of service modules, a registration module and an Application Programming Interface (API) (application programming interface) hosting module, wherein the service modules are registered in the registration module, registration information corresponding to the service modules is stored in the registration module, the types of services provided by the service modules are different, the services of various types are obtained by decomposing business services which can be provided by a management system for rail transit in advance, the service modules are independently deployed and operated, the services provided by the service modules jointly form the business services, and the application terminal receives service requests related to rail transit and sends the service requests to the API hosting module; the API hosting module determines a target service module corresponding to the service request from registration information prestored in the registration module, generates a target calling interface, and calls the target service module through the target calling interface to enable the target service module to provide target service; and the target service module in the service modules acquires target service data corresponding to the target service and generates a response message of the service request according to the target service data.
In the management system for rail transit provided in the embodiment of the first aspect of the present invention, since the services that can be provided by the existing management system for rail transit developed based on the monolithic architecture mode are decomposed into a plurality of tiny and interconnected services, and the types of the services provided by the service modules are configured to be different, each type of service is obtained by decomposing the service that can be provided by the management system for rail transit in advance, and the service modules are deployed and operated independently from each other, the services provided by the service modules jointly form a service, and the service flow applied to the management system for rail transit is realized by calling the required service module, the coupling of the system can be reduced, the system is easier to maintain and expand new functions, and the maintenance and expansion efficiency of the system is improved.
In order to achieve the above object, a line center management method according to an embodiment of a second aspect of the present invention includes: receiving a service request related to rail transit, and sending the service request to an Application Programming Interface (API) hosting module; determining a target service module corresponding to the service request from registration information prestored in a registration module, generating a calling interface for calling the target service provided by the target service module, and calling the target service through the calling interface; and acquiring target service data corresponding to the target service, and generating a response message according to the target service data so as to respond to the service request.
In the line center management method provided by the embodiment of the second aspect of the present invention, since the services that can be provided by the existing management system for rail transit developed based on the monolithic architecture mode are decomposed into a plurality of tiny and interconnected services, and the types of the services provided by the service modules are configured to be different, each type of service is obtained by decomposing the service that can be provided by the management system for rail transit in advance, and the service modules are deployed and operated independently from each other, the services provided by the service modules jointly form a service, and the service flow applied to the management system for rail transit is realized by calling the required service module, the coupling of the system can be reduced, the system is easier to maintain and expand new functions, and the maintenance and expansion efficiency of the system is improved.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic structural diagram of a management system for rail transit according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a management system for rail transit according to another embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating the migration of an LC monomer architecture to an LC micro-service architecture according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an overall architecture of an LC system based on an LC microservice architecture according to an embodiment of the present invention;
FIG. 5 is a technical framework design diagram of an LC system based on an LC microservice architecture in an embodiment of the present invention;
FIG. 6 is a schematic diagram of a layered architecture of an application layer of an LC system based on a micro-service architecture according to an embodiment of the present invention;
FIG. 7 is a flowchart of an operation management service according to an embodiment of the present invention;
fig. 8 is a flowchart illustrating a management method applied to rail transit according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention. On the contrary, the embodiments of the invention include all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.
Fig. 1 is a schematic structural diagram of a management system applied to rail transit according to an embodiment of the present invention.
In the embodiment of the present invention, a management system applied to rail transit is taken as an example of a line center management system (LineCenter, LC), which is not limited herein.
Referring to fig. 1, the system 10 includes:
the system comprises an application terminal 106, a plurality of service modules 101, a registration module 102 and an application programming interface API (application programming interface) hosting module 103, wherein the service modules 101 are registered in the registration module 102, registration information corresponding to the service modules 101 is stored in the registration module 102, the types of services provided by the service modules 101 are different, the services of various types are obtained by decomposing service services which can be provided by a management system 10 for rail transit in advance, the service modules 101 are independently deployed and operated, the services provided by the service modules 101 jointly form service services, wherein,
the application terminal 106 receives a service request related to rail transit, and sends the service request to the API hosting module 103.
The API hosting module 103 determines a target service module 101 corresponding to the service request from registration information pre-stored in the registration module 102, generates a target call interface, and calls the target service module 101 through the target call interface, so that the target service module 101 provides the target service.
The service module 101, a target service module 101 in the service module 101 acquires target service data corresponding to a target service, and generates a response message of a service request according to the target service data.
In the embodiment of the present invention, a service module 101 embeds business processing logic for implementing one type of service, the service module 101 corresponding to a service request may be referred to as a target service module 101, one type of service that can be provided by the target service module 101 may be referred to as a target service, service data associated when the target service module 101 provides the target service may be referred to as target service data, and the target service data is stored in a database 104 corresponding to the target service module 101.
Compared with the prior art in which a management system applied to rail transit performs a monolithic architecture based on an MVC three-layer architecture system, in a specific execution process, the embodiment of the present invention decomposes services that can be provided by an existing management system applied to rail transit, which is developed based on a monolithic architecture mode, into a plurality of tiny and interconnected services, embeds business processing logic corresponding to each service into different service modules 101, and implements a business process of the management system 10 applied to rail transit by calling a required service module 101, where the business processing logic corresponding to each service can implement different types of business, each service module 101 can be regarded as a micro application, can be deployed and operated independently, and does not affect other service modules 101, and data can be performed between each service module 101 through a presentation layer State Transfer application Programming Interface REST API (presentation State Transfer application Programming Interface) based on a hypertext Transfer protocol (http) between the service modules 101 And (4) communication.
The types of the service processing logics are different, and the types of the service processing logics comprise at least one of the following types: an operation management service type, a user management service type, an asset management service type, a data management service type, a log and report management service type, a revenue management service type, and a maintenance service management type.
In the specific execution process of the embodiment of the present invention, the service that can be provided by the management system 10 for rail transit may be analyzed and processed in advance to obtain service processing logics for each type, where the service processing logic may be specifically a section of program code, and then each service processing logic is embedded into one service module 101, so as to form a plurality of service modules 101 that provide different types of services.
In the specific implementation process of the embodiment of the present invention, referring to fig. 2, the system further includes: and the databases 104 correspond to the service modules 101, and the database 104 stores service data corresponding to the service modules 101, wherein the target service module 101 acquires target service data corresponding to the target service from the corresponding database 104.
Specifically, in the embodiment of the present invention, the service data stored in the background database 104 of the management system 10 applied to the rail transit may be divided according to the types, and the service data corresponding to each type obtained by the division is stored in one database 104, and is subjected to data communication with the service module 101 of the corresponding type, so that the target service module 101 can obtain the target service data corresponding to the target service from the corresponding database 104.
Referring to fig. 3, fig. 3 is a schematic diagram illustrating a migration of an LC cell architecture to an LC micro service architecture in the embodiment of the present invention, where the micro service architecture is the architecture of the management system applied to rail transit in the embodiment of the present invention. Referring to fig. 4, fig. 4 is a diagram illustrating an overall architecture of an LC system based on an LC microservice architecture according to an embodiment of the present invention.
In the embodiment of the present invention, the API hosting module 103 of the application programming interface may be specifically an API gateway, where the API gateway is a core module, and is configured to determine the target service module 101 corresponding to the service request from the registration information pre-stored in the registration module 102, generate the target calling interface, and call the target service module 101 through the target calling interface, so that the target service module 101 provides the target service, the API gateway encapsulates an internal structure of the application, and the application terminal 106 only needs to interact with the API gateway without knowing a specific micro-service architecture.
The application terminal 106 may be, for example, a personal computer, a mobile terminal, and the like, and the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, and an electronic book.
In the specific implementation process of the embodiment of the present invention, referring to fig. 2, the system further includes: the configuration module 105 is connected to the registration module 102, wherein the configuration module 105 is configured to provide a configuration management logic, dynamically allocate registration information of each service module 101 in the registration module 102 based on the configuration management logic, and dynamically verify and manage the registration information.
In the specific execution process of the embodiment of the present invention, the service request is a non-bottom system service request, wherein when the service request is a non-bottom system service request, the application terminal 106 receives the non-bottom system service request related to rail transit, and sends the non-bottom system service request to the API hosting module 103.
In the specific execution process of the embodiment of the present invention, the embodiment further includes a service function module 107, an API hosting module 103, and a target calling interface sending module 107; and the service function module 107 is configured to parse the target call interface, generate a service request instruction corresponding to the target call interface, and send the service request instruction to a corresponding system application layer, so as to call the target service module 101 through the service request instruction.
As an example, the LC system in the embodiment of the present invention may further include a presentation layer, a platform layer, an application layer, and a resource layer. Referring to fig. 5, fig. 5 is a technical framework design diagram of an LC system based on an LC micro-service architecture in the embodiment of the present invention, a Spring Cloud (an ordered set of a series of frameworks) technical framework may be selected, and the Spring Cloud technical framework utilizes development convenience of a Spring Boot (a framework), so that development of a distributed system infrastructure can be effectively simplified, and for example, service discovery registration, load balancing, a configuration center, a message bus, and the like may all implement one-key startup and deployment based on the Spring Boot.
As an example, in the embodiment of the present invention, the LC system further includes a presentation layer, a platform layer, an application layer, and a resource layer, and describes an operation process of the LC system:
1. the display layer is used for receiving a user instruction to display or submit data, the user of the direct application terminal carries out interaction, the user can carry out operations such as adding, deleting, modifying and checking on information of the display layer through the application terminal, the display layer converts the operations into service requests agreed with the platform layer, the service requests are sent to the platform layer to carry out corresponding processing, and finally response messages corresponding to the service requests are generated and returned to the display layer, wherein the display layer and the platform layer carry out data communication based on JWT (JSON WEB TOKEN based on JSON open standard).
2. And the platform layer is responsible for receiving and analyzing the service request submitted by the display layer, analyzing the registration information in the service request, determining a corresponding target service module according to the registration information, calling the target service module to provide target service, wherein the service request is a non-bottom system service request, and when the service request is the non-bottom system service request, the application terminal receives the non-bottom system service request related to rail transit and sends the non-bottom system service request to the API hosting module.
The API gateway is a core module and is used for determining a target service module corresponding to the service request from registration information prestored in the registration module, generating a target calling interface and calling the target service module through the target calling interface to enable the target service module to provide target service, the API gateway encapsulates the internal structure of an application program, and the application terminal only needs to interact with the API gateway without knowing details of a specific micro-service architecture.
3. And the application layer is used for receiving the service request submitted by the platform layer, analyzing and processing the service request, and calling the corresponding business processing logic of the target service according to the service request so as to process the corresponding service request. For example, if the service request is to modify a user data, the user management service type is called according to the service request, and the user data is modified and stored in the corresponding database.
As an example, the application layer in the embodiment of the present invention may include a service application layer and a system application layer. The service application layer is used for analyzing and obtaining a service request corresponding to the service of the service application layer from the request instruction and sending the service request to a corresponding service module in the system application layer. The system application layer is responsible for specifically processing user service requirements indicated by various actual request instructions, such as parameter management, equipment management, user management and other specific service processing logics. The implementation principle of each business processing logic is to call a single or combined call core service to process different business requirements through different configurations. Typically by exposing the REST API interface for API gateway calls.
The specific implementation process is as follows:
1. and responding to the service request submitted by the service application layer, and analyzing and processing various service application configurations to provide corresponding services.
2. And analyzing the specific service request as a basic add-delete modify-check request.
3. And correspondingly modifying the data of the resource layer.
4. And the resource layer receives and analyzes the service request sent by the application layer, and then provides corresponding service data to the application layer according to a protocol analysis result of the service request. Referring to fig. 4, it can be seen that the resource layer at least includes SQL (Structured query Language) type relational databases and NOSQL (Not Only Structured query Language) type non-relational databases, and in the embodiment of the present invention, redis databases (a log type, Key-Value database) and mysql (relational database management system) databases that are open source, written using ANSI C Language (a standard for C Language introduced by the american national standards institute and international standardization organization), support networks, can be based on memory and can also be persisted) and mysql (a relational database management system) databases can be selected. The redis database is a cache database, the data processing efficiency can be rapidly improved, and the mysql database is mainly used for data persistence and storing all data of the system.
For the purpose of facilitating an understanding of the present invention, reference will now be made to the following detailed description of the embodiments taken in conjunction with the accompanying drawings.
Referring to fig. 6, fig. 6 is a schematic diagram of a layered architecture of an LC system application layer based on a micro-service architecture in an embodiment of the present invention, where the system application layer 320 includes a user management service 321, an operation management service 322, a log report management service 323, an asset management service 324, a data management service 325, a revenue management service 326, and a maintenance management service 327. The operation management service 322 according to the preferred embodiment of the present invention is specifically described.
As shown in fig. 7, fig. 7 is a flowchart of an operation management service in the embodiment of the present invention, and the operation management service flow of the present invention is as follows:
the user uses the application terminal to operate the operation management front-end scene, and the front-end interactive interface package protocol data submits a service request to the operation management server.
The service request is forwarded to the connection service through the load balancer, the connection service request session service verifies the identity, and the service data is forwarded to the operation management service through the resolution protocol after the verification passes.
And the operation management service executes the operation management logic script, requests the data access service to execute a data reading operation if the data needs to be read, otherwise generates a transaction and submits the transaction to the data access service to execute a data writing operation, and returns a result to the operation management service after the data access service is successfully executed.
And after the operation management service processes the service logic, the operation management service asynchronously sends the behavior log and returns the result to the connection service, and the connection service packages protocol data of the operation result and returns the protocol data to the front end.
In the embodiment of the present invention, compared with the single LC system based on the MVC three-layer architecture in the related art, the system has the following advantages: the whole business is divided into a plurality of services, and the granularity is fine; the centralized bus is not needed, and the system is a loose service architecture; the communication among the services is simple, and the communication is carried out based on a lightweight protocol; each service can be independently deployed and run in different threads without influence. The LC system based on the micro-service architecture mainly has the following advantages: the whole system is interacted in a component calling mode based on RESTAPI, high loose coupling is achieved, and reliability and expandability of the LC system are greatly improved. Each micro service is independently deployed, the change of each service does not affect other services, the redeployment only needs to deploy the micro service, and the deployment time and complexity are greatly reduced. Each micro-service can determine a proper technical scheme according to the application of the micro-service, specifically solves specific services, is not limited to a single technology any more, greatly improves the development efficiency and reduces the risk rate of the system. Each development team only needs to be concentrated on the service module of the development team, communication cost between team cooperation is reduced, and if new members join subsequently, only the corresponding modules need to be known, so that the development work threshold is reduced.
In this embodiment, since the services that can be provided by the management system applied to the rail transit developed based on the existing single architecture mode are decomposed into a plurality of tiny and interconnected services, and the types of the services provided by the service modules are configured to be different, each type of service is obtained by decomposing the service that can be provided by the management system applied to the rail transit in advance, and the service modules are deployed and operated independently from each other, the services provided by the service modules jointly constitute the service, and the service flow of the management system applied to the rail transit is realized by calling the required service module, the coupling of the system can be reduced, the system is easier to maintain and expand new functions, and the maintenance and expansion efficiency of the system is improved.
Fig. 8 is a flowchart illustrating a management method applied to rail transit according to an embodiment of the present invention.
Referring to fig. 8, the method includes:
s801: the method comprises the steps of controlling a plurality of service modules to register in a registration module, wherein registration information corresponding to each service module is stored in the registration module, types of services provided by each service module are different, each type of service is obtained by decomposing service services which can be provided by a management system for rail transit in advance, the service modules are deployed and operated independently, and the service provided by each service module jointly forms the service.
S802: receiving a service request related to rail transit, and sending the service request to an Application Programming Interface (API) hosting module.
S803: and determining a target service module corresponding to the service request from the registration information prestored in the registration module, generating a target calling interface, and calling the target service module through the target calling interface to enable the target service module to provide the target service.
S804: and acquiring target service data corresponding to the target service, and generating a response message of the service request according to the target service data.
Optionally, in some embodiments, the method further comprises:
and acquiring target service data corresponding to the target service from a database corresponding to the target service module.
Optionally, in some embodiments, the types include at least one of:
an operation management service type, a user management service type, an asset management service type, a data management service type, a log and report management service type, a revenue management service type, and a maintenance service management type.
Optionally, in some embodiments, the method further comprises:
and providing configuration management logic, dynamically distributing the registration information of each service module in the registration module based on the configuration management logic, and dynamically verifying and managing the registration information.
Optionally, in some embodiments, the service request is a non-underlying system service request, wherein,
when the service request is a non-bottom system service request, the application terminal receives the non-bottom system service request related to rail transit and sends the non-bottom system service request to the API hosting module.
Optionally, in some embodiments, the application programming interface API hosting module is an API gateway.
Alternatively, in some embodiments, wherein,
sending the target calling interface to a service function module;
and analyzing the target calling interface through the service function module, generating a service request instruction corresponding to the target calling interface, and sending the service request instruction to a corresponding system application layer so as to call the target service module through the service request instruction.
It should be noted that the explanation of the embodiment of the management system 10 for rail transit in the foregoing fig. 1-7 is also applicable to the management method for rail transit in this embodiment, and the implementation principle is similar, and is not repeated here.
In this embodiment, since the services that can be provided by the management system applied to the rail transit developed based on the existing single architecture mode are decomposed into a plurality of tiny and interconnected services, and the types of the services provided by the service modules are configured to be different, each type of service is obtained by decomposing the service that can be provided by the management system applied to the rail transit in advance, and the service modules are deployed and operated independently from each other, the services provided by the service modules jointly constitute the service, and the service flow of the management system applied to the rail transit is realized by calling the required service module, the coupling of the system can be reduced, the system is easier to maintain and expand new functions, and the maintenance and expansion efficiency of the system is improved.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present invention, "a plurality" means two or more unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (12)
1. A management system applied to rail transit is characterized by comprising: an application terminal, a plurality of service modules, a registration module, and an application programming interface, API, hosting module, wherein,
the plurality of service modules are registered in the registration module, the registration module stores registration information corresponding to each service module, the types of services provided by each service module are different, each type of service is obtained by decomposing service services which can be provided by a management system for rail transit in advance, the service modules are deployed and operated independently, the service provided by each service module jointly forms the service, wherein,
the application terminal receives a service request related to rail transit and sends the service request to the API hosting module;
the API hosting module determines a target service module corresponding to the service request from registration information prestored in the registration module, generates a target calling interface, and calls the target service module through the target calling interface to enable the target service module to provide target service;
the target service module in the service modules acquires target service data corresponding to the target service and generates a response message of the service request according to the target service data;
the system further comprises: a configuration module coupled to the registration module, wherein,
the configuration module is used for providing configuration management logic, dynamically distributing the registration information of each service module in the registration module based on the configuration management logic, and dynamically verifying and managing the registration information.
2. The management system for rail transit as set forth in claim 1, wherein said system further comprises: a plurality of databases, each of which corresponds to each service module, each of which stores service data of the corresponding service module, wherein,
and the target service module acquires target service data corresponding to the target service from a corresponding database.
3. The management system for rail transit as set forth in claim 1, wherein said type includes at least one of:
an operation management service type, a user management service type, an asset management service type, a data management service type, a log and report management service type, a revenue management service type, and a maintenance service management type.
4. The management system for rail transit application of claim 1, wherein the service request is a non-underlying system service request, wherein,
and when the service request is the non-bottom system service request, the application terminal receives the non-bottom system service request related to rail transit and sends the non-bottom system service request to the API hosting module.
5. The management system applied to rail transit of any one of claims 1 to 4, wherein the Application Programming Interface (API) hosting module is an API gateway.
6. The management system for rail transit according to any one of claims 1 to 4, further comprising a service function module, wherein,
the API hosting module is also used for sending the target calling interface to the business function module;
and the business function module is used for analyzing the target calling interface, generating a service request instruction corresponding to the target calling interface, and sending the service request instruction to a corresponding system application layer so as to call the target service module through the service request instruction.
7. A management method applied to rail transit is characterized by comprising the following steps:
controlling a plurality of service modules to register in a registration module, wherein registration information corresponding to each service module is stored in the registration module, the types of services provided by each service module are different, each type of service is obtained by decomposing service services which can be provided by a management system for rail transit in advance, the service modules are deployed and operated independently, and the service provided by each service module jointly forms the service;
receiving a service request related to rail transit, and sending the service request to an Application Programming Interface (API) hosting module;
determining a target service module corresponding to the service request from registration information prestored in a registration module, generating a target calling interface, and calling the target service module through the target calling interface to enable the target service module to provide a target service;
acquiring target service data corresponding to the target service, and generating a response message of the service request according to the target service data;
further comprising:
and providing configuration management logic, dynamically distributing the registration information of each service module in the registration module based on the configuration management logic, and dynamically verifying and managing the registration information.
8. The management method applied to rail transit of claim 7, further comprising:
and acquiring target service data corresponding to the target service from a database corresponding to the target service module.
9. The management method applied to rail transit of claim 7, wherein the type includes at least one of:
an operation management service type, a user management service type, an asset management service type, a data management service type, a log and report management service type, a revenue management service type, and a maintenance service management type.
10. The management method for rail transit application according to claim 7, wherein the service request is a non-underlying system service request,
and when the service request is the non-bottom system service request, the application terminal receives the non-bottom system service request related to rail transit and sends the non-bottom system service request to the API hosting module.
11. The management method applied to rail transit of any one of claims 7 to 10, wherein the API hosting module is an API gateway.
12. The management method applied to rail transit of any one of claims 7 to 10, wherein,
sending the target calling interface to a service function module;
and analyzing the target calling interface through the service function module, generating a service request instruction corresponding to the target calling interface, and sending the service request instruction to a corresponding system application layer so as to call the target service module through the service request instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811366435.2A CN109741229B (en) | 2018-11-16 | 2018-11-16 | Management system and method applied to rail transit |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811366435.2A CN109741229B (en) | 2018-11-16 | 2018-11-16 | Management system and method applied to rail transit |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109741229A CN109741229A (en) | 2019-05-10 |
| CN109741229B true CN109741229B (en) | 2020-04-24 |
Family
ID=66355688
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811366435.2A Active CN109741229B (en) | 2018-11-16 | 2018-11-16 | Management system and method applied to rail transit |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109741229B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110427676A (en) * | 2019-07-23 | 2019-11-08 | 交控科技股份有限公司 | A kind of public cloud service system of rail traffic based on micro services framework |
| CN112394675B (en) * | 2019-08-12 | 2023-02-10 | 比亚迪股份有限公司 | Monitoring system, method and server for rail transit |
| CN111376953B (en) * | 2019-12-30 | 2021-11-12 | 交控科技股份有限公司 | Method and system for issuing plan for train |
| CN111865746B (en) * | 2020-06-19 | 2022-08-19 | 苏宁云计算有限公司 | System development method and device based on loop bus |
| CN113077241B (en) * | 2021-04-21 | 2024-06-18 | 北京沃东天骏信息技术有限公司 | Approval processing method, device, equipment and storage medium |
| CN113269460B (en) * | 2021-06-08 | 2023-09-01 | 巨石集团有限公司 | Collaborative system and collaborative architecture for multiple management systems |
| CN113726578B (en) * | 2021-09-01 | 2024-04-12 | 网络通信与安全紫金山实验室 | Fusion method of API gateway and network architecture system |
| CN115712499A (en) * | 2022-11-09 | 2023-02-24 | 北京城建设计发展集团股份有限公司 | Rail transit service AI chip driving task processing method and system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2042986A1 (en) * | 2007-09-21 | 2009-04-01 | Nokia Siemens Networks Oy | Method and system for execution of a service-related process |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006102467A2 (en) * | 2005-03-21 | 2006-09-28 | Primitive Logic, Inc. | Service-oriented architecture |
| CN103440298A (en) * | 2013-08-20 | 2013-12-11 | 曙光信息产业(北京)有限公司 | Data access management device and management method and database service platform |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN106130759B (en) * | 2016-06-22 | 2021-02-09 | 白杨 | Service-oriented modular system architecture |
| CN106878393A (en) * | 2017-01-16 | 2017-06-20 | 深圳市商沃科技发展有限公司 | A kind of system based on fusion micro services framework |
| CN107193546B (en) * | 2017-04-11 | 2021-05-04 | 国网天津市电力公司信息通信公司 | Micro-service business application system |
| CN108737525A (en) * | 2018-05-10 | 2018-11-02 | 江苏天时新材料科技有限公司 | A kind of Web service system based on REST frameworks |
-
2018
- 2018-11-16 CN CN201811366435.2A patent/CN109741229B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2042986A1 (en) * | 2007-09-21 | 2009-04-01 | Nokia Siemens Networks Oy | Method and system for execution of a service-related process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109741229A (en) | 2019-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109741229B (en) | Management system and method applied to rail transit | |
| CN107241315B (en) | Access method and device of bank gateway interface and computer readable storage medium | |
| KR20140047580A (en) | Method and system for synchronization mechanism on multi-server reservation system | |
| CN108022090B (en) | Virtual account management method, device, system and readable storage medium | |
| CN112073269A (en) | Block chain network testing method, device, server and storage medium | |
| CN110413676A (en) | The access method and its device of database, electronic equipment and medium | |
| CN101286212A (en) | Business flow path execution method, business flow path engines and its deployment method | |
| CN113505520A (en) | Method, device and system for supporting heterogeneous federated learning | |
| CN112418784B (en) | Service arranging and executing system and method | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| CN114358921A (en) | System switching method, apparatus, device, medium, and program product | |
| CN112910835B (en) | Block chain-based configuration management method, apparatus, system, device, and medium | |
| CN110442601A (en) | A kind of method and apparatus that Openstack mirror image data accelerates parallel | |
| US11330053B1 (en) | Making eventual consistency cache updates deterministic | |
| US20230267430A1 (en) | Data processing method and device, and computer-readable storage medium | |
| US9059992B2 (en) | Distributed mobile enterprise application platform | |
| CN112988738B (en) | Data slicing method and device for block chain | |
| US20180205617A1 (en) | System and method for graphically building a virtual network of computer components | |
| CN115146316A (en) | Cross-system data access method, device, equipment and medium | |
| CN110990280B (en) | Automatic test data generation system and method | |
| CN112558941A (en) | DDD-based micro-service request processing method, system, device and medium | |
| CN113590575A (en) | Service integration sharing-based method, device, terminal and storage medium | |
| CN111866171A (en) | Message processing method and device, electronic equipment and medium | |
| CN113077241B (en) | Approval processing method, device, equipment and storage medium | |
| CN114398082B (en) | Compatible operation method and device for frame type block chain application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |