Business processing method in multi-application integration scenario

Abstract

The application provides a service processing method in a multi-application integration scene. The method first acquires an interface call request initiated by a target integration party; then converts a first service processing request into a second service processing request in a format recognizable by the target integrated party; then determines a first call interface corresponding to a second URL in the integration gateway, so as to call the first call interface to enable the target integrated party to process the second service processing request and acquire a first processing result; converts the first processing result into a second processing result in a format recognizable by the target integration party; and finally determines a second call interface corresponding to the first URL in the integration gateway, so as to send the second processing result to the target integration party through the second call interface. The method of the application improves the speed of service processing in the multi-application integration scene and improves the integration efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data processing, in particular to a business processing method in a multi-application integration scenario. BACKGROUND

[0002] In the Internet of Things business system, a Software as a Service (SaaS) platform is the last link to embody the value of Internet of Things customers. The SaaS platform can be a comprehensive application platform that meets a type of application scenario, or a specific application platform for a certain or several Internet of Things devices. To avoid repeated construction and quickly build a scenario-based SaaS platform, the most common approach is to integrate existing specific application platforms to build a complex scenario application platform.

[0003] Currently, the integration between SaaS platforms mainly adopts the opening of interfaces of both platforms, directly connects the interfaces of both platforms according to the interface specifications, and then calls the interfaces as needed to realize the correspondence or association of users, organizations, and roles between platforms. From the integrated party, the integrated party is authenticated and authorized to log in.

[0004] However, the existing integration method has the problems of complex interface connection and low integration efficiency when the integration demand is large. SUMMARY

[0005] The present application provides a business processing method in a multi-application integration scenario to solve the technical problems of complex integration interface connection and low integration efficiency in business processing.

[0006] In a first aspect, the present application provides a business processing method in a multi-application integration scenario, comprising:

[0007] An interface call request initiated by a target integrated party is obtained, the interface call request carrying a first uniform resource locator (URL) corresponding to an interface of the target integrated party, a second URL corresponding to an interface of a target integrated party to be called, and a first business processing request. The target integrated party is one of at least one integrated party, the integrated party is a scenario-based platform of a Software as a Service (SaaS) platform, and the target integrated party is one of at least one integrated party. The integrated party is an application of a SaaS platform.

[0008] The first business processing request is converted into a second business processing request in a format recognizable by the target integrated party.

[0009] determining a first calling interface corresponding to the second URL in the integration gateway, so as to call the first calling interface to make the target integrated party process the second service processing request and obtain a first processing result, wherein the integration gateway records a plurality of URLs and a calling interface corresponding to each URL;

[0010] converting the first processing result into a second processing result in a format recognizable by the target integrated party;

[0011] determining a second calling interface corresponding to the first URL in the integration gateway, so as to send the second processing result to the target integrated party through the second calling interface.

[0012] In one or more embodiments, the interface calling request further carries target credential information, wherein the target credential information is at least one credential information issued by the integration gateway to the target integrated party for accessing the integrated party;

[0013] Correspondingly, the conversion of the first service processing request into a second service processing request in a format recognizable by the target integrated party includes:

[0014] If no credential information consistent with the target credential information is determined in the at least one first credential information marked in advance, the first service processing request is converted into a second service processing request in a format recognizable by the target integrated party, wherein the first credential information is a credential information restricted for access.

[0015] In one or more embodiments, the method further includes:

[0016] If the credential information consistent with the target credential information is determined in the at least one first credential information, first information is returned to the target integrated party through the second calling interface corresponding to the first URL, wherein the first information is used to indicate the failure of the target integrated party in calling the interface of the target integrated party.

[0017] In one or more embodiments, the method further includes:

[0018] In response to the configuration operation of the administrator, the at least one credential information is configured, and the configuration includes at least one of the following: deleting a credential, adding a credential, modifying a credential, and marking a credential.

[0019] In one or more embodiments, before the interface calling request initiated by the target integrated party is obtained, the method further includes:

[0020] The at least one integrated party is respectively issued with corresponding credential information, and the at least one integrated party respectively corresponding to the credential information is recorded.

[0021] For each integrated party, after the integrated party is authenticated based on credential information of the integrated party, an interface of the integrated party and a URL corresponding to the interface of the integrated party are obtained.

[0022] In one or more embodiments, before the interface call request initiated by the target integrated party is obtained, the method further includes:

[0023] Credential information corresponding to each integrated party is issued, and the credential information corresponding to each integrated party is recorded.

[0024] For each integrated party, after the integrated party is authenticated based on credential information of the integrated party, an interface of the integrated party and a URL corresponding to the interface of the integrated party are obtained.

[0025] The interface of the integrated party and the URL corresponding to the interface of the integrated party are converted into a format recognizable by the integrated party.

[0026] In one or more embodiments, before the interface call request initiated by the target integrated party is obtained, the method further includes:

[0027] User information sent by the target integrated party through a login URL or a registration URL is obtained.

[0028] According to the login URL or the registration URL, a third URL corresponding to the target integrated party is redirected out.

[0029] The user information is sent to the target integrated party through the third URL, so that the target integrated party performs login verification processing.

[0030] In a second aspect, the application provides a business processing device in a multi-application integration scenario, including:

[0031] An obtaining module is configured to obtain an interface call request initiated by a target integrated party, the interface call request carrying a first uniform resource locator (URL) corresponding to an interface of the target integrated party, a second URL corresponding to an interface of a target integrated party called, and a first business processing request, the target integrated party being one of at least one integrated party, the integrated party being a scenario-based platform of a software as a service (SaaS) platform, the target integrated party being one of at least one integrated party, and the integrated party being an application of the SaaS platform.

[0032] A first conversion module is configured to convert the first business processing request into a second business processing request in a format recognizable by the target integrated party.

[0033] a first determining module, configured to determine a first calling interface corresponding to the second URL in the integrated gateway, so as to call the first calling interface to make the target integrated party process the second service processing request and obtain a first processing result, wherein the integrated gateway records a plurality of URLs and a calling interface corresponding to each URL;

[0034] a second converting module, configured to convert the first processing result into a second processing result in a format recognizable by the target integrated party;

[0035] a second determining module, configured to determine a second calling interface corresponding to the first URL in the integrated gateway, so as to send the second processing result to the target integrated party through the second calling interface.

[0036] In one or more embodiments, the interface calling request further carries target credential information, wherein the target credential information is at least one credential information issued by the integrated gateway for the target integrated party to access the integrated party;

[0037] Correspondingly, the first converting module is specifically configured to:

[0038] if no credential information consistent with the target credential information is determined in the at least one first credential information marked in advance, the first service processing request is converted into a second service processing request in a format recognizable by the target integrated party, wherein the first credential information is a credential information restricted for access.

[0039] In one or more embodiments, the first converting module is further configured to:

[0040] if the credential information consistent with the target credential information is determined in the at least one credential information, the first information is returned to the target integrated party through the second calling interface corresponding to the first URL, wherein the first information is used to indicate the failure of the target integrated party in calling the interface of the target integrated party.

[0041] In one or more embodiments, the first converting module is further configured to:

[0042] in response to the configuration operation of the administrator, the at least one credential information is configured, and the configuration processing includes at least one of the following: deleting a credential, adding a credential, modifying a credential, and marking a credential.

[0043] In one or more embodiments, before the interface calling request initiated by the target integrated party is obtained, the obtaining module is further configured to:

[0044] issue corresponding credential information to the at least one integrated party respectively, and record the corresponding credential information of the at least one integrated party respectively;

[0045] For each integrated party, after the integrated party is authenticated based on the credential information of the integrated party, an interface of the integrated party and a URL corresponding to the interface of the integrated party are obtained.

[0046] In one or more embodiments, before the interface call request initiated by the target integrated party is obtained, the obtaining module is further configured to:

[0047] issue corresponding credential information to the at least one integrated party respectively, and record the corresponding credential information of the at least one integrated party respectively;

[0048] For each integrated party, after the integrated party is authenticated based on the credential information of the integrated party, an interface of the integrated party and a URL corresponding to the interface of the integrated party are obtained.

[0049] The interface of the integrated party and the URL corresponding to the interface of the integrated party are converted into a format recognizable by the integrated party.

[0050] In one or more embodiments, before the interface call request initiated by the target integrated party is obtained, the obtaining module is further configured to:

[0051] Obtain user information sent by the target integrated party through a login URL or a registration URL;

[0052] According to the login URL or the registration URL, a third URL corresponding to the target integrated party is redirected out;

[0053] The user information is sent to the target integrated party through the third URL, so that the target integrated party performs login verification processing.

[0054] In a third aspect, the present application provides an integrated gateway, comprising:

[0055] A processor, and a memory connected with the processor in communication;

[0056] The memory stores computer execution instructions;

[0057] The processor executes the computer execution instructions stored in the memory to implement the method in the first aspect and any one of the embodiments.

[0058] In a fourth aspect, the present application provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and the computer execution instructions are used to implement the method in the first aspect and any one of the embodiments when executed by a processor.

[0059] In a fifth aspect, the present application provides a computer program product, comprising a computer program, and the computer program is used to implement the method for processing a service in a multi-application integration scenario when executed by a processor.

[0060] The method for processing a service in a multi-application integration scenario provided by the present application first acquires an interface call request initiated by a target integration party, wherein the interface call request carries a first uniform resource locator (URL) corresponding to an interface of the target integration party, a second URL corresponding to an interface of a target integrated party to be called, and a first service processing request; then converts the first service processing request into a second service processing request in a format recognizable by the target integrated party; then determines a first call interface corresponding to the second URL in an integration gateway, so as to call the first call interface to make the target integrated party process the second service processing request and acquire a first processing result; converts the first processing result into a second processing result in a format recognizable by the target integration party; and finally determines a second call interface corresponding to the first URL in the integration gateway, so as to send the second processing result to the target integration party through the second call interface. In the method, the integration gateway can be used to realize the scenario-based platform integration of the SaaS platform and the application of the SaaS platform, and at least one integration party can be used to integrate at least one integrated party, so that in a multi-integration application scenario, a plurality of integration parties can be used to integrate a plurality of integrated parties based on the integration gateway, thereby improving the integration efficiency; the first service processing request in the interface call request initiated by the target integration party is converted into the second service processing request in the format recognizable by the target integrated party through the integration gateway, and the first processing result of the target integrated party after the interface call is converted into the second processing result in the format recognizable by the target integration party, so that efficient interface connection can be realized through format conversion. BRIEF DESCRIPTION OF DRAWINGS

[0061] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0062] Figure 1 The flowchart of the method for processing a service in a multi-application integration scenario provided by the embodiments of the present application Figure One ;

[0063] Figure 2 The structural diagram of the method for processing a service in a multi-application integration scenario provided by the embodiments of the present application

[0064] Figure 3 Flowchart of the service processing method in the multi-application integration scenario according to an embodiment of the present application Figure Two

[0065] Figure 4 Flowchart of the service processing method in the multi-application integration scenario according to an embodiment of the present application Figure Three

[0066] Figure 5 Flowchart of the service processing method in the multi-application integration scenario according to an embodiment of the present application Figure Four

[0067] Figure 6 Flowchart of the service processing method in the multi-application integration scenario according to an embodiment of the present application Figure Five

[0068] Figure 7 Flowchart of the service processing method in the multi-application integration scenario according to an embodiment of the present application Figure Six

[0069] Figure 8 Structure diagram of the service processing device in the multi-application integration scenario according to an embodiment of the present application

[0070] Figure 9 Structure diagram of the integrated gateway according to an embodiment of the present application

[0071] The specific embodiments of the present application have been shown through the above-described drawings, and will be described in more detail hereinafter. The drawings and the written description are not intended to restrict the scope of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0072] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The same reference numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all the implementations consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0073] ​​​​​It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards, and provide corresponding operation portal for user to choose authorization or refusal.

[0074] Firstly, the terms involved in the present application are explained:

[0075] Software as a Service (SaaS): refers to a service mode based on cloud computing, which allows users to access and use software applications through the Internet without installing and maintaining the software on local devices. SaaS platform is usually hosted by service providers, and is responsible for software maintenance, update, security and infrastructure management;

[0076] Uniform Resource Identifier (URI): refers to a string used to identify the name of an Internet resource, allowing users to interact with any (including local and Internet) resource through a specific protocol;

[0077] Callback URL: refers to when a certain action or event is triggered, the system will send relevant information to a URL address hosted on a remote server, which is the callback URL;

[0078] Customer Premises Equipment (CPE) platform: refers to the equipment and platform provided by the communication service provider or enterprise to support the service in the client environment;

[0079] ClientId: refers to a public identifier, used to identify an application or client;

[0080] ClientSecret: refers to a secret key, which is used in pairs with ClientId, and is only provided to the client and the authentication server to protect the identity information of the client;

[0081] Authentication: refers to confirming the identity of a user or system, verifying whether the identity of a user is legal;

[0082] Authorization: refers to verifying whether a user has the right to access certain resources or perform certain operations;

[0083] Hypertext Transfer Protocol (HTTP): is an application layer protocol, can refer to a simple request-response protocol, the main role is to allow the client to request resources from the server through the network, and the server returns the resources to the client;

[0084] REST interface: refers to a set of interface rules based on HTTP protocol, which uses HTTP protocol request type and message parameter definition;

[0085] Simple Object Access Protocol (SOAP) protocol: is a protocol based on eXtensible Markup Language (XML), used for message transmission on the Web, allowing applications to interact in a distributed environment, and supporting communication between different operating systems and programming languages;

[0086] POST request: is a request method in HTTP protocol, used to submit data to a specified resource;

[0087] Redirection: refers to the process of directing user requests to another page by the server, which can be used for URL changes, page jumps and access control scenarios.

[0088] Secondly, the technical background of the present application is explained:

[0089] In the Internet of Things business system, the Software as a Service (SaaS) platform is the last link to realize the value of Internet of Things customers. The SaaS platform can be a comprehensive application that meets a class of application scenarios, or a specific application for a certain or several Internet of Things devices. In order to avoid repeated construction and quickly build a scenario-based SaaS platform, the most common practice is to integrate existing specific applications and build complex scenario applications.

[0090] Currently, the integration between SaaS platforms mainly adopts the open interface of both platforms, and directly connects the interfaces of both platforms according to the interface specification. Then, according to the needs, the interface is called to realize the correspondence or association of users, organizations and roles between platforms. From the integrated party to the integrated party, the integrated party is authenticated and authorized to log in.

[0091] However, when the integration demand is large, the existing integration method needs to be debugged by the integrated party every time, resulting in complex interface connection and low integration efficiency.

[0092] The method for service processing in a multi-application integration scenario provided in the application aims to solve the above technical problems of the prior art. The inventive concept of the application is as follows: in a multi-integration scenario, the interface formats of different integrated parties can be different, and the existing integration method needs to debug the interfaces of the integrated parties each time integration is performed, and then realizes the interface docking of the integrated party to the integrated party, which can cause the problem of low integration efficiency. Through the integration gateway, the interface formats of different integrated parties can be converted according to a unified format standard, and after the interface with a unified format is obtained, the integrated party is faced, when the integrated party performs interface calling, the integrated party interface with a standard format in the integration gateway is accessed, which can effectively improve the integration efficiency between different integrated parties and different integrated parties. At the same time, the integration gateway issues credential information to the target integrated party and the target integrated party, identifies the target integrated party and the target integrated party according to the issued credential information, and performs authentication, which can ensure the information security when the target integrated party and the target integrated party interact.

[0093] The technical solutions of the application and how the technical solutions of the application solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described again in some embodiments. The embodiments of the application will be described below with reference to the drawings.

[0094] Figure 1 The flowchart of the method for service processing in a multi-application integration scenario provided in the embodiments of the application Figure One . As shown in Figure 1 , the execution subject of the method for service processing in a multi-application integration scenario is an integration gateway, which includes the following steps:

[0095] The integration gateway can be a capability integration platform.

[0096] S110, obtaining an interface calling request initiated by a target integrated party;

[0097] The interface calling request carries a first uniform resource locator URL corresponding to the interface of the target integrated party, a second URL corresponding to the interface of the called target integrated party, and a first service processing request. The target integrated party is one of at least one integrated party, the integrated party is a scenario-based platform of a software as a service (SaaS) platform, the target integrated party is one of at least one integrated party, and the integrated party is an application of the SaaS platform.

[0098] In this step, first, the target integrated party is determined in at least one integrated party, and the target integrated party is determined in at least one integrated party according to the service function required by the target integrated party, then according to the interface provided by the target integrated party and the target integrated party, the first uniform resource locator URL corresponding to the interface of the target integrated party and the second URL corresponding to the interface of the called target integrated party are obtained, and then the interface calling request is constructed by combining the first business processing request of the target integrated party, the interface calling request is initiated by the target integrated party, and the integrated gateway obtains the interface calling request initiated by the target integrated party.

[0099] For example, the first business request refers to the specific content of the business processing initiated by the target integrated party to the target integrated party, including business data or request parameters, and can require the target integrated party to perform an operation or provide a service.

[0100] In a possible implementation, the integrated party can be a SaaS platform of a scenario service constructed according to different application scenarios, for example, a smart building platform can provide a complete building intelligent solution, including building management, resource management, security monitoring and other service functions; a smart city platform can provide a comprehensive platform for city management, including traffic management, environmental monitoring and other service functions; a smart hotel platform can provide intelligent services for hotels, including environmental monitoring, security door locks and other service functions.

[0101] The integrated party can be an application of a SaaS platform including at least one Internet of Things device, for example, a video monitoring platform application can provide real-time video monitoring, video storage, event alarm and other functions, including monitoring cameras, video recorders, sensors and other Internet of Things devices; a customer premises equipment (CPE) platform application can provide user management, configuration and other functions for specific application devices, including routers, switches and other Internet of Things devices; a door lock platform application can provide remote control, monitoring and other functions for various smart door locks, including smart door locks, sensors and other Internet of Things devices.

[0102] For example, taking the smart hotel platform as the target integrated party, the target integrated party can be a video monitoring platform, a door lock platform and the like, which requires to provide environmental monitoring, security door lock and other service functions.

[0103] S120, convert the first business processing request into a second business processing request in a format recognizable by the target integrated party.

[0104] In this step, the integrated gateway parses the interface call request of the target integrated party obtained to obtain a first service request. The service processing request formats of the target integrated party and the target integrated party are different. The first service processing request sent by the target integrated party needs to be converted to obtain a second service processing request that can be recognized by the target integrated party. The integrated gateway converts the request format according to the request format of the target integrated party to obtain a second service processing request in a format that can be recognized by the target integrated party.

[0105] In a possible implementation, converting the first service processing request can include converting the fields in the request into a request field format that can be recognized by the target integrated party, and converting the content in the request into a request content format that can be recognized by the target integrated party, and then combining the converted fields and request content into the second service processing request.

[0106] For example, if the format of the first service processing request is (user_id: "12345", action: "login", Timestamp: "3333-22-11T00:01:02Z"), and the request format that can be recognized by the target integrated party is (user_id: "12345", event_type: "user_login", event_time: "3333-22-11T00:01:02Z"), then the field name is converted from "action" to "event_type", "Timestamp" is converted to "event_time", and the request content format is converted from "login" to "user_login".

[0107] S130, determining the first call interface corresponding to the second URL in the integrated gateway to call the first call interface to make the target integrated party process the second service processing request and obtain a first processing result;

[0108] The integrated gateway records a plurality of URLs and a call interface corresponding to each URL.

[0109] In this step, according to the plurality of URLs and the call interface corresponding to each URL recorded in the integrated gateway, the first call interface corresponding to the second URL can be determined in the integrated gateway according to the second URL. Then, by calling the first call interface, the target integrated party can process the obtained second service processing request, perform corresponding processing according to the content of the second service processing request, and take the processing result as the first processing result.

[0110] In a possible implementation, the first processing result is generated according to a format of a processing result of the target integrated party. The first processing result can include processing status information, a data processing result, response data, processing time, and the like.

[0111] For example, the processing status information can include whether the request is successfully processed, whether there is an error or exception, and the like, and a status code can be used to indicate success or failure.

[0112] The data processing result can include a specific business logic result, such as business data, a calculation result, or processed information, and can be structured data or unstructured data.

[0113] The response data can be return data from the first calling interface, such as an analysis result, an application execution result, and the like.

[0114] The processing time can include a timestamp, a start time, an end time, and a response time of the first calling interface of the second business processing request.

[0115] S140, converting the first processing result into a second processing result in a format recognizable by the target integrated party.

[0116] In this step, the integrated gateway parses the first processing result obtained from the target integrated party. The first processing result sent by the target integrated party needs to be converted into a second processing result recognizable by the target integrated party, because the processing result formats of the target integrated party and the target integrated party are different. The integrated gateway converts the first processing result according to the processing result format of the target integrated party, to obtain the second processing result in a format recognizable by the target integrated party.

[0117] In a possible implementation, converting the first processing result can include converting a data format of the processing result, such as converting a binary format into a text format, and can also include converting a field in the processing result into a processing result field format recognizable by the target integrated party, and converting a data format in the processing result content into a processing result content format recognizable by the target integrated party.

[0118] For example, if the format of the first business processing result is (order_id: “222”, status: “success”, order_date: “2020-01-01”, order_content: “order content”)

[0119] For example, if the first business processing request is in the format of {order_id: "11-22-33T00:01:02Z", status: "success", order_date: "11-22-33"}, and the target integrated party can identify the request in the format of {order_number: "222", order_status: "Success", order_time: "11-22-33-00:01:02"}, the field name is converted from "order_id" to "order_number", "status" to "order_status", and "order_date" to "order_time", and the processing result content format is converted from "success" to "Success" (capitalized first letter), and "11-22-33T00:01:02Z" to "11-22-33-00:01:02".

[0120] S150, determining, in the integration gateway, a second calling interface corresponding to the first URL, so as to send the second processing result to the target integrated party through the second calling interface.

[0121] In this step, according to the first URL and the corresponding calling interface recorded by the integration gateway, the calling interface corresponding to the first URL is determined in the integration gateway and recorded as a second calling interface, and then the second processing result can be sent to the target integrated party by calling the second calling interface.

[0122] In a possible implementation, Figure 2 The structure diagram of the business processing provided for this embodiment is shown in FIG. 1. Figure 2 As shown in FIG. 1, at least one integrated party and at least one integrated party are connected with the integration gateway respectively, and the access connection between the integrated party and the integrated party is realized through the integration gateway.

[0123] In this embodiment, the integrated party is a scenario platform of a software as a service (SaaS) platform, and the integrated party is an application of the SaaS platform. The integration gateway has an authentication function, a format conversion function, and an access management function.

[0124] In a possible implementation, the interface calling request further carries target credential information, and the target credential information is at least one credential information issued by the integration gateway for the target integrated party to access the integrated party.

[0125] Correspondingly, converting the first business processing request into a second business processing request in a format recognizable by the target integrated party includes: if no credential information consistent with the target credential information is determined in the at least one first credential information marked in advance, converting the first business processing request into a second business processing request in a format recognizable by the target integrated party, and the first credential information is a credential information restricted from being accessed.

[0126] Exemplarily, the integrated gateway can issue credential information for the integrated party, the target credential information is at least one credential information issued by the integrated gateway for the target integrated party to access the integrated party, and the first credential information is the credential information restricted from being accessed, i.e., the integrated party with the first credential information cannot access the integrated party.

[0127] The integrated gateway compares the target credential information carried in the interface call request with the at least one first credential information marked in advance, and if no credential information consistent with the target credential information is determined in the at least one first credential information marked in advance, the integrated gateway converts the first service processing request into a second service processing request in a format recognizable by the target integrated party.

[0128] In a possible implementation, the credential information issued by the integrated gateway to the target integrated party can be a combination of ClientId and ClientSecret, the ClientId uniquely identifies the target integrated party, and the target integrated party sends the ClientSecret to the integrated gateway for verification. If the ClientSecret is not the credential information restricted from being accessed marked in advance, the target integrated party can access the integrated party through the integrated gateway.

[0129] In a possible implementation, if the credential information consistent with the target credential information is determined in the at least one first credential information, the first information is returned to the target integrated party through the second call interface corresponding to the first URL, and the first information is used to indicate the failure of the target integrated party in calling the interface of the target integrated party.

[0130] Exemplarily, the integrated gateway compares the target credential information with the at least one first credential information, if the credential information consistent with the target credential information is determined in the at least one first credential information, it indicates that the target credential information is restricted from being accessed, and the corresponding target integrated party cannot access the integrated party through the target credential information. The integrated gateway can return the first information to the target integrated party through the second call interface corresponding to the first URL, indicating the failure of the target integrated party in calling the interface of the target integrated party.

[0131] In a possible implementation, the target integrated party sends the ClientSecret to the integrated gateway for verification, if the ClientSecret is the credential information restricted from being accessed marked in advance, the first information is sent back to the callback URL of the target integrated party through the second call interface corresponding to the first URL, indicating the failure of the target integrated party in calling the interface of the target integrated party.

[0132] In a possible implementation, the at least one credential information is configured in response to a configuration operation of the administrator, and the configuration operation includes at least one of deleting a credential, adding a credential, modifying a credential, and marking a credential.

[0133] For example, the administrator can perform a configuration operation on the at least one credential information, and the at least one credential information is configured in response to the configuration operation of the administrator by the integrated gateway,

[0134] In a possible implementation, deleting a credential can be deleting an already issued credential information, adding a credential can be the integrated gateway issuing a new credential information to the integrated party, modifying a credential can be modifying the content of the ClientId or ClientSecret in the already issued credential information, and marking a credential can be adding a mark to the credential information, such as adding a mark to identify whether the credential information is limited in access.

[0135] The method provided by the embodiment of the application for processing a service in a multi-application integration scenario first acquires an interface call request initiated by a target integrated party, wherein the interface call request carries a first uniform resource locator (URL) corresponding to an interface of the target integrated party, a second URL corresponding to an interface of a target integrated party to be called, and a first service processing request, the target integrated party is one of at least one integrated party, the integrated party is a scenario platform of a software as a service (SaaS) platform, and the target integrated party to be called is one of at least one integrated party, the integrated party being an application of the SaaS platform; then, the first service processing request is converted into a second service processing request in a format recognizable by the target integrated party to be called; then, a first call interface corresponding to the second URL is determined in an integrated gateway, so that the first call interface is called to enable the target integrated party to be called to process the second service processing request and acquire a first processing result, wherein the integrated gateway records a plurality of URLs and a call interface corresponding to each URL; the first processing result is converted into a second processing result in a format recognizable by the target integrated party; finally, a second call interface corresponding to the first URL is determined in the integrated gateway, so that the second processing result is sent to the target integrated party through the second call interface. In the embodiment, the scenario platform of the SaaS platform can integrate the application of the SaaS platform through the integrated gateway, and at least one integrated party can integrate at least one integrated party to be called, so that a plurality of integrated parties can integrate a plurality of integrated parties to be called based on the integrated gateway in a multi-integrated application scenario, thereby improving the integration efficiency; the first service processing request in the interface call request initiated by the target integrated party is converted into the second service processing request in the format recognizable by the target integrated party to be called through the integrated gateway, and the first processing result of the target integrated party to be called after the interface call is converted into the second processing result in the format recognizable by the target integrated party, so that efficient interface connection can be realized through the format conversion.

[0136] On the basis of the above embodiments, Figure 3 The flowchart of the service processing method in the multi-application integration scenario provided by the embodiments of the present application is shown in Figure Two As shown in Figure 3 The service processing method in the multi-application integration scenario further includes the following steps:

[0137] S310, issuing corresponding credential information to at least one integration party respectively, and recording the credential information corresponding to the at least one integration party respectively.

[0138] In this step, the credential information corresponding to different integration parties is different, and the integration gateway issues corresponding credential information to at least one integration party respectively, and records the credential information corresponding to the at least one integration party respectively.

[0139] In a possible implementation, the integration gateway can issue corresponding credential information to at least one integration party respectively, which can be a combination of ClientId and ClientSecret, wherein the integration party is uniquely identified by ClientId, and the integration party is authenticated according to ClientSecret.

[0140] For example, the integration gateway issues credential information ClientId_A and ClientSecret_A to integration party A, issues credential information ClientId_B and ClientSecret_B to integration party B, and issues credential information ClientId_C and ClientSecret_C to integration party C.

[0141] S320, for each integration party, after the integration party is authenticated based on the credential information of the integration party, obtaining the interface of the integration party and the URL corresponding to the interface of the integration party.

[0142] In this step, for each integration party, the integration gateway authenticates the integration party according to the credential information of the integration party, and when the authentication is passed, the interface of the integration party and the URL corresponding to the interface of the integration party are obtained.

[0143] In a possible implementation, the integration gateway can identify the integration party through ClientId, and then send ClientSecret to the integration gateway by the integration party. The integration gateway authenticates and verifies the integration party based on the recorded ClientId and ClientSecret of the integration party. If the ClientSecret of the integration party is consistent with the recorded ClientSecret, the verification is passed.

[0144] For example, further illustrated by the above example, for the integration party A, first, the integration party A is identified according to the ClientId_A of the credential information of the integration party A, and then the integration party A sends the ClientSecret_D to the integration gateway, which is inconsistent with the ClientSecret_A of the integration party A that has been recorded, and thus the verification fails; for the integration party B, the integration party B is identified according to the ClientId_B of the credential information of the integration party B, and then the integration party B sends the ClientSecret_B to the integration gateway, which is consistent with the ClientSecret_B of the integration party B that has been recorded, and thus the verification passes, and the integration gateway acquires the interface of the integration party B and the URL corresponding to the interface of the integration party B.

[0145] The business processing method in the multi-application integration scenario provided by the embodiments of the present application first issues corresponding credential information to at least one integration party and records the credential information corresponding to the at least one integration party, and then, for each integration party, acquires the interface of the integration party and the URL corresponding to the interface of the integration party after the integration party is authenticated based on the credential information of the integration party. In the embodiments, by issuing and recording the corresponding credential information of the at least one integration party, the corresponding integration party can be identified according to the credential information, and the effectiveness of the credential information is ensured; by authenticating the credential information of the integration party, the rights of the integration party can be managed, and when the authentication passes, the interface of the integration party and the URL corresponding to the interface of the integration party can be acquired, thereby improving the security of integration.

[0146] On the basis of the above embodiments, Figure 4 The flowchart of the business processing method in the multi-application integration scenario provided by the embodiments of the present application is shown in Figure Three . As shown in Figure 4 , the business processing method in the multi-application integration scenario further includes the following steps:

[0147] S410, corresponding credential information is issued to at least one integrated party, and the credential information corresponding to the at least one integrated party is recorded.

[0148] In this step, the credential information corresponding to different integrated parties is different, and the integration gateway issues corresponding credential information to at least one integrated party, and records the credential information corresponding to the at least one integrated party.

[0149] In one possible implementation, the integration gateway can issue corresponding credential information to at least one integrated party, which can be a combination of ClientId and ClientSecret, wherein the integrated party is uniquely identified by ClientId, and the integrated party is authenticated according to ClientSecret.

[0150] For example, the integrated gateway issues credential information Clientldl and ClientSecretl to integrated party 1, and issues credential information Clientld2 and ClientSecret2 to integrated party 2.

[0151] S420, for each integrated party, after the integrated party is authenticated based on the credential information of the integrated party, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained.

[0152] In this step, for each integrated party, the integrated gateway authenticates according to the credential information of the integrated party, and when the authentication is passed, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained.

[0153] In a possible implementation, the integrated gateway identifies the integrated party through Clientld, and the integrated party sends ClientSecret to the integrated gateway. The integrated gateway authenticates the integrated party based on the Clientld and ClientSecret of the integrated party as described above. If the ClientSecret of the integrated party is consistent with the ClientSecret as described above, the authentication is passed.

[0154] For example, further illustrated by the above example, for integrated party 1, first, the integrated party is identified according to the Clientldl of the credential information of integrated party 1. Integrated party 1 sends ClientSecret3 to the integrated gateway, which is inconsistent with the ClientSecretl of integrated party 1 as described above, and the authentication fails. For integrated party 2, the integrated party is identified according to the Clientld2 of the credential information of integrated party 2. Then integrated party 2 sends ClientSecret2 to the integrated gateway, which is consistent with the ClientSecret2 of integrated party 2 as described above, and the authentication is passed. The integrated gateway obtains the interface of integrated party B and the URL corresponding to the interface of integrated party B.

[0155] S430, the interface of the integrated party and the URL corresponding to the interface of the integrated party are format-converted to obtain a format recognizable by the integrated party.

[0156] In this step, the format of the interface of the integrated party and the URL corresponding to the interface of the integrated party is different from that of the integrated party. The integrated gateway converts the format of the interface of the integrated party and the URL corresponding to the interface of the integrated party to obtain the interface in a format recognizable by the integrated party and the corresponding URL.

[0157] In a possible implementation, the format conversion of the interface of the integrated party and the URL corresponding to the interface of the integrated party by the integrated gateway can include conversion of the interface protocol, conversion of the URL path format, etc.

[0158] For example, if the interface of the integrated party is a REST interface based on the HTTP protocol, and the interface of the integrated party is a SOAP interface based on the XML protocol, protocol conversion needs to be performed through the corresponding service framework;

[0159] If the URL path format of the integrated party is / users / (userId) / orders, and the URL path format of the integrated party is / getOrders?id=(userId), the URL path format of the integrated party needs to be converted into the URL path format of the integrated party.

[0160] The business processing method in the multi-application integration scenario provided by the embodiment of the present application first issues corresponding credential information to at least one integrated party, and records the credential information corresponding to each integrated party. Then, for each integrated party, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained after the integrated party is authenticated based on the credential information of the integrated party. Finally, the interface of the integrated party and the URL corresponding to the interface of the integrated party are converted in format to obtain a format recognizable by the integrated party. In this embodiment, by issuing unique credential information to each integrated party and recording the credential information, it is ensured that only the integration gateway that passes the verification can integrate the functions of the integrated party. The integrated party can obtain its interface and the corresponding URL only after authentication, which can improve the security of integration. By converting the format of the interface of the integrated party and the corresponding URL into a format recognizable by the integrated party, the integrated party can flexibly cope with the technical requirements and interface specifications of different integrated parties, and the efficiency of integration is improved.

[0161] On the basis of the above embodiment, Figure 5 The flowchart of the business processing method in the multi-application integration scenario provided by the embodiment of the present application is shown in Figure Four . As Figure 5 shown, the business processing method in the multi-application integration scenario further includes the following steps:

[0162] S510, obtaining user information sent by the target integrated party through a login URL or a registration URL.

[0163] In this step, the target integrated party provides a login interface or a registration interface. The login interface corresponds to a login URL, and the registration interface corresponds to a registration URL. The target integrated party sends user information while accessing the integration gateway through the login URL or the registration URL, and the integration gateway obtains the user information sent by the target integrated party.

[0164] In a possible implementation, the user information can include a unique identifier of the user and user data, the user data can include a login password of the user or registration information of the user, the login URL can be a POST request for sending the unique identifier of the user and the user data to the integration gateway, and the registration URL can be a POST request for sending the user information and the registration information of the user to the integration gateway.

[0165] For example, the user information can include a unique identifier "user-id: 1122" of the user, a username "user-name: max", a login password "user-code: 35526" of the user, and a registration verification code "user-token: 5858" of the user.

[0166] S520, redirecting a third URL corresponding to the target integrated party according to the login URL or the registration URL.

[0167] In this step, the integration gateway parses the login URL or the registration URL, determines the target integrated party to which the user information needs to be transmitted, and determines an interface corresponding to the login URL or the registration URL provided by the target integrated party, and then redirects a third URL corresponding to the target integrated party according to the URL corresponding to the interface.

[0168] For example, the third URL refers to a URL in the target integrated party that can receive the user information and return a processing result in connection with the login URL or the registration URL of the target integrated party.

[0169] S530, transmitting the user information to the target integrated party through the third URL, so that the target integrated party performs login verification processing.

[0170] In this step, the target integrated party pre-stores user information of a historical login user, and after receiving the user information through the third URL, the target integrated party parses the received user information and compares the parsed user information with the user information of the historical login user to perform login verification.

[0171] In a possible implementation, after the third URL sends the user information to the target integrated party, the target integrated party parses the user information to obtain a unique identifier and a username of the user, identifies the unique identifier of the user in the historical login user information according to the unique identifier of the user, and if the unique identifier of the user is identified, further acquires a user login password through the third URL and verifies whether the user login password is correct, if the user login password is correct, the current user successfully logs in the target integrated party, otherwise, the login fails; if the unique identifier of the current user is not identified in the historical login user information, the user can be registered through a user registration verification code, and after the user is successfully registered, the login can be further verified according to the user login password.

[0172] Further, when the user successfully logs in the target integrated party, an interface call request is sent to the target integrated party, the target integrated party parses the interface call request and performs corresponding business processing, generates a processing result after the business processing is completed, and returns the generated processing result to the target integrated party through the third URL.

[0173] The business processing method in the multi-application integration scenario provided by the embodiment of the application first acquires user information sent by a target integrated party through a login URL or a registration URL, then redirects a third URL corresponding to the target integrated party according to the login URL or the registration URL, and finally sends the user information to the target integrated party through the third URL, so that the target integrated party performs login verification processing. In the embodiment, the target integrated party can send user information through a login URL or a registration URL, and can redirect a third URL corresponding to the target integrated party. Based on the redirection, the target integrated party can be guided to the correct target integrated party, and after the login verification is completed, the target integrated party can quickly jump back to the login URL or the registration URL of the target integrated party, so that the business processing speed in the integration can be accelerated. After the user information is sent to the target integrated party through the third URL, the target integrated party performs login verification processing. The login verification on the user information can ensure the security of the user information.

[0174] On the basis of the above embodiment, Figure 6 The flowchart of the business processing method in the multi-application integration scenario provided by the embodiment of the application is as follows Figure Five . As shown in the figure, the business processing method in the multi-application integration scenario further includes the following steps: Figure 6

[0175] Step 1, the integrated gateway issues credential information to the target integrated party.

[0176] The credential information can be a combination of ClientId and ClientSecret.

[0177] ​Step 2, the target integrated party accesses the integration gateway after authentication and authorization according to the obtained credential information, and provides the interfaces of the target integrated party and the URLs corresponding to the interfaces to the integration gateway.

[0178] The interfaces of the target integrated party can include a user login interface, a user registration interface, a callback interface, etc., and the URLs corresponding to the interfaces respectively include a user login URL, a user registration URL, and a callback URL, etc.

[0179] Step 3, the integration gateway converts the interfaces of the target integrated party to obtain interfaces with a unified standard format and the URLs corresponding to the interfaces.

[0180] In a possible implementation, the interfaces of different integrated parties have different formats, and the interfaces with a unified standard format after conversion can improve integration efficiency.

[0181] Step 4, the integration gateway issues target credential information to the target integrated party.

[0182] The target credential information can be a combination of a ClientId and a ClientSecret.

[0183] Step 5, the target integrated party accesses the integration gateway after authentication and authorization according to the obtained target credential information.

[0184] The target integrated party can provide interfaces with a standard format and the URLs corresponding to the interfaces, and the interfaces can include a user login interface and a user registration interface, and the URLs corresponding to the interfaces respectively include a user login URL and a user registration URL.

[0185] Step 6, the target integrated party sends an interface call request to the integration gateway.

[0186] The interface call request includes a first URL corresponding to an interface of the target integrated party, target credential information of the target integrated party, a first business processing request of the target integrated party, and a second URL corresponding to an interface of the target integrated party.

[0187] Step 7, the integration gateway receives and parses the interface call request, and determines whether the target credential information of the target integrated party is consistent with the pre-marked credential information that is restricted from being accessed. If the target credential information is not consistent with the pre-marked credential information that is restricted from being accessed, the integration gateway returns a call success to the target integrated party through the callback URL, otherwise, the integration gateway returns a call failure to the target integrated party through the callback URL.

[0188] Further, Figure 7 A flowchart of a business processing method in a multi-application integration scenario is provided for the embodiment Figure Six . As Figure 7As shown, when the return call is successful to the target integrated party, the following steps are further included:

[0189] Step 1, the target integrated party sends an interface call request to the integration gateway;

[0190] Step 2, the integration gateway converts the interface call request into a format recognizable by the target integrated party;

[0191] Step 3, the integration gateway sends the interface call request after format conversion to the target integrated party, and calls the interface of the target integrated party in the unified format;

[0192] Step 4, the target integrated party processes the received interface call request after format conversion to obtain a first processing result;

[0193] Step 5, the target integrated party converts the obtained first processing result into a format recognizable by the target integrated party to obtain a second processing result;

[0194] Step 6, the integration gateway receives the second processing result and returns it to the target integrated party.

[0195] The business processing method in the multi-application integration scenario provided by the embodiment of the present application can ensure the information security when the target integrated party and the target integrated party interact by issuing credential information to the target integrated party and the target integrated party by the integration gateway, identifying the target integrated party and the target integrated party according to the issued credential information, and performing authentication. The integration gateway can convert the interface call request sent by the target integrated party into a format recognizable by the target integrated party, and convert the first processing result obtained by the target integrated party into a format recognizable by the target integrated party, so that the integration gateway has the function of format conversion, and the efficiency of integration between different integrated parties and integrated parties can be improved.

[0196] On the basis of the above embodiment, the following is the device embodiment related by the present application:

[0197] Figure 8 The structure diagram of the business processing device in the multi-application integration scenario provided by the embodiment of the present application is shown in the figure. Figure 8 As shown, the business processing device 800 in the multi-application integration scenario includes:

[0198] The acquisition module 810 is configured to acquire an interface call request initiated by a target integrated party, the interface call request carrying a first uniform resource locator URL corresponding to an interface of the target integrated party, a second URL corresponding to an interface of a called target integrated party, and a first business processing request, the target integrated party being one of at least one integrated party, the integrated party being a scenario platform of a software as a service (SaaS) platform, the target integrated party being one of at least one integrated party, and the integrated party being an application of the SaaS platform.

[0199] The first conversion module 820 is configured to convert the first service processing request into a second service processing request in a format recognizable by the target integrated party;

[0200] The first determination module 830 is configured to determine, in the integration gateway, a first calling interface corresponding to the second URL, so as to call the first calling interface to enable the target integrated party to process the second service processing request and obtain a first processing result, and the integration gateway records a plurality of URLs and calling interfaces corresponding to each URL;

[0201] The second conversion module 840 is configured to convert the first processing result into a second processing result in a format recognizable by the target integrated party;

[0202] The second determination module 850 is configured to determine, in the integration gateway, a second calling interface corresponding to the first URL, so as to send the second processing result to the target integrated party through the second calling interface.

[0203] In an optional embodiment, the interface calling request further carries target credential information, and the target credential information is at least one credential information issued by the integration gateway to the target integrated party for accessing the integrated party;

[0204] Correspondingly, the first conversion module 820 is specifically configured to:

[0205] If no credential information consistent with the target credential information is determined in the at least one first credential information marked in advance, the first service processing request is converted into a second service processing request in a format recognizable by the target integrated party, and the first credential information is a credential information restricted from being accessed.

[0206] In an optional embodiment, the first conversion module 820 is further configured to:

[0207] If the credential information consistent with the target credential information is determined in the at least one first credential information, the first information is returned to the target integrated party through the second calling interface corresponding to the first URL, and the first information is used to indicate the failure of the target integrated party in calling the interface of the target integrated party.

[0208] In an optional embodiment, the first conversion module 820 is further configured to:

[0209] In response to a configuration operation of the administrator, the at least one credential information is configured, and the configuration processing includes at least one of the following: deleting a credential, adding a credential, modifying a credential, and marking a credential.

[0210] In an optional embodiment, before the interface calling request initiated by the target integrated party is obtained, the obtaining module 810 is further configured to:

[0211] issue the corresponding credential information to the at least one integrated party respectively, and record the credential information corresponding to the at least one integrated party respectively;

[0212] For each integrated party, after the integrated party is authenticated based on the credential information of the integrated party, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained.

[0213] In an optional embodiment, before obtaining the interface call request initiated by the target integrated party, the obtaining module 810 is further configured to:

[0214] issue the corresponding credential information to the at least one integrated party respectively, and record the credential information corresponding to the at least one integrated party respectively;

[0215] For each integrated party, after the integrated party is authenticated based on the credential information of the integrated party, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained.

[0216] The interface of the integrated party and the URL corresponding to the interface of the integrated party are format-converted to obtain a format recognizable by the integrated party.

[0217] In an optional embodiment, before obtaining the interface call request initiated by the target integrated party, the obtaining module 810 is further configured to:

[0218] Obtain the user information sent by the target integrated party through the login URL or the registration URL;

[0219] According to the login URL or the registration URL, the third URL corresponding to the target integrated party is redirected out;

[0220] The user information is sent to the target integrated party through the third URL, so that the target integrated party performs login verification processing.

[0221] On the basis of the above embodiments, Figure 9 The structure diagram of the integrated gateway provided in the embodiments of the present application is shown in the figure. Figure 9 As shown in the figure, the integrated gateway 900 includes a processor 910, a memory 920 and a bus 930;

[0222] The entity corresponding to the integrated gateway can be an electronic device related to the integrated gateway.

[0223] The memory 920 is used to store the computer execution instructions of the processor 910;

[0224] The processor 910 is configured to execute the technical solutions of any one of the preceding method embodiments by executing the computer execution instructions.

[0225] Optionally, the memory 920 can be independent or integrated with the processor 910.

[0226] Optionally, the memory 920 can include a random access memory (RAM) and can also include a non-volatile memory (NVM), such as at least one disk memory.

[0227] The bus 930 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in the drawings of the present application, but it does not mean that there is only one bus or only one type of bus.

[0228] The processor described above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), and the like; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

[0229] The integrated gateway is used to execute the technical solutions of any of the preceding method embodiments, and has similar implementation principles and technical effects, which will not be described here.

[0230] The embodiments of the present application also provide a computer readable storage medium, which stores computer execution instructions, and the computer execution instructions are used to implement the technical solutions provided by any of the preceding method embodiments when executed by a processor.

[0231] The embodiments of the present application also provide a computer program product, which includes a computer program and a computer instruction stored in a computer readable storage medium, and the computer program is used to implement the technical solutions provided by any of the preceding method embodiments when executed by a processor.

[0232] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all described as a combination of a series of actions, but those skilled in the art should know that the present application is not limited to the order of the actions described, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0233] Further, it should be noted that although each step in the flowchart is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in sequence according to the direction of the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed in rotation or alternation with other steps or sub-steps or stages of other steps.

[0234] It should be understood that the above-described device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and actual implementation can have another division method. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be omitted or not executed.

[0235] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application can be integrated in one unit / module, or each unit / module can exist physically, or two or more units / modules can be integrated together. The integrated unit / module can be realized in the form of hardware or in the form of a software program module.

[0236] If the integrated units / modules are implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the storage unit can be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0237] If the integrated units / modules are implemented in the form of software program modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the essential part or all or part of the technical solutions that make contributions to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0238] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combination of the technical features does not exist contradictory, it should be considered as the scope of the present application

[0239] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0240] It is to be understood that the application is not limited to the precise construction herein disclosed and shown in the drawings, and that various changes in shape, size and arrangements of parts can be made without departing from the scope of the application. The scope of the application is limited only by the claims that follow.

Claims

1. A business processing method in a multi-application integration scenario, characterized in that, Applied to an integrated gateway, the method includes: Obtain the interface call request initiated by the target integrator. The interface call request carries the first Uniform Resource Locator URL corresponding to the interface of the target integrator, the second URL corresponding to the interface of the target integrator being called, and the first business processing request. The target integrator is one of at least one integrator, which is a scenario-based platform of the Software as a Service (SaaS) platform. The target integrator is one of at least one integrator, which is an application of the SaaS platform. The first business processing request is converted into a second business processing request in a format recognizable by the target integration party; The integration gateway determines the first call interface corresponding to the second URL, and calls the first call interface to enable the target integrated party to process the second business processing request and obtain the first processing result. The integration gateway records multiple URLs and the call interface corresponding to each URL. The first processing result is converted into a second processing result in a format recognizable by the target integrator; The second calling interface corresponding to the first URL is determined in the integration gateway, so that the second processing result is sent to the target integrator through the second calling interface.

2. The method according to claim 1, characterized in that, The interface call request also carries target credential information, which is at least one credential issued by the integration gateway to the target integrator for accessing the integrator. Accordingly, the step of converting the first service processing request into a second service processing request in a format recognizable by the target integration party includes: If no credential information matching the target credential information is found among at least one pre-marked first credential information, the first business processing request is converted into a second business processing request in a format recognizable by the target integrated party, wherein the first credential information is credential information with restricted access.

3. The method according to claim 2, characterized in that, The method further includes: If a credential that matches the target credential is identified among the at least one first credential information, the first information is returned to the target integrator through the second calling interface corresponding to the first URL. The first information is used to indicate the failure of the target integrator to call the interface of the target integrator.

4. The method according to claim 2 or 3, characterized in that, The method further includes: In response to the configuration operation of the administrator, the at least one voucher information is configured, and the configuration process includes at least one of the following: deleting voucher, adding voucher, modifying voucher, and marking voucher.

5. The method according to any one of claims 1-3, characterized in that, Before obtaining the interface call request initiated by the target integrator, the method further includes: Issue corresponding credential information to each of the at least one integrator and record the credential information corresponding to each of the at least one integrator; For each integrator, after the integrator is authenticated based on its credentials, the integrator's interface and the URL corresponding to the integrator's interface are obtained.

6. The method according to any one of claims 1-3, characterized in that, Before obtaining the interface call request initiated by the target integrator, the method further includes: Issue corresponding credential information to each of the at least one integrated party, and record the credential information corresponding to each of the at least one integrated party; For each integrated party, after the integrated party authenticates based on the integrated party's credentials, the interface of the integrated party and the URL corresponding to the interface of the integrated party are obtained. The interface of the integrated party and the URL corresponding to the interface of the integrated party are converted into a format that the integrator can recognize.

7. The method according to any one of claims 1-3, characterized in that, Before obtaining the interface call request initiated by the target integrator, the method further includes: Obtain the user information sent by the target integrator via the login URL or registration URL; Based on the login URL or the registration URL, redirect to the third URL corresponding to the target integrated party; The user information is sent to the target integration party via the third URL so that the target integration party can perform login verification.

8. A business processing device for multi-application integration scenarios, characterized in that, include: The acquisition module is used to acquire the interface call request initiated by the target integrator. The interface call request carries the first Uniform Resource Locator URL corresponding to the interface of the target integrator, the second URL corresponding to the interface of the target integrator being called, and the first business processing request. The target integrator is one of at least one integrator, which is a scenario-based platform of the Software as a Service (SaaS) platform. The target integrator is one of at least one integrator, which is an application of the SaaS platform. The first conversion module is used to convert the first business processing request into a second business processing request in a format recognizable by the target integration party. The first determining module is used to determine the first calling interface corresponding to the second URL in the integration gateway, so as to call the first calling interface to enable the target integrated party to process the second business processing request and obtain the first processing result. The integration gateway records multiple URLs and the calling interface corresponding to each URL. The second conversion module is used to convert the first processing result into a second processing result in a format recognizable by the target integration entity; The second determining module is used to determine the second calling interface corresponding to the first URL in the integration gateway, so as to send the second processing result to the target integrator through the second calling interface.

9. An integrated gateway, characterized in that, include: Processor; memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images