WO2021232860A1

WO2021232860A1 - Communication method, apparatus and system

Info

Publication number: WO2021232860A1
Application number: PCT/CN2021/075691
Authority: WO
Inventors: 陈曦; 李光成
Original assignee: 华为技术有限公司
Priority date: 2020-05-18
Filing date: 2021-02-06
Publication date: 2021-11-25
Also published as: CN113691575A

Abstract

Disclosed are a communication method, apparatus and system, which belong to the field of cloud computing. The method comprises: a first application programming interface (API) gateway receiving a first API request; the first API gateway determining, from among a plurality of cloud platforms, a target cloud platform for responding to the first API request, wherein the format of the first API request is a format supported by the first API gateway; and the first API gateway sending a second API request to a second API gateway, wherein the second API request is determined on the basis of the first API request, the format of the second API request is a format supported by the second API gateway, and the second API gateway is an API gateway of the target cloud platform. By means of the present application, the flexibility of the communication between a user equipment and different cloud platforms is improved.

Description

Communication method, device and system

Technical field

This application relates to the field of cloud computing, and in particular to a communication method, device and system.

Background technique

Cloud technology is a hosting technology used to realize the calculation, storage, processing or sharing of data. The platform used to implement cloud technology is called cloud platform.

As users' different requirements for data gradually increase, a user may call different resources on different cloud platforms through user equipment. For example, create different virtual machines on different cloud platforms. In this way, when the user equipment accesses different cloud platforms, it needs to issue different application programming interface (API) requests that conform to the formats supported by the different cloud platforms, and the communication flexibility between the user equipment and different cloud platforms is low.

Summary of the invention

The embodiments of the present application provide a communication method, device, and system. The technical solution is as follows:

In a first aspect, a communication method is provided, and the method includes:

The first application program interface API gateway receives the first API request; the first API gateway determines the target cloud platform used to respond to the first API request among multiple cloud platforms, and the format of the first API request is the first API gateway Supported format; the first API gateway sends a second API request to the second API gateway, the second API request is determined based on the first API request, and the format of the second API request is a format supported by the second API gateway , The second API gateway is the API gateway of the target cloud platform.

In the embodiment of the present application, after receiving the first API request, the first API gateway determines the second API request in the format supported by the target cloud platform, and sends the second API request to the second API gateway of the target cloud platform , The user only needs to use the API request in the format supported by the first API gateway to access the API unified gateway to achieve access to the target cloud platform among multiple cloud platforms, which reduces the user’s operational complexity and improves user equipment and different clouds. The communication flexibility of the platform.

In the embodiment of the present application, the first API gateway needs to predetermine the format of the API request that it supports, so as to provide convenience for subsequent users. The format of the API request is consistent with the format of the resource deployed by the first API gateway, so it is also called the resource format. The resource format mainly includes two parts, one part is the format (schema, also called specification) of the resource parameters carried in the API request; the other part includes the interface calling rules corresponding to the API request. Among them, the resource parameter refers to the parameter (also called the object) of the resource to which the data belongs. The resource parameter format is the structure definition of the data object. The interface calling rules of the calling operation are used to indicate the interface set corresponding to the calling operation and the calling timing of the interface set. Among them, the time sequence of the interface set called through the same API request is the same, and the time sequence of the interface set called through different API requests is different.

The embodiment of the present application describes the process of determining the format of the supported API request by the first API gateway in the following two aspects.

In the first optional implementation manner, the first API gateway determines the resource parameter format of the supported API request. The process includes:

The first API gateway integrates resource parameter formats corresponding to the same calling operation of the same resource in the multiple cloud platforms to obtain the resource parameter format of the same calling operation of the same resource supported by the first API gateway.

Optionally, the resource parameter format of the same calling operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same calling operation of the same resource in the multiple cloud platforms.

Correspondingly, the resource parameter format corresponding to the same calling operation of the same resource in the multiple cloud platforms should be integrated to obtain the uniform resource parameter format of the same calling operation of the same resource supported by the first API gateway The process includes: obtaining the union of resource parameter formats corresponding to the same calling operation of the same resource in the multiple cloud platforms, and obtaining the resource parameter format of the same calling operation of the same resource supported by the first API gateway.

Corresponding to the first optional implementation manner, the first API request includes first resource parameter data, the second API request includes second resource parameter data, and the format of the first resource parameter data is supported by the first API gateway The format of the first resource parameter data is a resource parameter format supported by the second API gateway, and the second resource parameter data is obtained by converting the first resource parameter data into a resource parameter format.

In the second optional implementation manner, the first API gateway determines the interface calling rules of the supported API requests. The process includes:

For the same calling operation of the same resource in the multiple cloud platforms, the first API gateway determines the first interface calling rule corresponding to the same calling operation of the same resource based on the interface calling rule corresponding to the calling operation.

Optionally, the interface calling rule of the calling operation is used to indicate the interface set corresponding to the calling operation and the calling timing of the interface set;

When the interface set corresponding to the same calling operation of the same resource in the multiple cloud platforms and the calling sequence of the interface set are the same, the first interface calling rule corresponding to the same calling operation of the same resource is to call the interface according to the calling sequence. API interface in the interface set; when the same call operation of the same resource in the multiple cloud platforms corresponds to the same interface set and the call sequence is different, the first interface call rule corresponding to the same call operation of the same resource is to use one API Request to call the API interface in the interface set corresponding to the same calling operation; when the same calling operation of the same resource in the multiple cloud platforms corresponds to different interface sets, the first interface calling rule corresponding to the same calling operation of the same resource To use one API request to call the API interface in the interface set corresponding to the same calling operation.

Corresponding to the second optional implementation manner, the second API request is sent by the first API gateway based on a second interface invocation rule, and the second interface invocation rule is an interface invocation rule supported by the second API gateway. The second interface call rule is determined by the first API gateway based on the first interface call rule supported by the first API gateway and the first API request; the method further includes:

The first API gateway receives the second API response sent by the second API gateway; based on the second API response, the first API gateway replies with the first API to the sender of the first API request according to the first interface calling rule response.

Optionally, the API response includes resource parameter data. The resource parameter data included in the second API response sent by the second API follows the resource parameter format supported by the API gateway of the target cloud platform. The first API gateway publishes the format of the API request that it supports. Therefore, the user learns the first resource parameter format supported by the first API gateway. If the first API gateway directly passes the resource parameter data included in the second API response The first API response is fed back to the user, and the user also needs to learn the resource parameter format supported by the second API gateway, which will increase the user's learning cost. In the embodiment of the present application, the first API gateway may also escape the resource parameter data in the second API response sent by the second API gateway to obtain the resource parameter data in the first API response, which can reduce user learning costs.

Assuming that the first API response includes third resource parameter data, the second API response includes fourth resource parameter data, the format of the third resource parameter data is the resource parameter format supported by the first API gateway, and the format of the third resource parameter data is the first Second, the resource parameter format supported by the API gateway, the third resource parameter data is obtained by the first API gateway converting the fourth resource parameter data into the resource parameter format.

It should be noted that in the foregoing first optional implementation manner and the second optional implementation manner, the resources provided by multiple cloud platforms provide the same or similar services, and the first API gateway needs to be determined in advance in multiple cloud platforms The same resource, that is, the resource of the same resource type, is used to integrate the resource format of the same resource. Optionally, the same resource is a resource whose similarity defined by the resource is greater than a similarity threshold. Or, the same type of resource is a resource whose identifier of the resource has a similarity greater than the second similarity threshold.

Optionally, in addition to the aforementioned format integration function for API requests, the first API gateway also supports other functions. For example, the first API gateway supports the presentation function of service information, and the method further includes: the first API gateway uses the user interface cloud Service information of the resources of the platform, where the service information includes at least one of service capability information and service prices.

There may be multiple situations when the first API gateway obtains the service information. For example, after receiving the service information retrieval request through the user interface, the first API gateway obtains the service information of the resources of the cloud platform; or, after receiving the first API request, the first API gateway obtains the cloud platform The service information of the resource.

Optionally, when the presented capability information of the resource includes multiple sets of capability information corresponding to multiple resources on a one-to-one basis, each set of capability information may be presented in the form of a list.

In an implementation manner, after receiving the service information retrieval request, the first API gateway obtains the service information of the resources of the cloud platform, and presents the obtained service information through the user interface, which can realize the retrieval function of the service information through the user interface , Which is convenient for users to search on demand and get the service information they want to obtain. Users do not need to check whether resources meet their own needs on a cloud platform one by one, reducing user operation complexity and improving user experience.

In another implementation manner, after receiving the first API request, the first API gateway obtains the service information of the resources of the cloud platform, and presents the obtained service information through the user interface, which can realize that when the user makes an interface call, The user provides the service information of the resource that meets the demand, so that the user can understand the service information of the resource and make better interface calls.

In another implementation manner, the first API gateway may obtain the latest capability information of the resources of the cloud platform in the designated storage space after detecting that the user accesses the specified page for the presentation of capability information through the user interface, and The capacity information of the latest cloud platform resources is presented through the designated page. When the presented cloud platform is multiple cloud platforms managed by the first API gateway, it is convenient for the user to have an overall understanding of the capability information of the resources of the cloud platform managed by the first API gateway.

It should be noted that the aforementioned capability information may be real-time capability information, that is, the capability information is dynamically variable; the capability information may also be rated capability information, and the rated capability information is fixed and used to reflect resource Capability limit. When the capability information is real-time capability information, the first API gateway can present the real-time capability information of the resource to realize the user's timely and accurate understanding of the current capability information and improve the user experience.

Optionally, the target cloud platform is determined based on a selection instruction sent by the management node, the selection instruction is used to instruct the target cloud platform, and the selection instruction is received by the management node through a user interface; or, the target cloud platform is based on If the selection instruction sent by the client is determined, the selection instruction is used to indicate the target cloud platform; or, the first API request includes the identifier of the target cloud platform.

Optionally, the first API gateway also supports a resource migration function across cloud platforms. Then the method further includes: the first API gateway converts the resource parameter format of the resource parameter data of the resource to be migrated into the resource parameter format supported by the API gateway of the target cloud platform; the first API gateway converts the converted resource parameter data Sent to the API gateway of the destination cloud platform.

Optionally, the first API request is sent by the client to the first API gateway; or, the first API request is received by the management node on the user interface and sent to the first API gateway.

Optionally, the calling operation indicated by the first API request includes any one of the following: resource establishment operation, resource deletion operation, resource modification operation, and resource query operation.

In a second aspect, a communication device is provided, which is applied to a first application program interface API gateway. The device may include at least one module, and the at least one module may be used to implement the above-mentioned first aspect or various aspects of the first aspect. It is possible to implement the provided communication method.

In a third aspect, the present application provides a communication system. The communication system includes: a first API gateway and multiple cloud platforms, each cloud platform includes an API gateway, and the first API gateway includes any one described in the second aspect的通信装置。 Communication device.

In a third aspect, this application provides a computer device including a processor and a memory. The memory stores computer instructions; the processor executes the computer instructions stored in the memory, so that the computer device executes the methods provided by the foregoing first aspect or various possible implementations of the first aspect, so that the computer device deploys the foregoing second aspect or the first aspect. The communication device provided by various possible implementations of the two aspects.

In a fourth aspect, the present application provides a computer-readable storage medium having computer instructions stored in the computer-readable storage medium, and the computer instructions instruct the computer device to execute the above-mentioned first aspect or various possible implementations of the first aspect. The method or the computer instruction instructs the computer device to deploy the communication device provided by the foregoing second aspect or various possible implementations of the second aspect.

In a fifth aspect, the present application provides a computer program product. The computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device can read the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the above-mentioned first aspect or the methods provided by various possible implementations of the first aspect, so that the computer The device deploys the communication device provided by the foregoing second aspect or various possible implementations of the second aspect.

In a sixth aspect, a chip is provided. The chip may include a programmable logic circuit and/or program instructions, and is used to implement any communication method as in the first aspect when the chip is running.

The beneficial effects brought about by the technical solutions provided by the embodiments of the present application are:

Since the first API gateway is newly added, it provides a unified entrance for API interface calls of multiple cloud platforms. Therefore, the user-oriented API gateway is the first API gateway, and the user only needs to program according to the resource format supported by the first API gateway or The call operation is triggered through the user interface of the management node, which reduces the user's repeated learning and configuration costs for similar resources (that is, the aforementioned same resource), and improves user experience.

In addition, the service information presentation function of the first API gateway can present the capability information of the resource of the cloud platform to the user, so that the user can understand the capability information of the resource.

In the embodiments of the present application, since the first API provides users with a unified resource format, the communication method provided in the embodiments of the present application can also be used for resource orchestration across cloud platforms. The user arranges and generates a unified resource template in a blueprint. The user only needs to set in the resource template which cloud platform (ie the aforementioned target cloud platform) each resource of the user system or application is deployed on, and then run the set resource template Deploy instances on multiple cloud platforms, and set the resource template of the target cloud platform as the aforementioned client. This can effectively reduce user operations and improve resource deployment efficiency.

In the embodiments of this application, if a user needs to perform resource migration across cloud platforms, he only needs to specify the source cloud platform and the destination cloud platform through a resource migration request or other means, and the first API gateway can realize automatic resource migration across cloud platforms. There is no need for the user to reprogram, reducing operation complexity and improving user experience.

Description of the drawings

FIG. 1 is a schematic diagram of an application scenario of a communication system involved in a communication method provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario of another communication system provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 4 is a schematic flowchart of another communication method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a user interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another user interface provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application;

FIG. 9 is a schematic structural diagram of another communication device provided by an exemplary embodiment of the present application;

FIG. 10 is a schematic structural diagram of another communication device provided by an exemplary embodiment of the present application;

FIG. 11 is a schematic structural diagram of still another communication device according to an exemplary embodiment of the present application;

FIG. 12 is a schematic structural diagram of a communication device provided by another exemplary embodiment of the present application;

FIG. 13 is a schematic structural diagram of another communication device provided by another exemplary embodiment of the present application;

FIG. 14 schematically provides a possible basic hardware architecture in an actual application scenario of the first API gateway provided by an embodiment of the present application;

FIG. 15 schematically provides a possible basic hardware architecture of a computer device provided in an embodiment of the present application.

Detailed ways

In order to make the principles and technical solutions of the present application clearer, the implementation manners of the present application will be further described in detail below with reference to the accompanying drawings.

In order to facilitate readers' understanding, the terms involved in the embodiments of the present application are explained below.

Cloud platform, also known as cloud system, cloud environment or cloud, is a software system for cloud technology (also known as cloud computing technology) services provided by cloud providers.

Public cloud is a cloud platform provided by a third-party public cloud provider for a large number of individuals or enterprises. In public clouds, hardware, software, and other structures are owned and managed by third-party public cloud providers.

Private cloud is a dedicated cloud platform for an enterprise or organization. The private cloud can be operated internally by the corresponding enterprise or organization. Private cloud is mainly for enterprise users, also known as enterprise cloud.

Hybrid cloud refers to a cloud platform formed by different cloud platforms. Hybrid cloud includes at least two cloud platforms, also known as multi-cloud platforms or multi-clouds. Optionally, hybrid cloud combines public and private clouds. For security reasons, some enterprise users prefer to store data in private clouds, but at the same time hope to obtain computing resources from public clouds. In this case, hybrid clouds including public clouds and private clouds are increasingly adopted. Hybrid cloud mixes and matches public and private clouds to obtain good usage results.

Virtual Machine (VM) refers to a complete computer system with complete hardware system functions that is simulated by software and runs in an isolated environment. The work that can be done in a physical computer (referred to as a physical machine) can be realized in a virtual machine. When creating a virtual machine in a computer, part of the hard disk and memory capacity of the physical computer needs to be used as the hard disk and memory capacity of the virtual machine. Optionally, each virtual machine has an independent Complementary Metal Oxide Semiconductor (CMOS), hard disk, and operating system, and the virtual machine can be operated like a physical computer.

Container (container), also called container image, is a lightweight independent executable software package built with container technology. Container technology refers to a virtualization technology in a computer operating system, which enables processes to run in a relatively independent and isolated environment (including independent file systems, namespaces and/or resource views, etc.), thereby simplifying software The deployment process enhances the portability and security of the software, and improves the utilization of system resources. Container technology is widely used in service-oriented scenarios in the field of cloud computing.

Application program interface, also known as program interface, is the "interface between program and operating system" provided by the cloud platform's operating system to users, such as programmers. This interface is for users to use when programming. Through the application program interface, users can access resources in the cloud platform and obtain corresponding services. An application program interface is a collection of definitions, functions, procedures, and/or protocols. For example, an application program interface of a cloud platform includes one or more system calls, and each system call is a program that can complete a specific function.

API Gateway (Application Programming Interface Gateway, APIG), a gateway that provides API hosting services, can perform unified authentication, metering, publishing, and/or flow control management of APIs.

Services, including: computing services, storage services or network services, etc. The devices or functions that the user equipment can access on the cloud platform can be regarded as the services provided by the cloud platform.

Resources, hardware or software resources used to provide services. For example, corresponding to computing services, storage services, or network services, resources include computing resources, storage resources, or network resources. Optionally, the computing resources include central processing unit (CPU, central processing unit) resources, memory resources, and/or hard disk resources.

FIG. 1 is a schematic diagram of an application scenario of a communication system involved in a communication method provided by an embodiment of the present application. As shown in FIG. 1, the communication system includes: a first API gateway 101, multiple cloud platforms 102, and one or more user equipment 103. Wherein, each cloud platform 102 includes an API gateway 1021, and each cloud platform 102 is deployed with one or more resources to provide services for the user equipment 103, and multiple cloud platforms 102 correspond to multiple API gateways 1021 one-to-one. . The first API gateway 101 establishes a communication connection with API gateways 1021 of multiple cloud platforms 102. Optionally, the first API gateway 101 also establishes a communication connection with the user equipment 103. The first API gateway 101 is used to manage the information communicated between the user equipment 103 and the API gateways 1021 of the multiple cloud platforms 102. The user equipment 103 may implement communication with the API gateway 1021 of the multiple cloud platforms 102 through the first API gateway 101. Optionally, the user equipment 103 is a computer device such as a computer or a notebook computer. Optionally, the user equipment 103 may be installed with a client, and the user realizes communication with the first API gateway 101 through the client. The client is usually programmed by the user.

Fig. 2 is a schematic diagram of an application scenario of another communication system provided by an embodiment of the present application. On the basis of FIG. 1, the communication system further includes: a management node 104, and the management node 101 may be a single node. It can be a server or a server cluster composed of multiple servers. It can also be one or more set minimum processing units, such as virtual machines or containers. The management node 104 respectively establishes a communication connection with the first API gateway 101 and the user equipment 103. The management node 104 may provide a user interface (UI) for the user equipment 103 for the user equipment 103 and the first API gateway 101 To communicate. In an optional manner, a web client corresponding to the management node 104 is installed in the user equipment 103, and the user equipment 103 accesses the user interface provided by the management node 104 by running the web client; in another optional manner A browser is installed in the user equipment 103, and the user equipment 103 can access the user interface of the webpage version provided by the management node 104 by running the browser.

Among them, FIG. 1 and FIG. 2 only take two cloud platforms 102 and one user equipment 103 as an example for description, and do not limit the number of cloud platforms and the number of user equipment in the communication system.

Optionally, the first API gateway is an application in the form of a microservice, and each component included in it can be deployed in a virtual machine or container that is reachable on the network.

In traditional communication systems including hybrid clouds, when user equipment accesses different cloud platforms, it needs to issue different API requests conforming to formats supported by different cloud platforms, resulting in low communication flexibility between the user equipment and different cloud platforms. In addition, users need to be familiar with the API request formats supported by different cloud platforms, which results in high learning costs and poor user experience.

In the communication system provided by the embodiment of the present application, since the first API gateway is newly added, the information communicated between the user equipment 103 and the API gateways 1021 of the multiple cloud platforms 102 is uniformly managed, without the need for users to target different cloud platforms. Different API requests are sent through the user equipment, thereby reducing the user's operational complexity and improving the communication flexibility between the user equipment and different cloud platforms. The user only needs to learn the API request format supported by the first API gateway to access each cloud platform managed by the first API gateway. Therefore, the user's learning cost is reduced and the user experience is improved.

In addition, in the communication system provided by the embodiment of the present application, the newly added management node can also realize the communication between the user and different cloud platforms through the user interface, which further improves the communication flexibility between the user equipment and the different cloud platforms.

FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application. The communication method may be applied to the communication system shown in FIG. 1 or FIG. 2. As shown in Figure 3, the method includes:

S301. The first API gateway determines the format of the supported API request.

In the embodiment of the present application, the first API gateway needs to predetermine the format of the API request that it supports, so as to provide convenience for subsequent users. An API request is a call request sent by a user device when calling an API interface. The format of the API request is consistent with the format of the resource deployed by the first API gateway, so it is also called the resource format. The resource format mainly includes two parts, one part is the resource parameter format (schema, also called specification) carried in the API request, referred to as the resource parameter format or API format; the other part includes the interface calling rules corresponding to the API request. Among them, the resource parameter refers to the parameter (also called the object) of the resource to which the data belongs. The resource parameter format is the structural definition of the object of the data, that is, the definition of the resource parameter. For example, the resource parameter format corresponding to a certain call operation of a resource is: the resource parameter is the name and phone number, or the resource parameter is the number of CPUs and/or the number of GPUs (Graphics Processing Unit) And other computing resource specifications. The interface calling rules of the calling operation are used to indicate the interface set (also called API interface set) corresponding to the calling operation and the calling sequence of the interface set. Among them, the time sequence of the interface set called through the same API request is the same, and the time sequence of the interface set called through different API requests is different. For example, the interface calling rule corresponding to a certain calling operation of a certain resource is: the interface set includes API interface 1 and API interface 2. The timing of API interface 1 and API interface 2 is that API interface 1 comes first, and API interface 2 comes later. . That is, the interface calling rule is: call API interface 1 and API interface 2 in two times according to time sequence. An interface set includes at least one API interface identifier, and the API interface identifier is used to identify one API interface. Optionally, the identifier of the API interface is the interface routing address of the API interface, such as a uniform resource identifier (URI).

As shown in Figure 1 and Figure 2, each cloud platform is deployed with one or more resources, and the first API gateway supports different invocation operations to different resources in the cloud platform. In this way, for each resource, the user equipment can perform different calling operations.

Wherein, the calling operations supported by the first API gateway include any of the following: resource creation operations (also called creation operations or adding operations), resource deletion operations, resource modification operations, and resource query operations. The aforementioned resource establishment operations are used for the establishment of resources, such as cloud disks, networks, virtual machines, or containers; resource deletion operations are used for resource deletion, such as cloud disks, networks, virtual machines, or containers; resource modification Operations are used to modify resources, such as modifying the rules of computing resources, mirroring versions, or network bandwidth, etc.; resource query operations are used to query resources, such as querying resource running status or parameter specifications.

Then, the format of the API request supported by the aforementioned first API gateway includes the format of the API request corresponding to the multiple calling operations of multiple resources supported by the first API gateway. The resource parameter format supported by the first API gateway includes resource parameter formats corresponding to multiple invocation operations of multiple resources supported by the first API gateway. The interface calling rules supported by the first API gateway include interface calling rules corresponding to multiple calling operations of multiple resources supported by the first API gateway.

Optionally, the API request carries a corresponding call operation identifier, and the call operation identifier is used to identify the call operation. For example, the identification of the calling operation may be expressed by an action (verb) in the API request. In order to facilitate the reader's understanding, the identifier of the subsequent call operation is represented by the name of the call operation.

For each call operation of each resource, the first API gateway needs to determine a unified API request format, which includes a unified resource parameter format and a unified interface calling rule, so as to provide convenience for subsequent users.

In the first aspect, the first API gateway determines the resource parameter format of the supported API request. The process includes:

Step A1. The first API gateway obtains resource parameter formats corresponding to different invocation operations of various resources in multiple cloud platforms.

In the first optional implementation manner, the first API gateway may determine the resource parameter format corresponding to different invocation operations of each resource in the multiple cloud platforms based on the resource definitions of the multiple resources in the multiple cloud platforms. The resource definition is used to describe the corresponding resource, which includes the resource parameters involved in the resource. Resource definitions are usually stored in text form. The first API gateway may obtain resource definitions of multiple resources in multiple cloud platforms, and obtain resource parameter formats corresponding to different invocation operations of various resources in multiple cloud platforms by identifying the resource definitions. Among them, the resource definitions of multiple cloud platforms can be pulled from multiple cloud platforms by the first API gateway, or the resource definitions of multiple cloud platforms can be specified by the first API gateway storing resource definitions of multiple cloud platforms Storage space 1 is extracted. Among them, the resource definitions of multiple cloud platforms can be pre-determined by the management personnel of the communication system and input into the designated storage space 1, or the resource definitions of multiple cloud platforms can be pulled from the designated storage space 1 in multiple cloud platforms And maintain. The designated storage space 1 may be a database.

Optionally, the first API gateway may also maintain different versions of resource definitions in the database, and the administrator of the communication system may also manage the resource definitions in the database, such as adding, deleting, modifying, and querying resource definitions.

In the second optional implementation manner, the resource parameter format corresponding to different invocation operations of various resources in multiple cloud platforms can be predetermined by the management personnel of the communication system and input into the designated storage space 2, where the first API gateway is located. The designated storage space 2 only needs to extract resource parameter formats corresponding to different invocation operations of various resources in multiple cloud platforms. The designated storage space 2 may be a database.

Step A2. The first API gateway integrates resource parameter formats corresponding to the same calling operation of the same resource in multiple cloud platforms to obtain the resource parameter format of the same calling operation of the same resource supported by the first API gateway.

For each call operation of each resource, the first API gateway needs to determine a unified resource parameter format, so as to provide convenience for subsequent users. Optionally, the first API gateway integrates resource parameter formats corresponding to the same calling operation of the same resource in multiple cloud platforms to obtain the resource parameter format of the same calling operation of the same resource supported by the first API gateway. For example, the resource parameter format of the same calling operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same calling operation of the same resource in multiple cloud platforms. Then the first API gateway can obtain the union of resource parameter formats corresponding to the same call operation of the same resource in multiple cloud platforms to obtain the resource parameter format of the same call operation of the same resource supported by the first API gateway .

For example, suppose that multiple cloud platforms are cloud platform 1 to cloud platform n, n≥2, and the same call operation of the same resource is call operation 1 of resource 1, then the first API gateway obtains the cloud platform 1 to cloud platform n The union of the resource parameter formats corresponding to the calling operation 1 of the resource 1 obtains the resource parameter format of the calling operation 1 of the resource 1 supported by the first API gateway.

For example, suppose n=2, resource 1 is a virtual machine used to provide disk performance optimization, and call operation 1 is a query operation. The resource parameter format corresponding to the call operation 1 of the resource 1 of the cloud platform 1 is: the resource parameters are names and phone numbers respectively; the resource parameter format corresponding to the call operation 1 of the resource 1 of the cloud platform 2 is that the resource parameters are names, Phone number and favorite identifier (the favorite identifier is used to indicate whether to favorite the corresponding phone number). Then the first API gateway obtains the union of the resource parameter format corresponding to the call operation 1 of the resource 1 of the cloud platform 1 and the resource parameter format corresponding to the call operation 1 of the resource 1 of the cloud platform 2, and the obtained first API gateway supports The resource parameter format corresponding to the invocation operation 1 of resource 1, for example, the finally obtained resource parameter format is: the resource parameters are respectively the name, phone number, and collection identifier.

Obtaining the resource parameter format by taking the union method can ensure that the finally obtained resource parameter format is not only a unified format, but also meets the requirements of each cloud platform for the resource parameter format.

In the second aspect, the first API gateway determines the interface calling rules of the supported API requests.

For the same calling operation of the same resource in multiple cloud platforms, the first API gateway determines the first interface calling rule corresponding to the same calling operation of the same resource based on the interface calling rule corresponding to the calling operation.

Optionally, assuming that the same invocation operation of the same resource in multiple cloud platforms is the first invocation operation, for the first invocation operation, the number of interface invocations indicated by the first interface invocation rule (equal to the number of API requests) Less than or equal to the number of interface calls indicated by the API gateway corresponding to the API gateway of each of the multiple cloud platforms. For example, the first interface invocation rule corresponding to the first invocation operation satisfies:

When the interface set corresponding to the first calling operation of multiple cloud platforms and the calling timing of the interface set are the same, the first interface calling rule corresponding to the first calling operation is to call the API interfaces in the interface set according to the calling timing; when multiple cloud platforms The first call operation corresponds to the same set of interfaces, and the call sequence is different. The first interface call rule corresponding to the first call operation is to use one API request to call the API interface in the interface set corresponding to the same call operation. The corresponding interface set is the same. Therefore, this one API request can carry the identifier of the API interface in the interface set (such as uri), or it may not carry the identifier of the API interface in the interface set, but only carry the instruction information indicating the call to all API interfaces in the interface set; The interface sets corresponding to the first calling operation of each cloud platform are different. The first interface calling rule corresponding to the first calling operation is to use one API request to call the API interface in the interface set corresponding to the same calling operation. Corresponding interface sets are different. One API request cannot uniformly carry the API interface identifiers of different interface sets. Therefore, this API request may not carry the identifiers of the API interfaces in the interface set, but only carry the instruction information indicating to call all the API interfaces in the interface set, thus Ensure that for different cloud platforms, all API interfaces in the interface set can be called.

For example, if multiple cloud platforms are cloud platform 1 to cloud platform n, n≥2, and the same call operation of the same resource is call operation 2 of resource 2, then the first API gateway is based on the resources of cloud platform 1 to cloud platform n The interface calling rule corresponding to the calling operation 2 of 2 determines the first interface calling rule of the calling operation 2 of the resource 2 supported by the first API gateway.

Assuming n=2, resource 2 is a virtual machine used to provide GPU acceleration services, and calling operation 2 is a setup operation. If the interface calling rule corresponding to the calling operation 2 of resource 2 of cloud platform 1 is to call API interface 1 and API interface 2 in turn, that is, the interface set includes: API interface 1 and API interface 2, and the calling sequence is that API interface 1 is in First, the API interface 2 comes later; the interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platform 2 is to call the API interface 1 and the API interface 2 in turn. Then, the interface calling rule corresponding to the calling operation 2 of resource 2 supported by the first API gateway is: calling API interface 1 and API interface 2 in turn.

If the interface call rule corresponding to the call operation 2 of resource 2 of cloud platform 1 is to call API interface 2 and API interface 1 in turn, that is, the interface set includes: API interface 1 and API interface 2, and the calling sequence is API interface 2 in First, the API interface 1 comes later; the interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platform 2 is to call the API interface 1 and the API interface 2 in turn. Then, the interface calling rule corresponding to the calling operation 2 of resource 2 supported by the first API gateway is: calling API interface 1 and API interface 2 with one API request.

The interface calling rule corresponding to the calling operation 2 of resource 2 of cloud platform 1 is to call API interface 1, API interface 2 and interface 3 in turn, that is, the interface set includes: API interface 1 and API interface 2, and the calling sequence is API interface. 1 first, API interface 2 is centered, and interface 3 is last; the interface calling rule corresponding to the calling operation 2 of resource 2 of cloud platform 2 is to call API interface 1 and API interface 2 in turn. Then, the interface calling rule corresponding to the calling operation 2 of the resource 2 supported by the first API gateway is: one API request is used to call the API interface in the interface set corresponding to the calling operation 2.

Due to different calling operations for different resources of different cloud platforms, the corresponding interface calling rules are different. If the unified first interface calling rule changes greatly compared with the interface calling rules of each cloud platform, the subsequent first interface calling rules will actually be used. When used, it is easy to generate more storage and calculation overhead. Therefore, the aforementioned first interface calling rule is adopted. When the interface set corresponding to the first calling operation of multiple cloud platforms and the calling sequence of the interface set are the same, the first interface calling rule corresponding to the first calling operation is to call the interface according to the calling sequence. The centralized API interface, that is, the first interface call rule corresponding to the first call operation is unchanged from the interface call rule corresponding to the first call operation of multiple cloud platforms, which can reduce the first interface call rule compared to each The change of the interface call rules of the cloud platform further reduces the storage and calculation overhead when the first interface call rule is actually used.

It is worth noting that the first interface invocation rule corresponding to the first invocation operation may also have other setting methods. For example, for the same resource, the first interface calling rule is to use one API request to call the API interface in the interface set corresponding to one calling operation. In this way, for the same resource, no matter what kind of calling operation, for one calling operation, one API request is used to call the API interface in the interface set. Thereby, the interface calling rules of the same resource can be unified, and the learning cost of users can be reduced.

For another example, for different resources in the same cloud platform, the first interface calling rule is to use one API request to call the API interface in the interface set corresponding to one calling operation. In this way, for the same cloud platform, no matter what kind of resource and what kind of call operation, for one call operation, one API request is used to call the API interface in the interface set. In this way, the interface calling rules of different resources of the same cloud platform can be unified, and the learning cost of users can be reduced.

For another example, for different resources in multiple cloud platforms, the first interface calling rule is to use one API request to call the API interface in the interface set corresponding to one calling operation. In this way, no matter what kind of resource and what kind of calling operation, for one calling operation, one API request is used to call the API interface in the interface set. In this way, the interface calling rules of different resources of different cloud platforms can be unified, and the learning cost of users can be reduced.

It should be noted that in the aforementioned first aspect and second aspect, the services provided by the resources deployed by multiple cloud platforms are the same or similar, and the first API gateway needs to pre-determine the same type of resource in multiple cloud platforms, that is, resources. Resources of the same type, and then the integration of the resource format of the same resource. Optionally, the resource type is divided according to the service provided by the resource, for example, divided into GPU acceleration, disk performance optimization, or network speed and bandwidth optimization. The first API gateway determines resources of the same resource type in multiple cloud platforms There are several optional implementation methods:

In the first optional implementation manner, the same resource is a resource whose similarity defined by the resource is greater than the similarity threshold. For example, the value range of the similarity threshold is 80% to 90%. The first API gateway may determine resources with similarity of resource definitions in multiple cloud platforms that are greater than the similarity threshold as the same resource.

In the foregoing first optional implementation manner, the first API gateway may use a clustering algorithm to determine resources of the same resource type among multiple cloud platforms. For example, the first API gateway may execute a clustering algorithm on resource definitions of resources deployed in multiple cloud platforms. The first API gateway may also use other algorithms to determine resources of the same resource type in multiple cloud platforms. The embodiment of the application does not limit this.

In the second alternative implementation, the same resource is preset.

In the foregoing two aspects, after the first API gateway determines the format of the API request (that is, the resource format) that it supports, it can store the determined resource format in the designated storage space 3. The designated storage space 3 may be a database.

The foregoing two aspects are described by taking the first API gateway automatically determining the format of the API request supported by itself as an example. In the embodiment of this application, the resource format supported by the first API gateway may also be predetermined by the management personnel of the communication system and input to The storage space 3 is designated, and the first API gateway extracts the required resource format in the designated storage space 3.

Optionally, the API interface corresponding to the resource format stored in the designated storage space 3 needs to be registered in the designated storage space 3. The registered API interface is the interface that the first API gateway can call, and the unregistered API interface is due to its The resource format of the cloud platform to which it belongs is not unified, so it cannot be called by the first API gateway. The resource format stored in the designated storage space 3 can be manually adjusted by the manager, such as adding, modifying or deleting.

It is worth noting that the designated storage spaces 1, 2 and 3 in the embodiment of the present application may be the same or different, which is not limited in the embodiment of the present application.

S302. The first API gateway publishes the format of the API request supported by the first API gateway.

In an optional manner, the first API gateway may push the format of the API request supported by the first API gateway to the client of the user equipment, so as to realize the publication of the format of the API request; in another optional manner, The first API gateway may present the format of the API request supported by the first API gateway through a user interface. For example, the format of the API request is presented through the user interface of the aforementioned management node. The first API gateway implements the pre-arrangement of the API request format between the first API gateway and the user equipment by publishing the format of the API request supported by the first API gateway.

Optionally, there are multiple ways of expressing the format of the API request supported by the aforementioned first API gateway. In an optional way, it can be represented by a software model; in another optional way, it can be represented by a software template; in another optional way, it can also be represented by a table or Graphical representation. The embodiment of this application does not limit the format of the API request. For example, the format of the aforementioned API request can be set with reference to an industry standard format, such as the format of the openAPI2.0 standard.

S303. The user equipment sends a first API request to the first API gateway.

The format of the first API request is a format supported by the first API gateway. The user equipment may send the first API request to the first API gateway in multiple ways. For example, in the first method, the user equipment has a client installed, and the first API request is sent by the client to the first API gateway, that is, the user equipment sends the first API request through the client; in the second method , The user equipment sends a first API request to the management node through the user interface provided by the management node, and the first API request is received by the management node on the user interface and sent to the first API gateway.

S304. After receiving the first API request, the first API gateway determines a target cloud platform for responding to the first API request among the multiple cloud platforms.

Corresponding to the aforementioned S303, there are multiple ways for the first API gateway to receive the first API request. Corresponding to the first method of S303, the first API gateway receives the first API request sent by the user equipment through the client; corresponding to the second method of S303, the first API gateway receives the first API request sent by the management node .

There are multiple ways for the first API gateway to determine the target cloud platform for responding to the first API request among multiple cloud platforms. The embodiments of this application take the following optional methods as examples for description:

In the first optional manner, the target cloud platform is determined based on a selection instruction sent by the management node, the selection instruction is used to instruct the target cloud platform, and the selection instruction is received by the management node through a user interface. Correspondingly, after receiving the selection instruction, the first API gateway determines the target cloud platform based on the selection instruction. For example, the management node presents the identities of multiple cloud platforms to the user equipment through the user interface. If the user wants to operate on the resources in a certain cloud platform, he can select and operate on the user interface through the user equipment, thereby triggering the management node to generate the corresponding The selection instruction carries the identification of the target cloud platform selected by the user, and the management node sends the selection instruction to the first API gateway. After receiving the selection instruction, the first API gateway extracts the identification of the target cloud platform to Determine the target cloud platform. The identifier of the cloud platform may be the name of the cloud platform, such as "AA Cloud" or "BB Cloud", or the identifier of the API gateway in the cloud platform, such as the address of the API gateway.

Optionally, the management node may present the identities of multiple cloud platforms after the first API gateway receives the first API request; or after receiving the access instruction sent by the user equipment, the management node may present the identities of the multiple cloud platforms.

In the second optional manner, the target cloud platform is determined based on the selection instruction sent by the client, and the selection instruction is used to instruct the target cloud platform. Correspondingly, after receiving the selection instruction, the first API gateway determines the target cloud platform based on the selection instruction. For example, if a user wants to operate on a resource in a cloud platform, he can generate a corresponding selection instruction through the client running on the user device. The selection instruction carries the identifier of the target cloud platform selected by the user, and the client selects The instruction is sent to the first API gateway, and after receiving the selection instruction, the first API gateway extracts the identifier of the target cloud platform to determine the target cloud platform.

Optionally, the client may send the selection instruction after the first API gateway receives the first API request, or before the first API gateway receives the first API request, the client may send the selection instruction. This is not limited.

In the third optional manner, the first API request includes the identification of the target cloud platform. Correspondingly, after receiving the first API request, the first API gateway determines the target cloud platform based on the first API request.

It is worth noting that, after receiving the first API request, the first API gateway may first authenticate the first API request, and after the authentication succeeds, determine the target cloud platform. If the authentication fails, an API response indicating the authentication failure is sent to the user equipment, or the action is stopped. For example, referring to S302, the first API gateway may detect whether the API interface required to be called by the first API request is a registered interface, and if the API interface required to be called by the first API request is not a registered interface, it is determined that the authentication fails; if The API interface that the first API request needs to call is a registered interface, and it is determined that the authentication is successful. Alternatively, the first API gateway may detect whether the user account carried in the first API request has the permission to access the first API gateway (or whether it is a legal account), if the user account carried in the first API request does not have access to the first API The authority of the gateway (or not a legal account) determines that the authentication fails; if the user account carried in the first API request has the authority to access the first API gateway (or is a legal account), it is determined that the authentication is successful.

The first API gateway can ensure the security of the communication system and reduce unnecessary operations by authenticating the API request.

S305. The first API gateway determines a second API request based on the first API request, the second API request is determined based on the first API request, and the format of the second API request is a format supported by the second API gateway, and the second API gateway It is the API gateway of the target cloud platform.

With reference to S301 and S302, the API request includes resource parameter data. Since the first API gateway publishes the format of the API request it supports, the first API request sent by the user through the user device is sent in accordance with the resource parameter format supported by the first API gateway. When accessing the target cloud platform, the resource parameter The data follows the resource parameter format supported by the API gateway of the target cloud platform.

Assuming that the first API request includes first resource parameter data, the second API request includes second resource parameter data, the format of the first resource parameter data is the resource parameter format supported by the first API gateway, and the format of the first resource parameter data is the first resource parameter data format. 2. The resource parameter format supported by the API gateway, the second resource parameter data is obtained by the first resource parameter format conversion of the first resource parameter data by the first API gateway.

Among them, the first API gateway may perform resource parameter format conversion on the first resource parameter data in a variety of ways. The embodiment of the present application takes the following two optional methods as examples for description:

In the first optional manner, referring to the first aspect in S301, the first API gateway establishes the resource parameters supported by the API gateway of each of the multiple cloud platforms after determining the resource parameter format of the supported API request The first correspondence between the format and the resource parameter format supported by the first API gateway. After receiving the first API request, the first API gateway queries the first correspondence based on the identifier of the second API gateway to obtain the resource parameter format supported by the second API gateway; and based on the resource parameter format supported by the second API gateway, The first resource parameter data included in the first API request is escaped to obtain the second resource parameter data.

The first correspondence can be expressed in multiple ways. For example, the first correspondence may include multiple sub-correspondences that correspond to multiple call operations one-to-one, and each sub-correspondence is used to record the resource identifier and resource parameter format supported by the API gateway of the cloud platform under the corresponding call operation. Correspondence with the resource parameter format supported by the first API gateway.

For another example, the first correspondence may include multiple sub-correspondences corresponding to the identifiers of multiple resources one-to-one, and each sub-correspondence is used to record the identifier of the corresponding resource, the identifier of the call operation, and the API gateway of the cloud platform supports The corresponding relationship between the resource parameter format and the resource parameter format supported by the first API gateway. As an example, assuming that the first correspondence relationship includes multiple sub-correspondences corresponding to the identifiers of multiple resources one-to-one, the sub-correspondence corresponding to the identifier of a certain resource may be as shown in Table 1. Table 1 records the corresponding relationship between the call operation identifier, the resource parameter format supported by the API gateway of the cloud platform and the resource parameter format supported by the first API gateway under the identifier of the certain resource, where the call operation identifier uses the call The name of the operation indicates that the resource parameter format supported by the API gateway of the cloud platform may adopt the identifier of the API gateway and the identifier of the resource parameter format. It can be seen from Table 1 that there are two cloud platforms in the multiple cloud platforms deploying the resource corresponding to the identifier of the certain resource, the identifiers of the API gateways of the two cloud platforms are 1 and 2, respectively, and the identifier of the first API gateway Is 0. For the establishment operation, the resource parameter format X1 of the API gateway 1 corresponds to the resource parameter format M1 of the first AP1 gateway 0; for the establishment operation, the resource parameter format X2 of the API gateway 2 corresponds to the resource parameter format M1 of the first AP1 gateway 0; For the deletion operation, the resource parameter format Y1 of the API gateway 1 corresponds to the resource parameter format M2 of the first AP1 gateway 0; for the establishment operation, the resource parameter format Y2 of the API gateway 2 corresponds to the resource parameter format M2 of the first AP1 gateway 0. For other calling operations, refer to Table 1 for the corresponding relationship, which is not described in detail in the embodiment of the present application.

Table 1

For another example, the first correspondence may include the identity of the calling operation, the identity of the resource, and the correspondence between the resource parameter format supported by the API gateway of the cloud platform and the resource parameter format supported by the first API gateway.

In the second optional manner, referring to the first aspect in S301, after the first API gateway determines the resource parameter format of the supported API request, it is based on the resource parameters supported by the API gateway of each of the multiple cloud platforms Format, and the resource parameter format supported by the first API gateway, establish an escape model, which is used to output resource parameter data corresponding to the received API gateway identifier after receiving the API gateway identifier and resource parameter data. After receiving the first API request, the first API gateway inputs the first resource parameter data included in the first API request and the identification of the second API gateway (or the identification of the target cloud platform) into the escape model, and the escape The resource parameter data output by the model is determined to be the second resource parameter data.

Referring to step A1, if the resource parameter format of the same calling operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same calling operation of the same resource in multiple cloud platforms. In this way, the first resource parameter format includes the second resource parameter format, that is, the second parameter resource format belongs to the first resource parameter format, and the second resource parameter data may include data that is not required by the second API gateway, that is, invalid data. The data is data that does not correspond to the second parameter resource format. In an optional manner, the first API gateway may eliminate invalid data in the second parameter data, obtain updated second parameter data, and generate a second API request including the updated second parameter data . For example, the format of the first resource parameter is: the resource parameters are name, phone number, and age. The second resource parameter format is: the resource parameters are the name and the phone number respectively. Since the data corresponding to the age does not correspond to the second resource parameter format, the data corresponding to the age in the first resource parameter data is invalid data.

In another optional manner, the first API gateway may generate a second API request, the second API request includes the second parameter data, after the second API gateway receives the second API request, the second parameter data The invalid data in the data is eliminated, and the updated second parameter data is obtained.

S306. The first API gateway sends a second API request to the second API gateway.

Wherein, the second API request is sent by the first API gateway based on the second interface calling rule, the second interface calling rule is the interface calling rule supported by the second API gateway, and the second interface calling rule is based on the first API gateway by the first API gateway The supported first interface calling rules and the first API request are determined. The first API gateway sends the second API request to the second API gateway according to the second interface invocation rule, which can ensure that the sent second API request follows the interface invocation rule supported by the second API gateway, thereby ensuring the effective invocation of the API interface.

In the embodiment of the present application, the first API gateway may determine the second interface calling rule in multiple ways. For example, please refer to the second aspect of the aforementioned S301. After determining the interface calling rules of the supported API requests, the first API gateway establishes the interface calling rules supported by the API gateway of each cloud platform in the multiple cloud platforms and the first API. The second corresponding relationship of the interface invocation rule supported by the gateway. After receiving the first API request, the first API gateway queries the second correspondence based on the identifier of the second API gateway to obtain the second interface calling rule corresponding to the second API gateway.

The second correspondence can be expressed in multiple ways. For example, the second correspondence may include multiple sub-correspondences corresponding to multiple call operations one-to-one, and each sub-correspondence is used to record the resource identification and the interface call rules supported by the API gateway of the cloud platform under the corresponding call operation. Correspondence with the interface calling rules supported by the first API gateway.

For another example, the second correspondence may include multiple sub-correspondences corresponding to the identifiers of multiple resources one-to-one, and each sub-correspondence is used to record the identifier of the corresponding resource, the identifier of the call operation, and the API gateway support of the cloud platform. Correspondence between the interface calling rules of the API and the interface calling rules supported by the first API gateway. As an example, assuming that the second correspondence relationship includes multiple sub-correspondences corresponding to the identifiers of multiple resources one-to-one, the sub-correspondence corresponding to the identifier of a certain resource may be as shown in Table 2. This table 2 records the corresponding relationship between the call operation identifier, the interface call rule supported by the API gateway of the cloud platform, and the interface call rule supported by the first API gateway under the identifier of the certain resource, where the call operation identifier uses the call The name of the operation indicates that the interface call rule supported by the API gateway of the cloud platform can be expressed by the identifier of the API gateway and the identifier of the interface call rule. It can be seen from Table 2 that there are two cloud platforms in the multiple cloud platforms deploying the resource corresponding to the identifier of the certain resource, the API gateway identifiers of the two cloud platforms are 1 and 2, respectively, and the identifier of the first API gateway Is 0. For the establishment operation, the interface calling rule A1 of the API gateway 1 corresponds to the interface calling rule E1 of the first AP1 gateway 0; for the establishment operation, the interface calling rule A2 of the API gateway 2 corresponds to the interface calling rule E1 of the first AP1 gateway 0; For the deletion operation, the interface calling rule B1 of the API gateway 1 corresponds to the interface calling rule E2 of the first AP1 gateway 0; for the establishment operation, the interface calling rule B2 of the API gateway 2 corresponds to the interface calling rule E2 of the first AP1 gateway 0. For other calling operations, refer to Table 2 for the corresponding relationship, which is not described in detail in the embodiment of the present application.

Table 2

For another example, the second correspondence may include the identity of the calling operation, the identity of the resource, and the correspondence between the interface calling rules supported by the API gateway of the cloud platform and the interface calling rules supported by the first API gateway.

S307. The second API gateway sends a second API response to the first API gateway.

After receiving the second API request, the second API gateway calls the API interface in the target cloud platform according to the second API request, and after completing the interface call corresponding to the second API request, sends the second API to the first API gateway response.

It is worth noting that after receiving the second API request, the second API gateway may first authenticate the second API request, and after the authentication succeeds, perform the interface call action. If the authentication fails, an API response indicating the authentication failure is sent to the first API gateway, or the action is stopped. For example, the second API gateway can detect whether the API interface called by the second API request is a registered interface in the target cloud platform, and if the API interface called by the second API request is not a registered interface, it is determined that the authentication fails ; If the API interface to be called by the second API request is a registered interface, it is determined that the authentication is successful. Alternatively, the second API gateway may detect whether the user account carried in the second API request has the permission to access the second API gateway (or whether it is a legal account), if the user account carried in the second API request does not have access to the second API The authority of the gateway (or not a legal account) determines that the authentication fails; if the user account carried in the second API request has the authority to access the second API gateway (or is a legal account), it is determined that the authentication is successful.

The second API gateway can ensure the security of the communication system and reduce unnecessary operations by authenticating the API request.

S308. The second API gateway sends the first API response to the user equipment based on the second API response.

In the embodiment of the present application, the sender of the first API request is the user equipment. Corresponding to the aforementioned S303, the first API gateway sends the first API request to the client running on the user equipment, or sends the first API request to the management node. The management node forwards it to the user equipment.

Please refer to the aforementioned S302. Since the first API gateway publishes the format of the API request that it supports, the first API request sent by the user through the user device is sent according to the first interface calling rule supported by the first API gateway. When the API gateway returns the corresponding API response, it needs to follow the same interface call rule, that is, send the first API response according to the first interface call rule.

With reference to the second aspect of S302, assume that the same invocation operation of the same resource in multiple cloud platforms is the first invocation operation. For the first invocation operation, the number of interface invocations indicated by the first interface invocation rule is less than or equal to that of the multiple clouds. The number of interface calls indicated by the API gateway corresponding to each cloud platform of the platform. Therefore, the number of first API requests is less than or equal to the number of second API requests. Each API gateway responds to the received API request in a question-and-answer manner, that is, every time an API request is received, an API response is returned. Then in S303 to S308, the number of first API requests is equal to the number of first API responses; the number of second API requests is equal to the number of second API responses.

For example, when the first interface calling rule and the second interface calling rule are the same, the first API gateway sends a second API request to the second API gateway every time after receiving a first API request. After a second API response returned by the second API gateway, a first API response is sent to the sender of the first API request.

For example, the interface calling rules corresponding to the calling operation 2 of the resource 2 supported by the first API gateway and the second API gateway are both: calling API interface 1 and API interface 2 in turn. Then, after receiving the first API request for calling API interface 1, the first API gateway sends a second API request for calling API interface 1 to the second API gateway, and then receives the API interface 1 returned by the second API gateway. After the corresponding second API response, the first API response corresponding to API interface 1 is sent to the sender of the first API request; after receiving the first API request for calling API interface 2, the first API gateway sends the second API The API gateway sends the second API request for calling API interface 2, and after receiving the second API response corresponding to API interface 2 returned by the second API gateway, sends the first API request corresponding to API interface 2 to the sender of the first API request. API response.

When the number of the first API request is less than the number of the second API request, the first API gateway will execute at least two call processes in sequence according to the second interface call rule after receiving a first API request each time until the received The second API response can generate a first API response corresponding to the first API request, and then send the first API response to the sender of the first API request according to the first interface calling rule. Wherein, the calling process includes: sending a second API request to the second API gateway, and receiving a second API response sent by the second API gateway.

For example, the second interface calling rule is to call API interface 1 and API interface 2 in sequence, and the first interface calling rule is to call API interface 1 and API interface 2 with one API request. Then, after receiving the first API request for calling API interface 1 and API interface 2, the first API gateway sends a second API request for calling API interface 1 to the second API gateway, and returns after receiving the second API gateway After receiving the second API response corresponding to API interface 1 of the second API gateway, send a second API request for calling API interface 2 to the second API gateway. After receiving the second API response corresponding to API interface 2 returned by the second API gateway, send the second API request to the second API gateway. The sender of the first API request sends the first API response corresponding to the API interface 1 and the API interface 2 (that is, the first API response corresponding to the first API request).

Optionally, the API response includes resource parameter data. The resource parameter data included in the second API response sent by the second API follows the resource parameter format supported by the API gateway of the target cloud platform. The first API gateway publishes the format of the API request that it supports. Therefore, the user learns the first resource parameter format supported by the first API gateway. If the first API gateway directly passes the resource parameter data included in the second API response, The first API response is fed back to the user, and the user also needs to learn the resource parameter format supported by the second API gateway, which will increase the user's learning cost. In the embodiment of the present application, the first API gateway may also escape the resource parameter data in the second API response sent by the second API gateway to obtain the resource parameter data in the first API response, which can reduce user learning costs.

Among them, the first API gateway may perform resource parameter format conversion on the fourth resource parameter data in a variety of ways. The embodiment of the present application takes the following two optional methods as examples for description:

In the first optional manner, referring to the first aspect in S301, the first API gateway establishes the resource parameters supported by the API gateway of each of the multiple cloud platforms after determining the resource parameter format of the supported API request The first correspondence between the format and the resource parameter format supported by the first API gateway. After receiving the second API response, the first API gateway queries the first correspondence based on the identifier of the first API gateway to obtain the resource parameter format supported by the first API gateway; and based on the resource parameter format supported by the first API gateway, The fourth resource parameter data included in the second API response is escaped to obtain the third resource parameter data.

For the expression mode and escaping process of the first correspondence, refer to S305, which is not described in detail in the embodiment of the present application.

In the second optional manner, after the first API gateway determines the resource parameter format of the supported API request, it is based on the resource parameter format supported by the API gateway of each cloud platform among the multiple cloud platforms, and the first API gateway supports An escape model is established, which is used to output resource parameter data corresponding to the received API gateway identifier and resource parameter data after receiving the API gateway identifier and resource parameter data. After receiving the second API response, the first API gateway inputs the fourth resource parameter data included in the second API response and the identification of the first API gateway into the escape model, and determines the resource parameter data output by the escape model as The third resource parameter data.

In related technologies, when users use resources of multiple cloud platforms, they need to repeatedly learn the open resource formats of multiple cloud platforms that need to call API interfaces, and perform repeated coding to implement the calls of API interfaces of the multiple cloud platforms.

In the embodiment of this application, since the first API gateway is newly added, a unified entry is provided for API interface calls of multiple cloud platforms. Therefore, the user-oriented API gateway is the first API gateway, and the user only needs to support according to the first API gateway. The resource format is programmed or the call operation is triggered through the user interface of the management node, which reduces the user's repeated learning and configuration costs for the same or similar resources (that is, the aforementioned same resource), and improves the user experience.

A set of user systems or an application may be deployed hierarchically using the resources of multiple cloud platforms. In related technologies, users need to use corresponding resources on the multiple cloud platforms in a programmatic manner to implement word segmentation deployment of user systems or applications.

In the embodiment of the present application, since the first API provides users with a unified resource format, the communication method provided in the embodiment of the present application can also be used for resource orchestration across cloud platforms. The user arranges and generates a unified resource template in a blueprint. The user only needs to set in the resource template which cloud platform (ie the aforementioned target cloud platform) each resource of the user system or application is deployed on, and then run the set resource template Deploy instances on multiple cloud platforms, and set the resource template of the target cloud platform as the aforementioned client. This can effectively reduce user operations and improve resource deployment efficiency.

Optionally, in addition to the aforementioned API request format integration function, the first API gateway also supports other functions. For example, the first API gateway supports the presentation function of service information. As shown in FIG. 4, the communication method provided in the embodiment of the present application also include:

S309. The first API gateway obtains service information of the resources of the cloud platform, where the service information includes at least one of service capability information and service prices.

Among them, the service information is information related to the service provided by the resource. The service capability information is used to reflect the size of the resource's ability to provide services. The service capability information includes one or more parameter values that reflect the service capability, or the service capability information may be a service capability index value, which may be based on The aforementioned parameter values are determined, and can also be preset values. For example, for a resource used to provide GPU acceleration services, its service capability information includes one or one of the number of CPUs, the number of memory, the size of memory (for example, 4G memory), the system architecture, the information of the intranet transceiver capability, and the GPU indicator. There are multiple. Intranet sending and receiving capability information is used to reflect the information sending and receiving capability of resources in the internal network. For example, the information is the number of packets per second (PPS). Assuming that the intranet sending and receiving capability information indicates that the intranet sends and receives more than 1 million packets , Refers to the internal network sending more than 1 million packets per second; the system architecture is used to indicate the system architecture supported by the resource. The system architecture can be at least one of the IOS architecture, the Android architecture and the Kunpeng architecture, for example, The values 0, 1, and 2 respectively represent the aforementioned three architectures; the GPU indicator is used to indicate whether the corresponding resource has a GPU or the number of GPUs. There is a GPU; the service price is used to reflect the price of the service provided by the resource.

The first API gateway has the ability to identify service information of resources in each cloud platform. There may be multiple situations when the first API gateway obtains the service information. The embodiments of this application take the following three situations as examples for description:

In the first case, the first API gateway obtains the service information of the resources of the cloud platform after receiving the service information retrieval request through the user interface. Referring to Figure 2, the management node can provide a user interface to the user equipment, and the user can perform retrieval operations on the user interface through the user equipment. Correspondingly, after receiving the service information retrieval request on the user interface, the management node sends the service information retrieval request to the first API gateway, and the first API gateway obtains the service information of the resources of the cloud platform based on the service information retrieval request. Among them, the service information retrieval request includes the resource requirements of the retrieved cloud platform, including requirements on the function, resource format, and resource performance of the resource. The resources of the cloud platform from which the first API gateway obtains the service information need to meet the service information retrieval request , That is, it matches the service information retrieval request.

In an optional example, the user interface 50 provided by the management node may be as shown in FIG. The management node receives the service information retrieval request triggered by the retrieval operation, the service information retrieval request includes the keyword, and the first API gateway may obtain the service information of the resource matching the keyword based on the service information retrieval request. For example, if the keyword is: "GPU acceleration, 4-core CPU", the first API gateway obtains service information of a resource with a 4-core CPU for providing GPU acceleration services.

In another alternative example, the user interface 60 provided by the management node may be as shown in FIG. 6. The user interface 60 includes one or more prompt options 601, and the one or more prompt options 601 may include resource category prompt options. 6011, used to prompt the types of resources deployed in multiple cloud platforms. This type can be the service type provided by the resource, such as GPU acceleration, disk performance optimization, or network speed and bandwidth optimization; this type can also be the resource's own attribute type , Such as virtual machines or containers. The one or more prompt options 601 may also include prompt options 6012 reflecting parameters of the service capability, such as the number of CPU options or the number of memory options. Each prompt option 601 is provided with a pull button. When the user needs to select from the prompt information provided by a certain prompt option 601, the user clicks the pull-down button to trigger the presentation of the prompt information corresponding to the certain prompt option. After the user selects the prompt information corresponding to one or more prompt options, the search button is triggered to perform the search operation. Correspondingly, the management node receives the service information retrieval request triggered by the retrieval operation. The service information retrieval request includes the prompt information selected by the user. The first API gateway may obtain the service information retrieval request based on the service information retrieval request. Service information of the resource. For example, the service information retrieval request indicates that the resource category is GPU accelerated, the number of CPUs is 4, and the number of memory is 8.

In yet another alternative example, the management node may simultaneously present a search box and one or more prompt options on the user interface. For specific presentation methods, refer to the foregoing two optional examples.

In the second case, after receiving the first API request, the first API gateway obtains the service information of the resources of the cloud platform. The service information of the resource of the cloud platform matches the first API request. For example, the first API request includes the identifier of the resource, and the service information of the resource acquired by the first API gateway is the service information of the resource corresponding to the identifier of the resource. For example, the identifier of the resource is "GPU acceleration", and the service information of the resource acquired by the first API gateway is the service information of the resource used to provide GPU acceleration services in multiple cloud platforms.

In the third case, the first API gateway periodically obtains the capability information of the resources of multiple cloud platforms. The multiple cloud platforms may be all cloud platforms managed by the first API gateway, and each time the resources of the multiple cloud platforms are obtained After the capability information, the first API gateway stores the acquired capability information of the resources of the cloud platform in the designated storage space 4.

S310. The first API gateway presents the capability information of the resources of the cloud platform through the user interface.

Optionally, the first API gateway sends the acquired capability information of the resources of the cloud platform to the management node, and the management node presents the capability information of the resources of the cloud platform through a user interface.

It can be seen from S309 and S310 that the service information presentation function of the first API gateway can present the capability information of the resources of the cloud platform to the user, so that the user can understand the capability information of the resource.

Although the resource capabilities of multiple cloud platforms are similar, there are still some differences. In related technologies, if users need to understand the resource capabilities of different cloud platforms, they need to check whether the resources meet their own needs through query operations on each cloud platform.

In the embodiment of the present application, for the first case of S309, after receiving the service information retrieval request, the first API gateway obtains the service information of the resources of the cloud platform, and presents the obtained service information through the user interface, which can be realized through the user The interface performs the retrieval function of service information, so that users can retrieve on demand and obtain the service information they want to obtain. Users do not need to check whether resources meet their own needs on a cloud platform one by one, reducing user operation complexity and improving user experience. Optionally, S309 and S310 may be performed before the aforementioned S303. Then in S303, the user can send the first API request to the first API gateway through the user equipment based on the search result.

For the second case of S309, after receiving the first API request, the first API gateway obtains the service information of the resources of the cloud platform, and presents the obtained service information through the user interface, which can realize that when the user makes an interface call, The user provides the service information of the resource that meets the demand, so that the user can understand the service information of the resource and make better interface calls. Optionally, S309 and S310 may be executed after the aforementioned S303.

For the third case of S309, the first API gateway may obtain the latest capability information of the resources of the cloud platform in the designated storage space 4 after detecting that the user accesses the specified page for presentation of capability information through the user interface. And the latest cloud platform resource capability information is presented through the designated page. When the capability information of the resources of the latest cloud platform is presented as multiple cloud platforms managed by the first API gateway, it is convenient for the user to have an overall understanding of the capability information of the resources of the cloud platform managed by the first API gateway.

Optionally, the aforementioned management node may also support the resource quota allocation function. The management node presents a unified user interface of multiple cloud platforms. The user can perform resource allocation through the user interface. After receiving the allocation instruction, the management node performs resource quota Distribution. For example, the user needs to create virtual machine 1 on cloud platform 1 and virtual machine 2 on cloud platform 2, and the user allocates resource quotas for the two virtual machines through the user interface. For example, a 4-core CPU and 2G memory are allocated to virtual machine 1; an 8-core CPU and 4G memory are allocated to virtual machine 2.

Optionally, the aforementioned management node may also support the function of setting resource usage rights. The management node presents a unified user interface of multiple cloud platforms. The user can set the resource usage rights on the user interface. After the management node receives the permission instruction instruction , Set up resource usage permissions. For example, the aforementioned user whose user account is M1 has the right to use virtual machine 1; the user whose user account is M2 has the right to use virtual machine 2.

Optionally, the first API gateway also supports a resource migration function across cloud platforms. As shown in FIG. 7, the communication method provided by the embodiment of the present application further includes:

S311. The first API gateway converts the resource parameter format of the resource parameter data of the resource to be migrated into a resource parameter format supported by the API gateway of the target cloud platform.

When the first API gateway performs resource migration, it first determines the source cloud platform to which the resource to be migrated belongs and the destination cloud platform to which it needs to be migrated, and then obtains the resource parameter data of the resource to be migrated on the source cloud platform, and the resource parameter data The resource parameter format is converted into the resource parameter format supported by the API gateway of the target cloud platform.

Among them, the first API gateway can determine the source cloud platform and the destination cloud platform in a variety of ways. In an optional example, the first API gateway receives a resource migration request, and the resource migration request indicates a source cloud platform and a destination cloud platform; in another optional example, the source cloud platform and the destination cloud platform are preset Cloud platform.

The first API gateway may convert the resource parameter format of the resource parameter data into a resource parameter format supported by the target cloud platform in various ways. In the first optional example, the first API gateway may first convert the resource parameter format of the resource parameter data into the resource parameter format supported by the first API gateway. This conversion process is called the first conversion, and then the converted The resource parameter format of the resource parameter data is converted into the resource parameter format supported by the destination cloud platform. This conversion process is called the second conversion. Referring to S305, the first API gateway pre-establishes a first correspondence between the resource parameter format supported by the API gateway of each cloud platform in the multiple cloud platforms and the resource parameter format supported by the first API gateway. For the resource to be migrated, first Based on the first correspondence, the API gateway determines the correspondence between the resource parameter format supported by the first API gateway and the resource parameter format supported by the source cloud platform, as well as the resource parameter format supported by the first API gateway and the resource supported by the destination cloud platform. Correspondence of parameter format 2. The first API gateway completes the aforementioned first conversion based on the corresponding relationship 1, and completes the aforementioned second conversion based on the corresponding relationship 2.

In the second optional example, the first API gateway may directly convert the resource parameter format of the resource parameter data into the resource parameter format supported by the target cloud platform. With reference to the first optional example, for the resource to be migrated, the first API gateway determines the correspondence between the resource parameter format supported by the first API gateway and the resource parameter format supported by the source cloud platform based on the first correspondence1, and Correspondence between the resource parameter format supported by the first API gateway and the resource parameter format supported by the target cloud platform 2, and then determine the resource parameter format supported by the source cloud platform and the resource parameter format supported by the destination cloud platform based on the corresponding relationship 1 and the corresponding relationship 2. The corresponding relationship 3. The first API gateway completes the process of converting the resource parameter format of the resource parameter data into the resource parameter format supported by the target cloud platform based on the correspondence relationship 3.

S312. The first API gateway sends the transformed resource parameter data to the API gateway of the target cloud platform.

The first API gateway sends the converted resource parameter data to the API gateway of the target cloud platform. The API gateway of the target cloud platform creates a new resource based on the transformed resource parameter data, thereby realizing the resource parameter data from the source cloud platform to the target Migration of cloud platforms. It should be noted that the target cloud platform and the foregoing target cloud platform may be the same or different, which is not limited in the embodiment of the present application.

In the related technology, if a user needs to migrate the original resources deployed on the platform 1 to the platform 2, the resources of the platform 1 need to be deleted first, and then new resources are created on the cloud platform 2 through reprogramming.

In the embodiment of this application, if a user needs to perform resource migration across cloud platforms, he only needs to specify the source cloud platform and the destination cloud platform through a resource migration request or other means, and the first API gateway can realize the automatic resource migration across cloud platforms. , No need for users to reprogram, reduce operation complexity and improve user experience.

It should be noted that after the resources are migrated across cloud platforms, the business data generated when the resources in the source cloud platform provide services also needs to be controlled by the user to send from the source cloud platform to the destination cloud platform to realize the complete migration of resources and business data .

In order to facilitate readers’ understanding, the embodiments of this application assume the following example for description: User X needs to create a virtual machine with a 4-core CPU, 8G memory, and GPU, which is accessed by running the web client corresponding to the management node on the user device The user interface provided by the management node, the user interface may be as shown in Figure 5 or Figure 6, the user performs a retrieval operation through the user interface, and triggers a service information retrieval request "4 core CPU, 8G memory, with GPU". The first API gateway obtains a resource that meets the requirements of the service information retrieval request and obtains its service information. The service information of the resource obtained by the first API gateway is presented through the user interface of the management node. For example, the service information of the resource is presented in the form of a table (refer to the aforementioned S309 and S310 for this process). Users can determine the target cloud platform based on the service information of multiple resources. Optionally, the user interface also presents the identification of the cloud platform to which multiple resources belong (for example, the name of the cloud platform), and the user selects the target cloud platform on the user interface through the web client. Accordingly, the management node receives the selection instruction and will indicate The selection instruction of the target cloud platform is sent to the first API gateway. After that, the user equipment sends a first API request to the first API gateway through the client or the management node according to the first interface calling rule, and the calling operation indicated by the first API request is a resource establishment operation. After receiving the first API request, the first API gateway converts the first resource data in the first API request into resource parameter format to obtain the second resource parameter data, and according to the second interface calling rule, converts the second parameter data including the second parameter data. The API request is sent to the second API gateway in the target cloud platform. Assuming that the first API request indicates that the resource to be established is a virtual machine, the second API gateway establishes a virtual machine with "4-core CPU, 8G memory, and GPU" in the target cloud platform based on the second API request. The second API gateway sends a second API response to the first API gateway. After receiving the second API response, the first API gateway sends the first API response to the user equipment according to the first interface calling rule (refer to the foregoing S303 to S308 for this process).

It should be noted that the sequence of the steps of the communication method provided in the embodiments of this application can be adjusted appropriately, and the steps can also be increased or decreased accordingly according to the situation. Anyone skilled in the art within the technical scope disclosed in this application can Any method that can be easily thought of changes should be covered by the scope of protection of this application, so I will not repeat them.

An embodiment of the present application provides a communication device 70, which is applied to a first API gateway. As shown in FIG. 8, the device 70 includes:

The receiving module 701 is used to receive the first API request; the determining module 702 is used to determine the target cloud platform used to respond to the first API request among multiple cloud platforms, and the format of the first API request is supported by the first API gateway Format; sending module 703, used to send a second API request to the second API gateway, the second API request is determined based on the first API request, and the format of the second API request is a format supported by the second API gateway, the second API gateway It is the API gateway of the target cloud platform.

In summary, after the receiving module receives the first API request, the determining module determines the second API request in the format supported by the target cloud platform, and the sending module sends the second API request to the second API request of the target cloud platform. API gateway, the user only needs to use the API request in the format supported by the first API gateway to access the API unified gateway to achieve access to the target cloud platform among multiple cloud platforms, which reduces the complexity of user operations and improves user equipment and Communication flexibility of different cloud platforms.

Optionally, the first API request includes first resource parameter data, and the second API request includes second resource parameter data. The format of the first resource parameter data is the resource parameter format supported by the first API gateway. The format is a resource parameter format supported by the second API gateway, and the second resource parameter data is obtained by converting the first resource parameter data into the resource parameter format.

Optionally, as shown in FIG. 9, the device 70 further includes: an integration module 704, configured to integrate resource parameter formats corresponding to the same invocation operation of the same resource in multiple cloud platforms, to be supported by the first API gateway The resource parameter format of the same call operation of the same resource.

Optionally, the resource parameter format of the same calling operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same calling operation of the same resource in multiple cloud platforms.

Optionally, the second API request is sent by the first API gateway based on the second interface calling rule, the second interface calling rule is the interface calling rule supported by the second API gateway, and the second interface calling rule is based on the first API gateway. The first interface calling rule supported by the API gateway and the determination of the first API request; the receiving module 701 is also used to receive the second API response sent by the second API gateway; the sending module 703 is also used to follow the second API response based on the second API response An interface calling rule replies the first API response to the sender of the first API request.

Optionally, as shown in FIG. 10, the apparatus 70 further includes: a rule determination module 705, configured to determine the same calling operation for the same resource in multiple cloud platforms based on the interface calling rule corresponding to the calling operation The first interface calling rule corresponding to the same calling operation of the resource.

Optionally, the interface calling rules of the calling operation are used to indicate the interface set corresponding to the calling operation and the calling timing of the interface set; when the same calling operation of the same resource in multiple cloud platforms corresponds to the interface set and the calling timing of the interface set The first interface calling rule corresponding to the same calling operation of the same resource is to call the API interfaces in the interface set according to the calling sequence; when the same calling operation of the same resource in multiple cloud platforms corresponds to the same set of interfaces, the calling sequence Different, the first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the API interface in the interface set corresponding to the same calling operation; when the same calling operation of the same resource in multiple cloud platforms corresponds to the interface The set is different. The first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the API interface in the interface set corresponding to the same calling operation.

Optionally, the same resource is a resource whose similarity defined by the resource is greater than a similarity threshold.

Optionally, as shown in FIG. 11, the device 70 further includes: a presentation module 706, configured to provide service information of the resources of the cloud platform through a user interface, the service information including at least one of service capability information and service prices.

Optionally, as shown in FIG. 12, the apparatus 70 further includes: an obtaining module 707, configured to obtain service information of the resources of the cloud platform after receiving the service information retrieval request through the user interface; or, after receiving the first service information retrieval request; After the API request, the service information of the resources of the cloud platform is obtained.

Optionally, the target cloud platform is determined based on the selection instruction sent by the management node, the selection instruction is used to instruct the target cloud platform, and the selection instruction is received by the management node through the user interface; or, the target cloud platform is based on the selection sent by the client If the instruction is determined, the selection instruction is used to indicate the target cloud platform; or, the first API request includes the identification of the target cloud platform.

Optionally, as shown in FIG. 13, the device 70 further includes: a conversion module 708, configured to convert the resource parameter format of the resource parameter data of the resource to be migrated into a resource parameter format supported by the API gateway of the target cloud platform; a sending module 703 It is also used to send the transformed resource parameter data to the API gateway of the target cloud platform.

It should be noted that when the communication device provided in the above embodiment executes the communication method, only the division of the above functional modules is used as an example for illustration. In actual applications, the above functions can be allocated by different functional modules as needed. That is, the internal structure of the communication device is divided into different functional modules to complete all or part of the functions described above. FIG. 14 assumes that the above-mentioned communication device is the first API gateway, and FIG. 14 schematically provides a possible basic hardware architecture in an actual application scenario of the first API gateway provided by an embodiment of the present application. The first API gateway 101 includes: an API service module 1011, an authority authentication module 1012, a resource management module 1013, an API analysis module 1014, and an API database 1015.

The API service module 1011 is used to publish the API request format supported by the first API gateway to provide a unified API interface to the user equipment, which can implement the aforementioned S302 function.

The permission authentication module 1012 is used to perform permission authentication on the received first API request, and it can implement the authentication function described in S304.

The resource management module 1013 is configured to determine the target cloud platform among multiple cloud platforms after receiving the first API request, and determine the second API request based on the first API request, which can implement the aforementioned functions of S304 and S305.

Optionally, the API service module 1011 is further configured to receive the first API request, call the authority authentication module 1012 to authenticate the first API request, and transparently transmit the first API request that is successfully authenticated to the resource management module 1013.

The API analysis module 1014 is used to determine the format of the API request, which can implement the aforementioned function of S301.

The API database 1015 is used to store at least one of resource definitions of multiple cloud platforms, resource formats of multiple cloud platforms, and capability information of resources of multiple cloud platforms, which can implement the aforementioned designated storage space 1 to designated storage space 4 The function of at least one of them.

The environment outside the first API gateway 101 in FIG. 14 is only a schematic environment, and for related explanations, reference may be made to the corresponding explanations in FIGS. 1 and 2 described above.

It is worth noting that the functions of the aforementioned API service module 1011 can be realized by the receiving module 701; the authority authentication module 1012 and the API analysis module 1014 can be realized by the determining module 702; the function of the resource management module 1013 can be realized by the sending module 703. FIG. 14 only provides an example in which the above-mentioned function allocation is completed by different function modules according to needs, and does not limit the division of modules in the first API gateway.

Optionally, FIG. 15 schematically provides a possible basic hardware architecture of the computer device provided in the embodiment of the present application.

Referring to FIG. 15, the computer device 900 includes a processor 901, a memory 902, a communication interface 903, and a bus 904.

In the computer device 900, the number of processors 901 may be one or more, and FIG. 15 only illustrates one of the processors 901. Optionally, the processor 901 may be a central processing unit (CPU). If the computer device 900 has multiple processors 901, the types of the multiple processors 901 may be different or may be the same. Optionally, multiple processors 901 of the computer device 900 may also be integrated into a multi-core processor.

The memory 902 stores computer instructions and data; the memory 902 may store computer instructions and data required to implement the communication method provided in the present application. For example, the memory 902 stores instructions for implementing the steps of the communication method. The memory 902 may be any one or any combination of the following storage media: non-volatile memory (for example, read only memory (ROM), solid state drive (SSD), hard disk (HDD), optical disc), volatile memory.

The communication interface 903 may be any one or any combination of the following devices: a network interface (for example, an Ethernet interface), a wireless network card, and other devices with a network access function.

The communication interface 903 is used for data communication between the computer device 900 and other computer devices or terminals.

The bus 904 can connect the processor 901 with the memory 902 and the communication interface 903. In this way, through the bus 904, the processor 901 can access the memory 902, and can also use the communication interface 903 to interact with other computer devices or terminals.

In this application, the computer device 900 executes the computer instructions in the memory 902, so that the computer device 900 implements the communication method provided in this application, or causes the computer device 900 to deploy a communication system.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as a memory including instructions, which can be executed by a processor of a server to complete the communication methods shown in the various embodiments of the present application. . For example, the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

An embodiment of the present application provides a communication system, including: a first API gateway and multiple cloud platforms, each cloud platform includes an API gateway, and the first API gateway includes any one of the communications provided in the embodiments of the present application A device, such as a communication device 70. Optionally, the structure of the communication system may refer to the structures in FIG. 1, FIG. 2 and FIG. 14.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in the form of a computer program product in whole or in part, and the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data. The center transmits to another website, computer, server, or data center through wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium, or a semiconductor medium (for example, a solid state hard disk).

In this application, the terms "first", "second" and "third" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance. The term "at least one" means one or more, and the term "plurality" means two or more, unless specifically defined otherwise. A refers to B, which means that A is the same as B or A is a simple modification of B.

It should be noted that when the communication device or communication system provided in the above-mentioned embodiment executes the communication method, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated to different functions according to needs. Module completion, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the communication device, the communication system, and the communication method embodiments provided in the foregoing embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

The above are only optional embodiments of this application and are not intended to limit this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection of this application. Within range.

Claims

A communication method, characterized in that the method includes:

The first application program interface API gateway receives the first API request;

The first API gateway determines a target cloud platform for responding to the first API request among multiple cloud platforms, and the format of the first API request is a format supported by the first API gateway;

The first API gateway sends a second API request to the second API gateway, the second API request is determined based on the first API request, and the format of the second API request is supported by the second API gateway Format, the second API gateway is the API gateway of the target cloud platform.
The method according to claim 1, wherein the first API request includes first resource parameter data, the second API request includes second resource parameter data, and the format of the first resource parameter data is The resource parameter format supported by the first API gateway, the first resource parameter data format is the resource parameter format supported by the second API gateway, and the second resource parameter data is a combination of the first resource parameter data The resource parameter format is converted.
The method according to claim 2, wherein the method further comprises:

The first API gateway integrates resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms to obtain the same call operation of the same resource supported by the first API gateway Resource parameter format.
The method according to claim 3, wherein the resource parameter format of the same call operation of the same resource supported by the first API gateway corresponds to the same call operation of the same resource in the multiple cloud platforms The union of resource parameter formats.
The method according to any one of claims 1 to 4, wherein the second API request is sent by the first API gateway based on a second interface calling rule, and the second interface calling rule is the second The interface call rule supported by the API gateway, the second interface call rule is determined by the first API gateway based on the first interface call rule supported by the first API gateway and the first API request; the method further includes :

Receiving, by the first API gateway, a second API response sent by the second API gateway;

Based on the second API response, the first API gateway replies a first API response to the sender of the first API request according to the first interface calling rule.
The method according to claim 5, wherein the method further comprises:

For the same calling operation of the same resource in the multiple cloud platforms, the first API gateway determines the first interface corresponding to the same calling operation of the same resource based on the interface calling rule corresponding to the calling operation Call rules.
The method according to claim 6, wherein the interface invoking rule of the invoking operation is used to indicate the interface set corresponding to the invoking operation and the invoking timing of the interface set;

When the interface set corresponding to the same calling operation of the same resource in the multiple cloud platforms and the calling sequence of the interface set are the same, the first interface calling rule corresponding to the same calling operation of the same resource is according to the calling Call the API interface in the interface set in time sequence;

When the interface sets corresponding to the same calling operation of the same resource in the multiple cloud platforms are the same, and the calling sequence is different, the first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the API interface in the interface set corresponding to the same call operation;

When the interface sets corresponding to the same calling operation of the same resource in the multiple cloud platforms are different, the first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the same calling operation corresponding Centralized API interface.
The method according to claim 3, 4, 6 or 7, wherein the same resource is a resource whose similarity defined by the resource is greater than a similarity threshold.
The method according to any one of claims 1 to 8, wherein the method further comprises:

The service information of the resource of the first API gateway through the user interface cloud platform, the service information includes at least one of service capability information and service price.
The method according to claim 9, wherein the method further comprises:

After receiving the service information retrieval request through the user interface, the first API gateway obtains the service information of the resource of the cloud platform;

Alternatively, after receiving the first API request, the first API gateway obtains the service information of the resource of the cloud platform.
The method according to any one of claims 1 to 10, wherein the target cloud platform is determined based on a selection instruction sent by a management node, and the selection instruction is used to instruct the target cloud platform, and the selection instruction Is received by the management node through the user interface;

Alternatively, the target cloud platform is determined based on a selection instruction sent by the client, and the selection instruction is used to instruct the target cloud platform;

Alternatively, the first API request includes the identifier of the target cloud platform.
The method according to any one of claims 1 to 11, wherein the method further comprises:

The first API gateway converts the resource parameter format of the resource parameter data of the resource to be migrated into the resource parameter format supported by the API gateway of the target cloud platform;

The first API gateway sends the transformed resource parameter data to the API gateway of the target cloud platform.
The method according to any one of claims 1 to 12, wherein the first API request is sent by the client to the first API gateway;

Alternatively, the first API request is received by the management node on the user interface and sent to the first API gateway.
The method according to any one of claims 1 to 13, wherein the calling operation indicated by the first API request includes any one of the following:

Resource creation operations, resource deletion operations, resource modification operations, and resource query operations.
A communication device, characterized in that the device is applied to a first application program interface API gateway, and the device includes:

The receiving module is used to receive the first API request;

A determining module, configured to determine a target cloud platform used to respond to the first API request among multiple cloud platforms, and the format of the first API request is a format supported by the first API gateway;

The sending module is configured to send a second API request to the second API gateway, the second API request is determined based on the first API request, and the format of the second API request is a format supported by the second API gateway , The second API gateway is an API gateway of the target cloud platform.
The device according to claim 15, wherein the first API request includes first resource parameter data, the second API request includes second resource parameter data, and the format of the first resource parameter data is The resource parameter format supported by the first API gateway, the first resource parameter data format is the resource parameter format supported by the second API gateway, and the second resource parameter data is a combination of the first resource parameter data The resource parameter format is converted.
The device according to claim 16, wherein the device further comprises:

The integration module is used to integrate the resource parameter format corresponding to the same call operation of the same resource in the multiple cloud platforms to obtain the resource of the same call operation of the same resource supported by the first API gateway Parameter format.
The device according to claim 17, wherein the resource parameter format of the same calling operation of the same resource supported by the first API gateway corresponds to the same calling operation of the same resource in the multiple cloud platforms The union of resource parameter formats.
The apparatus according to any one of claims 15 to 18, wherein the second API request is sent by the first API gateway based on a second interface invocation rule, and the second interface invocation rule is the second An interface call rule supported by the API gateway, the second interface call rule is determined by the first API gateway based on the first interface call rule supported by the first API gateway and the first API request;

The receiving module is further configured to receive a second API response sent by the second API gateway;

The sending module is further configured to reply a first API response to the sender of the first API request according to the first interface calling rule based on the second API response.
The device according to claim 19, wherein the device further comprises:

The rule determination module is configured to determine the first interface corresponding to the same calling operation of the same resource based on the interface calling rule corresponding to the calling operation for the same calling operation of the same resource in the multiple cloud platforms Call rules.
The device according to claim 20, wherein the interface invoking rule of the invoking operation is used to indicate the interface set corresponding to the invoking operation and the invoking timing of the interface set;

When the interface set corresponding to the same calling operation of the same resource in the multiple cloud platforms and the calling sequence of the interface set are the same, the first interface calling rule corresponding to the same calling operation of the same resource is according to the calling Call the API interface in the interface set in time sequence;

When the interface sets corresponding to the same calling operation of the same resource in the multiple cloud platforms are the same, and the calling sequence is different, the first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the API interface in the interface set corresponding to the same call operation;

When the interface sets corresponding to the same calling operation of the same resource in the multiple cloud platforms are different, the first interface calling rule corresponding to the same calling operation of the same resource is to use one API request to call the same calling operation corresponding Centralized API interface.
The device according to claim 17, 18, 20 or 21, wherein the same resource is a resource whose similarity defined by the resource is greater than a similarity threshold.
The device according to any one of claims 15 to 22, wherein the device further comprises:

The presentation module is used for service information of the resources of the cloud platform through the user interface, the service information includes at least one of service capability information and service price.
The device according to claim 23, wherein the device further comprises:

Obtain modules for:

After receiving the service information retrieval request through the user interface, acquiring the service information of the resources of the cloud platform;

Or, after receiving the first API request, the service information of the resource of the cloud platform is acquired.
The device according to any one of claims 15 to 24, wherein the target cloud platform is determined based on a selection instruction sent by a management node, the selection instruction is used to instruct the target cloud platform, the selection instruction Is received by the management node through the user interface;

Alternatively, the target cloud platform is determined based on a selection instruction sent by the client, and the selection instruction is used to instruct the target cloud platform;

Alternatively, the first API request includes the identifier of the target cloud platform.
The device according to any one of claims 15 to 25, wherein the device further comprises:

The conversion module is used to convert the resource parameter format of the resource parameter data of the resource to be migrated into the resource parameter format supported by the API gateway of the target cloud platform;

The sending module is also used to send the transformed resource parameter data to the API gateway of the target cloud platform.
The device according to any one of claims 15 to 26, wherein the first API request is sent by the client to the first API gateway;

Alternatively, the first API request is received by the management node on the user interface and sent to the first API gateway.
The device according to any one of claims 15 to 27, wherein the calling operation indicated by the first API request includes any one of the following:

Resource creation operations, resource deletion operations, resource modification operations, and resource query operations.
A computer device, characterized in that it comprises:

Processor and memory;

The memory is used to store computer instructions;

The processor is configured to execute computer instructions stored in the memory, so that the computer device executes the communication method according to any one of claims 1 to 14.
A computer-readable storage medium, wherein the computer-readable storage medium includes computer instructions that instruct a computer device to execute the communication method according to any one of claims 1 to 14.
A communication system, characterized by comprising: a first API gateway and a plurality of cloud platforms, each cloud platform comprising an API gateway, and the first API gateway comprising the communication device according to any one of claims 15 to 28.