Container terminal management and control cloud platform and container terminal management and control system

Abstract

The invention relates to the technical field of port logistics information, and provides a container terminal management and control cloud platform and a container terminal management and control system. The platform comprises an access layer, an application layer and a platform service layer, the access layer is configured to be in communication connection with a plurality of user sides and a plurality of execution sides and is used for acquiring operation data transmitted by each user side and operation data transmitted by each execution side, and the application layer comprises at least one service unit and is used for transmitting operation data transmitted by each execution side. Each service unit outputs a control instruction based on the job data and the operation data, and the platform service layer is used for storing the control instruction in a message queue, so that an execution end obtains the control instruction from the message queue and executes an operation corresponding to the control instruction. The cloud platform flexibly replaces a local machine room, hardware and operation and maintenance are avoided, expansion and contraction are carried out according to needs, and the comprehensive cost is suddenly reduced. The three-layer architecture and the message queue get through a multi-port data island, instructions are reliably and orderly issued, operation conflicts return to zero, and the response is millisecond.

Description

Container terminal management cloud platform, and container terminal management system Technical Field

[0001] This application relates to the field of port logistics information technology, and in particular to a container terminal management cloud platform and a container terminal management system. Background Technology

[0002] As a core hub of the global supply chain, the operational efficiency of container terminals directly impacts the speed of international trade. The terminal operating system (TOS), as the core software coordinating the entire process of terminal operations including loading, unloading, storage, and transportation, is a key technological support for ensuring the efficient operation of the terminal.

[0003] Currently, traditional container terminal operating systems generally adopt a localized deployment model, which involves purchasing dedicated servers, storage devices, and other hardware resources locally at the terminal, building an independent data center, and completing the software installation and configuration. This deployment model has gradually revealed many insurmountable technical shortcomings in long-term application:

[0004] First, hardware procurement and data center construction costs are high, and the deployment cycle is lengthy. Localized deployment requires ports to invest heavily in purchasing high-performance servers, redundant storage devices, and supporting data center cooling and power supply systems, with hardware procurement costs accounting for a very high proportion. At the same time, the processes of data center construction, equipment debugging, software installation, and system adaptation are cumbersome, resulting in the entire deployment cycle typically lasting several months, making it impossible to quickly respond to the port's business launch needs.

[0005] Secondly, there is a lack of unified management and data collaboration capabilities for multiple terminals and ports. Traditional TOS systems are mostly custom-developed for single terminals, with each terminal's system operating independently and data storage scattered, forming information silos. For large enterprises with multiple terminals, this results in low management efficiency and difficulties in optimizing resource allocation.

[0006] Third, the operation and maintenance process is complex, requiring frequent manual intervention and resulting in low overall efficiency. Locally deployed TOS requires a dedicated operation and maintenance team responsible for hardware maintenance, software updates, and troubleshooting, which not only increases labor costs but also increases the risk of operational errors due to manual intervention. Furthermore, system fault response and problem repair rely on on-site handling, making remote rapid location and resolution impossible, further impacting the continuity of port operations.

[0007] In recent years, with the rapid development of cloud computing technology, cloud-based deployment models have been widely adopted across various industries due to their advantages such as elastic scaling, resource sharing, and remote operation and maintenance. Simultaneously, the deepening of the domestic IT innovation strategy requires key industry software to achieve domestic adaptation and independent control. Against this backdrop, traditional locally deployed TOS (Terminal Operating System) can no longer meet the terminal industry's demands for low-cost, highly collaborative, highly secure, and intelligent operations. There is an urgent need for a container terminal operating system that supports cloud deployment, group-based management, intelligent operation and maintenance, and flexible billing to address the many shortcomings of existing technologies and drive the digital and intelligent transformation of the container terminal industry. Summary of the Invention

[0008] In view of this, this application provides a container terminal management and control cloud platform and a container terminal management and control system, which can solve the problems of high hardware and computer room costs, long deployment cycle, lack of multi-terminal data collaboration and unified management capabilities, complex operation and maintenance, and low efficiency of existing container terminal management and control systems.

[0009] This application provides a container terminal management cloud platform and a container terminal management system through several embodiments. The following description covers multiple aspects, and the embodiments and beneficial effects described below can be referenced interchangeably.

[0010] Firstly, this application provides a container terminal management and control cloud platform, comprising:

[0011] The access layer is configured to communicate with multiple user terminals and multiple execution terminals to obtain the operation data transmitted by each user terminal and the running data transmitted by each execution terminal. The operation data includes at least the loading and unloading requirements, container specifications and quantities, and the location of the operation terminal. The execution terminal includes at least the terminal crane equipment and the transport equipment. The running data includes at least the lifting height of the terminal crane equipment and the location of the transport equipment.

[0012] The application layer includes at least one service unit, each of which is used to output control instructions based on job data and running data, wherein the control instructions are used to control the execution end to run;

[0013] The platform service layer stores each control command in a message queue, enabling the execution end to retrieve the control command from the message queue and execute the operation corresponding to the control command.

[0014] According to the embodiments of this application, the above-described technical solution of this application has at least the following beneficial effects:

[0015] By replacing traditional on-premises deployment with cloud platform architecture, there is no need to purchase dedicated hardware and build data centers. Relying on the elastic resource supply of cloud computing, it is possible to expand and shrink on demand. This not only saves on hardware procurement, data center construction and maintenance costs, but also avoids idle or insufficient resources. At the same time, it reduces the investment of professional operation and maintenance personnel, and significantly reduces the overall deployment and operation and maintenance costs.

[0016] The access layer centrally collects data on operations and equipment from multiple terminals, breaking down data silos. The application layer coordinates the processing of data from each terminal and generates optimal control commands. The platform service layer ensures command synchronization through message queues, achieving unified management and efficient data collaboration across multiple terminals and ports, and avoiding operational conflicts.

[0017] The message queue design of the platform service layer ensures reliable storage and orderly distribution of control commands, avoiding transmission loss or delay, while also enabling the execution end to obtain commands in real time, shortening the response cycle, improving the reliability of operation command transmission and the timeliness of execution end response, and ensuring accurate and efficient port operations.

[0018] In one possible implementation of the first aspect above, the platform service layer further includes at least one functional component, wherein the functional component is used to perform calculations on the input core data and output the calculation results;

[0019] Each service unit is used to output control commands based on job data and runtime data, including:

[0020] Each service unit preprocesses the job data and operation data to obtain the core data corresponding to each service unit. The preprocessing includes at least data cleaning, format standardization, data filtering and outlier removal.

[0021] The core data is input into the functional components, the calculation results output by the functional components are obtained, and the calculation results are combined based on the preset business logic to obtain control instructions.

[0022] According to the embodiments of this application, the above-described technical solution of this application has at least the following beneficial effects:

[0023] By deploying functional components at the platform service layer for core data computation, and having application layer service units solely responsible for generating control instructions based on the combined computation results according to business logic, the separation of computation and business logic is achieved, improving system modularity and maintainability. Data preprocessing ensures input quality, avoiding control errors caused by dirty data or inconsistent formats, thus enhancing system stability and security. This layered design reduces the computational burden on service units, improves instruction generation efficiency, and allows the control flow to flexibly adapt to different job and equipment requirements. Furthermore, functional components can be reused across service units and job types, facilitating system expansion and reducing development and maintenance costs.

[0024] In one possible implementation of the first aspect above, the functional component is also used to output scheduling instructions based on core data, wherein the scheduling instructions are used to indicate the size of storage resources, computing resources and network resources required by the functional component when it obtains the operation result.

[0025] According to the implementation of this application, the above-mentioned technical solution of this application has at least the following beneficial effects: the functional components clearly output the resource specifications required for their own operation through scheduling instructions, providing a precise basis for resource allocation in the infrastructure layer, and completely changing the traditional cloud platform's passive expansion and extensive allocation mode.

[0026] One possible implementation of the first aspect mentioned above also includes:

[0027] The infrastructure layer includes at least one cloud host, which allocates resources to each functional component based on scheduling instructions to enable each functional component to operate normally. These resources include computing resources, storage resources, and network resources.

[0028] According to the embodiments of this application, the above-described technical solution of this application has at least one of the following beneficial effects:

[0029] Resources are precisely allocated according to the computational needs of functional components to avoid resource shortages or idle waste.

[0030] For multi-component concurrent scenarios, resource requirements are aggregated and allocated globally in an optimal manner to avoid a single component consuming too many resources, thereby improving overall resource utilization and reducing usage costs.

[0031] Before the functional components are started, scheduling instructions are output, and the infrastructure layer allocates resources in advance to avoid interruption and delay due to temporary resource shortages. It can also expand the capacity of high-complexity components in advance, ensuring the timeliness of control instruction generation and supporting the continuous and efficient operation of the dock.

[0032] In one possible implementation of the first aspect above, the cloud host includes at least one primary cloud host and one secondary cloud host, and the primary cloud host and the secondary cloud host are synchronized in real time.

[0033] According to the embodiments of this application, the above-mentioned technical solution of this application has at least the following beneficial effects: Through the dual-machine architecture of real-time synchronization of primary and secondary cloud hosts, redundant backup and seamless fault switching of underlying resources are realized, avoiding platform service interruption caused by the failure of a single cloud host, and ensuring the continuity of computing, storage and network resource supply; at the same time, real-time synchronization ensures that the data and configuration of the primary and secondary machines are completely consistent, and no additional recovery operation is required after switching, which not only enhances the reliability of the underlying resources of the cloud platform, but also provides continuous and stable resource support for core scenarios such as multi-port collaborative operation and critical command transmission, further improving the overall availability and business continuity of the system.

[0034] In one possible implementation of the first aspect described above, the access layer also communicates with the management terminal to obtain configuration requests transmitted by the management terminal.

[0035] The application layer also includes an intelligent operation and maintenance unit, which generates configuration files based on configuration requests. The configuration files include task templates, variable parameters, and target cloud hosts.

[0036] The platform service layer includes operation and maintenance components, which are used to perform configuration management and deployment operations based on configuration files.

[0037] According to the implementation method of this application, the above-mentioned technical solution of this application has at least the following beneficial effects: Through the layered collaboration of the access layer, intelligent operation and maintenance unit, and platform service layer operation and maintenance components, a closed loop is constructed from request reception to file generation and operation execution, realizing full-process automation and standardization of configuration management, avoiding human errors and ensuring consistent configuration of primary and secondary cloud hosts to support seamless switching. Relying on task template reuse and variable differentiation design, it takes into account both general deployment and multi-scenario adaptation, reducing development costs. The layered architecture makes the responsibilities of each link clear, the entire process traceable, and has good scalability, adapting to the operation and maintenance audit, fault tracing, and functional expansion needs of the dock cloud platform.

[0038] In one possible implementation of the first aspect above, the access layer is also used to obtain the usage of each service unit, wherein the usage includes at least the number of containers operated, the on-site time of each container, and the project duration;

[0039] The application layer also includes a billing unit, which is used to obtain the cost data generated by each service unit based on usage and preset calculation rules;

[0040] The platform service layer also includes a database, which is used to store cost data.

[0041] According to the embodiments of this application, the above-mentioned technical solution of this application has at least the following beneficial effects: the billing unit generates cost data based on usage and preset rules, making costs and expenses quantifiable and traceable.

[0042] In one possible implementation of the first aspect described above, the message queue includes a main message queue and a secondary message queue;

[0043] Control commands are stored in a message queue so that the executor can retrieve control commands from the message queue, including:

[0044] Control commands are stored in the main message queue and / or the secondary message queue according to preset rules, so that the execution end can retrieve control commands from the main message queue and / or the secondary message queue respectively.

[0045] According to the embodiments of this application, the above-mentioned technical solution of this application has at least the following beneficial effects: By using a dual-queue design of primary and secondary message queues and storing control instructions according to preset rules, on the one hand, redundant backup of control instructions is achieved, avoiding instruction loss due to single-queue failure and ensuring the reliability of critical instruction transmission for terminal operations. On the other hand, instructions can be distributed and stored according to rules such as operation priority and business type, reducing the load pressure on a single queue, while supporting the execution end to obtain instructions from the corresponding queue in parallel, improving instruction distribution and execution efficiency, and further enhancing the stability and efficiency of system operation in multi-terminal collaborative scenarios.

[0046] Secondly, this application provides a container terminal management and control system, comprising:

[0047] Multiple user terminals are used to obtain operational data, which includes at least the loading and unloading requirements, container specifications and quantities, and the location of the operational terminal.

[0048] Multiple execution terminals are used to acquire operational data. The execution terminals include at least dock lifting equipment and transport equipment, and the operational data includes at least the lifting height of the dock lifting equipment and the position of the transport equipment.

[0049] The cloud platform communicates with each user terminal and each execution terminal to generate control instructions based on job data and operation data, and transmits the control instructions to the execution terminal so that the execution terminal can perform the operation corresponding to the control instructions.

[0050] One possible implementation of the second aspect above also includes:

[0051] The management console communicates with the cloud platform to obtain configuration requests.

[0052] The cloud platform is also used to perform configuration management and deployment operations corresponding to configuration requests.

[0053] The beneficial effects of the second aspect and any possible implementation of the second aspect can be found in the first aspect and the beneficial effects of any possible implementation of the first aspect, and will not be repeated here. Attached Figure Description

[0054] Figure 1 is a schematic diagram of an application scenario of an embodiment of this application;

[0055] Figure 2 is a schematic diagram of the container terminal control system structure in an embodiment of this application;

[0056] Figure 3 is a schematic diagram of the cloud platform structure in an embodiment of this application;

[0057] Figure 4 is a diagram of the intelligent operation and maintenance architecture in an embodiment of the present invention;

[0058] Figure 5 is a block diagram of the electronic device in an embodiment of this application;

[0059] Figure 6 is a block diagram of the system on chip (SoC) in the embodiments of this application.

[0060] Figure label:

[0061] 100. Cloud Platform; 200. User Terminal; 300. Execution Terminal; 400. Management Terminal; 110. Access Layer; 120. Application Layer; 130. Platform Service Layer; 140. Infrastructure Layer. Detailed Implementation

[0062] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0063] The following is an explanation of the terms used in the embodiments of this application.

[0064] Cloud platform: A distributed internet resource pooling service system based on network (Internet / private network). Its core is to abstract resources such as computing, storage, network, and software into services that can be called on demand. Through technologies such as virtualization and distributed architecture, it realizes the elastic scaling, centralized management and efficient sharing of resources. In essence, it is a combination of resource virtualization and upper-layer service modularization.

[0065] Terminal Operating System (TOS): The core production control system of a container terminal, responsible for coordinating the entire process of container operations from ship loading and unloading, yard storage to gate entry and exit, and realizing intelligent control of the entire process of production planning, equipment scheduling, and resource allocation.

[0066] Cloud servers: core components of the infrastructure layer. Through virtualization technology, they abstract the hardware resources of physical server clusters, such as CPU, memory, storage, and network, into independent virtual computing environments that can be allocated on demand. They have the core characteristics of elastic scaling, resource isolation, and pay-as-you-go billing. Essentially, they are computing units that virtualize hardware resources and deliver them as services.

[0067] Localized deployment: Install and run all software, systems, and data on hardware environments that you control, rather than renting external public clouds or hosting data centers.

[0068] Container Quantity (TUE): Also known as the 20-foot equivalent unit, it is a conversion unit for calculating the number of containers. It is also called the international standard container unit. A 20-foot container is used as one unit of calculation, and a 40-foot container as two separate units, to unify the calculation of container throughput.

[0069] The technical problems to be solved by the embodiments of this application will be described below with reference to the accompanying drawings.

[0070] Referring to Figure 1, Figure 1 is a schematic diagram of an application scenario of an embodiment of this application.

[0071] As shown in Figure 1, the group headquarters needs to manage multiple ports under its umbrella. However, each port has multiple terminals, and each terminal is equipped with an independent Container Terminal Operating System (TOS). As mentioned earlier, traditional container terminal operating systems adopt a localized deployment model. This deployment model requires the purchase of dedicated servers, storage devices, and other hardware resources, and requires a dedicated data center to install and configure the software on these hardware devices. This localized deployment model has many problems, including high costs for hardware procurement and data center construction, and a lack of unified management and data collaboration capabilities for multiple terminals and ports.

[0072] Therefore, to address the aforementioned issues, this application provides a container terminal management cloud platform and a container terminal management system. This container terminal management cloud platform replaces the traditional localized model with cloud deployment. Through a three-layer architecture of access layer, application layer, and platform service layer, it realizes functions such as cross-terminal resource scheduling, business collaboration, and data aggregation and analysis. Moreover, this platform can significantly reduce hardware procurement, data center construction, and operation and maintenance costs, break down data silos and management barriers between multiple terminals and ports, realize centralized collection and collaborative processing of operational data and running data, and reliable distribution of control commands. At the same time, it has flexible scalability and scenario adaptability, significantly improving the collaborative efficiency of terminal operations, the reliability of command transmission, and the overall practicality of the system.

[0073] To better understand the container terminal management cloud platform of this application embodiment, the container terminal management system applying this platform will be described in detail below with reference to Figure 2.

[0074] Referring to Figure 2, which is a schematic diagram of the container terminal management and control system in an embodiment of this application.

[0075] As shown in Figure 2, the container terminal management and control system includes a cloud platform 100, a user terminal 200, and an execution terminal 300.

[0076] In the container terminal management system, there can be multiple user terminals 200 and execution terminals 300, and each user terminal 200 and execution terminal 300 is connected to the cloud platform 100.

[0077] In actual operation, each user terminal 200 obtains operational data input by terminal staff through a human-computer interaction interface. This operational data may include at least the requirements for loading and unloading ships, container specifications and quantities, and the location of the operational terminal. Each user terminal 200 transmits the obtained operational data to the aforementioned cloud platform 100.

[0078] Each actuator 300 is equipped with multiple sensors. These sensors acquire operational data from the actuator 300 and transmit this data to a controller integrated within the actuator 300. The controller then transmits the operational data to the cloud platform 100. The actuator 300 may include dockside lifting equipment and transport equipment. The operational data includes information such as the lifting height of the dockside lifting equipment and the position of the transport equipment.

[0079] It should be noted that the aforementioned terminal lifting equipment includes at least yard cranes and quay cranes, and the aforementioned transport equipment includes at least flatbed trucks. In addition to the aforementioned equipment, all transport equipment and terminal lifting equipment that can be used in a container terminal scheduling system are within the scope of protection of this application, and will not be elaborated further here.

[0080] The aforementioned cloud platform 100 includes multiple service units, which can be the container terminal operating system. After receiving operational data transmitted from each user terminal 200 and running data transmitted from each execution terminal 300, the cloud platform 100 parses each set of operational and running data and transmits them to the corresponding service unit. The service unit further parses and processes the operational and running data to obtain control instructions for controlling the execution terminal's operation and stores these control instructions in the cloud platform's message queue. Each execution terminal can retrieve the control instructions from the cloud platform's message queue and execute the corresponding operations to unload and load container ships, ensuring the normal operation of the terminal.

[0081] It should be noted that, in this embodiment of the application, the communication connection method between the cloud platform 100 and the user terminal 200, and between the cloud platform 100 and the execution terminal 300, is not limited. There can be various communication connection methods. For example, the communication connection method can be a wireless communication connection method such as ZigBee, LoRa, Wi-Fi, or Bluetooth, or a wired communication connection method such as fiber optic or power line.

[0082] In some embodiments, continuing to refer to Figure 2, the above-mentioned container terminal control system also includes a management terminal 400, which is connected to the cloud platform 100 via communication.

[0083] Among them, the core function of the management terminal 400 is to serve as the unified management and control entry point of the container terminal management and control cloud platform, undertaking full-process management functions such as configuration distribution, operation and maintenance monitoring, billing management, and data query.

[0084] In practical applications, the management terminal 400 plays different roles under different circumstances.

[0085] For example, if an administrator needs to modify the configuration of the cloud platform, the management terminal 400 can receive the configuration request input by the administrator through the front-end page and transmit the configuration request to the cloud platform 100. The cloud platform 100 performs corresponding configuration management and deployment operations based on the configuration request and transmits the completion signal of the configuration management and deployment operations to the management terminal 400 to indicate to the administrator that the configuration modification of the cloud platform has been completed or the configuration modification of the cloud platform has failed.

[0086] It should be noted that the above configuration management and deployment operations include, but are not limited to, expanding the memory of the cloud platform, and modifying, adding and deleting service units (i.e., the above container terminal operating system). The above completion signals may include deployment operation success and deployment operation failure signals.

[0087] When an administrator needs to query data stored in the cloud platform 100, the management terminal 400 obtains the data query request input by the administrator and transmits the data query request to the cloud platform 100. Based on the data query request, the cloud platform 100 retrieves the response data corresponding to the data query request from the database and transmits the response data back to the management terminal 400 for the administrator to view the data.

[0088] It should be noted that the aforementioned response data may include system indicator data, visualization data, and cost data. In practical applications, the management terminal can also obtain other instructions and transmit them to the cloud platform. The cloud platform then executes corresponding operations based on the instructions transmitted from the management terminal, which will not be elaborated upon here.

[0089] The cloud platform in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0090] Referring to Figure 3, Figure 3 shows a schematic diagram of the structure of the cloud platform in an embodiment of this application.

[0091] As shown in Figure 3, the cloud platform 100 of this application includes an access layer 110, an application layer 120, and a platform service layer 130.

[0092] The access layer 110 is configured to communicate with multiple user terminals and multiple execution terminals. The access layer 110 has multiple application programming interfaces (APIs) and network service interfaces to obtain job data transmitted by each user terminal and running data transmitted by each execution terminal.

[0093] It should be noted that the operational data should include at least the ship loading and unloading requirements, container specifications and quantities, and the location of the operating terminal. The execution end should include at least the terminal crane equipment and transport equipment, and the operation data should include at least the lifting height of the terminal crane equipment and the location of the transport equipment.

[0094] The application layer 120 includes at least one service unit. Each service unit outputs control instructions based on job data and running data, wherein the control instructions are used to control the operation of the execution end.

[0095] The platform service layer 130 is used to store control commands in a message queue so that the execution end can retrieve control commands from the message queue and perform operations corresponding to the control commands.

[0096] It is understandable that the cloud platform of this application has at least the following advantages.

[0097] First, it significantly reduces deployment and maintenance costs, breaking through the limitations of the localization model.

[0098] This application replaces traditional on-premises deployment with a cloud platform architecture, eliminating the need to purchase dedicated servers, storage devices, and build independent data centers. It directly leverages the elastic resource provisioning capabilities of cloud computing to achieve system deployment, thus saving the high costs associated with hardware procurement, data center construction, and subsequent hardware maintenance.

[0099] Second, it enables unified management and efficient data collaboration among multiple wharves and ports.

[0100] To address the shortcomings of traditional multi-terminal and multi-port collaboration models, this application constructs end-to-end collaborative capabilities through a three-layer architecture. The access layer can simultaneously communicate with user terminals (work request initiators) and execution terminals (terminal cranes, transport equipment, etc.) at multiple terminals, centrally collecting operational data (ship loading / unloading requirements, container information, terminal location) and equipment operation data from different terminals, such as spreader height and transport location. The application layer generates control commands through service units to achieve coordinated scheduling of multi-terminal operations, such as transport equipment scheduling.

[0101] Third, improve the reliability of job instruction transmission and the timeliness of execution terminal response.

[0102] The platform service layer employs a message queue design to store control commands, offering dual technological advantages. First, it avoids the loss and delay issues inherent in direct command transmission, ensuring reliable storage and orderly distribution of control commands. Second, the execution end can retrieve corresponding commands from the message queue in real time, eliminating the need to wait for a single data interaction to complete, thus shortening the command response cycle and improving the real-time performance and accuracy of terminal operations such as ship loading and unloading, and container transshipment.

[0103] In some embodiments, continuing to refer to FIG3, the platform service layer 130 further includes at least one functional component, wherein the functional component is used to perform calculations on the input core data and output the calculation results. The calculation results may include optimal path data for the transport equipment, etc.

[0104] Each service unit outputs control commands based on job data and operational data. This includes: preprocessing the job data and operational data to obtain core data corresponding to each service unit. Preprocessing includes at least data cleaning, format standardization, data filtering, and outlier removal. The core data is then used as input to functional components to obtain their output calculation results. Based on preset business logic, these results are combined to generate control commands.

[0105] Understandably, placing functional components explicitly in the platform service layer, specifically responsible for calculating core data, separates computational tasks from business logic assembly tasks. Service units, residing in the application layer, are only responsible for generating control instructions from the computational results of functional components according to business logic, thus improving the system's modularity and maintainability.

[0106] Preprocessing job data and operational data before inputting them into functional components ensures data quality and the accuracy of calculation results. This effectively avoids control errors caused by dirty data, inconsistent formats, or abnormal data, improving system stability and security.

[0107] After the functional components output their calculation results, the service units combine them based on preset business logic to generate control commands, enabling the control flow to flexibly adapt to different operational needs and dock equipment conditions. This layered processing approach reduces the computational burden on service units, improves command generation efficiency, and facilitates the reuse of functional component calculation logic. As independent calculation modules, functional components can be used in different service units or for different operation types, exhibiting reusability. The system can be functionally expanded as operational needs change without refactoring the entire control logic, reducing development and maintenance costs.

[0108] In some embodiments, continuing to refer to Figure 3, the platform service layer 130 provides a container platform, such as a container engine and a container orchestration component. These functional components are stored in containers within the container engine, and operational operations such as scheduling and elastic scaling of containers can be achieved through the container orchestration component in the platform service layer.

[0109] In some embodiments, the aforementioned functional components are also used to output scheduling instructions based on the core data they receive.

[0110] It should be noted that the above scheduling instructions are used to indicate the size of the storage resources, computing resources and network resources required for the functional component to obtain the calculation result.

[0111] Understandably, functional components use scheduling instructions to precisely declare the resource requirements corresponding to their own operations, providing a precise reference for resource allocation at the infrastructure layer and completely breaking the traditional cloud platform's inherent model of passive expansion and extensive allocation.

[0112] In some embodiments, the message queue includes a primary message queue and a secondary message queue.

[0113] Storing control instructions in a message queue so that the executor can retrieve the control instructions from the message queue includes:

[0114] Control commands are stored in the main message queue and / or the secondary message queue according to preset rules, so that the execution end can retrieve the control commands from the main message queue and / or the secondary message queue respectively.

[0115] It should be noted that control commands can be segmented according to a preset length, and the segmented control commands can be stored in the main message queue and the secondary message queue respectively according to priority, size, or hash value. The execution end can retrieve control commands from both queues simultaneously, thereby speeding up command retrieval. Alternatively, all control commands can be placed in the main message queue and the secondary message queue. The execution end first retrieves the control command from the main message queue. If the main message queue fails, the execution end can switch interfaces to retrieve the control command from the secondary message queue, improving the system's resilience.

[0116] In some embodiments, continuing to refer to FIG3, the cloud platform 100 described above also includes an infrastructure layer 140.

[0117] The aforementioned infrastructure layer 140 includes at least one cloud host, which allocates resources to each functional component based on the aforementioned scheduling instructions to enable each functional component to operate normally. The aforementioned resources include computing resources, storage resources, and network resources.

[0118] Understandably, cloud servers are installed on the infrastructure layer 140. These cloud servers allocate corresponding computing, storage, and network resources to each functional component based on scheduling instructions, avoiding blind allocation and idle waste of resources. This effectively improves the utilization rate of infrastructure layer resources and reduces the overall operating cost of the cloud platform. By supplying computing, storage, and network resources on demand, the differentiated operational needs of different functional components are met, ensuring that each component receives stable and reliable underlying resource support and avoiding component downtime and performance degradation due to resource shortages.

[0119] Referring to Figure 4, Figure 4 shows an intelligent operation and maintenance architecture diagram of an embodiment of this application.

[0120] In some embodiments, the cloud host may consist of one primary cloud host and one secondary cloud host, or one primary cloud host and multiple secondary cloud hosts. Regardless of whether it is a primary cloud host and one secondary cloud host or a primary cloud host and multiple secondary cloud hosts, the primary cloud host and the secondary cloud hosts always maintain synchronization.

[0121] For example, as shown in Figure 4, the cloud platform has a primary cloud host and a secondary cloud host. The primary and secondary cloud hosts not only share identical configurations in terms of database, functional components, microservices, and front-end pages or gateways, but they can also synchronize in real time. This ensures that if one fails, the system can automatically or manually switch between the primary and secondary cloud hosts via virtual IP, guaranteeing the normal operation of the terminal scheduling. The microservices can include the aforementioned billing unit, query unit, service unit, intelligent operation and maintenance unit, and log management unit.

[0122] It should be noted that, apart from the aforementioned functional components, the primary cloud host and the secondary cloud host also share other components, such as log management components, message queues, container platforms, and operation and maintenance components.

[0123] Understandably, adopting a dual-machine architecture with real-time synchronization of primary and secondary cloud hosts enables redundant backup of underlying resources and seamless failover, effectively mitigating the risk of platform service interruption caused by the failure of a single cloud host and ensuring the continuous and stable supply of computing, storage, and network resources. Simultaneously, the real-time synchronization mechanism guarantees complete consistency of data and configuration between the primary and secondary cloud hosts, eliminating the need for additional recovery operations after a switch. This significantly enhances the reliability of the cloud platform's underlying resources and provides continuous and stable resource guarantees for core business scenarios such as multi-host collaborative operations and critical command transmission, thereby greatly improving overall system availability and business continuity.

[0124] In practical applications, the primary and secondary cloud hosts can be kept in sync through methods such as distributed replication block devices or database cluster synchronization.

[0125] In this distributed replication block device, the disk blocks of the primary cloud host are used as the primary volume and the disk blocks of the secondary cloud host are used as the secondary volume. When data is written to the primary volume, the distributed replication block device captures disk input / output (I / O) operations in real time through the kernel module and synchronously replicates them to the secondary volume.

[0126] In the database cluster synchronization mode, based on multi-master synchronous replication, the databases of the primary cloud host and the secondary cloud host are all cluster nodes. After data is written to any node, it is synchronized to all nodes through the group communication protocol, realizing synchronization upon writing.

[0127] It should be noted that, in addition to the two methods mentioned above for synchronizing the primary and secondary cloud hosts, other methods can also be used to achieve synchronization between the primary and secondary cloud hosts. For details, please refer to existing technologies. Regardless of the method used to achieve real-time synchronization between the primary and secondary cloud hosts, it falls within the scope of protection of this application and will not be elaborated here.

[0128] When the primary cloud host fails, a failover between the primary and secondary cloud hosts can be achieved through automatic or manual failover. The automatic failover method involves real-time health monitoring of the primary cloud host using cluster management tools or the cloud platform's built-in high-availability components (monitoring dimensions include: host liveness status, processor / memory resource availability, core service port connectivity, and data synchronization status). If the primary cloud host meets the failure criteria, it is determined that the primary cloud host cannot provide service. The cluster management tool automatically unbinds the Virtual Internet Protocol (IP) interface from the primary cloud host's network interface card (NIC) and simultaneously binds it to the corresponding NIC interface on the secondary cloud host.

[0129] Since the secondary cloud host has obtained all the data of the primary cloud host (such as job data, configuration files, etc.) through the real-time synchronization mechanism, it immediately takes over all business requests (such as message queue scheduling of the platform service layer and resource supply of the infrastructure layer) after binding the virtual Internet Protocol. The upper-layer applications (access layer, application layer) still access through the original virtual IP, and the switching is seamless, ensuring that the collaborative operation of multiple terminals is not interrupted.

[0130] Manually switch to confirm that the data synchronization between the primary and secondary cloud hosts is complete in real time, and suspend the reception of new service requests on the primary cloud host. This can be done by issuing a manual switch command through the management console or by triggering the switch through the cluster management tool's backend console. After manual confirmation, the cluster management tool performs the virtual IP unbinding and binding operation (i.e., migrating from the primary cloud host to the secondary cloud host). The process can be manually controlled. After the secondary cloud host binds the virtual IP and confirms that service requests are responding normally, then perform maintenance shutdown on the primary cloud host. After maintenance is complete, the virtual IP can be migrated back to the primary cloud host.

[0131] In some embodiments, referring to Figure 3, the access layer 110 of the cloud platform 100 is also connected to the management terminal to obtain configuration requests transmitted by the management terminal.

[0132] The application layer 120 contains an intelligent operation and maintenance unit. This unit generates a configuration file based on a configuration request and transmits it to the operation and maintenance component in the platform service layer 130 via a pre-defined interface. The operation and maintenance component then performs corresponding configuration management and deployment operations based on this configuration file. These configuration management and deployment operations may include starting / stopping functional components on a specified cloud host, or scaling up / down existing components, according to the component deployment rules in the configuration file (such as the number of components, deployment nodes, and resource quotas).

[0133] When the operation and maintenance component completes the configuration or fails to configure, the corresponding prompt information is transmitted to the intelligent operation and maintenance unit in the application layer 120 through a preset interface. The operation and maintenance unit then forwards the prompt information to the access layer 110, which in turn forwards it to the management terminal to notify the administrator that the configuration and deployment have been completed or that the configuration and deployment have failed.

[0134] The above steps are equivalent to those in Figure 4. The management terminal transmits the configuration request to the operation and maintenance component. Based on the configuration request, the operation and maintenance component performs operation and maintenance on the database, functional components and microservices of the cloud host in the cloud platform to ensure that the data of the database, functional components and microservices are updated.

[0135] Understandably, the intelligent operations and maintenance unit generates a configuration file based on a configuration request. This process involves: first, querying the hostname of the target cloud host from the configuration database to construct a target cloud host set; then, determining the variable parameters; and finally, filling the target cloud host set and variable parameters into the task template to construct the aforementioned configuration file. The target cloud host set defines which cloud hosts the task will run on. Variable parameters are used to parameterize the task (version, path, etc.). The task template defines what operation to perform; it can be selected from a template library or dynamically generated, as detailed in existing technologies, which will not be elaborated upon here.

[0136] It should be noted that the above-mentioned operation and maintenance operations may include modifying the business logic in the above-mentioned service units, as well as adding and deleting service units.

[0137] In some embodiments, continuing to refer to Figure 3, a lightweight data collection tool is provided in the platform service layer 130. This tool collects log data generated at various layers on the cloud host and transmits the log data to the log management component in the platform service layer 130. The log management component generates visualized data and stores this data in a database. After receiving a user's log operation command, the access layer 110 transmits the command to the log management unit in the application layer 120. The log management unit parses the command and performs corresponding operations on the visualized data based on the command. These operations may include querying, deleting, etc.

[0138] The above steps are equivalent to those in Figure 4. The lightweight data collection tool collects log data from the cloud platform, cleans the data, and transmits the processed log data to the distributed search and analysis engine for log storage and indexing. The graphical display and interactive tools visualize the log data, and finally, the management end can directly schedule the visualized data so that the administrator can intuitively understand the detailed situation of the cloud platform.

[0139] It is understandable that the aforementioned log management components may include a distributed search and analysis engine and graphical display and interactive tools.

[0140] In some embodiments, continuing to refer to FIG3, the access layer 110 is further configured to obtain the usage of each service unit, wherein the usage includes at least the number of containers operated, the on-site time of each container, and the project duration.

[0141] The application layer 120 includes a billing unit, which is used to obtain the cost data generated by each service unit based on the usage and preset calculation rules, and transmit the cost data to the database in the platform service layer 130 for storage through a preset interface.

[0142] The on-site duration for each container refers to the total time a container is stored in the yard. This duration may include the number of days from the service unit's activation date to the current date.

[0143] Understandably, this billing unit generates cost data based on the aforementioned usage and pre-design fee rules, enabling quantifiable accounting and full-process traceability of costs and expenses.

[0144] In some embodiments, continuing to refer to FIG3, the access layer 110 is also used to collect query instructions transmitted from the management terminal. Based on the query instructions, the query unit in the application layer 120 obtains response data corresponding to the query instructions from the database of the platform service layer 130 through a preset interface, and submits the response data to the access layer 110. The access layer 110 sends the response data to the management terminal through the interface.

[0145] It is understandable that the response data can be the aforementioned log data, visualization data, and cost data, etc.

[0146] In some embodiments, the platform service layer described above also includes a monitoring component, an alarm scheduling component, and a visualization tool for collecting, storing, querying, and alarming cloud platform operation metrics. The monitoring component, as the core of cloud-native monitoring, actively pulls metric data from each monitored object and generates an original alarm when the metric data meets preset alarm rules.

[0147] After receiving the alarm, the alarm dispatch component reduces noise through intelligent governance mechanisms such as grouping, suppression, and routing. Then, it accurately pushes the effective alarm to relevant personnel through multiple channels such as email. The two work together to complete an end-to-end monitoring closed loop of data collection, alarm triggering, intelligent distribution, and fault response. After receiving the data collected by the monitoring component, the visualization tool presents this data intuitively in the form of charts, tables, etc. through a customizable dashboard.

[0148] The monitored objects can be configured according to requirements. Each monitored object has a metric interface that can be recognized by the monitoring component. By writing these metric interfaces into the monitoring component's configuration file, the metric data of these monitored objects can be obtained. These monitored objects can be functional modules such as billing units, query units, and functional components set up on the cloud platform.

[0149] Specifically, referring to Figure 4, the monitoring component collects metric data for each monitored object on the cloud platform and generates alarm information. The alarm scheduling component then transmits this alarm information to the management terminal via email or other means. The visualization tool uses the metric data collected by the monitoring component to generate visualized data, which is then transmitted to the management terminal so that administrators can clearly see the status of each monitored object on the cloud platform.

[0150] This application provides an electronic device, which includes a processor and a memory. The memory stores at least one instruction or at least one program. When the processor loads and executes the instruction or program, the electronic device performs the method described in the above embodiments for the container terminal management cloud platform. Its specific functions and corresponding technical effects can be found in the container terminal management cloud platform illustrated in Figures 1-4 of the above embodiments, and will not be repeated here. The electronic device of this application embodiment will be described in detail below with reference to Figure 5.

[0151] Referring to FIG5, a block diagram of an electronic device 1200 according to an embodiment of the present application is shown. The electronic device 1200 may include one or more processors 1201 coupled to a controller hub 1203. In at least one embodiment, the controller hub 1203 communicates with the processor 1201 via a multi-branch bus such as a front side bus (FSB) 1210, a point-to-point interface such as a quick path interconnect (QPI), or a similar connection. The processor 1201 executes instructions controlling general types of data processing operations. In one embodiment, the controller hub 1203 includes, but is not limited to, a graphics memory controller hub (GMCH) (not shown) and an input / output hub (IOH) (which may be on a separate chip) (not shown), wherein the GMCH includes memory and a graphics controller and is coupled to the IOH.

[0152] Electronic device 1200 may also include a coprocessor 1202 and a memory 1204 coupled to a controller hub 1203. Alternatively, one or both of the memory and the GMCH may be integrated within the processor (as described in this application), with memory 1204 and coprocessor 1202 directly coupled to processor 1201 and controller hub 1203, which is on a single chip with IOH. Memory 1204 may be, for example, dynamic random access memory (DRAM), phase change memory (PCM), or a combination of both. In one embodiment, coprocessor 1202 is a dedicated processor, such as, for example, a high-throughput MIC (many integerized core) processor, a network or communication processor, a compression engine, a graphics processor, a general-purpose computing on GPU (GPGPU), or an embedded processor, etc. Optional properties of coprocessor 1202 are indicated by dashed lines in Figure 5.

[0153] As a computer-readable storage medium, memory 1204 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. For example, memory 1204 may include any suitable non-volatile memory such as flash memory and / or any suitable non-volatile storage device such as one or more hard-disk drives (HDDs), one or more compact disc (CD) drives, and / or one or more digital versatile disc (DVD) drives.

[0154] In one embodiment, electronic device 1200 may further include a network interface controller (NIC) 1206. Network interface 1206 may include a transceiver for providing a radio interface for electronic device 1200 to communicate with any other suitable device, such as a front-end module, antenna, etc. In various embodiments, network interface 1206 may be integrated with other components of electronic device 1200. Network interface 1206 can implement the functions of the communication unit in the above embodiments.

[0155] Electronic device 1200 may further include input / output (I / O) device 1205. I / O device 1205 may include: a user interface designed to enable a user to interact with electronic device 1200; a peripheral component interface designed to enable peripheral components to also interact with electronic device 1200; and / or sensors designed to determine environmental conditions and / or location information related to electronic device 1200.

[0156] It is worth noting that Figure 5 is merely exemplary. That is, although Figure 5 shows the electronic device 1200 including multiple devices such as a processor 1201, a coprocessor 1202, a controller hub 1203, and a memory 1204, in actual applications, devices using the methods of this application may only include a portion of the devices in the electronic device 1200. For example, it may only include the processor 1201 and the network interface 1206. The nature of optional devices in Figure 5 is shown with dashed lines. According to some embodiments of this application, the memory 1204, as a computer-readable storage medium, stores instructions or programs that, when executed on a computer, execute the container terminal management cloud platform described in the above embodiments. Specific details can be found in the methods of the above embodiments, which will not be repeated here.

[0157] Referring now to FIG. 6, a block diagram of a system-on-chip (SoC) 1300 according to an embodiment of the present application is shown. In FIG. 6, similar components have the same reference numerals. Additionally, dashed boxes represent optional features of more advanced SoCs. In FIG. 6, the SoC 1300 includes: an interconnect unit 1350 coupled to an application processor 1310; a system proxy unit 1380; a bus controller unit 1390; an integrated memory controller unit 1340; a group or one or more coprocessors 1320, which may include integrated graphics logic, an image processor, an audio processor, and a video processor; a static random access memory (SRAM) unit 1330; and a direct memory access (DMA) unit 1360. In one embodiment, the coprocessor 1320 includes a dedicated processor, such as, for example, a network or communication processor, a compression engine, a GPGPU, a high-throughput MIC processor, or an embedded processor.

[0158] The static random access memory (SRAM) cell 1330 may include one or more computer-readable media for storing data and / or instructions. The computer-readable storage medium may store instructions, specifically, temporary and permanent copies of those instructions. These instructions may include, when executed by at least one unit in the processor, causing the SoC 1300 to perform the container terminal management cloud platform according to the above embodiments; specific details can be found in the methods of the above embodiments, and will not be repeated here.

[0159] This application provides a computer-readable storage medium storing at least one instruction or at least one program. The at least one instruction or at least one program is loaded and executed by a processor to implement the method of the container terminal management cloud platform described in the above embodiments. Its specific functions and corresponding technical effects can be referred to the container terminal management cloud platform explained in Figures 1-4 of the above embodiments, and will not be repeated here.

[0160] This application provides a computer program product, including computer instructions. When the computer instructions are executed on an electronic device, the electronic device enables the container terminal management cloud platform described in the above embodiments. Its specific functions and corresponding technical effects can be found in Figures 1-4 of the above embodiments illustrating the container terminal management cloud platform, and will not be repeated here.

[0161] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0162] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0163] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0164] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, compact disc read-only memory (CD-ROMs), magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable media include any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0165] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the accompanying drawings. Furthermore, including structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0166] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0167] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0168] It should be noted that in the examples and description of this application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0169] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art should understand that various changes in form and detail may be made thereto without departing from the spirit and scope of this application.

Claims

1. A cloud platform for the management and control of a container terminal, characterized in that, include: An access layer is configured to communicate with multiple user terminals and multiple execution terminals, and is used to acquire operation data transmitted by each user terminal and running data transmitted by each execution terminal. The operation data includes at least loading / unloading requirements, container specifications and quantities, and the location of the operation terminal. The execution terminals include at least terminal crane equipment and transport equipment. The running data includes at least the spreader height of the terminal crane equipment and the location of the transport equipment. An application layer includes at least one service unit, each of which is used to output control commands based on the operation data and the running data. The control commands are used to control the operation of the execution terminals. A platform service layer stores each control command in a message queue, so that the execution terminal can retrieve the control command from the message queue and execute the operation corresponding to the control command.

2. The container terminal management and control cloud platform according to claim 1, characterized in that, The platform service layer further includes at least one functional component, wherein the functional component is used to perform calculations on the input core data and output the calculation results; each service unit is used to output control instructions based on the job data and the running data, including: each service unit preprocesses the job data and the running data to obtain the core data corresponding to each service unit, the preprocessing including at least data cleaning, format standardization, data filtering and outlier removal; inputting the core data into the functional component to obtain the calculation results output by the functional component, and combining the calculation results based on preset business logic to obtain the control instructions.

3. The container terminal management and control cloud platform according to claim 2, characterized in that, The functional component is also used to output scheduling instructions based on the core data, wherein the scheduling instructions are used to indicate the size of storage resources, computing resources and network resources required by the functional component to obtain the calculation result.

4. The container terminal management and control cloud platform according to claim 3, characterized in that, Also includes: The infrastructure layer includes at least one cloud host, which allocates resources to each of the functional components based on the scheduling instructions to enable each of the functional components to operate normally, wherein the resources include the computing resources, the storage resources, and the network resources.

5. The container terminal management and control cloud platform according to claim 4, characterized in that, The cloud host includes at least one primary cloud host and one secondary cloud host, and the primary cloud host and the secondary cloud host are synchronized in real time.

6. The container terminal management and control cloud platform according to claim 4, characterized in that, The access layer also communicates with the management terminal to obtain configuration requests transmitted by the management terminal; the application layer also includes an intelligent operation and maintenance unit, which generates a configuration file based on the configuration request, the configuration file including task templates, variable parameters and target cloud hosts; the platform service layer includes an operation and maintenance component, which performs configuration management and deployment operations based on the configuration file.

7. The container terminal management and control cloud platform according to claim 1, characterized in that, The access layer is also used to obtain the usage of each service unit, the usage including at least the number of containers operated, the on-site time of each container, and the project duration; the application layer also includes a billing unit, which is used to obtain the cost data generated by each service unit based on the usage and preset calculation rules; the platform service layer also includes a database, which is used to store the cost data.

8. The container terminal management and control cloud platform according to claim 1, characterized in that, The message queue includes a main message queue and a secondary message queue; storing the control instruction in the message queue so that the execution terminal can obtain the control instruction from the message queue includes: storing the control instruction in the main message queue and / or the secondary message queue according to a preset rule so that the execution terminal can obtain the control instruction from the main message queue and / or the secondary message queue respectively.

9. A container terminal management and control system, characterized in that, include: Multiple user terminals are used to acquire operational data, which includes at least loading and unloading requirements, container specifications and quantities, and the location of the operational terminal; multiple execution terminals are used to acquire operational data, which includes at least terminal crane equipment and transport equipment, and the operational data includes at least the lifting height of the terminal crane equipment and the location of the transport equipment; a cloud platform is communicatively connected to each user terminal and each execution terminal, and is used to generate control commands based on the operational data and the operational data, and transmit the control commands to the execution terminals so that the execution terminals perform operations corresponding to the control commands.

10. The container terminal control system according to claim 9, characterized in that, Also includes: The management terminal communicates with the cloud platform to obtain configuration requests; the cloud platform is also used to perform configuration management and deployment operations corresponding to the configuration requests.

Images