Application deployment methods, devices, and storage media

By automatically acquiring and encapsulating dependency information and executable files from edge devices via cloud devices, efficient and accurate deployment of applications on devices that do not support containerization technology is achieved, solving the problems of high dependency information complexity and low deployment efficiency in existing technologies.

CN123114490APending Publication Date: 2026-11-17RICHFIT INFORMATION TECH +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510619150.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-14
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, edge devices that do not support containerization technology have high dependency complexity, low accuracy of manual configuration, and low deployment efficiency when deploying applications.

Method used

Cloud devices automatically obtain target dependency information and executable files adapted to edge devices through deployment commands, package them into an installation package, and send them to edge devices for automated deployment, which is suitable for native system architectures.

Benefits of technology

It improves the accuracy and efficiency of application deployment on different hardware architectures and operating system versions, reduces installation package size and transmission time, and is suitable for edge environments with limited network bandwidth.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114490A_ABST
    Figure CN123114490A_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, and storage medium for deploying an application. The method is applied to a cloud-edge collaborative system, which includes a cloud device and an edge device. The edge device deploys the application based on a native system architecture. The method includes: responding to a deployment command, determining the application to be installed and a target edge device; obtaining target dependency information adapted to the target edge device and an executable file of the application to be installed; encapsulating the executable file and the target dependency information into an installation package; and sending the installation package to the target edge device. The target edge device deploys the application to be installed according to the installation package. This method aims to improve the efficiency and accuracy of application deployment.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of edge computing technology, and in particular to a method, apparatus and storage medium for deploying an application. Background Technology

[0002] With the development of cloud computing and edge computing technologies, cloud-edge collaborative architecture has gradually become the mainstream solution for handling large-scale distributed systems. In this architecture, container images are typically used to deploy applications between cloud devices and edge devices to meet computing needs in different scenarios.

[0003] In related technologies, the Kubernetes container orchestration system can be applied to cloud devices, and the kubeedge edge computing extension can be applied to edge devices, thereby enabling application deployment on edge devices based on containers. However, this approach requires that the edge devices support containerization technology. For edge devices that do not support containerization technology, the common method is to manually configure application dependencies, but the dependency information is complex, the accuracy of manual configuration is low, and the deployment efficiency is low. Summary of the Invention

[0004] This application provides a method, apparatus, and storage medium for deploying applications, thereby improving the efficiency and accuracy of application deployment.

[0005] In a first aspect, embodiments of this application provide a method for deploying an application, the method being applied to a cloud device in a cloud-edge collaborative system, the cloud-edge collaborative system including a cloud device and an edge device, the edge device implementing application deployment based on a native system architecture; including:

[0006] In response to deployment instructions, determine the applications to be installed and the target edge devices;

[0007] Obtain the target dependency information adapted to the target edge device and the executable file of the application to be installed;

[0008] The executable file and the target dependency information are packaged into an installation package;

[0009] The installation package is sent to the target edge device; wherein the target edge device is used to deploy the application to be installed according to the installation package.

[0010] In one possible implementation, the deployment instruction is used to instruct the application to be installed to the target edge device; or, the deployment instruction is used to instruct the application to be installed in a preset deployment mode, which is either a fresh deployment or an overwrite deployment.

[0011] In one possible implementation, the deployment instruction is used to instruct the application to be installed to be installed in a preset deployment manner, and the step of determining the application to be installed and the target edge device in response to the deployment instruction includes:

[0012] In response to the deployment command, an application installation list is obtained; wherein, the application installation list represents information about applications installed on the edge device;

[0013] The target edge device is determined based on the application to be installed as indicated by the deployment instruction, the deployment method, and the application installation list.

[0014] In one possible implementation, the deployment method is a fresh deployment, and the step of determining the target edge device based on the application to be installed indicated by the deployment instruction, the deployment method, and the application installation list includes:

[0015] Based on the deployment method, edge devices that do not have the application to be installed installed are selected from the application installation list and used as target edge devices.

[0016] In one possible implementation, the deployment method is overlay deployment, and determining the target edge device based on the application to be installed indicated by the deployment instruction, the deployment method, and the application installation list includes:

[0017] Based on the deployment method, edge devices that have the application to be installed installed are selected from the application installation list and used as target edge devices.

[0018] In one possible implementation, when the deployment method is an overlay deployment, the deployment instruction is further used to indicate a sub-method of the overlay deployment, wherein the sub-method of the overlay deployment is an alternative deployment or a parallel deployment; the method further includes:

[0019] Based on the sub-method of the coverage deployment, generate the description file of the application to be installed;

[0020] Add the description file to the installation package.

[0021] In one possible implementation, the target edge device is configured to replace the old installation package with the new installation package according to the replacement deployment indicated in the description file; or...

[0022] The target edge device is used to store the installation package in a directory other than the directory where the old installation package is located, according to the parallel deployment indicated in the description file.

[0023] In one possible implementation, obtaining target dependency information adapted to the target edge device includes:

[0024] Obtain the environmental information of the target edge device, and the initial dependency information required by the application to be installed;

[0025] The target dependency information is determined based on the environmental information and the initial dependency information.

[0026] In one possible implementation, the installation package further includes management scripts, which include installation scripts, uninstallation scripts, startup scripts, and stop scripts; the method further includes:

[0027] Send a scheduling instruction; wherein the scheduling instruction is an installation instruction, an uninstallation instruction, a start instruction, or a stop instruction; the target edge device is used to respond to the scheduling instruction, call the management script corresponding to the scheduling instruction, process the application to be installed, and return the processing result.

[0028] Secondly, embodiments of this application provide an application deployment apparatus, which is applied to a cloud device in a cloud-edge collaborative system. The cloud-edge collaborative system includes a cloud device and an edge device, and the edge device implements application deployment based on a native system architecture; including:

[0029] The determination module is used to determine the application to be installed and the target edge device in response to deployment instructions;

[0030] The acquisition module is used to acquire target dependency information adapted to the target edge device and the executable file of the application to be installed;

[0031] A packaging module is used to package the executable file and the target dependency information into an installation package;

[0032] A sending module is used to send the installation package to the target edge device; wherein the target edge device is used to deploy the application to be installed according to the installation package.

[0033] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0034] The memory stores computer-executed instructions;

[0035] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0036] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0037] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0038] The application deployment method, apparatus, and storage medium provided in this application embodiment, when deploying an application on an edge device based on its native system architecture, allow the cloud device to determine the application to be installed and the target edge device via deployment instructions. It can then determine the target dependency information adapted to the target edge device and the executable file of the application to be installed, ensuring the application can run on the target edge device. The target dependency information and executable file are then packaged into an installation package and sent to the target edge device, enabling the target edge device to automatically deploy the application based on the installation package. In this way, on the one hand, the cloud device can automatically obtain the adapted target dependency information according to the native system architecture of the target edge device, ensuring that the application to be installed can run normally on edge devices with different hardware architectures and operating system versions, improving deployment accuracy. Furthermore, the cloud device can automatically match and package, improving deployment efficiency. On the other hand, by only obtaining and packaging the dependency information required by the target edge device, compared to containerized deployment, the installation package size is relatively small, and the transmission time and bandwidth consumption are correspondingly reduced, accelerating the application deployment speed and making it more suitable for edge environments with limited network bandwidth. Attached Figure Description

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

[0040] Figure 1 A schematic diagram illustrating one application scenario provided in this application;

[0041] Figure 2 A flowchart illustrating the deployment method of the application provided in this application. Figure 1 ;

[0042] Figure 3 A schematic diagram of a front-end interface provided for this application;

[0043] Figure 4 A schematic diagram of another front-end interface provided for this application;

[0044] Figure 5A flowchart illustrating the deployment method of the application provided in this application. Figure 2 ;

[0045] Figure 6 A schematic diagram of the structure of the deployment device for the application provided in this application;

[0046] Figure 7 A schematic diagram of the structure of the electronic device provided in this application.

[0047] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0049] In related technologies, deploying containers on edge devices enables applications to be deployed on edge devices in different system environments. However, some edge devices may not support containerization technology due to hardware resource limitations. In this case, applications often need to manually configure their dependencies, but the dependency information is complex, the accuracy of manual configuration is low, and the deployment efficiency is low.

[0050] In view of this, this application provides a method for deploying an application. When the application is deployed on the edge device based on the native system architecture, the cloud device can automatically obtain the dependency information and executable file adapted to the system environment of the edge device based on the user's instructions, package them, and send them to the corresponding edge device for automated installation. The dependency information does not need to be manually configured, which improves the deployment efficiency and accuracy of the application.

[0051] Figure 1 A schematic diagram illustrating an application scenario provided in this application, such as... Figure 1 As shown, the cloud-edge collaborative system includes cloud devices and multiple edge devices. It should be noted that... Figure 1 The following is an example illustrating the concept of three edge devices.

[0052] The aforementioned cloud-based device is used to manage edge devices, such as managing their registration, authentication, and status monitoring (e.g., online / offline status, load conditions); and distributing application installation packages, configuration updates, and policy commands. This cloud-based device can be a server or a server cluster.

[0053] The aforementioned edge device is used for computational processing. This edge device can be a computing device with processing capabilities, such as a gateway, server, or terminal; this application embodiment does not limit the type of edge device. This edge device implements application deployment based on a native system architecture; in other words, it does not support containerization technology. Here, native system architecture refers to a mode of software development and deployment that is based on the underlying architecture of the device hardware platform and operating system, directly utilizing the system's native capabilities (such as kernel, drivers, APIs, etc.) without introducing additional abstraction layers or runtime environments; the application runs directly on top of the operating system.

[0054] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0055] Figure 2 A flowchart illustrating the deployment method of the application provided in this application. Figure 1 ,refer to Figure 1 and Figure 2 As shown, the method includes:

[0056] S201. The cloud device responds to the deployment command and determines the application to be installed and the target edge device.

[0057] For example, the application to be installed represents an application that needs to be installed or deployed to an edge device. It can be an independent functional module, such as a data acquisition program or an intelligent analysis algorithm program, or it can be a complete application system. This application embodiment does not limit the function and number of applications to be installed. It should be noted that the application to be installed can be a script-driven application; in other words, a script needs to be called to manage the application, such as calling a script to install the application.

[0058] The aforementioned target edge device represents an edge device that requires the application to be installed. This edge device is based on a native system architecture, meaning it runs directly on the device's underlying operating system and does not rely on containerization technology. The aforementioned deployment command is used to trigger the deployment operation of the application. This deployment command can be triggered by the user manually selecting the application to be installed through the front-end interface, or it can be automatically triggered by a scheduled task or API call, etc. This embodiment of the application does not limit this.

[0059] In one example, the deployment instruction may carry the identifier of the application to be installed and the identifier of the target edge device. The identifier of the application to be installed is used to uniquely identify the application, and can be the application's ID, name, or version number, etc.; the identifier of the target edge device is used to uniquely identify the edge device, and can be the edge device's ID, host number, IP address, or MAC address, etc. For example, the user manually selects the ID of the application to be installed and the ID of the target edge device through the front-end interface, thereby generating the deployment instruction. Therefore, the cloud device can determine the application to be installed and the target edge device based on the application ID and the target edge device ID by parsing the deployment instruction.

[0060] In another example, the deployment instruction may carry the identifier of the application to be installed and the deployment method. The deployment method characterizes how the application will be deployed, such as a fresh deployment (deploying to an edge device that has not been installed before) or an overwrite deployment (deploying to an edge device that has already been installed). Therefore, after the cloud device parses the deployment instruction to determine the application to be installed and the deployment method, it can determine the target edge device based on the deployment method. For example, it can obtain information about the applications already installed on each edge device and then determine the target edge device based on the deployment method.

[0061] Optionally, after identifying the target edge device, the cloud device can obtain the status information of each target edge device, including the status information of computing resources, network resources, storage resources, etc. If it is determined from the status information of the target edge device that the target edge device does not meet the running conditions of the application to be installed, then the target edge device is removed.

[0062] S202. The cloud device obtains target dependency information and executable files of the application to be installed that are adapted to the target edge device.

[0063] For example, target dependency information refers to the external resources and conditions necessary for the application to be installed to run on the target edge device. These may include operating system version, hardware drivers, system library files, environment variables, etc., and the target dependency information must be compatible with the native system architecture of the target edge device to ensure that the application can run normally.

[0064] The executable file of the application to be installed is a program file that can be directly loaded and executed by the operating system. This executable file contains all the instructions and data required for the program to run, enabling the computer to perform specific tasks or operations. Similarly, the executable file of the application to be installed also needs to be compatible with the native system architecture of the target edge device. The format of executable files may differ between different operating systems; therefore, it is necessary to obtain an executable file of the application to be installed that is compatible with the target edge device.

[0065] In one example, the cloud device can pre-define a resource library, which can represent the correspondence between applications, edge device environment information, dependency information, and executable files. The environment information may include the edge device's hardware architecture, operating system version, etc. For example, Table 1 illustrates a resource library provided in an embodiment of this application.

[0066] Table 1 Resource Library

[0067]

[0068] Therefore, cloud devices can determine the environment information of the target edge device based on preset environment information of the edge devices, and then retrieve target dependency information adapted to the target edge device from a preset resource library based on the target edge device's environment information. For example, for a target edge device running a Linux system on an ARM architecture, the cloud device will retrieve dependency library files (dependency information) suitable for that architecture and system. It can also retrieve executable files of the application to be installed on the target edge device from a preset resource library based on the target edge device's environment information.

[0069] S203. The cloud device encapsulates the executable file and target dependency information into an installation package.

[0070] For example, cloud devices have pre-defined installation package packaging rules. Based on these rules, a packaging tool is used to package the executable file and its dependencies into an installation package. It should be noted that this application embodiment does not limit how the package is formed into an installation package. Optionally, the installation package may also include configuration files, databases, and other resource information, as well as management scripts such as installation scripts, uninstallation scripts, stop scripts, and start scripts. This application embodiment does not limit these aspects.

[0071] S204. The cloud device sends the installation package to the target edge device.

[0072] For example, a cloud device sends an installation package to a target edge device, which then uses the package to automatically deploy the application to be installed. For instance, the target edge device can invoke an installation script within the package to install the application.

[0073] Optionally, the cloud device can send scheduling instructions to the target edge device. These instructions are used to manage the application and can be installation, uninstallation, startup, or shutdown commands. As mentioned earlier, the installation package may include management scripts such as installation scripts, uninstallation scripts, shutdown scripts, and startup scripts. The target edge device responds to the scheduling instructions by calling the corresponding management scripts, processing the application to be installed, and returning the processing result. This result could be, for example, an installation result (successful or failed), an uninstallation result (successful or failed), a shutdown result (successful or failed), or a startup result (successful or failed).

[0074] For example, in response to an installation command, the target edge device calls the installation script, installs the application to be installed, and returns the installation result.

[0075] After the application to be installed is installed, the target edge device responds to the uninstall command by calling the uninstall script to uninstall the application and returns the uninstall result.

[0076] After the application to be installed is installed, the target edge device responds to the startup command, calls the startup script, starts the application to be installed, and returns the startup result.

[0077] After the application to be installed is launched, the target edge device responds to the stop command by calling the stop script, stopping the application to be installed, and returning the stop result.

[0078] Optionally, the cloud device can also send monitoring commands, and the target edge device responds to the monitoring commands by returning application status information, which may include CPU usage, memory usage, startup time, etc.

[0079] In this way, cloud devices can flexibly schedule and manage applications based on scheduling instructions and management scripts, reducing the difficulty of application scheduling.

[0080] The application deployment method provided in this application embodiment allows the cloud device to determine the application to be installed and the target edge device through deployment instructions when the application is deployed on the edge device based on the native system architecture. After determining the application to be installed and the target edge device, the cloud device can determine the target dependency information adapted to the target edge device and the executable file of the application to be installed, ensuring that the application can run on the target edge device. Then, the target dependency information and the executable file are packaged into an installation package and sent to the target edge device, so that the target edge device can automatically deploy the application to be installed based on the installation package.

[0081] This approach offers several advantages. First, cloud devices can automatically obtain appropriate target dependency information based on the native system architecture of the target edge device, ensuring that the application to be installed can run normally on edge devices with different hardware architectures and operating system versions, thus improving deployment accuracy. Furthermore, cloud devices can automatically match and package the dependencies, enhancing deployment efficiency. Second, by only acquiring and packaging the dependency information required by the target edge device, compared to containerized deployment, the installation package size is relatively small, and transmission time and bandwidth consumption are correspondingly reduced, accelerating application deployment and making it more suitable for edge environments with limited network bandwidth.

[0082] In some embodiments, deployment instructions are used to instruct the application to be installed to the target edge device. For example, Figure 3 A schematic diagram of a front-end interface provided for this application, such as... Figure 3 As shown, users can select the identifier of the application to be installed and the identifier of the target edge device based on the selection controls provided on the front-end interface. By triggering the confirmation control, a deployment instruction including the identifier of the application to be installed and the identifier of the target edge device is generated.

[0083] In some embodiments, the deployment instruction is used to instruct the application to be installed in a preset deployment manner, which is either a fresh deployment or an overwrite deployment. A fresh deployment indicates deployment on an edge device that has never been installed before, while an overwrite deployment indicates deployment on an edge device that has already been installed. For example, Figure 4 An illustration of another front-end interface provided for this application, such as... Figure 4 As shown, users can select the identifier and deployment method of the application to be installed based on the selection controls provided on the front-end interface. By triggering the confirmation control, a deployment instruction including the identifier and deployment method of the application to be installed is generated.

[0084] Optional, see reference Figure 4As shown, the deployment instructions also specify the sub-methods of overlay deployment, which can be either replacement deployment or parallel deployment. Replacement deployment directly replaces the old installation package; in other words, the installation package of the application to be installed and the old installation package are stored in the same directory. Parallel deployment allows the two applications to run in parallel to ensure a smooth transition of application data; in other words, the installation package of the application to be installed and the old installation package are stored in different directories. The cloud device can generate a description file for the application to be installed based on the sub-method of overlay deployment and add the description file to the installation package.

[0085] For example, the target edge device is configured to replace the old installation package with the new installation package according to the replacement deployment indicated in the description file after receiving the installation package; or, the target edge device is configured to store the installation package in a directory other than the directory where the old installation package is located according to the parallel deployment indicated in the description file after receiving the installation package.

[0086] The application deployment method provided in this application embodiment provides a visual front-end interface for application deployment on a cloud device. Users can flexibly configure application deployment schemes based on the front-end interface, which facilitates application deployment and improves the flexibility and convenience of deployment.

[0087] Figure 5 A flowchart illustrating the deployment method of the application provided in this application. Figure 2 ,like Figure 5 As shown, in this embodiment... Figure 2 Based on the embodiments, taking the deployment instruction used to instruct the installation of the application to be installed in a preset deployment mode as an example, the deployment method of the application is described in detail. The method includes:

[0088] S301, the cloud device responds to the deployment command and obtains the application installation list.

[0089] For example, the application installation list represents information about applications installed on edge devices. This list may include the identifier of the edge device, the identifier of the installed application, and version information of the installed application. One possible implementation is that the cloud device can periodically communicate with each edge device to obtain information about the applications installed on each edge device and construct the application installation list. Another possible implementation is that the application installation list can be imported from an external device, such as a USB flash drive.

[0090] S302. The cloud device determines the target edge device based on the application to be installed, the deployment method, and the application installation list indicated by the deployment instructions.

[0091] For example, as mentioned above, the deployment instruction in this embodiment is used to instruct the application to be installed in a preset deployment mode. This deployment mode can be a new deployment or an overwrite deployment. Therefore, the target edge device can be determined according to the deployment mode.

[0092] One possible implementation is to select edge devices that do not have the application to be installed from the application installation list as target edge devices when the deployment method is a fresh deployment.

[0093] Another possible implementation is to select edge devices with the application to be installed from the application installation list as target edge devices when the deployment method is overlay deployment.

[0094] S303: The cloud device obtains the executable file of the application to be installed, which is adapted to the target edge device.

[0095] It should be noted that this step is similar to the aforementioned step S202, and will not be repeated here.

[0096] S304. The cloud device obtains environmental information of the target edge device, as well as the initial dependency information required by the application to be installed.

[0097] For example, the cloud device can communicate with the target edge device to obtain the target edge device's environment information, which may include the target edge device's hardware architecture, operating system version, configured dependency information, etc. Simultaneously, the initial dependency information required by the application to be installed under this environment information is determined from a preset resource library. Referring to Table 1, the initial dependency information required by application 1 under environment 1 is information 1.

[0098] S305. The cloud device determines the target dependency information based on the environmental information and the initial dependency information.

[0099] For example, target dependency information represents the initial dependencies required by the application to be installed that are not configured on the target edge device. Therefore, the cloud device can compare the configured dependency information and the initial dependency information included in the environment information of the target edge device to determine the initial dependency information that is not configured on the target edge device as the target dependency information. In this way, the cloud device can package only the dependency information that is not configured on the target edge device, reducing the size of the installation package and improving transmission efficiency.

[0100] S306, Cloud devices encapsulate executable files and target dependency information into an installation package.

[0101] It should be noted that this step is similar to the aforementioned step S203, and will not be repeated here.

[0102] S307, The cloud device sends the installation package to the target edge device.

[0103] It should be noted that this step is similar to the aforementioned step S204, and will not be repeated here.

[0104] S308, cloud device sends installation instructions.

[0105] For example, cloud devices can receive instructions triggered by users or scheduled tasks and generate the installation instructions.

[0106] S309. The target edge device responds to the installation command, calls the installation script, installs the application to be installed, and obtains the installation result.

[0107] S310, The target edge device returns the installation result.

[0108] The application deployment method provided in this application embodiment, when deploying an application on an edge device based on a native system architecture, involves the cloud device responding to a deployment command by first obtaining an application installation list. Based on the application to be installed and the deployment method indicated by the deployment command, the cloud device identifies the target edge device and obtains the executable file of the application to be installed, adapted to the target edge device. Simultaneously, based on the environment information of the target edge device and the initial dependency information of the application to be installed, the cloud device determines the target dependency information. The executable file and the target dependency information are then packaged into an installation package and sent to the target edge device. An installation command is sent to the target edge device, enabling it to automatically install the application by calling the installation script within the installation package. This method allows the cloud device to precisely adapt and deploy to the target edge device based on the deployment method indicated in the deployment command, improving deployment accuracy. Furthermore, it allows the cloud device to encapsulate dependency information not configured by the target edge device during installation, reducing redundant distribution of dependency information, improving transmission efficiency, and ultimately enhancing deployment efficiency.

[0109] Figure 6 A schematic diagram of the structure of the application deployment device provided in this application is shown below. Figure 6 As shown, the application deployment device 400 provided in this embodiment includes:

[0110] Module 401 is used to determine the application to be installed and the target edge device in response to a deployment command;

[0111] The acquisition module 402 is used to acquire target dependency information adapted to the target edge device and the executable file of the application to be installed;

[0112] The packaging module 403 is used to package the executable file and the target dependency information into an installation package;

[0113] The sending module 404 is used to send the installation package to the target edge device; wherein the target edge device is used to deploy the application to be installed according to the installation package.

[0114] In one possible implementation, the deployment instruction is used to instruct the application to be installed to the target edge device; or, the deployment instruction is used to instruct the application to be installed in a preset deployment mode, which is either a fresh deployment or an overwrite deployment.

[0115] In one possible implementation, the deployment instruction is used to instruct the application to be installed to be installed in a preset deployment manner, and the determining module 401 is specifically used for:

[0116] In response to the deployment command, an application installation list is obtained; wherein, the application installation list represents information about applications installed on the edge device;

[0117] The target edge device is determined based on the application to be installed as indicated by the deployment instruction, the deployment method, and the application installation list.

[0118] In one possible implementation, the deployment method is a completely new deployment, and module 401 is specifically used for:

[0119] Based on the deployment method, edge devices that do not have the application to be installed installed are selected from the application installation list and used as target edge devices.

[0120] In one possible implementation, the deployment method is overlay deployment, and the determination module 401 is specifically used for:

[0121] Based on the deployment method, edge devices that have the application to be installed installed are selected from the application installation list and used as target edge devices.

[0122] In one possible implementation, when the deployment method is an overlay deployment, the deployment instruction is further used to indicate a sub-method of the overlay deployment, wherein the sub-method of the overlay deployment is a replacement deployment or a parallel deployment; the apparatus further includes an adding module, used for:

[0123] Based on the sub-method of the coverage deployment, generate the description file of the application to be installed;

[0124] Add the description file to the installation package.

[0125] In one possible implementation, the target edge device is configured to replace the old installation package with the new installation package according to the replacement deployment indicated in the description file; or...

[0126] The target edge device is used to store the installation package in a directory other than the directory where the old installation package is located, according to the parallel deployment indicated in the description file.

[0127] In one possible implementation, the acquisition module 402 is specifically used for:

[0128] Obtain the environmental information of the target edge device, and the initial dependency information required by the application to be installed;

[0129] The target dependency information is determined based on the environmental information and the initial dependency information.

[0130] In one possible implementation, the installation package further includes management scripts, which include installation scripts, uninstallation scripts, startup scripts, and stop scripts; the sending module 404 is further configured to:

[0131] Send a scheduling instruction; wherein the scheduling instruction is an installation instruction, an uninstallation instruction, a start instruction, or a stop instruction; the target edge device is used to respond to the scheduling instruction, call the management script corresponding to the scheduling instruction, process the application to be installed, and return the processing result.

[0132] The application deployment device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0133] Figure 7 A schematic diagram of the structure of the electronic device provided in this application. Figure 7 As shown, the electronic device 500 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the electronic device 500 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus. This electronic device can be a cloud device in the form of a server, or an edge device in the form of a gateway, server, or terminal.

[0134] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0135] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0136] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0137] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0138] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

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

[0140] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0141] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0142] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0143] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0144] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0145] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0147] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0148] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method of deploying an application program, characterized by, The method is applied to cloud devices in a cloud-edge collaborative system, which includes cloud devices and edge devices. The edge devices deploy applications based on a native system architecture. This includes: In response to deployment instructions, determine the applications to be installed and the target edge devices; Obtain the target dependency information adapted to the target edge device and the executable file of the application to be installed; The executable file and the target dependency information are packaged into an installation package; The installation package is sent to the target edge device; wherein the target edge device is used to deploy the application to be installed according to the installation package.

2. The method according to claim 1, characterized in that, The deployment instruction is used to instruct the application to be installed to the target edge device; or, the deployment instruction is used to instruct the application to be installed in a preset deployment mode, wherein the deployment mode is a new deployment or an overwrite deployment.

3. The method according to claim 1, characterized in that, The deployment instruction is used to instruct the application to be installed to be installed in a preset deployment mode. The step of determining the application to be installed and the target edge device in response to the deployment instruction includes: In response to the deployment command, an application installation list is obtained; wherein, the application installation list represents information about applications installed on the edge device; The target edge device is determined based on the application to be installed as indicated by the deployment instruction, the deployment method, and the application installation list.

4. The method according to claim 3, characterized in that, The deployment method is a fresh deployment. The step of determining the target edge device based on the application to be installed indicated by the deployment instruction, the deployment method, and the application installation list includes: Based on the deployment method, edge devices that do not have the application to be installed installed are selected from the application installation list and used as target edge devices.

5. The method according to claim 3, characterized in that, The deployment method is overlay deployment. Determining the target edge device based on the application to be installed indicated by the deployment instruction, the deployment method, and the application installation list includes: Based on the deployment method, edge devices that have the application to be installed installed are selected from the application installation list and used as target edge devices.

6. The method according to claim 5, characterized in that, When the deployment method is an overlay deployment, the deployment instruction is further used to indicate a sub-method of the overlay deployment, wherein the sub-method of the overlay deployment is a replacement deployment or a parallel deployment; the method further includes: Based on the sub-method of the coverage deployment, generate the description file of the application to be installed; Add the description file to the installation package.

7. The method according to claim 6, characterized in that, The target edge device is used to replace the old installation package with the new one according to the replacement deployment indicated in the description file; or, The target edge device is used to store the installation package in a directory other than the directory where the old installation package is located, according to the parallel deployment indicated in the description file.

8. The method according to any one of claims 1-7, characterized in that, The step of obtaining target dependency information adapted to the target edge device includes: Obtain the environmental information of the target edge device, and the initial dependency information required by the application to be installed; The target dependency information is determined based on the environmental information and the initial dependency information.

9. The method according to any one of claims 1-7, characterized in that, The installation package also includes management scripts, which include installation scripts, uninstallation scripts, startup scripts, and stop scripts; the method further includes: Send a scheduling instruction; wherein the scheduling instruction is an installation instruction, an uninstallation instruction, a start instruction, or a stop instruction; the target edge device is used to respond to the scheduling instruction, call the management script corresponding to the scheduling instruction, process the application to be installed, and return the processing result.

10. An application deployment apparatus, characterized in that, The device is applied to a cloud-edge collaborative system, which includes cloud devices and edge devices. The edge devices deploy applications based on a native system architecture. The system includes: The determination module is used to determine the application to be installed and the target edge device in response to deployment instructions; The acquisition module is used to acquire target dependency information adapted to the target edge device and the executable file of the application to be installed; A packaging module is used to package the executable file and the target dependency information into an installation package; A sending module is used to send the installation package to the target edge device; wherein the target edge device is used to deploy the application to be installed according to the installation package.

11. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-9.