CN114049122A

CN114049122A - Service processing method and system

Info

Publication number: CN114049122A
Application number: CN202111439481.2A
Authority: CN
Inventors: 郑富伟; 黄显龙
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2022-02-15

Abstract

The invention discloses a business processing method and a business processing system, and relates to the technical field of financial information services. One embodiment of the method comprises: receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier, identifying the transaction identifier through the target universal interface so as to route the request to a target business operation module of a second channel party for processing the request, and returning a processing result of the target business operation module to the client of the first channel party through the target universal interface. The embodiment can realize the standardization of access, so that different channel parties do not need to be adapted to interfaces of other channel parties when in butt joint, the problem of difficult butt joint is solved, and the safety risk of a channel party system is reduced.

Description

Service processing method and system

Technical Field

The invention relates to the technical field of financial information services, in particular to a business processing method and a business processing system.

Background

With the continuous development of domestic and popular financial business, besides the traditional business model in the institution, the financial institution is continuously cooperating with external scene parties (refer to cooperation scenes or companies outside the institution providing platform entrance for the financial institution business), and the financial institution is used as a fund party to butt up different scene parties and provides targeted financial information service by combining scene characteristics.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

in the process of docking different channel parties (such as a fund party, a scene party and a third-party service), the fund party needs to adapt to the interfaces of different scene parties; the funder needs to adapt to the interface of different third party services; the fund party, the scene party and the third-party service need to sign a three-party contract so that the fund party can directly access the third-party service to obtain related information, and therefore the multi-party docking difficulty is increased; the funding party needs to access a large number of third party services through the internet, increasing the security risk of the system.

Disclosure of Invention

In view of this, embodiments of the present invention provide a service processing method and system, which can implement standardization of interface access, so that when different channel parties are docked, interfaces of other channel parties do not need to be adapted, the problem of difficulty in docking is solved, and the security risk of the channel party system is reduced.

To achieve the above object, according to an aspect of an embodiment of the present invention, a service processing method is provided.

A service processing method comprises the following steps: receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier; identifying the transaction identification through the target universal interface so as to route the request to a target business operation module of a second channel party processing the request 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.

Optionally, the identifying the transaction identifier through the target generic interface to route the request to a target service operation module of a second channel party processing the request for processing includes: identifying a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier through the target universal interface; and searching the channel party category corresponding to the connection identifier, the channel party name corresponding to the channel identifier, and the provided service corresponding to the service identifier and the executed operation corresponding to the service operation module of the operation identifier, serving as the target service operation module, and routing the request to the target service operation module for processing.

Optionally, traversing each stored transaction identifier annotation according to a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier to find out that the channel party category corresponds to the connection identifier, the channel party name corresponds to the channel identifier, and the provided service corresponds to the service identifier and the executed operation corresponds to the business operation module of the operation identifier.

Optionally, before receiving the request sent by the client of the first channel party by invoking the target generic interface, the method includes: one or more universal interfaces are predefined according to functions aiming at operations executed under various channel party categories, channel party names and provided services, wherein one universal interface is the target universal interface, and each universal interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one executed operation.

Optionally, the one or more predefined common interfaces include one or more of a common data interface, a common file download interface, a common file upload interface, a common file stream proxy download interface, and a common file stream download interface.

Optionally, identifying the transaction identifier through the target generic interface to route the request to a target service operation module of a second channel party processing the request for processing includes: and calling a transaction identifier management service through the target universal 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 respectively routes the request to a first target service operation module corresponding to the first transaction identifier and a second target service operation module corresponding to the second transaction identifier, and the first target service operation module and the second target service operation module respectively process the requests.

Optionally, the number of the second channel parties is two or more, and the first target service operation module and the second target service operation module are the same or different service operation modules of the second channel parties.

Optionally, the returning the processing result of the target service operation module to the client of the first channel party through the target generic interface includes: and receiving a first processing result of the first target business operation module and a second processing result of the second target business operation module through the transaction identifier management service, packaging the first processing result and the second processing result into a uniform processing result, and returning the uniform processing result to the client of the first channel party.

Optionally, before receiving the request sent by the client of the first channel party by invoking the target generic interface, the method includes: and confirming that the client of the first channel side has an interface access right for calling the target universal interface.

Optionally, the target generic interface is provided through a connector deployed on the container cloud service to receive a request sent by the client of the first channel party by calling the target generic interface.

Optionally, before receiving the request sent by the client of the first channel party by invoking the target generic interface, the method further includes: verifying login information of the client of the first channel party to the connector, verifying whether the client of the first channel party has an access right for accessing the application of the second channel party after the login information is verified, and if the client of the first channel party has the access right, returning a JSON (JavaScript Object Notification) Web token to the client of the first channel party so as to enable the JSON Web token to be carried in the request; the confirming that the client of the first channel side has the interface access authority for calling the target universal interface comprises the following steps: and verifying the JSON Web token through the target general interface, wherein if the token is verified to be passed, the client of the first channel party has an interface access right for calling the target general interface.

Optionally, the request sent by the client of the first channel party by calling the target universal interface includes a request signature value; the method further comprises the following steps: after receiving a request sent by a client of a first channel party by calling a target universal interface, firstly carrying out signature verification on the request and determining that the signature verification is passed.

Optionally, the routing the request to a target service operation module of a second channel party processing the request for processing includes: and determining a target business operation module of a second channel party for processing the request, providing the address of the target business operation module for the client of the first channel party so that the client of the first channel party accesses the address, and processing the request through the target business operation module.

Optionally, the method further includes providing a configuration information set to the client of the first channeling party, so that the client of the first channeling party selects configuration information from the configuration information set, and the transaction identifier in the request is generated according to the configuration information selected by the client of the first channeling party.

According to another aspect of the embodiments of the present invention, a service processing system is provided.

A business processing system comprising: the request receiving module is used for receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier; the request routing module is used for identifying the transaction identifier through the target general interface so as to route the request to a target business operation module of a second channel party processing the request for processing; and the result returning module is used for returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

Optionally, the request routing module is further configured to: identifying a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier through the target universal interface; and searching the channel party category corresponding to the connection identifier, the channel party name corresponding to the channel identifier, and the provided service corresponding to the service identifier and the executed operation corresponding to the service operation module of the operation identifier, serving as the target service operation module, and routing the request to the target service operation module for processing.

Optionally, the system further comprises a common interface creating module, configured to: one or more universal interfaces are predefined according to functions aiming at operations executed under various channel party categories, channel party names and provided services, wherein one universal interface is the target universal interface, and each universal interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one executed operation.

Optionally, the request routing module is further configured to: and calling a transaction identifier management service through the target universal 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 respectively routes the request to a first target service operation module corresponding to the first transaction identifier and a second target service operation module corresponding to the second transaction identifier, and the first target service operation module and the second target service operation module respectively process the requests.

Optionally, the result returning module is further configured to: and receiving a first processing result of the first target business operation module and a second processing result of the second target business operation module through the transaction identifier management service, packaging the first processing result and the second processing result into a uniform processing result, and returning the uniform processing result to the client of the first channel party.

Optionally, the system further comprises an access right verification module, configured to: and confirming that the client of the first channel side has an interface access right for calling the target universal interface.

Optionally, the system further comprises a token providing module, configured to: verifying login information of the client of the first channel party to the connector, verifying whether the client of the first channel party has an access right for accessing the application of the second channel party after the login information is verified, and returning a JSON Web token to the client of the first channel party if the client of the first channel party has the access right so that the JSON Web token is carried in the request; the access right verification module is further configured to: and verifying the JSON Web token through the target general interface, wherein if the token is verified to be passed, the client of the first channel party has an interface access right for calling the target general interface.

Optionally, the request sent by the client of the first channel party by calling the target universal interface includes a request signature value; the system further includes a signature verification module to: after the request receiving module receives a request sent by a client of the first channel party by calling a target universal interface, signature verification is firstly carried out on the request, and the signature verification is confirmed to be passed.

Optionally, the request routing module is further configured to: and determining a target business operation module of a second channel party for processing the request, providing the address of the target business operation module for the client of the first channel party so that the client of the first channel party accesses the address, and processing the request through the target business operation module.

Optionally, the system further comprises a configuration module, configured to: and 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, wherein the transaction identifier in the request is generated according to the configuration information selected by the client of the first channel party.

According to yet another aspect of an embodiment of the present invention, an electronic device is provided.

An electronic device, comprising: one or more processors; 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 service processing method provided by the embodiments of the present invention.

According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.

A computer-readable medium, on which a computer program is stored, which, when executed by a processor, implements a service processing method provided by an embodiment of the present invention.

According to yet another aspect of an embodiment of the present invention, a computer program product is provided.

A computer program product comprising a computer program which, when executed by a processor, implements a method of service processing as provided by an embodiment of the invention.

One embodiment of the above invention has the following advantages or benefits: and identifying a transaction identifier carried by a request sent by the client of the first channel party through the target universal interface so as to route the request to a target service operation module of a second channel party for processing the request, and returning a corresponding processing result to the client of the first channel party through the target universal interface. The standardization of interface access can be realized for different channel parties, so that the different channel parties do not need to be adapted to the interfaces of other channel parties when in butt joint, the problem of difficult butt joint is solved, the safety risk of a channel party system is reduced, in addition, only the address of a target business operation module needs to be provided for the client side of the first channel party, the client side of the first channel party carries out business processing by accessing the address, the data safety of the first channel party is ensured, and data leakage is prevented.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram of main steps of a service processing method according to an embodiment of the present invention;

FIG. 2 is a system architecture diagram of a business process, according to one embodiment of the invention;

FIG. 3 is a flow diagram illustrating the implementation of a combined transaction in a business process, according to one embodiment of the invention;

FIG. 4 is a flow diagram illustrating the process of verifying access rights to an interface in a business process according to one embodiment of the invention;

FIG. 5 is a schematic diagram of the main modules of a business processing system in accordance with one embodiment of the present invention;

FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

FIG. 7 is a schematic block diagram of a computer system suitable for use with a server implementing an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

According to the technical scheme, the data acquisition, storage, use, processing and the like meet relevant regulations of national laws and regulations.

Fig. 1 is a schematic diagram of main steps of a service processing method according to an embodiment of the present invention. As shown in fig. 1, the service processing method according to an embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier;

step S102: identifying the transaction identifier in the request through a target universal interface so as to route the request to a target service operation module of a second channel party processing the request for processing;

step S103: and returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

The first channel party is a channel party calling a general interface, and in the field of financial business processing, the channel party is a scene party, a fund party and a third-party service party. The scenario party refers to a collaboration scenario or company outside the financial institution that provides platform access for financial institution services. The funder refers to a financial institution that provides financing loan services. Third party services refer to providers that provide trusted services for the scenic and funding parties. The second channelizer may be a different channelizer than the first channelizer.

The transaction identifier is used to identify a transaction, and may be a transaction code. The target service operation module is a service operation module of the second channel side for processing the request, and the service operation module may be specifically a logic code for processing the request.

Identifying the transaction identifier through the target universal interface so as to route the request sent by the client of the first channel party to the target service operation module of the second channel party for processing the request by calling the target universal interface, wherein the specific steps can include: identifying a connection identifier, a channel identifier, a service identifier and an operation identifier in a transaction identifier contained in a request sent by calling a target universal interface by a client of a first channel party through the target universal interface; searching the channel party category corresponding to the connection identifier, the channel party name corresponding to the channel identifier, the service operation module of which the provided service corresponds to the service identifier and the executed operation corresponds to the operation identifier, serving as a target service operation module, and routing the request sent by the client of the first channel party to the target service operation module for processing. The channel party is a specific interface provider of the fund party, the scene party or the third party service. The categories of the channel parties are three categories, such as a scenic party, a funder party or a third-party service party, and are used for distinguishing which channel party is, for example, an interface provider of a scenic party or an interface provider of a funder party. Each category of channel party may comprise a plurality of specific different channel parties, each having a respective name, the name of a channel party being the name of a specific channel party, for example, the name AA of a channel party of a certain scene party. Each particular channel side may provide one or more services, and the service identification is used to identify the particular service provided by the channel side. One or more operations may be performed under each service, with the operation identification identifying the different operations performed. The connection identifier, the channel identifier, the service identifier and the operation identifier may respectively correspond to specifically: connection code, channel code, service code, operation code.

The method comprises the steps that various transaction identifications are prestored in a transaction identification library according to a connection identification, a channel identification, a service identification and an operation identification in the transaction identification contained in a request sent by a client of a first channel party, the transaction identifications are called stored transaction identifications, special annotations are added to the stored transaction identifications, the connection identification in the transaction identification contained in the request corresponding to the type of the channel party can be found out by traversing the stored transaction identification annotations, the name of the channel party corresponds to the channel identification in the transaction identification contained in the request, the provided service corresponds to the service identification in the transaction identification contained in the request, and the executed operation corresponds to the service operation module of the operation identification in the transaction identification contained in the request.

Before receiving a request sent by a client of a first channel party by calling a target universal interface, one or more universal interfaces can be predefined according to functions aiming at operations executed under various channel party categories, channel party names and provided services, wherein one universal interface is the target universal interface, and each universal interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one executed operation.

The predefined one or more common interfaces include one or more of a common data interface, a common file download interface, a common file upload interface, a common file stream proxy download interface, and a common file stream download interface. Various general interfaces will be described in detail below.

In an embodiment, identifying, by the target generic interface, a transaction identifier included in a request issued by a client of the first channel party, so as to route the request issued by the client of the first channel party to a target service operation module of a second channel party, which processes the request, by invoking the target generic interface, may specifically include: and calling a transaction identifier management service through the target universal interface so that the transaction identifier management service identifies a first transaction identifier and at least one second transaction identifier from the transaction identifier, and respectively routing the request to a first target service operation module corresponding to the first transaction identifier and a second target service operation module corresponding to the second transaction identifier, and respectively processing the request by the first target service operation module and the second target service operation module.

The number of the second channel parties 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 parties. Two or more second channelizers may belong to different categories of channelizers, e.g. some two second channelizers serve the scenic and third parties, respectively.

Returning the processing result of the target service operation module to the client of the first channel party through the target general interface, which may specifically include: and receiving a first processing result of the first target business operation module and a second processing result of the second target business operation module through the transaction identifier management service, packaging the first processing result and the second processing result into a uniform processing result, and returning the uniform processing result to the client of the first channel party.

Before receiving a request sent by the client of the first channel party by calling the target universal interface, the client of the first channel party can be confirmed to have the interface access authority for calling the target universal interface.

The universal interface of the embodiment of the invention can be provided by a connector, the connector of the embodiment of the invention can be deployed on the container cloud service, and a target universal interface can be provided by the connector deployed on the container cloud service so as to receive a request sent by a client of a first channel party by calling the target universal interface.

Before receiving a request sent by a client of a first channel party by calling a target universal interface, the client of the first channel party can also verify the login information of the client of the first channel party to a connector, after the login information is verified, whether the client of the first channel party has the access authority of accessing the application of a second channel party is verified, a preset corresponding relation exists between the client of the first channel party and the application of the second channel party according to business needs, and whether the client of the first channel party has the authority of accessing the second channel party can be judged according to the corresponding relation. And if the access authority is provided, returning a JSON Web token (JWT for short) to the client of the first channel party so that the JSON Web token is carried in a request sent by the client of the first channel party by calling the target universal interface.

Confirming that the client of the first channel side has an interface access right for calling the target universal interface specifically includes: and verifying the JSON Web token through the target general interface, wherein if the token is verified to be passed, the client of the first channel party has an interface access right for calling the target general interface.

The request issued by the client of the first channel side by calling the target generic interface includes a request signature value. After receiving a request sent by a client of a first channel party by calling a target universal interface, signature verification can be performed on the request sent by the client of the first channel party, and the signature verification is determined to be passed, wherein the signature verification is used for confirming that the identity of the client is legal.

In an embodiment, the routing, by a client of a first channel party, a request sent by invoking a target universal interface to a target service operation module of a second channel party that processes the request may specifically include: and determining a target business operation module of a second channel party for processing the request, providing the address of the target business operation module for the client of the first channel party, so that the client of the first channel party accesses the address, and processing the request through the target business operation module. Through the implementation manner, the business data related to the current transaction of the first channel party in the embodiment of the invention does not need to pass through the business processing system in the embodiment of the invention, but the business processing system only needs to provide the address of the target business operation module for the client of the first channel party, and the client performs business processing by accessing the address, so that the data security of the first channel party is ensured, and data leakage is prevented.

In one embodiment, the configuration information set may be provided to the client of the first channeling party for the client of the first channeling party to select the configuration information from the configuration information set, and the transaction identifier in the request sent by the client of the first channeling party is generated according to the configuration information selected by the client of the first channeling party. The configuration information can specifically correspond to the configured atomic transaction code, the atomic transaction code can be established according to business needs, and one transaction code, namely a transaction identifier, can be generated according to a plurality of atomic transaction codes. The transaction identifier is generated by using the configuration information, so that the problem that development efficiency is influenced because function updating needs to be recoded every time when the function updating is realized through hard coding can be solved, the configuration of transaction combination can be realized through a configuration file mode, and the aim of improving the development efficiency is fulfilled.

The channel party of one embodiment of the invention is a specific interface provider of the funder, scenic party or third party service. The scenario party refers to a collaboration scenario or company outside the financial institution that provides platform access for financial institution services. The funder refers to a financial institution that provides financing loan services. Third party services refer to providers that provide trusted services for the scenic and funding parties. For example, a third party service a is a channel side of the electronic signature service, a fund side b is a channel side of the loan service, and a scene side c is a scene channel side. The embodiment of the invention solves the problem of difficult butt joint of the fund party, the scene party and the third party service by adopting the schemes of standardization of scene access, standardization of fund party access and standardization of third party service access, and achieves the effect of finishing all butt joints by one-time standardization. The scene access standardization unifies the service interface and the data format of a scene party. The fund party access standardization unifies the business interface and data format of the fund party. The third-party service access standardization unifies the business interface and the data format of the third-party service. Therefore, the aim of completing access to all the fund party, the scene party and the third party service through one-time standardization is achieved by adapting and standardizing the API interfaces of the scene party, the third party service and the fund party.

Fig. 2 is a system architecture diagram of a business process according to one embodiment of the invention. As shown in fig. 2, taking the financial field as an example, the components in the architecture of the present embodiment are first described.

The funder API refers to an API definition for unifying funder backend systems, including, for example, loan services, credit card services, payment settlement services, account management services, lifestyle services, and the like. The fund side adapter is used for encapsulating different fund side background system interfaces into a uniform fund side API interface. For example, in fig. 2, funder 1, funder 2, funder 3, and funder 4 are each different funders, such as different banks. Each funding party background system (funding party 1 background, funding party 2 background, funding party 3 background, funding party 4 background) interfaces with funding party API interfaces through funding party adapters (funding party 1 adapter, funding party 2 adapter, funding party 3 adapter, funding party 4 adapter).

The scenario party API refers to an API definition for unifying the service background systems of the scenario party, including user information, loan data, scenario service data, and the like. The scene side adapter is used for encapsulating different scene background system interfaces into a uniform scene side API interface. For example, in fig. 2, the scenario party 1, the scenario party 2, the scenario party 3, and the scenario party 4 are different scenario parties, such as different businesses, respectively. Each scene side background system (scene side 1 background, scene side 2 background, scene side 3 background, scene side 4 background) is connected with the scene side API interface through the scene side adapter (scene side 1 adapter, scene side 2 adapter, scene side 3 adapter, scene side 4 adapter).

The third-party service API refers to a unified API definition for a background system of the third-party service, which includes services such as electronic signature, ORC (optical character recognition), real-name authentication, data and wind control, anti-fraud and collection, authority information verification, guarantee and insurance, and the like. The third-party service adapter is used for packaging background system interfaces of different third-party service providers into a uniform third-party service API interface. For example, in fig. 2, the third-party service 1, the third-party service 2, and the third-party service 3 are respectively different third-party services, for example, the third-party service 1 is an electronic signature service, the third-party service 2 is an ORC service, and the third-party service 3 is a data wind control service. Each third party service may have a specific service provider, for example, the third party services 1-1, 1-2 may be two different service providers that provide electronic signature services, the third party service 2-1, 2-2 can be two different service providers providing ORC services, the third party services 3-1, 3-2 can be two different service providers providing data-centric services, and each third party service backend (the backend of the third party services 1-1, 1-2, 2-1, 2-2, 3-1, 3-2) interfaces with the third party service API interface through a third party service adapter (the adapter of the third party services 1-1, 1-2, 2-1, 2-2, 3-1, 3-2).

The API, Application Programming Interface, refers to a predefined Interface, generally used as a convention for a connection specification between software systems, and has its own API standard in various industries.

The connector central control platform is responsible for providing functions of account registration, product shelving and shelving, permission application, connector management, access control and the like for various channel parties (such as scene parties, fund parties and third-party services) in the embodiment of the invention, wherein the functions comprise an operation background management system, a partner background management system, a financial institution background management system and the like.

The connector can be deployed in a distributed manner, and therefore can also be called a distributed connector, and the connector packages services standardized by an API (application programming interface) interface and an adapter into Web applications which can be deployed independently according to different channels, and deploys the Web applications to channel servers of different scene parties, fund parties and third-party services, and can also deploy the Web applications to container cloud services. That is, the embodiment of the present invention may deploy the connector on a private network, and access the connector through a private line by a channel party such as a fund party, or may deploy the connector on the internet, and ensure the confidentiality of the connector through interface access right control and asymmetric encryption technology.

The funding SDK is an SDK developed specifically for the funding that has access to other services for quick access into the central platform of the distributed connector.

The scenic side SDK is an SDK developed specifically for the scenic side that can access other services for quick access into the central platform of the distributed connector.

The client of the first channel party may be a funder SDK or a scenic party SDK.

In order to meet various interface functions, the embodiment of the invention needs to define a standard API interface to meet the requirements of different transaction types. The definition of the functional interface can also be realized by means of a configuration file.

The distributed connector defines 5 kinds of general interfaces (or called general API interfaces) for the API, which are as follows:

a universal data interface: the interface is used for receiving a Json object request and returning Json object content. Generally used as a service data interface, the transaction code of a connector is mainly defined by the type of the interface. The HTTP request design is specifically shown in table 1.

TABLE 1

A general file download interface: the interface is used for receiving a Json object request, putting a plurality of file contents into the Json object and returning the file contents to a calling party. Generally used as an interface for requesting the contents of a plurality of files at a time, and used for downloading a service scenario of a plurality of small files, such as downloading a plurality of contract files. The HTTP request design is specifically shown in table 2.

TABLE 2

The universal file uploading interface comprises: the interface is used for receiving single file uploads and returning Json object contents. Uploading is performed in a streaming mode, so that the occupation of a memory can be reduced. The method is generally used for a business scenario of document uploading, such as uploading a loan document. The HTTP request design is specifically shown in table 3.

TABLE 3

The general file flow agent download interface: the interface is used for receiving the Json object of the address downloaded by the target file and returning the target file to the caller in a streaming manner. And the downloading is carried out in a streaming mode, so that the occupation of a memory can be reduced. The method is generally used for agency downloading the service scene of the current oversized file, such as downloading a single loan application data file from a scene side. Since the interface is proxy downloaded, no transaction code is required. The HTTP request design is specifically shown in table 4.

TABLE 4

The universal file stream downloading interface comprises: the interface is used for receiving the Json object of the address downloaded by the target file and returning the file to the caller in a streaming manner. And the downloading is carried out in a streaming mode, so that the occupation of a memory can be reduced. The method is generally used for downloading a business scenario of a current oversized file, such as downloading an evidence report file from a third-party signature service. The HTTP request design is specifically shown in table 5.

TABLE 5

In the embodiment of the present invention, the transaction code is an example of a transaction identifier, the transaction code is used to define a transaction number of a single transaction, and the universal interface is used to forward a request sent by a client of a first channel party to a specific service adapter by identifying the transaction code, and return corresponding content. The specific method of the service adapter is that the target service operation module which needs to process the request returns the content which is the processing result of the request.

The transaction identifier, i.e., the transaction code (transCode), according to an embodiment of the present invention is composed of a 1-bit connector code (connectrorcode) + 4-bit channel code (channelCode) + 4-bit service code (serviceCode) + 4-bit operation code (actionCode), and each part is described in detail as follows.

Connector code (connectorCode), or connection code, i.e. connection id: is composed of a 1-bit letter. For example, T represents a third party service, S represents a scenic party, and B represents a funding party.

Channel code (channel code) or channel identification: the signature service is composed of 4 digits, is a manufacturer for providing service realization, corresponds to a provider name of the signature service, and is a concrete realization of a service code.

Service code (serviceCode) i.e. service identification: is composed of 4-digit numbers and is used for defining a specific service, such as a signature service.

Operation code (actionCode) is an operation identifier: the system is composed of 4-digit numbers and is used for defining a single specific transaction operation provided under a specific service, such as a signature verification operation under a signature service.

One specific example of a transaction code is: t100110010001 indicates that T indicates a third-party service (S indicates a scene party and B indicates a fund party), 1001 indicates a specific third-party service provider, 1001 indicates a signature service, and 0001 indicates a download credit report operation, corresponding to the provider name. The transaction code T100110010001 allows for routing to the third party service for downloading of the credentialing report under the signing service provided by a particular third party service provider of the third party service.

The distributed connector of the application is specially designed with special notes for each transaction code which is stored, and is used for loading and routing service when the application is started. Examples of annotations are specifically as follows:

ConnectorCode: for defining connector types (i.e., channel side categories).

ChannelCode: the user defines the channel type (i.e., the name of the channel party).

ServiceCode: for defining the type of service (indicating the service provided).

Actioncode: the user defines the type of operation (indicating the operation performed).

Taking the signature service as an example, the functions of traversing transaction code annotation and request routing can be realized by the connector through a transaction code management service transcodeservie (i.e. transaction identifier management service). And traversing each stored transaction code annotation, namely traversing ConnectorCode, ChannelCode, ServiceCode and ActionCode of each stored transaction code according to a connection code, a channel code, a service code and an operation code in the transaction code carried by the request so as to find out the connection code in the transaction code corresponding to the channel party type, the channel code in the transaction code corresponding to the channel party name, and the service provided corresponds to the service code in the transaction code and the executed operation corresponds to the service operation module of the operation code in the transaction code.

Through the routing function of the transaction code management service TransCodeService, a plurality of transaction codes can be combined into one transaction code to realize the function of combined transaction. Fig. 3 is a schematic flow diagram illustrating a process of implementing combined transaction in service processing according to an embodiment of the present invention, as shown in fig. 3, for example, a client of a first channel side issues a request to invoke a universal interface (S301), the request includes a transaction code a (i.e., a transaction identifier in the request), the universal interface invokes a transaction code management service (S302), the transaction code management service routes the request to a service operation module (S303, S304) corresponding to a transaction code B (an example of a first transaction identifier) and a service operation module (S304, S) corresponding to a transaction code C (an example of a second transaction identifier), the service operation modules corresponding to the transaction codes B and C are respectively used for processing, and steps S303 and S304 can be performed simultaneously. The transaction code management service respectively receives the processing result of the business operation module corresponding to the transaction code B and the processing result of the business operation module corresponding to the transaction code C (S305 and S306), and the execution sequence of the steps S305 and S306 is not limited by the sequence of the step numbers. And packaging the two processing results into a uniform processing result and returning the uniform processing result to the client of the first channel party, specifically, returning the uniform processing result to the universal interface by the transaction code management service (S307), and then returning the uniform processing result to the client of the first channel party through the universal interface (S308).

The server and the client in the embodiment of the present invention use HTTPs (secure hypertext transfer protocol) services, the server is the service processing system in the embodiment of the present invention, the client is the client of the first channel, for example, the fund party SDK or the scene party SDK, the server performs signature verification on all requests sent by the client, all requests are subjected to signature verification, the Request signature parameters are put into an HTTP Request Header, and the specific parameters are as in table 6 below. The signature algorithm is SHA256 algorithm (an algorithm subdivided under SHA-2 (a cryptographic hash function algorithm standard)).

TABLE 6

An example of the text to be signed is shown in table 7.

TABLE 7

The distributed connector of the embodiment of the invention adopts the standard of OAuth2.0 (the extended version of OAuth (open authorization)) protocol) and uses JWT (JSON Web token) to realize identity verification and access right control. The channel side SDK (client) and the distributed connector store own public key, and the central control platform stores private key. Fig. 4 is a schematic flowchart of verifying access rights of an interface in a business process according to an embodiment of the present invention, as shown in fig. 4,

step S401: a client of the first channel party (e.g., a channel party SDK) logs on to the connector and requests to obtain a JSON Web token.

Wherein the JSON Web token is abbreviated as JWT, for which an expiration time, e.g., 2 hours, can be set.

Step S402: the connector verifies the login information of the client of the first channel side, and if the login information is not verified, the step S407 is skipped to. If the login information is verified, step S403 is executed.

The login information comprises information such as a user name and a password of the client of the first channel party.

Step S403: and verifying whether the client of the first channel side has the access authority for accessing the application of the second channel side, if so, executing the step S404, otherwise, jumping to the step S407.

The correspondence between the client and the accessible applications may be pre-saved to verify whether the client of the first channel side has access rights to access the applications of the second channel side.

Step S404: and returning the JSON Web token to the client of the first channel party so that the JSON Web token is carried in the request sent by the client of the first channel party.

The JSON Web token is carried in a request from a client on the first channel side, such as a request to a connector via a URL (Uniform resource locator) to bring up the JWT.

Step S405: and verifying the JSON Web token through a target general interface to be called by the client side of the first channel side, if the JSON Web token is verified to be passed, continuing to the step S406, and if not, jumping to the step S407.

Step S406: and determining that the client of the first channel side has an interface access right for calling the target universal interface.

And if the JSON Web token passes the verification, the client of the first channel side indicates that the interface access authority of the target universal interface passes the verification. The JSON Web token can be verified using a private key maintained by the central control platform.

Step S407: and determining that the client of the first channel side does not have the interface access authority for calling the target universal interface.

The embodiment of the invention realizes the control of the identity and the interface authority through the connector central control platform (central control platform for short) by appointing the API interfaces of the services of the fund party, the scene party and the third party and adapting to different channels, and provides the fund party SDK and the scene party SDK to realize the calling of the standard API, thereby shielding different implementation modes of each channel bottom layer. The problem of difficult butt joint of fund side, scene side and third party service in the financial field is solved, and the butt joint among different systems is accomplished in a standardized way. The specific service data of the first channel party and the second channel party in the embodiment of the invention does not need to be submitted to a central control platform or a connector, thereby ensuring the data security.

FIG. 5 is a schematic diagram of the main modules of a business processing system in accordance with one embodiment of the present invention; as shown in fig. 5, a service 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.

A request receiving module 501, configured to receive a request sent by a client of a first channel party by invoking a target generic interface, where the request includes a transaction identifier. The request routing module 502 is configured to identify the transaction identifier in the request through the target generic interface, so as to route the request to a target service operation module of a second channel party processing the request for processing.

And a result returning module 503, configured to return the processing result of the target service operation module to the client of the first channel side through the target general interface.

The request routing module 502 is specifically configured to: identifying a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier through the target universal interface; searching the channel party category corresponding to the connection identifier, the channel party name corresponding to the channel identifier, the service operation module of which the provided service corresponds to the service identifier and the executed operation corresponds to the operation identifier, serving as a target service operation module, and routing the request sent by the client of the first channel party to the target service operation module for processing.

The business operation module can traverse the stored transaction identifier notes according to the connection identifier, the channel identifier, the service identifier and the operation identifier in the transaction identifier contained in the request so as to find out the business operation module of which the channel party type corresponds to the connection identifier, the channel party name corresponds to the channel identifier, and the provided service corresponds to the service identifier and the executed operation corresponds to the operation identifier.

The business processing system 500 can also include a generic interface creation module to: one or more universal interfaces are predefined according to functions aiming at operations executed under various channel party categories, channel party names and provided services, wherein one universal interface is a target universal interface, and each universal interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one executed operation.

In one embodiment, the predefined one or more generic interfaces may include one or more of a generic data interface, a generic file download interface, a generic file upload interface, a generic file stream proxy download interface, a generic file stream download interface.

In one embodiment, the request routing module 502 is specifically configured to: and calling a transaction identifier management service through the target universal interface so that the transaction identifier management service identifies a first transaction identifier and at least one second transaction identifier from the transaction identifiers in the request, routes the request to a first target service operation module corresponding to the first transaction identifier and a second target service operation module corresponding to the second transaction identifier respectively, and processes the requests by the first target service operation module and the second target service operation module respectively.

The number of the second channel parties can be 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.

The result returning module 503 may be specifically configured to: and receiving a first processing result of the first target business operation module and a second processing result of the second target business operation module through the transaction identifier management service, packaging the first processing result and the second processing result into a uniform processing result, and returning the uniform processing result to the client of the first channel party.

The business processing system 500 may further include an access right verification module for: and confirming that the client of the first channel side has an interface access right for calling the target universal interface.

The target generic interface may be provided through a connector deployed on the container cloud service to receive a request issued by a client of the first channel party by invoking the target generic interface.

The business processing system 500 can also include a token provisioning module to: and verifying the login information of the client of the first channel party to the connector, verifying whether the client of the first channel party has the access authority for accessing the application of the second channel party after the login information is verified, and returning a JSON Web token to the client of the first channel party if the client of the first channel party has the access authority so as to enable the request to carry the JSON Web token.

The access permission validation module is specifically operable to: and verifying the JSON Web token through the target general interface, wherein if the token is verified to be passed, the client of the first channel party has an interface access right for calling the target general interface.

The request issued by the client of the first channel party by invoking the target generic interface may comprise a request signature value. The business processing system 500 can further include a signature verification module for: after the request receiving module 501 receives a request sent by a client of a first channel party by calling a target universal interface, signature verification is performed on the request, and it is determined that the signature verification is passed.

The request routing module 502 is further specifically configured to: and determining a target business operation module of a second channel party for processing the request, providing the address of the target business operation module for the client of the first channel party, accessing the address by the client of the first channel party, and processing the request through the target business operation module.

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

Based on the service processing system 500 of the embodiment of the present invention, referring to the architecture shown in fig. 2 of the above embodiment, the request receiving module 501, the request routing module 502, the result returning module 503, and the access right verifying module may be disposed in a connector, and the token providing module may be disposed in a central control platform of the connector. The general interface creating module and the configuration module can be arranged in another server, and the business operation module can be logic codes of a scene party, a fund party and a third-party service background.

In addition, the specific implementation content of the service processing system in the embodiment of the present invention has been described in detail in the above service processing method, so that repeated content herein is not described again.

Fig. 6 shows an exemplary system architecture 600 of a business processing method or business processing system to which embodiments of the invention may be applied.

As shown in fig. 6, the system architecture 600 may include

terminal devices

601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the

terminal devices

601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The

terminal devices

601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the

terminal devices

601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.

It should be noted that the service processing method provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the service processing system is generally disposed in the server 605.

It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use in implementing a server according to embodiments of the present application. The server shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. 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 magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program executes the above-described functions defined in the system of the present application when executed by the Central Processing Unit (CPU) 701.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a request receiving module, a request routing module and a result returning module. The names of these modules do not constitute a limitation to the module itself in some cases, for example, the request receiving module may also be described as "a module for receiving a request issued by a client of the first channel party by calling the target common interface".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier; identifying the transaction identification through the target universal interface so as to route the request to a target business operation module of a second channel party processing the request 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.

As a further aspect, the present invention also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the service processing method of the embodiment of the present invention.

According to the technical scheme of the embodiment of the invention, a request sent by a client of a first channel party by calling a target universal interface is received, the request comprises a transaction identifier, the transaction identifier is identified through the target universal interface so as to route the request to a target business operation module of a second channel party for processing the request, and a processing result of the target business operation module is returned to the client of the first channel party through the target universal interface. The access standardization can be realized, so that interfaces of other channel parties do not need to be adapted when different channel parties are in butt joint, the problem of difficult butt joint is solved, and the safety risk of the system is reduced.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for processing a service, comprising:

receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier;

identifying the transaction identification through the target universal interface so as to route the request to a target business operation module of a second channel party processing the request 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.

2. The method of claim 1, wherein said identifying the transaction identifier through the target generic interface for routing the request to a target business operations module of a second channel party processing the request comprises:

identifying a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier through the target universal interface;

and searching the channel party category corresponding to the connection identifier, the channel party name corresponding to the channel identifier, and the provided service corresponding to the service identifier and the executed operation corresponding to the service operation module of the operation identifier, serving as the target service operation module, and routing the request to the target service operation module for processing.

3. The method according to claim 2, wherein the stored transaction identifier annotations are traversed according to a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier to find out that a channel party category corresponds to the connection identifier, a channel party name corresponds to the channel identifier, a provided service corresponds to the service identifier and an executed operation corresponds to the business operation module of the operation identifier.

4. The method of claim 2, wherein before receiving the request from the client of the first channel party by calling the target generic interface, the method comprises:

one or more universal interfaces are predefined according to functions aiming at operations executed under various channel party categories, channel party names and provided services, wherein one universal interface is the target universal interface, and each universal interface corresponds to at least one channel party category, at least one channel party name, at least one provided service and at least one executed operation.

5. The method of claim 4, wherein the one or more predefined generic interfaces comprise one or more of a generic data interface, a generic file download interface, a generic file upload interface, a generic file stream proxy download interface, and a generic file stream download interface.

6. The method of claim 1, wherein identifying the transaction identifier through the target generic interface for routing the request to a target business operations module of a second channel party processing the request comprises:

and calling a transaction identifier management service through the target universal 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 respectively routes the request to a first target service operation module corresponding to the first transaction identifier and a second target service operation module corresponding to the second transaction identifier, and the first target service operation module and the second target service operation module respectively process the requests.

7. The method of claim 6, wherein the number of the 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 of claim 6, wherein the step of returning the processing result of the target business operation module to the client of the first channel side through the target generic interface comprises:

and receiving a first processing result of the first target business operation module and a second processing result of the second target business operation module through the transaction identifier management service, packaging the first processing result and the second processing result into a uniform processing result, and returning the uniform processing result to the client of the first channel party.

9. The method of claim 1, wherein before receiving the request from the client of the first channel party by calling the target generic interface, the method comprises:

and confirming that the client of the first channel side has an interface access right for calling the target universal interface.

10. The method of claim 9, wherein the target generic interface is provided through a connector deployed on a container cloud service to receive a request from a client of the first channel party by invoking the target generic interface.

11. The method of claim 10, wherein before receiving the request from the client of the first channel party by calling the target generic interface, the method further comprises:

verifying login information of the client of the first channel party to the connector, verifying whether the client of the first channel party has an access right for accessing the application of the second channel party after the login information is verified, and returning a JSON Web token to the client of the first channel party if the client of the first channel party has the access right so that the JSON Web token is carried in the request;

the confirming that the client of the first channel side has the interface access authority for calling the target universal interface comprises the following steps:

and verifying the JSON Web token through the target general interface, wherein if the token is verified to be passed, the client of the first channel party has an interface access right for calling the target general interface.

12. The method of claim 1, wherein the request issued by the client of the first channelizer by invoking the target generic interface comprises a request signature value;

the method further comprises the following steps: after receiving a request sent by a client of a first channel party by calling a target universal interface, firstly carrying out signature verification on the request and determining that the signature verification is passed.

13. The method of claim 1, wherein said routing said request to a target business operations module of a second conduit party processing said request comprises:

and determining a target business operation module of a second channel party for processing the request, providing the address of the target business operation module for the client of the first channel party so that the client of the first channel party accesses the address, and processing the request through the target business operation module.

14. The method of claim 1 further comprising providing a set of configuration information to the client of the first channeling party for the client of the first channeling party to select configuration information from the set of configuration information, the transaction identification in the request being generated based on the configuration information selected by the client of the first channeling party.

15. A transaction system, comprising:

the request receiving module is used for receiving a request sent by a client of a first channel party by calling a target universal interface, wherein the request comprises a transaction identifier;

the request routing module is used for identifying the transaction identifier through the target general interface so as to route the request to a target business operation module of a second channel party processing the request for processing;

and the result returning module is used for returning the processing result of the target business operation module to the client of the first channel party through the target general interface.

16. The system of claim 15, wherein the request routing module is further configured to:

17. The system of claim 16, wherein the transaction identifier notes are traversed according to a connection identifier, a channel identifier, a service identifier and an operation identifier in the transaction identifier to find out that a channel party category corresponds to the connection identifier, a channel party name corresponds to the channel identifier, a provided service corresponds to the service identifier and an executed operation corresponds to the business operation module of the operation identifier.

18. The system of claim 16, further comprising a generic interface creation module to:

19. The system of claim 18, wherein the one or more predefined generic interfaces comprise one or more of a generic data interface, a generic file download interface, a generic file upload interface, a generic file stream proxy download interface, and a generic file stream download interface.

20. The system of claim 15, wherein the request routing module is further configured to:

21. The system of claim 20 wherein the number of said second channel parties is two or more, and said first target business operations module and said second target business operations module are the same or different business operations modules of said second channel parties.

22. The system of claim 20, wherein the result return module is further configured to:

23. The system of claim 15, further comprising an access rights verification module to:

24. The system of claim 23, wherein the target generic interface is provided via a connector deployed on a container cloud service to receive a request from a client of the first channel party by invoking the target generic interface.

25. The system of claim 24, further comprising a token provisioning module configured to:

the access right verification module is further configured to:

26. The system of claim 15, wherein the request issued by the client of the first channelizer by invoking the target generic interface includes a request signature value;

the system further includes a signature verification module to: after the request receiving module receives a request sent by a client of the first channel party by calling a target universal interface, signature verification is firstly carried out on the request, and the signature verification is confirmed to be passed.

27. The system of claim 15, wherein the request routing module is further configured to:

28. The system of claim 15, further comprising a configuration module to: and 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, wherein the transaction identifier in the request is generated according to the configuration information selected by the client of the first channel party.

29. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-14.

30. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-14.

31. A computer program product comprising a computer program, characterized in that the computer program realizes the method according to any of claims 1-14 when executed by a processor.