CN111385318B - Method and device for deploying and/or using API (application program interface) service and cloud service network - Google Patents
Method and device for deploying and/or using API (application program interface) service and cloud service network Download PDFInfo
- Publication number
- CN111385318B CN111385318B CN201811612192.6A CN201811612192A CN111385318B CN 111385318 B CN111385318 B CN 111385318B CN 201811612192 A CN201811612192 A CN 201811612192A CN 111385318 B CN111385318 B CN 111385318B
- Authority
- CN
- China
- Prior art keywords
- api service
- api
- node
- available edge
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for deploying and/or using an API service and a cloud service network. The disclosed method comprises: acquiring deployment permission and/or use permission for deploying the API service on an edge node of a cloud service provider; acquiring relevant information of available edge nodes corresponding to deployment authority and/or use authority; deploying and/or calling an API service deployed on one or more available edge nodes, wherein the relevant information of an available edge node comprises at least one of the following: the address, port number of the available edge node. The technical scheme disclosed enables an API service provider and/or a consumer to directly deploy the API service on the API service intermediary platform and/or directly acquire the API service information and use the API service, manual operation of the API service intermediary is not needed, and the deployment and/or use process is quicker.
Description
Technical Field
The invention relates to the technical field of computer networks, in particular to a method and a device for deploying and/or using an API (application program interface) service and a cloud service network.
Background
Cloud service providers use cloud service networks to provide network acceleration services for websites of customers, such as content providers, to provide better user experience for users or consumers of the customer websites.
In the prior art, services (e.g., web services) of a content provider customer (i.e., API service consumer) website typically require that API services provided by a third party (i.e., API service provider) be invoked through a cloud services network provided by a cloud service provider (i.e., API service broker). For example, the API service provider needs to submit relevant information about API services that can be provided by the API service provider to the cloud service provider in advance, and the cloud service provider manually issues and deploys the API services to edge nodes of the cloud service network for the API service consumers to call.
That is, the API service discovery in the prior art has three roles: the service provider registers and updates the API service information provided by the service provider to the service intermediary, the service consumer obtains the API service information from the service intermediary and uses the services, and the service provider and the service consumer need to depend on the service intermediary.
Thus, when an API service provider desires to deploy a service to a cloud service node of an API service intermediary, relevant information needs to be provided to the API service intermediary, which deploys (e.g., includes service information registration, service resource upload, update, service start/stop, etc.) the API service. Similarly, the service consumer also needs to use (e.g., query, call) the API service through the API service intermediary.
The above technical solutions in the prior art have the following problems:
1. since the whole deployment process requires a certain amount of time, the cloud service provider may not be able to deploy the API service of the customer in time.
2. When the API service fails, the method only depends on manual processing of a cloud service provider, and the client cannot delete and stop the service.
3. The cloud service provider does not know the actual conditions of the API service and the API service consumer website service, and is easy to make mistakes during manual processing, so that other problems are caused.
In order to solve the above problems, a new technical solution needs to be proposed.
Disclosure of Invention
A method of deploying and/or using API services in accordance with the invention comprises:
acquiring deployment permission and/or use permission for deploying the API service on an edge node of a cloud service provider;
acquiring relevant information of available edge nodes corresponding to deployment authority and/or use authority;
deploying API services on one or more available edge nodes and/or calling API services deployed on one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: the address of the edge node, port number, is available.
According to the method for deploying and/or using the API service, the step of acquiring the deployment authority and/or the use authority for deploying the API service on the edge node of the cloud service provider comprises the following steps:
the method comprises the steps of sending a client registration request to a registration server of the cloud service provider, obtaining a client authentication identifier corresponding to deployment authority and/or use authority after client registration authentication, and obtaining the deployment authority and/or use authority through the client authentication identifier.
According to the method for deploying and/or using the API service, the step of deploying the API service on one or more available edge nodes comprises the following steps:
selecting an available edge node as a registration node, and registering API service information for describing API service on the registration node; and
uploading API service resources on a designated storage space of a registered node, enabling API services, synchronizing API service information on a non-registered node of a plurality of available edge nodes, deploying API services in a first manner, or uploading API service resources on a designated storage space of all nodes of a plurality of available edge nodes, enabling API services, synchronizing API service information on a non-registered node of a plurality of available edge nodes, deploying API services in a second manner,
wherein, the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in a first mode or a second mode.
The method for deploying and/or using the API service further comprises the following steps:
when the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
When the API service is deployed on a plurality of available edge nodes, one available edge node is selected as a parent node, and the rest of the available edge nodes are managed through the parent node.
The device for deploying and/or using the API service comprises the following components:
the authority acquisition module is used for acquiring deployment authority and/or use authority for deploying the API service on the edge node of the cloud service provider;
the node information acquisition module is used for acquiring relevant information of available edge nodes corresponding to the deployment authority and/or the use authority;
an API service deployment and/or invocation module to deploy API services on the one or more available edge nodes and/or to invoke API services deployed on the one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: the address, port number of the available edge node.
According to the device for deploying and/or using the API service, the authority acquiring module is further used for:
sending a client registration request to a registration server of the cloud service provider, obtaining a client authentication identifier corresponding to the deployment authority and/or the use authority after the client registration authentication is carried out, and obtaining the deployment authority and/or the use authority through the client authentication identifier.
According to the device for deploying and/or using the API service, the API service deploying and/or calling module is further used for:
selecting an available edge node as a registration node, and registering API service information for describing API service on the registration node; and
uploading API service resources and enabling API services in a designated storage space of a registered node, synchronizing API service information on a non-registered node of a plurality of available edge nodes, and deploying the API services in a first mode, or uploading API service resources and enabling API services in a designated storage space of all nodes of a plurality of available edge nodes, synchronizing API service information on a non-registered node of the plurality of available edge nodes, and deploying the API services in a second mode; and/or
When the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
When the API service is deployed on a plurality of available edge nodes, one available edge node is selected as a parent node, the rest of the available edge nodes are managed through the parent node,
wherein, the storage space is designated as an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in a first mode or a second mode.
The cloud service network for deploying and/or using the API service comprises the following components:
the client registration server is used for providing deployment authority and/or use authority for deploying the API service on the edge node of the cloud service provider and providing relevant information of an available edge node corresponding to the deployment authority and/or use authority;
and the edge node is used for deploying and/or providing the API service.
The cloud service network for deploying and/or using the API service further comprises the following steps:
the apparatus for deploying and/or using API services as described above,
its client registration server is also used for:
receiving a customer registration request from a device deploying and/or using the API service;
after authenticating the client registration, providing a client authentication identification corresponding to the deployment right and/or the usage right,
the client authentication identification is used for identifying the deployment authority and/or the use authority.
According to the cloud service network for deploying and/or using the API service, the edge node is further used for:
selecting one available edge node from one or more available edge nodes as a registration node for registering API service information for describing the API service; and
the registered nodes store the uploaded API service resources and the enabled API service in the designated storage space of the registered nodes, the non-registered nodes in the plurality of available edge nodes respectively synchronize API service information and deploy the API service in a first mode, or all the nodes in the plurality of available edge nodes store the uploaded API service resources and the enabled API service in the designated storage space of the registered nodes respectively, the non-registered nodes in the plurality of available edge nodes respectively synchronize the API service information and deploy the API service in a second mode; and/or
When the API service deployed on one available edge node cannot be accessed, the available edge node deletes the API service information related to the API service, and the other available edge nodes containing the API service information of the API service delete the API service information related to the API service; and/or
When the API service is deployed on multiple available edge nodes, one available edge node is selected as a parent node, the parent node manages the remaining available edge nodes,
wherein, the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in a first mode or a second mode.
According to the technical scheme of the invention, the API service provider and/or the consumer can directly deploy the API service on the API service intermediary platform and/or directly acquire the API service information and use the API service, the manual operation of the API service intermediary is not needed, and the deployment and/or use process is quicker.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. In the drawings, like reference numerals are used to indicate like elements. The drawings in the following description are illustrative of some, but not all embodiments of the invention. To a person skilled in the art, without inventive effort, other figures can be derived from these figures.
FIG. 1 schematically illustrates a schematic flow chart of a method of deploying and/or using an API service according to the present invention.
FIG. 2 schematically shows a block schematic of an apparatus for deploying and/or using API services according to the present invention.
FIG. 3 illustratively depicts a schematic diagram of a cloud services network deploying and/or using API services in accordance with the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
FIG. 1 schematically illustrates a schematic flow chart of a method of deploying and/or using an API service according to the present invention.
As shown in the solid line box of FIG. 1, the method for deploying and/or using API services according to the present invention comprises:
step S102: acquiring a deployment authority and/or a use authority for deploying the API service on an edge node of a cloud service provider;
step S104: acquiring relevant information of available edge nodes corresponding to deployment authorities and/or use authorities;
step S106: deploying API services on one or more available edge nodes and/or calling API services deployed on one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: the address, port number of the available edge node.
For example, the connectable cloud service network edge node (i.e., the available edge node) information refers to an address (e.g., an IP address) of an edge node that an API service provider needs to first obtain and can access in order to deploy (e.g., including service information registration, service resource upload, update, service start/stop, and the like) its API service to the cloud service network edge node, or in order for an API service consumer to use (e.g., query, call) the API service.
Corresponding to the above steps S102 and S104, for example, the API service provider or API service consumer may obtain cloud service network edge available node information and authentication information (through a custom interface module, for example, the right obtaining module 201 described below in conjunction with fig. 2) containing the following from a cloud service provider (for example, the customer registration server 301 described below in conjunction with fig. 3):
the ip is an ip address of an edge node of the cloud service network, the port is a port number, and the vkey is authentication information (corresponding to the deployment authority and/or the use authority).
Corresponding to the step S102, in order to prevent the occurrence of malicious API services, the above technical solution introduces a vkey check mechanism. Before the API service provider deploys the API service and/or before the API service consumer uses the API service, the information of the API service provider is required to be registered with the cloud service provider, and after the cloud service provider confirms that the information is passed, a vkey value is returned to the user.
Corresponding to the step S106, when the API service provider uploads the service to the edge node and/or before the API service consumer uses the API service, (e.g., the API service pool) performs authentication through the vkey value, and the authentication passing party can upload (i.e., deploy) the API service-related information and/or use the API service. If the authentication is not passed, the API service provider is not allowed to deploy the API service, so that the safe deployment of the API service is ensured, or the API service consumer is not allowed to use the API service, so that the safe use of the API service is ensured.
According to the technical scheme, manual authentication and deployment of a cloud service provider are not needed, automatic authentication and deployment can be achieved, and after the deployment right and/or the use right are distributed, unauthorized clients can be directly isolated and refused to deploy and/or use the API service according to the client right.
For example, the malicious API service deployment request of the unauthorized API service provider can be directly rejected, and/or the use request of the unauthorized API service consumer for malicious use of the API service can be directly rejected, so that the authorized API service provider can directly deploy the legal API service, and/or the authorized API service consumer can directly use the API service.
Optionally, the API service provider and/or the API service consumer may store the obtained available node information and authentication information for subsequent direct use.
Optionally, after the vkey has expired, a new vkey may be obtained from the cloud service provider.
Optionally, step S102 includes:
sending a client registration request to a registration server of the cloud service provider, obtaining a client authentication identifier corresponding to the deployment authority and/or the use authority after the client registration authentication is carried out, and obtaining the deployment authority and/or the use authority through the client authentication identifier.
For example, the client authentication identifier used by the API service provider and/or API service consumer may be the vkey described above.
Optionally, step S106 includes:
selecting an available edge node as a registration node, and registering API service information for describing API service on the registration node; and
uploading API service resources on a designated storage space of a registered node, enabling API services, synchronizing API service information on a non-registered node of a plurality of available edge nodes, deploying API services in a first manner, or uploading API service resources on a designated storage space of all nodes of a plurality of available edge nodes, enabling API services, synchronizing API service information on a non-registered node of a plurality of available edge nodes, deploying API services in a second manner,
wherein, the storage space is designated as an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in a first mode or a second mode.
For example, the API service pool is responsible for managing and maintaining API service information, and may be separately run on each cloud service network (available edge) node providing the service.
For example, an API service provider may upload an API service to an API service pool of available (cloud services network) edge nodes (e.g., registered edge nodes specified by a cloud service provider).
For example, the API service pool is used to provide a functional interface for API service registration, and after acquiring connectable cloud service network edge node information, the API service provider may upload its API service to the API service pool through the interface.
For example, the API service pool may also be used to call a registration interface module (e.g., API service deployment and/or call module 205 described below in connection with fig. 2), in connection with the vkey information (optional), to complete registration of service information (i.e., perform API service registration) including the following information:
wherein, level is the level of the API service, the default is 0, and the selectable values are 0 and 1. Corresponding to the above-described API service deployment in the first manner, 0 means that this API service only needs single-point deployment, and at this time, the remaining edge nodes (i.e., the above-described unregistered nodes) of the entire network only need to store API service information (i.e., synchronization API service information). Corresponding to the above API service deployment in the second manner, 1 indicates that the API service needs to be deployed by all cloud service network edge nodes (or multiple cloud service network edge nodes in the entire network), and at this time, the API service (resource) is also copied (for example, by the API service pool of each node) in addition to the API service information. The second mode of deploying the API service is useful for scenarios with high delay requirements of the API service, and can reduce delay. As described above, the vkey value may be checked at deployment time (e.g., via an API service pool), the service may be registered by the party when passing, and if the check does not pass, the vkey value may be retrieved from a cloud service provider (e.g., the customer registration server 301 described below in conjunction with fig. 3).
Optionally, as shown in the dashed box of fig. 1, the method for deploying and/or using API services according to the present invention further includes:
step S108: when the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
Step S110: when the API service is deployed on a plurality of available edge nodes, one available edge node is selected as a parent node, and the rest of the available edge nodes are managed through the parent node.
Corresponding to the step S110, for example, when the API service is deployed in the plurality of available edge nodes in the first manner, the API service (including uploading API service resources, API service information) may be deployed on one of the available child edge nodes, and the API service information corresponding to the API service may be synchronously updated to the remaining available child edge nodes in the plurality of available edge nodes and/or other available edge nodes in the entire network through the selected parent node.
Corresponding to the step S110, for example, after the API service provider registers or updates (e.g., modifies or deletes) an API service with (an API service pool of) a certain cloud service network edge node, the cloud service network edge node (e.g., through the API service pool set thereon) may send the API service information to its parent node for synchronous storage or update, in addition to storing or updating the API service information locally or updating locally. And the father node receiving the API service information issues the API service information to other cloud service network edge nodes in real time, and finally each cloud service network edge node stores a complete API service information list, so that synchronous registration or synchronous updating operation of related nodes is completed.
Corresponding to the step S110 and the step S108, for example, when an edge node with API service deployed fails and is inaccessible, the parent node detects the failure of the edge node, deletes the API service information deployed on the failed node and notifies other edge nodes, and after receiving the notification, other edge nodes immediately delete the corresponding API service information, and finally, the edge nodes in the entire network (or a plurality of edge nodes in the entire network related to the specified API service) all delete the API service related content information in the failure. That is, when the API service a is deployed on the edge node a, after the node fails, and the parent node senses the failure, the API service information (i.e., the API service information about the service a) related to the node (e.g., stored in the API service pool of the node) is deleted, and meanwhile, the message is notified to other edge nodes (e.g., the edge node B) in real time, and the other edge nodes also correspondingly delete the API service information about the service a stored on the other edge nodes after receiving the notification.
Since the API service information is only a part of simple text content, the storage space is not occupied too much.
Through the technical scheme, different permissions (such as uploading, modifying, deleting and the like) can be set for the API service provider and the available edge nodes capable of deploying the API service can be specified for the API service provider.
Through the technical scheme, different permissions (such as inquiry and call) can be set for the API service consumer, and the available edge node capable of deploying the web service can be specified for the API service consumer.
For example, an API service consumer may perform the following specific operations:
1. an API service consumer may send a request to any connectable edge node to query information for an API service. For example, since each edge node stores complete API service information, the content of the API service information (i.e., the information such as the address of the node where the API service is located, the API service port, the API request (service) path, and the API service method (function) as described above) can be easily queried.
2. The API service consumer can call the specified API service by using the inquired API service information. For example, when an API service consumer requests certain API service information, the API service consumer may call the API service at a corresponding node according to the API service information. If the level of the API service is 0, a service request needs to be made to a node providing the API service, and if the level of the API service is 1, the service request can be made at the edge node which is connected currently.
FIG. 2 schematically illustrates a block schematic diagram of an apparatus for deploying and/or using API services in accordance with the present invention.
As shown in fig. 2, an apparatus 200 for deploying and/or using an API service according to the present invention includes:
the permission acquiring module 201 is configured to acquire a deployment permission and/or a usage permission for deploying the API service on an edge node of a cloud service provider;
a node information obtaining module 203, configured to obtain relevant information of an available edge node corresponding to a deployment authority and/or a use authority;
an API service deployment and/or invocation module 205 to deploy API services on one or more available edge nodes and/or to invoke API services deployed on one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: the address of the edge node, port number, is available.
Optionally, the right obtaining module 201 is further configured to:
sending a client registration request to a registration server of the cloud service provider, obtaining a client authentication identifier corresponding to the deployment authority and/or the use authority after the client registration authentication is carried out, and obtaining the deployment authority and/or the use authority through the client authentication identifier.
Optionally, the API service deploying and/or calling module 205 is further configured to:
selecting an available edge node as a registration node, and registering API service information for describing API service on the registration node; and
uploading API service resources and enabling API services in a designated storage space of a registered node, synchronizing API service information on a non-registered node of a plurality of available edge nodes, and deploying the API services in a first mode, or uploading API service resources and enabling API services in a designated storage space of all nodes of a plurality of available edge nodes, synchronizing API service information on a non-registered node of the plurality of available edge nodes, and deploying the API services in a second mode; and/or
When the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
When the API service is deployed on multiple available edge nodes, one available edge node is selected as a parent node, the remaining available edge nodes are managed by the parent node,
wherein, the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in a first mode or a second mode.
FIG. 3 illustratively depicts a schematic diagram of a cloud services network deploying and/or using API services in accordance with the present invention.
As shown in fig. 3, a cloud services network 300 that deploys and/or uses API services includes:
the client registration server 301 is configured to provide a deployment right and/or a usage right for deploying the API service on an edge node of a cloud service provider, and provide related information of an available edge node corresponding to the deployment right and/or the usage right;
an edge node 303 for deploying and/or providing API services.
Optionally, as shown in fig. 3, the cloud service network 300 for deploying and/or using the API service further includes:
such as the apparatus 200 for deploying and/or using API services shown in figure 2,
the client registration server 301 is also configured to:
receiving a client (e.g., client 305 in FIG. 3) registration request from a device deploying and/or using the API service;
after authenticating the client registration, providing a client authentication identification corresponding to the deployment right and/or the usage right,
wherein, the client authentication identifier is used for identifying the deployment authority and/or the use authority.
Optionally, the edge node 303 is further configured to:
selecting one available edge node 303 from one or more available edge nodes 303 as a registration node for registering API service information for describing the API service; and
the registered node stores the uploaded API service resource and the enabled API service in a designated storage space of the registered node, the unregistered nodes in the plurality of available edge nodes 303 synchronize API service information respectively, and the API service is deployed in a first mode, or all the nodes in the plurality of available edge nodes 303 store the uploaded API service resource and the enabled API service in the designated storage spaces respectively, and the unregistered nodes in the plurality of available edge nodes 303 synchronize API service information respectively, and the API service is deployed in a second mode; and/or
When an API service deployed on one available edge node 303 cannot be accessed, the available edge node 303 deletes API service information related to the API service, and the remaining available edge nodes 303 including the API service information of the API service delete the API service information related to the API service; and/or
When deploying API services on multiple available edge nodes 303, one available edge node 303 is selected as a parent node, the parent node manages the remaining available edge nodes 303,
wherein, the storage space is designated as an API service pool, and the API service information comprises at least one of the following items: the API service comprises an API service name, API service content, an address of an edge node 303 where the API service is located, an API service port, an API service path, a request mode of the API service, an API service function, an API service parameter, and an API service level, wherein the API service level is used for describing whether the API service is deployed in a first manner or in a second manner.
According to the technical scheme of the invention, the method has the following advantages:
1. the API service provider and/or the consumer can directly deploy the API service on an API service intermediary platform (such as a cloud service network of a cloud service provider) and/or directly acquire the API service information and use the API service, manual operation of the API service intermediary is not needed, and the deployment and/or use process is quicker. For example, a cloud service provider is not required to collect and issue available API service information manually, so that the whole process is simplified, and possible errors in the process are avoided. Participants (e.g., API service intermediaries) are reduced, improving the overall stability of the service. That is, the whole API service system can be ensured to operate autonomously and stably without depending on an external condition (e.g., API service intermediary).
2. The API service (e.g., each node deploying the API service) can be managed and maintained autonomously, reducing manual operations. For example, when a fault occurs, autonomous discovery processing can be realized, fault information can be deleted in real time, and manual intervention is not needed.
3. Different deployment permissions (e.g., upload, modify, delete, etc.) may be set for an API service provider and designated for it the available edge nodes for which API services may be deployed. Similarly, different usage rights (e.g., queries, calls) may also be set for the API service consumer.
The above-described aspects may be implemented individually or in various combinations, and such variations are within the scope of the present invention.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as is well known to those skilled in the art.
Finally, it should be noted that: the above examples are only for illustrating the technical solutions of the present invention, and are not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A method of deploying and/or using API services, comprising:
acquiring deployment permission and/or use permission for deploying the API service on an edge node of a cloud service provider;
acquiring relevant information of available edge nodes corresponding to the deployment authority and/or the use authority;
deploying API services on one or more available edge nodes and/or calling API services deployed on one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: addresses, port numbers of available edge nodes;
the step of deploying API services on one or more available edge nodes comprises:
selecting an available edge node as a registration node, and registering API service information for describing the API service on the registration node; and
uploading API service resources in the specified storage space of the registered node, enabling the API service, synchronizing the API service information on the unregistered nodes in the plurality of available edge nodes, and deploying the API service in a first mode, or uploading API service resources in the specified storage space of all the plurality of available edge nodes, enabling the API service, synchronizing the API service information on the unregistered nodes in the plurality of available edge nodes, and deploying the API service in a second mode.
2. The method of deploying and/or using an API service as recited in claim 1, wherein the step of obtaining deployment rights and/or usage rights for deploying the API service on an edge node of a cloud service provider comprises:
and sending a client registration request to a registration server of the cloud service provider, acquiring a client authentication identifier corresponding to the deployment authority and/or the use authority after client registration authentication, and acquiring the deployment authority and/or the use authority through the client authentication identifier.
3. The method for deploying and/or using an API service of claim 1,
the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in the first mode or the second mode.
4. The method of deploying and/or using an API service of claim 3, further comprising:
when the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
When the API service is deployed on a plurality of available edge nodes, one available edge node is selected as a parent node, and the rest of the available edge nodes are managed through the parent node.
5. An apparatus for deploying and/or using API services, comprising:
the authority acquisition module is used for acquiring deployment authority and/or use authority for deploying the API service on the edge node of the cloud service provider;
a node information acquisition module, configured to acquire relevant information of an available edge node corresponding to the deployment authority and/or the usage authority;
an API service deployment and/or invocation module to deploy API services on the one or more available edge nodes and/or to invoke API services deployed on the one or more available edge nodes,
wherein the relevant information of the available edge nodes comprises at least one of the following: addresses and port numbers of available edge nodes;
the step of deploying API services on one or more available edge nodes comprises:
selecting an available edge node as a registration node, and registering API service information for describing the API service on the registration node; and
uploading API service resources in the designated storage space of the registered node, enabling the API service, synchronizing the API service information on the unregistered nodes in the plurality of available edge nodes, and deploying the API service in a first mode, or uploading API service resources in the designated storage space of all the plurality of available edge nodes, enabling the API service, synchronizing the API service information on the unregistered nodes in the plurality of available edge nodes, and deploying the API service in a second mode.
6. The apparatus for deploying and/or using an API service of claim 5, wherein the rights acquisition module is further to:
and sending a client registration request to a registration server of the cloud service provider, acquiring a client authentication identifier corresponding to the deployment authority and/or the use authority after client registration authentication, and acquiring the deployment authority and/or the use authority through the client authentication identifier.
7. The apparatus for deploying and/or using an API service of claim 5, wherein the API service deploying and/or calling module is further to:
when the API service deployed on one available edge node cannot be accessed, deleting the API service information related to the API service in the available edge node, and deleting the API service information related to the API service in the rest available edge nodes containing the API service information of the API service; and/or
When the API service is deployed on a plurality of available edge nodes, one available edge node is selected as a parent node, the rest of the available edge nodes are managed through the parent node,
wherein the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in the first mode or the second mode.
8. A cloud services network that deploys and/or uses API services, comprising:
the client registration server is used for providing deployment authority and/or use authority for deploying the API service on the edge node of the cloud service provider and providing relevant information of the available edge node corresponding to the deployment authority and/or use authority;
an edge node for deploying and/or providing API services;
further comprising:
an apparatus for deploying and/or using an API service as claimed in any one of claims 5 to 7.
9. The cloud services network for deploying and/or using API services according to claim 8,
the client registration server is further configured to:
receiving a customer registration request from the device deploying and/or using the API service;
providing a client authentication identification corresponding to the deployment and/or usage rights after authenticating the client registration,
wherein, the client authentication identifier is used for identifying the deployment authority and/or the use authority.
10. The cloud services network for deploying and/or using API services as recited in claim 8, wherein said edge node is further configured to:
selecting one available edge node from one or more available edge nodes as a registration node for registering API service information for describing the API service; and
the registered node stores the uploaded API service resource in a designated storage space of the registered node and enables the API service, the unregistered nodes in the plurality of available edge nodes synchronize the API service information respectively and deploy the API service in a first mode, or all the nodes in the plurality of available edge nodes store the uploaded API service resource in a designated storage space of each registered node and enable the API service, and the unregistered nodes in the plurality of available edge nodes synchronize the API service information respectively and deploy the API service in a second mode; and/or
When the API service deployed on one available edge node cannot be accessed, the available edge node deletes the API service information related to the API service, and the other available edge nodes containing the API service information of the API service delete the API service information related to the API service; and/or
When the API service is deployed on multiple available edge nodes, one available edge node is selected as a parent node, the parent node manages the remaining available edge nodes,
wherein the designated storage space is an API service pool, and the API service information comprises at least one of the following items: the API service level is used for describing whether the API service is deployed in the first mode or the second mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811612192.6A CN111385318B (en) | 2018-12-27 | 2018-12-27 | Method and device for deploying and/or using API (application program interface) service and cloud service network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811612192.6A CN111385318B (en) | 2018-12-27 | 2018-12-27 | Method and device for deploying and/or using API (application program interface) service and cloud service network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111385318A CN111385318A (en) | 2020-07-07 |
| CN111385318B true CN111385318B (en) | 2022-11-08 |
Family
ID=71216366
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811612192.6A Active CN111385318B (en) | 2018-12-27 | 2018-12-27 | Method and device for deploying and/or using API (application program interface) service and cloud service network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111385318B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1510862A (en) * | 2002-12-26 | 2004-07-07 | 华为技术有限公司 | Identification and business management for network user |
| CN101102251A (en) * | 2006-07-07 | 2008-01-09 | 中兴通讯股份有限公司 | A method for deploying VLAN service in the whole network |
| CN101938483A (en) * | 2010-09-03 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for distributing live broadcast contents |
| CN102164158A (en) * | 2010-02-15 | 2011-08-24 | 株式会社日立制作所 | Network node, information processing system and method |
| US8484716B1 (en) * | 2009-08-07 | 2013-07-09 | Adobe Systems Incorporated | Hosting a server application on multiple network tiers |
| WO2017100640A1 (en) * | 2015-12-11 | 2017-06-15 | Interdigital Patent Holdings, Inc. | Method and apparatus for enabling third party edge clouds at the mobile edge |
| CN106998345A (en) * | 2016-01-26 | 2017-08-01 | 中兴通讯股份有限公司 | The processing method of business network, apparatus and system |
| CN107872823A (en) * | 2016-09-28 | 2018-04-03 | 维布络有限公司 | The method and system of communication operational mode in the mobile edge calculations environment of identification |
| CN108616578A (en) * | 2018-04-09 | 2018-10-02 | 上海点融信息科技有限责任公司 | Method for processing business, equipment and the computer readable storage medium of transregional piece of platform chain |
| CN108737271A (en) * | 2017-04-14 | 2018-11-02 | 华为技术有限公司 | A kind of packet routing method, apparatus and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7266541B2 (en) * | 2002-04-12 | 2007-09-04 | International Business Machines Corporation | Adaptive edge processing of application data |
-
2018
- 2018-12-27 CN CN201811612192.6A patent/CN111385318B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1510862A (en) * | 2002-12-26 | 2004-07-07 | 华为技术有限公司 | Identification and business management for network user |
| CN101102251A (en) * | 2006-07-07 | 2008-01-09 | 中兴通讯股份有限公司 | A method for deploying VLAN service in the whole network |
| US8484716B1 (en) * | 2009-08-07 | 2013-07-09 | Adobe Systems Incorporated | Hosting a server application on multiple network tiers |
| CN102164158A (en) * | 2010-02-15 | 2011-08-24 | 株式会社日立制作所 | Network node, information processing system and method |
| CN101938483A (en) * | 2010-09-03 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for distributing live broadcast contents |
| WO2017100640A1 (en) * | 2015-12-11 | 2017-06-15 | Interdigital Patent Holdings, Inc. | Method and apparatus for enabling third party edge clouds at the mobile edge |
| CN106998345A (en) * | 2016-01-26 | 2017-08-01 | 中兴通讯股份有限公司 | The processing method of business network, apparatus and system |
| CN107872823A (en) * | 2016-09-28 | 2018-04-03 | 维布络有限公司 | The method and system of communication operational mode in the mobile edge calculations environment of identification |
| CN108737271A (en) * | 2017-04-14 | 2018-11-02 | 华为技术有限公司 | A kind of packet routing method, apparatus and system |
| CN108616578A (en) * | 2018-04-09 | 2018-10-02 | 上海点融信息科技有限责任公司 | Method for processing business, equipment and the computer readable storage medium of transregional piece of platform chain |
Non-Patent Citations (4)
| Title |
|---|
| Evelina Pencheva，Ivaylo Atanasov，."An_Extension_of_Mobile_Edge_Computing_Bandwidth_Management_API".《2018 International Symposium on Networks, Computers and Communications (ISNCC)》.2018, * |
| LG Electronics等."Technical Report：3rd Generation Partnership Project * |
| Study on Common API Framework for 3GPP Northbound APIs".《3GPP TR 23.722 V0.2.0 (2017-05)》.2017, * |
| Technical Specification Group Services and System Aspects * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111385318A (en) | 2020-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11088903B2 (en) | Hybrid cloud network configuration management | |
| CN109391592B (en) | Method and equipment for discovering network function service | |
| CN107948135B (en) | Data processing method and device supporting multiple API protocols | |
| CA2824705C (en) | Communications network, computer architecture, computer-implemented method and computer program product for development and management of femtocell-based applications | |
| US11316923B2 (en) | Unstructured data storage function (UDSF) services | |
| US9430672B2 (en) | Stack fusion architecture including distributed software clusters to enable software communication services | |
| EP3298812B1 (en) | Loading of subscription profile into an embedded sim card | |
| CN107111510B (en) | Method and device for operating VNF packet | |
| CN113360862A (en) | Unified identity authentication system, method, electronic device and storage medium | |
| US20150135288A1 (en) | Messaging gateway | |
| CN113572689A (en) | Microservice gateway management method, system, device, readable storage medium and product | |
| CN113453213B (en) | Authentication data synchronization method and device | |
| US10367696B2 (en) | Automatic network management system and methods | |
| US11245577B2 (en) | Template-based onboarding of internet-connectible devices | |
| CN112532413A (en) | Business support Saas system, method, medium and device based on micro-service architecture | |
| US10547496B2 (en) | Automatic network management system and methods | |
| CN105871794A (en) | Distributed file system date storage method and system, client and server | |
| CN114281253A (en) | Storage volume management method | |
| CN113037761A (en) | Login request verification method and device, storage medium and electronic equipment | |
| EP3128715B1 (en) | Resource creation method and apparatus | |
| CN113489689B (en) | Authentication method and device for access request, storage medium and electronic equipment | |
| CN111385318B (en) | Method and device for deploying and/or using API (application program interface) service and cloud service network | |
| CN110809051B (en) | Service data processing method and system | |
| CN109344202B (en) | Data synchronization method and management node | |
| US10924575B2 (en) | Automatic network management system and methods |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |