Business processing method in multi-application integration scene

Abstract

The invention provides a service processing method in a multi-application integration scene. The method comprises the steps of firstly obtaining an interface calling request initiated by a target integration party; converting the first service processing request into a second service processing request in a format which can be identified by the target integrated party; determining a first calling interface corresponding to the second URL in the integrated gateway, calling the first calling interface to enable the target integrated party to process the second service processing request, and obtaining a first processing result; converting the first processing result into a second processing result in a format which can be identified by the target integration party; and finally, a second calling interface corresponding to the first URL is determined in the integrated gateway, so that the second processing result is sent to the target integration party through the second calling interface. According to the method provided by the invention, the service processing speed in a multi-application integration scene is improved, and the integration efficiency is improved.

Description

Technical Field

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

[0002] In the IoT business ecosystem, Software as a Service (SaaS) platforms are the final link in delivering IoT customer value. SaaS platforms can be comprehensive platforms that address a broad range of application scenarios, or they can be specific application platforms for one or several IoT devices. To avoid duplication and rapidly build scenario-specific SaaS platforms, the most common approach is to integrate existing specific application platforms to create complex scenario-based application platforms.

[0003] At present, the integration between SaaS platforms mainly adopts the open interfaces of both platforms. The interfaces of both platforms are directly connected according to the interface specifications. Then, the interfaces are called as needed to achieve the correspondence or association of users, organizations, and roles between the platforms. The integrator logs in to the integrated party in a unified manner, and the integrated party performs authentication and authorized login.

[0004] However, existing integration methods have problems such as complex interface docking and low integration efficiency when the integration demand is large. Summary of the Invention

[0005] The present application provides a business processing method in a multi-application integration scenario to solve the technical problems of complex integration interface docking 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] Obtaining an interface call request initiated by a target integrator, the interface call request carrying a first uniform resource locator (URL) corresponding to the interface of the target integrator, a second URL corresponding to the interface of the target integrated party being called, and a first business processing request, wherein the target integrator is one of at least one integrator, the integrator being 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 being an application of the SaaS platform;

[0008] converting the first business processing request into a second business processing request in a format recognizable by the target integrated party;

[0009] Determining, in the integration gateway, a first call interface corresponding to the second URL, and invoking the first call interface to cause the target integrated party to process the second business processing request and obtain a first processing result, wherein the integration gateway records a plurality of URLs and a call interface corresponding to each URL;

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

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

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

[0013] Accordingly, converting the first business processing request into a second business 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 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, and the first credential information is credential information with restricted access.

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

[0016] If 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 integrator through the second calling interface corresponding to the first URL, and the first information is used to indicate the failure of the target integrator to call the interface of the target integrated party.

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

[0018] In response to the configuration operation of the administrator, the at least one credential information is configured and processed, and the configuration processing 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 obtaining the interface call request initiated by the target integrator, the method further includes:

[0020] issuing corresponding credential information to the at least one integrator respectively, and recording the credential information corresponding to the at least one integrator respectively;

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

[0022] In one or more embodiments, before obtaining the interface call request initiated by the target integrator, the method further includes:

[0023] issuing corresponding credential information to the at least one integrated party respectively, and recording the credential information corresponding to the at least one integrated party respectively;

[0024] For each integrated party, after the integrated party authenticates based on the credential information of the integrated party, obtain the interface of the integrated party and the URL corresponding to the interface of the integrated party;

[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 integrating party.

[0026] In one or more embodiments, before obtaining the interface call request initiated by the target integrator, the method further includes:

[0027] Obtain user information sent by the target integrator via the login URL or registration URL;

[0028] Redirecting to a third URL corresponding to the target integrated party according to the login URL or the registration URL;

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

[0030] In a second aspect, the present application provides a service processing device in a multi-application integration scenario, comprising:

[0031] an acquisition module configured to acquire an interface call request initiated by a target integrator, the interface call request carrying a first uniform resource locator (URL) corresponding to an interface of the target integrator, a second URL corresponding to an interface of a target integrated party being called, and a first business processing request, wherein the target integrator is one of at least one integrator, the integrator being 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 being an application of the SaaS platform;

[0032] a first conversion module, 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, in the integration gateway, a first calling interface corresponding to the second URL, to call the first calling interface to cause the target integrated party to process the second business processing request, and to obtain a first processing result, wherein the integration gateway records a plurality of URLs and a calling interface corresponding to each URL;

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

[0035] The second determining module is used to determine a second calling 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 calling interface.

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

[0037] Accordingly, the first conversion module is specifically configured to:

[0038] If no credential information consistent with the target credential information is determined in 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, and the first credential information is credential information with restricted access.

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

[0040] If 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 integrator through the second calling interface corresponding to the first URL, and the first information is used to indicate the failure of the target integrator to call the interface of the target integrated party.

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

[0042] In response to the configuration operation of the administrator, the at least one credential information is configured and processed, 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 obtaining the interface call request initiated by the target integration party, the obtaining module is further configured to:

[0044] issuing corresponding credential information to the at least one integrator respectively, and recording the credential information corresponding to the at least one integrator respectively;

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

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

[0047] issuing corresponding credential information to the at least one integrated party respectively, and recording the credential information corresponding to the at least one integrated party respectively;

[0048] For each integrated party, after the integrated party authenticates based on the credential information of the integrated party, obtain the interface of the integrated party and the URL corresponding to the interface of the integrated party;

[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 integrating party.

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

[0051] Obtain user information sent by the target integrator via the login URL or registration URL;

[0052] Redirecting to a third URL corresponding to the target integrated party according to the login URL or the registration URL;

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

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

[0055] a processor, and a memory communicatively connected to the processor;

[0056] The memory stores computer-executable instructions;

[0057] The processor executes the computer-executable instructions stored in the memory to implement the method described 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-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect and any one of the embodiments.

[0059] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a business processing method in a multi-application integration scenario such as the first aspect and various possible implementation methods of the first aspect.

[0060] The present application provides a business processing method in a multi-application integration scenario. The method first obtains an interface call request initiated by a target integrator, wherein the interface call request carries a first uniform resource locator URL corresponding to the interface of the target integrator, a second URL corresponding to the interface of the called target integrated party, and a first business processing request; then, the first business processing request is converted into a second business processing request in a format recognizable by the target integrated party; then, a first calling interface corresponding to the second URL is determined in the integration gateway, so as to call the first calling interface so that the target integrated party processes the second business processing request and obtains a first processing result; the first processing result is converted into a second processing result in a format recognizable by the target integrator; finally, a second calling interface corresponding to the first URL is determined in the integration gateway, so as to send the second processing result to the target integrator through the second calling interface. In the above method, the scenario-based platform of the SaaS platform can be integrated into the application of the SaaS platform through the integration gateway, and at least one integrator can be integrated with at least one integrated party. In multi-integration application scenarios, multiple integrators can be integrated with multiple integrated parties based on the integration gateway to improve integration efficiency; the first business processing request in the interface call request initiated by the target integrator is converted into a second business processing request in a 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 can be converted into a second processing result in a format recognizable by the target integrator. Through format conversion, efficient interface docking can be achieved. BRIEF DESCRIPTION OF THE 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 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 1 ;

[0063] Figure 2 A schematic diagram of the structure of business processing in a multi-application integration scenario provided by an embodiment of the present application;

[0064] Figure 3 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 2 ;

[0065] Figure 4 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 3 ;

[0066] Figure 5 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 4 ;

[0067] Figure 6 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 5 ;

[0068] Figure 7 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 6 ;

[0069] Figure 8 A schematic diagram of the structure of a business processing device in a multi-application integration scenario provided by an embodiment of the present application;

[0070] Figure 9 A schematic diagram of the structure of the integrated gateway provided in an embodiment of the present application.

[0071] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0072] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain 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 device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0074] First, let’s explain the terms used in this application:

[0075] Software as a Service (SaaS): A cloud-based service model that allows users to access and use software applications over the internet without having to install and maintain them on local devices. SaaS platforms are typically hosted by a service provider, who is responsible for software maintenance, updates, security, and infrastructure management.

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

[0077] Callback URL: When an action or event is triggered, the system will send relevant information to a URL address hosted on a remote server. This address is the callback URL.

[0078] Customer Premises Equipment (CPE) platform: refers to the equipment and platform that supports communication service providers or enterprises in providing services in the customer premises environment;

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

[0080] ClientSecret: refers to the secret key, which is paired with ClientId and is only provided to the client and the authentication server to protect the client's identity information;

[0081] Authentication: refers to confirming the identity of a user or system and verifying whether a user's identity is legitimate;

[0082] Authentication: refers to verifying whether the user has the authority to access certain resources or perform certain operations;

[0083] Hypertext Transfer Protocol (HTTP): is an application layer protocol that can be referred to as a simple request-response protocol. Its main function is to allow a client to request resources from a server over the network, and the server then returns the resources to the client.

[0084] REST interface: refers to a set of interface rules implemented based on the HTTP protocol, using HTTP protocol request types and message parameter definitions;

[0085] Simple Object Access Protocol (SOAP): An XML-based protocol for messaging on the Web, allowing applications to interact in a distributed environment and supporting communication between different operating systems and programming languages.

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

[0087] Redirection: refers to the process of the server pointing the user request to another page. It can be used in scenarios such as URL change, page jump and access control.

[0088] Next, the technical background of this application is described as follows:

[0089] In the IoT business ecosystem, Software as a Service (SaaS) platforms are the final link in delivering IoT customer value. SaaS platforms can be comprehensive applications that address a broad range of scenarios, or they can be specific applications targeting a specific IoT device or devices. To avoid duplication and rapidly build scenario-specific SaaS platforms, the most common approach is to integrate existing specific applications to create complex scenario-based applications.

[0090] At present, the integration between SaaS platforms mainly adopts the open interfaces of both platforms. The interfaces of both platforms are directly connected according to the interface specifications. Then, the interfaces are called as needed to achieve the correspondence or association of users, organizations, and roles between the platforms. The integrator logs in to the integrated party in a unified manner, and the integrated party performs authentication and authorized login.

[0091] However, when the integration demand is large, the existing integration method requires the integrated party to perform debugging every time the integration is performed, resulting in complex interface docking and low integration efficiency.

[0092] The method for business processing in a multi-application integration scenario provided by the present application is intended to solve the above technical problems of the prior art. The inventive concept of the present application is as follows: in a multi-integration scenario, the interface formats of different integrated parties may be different. The existing integration method needs to debug the interface of the integrated party each time the integration is performed, and then realize the interface docking between the integrator and the integrated party, which will lead to 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 the interface with a unified format is obtained and then presented to the integrator. When the integrator makes an interface call, it can access the integrated party interface in the standard format in the integration gateway, which can effectively improve the efficiency of integration between different integrators and different integrated parties. At the same time, the integration gateway issues credential information to the target integrated party and the target integrator respectively, identifies the target integrated party and the target integrator according to the issued credential information, and performs authentication, which can ensure the information security when the target integrated party and the target integrator interact.

[0093] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0094] Figure 1 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 1 .like Figure 1 As shown, the execution subject of the business processing method in the multi-application integration scenario is the integration gateway, which includes the following steps:

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

[0096] S110: Obtain an interface call request initiated by the target integrator;

[0097] Among them, 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 integrated party being called, and the first business processing request. The target integrator is one of at least one integrator, and the integrator is a scenario-based platform of the 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, a target integrator is determined among at least one integrator, and based on the service functions that the target integrator needs to provide, a target integrated party is determined among at least one integrated party. Then, based on the interfaces provided by the target integrator and the target integrated party, a first uniform resource locator URL corresponding to the interface of the target integrator and a second URL corresponding to the interface of the called target integrated party are obtained. Then, in combination with the first business processing request of the target integrator, an interface call request is constructed. The target integrator initiates the interface call request, and the integration gateway obtains the interface call request initiated by the target integrator.

[0099] Illustratively, the first business request refers to the specific content of the business processing initiated by the target integrator to the target integrated party, including business data or request parameters, and may require the target integrated party to perform a certain operation or provide a certain service.

[0100] In one possible implementation, the integrator can be a SaaS platform that provides scenario-based services based on different application scenarios. For example, a smart building platform can provide a complete building intelligence solution, including building management, resource management, security monitoring and other service functions; a smart city platform can provide a comprehensive platform for urban 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 that includes at least one IoT device. For example, a video surveillance platform application can provide real-time video monitoring, video storage, event alarm and other functions, including IoT devices such as surveillance cameras, video recorders, and sensors; a customer premises equipment (CPE) platform application can provide users with management and configuration functions for specific application devices, including IoT devices such as routers and switches; a door lock platform application can provide remote control and monitoring functions for various smart door locks, including IoT devices such as smart door locks and sensors.

[0102] For example, if the target integrator is a smart hotel platform and needs to provide service functions such as environmental monitoring and security door locks, then the target integrated party can be applications such as video surveillance platforms and door lock platforms.

[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 integration gateway parses the interface call request received from the target integrator to obtain a first business request. The business processing requests from the target integrator and the target integrated party have different formats. Therefore, the first business processing request sent by the target integrator must be formatted to obtain a second business processing request recognizable by the target integrated party. The integration gateway converts the request according to the target integrated party's request format to obtain the second business processing request in a format recognizable by the target integrated party.

[0105] In one possible implementation, converting the first business processing request may 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 a second business processing request.

[0106] For example, if the format of the first business processing request is (user_id: "12345", action: "login", Timestamp: "3333-22-11T00:01:02Z"), and the request format that the target integrated party can recognize 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: Determine, in the integration gateway, a first calling interface corresponding to the second URL, and call the first calling interface to enable the target integrated party to process the second business processing request and obtain a first processing result;

[0108] The integrated gateway records multiple URLs and the calling interface corresponding to each URL.

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

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

[0111] Exemplarily, the processing status information may include whether the request is successfully processed, whether there is an error or exception, and a status code may usually be used to indicate success or failure;

[0112] Data processing results may include specific business logic results, such as business data, calculation results, or processed information, which can be structured data or unstructured data;

[0113] The response data may be return data from the first calling interface, such as analysis results, application execution results, etc.;

[0114] The processing time may include the timestamp, start time, end time of the second service processing request, and the response time of the first calling interface.

[0115] S140: Convert the first processing result into a second processing result in a format recognizable by the target integration party.

[0116] In this step, the integration gateway parses the first processing result received from the target integrated party. Since the processing results from the target integrator and the target integrated party are in different formats, the first processing result sent by the target integrated party must be converted into a second processing result recognizable by the target integrator. The integration gateway converts the processing result according to the target integrator's format to obtain the second processing result in a format recognizable by the target integrator.

[0117] In one possible implementation, converting the first processing result may include converting the data format of the processing result, such as converting a binary format into a text format, and may also include converting fields in the processing result into a processing result field format that can be recognized by the target integrator, and converting the data format in the processing result content into a processing result content format that can be recognized by the target integrator.

[0118] For example, if the format of the first business processing result is (order_id: "222", status: "success", order_date:

[0119] "11-22-33T00:01:02Z"), and the request format that the target integrated party can recognize is (order_number: "222", order_status: "Success", order_time: "11-22-33-00:01:02"), then the field name is converted from "order_id" to "order_number", "status" to "order_status", "order_date" to "order_time", and the processing result content format is converted from "success" to "Success" (the first letter is capitalized), and "11-22-33T00:01:02Z" to "11-22-33-00:01:02".

[0120] S150: Determine, in the integration gateway, a second calling interface corresponding to the first URL, and send the second processing result to the target integration party through the second calling interface.

[0121] In this step, based on 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 the second calling interface. Then, the second processing result can be sent to the target integrator by calling the second calling interface.

[0122] In one possible implementation, Figure 2 A schematic diagram of the business process structure provided in this embodiment, such as Figure 2 As shown, at least one integrator and at least one integrated party are connected to the integration gateway respectively, and the access connection between the integrator and the integrated party is realized through the integration gateway.

[0123] The integrator is a scenario-based platform for the Software as a Service (SaaS) platform, and the integrated party is an application on the SaaS platform. The integration gateway has authentication, format conversion, and access management functions.

[0124] In a possible implementation, the interface call request further carries target credential information, where the target credential information is at least one credential information issued by the integration gateway to the target integrator for accessing the integrated party;

[0125] Correspondingly, the first business processing request is converted into a second business processing request in a format recognizable by the target integrated party, including: if no credential information consistent with the target credential information is determined in 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, and the first credential information is credential information with restricted access.

[0126] Exemplarily, the integration gateway can issue credential information to the integrator, the target credential information is at least one credential information issued by the integration gateway to the target integrator for accessing the integrated party, and the first credential information is credential information with restricted access, that is, the integrator with the first credential information cannot access the integrated party.

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

[0128] In one possible implementation, the credential information issued by the integration gateway to the target integrator can be a combination of ClientId and ClientSecret, where ClientId uniquely identifies the target integrator. The target integrator sends the ClientSecret to the integration gateway for verification. If the ClientSecret is not pre-marked credential information with restricted access, the target integrator can access the integrated party through the integration gateway.

[0129] In one possible implementation, if credential information consistent with the target credential information is determined in 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, and the first information is used to indicate the failure of the target integrator to call the interface of the target integrated party.

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

[0131] In one possible implementation, the target integrator sends the ClientSecret to the integration gateway for verification. If the ClientSecret is pre-marked credential information with restricted access, the first information is sent to the target integrator through the callback URL of the second calling interface corresponding to the first URL, indicating the failure of the target integrator to call the interface of the target integrated party.

[0132] In a possible implementation, in response to a configuration operation by an administrator, configuration processing is performed on at least one credential information, where the configuration processing includes at least one of the following: deleting a credential, adding a credential, modifying a credential, and marking a credential.

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

[0134] In one possible implementation, deleting a credential can be deleting the credential information that has been issued, adding a new credential can be the integration gateway issuing new credential information to the integrator, modifying a credential can be modifying the content of the ClientId or ClientSecret in the issued credential information, and marking a credential can be adding a mark to the credential information, such as adding a mark to indicate whether the credential information is restricted from access.

[0135] The business processing method in a multi-application integration scenario provided by an embodiment of the present application first obtains an interface call request initiated by a target integrator, wherein the interface call request carries a first uniform resource locator (URL) corresponding to the interface of the target integrator, a second URL corresponding to the interface of the target integrated party to be called, and a first business processing request, wherein the target integrator is one of at least one integrator, the integrator 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 the SaaS platform; then, the first business processing request is converted into a second business processing request in a format recognizable by the target integrated party; thereafter, a first call interface corresponding to the second URL is determined in the integration gateway, so as to call the first call interface so that the target integrated party processes the second business processing request and obtains a first processing result, wherein the integration gateway records multiple 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 integrator; finally, a second call interface corresponding to the first URL is determined in the integration gateway, so as to send the second processing result to the target integrator through the second call interface. In this embodiment, the scenario-based platform of the SaaS platform can be integrated into the application of the SaaS platform through the integration gateway, and at least one integrator can be integrated with at least one integrated party. In a multi-integration application scenario, multiple integrators can be integrated with multiple integrated parties based on the integration gateway, thereby improving integration efficiency. The first business processing request in the interface call request initiated by the target integrator is converted into a second business processing request in a 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 can be converted into a second processing result in a format recognizable by the target integrator. Through format conversion, efficient interface docking can be achieved.

[0136] Based on the above embodiments, Figure 3 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 2 .like Figure 3 As shown, the business processing method in the multi-application integration scenario also includes the following steps:

[0137] S310: Issue corresponding credential information to at least one integrator, and record the credential information corresponding to at least one integrator.

[0138] In this step, different integrators have different corresponding credential information. The integration gateway issues corresponding credential information to at least one integrator respectively, and records the credential information corresponding to at least one integrator respectively.

[0139] In a possible implementation, the corresponding credential information issued by the integration gateway to at least one integration party may 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 integrator, after the integrator is authenticated based on the integrator's credential information, obtain the integrator's interface and the URL corresponding to the integrator's interface.

[0142] In this step, for each integrator, the integration gateway performs authentication based on the integrator's credential information. When the authentication is successful, the integrator's interface and the URL corresponding to the integrator's interface are obtained.

[0143] In one possible implementation, the integration gateway can identify the integrator through ClientId, and then the integrator sends ClientSecret to the integration gateway. The integration gateway authenticates the integrator based on the recorded ClientId and ClientSecret of the integrator. If the ClientSecret of the integrator is consistent with the recorded ClientSecret, the verification is successful.

[0144] For example, taking the above example to further illustrate, for integrator A, the integrator is first identified based on the ClientId_A of the integrator A's credential information, and then integrator A sends ClientSecret_D to the integration gateway. If it is inconsistent with the recorded ClientSecret_A of integrator A, the verification fails; for integrator B, the integrator is identified based on the ClientId_B of the integrator B's credential information, and then integrator B sends ClientSecret_B to the integration gateway. If it is consistent with the recorded ClientSecret_B of integrator B, the verification passes, and the integration gateway obtains the interface of integrator B and the URL corresponding to the interface of integrator B.

[0145] The business processing method in a multi-application integration scenario provided by an embodiment of the present application first issues corresponding credential information to at least one integrator and records the corresponding credential information of at least one integrator; then, for each integrator, after the integrator authenticates based on the integrator's credential information, the integrator's interface and the URL corresponding to the integrator's interface are obtained. In this embodiment, by issuing corresponding credential information to at least one integrator and recording it, the corresponding integrator can be identified based on the credential information, and the validity of the credential information is ensured; by authenticating the integrator's credential information, the integrator's permissions can be managed. When the authentication is passed, the integrator's interface and the URL corresponding to the integrator's interface can be obtained, thereby improving the security of the integration.

[0146] Based on the above embodiments, Figure 4 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 3 .like Figure 4 As shown, the business processing method in the multi-application integration scenario also includes the following steps:

[0147] S410: Issue corresponding credential information to at least one integrated party, and record the corresponding credential information of at least one integrated party.

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

[0149] In a possible implementation, the integration gateway issues corresponding credential information to at least one integrated party, which may 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 integration gateway issues credential information ClientId1 and ClientSecret1 to integrated party 1, and issues credential information ClientId2 and ClientSecret2 to integrated party 2.

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

[0152] In this step, for each integrated party, the integration gateway performs authentication based on the integrated party's credential information. When the authentication is successful, the integrated party's interface and the URL corresponding to the integrated party's interface are obtained.

[0153] In one possible implementation, the integration gateway identifies the integrated party through ClientId, and the integrated party sends ClientSecret to the integration gateway. The integration gateway authenticates the integrated party based on the recorded ClientId and ClientSecret of the integrated party. If the ClientSecret of the integrated party is consistent with the recorded ClientSecret, the verification is successful.

[0154] For example, taking the above example to further illustrate, for the integrated party 1, the integrated party is first identified according to the ClientId1 of the integrated party 1 credential information, and the integrated party 1 sends ClientSecret3 to the integration gateway. If it is inconsistent with the recorded ClientSecret1 of the integrated party 1, the verification fails; for the integrated party 2, the integrator is identified according to the ClientId2 of the integrated party 2 credential information, and then the integrated party 2 sends ClientSecret2 to the integration gateway. If it is consistent with the recorded ClientSecret2 of the integrated party 2, the verification passes, and the integration gateway obtains the interface of the integrated party B and the URL corresponding to the interface of the integrated party B.

[0155] S430: Convert the format of the interface of the integrated party and the URL corresponding to the interface of the integrated party to obtain a format that can be recognized by the integrating party.

[0156] In this step, the formats of the interfaces of the integrated party and the integrating party, as well as the URLs corresponding to the interfaces, are different. The integration gateway converts the formats of the integrated party's interface and the URL corresponding to the integrating party's interface to obtain the interface and corresponding URL in a format that the integrating party can recognize.

[0157] In a possible implementation, the integration gateway may convert the format of the interface of the integrated party and the URL corresponding to the interface of the integrated party by converting the interface protocol, converting the URL path format, and the like.

[0158] For example, if the interface of the integrated party is a REST interface based on HTTP protocol, and the interface of the integrating party is a SOAP interface based on 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 integrating party is / getOrders?id=(userId), the URL path format of the integrated party needs to be converted to the path format of the integrating party's URL.

[0160] The business processing method in a 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 at least one integrated party; then, for each integrated party, after the integrated party authenticates based on the credential information of the integrated party, obtains the interface of the integrated party and the URL corresponding to the interface of the integrated party; finally, the interface of the integrated party and the URL corresponding to the interface of the integrated party are formatted and converted to a format that can be recognized by the integrating party. In this embodiment, by issuing unique credential information to each integrated party and recording it, it is ensured that the functions of the integrated party can only be integrated after verification; the integrated party can obtain its interface and corresponding URL only after authentication, which can improve the security of the integration; by converting the format of the interface of the integrated party and the corresponding URL into a format that can be recognized by the integrating party, the integrating party can flexibly respond to the technical requirements and interface specifications of different integrated parties, thereby improving the efficiency of integration.

[0161] Based on the above embodiments, Figure 5 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 4 .like Figure 5 As shown, the business processing method in the multi-application integration scenario also includes the following steps:

[0162] S510: Obtain user information sent by the target integrator via the login URL or registration URL.

[0163] In this step, the target integrator provides a login or registration interface. The login interface corresponds to the login URL, and the registration interface corresponds to the registration URL. The target integrator accesses the integration gateway through the login URL or registration URL and sends user information at the same time. The integration gateway obtains the user information sent by the target integrator.

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

[0165] Exemplarily, the user information may include: the user's unique identifier "user-id: 1122", the user name "user-name: max", the user login password "user-code: 35526", and the user registration verification code "user-token: 5858".

[0166] S520: Redirect the target integrated party to a third URL according to the login URL or the registration URL.

[0167] In this step, the integration gateway parses the login URL or registration URL to determine the target integrated party to which user information needs to be transmitted. The target integrated party provides an interface corresponding to the login URL or registration URL, and then redirects the third URL corresponding to the target integrated party based on the URL corresponding to the interface.

[0168] Exemplarily, the third URL refers to a URL in the target integrated party that is connected to the login URL or registration URL of the target integrator and can receive user information and return processing results.

[0169] S530: Send the user information to the target integrated party via the third URL, so that the target integrated party performs login verification.

[0170] In this step, the target integrated party has user information of historical login users in advance. After the received user information is sent to the target integrated party via the third URL, the target integrated party parses the user information after receiving it and compares the parsed user information with the user information of historical login users to perform login verification.

[0171] In one 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 the user's unique identifier and user name, and identifies the user's unique identifier in the historical login user information based on the user's unique identifier. If the user's unique identifier is identified, the user's login password is further obtained through the third URL and the user's login password is verified to be correct. If the login password is correct, the current user successfully logs in to the target integrated party, otherwise the login fails. If the current user's unique identifier is not identified in the historical login user information, the user can be registered through the user registration verification code. After the user registration is successful, the login can be further verified based on the user login password.

[0172] Furthermore, when the user successfully logs in to 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. After the business processing is completed, a processing result is generated. The target integrated party returns the generated processing result to the target integrator through a third URL.

[0173] The business processing method in a multi-application integration scenario provided by an embodiment of the present application first obtains the user information sent by the target integrator through the login URL or registration URL; then, based on the login URL or registration URL, redirects the third URL corresponding to the target integrated party; finally, sends the user information to the target integrated party through the third URL, so that the target integrated party performs login verification. In this embodiment, the target integrator can send user information through the login URL or registration URL, and can redirect the third URL corresponding to the target integrated party. Based on the redirection, the target integrator can be guided to correspond to the correct target integrated party, and at the same time, it can quickly jump back to the login URL or registration URL of the target integrator after completing the login verification, which can speed up the business processing speed in the integration; after sending the user information to the target integrated party through the third URL, the target integrated party performs login verification, and login verification of the user information can ensure the security of the user information.

[0174] Based on the above embodiments, Figure 6 Schematic diagram of the process of business processing method in multi-application integration scenario provided by the embodiment of this application Figure 5 .like Figure 6 As shown, the business processing method in the multi-application integration scenario also includes the following steps:

[0175] Step 1: The integration gateway issues credential information to the target integrated party.

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

[0177] Step 2: The target integrated party accesses the integration gateway after authentication and authorization based on the obtained credential information, and provides the target integrated party's interface and the URL corresponding to the interface to the integration gateway.

[0178] The target integrated party's interface may include a user login interface, a user registration interface, a callback interface, etc. The URL corresponding to each interface includes a user login URL, a user registration URL, and a callback URL, etc.

[0179] Step 3: The integration gateway converts the format of the target integrated party's interface to obtain an interface with a unified standard format and the URL corresponding to the interface.

[0180] In a possible implementation, different integrated parties have different interface formats. By converting the formats into interfaces with a unified standard format, integration efficiency can be improved.

[0181] Step 4: The integration gateway issues target credential information to the target integration party.

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

[0183] Step 5: The target integrator accesses the integration gateway after authentication and authorization based on the target credential information obtained.

[0184] The target integrator may provide an interface in a standard format and a URL corresponding to the interface. The interface may include a user login interface, a user registration interface, etc. The URL corresponding to each interface includes a user login URL, a user registration URL, etc.

[0185] Step 6: The target integration direction sends an interface call request to the integration gateway.

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

[0187] Step 7: After receiving the interface call request, the integration gateway parses it to check whether the target credential information of the target integrator is consistent with the pre-marked restricted access credential information. If not, the call success is returned to the target integrator through the callback URL; otherwise, the call failure is returned to the target integrator through the callback URL.

[0188] Further, Figure 7 Schematic diagram of the business processing method in the multi-application integration scenario provided by this embodiment Figure 6 .like Figure 7As shown, when the call is successfully returned to the target integrator, the following steps are also included:

[0189] Step 1: The target integration direction sends an interface call request to the integration gateway;

[0190] Step 2: The integration gateway converts the interface call request into a format that can be recognized by the target integrated party;

[0191] Step 3: The integration gateway sends the format-converted interface call request to the target integrated party and calls the target integrated party's interface 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 first processing result into a format recognizable by the target integrator to obtain a second processing result;

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

[0195] The business processing method in a multi-application integration scenario provided by an embodiment of the present application is that the integration gateway issues credential information to the target integrated party and the target integrator respectively, identifies the target integrated party and the target integrator based on the issued credential information, and performs authentication, thereby ensuring information security when the target integrated party and the target integrator interact; the integration gateway converts the interface call request sent by the target integrator into a format that can be recognized by the target integrated party, and converts the first processing result obtained by the target integrated party into a format that can be recognized by the target integrator. The integration gateway has the function of format conversion, which can improve the efficiency of integration between different integrators and integrated parties.

[0196] Based on the above embodiments, the following are device embodiments involved in this application:

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

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

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

[0200] A first determining module 830 is configured to determine, in the integration gateway, a first calling interface corresponding to the second URL, invoke the first calling interface to cause the target integrated party to process the second business processing request, and obtain a first processing result. The integration gateway may record multiple URLs and a calling interface corresponding to each URL.

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

[0202] The second determining 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 integration party through the second calling interface.

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

[0204] Accordingly, 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 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, and the first credential information is credential information with restricted access.

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

[0207] If credential information consistent with the target credential information is determined in 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 integrated party.

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

[0209] In response to the configuration operation of the administrator, configuration processing is performed on at least one credential information, 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 obtaining the interface call request initiated by the target integrator, the obtaining module 810 is further configured to:

[0211] issuing corresponding credential information to at least one integrator respectively, and recording the credential information corresponding to at least one integrator respectively;

[0212] For each integrator, after the integrator is authenticated based on the integrator's credential information, the integrator's interface and the URL corresponding to the integrator's interface are obtained.

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

[0214] issuing corresponding credential information to at least one integrated party, and recording the credential information corresponding to at least one integrated party;

[0215] For each integrated party, after the integrated party authenticates based on the integrated party's credential information, obtain the integrated party's interface and the URL corresponding to the integrated party's interface;

[0216] The interface of the integrated party and the URL corresponding to the interface of the integrated party are converted into a format that can be recognized by the integrating party.

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

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

[0219] Redirect the target integrated party to a third URL based on the login URL or registration URL;

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

[0221] Based on the above embodiments, Figure 9 This is a schematic diagram of the structure of the integrated gateway provided in the embodiment of this application. Figure 9 As shown, the integrated gateway 900 includes: a processor 910, a memory 920 and a bus 930;

[0222] The entity corresponding to the integrated gateway may be an electronic device corresponding to the integrated gateway;

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

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

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

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

[0227] Bus 930 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified as address buses, data buses, control buses, etc. For ease of illustration, the drawings of this application use only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0228] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; 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 devices, discrete gate or transistor logic devices, and discrete hardware components.

[0229] The integrated gateway is used to execute the technical solution of any of the aforementioned method embodiments, and its implementation principles and technical effects are similar and will not be repeated here.

[0230] An embodiment of the present application also provides a computer-readable storage medium on which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution provided by any of the above method embodiments.

[0231] An embodiment of the present application also provides a computer program product, including a computer program, which includes computer instructions stored in a computer-readable storage medium. When the computer program is executed by a processor, it is used to implement the technical solution provided by any of the above method embodiments.

[0232] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0233] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

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

[0235] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0236] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may 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 unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0238] In the above embodiments, the description of each embodiment has its own focus. For parts not described in detail in a certain embodiment, please refer to the relevant 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. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0239] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0240] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A business processing method in a multi-application integration scenario, characterized in that: Applied to an integrated gateway, the method comprises: Acquire an interface call request initiated by a target integrator, wherein the interface call request carries a first uniform resource locator URL corresponding to the interface of the target integrator, a second URL corresponding to the interface of the called target integrated party, and a first business processing request, wherein the target integrator is one of at least one integrator, the integrator 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 the SaaS platform; converting the first business processing request into a second business processing request in a format recognizable by the target integrated party; 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 business 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; Converting the first processing result into a second processing result in a format recognizable by the target integration party; A second calling interface corresponding to the first URL is determined in the integration gateway, so as to send the second processing result to the target integration party through the second calling interface.

2. The method according to claim 1, characterized in that The interface call request also carries target credential information, where the target credential information is at least one credential information issued by the integration gateway to the target integrator for accessing the integrated party; Accordingly, the step of 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 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, and the first credential information is credential information with restricted access.

3. The method according to claim 2, characterized in that The method further comprises: If 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 integrator through the second calling interface corresponding to the first URL, and the first information is used to indicate the failure of the target integrator to call the interface of the target integrated party.

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

5. The method according to any one of claims 1 to 3, characterized in that: Before obtaining the interface call request initiated by the target integration party, the method further includes: issuing corresponding credential information to the at least one integrator respectively, and recording the credential information corresponding to the at least one integrator respectively; For each integrator, after the integrator is authenticated based on the credential information of the integrator, the interface of the integrator and the URL corresponding to the interface of the integrator are obtained.

6. The method according to any one of claims 1 to 3, characterized in that: Before obtaining the interface call request initiated by the target integration party, the method further includes: issuing corresponding credential information to the at least one integrated party respectively, and recording the credential information corresponding to the at least one integrated party respectively; 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; 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 integrating party.

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

8. A business processing device in a multi-application integration scenario, characterized in that: include: an acquisition module, configured to acquire an interface call request initiated by a target integrator, wherein the interface call request carries a first uniform resource locator URL corresponding to an interface of the target integrator, a second URL corresponding to an interface of a target integrated party being called, and a first business processing request, wherein the target integrator is one of at least one integrator, the integrator 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 the SaaS platform; A first conversion module, configured to convert the first business processing request into a second business processing request in a format recognizable by the target integrated party; a first determination module, configured to determine a first call interface corresponding to the second URL in the integration gateway, so as to call the first call interface to enable the target integrated party to process the second business processing request and obtain a first processing result, wherein the integration gateway records a plurality of URLs and a call interface corresponding to each URL; A second conversion module, used for converting the first processing result into a second processing result in a format recognizable by the target integration party; The second determination 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 integration party through the second calling interface.

9. An integrated gateway, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to 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 are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images