Information registration method and device, computer device, storage medium and program product

Abstract

The application relates to an information registration method and device, computer equipment, a storage medium and a program product. The method comprises the following steps: after receiving a target transaction request sent by a client, according to a target account identifier carried in the target transaction request, querying whether the target account identifier corresponds to unregistered transaction necessary information in a target data table stored locally; if the target account identifier is not found to correspond to unregistered transaction necessary information, responding to the target transaction request; wherein the content stored in the target data table is periodically updated by a target server, and the target server stores registered transaction necessary information corresponding to different account identifiers. By using the method, network delay and server performance pressure can be reduced when a large amount of user necessary information is queried.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information security, and in particular to an information registration method and device, a computer device, a storage medium and a program product. BACKGROUND

[0002] With the continuous development of the network, various application software with different application functions have emerged. Nowadays, the normal use of the functions of many application software requires necessary information of a user. When a user sends a transaction request and needs to log in, the application software needs to confirm whether the necessary information of the user is registered completely in a server storing the necessary information of the user. For example, the necessary information of a user of application software for traffic ticket purchase includes a user mobile phone number, a certificate type, a certificate number and the like. The user must register and update the necessary information to further perform other business operations and normally use the functions of the application software.

[0003] In the prior art, when a transaction request sent by a user is received, a network request is sent to a server storing necessary information of the user to query whether the necessary information of the user is registered completely.

[0004] However, if the application software has a wide audience and a large number of users, when a large number of transaction requests sent by users are simultaneously received, multiple network requests need to be sent to the server storing the necessary information of the user to query whether the necessary information of the user is registered completely, which causes problems such as network delay and increased performance pressure of a database system. Therefore, the problem of reducing network delay and server performance pressure when a large number of necessary information of users is queried needs to be solved. SUMMARY

[0005] Therefore, it is necessary to provide an information registration method, device, computer device, storage medium and program product capable of reducing network delay when a large number of necessary information of users is queried.

[0006] In a first aspect, the present application provides an information registration method. The method comprises:

[0007] After receiving a target transaction request sent by a client, whether the target transaction request carries target account identification, the target account identification is queried in a target data table stored locally to determine whether the target account identification corresponds to unregistered transaction necessary information. If no unregistered transaction necessary information corresponding to the target account identification is found, the target transaction request is responded. The content stored in the target data table is periodically updated by a target server, and the target server stores registered transaction necessary information corresponding to different account identifications.

[0008] In one of the embodiments, the method further comprises:

[0009] If it is found that the target account identifier corresponds to unregistered transaction necessary information, an information registration instruction is sent to the client to make the client register the unregistered transaction necessary information corresponding to the target account identifier and return a registration processing result; and the target transaction request is responded to based on the registration processing result.

[0010] In one of the embodiments, sending the information registration instruction to the client comprises: detecting whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold; and if the frequency at which the target server periodically updates the target data table is not lower than the preset frequency threshold, sending the information registration instruction to the client based on the query result of the target data table.

[0011] In one of the embodiments, the method further comprises:

[0012] If the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold, a query request is sent to the target server, the query request carrying the target account identifier to make the target server query whether there is unregistered transaction necessary information corresponding to the target account identifier according to the target account identifier; and the information registration instruction is sent to the client according to the query result of the target server.

[0013] In one of the embodiments, responding to the target transaction request based on the registration processing result comprises: judging whether the unregistered transaction necessary information corresponding to the target account identifier is all registered based on the registration processing result; and if the unregistered transaction necessary information corresponding to the target account identifier is all registered, responding to the target transaction request.

[0014] In one of the embodiments, the method further comprises: if the unregistered transaction necessary information corresponding to the account identifier is all registered, deleting the content corresponding to the target account identifier in the target data table.

[0015] In one of the embodiments, the method further comprises: sending the transaction necessary information registered by the client to the target server based on the registration processing result.

[0016] In a second aspect, the application further provides an information registration device. The device comprises:

[0017] A first query module is configured to, after receiving a target transaction request sent by a client, query whether there is unregistered transaction necessary information corresponding to a target account identifier carried by the target transaction request in a target data table stored locally.

[0018] The first response module is used to respond to the target transaction request if no unregistered transaction necessary information corresponding to the target account identifier is found; wherein, the content stored in the target data table is periodically updated by the target server, and the target server stores registered transaction necessary information corresponding to different account identifiers.

[0019] In one embodiment, the device further includes:

[0020] The first registration module is used to send an information registration instruction to the client if it finds that there is no registered transaction necessary information corresponding to the target account identifier, so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration processing result.

[0021] The second response module is used to respond to the target transaction request based on the registration processing result.

[0022] In one embodiment, the first registration module is specifically used to: detect whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold; if the frequency at which the target server periodically updates the target data table is not lower than the preset frequency threshold, then based on the query results of the target data table, send the information registration instruction to the client.

[0023] In one embodiment, the device further includes:

[0024] The second query module is used to send a query request to the target server if the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold. The query request carries the target account identifier so that the target server can query whether there is any unregistered transaction necessary information corresponding to the target account identifier.

[0025] The first sending module is used to send the information registration instruction to the client based on the query result of the target server.

[0026] In one embodiment, the second response module is specifically used to: determine whether all the unregistered transaction necessary information corresponding to the target account identifier has been registered based on the registration processing result; if all the unregistered transaction necessary information corresponding to the target account identifier has been registered, then respond to the target transaction request.

[0027] In one embodiment, the device further includes:

[0028] The deletion module is used to delete the content corresponding to the target account identifier in the target data table if all the unregistered transaction necessary information corresponding to the account identifier has been registered.

[0029] In one embodiment, the device further includes:

[0030] The second sending module is used to send the necessary transaction information registered by the client to the target server based on the registration processing result.

[0031] Thirdly, this application also provides a computer device, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method described in any of the first aspects above.

[0032] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in any one of the first aspects above.

[0033] Fifthly, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the method described in any one of the first aspects above.

[0034] The aforementioned information registration method, apparatus, computer equipment, storage medium, and program product, based on the target account identifier carried in the target transaction request sent by the client, query a target data table stored locally and updated periodically by the target server to see if there is any unregistered necessary transaction information corresponding to the target account identifier. If no unregistered necessary transaction information corresponding to the target account identifier is found, the system responds to the target transaction request. By querying the target data table stored locally to determine whether information registration is required, instead of querying the target server storing registration information for different accounts, the system can effectively avoid network latency and pressure on the target server when a large number of users send transaction requests, further improving the efficiency of transaction request response and reducing the time consumed in transaction request response. Attached Figure Description

[0035] Figure 1 This is a diagram illustrating the application environment of the information registration method in one embodiment;

[0036] Figure 2 This is a flowchart illustrating an information registration method in one embodiment;

[0037] Figure 3 This is a schematic diagram of the registration process in one embodiment;

[0038] Figure 4 This is a flowchart illustrating the response to a target transaction request in one embodiment;

[0039] Figure 5 This is a flowchart illustrating the process of sending an information registration instruction in one embodiment;

[0040] Figure 6 This is a flowchart illustrating the login response in one embodiment;

[0041] Figure 7 This is a structural block diagram of an information registration device in one embodiment;

[0042] Figure 8 This is a structural block diagram of the second type of information registration device in one embodiment;

[0043] Figure 9 This is a structural block diagram of a third type of information registration device in one embodiment;

[0044] Figure 10 This is a structural block diagram of the fourth type of information registration device in one embodiment;

[0045] Figure 11 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] With the continuous development of the internet, various application software with different functions have emerged. Nowadays, the normal use of many application software functions requires the user's necessary information. When most application software receives a transaction request from a user and needs to log in, it must first confirm whether the user's necessary information is completely registered in the server storing the user's necessary information. For example, in transportation ticketing application software, the user's necessary information includes the user's mobile phone number, ID type, ID number, etc. The user must register and update this necessary information before further business operations can be carried out in order to use the various functions of the application software normally.

[0048] In traditional technologies, when a transaction request is received from a user, the system primarily checks whether the user's necessary information has been registered completely by sending a network request to a server that stores the user's essential information.

[0049] However, if the application software has a wide audience and a large number of users, when it receives a large number of transaction requests from users at the same time, it needs to send multiple network requests to the server storing the necessary user information to check whether the necessary user information is registered completely. This will cause problems such as increased network latency and increased performance pressure on the database system. Therefore, it is urgent to solve the problem of reducing network latency and server performance pressure when querying a large number of users' necessary information.

[0050] The information registration method provided in this application embodiment can be applied to, for example... Figure 1 The application environment shown includes a terminal 101, a server 102, and a server 103. Server 103 periodically sends content to server 102 to update the target data table stored on server 102. Server 102 receives target transaction requests from terminal 101, queries the target data table based on the target account identifier carried in the transaction request to see if there is any corresponding unregistered transaction necessary information, and responds to the target transaction request if no unregistered transaction necessary information is found for the target account identifier. Terminal 101 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart in-vehicle devices, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. Servers 102 and 103 can be implemented using independent servers or a server cluster consisting of multiple servers.

[0051] In one embodiment, such as Figure 2 As shown, an information registration method is provided, which can be applied to... Figure 1 Taking server 102 as an example, the explanation includes the following steps:

[0052] Step 201: After receiving the target transaction request sent by the client, query the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the target transaction request.

[0053] In this process, for application software installed on the client, the account information entered by the user when using the application software serves as the target account identifier. The operation the user needs to perform in the application software is the target transaction request, such as logging in. Before allowing the user to perform the next operation on the client, the client sends the target transaction request carrying the target account identifier to the server 102. For example, when the user needs to use the functions in the application software after logging in, the client sends a login request to the server 102. Only after the server 102 returns a target transaction request response can the user proceed to the next operation. The server 102 stores a target data table. The target data table includes identifiers for unregistered transaction-essential information corresponding to different account identifiers. For example, if the target account does not have a registered contact phone number, then the identifier for this unregistered information is the contact phone number. The accounts and the identifiers for unregistered transaction-essential information are stored in the target data table. It should be noted that the transaction-essential information that users need to register varies in different application software. For example, it may include name, contact phone number, ID number, etc. When the server 102 receives a target transaction request sent by the client, it queries the locally stored target data table to see if there is any unregistered transaction-essential information corresponding to the target account identifier carried in the target transaction request.

[0054] Step 202: If no unregistered transaction necessary information is found corresponding to the target account identifier, then a response is made to the target transaction request; wherein, the content stored in the target data table is periodically updated by the target server, and the target server stores the registered transaction necessary information corresponding to different account identifiers.

[0055] If no unregistered transaction information is found corresponding to the target account identifier in the target data table, it indicates that the necessary transaction information for the user corresponding to the target account has been fully registered, and the next step can be directly performed. In this case, the target transaction request is responded to, allowing the user to proceed to the next step. The target data table stores the accounts corresponding to each registered user of the application software and identifiers of any unregistered transaction information. The content of this target data table is periodically updated by the target server, which refers to the server used to store the transaction information registered by different users of the application software. Figure 1The target server 103 stores the account identifiers corresponding to each user and the necessary transaction information registered by the user. The target server statistically analyzes the registered necessary transaction information corresponding to each account identifier, determines the unregistered necessary transaction information corresponding to different account identifiers, and periodically sends each account identifier and the corresponding unregistered necessary transaction information to the target data table, overwriting or deleting the content previously stored in the target data table, and storing the content currently sent by the target server to the target data table in the target data table, thereby updating the content in the target data table.

[0056] In the aforementioned information registration method, based on the target account identifier carried in the target transaction request sent by the client, the system queries the target data table stored locally and updated periodically by the target server to see if there is any unregistered necessary transaction information corresponding to the target account identifier. If no unregistered necessary transaction information is found for the target account identifier, the system responds to the target transaction request. By querying the target data table stored locally to determine whether information registration is required, instead of querying the target server storing registration information for different accounts, the system can effectively avoid network latency and pressure on the target server when a large number of users send transaction requests, improve the speed and stability of information query, and further improve the efficiency of transaction request response and reduce the time consumed in transaction request response.

[0057] In one embodiment, such as Figure 3 As shown, it illustrates a flowchart of a registration process provided in an embodiment of this application; the method further includes:

[0058] Step 301: If the target account identifier is found to have unregistered transaction necessary information, an information registration instruction is sent to the client so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration result.

[0059] Upon receiving a target transaction request from the client, the system queries the target data table based on the target account identifier carried in the request to see if there is any unregistered transaction-related information corresponding to that target account identifier. If unregistered transaction-related information is found, it indicates that the target account needs to register the unregistered transaction-related information to complete the transaction information before proceeding to the next step in the application software. Therefore, if unregistered transaction-related information is found, an information registration instruction is sent to the client. This information registration instruction can be used to guide the user of the target account to register the unregistered transaction-related information on the client according to the identifier of the unregistered transaction-related information, and return the registration result after registration. The registration result includes the unregistered transaction-related information supplemented and registered by the user of the target account.

[0060] Step 302: Respond to the target transaction request based on the registration processing result.

[0061] When the client returns the registration processing result, the server 102 determines whether to respond to the target transaction request based on the registration processing result.

[0062] Please refer to Figure 4 It illustrates a flowchart of a response to a target transaction request provided by an embodiment of this application; responding to the target transaction request based on the registration processing result includes:

[0063] Step 401: Based on the registration processing result, determine whether all the unregistered necessary transaction information corresponding to the target account identifier has been registered.

[0064] Step 402: If all the necessary unregistered transaction information corresponding to the target account identifier is registered, then respond to the target transaction request.

[0065] Specifically, server 102 determines whether the necessary transaction information corresponding to the target account has been completely registered based on the registration processing result returned by the client. If the returned registration processing result includes all the unregistered necessary transaction information supplemented by the client for the target account, it means that all the necessary transaction information of the target account has been obtained, and the target account can be allowed to perform the next operation in the application software, and the server responds to the target transaction request. If server 102 determines that the necessary transaction information corresponding to the target account in the registration processing result returned by the client is not complete, the server cannot respond to the target transaction request.

[0066] When a target account is found to have unregistered necessary transaction information, the client is guided to register the unregistered necessary transaction information for that target account. This improves the efficiency of registering necessary transaction information, ensures the completeness of user transaction information registration, guarantees the timeliness of target account data acquisition, and facilitates the user of the target account to perform the next step in the application software.

[0067] In one embodiment, the method further includes: if all unregistered transaction-related information corresponding to the account identifier is registered, deleting the content corresponding to the target account identifier in the target data table; and sending the transaction-related information registered by the client to the target server based on the registration processing result.

[0068] The target data table stores identifiers for different accounts and their corresponding unregistered transaction necessary information. If all unregistered transaction necessary information corresponding to an account identifier is registered, that is, if the unregistered transaction necessary information corresponding to the target account registered by the client is obtained, then the identifier of the unregistered transaction necessary information corresponding to the target account in the target data table is deleted. Furthermore, the target server stores registered transaction necessary information corresponding to different accounts. When the registration processing result of the client is obtained, the transaction necessary information corresponding to the target account included in the registration processing result is sent to the target server for storage. Based on the registration processing results, by deleting the content corresponding to the target account in the target data table, it is possible to avoid the situation where, when a transaction request is received from the target account again, even though the necessary registered transaction information has already been obtained, unregistered necessary transaction information is found again, which would prevent the target account from receiving the transaction request response and affect the user of the target account from performing the next operation on the client. This ensures timely updates to the target data table. Furthermore, based on the registration processing results, the necessary transaction information corresponding to the registered target account returned by the client is sent to the target server for storage. This ensures the accuracy and completeness of the target server's data without putting performance pressure on the target server due to queries, guarantees the timeliness of data storage on the target server, and facilitates interaction between the target server and other systems based on the stored data.

[0069] In one embodiment, such as Figure 5 The diagram illustrates a flowchart of sending an information registration instruction according to an embodiment of this application; sending the information registration instruction to the client includes:

[0070] Step 501: Detect whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold.

[0071] The frequency at which the target server periodically updates the target data table can be set by the target server's maintenance personnel based on the number of application users in different time periods. For example, in the early stages of the application's use, when the number of registered accounts is large, the frequency can be set to once a day; after the application has been used for a longer period, when the number of users tends to stabilize and the number of daily registered accounts is small, the frequency can be set to once every 5 days; the highest frequency can be set to once a day, and the lowest frequency can be set to once a month. Optionally, the maintenance personnel can update the target data table when the number of unregistered transaction necessary information counted by the target server exceeds one percent of the total transaction necessary information. A frequency threshold is preset, and this update frequency is synchronously recorded in server 102. After receiving a target transaction request and querying that the target account has corresponding unregistered transaction necessary information in the target data table, the frequency at which the target server periodically updates the target data table, as recorded in server 102, is lower than the preset frequency threshold to determine whether the content stored in the target data table has been updated in a timely manner.

[0072] Step 502: If the target server updates the target data table at a frequency not lower than the preset frequency threshold, then based on the query results of the target data table, the information registration instruction is sent to the client.

[0073] If it is detected that the target server periodically updates the target data table at a frequency not lower than the preset frequency threshold, it is determined that the content in the target data table is updated in a timely manner. Then, based on the content queried from the target data table, an information registration instruction can be sent to the client to guide the user to register the necessary transaction information that has not been registered, so as to complete the necessary transaction information of the target account.

[0074] Step 503: If the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold, a query request is sent to the target server. The query request carries the target account identifier so that the target server can query whether there is any unregistered transaction necessary information corresponding to the target account identifier.

[0075] Step 504: Based on the query results of the target server, send the information registration instruction to the client.

[0076] If the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold, it is determined that the content in the target data table may not be updated in a timely manner. The user has already supplemented the unregistered transaction information through other channels and stored it on the target server. Therefore, to determine what the truly accurate unregistered transaction information of the target account is at the current moment, a query request carrying the target account identifier is sent to the target server. This query request can be, for example, an HTTP network request. After receiving the query request, the target server checks whether the transaction information corresponding to the target account is completely registered. If it is not completely registered, the queried target account information is then sent to the target server. The query results return any unregistered transaction information corresponding to the account. This query result is more accurate than the content stored in the target data table. Based on this query result, an information registration instruction can be sent to the client, and the transaction information registered by the client based on the information registration instruction can be obtained. If the query finds that the transaction information of the target account has been fully registered, the fully registered information is returned as the query result, allowing the target account to log in directly based on the query result. At the same time, based on the query result, the identifiers of the target account and its corresponding unregistered transaction information stored in the target data table can be deleted so that the target account can directly obtain transaction request responses in the future.

[0077] By setting an update frequency, the system ensures timely and effective updates to the target data table by the target server. At the same time, by setting a frequency threshold, a query request is sent directly to the target server only when the update frequency is lower than the preset threshold. This retrieves the latest transaction information of the target account stored on the target server, ensuring the accuracy of the transaction information and saving network resources. This achieves a balance between the accuracy of transaction information confirmation and the stability of the target server's performance to the greatest extent possible.

[0078] In one embodiment, such as Figure 6 As shown, it illustrates a flowchart of a login response provided in an embodiment of this application; after receiving a login request from a target account, the login request is responded to after confirming the necessary information of the target account through the following steps; including:

[0079] Step 601: After receiving the login request sent by the client, query the target data table to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the login request.

[0080] The target data table stores the accounts of each registered user of the application software and the identifiers of any unregistered transaction necessary information. This target data table is stored locally, and its content is periodically updated by the target server. The target server stores the registered transaction necessary information corresponding to different account identifiers. By statistically analyzing the registered transaction necessary information corresponding to each account identifier, the target server determines the unregistered transaction necessary information corresponding to different account identifiers and periodically sends each account identifier and its corresponding unregistered transaction necessary information to server 102, overwriting or deleting the previously stored content in the target data table. The content currently sent by the target server to server 102 is then stored in the target data table, thus updating the content in the target data table.

[0081] Step 602: If no unregistered transaction information is found corresponding to the target account identifier, then respond to the login request.

[0082] If no unregistered transaction information is found for the target account identifier in the target data table, it means that the necessary transaction information for the user corresponding to the target account has been fully registered, and the next step can be directly performed. In this case, the login request for the target account will be responded to, allowing the user to log in and perform other operations.

[0083] Step 603: If the target account identifier is found to have unregistered transaction information, check whether the frequency of the target server periodically updating the target data table is lower than the preset frequency threshold.

[0084] The frequency at which the target server periodically updates the target data table can be set by the target server's operations and maintenance personnel according to the number of application software users in different time periods. The highest frequency can be set to once a day, and the lowest frequency can be set to once a month. Optionally, the operations and maintenance personnel can update the target data table when the number of unregistered transaction necessary information counted by the target server exceeds one percent of the total transaction necessary information.

[0085] Step 604: If the frequency at which the target server periodically updates the target data table is not lower than a preset frequency threshold, then based on the query results of the target data table, an information registration instruction is sent to the client.

[0086] If it is detected that the target server periodically updates the target data table at a frequency not lower than the preset frequency threshold, it is determined that the content in the target data table is updated in a timely manner. Then, based on the content queried from the target data table, an information registration instruction can be sent to the client to enable the client to register the necessary information for unregistered transactions corresponding to the target account identifier and return the registration result.

[0087] Step 605: If the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold, then a query request is sent to the target server.

[0088] If the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold, it is determined that the content in the target data table may not be updated in a timely manner. The user has already supplemented the level of the unregistered transaction necessary information through other channels and stored it in the target server. Therefore, in order to determine what the true and accurate unregistered transaction necessary information of the target account is at the current moment, a query request carrying the target account identifier is sent to the target server, so that the target server can query whether there is unregistered transaction necessary information corresponding to the target account identifier. The query result of the target server is obtained, which includes the identifier of the unregistered transaction necessary information corresponding to the target account at the current moment.

[0089] Step 606: Based on the query results from the target server, send an information registration instruction to the client.

[0090] Step 607: Obtain the registration processing result returned by the client; respond to the login request based on the registration processing result.

[0091] Specifically, based on the registration processing results, it is determined whether all unregistered transaction necessary information corresponding to the target account identifier has been registered. If all unregistered transaction necessary information corresponding to the target account identifier has been registered, a login request is responded to. Furthermore, if all unregistered transaction necessary information corresponding to the account identifier has been registered, the content corresponding to the target account identifier in the target data table is deleted, and the transaction necessary information registered by the client is sent to the target server based on the registration processing results.

[0092] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0093] Based on the same inventive concept, this application also provides an information registration device for implementing the information registration method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more information registration device embodiments provided below can be found in the limitations of the information registration method described above, and will not be repeated here.

[0094] In one embodiment, such as Figure 7 As shown, an information registration device is provided, including: a first query module 701 and a first response module 702, wherein:

[0095] The first query module 701 is used to, after receiving a target transaction request sent by the client, query the target account identifier carried in the target transaction request in the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier.

[0096] The first response module 702 is used to respond to the target transaction request if no unregistered transaction necessary information corresponding to the target account identifier is found; wherein, the content stored in the target data table is periodically updated by the target server, and the target server stores registered transaction necessary information corresponding to different account identifiers.

[0097] In one embodiment, such as Figure 8 As shown, a block diagram of a second information registration device provided in an embodiment of this application is illustrated. The information registration device 800 further includes:

[0098] The first registration module 703 is used to send an information registration instruction to the client if it finds that there is no registered transaction necessary information corresponding to the target account identifier, so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration processing result.

[0099] The second response module 704 is used to respond to the target transaction request based on the registration processing result.

[0100] In one embodiment, the first registration module 703 is specifically used to: detect whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold; if the frequency at which the target server periodically updates the target data table is not lower than the preset frequency threshold, then based on the query results of the target data table, send the information registration instruction to the client.

[0101] In one embodiment, such as Figure 9 As shown, a block diagram of a third information registration device provided in an embodiment of this application is illustrated. The information registration device 900 further includes:

[0102] The second query module 705 is used to send a query request to the target server if the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold. The query request carries the target account identifier so that the target server can query whether there is any unregistered transaction necessary information corresponding to the target account identifier based on the target account identifier.

[0103] The first sending module 706 is used to send the information registration instruction to the client based on the query result of the target server.

[0104] In one embodiment, the second response module 704 is specifically used to: determine, based on the registration processing result, whether all unregistered transaction necessary information corresponding to the target account identifier has been registered; if all unregistered transaction necessary information corresponding to the target account identifier has been registered, then respond to the target transaction request.

[0105] In one embodiment, such as Figure 10 As shown, a block diagram of a fourth information registration device provided in an embodiment of this application is illustrated. The information registration device 1000 further includes:

[0106] The deletion module 707 is used to delete the content corresponding to the target account identifier in the target data table if all the unregistered transaction necessary information corresponding to the account identifier has been registered.

[0107] The second sending module 708 is used to send the necessary transaction information registered by the client to the target server based on the registration processing result.

[0108] Each module in the aforementioned information registration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0109] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 11As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores information registration data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements an information registration method.

[0110] Those skilled in the art will understand that Figure 11 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0111] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0112] Upon receiving a target transaction request from the client, the system queries the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the target transaction request. If no unregistered transaction necessary information corresponding to the target account identifier is found, the system responds to the target transaction request. The content stored in the target data table is periodically updated by the target server, which stores the registered transaction necessary information corresponding to different account identifiers.

[0113] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0114] If the query finds that there is no registered transaction necessary information corresponding to the target account identifier, an information registration instruction is sent to the client so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration result; the client responds to the target transaction request based on the registration result.

[0115] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0116] Based on the registration processing result, determine whether all the unregistered transaction necessary information corresponding to the target account identifier has been registered; if all the unregistered transaction necessary information corresponding to the target account identifier has been registered, then respond to the target transaction request.

[0117] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0118] If all unregistered transaction-related information corresponding to the account identifier is registered, then the content corresponding to the target account identifier in the target data table is deleted; and based on the registration processing result, the transaction-related information registered by the client is sent to the target server.

[0119] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0120] The system checks whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold. If the frequency is not lower than the preset threshold, the system sends an information registration instruction to the client based on the query results of the target data table. If the frequency is lower than the preset threshold, the system sends a query request to the target server. This query request carries the target account identifier, enabling the target server to query whether there is any unregistered transaction information corresponding to the target account identifier. Based on the query results of the target server, the system sends the information registration instruction to the client.

[0121] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0122] Upon receiving a target transaction request from the client, the system queries the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the target transaction request. If no unregistered transaction necessary information corresponding to the target account identifier is found, the system responds to the target transaction request. The content stored in the target data table is periodically updated by the target server, which stores the registered transaction necessary information corresponding to different account identifiers.

[0123] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0124] If the query finds that there is no registered transaction necessary information corresponding to the target account identifier, an information registration instruction is sent to the client so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration result; the client responds to the target transaction request based on the registration result.

[0125] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0126] Based on the registration processing result, determine whether all the unregistered transaction necessary information corresponding to the target account identifier has been registered; if all the unregistered transaction necessary information corresponding to the target account identifier has been registered, then respond to the target transaction request.

[0127] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0128] If all unregistered transaction-related information corresponding to the account identifier is registered, then the content corresponding to the target account identifier in the target data table is deleted; and based on the registration processing result, the transaction-related information registered by the client is sent to the target server.

[0129] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0130] The system checks whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold. If the frequency is not lower than the preset threshold, the system sends an information registration instruction to the client based on the query results of the target data table. If the frequency is lower than the preset threshold, the system sends a query request to the target server. This query request carries the target account identifier, enabling the target server to query whether there is any unregistered transaction information corresponding to the target account identifier. Based on the query results of the target server, the system sends the information registration instruction to the client.

[0131] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0132] Upon receiving a target transaction request from the client, the system queries the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the target transaction request. If no unregistered transaction necessary information corresponding to the target account identifier is found, the system responds to the target transaction request. The content stored in the target data table is periodically updated by the target server, which stores the registered transaction necessary information corresponding to different account identifiers.

[0133] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0134] If the query finds that there is no registered transaction necessary information corresponding to the target account identifier, an information registration instruction is sent to the client so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration result; the client responds to the target transaction request based on the registration result.

[0135] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0136] Based on the registration processing result, determine whether all the unregistered transaction necessary information corresponding to the target account identifier has been registered; if all the unregistered transaction necessary information corresponding to the target account identifier has been registered, then respond to the target transaction request.

[0137] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0138] If all unregistered transaction-related information corresponding to the account identifier is registered, then the content corresponding to the target account identifier in the target data table is deleted; and based on the registration processing result, the transaction-related information registered by the client is sent to the target server.

[0139] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0140] The system checks whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold. If the frequency is not lower than the preset threshold, the system sends an information registration instruction to the client based on the query results of the target data table. If the frequency is lower than the preset threshold, the system sends a query request to the target server. This query request carries the target account identifier, enabling the target server to query whether there is any unregistered transaction information corresponding to the target account identifier. Based on the query results of the target server, the system sends the information registration instruction to the client.

[0141] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0142] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0143] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0144] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An information registration method, characterized in that, The method includes: After receiving the target transaction request sent by the client, the system queries the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier carried in the target transaction request. If no unregistered transaction information is found corresponding to the target account identifier, then the target transaction request will be responded to. The target data table stores information that is periodically updated by the target server. The target server stores necessary transaction information that has been registered and corresponds to different account identifiers. The frequency at which the target server periodically updates the target data table is determined based on the number of users of the application software in different time periods. If unregistered transaction information is found corresponding to the target account identifier, an information registration instruction is sent to the client, so that the client can register the unregistered transaction information corresponding to the target account identifier and return the registration result; and respond to the target transaction request based on the registration result. Sending the information registration instruction to the client includes: detecting whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold; if the frequency at which the target server periodically updates the target data table is not lower than the preset frequency threshold, then sending the information registration instruction to the client based on the query results of the target data table; If the target server updates the target data table at a frequency lower than the preset frequency threshold, a query request is sent to the target server. The query request carries the target account identifier so that the target server can query whether there is any unregistered transaction information corresponding to the target account identifier. Based on the query result of the target server, the information registration instruction is sent to the client.

2. The method according to claim 1, characterized in that, The step of responding to the target transaction request based on the registration processing result includes: Based on the registration processing results, it is determined whether all the necessary unregistered transaction information corresponding to the target account identifier has been registered; If all the necessary unregistered transaction information corresponding to the target account identifier is registered, then the target transaction request is responded to.

3. The method according to claim 2, characterized in that, The method further includes: If all the necessary transaction information that was not registered for the account identifier is registered, then the content corresponding to the target account identifier in the target data table is deleted.

4. The method according to claim 2, characterized in that, The method further includes: Based on the registration processing result, the necessary transaction information registered by the client is sent to the target server.

5. An information registration device, characterized in that, The device includes: The first query module is used to, after receiving a target transaction request sent by the client, query the target account identifier carried in the target transaction request in the target data table stored locally to see if there is any unregistered transaction necessary information corresponding to the target account identifier. The first response module is used to respond to the target transaction request if no unregistered transaction necessary information is found corresponding to the target account identifier. The target data table stores information that is periodically updated by the target server. The target server stores necessary transaction information that has been registered and corresponds to different account identifiers. The frequency at which the target server periodically updates the target data table is determined based on the number of users of the application software in different time periods. The first registration module is used to send an information registration instruction to the client if unregistered transaction necessary information is found corresponding to the target account identifier, so that the client can register the unregistered transaction necessary information corresponding to the target account identifier and return the registration processing result; the second response module is used to respond to the target transaction request based on the registration processing result; The first registration module is further configured to detect whether the frequency at which the target server periodically updates the target data table is lower than a preset frequency threshold; if the frequency at which the target server periodically updates the target data table is not lower than the preset frequency threshold, then based on the query results of the target data table, the information registration instruction is sent to the client. The second query module is used to send a query request to the target server if the frequency at which the target server periodically updates the target data table is lower than the preset frequency threshold. The query request carries the target account identifier so that the target server can query whether there is any unregistered transaction necessary information corresponding to the target account identifier. The first sending module is used to send the information registration instruction to the client based on the query result of the target server.

6. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Images