Method, device and equipment for determining user risk information and readable storage medium

Abstract

The application discloses a method, device and equipment for determining user risk information and a readable storage medium. When a plurality of risk information determination requests of a plurality of operations corresponding to user behavior are acquired, a time lock corresponding to the user is acquired, and the time lock is distributed to the plurality of risk information determination requests. For a target risk information determination request distributed to the time lock, an interface is called to query user identity information and user equipment information. For other risk information determination requests, data is read from a cache. If the user identity information and the user equipment information are read from the cache within a first time period corresponding to the time lock, the user identity information and the user equipment information are returned to each operation corresponding to each risk information determination request, so that each operation determines user risk information according to the user identity information and the user equipment information. In this way, the user identity information and the user equipment information are queried only once, and the probability of platform system jamming is reduced.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a method, apparatus, device, and readable storage medium for determining user risk information. Background Technology

[0002] With the development of information technology, many platforms now support online resource application and allocation. These platforms generally require user verification. Verification involves calling the platform's API to query the user's identity and device information, and then using this information to confirm the user's risk profile. If the user accesses the platform through a third-party service, the third-party service's API must be called to query the user's device information.

[0003] Currently, API calls are typically made in real time to query user identity and device information. However, this query method becomes problematic when a user's action triggers multiple platform operations. Because these operations are independent of each other, each operation calls the API to query the user's identity and device information to confirm user risk information. This results in frequent API calls, causing platform system lag and a degraded user experience. Summary of the Invention

[0004] In view of this, the embodiments of this application provide a method, apparatus, device and readable storage medium for determining user risk information, in order to solve the problem in the prior art that when a user's behavior triggers multiple operations of the system, the interface call process is frequent, causing the platform system to lag and reducing the user experience.

[0005] According to a first aspect of this application, embodiments of this application provide a method for determining user risk information, comprising: when multiple risk information determination requests corresponding to multiple operations of user behavior are obtained, acquiring a time lock corresponding to the user and allocating the time lock to the multiple risk information determination requests; for a target risk information determination request allocated a time lock, calling an interface to query user identity information and user device information corresponding to the user, and storing the user identity information and user device information in a cache; for each other risk information determination request of the user other than the target risk information determination request, reading data from the cache; if user identity information and user device information are read from the cache within a first time period corresponding to the time lock, returning the user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines user risk information based on the user identity information and user device information.

[0006] Optionally, obtaining multiple risk information determination requests for multiple operations corresponding to user behavior includes: if multiple risk information determination requests with the same user ID are obtained within the second time period, obtaining multiple risk information determination requests for multiple operations corresponding to user behavior.

[0007] Optionally, the time lock can be assigned to multiple risk information determination requests, including: randomly assigning the time lock to any one of the risk information determination requests.

[0008] Optionally, the method for determining user risk information also includes: if the API call fails, or if user identity information and user device information are not read from the cache within the first time period corresponding to the time lock, inserting multiple risk information determination requests into the message queue.

[0009] Optionally, the method for determining user risk information further includes: batch processing multiple risk information determination requests from users in the message queue, calling the interface to query the user identity information and user device information corresponding to the user; if user identity information and user device information are found within a preset number of queries, returning user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines user risk information based on user identity information and user device information.

[0010] Optionally, the method for determining user risk information may also include: if user identity information and user device information are not found within a preset number of queries, record the abnormal information and issue an abnormal prompt.

[0011] Optionally, methods for determining user risk information may also include: deleting user identity information and user device information stored in the cache.

[0012] According to a second aspect of this application, embodiments of this application provide a device for determining user risk information, comprising: an acquisition unit, configured to acquire a time lock corresponding to the user and allocate the time lock to the multiple risk information determination requests when multiple risk information determination requests corresponding to multiple operations of a user behavior are acquired; a calling unit, configured to call an interface to query user identity information and user device information corresponding to the user for the target risk information determination request allocated the time lock, and store the user identity information and user device information in a cache; and read data from the cache for each other risk information determination request of the user other than the target risk information determination request; and a return unit, configured to return the user identity information and user device information to each operation corresponding to each risk information determination request if the user identity information and user device information are read from the cache within a first time period corresponding to the time lock, so that each operation determines user risk information based on the user identity information and user device information.

[0013] According to a third aspect of this application, an embodiment of this application provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform a method for determining user risk information as described in the first aspect or any embodiment of the first aspect.

[0014] According to a fourth aspect of this application, embodiments of this application provide a computer-readable storage medium storing computer instructions for causing a computer to perform a method for determining user risk information as described in the first aspect or any embodiment of the first aspect.

[0015] The user risk information determination method, apparatus, device, and readable storage medium provided in this application embodiment, when multiple risk information determination requests corresponding to multiple operations of user behavior are obtained, acquires a time lock corresponding to the user and allocates the time lock to multiple risk information determination requests; for the target risk information determination request allocated the time lock, calls the interface to query the user's identity information and user device information corresponding to the user, and stores the user's identity information and user device information in a cache; for each other risk information determination request of the user other than the target risk information determination request, reads data from the cache; if the user's identity information and user device information are read from the cache within the first time period corresponding to the time lock, the user's identity information and user device information are returned to each operation corresponding to each risk information determination request, so that each operation determines the user's risk information based on the user's identity information and user device information; thus, when multiple risk information requests corresponding to multiple operations of user behavior are obtained in a short period of time, the interface can be called to query the user's identity information and user device information only once, which can greatly reduce the calls to platform interfaces and / or third-party service interfaces, reduce the probability of platform system lag, and improve user experience.

[0016] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating a method for determining user risk information in an embodiment of this application;

[0018] Figure 2 This is a schematic diagram of the structure of a user risk information determination device according to an embodiment of this application;

[0019] Figure 3This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] This application provides a method for determining user risk information, used by a platform to determine user risk information, such as... Figure 1 As shown, the methods for determining user risk information include:

[0022] S101, when multiple risk information determination requests corresponding to multiple operations of user behavior are obtained, the user's corresponding time lock is obtained and the time lock is allocated to multiple risk information determination requests.

[0023] In this embodiment, an operation can refer to a functional module of the platform, such as a settlement operation referring to the platform's settlement function module. A user's action may trigger multiple functional modules of the platform to perform their functions. For example, when a user clicks the "Generate Order" button on the client, the client sends a "Generate Order" request to the platform. Upon receiving the "Generate Order" request, the platform triggers the settlement function module to generate settlement information and the discount function module to generate discount information. Before performing their functions, each functional module needs to determine the user's identity information and device information to ascertain user risk information. Therefore, each functional module initiates a risk information determination request to the platform's user risk information determination module / device, thereby obtaining multiple risk information determination requests for multiple operations corresponding to the user's action. The time at which each functional module initiates the risk information determination request is simultaneous or within a short time interval.

[0024] In some embodiments, the duration of the time lock can be preset, i.e., a first time period, such as 1 second, and a one-to-one correspondence between the time lock and the user can be established, so that each user can only have one time lock. Specifically, a one-to-one correspondence between the user ID and the time lock can be established, where the user ID can be the ID of the client used by the user. Since the user ID is unique, the time lock and the user are also unique. Specifically, when acquiring the time lock corresponding to a user, the time lock corresponding to the user ID can be acquired. Once the time lock is acquired, the countdown for the corresponding duration begins.

[0025] In some embodiments, once a time lock is acquired, since there is only one time lock, when allocating the time lock to multiple risk information determination requests, the time lock can be randomly assigned to any one of the risk information determination requests. Thus, the time lock is allocated to multiple risk information determination requests in a random manner, without considering the order or importance of the receipt times of the multiple risk information determination requests.

[0026] In some embodiments, once a time lock is acquired, since there is only one time lock, when allocating the time lock to multiple risk information determination requests, the time lock can be assigned to the risk information determination request with the earliest sending time. This takes into account the order in which multiple risk information determination requests are received.

[0027] S102, for the target risk information determination request allocated with the time lock, call the interface to query the user identity information and user device information corresponding to the user, and store the user identity information and user device information in the cache; for the user's other risk information determination requests other than the target risk information determination request, read the data from the cache.

[0028] In this embodiment, since there is only one time lock, only one risk information determination request is allocated to the time lock. The risk information determination request allocated to the time lock is the target risk information determination request.

[0029] For requests to determine target risk information, the normal business processing flow is followed. For example, if a user accesses the platform through a third-party service, the third-party service interface can be called to query the user's device information, and the platform interface can be called to query the user's identity information. User device information includes the mobile phone number. User identity information includes the user's ID card number, user name, and user login name. If a user logs into the platform through a client-side platform application (APP), the platform interface can be called to query both user device information and user identity information.

[0030] If user device information and user identity information are found, they will be stored in the cache.

[0031] In some embodiments, when storing user device information and user identity information in a cache, user device information and user identity information can be stored based on the user ID.

[0032] In this embodiment of the application, for each other risk information determination request besides the target risk information determination request, the results in the cache are continuously obtained.

[0033] In some embodiments, for other risk information determination requests, the results in the cache can be read at certain time intervals within the first time period corresponding to the time lock. For example, within the 1 second corresponding to the time lock, the results in the cache can be read every 200ms. The results in the cache can be read based on the user ID.

[0034] S103, if user identity information and user device information are read from the cache within the first time period corresponding to the time lock, then return user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation can determine user risk information based on user identity information and user device information.

[0035] In the embodiments of this application, after receiving user identity information and user device information, each operation can calculate user risk information based on a predetermined strategy.

[0036] The method for determining user risk information provided in this application involves acquiring a time lock corresponding to the user when multiple risk information determination requests for multiple operations corresponding to user behavior are received. The time lock is then allocated to the multiple risk information determination requests. For the target risk information determination request allocated the time lock, an interface is called to query the user's identity information and user device information, which are then stored in a cache. For other risk information determination requests besides the target risk information determination request, data is read from the cache. If user identity information and user device information are retrieved from the cache within the first time period corresponding to the time lock, the user identity information and user device information are returned to the corresponding operations for each risk information determination request, enabling each operation to determine user risk information based on the user identity information and user device information. Thus, when multiple risk information requests for multiple operations corresponding to user behavior are received within a short period, only one query of user identity information and user device information needs to be performed, significantly reducing calls to platform interfaces and / or third-party service interfaces, reducing the likelihood of platform system lag, and improving user experience.

[0037] In an optional embodiment, step S101, obtaining multiple risk information determination requests for multiple operations corresponding to user behavior, includes: if multiple risk information determination requests with the same user ID are obtained within the second time period, obtaining multiple risk information determination requests for multiple operations corresponding to user behavior.

[0038] In practice, since multiple risk information determination requests for multiple operations may not be sent at the same time, but are sent within a very short period of time, a second time period can be set. If multiple risk information determination requests with the same user ID are obtained within the second time period, then it is confirmed that multiple risk information determination requests for multiple operations corresponding to the user behavior have been obtained.

[0039] In this embodiment of the application, by confirming whether multiple risk information determination requests with the same user ID are obtained within the second time period, it can be confirmed whether the multiple risk information determination requests are received within a short period of time, and whether the multiple risk information determination requests are for the same user.

[0040] In an optional embodiment, the method for determining user risk information further includes: if the interface call fails, or if user identity information and user device information are not read from the cache within the first time period corresponding to the time lock, inserting multiple risk information determination requests into a message queue.

[0041] In practice, if calling a third-party service interface or calling a platform interface fails, and the user device information or user identity information cannot be found for the target risk information determination request, and the user identity information and user device information cannot be read from the cache within the first time period for other risk information determination requests, then multiple risk information determination requests can be inserted into a message queue and processed according to the order of the message queue, such as processing each risk information determination request separately.

[0042] If user identity information and user device information are not obtained within the first time period for other risk information determination requests, multiple risk information determination requests can be inserted into a message queue and processed according to the order of the message queue, such as processing each risk information determination request separately.

[0043] In this embodiment of the application, if it is determined that the call to the interface failed, or if the user identity information and user device information are not read from the cache within the first time period corresponding to the time lock, multiple risk information determination requests are inserted into the message queue. This allows multiple risk information determination requests to be processed again, avoiding the omission of multiple risk information determination requests.

[0044] In an optional embodiment, the method for determining user risk information further includes: batch processing multiple risk information determination requests from users in the message queue, and calling an interface to query the user identity information and user device information corresponding to the user; if user identity information and user device information are found within a preset threshold number of queries, returning the user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines the user risk information based on the user identity information and user device information; if user identity information and user device information are not found within the preset threshold number of queries, recording abnormal information and issuing an abnormal prompt.

[0045] In practice, when processing multiple risk information determination requests in the message queue, the user ID can be used to confirm whether the multiple requests are for the same user. If they are for the same user, the multiple risk information determination requests can be batch-processed (merged) to speed up the processing of multiple risk information determination requests. During batch processing, the normal business process continues, i.e., calling the interface to query the user's identity information and user device information. If processing fails within a preset threshold, such as 3 failures, an exception is recorded and reported.

[0046] In this embodiment of the application, by batch processing multiple risk information determination requests, the speed of multiple risk information determination requests can be accelerated. By setting a preset number threshold, the probability of obtaining multiple user identity information and user device information can be increased. By recording abnormal information and issuing abnormal prompts, the user can be promptly reminded of the cause of the abnormality.

[0047] In an optional embodiment, the method for determining user risk information further includes: deleting user identity information and user device information stored in the cache.

[0048] In practice, the user identity information and user device information stored in the cache can be deleted when the first time period is completed.

[0049] In this embodiment of the application, since user identity information and user device information may change at any time, after processing multiple risk information determination requests in the second time period, timely deletion of user identity information and user device information stored in the cache can release the cache capacity.

[0050] This application also provides a device for determining user risk information, such as... Figure 2 As shown, it includes:

[0051] The acquisition unit 21 is used to acquire the time lock corresponding to the user when multiple risk information determination requests for multiple operations corresponding to user behavior are acquired, and to allocate the time lock to multiple risk information determination requests; for details of the specific implementation, please refer to the description of step S101 of the above method embodiment, which will not be repeated here.

[0052] Calling unit 22 is used to call the interface to query the user identity information and user device information corresponding to the user for the target risk information determination request allocated to the time lock, and store the user identity information and user device information in the cache; for the user's other risk information determination requests besides the target risk information determination request, data is read from the cache; for specific implementation details, please refer to the description of step S102 of the above method embodiment, which will not be repeated here.

[0053] Return unit 23 is used to return user identity information and user device information to each operation corresponding to each risk information determination request if user identity information and user device information are read from the cache within the first time period corresponding to the time lock, so that each operation can determine user risk information based on user identity information and user device information. For detailed implementation methods, please refer to the description of step S103 in the above method embodiment, which will not be repeated here.

[0054] The user risk information determination device provided in this application embodiment, when receiving multiple risk information determination requests for multiple operations corresponding to user behavior, acquires a time lock corresponding to the user and allocates the time lock to multiple risk information determination requests. For the target risk information determination request allocated the time lock, it calls an interface to query the user's identity information and user device information corresponding to the user, and stores the user's identity information and user device information in a cache. For other risk information determination requests of the user besides the target risk information determination request, it reads data from the cache. If the user's identity information and user device information are read from the cache within the first time period corresponding to the time lock, it returns the user's identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines the user's risk information based on the user's identity information and user device information. In this way, when multiple risk information requests for multiple operations corresponding to user behavior are received in a short period of time, the interface can be called to query the user's identity information and user device information only once, which can greatly reduce the calls to platform interfaces and / or third-party service interfaces, reduce the probability of platform system lag, and improve user experience.

[0055] In some optional embodiments, the acquisition unit 21 is used to acquire multiple risk information determination requests corresponding to multiple operations of user behavior if multiple risk information determination requests with the same user ID are acquired within the second time period.

[0056] In some alternative embodiments, the acquisition unit 21 is used to randomly assign the time lock to any risk information determination request.

[0057] In some optional embodiments, if the calling unit 22 fails to call the interface, or if the returning unit 23 fails to read the user identity information and user device information from the cache within the first time period corresponding to the time lock, the returning unit 23 is used to insert multiple risk information determination requests into the message queue.

[0058] In some optional embodiments, the return unit 23 is further configured to batch process multiple risk information determination requests from users in the message queue, call the interface to query the user identity information and user device information corresponding to the user; if the user identity information and user device information are found within a preset number of times threshold, return the user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines the user risk information based on the user identity information and user device information.

[0059] In some optional embodiments, the return unit 23 is also used to record abnormal information and issue an abnormal prompt if user identity information and user device information are not found within a preset number of times threshold.

[0060] In some optional embodiments, the return unit 23 is also used to delete the user identity information and user device information stored in the cache.

[0061] According to embodiments of this application, this application also provides an electronic device and a readable storage medium.

[0062] Figure 3 A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of this application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0063] like Figure 3As shown, device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 802 or a computer program loaded from storage unit 808 into random access memory (RAM) 803. RAM 803 may also store various programs and data required for the operation of device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0064] Multiple components in device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of monitors, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0065] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the method for determining user risk information. For example, in some embodiments, the method for determining user risk information may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the method for determining user risk information described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the method for determining user risk information by any other suitable means (e.g., by means of firmware).

[0066] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0067] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0068] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0069] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0070] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0071] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0072] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application can be achieved, and this is not limited herein.

[0073] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0074] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for determining user risk information, characterized in that, include: When multiple risk information determination requests are obtained within the second time period, each with the same user ID and caused by multiple operations triggered by a single user action, a time lock uniquely corresponding to the user ID is obtained, and the time lock is allocated to the multiple risk information determination requests; wherein, the multiple operations triggered by a single user action refer to multiple logically related functional operations initiated by the user in the same interaction scenario; For a target risk information determination request assigned to the time lock, the interface is called to query the user identity information and user device information corresponding to the user ID, and the user identity information, user device information and user ID are associated and stored in the cache; for other risk information determination requests of the user other than the target risk information determination request, data is read from the cache based on the user ID; If the user identity information and user device information are read from the cache within the first time period corresponding to the time lock, the user identity information and user device information are returned to each operation corresponding to each risk information determination request, so that each operation can determine the user risk information based on the user identity information and user device information. If the API call fails, or if the user identity information and user device information are not read from the cache within the first time period corresponding to the time lock, multiple risk information determination requests will be inserted into the message queue.

2. The method for determining user risk information according to claim 1, characterized in that, The step of assigning the time lock to multiple risk information determination requests includes: The time lock is randomly assigned to any of the risk information determination requests.

3. The method for determining user risk information according to claim 1, characterized in that, Also includes: The multiple risk information determination requests of the user in the message queue are batch processed, and the interface is called to query the user identity information and user device information corresponding to the user. If the user identity information and user device information are found within a preset threshold number of queries, the user identity information and user device information are returned to each operation corresponding to each risk information determination request, so that each operation can determine the user risk information based on the user identity information and user device information.

4. The method for determining user risk information according to claim 3, characterized in that, Also includes: If the user identity information and user device information are not found within the preset number of queries, an abnormal message is recorded and an abnormal prompt is issued.

5. The method for determining user risk information according to claim 1, characterized in that, Also includes: Delete the user identity information and user device information stored in the cache.

6. A device for determining user risk information, characterized in that, include: The acquisition unit is used to acquire a time lock uniquely corresponding to the user ID when multiple risk information determination requests caused by multiple operations triggered by a single user behavior with the same user ID are acquired within the second time period, and to allocate the time lock to multiple risk information determination requests; wherein, the multiple operations triggered by a single user behavior refer to multiple logically related functional operations initiated by the user in the same interaction scenario. The calling unit is used to, for the target risk information determination request allocated to the time lock, call the interface to query the user identity information and user device information corresponding to the user ID, and store the user identity information, user device information and user ID in the cache after associating them; for the user's other risk information determination requests other than the target risk information determination request, read data from the cache based on the user ID; The return unit is configured to, if the user identity information and user device information are read from the cache within the first time period corresponding to the time lock, return the user identity information and user device information to each operation corresponding to each risk information determination request, so that each operation determines the user risk information based on the user identity information and user device information; if the interface call fails, or the user identity information and user device information are not read from the cache within the first time period corresponding to the time lock, insert multiple risk information determination requests into a message queue.

7. An electronic device, characterized in that, include: At least one processor; The at least one processor is also connected in communication with a memory, wherein the memory stores instructions that can be executed by the at least one processor to cause the at least one processor to perform the method for determining user risk information as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the method for determining user risk information as described in any one of claims 1-5.

Images