A method and system for detecting user input

Abstract

This invention discloses a method and system for detecting user data entry. A first server, responding to a user data entry request input by a staff member on a user terminal, obtains the addresses of several user lists from a file management system. Each user list contains user data for at least several users. A database server generates a user list queue based on the addresses of the user lists, according to preset rules. This queue contains several user data entry tasks. A task allocation module distributes these tasks from the queue to several service nodes. The service nodes then input the user data from the user lists corresponding to the tasks into the user database. By sending user data to multiple service nodes in units of user lists, the system reduces the possibility of system overload and the likelihood of system lag.

Description

Technical Field

[0001] This invention relates to the field of information management technology, and in particular to a method and system for detecting user input. Background Technology

[0002] In medical testing, testing systems typically store a large amount of user data for use in generating test reports based on this pre-stored user data and test data. When there are numerous requests for test reports, it is necessary to enter the user data of the test users into the testing system so that the user data can be quickly retrieved from the system's user database when generating test reports.

[0003] The current method for inputting user data for testing involves responding to user requests by reading each request containing user data, judging each piece of user information according to preset conditions, and then inputting the qualified user information into the user database of the testing system. The existing technical solution has a slow data entry speed, and when faced with a large number of user input requests, the number of requests is high, which can easily cause the testing system to be overloaded and lag. Summary of the Invention

[0004] This invention provides a method and system for detecting user input, in order to reduce the possibility of system overload and the probability of system lag.

[0005] According to one aspect of the present invention, a method for detecting user input is provided, comprising:

[0006] In response to the user input request entered by the staff on the user terminal, the first server obtains the addresses of several user lists in the file management system, wherein each user list includes user data of at least several user groups.

[0007] The database server generates a queue of detection user lists based on the addresses of the detection user list according to preset rules, wherein the detection user list queue contains several detection user entry tasks.

[0008] The task allocation module distributes the task of entering a number of the detected users from the detected user list queue to a number of service nodes;

[0009] The service node enters the user data from the list of users corresponding to the user entry task into the user entry database.

[0010] According to another aspect of the present invention, a user input detection device is provided, comprising:

[0011] The system comprises a first server, a database server, a file management system, a task allocation module, and several service nodes.

[0012] The first server is connected to the database server and the file management system respectively. The first server is used to respond to the user input request entered by the staff on the user terminal and obtain the address of several user lists in the file management system. Each user list includes user data of at least several users.

[0013] The database server is connected to the file management system and the task allocation module respectively. The database server is used to generate a detection user list queue according to preset rules based on the address of the detection user list. The detection user list queue contains several detection user input tasks.

[0014] The file management system is used to store the list of detection users;

[0015] The task allocation module is connected to several service nodes, and the task allocation module is used to distribute several detection user entry tasks from the detection user list queue to several service nodes.

[0016] The service node is used to input the user data from the list of users corresponding to the user input task into the user input database.

[0017] The technical solution of this invention involves a first server responding to a user input request from a staff member on a user terminal, obtaining addresses of several user lists from a file management system. Each user list contains user data for at least several users. A database server generates a user list queue based on the addresses of the user lists, according to preset rules. This queue contains several user input tasks. A task allocation module distributes these user input tasks from the queue to several service nodes. The service nodes input the user data from the user lists corresponding to the user input tasks into the user database. When the detection system has a large amount of user data waiting to be input into its user database, the addresses of multiple user data sets are grouped into a single user list, which is then sent to multiple service nodes for user input. This allows for batch processing of user data and simultaneous input across multiple service nodes, eliminating the need for multiple requests to the file management system, reducing the possibility of system overload, and minimizing system lag.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1A This is a flowchart of a user input detection method provided according to Embodiment 1 of the present invention;

[0021] Figure 1B This is a flowchart of a user input detection method applicable to Embodiment 1 of the present invention;

[0022] Figure 2 This is a schematic diagram of a user input detection system provided according to Embodiment 2 of the present invention. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] Example 1

[0026] Figure 1AThis invention provides a flowchart of a user input detection method according to Embodiment 1. This embodiment is applicable to situations where the detection system may be overloaded or experience system lag. The method can be executed by a user input detection system, which can be implemented in hardware and / or software and can be configured in a service cluster. Figure 1A As shown, the method includes:

[0027] S101. The first server responds to the user input request entered by the staff on the user terminal and obtains the addresses of several user lists from the file management system.

[0028] Each list of users to be tested includes user data for at least a number of users. For example, user data may include users' names, ages, dates of birth, etc. For example, the list of users to be tested may be in the form of an Excel spreadsheet.

[0029] For example, during the detection process, multiple regions will upload the integrated list of detection users separately. User data from the same region will be automatically integrated into the same list of detection users, resulting in multiple lists of detection users generated from multiple regions.

[0030] It should be noted that the application scenarios and specific generation methods of each detection user list in the embodiments of the present invention are exemplary descriptions of the embodiments of the present invention. The embodiments of the present invention are only examples and are not intended to limit the scope.

[0031] The first server is connected to the user terminal, the file management system, and the database server. When a staff member enters a user entry request in the user terminal, the first server receives the user entry request from the staff member and sends a request to the file management system to obtain the addresses of several user lists stored in the file management system for subsequent allocation of user list entry tasks.

[0032] For example, the user input request entered by the staff on the user terminal can be by clicking the corresponding "User Input" or "Report Generation" button, which generates the corresponding user input request and sends it to the first server. The first server retrieves several EXCEL tables containing user data of multiple users from the file management system and obtains the address of each user list in the file management system.

[0033] It should be noted that the EXCEL spreadsheet used in the embodiments of the present invention is an exemplary illustration of the embodiments of the present invention. In some embodiments of the present invention, the user list may also be multiple string groups. The embodiments of the present invention are only examples and are not intended to limit the scope.

[0034] Figure 1B This is a flowchart of a user input detection method applicable to Embodiment 1 of the present invention, as shown below. Figure 1B As shown, in some embodiments of the present invention, S101 includes:

[0035] S1011. The first server responds to the staff's request to enter the testing users and obtains the URL address of the testing user list from the file management system.

[0036] Every information resource on the World Wide Web has a unique address on the network, called a URL (Uniform Resource Locator). It is a Uniform Resource Locator in the World Wide Web, which is also a network address.

[0037] In the document management system, each list of users to be tested has a corresponding URL address. In response to the user's request for testing on the user's end, the first server obtains the URL address of the list of users who have not been entered into the document management system.

[0038] It should be noted that obtaining the URLs corresponding to several lists of detected users in the file management system is an exemplary description of this invention. In other embodiments of this invention, several URLs of the list of detected users can also be obtained according to the nature of the file management system.

[0039] S1012. The first server extracts the URL address to obtain the ID address corresponding to the list of detected users.

[0040] The first server will include the IDs (unique encoded addresses) of the users in the list of those to be tested in the URL address.

[0041] The corresponding ID address of the detected user list can be extracted from the URL address to determine the specific ID address of the detected user list, that is, to determine the specific location of the detected user list in the file management system.

[0042] The example provided in this embodiment of the invention, in which the first server extracts the URL address to obtain the ID address corresponding to the list of detected users, is merely an example and not a limitation.

[0043] S102. The database server generates a queue of detected user lists based on the addresses of the detected user lists according to preset rules.

[0044] The database server generates a queue of detection user lists according to the addresses of the obtained detection user list and in accordance with pre-set rules. The detection user list queue contains several detection user entry tasks.

[0045] For example, the database server encapsulates the corresponding ID address and file parameters of a certain list of detection users to obtain the detection user entry task for that list, and generates a detection user list queue by uploading multiple detection user entry tasks to the file management system in ascending order.

[0046] It should be noted that the specific content included in the user input task and the rules for generating the user list queue in the embodiments of the present invention are only examples and are not limited. In other embodiments of the present invention, the specific content included in the user input task and the specific rules for generating the user list queue can be other content.

[0047] S103, The task allocation module distributes several user entry tasks from the user list queue to several service nodes.

[0048] The task allocation module retrieves the detection user list queue from the database server and distributes several detection user entry tasks from the detection user list queue to multiple service nodes in the detection user entry system according to pre-set rules, so as to complete multiple detection user entry tasks.

[0049] It should be noted that the embodiments of the present invention do not limit how several user input tasks are distributed to several service nodes.

[0050] In some embodiments of the present invention, S103 includes:

[0051] S1031. The task allocation module sequentially determines whether the service node is in an idle state; if the service node is in an idle state, then execute S1032; if the service node is not in an idle state, then return to execute S1031.

[0052] S1032, The task allocation module enters the detection user at the head of the detection user list queue into the task and sends it to the service node.

[0053] The service node has two states: when the service node is processing user input detection, the service node's state is set to working state; when the service node is not currently detecting user input tasks, the service node's state is set to idle state.

[0054] The task allocation module polls multiple service nodes in turn to determine whether each service node is idle. When the polling finds that a service node is idle, it executes S1032 to send the user entry task corresponding to the head of the current user list queue to that service node so that the service node can complete the user entry task and remove the user entry task from the user list queue. Then, it continues to execute S1031 to continue polling to allocate tasks. When the polling finds that a service node is not in a working state, it returns to S1031 to continue polling to determine whether the next service node is idle.

[0055] It should be noted that the specific method of distributing the detection user entry tasks from the detection user list queue to several service nodes in this embodiment of the invention is an exemplary description. In other embodiments of the invention, there may be other methods of distributing detection user entry tasks. This embodiment of the invention is only an example and is not intended to limit the scope.

[0056] S104. The service node enters the user data from the list of users corresponding to the user input task into the user database.

[0057] After receiving the user data entry task, each service node enters the specific user data from the user list corresponding to the task in the file management system into the user database to update the user data in the user database.

[0058] For example, during the detection process, the service node enters the user data from the user list in the user entry task into the user database to expand the user database and also enters the user data of users who have never been detected in the detection system before into the user database.

[0059] Multiple service nodes simultaneously input user data from the user detection list into the user detection database. Furthermore, since the user detection list contains user data for multiple users, the service nodes can perform batch input operations for user detection. This reduces the number of requests to the file management system, and the simultaneous processing by multiple service nodes can reduce system load, prevent system lag, and improve the efficiency of user detection input.

[0060] It should be noted that the embodiments of the present invention do not limit the specific implementation method of the service node entering the user data in the detection user list corresponding to the detection user entry task into the detection user database.

[0061] In some embodiments of the present invention, S104 includes:

[0062] S1041, Service node extracts and detects the address in the user input task.

[0063] When a service node receives a user entry detection task, it extracts the address from the user entry detection task. For example, the address in the user entry detection task is the ID address of the user entry list in the file management system. The extracted address is used by the service node to retrieve the user entry list corresponding to that address from the file management system.

[0064] It should be noted that the address extracted by the service node in the user input task detection in this embodiment of the invention is an exemplary illustration. In other embodiments of the invention, the address in the user input task detection may be in other forms depending on the actual situation. This embodiment of the invention is only an example and is not intended to limit the scope.

[0065] S1042. The service node obtains the list of detection users corresponding to the address in the file management system.

[0066] The service node retrieves the list of users corresponding to the address from the file management system based on the address extracted in the user entry task, so that the user data in the list can be entered into the user database later.

[0067] The embodiments of the present invention provide only examples of how service nodes obtain the list of detection users corresponding to addresses in the file management system, and are not intended to limit the scope of the invention.

[0068] S1043. The service node sequentially checks whether the user data in the user list meets the preset user data standard; if the user data in the user list meets the preset user data standard, then execute S1044; if the user data in the user list does not meet the preset user data standard, then execute S1045.

[0069] S1044. The service node enters the user data into the detection user database and returns to the execution service node to determine whether the user data in the detection user list meets the preset user data standards.

[0070] S1045, The service node sends the first entry failure prompt to the first server, and returns to the execution service node to judge whether the user data in the user list meets the preset user data standard.

[0071] The user data in the user list obtained from the file management system is filled in by the users during the testing process. Therefore, errors, omissions, or misplacement may occur during the filling process. Consequently, the user data in the user list may contain errors. Therefore, before entering the user data into the user database, it is necessary to check whether each piece of user data in the user list meets the pre-set user data standards. When a piece of user data meets the standards, the service node S1044 adds the user data to the user database and continues to check whether the next piece of user data in the user list meets the pre-set user data standards. If a piece of user data does not meet the pre-set user data standards, it means that the user data cannot be entered into the user database. The service node S1045 sends a first entry failure message to the first server to inform the first server that the user data cannot be entered into the system and continues to check whether the next piece of user data in the user list meets the pre-set user data standards.

[0072] For example, user data standards can be used to determine whether the content type of a certain item in the user data is a preset type, and to determine whether a certain item in the user data exceeds a preset character length. Specifically, this includes determining whether the name item in the user data is character data within a preset length range, and determining whether the age item in the user data is numeric data with two digits.

[0073] It should be noted that the user data standard preset in the embodiments of the present invention is an exemplary description of the embodiments of the present invention. In other embodiments of the present invention, other user data standards may also be used. The present invention is only for example and is not intended to limit.

[0074] In some embodiments of the present invention, S1044 includes:

[0075] S441, The service node extracts several key user data from the user data.

[0076] Key user data refers to the specific user data related to the user being tested that needs to be stored in the user database.

[0077] The service node extracts key user data from user data that meets the preset user data standards, so that it can be subsequently entered into the detection user database.

[0078] For example, the service node extracts key user data such as the user's name, age, ID number, and region from the user data. The ID number in the user information is obtained by the user entry system with the user's informed consent.

[0079] It should be noted that the specific key user data in the embodiments of the present invention are illustrative examples, and the key user data in the embodiments of the present invention are only examples and are not limited thereto.

[0080] Because some user data in the detected user list is missing, but some key user data can be deduced from other key user data, in some embodiments of the present invention, when some data is missing, S441 includes:

[0081] S4411, The service node extracts the first key user data from the preset location of the user data.

[0082] The first key user data is the second key user data that can be calculated from the user data.

[0083] The service node extracts the first key user data from a preset position in the user data. For example, the service node extracts the first key user data from the corresponding column of a pre-set column in the user data row of a certain detected user in the EXCEL table of detected user list.

[0084] For example, the service node extracts the data in the column corresponding to the "ID number" from the user data row of a certain user in the EXCEL table of detected users, and uses it as the first key user data.

[0085] It should be noted that the specific method of extracting the first key user data from the preset location of user data in this embodiment of the invention is an exemplary description of this embodiment of the invention. This embodiment of the invention is only an example and is not intended to limit the scope of the invention.

[0086] S4412, The service node calculates the second key user data based on the first key user data.

[0087] Since the second key user data can be obtained by calculation or conversion from the first key user data, the service node calculates the second key user data according to certain calculation rules after extracting the first key user data.

[0088] For example, the year value corresponding to the birth year is extracted from the first key user data of "ID number", and the year value corresponding to the birth year is subtracted from the current year to obtain the second key user data of the user's "age", thereby completing the missing second key user data of age for the detected user.

[0089] It should be noted that the first key user data and the second key user data mentioned in the embodiments of the present invention are exemplary illustrations of the embodiments of the present invention. The embodiments of the present invention are only examples and are not intended to limit the scope of the invention.

[0090] S442. The service node compares the critical user data with the critical user data pre-stored in the detection user database; if the detection user database already contains critical user data, then execute S443; if the detection user database does not contain critical user data, then execute S444.

[0091] S443, The service node sends an existing notification to the first server.

[0092] S444, The service node enters key user data into the detection user database.

[0093] Some of the users on the detection user list may have previously conducted detection in this system. Therefore, the user information of some of the users on the detection user list has already been stored in the detection user database. So, there is no need to store the user information of these users in the detection user database again. It is only necessary to store the key user data corresponding to the detection users that have not been stored in the detection user database into the detection user database to improve the detection user database and avoid storing the user data of the same detection user multiple times, which would waste the resources of the detection user database.

[0094] The service node compares the key user data corresponding to a user with the key user data pre-stored in the detection user database to determine whether the key user data of the user being detected exists in the detection user database. If the key user data of the user being detected is already contained in the detection user database, it means that there is no need to enter the key user data of the user being detected again. Execute S443, and the service node sends a notification to the server that the key user data of the user being detected already exists in the detection user database. If the comparison shows that the key user data of the user being detected does not exist in the detection user database, execute S444, and enter the key user data of the user being detected into the detection user database.

[0095] It should be noted that the embodiments of the present invention do not limit the specific content and form of the existing prompt sent by the service node.

[0096] In some embodiments of the present invention, S444 includes:

[0097] S4441. The service node monitors whether the service node has successfully entered the key user data into the detection user database. If the service node monitors whether the service node has successfully entered the key user data into the detection user database, then execute S4442. If the service node monitors whether the service node has failed to enter the key user data into the detection user database, then execute S4443.

[0098] S4442, The service node sends a success message to the first server.

[0099] S4443, The service node sends an input failure message and the specific failure type to the first server.

[0100] When a service node enters key user data, it needs to continuously monitor whether it has successfully stored all key user data of a certain user in the user database. When it is detected that the key user data of the user has been entered into the user database, S4442 is executed, and the service node sends a success message to the first server, informing the first server that all key user data of the current user has been entered. When the service node detects that it has not entered all key user data of the user into the user database, S4443 is executed, and a failure message and the specific failure type are sent to the first server. For example, if a certain key user data of a certain user cannot be uploaded to the user database due to a network connection failure, after the service node detects the key data entry failure, it generates an entry failure message, which includes the specific location of the key data and the network connection failure message, and sends it to the first server.

[0101] The technical solution of this invention involves a first server responding to a user input request from a staff member on a user terminal, obtaining addresses of several user lists from a file management system. Each user list contains user data for at least several users. A database server generates a user list queue based on the addresses of the user lists, according to preset rules. This queue contains several user input tasks. A task allocation module distributes these user input tasks from the queue to several service nodes. The service nodes input the user data from the user lists corresponding to the user input tasks into the user database. When the detection system has a large amount of user data waiting to be input into its user database, the addresses of multiple user data sets are grouped into a single user list, which is then sent to multiple service nodes for user input. This allows for batch processing of user data and simultaneous input across multiple service nodes, eliminating the need for multiple requests to the file management system, reducing the possibility of system overload, and minimizing system lag.

[0102] Example 2

[0103] Figure 2 A schematic diagram of a user input detection system provided in Embodiment 2 of the present invention is shown. Figure 2 As shown, the system includes: a first server 201, a database server 202, a file management system 203, a task allocation module 204, and several service nodes 205.

[0104] The first server 201 is connected to the database server 202 and the file management system 203 respectively. The first server 201 is used to respond to the user input request entered by the staff on the user terminal and obtain the address of several user lists in the file management system 203. Each user list includes user data of at least several users.

[0105] Optionally, the first server 201 includes:

[0106] The URL address acquisition module is used to retrieve the URL address of the list of inspection users from the file management system 203 in response to the staff's request for inspection user entry.

[0107] The address extraction module is used to extract the URL address into the ID address corresponding to the list of detected users.

[0108] The database server 202 is connected to the file management system 203 and the task allocation module 204 respectively. The database server 202 is used to generate a detection user list queue according to preset rules based on the address of the detection user list. The detection user list queue contains several detection user input tasks.

[0109] The file management system 203 is used to store the list of detection users;

[0110] The task allocation module 204 is connected to several service nodes 205. The task allocation module 204 is used to distribute several detection user entry tasks in the detection user list queue to several service nodes 205.

[0111] Optionally, the task assignment module 204 includes:

[0112] The idle state determination submodule is used to sequentially determine whether the service node 205 is in an idle state.

[0113] The task distribution submodule is used to input the detection user at the head of the detection user list queue into a task and distribute it to the service node 205;

[0114] The idle judgment submodule is returned to the task allocation module 204 to determine whether the service node 205 is in an idle state.

[0115] Service node 205 is used to input the user data in the list of detection users corresponding to the detection user input task into the detection user database.

[0116] Optionally, service node 205 includes: an address extraction module, a list acquisition module, a user data standard judgment module, a user data entry module, and a first entry failure prompt module;

[0117] The address extraction module is connected to the first server 201 and is used to extract the address from the user input task.

[0118] The list acquisition module is connected to the file management system 203 and is used to acquire the list of detected users corresponding to the address in the file management system 203.

[0119] The user data standard judgment module is connected to the list acquisition module, the user data entry module, and the first entry failure prompt module, respectively, and is used to sequentially judge whether the user data in the detected user list meets the preset user data standard.

[0120] The user data entry module is used to enter user data into the detection user database and return to the execution of the service node 205 to determine whether the user data in the detection user list meets the preset user data standards.

[0121] The first input failure prompt module is used to send the first input failure prompt to the first server 201, and return to the execution of the service node 205 to determine whether the user data in the detection user list meets the preset user data standard.

[0122] Optionally, the user data entry module includes: a key user data extraction submodule, a key user data comparison submodule, an existing data prompt sending submodule, and a key user data entry submodule;

[0123] The key user data extraction submodule is connected to the user data standard judgment module and is used to extract several key user data from the user data.

[0124] Optional, the key user data extraction submodule includes:

[0125] The first key user data extraction unit is used to extract the first key user data from the preset location of the user data.

[0126] The second key user data calculation unit is used to calculate the second key user data based on the first key user data.

[0127] The key user data comparison submodule is connected to the key user data extraction submodule, the existing prompt sending submodule, and the key user data entry submodule, respectively, and is used to compare the key user data with the key user data pre-stored in the detection user database;

[0128] The "Already Existing Prompt Sending Submodule" is used to send an "Already Existing Prompt" to the first server 201;

[0129] The key user data entry submodule is used to enter the key user data into the detection user database.

[0130] The user input detection system provided in this embodiment of the invention can execute the user input detection method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0131] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

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

Claims

1. A method for detecting user input, characterized in that, include: In response to the user input request entered by the staff on the user terminal, the first server obtains the addresses of several user lists in the file management system, wherein each user list includes user data of at least several user groups. The database server generates a queue of detection user lists based on the addresses of the detection user list according to preset rules, wherein the detection user list queue contains several detection user entry tasks. The task allocation module distributes the task of entering a number of the detected users from the detected user list queue to a number of service nodes; The service node enters the user data from the list of detection users corresponding to the detection user entry task into the detection user database, including: The service node extracts several key user data from the user data. The service node compares the key user data with the key user data pre-stored in the detection user database; If the key user data is already contained in the user database, the service node sends an existence notification to the first server. If the key user data is not contained in the detection user database, the service node will enter the key user data into the detection user database.

2. The method according to claim 1, characterized in that, In response to a user input request submitted by a staff member on the user terminal, the first server retrieves the addresses of several user lists from the file management system, including: The first server responds to the staff's request to enter the testing users and retrieves the URL address of the testing user list from the file management system; The first server extracts the URL address into the ID address corresponding to the list of detected users.

3. The method according to claim 1, characterized in that, The task allocation module distributes several user entry tasks from the user list queue to several service nodes, including: The task allocation module sequentially determines whether the service node is in an idle state; If the service node is idle, the task allocation module will send the detection user at the head of the detection user list queue to the service node in the task entry. If the service node is not in an idle state, then return to the task allocation module to determine whether the service node is in an idle state.

4. The method according to any one of claims 1-3, characterized in that, The service node enters the user data from the list of detection users corresponding to the detection user entry task into the detection user database, including: The service node extracts the address from the user input task. The service node obtains the list of detection users corresponding to the address from the file management system; The service nodes sequentially determine whether the user data in the detected user list meets the preset user data standards. If the user data in the detected user list meets the preset user data standard, the service node will enter the user data into the detected user database and return to execute the service node to determine whether the user data in the detected user list meets the preset user data standard. If the user data in the detected user list does not meet the preset user data standard, the service node sends a first input failure prompt to the first server and returns to execute the service node to determine whether the user data in the detected user list meets the preset user data standard.

5. The method according to claim 1, characterized in that, The service node inputs the key user data into the detection user database, including: The service node monitors whether it has successfully entered the key user data into the detection user database. If the service node detects that the key user data has been successfully entered into the detection user database, the service node sends a success message to the first server. If the service node detects that it has failed to successfully input the key user data into the detection user database, the service node sends an input failure prompt and the specific failure type to the first server.

6. The method according to claim 1, characterized in that, The service node extracts several key user data from the user data, including: The service node extracts the first key user data from the preset location of the user data. The service node calculates the second key user data based on the first key user data.

7. A user input detection system, characterized in that, The user input detection system, used to perform the method according to any one of claims 1-6, comprises: a first server, a database server, a file management system, a task allocation module, and several service nodes. The first server is connected to the database server and the file management system respectively. The first server is used to respond to the user input request entered by the staff on the user terminal and obtain the address of several user lists in the file management system. Each user list includes user data of at least several users. The database server is connected to the file management system and the task allocation module respectively. The database server is used to generate a detection user list queue according to preset rules based on the address of the detection user list. The detection user list queue contains several detection user input tasks. The file management system is used to store the list of detection users; The task allocation module is connected to several service nodes, and the task allocation module is used to distribute several detection user entry tasks from the detection user list queue to several service nodes. The service node is used to input the user data from the list of users corresponding to the user input task into the user input database.

8. The system according to claim 7, characterized in that, The service node includes: an address extraction module, a list acquisition module, a user data standard judgment module, a list acquisition module, a user data entry module, and a first entry failure prompt module; The address extraction module is connected to the first server and is used to extract the address from the user input task. The list acquisition module is connected to the file management system and is used to acquire the list of detection users corresponding to the address in the file management system. The user data standard judgment module is connected to the list acquisition module, the user data input module, and the first input failure prompt module respectively, and is used to sequentially judge whether the user data in the detected user list meets the preset user data standard. The user data entry module is used to enter the user data into the detection user database and return to the execution of the service node to determine whether the user data in the detection user list meets the preset user data standards. The first input failure prompt module is used to send the first input failure prompt to the first server and return to the execution of the service node to determine whether the user data in the detection user list meets the preset user data standard.

9. The system according to claim 8, characterized in that, The user data entry module includes: a key user data extraction submodule, a key user data comparison submodule, an existing user data prompt sending submodule, and a key user data entry submodule; The key user data extraction submodule is connected to the user data standard judgment module and is used to extract several key user data from the user data. The key user data comparison submodule is connected to the key user data extraction submodule, the existing prompt sending submodule, and the key user data input submodule, respectively, and is used to compare the key user data with the key user data pre-stored in the detection user database; The existing prompt sending submodule is used to send an existing prompt to the first server; The key user data entry submodule is used to enter the key user data into the detection user database.

Images