Rapid deployment method and device for rail transit signal system

Abstract

The invention provides a rapid deployment method and device for a rail transit signal system, and relates to the technical field of rail transit, and the method comprises the steps: splitting a code program of the rail transit signal system into execution codes of a plurality of business services, and constructing a container mirror image for each business service; initializing the deployment file template to generate a configuration file; based on the configuration file and the container mirror image, executing a deployment task in the to-be-deployed environment; and performing health state check on each started business service, and verifying that the rail transit signal system is successfully deployed according to the configuration file. According to the method and the device provided by the invention, the container mirror image is constructed for each business service, so that the separation of the running environment and the service application is realized; the problem of configuration complexity caused by operation environment difference is solved through the configuration file; through the configuration file and the container mirror image, the deployment efficiency of the rail transit signal system is improved, the risk caused by human errors is reduced, and the operation and maintenance cost of the system is reduced.

Description

Technical Field

[0001] This application relates to the field of rail transit technology, and in particular to a method and apparatus for the rapid deployment of a rail transit signaling system. Background Technology

[0002] The rapid development of urban rail transit has placed higher demands on the deployment efficiency of signaling systems. Traditional signaling system deployment methods suffer from problems such as long installation cycles and complex configurations, making it difficult to meet the rapid and efficient needs of modern rail transit.

[0003] Therefore, how to improve the deployment efficiency of rail transit signaling systems and reduce operation and maintenance costs has become a technical problem that the industry urgently needs to solve. Summary of the Invention

[0004] This application provides a method and apparatus for rapid deployment of a rail transit signaling system, which addresses the technical problem of how to improve the deployment efficiency of rail transit signaling systems and reduce operation and maintenance costs.

[0005] This application provides a method for rapid deployment of a rail transit signaling system, including: The code program of the rail transit signaling system is split into the execution code of multiple independent business services, and a container image containing the runtime environment and execution code is built for each business service. Obtain the deployment file template, and initialize the deployment file template based on the network information and node configuration information of the environment to be deployed in the rail transit signaling system, and generate a configuration file; Based on the configuration file and the container image, the deployment task is executed in the environment to be deployed, and various business services are started. Perform a health status check on each activated business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

[0006] In some embodiments, the step of splitting the code program of the rail transit signaling system into the executable code of multiple independent business services, and building a container image containing the runtime environment and executable code for each business service, includes: Based on the type of the code program of the rail transit signaling system, the code program is atomically decomposed to obtain the execution code of each decomposed business service. Determine the operating environment that is compatible with the code program of the rail transit signaling system, and start the basic container in the operating environment; The execution code of each business service is deployed and started within the basic container, and the program files and configurations inside the basic container are standardized. The standardized base container is then solidified into container images for each business service.

[0007] In some embodiments, the method further includes: Record the mapping relationship between the version of the execution code of each business service and the attribute information of the container image of each business service.

[0008] In some embodiments, the code program of the rail transit signaling system includes front-end programs, middleware programs, and back-end programs; The front-end program includes a front-end web page program; The middleware program includes a database service program and / or a message queue service program; The backend program includes at least one of the following: an interface program, a data collection service program, a scheduled task service program, a task scheduling service program, a monitoring and control integration service program, and an alarm service program.

[0009] In some embodiments, the method further includes: The load balancing deployment mode is determined to be a dual-active mode for service components; Based on the load deployment mode, determine the number of container image replicas deployed for each business service.

[0010] In some embodiments, the step of executing deployment tasks and starting various business services in the environment to be deployed based on the configuration file and the container image includes: Obtain container logs for each business service; The deployment task's process status is tracked based on the container logs.

[0011] In some embodiments, the health status check of each initiated service to verify that the rail transit signaling system has been successfully deployed according to the configuration file includes: Automated checks are performed on at least one of the following: version information, service availability, and environment parameters of each launched business service, and a deployment report is generated.

[0012] This application provides a rapid deployment device for a rail transit signaling system, comprising: The split module is used to split the code program of the rail transit signaling system into the execution code of multiple independent business services, and build a container image containing the runtime environment and execution code for each business service. The generation module is used to obtain the deployment file template and initialize the deployment file template based on the network information and node configuration information of the environment to be deployed of the rail transit signaling system, and generate a configuration file. The deployment module is used to execute deployment tasks and start various business services in the environment to be deployed based on the configuration file and the container image. The inspection module is used to perform health status checks on each started business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

[0013] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement a rapid deployment method for a rail transit signaling system.

[0014] This application provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the rapid deployment method for the rail transit signaling system.

[0015] The rapid deployment method and apparatus for rail transit signaling systems provided in this application separate the operating environment and service applications by splitting the code program of the rail transit signaling system into the executable code of multiple independent business services and building a container image containing the runtime environment and executable code for each business service. It initializes the deployment file template based on the network information and node configuration information of the environment to be deployed in the rail transit signaling system, generating configuration files and solving the configuration complexity problem caused by differences in the operating environment. Using the configuration files and container images, the deployment task is executed in the environment to be deployed, starting each business service and performing health status checks on each started business service, ensuring the deployment process is fast, reliable, and verifiable. This greatly improves the deployment efficiency of rail transit signaling systems, reduces the risk of human error, and lowers the system's operation and maintenance costs. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is one of the flowcharts illustrating the rapid deployment method for the rail transit signaling system provided in this application.

[0019] Figure 2 This is the second flowchart illustrating the rapid deployment method for the rail transit signaling system provided in this application.

[0020] Figure 3This is a structural schematic diagram of the rapid deployment device for the rail transit signaling system provided in this application.

[0021] Figure 4 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0023] It should be noted that the terms "first," "second," etc., used in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps, units, or modules is not necessarily limited to those explicitly listed, but may include other steps, units, or modules not explicitly listed or inherent to such processes, methods, products, or devices.

[0024] In related technologies, the deployment of rail transit signaling systems is carried out manually, mainly including: (1) the initialization of the node basic environment is done manually, such as installing database services and middleware services; (2) the middleware service program is started manually using commands; (3) the network address configuration before the middleware service program starts normally is done manually by modifying the address parameters; (4) after the middleware service is started, the application programming interface (API) of the platform and other monitoring platforms is connected manually by modifying the database fields; (5) the joint debugging test verification between various functional components of the platform is done manually by using the interface testing tool (postman); (6) the configuration files corresponding to the functional components are modified manually; (7) the values ​​of the fields in the database initialization table are modified.

[0025] The aforementioned manual deployment of the system takes a long time and is prone to errors that lead to troubleshooting problems. Troubleshooting these problems consumes a lot of time and manpower, and can easily result in incorrect configurations that delay the deployment schedule.

[0026] To solve the above technical problems, Figure 1 This is one of the flowcharts illustrating the rapid deployment method for the rail transit signaling system provided in this application, such as... Figure 1 As shown, the method includes steps 110, 120, 130 and 140.

[0027] Step 110: Split the code program of the rail transit signaling system into the execution code of multiple independent business services, and build a container image containing the runtime environment and execution code for each business service.

[0028] Specifically, the rapid deployment method for rail transit signaling systems provided in this application is implemented by a rapid deployment device or system. This device can be implemented in software, such as a rapid deployment application running on a computer; or in hardware, such as a server, cloud computing platform, or terminal device with sufficient computing power to execute the rapid deployment method for rail transit signaling systems.

[0029] The rail transit signaling system is a key system equipment for ensuring train operation safety, modernizing train command and operation, and improving transportation efficiency. It integrates control technology, computer technology, network technology, and communication technology, and is mainly used for train route control and scheduling, information management, operational condition monitoring, and maintenance management. Its code program typically includes multiple functional modules such as a front-end interactive interface, back-end business logic, database interaction, message queue communication, and interface with external systems.

[0030] The code of a rail transit signaling system can be atomically decomposed into multiple independent business service execution codes. This allows each decomposed service to run, upgrade, and expand independently, and provides clearly defined functional interfaces to the outside world. For example, the entire system can be decomposed into front-end web services, interface services, data acquisition services, scheduled task services, alarm services, database services, message queue (MQ) services, etc.

[0031] After atomic splitting, a container image needs to be built for each independent business service. This container image is a lightweight, portable, self-contained software package that encapsulates everything needed to run the business service, including: executable code (i.e., the business service's own program files), runtime environment (such as specific versions of operating system libraries, programming language runtime environments, etc.), system tools, dependency libraries, and related configuration files. By packaging the execution service and its runtime environment together, consistent performance across any deployment environment can be ensured.

[0032] The specific process of building a container image may include: First, selecting a suitable operating system base image; then, installing all the dependency libraries and runtime environment required by the business service on top of the base image; next, copying the executable code of the business service to a specified path within the image; finally, defining the commands to be executed when the container starts (such as a script to start the service), and saving this state containing the complete environment and code as a new, immutable container image.

[0033] Step 120: Obtain the deployment file template, and initialize the deployment file template based on the network information and node configuration information of the rail transit signaling system's deployment environment to generate a configuration file.

[0034] Specifically, a deployment file template is a predefined configuration file or a set of configuration files. These templates define how to deploy and run various business services, such as which services need to be started, how many instances (replicas) of each service are required, the dependencies between services, port mapping rules, etc. However, parameters related to the specific deployment environment (such as network address, database password, node name, etc.) are represented using variable placeholders. Deployment file templates can be pulled from the environment center repository.

[0035] The network information and node configuration information of the environment to be deployed refer to the parameters of the specific physical or virtual environment where the rail transit signaling system will be deployed. This information typically includes: the network address (IP address) and hostname of each server node, the port numbers to be exposed, the database connection address, username and password, and the allocation strategy for which nodes(s) each service is deployed on. This information can be centrally stored and managed, for example, in a central environment repository, for easy retrieval and modification.

[0036] After initializing the deployment file template, a directly executable configuration file can be generated.

[0037] Step 130: Based on the configuration file and container image, execute the deployment task in the environment to be deployed and start each business service.

[0038] Specifically, the environment to be deployed refers to a server node that has already installed an operating system and a container runtime engine.

[0039] You can use container orchestration tools or custom deployment scripts to parse configuration files, pull container images corresponding to each business service according to the instructions in the configuration files, distribute them to the specified server nodes, and start the containers on the corresponding nodes to run each business service.

[0040] Step 140: Perform a health check on each started business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

[0041] Specifically, a pre-defined health check is performed on each business service after deployment. For example, it checks whether the database service port is reachable, whether the interface service can correctly respond to interface call requests, and whether the data acquisition service has established a connection with the lower-level device.

[0042] Only when all critical business services have passed the health status check will the system finally confirm that the rail transit signaling system has been successfully deployed according to the configuration file. The check results can automatically generate a deployment report, which includes version information, operating status, environmental parameter verification, etc., for operation and maintenance personnel to refer to and archive.

[0043] The rapid deployment method for rail transit signaling systems provided in this application separates the system's code into the executable code of multiple independent business services. For each service, a container image containing the runtime environment and executable code is built, achieving separation of the runtime environment and service applications. By initializing the deployment file template based on the network information and node configuration information of the environment to be deployed, a configuration file is generated, resolving the configuration complexity issue caused by differences in runtime environments. Using the configuration file and container image, deployment tasks are executed in the environment to be deployed, starting each business service and performing health checks on the started services, ensuring a fast, reliable, and verifiable deployment process. This significantly improves the deployment efficiency of rail transit signaling systems, reduces the risk of human error, and lowers system operation and maintenance costs.

[0044] It should be noted that each implementation method of this application can be freely combined, rearranged, or executed individually, and does not need to rely on or depend on a fixed execution order.

[0045] In some embodiments, the code program of the rail transit signaling system is split into the executable code of multiple independent business services, and a container image containing the runtime environment and executable code is built for each business service, including: Based on the type of code program in the rail transit signaling system, the code program is atomically decomposed to obtain the execution code of each decomposed business service. Determine the operating environment that is compatible with the code program of the rail transit signaling system, and start the basic container in the operating environment; Deploy and start the execution code of each business service within the base container, and standardize the program files and configurations inside the base container; The standardized base container is then solidified into container images for each business service.

[0046] Specifically, the code program of the rail transit signaling system can be atomically decomposed according to its type. Atomic decomposition refers to breaking down this monolithic application according to its business boundaries, into the smallest autonomous service units that can independently provide complete functionality.

[0047] The code programs for rail transit signaling systems can be categorized into front-end programs, middleware programs, and back-end programs. Front-end programs include web applications. Middleware programs include database (DB) services and / or message queue (MQ) services. Back-end programs include interface programs, data acquisition services, scheduled task services, task scheduling services, monitoring integration services, and alarm services, among others.

[0048] After atomic decomposition, the originally large and complex code program was broken down into a series of independent code projects with single functions and clear responsibilities, namely the execution code of each business service.

[0049] The runtime environment refers to the software environment necessary for running the execution code of various business services, including but not limited to the operating system, specific versions of programming languages, and necessary third-party dependency libraries and frameworks. For business services developed using different technology stacks, their compatible runtime environments need to be determined. In this embodiment, the runtime environment compatible with the code program of the rail transit signaling system refers to the runtime environment on the physical server in the deployment environment.

[0050] After determining the runtime environment, you need to select a trusted base image that contains that environment and start a temporary container instance in the container engine. This temporary container instance is the base container. To achieve standardization and consistency within the base container, the following steps can be performed: First, copy or deploy the execution code of each split business service to the designated directory of the base container. Standardize the code to ensure the container image is portable and environment-independent. Standardization can include configuration standardization, path standardization, startup script standardization, and permission standardization. For programs started inside the container, perform external API call checks and verifications.

[0051] Secondly, the standardized base container is solidified into container images for each business service. Once the standardization process is complete, the base container contains a complete, clean, and configurable instance of the business service. At this point, using commands provided by the container engine, the base container, along with its fixed configuration and standard programs, is used to create an image, solidifying it into a new, immutable image file. This file is the container image for that business service.

[0052] By following the steps above, separate container images can be built for each business service. These images will then be centrally managed for future deployment.

[0053] The rapid deployment method for rail transit signaling systems provided in this application can atomically decompose complex rail transit signaling system code programs and systematically and standardizedly transform them into container images of a series of independent business services. This lays a solid technical foundation for subsequent automated deployment and effectively ensures the consistency of applications in different operating environments, thereby significantly improving the deployment efficiency of rail transit signaling systems.

[0054] In some embodiments, the method further includes: Record the mapping relationship between the version of the execution code of each business service and the attribute information of the container image of each business service.

[0055] Specifically, in this embodiment, the version of the executable code for the business service can be a string that uniquely identifies a code commit or release. For example, the version may include the commit hash of the source code management system, a tag of the source code management system, or the build number of the continuous integration / continuous deployment system. This embodiment does not specifically limit the form of the version.

[0056] The attribute information of a container image for a business service is a set of data used to describe and uniquely identify a container image. For example, attribute information may include the image name, tags, and image summary. This embodiment does not specifically limit the content of the attribute information.

[0057] After building the container images for each business service, a clear mapping relationship needs to be established and recorded. This mapping relationship associates the version of the executable code of each business service with the attribute information of the container image built from that version of code.

[0058] In rail transit signaling systems, where safety and stability are paramount, version control and change tracking are crucial. When system problems arise, operations and maintenance personnel and developers need to quickly pinpoint which version of the code caused the issue. Similarly, during system upgrades or rollbacks, it is essential to ensure that the correct version of the software is deployed. Without a clear mapping, confusion can easily arise in complex environments with multiple code versions and mirror versions, leading to deployment errors or difficulties in troubleshooting.

[0059] The rapid deployment method for rail transit signaling systems provided in this application establishes a clear and reliable mapping relationship from the version of the executable code of a business service to the attribute information of the container image. When troubleshooting code issues, operations and maintenance personnel can quickly locate the specific commit version of the source code causing the problem by querying this mapping relationship based on the attribute information of the running container. This greatly improves the efficiency of fault diagnosis and repair and reduces the system's operation and maintenance costs.

[0060] In some embodiments, the method further includes: The load balancing deployment mode is determined to be a dual-active mode for service components; Based on the load balancing deployment model, determine the number of container image replicas deployed for each business service.

[0061] Specifically, load balancing deployment mode refers to the system architecture and service instance distribution strategy adopted to cope with business load and ensure service continuity. In this embodiment, the load balancing deployment mode selected is the active-active mode of service components.

[0062] The active-active mode of a service component refers to the simultaneous operation of at least two or more instances (or replicas) with identical functionality for a single business service, and these instances are all active and can receive and process external requests at any time.

[0063] In the rapid deployment of rail transit signaling systems, adopting a dual-active service component mode means that the failure of any one service instance (e.g., downtime due to software defects, hardware failures, or network problems) will not cause interruption of the service, as other active instances can immediately and seamlessly take over its work. This avoids single points of failure and ensures service continuity. Establishing this mode as the standard deployment strategy for the system, especially core business services, can guarantee the stable operation of the entire rail transit signaling system.

[0064] After deciding to adopt the active-active mode for service components, this needs to be quantified into specific deployment parameters, namely the number of container image replicas. In container orchestration technology, this number defines how many identical container instances need to be launched for each business service.

[0065] In one specific implementation, the rail transit signaling system needs to be deployed on two physical servers. The number of backend program container image copies is set to 2, the number of interface program container image copies is set to 2, the number of data acquisition service program container image copies is set to 2, the number of timed task service program container image copies is set to 2, the number of task scheduling service program container image copies is set to 2, the number of monitoring docking service program container image copies is set to 2, and the number of alarm service program container image copies is set to 2.

[0066] The rapid deployment method for rail transit signaling systems provided in this application adopts a service component active-active mode and configures at least two container image copies for each business service accordingly. This enables the deployed rail transit signaling system to have high fault tolerance, not only eliminating the risk of single point of failure in critical businesses and achieving high availability of services, but also naturally supporting load balancing and improving the overall performance and throughput of the system.

[0067] In some embodiments, based on configuration files and container images, deployment tasks are executed in the environment to be deployed to start various business services, including: Obtain container logs for each business service; The deployment process status is tracked based on container logs.

[0068] Specifically, container logs refer to all output information generated by business service processes running inside a container, typically including standard output and standard error. These logs are the most direct and detailed source of information reflecting the internal operating status of the service.

[0069] For the operational services of rail transit signaling systems, their container logs may contain startup information, operational information, error and exception information, etc.

[0070] Logs of a specific container can be obtained by directly calling the interface or command-line tools provided by the container runtime engine, or by automatically discovering and collecting logs generated by all containers on a node through a centralized log collection system.

[0071] The acquired container logs can be parsed to track the progress of deployment tasks. For example, the progress of deployment tasks can be identified by searching for specific keywords or regular expressions in the logs.

[0072] These real-time tracked process statuses can be displayed on a visual interface. Operations personnel can clearly see the startup progress of each business service and each replica. If a service fails to start, the visual interface can directly highlight the service and attach a summary of the key error logs that caused the failure, thereby enabling rapid fault location.

[0073] The rapid deployment method for rail transit signaling systems provided in this application actively acquires container logs during the deployment process and tracks the process status based on the log content, which greatly shortens the troubleshooting time, improves the success rate and reliability of deployment, and ensures that complex rail transit signaling systems can be deployed quickly and robustly.

[0074] In some embodiments, a health check is performed on each initiated service to verify that the rail transit signaling system has been successfully deployed according to the configuration file, including: Automated checks are performed on at least one of the following: version information, service availability, and environment parameters of each launched business service, and a deployment report is generated.

[0075] Specifically, version information is checked to ensure that the correct version of the business service is deployed to the environment to be deployed. This can be obtained, for example, by reading the container's metadata tags or by calling a specific interface provided by the service itself. The obtained version information is then compared with the version information specified in the deployment plan. Only if the two are completely identical is the version information check considered successful.

[0076] Service availability is checked to confirm that the service has not only started but is also able to respond to requests normally and has the capability to provide services. For example, a request can be sent to the service; if the expected successful response is received, it indicates that the service has completed initialization and is ready to receive business traffic.

[0077] The environment parameters are checked to verify that they completely match the specifications in the configuration file. For example, the management interface can be used to query the running service instance and obtain its currently effective environment parameters. Then, these actual parameters are compared item by item with the expected values ​​in the configuration file used during deployment.

[0078] After completing the above checks, a deployment report is generated. The deployment report is an automatically generated, formatted document that records the entire verification process and results.

[0079] The rapid deployment method for rail transit signaling systems provided in this application, through rigorous verification of version information, service availability, and environmental parameters, can effectively prevent deployment failures caused by version errors, configuration oversights, or service freezes, ensuring that the final delivered rail transit signaling system is a healthy and reliable system that fully meets design and configuration requirements. The automatically generated deployment report provides a formal and traceable audit record for the entire deployment activity, greatly improving the standardization and professionalism of operation and maintenance work.

[0080] Figure 2This is the second flowchart illustrating the rapid deployment method for the rail transit signaling system provided in this application, as shown below. Figure 2 As shown, this method is used to quickly deploy a rail transit signaling system on two physical machine servers.

[0081] Step 1: Node preparation: Prepare two physical servers, install the operating system, and configure the required network according to your needs.

[0082] Step 2, Media Preparation: Transfer the image file required for the program container to the storage medium and send it to a physical server.

[0083] Step 3: Template Initialization: Pull the deployment file template from the Environment Center repository, and complete the initialization of the template's network address and node distribution role configuration according to the relevant actual information in the Environment Center.

[0084] Step 4: Build the execution code: Based on the initialized template, find the code branch version number and execute the build of the corresponding version code.

[0085] Step 5: Package the code: For the built code and the version number to be deployed, download the main program package and dependent program packages, and complete the program packaging operation.

[0086] Step Six: Upload and Deploy the Program: Upload the packaged program to the project environment, along with the image file on the accompanying storage medium, to execute the version upgrade deployment task.

[0087] Step 7: Deployment process control: Track the deployment task status through container logs and view the deployment results through the logs.

[0088] Step 8: Generate Deployment Report: After the deployment task is completed, a deployment check service will be started to perform deployment checks on the deployed system, including version information checks, service availability checks, and environment parameter checks. After the checks are completed, a deployment report will be generated.

[0089] To create an image file, follow these steps: Step 1: Based on the three types of programs—front-end, middleware, and back-end—the system's code is split into atomic services.

[0090] Step 2: Create separate container images for each of the split atomic services.

[0091] Step 3: Set the number of replicas for each type of atomic service to be started using containers, so as to achieve a dual-active load balancing deployment mode for service components.

[0092] Step 4: Record the mapping relationship between the code version of each type of atomic service and the attribute information inside the image to standardize the system version management, and upload the corresponding container image to the physical machine where it needs to be deployed for system deployment.

[0093] The beneficial effects of the rapid deployment method for rail transit signaling systems provided in this application include: (1) Improved system deployment efficiency. The method provided in this application embodiment can automate the entire process from code submission to website deployment by writing scripts or using automation tools. This greatly reduces the manual operation of developers, reduces their workload, and thus improves development efficiency. Automated deployment reduces the risk of errors caused by manual operation. By automatically executing the deployment process through scripts or tools, deployment failures or system anomalies caused by human negligence or improper operation can be avoided.

[0094] (2) System stability is ensured. When a problem occurs in the system, the method provided in this application embodiment can easily achieve a rapid system rollback. Developers can restore the system to its previous state by executing the rollback script, thereby avoiding large-scale system failures. The method provided in this application embodiment can gradually introduce new functions into the online environment, and through small-scale testing and user feedback, timely discover and fix potential problems, thereby reducing the overall system risk.

[0095] (3) Reduced system operation and maintenance costs. The method provided in this application simplifies the operation and maintenance process, enabling operation and maintenance personnel to manage and maintain the system more conveniently. Through automation tools and scripts, operation and maintenance personnel can quickly complete tasks such as system deployment, updates, and monitoring. The method provided in this application can utilize server resources more efficiently. Through precise deployment and configuration management, resource waste and conflicts can be avoided, thereby improving resource utilization and system performance.

[0096] The method provided in this application embodiment, on the one hand, eliminates the need for manual configuration of parameters and management of service programs, greatly reducing the deployment cycle; on the other hand, when local code programs of the system are modified, there is no need to test and verify the remaining code programs during the deployment process, reducing the testing scope and improving the delivery efficiency of system operation and maintenance upgrade versions.

[0097] The apparatus provided in the embodiments of this application is described below. The apparatus described below can be referred to in correspondence with the method described above.

[0098] Figure 3 This is a structural schematic diagram of the rapid deployment device for the rail transit signaling system provided in this application, as shown below. Figure 3 As shown, the device includes: The splitting module 310 is used to split the code program of the rail transit signaling system into the execution code of multiple independent business services, and to build a container image containing the runtime environment and execution code for each business service. The generation module 320 is used to obtain the deployment file template and initialize the deployment file template based on the network information and node configuration information of the rail transit signaling system's deployment environment to generate a configuration file; Deployment module 330 is used to execute deployment tasks and start various business services in the environment to be deployed, based on configuration files and container images. The inspection module 340 is used to perform health status checks on each started business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

[0099] The rapid deployment device for rail transit signaling systems provided in this application separates the system's code into the execution code of multiple independent business services. For each service, a container image containing the runtime environment and execution code is built, achieving separation of the runtime environment and service applications. By initializing the deployment file template based on the network information and node configuration information of the rail transit signaling system's deployment environment, a configuration file is generated, resolving the configuration complexity issue caused by differences in runtime environments. Using the configuration file and container image, deployment tasks are executed in the deployment environment, starting each business service and performing health checks on the started services, ensuring a fast, reliable, and verifiable deployment process. This significantly improves the deployment efficiency of rail transit signaling systems, reduces the risk of human error, and lowers system operation and maintenance costs.

[0100] Figure 4 This is a schematic diagram of the structure of the electronic device provided in this application, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communications bus 440, wherein the processor, communications interface, and memory communicate with each other via the communications bus. The processor can invoke logical commands stored in the memory to execute the methods described in the above embodiments, for example: The code program of the rail transit signaling system is split into the execution code of multiple independent business services. A container image containing the runtime environment and execution code is built for each business service. A deployment file template is obtained, and the deployment file template is initialized based on the network information and node configuration information of the rail transit signaling system's deployment environment to generate a configuration file. Based on the configuration file and container image, the deployment task is executed in the deployment environment to start each business service. A health status check is performed on each started business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

[0101] Furthermore, the logical commands in the aforementioned memory can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several commands to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0102] The processor in the electronic device provided in this application embodiment can call logical instructions in the memory to implement the above method. Its specific implementation method is the same as the aforementioned method implementation method and can achieve the same beneficial effect, which will not be repeated here.

[0103] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the methods provided in the above embodiments.

[0104] The specific implementation method is the same as the aforementioned method implementation method and can achieve the same beneficial effects, so it will not be repeated here.

[0105] This application provides a computer program product, including a computer program that, when executed by a processor, implements the method described above.

[0106] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0107] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0108] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for rapid deployment of a rail transit signaling system, characterized in that, include: The code program of the rail transit signaling system is split into the execution code of multiple independent business services, and a container image containing the runtime environment and execution code is built for each business service. Obtain the deployment file template, and initialize the deployment file template based on the network information and node configuration information of the environment to be deployed in the rail transit signaling system, and generate a configuration file; Based on the configuration file and the container image, the deployment task is executed in the environment to be deployed, and various business services are started. Perform a health status check on each activated business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

2. The rapid deployment method for a rail transit signaling system according to claim 1, characterized in that, The process of splitting the code program of the rail transit signaling system into the execution code of multiple independent business services, and building a container image containing the runtime environment and execution code for each business service, includes: Based on the type of the code program of the rail transit signaling system, the code program is atomically decomposed to obtain the execution code of each decomposed business service. Determine the operating environment that is compatible with the code program of the rail transit signaling system, and start the basic container in the operating environment; The execution code of each business service is deployed and started within the basic container, and the program files and configurations inside the basic container are standardized. The standardized base container is then solidified into container images for each business service.

3. The rapid deployment method for a rail transit signaling system according to claim 2, characterized in that, The method further includes: Record the mapping relationship between the version of the execution code of each business service and the attribute information of the container image of each business service.

4. The rapid deployment method for a rail transit signaling system according to claim 2, characterized in that, The code programs of the rail transit signaling system include front-end programs, middleware programs, and back-end programs. The front-end program includes a front-end web page program; The middleware program includes a database service program and / or a message queue service program; The backend program includes at least one of the following: an interface program, a data collection service program, a scheduled task service program, a task scheduling service program, a monitoring and control integration service program, and an alarm service program.

5. The rapid deployment method for a rail transit signaling system according to claim 1, characterized in that, The method further includes: The load balancing deployment mode is determined to be a dual-active mode for service components; Based on the load deployment mode, determine the number of container image replicas deployed for each business service.

6. The rapid deployment method for a rail transit signaling system according to claim 1, characterized in that, Based on the configuration file and the container image, the deployment task is executed in the environment to be deployed, and various business services are started, including: Obtain container logs for each business service; The deployment task's process status is tracked based on the container logs.

7. The rapid deployment method for a rail transit signaling system according to claim 1, characterized in that, The health status check of each initiated service to verify that the rail transit signaling system has been successfully deployed according to the configuration file includes: Automated checks are performed on at least one of the following: version information, service availability, and environment parameters of each launched business service, and a deployment report is generated.

8. A rapid deployment device for a rail transit signaling system, characterized in that, include: The split module is used to split the code program of the rail transit signaling system into the execution code of multiple independent business services, and build a container image containing the runtime environment and execution code for each business service. The generation module is used to obtain the deployment file template and initialize the deployment file template based on the network information and node configuration information of the environment to be deployed of the rail transit signaling system, and generate a configuration file. The deployment module is used to execute deployment tasks and start various business services in the environment to be deployed based on the configuration file and the container image. The inspection module is used to perform health status checks on each started business service to verify that the rail transit signaling system has been successfully deployed according to the configuration file.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the rapid deployment method of the rail transit signaling system according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the rapid deployment method of the rail transit signaling system according to any one of claims 1 to 7.

Images