Embodiments of the present invention provide an application upgrade method and an apparatus. The application upgrade method includes: receiving an application deployment request; determining a deployment package of a to-be-deployed application; determining that a version of a first platform node is below a version requirement of a node template of the to-be-deployment application for a first platform node template; acquiring a first platform node upgrade package that meets the version requirement of the node template of the to-be-deployed application for the first platform node template; upgrading the first platform node indicated by an identifier of the first platform node by using the first platform node upgrade package; determining an identifier of a to-be-upgraded application node; and upgrading the application node indicated by the identifier of the to-be-upgraded application node by using the deployment package of the to-be-deployed application.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. An application upgrade method performed by an application deployment server, the method comprising: receiving an application deployment request comprising a deployment package of a to-be-deployed application, wherein the deployment package describes a node template of the to-be-deployed application, an identifier of a deployed application to be upgraded by the to-be-deployed application, an identifier of a node template of the deployed application, an identifier of a first platform node template, and a version requirement of the first platform node template required by the node template of the to-be-deployed application; acquiring, according to the identifier of the deployed application, an identifier of a first platform node corresponding to the identifier of the first platform node template, and acquiring a version of the first platform node indicated by the identifier of the first platform node; wherein the to-be-deployed application runs based on a capability provided by the first platform node, and the first platform node is deployed prior to the to-be-deployed application according to the first platform node template; determining that the version of the first platform node is below the version requirement of the first platform node template required by the node template of the to-be-deployed application; acquiring a first platform node upgrade package that meets the version requirement in response to the determination result, wherein the first platform node upgrade package maintained by the application deployment server is acquired according to the version requirement of the first platform node template required by the node template of the to-be-deployed application; upgrading the first platform node indicated by the identifier of the first platform node by using the first platform node upgrade package; determining an identifier of a to-be-upgraded application node; and upgrading the application node after the first platform node is upgraded, wherein the application node is indicated by the identifier of the to-be-upgraded application node, and wherein the application node is upgraded using the deployment package carried in the application deployment request of the to-be-deployed application.
An application deployment server upgrades applications by first receiving a request containing a deployment package. This package describes the application to be deployed, identifies the application to be upgraded, specifies a required version for a platform node (a pre-existing software component), and links these components together. The server checks if the existing platform node meets the required version. If the platform node is out of date, the server retrieves an upgrade package for the platform node. After upgrading the platform node, the server upgrades the target application node using the deployment package provided in the initial request. This ensures compatibility between the application and the underlying platform.
2. The method according to claim 1 , wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and an upgrade identifier is carried in the relationship template; or the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and an upgrade identifier is carried in the node type implementation.
Building upon the application upgrade method of claim 1 (An application deployment server upgrades applications by first receiving a request containing a deployment package. This package describes the application to be deployed, identifies the application to be upgraded, specifies a required version for a platform node (a pre-existing software component), and links these components together. The server checks if the existing platform node meets the required version. If the platform node is out of date, the server retrieves an upgrade package for the platform node. After upgrading the platform node, the server upgrades the target application node using the deployment package provided in the initial request. This ensures compatibility between the application and the underlying platform), the deployment package also contains either a "relationship template" or a "node type implementation" that includes an "upgrade identifier". This identifier provides specific instructions or parameters related to the upgrade process, guiding the server on how to handle dependencies or configurations during the upgrade of application nodes or platform nodes.
3. The method according to claim 1 wherein the determining the identifier of the to-be-upgraded application node comprises: determining identifiers of all application nodes and corresponding to the identifier of the node template of the deployed application, as the identifier of the to-be-upgraded application node; or when the deployment package of the to-be-deployed application further comprises an identifier of at least one deployed application node and corresponding to the identifier of the node template of the deployed application, the determining the identifier of the to-be-upgraded application node comprises: determining the identifier of the at least one deployed application node corresponding to the identifier of the node template of the deployed application, and comprised in the application deployment package as the identifier of the to-be-upgraded application node.
Refining the application upgrade method of claim 1 (An application deployment server upgrades applications by first receiving a request containing a deployment package. This package describes the application to be deployed, identifies the application to be upgraded, specifies a required version for a platform node (a pre-existing software component), and links these components together. The server checks if the existing platform node meets the required version. If the platform node is out of date, the server retrieves an upgrade package for the platform node. After upgrading the platform node, the server upgrades the target application node using the deployment package provided in the initial request. This ensures compatibility between the application and the underlying platform), there are two ways to identify which application nodes need upgrading. One way is to upgrade *all* application nodes associated with the template of the application being upgraded. Alternatively, the deployment package can *explicitly* list the specific application node(s) that require upgrading, allowing for a more targeted upgrade process.
4. The method according to claim 1 , wherein before the upgrading the first platform node indicated by the identifier of the first platform node, the method further comprises: acquiring, according to the identifier of the deployed application, a stored description file of a deployment package of the deployed application; determining, according to the acquired description file of the deployment package of the deployed application, that the description file of the deployment package of the deployed application describes a second platform node template that uses the first platform node template as a source node template; acquiring a version requirement, of a second platform node, required by the upgraded first platform node for a second platform node, and a version of the second platform node; and determining that the version of the second platform node is below the version requirement, of a second platform node, required by the upgraded first platform node; and before the upgrading the first platform node by using the first platform node upgrade package, the method further comprises: acquiring in response to the determination result of which the version of the second platform node is below the version requirement, of a second platform node, required by the upgraded first platform node, a second platform node upgrade package that meets the version requirement, of a second platform node, required by the upgraded first platform node; and upgrading the second platform node according to the second platform node upgrade package.
Extending the application upgrade method of claim 1 (An application deployment server upgrades applications by first receiving a request containing a deployment package. This package describes the application to be deployed, identifies the application to be upgraded, specifies a required version for a platform node (a pre-existing software component), and links these components together. The server checks if the existing platform node meets the required version. If the platform node is out of date, the server retrieves an upgrade package for the platform node. After upgrading the platform node, the server upgrades the target application node using the deployment package provided in the initial request. This ensures compatibility between the application and the underlying platform), before upgrading a platform node, the server checks if other platform nodes *depend* on it. If so, it examines the version requirements of these dependent platform nodes *after* the first platform node is upgraded. If a dependent platform node's version is too old, the server acquires and applies an upgrade package to *that* dependent platform node *before* upgrading the original platform node. This cascading upgrade ensures all platform nodes remain compatible after the upgrade process.
5. An application deployment server, comprising: a receiver, configured to: receive an application deployment request comprising a deployment package of a to-be-deployed application, wherein the deployment package describes a node template of the to-be-deployed application, an identifier of a deployed application to be upgraded by the to-be-deployed application, an identifier of a node template of the deployed application, an identifier of a first platform node template, and a version requirement of the first platform node template required by the node template of the to-be-deployed application; and send the deployment package of the to-be-deployed application to a processor; and the processor, configured to: receive the deployment package of the to-be-deployed application sent by the receiver; acquire, according to the identifier of the deployed application, an identifier of a first platform node corresponding to the identifier of the first platform node template, and acquire a version of the first platform node indicated by the identifier of the first platform node; wherein the to-be-deployed application should be running based on a capability provided by the first platform node, and the first platform node is deployed prior to the to-be-deployed application according to the first platform node template; determine that the version of the first platform node is below the version requirement of the first platform node template required by the node template of the to-be-deployed application; acquire a first platform node upgrade package that meets the version requirement in response to the determination result, wherein the first platform node upgrade package maintained by the application deployment server is acquired according to the version requirement of the first platform node template required by the node template of to-be-deployed application; upgrade the first platform node indicated by the identifier of the first platform node template using the first platform node upgrade package; determine an identifier of a to-be-upgraded application node; and upgrade the application node after the first platform node is upgraded, wherein the application node is indicated by the identifier of the to-be-upgraded application node, and wherein the application node is upgraded using the deployment package carried in the application deployment request of the to-be-deployed application.
An application deployment server is designed to upgrade applications. It includes a receiver and a processor. The receiver gets an application deployment request with a deployment package. This package has information about the application to be deployed, the application to be upgraded, a platform node, and the platform node's version requirements. The processor checks if the platform node meets the version requirement. If not, it gets an upgrade package for the platform node and upgrades it. After the platform node upgrade, it identifies and upgrades the application node using the provided deployment package. The server ensures platform nodes meet dependency requirements, then upgrades application nodes.
6. The application deployment server according to claim 5 , wherein the deployment package of the to-be-deployed application further comprises a relationship template that describes the node template of the to-be-deployed application, and an upgrade identifier is carried in the relationship template; or the deployment package of the to-be-deployed application further comprises a node type implementation corresponding to the node template of the to-be-deployed application, and an upgrade identifier is carried in the node type implementation.
Improving the application deployment server from claim 5 (An application deployment server is designed to upgrade applications. It includes a receiver and a processor. The receiver gets an application deployment request with a deployment package. This package has information about the application to be deployed, the application to be upgraded, a platform node, and the platform node's version requirements. The processor checks if the platform node meets the version requirement. If not, it gets an upgrade package for the platform node and upgrades it. After the platform node upgrade, it identifies and upgrades the application node using the provided deployment package. The server ensures platform nodes meet dependency requirements, then upgrades application nodes), the deployment package contains either a "relationship template" or a "node type implementation" that includes an "upgrade identifier". This upgrade identifier provides specific upgrade instructions during the upgrade process, improving the server's ability to handle dependencies or configurations during application and platform node upgrades.
7. The application deployment server according to claim 6 wherein the processor is configured to determine identifiers of all application nodes and corresponding to the identifier of the node template of the deployed application, as the identifier of the to-be-upgraded application node; or when the deployment package of the to-be-deployed application further comprises an identifier of at least one deployed application node and corresponding to the identifier of the node template of the deployed application, the determining the identifier of the to-be-upgraded application node comprises: determining the identifier of the at least one deployed application node corresponding to the identifier of the node template of the deployed application, and comprised in the application deployment package as the identifier of the to-be-upgraded application node.
Concerning the application deployment server described in claim 5 (An application deployment server is designed to upgrade applications. It includes a receiver and a processor. The receiver gets an application deployment request with a deployment package. This package has information about the application to be deployed, the application to be upgraded, a platform node, and the platform node's version requirements. The processor checks if the platform node meets the version requirement. If not, it gets an upgrade package for the platform node and upgrades it. After the platform node upgrade, it identifies and upgrades the application node using the provided deployment package. The server ensures platform nodes meet dependency requirements, then upgrades application nodes), the processor can identify application nodes to upgrade in two ways. It can upgrade *all* application nodes related to the upgraded application's template. Alternatively, the deployment package can *explicitly* define which application nodes need upgrading, providing the processor with a specific list of application nodes to upgrade and allowing more targeted upgrades.
8. The application deployment server according to claim 5 , wherein the processor is further configured to: acquire, according to the identifier of the deployed application, a stored description file of a deployment package of the deployed application; determine, according to the acquired description file of the deployment package of the deployed application, that the description file of the deployment package of the deployed application describes a second platform node template that uses the first platform node template as a source node template; acquire a version requirement, of a second platform node, required by the upgraded first platform node for a second platform node, and a version of the second platform node; determine that the version of the second platform node is below the version requirement, of a second platform node, required by the upgraded first platform node; acquire in response to the determination result of which the version of the second platform node is below the version requirement, of a second platform node, required by the upgraded first platform node, a second platform node upgrade package that meets the version requirement, of a second platform node, required by the upgraded first platform node; and upgrade the second platform node according to the second platform node upgrade package.
Expanding on the application deployment server from claim 5 (An application deployment server is designed to upgrade applications. It includes a receiver and a processor. The receiver gets an application deployment request with a deployment package. This package has information about the application to be deployed, the application to be upgraded, a platform node, and the platform node's version requirements. The processor checks if the platform node meets the version requirement. If not, it gets an upgrade package for the platform node and upgrades it. After the platform node upgrade, it identifies and upgrades the application node using the provided deployment package. The server ensures platform nodes meet dependency requirements, then upgrades application nodes), the processor also checks for dependencies between platform nodes. Before upgrading a platform node, the processor determines if other platform nodes rely on it. If so, it checks the version requirements of these dependent platform nodes *after* the upgrade. If a dependent node's version is too low, the processor retrieves and applies an upgrade to *that* dependent node *before* upgrading the initial platform node, ensuring overall system compatibility through cascading upgrades.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
August 7, 2015
July 4, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.