CN113691575A

CN113691575A - Communication method, device and system

Info

Publication number: CN113691575A
Application number: CN202010470931.3A
Authority: CN
Inventors: 陈曦; 李光成
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2020-05-18
Filing date: 2020-05-28
Publication date: 2021-11-23
Anticipated expiration: 2040-05-28
Also published as: WO2021232860A1; CN113691575B

Abstract

The application discloses a communication method, a communication device and a communication system, and belongs to the field of cloud computing. The method comprises the following steps: a first Application Program Interface (API) gateway receives a first API request; the first API gateway determines a target cloud platform used for responding to the first API request in the plurality of cloud platforms, wherein 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 a second API gateway, the second API request is determined based on 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. The method and the device improve the communication flexibility of the user equipment and different cloud platforms.

Description

Communication method, device and system

The present application claims priority from chinese patent application No. 202010421087.5 entitled "a hybrid cloud intelligent API gateway" filed on 18/5/2020, which is incorporated herein by reference in its entirety.

Technical Field

The present application relates to the field of cloud computing, and in particular, to a communication method, apparatus, and system.

Background

Cloud technology (cloudstechnology) is a hosting technology for enabling the computation, storage, processing, or sharing of data. A platform for implementing cloud technology is called a cloud platform.

With the gradual increase of different demands of users on data, one user may make calls of different resources on different cloud platforms through the user equipment. For example, different virtual machines are established on different cloud platforms. Thus, when accessing different cloud platforms, the user equipment needs to send out different Application Programming Interface (API) requests according to formats supported by the different cloud platforms, and the flexibility of communication between the user equipment and the different cloud platforms is low.

Disclosure of Invention

The embodiment of the application provides a communication method, a communication device and a communication system. The technical scheme is as follows:

in a first aspect, a communication method is provided, the method including:

a first Application Program Interface (API) gateway receives a first API request; the first API gateway determines a target cloud platform used for responding to the first API request in the plurality of cloud platforms, wherein 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 a second API gateway, the second API request is determined based on 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.

In the embodiment of the application, after receiving the first API request, the first API gateway determines a second API request in a format supported by the target cloud platform, and sends the second API request to the second API gateway of the target cloud platform, so that a user can access the target cloud platform in the multiple cloud platforms only by accessing the API unified gateway with the API request in the format supported by the first API gateway, the operation complexity of the user is reduced, and the communication flexibility between the user equipment and different cloud platforms is improved.

In the embodiment of the application, the first API gateway needs to determine the format of the API request supported by the first API gateway in advance, so as to facilitate the use of the subsequent user. The format of the API request is consistent with the format of the resource deployed by the first API gateway and is therefore also referred to as the resource format. The resource format mainly comprises two parts, one part is the format (schema, also called specification) of the resource parameters carried in the API request; the other part comprises interface calling rules corresponding to the API requests. The resource parameter refers to a parameter (also referred to as an object) of a resource to which data belongs. The resource parameter format is a structural definition of the object of the data. And the interface calling rule of the calling operation is used for indicating the interface set corresponding to the calling operation and the calling time sequence of the interface set. The time sequences of the interface sets called by the same API request are the same, and the time sequences of the interface sets called by different API requests are different.

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

In a first alternative implementation, the first API gateway determines a resource parameter format of the supported API request. The process comprises the following steps:

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 call operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms.

Correspondingly, the process of integrating the resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms to obtain the uniform resource parameter format of the same call operation of the same resource supported by the first API gateway includes: and acquiring a union set of resource parameter formats corresponding to the same calling operation of the same resource in the plurality of cloud platforms, and acquiring 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, the format of the first resource parameter data is a resource parameter format 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 performing resource parameter format conversion on the first resource parameter data.

In a second alternative implementation, the first API gateway determines the interface invocation rules for the supported API requests. The process comprises the following steps:

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

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

when the interface set corresponding to the same calling operation of the same resource in the plurality of cloud platforms and the calling time sequence of the interface set are the same, a first interface calling rule corresponding to the same calling operation of the same resource is to call the API interface in the interface set according to the calling time sequence; when the interface sets corresponding to the same calling operation of the same resource in the multiple cloud platforms are the same, the calling time sequence is different, and the first interface calling rule corresponding to the same calling operation of the same resource is to call the API interface in the interface set corresponding to the same calling operation by adopting an API request; 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 calls the API interface in the interface set corresponding to the same calling operation by adopting an API request.

Corresponding to a second optional implementation manner, the second API request is sent by the first API gateway based on a second interface call rule, where the second interface call rule is an interface call rule supported by the second API gateway, and 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 comprises the following steps:

the first API gateway receives a second API response sent by the second API gateway; and the first API gateway replies a first API response to the sending end of the first API request according to the first interface calling rule based on the second API response.

Optionally, the API response includes resource parameter data. The second API response sent by the second API comprises resource parameter data conforming to a resource parameter format supported by the API gateway of the target cloud platform. And the first API gateway issues the format of the API request supported by the first API gateway, so that the user learns the first resource parameter format supported by the first API gateway, and if the first API gateway directly feeds back the resource parameter data included in the second API response to the user through the first API response, the user needs to learn the resource parameter format supported by the second API gateway, thereby increasing the learning cost of the user. In the embodiment of the application, the first API gateway may further perform escape on 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, so that the user learning cost may be reduced.

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 a resource parameter format supported by the first API gateway, and the format of the third resource parameter data is a resource parameter format supported by the second API gateway, the third resource parameter data is obtained by the first API gateway converting the resource parameter format of the fourth resource parameter data.

It should be noted that, in the first optional implementation manner and the second optional implementation manner, the services provided by the resources provided by the multiple cloud platforms are the same or similar, and the first API gateway needs to determine the same resource, that is, the resource with the same resource type, in the multiple cloud platforms in advance, so as to perform the integration of the resource formats 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 resource is a resource whose similarity of the identifiers of the resource is greater than the second similarity threshold.

Optionally, the first API gateway supports other functions besides the aforementioned format integration function for making the API request, for example, the first API gateway supports a presentation function of the service information, and then the method further includes: the first API gateway passes service information of resources of the user interface cloud platform, and the service information comprises at least one of service capability information and service price.

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

Alternatively, when the capability information of the presented resource includes a plurality of sets of capability information in one-to-one correspondence with a plurality of resources, each set of capability information may be presented in a list manner.

In one implementation manner, after receiving a service information retrieval request, the first API gateway obtains service information of resources of the cloud platform, and presents the obtained service information through the user interface, so that a function of retrieving the service information through the user interface can be realized, thereby facilitating a user to retrieve the service information as required and obtaining the service information which the user wants to obtain. The user does not need to inquire whether the resources meet the self requirements one by one through the cloud platform, the operation complexity of the user is reduced, and the user experience is improved.

In another implementation manner, after receiving the first API request, the first API gateway obtains the service information of the resource of the cloud platform, and presents the obtained service information through the user interface, so that the service information of the resource meeting the requirement can be provided for the user when the user calls the interface, and the user can know the service information of the resource conveniently, thereby better calling the interface.

In still another implementation manner, the first API gateway may obtain, after detecting that a user accesses a specified page for capability information presentation through the user interface, capability information of a resource of the latest cloud platform in the specified storage space, and present the capability information of the resource of the latest cloud platform through the specified page. When the presented cloud platform is a plurality of cloud platforms managed by the first API gateway, the user can conveniently and integrally know 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 be rated capability information, which is fixed to reflect an upper limit of the capability of the resource. When the capability information is real-time capability information, the first API gateway can realize timely and accurate understanding of the current capability information by the user through presenting the real-time capability information of the resource, and improve user experience.

Optionally, the target cloud platform is determined based on a selection instruction sent by the management node, the selection instruction is used for indicating the target cloud platform, and the selection instruction is received by the management node through a user interface; or the target cloud platform is determined based on a selection instruction sent by a client, wherein the selection instruction is used for indicating the target cloud platform; alternatively, the first API request includes an identification of the target cloud platform.

Optionally, the first API gateway also supports resource migration functionality across cloud platforms. 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 a resource parameter format supported by the API gateway of the target cloud platform; and the first API gateway sends the converted resource parameter data to the API gateway of the target cloud platform.

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

Optionally, the call operation indicated by the first API request includes any one of: establishing operation of resources, deleting operation of resources, modifying operation of resources and inquiring operation of resources.

In a second aspect, a communication apparatus is provided, which is applied to a first application program interface, API, gateway, and may include at least one module, which may be configured to implement the communication method provided by the first aspect or various possible implementations of the first aspect.

In a third aspect, the present application provides a communication system comprising: a first API gateway and a plurality of cloud platforms, each cloud platform comprising an API gateway, the first API gateway comprising the communication device of any of the second aspects.

In a third aspect, the present application provides a computer device comprising a processor and a memory. The memory stores computer instructions; the processor executes the computer instructions stored by the memory to cause the computer device to perform the methods provided by the first aspect or the various possible implementations of the first aspect, to cause the computer device to deploy the communication apparatus provided by the second aspect or the various possible implementations of the second aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer instructions that instruct a computer device to execute the method provided by the above first aspect or various possible implementations of the first aspect, or instruct the computer device to deploy the communication apparatus provided by the above second aspect or various possible implementations of the second aspect.

In a fifth aspect, the present application provides a computer program product comprising computer instructions stored in a computer readable storage medium. A processor of a computer device may read the computer instructions from a computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided by the above first aspect or various possible implementations of the first aspect, to cause the computer device to deploy the communication apparatus provided by the above second aspect or various possible implementations of the second aspect.

A sixth aspect provides a chip, which may comprise programmable logic circuits and/or program instructions, for implementing the communication method according to any of the first aspects when the chip is operated.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

Because the first API gateway is additionally arranged and a uniform entrance is provided for calling the API interfaces of the multiple cloud platforms, the first API gateway faces the user, the user only needs to program according to a resource format supported by the first API gateway or trigger calling operation through the user interface of the management node, repeated learning and configuration cost of the user on similar resources (namely the same resource) is reduced, and user experience is improved.

Moreover, the presenting function of the service information 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 know the capability information of the resources conveniently.

In the embodiment of the application, because the first API provides a uniform resource format for the user, the communication method provided by the embodiment of the application can also be used for resource arrangement across cloud platforms. The user arranges and generates a uniform resource template in a blueprint, the user only needs to set which cloud platform the resources of the user system or the application are deployed on (namely, the target cloud platform) in the resource template, the user can deploy instances on a plurality of cloud platforms by operating the set resource template, and the set resource template of the target cloud platform is the client. Therefore, the operation of the user can be effectively reduced, and the resource deployment efficiency is improved.

In the embodiment of the application, if a user needs to perform resource migration across cloud platforms, only a source cloud platform and a target cloud platform need to be designated through a resource migration request or other modes, the first API gateway can achieve automatic migration of the resources across the cloud platforms, the user does not need to reprogram again, operation complexity is reduced, and user experience is improved.

Drawings

Fig. 1 is a schematic application scenario diagram of a communication system related to a communication method according to an embodiment of the present application;

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

fig. 3 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 4 is a schematic flow chart of another communication method provided in the embodiments 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 embodiments of the present application;

fig. 7 is a flowchart illustrating another communication method provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device according to an exemplary embodiment of the present application;

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

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

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

fig. 12 is a schematic structural diagram of a communication device according to another exemplary embodiment of the present application;

fig. 13 is a schematic structural diagram of another communication device according to another exemplary embodiment of the present application;

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

fig. 15 schematically provides one possible basic hardware architecture of a computer device provided by the embodiments of the present application.

Detailed Description

In order to make the principle and technical solution of the present application clearer, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

For the convenience of the reader, the following explains the terms referred to in the embodiments of the present application.

A cloud platform, also called a cloud system, a cloud environment, or a cloud, is a software system for cloud technology (also called cloud computing) services provided by a cloud provider.

The public cloud is a cloud platform provided by a public cloud provider of a third party for vast individuals or enterprises. In a public cloud, hardware, software, and other structures are owned and managed by a third party's public cloud provider.

Private cloud is a dedicated cloud platform provided for an enterprise or organization. The private cloud may be operated internally by the corresponding enterprise or organization. Private clouds are mainly enterprise user oriented, also known as enterprise clouds.

The mixed cloud refers to a cloud platform formed by different cloud platforms. The hybrid cloud includes at least two cloud platforms, also referred to as multi-cloud platforms or clouds. Optionally, the hybrid cloud merges a public cloud and a private cloud. Some enterprise users prefer to have data stored in a private cloud for security reasons, but also desire to have access to the computing resources of a public cloud. In this case, a hybrid cloud including a public cloud and a private cloud is increasingly adopted. The public cloud and the private cloud are mixed and matched by the mixed cloud so as to obtain a good use effect.

A Virtual Machine (VM) refers to a complete computer system with complete hardware system functions, which is simulated by software and runs in an isolated environment. The work that can be done in a physical computer (a physical machine for short) can be implemented in a virtual machine. When creating a virtual machine in a computer, it is necessary to use a part of the hard disk and the memory capacity of the physical computer as the hard disk and the memory capacity of the virtual machine. Optionally, each virtual machine has a separate Complementary Metal Oxide Semiconductor (CMOS), hard disk, and operating system, and the virtual machine can be operated as if a physical computer were used.

Containers (containers), also known as container images, are lightweight independently executable software packages of software built using container technology. The container technology refers to a virtualization technology in a computer operating system, and the technology enables processes to run in relatively independent and isolated environments (including independent file systems, namespaces, resource views and/or the like), so that the deployment process of software can be simplified, the portability and the safety of the software can be enhanced, and the utilization rate of system resources can be improved. The container technology is widely applied to service scenes in the field of cloud computing.

The application program interface, also called program interface, is an "interface between a program and an operating system" provided by an operating system of a cloud platform to a user, such as a programmer. The interface is used by the user at the time of programming. Through the application program interface, a user 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 (system calls), each of which is a program that can perform a specific function.

API Gateway (API) is a Gateway that provides API hosting services, and can perform unified management such as authentication, metering, distribution, and/or flow control on APIs.

A service, comprising: 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 services provided by the cloud platform.

Resources, hardware or software resources for providing services. For example, a resource corresponds to a computing service, a storage service, or a network service, and includes a computing resource, a storage resource, or a network resource. Optionally, the computing resources include Central Processing Unit (CPU) resources, memory resources, hard disk resources, and/or the like.

Fig. 1 is a schematic application scenario diagram of a communication system related to a communication method according to an embodiment of the present application. As shown in fig. 1, the communication system includes: a first API gateway 101, a plurality of cloud platforms 102, and one or more user devices 103. Each cloud platform 102 includes one API gateway 1021, each cloud platform 102 deploys one or more resources for providing services for the user equipment 103, and the plurality of cloud platforms 102 correspond to the plurality of API gateways 1021 one to one. The first API gateway 101 establishes a communication connection with API gateways 1021 of the plurality of 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 for managing information communicated between the user device 103 and the API gateways 1021 of the plurality of cloud platforms 102. The user device 103 may enable communication with the API gateway 1021 of the plurality of 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. Alternatively, the user device 103 may be installed with a client through which the user realizes communication with the first API gateway 101. The client is typically programmed by the user.

Fig. 2 is a schematic application scenario diagram of another communication system according to an embodiment of the present application. On the basis of fig. 1, the communication system further includes: the management node 104 and the management node 101 may be a single node. Which may be one server or a server cluster consisting of multiple servers. Or may be one or more defined minimum processing units such as virtual machines or containers. The management node 104 establishes communication connections with the first API gateway 101 and the User equipment 103, respectively, and the management node 104 may provide a User Interface (UI) for the User equipment 103, so that the User equipment 103 communicates with the first API gateway 101. 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 a user interface provided by the management node 104 by operating the web client; in another alternative, a browser is installed in the user equipment 103, and the user equipment 103 can access the user interface of the web page version provided by the management node 104 by running the browser.

Fig. 1 and fig. 2 only use two cloud platforms 102 and one user equipment 103 as examples for description, and the number of cloud platforms and the number of user equipments in the communication system are not limited.

Optionally, the first API gateway is an application in the form of a microservice, and each of the components included in the first API gateway may be deployed in a virtual machine or a container accessible by the network.

In a conventional communication system including a hybrid cloud, when a user equipment accesses different cloud platforms, different API requests conforming to formats supported by the different cloud platforms need to be sent, so that the flexibility of communication between the user equipment and the different cloud platforms is low. In addition, the user needs to be familiar with the formats of the API requests supported by different cloud platforms, the learning cost is high, and the user experience is poor.

In the communication system provided by the embodiment of the application, because the first API gateway is additionally arranged, the information communicated between the user equipment 103 and the API gateways 1021 of the plurality of cloud platforms 102 is uniformly managed, and a user does not need to send different API requests to different cloud platforms through the user equipment, so that the operation complexity of the user is reduced, and the communication flexibility between the user equipment and different cloud platforms is improved. The user can access each cloud platform managed by the first API gateway only by learning the format of the API request supported by the first API gateway. Therefore, the learning cost of the user is reduced, and the user experience is improved.

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

Fig. 3 is a flowchart of a communication method provided in an embodiment of the present application, where the communication method may be applied to the communication system shown in fig. 1 or fig. 2. As shown in fig. 3, the method includes:

s301, the first API gateway determines the format of the supported API request.

In the embodiment of the application, the first API gateway needs to determine the format of the API request supported by the first API gateway in advance, so as to facilitate the use of the subsequent user. The API request is a call request sent by the user equipment when calling the API interface. The format of the API request is consistent with the format of the resource deployed by the first API gateway and is therefore also referred to as the resource format. The resource format mainly comprises two parts, wherein one part is the format (schema, also called specification) of the resource parameters carried in the API request, and is called the resource parameter format or the API format for short; the other part comprises interface calling rules corresponding to the API requests. The resource parameter refers to a parameter (also referred to as an object) of a resource to which data belongs. The resource parameter format is a structural definition of the object of the data, i.e., a definition of a resource parameter. For example, the format of a resource parameter corresponding to a certain call operation of a certain resource is: the resource parameters are respectively name and telephone number, or the resource parameters are computing resource specification parameters such as the number of CPUs and/or the number of Graphics Processing Units (GPUs). The interface calling rule of the calling operation is used for indicating an interface set (also called an API interface set) corresponding to the calling operation and the calling time sequence of the interface set. The time sequences of the interface sets called by the same API request are the same, and the time sequences of the interface sets called by different API requests are different. For example, an interface call rule corresponding to a certain call operation of a certain resource is: the interface set comprises an API interface 1 and an API interface 2, and the time sequence of the API interface 1 and the API interface 2 is that the API interface 1 is prior to the API interface 2. That is, the interface calling rule is: and calling the API interface 1 and the API interface 2 twice according to the time sequence. An interface set includes at least one API interface identifier, which identifies an API interface. Optionally, the Identifier of the API interface is an interface routing address of the API interface, such as a Uniform Resource Identifier (URI).

As shown in fig. 1 and 2, each cloud platform is deployed with one or more resources, and the first API gateway supports different call operations for different resources in the cloud platform. As such, the user equipment may perform different invocation operations for each resource.

The calling operation supported by the first API gateway comprises any one of the following operations: a resource creation operation (also called a creation operation or an addition operation), a resource deletion operation, a resource modification operation, and a resource query operation. The establishing operation of the resources is used for establishing the resources, such as the cloud disk, the network, the virtual machine or the container; the deletion operation of the resource is used for deleting the resource, such as deleting a cloud disk, a network, a virtual machine or a container; the modification operation of the resource is used for modifying the resource, such as modifying the rule, the mirror image version or the network bandwidth of the computing resource; the query operation of the resource is used for querying the resource, such as querying the running state or parameter specification of the resource.

The format of the API request supported by the first API gateway includes a format of the API request corresponding to multiple calling operations of multiple resources supported by the first API gateway. The resource parameter formats supported by the first API gateway comprise resource parameter formats corresponding to a plurality of calling operations of a plurality of resources supported by the first API gateway. The interface calling rules supported by the first API gateway comprise interface calling rules corresponding to various calling operations of various resources supported by the first API gateway.

Optionally, the API request carries an identifier of a corresponding call operation, where the identifier of the call operation is used to identify the call operation. Illustratively, the identity of the calling operation may be represented by an action (verb) in the API request. For the convenience of the reader, the identity of the subsequent call operation is represented by the name of the call operation.

For each calling operation of each resource, the first API gateway needs to determine a uniform API request format, which includes a uniform resource parameter format, and a uniform interface calling rule, so as to facilitate the use of the subsequent user.

In a first aspect, a first API gateway determines a resource parameter format of a supported API request. The process comprises the following steps:

step A1, the first API gateway obtains resource parameter formats corresponding to different calling operations of each resource in the plurality of cloud platforms.

In a first optional implementation manner, the first API gateway may determine, based on resource definitions of multiple resources in multiple cloud platforms, resource parameter formats corresponding to different call operations of the resources in the multiple cloud platforms. The resource definition is used to describe the corresponding resource, which includes the resource parameters involved by the resource. Resource definitions are typically stored in textual form. The first API gateway may obtain resource definitions of a plurality of resources in the plurality of cloud platforms, and obtain resource parameter formats corresponding to different call operations of the respective resources in the plurality of cloud platforms by recognizing the resource definitions. The resource definitions of the multiple cloud platforms can be pulled by the first API gateway on the multiple cloud platforms, or the resource definitions of the multiple cloud platforms can be extracted by the first API gateway on the designated storage space 1 in which the resource definitions of the multiple cloud platforms are stored. The resource definitions of the multiple cloud platforms may be predetermined by a manager of the communication system and input to the designated storage space 1, or the resource definitions of the multiple cloud platforms may be pulled and maintained in the multiple cloud platforms by the designated storage space 1. The designated storage space 1 may be a database.

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

In a second optional implementation manner, the resource parameter formats corresponding to the different calling operations of the resources in the multiple cloud platforms may be predetermined by a manager of the communication system, and input to the specified storage space 2, and the first API gateway may extract the resource parameter formats corresponding to the different calling operations of the resources in the multiple cloud platforms in the specified storage space 2. 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 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.

For each calling operation of each resource, the first API gateway needs to determine a uniform resource parameter format, so as to facilitate the use of subsequent users. Optionally, the first API gateway integrates resource parameter formats corresponding to the same calling operation of the same resource in the multiple cloud platforms, so as 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 call operation of the same resource supported by the first API gateway is a union of resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms. The first API gateway may obtain a union of the resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms, so as to obtain the resource parameter format of the same call operation of the same resource supported by the first API gateway.

For example, assuming that the plurality of cloud platforms are respectively cloud platforms 1 to n, n is greater than or equal to 2, and the same calling operation of the same resource is a calling operation 1 of the resource 1, the first API gateway obtains a union of resource parameter formats corresponding to the calling operations 1 of the resources 1 of the cloud platforms 1 to n, and obtains the resource parameter format of the calling operation 1 of the resource 1 supported by the first API gateway.

For example, assume that n is 2, resource 1 is a virtual machine for providing disk performance optimization, and call operation 1 is a query operation. The resource parameter format corresponding to the calling operation 1 of the resource 1 of the cloud platform 1 is as follows: the resource parameters are name and telephone number respectively; the resource parameter format corresponding to the calling operation 1 of the resource 1 of the cloud platform 2 is that the resource parameters are a name, a phone number and a collection identifier (the collection identifier is used for indicating whether to collect the corresponding phone number). The first API gateway obtains a union of the resource parameter format corresponding to the calling operation 1 of the resource 1 of the cloud platform 1 and the resource parameter format corresponding to the calling operation 1 of the resource 1 of the cloud platform 2, and obtains the resource parameter format corresponding to the calling operation 1 of the resource 1 supported by the first API gateway, for example, the finally obtained resource parameter format is: the resource parameters are name, telephone number and collection identification respectively.

The resource parameter format is obtained by adopting a way of obtaining a union set, so that the finally obtained resource parameter format is ensured to be a uniform format, and the requirements of each cloud platform on the resource parameter format can be met.

In a second aspect, a first API gateway determines interface invocation rules for supported API requests.

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

when the interface sets corresponding to the first calling operations of the plurality of cloud platforms and the calling time sequences of the interface sets are the same, calling rules of the first interfaces corresponding to the first calling operations are to call API interfaces in the interface sets according to the calling time sequences; when the interface sets corresponding to the first calling operations of the multiple cloud platforms are the same, the calling time sequences are different, and the first interface calling rule corresponding to the first calling operation is to call the API interfaces in the interface sets corresponding to the same calling operation by adopting one-time API request, wherein the one-time API request can carry the identifier (such as uri) of the API interfaces in the interface sets or can not carry the identifier of the API interfaces in the interface sets and only carry indication information indicating all the API interfaces in the calling interface sets because the interface sets corresponding to the first calling operation are the same; when the interface sets corresponding to the first calling operations of the plurality of cloud platforms are different, the first interface calling rule corresponding to the first calling operation is to call the API interfaces in the interface set corresponding to the same calling operation by adopting an API request, wherein because the interface sets corresponding to the first calling operation are different, the API requests cannot uniformly carry the identifiers of the API interfaces in different interface sets, so that the API request can only carry indication information indicating all the API interfaces in the calling interface set without carrying the identifiers of the API interfaces in the interface set, thereby ensuring that the calling of all the API interfaces in the interface set can be realized aiming at different cloud platforms.

For example, the cloud platforms are respectively cloud platforms 1 to n, n is greater than or equal to 2, the same calling operation of the same resource is a calling operation 2 of the resource 2, and the first API gateway determines, based on an interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platforms 1 to n, a first interface calling rule of the calling operation 2 of the resource 2 supported by the first API gateway.

Assuming that n is 2, resource 2 is a virtual machine for providing GPU acceleration services, and call operation 2 is a setup operation. If the interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platform 1 is to call the API interface 1 and the API interface 2 in sequence, that is, the interface set includes: the calling time sequence of the API interface 1 and the API interface 2 is that the API interface 1 is first and the API interface 2 is second; 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 sequence. The interface call rule corresponding to the call operation 2 of the resource 2 supported by the first API gateway is: and calling the API interface 1 and the API interface 2 in sequence.

If the interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platform 1 is to call the API interface 2 and the API interface 1 in sequence, that is, the interface set includes: the calling time sequence of the API interface 1 and the API interface 2 is that the API interface 2 is first and the API interface 1 is second; 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 sequence. The interface call rule corresponding to the call operation 2 of the resource 2 supported by the first API gateway is: and calling the API interface 1 and the API interface 2 by adopting one API request.

The interface calling rule corresponding to the calling operation 2 of the resource 2 of the cloud platform 1 is to call the API interface 1, the API interface 2, and the interface 3 in sequence, that is, the interface set includes: the calling time sequence of the API interface 1 and the API interface 2 is that the API interface 1 is in the first, the API interface 2 is in the middle, and the API interface 3 is in the last; 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 sequence. The interface call rule corresponding to the call operation 2 of the resource 2 supported by the first API gateway is: and calling the API interface in the interface set corresponding to the calling operation 2 by adopting an API request.

Because the corresponding interface calling rules are different for different calling operations of different resources of different cloud platforms, if the unified first interface calling rule is changed greatly compared with the interface calling rules of each cloud platform, more storage and calculation overheads are easily generated when the subsequent first interface calling rule is actually used. Therefore, by adopting the first interface calling rule, when the interface set corresponding to the first calling operation of the plurality of cloud platforms and the calling time sequence of the interface set are the same, the first interface calling rule corresponding to the first calling operation is an API interface in the interface set according to the calling time sequence, that is, the first interface calling rule corresponding to the first calling operation is not changed relative to the interface calling rule corresponding to the first calling operation of the plurality of cloud platforms, so that the change of the first interface calling rule relative to the interface calling rule of each cloud platform can be reduced, and the storage and calculation overhead when the first interface calling rule is actually used can be further reduced.

It should be noted that the first interface call rule corresponding to the first call operation may also have other setting manners. For example, for the same resource, the first interface calling rules are all API interfaces in an interface set corresponding to one-time calling operation called by one-time API request. In this way, for the same resource, no matter which kind of calling operation, the API interface in the interface set is called by adopting one API request for one calling operation. Therefore, the interface calling rules of the same resource can be unified, and the learning cost of the user is reduced.

For another example, for different resources in the same cloud platform, the first interface call rules are all API interfaces in an interface set corresponding to one call operation called by one API request. Therefore, for the same cloud platform, no matter which resource and which calling operation are used, the API request is adopted once for calling operation once to call the API interface in the interface set. Therefore, interface calling rules of different resources of the same cloud platform can be unified, and the learning cost of a user is reduced.

For another example, for different resources in multiple cloud platforms, the first interface call rule is an API interface in an interface set corresponding to a call operation that is called by using an API request once. In this way, regardless of which resource and which calling operation, the API interface in the interface set is called by one API request for one calling operation. Therefore, interface calling rules of different resources of different cloud platforms can be unified, and the learning cost of a user is reduced.

It should be noted that, in the first aspect and the second aspect, the services provided by the resources deployed by the multiple cloud platforms are the same or similar, and the first API gateway needs to determine the same resource, that is, the resource with the same resource type, in the multiple cloud platforms in advance, and further perform the integration of the resource formats of the same resource. Optionally, the resource types are divided according to services provided by the resources, for example, the resource types are divided into GPU acceleration, disk performance optimization, network speed bandwidth optimization, and the like, and the following optional implementation manners are available for the first API gateway to determine the resources with the same resource type in the multiple cloud platforms:

in a first alternative implementation, the same resource is a resource whose similarity defined by the resource is greater than a similarity threshold. For example, the similarity threshold value ranges from 80% to 90%. The first API gateway may determine, as the same resource, a resource whose similarity defined by the resources in the plurality of cloud platforms is greater than a similarity threshold.

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

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

In the two aspects, after the first API gateway determines the format (i.e., resource format) of the API request supported by itself, the determined resource format may be stored in the designated storage space 3. The designated memory space 3 may be a database.

In the embodiments of the present application, the resource format supported by the first API gateway may be predetermined by an administrator of the communication system and input to the specified storage space 3, and the first API gateway may extract the required resource format in the specified storage space 3.

Optionally, the API interface corresponding to the resource format stored in the specified storage space 3 needs to be registered in the specified storage space 3, the registered API interface is an interface that can be called by the first API gateway, and the unregistered API interface cannot be called by the first API gateway because the resource formats of the cloud platforms to which the API interface corresponds are not unified. The resource format stored in the designated storage space 3 may be manually adjusted by an administrator, for example, added, modified, or deleted.

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

S302, the first API gateway issues the format of the API request supported by the first API gateway.

In an optional manner, the first API gateway may push a format of an API request supported by the first API gateway to a client of the user equipment, so as to implement issuing of the format of the API request; in another alternative, the first API gateway may present, via a user interface, the format of API requests supported by the first API gateway. The format of the API request is presented, for example, through the user interface of the aforementioned management node. The first API gateway realizes the pre-agreement of the first API gateway and the user equipment on the format of the API request by issuing the format of the API request supported by the first API gateway.

Optionally, there are various ways to express the format of the API request supported by the first API gateway. In an alternative, it may be represented by means of a software model; in another alternative, it may be represented by way of a software template; in yet another alternative, it may also be represented by way of a table or a graph. The embodiment of the present application does not limit the manner of representing the format of the API request. As an example, the format of the aforementioned API request may 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 device may send the first API request to the first API gateway in a variety of ways. For example, in the first mode, the user equipment installs a client, and the first API request is sent to the first API gateway by the client, that is, the user equipment sends the first API request through the client; in a second way, the user equipment sends a first API request to the management node through a user interface provided by the management node, and the first API request is received by the management node at 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 from the plurality of cloud platforms.

Corresponding to the foregoing S303, there are various ways in which the first API gateway receives the first API request. Corresponding to the first mode of S303, the first API gateway receives a first API request sent by the user equipment through the client; corresponding to the second mode of S303, the first API gateway receives the first API request sent by the management node.

There are various ways in which the first API gateway determines a target cloud platform among the plurality of cloud platforms for responding to the first API request. The embodiments of the present application are described by taking several alternative ways as examples:

in a first alternative, the target cloud platform is determined based on a selection instruction sent by the management node, where the selection instruction is used to indicate the target cloud platform, and the selection instruction is received by the management node through the 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 identifiers of the multiple cloud platforms to the user equipment through the user interface, if a user wants to operate resources in a certain cloud platform, the user equipment can perform selection operation on the user interface, so that the management node is triggered to generate a corresponding selection instruction, the selection instruction carries the identifier of a target cloud platform selected by the user, the management node sends the selection instruction 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. The identifier of the cloud platform may be a name of the cloud platform, such as "AA cloud" or "BB cloud", or may be an identifier of an API gateway in the cloud platform, such as an address of the API gateway.

Optionally, the management node may present the identifiers of the plurality of cloud platforms after the first API gateway receives the first API request; the identifiers of the plurality of cloud platforms may also be presented after receiving an access instruction sent by the user device.

In a second alternative, the target cloud platform is determined based on a selection instruction sent by the client, where 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 a resource in a certain cloud platform, a corresponding selection instruction may be generated by a client operating in user equipment, where the selection instruction carries an identifier of a target cloud platform selected by the user, the client sends the selection instruction to a first API gateway, and the first API gateway extracts the identifier of the target cloud platform to determine the target cloud platform after receiving the selection instruction.

Optionally, the client may send the selection instruction after the first API gateway receives the first API request, or may send the selection instruction before the first API gateway receives the first API request, which is not limited in this embodiment of the application.

In a third alternative, the first API request includes an 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 should be noted that, after receiving the first API request, the first API gateway may authenticate the first API request, and after the authentication is successful, determine the target cloud platform. And if the authentication fails, sending an API response indicating the authentication failure to the user equipment, or stopping the action. For example, referring to S302, the first API gateway may detect whether an API interface that needs to be called by the first API request is a registered interface, and determine that the authentication fails if the API interface that needs to be called by the first API request is not a registered interface; and if the API interface required to be called by the first API request is the registered interface, determining that the authentication is successful. Or, the first API gateway may detect whether the user account carried in the first API request has an authority to access the first API gateway (or is a legal account), and if the user account carried in the first API request does not have the authority to access the first API gateway (or is not a legal account), determine that the authentication fails; and if the user account carried by the first API request has the authority (or is a legal account) of accessing the first API gateway, determining that the authentication is successful.

The first API gateway can ensure the safety of the communication system and reduce unnecessary operation by requesting authentication for the API.

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, 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.

Referring to S301 and S302, the API request includes resource parameter data. Because the first API gateway issues the API request format supported by the first API gateway, the first API request sent by the user through the user equipment is sent according to the resource parameter format supported by the first API gateway, and when accessing the target cloud platform, the resource parameter data conforms to 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 a resource parameter format supported by the first API gateway, and the format of the first resource parameter data is a resource parameter format supported by the second API gateway, the second resource parameter data is obtained by the first API gateway performing resource parameter format conversion on the first resource parameter data.

The first API gateway may perform resource parameter format conversion on the first resource parameter data in multiple ways. The embodiments of the present application are described by taking the following two alternatives as examples:

in a first optional manner, referring to the first aspect in S301, after determining the resource parameter format of the supported API request, the first API gateway establishes a first corresponding relationship 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. After receiving the first API request, the first API gateway queries the first corresponding relation based on the identifier of the second API gateway to obtain a resource parameter format supported by the second API gateway; and the first resource parameter data included in the first API request is transferred to obtain second resource parameter data based on the resource parameter format supported by the second API gateway.

The first correspondence may be expressed in various ways. For example, the first corresponding relationship may include a plurality of sub-corresponding relationships in one-to-one correspondence with a plurality of call operations, where each sub-corresponding relationship is used to record a corresponding relationship between an identifier of a resource, a resource parameter format supported by an API gateway of the cloud platform, and a resource parameter format supported by the first API gateway under the corresponding call operation.

For another example, the first corresponding relationship may include a plurality of sub-corresponding relationships in one-to-one correspondence with identifiers of a plurality of resources, where each sub-corresponding relationship is used to record a corresponding relationship between an identifier of a calling operation, a resource parameter format supported by an API gateway of the cloud platform, and a resource parameter format supported by the first API gateway under the identifier of the corresponding resource. For example, assuming that the first corresponding relationship includes a plurality of sub-corresponding relationships corresponding to the identifiers of the plurality of resources one to one, the sub-corresponding relationship corresponding to the identifier of a certain resource may be as shown in table 1. The table 1 records a corresponding relationship between an identifier of a calling operation, a resource parameter format supported by an API gateway of the cloud platform, and a resource parameter format supported by the first API gateway, where the identifier of the calling operation is represented by a name of the calling operation, and the resource parameter format supported by the API gateway of the cloud platform may be represented by the identifier of the API gateway and the identifier of the resource parameter format. As can be seen from table 1, two cloud platforms in the plurality of cloud platforms deploy 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 set up 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 set up 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 delete operation, the resource parameter format Y1 of API gateway 1 corresponds to resource parameter format M2 of the first AP1 gateway 0; for the set up 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, the corresponding relationship refers to table 1, and details thereof are not described in this embodiment of the present application.

TABLE 1

For another example, the first corresponding relationship may include an identifier of a call operation, an identifier of a resource, and a corresponding relationship between a resource parameter format supported by an API gateway of the cloud platform and a resource parameter format supported by the first API gateway.

In a second optional manner, referring to the first aspect in S301, after determining the resource parameter format of the supported API request, the first API gateway establishes an escape model based on the resource parameter format supported by the API gateway of each of the multiple cloud platforms and the resource parameter format supported by the first API gateway, where the escape model is configured to, after receiving the identifier of the API gateway and the resource parameter data, output the resource parameter data corresponding to the received identifier of the API gateway. After receiving the first API request, the first API gateway inputs the first resource parameter data included in the first API request and the identifier of the second API gateway (or the identifier of the target cloud platform) into the escape model, and determines the resource parameter data output by the escape model as the second resource parameter data.

Referring to step a1, if the resource parameter format of the same call operation of the same resource supported by the first API gateway is a union of the resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms. As such, the first resource parameter format includes the second resource parameter format, that is, the second resource parameter format belongs to the first resource parameter format, and the second resource parameter data may include data that is not needed by the second API gateway, that is, invalid data, where the invalid data is data that does not correspond to the second resource parameter format. In an alternative manner, the first API gateway may remove invalid data in the second parameter data to obtain updated second parameter data, and generate a second API request including the updated second parameter data. For example, the first resource parameter format is: the resource parameters are name, phone number and age, respectively. The second resource parameter format is: the resource parameters are name and phone number, respectively. And if the data corresponding to the age does not correspond to the format of the second resource parameter, 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, where the second API request includes second parameter data, and after the second API gateway receives the second API request, the second API gateway removes invalid data in the second parameter data to obtain updated second parameter data.

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

The second API request is sent by the first API gateway based on a second interface calling rule, the second interface calling rule is an interface calling rule supported by the second API gateway, and the second interface calling rule is determined by the first API gateway based on a first interface calling rule supported by the first API gateway and the first API request. The first API gateway sends the second API request to the second API gateway according to the second interface calling rule, and the sent second API request can be ensured to follow the interface calling rule supported by the second API gateway, so that the effective calling of the API interface is ensured.

In this embodiment, the first API gateway may determine the second interface invocation rule in a variety of ways. For example, please refer to the second aspect of S301, after determining the interface call rule of the supported API request, the first API gateway establishes a second corresponding relationship between the interface call rule supported by the API gateway of each cloud platform of the plurality of cloud platforms and the interface call rule supported by the first API gateway. And after receiving the first API request, the first API gateway queries the second corresponding relation based on the identifier of the second API gateway to obtain a second interface calling rule corresponding to the second API gateway.

The second correspondence may be expressed in various ways. For example, the second corresponding relationship may include a plurality of sub-corresponding relationships in one-to-one correspondence with a plurality of calling operations, where each sub-corresponding relationship is used to record a corresponding relationship between an identifier of a resource, an interface calling rule supported by an API gateway of the cloud platform, and an interface calling rule supported by the first API gateway under the corresponding calling operation.

For another example, the second mapping relationship may include a plurality of sub-mapping relationships in one-to-one correspondence with identifiers of a plurality of resources, where each sub-mapping relationship is used to record a mapping relationship between an identifier of a calling operation, an interface calling rule supported by an API gateway of the cloud platform, and an interface calling rule supported by the first API gateway under the identifier of the corresponding resource. For example, assuming that the second correspondence includes a plurality of sub-correspondences corresponding to the identifiers of the plurality of resources one to one, the sub-correspondences corresponding to the identifier of a certain resource may be as shown in table 2. The table 2 records a corresponding relationship between an identifier of a calling operation, an interface calling rule supported by the API gateway of the cloud platform, and an interface calling rule supported by the first API gateway, where the identifier of the calling operation is represented by a name of the calling operation, and the interface calling rule supported by the API gateway of the cloud platform may be represented by the identifier of the API gateway and the identifier of the interface calling rule. As can be seen from table 2, two cloud platforms in the plurality of cloud platforms deploy 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 setup operation, the interface call rule a1 of the API gateway 1 corresponds to the interface call rule E1 of the first AP1 gateway 0; for the setup operation, the interface call rule a2 of the API gateway 2 corresponds to the interface call rule E1 of the first AP1 gateway 0; for the delete operation, the interface call rule B1 of the API gateway 1 corresponds to the interface call rule E2 of the first AP1 gateway 0; for the set-up operation, the interface call rule B2 of the API gateway 2 corresponds to the interface call rule E2 of the first AP1 gateway 0. For other calling operations, the corresponding relationship refers to table 2, and details thereof are not described in this embodiment of the present application.

TABLE 2

For another example, the second corresponding relationship may include an identifier of a call operation, an identifier of a resource, and a corresponding relationship between an interface call rule supported by the API gateway of the cloud platform and an interface call rule supported by the first API gateway.

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

And after receiving the second API request, the second API gateway calls an API interface in the target cloud platform according to the second API request, and after finishing the interface call corresponding to the second API request, the second API gateway sends a second API response to the first API gateway.

It should be noted that, after receiving the second API request, the second API gateway may authenticate the second API request, and after the authentication is successful, execute the interface call action. And if the authentication fails, sending an API response indicating the authentication failure to the first API gateway, or stopping the action. For example, the second API gateway may detect whether an API interface that the second API request needs to call is a registered interface in the target cloud platform, and determine that the authentication fails if the API interface that the second API request needs to call is not a registered interface; and if the API interface required to be called by the second API request is the registered interface, determining that the authentication is successful. Or, the second API gateway may detect whether the user account carried in the second API request has a right to access the second API gateway (or is a valid account), and if the user account carried in the second API request does not have a right to access the second API gateway (or is not a valid account), determine that the authentication fails; and if the user account carried by the second API request has the authority (or is a legal account) of accessing the second API gateway, determining that the authentication is successful.

The second API gateway can ensure the safety of the communication system and reduce unnecessary operation by requesting authentication to the API.

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

In this embodiment of the application, a sending end of the first API request is the user equipment, and corresponding to the foregoing S303, the first API gateway sends the first API request to a client operated by the user equipment, or sends the first API request to the management node, and the management node forwards the first API request to the user equipment.

Referring to the foregoing S302, since the first API gateway issues the format of the API request supported by the first API gateway, the first API request sent by the user through the user equipment is sent according to the first interface call rule supported by the first API gateway, and when the first API gateway returns the corresponding API response, the first API gateway needs to follow the same interface call rule, that is, send the first API response according to the first interface call rule.

Referring to the second aspect of S302, assuming that the same call operation of the same resource in the multiple cloud platforms is a first call operation, for the first call operation, the interface call frequency indicated by the first interface call rule is less than or equal to the interface call frequency indicated by the interface call rule corresponding to the API gateway of each of the multiple cloud platforms. Thus, 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 response manner, that is, each API request is received and an API response is replied. 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 equals the number of second API responses.

For example, when the first interface call rule and the second interface call rule are the same, the first API gateway sends a second API request to the second API gateway after receiving a first API request each time, and sends a first API response to the sender of the first API request after receiving a second API response returned by the second API gateway each time.

For example, the interface call rules corresponding to the call operation 2 of the resource 2 supported by the first API gateway and the second API gateway are: and calling the API interface 1 and the API interface 2 in sequence. After receiving a 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 after receiving a second API response corresponding to API interface 1 returned by the second API gateway, sends a first API response corresponding to API interface 1 to the sending end of the first API request; and after receiving a second API response corresponding to the API interface 2 returned by the second API gateway, the first API gateway sends a first API response corresponding to the API interface 2 to a sending end of the first API request.

When the number of the first API requests is smaller than that of the second API requests, after the first API gateway receives one first API request every time, the first API gateway executes at least two calling processes in sequence according to the second interface calling rule until the obtained second API response can generate a first API response corresponding to the first API request, and then sends the first API response to the sending end of the first API request according to the first interface calling rule. Wherein, this calling process includes: and 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 the API interface 1 and the API interface 2 in sequence, and the first interface calling rule is to call the API interface 1 and the API interface 2 by using an API request once. The first API gateway sends a second API request for calling API interface 1 to the second API gateway after receiving a first API request for calling API interface 1 and API interface 2, sends a second API request for calling API interface 2 to the second API gateway after receiving a second API response corresponding to API interface 1 returned by the second API gateway, and sends a first API response corresponding to API interface 1 and API interface 2 (i.e., a first API response corresponding to the first API request) to the sending end of the first API request after receiving a second API response corresponding to API interface 2 returned by the second API gateway.

The first API gateway may perform resource parameter format conversion on the fourth resource parameter data in multiple ways. The embodiments of the present application are described by taking the following two alternatives as examples:

in a first optional manner, referring to the first aspect in S301, after determining the resource parameter format of the supported API request, the first API gateway establishes a first corresponding relationship 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. After receiving the second API response, the first API gateway queries the first corresponding relation based on the identifier of the first API gateway to obtain a resource parameter format supported by the first API gateway; and the fourth resource parameter data included in the second API response is transferred to obtain third resource parameter data based on the resource parameter format supported by the first API gateway.

The representation manner and the escaping process of the first corresponding relationship may refer to S305, which is not described in detail in this embodiment of the application.

In a second alternative, after determining the resource parameter format of the supported API request, the first API gateway establishes an escape model based on the resource parameter format supported by the API gateway of each of the multiple cloud platforms and the resource parameter format supported by the first API gateway, where the escape model is configured to output resource parameter data corresponding to the received identifier of the API gateway after receiving the identifier of the API gateway and the resource parameter data. And after receiving the second API response, the first API gateway inputs the fourth resource parameter data included in the second API response and the identifier of the first API gateway into the escape model, and determines the resource parameter data output by the escape model as third resource parameter data.

In the related art, when a user uses resources of multiple cloud platforms, the user needs to repeatedly learn a resource format opened by the multiple cloud platforms, in which the API interfaces need to be called, and repeatedly encode the resource format to call the API interfaces of the multiple cloud platforms.

In the embodiment of the application, because the first API gateway is additionally arranged, a uniform entry is provided for calling API interfaces of a plurality of cloud platforms, and therefore, the first API gateway is oriented to a user, and the user only needs to program according to a resource format supported by the first API gateway or trigger a calling operation through a user interface of a management node, so that repeated learning and configuration costs of the user on the same or similar resources (namely, the same resource) are reduced, and user experience is improved.

A suite of user systems or an application may be deployed hierarchically using resources of multiple cloud platforms. In the related art, a user needs to use corresponding resources on the plurality of cloud platforms in a programming manner, so as to implement word segmentation deployment of a user system or application.

Optionally, the first API gateway supports other functions besides the foregoing format integration function for making an API request, for example, the first API gateway supports a service information presentation function, as shown in fig. 4, the communication method provided in this embodiment of the present application further includes:

s309, the first API gateway obtains service information of resources of the cloud platform, wherein the service information comprises at least one of service capacity information and service price.

The service information is information related to a service provided by the resource. The service capability information is used for reflecting the size of the capability of the resource for providing the service, and the service capability information comprises one or more parameter values reflecting the service capability, or the service capability information can be a service capability index value which can be determined based on the parameter values or can be a preset value. For example, for a resource for providing a GPU acceleration service, the service capability information includes one or more of the number of CPUs, the number of memories, the memory size (e.g. 4G memory), the system architecture, the intranet transceiving capability information and a GPU indicator, the intranet transceiving capability information is used to reflect the information transceiving capability of the resource in the internal network, for example, the information is the number of Packets Per Second (PPS), and it is assumed that the intranet transceiving capability information indicates that the intranet transceiving packets are more than 100 tens of thousands, which means that the number of packets per second of the internal network is more than 100 tens of thousands; the system architecture is used for indicating a system architecture supported by a resource, and the system architecture may be at least one of an IOS architecture, an android architecture and a spread architecture, for example, the three architectures may be represented by values 0, 1 and 2 respectively; the GPU indicator is used to indicate whether the corresponding resource has a GPU or the number of GPUs, for example, values 0 and 1 may be used to indicate that there is a GPU and there is no GPU, respectively; the service price is used to reflect the price at which the resource provides the service.

The first API gateway has the capability of recognizing service information of resources in the respective cloud platforms. There may be a plurality of situations when the first API gateway obtains the service information. The examples of the present application are illustrated by taking the following three cases as examples:

in the first case, the first API gateway obtains the service information of the resource of the cloud platform after receiving the service information retrieval request through the user interface. Referring to fig. 2, the management node may provide a user interface to the user device, and the user may perform a retrieval operation on the user interface through the user device. Correspondingly, after receiving the service information retrieval request at the user interface, the management node sends the service information retrieval request to the first API gateway, and the first API gateway acquires the service information of the resources of the cloud platform based on the service information retrieval request. The service information retrieval request comprises resource requirements of a retrieved cloud platform, including requirements of functions, resource formats, resource performance and the like of resources, and the resources of the cloud platform, which are obtained by the first API gateway, need to meet the requirements of the service information retrieval request, that is, are matched with the service information retrieval request.

In an alternative example, the user interface 50 provided by the management node may be as shown in fig. 5, and the user interface 50 includes a search box 501, and the user may input keywords in the search box 501 to perform a search operation. The management node receives a 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 matched with the keyword based on the service information retrieval request. For example, the keyword is: "GPU acceleration, 4-core CPU", the first API gateway obtains service information for resources having 4-core CPU for providing GPU acceleration service.

In another alternative example, the user interface 60 provided by the management node may be as shown in fig. 6, where the user interface 60 includes one or more prompt options 601, where the one or more prompt options 601 may include a resource category prompt option 6011 for prompting a category of resources deployed in the multiple cloud platforms, where the category may be a service category provided by the resources, such as GPU acceleration, disk performance optimization, or network speed bandwidth optimization; the category may also be a self-attribute category of the resource, such as a virtual machine or container. The one or more prompt options 601 may further include a prompt option 6012 reflecting parameters of service capabilities, such as a CPU count option or a memory count option. Each prompt option 601 is provided with a pull-down button, and when a 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 prompt information corresponding to the certain prompt option to be presented. And after the user selects the prompt information corresponding to one or more prompt options, triggering a retrieval button to perform retrieval operation. Correspondingly, the management node receives a service information retrieval request triggered by the retrieval operation, the service information retrieval request includes prompt information selected by the user, and the first API gateway may obtain service information of a resource matched with the service information retrieval request based on the service information retrieval request. For example, the service information retrieval request indicates: the resource type is GPU acceleration, the number of CPUs is 4, and the number of memories is 8.

In yet another alternative example, the management node may present the search box and one or more prompt options at the same time in the user interface. The specific presentation refers to the two aforementioned alternative examples.

In the second case, the first API gateway obtains the service information of the resource of the cloud platform after receiving the first API request. The service information of the resources of the cloud platform is matched with the first API request. For example, the first API request includes an identifier of a resource, and the service information of the resource acquired by the first API gateway is service information of the resource corresponding to the identifier of the resource. For example, the resource is identified as "GPU acceleration", and the service information of the resource acquired by the first API gateway is service information of a resource in the plurality of cloud platforms for providing the GPU acceleration service.

In a third case, the first API gateway periodically obtains capability information of resources of multiple cloud platforms, where the multiple cloud platforms may be all cloud platforms managed by the first API gateway, and after obtaining the capability information of the resources of the multiple cloud platforms each time, the first API gateway stores the obtained capability information of the resources of the cloud platforms 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 resource of the cloud platform to the management node, and the management node presents the capability information of the resource of the cloud platform through a user interface.

As can be seen from S309 and S310, the presenting function of the service information 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 know the capability information of the resource conveniently.

Although the resource capacities of the multiple cloud platforms are different, a certain differentiation still exists. In the related art, if a user needs to know the capability of resources of different cloud platforms, the user needs to query whether the resources meet the self-demand of the user one by one through query operation.

In this embodiment of the application, for the first case of S309, after receiving the service information retrieval request, the first API gateway obtains the service information of the resource of the cloud platform, and presents the obtained service information through the user interface, so that the function of retrieving the service information through the user interface can be implemented, thereby facilitating the user to retrieve the service information as needed and obtaining the service information that the user wants to obtain. The user does not need to inquire whether the resources meet the self requirements one by one through the cloud platform, the operation complexity of the user is reduced, and the user experience is improved. Alternatively, S309 and S310 may be performed before the aforementioned S303. The user may send a first API request to the first API gateway through the user device based on the retrieval result in S303.

For the second case of S309, after receiving the first API request, the first API gateway obtains the service information of the resource of the cloud platform, and presents the obtained service information through the user interface, so that the service information of the resource meeting the requirement can be provided for the user when the user calls the interface, thereby facilitating the user to know the service information of the resource, and better calling the interface. Alternatively, S309 and S310 may be performed after the aforementioned S303.

For the third case of S309, after detecting that the user accesses the specified page for capability information presentation through the user interface, the first API gateway may obtain the capability information of the latest resource of the cloud platform in the specified storage space 4, and present the capability information of the latest resource of the cloud platform through the specified page. When the capability information of the resources of the latest cloud platform is presented to the plurality of cloud platforms managed by the first API gateway, the user can conveniently know the capability information of the resources of the cloud platform managed by the first API gateway as a whole.

Optionally, the management node may further support a resource quota allocation function, the management node presents a uniform user interface of a plurality of cloud platforms, a user may perform resource coordination allocation on the user interface, and the management node performs resource quota allocation after receiving the allocation instruction. For example, a user needs to establish a virtual machine 1 on the cloud platform 1, establish a virtual machine 2 on the cloud platform 2, and allocate resource quotas of the two virtual machines through the user interface. Illustratively, a 4-core CPU and a 2G memory are allocated to the virtual machine 1; and allocating 8-core CPUs and 4G memories for the virtual machine 2.

Optionally, the management node may further support a resource usage right setting function, the management node presents a unified user interface of the multiple cloud platforms, a user may set a resource usage right on the user interface, and the management node sets the resource usage right after receiving the right instruction. For example, the user with the user account M1 has the usage right of the virtual machine 1; the user with the user account M2 has the usage right of the virtual machine 2.

Optionally, the first API gateway also supports resource migration functionality across cloud platforms. As shown in fig. 7, the communication method provided in 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 the resource parameter format supported by the API gateway of the target cloud platform.

When the first API gateway carries out resource migration, a source cloud platform to which resources to be migrated belong and a target cloud platform to which the resources to be migrated need to be migrated are determined, then resource parameter data of the resources to be migrated are obtained on the source cloud platform, and resource parameter formats of the resource parameter data are converted into resource parameter formats supported by the API gateway of the target cloud platform.

The first API gateway can determine the source cloud platform and the destination cloud platform in various ways. In an optional example, the first API gateway receives a resource migration request, the resource migration request indicating a source cloud platform and a destination cloud platform; in another alternative example, the source cloud platform and the destination cloud platform are preset cloud platforms.

The first API gateway may convert the resource parameter format of the resource parameter data into a resource parameter format supported by the destination cloud platform in a plurality of ways. In a first optional example, the first API gateway may first convert the resource parameter format of the resource parameter data into a resource parameter format supported by the first API gateway, where the conversion process is referred to as first conversion, and then convert the resource parameter format of the converted resource parameter data into a resource parameter format supported by the destination cloud platform, and the conversion process is referred to as second conversion. Referring to S305, the first API gateway establishes a first corresponding relationship between a resource parameter format supported by the API gateway of each cloud platform of the multiple cloud platforms and a resource parameter format supported by the first API gateway in advance, and for the resource to be migrated, the first API gateway determines, based on the first corresponding relationship, a corresponding relationship 1 between the resource parameter format supported by the first API gateway and a resource parameter format supported by the source cloud platform, and a corresponding relationship 2 between the resource parameter format supported by the first API gateway and a resource parameter format supported by the destination cloud platform. The first API gateway completes the first conversion based on the corresponding relation 1, and completes the second conversion based on the corresponding relation 2.

In a second optional example, the first API gateway may directly convert the resource parameter format of the resource parameter data into a resource parameter format supported by the destination cloud platform. Referring to the first optional example, for the resource to be migrated, the first API gateway determines, based on the first corresponding relationship, a corresponding relationship 1 between a resource parameter format supported by the first API gateway and a resource parameter format supported by the source cloud platform, and a corresponding relationship 2 between a resource parameter format supported by the first API gateway and a resource parameter format supported by the destination cloud platform, and then determines, based on the corresponding relationship 1 and the corresponding relationship 2, a corresponding relationship 3 between a resource parameter format supported by the source cloud platform and a resource parameter format supported by the destination cloud platform. And 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 corresponding relation 3.

And S312, the first API gateway sends the converted resource parameter data to an 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, and the API gateway of the target cloud platform establishes new resources based on the converted resource parameter data, so that the resource parameter data are transferred from the source cloud platform to the target cloud platform. It should be noted that the target cloud platform may be the same as or different from the target cloud platform, and this is not limited in this embodiment of the application.

In the related art, if a user needs to migrate an original resource deployed on the platform 1 to the platform 2, the resource of the platform 1 needs to be deleted first, and then a new resource is established on the cloud platform 2 in a reprogramming manner.

In the embodiment of the application, if a user needs to perform resource migration across cloud platforms, only a source cloud platform and a target cloud platform need to be specified through a resource migration request or other modes, the first API gateway can achieve automatic migration of the resources across the cloud platforms, reprogramming of the user is not needed, operation complexity is reduced, and user experience is improved.

It should be noted that after the resource is migrated across the cloud platforms, the service data generated when the resource in the source cloud platform provides the service also needs to be controlled by the user to be sent to the destination cloud platform by the source cloud platform, so as to implement complete migration of the resource and the service data.

For the convenience of the reader, the present embodiments are assumed to be illustrated by the following examples: the user X needs to create a virtual machine with 4-core CPU, 8G memory and GPU, and accesses the user interface provided by the management node by running the web client corresponding to the management node on the user device, where the user interface may be as shown in fig. 5 or fig. 6, and the user performs a retrieval operation through the user interface to trigger a service information retrieval request "4-core CPU, 8G memory and GPU". The first API gateway acquires the resource meeting the requirement of the service information retrieval request and acquires the service information of the resource, and the service information of the resource acquired by the first API gateway is presented through a user interface of the management node. The service information of the resource is presented, for example, in the form of a table (the process may refer to the aforementioned S309 and S310). The user may determine a target cloud platform based on the service information of the plurality of resources. Optionally, identifiers (for example, names of cloud platforms) of cloud platforms to which the plurality of resources belong are also presented in the user interface, the user selects a target cloud platform on the user interface through the web client, and correspondingly, the management node receives a selection instruction and sends the selection instruction indicating the target cloud platform to the first API gateway. And then, 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, wherein the calling operation indicated by the first API request is the establishment operation of the resource. And the first API gateway receives the first API request, performs resource parameter format conversion on the first resource data in the first API request to obtain second resource parameter data, and sends the second API request including the second parameter data to a second API gateway in the target cloud platform according to a second interface calling rule. Assuming that the first API request indicates that the resource to be established is a virtual machine, the second API gateway establishes a "4-core CPU, 8G memory, and virtual machine with 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 call rule (the process may refer to S303 to S308).

It should be noted that, the order of the steps of the communication method provided in the embodiment of the present application may be appropriately adjusted, and the steps may also be increased or decreased according to the circumstances, and any method that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application shall be included in the protection scope of the present application, and therefore, the details are not described again.

The embodiment of the present application provides a communication apparatus 70, which is applied to a first API gateway, as shown in fig. 8, where the apparatus 70 includes:

a receiving module 701, configured to receive a first API request; a determining module 702, configured to determine, in the plurality of cloud platforms, a target cloud platform for responding to a first API request, where a format of the first API request is a format supported by a first API gateway; the sending module 703 is configured to send a second API request to a second API gateway, where the second API request is determined based on the first API request, a 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.

In summary, after the receiving module receives the first API request, the determining module determines a second API request in a format supported by the target cloud platform, and the sending module sends the second API request to the second API gateway of the target cloud platform, so that the user can access the target cloud platform in the multiple cloud platforms only by accessing the API unified gateway with the API request in the format supported by the first API gateway, thereby reducing the operation complexity of the user and improving the communication flexibility between the user equipment and different cloud platforms.

Optionally, the first API request includes first resource parameter data, the second API request includes second resource parameter data, a format of the first resource parameter data is a resource parameter format supported by the first API gateway, a 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 performing resource parameter format conversion on the first resource parameter data.

Optionally, as shown in fig. 9, the apparatus 70 further comprises: the integration module 704 is configured to integrate resource parameter formats corresponding to the same call operation of the same resource in the multiple cloud platforms, so as to obtain a resource parameter format of the same call operation of the same resource supported by the first API gateway.

Optionally, the second API request is sent by the first API gateway based on a second interface call rule, where the second interface call rule is an interface call rule supported by the second API gateway, and 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 701 is further configured to receive a second API response sent by the second API gateway; the sending module 703 is further configured to reply the first API response to the sending end of the first API request according to the first interface call rule based on the second API response.

Optionally, as shown in fig. 10, the apparatus 70 further comprises: the rule determining module 705 is configured to determine, for the same call operation of the same resource in the multiple cloud platforms, a first interface call rule corresponding to the same call operation of the same resource based on an interface call rule corresponding to the call operation.

Optionally, the interface calling rule of the calling operation is used to indicate an interface set corresponding to the calling operation and a calling time sequence of the interface set; when the interface set corresponding to the same calling operation of the same resource in the plurality of cloud platforms and the calling time sequence of the interface set are the same, a first interface calling rule corresponding to the same calling operation of the same resource is to call an API (application program interface) in the interface set according to the calling time sequence; when the interface sets corresponding to the same calling operation of the same resource in a plurality of cloud platforms are the same, calling time sequences are different, and a first interface calling rule corresponding to the same calling operation of the same resource is to call an API interface in the interface set corresponding to the same calling operation by adopting an API request; 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 call the API interface in the interface set corresponding to the same calling operation by adopting an API request.

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 apparatus 70 further comprises: the presenting module 706 is configured to provide service information of the resource of the cloud platform through the user interface, where the service information includes at least one of service capability information and service price.

Optionally, as shown in fig. 12, the apparatus 70 further comprises: an obtaining module 707 configured to: after receiving a service information retrieval request through a user interface, acquiring service information of resources of a cloud platform; or after receiving the first API request, acquiring service information of the resources of the cloud platform.

Optionally, the target cloud platform is determined based on a selection instruction sent by the management node, the selection instruction is used for indicating the target cloud platform, and the selection instruction is received by the management node through the user interface; or the target cloud platform is determined based on a selection instruction sent by the client, wherein the selection instruction is used for indicating the target cloud platform; alternatively, the first API request includes an identification of the target cloud platform.

Optionally, as shown in fig. 13, the apparatus 70 further includes: a conversion module 708, configured to convert a resource parameter format of the resource parameter data of the resource to be migrated into a resource parameter format supported by an API gateway of the destination cloud platform; the sending module 703 is further configured to send the converted resource parameter data to an API gateway of the destination cloud platform.

Optionally, 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 at the user interface and sent to the first API gateway.

It should be noted that: in the communication device provided in the above embodiment, when executing the communication method, only the division of the above functional modules is taken as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the communication device is divided into different functional modules so as to complete all or part of the above described functions. Fig. 14 assumes that the communication device is a first API gateway, and fig. 14 schematically provides a possible basic hardware architecture of the first API gateway provided in the embodiment of the present application in an actual application scenario. The first API gateway 101 includes: API service module 1011, rights authentication module 1012, resource management module 1013, API analysis module 1014, and API database 1015.

The API service module 1011 is configured to issue a format of an API request supported by the first API gateway to provide a uniform API interface to the user equipment, which may implement the aforementioned function of S302.

The authority authentication module 1012 is configured to perform authority authentication on the received first API request, and may implement the authentication function described in the foregoing S304.

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

Optionally, the API service module 1011 is further configured to receive the first API request, and after the authority authentication module 1012 is invoked to authenticate the first API request, pass the successfully authenticated first API request to the resource management module 1013.

The API analysis module 1014 is configured to determine a format of the API request, which may implement the aforementioned function of S301.

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

The environment outside the first API gateway 101 in fig. 14 is only an exemplary environment, and the relevant explanation may refer to the corresponding explanations in fig. 1 and fig. 2 described above.

It is worth noting that the functions of the aforementioned API service module 1011 can be implemented by the receiving module 701; rights authentication module 1012 and API analysis module 1014 may be implemented by determination module 702; the function of the resource management module 1013 may be implemented by the sending module 703. Fig. 14 merely provides an example in which the above-described function allocation is performed by different function modules as needed, and does not limit the division of the 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, 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 the processors 901 may be one or more, and fig. 15 only illustrates one of the processors 901. Alternatively, 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. Alternatively, the plurality of processors 901 of the computer device 900 may also be integrated as a multi-core processor.

Memory 902 stores computer instructions and data; the memory 902 may store computer instructions and data needed to implement the communication methods provided herein, e.g., the memory 902 stores instructions for implementing steps of the communication methods. Memory 902 may be any one or any combination of the following storage media: nonvolatile memory (e.g., Read Only Memory (ROM), Solid State Disk (SSD), hard disk (HDD), optical disk), volatile memory.

The communication interface 903 may be any one or any combination of the following devices: a network interface (e.g., an ethernet interface), a wireless network card, etc. having 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 may connect the processor 901 with the memory 902 and the communication interface 903. Thus, via bus 904, processor 901 may access memory 902 and may also interact with other computer devices or terminals via communication interface 903.

In the present application, computer device 900 executes computer instructions in memory 902, causing computer device 900 to implement the communication methods provided herein, or causing computer device 900 to deploy a communication system.

In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as a memory comprising instructions, executable by a processor of a server to perform a communication method as shown in various embodiments of the present application is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

An embodiment of the present application provides a communication system, including: a first API gateway and a plurality of cloud platforms, each cloud platform including an API gateway, the first API gateway including any of the communication devices provided in the embodiments of the present application, for example, communication device 70. Alternatively, the structure of the communication system may refer to the aforementioned structures in fig. 1, fig. 2, and fig. 14.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product comprising one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (e.g., solid state disk), among others.

In this application, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The term "at least one" means 1 or more, and the term "plurality" means two or more unless explicitly defined otherwise. A refers to B and refers to the simple variation where A is the same as B or A is B.

It should be noted that: in the communication apparatus or the communication system provided in the above embodiments, when the communication method is executed, only the division of the above functional modules is illustrated, and in practical applications, the above functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to complete all or part of the above described functions. In addition, the communication apparatus, the communication system, and the communication method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of communication, the method comprising:

a first Application Program Interface (API) gateway receives a first API request;

the first API gateway determines a target cloud platform used for responding to the first API request in a plurality of cloud platforms, wherein 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 a second API gateway, the second API request is determined based on 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 the API gateway of the target cloud platform.

2. 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, the format of the first resource parameter data is a resource parameter format 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 performing resource parameter format conversion on the first resource parameter data.

3. The method of claim 2, further comprising:

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

4. 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 is a union of the resource parameter formats corresponding to the same call operation of the same resource in the plurality of cloud platforms.

5. 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 invocation rule, the second interface invocation rule being an interface invocation rule supported by the second API gateway, the second interface invocation rule being determined by the first API gateway based on the first interface invocation rule supported by the first API gateway and the first API request; the method further comprises the following steps:

the first API gateway receives a second API response sent by the second API gateway;

and the first API gateway replies a first API response to the sending end of the first API request according to the first interface calling rule based on the second API response.

6. The method of claim 5, further comprising:

7. The method according to claim 6, wherein the interface calling rule of the calling operation is used for indicating the interface set corresponding to the calling operation and the calling timing sequence of the interface set;

when the interface set corresponding to the same calling operation of the same resource in the plurality of cloud platforms and the calling time sequence of the interface set are the same, a first interface calling rule corresponding to the same calling operation of the same resource is to call an API (application program interface) in the interface set according to the calling time sequence;

when the interface sets corresponding to the same calling operation of the same resource in the plurality of cloud platforms are the same, the calling time sequence is different, and the first interface calling rule corresponding to the same calling operation of the same resource is that an API interface in the interface set corresponding to the same calling operation is called by adopting an API request;

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 calls the API interfaces in the interface sets corresponding to the same calling operation by adopting an API request.

8. The method of 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.

9. The method according to any one of claims 1 to 8, further comprising:

the first API gateway passes service information of resources of a user interface cloud platform, and the service information comprises at least one of service capacity information and service price.

10. The method of claim 9, further comprising:

after receiving a service information retrieval request through the user interface, the first API gateway acquires service information of resources of the cloud platform;

or after receiving the first API request, the first API gateway obtains service information of the resource of the cloud platform.

11. 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, the selection instruction is used for indicating the target cloud platform, and the selection instruction is received by the management node through a user interface;

or the target cloud platform is determined based on a selection instruction sent by a client, wherein the selection instruction is used for indicating the target cloud platform;

alternatively, the first API request includes an identification of the target cloud platform.

12. The method according to any one of claims 1 to 11, further comprising:

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;

and the first API gateway sends the converted resource parameter data to an API gateway of the target cloud platform.

13. The method of any of claims 1 to 12, wherein the first API request is sent by a client to the first API gateway;

or, the first API request is received by a management node at a user interface and sent to the first API gateway.

14. The method according to any of claims 1 to 13, wherein the calling operation indicated by the first API request comprises any of:

establishing operation of resources, deleting operation of resources, modifying operation of resources and inquiring operation of resources.

15. A communications apparatus, the apparatus being adapted for use with a first application program interface, API, gateway, the apparatus comprising:

a receiving module, configured to receive a first API request;

a determining module, configured to determine, among a plurality of cloud platforms, a target cloud platform for responding to the first API request, where a format of the first API request is a format supported by the first API gateway;

a sending module, configured to send a second API request to a second API gateway, where the second API request is determined based on the first API request, a 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.

16. The apparatus according to claim 15, wherein the first API request includes first resource parameter data, the second API request includes second resource parameter data, the first resource parameter data is in a resource parameter format supported by the first API gateway, the first resource parameter data is in a resource parameter format supported by the second API gateway, and the second resource parameter data is obtained by performing resource parameter format conversion on the first resource parameter data.

17. The apparatus of claim 16, further comprising:

and the integration module is used for integrating the resource parameter formats corresponding to the same calling operation of the same resource in the plurality of cloud platforms to obtain the resource parameter formats of the same calling operation of the same resource supported by the first API gateway.

18. The apparatus according to claim 17, wherein the resource parameter format of the same call operation of the same resource supported by the first API gateway is a union of the resource parameter formats corresponding to the same call operation of the same resource in the plurality of cloud platforms.

19. The apparatus according to any of claims 15 to 18, wherein the second API request is sent by the first API gateway based on a second interface invocation rule, the second interface invocation rule being an interface invocation rule supported by the second API gateway, the second interface invocation rule being determined by the first API gateway based on the first interface invocation 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;

and the sending module is further configured to reply a first API response to the sending end of the first API request according to the first interface call rule based on the second API response.

20. The apparatus of claim 19, further comprising:

and the rule determining module is used for determining a 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 for the same calling operation of the same resource in the plurality of cloud platforms.

21. The apparatus according to claim 20, wherein the interface calling rule of the calling operation is used to indicate the interface set corresponding to the calling operation and the calling timing sequence of the interface set;

22. The apparatus of claim 17, 18, 20 or 21, wherein the same resource is a resource whose resource defines a similarity greater than a similarity threshold.

23. The apparatus of any one of claims 15 to 22, further comprising:

the presentation module is used for service information of resources of the cloud platform through the user interface, and the service information comprises at least one of service capacity information and service price.

24. The apparatus of claim 23, further comprising:

an acquisition module to:

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

or after receiving the first API request, acquiring service information of the resources of the cloud platform.

25. The apparatus 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 for indicating the target cloud platform, and the selection instruction is received by the management node through a user interface;

26. The apparatus of any one of claims 15 to 25, further comprising:

the conversion module is used for converting 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 further configured to send the converted resource parameter data to an API gateway of the destination cloud platform.

27. The apparatus of any of claims 15 to 26, wherein the first API request is sent by a client to the first API gateway;

28. The apparatus according to any of claims 15 to 27, wherein the calling operation indicated by the first API request comprises any of:

29. A computer device, comprising:

a processor and a memory;

the memory to store computer instructions;

the processor, configured to execute the computer instructions stored by the memory, to cause the computer device to perform the communication method of any one of claims 1 to 14.

30. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises computer instructions that instruct a computer device to perform the communication method of any of claims 1 to 14.

31. A communication system, comprising: a first API gateway and a plurality of cloud platforms, each cloud platform comprising an API gateway, the first API gateway comprising the communication device of any of claims 15 to 28.