Methods, systems, and computer devices and program products for deploying objects

Abstract

Embodiments of the present disclosure provide a method, system, computing device and program product for deploying objects. The method comprises: constructing, in a central management node, deployment groups for a plurality of objects to be deployed; in response to a deployment trigger instruction for the deployment groups, issuing deployment information corresponding to the deployment groups to at least one target edge management node; the target edge management node receives the deployment information, obtains group information of the deployment groups and the plurality of objects to be deployed based on the deployment information; and the target edge management node distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the group information. Embodiments of the present disclosure construct a deployment channel in a multi-level industrial edge architecture, which can avoid the risk of repetition and inconsistency of single configuration.

Description

Technical Field

[0001] This disclosure relates to the fields of industrial automation and edge computing technology, and more particularly to a method, system, computing device, and program product for deploying objects. Background Technology

[0002] With the deep integration of industrial automation and the Internet of Things (IoT), industrial edge computing technology has been widely adopted. As the complexity of industrial field operations increases, the number of applications, microservice components, and related data entities deployed at the edge is growing exponentially.

[0003] In existing industrial edge platforms, applications are typically presented as single, ungrouped, independent projects in an application library. As the number of available applications increases significantly, the application library interface becomes cluttered, causing field technicians to spend considerable time searching for and locating related application sets with specific collaborative relationships, significantly reducing configuration efficiency. Furthermore, existing edge management solutions often require users to deploy each application as a standalone unit. When multiple applications with runtime dependencies need to be deployed in an industrial field, this standalone deployment method leads to a large number of repetitive manual configuration operations. Since the configuration parameters of each application need to be manually associated one by one, this significantly increases the probability of configuration inconsistencies and can easily lead to runtime conflicts. Summary of the Invention

[0004] In view of this, the present disclosure provides a method, system, computing device, and program product for deploying objects, which at least partially solves the above-mentioned technical problems.

[0005] A first aspect of this disclosure provides a method for deploying objects, the method comprising: constructing a deployment group for a plurality of objects to be deployed in a central management node; in response to a deployment trigger instruction for the deployment group, sending deployment information corresponding to the deployment group to at least one target edge management node; the target edge management node receiving the deployment information, obtaining grouping information of the deployment group and the plurality of objects to be deployed based on the deployment information; and the target edge management node distributing the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information.

[0006] In one possible implementation, the plurality of objects to be deployed may be used to obtain information about the plurality of objects to be deployed, as well as the grouping information of the deployment groups.

[0007] In one possible implementation, the method further includes: before the target edge management node distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node, reconstructing the deployment group in the local storage of the target edge management node based on the grouping information and the plurality of objects to be deployed; wherein, the target edge management node distributing the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information includes: distributing the plurality of objects to be deployed to the at least one target edge execution node in response to a deployment instruction triggered for the deployment group.

[0008] In one possible implementation, the step of constructing a deployment group for multiple objects to be deployed in the central management node includes: constructing the deployment group for the multiple objects to be deployed in the central management node based on at least one of the target application scenario, the functional attributes of the objects to be deployed, user-defined rules, and the relationship between the deployment objects.

[0009] In one possible implementation, the method further includes managing the deployment group, the management including at least one of the following: adding or removing the objects to be deployed from the deployment group in response to a member modification instruction for the deployment group; modifying the name of the deployment group in response to a rename instruction; deleting the deployment group in response to a deletion instruction for the deployment group, and restoring each of the objects to be deployed that originally belonged to the deployment group as an independent object to be deployed.

[0010] In one possible implementation, the deployment trigger instruction is a one-click deployment instruction triggered by a single user operation targeting the deployment group.

[0011] In one possible implementation, the deployment information further includes version information of the plurality of objects to be deployed, and at least one of the runtime dependencies between the plurality of objects to be deployed.

[0012] In one possible implementation, the method further includes: distributing the runtime dependencies to the target edge execution node; and the target edge execution node determining the startup order of the multiple objects to be deployed based on the runtime dependencies when jointly starting the distributed objects.

[0013] In one possible implementation, the object to be deployed includes an application and / or an application update package.

[0014] A second aspect of this disclosure provides a method for deploying objects, the method being applied to a central management node, comprising: constructing a deployment group for a plurality of objects to be deployed; and, in response to a deployment trigger instruction for the deployment group, sending deployment information corresponding to the deployment group to at least one target edge management node, such that the target edge management node obtains grouping information of the deployment group and the plurality of objects to be deployed based on the deployment information, and distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information.

[0015] A third aspect of this disclosure provides a method for deploying objects, the method being applied to a target edge management node, comprising: receiving deployment information corresponding to a deployment group issued by a central management node, wherein the deployment group is constructed in the central management node for multiple objects to be deployed, and the deployment information is issued by the central management node in response to a deployment trigger command after the deployment group is constructed; obtaining grouping information of the deployment group and the multiple objects to be deployed based on the deployment information; and distributing the multiple objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information.

[0016] A fourth aspect of this disclosure provides a method for deploying objects, the method being applied to a target edge execution node, comprising: receiving a plurality of objects to be deployed distributed by a target edge management node, wherein the plurality of objects to be deployed belong to a deployment group, deployment information corresponding to the deployment group is sent by a central management node to the target edge management node in response to a deployment trigger command, and the target edge management node obtains grouping information of the deployment group and the plurality of objects to be deployed based on the deployment information, and then distributes them to the target edge execution node based on the grouping information; and deploying and running the plurality of objects to be deployed locally.

[0017] A fifth aspect of this disclosure provides a system for deploying objects, the system including a central management node, at least one target edge management node, and at least one target edge execution node connected to the target edge management node; the central management node is configured to perform the method described in the second aspect above; the target edge management node is configured to perform the method described in the third aspect above; and the target edge execution node is configured to perform the method described in the fourth aspect above.

[0018] A sixth aspect of this disclosure provides a computing device including a processor and a memory, the memory storing a computer program, wherein the processor executes the computer program to implement the method described in the second aspect above.

[0019] A seventh aspect of this disclosure provides a computing device including a processor and a memory, the memory storing a computer program, wherein the processor executes the computer program to implement the method described in the third aspect above.

[0020] The eighth aspect of this disclosure provides a computing device including a processor and a memory, the memory storing a computer program, wherein the processor executes the computer program to implement the method described in the fourth aspect above.

[0021] The ninth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, implements the methods described in the second, third, or fourth aspects described above.

[0022] In the embodiments of this disclosure, by constructing deployment groups at the central management node and distributing them level by level, the retrieval complexity of large-capacity application libraries is significantly reduced, the high-frequency repetitive operations caused by deploying individual applications one by one are effectively reduced, and the inconsistency risk caused by human configuration errors is effectively reduced, thereby establishing an efficient and highly reliable deployment channel in a multi-level industrial edge architecture. Based on this, the target edge management node reconstructs the deployment groups in local storage, realizing a persistent edge-side mirror of the group structure, significantly enhancing local management autonomy and effectively improving the system's fault tolerance. Simultaneously, it supports multi-dimensional clustering to construct groups, enabling the software-level deployment structure to highly match the physical process topology of the industrial site, helping to alleviate the technical bottleneck of disordered stacking of massive applications. Combined with a closed-loop management mechanism that dynamically modifies and renames members and automatically restores members to their independent state after group deletion, the risk of orphan applications or accidental deletion is effectively avoided without damaging the application entity. Furthermore, by incorporating version information and runtime dependencies into the deployment information, a reliable data foundation is provided for subsequent precise version control and timing orchestration. Based on the distributed runtime dependencies, the target edge execution nodes establish a joint startup order locally, resolving startup timing conflicts in multi-component collaborative runtime. This effectively avoids the engineering risk of downstream service crashes due to upstream services not being ready, and significantly improves the high-reliability transient response of the industrial field control and monitoring business chain. The aforementioned grouping mechanism is also compatible with applications and their update packages, thus ensuring efficient operation and maintenance throughout the entire software lifecycle. Attached Figure Description

[0023] Figure 1 This is a flowchart of a method for deploying objects according to embodiments of the present disclosure.

[0024] Figure 2 This diagram illustrates an embodiment of how deployment groups are distributed from a central management node to a target edge management node.

[0025] Figure 3 This is a flowchart of a method for deploying an object to a central management node according to an embodiment of the present disclosure.

[0026] Figure 4 This is a flowchart of a method for deploying an object to a target edge management node according to an embodiment of the present disclosure.

[0027] Figure 5 This is a flowchart of a method for applying a deployment object to a target edge execution node according to an embodiment of the present disclosure.

[0028] Figure 6 This is a structural diagram of a system for deploying objects according to embodiments of the present disclosure.

[0029] Figure 7 This is a structural diagram of a computing device or server according to embodiments of the present disclosure.

[0030] List of reference numerals: User 10; Central management node 20; Edge management node 30; Target edge management node 30a; Edge execution node 40; Target edge execution node 40a; First deployment group 21; First object to be deployed 211; Second object to be deployed 212; Third object to be deployed 213; Second deployment group 22; Fourth object to be deployed 221; Fifth object to be deployed 222; Sixth object to be deployed 223; Seventh object to be deployed 224; System of the deployed object 600; Computing device 700; Memory 702; Processor 704; Bus 706. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided with reference to the accompanying drawings and embodiments. Obviously, the described embodiments are merely some, not all, of the embodiments of this disclosure. All other technical solutions obtained by those skilled in the art based on the embodiments of this disclosure are within the scope of protection of this disclosure.

[0032] In the description of this disclosure, a central management node refers to a centralized edge management node with global application storage, group configuration, and distribution control capabilities, such as an Industrial Edge Hub (IE Hub) deployed in the cloud or on a server. An edge management node refers to an intermediary management instance between the central management node and specific physical devices, such as an Industrial Edge Management System (IEM) used to manage specific clusters of edge devices. An edge execution node refers to a physical or virtual edge device deployed in an industrial field that actually runs the object to be deployed, such as an Industrial Edge Device (IED).

[0033] Figure 1 This is a flowchart of a method for deploying objects according to embodiments of the present disclosure. Figure 6 This is a structural diagram of a system for deploying objects according to embodiments of the present disclosure.

[0034] First, see Figure 6 System 600 includes a central management node 20, at least one edge management node 30 (including a target edge management node 30a), and at least one edge execution node 40 (including a target edge execution node 40a). For example, the central management node 20 is deployed in a first computing device (such as the cloud) on the service side, and the edge management node 30 is deployed in a second computing device (such as a local edge management server) on the factory customer side. The edge execution node 40 is typically an edge device (such as a smart gateway, edge controller, or industrial PC) deployed in an industrial production site.

[0035] The method of the embodiment shown in Figure 1 will be described in detail below with reference to the system architecture shown in Figure 6. Referring to Figure 1, the method specifically includes the following steps:

[0036] S102: In the central management node 20, a deployment group is built for multiple objects to be deployed.

[0037] In practice, user 10 can build deployment groups for multiple objects to be deployed through the user interface or API interface of the central management node 20. For example... Figure 2 As shown, a first deployment group 21 and a second deployment group 22 are constructed in the central management node 20. For example, the first deployment group 21 can be an "AI" group containing "AI Asset Manager" (corresponding to the first object to be deployed 211), "AI Inference Server" (corresponding to the second object to be deployed 212), and "AI Model Monitor" (corresponding to the third object to be deployed 213); the second deployment group 22 can be an "IIH" group containing "IIH DatabusGateway" (corresponding to the fourth object to be deployed 221), "IIH Semantics" (corresponding to the fifth object to be deployed 222), "IIH Essentials" (corresponding to the sixth object to be deployed 223), and "IIH Registry Service" (corresponding to the seventh object to be deployed 224). By establishing this grouped logical structure in the central management node 20, the originally scattered objects to be deployed are aggregated.

[0038] For example, when constructing deployment groups in the central management node 20, the construction basis includes at least one of the following: target application scenario (e.g., grouping AI Asset Manager, AI Inference Server and AI Model Monitor into the "AI" scenario group), functional attributes of the objects to be deployed, user-defined rules, and relationships between deployment objects (e.g., but not limited to deployment dependencies, business collaboration relationships, and runtime dependencies).

[0039] Optionally, the objects to be deployed can refer to software entities that need to be distributed and deployed to the edge for operation, such as, but not limited to, monolithic applications, microservice components, container images, application update packages, etc. As an exemplary implementation, these multiple objects to be deployed include applications and / or application update packages, making this embodiment applicable not only to the initial deployment phase but also to subsequent incremental updates and version iterations, achieving full lifecycle management. Additionally, optionally, the objects to be deployed can also be non-executable data entities such as device configuration files, machine learning model weight files, PLC license certificates, etc.

[0040] S104: Initiate (e.g., initiated by user 10) a deployment trigger instruction for a deployment group (e.g., the first deployment group 21).

[0041] For example, the deployment trigger instruction may be an instruction triggered by a single operation targeting the deployment group (e.g., clicking the "One-Click Deployment" button next to the corresponding group on the user interface). For example, the deployment trigger instruction may also be generated by a webhook of an external continuous integration and continuous deployment (CI / CD) pipeline, a scheduled task scheduler, or a northbound API call automatically triggered based on the resource availability of edge execution nodes.

[0042] S106: In response to the deployment trigger command, the central management node 20 generates the corresponding deployment information.

[0043] For example, the deployment information includes the plurality of objects to be deployed and the grouping information of the deployment group. Optionally, the deployment information may not necessarily include the objects to be deployed themselves, but may also include information for obtaining the objects to be deployed, such as download addresses, image repository references, resource identifiers, etc. The grouping information refers to metadata or a set of metadata used to logically and / or physically define, organize, constrain, and coordinate the plurality of objects to be deployed within the deployment group. The grouping information is distributed from the central management node 20 to the target edge management node 30a as part of the deployment information, so that the target edge management node 30a can completely restore the business logic of the deployment group locally. In one embodiment, the grouping information includes a membership relationship indicating that the plurality of objects to be deployed belong to the deployment group, and this membership relationship is the technical basis for the target edge management node 30a to reconstruct the deployment group locally on the edge side. Furthermore, in order to meet the more complex collaborative control and resource sharing needs of industrial sites, the group information may optionally include at least one of the following: (1) Operational collaborative control strategy: such as the start order, stop order, and operation dependency of each object to be deployed in the deployment group; (2) Member deployment mapping relationship: such as the mapping rules used to indicate which different target edge execution nodes 40 to which different objects to be deployed in the deployment group are respectively directed; (3) Group attribute information: such as the group name of the deployment group and the group version number used for the overall collaborative upgrade or rollback.

[0044] S108: The central management node 20 sends the deployment information corresponding to the deployment group to at least one target edge management node 30a.

[0045] The at least one target edge management node 30a is determined by filtering candidate edge management nodes 30 connected to the central management node 20. For example, one or more edge management nodes 30 can be dynamically specified as target edge management nodes 30a in response to a user's selection command on a visual interface. Alternatively, one or more edge management nodes 30 that meet preset conditions can be automatically matched and filtered as target nodes 30a based on routing policies, device labels, or network topology rules pre-configured in the central management node 20.

[0046] S110: The target edge management node 30a receives the deployment information and obtains the group information and the multiple objects to be deployed.

[0047] For example, the target edge management node 30a can obtain the grouped information and the multiple objects to be deployed by parsing, unpacking, deserializing, or extracting the received deployment information (if the deployment information contains information for obtaining the objects to be deployed, the target edge management node 30a can pull the objects to be deployed from the corresponding repository based on such information, such as a download address). Optionally, the target edge management node 30a may not perform complete parsing of the deployment information, but instead dynamically extract the grouped information and the objects to be deployed during data stream transmission through methods such as data stream redirection, pipeline transmission, or memory mapping.

[0048] Optionally, in some implementations, after step S110, the method of this embodiment may further include a step of physically rebuilding the deployment group in local non-volatile storage: based on the grouping information and the plurality of objects to be deployed, rebuilding the deployment group in the local storage of the target edge management node. Specifically, as Figure 2 As shown, after receiving the deployment information, the target edge management node 30a reconstructs locally the first deployment group 21 and the second deployment group 22, which are mirror images (structurally corresponding) to the central management node 20, and maintains the hierarchical relationship between each object to be deployed and its corresponding deployment group. This cross-level structural preservation allows the logical organizational relationships defined on the central side to be maintained on the edge management side, reducing the management and maintenance costs on the edge side.

[0049] Optionally, in other implementations, the target edge management node 30a may omit the aforementioned step of physically rebuilding the deployment group, and instead adopt, for example, but not limited to, any of the following equivalent variant implementations: (1) After receiving and parsing the deployment information, the target edge management node 30a only establishes a temporary logical mapping relationship of the deployment group in the running memory (RAM) without writing it to the local database or disk. Once the distribution is completed or the system restarts, the memory view is released. (2) The target edge management node 30a implicitly rebuilds the group relationship by dynamically binding the same "group identifier" to the multiple objects to be deployed to a distributed key-value system or service registry. (3) As a data relay channel, the target edge management node 30a, upon receiving the deployment information, directly streams the multiple objects to be deployed to the target edge execution node 40 based on the group information.

[0050] S112: Based on the grouping information, the target edge management node 30a distributes the plurality of objects to be deployed to at least one target edge execution node 40a connected to the target edge management node 30a.

[0051] The at least one target edge execution node 40a is determined by filtering candidate edge management nodes 40 connected to the target edge management node 30a. For example, one or more edge execution nodes 40 can be dynamically specified as target edge execution nodes 40a in response to a user's selection command on a visual interface. Alternatively, one or more edge execution nodes 40 that meet preset conditions can be automatically matched and filtered as target nodes 40a based on routing policies, device labels, or network topology rules pre-configured in the target edge management node 30a.

[0052] In specific implementation, in order to adapt to different reconstruction states (physical reconstruction, virtual reconstruction or no reconstruction) after the aforementioned step S110 and the ever-changing communication and security needs of industrial sites, the process of distributing based on the grouped information in step S112 specifically includes the following parallel or combined implementation methods: (1) Delayed / manual distribution based on local persistent reconstruction: If the target edge management node 30a physically reconstructs the deployment group in local non-volatile storage after step S110, then in step S112, the target edge management node 30a first temporarily stores the multiple objects to be deployed and the grouped information locally. When the target edge management node 30a receives the deployment instruction triggered by the local Web interface or local physical button of the target edge management node 30a through the local operation and maintenance personnel, or receives the timed deployment instruction automatically generated by the local policy engine (such as based on the production line schedule or equipment shutdown maintenance window), the target edge management node 30a extracts the objects to be deployed from the local storage and performs the distribution. (2) Automatic pipeline distribution based on reconstruction completion event: If the target edge management node 30a reconstructs the deployment group locally (physical reconstruction or memory virtual view reconstruction) after step S110, the event listener inside the target edge management node 30a automatically captures the "reconstruction complete" event at the moment the reconstruction action is completed and immediately generates an internal trigger signal. In response to the internal trigger signal, the target edge management node 30a automatically executes the distribution step immediately without any manual intervention. This method realizes the deployment of "one-click triggering in the cloud and automatic flow at the edge". (3) Reconstruction-free instant distribution based on streaming pass-through: If the target edge management node 30a omits the local reconstruction step after step S110, the target edge management node 30a acts as a data relay channel in step S112. Upon receiving the deployment information, the target edge management node 30a uses pipeline transmission technology to dynamically parse the distribution routing rules in the grouped information in memory, and transmits the multiple objects to be deployed to the target edge execution node 40a in real time and instant as a data stream.

[0053] S114: The target edge execution node 40a receives multiple objects to be deployed after distribution and deploys and runs them locally.

[0054] As an example implementation, the method disclosed herein also includes a step of dynamically managing the deployment groups. Specifically: in response to a member modification instruction, objects to be deployed are dynamically added to or removed from the deployment group. For example, a new data preprocessing component is added to the "AI" group. In response to a rename instruction, the name of the deployment group is modified. In response to a deletion instruction for the deployment group, the deployment group is deleted, and each object to be deployed that originally belonged to the deployment group is restored as an independent object to be deployed, so that it is presented as an independent tile in the application library. The dynamic management mechanism gives users flexible control over the lifecycle of the groups. In particular, the design of restoring members to an independent state when deleting a group effectively avoids the risk of accidental deletion of internal applications due to group disintegration, ensuring the integrity and security of software assets in the application library. In addition, optionally, when deleting a group, a soft deletion and version rollback mechanism can be introduced, allowing users to restore the disbanded group within a specific time window; or when deleting a group, a dual-track option of "cascading deletion" and "retaining individual units" can be provided to adapt to different on-site operation and maintenance strategies.

[0055] As an example implementation, the deployment information may also include version information of the multiple objects to be deployed and / or their runtime dependencies. The target edge management node 30a further distributes these runtime dependencies to the target edge execution node 40a. When jointly starting these objects to be deployed, the target edge execution node 40a determines the startup order based on these runtime dependencies (e.g., the data bus gateway must be started first, and the semantic resolution service and registration service should be started only after it is ready). Alternatively, the startup order control may not rely on a static dependency chain, but may be achieved by a lightweight orchestrator on the target edge execution node 40a through dynamically probing the health check interface (Readiness Probe) of each object to be deployed, i.e., dynamically determining the launch sequence of the next component through real-time feedback.

[0056] To ensure that the specification fully discloses the claims, the following is combined with Figure 3 , Figure 4 , Figure 5 , Figure 7 Describe the single-ended process and hardware structure:

[0057] Figure 3 This is a flowchart of a method for deploying an object to a central management node according to an embodiment of this disclosure. Figure 3 As shown, the method includes:

[0058] In step S302, deployment groups are built for multiple objects to be deployed in the central management node. In practice, users can aggregate the originally scattered objects to be deployed based on the target application scenario, functional attributes, or custom rules through the user interface or API interface of the central management node, thereby establishing a clear grouped logical structure on the central side.

[0059] In step S304, in response to the deployment trigger command for the deployment group, the central management node sends the deployment information corresponding to the deployment group to at least one target edge management node. The deployment information includes the plurality of objects to be deployed (or information for obtaining the plurality of objects to be deployed) and grouping information of the deployment group. This sending action enables the target edge management node, upon receiving the deployment information, to obtain the grouping information and the plurality of objects to be deployed based on the deployment information, and ultimately distribute the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information. This design locks in the core logic of grouped distribution in the cloud (central side), providing the necessary data foundation for subsequent collaborative distribution on the edge side.

[0060] Figure 4 This is a flowchart of a method for deploying an object to a target edge management node according to an embodiment of this disclosure. Figure 4 As shown, the method includes:

[0061] In step S402, the target edge management node receives deployment information corresponding to the deployment group issued by the central management node. Here, the deployment information is issued by the central management node in response to the deployment trigger command after constructing the deployment group, and the deployment information fully contains multiple objects to be deployed (or information for obtaining the multiple objects to be deployed) and the grouping information of the deployment group.

[0062] In step S404, the target edge management node obtains the group information and the multiple objects to be deployed based on the received deployment information. In specific implementations, the acquisition action can employ various equivalent data processing methods such as parsing, unpacking, deserialization, or streaming extraction to ensure compatibility with different edge software architectures.

[0063] In step S406, the target edge management node distributes the multiple objects to be deployed to at least one target edge execution node connected to the target edge management node based on the acquired grouping information. In this step, the target edge management node does not need to force the reconstruction of local physical storage during distribution. Instead, it can automatically and instantly distribute multiple objects to be deployed based on the member associations or node mapping relationships in the grouping information, thereby achieving good lightweight operation performance and low data processing latency on the edge management side.

[0064] Figure 5 This is a flowchart of a method for deploying an object to a target edge execution node according to an embodiment of this disclosure. Figure 5 As shown, the method includes:

[0065] In step S502, the target edge execution node receives multiple objects to be deployed distributed by the target edge management node. These multiple objects logically belong to the same deployment group, and the deployment information corresponding to the deployment group is sent from the central management node to the target edge management node in response to a deployment trigger command. Subsequently, the target edge management node, after obtaining the grouping information and the multiple objects to be deployed based on the deployment information, distributes these objects to the target edge execution node based on the grouping information.

[0066] In step S504, the target edge execution node deploys and runs the received multiple objects to be deployed locally. In specific implementations, the target edge execution node can automatically configure shared resources (such as shared storage volumes and shared virtual networks) locally based on the collaborative control strategy issued along with the objects to be deployed, and strictly follow the startup order determined by the runtime dependencies to jointly start and collaboratively run each object to be deployed, thereby executing the business logic defined in the cloud on the physical device side.

[0067] It should be noted that the foregoing embodiments are combined with Figure 1 , Figure 2 And various exemplary implementation methods, technical details, optional solutions, alternative implementation methods, and corresponding technical effects described in specific application scenarios (such as the "AI" group and the "IIH" group) (including but not limited to: the multi-dimensional construction basis of deployment groups, dynamic management mechanisms such as dynamic modification and deletion recovery of deployment group members, the trigger source and trigger mechanism of one-click deployment commands, the configuration and distribution of runtime dependencies and version information, and the joint startup order determined based on runtime dependencies, etc.), can all be applied to the methods applied to the deployment objects of the central management node 20 (such as...) provided that no logical conflict occurs. Figure 3 (as shown), the method applied to the deployment object of the target edge management node 30a (such as...) Figure 4 (as shown) and the method applied to the deployment object of the target edge execution node 40a (such as... Figure 5 As shown in the diagram. Specifically, the logical steps, data processing, state storage, and control mechanisms executed unilaterally by the central management node 20, the target edge management node 30a, or the target edge execution node 40a in the aforementioned collaborative interaction process have a mirror-symmetric correspondence in the corresponding steps of the single-end process. For example, the technical details in the aforementioned scheme regarding the central management node 20's dynamic management of deployment groups in response to instructions and the generation of deployment information containing runtime dependencies correspond to... Figure 3 Detailed execution methods for steps S302 and S304; the technical details in the aforementioned scheme regarding the reconstruction and deployment of the target edge management node 30a in local storage, parsing and distributing runtime dependencies, etc., are respectively used as... Figure 4 The detailed execution methods of steps S402 to S406; the technical details in the aforementioned scheme regarding the determination of the startup order of the target edge execution node 40a based on runtime dependencies, etc., are respectively used as... Figure 5 The detailed execution methods for steps S502 to S504 are described below. This corresponding application ensures that each single-end method, whether operating independently or interfacing with incompatible third-party nodes, still achieves the technical effects corresponding to the aforementioned collaborative solution. This effectively avoids the engineering design flaw of a disconnect between single-end control logic and overall collaborative logic, significantly reduces the system cascading failure rate in multi-level industrial edge environments, and guarantees high reliability and flexibility for each single-end node during actual deployment and maintenance.

[0068] Figure 7 This is a structural diagram of a computing device according to an embodiment of the present disclosure. (As shown) Figure 7 As shown, the computing device 700 includes a memory 702, a processor 704, and a bus 706 connecting the two. The memory 702 stores a computer program, which, when called and executed by the processor 704, enables the implementation of the specific method steps described above for the central management node 20.

[0069] Furthermore, embodiments of this disclosure also provide a computing device corresponding to the target edge management node 30a. This computing device includes a memory and a processor. The memory stores a computer program, and when the processor calls and executes the computer program, it can implement the specific method steps described above for the target edge management node 30a. Embodiments of this disclosure also provide a computing device corresponding to the target edge execution node 40a. This computing device includes a memory and a processor. The memory stores a computer program, and when the processor calls and executes the computer program, it can implement the specific method steps described above for the target edge execution node 40a.

[0070] In this disclosure, the computing device (or computing platform) is a broad concept of a computing system. Specifically, the computing device (or computing platform) includes, but is not limited to: physical entities such as a single physical server, a server cluster consisting of multiple servers, an industrial control computer (ICC), a personal computer (PC), a workstation, or a dedicated hardware control terminal; virtualization and cloud environments such as virtual machines, containers (e.g., Docker containers), virtualization clusters, public cloud platforms, private cloud platforms, and hybrid cloud platforms; and novel computing architectures such as serverless architecture (e.g., Function as a Service, FaaS) and distributed computing networks. Any hardware entity or logical set capable of providing storage, data processing, network communication, and running the relevant program code of the central management node falls within the scope of the computing device (or computing platform) described in this disclosure.

[0071] This disclosure also provides a computer program product, including computer instructions that instruct a computing device to perform any corresponding operation in the above-described plurality of method embodiments.

[0072] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this disclosure can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this disclosure.

[0073] The methods described above according to embodiments of this disclosure can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as a CD-ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be processed by software stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA). It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., RAM, ROM, flash memory, etc.) capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods described herein. Furthermore, when a general-purpose computer accesses code used to implement the methods shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for performing the methods shown herein.

[0074] It should be noted that not all steps and modules in the above processes and system structure diagrams are mandatory; some steps or modules can be omitted as needed. The execution order of each step is not fixed and can be adjusted as required. The system structure described in the above embodiments can be a physical structure or a logical structure. That is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or they may be jointly implemented by certain components in multiple independent devices.

[0075] In this patent application, nouns and pronouns relating to persons are not limited to specific genders. 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 limitation, 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.

[0076] In the above embodiments, the hardware modules can be implemented mechanically or electrically. For example, a hardware module may include permanent, dedicated circuitry or logic (such as a dedicated processor, FPGA, or ASIC) to perform the corresponding operations. The hardware module may also include programmable logic or circuitry (such as a general-purpose processor or other programmable processor), which can be temporarily configured by software to perform the corresponding operations. The specific implementation method (mechanical, dedicated, permanent circuitry, or temporarily configured circuitry) can be determined based on cost and time considerations.

[0077] The present disclosure has been described and illustrated in detail above with reference to the accompanying drawings and preferred embodiments. However, the present disclosure is not limited to the specific embodiments disclosed above. Those skilled in the art should understand that, without departing from the core concept of the present disclosure, reasonable cross-combinations, splits, or equivalent substitutions can be made of the various technical features in the different embodiments described above. All equivalent or alternative technical solutions derived therefrom should fall within the protection scope of the present disclosure.

Claims

1. A method for deploying objects, characterized in that, The method includes: In the central management node, deployment groups are created for multiple objects to be deployed; In response to a deployment trigger command for the deployment group, the deployment information corresponding to the deployment group is sent to at least one target edge management node; The target edge management node receives the deployment information and obtains the grouping information of the deployment group and the multiple objects to be deployed based on the deployment information; Based on the grouping information, the target edge management node distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node.

2. The method according to claim 1, characterized in that, The deployment information includes: the plurality of objects to be deployed, or information for obtaining the plurality of objects to be deployed; and grouping information of the deployment groups; The method further includes: Before the target edge management node distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node, the deployment group is reconstructed in the local storage of the target edge management node based on the grouping information and the plurality of objects to be deployed; The target edge management node distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information, including: distributing the plurality of objects to be deployed to the at least one target edge execution node in response to a deployment instruction triggered for the deployment group.

3. The method according to claim 1, characterized in that, In the central management node, deployment groups are constructed for multiple objects to be deployed, including: In the central management node, the deployment group is constructed for the multiple objects to be deployed based on at least one of the target application scenario, the functional attributes of the objects to be deployed, user-defined rules, and the relationship between the deployed objects.

4. The method according to claim 1, characterized in that, The method further includes managing the deployment group, the management including at least one of the following: In response to a member modification instruction for the deployment group, add or remove the object to be deployed from the deployment group; In response to the rename instruction, the name of the deployment group is modified; In response to a deletion command for the deployment group, the deployment group is deleted, and each of the objects to be deployed that originally belonged to the deployment group is restored to an independent object to be deployed.

5. The method according to claim 1, characterized in that, The deployment trigger command is a one-click deployment command triggered by a single user operation targeting the deployment group.

6. The method according to claim 1, characterized in that, The deployment information also includes version information of the plurality of objects to be deployed, and at least one of the runtime dependencies between the plurality of objects to be deployed.

7. The method according to claim 6, characterized in that, The method further includes: Distribute the runtime dependencies to the target edge execution nodes; When the target edge execution node jointly starts up multiple objects to be deployed after distribution, it determines the startup order of the multiple objects to be deployed based on the runtime dependencies.

8. The method according to any one of claims 1-7, characterized in that, The objects to be deployed include at least one of the following: an application, an application update package, a container image, an algorithm model file, a device configuration file, and an authorization license.

9. A method for deploying objects, characterized in that, The method is applied to the central management node and includes: Build deployment groups for multiple objects to be deployed; In response to a deployment trigger command for the deployment group, deployment information corresponding to the deployment group is sent to at least one target edge management node, so that the target edge management node obtains the grouping information of the deployment group and the plurality of objects to be deployed based on the deployment information, and distributes the plurality of objects to be deployed to at least one target edge execution node connected to the target edge management node based on the grouping information.

10. A method for deploying objects, characterized in that, The method is applied to the target edge management node, including: The system receives deployment information corresponding to a deployment group issued by the central management node. The deployment group is constructed by the central management node for multiple objects to be deployed. The deployment information is issued by the central management node in response to a deployment trigger command after the deployment group is constructed. Based on the deployment information, obtain the grouping information of the deployment group and the multiple objects to be deployed; Based on the grouping information, the plurality of objects to be deployed are distributed to at least one target edge execution node connected to the target edge management node.

11. A method for deploying objects, characterized in that, The method is applied to the target edge execution node, including: The system receives multiple objects to be deployed distributed by the target edge management node. The multiple objects to be deployed belong to a deployment group. The deployment information corresponding to the deployment group is sent from the central management node to the target edge management node in response to the deployment trigger command. The target edge management node obtains the grouping information of the deployment group and the multiple objects to be deployed based on the deployment information, and then distributes them to the target edge execution node based on the grouping information. The multiple objects to be deployed are deployed and run locally.

12. A system for deploying objects, characterized in that, The system includes a central management node, at least one target edge management node, and at least one target edge execution node connected to the target edge management node; The central management node is used to execute the method as described in claim 9; The target edge management node is used to perform the method as described in claim 10; The target edge execution node is used to execute the method as described in claim 11.

13. A computing device, characterized in that, The computing device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the method as described in claim 9.

14. A computing device, characterized in that, The computing device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the method as described in claim 10.

15. A computing device, characterized in that, The computing device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the method as described in claim 11.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 9 to 11.

Images