A cloud service deployment method of a cloud platform and a related device thereof

Abstract

The application provides a cloud service deployment method of a cloud platform and related equipment, wherein when deploying a cloud service for a certain tenant, the influence of the remaining tenants can be considered, thereby realizing cross-tenant cloud service optimized deployment. The method of the application comprises: a cloud platform provides a service feature setting interface, the service feature setting interface is used to obtain supply-dependence relationships of different tenants. The cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a supplier based on the supply-dependence relationships obtained by the service feature setting interface.

Description

TECHNICAL FIELD

[0001] The present application relates to the cloud technology field, and in particular to a cloud service deployment method of a cloud platform and a related device thereof. BACKGROUND

[0002] In a cloud scenario, when the cloud platform determines that a certain tenant has a demand for a cloud service, the cloud platform can directly deploy the cloud service (for example, a virtual machine, a container, a bare metal server, and the like allocated for the tenant) for the tenant.

[0003] Generally, there is usually business cooperation between different tenants, that is, the cloud services deployed by the cloud platform for different tenants can interact. However, when the cloud platform deploys a cloud service for a certain tenant, only the factors of the tenant itself are considered, and the influence of other tenants associated with the tenant is not considered, and cross-tenant cloud service optimization deployment cannot be achieved. SUMMARY

[0004] Embodiments of the present application provide a cloud service deployment method of a cloud platform and a related device thereof, which can consider the influence of the remaining tenants when deploying a cloud service for a certain tenant, thereby achieving cross-tenant cloud service optimization deployment.

[0005] A first aspect of embodiments of the present application provides a cloud service deployment method of a cloud platform, the method comprising:

[0006] The cloud platform can provide a service feature setting interface, and the service feature setting interface is used to obtain the supply-dependence relationship of different tenants. For example, the supply-dependence relationship 1 is used to represent the association relationship between the tenant 1 as a supply side and the tenant 2 as a dependence side, the supply-dependence relationship 2 is used to represent the association relationship between the tenant 3 as a supply side and the tenant 4 as a dependence side, and the like.

[0007] The cloud platform deploys a cloud service for a tenant as a dependence side or for a tenant as a supply side based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that the cloud platform can obtain the supply-dependence relationship of a certain tenant through the service feature setting interface when deploying a cloud service for the tenant. Since the relationship reflects the association relationship between the tenant and the remaining tenants, when the cloud platform deploys a cloud service for the tenant based on the relationship, if the tenant is a dependence side, the cloud platform can consider the influence of the remaining tenants as a supply side, and if the tenant is a supply side, the cloud platform can consider the influence of the remaining tenants as a dependence side, thereby achieving cross-tenant cloud service optimization deployment.

[0008] The tenant can operate a terminal device locally, the terminal device is installed with a browser or a client provided by the cloud platform, the terminal device accesses the cloud platform, and the tenant logs in the cloud platform by inputting a tenant account and a password in the cloud platform. Different tenants can register different tenant accounts and passwords in the cloud platform, the cloud platform distinguishes tenants by the tenant accounts input by the tenants, and authenticates the tenant accounts by the passwords.

[0009] Further, for any one of the supply-dependence relationship, the tenant as the dependent party and the tenant as the supply party, the cloud platform can set the cloud service of the tenant as the supply party and the cloud service of the tenant as the dependent party in the same logical area, thereby realizing the affinity deployment of the cloud service across tenants. In this way, when the cloud service of the tenant as the supply party and the cloud service of the tenant as the dependent party interact, data transmission across logical areas is not required, the time delay of data transmission can be reduced, and the efficiency of data transmission can be improved.

[0010] Specifically, the cloud service across tenants can be deployed in the same logical area, and the following advantages can be realized: (1) the communication time delay between cloud services can be reduced, and the experience is better. (2) The transmission of data across the aggregation layer can also be reduced, so that the transmission bandwidth can be guaranteed, which is beneficial to improve the service quality of big data supply and big data consumption, and is also beneficial to optimize the cooperation between video production and video processing service products. (3) It can also avoid large communication volume across the aggregation boundary, waste excessive network bandwidth, and thus improve the utilization rate of network resources.

[0011] In a possible implementation, the service feature setting interface is used to obtain the supply type of the first tenant and the supply type of the second tenant, wherein the supply type of the first tenant is a supply party, and the supply type of the second tenant is a dependent party. In the foregoing implementation, the first tenant and the second tenant can input their own supply types in the service feature setting interface provided by the cloud platform. Here, the supply type usually refers to a supply party or a dependent party. Then, based on the supply type of the first tenant and the supply type of the second tenant, the cloud platform can determine that the first tenant is a supply party and the second tenant is a dependent party.

[0012] It is worth noting that the cloud platform identifies the first tenant by the tenant account registered by the first tenant in the cloud platform, and identifies the second tenant by the tenant account registered by the second tenant in the cloud platform.

[0013] In a possible implementation, the service feature setting interface is further configured to acquire a supply type disclosure range of the first tenant, and acquire a supply type disclosure range of the second tenant, wherein the supply type disclosure range of the first tenant is visible to all external tenants or the second tenant, and the supply type disclosure range of the second tenant is visible to all external tenants or the first tenant. In the foregoing implementation, the first tenant and the second tenant can input their own supply type disclosure ranges in the service feature setting interface provided by the cloud platform, and then the cloud platform can set the supply type of the first tenant to be visible to all external tenants or the second tenant, and set the supply type of the second tenant to be visible to all external tenants or the first tenant based on the supply type disclosure range of the first tenant and the supply type disclosure range of the second tenant.

[0014] In a possible implementation, the service feature setting interface is further configured to acquire a dependent party set by the first tenant, or acquire a supply party set by the second tenant, wherein the dependent party set by the first tenant is the second tenant, and the supply party set by the second tenant is the first tenant. In the foregoing implementation, the first tenant can input the dependent party set by the first tenant in the service feature setting interface provided by the cloud platform, and the dependent party set by the first tenant is the second tenant, so that the cloud platform can determine that there is a supply-dependence relationship between the first tenant and the second tenant based on the dependent party set by the first tenant, or the second tenant can input the supply party set by the second tenant in the service feature setting interface provided by the cloud platform, and the supply party set by the second tenant is the first tenant, so that the cloud platform can determine that there is a supply-dependence relationship between the first tenant and the second tenant based on the supply party set by the second tenant.

[0015] In a possible implementation, the service feature setting interface is further configured to, in a case where the dependent party set by the first tenant is the second tenant, confirm, to the second tenant, whether the second tenant is willing to be a dependent party of the first tenant, and in a case where the supply party set by the second tenant is the first tenant, confirm, to the first tenant, whether the first tenant is willing to be a supply party of the second tenant. In the foregoing implementation, in the case where the dependent party set by the first tenant is the second tenant, the cloud platform can confirm, to the second tenant, whether the second tenant is willing to be a dependent party of the first tenant through the service feature setting interface, and if the second tenant confirms that it is willing to be a dependent party of the first tenant, the cloud platform can successfully acquire the supply-dependence relationship between the first tenant and the second tenant, or in the case where the supply party set by the second tenant is the first tenant, the cloud platform can confirm, to the first tenant, whether the first tenant is willing to be a supply party of the second tenant through the service feature setting interface, and if the first tenant confirms that it is willing to be a supply party of the second tenant, the cloud platform can successfully acquire the supply-dependence relationship between the first tenant and the second tenant.

[0016] In a possible implementation, the service feature setting interface obtains a supply-dependence relationship for a tenant as a dependent party or a tenant as a supply party to deploy a cloud service, including: confirming an availability zone where the cloud service of the tenant as the supply party is located; and setting the cloud service of the tenant as the dependent party in the availability zone. In the foregoing implementation, for any supply-dependence relationship involving a tenant as a dependent party and a tenant as a supply party, the cloud platform can first confirm an availability zone where the cloud service of the tenant as the supply party is located, and then set the cloud service of the tenant as the dependent party in the availability zone, so that cross-tenant cloud services are implemented in an affinity manner.

[0017] In a possible implementation, the service feature setting interface obtains a supply-dependence relationship for a tenant as a dependent party or a tenant as a supply party to deploy a cloud service, including: confirming an elasticity scaling policy of the cloud service of the tenant as the supply party; and adjusting the cloud service of the tenant as the dependent party according to the elasticity scaling policy. In the foregoing implementation, the cloud platform sets an elasticity scaling policy for the cloud service of the tenant as the supply party, and the elasticity scaling policy can be specifically: for any supply-dependence relationship involving a tenant as a dependent party and a tenant as a supply party, when the number of cloud instances of the tenant as the supply party changes, the number of cloud instances of the tenant as the dependent party also changes. Therefore, the cloud platform can adjust the cloud service of the tenant as the supply party according to the elasticity scaling policy.

[0018] In a possible implementation, the service feature setting interface obtains a supply-dependence relationship for a tenant as a dependent party or a tenant as a supply party to deploy a cloud service, including: confirming a quality of service (QoS) or a throughput of the cloud service of the tenant as the supply party; and adjusting the cloud service of the tenant as the dependent party according to the QoS or the throughput. In the foregoing implementation, the cloud platform can monitor a state parameter of the cloud service of the tenant as the supply party in real time, and the state parameter can be the QoS or the throughput. The cloud platform can adjust the cloud service of the tenant as the supply party according to the state parameter of the cloud service of the tenant as the supply party.

[0019] In a possible implementation, the service feature setting interface obtains a supply-dependence relationship for a tenant as a dependent party or a tenant as a supply party to deploy a cloud service, including: confirming an availability zone where the cloud service of the tenant as the supply party is located; and setting the cloud service of the tenant as the dependent party in the availability zone. In the foregoing implementation, for any supply-dependence relationship involving a tenant as a dependent party and a tenant as a supply party, the cloud platform can first confirm an availability zone where the cloud service of the tenant as the dependent party is located, and then set the cloud service of the tenant as the supply party in the availability zone, so that cross-tenant cloud services are implemented in an affinity manner.

[0020] In a possible implementation, the cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that the cloud platform can provide the service feature setting interface for obtaining the supply-dependence relationship of different tenants. The cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that when the cloud platform deploys the cloud service for a certain tenant, the supply-dependence relationship of the tenant can be obtained through the service feature setting interface. Since the relationship reflects the association relationship between the tenant and the remaining tenants, when the cloud platform deploys the cloud service for the tenant based on the relationship, if the tenant is a dependent party, the cloud platform can consider the influence of the remaining tenants as provider parties, and if the tenant is a provider party, the cloud platform can consider the influence of the remaining tenants as dependent parties, thereby achieving optimal deployment of the cloud service across tenants.

[0021] In a possible implementation, the cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that the cloud platform can provide the service feature setting interface for obtaining the supply-dependence relationship of different tenants. The cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that when the cloud platform deploys the cloud service for a certain tenant, the supply-dependence relationship of the tenant can be obtained through the service feature setting interface. Since the relationship reflects the association relationship between the tenant and the remaining tenants, when the cloud platform deploys the cloud service for the tenant based on the relationship, if the tenant is a dependent party, the cloud platform can consider the influence of the remaining tenants as provider parties, and if the tenant is a provider party, the cloud platform can consider the influence of the remaining tenants as dependent parties, thereby achieving optimal deployment of the cloud service across tenants.

[0022] A second aspect of the embodiment of the application provides a cloud platform, which comprises: an obtaining module configured to provide a service feature setting interface, the service feature setting interface being configured to obtain supply-dependence relationships of different tenants; and a deployment module configured to deploy a cloud service for a tenant as a dependent party or for a tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface.

[0023] It can be seen from the cloud platform that the cloud platform can provide a service feature setting interface for obtaining supply-dependence relationships of different tenants. The cloud platform deploys a cloud service for a tenant as a dependent party or for a tenant as a provider party based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that when the cloud platform deploys a cloud service for a certain tenant, the supply-dependence relationship of the tenant can be obtained through the service feature setting interface. Since the relationship reflects the association relationship between the tenant and the remaining tenants, when the cloud platform deploys the cloud service for the tenant based on the relationship, if the tenant is a dependent party, the cloud platform can consider the influence of the remaining tenants as provider parties, and if the tenant is a provider party, the cloud platform can consider the influence of the remaining tenants as dependent parties, thereby achieving optimal deployment of the cloud service across tenants.

[0024] In a possible implementation, the obtaining module is configured to obtain a supply type of the first tenant and a supply type of the second tenant through the service feature setting interface, where the supply type of the first tenant is a supplier, and the supply type of the second tenant is a dependent.

[0025] In a possible implementation, the obtaining module is further configured to obtain a supply type disclosure range of the first tenant and a supply type disclosure range of the second tenant through the service feature setting interface, where the supply type disclosure range of the first tenant is visible to all external tenants or visible to the second tenant, and the supply type disclosure range of the second tenant is visible to all external tenants or visible to the first tenant.

[0026] In a possible implementation, the obtaining module is further configured to obtain a dependent of the first tenant or a supplier of the second tenant set by the service feature setting interface, where the dependent of the first tenant set by the first tenant is the second tenant, and the supplier of the second tenant set by the second tenant is the first tenant.

[0027] In a possible implementation, the obtaining module is further configured to, in a case where the dependent of the first tenant set by the first tenant is the second tenant, confirm, through the service feature setting interface, whether the second tenant is willing to be the dependent of the first tenant, and in a case where the supplier of the second tenant set by the second tenant is the first tenant, confirm, through the service feature setting interface, whether the first tenant is willing to be the supplier of the second tenant.

[0028] In a possible implementation, the deployment module is configured to: confirm an availability zone where a cloud service of a tenant as a supplier is located; and set a cloud service of a tenant as a dependent in the availability zone.

[0029] In a possible implementation, the deployment module is configured to: confirm an elasticity scaling policy of a cloud service of a tenant as a supplier; and adjust a cloud service of a tenant as a dependent according to the elasticity scaling policy.

[0030] In a possible implementation, the deployment module is configured to: confirm a QoS or throughput of a cloud service of a tenant as a supplier; and adjust a cloud service of a tenant as a dependent according to the QoS or the throughput.

[0031] In a possible implementation, the deployment module is configured to: confirm an availability zone where a cloud service of a tenant as a dependent is located; and set a cloud service of a tenant as a supplier in the availability zone.

[0032] In a possible implementation, the deployment module is configured to: confirm an elasticity scaling policy of a cloud service of a tenant as a dependent; and adjust a cloud service of a tenant as a supplier according to the elasticity scaling policy.

[0033] In a possible implementation, the deployment module is configured to: confirm the QoS or throughput of the cloud service of the tenant as a dependent party; and adjust the cloud service of the tenant as a provider according to the QoS or throughput.

[0034] A third aspect of the embodiments of the present application provides a network device, which comprises a memory and a processor;

[0035] The memory stores codes, and the processor is configured to execute the codes, when the codes are executed, the network device executes the method according to the first aspect or any possible implementation of the first aspect.

[0036] A fourth aspect of the embodiments of the present application provides a computer storage medium, which stores a computer program, when the computer program is executed by a computer, the computer program causes the computer to implement the method according to the first aspect or any possible implementation of the first aspect.

[0037] A fifth aspect of the embodiments of the present application provides a computer program product, which stores instructions, when the instructions are executed by a computer, the instructions cause the computer to implement the method according to the first aspect or any possible implementation of the first aspect.

[0038] In the embodiments of the present application, the cloud platform can provide a service feature setting interface, the service feature setting interface is used to acquire the provider-dependent relationship of different tenants. The cloud platform deploys the cloud service for the tenant as a dependent party or for the tenant as a provider based on the provider-dependent relationship acquired by the service feature setting interface. It can be seen that when the cloud platform deploys the cloud service for a certain tenant, the cloud platform can acquire the provider-dependent relationship of the tenant through the service feature setting interface. Since the relationship reflects the association relationship between the tenant and the rest of the tenants, when the cloud platform deploys the cloud service for the tenant based on the relationship, if the tenant is a dependent party, the cloud platform can consider the influence of the rest of the tenants as providers, and if the tenant is a provider, the cloud platform can consider the influence of the rest of the tenants as dependent parties, thereby realizing the optimized deployment of the cloud service across tenants. BRIEF DESCRIPTION OF DRAWINGS

[0039] Figure 1 An illustrative diagram of a logical area provided by the embodiments of the present application;

[0040] Figure 2 An illustrative diagram of a cloud service deployment method of a cloud platform provided by the embodiments of the present application;

[0041] FIG. 3(a) is an illustrative diagram of a service feature setting interface provided by the embodiments of the present application;

[0042] FIG. 3(b) is another illustrative diagram of a service feature setting interface provided by the embodiments of the present application;

[0043] Fig. 3(c) is another schematic diagram of a service feature setting interface provided by an embodiment of the present application;

[0044] Fig. 3(d) is another schematic diagram of a service feature setting interface provided by an embodiment of the present application;

[0045] Figure 4 Fig. 1 is a schematic diagram of a cloud platform deploying cloud services provided by an embodiment of the present application;

[0046] Figure 5 Fig. 2 is another schematic diagram of a cloud platform deploying cloud services provided by an embodiment of the present application;

[0047] Figure 6 Fig. 3 is a structural schematic diagram of a cloud platform provided by an embodiment of the present application;

[0048] Figure 7 Fig. 4 is a structural schematic diagram of a network device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0049] Embodiments of the present application provide a cloud service deployment method of a cloud platform and related devices, when deploying cloud services for a certain tenant, the influence brought by the rest of the tenants can be considered, thereby realizing cross-tenant cloud service optimized deployment.

[0050] The terms "first", "second", and the like in the description and in the claims of the present application and above drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged, where appropriate, so that the embodiments described herein can be carried out in sequences other than those illustrated or described herein. Furthermore, the terms "comprise" and "have", and any variations thereof, are intended to cover non-exclusive inclusion, for example, processes, methods, systems, products, or devices that include a list of steps or modules as processes, methods, systems, products, or devices not necessarily limited to those clearly listed, but can include other steps or modules not clearly listed or inherent to these processes, methods, products, or devices. The naming or numbering of the steps in the present application does not mean that the steps in the method flow must be executed in the order / time / logical order indicated by the naming or numbering. The execution order of the named or numbered flow steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved. The division of modules in the present application is a logical division, and in actual application, it can have another division manner, for example, a plurality of modules can be combined or integrated in another system, or some features can be ignored or not executed, in addition, the coupling or direct coupling or communication connection between the displayed or discussed modules can be through some ports, the indirect coupling or communication connection between the modules can be electrical or other similar forms, which are not limited in the present application. In addition, the modules or sub-modules described as separate components can or can not be physically separated, can or can not be physical modules, or can be distributed to multiple circuit modules, and part or all of the modules can be selected according to actual needs to achieve the purpose of the present application scheme.

[0051] The embodiments of the present application can be applied to a cloud scenario, in which a cloud platform can deploy cloud services for a plurality of tenants. Specifically, the cloud platform can manage cloud instances in a plurality of logical regions, for example, the cloud platform can create, release, migrate, allocate, and monitor cloud instances in a certain logical region, etc. When a certain tenant has a demand for cloud services, the cloud platform can schedule cloud instances in a certain logical region (or certain logical regions) to provide services for the tenant, and these scheduled cloud instances can be used exclusively to implement the business of the tenant. Thus, the deployment of cloud services for the tenant is completed.

[0052] Among them, the tenant can operate a terminal device locally, wherein the terminal device is installed with a browser that can access the cloud platform or a client provided by the cloud platform, and the terminal device is used to access the cloud platform, and a tenant account and a password are input in the cloud platform to log in the cloud platform, wherein different tenants can register different tenant accounts and passwords in the cloud platform, the cloud platform distinguishes tenants by the tenant account input by the tenant, and authenticates the tenant account by the password.

[0053] Terminal devices include, for example, internet-connected mobile phones, laptops, desktop computers, tablets, in-vehicle systems, or other internet-connected devices that can be operated locally by an individual.

[0054] The following is a brief introduction to the logical regions involved in the embodiments of this application. Figure 1 This is a schematic diagram of a logical region provided in an embodiment of this application. Figure 1 As shown, logical regions include: regions, availability zones (AZs), and data centers (DCs), etc. Generally, a region is a physical area divided according to geographical location, such as Central China, South China, and East China. An availability zone is a smaller, independent, and physically isolated area within a region. A region can contain multiple availability zones; for example, South China includes multiple availability zones such as City X, City Y, and City Z. An availability zone can contain multiple data centers, each of which can accommodate multiple physical servers and multiple communication devices and other infrastructure. The multiple physical servers in a data center can be used to deploy cloud instances that provide cloud services. These cloud instances can be the physical servers themselves (also known as bare metal servers, i.e., bare machines), or virtual machines (VMs) and containers (Docker) deployed on physical servers.

[0055] In related technologies, different tenants typically have business collaborations, meaning that cloud services deployed by a cloud platform for different tenants can interact. For example, Company A's business is databases, while Company B's business is video applications that depend on Company A's database. After the cloud platform allocates cloud instances to Company A and Company B, when the cloud instance allocated to Company B is running the video application, it can retrieve video data from the database running on the cloud instance allocated to Company A. In other words, the cloud instances allocated to Company A and Company B can interact. However, when deploying cloud services for a specific tenant, the cloud platform can only consider the factors of that tenant itself, without considering the impact of other tenants, thus failing to achieve optimized deployment of cloud services across tenants.

[0056] To address the aforementioned issues, this application provides a cloud service deployment method for a cloud platform. Figure 2 A flowchart illustrating the cloud service deployment method of the cloud platform provided in this application embodiment is shown below. Figure 2 As shown, the method includes:

[0057] 201. The cloud platform provides a service feature setting interface, which is used to obtain the supply-dependency relationship of different tenants.

[0058] Once the cloud platform starts, it provides a service characteristic setting interface, which is used to obtain the supply-dependency relationships of different tenants. Specifically, the service characteristic setting interface can be a tenant interface, an application programming interface (API), a template upload interface, etc. For ease of explanation, the following description will use the service characteristic setting interface as the tenant interface for illustrative purposes. Figures 3(a) to 3(d) As shown in Figure 3(a), a schematic diagram of the service feature setting interface provided in this application embodiment; Figure 3(b), another schematic diagram of the service feature setting interface provided in this application embodiment; Figure 3(c), another schematic diagram of the service feature setting interface provided in this application embodiment; and Figure 3(d), another schematic diagram of the service feature setting interface provided in this application embodiment), the cloud platform can provide a user interface to multiple tenants. This tenant interface includes multiple input fields, each used to obtain different information about the tenant. For ease of explanation, the following will use two tenants with business dependencies as an example to describe each input field in detail. The tenant acting as the supplier will be referred to as the first tenant, and the tenant acting as the dependent will be referred to as the second tenant. The input fields of the tenant interface include:

[0059] (1) Supply Type Input Field. Tenants can input their own supply type in the supply type input field of the tenant interface provided by the cloud platform. The supply type here usually refers to the supplier or the dependent. Then, the cloud platform can divide multiple tenants into two categories based on their supply types: tenants who are suppliers and tenants who are dependents. Specifically, the supply type input field of the tenant interface provided for the first tenant can be used to obtain the supply type of the first tenant, and the supply type input field of the tenant interface provided for the second tenant can be used to obtain the supply type of the second tenant. In this case, the supply type of the first tenant is the supplier, and the supply type of the second tenant is the dependent. For example, suppose that the business provided by enterprise A is a database, and the business provided by enterprise B is a video application that depends on the database of enterprise A. Then, there is a supply-dependency relationship between enterprise A and enterprise B. In this relationship, enterprise A is the supplier and enterprise B is the dependent. As shown in Figure 3(a), when enterprise A registers information on the tenant interface a provided by the cloud platform, it can input its own supply type as a supplier in the supply type input field so that the cloud platform can determine that enterprise A is the supplier. Similarly, as shown in Figure 3(b), when Enterprise B registers its information on the tenant interface b provided by the cloud platform, it can enter its own supply type as a dependent in the supply type input field so that the cloud platform can identify Enterprise B as a dependent.

[0060] (2) A supply type public range input field can be used to obtain the public range of the supply type of a tenant. A tenant can input the public range of the supply type of the tenant at the supply type public range input field of the tenant interface provided by the cloud platform. If the public range is all external tenants, the cloud platform sets the supply type of the tenant as visible to all external tenants. If the public range is specific tenants, the cloud platform sets the supply type of the tenant as visible to some external tenants (e.g. the external tenants specified by the tenant). Specifically, the supply type public range input field of the tenant interface provided for the first tenant can be used to obtain the public range of the supply type of the first tenant, and the supply type public range input field of the tenant interface provided for the second tenant can be used to obtain the public range of the supply type of the second tenant, wherein the public range of the supply type of the first tenant is all external tenants or the second tenant, and the public range of the supply type of the second tenant is all external tenants or the first tenant. As an example, as shown in FIG. 3(a), when the enterprise A registers information on the tenant interface a provided by the cloud platform, the enterprise A can also input the public range of the supply type of the enterprise A as visible to the enterprise B at the supply type public range input field. Similarly, as shown in FIG. 3(b), when the enterprise B registers information on the tenant interface b provided by the cloud platform, the enterprise B can also input the public range of the supply type of the enterprise B as visible to the enterprise A at the supply type public range input field. Then, the enterprise A can subsequently query the supply type of the enterprise B on the cloud platform, and the enterprise B can also subsequently query the supply type of the enterprise A on the cloud platform, while the rest of the enterprises cannot query the supply type of the enterprise A or the supply type of the enterprise B.

[0061] (3) The opposite end setting input box can be used to obtain the opposite end tenant set (or specified) by the tenant. For a tenant as a supplier (or dependent), the tenant can input the opposite end tenant set as a dependent (or supplier) at the opposite end setting input box of the tenant interface provided by the cloud platform, so that the cloud platform determines that there is a supply-dependent relationship between the tenant and the opposite end tenant set by the tenant. Specifically, the opposite end setting input box of the tenant interface provided for the first tenant can be used to obtain the dependent set by the first tenant, and the opposite end setting input box of the tenant interface provided for the second tenant can be used to obtain the supplier set by the second tenant, wherein the dependent set by the first tenant is the second tenant, and the supplier set by the second tenant is the first tenant. Still as the above example, as shown in FIG. 3(a), when enterprise A registers information on the tenant interface a provided by the cloud platform, enterprise A can also input enterprise B at the opposite end setting input box (equivalent to enterprise A setting enterprise B as the dependent of enterprise A), so that the cloud platform can determine that there is a supply-dependent relationship between enterprise A and enterprise B, that is, enterprise B is determined as the dependent of enterprise A. Further, as shown in FIG. 3(b), when enterprise B registers information on the tenant interface b provided by the cloud platform, enterprise B can also input enterprise A at the opposite end setting input box, so that the cloud platform can determine that there is a supply-dependent relationship between enterprise A and enterprise B, that is, enterprise A is determined as the supplier of enterprise B. It should be understood that enterprise A setting enterprise B as the dependent of enterprise A and enterprise B setting enterprise A as the supplier of enterprise B can be executed, or only one of them can be executed, which is not limited here.

[0062] (4) an opposite end confirmation input field, which can be used to obtain the confirmation information of the opposite end tenant. For a tenant as a supplier (or a dependent), after the tenant sets the opposite end tenant as a dependent, the cloud platform can display the to-be-confirmed information to the opposite end tenant at the opposite end confirmation input field of the tenant interface, and the confirmation information is used to determine whether the opposite end tenant is willing to be the dependent (or the supplier) of the tenant. After the cloud platform receives the confirmation information of the opposite end tenant at the opposite end confirmation input field, if the confirmation information indicates that the opposite end tenant is willing to be the dependent (or the supplier) of the tenant, it is equivalent to successfully obtaining the supply-dependent relationship between the tenant and the opposite end tenant. Specifically, the opposite end confirmation input field of the tenant interface provided for the first tenant can be used to confirm whether the second tenant is willing to be the dependent of the first tenant when the dependent set by the first tenant is the second tenant, and the opposite end confirmation input field of the tenant interface provided for the second tenant can be used to confirm whether the first tenant is willing to be the supplier of the second tenant when the supplier set by the second tenant is the first tenant. For example, as shown in FIG. 3(c), if the enterprise A sets the enterprise B as the dependent of the enterprise A, the cloud platform can display the to-be-confirmed information at the opposite end confirmation input field of the tenant interface b facing the enterprise B, to confirm whether the enterprise B is willing to be the dependent of the enterprise A. If the enterprise B inputs the confirmation information indicating that the enterprise B is willing to be the dependent of the enterprise A at the opposite end confirmation input field, the cloud platform successfully obtains the supply-dependent relationship between the enterprise A and the enterprise B. Further, as shown in FIG. 3(d), if the enterprise B sets the enterprise A as the supplier of the enterprise B, the cloud platform can display the to-be-confirmed information at the opposite end confirmation input field of the tenant interface a facing the enterprise A, to confirm whether the enterprise A is willing to be the supplier of the enterprise B. If the enterprise A inputs the confirmation information indicating that the enterprise A is willing to be the supplier of the enterprise B at the opposite end confirmation input field, the cloud platform successfully obtains the supply-dependent relationship between the enterprise A and the enterprise B. It should be understood that the confirmation information of the enterprise A and the confirmation information of the enterprise B can be obtained, or only one of them can be obtained, which is not limited here.

[0063] 202. The cloud platform deploys the cloud service for the tenant as a dependent or for the tenant as a supplier based on the supply-dependent relationship obtained by the service feature setting interface.

[0064] After obtaining the supply-dependency relationships of different tenants through the service feature setting interface, the cloud platform can deploy cloud services for tenants acting as dependents or tenants acting as suppliers based on these relationships. The deployment of cloud services by the cloud platform can be divided into two scenarios: (1) cloud services of tenants acting as dependents are deployed along with cloud services of tenants acting as suppliers; (2) cloud services of tenants acting as suppliers are deployed along with cloud services of tenants acting as dependents. The following sections will describe these two scenarios respectively:

[0065] (1) For any supply-dependency relationship involving both the tenant acting as a dependent and the tenant acting as a supplier, the cloud platform can first identify the availability zone where the cloud service of the supplier tenant is located, and then set the cloud service of the dependent tenant in that availability zone. In this way, cross-tenant cloud services achieve affinity deployment. As in the example above, ... Figure 4 As shown ( Figure 4 (This is a schematic diagram illustrating the deployment of cloud services on a cloud platform provided in this application embodiment.) Assume Company A is located in City X. Company A can apply to the cloud platform to deploy a virtual machine running a database in City X. After the cloud platform deploys the virtual machine for running Company A's database in City X, due to the supply-dependency relationship between Company A and Company B, the cloud platform can also deploy a virtual machine for running Company B's video application in City X, and release the virtual machine already deployed in City Y for running Company B's video application.

[0066] For example, such as Figure 5 As shown ( Figure 5 (This is another schematic diagram illustrating the deployment of cloud services on a cloud platform provided in this application embodiment.) Suppose that Company A is located in City X. Due to certain factors (e.g., the price of virtual machines, etc.), Company A applies to the cloud platform to migrate the virtual machine running its database from City X to City Z. After the cloud platform deploys the virtual machine for running Company A's database in City Z, since there is a supply-dependency relationship between Company A and Company B, the cloud platform can also deploy a virtual machine for running Company B's video application in City Z, and release the virtual machine originally deployed in City X for running Company A's database and the virtual machine originally deployed in City X for running Company B's video application.

[0067] Further, the cloud platform sets an elasticity scaling policy for the tenant as the supplier of the cloud service, which can be specifically: for any supplier-dependence relationship involving a tenant as the dependence and a tenant as the supplier, after the number of cloud instances of the tenant as the supplier changes, the number of cloud instances of the tenant as the dependence also changes. Therefore, the cloud platform can adjust the cloud service of the tenant as the supplier according to the elasticity scaling policy. Still as the above example, enterprise A can apply to the cloud platform to increase the virtual machine for running the database in the X city area. Then, after the cloud platform receives the request of enterprise A, it can increase the virtual machine for running the database of enterprise A and the virtual machine for running the video application of enterprise B in the X city area.

[0068] Further, the cloud platform can monitor the state parameter of the cloud service of the tenant as the supplier in real time, which can be the quality of service (QoS) or throughput. The cloud platform can adjust the cloud service of the tenant as the supplier according to the state parameter of the cloud service of the tenant as the supplier. Still as the above example, the cloud platform can monitor the QoS of the virtual machine for running the database of enterprise A in real time, and if it is determined that the QoS is less than or equal to the preset QoS threshold, the virtual machine for running the video application of enterprise B is increased.

[0069] (2) For any supplier-dependence relationship involving a tenant as the dependence and a tenant as the supplier, the cloud platform can first confirm the availability zone where the cloud service of the tenant as the supplier is located, and set the cloud service of the tenant as the dependence in the availability zone, so that the cross-tenant cloud service is deployed in an affinity manner.

[0070] Further, the cloud platform sets an elasticity scaling policy for the tenant as the supplier of the cloud service, which can be specifically: for any supplier-dependence relationship involving a tenant as the dependence and a tenant as the supplier, after the number of cloud instances of the tenant as the supplier changes, the number of cloud instances of the tenant as the dependence also changes. Therefore, the cloud platform can adjust the cloud service of the tenant as the supplier according to the elasticity scaling policy.

[0071] Further, the cloud platform can monitor the state parameter of the cloud service of the tenant as the supplier in real time, which can be the quality of service (QoS) or throughput. The cloud platform can adjust the cloud service of the tenant as the supplier according to the state parameter of the cloud service of the tenant as the supplier.

[0072] It should be understood that the cloud service of the tenant as the supplier follows the introduction of the cloud service of the tenant as the dependent, and the related description part of the cloud service of the tenant as the dependent follows the cloud service of the tenant as the supplier for deployment, which will not be repeated here.

[0073] It should also be understood that Figure 4 and Figure 5 The example shown in the figure is only illustrative with a logical area as an availability zone, and does not constitute a limitation on the type of logical area in the embodiment. The logical area can also be a zone, a data center, and the like.

[0074] In the embodiment, the cloud platform can provide a service feature setting interface, which is used to obtain the supply-dependence relationship of different tenants. The cloud platform deploys the cloud service for the tenant as the dependent or for the tenant as the supplier based on the supply-dependence relationship obtained by the service feature setting interface. It can be seen that when the cloud platform deploys the cloud service for a certain tenant, the supply-dependence relationship of the tenant can be obtained through the service feature setting interface. Since the relationship reflects the association relationship between the tenant and the remaining tenants, when the cloud platform deploys the cloud service for the tenant based on the relationship, if the tenant is the dependent, the cloud platform can consider the influence of the remaining tenants as the supplier, and if the tenant is the supplier, the cloud platform can consider the influence of the remaining tenants as the dependent, thereby realizing the optimized deployment of the cloud service across tenants.

[0075] Further, for the tenant as the dependent and the tenant as the supplier involved in any supply-dependence relationship, the cloud platform can set the cloud service of the tenant as the supplier and the cloud service of the tenant as the dependent in the same logical area, thereby realizing the affinity deployment of the cloud service across tenants. In this way, when the cloud service of the tenant as the supplier and the cloud service of the tenant as the dependent interact, they do not need to transmit data across logical areas, which can reduce the time delay of data transmission and improve the efficiency of data transmission.

[0076] Specifically, the cloud service across tenants can be cooperatively deployed in the same logical area, which can realize the following advantages: (1) The communication time delay between cloud services can be reduced, and the experience is better. (2) The transmission of data across the aggregation layer can also be reduced, so the transmission bandwidth can also be guaranteed, which is conducive to improving the service quality of big data supply and big data consumption, and is also conducive to optimizing the cooperation between video production and video processing service products. (3) It can also avoid large communication volume across the aggregation boundary, waste excessive network bandwidth, and thus improve the utilization rate of network resources.

[0077] The above is a detailed description of the cloud service deployment method of the cloud platform provided in the embodiment. The cloud platform provided in the embodiment will be introduced below. Figure 6A structural schematic diagram of a cloud platform provided by an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the cloud platform includes: Figure 6

[0078] The obtaining module 601 is configured to provide a service feature setting interface, and the service feature setting interface is configured to obtain supply-dependence relationships of different tenants. For example, the obtaining module 601 is configured to implement step 201 in the embodiment shown in FIG. 2. Figure 2

[0079] The deployment module 602 is configured to deploy cloud services for tenants as dependents or for tenants as suppliers based on the supply-dependence relationships obtained by the service feature setting interface. For example, the deployment module 602 is configured to implement step 202 in the embodiment shown in FIG. 2. Figure 2

[0080] In a possible implementation, the obtaining module 601 is configured to obtain a supply type of a first tenant and a supply type of a second tenant through the service feature setting interface, where the supply type of the first tenant is a supplier, and the supply type of the second tenant is a dependent.

[0081] In a possible implementation, the obtaining module 601 is further configured to obtain a supply type disclosure range of the first tenant and a supply type disclosure range of the second tenant through the service feature setting interface, where the supply type disclosure range of the first tenant is visible to all external tenants or visible to the second tenant, and the supply type disclosure range of the second tenant is visible to all external tenants or visible to the first tenant.

[0082] In a possible implementation, the obtaining module 601 is further configured to obtain a dependent set by the first tenant or a supplier set by the second tenant through the service feature setting interface, where the dependent set by the first tenant is the second tenant, and the supplier set by the second tenant is the first tenant.

[0083] In a possible implementation, the obtaining module 601 is further configured to, in a case where the dependent set by the first tenant is the second tenant, confirm, to the second tenant, whether the second tenant is willing to be a dependent of the first tenant, and in a case where the supplier set by the second tenant is the first tenant, confirm, to the first tenant, whether the first tenant is willing to be a supplier of the second tenant.

[0084] In a possible implementation, the deployment module 602 is configured to confirm an availability zone in which a cloud service of a tenant as a supplier is located, and set a cloud service of a tenant as a dependent in the availability zone.

[0085] ​​​In a possible implementation, the deployment module 602 is configured to: confirm an elasticity scaling policy of the cloud service of the tenant as a supplier; and adjust the cloud service of the tenant as a dependent party according to the elasticity scaling policy.

[0086] In a possible implementation, the deployment module 602 is configured to: confirm a QoS or throughput of the cloud service of the tenant as a supplier; and adjust the cloud service of the tenant as a dependent party according to the QoS or throughput.

[0087] In a possible implementation, the deployment module 602 is configured to: confirm an availability zone in which the cloud service of the tenant as a dependent party is located; and set the cloud service of the tenant as a supplier in the availability zone.

[0088] In a possible implementation, the deployment module 602 is configured to: confirm an elasticity scaling policy of the cloud service of the tenant as a dependent party; and adjust the cloud service of the tenant as a supplier according to the elasticity scaling policy.

[0089] In a possible implementation, the deployment module 602 is configured to: confirm a QoS or throughput of the cloud service of the tenant as a dependent party; and adjust the cloud service of the tenant as a supplier according to the QoS or throughput.

[0090] It should be noted that the information interaction and execution process between the modules / units of the apparatus are based on the same consideration as the method embodiments of the present application, and the technical effects brought by the same are the same as those of the method embodiments of the present application. For details, refer to the foregoing description of the method embodiments of the present application, which will not be repeated here.

[0091] Figure 7 A structural schematic diagram of a network device provided by the present application embodiment is shown in FIG. 7. Figure 7 As shown in FIG. 7, one embodiment of the network device in the present application embodiment can include one or more central processors 701, memories 702, input / output interfaces 703, wired or wireless network interfaces 704, and power supplies 705.

[0092] The memory 702 can be temporary storage or persistent storage. Further, the central processor 701 can be configured to communicate with the memory 702 and execute a series of instruction operations in the memory 702 on the network device.

[0093] In the present embodiment, the central processor 701 can execute the operations of the cloud platform in the foregoing Figure 2 embodiments, which will not be repeated here.

[0094] In the present embodiment, the central processor 701 can execute the operations of the cloud platform in the foregoing Figure 6The division manners of the modules such as the acquisition module and the deployment module described in the above are similar, and thus are not described herein again.

[0095] The embodiments of the present application also relate to a computer storage medium comprising computer readable instructions which, when executed, implement the method as Figure 2 described.

[0096] The embodiments of the present application also relate to a computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method as Figure 2 described.

[0097] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the system, device and unit described above can refer to the corresponding processes in the foregoing method embodiments, and thus are not described herein again.

[0098] In the several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the device embodiments described above are merely schematic, for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0099] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. According to actual needs, some or all of the units can be selected to achieve the purpose of the embodiments of the present application.

[0100] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0101] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A cloud service deployment method of a cloud platform, characterized by, The application comprises: a service feature setting interface is provided for obtaining supply-dependence relationships of different tenants; a cloud service is deployed for a tenant as a dependent party or for a tenant as a supply party based on the supply-dependence relationships obtained by the service feature setting interface; wherein the service feature setting interface is configured to: obtain a supply type of a first tenant and a supply type of a second tenant, wherein the supply type of the first tenant is a supply party and the supply type of the second tenant is a dependent party; obtain a dependent party set by the first tenant or a supply party set by the second tenant, wherein the dependent party set by the first tenant is the second tenant and the supply party set by the second tenant is the first tenant; in a case where the dependent party set by the first tenant is the second tenant, confirm with the second tenant whether the second tenant is willing to be a dependent party of the first tenant, and in a case where the supply party set by the second tenant is the first tenant, confirm with the first tenant whether the first tenant is willing to be a supply party of the second tenant; in a case where the second tenant is willing to be a dependent party of the first tenant and the first tenant is willing to be a supply party of the second tenant, obtain a supply-dependence relationship of the first tenant and the second tenant, wherein the supply-dependence relationship is used to indicate that a service of the second tenant depends on a service of the first tenant.

2. The method of claim 1, wherein, The service feature setting interface is further configured to obtain a supply type disclosure range of the first tenant and a supply type disclosure range of the second tenant, wherein the supply type disclosure range of the first tenant is visible to all external tenants or the second tenant, and the supply type disclosure range of the second tenant is visible to all external tenants or the first tenant.

3. The method according to claim 1 or 2, characterized in that, The cloud service is deployed for the tenant as the dependent party based on the supply-dependence relationships obtained by the service feature setting interface, comprising: confirming an availability zone in which a cloud service of a tenant as a supply party is located; setting the cloud service of the tenant as the dependent party in the availability zone.

4. The method according to claim 1 or 2, characterized in that, The cloud service is deployed for the tenant as the dependent party based on the supply-dependence relationships obtained by the service feature setting interface, comprising: confirming an elasticity scaling policy of a cloud service of a tenant as a supply party; adjusting a cloud service of a tenant as a dependent party according to the elasticity scaling policy.

5. The method according to claim 1 or 2, characterized in that, The cloud service is deployed for the tenant as the dependent party based on the supply-dependence relationships obtained by the service feature setting interface, comprising: confirming a quality of service (QoS) or a throughput of a cloud service of a tenant as a supply party; adjusting a cloud service of a tenant as a dependent party according to the QoS or the throughput.

6. The method of claim 1 or 2, wherein, The cloud service is deployed for the tenant as the supply party based on the supply-dependence relationships obtained by the service feature setting interface, comprising: confirming an availability zone in which a cloud service of a tenant as a dependent party is located; setting the cloud service of the tenant as the supply party in the availability zone.

7. The method according to claim 1 or 2, characterized in that, The cloud service is deployed for the tenant as the supply party based on the supply-dependence relationships obtained by the service feature setting interface, comprising: confirm an elasticity scaling policy of a cloud service of a tenant as a dependent party; adjust the cloud service of the tenant as a provider according to the elasticity scaling policy.

8. The method of claim 1 or 2, wherein, the service feature setting interface is used to acquire the provider-dependent relationship of the different tenants, and the cloud service of the tenant as a provider is deployed based on the provider-dependent relationship acquired by the service feature setting interface. confirm QoS or throughput of a cloud service of a tenant as a dependent party; adjust the cloud service of the tenant as a provider according to the QoS or the throughput.

9. A cloud platform, characterized by comprise: an acquisition module, configured to provide a service feature setting interface, the service feature setting interface being used to acquire provider-dependent relationships of different tenants; a deployment module, configured to deploy cloud services of the tenants as the dependent parties or the tenants as the providers based on the provider-dependent relationships acquired by the service feature setting interface; wherein the service feature setting interface is used to: acquire a provider type of a first tenant and a provider type of a second tenant, the provider type of the first tenant being a provider, and the provider type of the second tenant being a dependent party; acquire a dependent party set by the first tenant or a provider set by the second tenant, the dependent party set by the first tenant being the second tenant, and the provider set by the second tenant being the first tenant; in a case where the dependent party set by the first tenant is the second tenant, confirm, to the second tenant, whether the second tenant is willing to be a dependent party of the first tenant, and in a case where the provider set by the second tenant is the first tenant, confirm, to the first tenant, whether the first tenant is willing to be a provider of the second tenant; in a case where the second tenant is willing to be the dependent party of the first tenant and the first tenant is willing to be the provider of the second tenant, acquire a provider-dependent relationship of the first tenant and the second tenant, the provider-dependent relationship being used to indicate that a service of the second tenant depends on a service of the first tenant.

10. The cloud platform of claim 9, wherein, the acquisition module is further configured to acquire a provider type disclosure range of the first tenant and a provider type disclosure range of the second tenant through the service feature setting interface, the provider type disclosure range of the first tenant being visible to all external tenants or the second tenant, and the provider type disclosure range of the second tenant being visible to all external tenants or the first tenant.

11. The cloud platform of claim 9 or 10, wherein, the deployment module is configured to: confirm an availability zone in which a cloud service of a tenant as a provider is located; set the cloud service of the tenant as the dependent party in the availability zone.

12. The cloud platform of claim 9 or 10, wherein, the deployment module is configured to: confirm an elasticity scaling policy of a cloud service of a tenant as a provider; adjust the cloud service of the tenant as a dependent party according to the elasticity scaling policy.

13. The cloud platform of claim 9 or 10, wherein, the deployment module is configured to: confirm QoS or throughput of a cloud service of a tenant as a provider; adjust the cloud service of the tenant as a dependent party according to the QoS or the throughput.

14. The cloud platform of claim 9 or 10, wherein, the deployment module is configured to: confirm an availability zone in which a cloud service of a tenant as a dependent party is located; set the cloud service of the tenant as the provider in the availability zone.

15. The cloud platform of claim 9 or 10, wherein, the deployment module is configured to: confirm an elasticity scaling policy of a cloud service of a tenant as a dependent party; adjust the cloud service of the tenant as a provider according to the elasticity scaling policy.

16. The cloud platform of claim 9 or 10, wherein, The deployment module is configured to: confirm a QoS or throughput of a cloud service of a tenant as a dependent party; adjust the cloud service of the tenant as a provider according to the QoS or the throughput.

17. A network device, comprising: The network device comprises a memory and a processor; The memory stores code, and the processor is configured to execute the code, and when the code is executed, the network device performs the method in any one of claims 1 to 8.

18. A computer storage medium, characterized in that, The computer storage medium stores a computer program, and the program is executed by a computer to cause the computer to implement the method in any one of claims 1 to 8.

19. A computer program product, characterised in that, The computer program product stores instructions, and the instructions are executed by a computer to cause the computer to implement the method in any one of claims 1 to 8.

Images