CN110782310A - Method, device and system for asynchronously acquiring user attribute information from third-party platform - Google Patents
Method, device and system for asynchronously acquiring user attribute information from third-party platform Download PDFInfo
- Publication number
- CN110782310A CN110782310A CN201910915374.9A CN201910915374A CN110782310A CN 110782310 A CN110782310 A CN 110782310A CN 201910915374 A CN201910915374 A CN 201910915374A CN 110782310 A CN110782310 A CN 110782310A
- Authority
- CN
- China
- Prior art keywords
- user
- server
- attribute information
- information
- query request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0609—Buyer or seller confidence or verification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Abstract
The invention discloses a method, a device, a system and a computer readable medium for asynchronously acquiring user attribute information from third-party platforms, wherein the method comprises the steps that a first server acquires basic information of a user, and inquires first attribute information of the user from one or more of a plurality of third-party platforms based on the basic information; the first server and the second server are synchronous, and the user information is sent to the second server; the second server inquires second attribute information of the user from one or more of the third-party platforms based on the acquired user information; the first server inquires third attribute information of the user from one or more of the plurality of third-party platforms; and the first server synchronizes with the second server again, and sends the third attribute information of the user to the second server. By adopting the technical scheme, the third-party platform is queried in parallel in an asynchronous mode, so that the overall query waiting time is reduced, and the user experience is better.
Description
Technical Field
The invention relates to the field of computer information processing, in particular to a method, a device and a system for asynchronously acquiring user attribute information from a third-party platform.
Background
After the user registers in the internet finance-related application program, in order to judge the type of the user, risk identification needs to be performed on the identity of the user. Usually, a merchant does not have attribute information of a user, and cannot directly perform judgment, and needs to acquire the attribute information of the user by querying a plurality of third-party platforms to perform judgment.
The currently adopted mode is that a series structure is formed between a merchant and a plurality of third party platforms, and attribute information of a user is acquired one by one through each third party platform. However, because the processing time of different third-party platforms is different, the time required for some third-party platforms to perform query processing is long, or a certain third-party platform has a high concurrency condition, so that the overall query time is too long, and the experience of the user is very poor.
Disclosure of Invention
The invention aims to solve the problems that the query time is not easy to control and the user experience is poor in the conventional user information query mode.
In order to solve the above technical problem, a first aspect of the present invention provides a method for acquiring user attribute information, including:
the method comprises the steps that a first server obtains basic information of a user, sends a first query request to one or more of a plurality of third-party platforms based on the basic information, and queries first attribute information of the user;
the first server and the second server are synchronous, and the user information is sent to the second server;
the second server sends a second query request to one or more of the third-party platforms based on the acquired user information, queries second attribute information of the user, returns first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returns second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request;
the first server sends a third query request to one or more of the third-party platforms based on the user information, third attribute information of the user is queried, and the one or more servers return the third attribute information of the user to the third server;
and the first server synchronizes with the second server again, and sends the third attribute information of the user to the second server.
According to a preferred embodiment of the present invention, the first query request and the second query request are asynchronous requests.
According to a preferred embodiment of the present invention, the user information includes basic information and identity information.
According to a preferred embodiment of the invention, the basic information comprises a telephone number of the user and the identity information comprises a name and a certificate ID of the user.
According to a preferred embodiment of the present invention, the one or more third party platforms receiving the first query request, the second query request and the third query request are different from each other.
According to a preferred embodiment of the present invention, the first server and the second server are REDIS servers.
According to a preferred embodiment of the present invention, the time for the one or more third party platforms receiving the first query request to query the first attribute information of the user is longer than the time for the one or more third platforms receiving the second query request to query the first attribute information of the user.
According to a preferred embodiment of the present invention, the second server classifies the user after receiving the first attribute information, the second attribute information, and the third attribute information of the user.
A second aspect of the present invention provides a system for asynchronously obtaining user attribute information from a third-party platform, the system comprising:
the first query module is used for acquiring basic information of a user through a first server, sending a first query request to one or more of a plurality of third-party platforms based on the basic information and querying first attribute information of the user;
the first synchronization module synchronizes the first server and the second server and sends the user information to the second server;
the second query module is used for sending a second query request to one or more of the third-party platforms through the second server based on the acquired user information, querying second attribute information of the user, returning first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returning second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request;
a third query module, configured to query, by the first server, third attribute information of the user by sending a third query request to one or more of the plurality of third party platforms based on the user information, where the one or more servers return the third attribute information of the user to a third server;
and the second synchronization module is used for synchronizing the first server with the second server again and sending the third attribute information of the user to the second server.
According to a preferred embodiment of the present invention, the first query request and the second query request are asynchronous requests.
According to a preferred embodiment of the present invention, the user information includes basic information and identity information
According to a preferred embodiment of the invention, the basic information comprises a telephone number of the user and the identity information comprises a name and a certificate ID of the user.
According to a preferred embodiment of the present invention, the one or more third party platforms receiving the first query request, the second query request and the third query request are different from each other.
According to a preferred embodiment of the present invention, the first server and the second server are REDIS servers.
According to a preferred embodiment of the present invention, the time for the one or more third party platforms receiving the first query request to query the first attribute information of the user is longer than the time for the one or more third platforms receiving the second query request to query the first attribute information of the user.
According to a preferred embodiment of the present invention, the second server classifies the user after receiving the first attribute information, the second attribute information, and the third attribute information of the user.
The third aspect of the present invention provides a system for asynchronously acquiring user attribute information from a third-party platform, including:
a storage unit for storing a computer executable program;
and the processing unit is used for reading the computer executable program in the storage unit so as to execute any method for asynchronously acquiring the user attribute information from the third-party platform.
A fourth aspect of the present invention is directed to a computer-readable medium storing a computer-readable program, wherein the computer-readable program is configured to perform a method for asynchronously obtaining user attribute information from a third-party platform.
By adopting the technical scheme, the third-party platform is queried in parallel in an asynchronous mode, the query time is reduced, the query time is long for partial third-party platforms, the query is carried out in advance, the whole query waiting time is reduced, and the user experience is better.
Drawings
In order to make the technical problems solved by the present invention, the technical means adopted and the technical effects obtained more clear, the following will describe in detail the embodiments of the present invention with reference to the accompanying drawings. It should be noted, however, that the drawings described below are only illustrations of exemplary embodiments of the invention, from which other embodiments can be derived by those skilled in the art without inventive step.
FIG. 1 is a schematic flow chart illustrating asynchronous acquisition of user attribute information from a third-party platform according to an embodiment of the present invention;
FIG. 2 is a timing diagram illustrating asynchronous retrieval of user attribute information from a third party platform in an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of an apparatus for asynchronously acquiring user attribute information from a third-party platform according to an embodiment of the present invention;
FIG. 4 is a block diagram of a structural framework of a system for asynchronously obtaining user attribute information from a third-party platform according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer-readable storage medium in an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention may be embodied in many specific forms, and should not be construed as limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art.
The structures, properties, effects or other characteristics described in a certain embodiment may be combined in any suitable manner in one or more other embodiments, while still complying with the technical idea of the invention.
In describing particular embodiments, specific details of structures, properties, effects, or other features are set forth in order to provide a thorough understanding of the embodiments by one skilled in the art. However, it is not excluded that a person skilled in the art may implement the invention in a specific case without the above-described structures, performances, effects or other features.
The flow chart in the drawings is only an exemplary flow demonstration, and does not represent that all the contents, operations and steps in the flow chart are necessarily included in the scheme of the invention, nor does it represent that the execution is necessarily performed in the order shown in the drawings. For example, some operations/steps in the flowcharts may be divided, some operations/steps may be combined or partially combined, and the like, and the execution order shown in the flowcharts may be changed according to actual situations without departing from the gist of the present invention.
The block diagrams in the figures generally represent functional entities and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different network and/or processing unit devices and/or microcontroller devices.
The same reference numerals denote the same or similar elements, components, or parts throughout the drawings, and thus, a repetitive description thereof may be omitted hereinafter. It will be further understood that, although the terms first, second, third, etc. may be used herein to describe various elements, components, or sections, these elements, components, or sections should not be limited by these terms. That is, these phrases are used only to distinguish one from another. For example, a first device may also be referred to as a second device without departing from the spirit of the present invention. Furthermore, the term "and/or", "and/or" is intended to include all combinations of any one or more of the listed items.
Fig. 1 is a flowchart of a method for acquiring user attribute information according to the present invention, and fig. 2 is a timing chart of the method for acquiring user attribute information according to the present invention, as shown in fig. 1, the method of the present invention has the following steps:
s1, the first server acquires the basic information of the user, and sends a first query request to one or more of the third-party platforms based on the basic information to query the first attribute information of the user.
In this embodiment, when the user registers, the registration information is filled in, and at this time, the first server can obtain the basic information of the user. The basic information of the user includes a phone number of the user.
In this embodiment, after the user registers, the user needs to be subjected to risk assessment, and at this time, the user attribute information needs to be queried according to the information registered by the user, where the attribute information includes, but is not limited to, borrowing information (e.g., whether there is a loan or not, the amount of the loan, etc.), repayment information (e.g., whether there is a repayment, the number of repayment items, the number of unpaid repayment items, etc.), transaction information (the number of recent transactions, the transaction amount, etc.), overdue information (the amount of overdue, the overdue time, the number of overdue times, etc.), and credit information. And the user attribute information is stored in different third party platforms. The third-party platform comprises various platforms such as an e-commerce platform and a payment platform. Some of these platforms take a long time to query due to interfaces, protocols, and other reasons, resulting in an overall query time that is too long. In order to reduce the time for inquiring, some third party platforms with longer inquiring time can inquire in advance.
In the present embodiment, the first attribute information, the second attribute information, and the third attribute information are one or more types of attribute information.
And S2, synchronizing the first server and the second server, and sending the user information to the second server.
In this embodiment, the second server stores a service model, and can perform calculation according to the attribute information of the user to determine the risk level of the user. A higher risk level indicates a lower financial security for the user.
In the embodiment, the user completes registration and fills in the user information, and the first server synchronizes with the second server after acquiring the user information and synchronizes the user information to the second server. The user information includes, but is not limited to, name, certificate ID, bank card information, family relationship information, interpersonal relationship information, biometric information, social security information, household registration information, and public accumulation fund information.
In this embodiment, the second server is a server of a third-party client credit inquiry institution authorized by a certain institution, the user gives authorization during registration, and the second server can inquire credit investigation information in the user attribute information according to the user information of the user. And inputting the credit information of the user into the service model, and judging the risk level of the user. In the used attribute information, different weights are set for different attribute information, and the weight of the credit information is relatively high. Therefore, the lower the risk level of the user is judged by the business model as the better the credit information of the user is.
In this embodiment, when the first server and the second server are synchronized, the second server further returns the risk level of the user obtained by the judgment to the first server.
In this embodiment, a threshold may be set for the risk level of the user, and when the risk level of the user determined by the business model is lower than the threshold, it indicates that the financial security of the user is very high, and the user may be given an operation of passing the audit without performing subsequent steps.
In other embodiments, the second server stores other information in the attribute information of the user, the second server obtains the stored attribute information of the user according to the user information, the attribute information is input into the service model, and the service model judges the risk level of the user according to the attribute information. If the business model can judge the risk level of the user according to the user attribute information stored in the second server, and the risk level of the user is lower than the set threshold, the financial security of the user is high, and subsequent steps do not need to be executed.
If the risk level of the user cannot be judged or the risk level of the user is judged to be higher than the threshold value, the subsequent steps are continuously executed, and more attribute information of the user is obtained from the third-party server for judgment.
In this embodiment, the first server and the second server are different servers, and in other embodiments, the first server and the second server may be the same server.
S3, the second server sends a second query request to one or more of the third-party platforms based on the obtained user information, queries the second attribute information of the user, returns the first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returns the second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request.
In the present embodiment, the first attribute information and the second attribute information are one or more kinds of attribute information. In order to save the query time, in the present embodiment, the first attribute information and the second attribute information do not overlap, so that the query is prevented from being repeated and the overall query time is prevented from being prolonged.
In this embodiment, as shown in the timing diagram of fig. 2, one or more third party platforms receiving the first query request are different from one or more third party platforms receiving the second query request.
In other embodiments, the one or more third-party platforms receiving the first query request and the one or more third-party platforms receiving the second query request may be the same, but the queried attribute information is different, and some attribute information queries take longer, so that asynchronous queries need to be performed in advance.
In the present embodiment, the time for returning the first attribute information is earlier than the time for returning the second attribute information. In other embodiments, the time for returning the first attribute information may be later than the time for returning the second attribute information, or may be returned at the same time.
In this embodiment, the first query request and the second query request are asynchronous requests.
S4, the first server sends a third query request to one or more of the third party platforms based on the user information, the third query request queries third attribute information of the user, and the one or more servers return the third attribute information of the user to the first server.
In this embodiment, after the first server and the second server are synchronized, the first server queries the third-party platform for the third attribute information of the user according to the user information. Similarly, the third attribute information is different from the first attribute information and the second attribute information. The third party platform for inquiring the third attribute information is also different from the third party platform for inquiring the first attribute information and the third party platform for inquiring the second attribute information.
In this embodiment, because the interfaces are different, the protocols are different, and the like, the first server and the second server both have their corresponding third-party platforms, and therefore it is necessary to query the attribute information of the user to their corresponding third-party platforms.
And S5, synchronizing the first server with the second server again, and sending the third attribute information of the user to the second server.
In this embodiment, when the first server synchronizes with the second server again, the third attribute information of the user is sent to the second server, and the second server collects the received first attribute information, second attribute information, and third attribute information of the user.
In this embodiment, the second server further inputs the summarized first attribute information, second attribute information, and third attribute information into the service model to determine the risk level of the user, and sends the determined user level to the first server.
Fig. 2 is a timing diagram of asynchronously acquiring user attribute information from a third-party platform, and fig. 2 is taken as an embodiment to describe an interaction process in detail.
Example 1:
s201, a user registers with a first server, the first server acquires a mobile phone number of the user during registration, the first server sends a first query request to a third-party platform according to the mobile phone number of the user to query first attribute information of the user, the first attribute information is borrowing information (such as whether the user has borrowed money, the amount of the borrowed money and the like), repayment information (such as whether the user has repayment, the amount of the repayment items and the amount of the unpaid items and the like), transaction information (recent transaction stroke number, transaction amount and the like), overdue information (overdue amount, overdue time, overdue times and the like), credit information and other attribute information.
S202, the user finishes registration, the first server obtains user information of the user, and the user information comprises but is not limited to names, certificate IDs, bank card information, family relation information, interpersonal relation information, biological feature information, social security information, household registration information and public accumulation fund information. And the first server is synchronous with the second server, and the acquired user information is synchronous to the second server.
S203, the second server sends a second query request to the third-party platform according to the acquired user information, and queries second attribute information of the user, wherein the second attribute information is one or more of borrowing information (such as whether the borrowed money exists or not, the borrowing amount and the like), repayment information (such as whether the repayment is carried out or not, the number of repayment items, the number of unpaid repayment items and the like), transaction information (recent transaction number, transaction amount and the like), overdue information (overdue amount, overdue time, overdue times and the like), credit investigation information and the like.
S204, the third-party platform queries and obtains the first attribute information of the user, and sends the first attribute information obtained through query to the second server.
S205, the third-party platform queries and obtains second attribute information of the user, and sends the second attribute information obtained through query to the second server.
S206, the first server sends a third inquiry request to the third-party platform according to the user information of the user, and inquires second attribute information of the user, wherein the second attribute information is one or more of borrowing information (such as whether the user has borrowed money, the amount of borrowed money and the like), repayment information (such as whether the user has repayment, the number of the repayment items and the number of the unpaid repayment items and the like), transaction information (the number of recent transactions, the transaction amount and the like), overdue information (overdue amount, overdue time, the overdue times and the like), credit information and the like.
S207, the third party platform queries and obtains third attribute information of the user, and the third attribute information obtained through query is sent to the first server.
S208, the first server and the second server are synchronized again, the first server sends the third attribute information of the user to the second server, and the second server collects the first attribute information, the second attribute information and the third attribute information of the user.
As shown in fig. 3, in this embodiment, a system 300 for asynchronously acquiring user attribute information from a third-party platform is further provided, where the system 300 includes:
the first query module 301 obtains basic information of a user through a first server, and sends a first query request to one or more of a plurality of third party platforms based on the basic information to query first attribute information of the user.
In this embodiment, when the user registers, the registration information is filled in, and at this time, the first server can obtain the basic information of the user. The basic information of the user includes a phone number of the user.
In this embodiment, after the user registers, the user needs to be subjected to risk assessment, and at this time, the user attribute information needs to be queried according to the information registered by the user, where the attribute information includes, but is not limited to, borrowing information (e.g., whether there is a loan or not, the amount of the loan, etc.), repayment information (e.g., whether there is a repayment, the number of repayment items, the number of unpaid repayment items, etc.), transaction information (the number of recent transactions, the transaction amount, etc.), overdue information (the amount of overdue, the overdue time, the number of overdue times, etc.), and credit information. And the user attribute information is stored in different third party platforms. The third-party platform comprises various platforms such as an e-commerce platform and a payment platform. Some of these platforms take a long time to query due to interfaces, protocols, and other reasons, resulting in an overall query time that is too long. In order to reduce the time for inquiring, some third party platforms with longer inquiring time can inquire in advance.
In the present embodiment, the first attribute information, the second attribute information, and the third attribute information are one or more types of attribute information.
The first synchronization module 302 synchronizes the first server with the second server and sends the user information to the second server.
In this embodiment, the second server stores a service model, and can perform calculation according to the attribute information of the user to determine the risk level of the user. A higher risk level indicates a lower financial security for the user.
In the embodiment, the user completes registration and fills in the user information, and the first server synchronizes with the second server after acquiring the user information and synchronizes the user information to the second server. The user information includes, but is not limited to, name, certificate ID, bank card information, family relationship information, interpersonal relationship information, biometric information, social security information, household registration information, and public accumulation fund information.
In this embodiment, the second server is a server of a third-party client credit inquiry institution authorized by a certain institution, the user gives authorization during registration, and the second server can inquire credit information in the user attribute information according to the user information of the user. And inputting the credit information of the user into the service model, and judging the risk level of the user. In the used attribute information, different weights are set for different attribute information, and the weight of the credit information is relatively high. Therefore, the lower the risk level of the user is judged by the business model as the better the credit information of the user is.
In this embodiment, when the first server and the second server are synchronized, the second server further returns the risk level of the user obtained by the judgment to the first server.
In this embodiment, a threshold may be set for the risk level of the user, and when the risk level of the user determined by the business model is lower than the threshold, it indicates that the financial security of the user is very high, and the user may be given an operation of passing the audit without performing subsequent steps.
In other embodiments, the second server stores other information in the attribute information of the user, the second server obtains the stored attribute information of the user according to the user information, the attribute information is input into the service model, and the service model judges the risk level of the user according to the attribute information. If the business model can judge the risk level of the user according to the user attribute information stored in the second server, and the risk level of the user is lower than the set threshold, the financial security of the user is high, and subsequent steps do not need to be executed.
If the risk level of the user cannot be judged or the risk level of the user is judged to be higher than the threshold value, the subsequent steps are continuously executed, and more attribute information of the user is obtained from the third-party server for judgment.
In this embodiment, the first server and the second server are different servers, and in other embodiments, the first server and the second server may be the same server.
The second query module 303 sends, by the second server, a second query request to one or more of the plurality of third-party platforms based on the obtained user information, queries the second attribute information of the user, returns, to the second server, the first attribute information of the user by the one or more third-party platforms that receive the first query request, and returns, to the second server, the second attribute information of the user by the one or more third-party platforms that receive the second query request.
In the present embodiment, the first attribute information and the second attribute information are one or more kinds of attribute information. In order to save the query time, in the present embodiment, the first attribute information and the second attribute information do not overlap, so that the query is prevented from being repeated and the overall query time is prevented from being prolonged.
In this embodiment, the one or more third party platforms that receive the first query request are different from the one or more third party platforms that receive the second query request.
In other embodiments, the one or more third-party platforms receiving the first query request and the one or more third-party platforms receiving the second query request may be the same, but the queried attribute information is different, and some attribute information queries take longer, so that asynchronous queries need to be performed in advance.
In the present embodiment, the time for returning the first attribute information is earlier than the time for returning the second attribute information. In other embodiments, the time for returning the first attribute information may be later than the time for returning the second attribute information, or may be returned at the same time.
In this embodiment, the first query request and the second query request are asynchronous requests.
The third query module 304 queries the third attribute information of the user by the first server sending a third query request to one or more of the plurality of third party platforms based on the user information, the one or more servers returning the third attribute information of the user to the first server.
In this embodiment, after the first server and the second server are synchronized, the first server queries the third-party platform for the third attribute information of the user according to the user information. Similarly, the third attribute information is different from the first attribute information and the second attribute information. The third party platform for inquiring the third attribute information is also different from the third party platform for inquiring the first attribute information and the third party platform for inquiring the second attribute information.
In this embodiment, because the interfaces are different, the protocols are different, and the like, the first server and the second server both have their corresponding third-party platforms, and therefore it is necessary to query the attribute information of the user to their corresponding third-party platforms.
The second synchronization module 305 synchronizes the first server with the second server again, and transmits the third attribute information of the user to the second server.
In this embodiment, when the first server synchronizes with the second server again, the third attribute information of the user is sent to the second server, and the second server collects the received first attribute information, second attribute information, and third attribute information of the user.
In this embodiment, the second server further inputs the summarized first attribute information, second attribute information, and third attribute information into the service model to determine the risk level of the user, and sends the determined user level to the first server.
As shown in fig. 4, in an embodiment of the present invention, a system for asynchronously acquiring user attribute information from a third-party platform is further disclosed, and the system for asynchronously acquiring user attribute information from a third-party platform shown in fig. 4 is merely an example, and should not bring any limitation to the function and the application scope of the embodiment of the present invention.
The system 400 for asynchronously obtaining user attribute information from a third party platform includes a storage unit 420 for storing a computer executable program; a processing unit 410 for reading the computer executable program in the storage unit to perform the steps of various embodiments of the present invention.
The system 400 for asynchronously acquiring user attribute information from a third party platform in this embodiment further includes a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410), a display unit 440, and the like.
The storage unit 420 stores a computer-readable program, which may be a code of a source program or a read-only program. The program may be executed by the processing unit 410 such that the processing unit 410 performs the steps of various embodiments of the present invention. For example, the processing unit 410 may perform the steps as shown in fig. 1.
The storage unit 420 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)4201 and/or a cache memory unit 4202, and may further include a read only memory unit (ROM) 4203. The storage unit 420 may also include a program/utility 4204 having a set (at least one) of program modules 4205, such program modules 4205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The system 400 for asynchronously obtaining user attribute information from a third party platform may also communicate with one or more external devices 470 (e.g., keyboard, display, network device, bluetooth device, etc.) such that a user may interact with the processing unit 410 via these external devices 470 via an input/output (I/O) interface 450, and may also interact with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via a network adapter 460. The network adapter 460 may communicate with other modules of the microservice architecture-based route management system 400 via the bus 430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in the microservice architecture-based route management system 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
FIG. 5 is a schematic diagram of one computer-readable medium embodiment of the present invention. As shown in fig. 5, the computer program may be stored on one or more computer readable media. The computer readable medium may be a readable signal medium or a readable storage medium. A 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 (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory unit (RAM), a read-only memory unit (ROM), an erasable programmable read-only memory unit (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory unit (CD-ROM), an optical storage unit, a magnetic storage unit, or any suitable combination of the foregoing. The computer program, when executed by one or more data processing devices, enables the computer-readable medium to implement the above-described method of the invention, namely:
s1, the first server acquires basic information of the user, sends a first query request to one or more of the third-party platforms based on the basic information, and queries first attribute information of the user;
s2, synchronizing the first server and the second server, and sending the user information to the second server;
s3, the second server sends a second query request to one or more of the third-party platforms based on the obtained user information, queries the second attribute information of the user, returns the first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returns the second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request;
s4, the first server sends a third query request to one or more of the third-party platforms based on the user information, third attribute information of the user is queried, and the one or more servers return the third attribute information of the user to the first server;
and S5, synchronizing the first server with the second server again, and sending the third attribute information of the user to the second server.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments of the present invention described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a data processing device (which can be a personal computer, a server, or a network device, etc.) execute the above-mentioned method according to the present invention.
The computer readable storage medium may include a propagated data signal with 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 readable storage medium may also be any readable medium that is not a 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 readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In summary, the present invention can be implemented as a method, an apparatus, an electronic device, or a computer-readable medium executing a computer program. Some or all of the functions of the present invention may be implemented in practice using general purpose data processing equipment such as a micro-processing unit or a digital signal processing unit (DSP).
While the foregoing embodiments have described the objects, aspects and advantages of the present invention in further detail, it should be understood that the present invention is not inherently related to any particular computer, virtual machine or electronic device, and various general-purpose machines may be used to implement the present invention. The invention is not to be considered as limited to the specific embodiments thereof, but is to be understood as being modified in all respects, all changes and equivalents that come within the spirit and scope of the invention.
Claims (10)
1. A method for asynchronously obtaining user attribute information from a third-party platform is characterized by comprising the following steps:
the method comprises the steps that a first server obtains basic information of a user, sends a first query request to one or more of a plurality of third-party platforms based on the basic information, and queries first attribute information of the user;
the first server and the second server are synchronous, and the user information is sent to the second server;
the second server sends a second query request to one or more of the third-party platforms based on the acquired user information, queries second attribute information of the user, returns first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returns second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request;
the first server sends a third query request to one or more of the third-party platforms based on the user information, third attribute information of the user is queried, and the one or more servers return the third attribute information of the user to the third server;
and the first server synchronizes with the second server again, and sends the third attribute information of the user to the second server.
2. The method of claim 1, wherein the first query request and the second query request are asynchronous requests.
3. The method of any of claims 1-2, wherein the user information comprises basic information and identity information.
4. A method as claimed in any one of claims 1 to 3, wherein the basic information comprises a telephone number of the user and the identity information comprises a name and a certificate ID of the user.
5. The method of any of claims 1-4, wherein the one or more third party platforms that receive the first query request, the second query request, and the third query request are different from each other.
6. The method of any of claims 1 to 5, wherein the first server and the second server are REDIS servers.
7. The method of any of claims 1-6, wherein the one or more third party platforms that receive a first query request query the user for the first attribute information for a greater time than the one or more third platforms that receive a second query request query the user for the first attribute information.
8. A system for asynchronously obtaining user attribute information from a third party platform, the system comprising:
the first query module is used for acquiring basic information of a user through a first server, sending a first query request to one or more of a plurality of third-party platforms based on the basic information and querying first attribute information of the user;
the first synchronization module synchronizes the first server and the second server and sends the user information to the second server;
the second query module is used for sending a second query request to one or more of the third-party platforms through the second server based on the acquired user information, querying second attribute information of the user, returning first attribute information of the user to the second server by the one or more third-party platforms receiving the first query request, and returning second attribute information of the user to the second server by the one or more third-party platforms receiving the second query request;
a third query module, configured to query, by the first server, third attribute information of the user by sending a third query request to one or more of the plurality of third party platforms based on the user information, where the one or more servers return the third attribute information of the user to a third server;
and the second synchronization module is used for synchronizing the first server with the second server again and sending the third attribute information of the user to the second server.
9. A system for asynchronously obtaining user attribute information from a third party platform, comprising:
a storage unit for storing a computer executable program;
a processing unit for reading the computer executable program in the storage unit to execute the method for asynchronously acquiring user attribute information from a third party platform according to any one of claims 1 to 7.
10. A computer readable medium storing a computer readable program for performing the method for asynchronously obtaining user attribute information from a third party platform of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910915374.9A CN110782310A (en) | 2019-09-26 | 2019-09-26 | Method, device and system for asynchronously acquiring user attribute information from third-party platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910915374.9A CN110782310A (en) | 2019-09-26 | 2019-09-26 | Method, device and system for asynchronously acquiring user attribute information from third-party platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110782310A true CN110782310A (en) | 2020-02-11 |
Family
ID=69384389
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910915374.9A Pending CN110782310A (en) | 2019-09-26 | 2019-09-26 | Method, device and system for asynchronously acquiring user attribute information from third-party platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110782310A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111612548A (en) * | 2020-05-27 | 2020-09-01 | 恩亿科(北京)数据科技有限公司 | Information acquisition method and device, computer equipment and readable storage medium |
| WO2023212478A1 (en) * | 2022-04-25 | 2023-11-02 | Sora ID, Inc. | System and method for identity verification |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101087263A (en) * | 2006-06-06 | 2007-12-12 | 阿里巴巴公司 | A method and system for capturing user status information via search engine |
| US20160127374A1 (en) * | 2014-11-05 | 2016-05-05 | Craig O'Connell | Using Third Party Information To Improve Predictive Strength for Authentications |
| CN105760477A (en) * | 2016-02-15 | 2016-07-13 | 中国建设银行股份有限公司 | Data query method and system for multiple data sources and associated equipment therefore |
| WO2017054481A1 (en) * | 2015-09-29 | 2017-04-06 | 腾讯科技（深圳）有限公司 | Information verification and processing method and apparatus, and information processing system |
| CN108777717A (en) * | 2018-06-08 | 2018-11-09 | 麒麟合盛网络技术股份有限公司 | A kind of information on services querying method and server |
-
2019
- 2019-09-26 CN CN201910915374.9A patent/CN110782310A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101087263A (en) * | 2006-06-06 | 2007-12-12 | 阿里巴巴公司 | A method and system for capturing user status information via search engine |
| US20160127374A1 (en) * | 2014-11-05 | 2016-05-05 | Craig O'Connell | Using Third Party Information To Improve Predictive Strength for Authentications |
| WO2017054481A1 (en) * | 2015-09-29 | 2017-04-06 | 腾讯科技（深圳）有限公司 | Information verification and processing method and apparatus, and information processing system |
| CN105760477A (en) * | 2016-02-15 | 2016-07-13 | 中国建设银行股份有限公司 | Data query method and system for multiple data sources and associated equipment therefore |
| CN108777717A (en) * | 2018-06-08 | 2018-11-09 | 麒麟合盛网络技术股份有限公司 | A kind of information on services querying method and server |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111612548A (en) * | 2020-05-27 | 2020-09-01 | 恩亿科(北京)数据科技有限公司 | Information acquisition method and device, computer equipment and readable storage medium |
| WO2023212478A1 (en) * | 2022-04-25 | 2023-11-02 | Sora ID, Inc. | System and method for identity verification |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200218737A1 (en) | Method, system and program product for matching of transaction records | |
| CN109034988B (en) | Accounting entry generation method and device | |
| CN109194495B (en) | Server, message processing method, and computer-readable storage medium | |
| CN111427971B (en) | Business modeling method, device, system and medium for computer system | |
| CN111046237A (en) | User behavior data processing method and device, electronic equipment and readable medium | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| CN112464204A (en) | Account management method and related product | |
| CN110942392A (en) | Service data processing method, device, equipment and medium | |
| CN111242462B (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN110782310A (en) | Method, device and system for asynchronously acquiring user attribute information from third-party platform | |
| US20190130029A1 (en) | Comparing tables with semantic vectors | |
| US8832120B2 (en) | Methods and systems for analyzing weirdness of variables | |
| CN109785107B (en) | Method for flexibly configuring fund duty ratio and related products | |
| CN110704486A (en) | Data processing method, device, system, storage medium and server | |
| CN115578170A (en) | Financial batch certificate making method, device, equipment and storage medium | |
| CN108038783B (en) | Position management method, system and computer readable storage medium | |
| CN111857670A (en) | Application architecture determination method and device | |
| CN114205639B (en) | Video processing method and device, electronic equipment and storage medium | |
| KR20160070932A (en) | Method for generating virtual account number and server performing the same | |
| CN110648208B (en) | Group identification method and device and electronic equipment | |
| CN114066613A (en) | Configuration method, device, medium and electronic equipment of financial business product | |
| CN116883109A (en) | Service processing method, device, electronic equipment and computer readable medium | |
| CN111861649A (en) | Method, device, equipment and computer readable medium for processing order | |
| CN110992187A (en) | Clue information determination method, clue information determination device, clue information determination server and storage medium | |
| CN114691682A (en) | Data table generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |