Integrated architecture and implementation method of automated terminal production command and control system

Abstract

The present invention discloses an integrated architecture and implementation method of an automated terminal production command and control system, including a terminal production system, an equipment control system, a data conversion system, an information management system, and a client; the terminal production system and the data conversion system both adopt a distributed architecture; the terminal production system includes a first command distribution service, a first load balancing service, and multiple first functional services; the data conversion system includes a second command distribution service, a second load balancing service, and a second functional service; the load balancing service is respectively connected to the client, the command distribution service, and each functional service for communication, receiving the service request of the client, the microservice list formed by each functional service registered on the command distribution service, and issuing service requests to each functional service according to the classification of the service request and the microservice list. The present invention improves the isolation between each microservice, improves the stability, reliability, and scalability of the system, shortens the fault location time, and improves the troubleshooting efficiency.

Description

Technical Field

[0001] The present invention belongs to the technical field of terminal freight systems, and specifically, relates to an integrated architecture and implementation method of an automated terminal production command and control system. Background Art

[0002] In the terminal operation systems currently popular around the world, the division of labor for various services is very clear, and after the service allocation is completed, it is impossible to elastically scale a single service, which means that once a small fluctuation occurs in the system, the entire system may be paralyzed, and it is difficult to locate the problem during maintenance, and the maintenance efficiency is low, which seriously affects the operating efficiency of the terminal. Summary of the invention

[0003] The present invention provides an integrated architecture and implementation method of an automated terminal production command and control system, which configures the terminal production command and control system as a distributed microservice system to improve maintenance efficiency and, in addition, improve the scalability and scalability of the system.

[0004] In order to solve the above technical problems, the present invention adopts the following technical solutions to achieve the above problems:

[0005] An integrated architecture of an automated terminal production command and control system, including a terminal production system, an equipment control system, a data conversion system, an information management system, and a client, which are respectively used for terminal production operation calculation, terminal production operation equipment control, data conversion between systems, terminal operation data collection and log analysis, and service request generation;

[0006] The terminal production system and the data conversion system both adopt a distributed architecture;

[0007] The terminal production system includes a first command distribution service, a first load balancing service, and a plurality of first functional services; the first load balancing service is respectively connected to the client, the first command distribution service, and each of the first functional services in communication, receives the service request of the client, receives a first microservice list formed by each of the first functional services being registered on the first command distribution service, and distributes the service request and traffic to each of the first functional services according to the received first microservice list;

[0008] The data conversion system includes a second command distribution service, a second load balancing service, and a second functional service; the second load balancing service is respectively communicated with the first load balancing service, the information management system, the second command distribution service, and the second functional service, receives the service requests of the first load balancing service and the information management system, receives the second microservice list formed by the second functional service registering on the second command distribution service, and allocates the service request and traffic to the second functional service according to the received second microservice list.

[0009] In one embodiment, the first command distribution service and the second command distribution service are collectively referred to as a command distribution service; the first load balancing service and the second load balancing service are collectively referred to as a load balancing service;

[0010] The load balancing service is respectively communicated with the client, the command distribution service, each of the first function services, and the second function service, receives the service request of the client, receives a microservice list formed by the first function service and the second function service registered on the command distribution service, and distributes the service request and traffic to each of the first function service and the second function service according to the received microservice list.

[0011] In one embodiment, each of the first functional services is a static computing service, a dynamic computing service, and a data flow service; the static computing service, the dynamic computing service, and the data flow service respectively include a plurality of microservices with different functions, which are used to process the specific service request;

[0012] The data conversion service includes multiple microservices with different functions, which are used to process specific service requests.

[0013] In one embodiment, the information management system, the command distribution service, the load balancing service, the data conversion service, and each of the microservices of the static computing service, each of the microservices of the dynamic computing service, and each of the microservices of the data flow service are respectively provided with multiple nodes, forming an information management system service cluster, a command distribution service cluster, a load balancing service cluster, each of the microservice clusters of the data conversion service, and each of the microservice clusters of the static computing service, each of the microservice clusters of the dynamic computing service, and each of the microservice clusters of the data flow service, and each microservice node runs on a separate virtual machine through a container.

[0014] In one embodiment, each of the virtual machines is configured on a plurality of physical machines that are configured in a pool.

[0015] An integrated implementation method of an automated terminal production command and control system includes building a terminal production command and control system with a distributed microservice architecture;

[0016] The terminal production command and control system includes a terminal production system, an equipment control system, a data conversion system, an information management system, and a client, and the terminal production system and the data conversion system are configured as a distributed architecture;

[0017] The terminal production system includes a first command distribution service, a first load balancing service, and multiple first functional services; each of the first functional services is a static computing service, a dynamic computing service, and a data flow service; the data conversion system includes a second command distribution service, a second load balancing service, and a second functional service; the second functional service is a data conversion service; the static computing service, the dynamic computing service, the data flow service, and the data conversion service each include multiple microservices.

[0018] In one embodiment, the first command distribution service, the first load balancing service, the microservices of the static computing service, the microservices of the dynamic computing service, the microservices of the data flow service, the second command distribution service, the second load balancing service, and the microservices of the data conversion service are respectively provided with multiple nodes, and are respectively run on separate virtual machines in the form of containers; the containers running the same microservices form clusters, namely the first command distribution service cluster, the first load balancing service cluster, the microservice clusters of the static computing service, the microservice clusters of the dynamic computing service, the microservice clusters of the data flow service, the second command distribution service cluster, the second load balancing service cluster, and the microservice clusters of the data conversion service.

[0019] In one embodiment, the first command distribution service cluster and the second command distribution service cluster are collectively referred to as a command distribution service cluster; the first load balancing service cluster and the second load balancing service cluster are collectively referred to as a load balancing service cluster; the microservice clusters of the first functional services and the microservice clusters of the second functional services are collectively referred to as functional service clusters;

[0020] The following workflows are also included:

[0021] S21 each of the functional service clusters registers its own service function and identification to the command distribution service cluster;

[0022] S22: the command distribution service cluster generates a microservice cluster list for each registered functional service cluster, stores it locally, and sends it to the load balancing service cluster;

[0023] S23: the load balancing service cluster distributes the received service request to the specific node of the microservice according to the microservice cluster list;

[0024] After the service request processing is completed in S24, the microservice node feeds back the result to the load balancing service cluster; the load balancing service cluster then processes the next service request according to the fed-back result.

[0025] In one embodiment, it further includes:

[0026] Each node of the command distribution service cluster is in a master-slave relationship, and each node stores a list of the microservice cluster; when a single node of the command distribution service cluster fails, one of the other nodes takes over the task of the failed node;

[0027] The nodes of the load balancing service cluster serve as the primary and backup nodes for each other; when a single node of the load balancing service cluster fails, the remaining nodes will take over the distribution and flow distribution of the service requests that the failed node is responsible for.

[0028] In one embodiment, the nodes of each functional service cluster are in a master-slave relationship; when one or more nodes fail, they will detect their own status and self-start; if the startup fails, the command distribution service cluster will remove the failed node from the microservice cluster list; within the specified time, the failed node will continue to restart and try to re-add itself to the microservice cluster list; the command distribution service cluster will report the address of the failed node and request manual maintenance.

[0029] Compared with the prior art, the advantages and positive effects of the present invention are as follows: the integrated architecture of the automated terminal production command and control system and the integrated implementation method of the automated terminal production command and control system of the present invention configure the terminal production command and control system as a terminal production system, an equipment control system, a data conversion system, an information management system, and a client, and configure the terminal production system and the data conversion system as a distributed microservice architecture, so that the functional services of the terminal production system and the data conversion system are configured as modules of multiple microservices, thereby improving the isolation between the microservices, thereby improving the isolation between the microservices during operation, improving the stability and reliability of the system, and improving the efficiency of fault location during failure, and improving the maintenance efficiency; furthermore, configuring the terminal production system and the data conversion system as distributed microservices facilitates the expansion and scalability of the system, thereby improving scalability. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0031] Figure 1 It is a schematic diagram of the composition and energy supply connection of an embodiment of an integrated architecture of an automated terminal production command and control system proposed by the present invention.

[0032] In the figure,

[0033] 1. Terminal production system; 2. Data conversion system; 3. Equipment control system; 4. Information management system; 5. Client; 11. First command distribution service; 12. First load balancing service; 13. Static computing service; 14. Dynamic computing service; 15. Data flow service; 21. Second command distribution service; 22. Second load balancing service; 23. Data conversion service; 31. Quay crane control; 32. AGV control; 33. Field crane control; 34. Interface database. DETAILED DESCRIPTION

[0034] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0035] Reference Figure 1 The integrated architecture of the automated terminal production command and control system of the present invention includes a terminal production system 1, an equipment control system 3, a data conversion system 2, an information management system 4, and a client 5, which are respectively used for terminal production operation calculation, terminal operation equipment control, data conversion between systems, terminal operation data collection and log analysis, and generating primary service requests.

[0036] The terminal production system 1 and the data conversion system 2 both adopt a distributed architecture. In addition, the terminal production system 1 and the data conversion system 2 both realize their system functions by setting up multiple microservices.

[0037] The terminal production system 1 includes a first command distribution service 11, a first load balancing service 12, and a plurality of first functional services; the data conversion system 2 includes a second command distribution service 21, a second load balancing service 22, and a second functional service.

[0038] The first load balancing service 12 is respectively communicated with the client 5, the first command distribution service 11, and each first functional service, receives the primary service request of the client 5, receives the first microservice list formed by the registration of each first functional service on the first command distribution service 11, and allocates the primary service request and traffic to each first functional service according to the received first microservice list.

[0039] The second load balancing service 22 is respectively communicated with the first load balancing service 12, the information management system 4, the second command distribution service 21, and the second functional service, receives secondary service requests from the first load balancing service 12 and the information management system 4, receives the second microservice list formed by the second functional service registered on the second command distribution service 21, and allocates secondary service requests and traffic to the second functional service according to the received second microservice list.

[0040] The integrated architecture of the automated terminal production command and control system of the present invention sets the terminal production command and control system as a terminal production system 1, an equipment control system 3, a data conversion system 2, an information management system 4, and a client 5, and sets the terminal production system 1 and the data conversion system 2 as a distributed microservice architecture, so that the functional services of the terminal production system 1 and the data conversion system 2 are set as modules of multiple microservices, thereby improving the isolation between the microservices, and then improving the isolation between the microservices at run time, improving the stability and reliability of the system, and improving the efficiency of fault location during failure, and improving the maintenance efficiency; furthermore, setting the terminal production system 1 and the data conversion system 2 as distributed microservices facilitates the expansion and scalability of the system, and improves scalability.

[0041] Preferably, the connection between the second load balancing service 22 and the first load balancing service 12 and the information management system 4 is achieved through an API.

[0042] In one embodiment, referring to Figure 1 The equipment control system includes quay crane control 31, AGV control 32, field crane control 33, and interface database 34.

[0043] The data conversion system 2 is a service for barrier-free information interaction between systems. It can not only realize format conversion between common serialization formats such as JSON, TOML, thrift, etc., but also has good compatibility with the long-standing XML and the relatively new YAML, and can realize barrier-free conversion of data between different systems. At the same time; the system can also parse data in excel, txt and other files to form XML, JSON and other formats that can be read by the system; in terms of communication, it supports synchronous and asynchronous dual transmission modes to improve the efficiency of data exchange between systems.

[0044] The information transmission between the data flow service 15 and the device control system 3 is implemented in the form of an interface database 34; the two systems are connected to the same interface database 34, and the two systems read and write data in the interface database 34 respectively. The two systems realize data interaction by means of data monitoring, and the process is as follows: System A writes data, and at the same time carries a status code of whether the data is read or not (only system A can recognize it). When the monitoring program of system B finds that there is unread data in the interface database 34, it goes to the interface database 34 to read the data written by system A, and at the same time changes the status code to (yes); after system B processes the data of system A, system B writes the processed data to the interface database 34, and writes the status code to no (only system B can recognize it). After system A monitors the status code, it goes to the interface database 34 to read the corresponding data.

[0045] In one embodiment, referring to Figure 1 The first command distribution service 11 and the second command distribution service 21 can be used as a command distribution service; the first load balancing service 12 and the second load balancing service 22 can be used as a load balancing service. That is, the terminal production system 1 and the data conversion system 2 share the command distribution service and the load balancing service.

[0046] The first functional services are respectively static computing services 13, dynamic computing services 14, and data flow services 15; and the first functional services static computing services 13, dynamic computing services 14, and data flow services 15 respectively include a plurality of microservices with different functions for processing specific tasks. The second functional service is a data conversion service 23.

[0047] The command distribution service is used to register each first function service, second function service and monitor the running status of each of the above microservices to generate a microservice list and send it to the load balancing service; the load balancing service connects the command distribution service and each microservice respectively, and distributes the primary service request sent by the client 5 and the secondary service request between systems to each microservice according to the microservice list and performs traffic sharing.

[0048] For example, the static computing service 13 is used to calculate the target position of the container; the dynamic computing service 14 commands the equipment to grab and transport the container to the target position; the data flow service 15 transmits data during the calculation and grabbing and transportation process, thereby realizing the combination of the dynamic computing service 14 and the static computing service 13.

[0049] Furthermore, the static computing service 13 includes microservices such as intelligent budget position, intelligent calculation position, interactive area calculation position, and abnormal box calculation position; the dynamic computing service 14 includes microservices such as AGV scheduling, AGV dispatch, ASC scheduling, ASC dispatch, core core processing service, and RF cold box instruction calculation service; the data flow service 15 includes microservices such as workflow service, data communication service, front-end service, message transmission service, TMS data interaction service, OCR data interaction service, and gate interaction service.

[0050] In one embodiment, in order to ensure high availability and high reliability, the above-mentioned information management system service, command distribution service, load balancing service, data conversion service 23, and each microservice of the static computing service 13, each microservice of the dynamic computing service 14, and each microservice of the data flow service 15 are all set up in a cluster manner.

[0051] This embodiment implements the distributed microservice cluster architecture setting of the terminal production system 1 and the data conversion system 2 of the integrated architecture of the automated terminal production command and control system.

[0052] In one embodiment, the integrated architecture of the automated terminal production command and control system is set on multiple physical machines; each physical machine has basic hardware for computing, storage, and transmission functions. The resources of each physical machine are pooled to maximize the utilization of the resources of the physical machine.

[0053] On the basis of the pooled physical machine hardware, multiple virtual machines with different environments are set up, and the information management system microservice cluster, the command distribution service cluster, the load balancing service cluster, the microservice clusters of the static computing service 13, the microservice clusters of the dynamic computing service 14, the microservice clusters of the data flow service 15, and the microservice clusters of the data conversion service 23 are respectively run on each virtual machine in the form of containers; the information management system microservice cluster, the command distribution service cluster, the load balancing service cluster, the microservice clusters of the static computing service 13, the microservice clusters of the dynamic computing service 14, the microservice clusters of the data flow service 15, and the microservice clusters of the data conversion service 23 are respectively run on each virtual machine in the form of containers; The microservice clusters of 5 and the microservice clusters of data conversion service 23 are isolated by running on different virtual machines through the setting of virtual machines, thereby improving the independence of each microservice and improving the reliability and scalability of operation; in addition, the information management system microservice cluster, the command distribution service cluster, the load balancing service cluster, the microservice clusters of static computing service 13, the microservice clusters of dynamic computing service 14, the microservice clusters of data flow service 15, and the microservice clusters of data conversion service 23 are further isolated through the containers in which they are located, thereby further improving the independence of the operation of each microservice and improving the reliability of operation.

[0054] By using virtualization technology to pool the resources of each physical machine, and according to the needs of different microservices, allocate the minimum resources, build virtual machines, and fully tap the performance of physical machines while isolating each virtual machine, it is the basis for realizing the microservice cluster deployment of the terminal production command and control system. At the same time, by applying the virtual machine migration strategy, when a single physical machine goes down, other physical machines will receive the virtual machines of the lost physical machine, improving the disaster recovery capability of the terminal production command and control system.

[0055] This embodiment implements a high-availability system architecture based on a distributed microservice cluster. By using the dual-engine technology of "virtualization plus container", it not only solves the requirements of different operating systems for different applications, but also realizes the dual separation of each microservice, thereby improving the overall scalability of the system and the reliability of operation. The deployment method of the microservice cluster makes the expansion of the integrated architecture service of the automated terminal production command and control system more flexible and the system disaster recovery capability stronger.

[0056] In one embodiment, due to the different operating environments and separation requirements of the information management system microservice cluster, the command distribution service cluster, the load balancing service cluster, each microservice cluster of the static computing service 13, each microservice cluster of the dynamic computing service 14, each microservice cluster of the data flow service 15, and each microservice cluster of the data conversion service 23, the information management system microservice cluster, the command distribution service cluster, the load balancing service cluster, each microservice cluster of the static computing service 13, each microservice cluster of the dynamic computing service 14, each microservice cluster of the data flow service 15, and each microservice cluster of the data conversion service 23 correspond to separate virtual machines. That is, each microservice runs on a separate virtual machine through a container.

[0057] This embodiment achieves complete isolation of each microservice, enhances separation effect, and improves scalability and operational reliability.

[0058] In a specific embodiment, the command distribution service cluster is configured with 3 to 5 nodes, which are in a master-slave relationship; each node stores a microservice cluster list; when a single node in the command distribution service cluster fails, one of the other nodes will take over the tasks of registering and discovering each microservice, detecting the health of the microservice, and sending the microservice cluster list.

[0059] The load balancing service cluster is configured with 2-3 nodes, which are configured as master and backup nodes. When a single node in the load balancing service cluster fails, the remaining nodes will take over the distribution of service requests and traffic balancing work that the failed node is responsible for. The above service request is sent by the client 5.

[0060] Each microservice cluster of the static computing service 13, each microservice cluster of the dynamic computing service 14, each microservice cluster of the data flow service 15, and each microservice cluster of the data conversion service 23 includes 3-10 nodes respectively; when a single node of each microservice cluster of the static computing service 13, each microservice cluster of the dynamic computing service 14, each microservice cluster of the data flow service 15, and each microservice cluster of the data conversion service 23 fails, it will detect its own status and start automatically; if the startup fails, the command distribution service cluster will remove the failed node from the microservice cluster list because it has not received the health report information of the relevant node within a certain period of time; and within the specified time, the failed node will continue to restart and try to send registration information to the command distribution service cluster to re-add itself to the microservice cluster list. At this time, the command distribution service cluster will report the failed node and request manual maintenance.

[0061] The nodes are virtual machines running container microservices.

[0062] The command distribution service cluster is used to receive registrations from each microservice cluster and monitor the health of each microservice cluster; the load balancing service cluster is used to connect the command distribution service cluster with the data conversion service 23 cluster, the static computing service 13 cluster, the dynamic computing service 14 cluster, the data flow service 15 cluster, and the client 5, receive primary service requests from the client 5 and secondary service requests between systems, and distribute the received service requests to the above-mentioned microservices according to classification and traffic.

[0063] The microservice clusters of the data conversion service 23, the static computing service 13 cluster, the dynamic computing service 14 cluster, and the data flow service 15 cluster are divided into active and standby clusters and common service clusters. The active and standby clusters are for services with small computing volume, and use the active and standby method to make the system more robust; the common service cluster is an active and standby integrated cluster that is mutually active and standby. From the inside, it is composed of multiple nodes, and each node is responsible for completing different tasks; from the outside, it is a service; and when a node fails, other nodes will take over the tasks of the failed node to complete the service; this method is for services with large computing volume; at the same time, the single node inside it also exists in the form of active and standby.

[0064] The integrated implementation method of the automated terminal production command and control system of the present invention includes dividing the terminal production command and control system into a terminal production system 1, an equipment control system 3, a data conversion system 2, and an information management system 4, and setting the terminal production system 1 and the data conversion system 2 as a distributed microservice architecture.

[0065] The terminal production system 1 is provided with a first command distribution service 11, a first load balancing service 12, and multiple first functional services; the first functional services are respectively a static computing service 13, a dynamic computing service 14, and a data flow service 15; the data conversion system 2 is provided with a second command distribution service 21, a second load balancing service 22, and a second functional service; the second functional service is a data conversion service 23.

[0066] Each microservice includes multiple nodes. Each microservice runs on a separate virtual machine in the form of a container. Virtual machines running the same microservice form a cluster, and the nodes in each cluster are set to be a master-slave relationship or a common service relationship. The microservice clusters of the static computing service 13 cluster, the dynamic computing service 14 cluster, the data flow service 15 cluster, and the data conversion service 23 are functional service clusters.

[0067] The integrated implementation method of the automated terminal production command and control system of the present invention sets the terminal production command and control system as a terminal production system 1, an equipment control system 3, a data conversion system 2, and an information management system 4, and sets the terminal production system 1 and the data conversion system 2 as a distributed microservice architecture, so that the functional services of the terminal production system 1 and the data conversion system 2 are set as modules of multiple microservices, thereby improving the isolation between the microservices, and then improving the isolation between the microservices at run time, improving the stability and reliability of the system, and improving the fault location efficiency during failure, and improving the maintenance efficiency; furthermore, setting the terminal production system 1 and the data conversion system 2 as distributed microservices facilitates the expansion and scalability of the system, and improves scalability.

[0068] The integrated implementation method of the automated terminal production command and control system of the present invention also includes executing the following steps when the system is running.

[0069] S21 Each functional service cluster registers its own service function and identification to the command distribution service cluster;

[0070] S22 commands the distribution service cluster to generate a microservice cluster list for each registered functional service, store it locally, and send it to the load balancing service cluster.

[0071] Specifically, the command distribution service cluster sets up multiple nodes, one of which is set as the leader node. The node will analyze the log entries during the operation of the command distribution service cluster; the log entries store the time when each microservice node in the functional service cluster sends its own operating status to the command distribution service cluster, and generate a list of microservice clusters, and copy its log entries to the follower; the log entries store the operating status of all nodes including the command distribution service cluster and each functional service cluster; in addition, the command distribution service cluster will also periodically poll to detect whether each functional service cluster is registered online, and update the log entries, while achieving the purpose of health detection of each functional service cluster.

[0072] S23 The load balancing service cluster classifies the primary service request of the client 5 and the secondary service request between systems, and distributes each service request to a specific microservice node for processing with reference to the microservice cluster list of the command distribution service cluster.

[0073] Specifically, the load balancing service cluster adopts a 4-layer and 7-layer hybrid service method to forward service requests. For the active-standby microservice clusters in each functional service cluster, a 4-layer load balancing method is adopted to directly forward service requests and traffic based on IP and port. For the common service microservice clusters in each functional service cluster, a 7-layer load balancing method is adopted to determine whether to use "IP+port" or domain name, URL to forward range requests and traffic based on the request content of the service request.

[0074] After the S24 service request is processed, the result is fed back to the load balancing service cluster, and then the next service request is processed based on the feedback result.

[0075] The integrated implementation method of the automated terminal production command and control system of the present invention also includes realizing high availability of the terminal production command and control system, which specifically includes the following contents.

[0076] The S31 command distribution service cluster consists of 3 to 5 nodes, each of which stores a list of microservice clusters. When a single node of the command distribution service cluster fails, other nodes in the cluster take over the tasks of registering and discovering the microservice cluster, checking the health of microservices, and sending the microservice list.

[0077] The S32 load balancing service cluster consists of 2-3 nodes, and each node is in the form of master and backup for each other; when a single node of the load balancing service cluster fails, the remaining nodes will take over the distribution of service requests and traffic distribution that the failed node is responsible for.

[0078] The S33 functional service cluster consists of multiple microservice clusters, and a single microservice cluster includes 3-10 nodes. When a single node in a microservice cluster fails, it will detect its own status and restart itself. If the startup fails, the command distribution service cluster will remove the failed node from the microservice cluster list. Within the specified time, the failed node will continue to restart and try to re-add itself to the microservice cluster list. The command distribution service cluster reports the address of the failed node and recommends manual maintenance.

[0079] In the description of the present invention, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0080] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0081] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. An integrated architecture of an automated terminal production command and control system, characterized in that: It includes the terminal production system, equipment control system, data conversion system, information management system, and client, which are used for terminal production operation calculation, terminal production operation equipment control, data conversion between systems, terminal operation data collection and log analysis, and service request generation; The terminal production system and the data conversion system both adopt a distributed architecture; The terminal production system includes a first command distribution service, a first load balancing service, and a plurality of first functional services; the first load balancing service is respectively connected to the client, the first command distribution service, and each of the first functional services in communication, receives the service request of the client, receives a first microservice list formed by each of the first functional services being registered on the first command distribution service, and distributes the service request and traffic to each of the first functional services according to the received first microservice list; The data conversion system includes a second command distribution service, a second load balancing service, and a second functional service; the second load balancing service is respectively communicated with the first load balancing service, the information management system, the second command distribution service, and the second functional service, receives the service requests of the first load balancing service and the information management system, receives the second microservice list formed by the second functional service registering on the second command distribution service, and allocates the service request and traffic to the second functional service according to the received second microservice list.

2. The integrated architecture of the automated terminal production command and control system according to claim 1 is characterized in that: The first command distribution service and the second command distribution service are collectively referred to as a command distribution service; the first load balancing service and the second load balancing service are collectively referred to as a load balancing service; The load balancing service is respectively communicated with the client, the command distribution service, each of the first function services, and the second function service, receives the service request of the client, receives a microservice list formed by the first function service and the second function service registered on the command distribution service, and distributes the service request and traffic to each of the first function service and the second function service according to the received microservice list.

3. The integrated architecture of the automated terminal production command and control system according to claim 2 is characterized in that: Each of the first functional services is a static computing service, a dynamic computing service, and a data flow service; the static computing service, the dynamic computing service, and the data flow service respectively include a plurality of microservices with different functions, which are used to process specific service requests; The second functional service is a data conversion service; the data conversion service includes multiple microservices with different functions, which are used to process the specific service request.

4. The integrated architecture of the automated terminal production command and control system according to claim 3 is characterized in that: The information management system, the command distribution service, the load balancing service, the data conversion service, and each of the microservices of the static computing service, each of the microservices of the dynamic computing service, and each of the microservices of the data flow service are respectively provided with multiple nodes, forming an information management system service cluster, a command distribution service cluster, a load balancing service cluster, each of the microservice clusters of the data conversion service, and each of the microservice clusters of the static computing service, each of the microservice clusters of the dynamic computing service, and each of the microservice clusters of the data flow service, and each microservice node runs on a separate virtual machine through a container.

5. The integrated architecture of the automated terminal production command and control system according to claim 4 is characterized in that: Each of the virtual machines is set on a plurality of physical machines that are pooled.

6. A method for realizing the integration of an automated terminal production command and control system, characterized in that: Including building a terminal production command and control system with a distributed microservice architecture; The terminal production command and control system includes a terminal production system, an equipment control system, a data conversion system, an information management system, and a client, and the terminal production system and the data conversion system are configured as a distributed architecture; The terminal production system includes a first command distribution service, a first load balancing service, and multiple first functional services; each of the first functional services is a static computing service, a dynamic computing service, and a data flow service; the data conversion system includes a second command distribution service, a second load balancing service, and a second functional service; the second functional service is a data conversion service; the static computing service, the dynamic computing service, the data flow service, and the data conversion service each include multiple microservices.

7. The integrated implementation method of the automated terminal production command and control system according to claim 6 is characterized in that: The first command distribution service, the first load balancing service, the microservices of the static computing service, the microservices of the dynamic computing service, the microservices of the data flow service, the second command distribution service, the second load balancing service, and the microservices of the data conversion service are respectively provided with a plurality of nodes, and are respectively run on separate virtual machines in the form of containers; The containers running the same microservices form clusters, which are respectively a first command distribution service cluster, a first load balancing service cluster, microservice clusters of the static computing service, microservice clusters of the dynamic computing service, microservice clusters of the data flow service, a second command distribution service cluster, a second load balancing service cluster, and microservice clusters of the data conversion service.

8. The integrated implementation method of the automated terminal production command and control system according to claim 7 is characterized in that: The first command distribution service cluster and the second command distribution service cluster are collectively referred to as a command distribution service cluster; the first load balancing service cluster and the second load balancing service cluster are collectively referred to as a load balancing service cluster; The microservice clusters of the first functional services and the microservice clusters of the second functional services are collectively referred to as functional service clusters; The following workflows are also included: S21 each of the functional service clusters registers its own service function and identification to the command distribution service cluster; S22: the command distribution service cluster generates a microservice cluster list for each registered functional service cluster, stores it locally, and sends it to the load balancing service cluster; S23: the load balancing service cluster distributes the received service request to the specific node of the microservice according to the microservice cluster list; S24 After the service request is processed, the microservice node feeds back the result to the load balancing service cluster; The load balancing service cluster then processes the next service request according to the feedback result.

9. The integrated implementation method of the automated terminal production command and control system according to claim 8 is characterized in that: Also includes: Each node of the command distribution service cluster is in a master-slave relationship, and each node stores a list of the microservice cluster; When a single node of the command distribution service cluster fails, one of the other nodes takes over the task of the failed node; The nodes of the load balancing service cluster are mutually active and standby; When a single node of the load balancing service cluster fails, the remaining nodes will take over the distribution and traffic allocation of the service requests that the failed node was responsible for.

10. The integrated implementation method of the automated terminal production command and control system according to claim 8, characterized in that: The nodes of each functional service cluster are in a master-slave relationship; when one or more nodes fail, they will detect their own status and self-start; if the startup fails, the command distribution service cluster will remove the failed node from the microservice cluster list; within the specified time, the failed node will continue to restart and try to re-add itself to the microservice cluster list; the command distribution service cluster will report the address of the failed node and request manual maintenance.

Images