CN110636115A - Cross-cloud service calling processing method, gateway server and requester server - Google Patents
Cross-cloud service calling processing method, gateway server and requester server Download PDFInfo
- Publication number
- CN110636115A CN110636115A CN201910808480.7A CN201910808480A CN110636115A CN 110636115 A CN110636115 A CN 110636115A CN 201910808480 A CN201910808480 A CN 201910808480A CN 110636115 A CN110636115 A CN 110636115A
- Authority
- CN
- China
- Prior art keywords
- service
- cloud gateway
- private cloud
- server
- registration
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- 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/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0209—Architectural arrangements, e.g. perimeter networks or demilitarized zones
- H04L63/0218—Distributed architectures, e.g. distributed firewalls
Abstract
The embodiment of the invention provides a processing method for cross-cloud service calling, a gateway server and a requester server, which can reduce the address information maintenance cost of each service provider in a distributed system comprising a public cloud and a private cloud to a certain extent. The method comprises the steps that a server requester acquires a target service identifier and a private cloud gateway address of a called target server from a registration center of a private cloud; thereby, a service calling request is sent to a private cloud gateway, so that the private cloud gateway forwards the service calling request to a public cloud gateway, and a service calling feedback message fed back by the public cloud gateway is forwarded to the server requester, wherein the service calling request comprises the target service identifier and a private cloud gateway address; the server requestor, in turn, receives the service invocation feedback message.
Description
[ technical field ] A method for producing a semiconductor device
The invention relates to the technical field of communication, in particular to a processing method for cross-cloud service calling, a gateway server and a requester server.
[ background of the invention ]
The cloud is a metaphor of a network and the internet, and means that a server of a provided service is in the cloud. Computer clouds can be classified into public clouds and private clouds according to different service properties. The public cloud is placed on the Internet and can be used by registered or paid users, but the public cloud can be used by registered or paid users at will, and the data security in the public cloud is not high. The private cloud is placed in a private environment, for example, an enterprise, a government, an organization and the like can construct the private cloud in a machine room of the enterprise, the private cloud is only used by personnel or branch institutions in the private environment.
However, compared with the public cloud, the private cloud has higher maintenance cost, is lack of resources, has low cloud computing processing speed, and the like, so when a service system is constructed, a distributed architecture is mostly adopted to deploy the service system, and when the private cloud resources are used, resources are also applied from the public cloud to deploy the service system.
In a distributed architecture system spanning a public cloud and a private cloud, when some business services are realized, the private cloud needs to call some services in the public cloud. In the prior art, the private cloud calls the public cloud in such a way that each server of the private cloud is configured with address information of each service provider in the public cloud, so that when each service provider of the public cloud is called, the address information of each service provider in the public cloud is directly acquired, and the http protocol is adopted for direct calling. However, in the process of implementing the present invention, the inventor finds that each server deployed in the private cloud needs to separately configure address information of each service provider in the public cloud, and if the address information of each service provider in the public cloud changes, the address information of each service provider in the public cloud in each server in the private cloud needs to be reconfigured, so that the maintenance cost for the address information of each service provider in the public cloud is high.
[ summary of the invention ]
In view of this, embodiments of the present invention provide a processing method for cross-cloud service invocation, a gateway server, and a requester server, which can reduce address information maintenance costs of service providers in a distributed system including a public cloud and a private cloud to a certain extent.
In a first aspect, an embodiment of the present invention provides a method for processing a cross-cloud service call, which is applied to a distributed system including a public cloud and a private cloud, and is executed in a service requester of the private cloud, where the method includes:
the server requester acquires a target service identifier and a private cloud gateway address of a called target service provider from a registration center of a private cloud;
the server requester sends a service calling request to a private cloud gateway, so that the private cloud gateway forwards the service calling request to a public cloud gateway, and forwards a service calling feedback message fed back by the public cloud gateway to the server requester, wherein the service calling request comprises the target service identifier and a private cloud gateway address;
the server requestor receives the service invocation feedback message.
The above-described aspect and any possible implementation manner further provide an implementation manner, where the server requester obtains a target service identifier of a called target service and a private cloud gateway address from a registry of a private cloud, including:
the server requester sends a service table query request to the registry so that the registry acquires and sends a service table, wherein the service table comprises service identifications and private cloud gateway addresses of all the servers;
the server requester receives the service table;
the server requester acquires selection operation information for each service identifier, wherein the selection operation information is used for indicating a target service identifier of a called target service provider.
In a second aspect, an embodiment of the present invention provides a method for processing a cross-cloud service call, where the method includes:
the method comprises the steps that a private cloud gateway receives a service calling request sent by a server requester, wherein the server calling request comprises a target service identifier of a called target server and a private cloud gateway address;
the private cloud gateway forwards the service calling request to a public cloud gateway, so that the public cloud gateway queries a target interface address corresponding to the target service identifier from a service identifier and interface address mapping table of a pre-stored server, and forwards a service calling feedback message acquired through the target interface to the private cloud gateway;
and the private cloud gateway receives the service calling feedback message sent by the public cloud gateway and forwards the service calling feedback message to the service requester.
The above aspect and any possible implementation manner further provide an implementation manner, before the receiving the service invocation request sent by the server requestor, the method further includes:
the private cloud gateway acquires registration information in the public cloud gateway, wherein the registration information comprises service identifications of all service providers in the public cloud;
the private cloud gateway sends an agent registration request to the registry, wherein the agent registration request is used for indicating the registry to register the service identifier of each service person in the public cloud and the private cloud gateway address carried in the agent registration request and feeding back an agent registration feedback message;
and the private cloud gateway receives the proxy registration feedback message sent by the registration center.
The above-described aspect and any possible implementation manner further provide an implementation manner, where the acquiring, by the private cloud gateway, the registration information in the public cloud gateway, where the registration information includes service identifiers of each service provider in the public cloud includes:
the private cloud gateway sends a registration information query request to the public cloud gateway periodically, wherein the registration information query request is used for indicating to search for a service identifier to be registered of a service provider which is not registered in the public cloud;
and the private cloud gateway receives registration information fed back by the public cloud gateway, wherein the registration information comprises the service identifier to be registered.
The above-described aspect and any possible implementation manner further provide an implementation manner, when the proxy registration feedback message indicates that registration of the service identifier and/or the private cloud gateway address of each service provider in the public cloud fails, the method further includes:
and the private cloud gateway sends a proxy service registration request to the registration center again.
The above-described aspects and any possible implementations further provide an implementation in which, before the private cloud gateway resends the proxy service registration request to the registry, the method further includes:
the private cloud gateway adds 1 to the number of the proxy registration feedback messages which fail to record the registration to obtain the current number of records;
if the current record number exceeds a preset value, the private cloud gateway sends a maintenance notice;
and the step of sending the proxy service registration request to the registration center again by the private cloud gateway is executed under the condition that the current record number is determined not to exceed a preset value.
The above-described aspect and any possible implementation manner further provide an implementation manner, where after the private cloud gateway receives the proxy registration feedback message sent by the registry, the method further includes:
and the private cloud gateway forwards the proxy registration feedback message to the public cloud gateway.
In a third aspect, an embodiment of the present invention provides a requester server, including: at least one processor; and at least one memory communicatively coupled to the processor,
wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of the first aspects.
In a fourth aspect, an embodiment of the present invention provides a gateway server, including: at least one processor; and at least one memory communicatively coupled to the processor,
wherein: the memory stores program instructions executable by the processor, the processor being capable of performing the method of any of the second aspects when invoked by the processor.
In a fifth aspect, the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the method according to any one of the first aspect.
In a sixth aspect, the present invention provides a non-transitory computer readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the method according to any one of the second aspects.
According to the technical scheme provided by the invention, in combination with the detailed explanation of the technical scheme provided by the invention, the service requester in the private cloud obtains the target service identifier and the private cloud gateway address of the called server through the registration center in the private cloud, so that the service calling request is sent to the public cloud gateway through the private cloud gateway, and because the mapping relation table of the service identifier and the interface address of the server is stored in the public cloud gateway, when the public cloud gateway receives the service calling request, the calling of the server corresponding to the target service identifier can be realized on the basis of the relation table. Because the interface address of the server is stored in the public cloud gateway, the public cloud gateway manages the service identifier and the interface address of the server in a unified way, and the identifier of the server and the private cloud gateway address are stored in the registration center, when the interface address of the server is changed, only the interface address in the public cloud gateway needs to be maintained, and the interface address change operation of the server does not need to be carried out for each service requester, so that the maintenance cost of the gateway address of the public cloud is greatly reduced.
In addition, in the embodiment of the invention, the service requester in the private cloud sends the service calling request process to the server in the public cloud, the service requester does not directly send the service calling request to the public cloud gateway, but the service calling request is forwarded to the public cloud gateway through the private cloud gateway, that is, in the technical scheme provided by the invention, when the service is called across the private cloud and the public cloud, only the private cloud gateway and the public cloud gateway are interacted, therefore, even when a plurality of service requesters need to call a plurality of service requesters across the private cloud and the public cloud, the firewall between the private cloud gateway and the public cloud gateway is opened without opening the firewall between each service requester and the public cloud gateway, therefore, the number of opening the firewall is reduced, and convenience of calling the service operation of the public cloud by the service requester in the private cloud is improved.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for processing a cross-cloud service call according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of another cross-cloud service call processing method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a method flow for a service requester side provided by an embodiment of the present invention;
fig. 4 is a schematic diagram of a method flow for a private cloud gateway side according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a method flow for a public cloud gateway side according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a processing apparatus for cross-cloud service invocation according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another cross-cloud service call processing apparatus according to an embodiment of the present invention;
FIG. 8 is a block diagram of a requester server according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a gateway server according to an embodiment of the present invention.
[ detailed description ] embodiments
For better understanding of the technical solutions of the present invention, the following detailed descriptions of the embodiments of the present invention are provided with reference to the accompanying drawings.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. 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.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
Aiming at the problem that in the prior art, the maintenance cost is high because each server in the private cloud is independently configured with the address information of the public cloud, the embodiment of the invention provides a corresponding solution: the service identification and the interface address mapping table of each service person in the public cloud are stored in the public cloud gateway, and the service identification and the private cloud gateway address of the service person in the public cloud are registered in the registration center of the private cloud in the process of registering the service person in the public cloud in the registration center of the private cloud, so that the private cloud can communicate with the public cloud gateway through the private cloud gateway address and the service identification when calling the service person in the public cloud, and the interface address is determined by using the service identification and the interface address mapping table stored in the public cloud gateway, and service calling is realized.
Under the guidance of the above idea, the embodiment of the present invention provides a processing method for cross-cloud service invocation.
Please refer to fig. 1, which is a flowchart illustrating a cross-cloud service invocation method according to an embodiment of the present invention. The method is applied to a distributed system comprising a public cloud and a private cloud.
In the embodiment of the invention, at least one server and a public cloud gateway are deployed in a public cloud of the distributed system; at least one service requester, a registry and a private cloud gateway are deployed in the private cloud.
The service provider in the public cloud is used for providing service for the service requester; the public cloud gateway is used for realizing interaction between the public cloud and devices (such as private cloud) outside the public cloud, and a mapping relation table of service identification and interface address of a service person in the public cloud is prestored in the public cloud gateway.
The service requester in the private cloud is used for calling the service provided by the service provider in the distributed system; the registration center is mainly used for registering and managing services; the private cloud gateway is used for realizing communication connection between private clouds and the outside, and in the distributed system architecture provided by the invention, the private cloud gateway is also used for realizing proxy registration.
Based on the distributed system, the overall interaction flow related to the method for cross-cloud service invocation provided by the invention is as shown in fig. 1, and the method comprises the following steps:
102, the server requester acquires a target service identification of the called target service provider and a private cloud gateway address from a registry of a private cloud.
In the embodiment of the invention, the service identifiers corresponding to all the servers in the public cloud and the private cloud gateway addresses in the private cloud are prestored in the registry, the server requester sends the query request through the registry of the private cloud, and the registry is triggered to send the prestored all the service identifiers and the private cloud gateway addresses to the service requester, so that the service requester can obtain the target service identifiers and the private cloud gateway addresses.
In a possible specific implementation manner, each service identifier and the private cloud gateway address stored in the registry may be stored in the form of a service table. When the service requester obtains the target service identifier of the called target service provider and the private cloud gateway address, the following operations may be specifically performed: the service requester sends a service table query request to the registry to trigger the registry to call the service table, and sends the service table to the service requester, so that the service requester receives the service table and displays the service table to a user through a display screen, the user can operate the service table through external input equipment such as a touch screen or a keyboard, a service identifier corresponding to a service person to be called is selected from the service table according to self requirements, the service requester collects selection operation information of the user aiming at each service identifier in the service table, the selection operation information is used for indicating a target service identifier of a called target service person, and the service requester obtains the target service identifier through analyzing the selection operation information.
The server requestor sends a service invocation request to the private cloud gateway 104. Wherein, the service call request includes: the target service identification of the called target service person and the private cloud gateway address.
And 106, the private cloud gateway forwards the service calling request to the public cloud gateway, so that the public cloud gateway queries a target interface address corresponding to the target service identifier from a mapping table of the service identifier and the interface address of the pre-stored service provider, and forwards the service calling feedback message acquired through the target interface to the private cloud gateway.
In the embodiment of the invention, a mapping relation table between the service identification and the interface address of each service provider in the public cloud is stored in the public cloud gateway in advance. The service calling request is forwarded to the public cloud gateway at the private cloud gateway, and after the public cloud gateway successfully receives the service calling request, the public cloud gateway analyzes the service calling request to obtain a target service identifier from the service calling request, then the public cloud gateway matches the obtained target service identifier with a service identifier in a mapping relation table between the service identifier and an interface address stored in the public cloud gateway, determines the interface address corresponding to the service identifier matched with the target service identifier as the target interface address, so that a server corresponding to the target service identifier is accessed by using the interface address, and obtains a service calling feedback message fed back by the server corresponding to the target service identifier through the target interface, and then sends the service calling feedback message to the private cloud gateway.
And 108, the private cloud gateway receives the service calling feedback message forwarded by the public cloud gateway and forwards the service calling feedback message to the service requester.
Optionally, with the implementation process, before the service requester in the private cloud obtains the service identifier and the private cloud gateway address from the registry, the identifier and the private cloud gateway address of each service requester in the public cloud need to be stored in the registry, so that the service requester can obtain the service identifier. The identification and the private cloud gateway address of each service person can be recorded into the registry by a developer through an external input device connected with the registry; or, a communication connection between the private cloud gateway and the registry can be established, and the private cloud gateway registers the identifier of each service provider and the private cloud gateway address to the registry in a registration mode.
The invention provides a feasible implementation way aiming at the realization that the identification and the private cloud gateway address of each service provider are stored in a registration center in a registration way, the flow chart is shown in figure 2, and the method also comprises the following steps:
and 201, the private cloud gateway acquires registration information in the public cloud gateway, wherein the registration information comprises service identifications of all service providers in the public cloud.
In the embodiment of the present invention, the registration information may be that after the private cloud gateway establishes a communication connection with the public cloud gateway, the private cloud gateway and the public cloud gateway perform information interaction, and the public cloud gateway transmits the registration information to the private cloud gateway. Specifically, before the private cloud gateway acquires the registration information in the public cloud, the public cloud gateway acquires the registration information, wherein the registration information comprises service identifiers of all service providers in the public cloud; and sending the registration information to a private cloud gateway; and the private cloud receives the registration information sent by the public cloud gateway to acquire the registration information in the public cloud.
For triggering the public cloud gateway to acquire the registration information, the following two triggering mechanisms are further provided. The first trigger mechanism is: when a service identifier is newly added in the public cloud gateway, the public cloud gateway immediately and actively bears the newly added service identifier in the registration information and sends the registration information to the private cloud gateway; the second trigger mechanism is: and the private cloud gateway sends a registration information query request to the public cloud gateway, so that the public cloud gateway is triggered to passively bear the service identifier in the registration information and send the registration information to the private cloud gateway.
In one possible implementation, the implementation for the first trigger mechanism may be: the public cloud gateway inquires the mapping relation between the service identification and the interface address stored in the public cloud gateway in real time, whether the number of the service identifications and/or the number of the interface addresses change or not is judged, if the number of the service identifications or the number of the interface addresses are increased, the public cloud gateway obtains the newly added service identification and generates registration information, and therefore the newly added service identification is sent to the private cloud gateway through the registration information to achieve registration; and if the number of the service identifications or the number of the interface addresses is determined to be increased, the public cloud gateway continuously monitors whether the number of the service identifications and/or the number of the interface addresses in the mapping relation table stored by the public cloud gateway are changed.
In one possible implementation, the implementation for the second trigger mechanism may be: the private cloud gateway sends a registration information query request to the public cloud gateway periodically, wherein the registration information query request is used for indicating to search the service identifier to be registered of the unregistered service provider in the public cloud; therefore, after receiving the registration information query request, the public cloud gateway queries the service identifier to be registered of the unregistered service provider in the public cloud; if the public cloud gateway finds the unregistered service identifier to be registered, registration information is generated and fed back to the private cloud gateway, and then the private cloud gateway registers the service identifier to be registered according to the received registration information; and if the service identifier to be registered is not found by the public cloud gateway, generating prompt information without registration, and feeding the prompt information back to the private cloud gateway.
Illustratively, the registered service identifier is carried in the registration information query request sent by the private cloud gateway to the public cloud gateway, so that when the public cloud gateway searches for the unregistered to-be-registered service identifier, the registered service identifier in the registration information query request is matched with the service identifier of the server stored by the public cloud gateway, and the service identifier which is not matched with the registered service identifier in the service identifier stored by the public cloud gateway is determined as the to-be-registered service identifier.
For example, after the service identifier in the public cloud gateway is registered in the registry of the private cloud, the public cloud gateway may mark the registered service identifier, so that when the public cloud gateway searches for an unregistered service identifier to be registered, the public cloud gateway checks whether the service identifier stored in the public cloud gateway has a registration mark, and determines the service identifier without the registration mark as the service identifier to be registered.
In the embodiment of the present invention, the registration information may also be obtained offline by a developer, and then the obtained registration information is configured to the configuration file of the private cloud gateway by using an input device, so that the private cloud gateway can directly read the configuration file of the private cloud gateway to obtain the registration information.
202, the private cloud gateway sends an agent registration request to a registry in the private cloud, where the agent registration request is used to instruct the registry to register the service identifiers of the service providers in the public cloud and the private cloud gateway address carried in the agent registration request, and feeds back an agent registration feedback message.
And 203, registering the registration information and the private cloud gateway address by the registry, and sending a proxy registration feedback message to the private cloud gateway.
In the embodiment of the invention, the registration feedback message carries indication information for indicating whether the private cloud gateway address and the service identifier of each service provider in the public cloud are successfully registered. If the indication information carried in the registration feedback message is successful in registration, determining that the private cloud gateway address and the service identifier of each service provider in the public cloud are stored in a registration center; and if the indication information carried in the registration feedback message is registration failure, retransmitting the proxy registration request.
204, the private cloud gateway receives the proxy registration feedback message sent by the registry in the private cloud.
In the embodiment of the invention, the registration feedback message carries indication information for indicating whether the private cloud gateway address and the service identifier of each service provider in the public cloud are successfully registered. If the indication information carried in the registration feedback message is successful in registration, determining that the private cloud gateway address and the service identifier of each service provider in the public cloud are stored in a registration center; if the indication information carried in the registration feedback message is registration failure, in order to ensure that the service requester in the subsequent private cloud can successfully call the service requester, the service requester is triggered to resend the proxy registration request.
In one possible embodiment, when a device such as the registry and/or the private cloud gateway fails to register, the private cloud gateway always sends a proxy registration request to the registry. In order to avoid occupation of running resources of devices such as the private cloud gateway and the registration center when the situation occurs, in the embodiment, before the private cloud gateway triggers the private cloud gateway to resend the proxy registration request, the private cloud gateway counts the number of indication information of registration failure, and if the number of indication information of registration failure is not greater than a preset value, the private cloud gateway is triggered to resend the proxy registration request; and if not, the private cloud gateway sends a maintenance notice to a system administrator to remind the system administrator to maintain the system, and meanwhile, the counted number of the indication information receiving the registration failure is reset. The private cloud gateway sends a maintenance notification to a system administrator in the form of an email, a short message or a WeChat.
In the embodiment of the present invention, in order to facilitate the public cloud gateway to know which servers of the servers deployed in the public cloud have been registered in the private cloud registry and which have not yet been registered, after receiving the proxy registration feedback message, the private cloud gateway needs to forward the proxy registration feedback message to the public cloud gateway, so that the public cloud gateway marks the service identifier to be registered according to the proxy registration feedback message.
In a specific feasible embodiment, in order to reduce information interaction between the private cloud gateway and the public cloud gateway as much as possible on the premise of not affecting the public cloud gateway to acquire the registered service identifier, the private cloud gateway only sends the carried indication information as an agent registration feedback message for successful registration to the public cloud gateway.
By combining the detailed explanation of the technical scheme provided by the invention, the service requester in the private cloud obtains the target service identifier and the private cloud gateway address of the called server through the registration center in the private cloud, so that the service calling request is sent to the public cloud gateway through the private cloud gateway, and because the mapping relation table of the service identifier and the interface address of the server is stored in the public cloud gateway, when the public cloud gateway receives the service calling request, the calling of the server corresponding to the target service identifier can be realized based on the relation table. Because the interface address of the server is stored in the public cloud gateway, the public cloud gateway manages the service identifier and the interface address of the server in a unified way, and the identifier of the server and the private cloud gateway address are stored in the registration center, when the interface address of the server is changed, only the interface address in the public cloud gateway needs to be maintained, and the interface address change operation of the server does not need to be carried out for each service requester, so that the maintenance cost of the gateway address of the public cloud is greatly reduced.
In addition, in the embodiment of the invention, the service requester in the private cloud sends the service calling request process to the server in the public cloud, the service requester does not directly send the service calling request to the public cloud gateway, but the service calling request is forwarded to the public cloud gateway through the private cloud gateway, that is, in the technical scheme provided by the invention, when the service is called across the private cloud and the public cloud, only the private cloud gateway and the public cloud gateway are interacted, therefore, even when a plurality of service requesters need to call a plurality of service requesters across the private cloud and the public cloud, the firewall between the private cloud gateway and the public cloud gateway is opened without opening the firewall between each service requester and the public cloud gateway, therefore, the number of opening the firewall is reduced, and convenience of calling the service operation of the public cloud by the service requester in the private cloud is improved.
Based on the above general flow, in cooperation with the above private cloud gateway side, the present embodiment further provides a method flow for the service requester side in the private cloud, as shown in fig. 3, including:
301, a private cloud gateway address and a target service identity of the called server are obtained from a registry of the private cloud.
The method specifically comprises the following steps: the server requester sends a service table query request to the registry so that the registry acquires and sends a service table, wherein the service table comprises service identifications and private cloud gateway addresses of all the servers; then, the server requester receives the service table; therefore, the server requester obtains the selection operation information for each service identifier in the service table, wherein the selection operation information is used for indicating the target service identifier of the called target service provider.
303, the server requester sends a service call request to the private cloud gateway, so that the private cloud gateway forwards the service call request to the public cloud gateway, and forwards a service call feedback message fed back by the public cloud gateway to the server requester, where the service call request includes a target service identifier and a private cloud gateway address.
The server requestor receives 304 a service invocation feedback message.
Since the present embodiment is based on the execution method of the service requester side in the above general flow, reference may be made to the related description in the general flow in the present embodiment for a part not described in detail.
Based on the foregoing general flow, the embodiment of the present invention further provides an overall method flow for the private cloud gateway side, as shown in fig. 4, including:
401, obtaining registration information in the public cloud gateway, where the registration information includes service identifiers of each service provider in the public cloud.
The public cloud gateway stores a mapping relation table of service identification and interface address of a service provider.
For the implementation of step 401, an embodiment of the present invention provides a feasible implementation manner, which specifically includes: regularly sending a registration information query request to a public cloud gateway, wherein the registration information query request is used for indicating to search for a service identifier to be registered of a service provider which is not registered in a public cloud; and receiving registration information fed back by the public cloud gateway, wherein the registration information comprises a service identifier to be registered.
And 402, sending a proxy registration request to a registry in the private cloud, wherein the proxy registration request comprises registration information and a private cloud gateway address.
And 403, acquiring an agent registration feedback message sent by a registration center in the private cloud.
Wherein, the proxy registration feedback message is used to indicate whether the registration of the registered service identifier is successful.
In a possible implementation manner, in order to make the public cloud gateway aware of the registration condition, after performing step 403, the private cloud gateway may further perform: and sending the proxy registration feedback message to the public cloud gateway.
404, obtaining a service invocation request sent by a service requester in the private cloud, where the service invocation request includes: the target service identification of the called target service person and the private cloud gateway address.
And 405, sending a service calling request to the public cloud gateway.
And 406, receiving the service call feedback message sent by the public cloud gateway, and forwarding the service call feedback message to the service requester.
Since the present embodiment is based on the execution method of the private gateway in the above general flow, reference may be made to the related description in the general flow in the present embodiment for a part not described in detail.
Based on the above general flow, in cooperation with the above private cloud gateway side, the embodiment of this scheme further provides a method flow for the public cloud gateway side, as shown in fig. 5, including:
the public cloud gateway stores a mapping relation table of service identification and interface address of a service provider.
As shown in fig. 5, the method includes:
501, obtaining registration information, where the registration information includes service identifiers of each server in the public cloud.
For the implementation of step 501, a feasible implementation manner is provided in the embodiment of the present invention, which specifically includes: firstly, the public cloud gateway receives a registration information query request sent by a private cloud gateway, wherein the registration information query request is used for indicating to-be-registered service identification of a service person which is not registered in the public cloud to be searched; therefore, the service identification to be registered of the unregistered service provider in the public cloud is inquired; and generates registration information according to the service identifier to be registered, and then executes step 402 after generating the registration information.
502, the registration information is sent to the private cloud gateway.
In the embodiment of the present invention, optionally, after the step 402 is executed by the public cloud gateway, the following steps are further executed: and receiving an agent registration feedback message sent by the private cloud gateway. Wherein, the proxy registration feedback message is used to indicate whether the registration of the registered service identifier is successful.
And 503, receiving a service calling request sent by the private cloud gateway, where the service calling request includes a target service identifier of a called target server and a private cloud gateway address.
And 504, searching a target interface address corresponding to the target service identification from the service identification and interface address mapping relation table of the server.
And 505, sending a service calling request to the called target server according to the target interface address.
And 506, receiving a service calling feedback message fed back by the called target server, and sending the service calling feedback message to the private cloud gateway.
Since the present embodiment is based on the execution method of the public gateway in the above general flow, reference may be made to the related description in the general flow in the present embodiment for a part not described in detail.
Based on the processing method for cross-cloud service invocation provided by the embodiment, the embodiment of the invention further provides an embodiment of a device for realizing the steps and the method in the embodiment of the method.
Please refer to fig. 6, which is a functional block diagram of a cross-cloud service call processing apparatus according to an embodiment of the present invention. As shown in fig. 6, the apparatus is provided in a service requester, and includes: an acquisition unit 61, a transmission unit 62 and a reception unit 63. The acquiring unit 61 is configured to acquire a target service identifier of a called target service provider and a private cloud gateway address from a registry of a private cloud; the sending unit 62 is configured to send a service calling request to the private cloud gateway, so that the private cloud gateway forwards the service calling request to the public cloud gateway, and forwards a service calling feedback message fed back by the public cloud gateway to the server requester, where the service calling request includes a target service identifier and a private cloud gateway address; a receiving unit 63, configured to receive the service invocation feedback message.
In this embodiment of the present invention, optionally, the obtaining unit 61 is configured to obtain the target service identifier of the called target service provider and the private cloud gateway address from the registry of the private cloud, and specifically perform: sending a service table query request to a registry so that the registry acquires and sends a service table, wherein the service table comprises service identifications and private cloud gateway addresses of all service providers; and, receiving a service table; and acquiring selection operation information aiming at each service identifier in the service table, wherein the selection operation information is used for indicating the target service identifier of the called target service provider.
Since each unit in the present embodiment can execute the method shown in fig. 3, reference may be made to the related description of fig. 3 for a part of the present embodiment that is not described in detail.
Fig. 7 is a functional block diagram of another cross-cloud service call processing apparatus according to an embodiment of the present invention. As shown in the figure, the apparatus is disposed in a private cloud gateway, and the apparatus includes: a receiving unit 71, a transmitting unit 72 and a processing unit 73. The receiving unit 71 is configured to receive a service invocation request sent by a server requester, where the server invocation request includes a target service identifier of a called target service provider and a private cloud gateway address; a sending unit 72, configured to forward the service call request to the public cloud gateway, so that the public cloud gateway queries a target interface address corresponding to the target service identifier from a mapping table of service identifiers and interface addresses of pre-stored servers, and forwards a service call feedback message obtained through the target interface to the private cloud gateway; and the processing unit 73 is configured to receive the service invocation feedback message sent by the public cloud gateway, and forward the service invocation feedback message to the service requester.
In this embodiment of the present invention, optionally, the processing unit 73 is further configured to obtain registration information in the public cloud gateway, where the registration information includes service identifiers of each service provider in the public cloud; sending an agent registration request to the registration center, wherein the agent registration request is used for indicating the registration center to register the service identification of each service person in the public cloud and the private cloud gateway address carried in the agent registration request, and feeding back an agent registration feedback message; and the proxy registration feedback message is used for receiving the proxy registration feedback message sent by the registration center.
In this embodiment of the present invention, optionally, the processing unit 73 is configured to acquire registration information in the public cloud gateway, where the registration information includes service identifiers of service providers in the public cloud, and specifically may perform the following operations: firstly, a registration information query request is sent to a public cloud gateway periodically, and the registration information query request is used for indicating to search a service identifier to be registered of a service provider which is not registered in a public cloud; and then, receiving registration information fed back by the public cloud gateway, wherein the registration information comprises a service identifier to be registered.
In this embodiment of the present invention, optionally, when the proxy registration feedback message indicates that the service identifier of each service provider in the public cloud and/or the private cloud gateway address fails to be registered, the processing unit 73 is further configured to send the proxy service registration request to the registry again.
In this embodiment of the present invention, optionally, before the processing unit 73 is further configured to send the proxy service registration request to the registry again, the processing unit 73 is further configured to add 1 to the number of proxy registration feedback messages in which registration recording fails by the private cloud gateway, so as to obtain a current number of records; if the current record number exceeds a preset value, the private cloud gateway sends a maintenance notice; and the step of sending the proxy service registration request to the registration center again by the private cloud gateway is executed under the condition that the current record number is determined not to exceed the preset value.
In this embodiment of the present invention, optionally, in order to facilitate the public cloud gateway to know whether the service identifier is successfully registered, the processing unit 73 may be further configured to forward the proxy registration feedback message to the public cloud gateway.
Since each unit in the present embodiment can execute the method shown in fig. 4, reference may be made to the related description of fig. 4 for a part of the present embodiment that is not described in detail.
The embodiment of the invention further provides a requester server for realizing the steps and the method in the embodiment of the method. Please refer to fig. 8, which is a block diagram illustrating a requester server according to an embodiment of the present invention. As shown in fig. 8, the requester server includes: at least one processor 81; and at least one memory 82 communicatively coupled to the processor 81. In fig. 8, a processor 81 and a memory 82 are taken as an example.
The electronic device may further include: a communication interface 83.
The processor 81, the memory 82 and the communication interface 83 may be connected by a communication bus 84 or in other ways, and fig. 8 illustrates the connection by the communication bus 84 as an example.
The memory 82 stores program instructions executable by the processor 81, and when the processor 81 calls the program instructions, the private cloud gateway executes the processing method called by the cross-cloud service.
In connection with the requester server shown in fig. 8, an embodiment of the present invention provides a non-transitory computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, causes the requester server to perform the method shown in fig. 3.
The embodiment of the invention further provides a gateway server for realizing the steps and the method in the embodiment of the method, wherein the gateway server is deployed in the private cloud. Please refer to fig. 9, which is a functional block diagram of a gateway server according to an embodiment of the present invention. As shown in fig. 9, the gateway server includes: at least one processor 91; and at least one memory 92 communicatively coupled to the processor 91. Fig. 9 illustrates an example of a processor 91 and a memory 92.
The electronic device may further include: a communication interface 93.
The processor 91, the memory 92, and the communication interface 93 may be connected by a communication bus 94 or other means, and fig. 9 illustrates an example in which these are connected by the communication bus 94.
The memory 92 stores program instructions executable by the processor 91, and when the processor 91 calls the program instructions, the public cloud gateway executes the processing method called by the cross-cloud service.
In connection with the gateway server shown in fig. 9, an embodiment of the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, causes the gateway server to execute the method shown in fig. 4.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a Processor (Processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method for processing a cross-cloud service call, the method comprising:
the server requester acquires a target service identifier and a private cloud gateway address of a called target service provider from a registration center of a private cloud;
the server requester sends a service calling request to a private cloud gateway, so that the private cloud gateway forwards the service calling request to a public cloud gateway, and forwards a service calling feedback message fed back by the public cloud gateway to the server requester, wherein the service calling request comprises the target service identifier and a private cloud gateway address;
the server requestor receives the service invocation feedback message.
2. The method of claim 1, wherein the server requester obtains the target service identifier of the called target service and the private cloud gateway address from a registry of the private cloud, comprising:
the server requester sends a service table query request to the registry so that the registry acquires and sends a service table, wherein the service table comprises service identifications and private cloud gateway addresses of all the servers;
the server requester receives the service table;
the server requester acquires selection operation information aiming at each service identifier in the service table, wherein the selection operation information is used for indicating a target service identifier of a called target server.
3. A method for processing a cross-cloud service call, the method comprising:
the method comprises the steps that a private cloud gateway receives a service calling request sent by a server requester, wherein the server calling request comprises a target service identifier of a called target server and a private cloud gateway address;
the private cloud gateway forwards the service calling request to a public cloud gateway, so that the public cloud gateway queries a target interface address corresponding to the target service identifier from a service identifier and interface address mapping table of a pre-stored server, and forwards a service calling feedback message acquired through the target interface to the private cloud gateway;
and the private cloud gateway receives the service calling feedback message sent by the public cloud gateway and forwards the service calling feedback message to the service requester.
4. The method of claim 3, wherein prior to receiving the service invocation request sent by the server requestor, the method further comprises:
the private cloud gateway acquires registration information in the public cloud gateway, wherein the registration information comprises service identifications of all service providers in the public cloud;
the private cloud gateway sends an agent registration request to the registry, wherein the agent registration request is used for indicating the registry to register the service identifier of each service person in the public cloud and the private cloud gateway address carried in the agent registration request and feeding back an agent registration feedback message;
and the private cloud gateway receives the proxy registration feedback message sent by the registration center.
5. The method of claim 4, wherein the private cloud gateway obtaining registration information in the public cloud gateway, the registration information including service identities of the servers in the public cloud comprises:
the private cloud gateway sends a registration information query request to the public cloud gateway periodically, wherein the registration information query request is used for indicating to search for a service identifier to be registered of a service provider which is not registered in the public cloud;
and the private cloud gateway receives registration information fed back by the public cloud gateway, wherein the registration information comprises the service identifier to be registered.
6. The method of claim 4, wherein when the proxy registration feedback message indicates that the registration of the service identity and/or the private cloud gateway address of each service provider in the public cloud fails, the method further comprises:
and the private cloud gateway sends a proxy service registration request to the registration center again.
7. The method of claim 4, wherein prior to the private cloud gateway resending the proxy service registration request to the registry, the method further comprises:
the private cloud gateway adds 1 to the number of the proxy registration feedback messages which fail to record the registration to obtain the current number of records;
if the current record number exceeds a preset value, the private cloud gateway sends a maintenance notice;
and the step of sending the proxy service registration request to the registration center again by the private cloud gateway is executed under the condition that the current record number is determined not to exceed a preset value.
8. The method according to any one of claims 4-7, wherein after the private cloud gateway receives the proxy registration feedback message sent by the registry, the method further comprises:
and the private cloud gateway forwards the proxy registration feedback message to the public cloud gateway.
9. A requestor server, comprising: at least one processor; and at least one memory communicatively coupled to the processor,
wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1 or 2.
10. A gateway server, comprising: at least one processor; and at least one memory communicatively coupled to the processor,
wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 3 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808480.7A CN110636115B (en) | 2019-08-29 | 2019-08-29 | Cross-cloud service calling processing method, gateway server and requester server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910808480.7A CN110636115B (en) | 2019-08-29 | 2019-08-29 | Cross-cloud service calling processing method, gateway server and requester server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110636115A true CN110636115A (en) | 2019-12-31 |
| CN110636115B CN110636115B (en) | 2022-07-29 |
Family
ID=68969555
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910808480.7A Active CN110636115B (en) | 2019-08-29 | 2019-08-29 | Cross-cloud service calling processing method, gateway server and requester server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110636115B (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110839087A (en) * | 2020-01-13 | 2020-02-25 | 北京懿医云科技有限公司 | Interface calling method and device, electronic equipment and computer readable storage medium |
| CN111355800A (en) * | 2020-02-28 | 2020-06-30 | 中国建设银行股份有限公司 | Service processing method, device, equipment and storage medium |
| CN112235400A (en) * | 2020-10-14 | 2021-01-15 | 腾讯科技（深圳）有限公司 | Communication method, communication system, communication apparatus, server, and storage medium |
| CN112468558A (en) * | 2020-11-16 | 2021-03-09 | 中科三清科技有限公司 | Request forwarding method, device, terminal and storage medium based on hybrid cloud |
| CN112866379A (en) * | 2021-01-15 | 2021-05-28 | 浪潮云信息技术股份公司 | Access method and device of microservice |
| CN112995273A (en) * | 2021-01-28 | 2021-06-18 | 腾讯科技（深圳）有限公司 | Network call-through scheme generation method and device, computer equipment and storage medium |
| CN113127411A (en) * | 2021-04-07 | 2021-07-16 | 华南理工大学 | Cross-cloud service application distributed data access system and method |
| CN113271362A (en) * | 2021-06-08 | 2021-08-17 | 天闻数媒科技（湖南）有限公司 | Education resource processing method, device, system and medium based on hybrid cloud |
| CN113472598A (en) * | 2021-08-31 | 2021-10-01 | 阿里云计算有限公司 | Cloud service method, electronic device, and computer-readable storage medium |
| CN113746928A (en) * | 2021-09-07 | 2021-12-03 | 中国银行股份有限公司 | Cross-cloud service calling method, device and system |
| CN113783969A (en) * | 2021-10-18 | 2021-12-10 | 广州新丝路信息科技有限公司 | Processing method based on gateway node forwarding request and related equipment |
| CN114155969A (en) * | 2021-11-16 | 2022-03-08 | 医渡云（北京）技术有限公司 | Medical data acquisition method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255933A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service medium, cloud computing method and cloud system |
| US20130060928A1 (en) * | 2010-05-20 | 2013-03-07 | Weixiang Shao | Cloud Service Publishing Method, Cloud Service Publishing Interface Message Packet and Cloud Service Broker |
| CN103701935A (en) * | 2014-01-13 | 2014-04-02 | 浪潮(北京)电子信息产业有限公司 | Construction method and system of cloud computing service platform |
| CN106209961A (en) * | 2016-04-22 | 2016-12-07 | 深圳市智物联网络有限公司 | Data processing method, publicly-owned Cloud Server and privately owned Cloud Server |
| CN106302117A (en) * | 2016-08-15 | 2017-01-04 | 上海云睦网络科技有限公司 | Message delivery system, method and apparatus |
| US20170099188A1 (en) * | 2015-10-06 | 2017-04-06 | Cisco Technology, Inc. | Policy-driven switch overlay bypass in a hybrid cloud network environment |
| US20170339070A1 (en) * | 2016-05-23 | 2017-11-23 | Cisco Technology, Inc. | Inter-cloud broker for hybrid cloud networks |
| CN109889621A (en) * | 2019-01-18 | 2019-06-14 | 北京百度网讯科技有限公司 | The configuration method and device of virtual private cloud service |
-
2019
- 2019-08-29 CN CN201910808480.7A patent/CN110636115B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255933A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service medium, cloud computing method and cloud system |
| US20130060928A1 (en) * | 2010-05-20 | 2013-03-07 | Weixiang Shao | Cloud Service Publishing Method, Cloud Service Publishing Interface Message Packet and Cloud Service Broker |
| CN103701935A (en) * | 2014-01-13 | 2014-04-02 | 浪潮(北京)电子信息产业有限公司 | Construction method and system of cloud computing service platform |
| US20170099188A1 (en) * | 2015-10-06 | 2017-04-06 | Cisco Technology, Inc. | Policy-driven switch overlay bypass in a hybrid cloud network environment |
| CN106209961A (en) * | 2016-04-22 | 2016-12-07 | 深圳市智物联网络有限公司 | Data processing method, publicly-owned Cloud Server and privately owned Cloud Server |
| US20170339070A1 (en) * | 2016-05-23 | 2017-11-23 | Cisco Technology, Inc. | Inter-cloud broker for hybrid cloud networks |
| CN106302117A (en) * | 2016-08-15 | 2017-01-04 | 上海云睦网络科技有限公司 | Message delivery system, method and apparatus |
| CN109889621A (en) * | 2019-01-18 | 2019-06-14 | 北京百度网讯科技有限公司 | The configuration method and device of virtual private cloud service |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110839087A (en) * | 2020-01-13 | 2020-02-25 | 北京懿医云科技有限公司 | Interface calling method and device, electronic equipment and computer readable storage medium |
| CN110839087B (en) * | 2020-01-13 | 2020-06-19 | 北京懿医云科技有限公司 | Interface calling method and device, electronic equipment and computer readable storage medium |
| CN111355800A (en) * | 2020-02-28 | 2020-06-30 | 中国建设银行股份有限公司 | Service processing method, device, equipment and storage medium |
| CN112235400A (en) * | 2020-10-14 | 2021-01-15 | 腾讯科技（深圳）有限公司 | Communication method, communication system, communication apparatus, server, and storage medium |
| CN112235400B (en) * | 2020-10-14 | 2024-02-02 | 腾讯科技（深圳）有限公司 | Communication method, communication system, communication device, server, and storage medium |
| CN112468558A (en) * | 2020-11-16 | 2021-03-09 | 中科三清科技有限公司 | Request forwarding method, device, terminal and storage medium based on hybrid cloud |
| CN112866379A (en) * | 2021-01-15 | 2021-05-28 | 浪潮云信息技术股份公司 | Access method and device of microservice |
| CN112995273B (en) * | 2021-01-28 | 2022-03-04 | 腾讯科技（深圳）有限公司 | Network call-through scheme generation method and device, computer equipment and storage medium |
| CN112995273A (en) * | 2021-01-28 | 2021-06-18 | 腾讯科技（深圳）有限公司 | Network call-through scheme generation method and device, computer equipment and storage medium |
| CN113127411A (en) * | 2021-04-07 | 2021-07-16 | 华南理工大学 | Cross-cloud service application distributed data access system and method |
| CN113271362A (en) * | 2021-06-08 | 2021-08-17 | 天闻数媒科技（湖南）有限公司 | Education resource processing method, device, system and medium based on hybrid cloud |
| CN113472598A (en) * | 2021-08-31 | 2021-10-01 | 阿里云计算有限公司 | Cloud service method, electronic device, and computer-readable storage medium |
| WO2023029974A1 (en) * | 2021-08-31 | 2023-03-09 | 阿里云计算有限公司 | Cloud service method, and electronic device and computer-readable storage medium |
| CN113746928A (en) * | 2021-09-07 | 2021-12-03 | 中国银行股份有限公司 | Cross-cloud service calling method, device and system |
| CN113746928B (en) * | 2021-09-07 | 2023-01-24 | 中国银行股份有限公司 | Cross-cloud service calling method, device and system |
| CN113783969A (en) * | 2021-10-18 | 2021-12-10 | 广州新丝路信息科技有限公司 | Processing method based on gateway node forwarding request and related equipment |
| CN114155969A (en) * | 2021-11-16 | 2022-03-08 | 医渡云（北京）技术有限公司 | Medical data acquisition method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110636115B (en) | 2022-07-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110636115B (en) | Cross-cloud service calling processing method, gateway server and requester server | |
| CN109618005B (en) | Method for calling server and proxy server | |
| US11012459B2 (en) | Rule-based network-threat detection | |
| US10187459B2 (en) | Distributed load balancing system, health check method, and service node | |
| US9774697B2 (en) | Method, apparatus, and system for pushing notification | |
| US9648033B2 (en) | System for detecting the presence of rogue domain name service providers through passive monitoring | |
| CN110602270B (en) | Domain name resolution method and device, computer equipment and storage medium | |
| US8386575B2 (en) | Method of realizing uniqueness assurance and method of determining message destination | |
| WO2021004528A1 (en) | Method, device and apparatus for address acquisition of application example and storage medium | |
| US20070165615A1 (en) | Apparatus and method for notifying communication network event in application server capable of supporting open API based on Web services | |
| US10069941B2 (en) | Scalable event-based notifications | |
| CN109246078B (en) | Data interaction method and server | |
| CN112152828B (en) | Game acceleration method and device, VPN terminal and storage medium | |
| CN109286684B (en) | Communication connection processing method and device, proxy server and storage medium | |
| US20210112025A1 (en) | Method and server for processing messages | |
| EP2381630B1 (en) | Monitoring a mobile data service associated with a mailbox | |
| CN110995890B (en) | Domain name request scheduling method and device | |
| CN114070624A (en) | Message monitoring method and device, electronic equipment and medium | |
| KR100798916B1 (en) | Method and system for handling the network events in application server using open API based web services | |
| CN110401686B (en) | WHOIS query method, device, equipment and storage medium thereof | |
| CN113923008B (en) | Malicious website interception method, device, equipment and storage medium | |
| CN110677417A (en) | Anti-crawler system and method | |
| US10313254B1 (en) | Network management interface for a network element with network-wide information | |
| US11902242B1 (en) | Nonexistant domain forwarding in authoritative zones | |
| WO2024057531A1 (en) | System, method, and medium for proactive monitoring of a network |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220524 Address after: 518000 China Aviation Center 2901, No. 1018, Huafu Road, Huahang community, Huaqiang North Street, Futian District, Shenzhen, Guangdong Province Applicant after: Shenzhen Ping An medical and Health Technology Service Co.,Ltd. Address before: Room 12G, Area H, 666 Beijing East Road, Huangpu District, Shanghai 200001 Applicant before: PING AN MEDICAL AND HEALTHCARE MANAGEMENT Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |