CN111552568A - Cloud service calling method and device - Google Patents
Cloud service calling method and device Download PDFInfo
- Publication number
- CN111552568A CN111552568A CN202010346973.6A CN202010346973A CN111552568A CN 111552568 A CN111552568 A CN 111552568A CN 202010346973 A CN202010346973 A CN 202010346973A CN 111552568 A CN111552568 A CN 111552568A
- Authority
- CN
- China
- Prior art keywords
- cloud service
- cloud
- service
- target
- platform
- 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
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000006243 chemical reaction Methods 0.000 claims description 22
- 230000002159 abnormal effect Effects 0.000 claims description 13
- 230000004044 response Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a cloud service calling method and device, wherein at least one cloud platform is associated in middleware equipment, and interface specifications and authentication rules of each cloud service in each cloud platform are configured in the middleware equipment. On this basis, when the application client needs to acquire the cloud service, the application client only needs to send a cloud service request to the middleware device, and the middleware device determines a target cloud platform capable of providing the target cloud service for the application client from at least one associated cloud platform based on the target cloud service requested by the cloud service request and a corresponding service request parameter set, and constructs a cloud service request capable of calling the target cloud service in the target cloud platform.
Description
Technical Field
The application relates to the technical field of cloud, in particular to a cloud service calling method and device.
Background
Cloud services refer to services provided for enterprises based on cloud computing. On the premise that the cloud platform provides certain cloud service, if the application needs to obtain the cloud service, the cloud service can be requested from the cloud platform through the application client.
With the continuous development of cloud technologies, the number of cloud platforms capable of providing cloud services is increasing, and the types of cloud services provided by different cloud platforms are different. In many cases, an application may need to obtain cloud services from different cloud platforms. However, the calling rules of cloud services of different cloud platforms are greatly different, and therefore, when an application needs to add a new calling requirement of a cloud service (for example, the application needs to change the calling of the cloud service M from the cloud platform 1 to the calling of the cloud service M from the cloud platform 2, or the application cannot call a cloud service of a certain cloud service originally, but now wants to be able to call a cloud service of a certain cloud platform of a cloud server of the cloud platform, etc.), some complex operations such as information configuration, code change, etc. need to be performed on the application, and thus the complexity of the application for obtaining the cloud service is high.
Disclosure of Invention
The application aims to provide a cloud service calling method and device so as to reduce the complex configuration and modification required by an application to obtain a cloud service and reduce the complexity of the application to obtain the cloud service.
In order to achieve the purpose, the application provides the following technical scheme:
in one aspect, the present application provides a cloud service invoking method, which is applied to a middleware device, where the middleware device is associated with at least one cloud platform, and the method includes:
receiving a first cloud service request sent by an application client;
analyzing a cloud service identifier and a service request parameter set in the first cloud service request, wherein the cloud service identifier is used for identifying a target cloud service requested to be called by the application client; the service request parameter set comprises at least one parameter required for executing the target cloud service;
if the target cloud service belongs to the cloud services available by the at least one cloud platform, determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform;
according to a first interface specification of the target cloud service in the target cloud platform, performing format conversion on at least one parameter in the service request parameter set to obtain a service request parameter set conforming to the first interface specification;
obtaining identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment;
according to an authentication rule corresponding to the target cloud service in the target cloud platform, constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information and the service request parameter set which accords with the first interface specification and the cloud service identifier;
and sending the second cloud service request to the target cloud platform.
Preferably, the method further comprises the following steps:
receiving a cloud service result returned by the target cloud platform, wherein the cloud service result is a calling result of the target cloud service returned by the target cloud platform in response to the second cloud service request;
according to a second interface specification between the middleware equipment and the application, carrying out format conversion on the cloud service result to obtain a cloud service result which accords with the second interface specification;
and returning the cloud service result which accords with the second interface specification to the application client.
Preferably, the constructing, according to an authentication rule corresponding to the target cloud service in the target cloud platform, a second cloud service request which conforms to the authentication rule and carries the identity authentication information, the service request parameter set conforming to the first interface specification, and the cloud service identifier includes:
calling and operating a pre-configured authentication packaging program corresponding to the target cloud service in the target cloud platform;
and constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier according to a set authentication rule by the authentication packaging program.
Preferably, the target cloud service belongs to cloud services available by the at least one cloud platform, and includes:
the target cloud service belongs to the cloud services of the at least one cloud platform and belongs to the cloud services in the normal service state in the at least one cloud platform.
Preferably, the method further comprises the following steps:
if the target cloud service does not belong to the cloud services of the at least one cloud platform, returning a service absence prompt to the application client, wherein the service absence prompt cannot call the target cloud service through the middleware equipment;
if the target cloud service belongs to the cloud service in the abnormal service state in the at least one cloud platform, returning a service fault alarm to the application client, wherein the service fault alarm is used for prompting that the target cloud service is in the abnormal service state.
Preferably, the determining, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client includes:
determining at least one cloud platform capable of providing the target cloud service from the at least one cloud platform;
and determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform capable of providing the target cloud service according to the respective load condition of the at least one cloud platform capable of providing the target cloud service.
In another aspect, the present application further provides a cloud service invoking device, which is applied to a middleware device, where the middleware device is associated with at least one cloud platform, and the cloud service invoking device includes:
the request receiving unit is used for receiving a first cloud service request sent by an application client;
the request analysis unit is used for analyzing a cloud service identifier and a service request parameter set in the first cloud service request, wherein the cloud service identifier is used for identifying a target cloud service requested to be called by the application client; the service request parameter set comprises at least one parameter required for executing the target cloud service;
a platform determination unit, configured to determine, if the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform, a target cloud platform from the at least one cloud platform for providing the target cloud service for the application client;
the parameter conversion unit is used for carrying out format conversion on at least one parameter in the service request parameter set according to a first interface specification of the target cloud service in the target cloud platform to obtain a service request parameter set conforming to the first interface specification;
an information obtaining unit, configured to obtain identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware device;
the request reconstruction unit is used for constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information, the service request parameter set which accords with the first interface specification and the cloud service identifier according to the authentication rule corresponding to the target cloud service in the target cloud platform;
a request sending unit, configured to send the second cloud service request to the target cloud platform.
Preferably, the method further comprises the following steps:
a result receiving unit, configured to receive a cloud service result returned by the target cloud platform, where the cloud service result is a call result of the target cloud service returned by the target cloud platform in response to the second cloud service request;
the result conversion unit is used for carrying out format conversion on the cloud service result according to a second interface specification between the middleware equipment and the application to obtain a cloud service result which accords with the second interface specification;
and the result returning unit is used for returning the cloud service result which accords with the second interface specification to the application client.
Preferably, the request reconstructing unit includes:
the program calling subunit is used for calling and operating a pre-configured authentication packaging program corresponding to the target cloud service in the target cloud platform;
and the request reconstruction subunit is used for constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier according to a set authentication rule through the authentication packaging program.
Preferably, the platform determining unit is specifically configured to determine, as the target cloud service belongs to the cloud services of the at least one cloud platform and belongs to the cloud service in the normal service state in the at least one cloud platform, the target cloud platform used for providing the target cloud service for the application client from the at least one cloud platform.
According to the scheme, at least one cloud platform is associated in the middleware device, and the interface specification and the authentication rule of each cloud service in each cloud platform are configured in the middleware device. On this basis, when the application client needs to acquire the cloud service, the application client only needs to send a cloud service request to the middleware device, and the middleware device determines a target cloud platform capable of providing the target cloud service for the application client from at least one associated cloud platform based on the target cloud service requested by the cloud service request and a corresponding service request parameter set, and constructs a cloud service request capable of calling the target cloud service in the target cloud platform.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 shows a scene architecture diagram to which the cloud service invocation method of the embodiment of the present application is applicable;
fig. 2 is a flowchart illustrating a cloud service invoking method according to an embodiment of the present application;
fig. 3 is a schematic flowchart illustrating a cloud service calling method according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a component structure of a cloud service invoking device according to an embodiment of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be practiced otherwise than as specifically illustrated.
Detailed Description
The cloud service calling method is applied to the middleware equipment, the middleware program capable of realizing cloud service calling for different applications runs in the middleware equipment, and at least one cloud platform can be associated through the middleware equipment. According to the cloud service calling method and device, the interface specifications, the calling rules and the like of the corresponding cloud services are configured in the application without aiming at the cloud services of different cloud platforms, so that the cloud services can be called by the application through the middleware equipment, and therefore even if the newly added cloud platform or cloud services exist, the application does not need to be configured in a related manner, and the newly added cloud services can be called through the middleware.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present disclosure.
For ease of understanding, the composition structure of a scene to which the scheme of the present application is applied will be described first. Fig. 1 is a schematic diagram illustrating a composition structure to which the cloud service invoking method of the present application is applied.
As shown in fig. 1, the scenario includes a middleware device 101, at least one application client 102, and at least one cloud platform 103.
The middleware device 101 and the application client may be connected through a network, and the middleware device and the cloud platform may be connected through a network.
In the embodiment of the present application, at least one cloud platform is associated with the middleware device, and as shown in fig. 1, M cloud platforms are shown, where M may be a natural number greater than or equal to one. The cloud platform associated with the middleware is the cloud platform accessed to the middleware device, so that the cloud platform associated with the middleware device is the cloud platform for the middleware device to have access authority, and the middleware device has the authority to acquire cloud services from the cloud platform.
In order for the middleware device to access the cloud platform and obtain the cloud service, the middleware device stores configuration information of each cloud platform associated with the middleware device, for example, the configuration information of each cloud platform may be maintained in an operation and maintenance management module of the middleware device in fig. 1.
Wherein the configuration information may include: the cloud service management system comprises one or more of information of cloud services of the cloud platform, interface specifications of the cloud services of the cloud platform, authentication rules corresponding to the cloud services of the cloud platform, identity authentication information for identity authentication corresponding to the cloud services of the cloud platform and the like. Of course, the configuration information may also store the address of the cloud platform and other relevant information of the cloud platform.
The information of the cloud service in the cloud platform may include: the type of cloud service the cloud platform has, identification of each cloud service, and so on.
The interface specification of the cloud service refers to parameters and specific parameter forms of the parameters required for obtaining the cloud service. In order to distinguish from the interface specification between the middleware device and the application, the interface specification of the cloud service is referred to as a first interface specification, and the interface specification between the subsequent middleware device and the application is referred to as a second interface specification.
Similarly, the authentication rule of the cloud service in the cloud platform refers to a rule related to identity authentication required for acquiring the cloud service.
It can be understood that, when a cloud platform is newly added or a cloud service is newly added to a certain cloud platform, the configuration related to the cloud platform or the cloud service in the cloud platform only needs to be newly added to the middleware device, so that only one configuration is needed, and then separate configuration, code modification and the like for different application clients are not needed.
In addition, the middleware device can also acquire the service running states of the cloud services of the cloud platforms, such as whether the cloud services are in a normal service state or abnormal service state, and record the service running states of different cloud services in the cloud platforms.
Correspondingly, if the association relationship between the cloud platform and the middleware device is cancelled, the middleware device can also delete the configuration information related to the cloud service in the cloud platform.
In the embodiment of the application, the middleware device may further have at least one application client associated therewith. As shown in fig. 1, N applications, N being a natural number equal to or greater than 1. The N applications are applications running outside the middleware device, and the corresponding application client is a device outside the middleware device. Any application client associated with the middleware device can access any cloud platform associated with the middleware device through the middleware device and acquire cloud services in the associated cloud platform.
Different applications can obtain cloud services of different cloud platforms through the middleware device, in the application, the middleware device can be associated with at least one application, and an application client of the application associated with the middleware device can obtain the cloud services of the cloud platforms through the middleware device. The middleware device stores information of each application associated therewith, such as an IP address or identification information of an application client of the application, and the like.
In the embodiment of the present application, data communication between the application and the middleware device only needs to conform to an interface specification between the middleware device and the application, and for convenience of distinguishing, the interface specification between the middleware device and the application is referred to as a second interface specification. Correspondingly, for any application, only the second interface specification needs to be stored, and a data request is sent to the middleware device according to the second interface specification, and even if the cloud platform or the cloud service changes, the application does not need to be configured and changed.
In order to enable the application to confirm the cloud services available through the middleware device, the middleware device may transmit information of each cloud service provided by the cloud platform associated with the middleware device to the middleware device; or, the application obtains a cloud service list by accessing the middleware device, and the cloud service list may include at least one cloud service that can be invoked through the middleware device.
In the application, the application may initiate a cloud service request to the middleware device to request a certain cloud service. Accordingly, the application may respond to the cloud service request and execute a cloud service call to provide the corresponding cloud service for the application.
Based on the above, the cloud service calling method of the present application is described below with reference to a flowchart.
Fig. 2 is a schematic flowchart illustrating a flow of an embodiment of a cloud service invoking method according to the present application, where the method of the present embodiment is applied to the aforementioned middleware device, and the middleware device is associated with at least one cloud platform. For example, the middleware device stores the associated configuration information of the cloud service in each cloud platform, and the configuration information at least comprises the first interface specification and the authentication rule corresponding to the cloud service, and the like.
The method of the embodiment may include:
s201, receiving a first cloud service request sent by an application client.
S202, the cloud service identifier and the service request parameter set in the first cloud service request are analyzed.
For convenience of differentiation, the cloud service request sent by the application client to the middleware device is referred to as a first cloud service request. The first cloud service request is used for requesting the middleware device to call a cloud service, and for example, the first cloud service request may be in a form of a message.
The first cloud service request carries relevant information of the requested cloud service. For example, the cloud service identifier and the service request parameter carried by the first cloud service request are included. For example, the receiving and parsing of the first cloud service request may be accomplished through an application interaction layer in the middleware device.
The cloud service identification is used for identifying a target cloud service requested to be called by the application client.
The service request parameter set includes at least one parameter required for executing the target cloud service, for example, if the target cloud service is used for querying a bank card account, the service request parameter set may need to include information such as a bank card number, an account type, an account identifier, and the like, so that the cloud platform can query information related to the bank card account based on the information.
The application client is a client of an application established with the middleware device, and on the basis, the application client is configured with a second interface specification between the middleware device and the application, wherein the second interface specification can specify a cloud service identifier carried in a cloud service request and parameters and parameter forms of various parameters required for executing the cloud service.
Accordingly, the application client may send the first cloud service request meeting the second interface specification to the middleware device according to the second interface specification. For example, the first cloud service request may be a first cloud service request packet constructed according to a second interface specification, a destination address of the first cloud service request is middleware equipment, and a specific format requirement of at least one parameter required for executing a target cloud service and an identifier of the target cloud service included in the first cloud service request both conform to the second interface specification, so that the middleware equipment may analyze the first cloud service request packet.
As an alternative, before step S201, the application client may also determine the identity of the requested cloud service. For example, the application client may request a cloud service list from the middleware device, the cloud service list including: the middleware device is associated with at least one cloud platform, and the cloud platform can provide all cloud services, such as identification information of all cloud services. Accordingly, the application client may generate a first cloud service request based on the identification of the desired cloud service.
For another example, if the middleware device sends the cloud service list to the application client in advance, that is, the application client maintains the cloud service list, the application client may also determine the identifier of the requested cloud service directly based on the stored cloud service list, and generate the first cloud service request.
Of course, in practical applications, there may be other possibilities for the process of generating the first cloud service request by the application client, which is not limited to this.
S203, if the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform, determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform.
The application client can provide the cloud services, namely the cloud services which can be provided by the middleware device, by at least one cloud platform.
The available cloud service can have multiple situations:
in one example, the cloud services that the at least one cloud platform associated with the middleware device can provide may be: the middleware device is associated with a cloud service that the at least one cloud platform has.
For example, the middleware device is associated with a cloud platform 1 and a cloud platform 2, where the cloud platform 1 has a cloud service 1 and a cloud service 2, and the cloud platform 2 has a cloud service 2 and a cloud service 3, then if the target cloud service is one of the cloud service 1, the cloud service 2, and the cloud service 3, the target cloud service belongs to the cloud services that can be provided by the at least one cloud platform.
In yet another example, the cloud services that the at least one cloud platform can provide refer to cloud services that the at least one cloud platform has and are in a normal service state. In this case, it is necessary to detect whether the target cloud service belongs to the cloud service of the at least one cloud platform, and on the premise that the target cloud service belongs to the cloud service of the at least one cloud platform, it is also necessary to detect whether the target cloud service in the at least one cloud platform is in a normal service state. Correspondingly, only if the target cloud service belongs to the cloud services of the at least one cloud platform and the target cloud service in the at least one cloud platform is in a normal service state, it is determined that the target cloud service belongs to the cloud services that can be provided by the at least one cloud platform.
The cloud service in the normal service state means that the cloud platform can normally provide the cloud service outwards, and the target cloud service cannot be called by other equipment or application due to reasons such as abnormal operation of the cloud platform and the like.
For example, still taking the middleware device associated with the cloud platform 1 and the cloud platform 2, and taking the example that the cloud platform 1 has the cloud service 1 and the cloud service 2, and the cloud platform 2 has the cloud service 2 and the cloud service 3, it is assumed that the cloud service 1 in the cloud platform 1 is in a normal service state, and the cloud service 2 is in an abnormal service state; and the cloud service 2 in the cloud platform 2 is in a normal service state, but the cloud service 3 is in an abnormal service state. Then, if the target cloud service is the cloud service 3, the target cloud service does not belong to the cloud services that can be provided by the at least one cloud platform associated with the middleware device, that is, the cloud service that can normally provide the service. If the target cloud service belongs to the cloud service 2, although the cloud service 2 in the cloud platform 1 is in the abnormal service state, the cloud service 2 in the cloud platform 2 is in the normal service state, and therefore, the target cloud service still belongs to the cloud services that can be provided by the middleware device.
It can be understood that, since different cloud platforms associated with the middleware device may have the same cloud service, in a case where a target cloud service belongs to cloud services that can be provided by the middleware device, there may be a plurality of cloud platforms that can provide the target cloud service. In this case, the middleware device needs to determine a target cloud platform from at least one cloud platform capable of providing the target cloud service, so as to provide the target cloud service for the application client through the target cloud platform.
There may be many possible ways for the middleware device to determine the target cloud platform. The following is illustrated in several possible cases:
in a possible implementation manner, after at least one cloud platform capable of providing the target cloud service is determined from the at least one cloud platform, the target cloud platform may be determined from the at least one cloud platform capable of providing the target cloud service according to a respective load state of the at least one cloud platform capable of providing the target service. For example, the target cloud platform may be a cloud platform with the smallest load among at least one cloud platform that can provide the target cloud service, or one cloud platform whose load state satisfies a set condition, and the like.
In another possible implementation manner, a rotation order in which the cloud platforms provide the cloud services may be preset, and in this case, the target cloud platform currently responsible for providing the target cloud service may be determined from at least one cloud platform that can provide the target cloud service according to the rotation order.
For example, for a plurality of cloud platforms providing a certain cloud service M, for example, the cloud platform 1 to the cloud platform 4, it may be preset that the cloud service M is provided in turn and outwards in the sequence from the cloud platform 1 to the cloud platform, and then, assuming that the cloud platform 2 provides the cloud service M for the last time, the cloud platform 3 may be selected to provide the cloud service M for this time according to the turn sequence, so that the cloud platform 3 is the target cloud platform.
S204, according to a first interface specification of the target cloud service in the target cloud platform, performing format conversion on at least one parameter in the service request parameters to obtain a service request parameter set meeting the first interface specification.
For example, the middleware device may store the first interface specification corresponding to each associated cloud service of each cloud platform, and thus, after the target cloud platform is determined, the middleware device may obtain, from the stored configuration information, the first interface specification corresponding to the target cloud service of the target cloud platform.
The first interface specification may call parameters and specific forms of the parameters, and the like, which are required to be related to the target cloud service in the target cloud platform. In this case, in order to invoke the target cloud service in the target cloud platform, format conversion needs to be performed on each parameter in the service request set according to the first interface specification, so that the parameter form of each parameter in the service request parameter set conforms to the specification of the first interface specification.
For example, if the first cloud service request is a bank account information query request, the service request parameter carries a bank card number and the like, and if the data type of the bank card number in the first cloud service request is different from the data type required in the first interface specification, the data type of the bank card number needs to be converted. Of course, this is merely an example, and the parameter items and the conversion modes related to the required conversion in practical applications may be more diversified.
S205, obtain identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware device.
The identity authentication information is verification information used by the target cloud platform to verify whether the middleware device has the authority to invoke the target cloud service.
In the embodiment of the application, when the cloud platform is connected to the middleware device, the middleware device may negotiate with the cloud platform about the identity authentication information of the cloud platform or the cloud services in the cloud platform, for example, if the identity authentication information of all the cloud services in the cloud platform is the same, the identity authentication information of the cloud platform is the identity authentication information corresponding to any one cloud service of the cloud platform; if different cloud services in the cloud platform correspond to different identity authentication information, the identity authentication information corresponding to each cloud service in the cloud platform needs to be stored respectively.
In the embodiment of the application, for the cloud service of each cloud platform, only the corresponding identity authentication information needs to be stored in the middleware device. For the cloud service of each cloud platform, only the identity authentication information of the cloud service needs to be negotiated in advance and stored in the middleware device, and it is not necessary that each application client configures the identity authentication information corresponding to the cloud services of different cloud platforms, and meanwhile, the user of the application client does not need to care about obtaining the identity authentication information required by the cloud services of different cloud platforms.
The above steps S203 to S205 may be implemented by the mapping layer in the middleware device interacting with the operation and maintenance management module.
S206, according to the authentication rule corresponding to the target cloud service in the target cloud platform, a second cloud service request which conforms to the authentication rule, carries the identity authentication information, and conforms to the service request parameter set of the first interface specification and the cloud service identifier is constructed.
The authentication rule corresponding to the target cloud service in the target cloud platform represents authentication information, information formats and the like required for obtaining the target cloud service. On this basis, based on the authentication rule corresponding to the target cloud service in the target cloud platform, a second cloud service request conforming to the authentication rule can be constructed.
Correspondingly, the identity authentication information in the second cloud service request, the service request parameter conforming to the first interface specification and the specific form of the cloud service identifier representing the target cloud service also conform to the authentication rule, so that the target cloud platform can analyze the second cloud service request and call the target cloud service to execute corresponding operation based on the service request parameter set.
When the first cloud service request is a request of the first cloud service request message, constructing the second cloud service request may also be regarded as reconstructing the first cloud service request message according to the authentication rule to obtain the second cloud service request.
As an alternative, it is considered that cloud services of different cloud platforms may correspond to an authentication encapsulation program, and the authentication encapsulation program is a program for encapsulating relevant data required for requesting the cloud services. The authentication encapsulation program is actually provided with an authentication rule corresponding to the cloud service. Correspondingly, the middleware device can install the software development kit SDK of the certification packaging program, and on this basis, the middleware device can construct a cloud service request conforming to the corresponding certification rule of the cloud service by calling and running the certification packaging program.
Correspondingly, the middleware device can call and run a pre-configured authentication encapsulation program corresponding to the target cloud service in the target cloud platform. And constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier corresponding to the target cloud service according to the set authentication rule by the authentication packaging program.
If the authentication rules of all the cloud services in one cloud platform are the same, the authentication rule corresponding to the cloud platform is the authentication rule corresponding to each cloud service in the cloud platform, and correspondingly, the authentication encapsulation program corresponding to the cloud platform is the authentication encapsulation program corresponding to each cloud service in the cloud platform. If the authentication rules of the cloud services in the cloud platform are not identical, the authentication rules or the authentication encapsulation programs of each cloud service in the cloud platform need to be configured separately.
The above step S206 may be implemented by a service interaction layer in the middleware device as shown in fig. 1.
S207, the second cloud service request is sent to the target cloud platform.
And if so, obtaining the address of the target cloud platform, and sending the second cloud service request according to the address of the target cloud platform.
For another example, when the second cloud service request is included, the address of the target cloud platform may also be carried in the second cloud service request message, so as to send the second cloud service request message to the target cloud platform.
It can be understood that in the embodiment of the application, the middleware device interacts with the target cloud platform to call the target cloud service, so that after the second cloud service request is sent to the target cloud platform, the middleware device can also receive a cloud service result returned by the target cloud platform. And the cloud service result is a calling result of the target cloud service returned by the target cloud platform in response to the second cloud service request. On this basis, the middleware device may perform format conversion on the cloud service result according to a second interface specification between the middleware device and the application to obtain a cloud service result conforming to the second interface specification, and return the cloud service result conforming to the second interface specification to the application client.
As can be seen from the above, at least one cloud platform is associated with the middleware device of the present application, and the interface specification and the authentication rule of each cloud service in each cloud platform are configured in the middleware device. On this basis, when the application client needs to acquire the cloud service, the application client only needs to send a cloud service request to the middleware device, and the middleware device determines a target cloud platform capable of providing the target cloud service for the application client from at least one associated cloud platform based on the target cloud service requested by the cloud service request and a corresponding service request parameter set, and constructs a cloud service request capable of calling the target cloud service in the target cloud platform.
For the convenience of understanding, the following describes the cloud service invocation method of the present application from the perspective of interaction between an application client, a middleware device and a cloud platform, taking a case as an example, as shown in fig. 3. The flow interaction diagram shown in fig. 3 may include the following steps:
s301, the application client sends a first cloud service request message to the middleware device.
And S302, the middleware device analyzes the first cloud service request message to obtain a cloud service identifier and a service request parameter set in the first cloud service request message.
S303, the middleware equipment detects whether a target cloud service represented by the cloud service identification exists or not according to the cloud service identification and the associated cloud service of at least one cloud platform, and if not, sends a service absence prompt to the application client; if so, step S304 is performed.
The service absence prompt cannot call the target cloud service through the middleware device, so that the application client can know that the cloud platform associated with the middleware device does not have the target cloud service after receiving the service absence prompt, and cannot call the target cloud service through the middleware device.
S304, the middleware device detects whether the target cloud service in at least one cloud platform is in a normal service state or not based on the running state of the cloud service in at least one cloud platform, and if not, the middleware device sends a service fault alarm back to the application client; if so, step S305 is performed.
If the target cloud service in the at least one cloud platform is not in the normal service state, it indicates that although the cloud platform associated with the middleware device includes the at least one cloud platform having the target cloud service, none of the cloud platforms having the target cloud service can normally provide the target cloud service, and therefore the target cloud service belongs to the cloud service in the abnormal service state in the at least one cloud platform associated with the middleware device. In this case, the application client needs to be notified that the target cloud service is in an abnormal service state.
Accordingly, if the target cloud service belongs to a cloud service that can normally provide a service in at least one cloud platform associated with the middleware device, the middleware device may continue to perform step S305 to select a cloud platform suitable for providing the target cloud service for the application client.
S305, the middleware device determines, from at least one cloud platform capable of normally providing the target cloud service, a target cloud platform suitable for providing the target cloud service for the application client.
For example, a suitable target cloud platform may be determined according to the aforementioned load status of each cloud platform capable of normally providing the target cloud service, or according to a preset polling sequence.
S306, the middleware device obtains a first interface specification of the target cloud service in the target cloud platform, and performs format conversion on the service request parameter set according to the first interface specification to obtain the service request parameter set conforming to the first interface specification.
S307, the middleware device obtains the stored address of the target cloud platform and the identity authentication information of the target cloud service in the target cloud platform.
The sequence of steps S306 and S307 is not limited to that shown in fig. 3, and in practical applications, the two steps may be executed simultaneously or the sequence may be interchanged.
And S308, the middleware equipment calls and runs an authentication packaging program of the target cloud service in the target cloud platform, and constructs a second cloud service request message which accords with the authentication rule of the target cloud service in the target cloud platform and contains the address, the identity authentication information, the converted service request parameter set and the cloud service identifier of the target cloud platform through the authentication packaging program.
S309, the middleware device sends the second cloud service request packet to the target cloud platform.
And S310, the target cloud platform responds to the second cloud service request message, and after the identity authentication information is verified, the target cloud service in the target cloud platform is called based on the service request parameter set and the cloud service identifier to obtain a cloud service result.
S311, the target cloud platform returns the cloud service result to the middleware device.
And S312, the middleware device converts the cloud service result according to the second interface specification, and returns the converted cloud service result to the application client.
If the middleware device finds that the target cloud service is failed to call by analyzing the cloud service result, the middleware device can also return a service call failure indication to the application client.
In the embodiment of the application, because the middleware device can be connected to a plurality of cloud platforms, the middleware device can also flexibly select the cloud platform for the application client by combining the running states of the cloud services in the cloud platforms under the condition that the cloud services provided by different cloud platforms have intersection, so that the flexibility and the reliability of the application client for acquiring the cloud services are improved.
The application also provides a cloud service calling device corresponding to the cloud service calling method. Fig. 4 is a schematic diagram illustrating a structural configuration of a cloud service invoking device according to the present application. The device is applied to middleware equipment, and the middleware equipment is associated with at least one cloud platform, and comprises:
a request receiving unit 401, configured to receive a first cloud service request sent by an application client;
a request parsing unit 402, configured to parse out a cloud service identifier and a service request parameter set in the first cloud service request, where the cloud service identifier is used to identify a target cloud service requested to be invoked by the application client; the service request parameter set comprises at least one parameter required for executing the target cloud service;
a platform determining unit 403, configured to determine, if the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform, a target cloud platform from the at least one cloud platform for providing the target cloud service for the application client;
a parameter conversion unit 404, configured to perform format conversion on at least one parameter in the service request parameter set according to a first interface specification of the target cloud service in the target cloud platform, so as to obtain a service request parameter set meeting the first interface specification;
an information obtaining unit 405, configured to obtain identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware device;
a request reconstruction unit 406, configured to construct, according to an authentication rule corresponding to the target cloud service in the target cloud platform, a second cloud service request that conforms to the authentication rule and carries the identity authentication information, the service request parameter set conforming to the first interface specification, and the cloud service identifier;
a request sending unit 407, configured to send the second cloud service request to the target cloud platform.
In one possible implementation, the apparatus may further include:
a result receiving unit, configured to receive a cloud service result returned by the target cloud platform, where the cloud service result is a call result of the target cloud service returned by the target cloud platform in response to the second cloud service request;
the result conversion unit is used for carrying out format conversion on the cloud service result according to a second interface specification between the middleware equipment and the application to obtain a cloud service result which accords with the second interface specification;
and the result returning unit is used for returning the cloud service result which accords with the second interface specification to the application client.
In a possible implementation manner, the request reconstructing unit may include:
the program calling subunit is used for calling and operating a pre-configured authentication packaging program corresponding to the target cloud service in the target cloud platform;
and the request reconstruction subunit is used for constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier according to a set authentication rule through the authentication packaging program.
In another possible implementation manner, the platform determining unit is specifically configured to determine, as the target cloud service belongs to the cloud services of the at least one cloud platform and belongs to the cloud services in the normal service state in the at least one cloud platform, the target cloud platform used for providing the target cloud service for the application client from the at least one cloud platform.
Optionally, the apparatus further comprises:
a prompt unit, configured to, if the target cloud service does not belong to a cloud service of the at least one cloud platform, return a service absence prompt to the application client, where the service absence prompt fails to invoke the target cloud service through the middleware device;
and the alarm unit is used for returning a service fault alarm to the application client if the target cloud service belongs to the cloud service in the abnormal service state in the at least one cloud platform, wherein the service fault alarm is used for prompting that the target cloud service is in the abnormal service state.
In another possible implementation manner, when the platform determining unit determines, from the at least one cloud platform, a target cloud platform for providing a target cloud service for the application client, specifically: determining at least one cloud platform capable of providing target cloud service from the at least one cloud platform; according to the respective load condition of at least one cloud platform capable of providing the target cloud service, determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform capable of providing the target cloud service.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. The cloud service calling method is applied to middleware equipment, wherein the middleware equipment is associated with at least one cloud platform, and comprises the following steps:
receiving a first cloud service request sent by an application client;
analyzing a cloud service identifier and a service request parameter set in the first cloud service request, wherein the cloud service identifier is used for identifying a target cloud service requested to be called by the application client; the service request parameter set comprises at least one parameter required for executing the target cloud service;
if the target cloud service belongs to the cloud services available by the at least one cloud platform, determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform;
according to a first interface specification of the target cloud service in the target cloud platform, performing format conversion on at least one parameter in the service request parameter set to obtain a service request parameter set conforming to the first interface specification;
obtaining identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment;
according to an authentication rule corresponding to the target cloud service in the target cloud platform, constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information and the service request parameter set which accords with the first interface specification and the cloud service identifier;
and sending the second cloud service request to the target cloud platform.
2. The method of claim 1, further comprising:
receiving a cloud service result returned by the target cloud platform, wherein the cloud service result is a calling result of the target cloud service returned by the target cloud platform in response to the second cloud service request;
according to a second interface specification between the middleware equipment and the application, carrying out format conversion on the cloud service result to obtain a cloud service result which accords with the second interface specification;
and returning the cloud service result which accords with the second interface specification to the application client.
3. The method according to claim 1, wherein the constructing a second cloud service request that conforms to the authentication rule and carries the identity authentication information, the service request parameter set conforming to the first interface specification, and the cloud service identifier according to the authentication rule corresponding to the target cloud service in the target cloud platform comprises:
calling and operating a pre-configured authentication packaging program corresponding to the target cloud service in the target cloud platform;
and constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier according to a set authentication rule by the authentication packaging program.
4. The method of claim 1, wherein the target cloud service belongs to cloud services available by the at least one cloud platform, and comprises:
the target cloud service belongs to the cloud services of the at least one cloud platform and belongs to the cloud services in the normal service state in the at least one cloud platform.
5. The method of claim 4, further comprising:
if the target cloud service does not belong to the cloud services of the at least one cloud platform, returning a service absence prompt to the application client, wherein the service absence prompt cannot call the target cloud service through the middleware equipment;
if the target cloud service belongs to the cloud service in the abnormal service state in the at least one cloud platform, returning a service fault alarm to the application client, wherein the service fault alarm is used for prompting that the target cloud service is in the abnormal service state.
6. The method of claim 1, wherein determining a target cloud platform from the at least one cloud platform for providing the target cloud service for the application client comprises:
determining at least one cloud platform capable of providing the target cloud service from the at least one cloud platform;
and determining a target cloud platform for providing the target cloud service for the application client from the at least one cloud platform capable of providing the target cloud service according to the respective load condition of the at least one cloud platform capable of providing the target cloud service.
7. The cloud service calling device is applied to a middleware device, the middleware device is associated with at least one cloud platform, and the cloud service calling device comprises:
the request receiving unit is used for receiving a first cloud service request sent by an application client;
the request analysis unit is used for analyzing a cloud service identifier and a service request parameter set in the first cloud service request, wherein the cloud service identifier is used for identifying a target cloud service requested to be called by the application client; the service request parameter set comprises at least one parameter required for executing the target cloud service;
a platform determination unit, configured to determine, if the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform, a target cloud platform from the at least one cloud platform for providing the target cloud service for the application client;
the parameter conversion unit is used for carrying out format conversion on at least one parameter in the service request parameter set according to a first interface specification of the target cloud service in the target cloud platform to obtain a service request parameter set conforming to the first interface specification;
an information obtaining unit, configured to obtain identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware device;
the request reconstruction unit is used for constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information, the service request parameter set which accords with the first interface specification and the cloud service identifier according to the authentication rule corresponding to the target cloud service in the target cloud platform;
a request sending unit, configured to send the second cloud service request to the target cloud platform.
8. The apparatus of claim 7, further comprising:
a result receiving unit, configured to receive a cloud service result returned by the target cloud platform, where the cloud service result is a call result of the target cloud service returned by the target cloud platform in response to the second cloud service request;
the result conversion unit is used for carrying out format conversion on the cloud service result according to a second interface specification between the middleware equipment and the application to obtain a cloud service result which accords with the second interface specification;
and the result returning unit is used for returning the cloud service result which accords with the second interface specification to the application client.
9. The apparatus of claim 7, wherein the request reconstruction unit comprises:
the program calling subunit is used for calling and operating a pre-configured authentication packaging program corresponding to the target cloud service in the target cloud platform;
and the request reconstruction subunit is used for constructing a second cloud service request carrying the identity authentication information, the service request parameter set conforming to the first interface specification and the cloud service identifier according to a set authentication rule through the authentication packaging program.
10. The apparatus according to claim 7, wherein the platform determining unit is configured to determine, if the target cloud service belongs to the cloud services of the at least one cloud platform and to the cloud service in the normal service state of the at least one cloud platform, a target cloud platform from the at least one cloud platform for providing the target cloud service for the application client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010346973.6A CN111552568B (en) | 2020-04-28 | 2020-04-28 | Cloud service calling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010346973.6A CN111552568B (en) | 2020-04-28 | 2020-04-28 | Cloud service calling method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552568A true CN111552568A (en) | 2020-08-18 |
| CN111552568B CN111552568B (en) | 2023-11-21 |
Family
ID=72003272
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010346973.6A Active CN111552568B (en) | 2020-04-28 | 2020-04-28 | Cloud service calling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552568B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112217840A (en) * | 2020-12-09 | 2021-01-12 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| CN112437138A (en) * | 2020-11-12 | 2021-03-02 | 安徽大学 | Measurement and control terminal based on NBIoT communication and communication docking and switching method thereof |
| CN113783741A (en) * | 2021-11-10 | 2021-12-10 | 云丁网络技术(北京)有限公司 | Method, device, server, gateway equipment and system for configuring gateway equipment |
| CN113824795A (en) * | 2021-10-21 | 2021-12-21 | 上海波顿诺华智能科技有限公司 | Communication method, device and system of vehicle end and cloud end |
| CN114100143A (en) * | 2021-11-11 | 2022-03-01 | 腾讯科技（深圳）有限公司 | Cloud service control method and related device |
| CN115883652A (en) * | 2022-12-08 | 2023-03-31 | 北京中电普华信息技术有限公司 | Cloud service adaptation method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739771A (en) * | 2012-04-18 | 2012-10-17 | 上海和辰信息技术有限公司 | Cloud application integrated management platform and method supporting service fusion |
| WO2015062399A1 (en) * | 2013-10-31 | 2015-05-07 | 乐视网信息技术（北京）股份有限公司 | Cloud service platform middleware and cloud uploading method |
| CN110365483A (en) * | 2018-04-11 | 2019-10-22 | 中国移动通信集团广东有限公司 | Cloud platform authentication method, client, middleware and system |
| US20190379663A1 (en) * | 2018-06-12 | 2019-12-12 | Sap Se | Mediated authentication and authorization for service consumption and billing |
| CN110650216A (en) * | 2019-10-24 | 2020-01-03 | 北京天润融通科技股份有限公司 | Cloud service request method and device |
| CN110784509A (en) * | 2019-09-16 | 2020-02-11 | 腾讯科技（深圳）有限公司 | Medical information processing method and system and related components |
| CN110830463A (en) * | 2019-10-30 | 2020-02-21 | 腾讯科技（深圳）有限公司 | Third party authorized login method and device |
-
2020
- 2020-04-28 CN CN202010346973.6A patent/CN111552568B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739771A (en) * | 2012-04-18 | 2012-10-17 | 上海和辰信息技术有限公司 | Cloud application integrated management platform and method supporting service fusion |
| WO2015062399A1 (en) * | 2013-10-31 | 2015-05-07 | 乐视网信息技术（北京）股份有限公司 | Cloud service platform middleware and cloud uploading method |
| CN110365483A (en) * | 2018-04-11 | 2019-10-22 | 中国移动通信集团广东有限公司 | Cloud platform authentication method, client, middleware and system |
| US20190379663A1 (en) * | 2018-06-12 | 2019-12-12 | Sap Se | Mediated authentication and authorization for service consumption and billing |
| CN110784509A (en) * | 2019-09-16 | 2020-02-11 | 腾讯科技（深圳）有限公司 | Medical information processing method and system and related components |
| CN110650216A (en) * | 2019-10-24 | 2020-01-03 | 北京天润融通科技股份有限公司 | Cloud service request method and device |
| CN110830463A (en) * | 2019-10-30 | 2020-02-21 | 腾讯科技（深圳）有限公司 | Third party authorized login method and device |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112437138A (en) * | 2020-11-12 | 2021-03-02 | 安徽大学 | Measurement and control terminal based on NBIoT communication and communication docking and switching method thereof |
| CN112217840A (en) * | 2020-12-09 | 2021-01-12 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| CN112217840B (en) * | 2020-12-09 | 2021-04-13 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| US11457046B2 (en) | 2020-12-09 | 2022-09-27 | Hangzhou Jindoutengyun Technologies Co., Ltd. | Distributed network resource security access management system and user portal |
| CN113824795A (en) * | 2021-10-21 | 2021-12-21 | 上海波顿诺华智能科技有限公司 | Communication method, device and system of vehicle end and cloud end |
| CN113783741A (en) * | 2021-11-10 | 2021-12-10 | 云丁网络技术(北京)有限公司 | Method, device, server, gateway equipment and system for configuring gateway equipment |
| CN113783741B (en) * | 2021-11-10 | 2022-03-11 | 云丁网络技术(北京)有限公司 | Method, device, server, gateway equipment and system for configuring gateway equipment |
| CN114100143A (en) * | 2021-11-11 | 2022-03-01 | 腾讯科技（深圳）有限公司 | Cloud service control method and related device |
| CN115883652A (en) * | 2022-12-08 | 2023-03-31 | 北京中电普华信息技术有限公司 | Cloud service adaptation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552568B (en) | 2023-11-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111552568B (en) | Cloud service calling method and device | |
| EP3748908B1 (en) | Method, system, network device, storage medium for creating a network slice | |
| US9479400B2 (en) | Servlet API and method for XMPP protocol | |
| CN112104754B (en) | Network proxy method, system, device, equipment and storage medium | |
| CN110554927A (en) | Micro-service calling method based on block chain | |
| CN111447185A (en) | Processing method of push information and related equipment | |
| CN112835782B (en) | Interface access test method and system | |
| CN115086176B (en) | System for realizing dynamic issuing of service administration strategy based on spring cloud micro-service technology | |
| CN111858083A (en) | Remote service calling method and device, electronic equipment and storage medium | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN109510799B (en) | Page display method, browser client, equipment and storage medium | |
| CN114938396A (en) | Routing method of service call request, method and device for creating service | |
| CN113360386A (en) | Switching chip drive test method, device, electronic equipment and storage medium | |
| US20020069257A1 (en) | Provisioning mechanism for a service gateway | |
| CN113760562A (en) | Link tracking method, device, system, server and storage medium | |
| US20040243693A1 (en) | Inbound connector | |
| CN114710311B (en) | Multi-project message management method and system | |
| CN116389385A (en) | System resource processing method, device, storage medium and equipment | |
| CN112448909A (en) | Electronic lock management method, device, system and storage medium | |
| CN115174592A (en) | Enterprise-level data request forwarding system and method | |
| CN113918245A (en) | Data calling method, device, equipment and computer readable storage medium | |
| CN114398082B (en) | Compatible operation method and device for frame type block chain application | |
| CN117609973B (en) | Registration center nano-tube method, system, device and server | |
| CN111368512B (en) | Service data conversion method, device, equipment and storage medium | |
| CN111131471B (en) | Operation method and device of service system and electronic equipment |
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 |