CN111552568B - Cloud service calling method and device - Google Patents
Cloud service calling method and device Download PDFInfo
- Publication number
- CN111552568B CN111552568B CN202010346973.6A CN202010346973A CN111552568B CN 111552568 B CN111552568 B CN 111552568B CN 202010346973 A CN202010346973 A CN 202010346973A CN 111552568 B CN111552568 B CN 111552568B
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000006243 chemical reaction Methods 0.000 claims description 20
- 230000002159 abnormal effect Effects 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
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
Abstract
The application discloses a cloud service calling method and a cloud service calling device. On the basis, when the application client needs to acquire cloud service, the application client only needs to send a cloud service request to the middleware equipment, the middleware equipment can determine 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 builds a cloud service request capable of calling the target cloud service in the target cloud platform, so that the application client does not need to respectively carry out different configurations for different cloud platforms and different cloud services, and can realize the calling of the cloud service of different cloud platforms through the middleware equipment, and the complexity of obtaining the cloud service by application is reduced.
Description
Technical Field
The present application relates to the field of cloud technologies, and 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 is provided with a certain cloud service, if the application needs to obtain the cloud service, the cloud service can be requested to the cloud platform through the application client.
With the continuous development of cloud technology, cloud platforms capable of providing cloud services are 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 have great difference, so that whenever an application needs to newly increase the calling requirement of one 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 the cloud service of a certain cloud service originally, but it is now hoped to be able to realize the calling of the cloud service of a certain cloud platform of a cloud server of the cloud platform, and the like), complex operations such as some information configuration, code change and the like need to be performed on the application, thereby resulting in higher complexity of acquiring the cloud service by the application.
Disclosure of Invention
The application aims to provide a cloud service calling method and device, so that complex configuration and modification required by an application for obtaining cloud service are reduced, and complexity of obtaining cloud service by the application is reduced.
In order to achieve the above purpose, the present application provides the following technical solutions:
in one aspect, the present application provides a cloud service invocation method 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 includes at least one parameter required to execute 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, wherein the target cloud service belongs to cloud services which can be provided by 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;
acquiring identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment;
Constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information, a 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;
and sending the second cloud service request to the target cloud platform.
Preferably, the method further comprises:
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, converting the format of the cloud service result to obtain a cloud service result conforming to the second interface specification;
and returning the cloud service result meeting 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 that conforms to the authentication rule and carries the identity authentication information, a service request parameter set that conforms to the first interface specification, and the cloud service identifier includes:
Invoking and running an authentication encapsulation program corresponding to the target cloud service in the target cloud platform which is pre-configured;
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 the set authentication rule by the authentication packaging program.
Preferably, the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform, and the target cloud service comprises:
the target cloud service belongs to a cloud service possessed by the at least one cloud platform and belongs to a cloud service in a normal service state in the at least one cloud platform.
Preferably, the method further comprises:
if the target cloud service does not belong to the cloud service 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;
and 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 at least one cloud platform capable of providing the target cloud service according to the respective load conditions of the at least one cloud platform capable of providing the target cloud service.
In still another aspect, the present application further provides a cloud service invocation apparatus, which is applied to a middleware device, where the middleware device is associated with at least one cloud platform, and includes:
the request receiving unit is used for receiving a first cloud service request sent by the 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 includes at least one parameter required to execute the target cloud service;
a platform determining unit, configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client, where the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform;
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;
the information obtaining unit is used for obtaining identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment;
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;
and the request sending unit is used for sending the second cloud service request to the target cloud platform.
Preferably, the method further comprises:
the result receiving unit is used for 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;
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 conforming to 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 reconstruction unit includes:
the program calling subunit is used for calling and running an authentication encapsulation program corresponding to the target cloud service in the target cloud platform which is configured in advance;
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 the set authentication rule by the authentication packaging program.
Preferably, the platform determining unit is specifically configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client, where the target cloud service belongs to a cloud service that the at least one cloud platform has and belongs to a cloud service that is in a normal service state in the at least one cloud platform.
According to the scheme, at least one cloud platform is associated in the middleware equipment, and interface specifications and authentication rules of each cloud service in each cloud platform are configured in the middleware equipment. On the basis, when the application client needs to acquire cloud service, the application client only needs to send a cloud service request to the middleware equipment, the middleware equipment can determine 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 builds a cloud service request capable of calling the target cloud service in the target cloud platform, so that the application client does not need to respectively carry out different configurations for different cloud platforms and different cloud services, and can realize the calling of the cloud service of different cloud platforms through the middleware equipment, and the complexity of obtaining the cloud service by application is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 shows a schematic view of a scenario architecture to which a cloud service invocation method according to an embodiment of the present application is applied;
FIG. 2 is a schematic flow chart of a cloud service invocation method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of a cloud service invocation method according to an embodiment of the present application;
fig. 4 is a schematic diagram of a composition structure of a cloud service invocation apparatus according to an embodiment of the present application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in other sequences than those illustrated herein.
Detailed Description
The cloud service calling method is applied to middleware equipment, wherein middleware programs capable of realizing cloud service calling for different applications are operated 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, interface specifications, calling rules and the like of corresponding cloud services are not required to be configured in the application aiming at cloud services of different cloud platforms, so that the application can realize the calling of the cloud services through middleware equipment, and therefore, even if a newly added cloud platform or cloud service exists, the application does not need to perform relevant configuration, and the calling of the newly added cloud service can be realized through middleware.
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without any inventive effort, are intended to be within the scope of the application.
For easy understanding, the composition structure of a scene to which the scheme of the present application is applied will be described. Fig. 1 is a schematic diagram showing a composition structure to which the cloud service calling 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 equipment 101 and the application client can be connected through a network, and the middleware equipment and the cloud platform can also be connected through the network.
In the embodiment of the present application, the middleware device is associated with at least one cloud platform, as shown in fig. 1, where M may be a natural number greater than or equal to one. The cloud platform associated with the middleware, namely, the cloud platform accessed to the middleware equipment, therefore, the cloud platform associated with the middleware equipment, namely, the cloud platform with access rights of the middleware equipment, is established, and the middleware equipment has rights of acquiring 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 may store 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 platform comprises one or more of information of cloud services, interface specifications of the cloud services, authentication rules corresponding to the cloud services, identity authentication information corresponding to the cloud services and used for identity authentication, 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 that the cloud platform has, the identity of each cloud service, and so on.
The interface specification of the cloud service refers to parameters of parameters required for acquiring the cloud service, specific parameter forms and the like. In order to facilitate distinguishing from interface specifications between middleware devices and applications, the interface specification of the cloud service is referred to as a first interface specification, and the interface specification between a subsequent middleware device and 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 in the case of newly adding a cloud platform or a cloud service of a certain cloud platform, the method only needs to newly adding the cloud platform or the configuration related to the cloud service in the cloud platform in the middleware equipment, so that only one configuration is needed, and later, the configuration, the code modification and the like do not need to be independently carried out for different application clients.
In addition, the middleware device can also acquire service running states of cloud services of each cloud platform, such as whether the cloud services are in a normal service state, whether service anomalies exist, and the like, and record the service running states of different cloud services in each cloud platform.
Correspondingly, if the association relationship between the cloud platform and the middleware equipment is canceled, the middleware equipment also deletes the configuration information related to the cloud service in the cloud platform.
In the embodiment of the application, the middleware device can be further associated with at least one application client. As shown in fig. 1, N applications, N being a natural number of 1 or more. The N applications are applications running outside the middleware equipment, and the corresponding application clients are equipment outside the middleware equipment. Any application client associated with the middleware equipment can access any cloud platform associated with the middleware equipment through the middleware equipment, and cloud services in the associated cloud platform are acquired.
Different applications can obtain cloud services of different cloud platforms through the middleware equipment, in the application, the middleware equipment can be associated with at least one application, and an application client of the application associated with the middleware equipment can obtain the cloud services of the cloud platforms through the middleware equipment. Wherein 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, etc.
In the embodiment of the application, the data communication between the application and the middleware device only needs to meet the interface specification between the middleware device and the application, and the interface specification between the middleware device and the application is called a second interface specification for convenience of distinction. Correspondingly, for any application, only the second interface specification is needed to be stored, and a data request is sent to the middleware equipment according to the second interface specification, so that even if the cloud platform or the cloud service is changed, the application does not need to be changed in configuration.
In order to enable an application to confirm cloud services available through a middleware device, the middleware device may send information of each cloud service provided by a cloud platform associated with the middleware device to the middleware device; alternatively, the application obtains a cloud service list by accessing the middleware device, where the cloud service list may include at least one cloud service that may be invoked by the middleware device.
In the application, the application can initiate a cloud service request to the middleware equipment to request a certain cloud service. Accordingly, the application may respond to the cloud service request and perform cloud service invocation to provide the application with the corresponding cloud service.
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 flow chart of an embodiment of a cloud service invocation 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 associated configuration information of cloud services in each cloud platform, where the configuration information at least includes a first interface specification and an authentication rule corresponding to the cloud services.
The method of the embodiment can comprise the following steps:
s201, a first cloud service request sent by an application client is received.
S202, resolving a cloud service identifier and a service request parameter set in the first cloud service request.
For convenience of distinction, a cloud service request sent by an application client to a 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 the cloud service, for example, the first cloud service request may be in the form of a message.
Wherein the first cloud service request carries information about the requested cloud service. Such as the cloud service identifier and the service request parameter carried by the first cloud service request. 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 invoked by the application client.
The service request parameter set includes at least one parameter required for executing the target cloud service, for example, the target cloud service is used for inquiring the bank card account, and then the service request parameter set may need to include information such as the bank card number, the account type, the account identification and the like, so that the cloud platform can realize inquiring of the related information of the bank card account based on the information.
The application client is a client establishing an associated application 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, parameters and parameter forms of various parameters required by executing the cloud service, and the like.
Accordingly, the application client may send a first cloud service request conforming to 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, where a destination address of the first cloud service request is a middleware device, and the first cloud service request includes an identifier of a target cloud service and a specific format requirement of at least one parameter required for executing the target cloud service all conform to the second interface specification, so that the middleware device may parse 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, where the cloud service list includes: and the information of all cloud services which can be provided by at least one cloud platform associated with the middleware equipment, 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 required 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, directly based on the stored cloud service list, an identifier of the requested cloud service, and generate the first cloud service request.
Of course, in practical applications, the process of generating the first cloud service request by the application client may also have other possibilities, which are not limited.
S203, if the target cloud service belongs to the cloud service which 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 cloud service provided by the at least one cloud platform, namely, the cloud service provided by the middleware device to the application client.
Among other things, the available cloud service may be in a variety of situations:
in one example, the cloud services that the at least one cloud platform associated with the middleware device may provide may be: the at least one cloud platform associated with the middleware device has cloud services.
For example, the middleware device is associated with a cloud platform 1 and a cloud platform 2, wherein 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, and 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 a cloud service that can be provided by the at least one cloud platform.
In yet another example, the cloud service that the at least one cloud platform can provide refers to a cloud service that the at least one cloud platform has and is in a normal service state. In this case, it is required to detect whether the target cloud service belongs to a cloud service that the at least one cloud platform has, and if the target cloud service belongs to a cloud service that the at least one cloud platform has, it is also required to detect whether the target cloud service in the at least one cloud platform is in a normal service state. Accordingly, only if the target cloud service belongs to the cloud service possessed by the at least one cloud platform and the target cloud service in the at least one cloud platform is in a normal service state, determining that the target cloud service belongs to the cloud service providable 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 problem that other equipment cannot be used or the target cloud service cannot be called due to abnormal operation of the cloud platform and other reasons does not occur.
For example, taking the example that the middleware device is associated with a cloud platform 1 and a cloud platform 2, and 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, 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; while in the cloud platform 2, the cloud service 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 a cloud service that can be provided by 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 an abnormal service state, the cloud service 2 in the cloud platform 2 is in a normal service state, and thus, the target cloud service still belongs to the cloud service that the middleware device can provide.
It may be appreciated that, since different cloud platforms associated with the middleware device may have the same cloud service, where the target cloud service belongs to a cloud service that may be provided by the middleware device, there may be multiple cloud platforms capable of providing 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.
The manner in which the middleware device determines the target cloud platform may be a variety of possibilities. The following description is made in several possible cases:
in one possible implementation manner, after determining at least one cloud platform capable of providing the target cloud service 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 respective load states 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 a cloud platform with a load state satisfying a set condition, or the like.
In yet another possible implementation manner, a rotation order of providing cloud services by each cloud platform may be preset, in which case, a target cloud platform currently responsible for providing the target cloud service may be determined from at least one cloud platform that may provide the target cloud service according to the rotation order.
For example, for a plurality of cloud platforms that provide a certain cloud service M, for example, cloud platform 1 to cloud platform 4, it may be preset that the cloud service M is provided outwards in turn in the order from cloud platform 1 to cloud platform, and if cloud platform 2 is providing cloud service M the last time, then cloud platform 3 may be selected to provide cloud service M this time in this turn, and thus cloud platform 3 is the target cloud platform.
S204, format conversion is carried out on at least one parameter in the service request parameters 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 which accords with the first interface specification.
For example, the middleware device may store the first interface specification corresponding to each cloud service of each cloud platform, so after determining the target cloud platform, the middleware device may obtain the first interface specification corresponding to the target cloud service in the target cloud platform from the stored configuration information.
The first interface specification may call parameters, specific forms of 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 be able 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 accords with 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 may carry a bank card number, 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, the examples are only for illustration, and the parameters related to the required conversion and the conversion mode in the practical application will be more diversified.
S205, obtaining identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment.
The identity authentication information is authentication information used for the target cloud platform to authenticate whether the middleware equipment has the authority to call the target cloud service.
In the embodiment of the application, when the cloud platform is connected to the middleware device, the middleware device can negotiate with the cloud platform about the identity authentication information of the cloud platform or the cloud service 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 corresponding identity authentication information is required to be stored in the middleware equipment. For the cloud service of each cloud platform, only the identity authentication information of the cloud service is required to be negotiated and stored in the middleware equipment in advance, each application client is not required to be respectively configured with the identity authentication information corresponding to the cloud service of different cloud platforms, and meanwhile, the user of the application client is not required to care about acquiring the identity authentication information required by the cloud service 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, 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.
The authentication rules corresponding to the target cloud service in the target cloud platform represent authentication information, information formats and the like required by acquiring the target cloud service. On the basis, a second cloud service request conforming to the authentication rule can be constructed based on the authentication rule corresponding to the target cloud service in the target cloud platform.
Correspondingly, the identity authentication information in the second cloud service request, the service request parameters 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 operations based on the service request parameter set.
Under the condition that the first cloud service request is a request of a first cloud service request message, constructing the second cloud service request can also be regarded as reconstructing the first cloud service request message according to the authentication rule so as to obtain the second cloud service request.
As an alternative, consider an authentication encapsulation program corresponding to a cloud service of a different cloud platform, which is a program for encapsulating related data required for requesting the cloud service. The authentication encapsulation program is actually provided with authentication rules corresponding to the cloud service. Correspondingly, the middleware equipment can install the software development kit SDK of the authentication encapsulation program, and on the basis, the middleware equipment can realize the construction of a cloud service request conforming to the authentication rule corresponding to the cloud service by calling and running the authentication encapsulation program.
Correspondingly, the middleware equipment 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, a service request parameter set conforming to the first interface specification and a 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 cloud services in one cloud platform are the same, the authentication rules corresponding to the cloud platform are the authentication rules corresponding to all cloud services in the cloud platform, and correspondingly, the authentication packaging program corresponding to the cloud platform is the authentication packaging program corresponding to all cloud services in the cloud platform. If the authentication rules of the cloud services in the cloud platform are not identical, the authentication rules or authentication packaging programs of each cloud service in the cloud platform need to be configured independently.
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.
If so, the address of the target cloud platform is obtained, and the second cloud service request is sent according to the address of the target cloud platform.
For another example, if the second cloud service request is included, the address of the target cloud platform may also be carried in the second cloud service request packet, so as to send the second cloud service request packet to the target cloud platform.
It can be understood that, in the embodiment of the present application, the middleware device interacts with the target cloud platform to implement the invocation of the target cloud service, so after sending the second cloud service request to the target cloud platform, the middleware device may also receive the cloud service result returned by the target cloud platform. 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 the basis, the middleware equipment can perform 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 conforming to the second interface specification, and the cloud service result conforming to the second interface specification is returned to the application client.
As can be seen from the above, at least one cloud platform is associated in the middleware device of the present application, and the interface specification and authentication rules of each cloud service in each cloud platform are configured in the middleware device. On the basis, when the application client needs to acquire cloud service, the application client only needs to send a cloud service request to the middleware equipment, the middleware equipment can determine 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 builds a cloud service request capable of calling the target cloud service in the target cloud platform, so that the application client does not need to respectively carry out different configurations for different cloud platforms and different cloud services, and can realize the calling of the cloud service of different cloud platforms through the middleware equipment, and the complexity of obtaining the cloud service by application is reduced.
For easy understanding, the cloud service invocation method of the present application will be described below with reference to an application client, and a middleware device interacting with a cloud platform, as shown in fig. 3, by taking an example. The flow interaction schematic shown in fig. 3 may include the following steps:
S301, an application client sends a first cloud service request message to middleware equipment.
S302, the middleware equipment 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 identifier exists or not according to the cloud service identifier and cloud services of at least one associated cloud platform, and if not, sends a service absence prompt to an application client; if so, step S304 is performed.
The service does not have a prompt that the target cloud service cannot be called through the middleware equipment, so that the application client receives the service does not have the prompt, and the application client can know that the cloud platform associated with the middleware equipment does not have the target cloud service and cannot call the target cloud service through the middleware equipment.
S304, the middleware equipment detects whether the target cloud service in at least one cloud platform is in a normal service state based on the running state of the cloud service in the at least one cloud platform, and if not, sends a service fault alarm returned to the application client; if so, step S305 is performed.
The target cloud service in the at least one cloud platform is not in a normal service state, which indicates that although the cloud platform associated with the middleware device includes the at least one cloud platform with the target cloud service, the cloud platform with the target cloud service cannot normally provide the target cloud service, so that the target cloud service belongs to the cloud service in an 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 of the information 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 execute step S305 to select a cloud platform suitable for providing the target cloud service for the application client.
And S305, the middleware equipment determines a target cloud platform suitable for providing the target cloud service for the application client from at least one cloud platform capable of normally providing the target cloud service.
For example, a suitable target cloud platform may be determined in combination with the aforementioned load status of each cloud platform capable of normally providing the target cloud service or a preset polling sequence, and the like.
S306, the middleware equipment 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 equipment 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 order of steps S306 and S307 is not limited to that shown in fig. 3, and in practical application, the steps may be performed simultaneously or the order may be interchanged.
S308, the middleware equipment invokes and runs an authentication encapsulation program of the target cloud service in the target cloud platform, and builds an authentication rule conforming to the target cloud service in the target cloud platform through the authentication encapsulation program, wherein the authentication rule comprises an address of the target cloud platform, identity authentication information, a converted service request parameter set and a second cloud service request message of the cloud service identifier.
S309, the middleware equipment sends the second cloud service request message to the target cloud platform.
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 identification, so that a cloud service result is obtained.
And S311, the target cloud platform returns the cloud service result to the middleware equipment.
S312, the middleware equipment 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 analyzes the cloud service result to find that the target cloud service call fails, the middleware device can also return a service call failure indication to the application client.
In the embodiment of the application, as the middleware equipment can be connected with a plurality of cloud platforms, the middleware equipment can flexibly select the cloud platform for the application client by combining the running state of the cloud service in the cloud platform under the condition that the cloud services provided by different cloud platforms have intersection, thereby being beneficial to improving the flexibility and the reliability of the application client for acquiring the cloud service.
The application also provides a cloud service calling device corresponding to the cloud service calling method. As shown in fig. 4, a schematic diagram of a composition structure of a cloud service invocation apparatus of the present application is shown. The apparatus is applied to a middleware device, the middleware device is associated with at least one cloud platform, and the apparatus 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 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 includes at least one parameter required to execute the target cloud service;
a platform determining unit 403, configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service to the application client, where the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform;
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 that meets 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, a service request parameter set that conforms 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:
the result receiving unit is used for 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;
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 conforming to 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 one possible implementation, the request reconstruction unit may include:
the program calling subunit is used for calling and running an authentication encapsulation program corresponding to the target cloud service in the target cloud platform which is configured in advance;
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 the set authentication rule by the authentication packaging program.
In yet another possible implementation manner, the platform determining unit is specifically configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client, where the target cloud service belongs to a cloud service that the at least one cloud platform has and belongs to a cloud service that is in a normal service state in the at least one cloud platform.
Optionally, the apparatus further comprises:
the prompting unit is used for returning a service absence prompt to the application client if the target cloud service does not belong to the cloud service of the at least one cloud platform, wherein the service absence prompt cannot call the target cloud service through the middleware equipment;
and the alarm unit is used for returning service fault alarms 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, and the service fault alarms are used for prompting that the target cloud service is in the abnormal service state.
In yet another possible implementation manner, the platform determining unit, when determining, from at least one cloud platform, a target cloud platform for providing a target cloud service for an application client, specifically is: determining at least one cloud platform capable of providing target cloud services from the at least one cloud platform; and determining the 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 conditions of 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 (8)
1. The cloud service calling method is characterized by being applied to middleware equipment, wherein the middleware equipment is associated with at least one cloud platform, and middleware programs capable of realizing cloud service calling for different applications are operated in the middleware equipment, and the cloud service calling method comprises the following steps of:
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 includes at least one parameter required to execute 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, wherein the target cloud service belongs to cloud services which can be provided by 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;
acquiring identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment; the identity authentication information is used for verifying whether the middleware equipment has the authority of calling the target cloud service or not by the target cloud platform, and the middleware equipment stores the identity authentication information corresponding to each cloud service;
constructing a second cloud service request which accords with the authentication rule and carries the identity authentication information, a 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;
sending the second cloud service request to the target cloud platform;
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 client, converting the format of the cloud service result to obtain a cloud service result conforming to the second interface specification;
and returning the cloud service result meeting the second interface specification to the application client.
2. The method of claim 1, wherein the constructing, according to the 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 that conforms to the first interface specification, and the cloud service identifier, includes:
invoking and running an authentication encapsulation program corresponding to the target cloud service in the target cloud platform which is pre-configured;
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 the set authentication rule by the authentication packaging program.
3. The method of claim 1, wherein the target cloud service belongs to a cloud service that the at least one cloud platform can provide, comprising:
the target cloud service belongs to a cloud service possessed by the at least one cloud platform and belongs to a cloud service in a normal service state in the at least one cloud platform.
4. A method according to claim 3, further comprising:
if the target cloud service does not belong to the cloud service 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;
and 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.
5. The method of claim 1, wherein the determining, from the at least one cloud platform, a target 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 at least one cloud platform capable of providing the target cloud service according to the respective load conditions of the at least one cloud platform capable of providing the target cloud service.
6. The cloud service calling device is characterized by being applied to middleware equipment, wherein at least one cloud platform is associated with the middleware equipment, and a middleware program capable of realizing cloud service calling for different applications is operated in the middleware equipment, and comprises the following components:
the request receiving unit is used for receiving a first cloud service request sent by the 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 includes at least one parameter required to execute the target cloud service;
a platform determining unit, configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client, where the target cloud service belongs to a cloud service that can be provided by the at least one cloud platform;
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;
the information obtaining unit is used for obtaining identity authentication information corresponding to the target cloud service in the target cloud platform configured in the middleware equipment; the identity authentication information is used for verifying whether the middleware equipment has the authority of calling the target cloud service or not by the target cloud platform, and the middleware equipment stores the identity authentication information corresponding to each cloud service;
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;
the result receiving unit is used for 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;
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 client to obtain a cloud service result conforming to 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.
7. The apparatus of claim 6, wherein the request reconstruction unit comprises:
the program calling subunit is used for calling and running an authentication encapsulation program corresponding to the target cloud service in the target cloud platform which is configured in advance;
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 the set authentication rule by the authentication packaging program.
8. The apparatus according to claim 6, wherein the platform determining unit is specifically configured to determine, from the at least one cloud platform, a target cloud platform for providing the target cloud service for the application client, as the target cloud service belongs to a cloud service that the at least one cloud platform has and belongs to a cloud service that is in a normal service state in the at least one cloud platform.
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 CN111552568A (en) | 2020-08-18 |
| CN111552568B true 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) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112437138B (en) * | 2020-11-12 | 2022-03-29 | 安徽大学 | Measurement and control terminal based on NBIoT communication and communication docking and switching method thereof |
| CN112217840B (en) * | 2020-12-09 | 2021-04-13 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| CN113824795A (en) * | 2021-10-21 | 2021-12-21 | 上海波顿诺华智能科技有限公司 | Communication method, device and system of vehicle end and cloud end |
| CN113783741B (en) * | 2021-11-10 | 2022-03-11 | 云丁网络技术(北京)有限公司 | Method, device, server, gateway equipment and system for configuring gateway equipment |
Citations (6)
| 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 |
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10708270B2 (en) * | 2018-06-12 | 2020-07-07 | Sap Se | Mediated authentication and authorization for service consumption and billing |
-
2020
- 2020-04-28 CN CN202010346973.6A patent/CN111552568B/en active Active
Patent Citations (6)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552568A (en) | 2020-08-18 |
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 | |
| CN109246251B (en) | Micro-service calling method, device, system, equipment and readable storage medium | |
| EP2561656B1 (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 | |
| CN112511591B (en) | Method, device, equipment and medium for realizing hospital interface data interaction | |
| US7191232B2 (en) | Extendable provisioning mechanism for a service gateway | |
| CN110109766B (en) | Data interaction method and device based on cross-department and cross-platform data sharing exchange | |
| CN114024826B (en) | Application multi-active system based on service grid technology and used in distributed ESB scene | |
| WO2016107120A1 (en) | Application programming interface calling method and device | |
| US20020069257A1 (en) | Provisioning mechanism for a service gateway | |
| US20130275489A1 (en) | Integration of web services with a clustered actor based model | |
| CN112860462A (en) | Method, device and system for realizing interconnection and intercommunication of IOT platform bases | |
| CN113760562A (en) | Link tracking method, device, system, server and storage medium | |
| CN102790684B (en) | Service information invocation method and system and enterprise service bus server | |
| CN111953931A (en) | Data sharing method and device and storage medium | |
| CN114710311B (en) | Multi-project message management method and system | |
| JP3805197B2 (en) | Method for connecting a network element to a telecommunications system | |
| CN113360386A (en) | Switching chip drive test method, device, electronic equipment and storage medium | |
| CN114938396A (en) | Routing method of service call request, method and device for creating service | |
| CN113918245A (en) | Data calling method, device, equipment and computer readable storage medium | |
| CN114296985A (en) | Global exception handling method and platform in large-scale micro-service cluster scene | |
| CN114024822A (en) | Block chain-based Internet of things equipment management method, equipment, server and medium |
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 |