CN112102063B

CN112102063B - Data request method, device, equipment, platform and computer storage medium

Info

Publication number: CN112102063B
Application number: CN202010900541.5A
Authority: CN
Inventors: 符修亮; 万磊; 李毅; 钱进
Original assignee: WeBank Co Ltd
Current assignee: WeBank Co Ltd
Priority date: 2020-08-31
Filing date: 2020-08-31
Publication date: 2024-05-14
Anticipated expiration: 2040-08-31
Also published as: CN112102063A

Abstract

The embodiment of the application provides a data request method, a data request device, electronic equipment, a loan platform and a computer readable storage medium; the method comprises the following steps: receiving a loan request message from an interface of a property party, and caching the loan request message into a queue; acquiring first data and second data, wherein the first data represents the success times of historical loan requests of the self-property side interface to a plurality of candidate fund side interfaces, and the second data represents the failure times of the historical loan requests of the self-property side interface to the plurality of candidate fund side interfaces; determining a target fund party interface for receiving the loan request message in a plurality of candidate fund party interfaces according to the first data and the second data; and reading loan request messages from the queue through preset threads in turn, and after any one of the threads reads the loan request messages from the queue, routing the loan request messages to the target fund party interface and receiving a loan request result returned by the target fund party interface.

Description

Data request method, device, equipment, platform and computer storage medium

Technical Field

The present application relates to the field of loan transactions in financial technology (Fintech), and relates to, but is not limited to, a data requesting method, apparatus, electronic device, loan platform, and computer readable storage medium.

Background

With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changed into financial technology, but due to the requirements of safety and instantaneity of the financial industry, higher requirements are also put on the technologies.

Currently, in the field of financial science and technology, a loan platform can realize the butt joint of a self-property side interface and a candidate fund side interface, however, the self-property side interface can only be in butt joint with the agreed candidate fund side interface, and the self-property side interface can not necessarily acquire a successful result of a loan request from the agreed candidate fund side interface, so that the possibility of successfully acquiring the loan is reduced to a certain extent; also, if the loan platform receives a large number of loan requests from candidate fund party interfaces at the same time, the computing resource consumption may be exacerbated due to the high concurrency of the loan requests.

Disclosure of Invention

The embodiment of the application provides a data request method, a data request device, electronic equipment, a loan platform and a computer readable storage medium, which are used for solving the problem that the consumption of computing resources is aggravated due to high concurrency of loan requests.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a data request method, which comprises the following steps:

Receiving a loan request message sent by an asset side interface, and caching the loan request message into a queue;

Obtaining first data and second data, wherein the first data represents the success times of historical loan requests of the self-property side interface to a plurality of candidate fund side interfaces, and the second data represents the failure times of historical loan requests of the self-property side interface to the plurality of candidate fund side interfaces;

determining a target fund party interface for receiving the loan request message in the candidate fund party interfaces according to the first data and the second data;

and reading the loan request message from the queue through each preset thread in turn, and after any one of the threads reads the loan request message from the queue, routing the loan request message to the target fund party interface and receiving a loan request result returned by the target fund party interface.

In some embodiments of the application, the determining a target fund party interface of the plurality of candidate fund party interfaces for receiving the loan request message according to the first data and the second data includes:

determining a routing weight coefficient between the self-asset side interface and each candidate fund side interface according to the first data and the second data;

Determining a first set according to the first data, the second data and the routing weight coefficient, wherein the first set comprises at least one candidate fund party interface;

and selecting any one candidate fund party interface from the first set as the target fund party interface.

In some embodiments of the application, said determining routing weight coefficients between said self-asset side interface and said each candidate funding side interface based on said first data and said second data comprises:

Deriving a routing weight coefficient between the self-asset side interface and each candidate fund side interface from the first data and the second data using the following formula:

Wherein w _i represents a routing weight coefficient between the self-asset side interface and the i-th candidate fund side interface, A_F _i _S represents the number of times the self-asset side interface obtains a successful result of a loan request from the i-th candidate fund side interface, and ALL_S represents the total number of times the self-asset side interface obtains a successful result of the loan request from each candidate fund side interface; a_f _i _f represents the number of times the self-side interface acquires a loan request failure result from the i-th candidate fund side interface, all_f represents the total number of times the self-side interface acquires a loan request failure result from each candidate fund side interface; i is 1 to n, n represents the number of candidate fund side interfaces of the plurality of candidate fund side interfaces.

In some embodiments of the application, the first set represents a set of candidate funding party interfaces that meet a first preset condition;

The method further comprises the steps of: determining a first difference value A_F _i corresponding to an i candidate fund party interface obtained by subtracting A_F _i _F from A_F _i _S; and under the condition that A_F _i is greater than 0 and A_F _i*w_i is greater than or equal to D, determining that the ith candidate fund party interface meets a first preset condition, wherein D represents a first preset value.

In some embodiments of the application, the method further comprises: and under the condition that the loan request result is a loan request failure result, re-selecting one candidate fund party interface from the unselected candidate fund party interfaces of the first set as the target fund party interface.

In some embodiments of the present application, the determining a target fund party interface of the plurality of candidate fund party interfaces for receiving the loan request message according to the first data and the second data further includes:

Responding to the condition that the loan request result corresponding to each candidate fund party interface of the first set is a loan request failure result, and obtaining a second set, wherein the second set represents a set of candidate fund party interfaces which do not meet the first preset condition in the plurality of candidate fund party interfaces;

the target funding party interface is determined in the second set.

In some embodiments of the application, the determining the target funding party interface in the second set comprises:

deleting candidate fund party interfaces meeting a second preset condition in the second set to obtain a third set; determining the target funding party interface in the third set;

The method further comprises the steps of:

And determining that the i candidate fund side interface meets a second preset condition under the condition that the first difference value corresponding to the i candidate fund side interface is smaller than or equal to 0 and the product of the first difference value corresponding to the i candidate fund side interface and the weight coefficient of the i candidate fund side interface is smaller than or equal to a second preset value, wherein the second preset value is smaller than the first preset value.

In some embodiments of the application, the determining the target funding party interface in the third set comprises:

In the third set, taking a set of candidate fund party interfaces meeting a third preset condition as a fourth set; determining the target funding party interface in the fourth set;

The method further comprises the steps of:

Determining a second difference value obtained by subtracting the second times from the first times; the first number of times represents a successful number of historical loan requests by the self-equity interface to a j-th candidate fund party interface of the third set, and the second number of times represents a failed number of historical loan requests by the self-equity interface to the j-th candidate fund party interface; j is 1 to Q, Q represents the number of candidate fund party interfaces in the third set;

and under the condition that the second difference value is larger than or equal to a third preset value, determining that the j candidate fund party interface meets a third preset condition.

In some embodiments of the application, the determining the target funding party interface in the fourth set comprises:

obtaining probability parameters, wherein the probability parameters represent the probability that the self-property side interface obtains a successful result of a loan request from each candidate fund side interface of the fourth set;

sequencing candidate fund party interfaces of the fourth set according to the probability parameters to obtain a sequencing result; and selecting a candidate fund party interface as the target fund party interface according to the sorting result.

In some embodiments of the present application, the selecting a candidate fund side interface as the target fund side interface according to the sorting result includes:

And under the condition that the loan request result is a loan request failure result, re-selecting one candidate fund party interface from the unselected candidate fund party interfaces of the fourth set as the target fund party interface according to the sorting result.

In some embodiments of the application, the determining the target funding party interface in the third set further comprises:

Responding to the condition that the loan request result corresponding to each candidate fund party interface of the fourth set is a loan request failure result, and obtaining a fifth set, wherein the fifth set represents a set of candidate fund party interfaces which do not meet the third preset condition in the third set;

the target funding party interface is randomly selected from the fifth set.

In some embodiments of the application, the method further comprises:

updating the number of successful loan requests from the property side interface to the target fund side interface under the condition that the loan request result is a loan request success result;

and updating the historical loan request failure times of the self-property side interface to the target fund side interface under the condition that the loan request result is a loan request failure result.

In some embodiments of the application, the method further comprises: after any one of the threads reads data from the queue, deleting the read data from the queue; and closing the corresponding thread under the condition that any thread fails to read data from the queue.

In some embodiments of the application, the method further comprises:

After receiving the loan request message from the self-property side interface, mapping the loan request message into a core routing table according to a predetermined field mapping table;

The routing the loan request message to the target fund party interface includes:

And routing the loan request message to the target fund party interface according to the content in the core routing table.

The embodiment of the application provides a data request device, which comprises:

The receiving and transmitting module is used for receiving a loan request message sent by the asset side interface and caching the loan request message into a queue;

An acquisition module configured to acquire first data and second data, where the first data represents a number of successful requests of historical loans from the property side interface to a plurality of candidate property side interfaces, and the second data represents a number of failed requests of historical loans from the property side interface to the plurality of candidate property side interfaces;

The processing module is used for determining a target fund party interface for receiving the loan request message in the plurality of candidate fund party interfaces according to the first data and the second data;

and the receiving and transmitting module is also used for reading the loan request message from the queue through each preset thread in turn, and after any one of the threads reads the loan request message from the queue, the loan request message is routed to the target fund party interface, and a loan request result returned by the target fund party interface is received.

In some embodiments of the present application, the processing module, configured to determine, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces, includes:

In some embodiments of the application, the processing module, configured to determine routing weight coefficients between the self-asset side interface and each candidate fund side interface based on the first data and the second data, includes:

The processing module is further configured to determine a first difference value a_f _i corresponding to an i candidate fund party interface obtained by subtracting a_f _i _f from a_f _i _s; and under the condition that A_F _i is greater than 0 and A_F _i*w_i is greater than or equal to D, determining that the ith candidate fund party interface meets a first preset condition, wherein D represents a first preset value.

In some embodiments of the present application, the processing module is further configured to, in a case where the loan request result is a loan request failure result, reselect one candidate fund side interface among the unselected candidate fund side interfaces of the first set as the target fund side interface.

In some embodiments of the present application, the processing module is configured to determine, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces, and further includes:

the target funding party interface is determined in the second set.

In some embodiments of the application, the processing module, configured to determine the target funding party interface in the second set, includes:

The processing module is further configured to determine that the i candidate fund side interface meets a second preset condition when a first difference value corresponding to the i candidate fund side interface is less than or equal to 0, and a product of the first difference value corresponding to the i candidate fund side interface and a weight coefficient of the i candidate fund side interface is less than or equal to a second preset value, where the second preset value is less than the first preset value.

In some embodiments of the application, the processing module, configured to determine the target funding party interface in the third set, includes:

the processing module is further configured to:

In some embodiments of the application, the processing module, configured to determine the target funding party interface in the fourth set, includes:

In some embodiments of the present application, the processing module, configured to select, according to the sorting result, a candidate fund party interface as the target fund party interface, includes:

In some embodiments of the application, the processing module, configured to determine the target fund party interface in the third set, further includes:

the target funding party interface is randomly selected from the fifth set.

In some embodiments of the application, the processing module is further configured to:

In some embodiments of the present application, after any one of the threads reads data from the queue, the read data is deleted from the queue; and closing the corresponding thread under the condition that any thread fails to read data from the queue.

In some embodiments of the present application, the transceiver module is further configured to map the loan request packet to a core routing table according to a predetermined field mapping table after receiving the loan request packet from the self-property side interface;

the transceiver module, configured to route the loan request message to the target fund party interface, includes: and routing the loan request message to the target fund party interface according to the content in the core routing table.

An embodiment of the present application provides an electronic device, including:

a memory for storing executable instructions;

And the processor is used for realizing any one of the data request methods when executing the executable instructions stored in the memory.

The embodiment of the application provides a loan platform, which comprises any one of the data request devices or any one of the electronic devices.

The embodiment of the application provides a computer readable storage medium which stores executable instructions for implementing any one of the data request methods when being executed by a processor.

In the embodiment of the application, a loan request message sent by an asset side interface is received, and the loan request message is cached in a queue; obtaining first data and second data, wherein the first data represents the success times of historical loan requests of the self-property side interface to a plurality of candidate fund side interfaces, and the second data represents the failure times of historical loan requests of the self-property side interface to the plurality of candidate fund side interfaces; determining a target fund party interface for receiving the loan request message in the candidate fund party interfaces according to the first data and the second data; and reading the loan request message from the queue through each preset thread in turn, and after any one of the threads reads the loan request message from the queue, routing the loan request message to the target fund party interface and receiving a loan request result returned by the target fund party interface. It can be seen that, for any self-property side interface, the target property side interface can be determined according to the historical loan requests of the self-property side interface to a plurality of candidate property side interfaces, and the loan platform is not required to configure corresponding candidate property side interfaces for the self-property side interfaces in advance; according to the successful times and the failed times of the historical loan request of the candidate fund party interface from the asset party interface, the probability of obtaining the successful result of the loan request from the candidate fund party interface is determined, and further after the target fund party interface is determined, the successful result of the loan request is obtained from the target fund party interface with high probability, so that the possibility of successfully obtaining the loan is improved to a certain extent; further, compared with a mechanism of directly reading the loan request message from the property side interface, the mechanism of obtaining the loan request message from the queue can alleviate the problem of excessive resource consumption caused by excessive loan request message to a certain extent.

Drawings

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

FIG. 2 is an alternative flow chart of a data request method provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of another application scenario of an embodiment of the present application;

FIG. 4 is a schematic diagram of an alternative composition of a data request device according to an embodiment of the present application;

Fig. 5 is a schematic diagram of an alternative composition structure of an electronic device according to an embodiment of the present application.

Detailed Description

In the related art, a loan platform may integrate a property party and a fund party, the property party representing a party who provides a source of a needed loan in a loan business, the fund party representing a party who provides a needed loan in the loan business; one or more self-asset party interfaces may be provided for each asset party, and one or more candidate fund party interfaces may be provided for each fund party; in practical implementation, the loan platform can uniformly formulate a docking mode of the self-property side interfaces and the candidate fund side interfaces, can provision a corresponding candidate fund side interface for each self-property side interface, can provision a corresponding self-property side interface for each candidate fund side interface, can only dock with the provision candidate fund side interface, and can only dock with the provision self-property side interface.

With the development of loan business, the loan platform makes a joint mode of the self-property party interface and the candidate fund party interface in a unified manner, so that the subsequent loan business requirement is difficult to meet; when new loan business requirements appear, candidate fund party interfaces may need to be changed for the self-property party interfaces, which is easy to influence the loan business; further, to meet new loan business requirements, it may be desirable to configure a new self-party interface for the party or to configure a new candidate party interface for the candidate party interface, while parties with a self-party interface or parties with an existing candidate party interface are typically reluctant to invest additional costs to develop additional interfaces, possibly resulting in loss of the party or party.

Further, when a new self-property party interface or a new candidate fund party interface appears, the loan platform needs to reformulate the docking mode of the self-property party interface and the candidate fund party interface for the new self-property party interface or the new candidate fund party interface, thereby increasing labor cost and time cost.

Aiming at the technical problems, the technical scheme of the embodiment of the application is provided.

The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

The embodiment of the application provides a data request method, a device, an electronic device, a loan platform and a computer readable storage medium, wherein the data request method of the embodiment of the application can be applied to the loan platform, and an exemplary application of the loan platform provided by the embodiment of the application is described below, the loan platform provided by the embodiment of the application can be implemented as a terminal and/or a server, and the terminal can be a tablet computer, a notebook computer, a desktop computer and the like, but is not limited to the terminal and the server; the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content distribution network (Content Delivery Network, CDN), basic cloud computing services such as big data and an artificial intelligent platform.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application, as shown in FIG. 1, a property party system 100 may be connected to a fund party system 102 through a loan platform 101; the asset party system 100 may include at least one self asset party interface, each belonging to an asset party; the funding party system may include at least one candidate funding party interface, each candidate funding party interface belonging to one funding party; each of the self-equity interfaces or each of the candidate equity interfaces may be connected to the loan platform 101 via a network, or may be connected to the loan platform 101 in other ways; the network may be a wide area network or a local area network, or a combination of both.

In some embodiments of the application, the loan platform 101 may receive a loan request message from a candidate funding party interface of the property party system 100, the loan request message representing a message requesting to obtain a funding party loan. After receiving the loan request message, the loan platform 101 may send the loan request message to any one of the candidate fund party interfaces of the fund party system 102.

After receiving the loan request message, the candidate fund party interface may return a loan request result to the loan platform 101, where the loan request result may be a loan request success result indicating that the obtaining of the loan is successful, or may be a loan request failure result indicating that the obtaining of the loan is failed.

The loan platform 101, upon receiving the loan request result, may send the loan request result to the self-equity interface to make the equity aware of the loan request result.

The loan request method according to the embodiment of the present application is described below in an exemplary manner with reference to the application scenario shown in fig. 1.

Fig. 2 is an optional flowchart of a data request method according to an embodiment of the present application, where, as shown in fig. 2, the flowchart may include:

Step 201: and receiving a loan request message sent from the property side interface, and caching the loan request message into a queue.

In the embodiment of the application, the loan request message can comprise an identity number (Ident ity Document, ID) of the self-owned party interface, an ID of the self-owned party interface and loan business content, wherein the loan business content comprises but is not limited to loan amount, loan time limit, loan interest rate and the like; in some embodiments, the loan request message further includes a candidate fund party interface ID, and in the case where the loan request message includes the candidate fund party interface ID, the loan platform may route the loan request message to the corresponding candidate fund party interface directly according to the candidate fund party interface ID; in the case where the loan request message does not include the candidate fund party interface ID, the loan platform may process according to the loan request method of an embodiment of the application.

In some embodiments of the application, the loan platform may include a message persistence module (persistor) for receiving the loan request message sent from the property side interface and storing the loan request message in a persistence table (T_ PERSIST _ASSET); here, for each self-property side interface, a corresponding message persistence module may be set, that is, the self-property side interface in the property side system and the persistence module in the loan platform form a one-to-one correspondence.

FIG. 3 is a schematic diagram of another application scenario of the embodiment of the present application, as shown in FIG. 3, the asset side system 100 has p own asset side interfaces, from the 1 st own asset side interface to the p own asset side interface, where p is an integer greater than 1; persistor-1 to persistor-p in the loan platform 101 represent p message persistence modules, respectively, and p self-property interfaces of the property side system 100 and p message persistence modules in the loan platform 101 form a one-to-one correspondence.

In connection with fig. 3, each message persistence module, upon receiving a loan request message, may store the loan request message in a persistence table, where table fields of the persistence table may include an asset_id field for populating the self-party INTERFACE ID, an interface_id field for populating the self-party ID to which the self-party INTERFACE belongs, and a BIZ_CONTENT field for populating the loan traffic CONTENT described above, and in some embodiments, a BIZ_CONTENT field for populating the self-party INTERFACE ID and the self-party INTERFACE ID to which the self-party INTERFACE belongs.

In some embodiments of the application, the table field of the persistence table may also include a FUND _id field, FUND _id field for populating the candidate funding party interface ID.

It can be understood that the buffering of the loan request message into the queue is beneficial to a plurality of threads to obtain the loan request message from the queue at the same time, so that on one hand, the processing speed of the loan request message is increased, and on the other hand, compared with a mechanism for directly reading the loan request message from the property side interface, the mechanism for obtaining the loan request message from the queue can alleviate the problem of excessive resource consumption caused by excessive loan request message to a certain extent.

In some embodiments of the application, the loan request message may be cached through a remote dictionary service (Remote Dictionary S erver, redis) queue; in one implementation, the persistence table may be cached via a Redis queue while the loan request message is stored in the persistence table; the processing mechanism of the loan request message based on the Re dis queue can fully utilize the processing capacity of the loan platform and can support a plurality of servers in the loan platform to read the message from the Redis queue at the same time; in addition, the processing mechanism of the loan request message based on the Redis queue can support the addition of computing devices such as a server and the like to the loan platform so as to realize the expansion of the computing devices of the loan platform.

In some embodiments of the present application, after the loan request message is cached via the Redis queue, response information may be returned to the corresponding self-property interface, the response information indicating that the loan platform successfully received the loan request message.

In some embodiments of the present application, after caching the persistent table through the Redis queue, the message persistence module may send a Redis broadcast message to inform all computing devices in the loan platform to read the data of the Redis queue.

Step 202: first data and second data are acquired.

Here, the first data represents a number of successful requests for historical loans from the property side interface to the plurality of candidate property side interfaces, and the second data represents a number of failed requests for historical loans from the property side interface to the plurality of candidate property side interfaces.

In the embodiment of the application, after a loan request is sent from a property party interface to a candidate fund party interface, if the loan request result is a successful loan request result after receiving the loan request result, the success number of historical loan requests can be increased by 1; if the loan request result is a loan request failure result, the number of times of failure of the historical loan request can be increased by 1; in this manner, the number of successful requests for historical loans from the equity interface to the plurality of candidate equity interfaces, and the number of failed requests for historical loans from the equity interface to the plurality of candidate equity interfaces may be determined.

Step 203: and determining a target fund party interface for receiving the loan request message from the plurality of candidate fund party interfaces according to the first data and the second data.

In the embodiment of the application, one candidate fund party interface can be selected from a plurality of candidate fund party interfaces as a target fund party interface according to the first data and the second data.

Step 204: and reading the loan request message from the queue through each preset thread in turn, and after any one of the threads reads the loan request message from the queue, routing the loan request message to a target fund party interface and receiving a loan request result returned by the target fund party interface.

In some embodiments of the application, data may be read from the queue by each thread in turn, as preset, before routing the loan request message to the target fund party interface; after any one thread in each thread reads data from the queue, deleting the read data from the queue; and closing the corresponding thread under the condition that any thread fails to read data from the queue.

Here, the number of the preset threads may be determined according to the computing resources of the loan platform; in some embodiments, the preset maximum number of threads may be determined according to the number of cores of the processor in the loan platform, for example, when the number of cores of the processor in the loan platform is a, the maximum number of threads may be t=2a.

It can be seen that, in the embodiment of the application, the data in the queue is obtained by each thread in turn, which is beneficial to improving the processing efficiency of the loan request message in the queue; and under the condition that any thread can not read data from the queue, closing the corresponding thread, so that the computing resource of a loan platform can be saved.

In some embodiments of the present application, the loan platform may further include a service logic processing module (dispo ser) configured to monitor the broadcast message sent by the message persistence module, and after monitoring the broadcast message, start a plurality of threads to read the data in the queue; here, for each self-property side interface, a corresponding message persistence module may be set, that is, the self-property side interface in the property side system and the business logic processing module in the loan platform form a one-to-one correspondence; and the message persistence module in the loan platform and the business logic processing module form a one-to-one correspondence.

Referring to fig. 3, disposer-1 to disposer-p in the loan platform 101 represent p business logic processing modules, respectively, and p message persistence modules in the loan platform 101 and the p business logic processing modules form a one-to-one correspondence.

In one implementation, after each service logic processing module monitors the dis broadcast message, it may detect the number of threads T _c currently running, and if T _c is less than T, it may create T-T _c threads.

Each thread reads data from the Redis queue in turn, and if any thread can successfully read the persistence table, the read data can be deleted from the Redis queue; if any thread cannot read the data, at least one retry to read the data from the Redis queue is possible; in some embodiments, if any thread cannot read data, after waiting for a set period of time, controlling the corresponding thread to try to read data from the Redis queue again, and if the data cannot be successfully read, indicating that the data in the Redis queue has been completely read, at this time, closing the corresponding thread to save the computing resources of the loan platform; here, the set time period may be set according to actual demands, for example, the set time period is 5 seconds, 6 seconds, 8 seconds, or the like.

After any thread reads the persistence table, the contents of each field in the persistence table can be analyzed to obtain the specific contents of the loan request message.

In some embodiments of the present application, after receiving the loan request message sent from the property side interface, the loan request message is mapped into the core routing table according to a predetermined field mapping table.

Accordingly, the implementation manner of routing the loan request message to the target fund party interface may be to route the loan request message to the target fund party interface according to the content in the core routing table.

In the embodiment of the application, the field mapping table is used for representing the mapping relation between the fields of the loan request message and the fields of the core routing table, so that the loan request message can be mapped into the core routing table according to the field mapping table.

In one implementation, the predetermined field mapping table may include the following fields: the asset_id field, the interface_id field, the asset_column field, the map_table_nam E field, the map_column field, the asset_column field for populating the ASSET side message field NAME, the map_table_name field for populating the TABLE NAME of the core routing TABLE, and the map_column field for populating the field NAME in the core routing TABLE.

It can be seen that, in the embodiment of the application, the mapping of the loan request message to the core routing table can be realized based on the field mapping table, so that the routing of the loan request message is realized, and the method has the characteristic of easy realization.

In some embodiments of the present application, referring to fig. 3, the loan platform 101 may further include a routing module, which may be a router, for routing the loan request message acquired by each business logic processing module to one candidate fund party interface based on the set routing rules.

In some embodiments of the present application, the loan platform 101 may further include a message conversion module (DISPA TCHER), where the message conversion module is connected to the routing module and the candidate fund party interface, and the message conversion module is configured to perform data conversion on the data sent by the routing module, and forward the data converted to the candidate fund party interface; here, for each candidate fund party interface, a corresponding message conversion module may be set, that is, the candidate fund party interface in the fund party system and the message conversion module in the loan platform form a one-to-one correspondence.

Referring to fig. 3, there are n candidate fund interfaces in the fund system 102, namely, the 1 st candidate fund interface to the n candidate fund interface, n is an integer greater than 1, and n and p may be equal or unequal; in the loan platform 101, dispatcher-1 through dispatcher-n represent n message conversion modules, respectively, and n self-property interfaces of the fund party system 102 and n message conversion modules in the loan platform 101 form a one-to-one correspondence.

In practical applications, steps 201 to 204 may be implemented by a loan-platform-based Processor, which may be at least one of Application SPECIFIC INTEGRATED Circuit (a SIC), digital signal Processor (DIGITAL SIGNAL Processor, DSP), digital signal processing device (DIGITAL SIGNAL Processing Device, DSPD), programmable logic device (Programmable Logic Device, PLD), field programmable gate array (Field Programmable GATE ARRAY, F PGA), central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor. It will be appreciated that the electronic devices implementing the above-described processor functions may be other, and embodiments of the present application are not limited.

It can be seen that, for any self-property side interface, the target property side interface can be determined according to the historical loan requests of the self-property side interface to a plurality of candidate property side interfaces, and the loan platform is not required to configure corresponding candidate property side interfaces for the self-property side interfaces in advance; according to the successful times and the failed times of the historical loan request of the candidate fund party interface from the asset party interface, the probability of obtaining the successful result of the loan request from the candidate fund party interface is determined, and further after the target fund party interface is determined, the successful result of the loan request is obtained from the target fund party interface with high probability, so that the possibility of successfully obtaining the loan is improved to a certain extent; further, compared with a mechanism of directly reading the loan request message from the property side interface, the mechanism of obtaining the loan request message from the queue can alleviate the problem of excessive resource consumption caused by excessive loan request message to a certain extent.

Further, the embodiment of the application can integrate a plurality of self-property side interfaces with a plurality of candidate fund side interfaces through the loan platform, and can determine a target fund side interface from the plurality of candidate fund side interfaces for each self-property side interface.

When new loan business requirements occur, the loan platform does not need to change candidate fund party interfaces for the self-property party interfaces, or configure new candidate fund party interfaces for the self-property party interfaces, but can determine a target fund party interface corresponding to each self-property party interface based on the first data and the second data, namely, the self-property party interfaces or the candidate fund party interfaces do not need to be reconfigured, and can determine the target fund party interfaces based on data processing logic of the loan platform, so that labor cost and time cost are reduced.

The routing rules employed by the routing module are described in exemplary fashion below.

For an implementation of determining a target fund party interface of a plurality of candidate fund party interfaces for receiving a loan request message based on the first data and the second data, a routing weight coefficient between the self-asset party interface and each candidate fund party interface may be determined, illustratively, based on the first data and the second data; determining a first set according to the first data, the second data and the routing weight coefficient, wherein the first set comprises at least one candidate fund party interface; and selecting any one candidate fund party interface from the first set as a target fund party interface.

In the embodiment of the application, the initial routing weight coefficient between the asset side interface and each candidate fund side interface can be preconfigured; in some embodiments, for the slave asset side interface and the different candidate fund side interfaces, a weight configuration table may be determined based on business factors such as regional factors, product attributes, etc., the weight configuration table representing initial routing weight coefficients between the slave asset side interface and each candidate fund side interface.

After the initial routing weight coefficient is determined, updating the initial routing weight coefficient between the self-asset side interface and each candidate fund side interface according to the first data and the second data after the first data and the second data are acquired, so as to obtain the routing weight coefficient between the self-asset side interface and each candidate fund side interface; for example, the routing weight coefficients between the slave asset side interface and the each candidate funding side interface may be calculated once per day.

Taking the kth self-asset interface in the asset side system as an example for explanation, k is 1 to p, and the kth self-asset interface is marked as A _k; the i-th candidate fund interface in the fund system can be marked as F _i, i is 1 to n; w _ki denotes the routing weight coefficient between the kth self-asset side interface and the ith candidate fund side interface; in some embodiments, w _ki can be calculated by the following equation (1):

Wherein A _k_F_i _S represents the number of times the kth self-property side interface obtains a successful result of the loan request from the ith candidate fund side interface, and ALL_S represents the total number of times the kth self-property side interface obtains a successful result of the loan request from each candidate fund side interface; a _k_F_i _F represents the number of times the kth self-side interface obtains the loan request failure result from the ith candidate fund side interface, ALL_F represents the total number of times the kth self-side interface obtains the loan request failure result from each candidate fund side interface.

As can be seen from the formula (1), when a _k_F_i _s increases, the ratio of a _k_F_i _s to all_s increases, and the value of w _ki increases; when A _k_F_i _F increases, the ratio of A _k_F_i _F to ALL_F increases, and the value of w _ki increases; it can be seen that w _ki is positively correlated with a _k_F_i _s and negatively correlated with a _k_F_i _f, and thus, when the value of w _ki is greater, it is indicated that the kth self-acquirer interface is more likely to obtain a successful outcome of the loan request from the ith candidate fund interface.

In the embodiment of the application, the first data and the second data can reflect the possibility of obtaining the successful result of the loan request from each candidate fund side interface by the property side interface, and the routing weight coefficient can also reflect the possibility of obtaining the successful result of the loan request from each candidate fund side interface by the property side interface, so that after the target fund side interface is selected in the first set determined according to the first data, the second data and the routing weight coefficient, the successful result of the loan request is obtained from the target fund side interface with high probability, thereby being beneficial to improving the possibility of successfully obtaining the loan.

In some embodiments of the application, the first set represents a set of candidate funding party interfaces that meet a first preset condition; accordingly, it may be determined whether the candidate fund side interface satisfies the first preset condition according to the following manner: for the kth asset side, determining a first difference value A _k_F_i corresponding to an ith candidate fund side interface obtained by subtracting A _k_F_i _F from A _k_F_i _S; under the condition that A _k_F_i is more than 0 and A _k_F_i*w_ki is more than or equal to D, determining that the ith candidate fund party interface meets a first preset condition; determining that the i candidate fund party interface does not meet a first preset condition under the condition that A _k_F_i is less than or equal to 0 or A _k_F_i*w_ki < D; wherein D represents a first preset value.

Here, the first preset value may be preset according to actual requirements, which is not limited in the embodiment of the present application.

It can be appreciated that the first difference corresponding to the i-th candidate fund party interface may reflect the possibility that the i-th candidate fund party interface obtains a successful result of the loan request from the i-th candidate fund party interface, and the greater the first difference corresponding to the i-th candidate fund party interface, the greater the possibility that the i-th candidate fund party interface obtains a successful result of the loan request from the i-th candidate fund party interface; further, according to the foregoing description, the greater the weight coefficient of the i candidate fund side interface, the greater the likelihood that the k candidate fund side interface will acquire a successful result of the loan request from the i candidate fund side interface is indicated; when the product of the first difference value corresponding to the ith candidate fund party interface and the weight coefficient of the ith candidate fund party interface is larger, determining that the ith candidate fund party interface meets a first preset condition, and on the basis, taking the ith candidate fund party interface as a target fund party interface, sending a loan request message to the ith candidate fund party interface, so that a loan request success result is more likely to be acquired, and the probability of failure result acquisition of the loan request can be reduced to a certain extent.

In some embodiments of the present application, in the case where the loan request result is a loan request failure result, one candidate fund party interface is selected again as the target fund party interface from the unselected candidate fund party interfaces in the first set.

It can be seen that, in the embodiment of the present application, when the result of the successful loan request is obtained from one candidate fund party interface of the first set, a loan request message may be sent to other candidate fund party interfaces of the first set, which is favorable for improving the probability of obtaining the successful result of the loan request.

In some embodiments of the present application, a second set is obtained in response to a situation that a loan request result corresponding to each candidate fund party interface of the first set is a loan request failure result, where the second set represents a set of candidate fund party interfaces that do not satisfy the first preset condition among the plurality of candidate fund party interfaces; the target funding party interface is determined in a second set.

It can be seen that, in the embodiment of the present application, when the result of the loan request failure is obtained from each candidate fund party interface of the first set, the loan request message may be sent from the candidate fund party interface that does not satisfy the first preset condition, which is favorable for improving the probability of obtaining the successful result of the loan request.

For the implementation manner of determining the target fund party interface in the second set, for example, candidate fund party interfaces meeting the second preset condition may be deleted in the second set to obtain a third set; a target funding party interface is determined in the third set.

Correspondingly, under the condition that the first difference value corresponding to the ith candidate fund side interface is smaller than or equal to 0 and the product of the first difference value corresponding to the ith candidate fund side interface and the weight coefficient of the ith candidate fund side interface is smaller than or equal to a second preset value, the ith candidate fund side interface can be determined to meet a second preset condition; the second preset value is smaller than the first preset value.

Here, the second preset value may be preset according to actual requirements, which is not limited in the embodiment of the present application.

It can be appreciated that the first difference value corresponding to the i-th candidate fund party interface may reflect the possibility that the loan request success result is obtained from the i-th candidate fund party interface by the property party interface, and the smaller the first difference value corresponding to the i-th candidate fund party interface is, the smaller the possibility that the loan request success result is obtained from the i-th candidate fund party interface by the property party interface is considered; further, according to the foregoing description, the smaller the weight coefficient of the i candidate fund side interface is, the greater the possibility that the k candidate fund side interface is to acquire the loan request failure result from the i candidate fund side interface is; and when the product of the first difference value corresponding to the ith candidate fund party interface and the weight coefficient of the ith candidate fund party interface is smaller, determining that the ith candidate fund party interface meets a second preset condition, deleting the candidate fund party interface meeting the second preset condition on the basis, and determining a target fund party interface in the rest interfaces, thereby being beneficial to obtaining the efficiency of successful result of the loan request.

In some embodiments of the application, determining the target funding party interface in the third set may include: in the third set, taking the set of candidate fund party interfaces meeting the third preset condition as a fourth set; a target funding party interface is determined in the fourth set.

Accordingly, it may be determined whether the candidate fund side interface satisfies the third preset condition according to the following manner:

Determining a second difference value obtained by subtracting the second times from the first times; the first number of times representing the number of successful requests for historical loans from the property side interface to the j-th candidate property side interface of the third set, and the second number of times representing the number of failures of the requests for historical loans from the property side interface to the j-th candidate property side interface; j is 1 to Q, Q represents the number of candidate fund party interfaces in the third set;

Under the condition that the second difference value is larger than or equal to a third preset value, determining that the j candidate fund party interface meets a third preset condition; and under the condition that the second difference value is smaller than a third preset value, determining that the j candidate fund party interface does not meet the third preset condition.

Here, the third preset value may be preset according to actual requirements, which is not limited in the embodiment of the present application.

It will be appreciated that, based on the meaning of the first number of times and the second number of times, the second difference value of the first number of times minus the second number of times may reflect a likelihood that a successful result of a loan request is obtained from the jth candidate fund side interface of the third set from the property side interface, the greater the second difference value, the greater the likelihood that a successful result of a loan request is obtained from the jth candidate fund side interface of the third set from the property side interface may be considered; therefore, the j candidate fund party interface of the third set is used as the target fund party interface, and the loan request message is sent to the j candidate fund party interface, so that the successful result of the loan request is likely to be acquired, and the probability of acquiring the failure result of the loan request can be reduced to a certain extent.

For an implementation in which the target fund party interface is determined in the fourth set, probability parameters may be obtained that characterize the probability of obtaining a successful outcome of the loan request from each candidate fund party interface of the fourth set; sequencing candidate fund party interfaces of the fourth set according to the probability parameters to obtain a sequencing result; and selecting the candidate fund party interface as a target fund party interface according to the sorting result.

In some embodiments, for the kth self-asset side interface and the ith candidate fund side interface, the probability parameter may be a first difference value corresponding to the ith candidate fund side interface, a weight coefficient of the ith candidate fund side interface, or a product of the first difference value corresponding to the ith candidate fund side interface and the weight coefficient of the ith candidate fund side interface.

It can be seen that the sorting result reflects the probability sorting of the successful result of obtaining the loan request, and the target fund party interface is selected according to the sorting result, so that the successful result of obtaining the loan request can be obtained quickly.

In some embodiments, selecting the candidate fund side interface according to the sorting result as the target fund side interface may be implemented by, in the case that the loan request result is a loan request failure result, re-selecting one candidate fund side interface according to the sorting result from the unselected candidate fund side interfaces of the fourth set as the target fund side interface.

It can be seen that, in the embodiment of the present application, when the result of the loan request failure is obtained from one candidate fund side interface of the fourth set, the loan request message may be sent to the other candidate fund side interfaces of the fourth set according to the ordering result, which is favorable for improving the probability of obtaining the result of the success of the loan request.

In some embodiments of the present application, a fifth set is obtained in response to a situation that a loan request result corresponding to each candidate fund side interface of the fourth set is a loan request failure result, where the fifth set represents a set of candidate fund side interfaces in the third set that do not satisfy a third preset condition; the target fund party interface is randomly selected from the fifth set.

It can be seen that, in the embodiment of the present application, when the result of the loan request failure is obtained from each candidate fund side interface of the fourth set, the loan request message may be sent from the candidate fund side interface that does not satisfy the third preset condition, which is favorable for improving the probability of obtaining the success result of the loan request.

In some embodiments of the application, after routing the loan request message to one of the target fund party interfaces, if the received loan request result is a successful loan request result, updating the number of successful loan requests from the property party interface to the target fund party interface; if the received loan request result is a loan request failure result, the historical number of failures of the loan request from the property party interface to the target fund party interface is updated.

It will be appreciated that in updating the number of failures and successes of historical loan requests from the property side interface to the target funds side interface, the target funds side interface may be accurately determined based on the updated data.

The routing rules of the present application are illustrated below using the kth asset side as an example.

The process of routing the loan request message sent by the kth property party may include the following steps; 1) maximum success rate matching, 2) minimum success rate removal, 3) weighted routing, 4) random routing.

The implementation of the maximum success rate matching is described below.

In the embodiment of the application, a count value A _k_F_i _L can be set, and the initial value of the count value A _k_F_i _L is 0; the method comprises the steps of adding 1 to a count value A _k_F_i _L when a kth self-side interface obtains a successful loan request result from an ith candidate fund side interface each time, subtracting 1 to the count value A _k_F_i _L when the kth self-side interface obtains a failed loan request result from the ith candidate fund side interface each time, and thus, for the kth self-side interface, the count value A _k_F_i _L is a first difference value corresponding to the ith candidate fund side interface.

In some embodiments, the count value a _k_F_i _l may be stored in an ARRAY land_array, where the ARRAY land_array stores the count values a _k_F₁ _l through a _k_F_n _l, since i may take 1 through n in sequence.

In some embodiments, all data greater than 0 is fetched from the ARRAY LOAN_ARRAY to obtain an ARRAY LOAN_ARRAY_G greater than 0; the average avg_g of the elements in the ARRAY land_array_g may then be found.

AVG_G＝sum(LOAN_ARRAY_G)/m (2)；

Where sum () represents the sum and m represents the number of elements in the ARRAY LOAN_ARRAY_G.

In some embodiments, the first preset value is determined according to an average avg_g of elements in the ARRAY load_array_g, the first preset value being avg_g x m/2.

It can be seen that, in the case that the first difference value corresponding to the i candidate fund party interface is greater than 0, a _k_F_i _l is an element in the group of the local_array_g, and at this time, it can be determined whether the product of a _k_F_i _l and w _ki is greater than or equal to a first preset value; when the product of a _k_F_i _l and w _ki is greater than or equal to the first preset value, it may be determined that the ith candidate fund party interface meets the first preset condition, it may be considered that the kth self-property party interface has a high possibility of acquiring a successful result of the loan request from the ith candidate fund party interface, and the ith candidate fund party interface may be preferentially considered as a candidate fund party interface in the first set, so as to promote the possibility of successfully acquiring the loan.

In some embodiments, in the case where the product of a _k_F_i _l and w _ki is greater than or equal to the first preset value, the i-th candidate fund party interface may be taken as the target fund party interface, then the routing module may route the k-th LOAN request message sent from the property party interface to the i-th candidate fund party interface, and when the received LOAN request result is a LOAN request failure result, may subtract 1 from the count value a _k_F_i _l, and remove a _k_F_i _l in the ARRAY land_array; when the received loan request result is a loan request success result, the count value A _k_F_i _L may be incremented by 1 and the loan request success result may be returned to the kth self-property side interface.

In the embodiment of the present application, a loan request message may be sent to any candidate fund party interface that satisfies a first preset condition, and in the case that a result of failure in the loan request is received, one candidate fund party interface may be reselected as a target fund party interface from unselected candidate fund party interfaces in the first set.

The implementation of very small success rate removal is described below.

Traversing the ARRAY LOAN_ARRAY, and taking out all elements smaller than or equal to 0, wherein all elements smaller than or equal to 0 taken out form an ARRAY LOAN_ARRAY_L; the average AVG L of the ARRAY load _ ARRAY _ L is found,

AVG_L＝ sum(LOAN_ARRAY_L)/s (3)；

Where s represents the number of elements in the ARRAY LOAN_ARRAY_L.

In some embodiments, a second preset value may be determined according to the average avg_l, the second preset value being avg_l x s/2.

As can be seen, in the case that the first difference value corresponding to the i candidate fund party interface is less than or equal to 0, a _k_F_i _l is an element in the group of the local_array_l, at this time, it can be determined whether the product of a _k_F_i _l and w _ki is less than or equal to the second preset value; in the case where the product of a _k_F_i _l and w _ki is less than or equal to the second preset value, it may be determined that the ith candidate fund side interface satisfies the second preset condition, it may be considered that the kth self-asset side interface has a high likelihood of acquiring a LOAN request failure result from the ith candidate fund side interface, and the ith candidate fund side interface may be deleted from the ARRAY load_array.

The implementation of weighted routing is described below.

In some embodiments, after each candidate fund side interface satisfying the second preset condition is deleted from the ARRAY loan_array, an average value of the ARRAY loan_array is calculated, and the average value of the ARRAY loan_array is used as the third preset value.

For each element in the ARRAY LOAN_ARRAY, the size relation between the element and the third preset value can be judged, so that all elements larger than the third preset value are taken out from the ARRAY LOAN_ARRAY to obtain an ARRAY LOAN_ARRAY_A.

For an ARRAY LOAN_ARRAY_A, calculating probability parameters corresponding to each element; illustratively, in the case where a _k_F_i _l is an element of the group of land_array_a, the probability parameter may be calculated according to equation (4):

V_ki＝A_k_F_i_L*w_ki (4)；

Wherein V _ki represents the probability parameter corresponding to a _k_F_i _l.

The probability parameters corresponding to each element in the ARRAY LOAN_ARRAY_A may form a weighting ARRAY LOAN_WEIGHT.

The WEIGHT ARRAYs LOAN_WEIGHT are ordered from large to small, so that an ordered WEIGHT ARRAY LOAN_WEIGHT_ARRAY can be obtained, wherein the WEIGHT ARRAY LOAN_WEIGHT_ARRAY is the ordering result.

Selecting a corresponding candidate fund party interface as a target fund party interface according to element ordering in the weighted ARRAY LOAN_WEIGHT_ARRAY, ordering the corresponding elements in the ARRAY LOAN_ARRAY under the condition that a LOAN request result returned by one target fund party interface is a LOAN request failure result, and re-selecting the other candidate fund party interface as the target fund party interface until a LOAN request success result is obtained or determining that the LOAN request result corresponding to each element in the weighted ARRAY LOAN_WEIGHT_ARRAY is the LOAN request failure result.

In some embodiments, after sending the loan request message to the ith candidate fund party interface, the count value a _k_F_i _l is incremented by 1 if a successful result of the loan request is obtained, and the count value a _k_F_i _l is decremented by 1 if a failed result of the loan request is obtained.

The implementation of random routing is described below.

In the process of the weighted routing, if the successful result of the loan request is not obtained, one candidate fund party interface is selected randomly from the rest candidate fund party interfaces to be used as the target fund party interface.

In some embodiments, the ARRAY LOAN_ARRAY may be traversed, and the weighted values of the elements of the ARRAY LOAN_ARRAY calculated; for example, in the case where a _k_F_i _l is an element of the group of the LOAN_ARRAY, the probability parameter described above may be taken as a weighted value of a _k_F_i _l.

Forming a weighted ARRAY LOAN_WEI GHT_A by using weighted values of all elements of the ARRAY LOAN_ARRAY, randomly taking out the elements from the weighted ARRAY LOAN_WEIGHT_A, and determining a target fund side interface based on the randomly taken out elements; in some embodiments, the elements may be randomly fetched from the weighting array LO an_weight_a based on equation (5):

V＝LOAN_WEIGHT_A[n％random(10)] (5)；

wherein [ n% random (10) ] represents that a remainder operation is performed on a random number smaller than or equal to 10, and V represents the sequence number of an element from the weighting array load_weight_a.

In some embodiments, a candidate fund party interface may be determined based on the randomly fetched elements, the determined candidate fund party interface may be used as the target fund party interface, and then the loan request message may be routed to the target fund party interface; under the condition that the LOAN request result returned by one target fund party interface is a LOAN request failure result, another candidate fund party interface can be reselected as the target fund party interface based on the weighted array LOAN_WEIGHT_A until a LOAN request success result is obtained, or the LOAN request result corresponding to each element in the weighted array LOAN_WEIGHT_A is determined to be the LOAN request failure result; when the LOAN request result corresponding to each element in the weighting array LOAN_WEIGHT_A is the LOAN request failure result, the flow of the LOAN request method of the embodiment of the application can be ended.

In some embodiments, after sending the loan request message to the i-th candidate fund party interface, if a successful result of the loan request is obtained, the count value a _k_F_i _l is incremented by 1; if a LOAN request failure result is obtained, the count value A _k_F_i _L is decremented by 1 and the element A _k_F_i _L is deleted from the LOAN_ARRAY.

On the basis of the data request method provided by the embodiment, the embodiment of the application also provides a data request device; fig. 4 is a schematic diagram of an alternative composition structure of a data request device according to an embodiment of the present application, and as shown in fig. 4, the data request device 400 may include:

the transceiver module 401 is configured to receive a loan request message sent from the property side interface, and cache the loan request message into a queue;

An obtaining module 402, configured to obtain first data and second data, where the first data represents a success number of historical loan requests from the property side interface to a plurality of candidate property side interfaces, and the second data represents a failure number of historical loan requests from the property side interface to the plurality of candidate property side interfaces;

A processing module 403, configured to determine, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces;

The transceiver module 401 is further configured to alternately read loan request messages from the queue through preset threads, and after any one of the threads reads a loan request message from the queue, route the loan request message to the target fund party interface, and receive a loan request result returned by the target fund party interface.

In some embodiments of the present application, the processing module 403, configured to determine, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces, includes:

In some embodiments of the present application, the processing module 403, configured to determine, according to the first data and the second data, a routing weight coefficient between the self-asset side interface and each candidate fund side interface, includes:

The processing module 403 is further configured to determine a first difference value a_f _i corresponding to an i candidate fund party interface obtained by subtracting a_f _i _f from a_f _i _s; and under the condition that A_F _i is greater than 0 and A_F _i*w_i is greater than or equal to D, determining that the ith candidate fund party interface meets a first preset condition, wherein D represents a first preset value.

In some embodiments of the present application, the processing module 403 is further configured to, in a case where the loan request result is a loan request failure result, reselect one candidate fund side interface among the unselected candidate fund side interfaces of the first set as the target fund side interface.

In some embodiments of the present application, the processing module 403 is configured to determine, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces, further includes:

the target funding party interface is determined in the second set.

In some embodiments of the application, the processing module 403, configured to determine the target funding party interface in the second set, includes:

In some embodiments of the application, the processing module 403, configured to determine the target funding party interface in the third set, includes:

the processing module 403 is further configured to:

In some embodiments of the application, the processing module 403, configured to determine the target funding party interface in the fourth set, includes:

In some embodiments of the present application, the processing module 403, configured to select, according to the sorting result, a candidate fund party interface as the target fund party interface, includes:

In some embodiments of the present application, the processing module 403, configured to determine the target fund party interface in the third set, further includes:

the target funding party interface is randomly selected from the fifth set.

In some embodiments of the present application, the processing module 403 is further configured to:

In some embodiments of the present application, the transceiver module 401 is further configured to map the loan request packet to a core routing table according to a predetermined field mapping table after receiving the loan request packet from the self-property side interface;

The transceiver module 401, configured to route the loan request message to the target fund party interface, includes: and routing the loan request message to the target fund party interface according to the content in the core routing table.

In practical applications, the transceiver module 401, the obtaining module 402 and the processing module 403 may be implemented by using a processor, where the processor may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, a controller, a microcontroller and a microprocessor. It will be appreciated that the electronic devices implementing the above-described processor functions may be other, and embodiments of the present application are not limited.

It should be noted that the description of the above device embodiments is similar to the description of the method embodiments described above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, please refer to the description of the embodiments of the method of the present application.

It should be noted that, in the embodiment of the present application, if the above-mentioned data request method is implemented in the form of a software functional module, and sold or used as a separate product, the data request method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied essentially or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a terminal, a server, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, embodiments of the application are not limited to any specific combination of hardware and software.

Correspondingly, the embodiment of the application further provides a computer program product, which comprises computer executable instructions for implementing any one of the data request methods provided by the embodiment of the application.

Accordingly, an embodiment of the present application further provides a computer storage medium, where computer executable instructions are stored on the computer storage medium, where the computer executable instructions are configured to implement any one of the data request methods provided in the foregoing embodiments.

An embodiment of the present application further provides an electronic device, and fig. 5 is a schematic diagram of an optional composition structure of the electronic device provided in the embodiment of the present application, as shown in fig. 5, where, the electronic device 500 includes:

a memory 501 for storing executable instructions;

the processor 502 is configured to implement any one of the data request methods described above when executing the executable instructions stored in the memory 501.

The processor 502 may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, a controller, a microcontroller, and a microprocessor.

The computer readable storage medium/Memory may be a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable programmable Read Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), a magnetic random access Memory (Ferromagnetic Random Access Memory, FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Read Only optical disk (Compact Disc Read-Only Memory, CD-ROM); but may also be various terminals such as mobile phones, computers, tablet devices, personal digital assistants, etc., that include one or any combination of the above-mentioned memories.

The embodiment of the application also provides a loan platform which comprises any one of the data request devices or any one of the electronic devices.

It should be noted here that: the description of the storage medium and apparatus embodiments above is similar to that of the method embodiments described above, with similar benefits as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and the apparatus of the present application, please refer to the description of the method embodiments of the present application.

It should be appreciated that reference throughout this specification to "some embodiments" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrase "in some embodiments" in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purposes of the embodiment of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.

Or the above-described integrated units of the application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied essentially or in a part contributing to the related art in the form of a software product stored in a storage medium, including several instructions for causing an apparatus automatic test line to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

The methods disclosed in the method embodiments provided by the application can be arbitrarily combined under the condition of no conflict to obtain a new method embodiment.

The features disclosed in the embodiments of the method or the apparatus provided by the application can be arbitrarily combined without conflict to obtain new embodiments of the method or the apparatus.

The foregoing is merely an embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of requesting data, the method comprising:

Receiving a loan request message sent from an asset side interface, and caching the loan request message into a queue;

Reading loan request messages from the queue through preset threads in turn, and after any one of the threads reads the loan request messages from the queue, routing the loan request messages to the target fund party interface and receiving a loan request result returned by the target fund party interface; the determining, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces includes:

Selecting any one candidate fund party interface from the first set as the target fund party interface; said determining, based on said first data and said second data, routing weight coefficients between said self-asset side interface and said each candidate fund side interface, comprising:

2. The data request method of claim 1, wherein the first set represents a set of candidate funding party interfaces that meet a first preset condition;

The method further comprises the steps of: determining a first difference value A_F _i corresponding to an i candidate fund party interface obtained by subtracting A_F _i _F from A_F _i _S;

And under the condition that A_F _i is greater than 0 and A_F _i*w_i is greater than or equal to D, determining that the ith candidate fund party interface meets a first preset condition, wherein D represents a first preset value.

3. The data request method according to claim 2, characterized in that the method further comprises: and under the condition that the loan request result is a loan request failure result, re-selecting one candidate fund party interface from the unselected candidate fund party interfaces of the first set as the target fund party interface.

4. The data request method of claim 3, wherein the determining a target one of the plurality of candidate fund party interfaces for receiving the loan request message based on the first data and the second data further comprises:

the target funding party interface is determined in the second set.

5. The data request method of claim 4, wherein the determining the target funding party interface in the second set comprises:

The method further comprises the steps of:

6. The data request method of claim 5, wherein the determining the target funding party interface in the third set comprises:

The method further comprises the steps of:

7. The data request method of claim 6, wherein the determining the target funding party interface in the fourth set comprises:

8. The method of claim 7, wherein selecting a candidate fund side interface as the target fund side interface according to the ranking result comprises:

9. The data request method of claim 8, wherein the determining the target funding party interface in the third set further comprises:

the target funding party interface is randomly selected from the fifth set.

10. The data request method according to any one of claims 1 to 9, characterized in that the method further comprises:

11. The data request method according to any one of claims 1 to 9, characterized in that the method further comprises: after any one of the threads reads data from the queue, deleting the read data from the queue; and closing the corresponding thread under the condition that any thread fails to read data from the queue.

12. The data request method according to any one of claims 1 to 9, characterized in that the method further comprises:

13. A data requesting apparatus, the apparatus comprising:

The receiving and transmitting module is used for receiving the loan request message sent by the property side interface and caching the loan request message into a queue;

The receiving and sending module is further configured to alternately read loan request messages from the queue through preset threads, and after any one of the threads reads a loan request message from the queue, route the loan request message to the target fund party interface, and receive a loan request result returned by the target fund party interface;

The determining, according to the first data and the second data, a target fund party interface for receiving the loan request message from among the plurality of candidate fund party interfaces includes:

14. An electronic device, the electronic device comprising:

a memory for storing executable instructions;

A processor for implementing the data request method of any one of claims 1 to 12 when executing executable instructions stored in said memory.

15. A loan platform comprising the data requesting apparatus of claim 13 or the electronic device of claim 14.

16. A computer readable storage medium storing executable instructions for implementing the data request method of any one of claims 1 to 12 when executed by a processor.