A business processing method and system

Abstract

This invention discloses a business processing method and system, relating to the field of financial information service technology. One specific embodiment of the method includes: receiving a request from a client of a first channel provider via a call to a target general interface, the request including a transaction identifier; identifying the transaction identifier through the target general interface to route the request to a target business operation module of a second channel provider for processing; and returning the processing result of the target business operation module to the client of the first channel provider through the target general interface. This embodiment enables standardized access, eliminating the need for different channel providers to adapt their interfaces, resolving integration difficulties, and reducing security risks for channel provider systems.

Description

Technical Field

[0001] This invention relates to the field of financial information service technology, and in particular to a business processing method and system. Background Technology

[0002] As inclusive finance continues to develop in China, financial institutions are increasingly collaborating with external stakeholders (referring to external partners or companies that provide platform access for financial institutions' business) in addition to their traditional internal business models. Financial institutions, as fund providers, connect with different stakeholders and provide targeted financial information services based on the characteristics of each scenario.

[0003] In the process of realizing this invention, the inventors discovered at least the following problems in the prior art:

[0004] During the integration process with different channels (such as funders, scenario providers, and third-party services), funders need to adapt to the interfaces of different scenario providers; funders need to adapt to the interfaces of different third-party services; funders, scenario providers, and third-party services need to sign a tripartite contract so that funders can directly access third-party services to obtain relevant information, thereby increasing the difficulty of multi-party integration; funders need to access a large number of third-party services through the Internet, which increases the security risks of the system. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a business processing method and system that can standardize interface access, so that different channel parties do not need to adapt to the interfaces of other channel parties when connecting, thus solving the problem of difficult connection and reducing the security risks of channel party systems.

[0006] To achieve the above objectives, according to one aspect of the present invention, a business processing method is provided.

[0007] A business processing method includes: receiving a request sent by a client of a first channel party through calling a target general interface, the request including a transaction identifier; identifying the transaction identifier through the target general interface to route the request to a target business operation module of a second channel party for processing; and returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

[0008] Optionally, the step of identifying the transaction identifier through the target general interface to route the request to the target business operation module of the second channel party for processing includes: identifying the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier through the target general interface; finding the business operation module whose channel party category corresponds to the connection identifier, whose channel party name corresponds to the channel identifier, whose provided service corresponds to the service identifier, and whose executed operation corresponds to the operation identifier, and selecting this module as the target business operation module, and then routing the request to the target business operation module for processing.

[0009] Optionally, based on the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier, the existing transaction identifier annotations are traversed to find the business operation module that corresponds to the channel type, the channel name, the service provided, and the operation performed.

[0010] Optionally, before receiving the request sent by the client of the first channel party through calling the target general interface, the process includes: pre-defining one or more general interfaces according to functions for operations performed under various channel party categories, channel party names and provided services, wherein one of the general interfaces is the target general interface, and each general interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one of the operations performed.

[0011] Optionally, the predefined one or more general interfaces include one or more of the following: general data interface, general file download interface, general file upload interface, general file stream proxy download interface, and general file stream download interface.

[0012] Optionally, identifying the transaction identifier through the target general interface to route the request to the target business operation module of the second channel party for processing includes: calling a transaction identifier management service through the target general interface, so that the transaction identifier management service identifies a first transaction identifier and at least one second transaction identifier from the transaction identifiers, and routes the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, for processing by the first target business operation module and the second target business operation module.

[0013] Optionally, the number of second channel parties may be two or more, and the first target business operation module and the second target business operation module may be the same or different business operation modules of the second channel parties.

[0014] Optionally, returning the processing result of the target business operation module to the client of the first channel party through the target general interface includes: receiving the first processing result of the first target business operation module and the second processing result of the second target business operation module through the transaction identifier management service, encapsulating the first processing result and the second processing result into a unified processing result and returning it to the client of the first channel party.

[0015] Optionally, before receiving the request sent by the client of the first channel party through calling the target general interface, the process includes: confirming that the client of the first channel party has interface access permissions to call the target general interface.

[0016] Optionally, the target general interface is provided through a connector deployed on the container cloud service to receive requests from the client of the first channel party by calling the target general interface.

[0017] Optionally, before receiving the request sent by the client of the first channel party through calling the target general interface, the method further includes: verifying the login information of the client of the first channel party to the connector; after the login information is verified, verifying whether the client of the first channel party has access permission to access the application of the second channel party; if it has such access permission, returning a JSON (JavaScript Object Notation) Web token to the client of the first channel party so that the request carries the JSON Web token; confirming that the client of the first channel party has interface access permission to call the target general interface includes: verifying the JSON Web token through the target general interface; if the token is verified, the client of the first channel party has interface access permission to call the target general interface.

[0018] Optionally, the request sent by the client of the first channel party through calling the target general interface includes a request signature value; the method further includes: after receiving the request sent by the client of the first channel party through calling the target general interface, first verifying the signature of the request, and determining that the signature verification is successful.

[0019] Optionally, routing the request to the target business operation module of the second channel party for processing includes: determining the target business operation module of the second channel party for processing the request, and providing the address of the target business operation module to the client of the first channel party, so that the client of the first channel party can access the address and process the request through the target business operation module.

[0020] Optionally, the system may also provide a set of configuration information to the client of the first channel provider, so that the client of the first channel provider can select configuration information from the set of configuration information, wherein the transaction identifier in the request is generated based on the configuration information selected by the client of the first channel provider.

[0021] According to another aspect of the present invention, a business processing system is provided.

[0022] A business processing system includes: a request receiving module for receiving a request sent by a client of a first channel party through calling a target general interface, the request including a transaction identifier; a request routing module for identifying the transaction identifier through the target general interface to route the request to a target business operation module of a second channel party for processing; and a result returning module for returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

[0023] Optionally, the request routing module is further configured to: identify the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier through the target general interface; find the business operation module that corresponds to the connection identifier for the channel type, the channel identifier for the channel name, the service provided for the service identifier, and the operation performed for the operation identifier, and use it as the target business operation module, and route the request to the target business operation module for processing.

[0024] Optionally, based on the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier, the existing transaction identifier annotations are traversed to find the business operation module that corresponds to the channel type, the channel name, the service provided, and the operation performed.

[0025] Optionally, it also includes a general interface creation module for: pre-defining one or more general interfaces according to functions for operations performed under various channel categories, channel names and provided services, wherein one of the general interfaces is the target general interface, and each general interface corresponds to at least one channel category, at least one channel name, at least one provided service and at least one of the performed operations.

[0026] Optionally, the predefined one or more general interfaces include one or more of the following: general data interface, general file download interface, general file upload interface, general file stream proxy download interface, and general file stream download interface.

[0027] Optionally, the request routing module is further configured to: call the transaction identifier management service through the target general interface, so that the transaction identifier management service can identify a first transaction identifier and at least one second transaction identifier from the transaction identifiers, and route the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, so that the first target business operation module and the second target business operation module can process the request respectively.

[0028] Optionally, the number of second channel parties may be two or more, and the first target business operation module and the second target business operation module may be the same or different business operation modules of the second channel parties.

[0029] Optionally, the result return module is further configured to: receive the first processing result of the first target business operation module and the second processing result of the second target business operation module through the transaction identifier management service, encapsulate the first processing result and the second processing result into a unified processing result and return it to the client of the first channel party.

[0030] Optionally, it also includes an access permission verification module, used to: confirm that the client of the first channel party has interface access permission to call the target general interface.

[0031] Optionally, the target general interface is provided through a connector deployed on the container cloud service to receive requests from the client of the first channel party by calling the target general interface.

[0032] Optionally, it also includes a token providing module, configured to: verify the login information of the first channel party's client to the connector; after the login information is verified, verify whether the first channel party's client has access permission to access the second channel party's application; if it has such access permission, return a JSON Web token to the first channel party's client so that the request carries the JSON Web token; the access permission verification module is further configured to: verify the JSON Web token through the target general interface; if the token verification is successful, the first channel party's client has interface access permission to call the target general interface.

[0033] Optionally, the request sent by the client of the first channel party through calling the target general interface includes a request signature value; the system further includes a signature verification module, used to: after the request receiving module receives the request sent by the client of the first channel party through calling the target general interface, first verify the signature of the request and determine that the signature verification is successful.

[0034] Optionally, the request routing module is further configured to: determine the target business operation module of the second channel party that processes the request, and provide the address of the target business operation module to the client of the first channel party, so that the client of the first channel party can access the address and process the request through the target business operation module.

[0035] Optionally, it also includes a configuration module, configured to: provide a set of configuration information to the client of the first channel party, so that the client of the first channel party can select configuration information from the set of configuration information, wherein the transaction identifier in the request is generated based on the configuration information selected by the client of the first channel party.

[0036] According to another aspect of the present invention, an electronic device is provided.

[0037] An electronic device includes: one or more processors; and a memory for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the business processing method provided in the embodiments of the present invention.

[0038] According to another aspect of the present invention, a computer-readable medium is provided.

[0039] A computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the business processing method provided in the embodiments of the present invention.

[0040] According to another aspect of the present invention, a computer program product is provided.

[0041] A computer program product includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiments of the present invention.

[0042] One embodiment of the above invention has the following advantages or beneficial effects: By identifying the transaction identifier carried in a request sent by the client of the first channel party through the target general interface, the request is routed to the target business operation module of the second channel party that handles the request for processing. The corresponding processing result is then returned to the client of the first channel party through the target general interface. Standardization of interface access for different channel parties eliminates the need for adaptation to other channel parties' interfaces during integration, solving the problem of difficult integration and reducing the security risks of the channel party's system. Furthermore, by simply providing the address of the target business operation module to the client of the first channel party, the client can perform business processing by accessing that address, ensuring the data security of the first channel party and preventing data leakage.

[0043] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0044] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0045] Figure 1 This is a schematic diagram of the main steps of a business processing method according to an embodiment of the present invention;

[0046] Figure 2 This is a schematic diagram of a system architecture for business processing according to an embodiment of the present invention;

[0047] Figure 3 This is a schematic diagram of the process of implementing combined transactions in business processing according to an embodiment of the present invention;

[0048] Figure 4 This is a flowchart illustrating the process of verifying interface access permissions in a business process according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram of the main modules of a business processing system according to an embodiment of the present invention;

[0050] Figure 6 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0051] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing the server of the present invention. Detailed Implementation

[0052] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0053] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0054] Figure 1 This is a schematic diagram illustrating the main steps of a business processing method according to an embodiment of the present invention. Figure 1 As shown, a service processing method according to an embodiment of the present invention mainly includes the following steps S101 to S103.

[0055] Step S101: Receive a request from the client of the first channel party by calling the target general interface, the request including the transaction identifier;

[0056] Step S102: Identify the transaction identifier in the request through the target general interface, so as to route the request to the target business operation module of the second channel party that handles the request for processing;

[0057] Step S103: Return the processing result of the target business operation module to the client of the first channel party through the target general interface.

[0058] The first channel provider is the one that calls the general interface. In the financial business processing field, channel providers include scenario providers, funding providers, and third-party service providers. Scenario providers refer to cooperative scenarios or companies outside of financial institutions that provide platform access for financial institutions' business. Funding providers are financial institutions that provide financing and loan services. Third-party service providers are trusted service providers that offer services to scenario providers and funding providers. The second channel provider can be a different channel provider from the first.

[0059] A transaction identifier is used to identify a transaction; specifically, it can be a transaction code. The target business operation module is the business operation module of the second channel party that processes the request; specifically, the business operation module can be the logic code that processes the request.

[0060] The system identifies transaction identifiers through a target generic interface to route requests from the first channel's client via the target generic interface to the target business operation module of the second channel for processing. Specific steps include: identifying the connection identifier, channel identifier, service identifier, and operation identifier within the transaction identifier of the request from the first channel's client via the target generic interface; finding the business operation module whose channel type corresponds to the connection identifier, whose channel name corresponds to the channel identifier, whose provided service corresponds to the service identifier, and whose executed operation corresponds to the operation identifier; and routing the request from the first channel's client to the target business operation module for processing. A channel is a specific interface provider for a funding party, a scenario party, or a third-party service. Channel party categories include, for example, scenario party, funding party, or third-party service provider, used to distinguish which type of channel party it is. For example, a channel party may be the interface provider for a scenario party or the interface provider for a funding party. Each category of channel party may include multiple specific channel parties, each with its own name. The channel party name refers to the specific name of the channel party; for example, the channel party name for a scenario party might be AA. Each specific channel provider can offer one or more services, with a service identifier identifying the specific service offered by the channel provider. Each service can execute one or more operations, with an operation identifier identifying the different operations performed. The connection identifier, channel identifier, service identifier, and operation identifier can correspond to the following respectively: connection code, channel code, service code, and operation code.

[0061] Based on the connection identifier, channel identifier, service identifier, and operation identifier contained in the transaction identifiers in the request sent by the client of the first channel party, various transaction identifiers are pre-stored in the transaction identifier library of this embodiment of the invention. These transaction identifiers are called stored transaction identifiers, and special annotations are added to the stored transaction identifiers. By traversing the stored transaction identifier annotations, the business operation modules that correspond to the channel party category with the connection identifier in the transaction identifiers contained in the request, the channel party name with the channel identifier in the transaction identifiers contained in the request, the provided services with the service identifier in the transaction identifiers contained in the request, and the executed operations with the operation identifier in the transaction identifiers contained in the request can be found.

[0062] Before receiving a request from the client of the first channel party by calling the target general interface, one or more general interfaces can be predefined according to the function for the operation to be performed under various channel party categories, channel party names and services provided. One of the general interfaces is the target general interface. Each general interface corresponds to at least one channel party category, at least one channel party name, at least one service provided and at least one operation to be performed.

[0063] One or more predefined general interfaces include one or more of the following: general data interface, general file download interface, general file upload interface, general file stream proxy download interface, and general file stream download interface. These general interfaces will be described in detail below.

[0064] In one embodiment, the transaction identifier contained in the request issued by the client of the first channel party is identified through the target general interface, so as to route the request issued by the client of the first channel party through calling the target general interface to the target business operation module of the second channel party that handles the request for processing. Specifically, it may include: calling the transaction identifier management service through the target general interface, so that the transaction identifier management service can identify a first transaction identifier and at least one second transaction identifier from the transaction identifier, and route the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, and the first target business operation module and the second target business operation module handle the request respectively.

[0065] There can be two or more secondary channel partners. The first target business operation module and the second target business operation module can be the same or different business operation modules of the secondary channel partners. The two or more secondary channel partners can belong to different channel partner categories. For example, two secondary channel partners may be a scenario provider and a third-party service provider, respectively.

[0066] The processing results of the target business operation module are returned to the client of the first channel party through the target general interface. Specifically, this may include: receiving the first processing result of the first target business operation module and the second processing result of the second target business operation module through the transaction identifier management service, encapsulating the first processing result and the second processing result into a unified processing result and returning it to the client of the first channel party.

[0067] Before receiving a request from the client of the first channel party by calling the target general interface, it can be confirmed that the client of the first channel party has the interface access permission to call the target general interface.

[0068] The general interface of this invention can be provided by a connector. In one embodiment of this invention, the connector can be deployed on a container cloud service. The target general interface can be provided through the connector deployed on the container cloud service to receive requests sent by the client of the first channel party by calling the target general interface.

[0069] Before receiving a request from the client of the first channel provider via a call to the target general interface, the system can verify the client's login information for the connector. After successful login verification, it verifies whether the client has access permissions to the application of the second channel provider. Based on business needs, there is a pre-defined correspondence between the client of the first channel provider and the application of the second channel provider. This correspondence determines whether the client of the first channel provider has permission to access the application of the second channel provider. If the client has such access permissions, a JSON Web Token (JWT) is returned to the client of the first channel provider, enabling the client to include this JSON Web Token in its requests to the target general interface.

[0070] Confirm that the client of the first channel has the access permission to call the target general interface. Specifically, this may include: verifying the JSON Web token through the target general interface. If the token verification is successful, then the client of the first channel has the access permission to call the target general interface.

[0071] The request sent by the client of the first channel through calling the target general interface includes a request signature value. After receiving the request sent by the client of the first channel through calling the target general interface, the signature of the request sent by the client of the first channel can be verified first, and the signature verification is confirmed to be successful. The signature verification is used to confirm the legitimacy of the client's identity.

[0072] In one embodiment, a request sent by the client of the first channel party through calling the target general interface is routed to the target business operation module of the second channel party for processing. Specifically, this may include: determining the target business operation module of the second channel party handling the request, and providing the address of the target business operation module to the client of the first channel party, so that the client can access the address and process the request through the target business operation module. Through this implementation, the business data involved in the transaction of the first channel party in this embodiment of the invention does not need to go through the business processing system of this embodiment. Instead, the business processing system of this application only needs to provide the address of the target business operation module to the client of the first channel party, and the client can perform business processing by accessing the address, thus ensuring the data security of the first channel party and preventing data leakage.

[0073] In one embodiment, a configuration information set can be provided to the client of the first channel provider, allowing the client to select configuration information from the set. The transaction identifier in the request issued by the client of the first channel provider is generated based on the configuration information selected by the client. Specifically, the configuration information can correspond to configured atomic transaction codes. Atomic transaction codes can be established according to business needs, and multiple atomic transaction codes can generate a single transaction code, i.e., the transaction identifier. Generating transaction identifiers using configuration information avoids the problem of needing to recode for every function update due to hard-coding, which impacts development efficiency. It allows for the configuration of transaction combinations through configuration files, thereby improving development efficiency.

[0074] In one embodiment of this invention, the channel provider is a specific interface provider for a funding party, a scenario provider, or a third-party service. A scenario provider refers to a cooperative scenario or company outside of a financial institution that provides a platform entry point for the financial institution's business. A funding party refers to a financial institution that provides financing and loan services. A third-party service provider refers to a provider of trusted services for both scenario providers and funding parties. For example, a third-party service 'a' is a channel provider for electronic signature services, a funding party 'b' is a channel provider for loan services, and a scenario provider 'c' is a scenario channel provider. This embodiment of the invention solves the problem of difficult integration between funding parties, scenario providers, and third-party services by standardizing scenario access, funding party access, and third-party service access, achieving the effect of completing all integrations with a single standardization. Specifically, scenario access standardization unifies the business interfaces and data formats of scenario providers. Funding party access standardization unifies the business interfaces and data formats of funding parties. Third-party service access standardization unifies the business interfaces and data formats of third-party services. Therefore, by adapting and standardizing the API interfaces of scenario providers, third-party services, and funding parties, the goal of achieving unified integration for all funding parties, scenario providers, and third-party services with a single standardization is achieved.

[0075] Figure 2 This is a schematic diagram of a system architecture for business processing according to an embodiment of the present invention. Figure 2 As shown, taking the financial field as an example, the components in the architecture of this embodiment will be introduced first.

[0076] Funding provider APIs refer to a unified API definition for the backend systems of funding providers, which may include services such as loan services, credit card services, payment and settlement services, account management services, and lifestyle services. Funding provider adapters encapsulate the interfaces of different funding provider backend systems into a unified funding provider API interface. For example... Figure 2Funding Provider 1, Funding Provider 2, Funding Provider 3, and Funding Provider 4 are different funding providers, such as different banks. The back-end systems of each funding provider (Funding Provider 1 back-end, Funding Provider 2 back-end, Funding Provider 3 back-end, Funding Provider 4 back-end) are connected to the funding provider API interface through funding provider adapters (Funding Provider 1 adapter, Funding Provider 2 adapter, Funding Provider 3 adapter, Funding Provider 4 adapter).

[0077] A scenario-based API refers to a unified API definition for the business backend system of a scenario provider, which may include user information, loan details, and scenario-based business data. A scenario-based adapter encapsulates the interfaces of different scenario backend systems into a unified scenario-based API interface. For example... Figure 2 Scenario 1, Scenario 2, Scenario 3, and Scenario 4 are different scenario parties, such as different enterprises. The backend systems of each scenario party (Scenario 1 backend, Scenario 2 backend, Scenario 3 backend, and Scenario 4 backend) connect to the scenario party API interface through scenario party adapters (Scenario 1 adapter, Scenario 2 adapter, Scenario 3 adapter, and Scenario 4 adapter).

[0078] Third-party service APIs refer to a unified API definition for the backend systems of third-party services. These include services such as electronic signatures, ORC (optical character recognition), real-name authentication, data and risk control, anti-fraud and debt collection, authoritative information verification, and guarantees and insurance. Third-party service adapters encapsulate the backend system interfaces of different third-party service providers into a unified third-party service API interface. For example... Figure 2 Third-party services 1, 2, and 3 are different third-party services. For example, third-party service 1 is an electronic signature service, third-party service 2 is an ORC service, and third-party service 3 is a data risk control service. Each third-party service can have a specific service provider. For example, third-party services 1-1 and 1-2 can be two different service providers offering electronic signature services, third-party services 2-1 and 2-2 can be two different service providers offering ORC services, and third-party services 3-1 and 3-2 can be two different service providers offering data risk control services. The backends of each third-party service (the backends of third-party services 1-1, 1-2, 2-1, 2-2, 3-1, and 3-2) connect to the third-party service API interface through third-party service adapters (the adapters for third-party services 1-1, 1-2, 2-1, 2-2, 3-1, and 3-2).

[0079] API, or Application Programming Interface, refers to a predefined interface, generally serving as a convention for connecting software systems. Various industries have their own API standards.

[0080] The connector central control platform is responsible for providing account registration, product listing and delisting, permission application, connector management, access control and other functions for various channel parties (such as scenario parties, funding parties, and third-party services) in the embodiments of the present invention. These include, for example, an operation back-end management system, a partner back-end management system and a financial institution back-end management system.

[0081] The connector can be deployed in a distributed manner, hence it can also be called a distributed connector. It packages standardized services through API interfaces and adapters into independently deployable web applications according to different channels, and deploys them to channel servers of different scenario providers, funders, and third-party services, or on container cloud services. That is, embodiments of this invention can deploy the connector on a private network, accessible to funders and other channel providers via dedicated lines; or, the connector can be deployed on the Internet, ensuring confidentiality through interface access control and asymmetric encryption technology.

[0082] The funding party SDK is a dedicated SDK developed for funding parties that allows them to access other services, enabling them to quickly integrate into the central control platform of the distributed connector.

[0083] The scenario-side SDK is a dedicated SDK developed for scenario-side applications that allows access to other services, enabling rapid integration into the central control platform of the distributed connector.

[0084] The client application of the primary channel provider can be either a funding SDK or a scenario SDK.

[0085] In order to meet the needs of various interface functions, this invention requires the definition of standard API interfaces to satisfy the requirements of different transaction types. The definition of functional interfaces can also be implemented through configuration files.

[0086] The distributed connector defines five general interfaces (or general API interfaces) for the API, as follows:

[0087] General Data Interface: This interface is used to receive JSON object requests and return JSON object content. It is generally used as a business data interface, and the connector's transaction codes are primarily defined by this interface type. The HTTP request design is shown in Table 1.

[0088] Table 1

[0089]

[0090] General File Download Interface: This interface receives JSON object requests and returns the contents of multiple files in a JSON object to the caller. It is typically used to request multiple file contents at once, suitable for scenarios involving downloading multiple small files, such as multiple contract documents. The HTTP request design is shown in Table 2.

[0091] Table 2

[0092]

[0093] General file upload interface: This interface receives single file uploads and returns a JSON object containing the file content. Using a streaming method for uploading reduces memory usage. It is typically used in business scenarios involving file uploads, such as uploading a loan document. The HTTP request design is shown in Table 3.

[0094] Table 3

[0095]

[0096] General File Stream Proxy Download Interface: This interface receives a JSON object containing the download address of the target file and returns the target file as a stream to the caller. Using a stream for downloading reduces memory usage. It is generally used in business scenarios where a very large file is downloaded on behalf of another party, such as downloading a single loan application document file from the client. Since this interface performs proxy downloads, no transaction code is required. The HTTP request design is shown in Table 4.

[0097] Table 4

[0098]

[0099] General File Stream Download Interface: This interface receives a JSON object containing the download address of the target file and returns the file as a stream to the caller. Using a stream for downloading reduces memory usage. It is generally used in business scenarios involving downloading very large files, such as downloading evidence report files from a third-party signing service. The HTTP request design is shown in Table 5.

[0100] Table 5

[0101]

[0102] The transaction code, or transaction identifier, in this embodiment of the invention is an example. The transaction code defines the transaction number of a single transaction. The general interface identifies the transaction code, forwards the request from the client of the first channel to the method of the specific business adapter, and returns the corresponding content. The method of the specific business adapter is the target business operation module to process the request, and the returned content is the processing result of the request.

[0103] In one embodiment of the present invention, the transaction identifier, namely the transaction code (transCode), consists of a 1-digit connector code (connectorCode), a 4-digit channel code (channelCode), a 4-digit service code (serviceCode), and a 4-digit action code (actionCode). The specific descriptions of each part are as follows.

[0104] Connector code, also known as connection code, is a connection identifier consisting of a single letter. For example, T represents a third-party service, S represents the scenario provider, and B represents the funding provider.

[0105] The channel code, or channel identifier, consists of 4 digits and represents the vendor providing the service. It corresponds to the name of the provider of the signature service and is the specific implementation of the service code.

[0106] A service code is a 4-digit number used to define a specific service, such as a signature service.

[0107] An action code, or action identifier, consists of four digits and is used to define a single specific transaction operation provided under a specific service, such as the signature verification operation under the signature service.

[0108] A specific example of a transaction code is T100110010001, where T represents a third-party service (S represents the scenario provider, B represents the funding provider), 1001 represents the specific provider of that third-party service, corresponding to the provider's name, 1001 indicates the signature service, and 0001 indicates the operation of downloading the evidence preservation report. Through this transaction code T100110010001, one can be routed to the operation of downloading the evidence preservation report under the signature service provided by a specific third-party service provider.

[0109] The distributed connector in this application includes dedicated annotations for each existing transaction code, used for service loading and routing during application startup. An example of the annotation is as follows:

[0110] ConnectorCode: Used to define the connector type (i.e., channel type).

[0111] ChannelCode: User-defined channel type (i.e., channel provider name).

[0112] ServiceCode: Used to define the service type (indicating the service provided).

[0113] ActionCode: User-defined action type (indicating the action to be performed).

[0114] Taking the signature service as an example, the connector can use the Transaction Code Management Service (TransCodeService, i.e., Transaction Identifier Management Service) to implement the functions of traversing transaction code annotations and request routing. Based on the connection code, channel code, service code, and action code in the transaction code carried in the request, it traverses the existing transaction code annotations, that is, it traverses the ConnectorCode, ChannelCode, ServiceCode, and ActionCode of each existing transaction code to find the connection code corresponding to the channel type, the channel code corresponding to the channel name, the service corresponding to the service code, and the business operation module corresponding to the action code.

[0115] The routing function of the TransCodeService allows multiple transaction codes to be combined into a single transaction code to enable combined trading. Figure 3 This is a schematic diagram of the process for implementing combined transactions in the business processing according to an embodiment of the present invention, such as... Figure 3 As shown, for example, the client of the first channel sends a request to call the general interface (S301). The request includes transaction code A (i.e., the transaction identifier in the request). The general interface calls the transaction code management service (S302). The transaction code management service routes the request to the business operation module corresponding to transaction code B (an example of the first transaction identifier) ​​and the business operation module corresponding to transaction code C (an example of the second transaction identifier) ​​respectively (S303, S304). The business operation modules corresponding to transaction code B and transaction code C are processed respectively. Steps S303 and S304 can be performed simultaneously. The processing results of the business operation module corresponding to transaction code B and the business operation module corresponding to transaction code C are received by the transaction code management service respectively (S305, S306). The execution order of steps S305 and S306 is not restricted by the order of the step numbers. The two processing results are encapsulated into a unified processing result and returned to the client of the first channel party. Specifically, the transaction code management service first returns the unified processing result to the general interface (S307), and then returns it to the client of the first channel party through the general interface (S308).

[0116] In this embodiment of the invention, both the server and client use HTTPS (Hypertext Transfer Protocol Secure). The server is the business processing system of this embodiment, and the client is the client of the first channel party, such as the funding party's SDK or the scenario party's SDK. The server signs and verifies all requests sent by the client. All requests must undergo signature verification, and the request signature parameters are placed in the HTTP Request Header. The specific parameters are shown in Table 6 below. The signature algorithm is SHA256 (an algorithm derived from SHA-2, a cryptographic hash function algorithm standard).

[0117] Table 6

[0118]

[0119]

[0120] An example of the text to be signed is shown in Table 7.

[0121] Table 7

[0122]

[0123] The distributed connector in this embodiment of the invention adopts the OAuth 2.0 standard (a continuation of the OAuth protocol) and uses JWT (JSON Web Token) to implement authentication and access control. The channel provider's SDK (client) and the distributed connector store their own PublicKey, while the central control platform stores the PrivateKey. Figure 4 This is a flowchart illustrating the process of verifying interface access permissions in a business process according to an embodiment of the present invention, as shown below. Figure 4 As shown,

[0124] Step S401: The client of the first channel (e.g., a channel SDK) logs in to the connector and requests to obtain a JSONWeb token.

[0125] The JSON Web Token (JWT) can have an expiration time set, such as 2 hours.

[0126] Step S402: The connector verifies the login information of the client from the first channel. If the login information verification fails, proceed to step S407. If the login information verification succeeds, proceed to step S403.

[0127] Login information includes the username, password, and other information of the client from the primary channel provider.

[0128] Step S403: Verify whether the client of the first channel has access permission to access the application of the second channel. If it has such access permission, proceed to step S404; otherwise, proceed to step S407.

[0129] The mapping between clients and accessible applications can be pre-saved to verify whether the client of the first channel has access rights to access the application of the second channel.

[0130] Step S404: Return a JSON Web token to the client of the first channel party so that the JSON Web token is included in the requests issued by the client of the first channel party.

[0131] The client of the first channel carries the JSON Web Token in the request, for example, when requesting the connector via a URL (Uniform Resource Locator).

[0132] Step S405: Verify the JSON Web token through the target general interface to be called by the client of the first channel. If the JSON Web token is verified, continue to step S406; otherwise, jump to step S407.

[0133] Step S406: Determine that the client of the first channel party has the interface access permission to call the target general interface.

[0134] If the JSON Web token verification is successful, it means that the client of the first channel has successfully verified its access rights to the target general interface. The JSON Web token can be verified using the private key stored on the central control platform.

[0135] Step S407: It is determined that the client of the first channel does not have the interface access permission to call the target general interface.

[0136] This invention addresses the challenge of interfacing with funding providers, scenario providers, and third-party services in the financial sector by defining and adapting API interfaces for different channels. A connector control platform (hereinafter referred to as the control platform) controls identity and interface permissions, and provides SDKs for funding providers and scenario providers to call the standard APIs, thus shielding the different underlying implementations of each channel. This solves the problem of difficult integration between funding providers, scenario providers, and third-party services in the financial field, achieving standardized integration between different systems in a single step. In this invention, the specific business data of the first and second channel providers does not need to be submitted to the control platform or connector, ensuring data security.

[0137] Figure 5 This is a schematic diagram of the main modules of a business processing system according to an embodiment of the present invention; as shown below. Figure 5As shown, a business processing system 500 according to an embodiment of the present invention mainly includes: a request receiving module 501, a request routing module 502, and a result returning module 503.

[0138] The request receiving module 501 is used to receive a request sent by the client of the first channel party through calling the target general interface, the request including a transaction identifier. The request routing module 502 is used to identify the transaction identifier in the request through the target general interface, so as to route the request to the target business operation module of the second channel party that handles the request for processing.

[0139] Result return module 503 is used to return the processing results of the target business operation module to the client of the first channel party through the target general interface.

[0140] The request routing module 502 is specifically used to: identify the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier through the target general interface; find the business operation module that corresponds to the channel type with the connection identifier, the channel name with the channel identifier, the provided service with the service identifier, and the executed operation with the operation identifier, and use it as the target business operation module, and route the request sent by the client of the first channel to the target business operation module for processing.

[0141] Based on the connection identifier, channel identifier, service identifier, and operation identifier contained in the transaction identifier contained in the request, the existing transaction identifier annotations can be traversed to find the business operation module that corresponds to the channel type, the channel name, the service provided, the operation performed, and the operation performed.

[0142] The business processing system 500 may also include a general interface creation module for: pre-defining one or more general interfaces according to functions for operations performed under various channel types, channel names and services provided, where one of the general interfaces is the target general interface, and each general interface corresponds to at least one channel type, at least one channel name, at least one service provided and at least one operation performed.

[0143] In one embodiment, one or more predefined general interfaces may include one or more of the following: a general data interface, a general file download interface, a general file upload interface, a general file stream proxy download interface, and a general file stream download interface.

[0144] In one embodiment, the request routing module 502 is specifically used to: call the transaction identifier management service through the target general interface, so that the transaction identifier management service can identify the first transaction identifier and at least one second transaction identifier from the transaction identifiers in the above request, and route the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, and the first target business operation module and the second target business operation module process them respectively.

[0145] The number of second channel partners can be two or more, and the first target business operation module and the second target business operation module can be the same or different business operation modules of the second channel partners.

[0146] Specifically, the result return module 503 can be used to: receive the first processing result of the first target business operation module and the second processing result of the second target business operation module through the transaction identifier management service, encapsulate the first processing result and the second processing result into a unified processing result and return it to the client of the first channel party.

[0147] The business processing system 500 may also include an access permission verification module, used to: confirm that the client of the first channel party has the interface access permission to call the target general interface.

[0148] A target generic interface can be provided through connectors deployed on container cloud services to receive requests from clients of the first channel party by calling the target generic interface.

[0149] The business processing system 500 may also include a token providing module for: verifying the login information of the first channel party's client to the connector; after the login information is verified, verifying whether the first channel party's client has access rights to access the second channel party's application; if it has such access rights, returning a JSON Web token to the first channel party's client so that the request carries the JSON Web token.

[0150] The access permission verification module can be used to: verify JSON Web tokens through the target general interface. If the token verification is successful, the client of the first channel party has the interface access permission to call the target general interface.

[0151] The request sent by the client of the first channel through calling the target general interface may include a request signature value. The business processing system 500 may also include a signature verification module, which is used to: after the request receiving module 501 receives the request sent by the client of the first channel through calling the target general interface, first verify the signature of the request, and determine that the signature verification is successful.

[0152] The request routing module 502 is further configured to: determine the target business operation module of the second channel party that handles the request, and provide the address of the target business operation module to the client of the first channel party, so that the client of the first channel party can access the address and process the request through the target business operation module.

[0153] The business processing system 500 may also include a configuration module for: providing a set of configuration information to the client of the first channel party, so that the client of the first channel party can select configuration information from the set of configuration information, and the transaction identifier in the request is generated based on the configuration information selected by the client of the first channel party.

[0154] The business processing system 500 based on the embodiments of the present invention, referring to the above embodiments... Figure 2 The architecture shown includes a request receiving module 501, a request routing module 502, a result return module 503, and an access permission verification module, which can be located within the connector. The token providing module can be located in the connector's central control platform. The general interface creation module and configuration module can be located on a separate server. The business operation module can be the logic code of the scenario provider, funding provider, or third-party service backend.

[0155] Furthermore, the specific implementation details of the business processing system described in this embodiment of the invention have been explained in detail in the business processing method described above, so the details will not be repeated here.

[0156] Figure 6 An exemplary system architecture 600 is shown that can be applied to the business processing method or business processing system of the present invention.

[0157] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0158] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0159] Terminal devices 601, 602, and 603 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0160] Server 605 can be a server that provides various services, such as a backend management server that supports shopping websites browsed by users using terminal devices 601, 602, and 603 (for example only). The backend management server can analyze and process data such as received product information query requests, and feed back the processing results (such as target push information, product information - for example only) to the terminal devices.

[0161] It should be noted that the business processing method provided in the embodiments of the present invention is generally executed by server 605, and correspondingly, the business processing system is generally set in server 605.

[0162] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0163] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing the server of the embodiments of this application. Figure 7 The server shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0164] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0165] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0166] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this application.

[0167] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0168] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0169] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a request receiving module, a request routing module, and a result returning module. The names of these modules do not necessarily limit the module itself; for example, the request receiving module can also be described as "a module for receiving requests sent by a client of a first channel party through calling a target general interface."

[0170] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: receiving a request from a client of a first channel party by invoking a target general interface, the request including a transaction identifier; identifying the transaction identifier through the target general interface to route the request to a target business operation module of a second channel party for processing; and returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

[0171] In another aspect, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the business processing method of the embodiments of the present invention.

[0172] According to the technical solution of this invention, a request is received from a client of a first channel party by calling a target general interface. This request includes a transaction identifier. The transaction identifier is identified through the target general interface, and the request is routed to a target business operation module of a second channel party for processing. The processing result of the target business operation module is then returned to the client of the first channel party through the target general interface. This standardization of access enables different channel parties to connect without needing to adapt to the interfaces of other channel parties, solving the problem of difficult connection and reducing system security risks.

[0173] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A business processing method, characterized in that, include: Receive a request from the client of the first channel party by calling the target general interface, the request including a transaction identifier; The transaction identifier is identified through the target general interface so that the request is routed to the target business operation module of the second channel party that handles the request for processing; The processing result of the target business operation module is returned to the client of the first channel party through the target general interface; The method further includes providing a configuration information set to the client of the first channel party, so that the client of the first channel party can select configuration information from the configuration information set, and the transaction identifier in the request is generated based on the configuration information selected by the client of the first channel party; the configuration information corresponds to the configuration atomic transaction code, and a transaction identifier can be generated based on multiple atomic transaction codes; Channel providers are the specific interface providers for funding providers, scenario providers, or third-party services; Funding provider API refers to the unified API definition for the funding provider's backend system, and funding provider adapter refers to the encapsulation of different funding provider backend system interfaces into a unified funding provider API interface, through which each funding provider backend system interfaces with the funding provider API interface; Scenario provider API refers to the unified API definition for the scenario provider's business backend system, and scenario provider adapter refers to the encapsulation of different scenario backend system interfaces into a unified scenario provider API interface, through which each scenario provider backend system interfaces with the scenario provider API interface. Third-party service API refers to a unified API definition for the backend system of third-party services. Third-party service adapter refers to encapsulating the backend system interfaces of different third-party service providers into a unified third-party service API interface. Each third-party service backend interfaces with the third-party service API interface through its third-party service adapter. The target general interface is provided through the connector to receive requests from the client of the first channel party by calling the target general interface; The step of routing the request to the target business operation module of the second channel party for processing includes: determining the target business operation module of the second channel party for processing the request, and providing the address of the target business operation module to the client of the first channel party, so that the client of the first channel party can access the address and process the request through the target business operation module.

2. The method according to claim 1, characterized in that, The step of identifying the transaction identifier through the target general interface to route the request to the target business operation module of the second channel party for processing includes: The connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier are identified through the target general interface; The system finds the business operation module that corresponds to the channel type, the channel name, the service provided, the operation performed, and the operation performed, and identifies it as the target business operation module. The system then routes the request to the target business operation module for processing.

3. The method according to claim 2, characterized in that, Based on the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier, traverse the existing transaction identifier annotations to find the channel type corresponding to the connection identifier, the channel name corresponding to the channel identifier, the service provided corresponding to the service identifier, and the operation performed corresponding to the business operation module of the operation identifier.

4. The method according to claim 2, characterized in that, Before the client of the first channel party sends a request by calling the target general interface, the process includes: For operations performed under various channel categories, channel names, and provided services, one or more general interfaces are predefined according to functions, one of which is the target general interface, and each general interface corresponds to at least one channel category, at least one channel name, at least one provided service, and at least one of the performed operations.

5. The method according to claim 4, characterized in that, The predefined one or more general interfaces include one or more of the following: general data interface, general file download interface, general file upload interface, general file stream proxy download interface, and general file stream download interface.

6. The method according to claim 1, characterized in that, The transaction identifier is identified through the target general interface, and the request is routed to the target business operation module of the second channel party for processing, including: The transaction identifier management service is invoked through the target general interface, so that the transaction identifier management service can identify a first transaction identifier and at least one second transaction identifier from the transaction identifiers, and route the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, and the first target business operation module and the second target business operation module process them respectively.

7. The method according to claim 6, characterized in that, The number of second channel parties is two or more, and the first target business operation module and the second target business operation module are the same or different business operation modules of the second channel parties.

8. The method according to claim 6, characterized in that, The step of returning the processing result of the target business operation module to the client of the first channel party through the target general interface includes: The transaction identifier management service receives the first processing result from the first target business operation module and the second processing result from the second target business operation module, encapsulates the first processing result and the second processing result into a unified processing result, and returns it to the client of the first channel party.

9. The method according to claim 1, characterized in that, Before the client of the first channel party sends a request by calling the target general interface, the process includes: Confirm that the client of the first channel provider has the interface access permission to call the target general interface.

10. The method according to claim 9, characterized in that, The target generic interface is provided through connectors deployed on container cloud services.

11. The method according to claim 10, characterized in that, Before the client of the first channel party sends a request by calling the target general interface, the method further includes: Verify the login information of the first channel party's client to the connector. After the login information is verified, verify whether the first channel party's client has access to the second channel party's application. If it has such access, return a JSON Web token to the first channel party's client so that the request carries the JSON Web token. The step of confirming that the client of the first channel party has interface access permissions to call the target general interface includes: The JSON Web token is verified through the target general interface. If the token verification is successful, the client of the first channel party has interface access permission to call the target general interface.

12. The method according to claim 1, characterized in that, The request sent by the client of the first channel party through calling the target general interface includes a request signature value; The method further includes: after receiving a request sent by the client of the first channel party through calling the target general interface, first performing signature verification on the request, and determining that the signature verification is successful.

13. A business processing system, characterized in that, include: The request receiving module is used to receive a request sent by the client of the first channel party through calling the target general interface, the request including a transaction identifier; The request routing module is used to identify the transaction identifier through the target general interface, so as to route the request to the target business operation module of the second channel party that processes the request for processing; The result return module is used to return the processing result of the target business operation module to the client of the first channel party through the target general interface; The configuration module is used to: provide a set of configuration information to the client of the first channel party, so that the client of the first channel party can select configuration information from the set of configuration information, wherein the transaction identifier in the request is generated based on the configuration information selected by the client of the first channel party; the configuration information corresponds to the configuration atomic transaction code, and a transaction identifier can be generated based on multiple atomic transaction codes; Channel providers are the specific interface providers for funding providers, scenario providers, or third-party services; Funding provider API refers to the unified API definition for the funding provider's backend system, and funding provider adapter refers to the encapsulation of different funding provider backend system interfaces into a unified funding provider API interface, through which each funding provider backend system interfaces with the funding provider API interface; Scenario provider API refers to the unified API definition for the scenario provider's business backend system, and scenario provider adapter refers to the encapsulation of different scenario backend system interfaces into a unified scenario provider API interface, through which each scenario provider backend system interfaces with the scenario provider API interface. Third-party service API refers to a unified API definition for the backend system of third-party services. Third-party service adapter refers to encapsulating the backend system interfaces of different third-party service providers into a unified third-party service API interface. Each third-party service backend interfaces with the third-party service API interface through its third-party service adapter. The connector provides the target general interface to receive requests sent by the client of the first channel party by calling the target general interface; the request routing module is further configured to: determine the target business operation module of the second channel party that processes the request, and provide the address of the target business operation module to the client of the first channel party, so that the client of the first channel party can access the address and process the request through the target business operation module.

14. The system according to claim 13, characterized in that, The request routing module is also used for: The connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier are identified through the target general interface; The system finds the business operation module that corresponds to the channel type, the channel name, the service provided, the operation performed, and the operation performed, and identifies it as the target business operation module. The system then routes the request to the target business operation module for processing.

15. The system according to claim 14, characterized in that, Based on the connection identifier, channel identifier, service identifier, and operation identifier in the transaction identifier, traverse the existing transaction identifier annotations to find the channel type corresponding to the connection identifier, the channel name corresponding to the channel identifier, the service provided corresponding to the service identifier, and the operation performed corresponding to the business operation module of the operation identifier.

16. The system according to claim 14, characterized in that, It also includes a general interface creation module for: For operations performed under various channel categories, channel names, and provided services, one or more general interfaces are predefined according to functions, one of which is the target general interface, and each general interface corresponds to at least one channel category, at least one channel name, at least one provided service, and at least one of the performed operations.

17. The system according to claim 16, characterized in that, The predefined one or more general interfaces include one or more of the following: general data interface, general file download interface, general file upload interface, general file stream proxy download interface, and general file stream download interface.

18. The system according to claim 13, characterized in that, The request routing module is also used for: The transaction identifier management service is invoked through the target general interface, so that the transaction identifier management service can identify a first transaction identifier and at least one second transaction identifier from the transaction identifiers, and route the request to the first target business operation module corresponding to the first transaction identifier and the second target business operation module corresponding to the second transaction identifier, respectively, and the first target business operation module and the second target business operation module process them respectively.

19. The system according to claim 18, characterized in that, The number of second channel parties is two or more, and the first target business operation module and the second target business operation module are the same or different business operation modules of the second channel parties.

20. The system according to claim 18, characterized in that, The result return module is also used for: The transaction identifier management service receives the first processing result from the first target business operation module and the second processing result from the second target business operation module, encapsulates the first processing result and the second processing result into a unified processing result, and returns it to the client of the first channel party.

21. The system according to claim 13, characterized in that, It also includes an access permission verification module, used for: Confirm that the client of the first channel provider has the interface access permission to call the target general interface.

22. The system according to claim 21, characterized in that, The target generic interface is provided through connectors deployed on container cloud services.

23. The system according to claim 22, characterized in that, It also includes a token providing module for: Verify the login information of the first channel party's client to the connector. After the login information is verified, verify whether the first channel party's client has access to the second channel party's application. If it has such access, return a JSON Web token to the first channel party's client so that the request carries the JSON Web token. The access permission verification module is also used for: The JSON Web token is verified through the target general interface. If the token verification is successful, the client of the first channel party has interface access permission to call the target general interface.

24. The system according to claim 13, characterized in that, The request sent by the client of the first channel party through calling the target general interface includes a request signature value; The system further includes a signature verification module, which is used to: after the request receiving module receives a request sent by the client of the first channel party through calling the target general interface, first verify the signature of the request and determine that the signature verification is successful.

25. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method as described in any one of claims 1-12.

26. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-12.

27. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-12.

Images