A method, device and electronic device for intelligent interaction of account data

Abstract

The embodiments of this specification disclose an intelligent interaction method, device and electronic device for account data. The method includes determining the first task of the target user, locking the first account data in the virtual account; when the current moment reaches the preset interaction moment, calling the target task, and processing the target tasks in sequence based on the current account data; when the second account data cannot process the current target task, determining the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and processing the current target task. The entire process of the embodiments of this specification does not require the user to operate personally, and the task processing efficiency is higher, avoiding the contract overdue caused by the user forgetting.

Description

Technical Field

[0001] One or more embodiments of the present specification relate to data processing technology, and more particularly, to a method, device, and electronic device for intelligent interaction of account data. Background Art

[0002] With the development of the Internet, users can sign terms, treaties, contracts, etc. with the platform on various platforms, and then obtain actual materials or virtual assets from the platform in advance, and then pay for the actual materials or virtual assets obtained on the contract performance date. Since users may have multiple accounts on different platforms, and the balance of each account is different, if users sign many contracts at the same time, they may need to frequently switch accounts according to the balance of each account and / or the account required by the contract, and manually perform payment operations. The whole process is very cumbersome and time-consuming, and it is easy for users to forget the contract performance date and cause the contract to expire. Summary of the invention

[0003] In order to solve the above problems, one or more embodiments of this specification describe a method, device and electronic device for intelligent interaction of account data.

[0004] According to a first aspect, a method for intelligent interaction of account data is provided, the method comprising:

[0005] Determine all unprocessed first tasks of the target user in the current time period, and lock first account data in the virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is the sum of each to-be-interacted data corresponding to each first task, and the task priorities corresponding to tasks of different task types are different;

[0006] When the current moment reaches the preset interaction moment, the target tasks are retrieved in order from the task list of the day in order, and the target tasks are processed in order based on the current account data in the virtual account, the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data;

[0007] When the second account data cannot process the current target task, determine the current task priority corresponding to the current target task, and determine the first associated user account corresponding to the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, and the second preset priority is less than the first preset priority.

[0008] Preferably, the processing of the target tasks in sequence based on the current account data in the virtual account includes:

[0009] When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed;

[0010] When the target task is the second task, the target task is processed based on the second account data.

[0011] Preferably, the task processing flow of determining the current target task based on the priority comparison result and the authorization status of the first account includes:

[0012] Comparing the current task priority with the second preset priority to generate a priority comparison result, the priority comparison result comprising a first comparison result indicating that the current task priority is greater than the second preset priority and a second comparison result indicating that the current task priority is not greater than the second preset priority;

[0013] querying a first account authorization status of the first associated user account, where the first account authorization status includes a first authorization status indicating a successful authorization and a second authorization status indicating a failed authorization;

[0014] When the priority comparison result is a first comparison result and the first account authorization status is a first authorization status, determining that the task processing flow of the current target task is a first processing flow, wherein the first processing flow is a flow for processing the current target task based on the account data of the first associated user account;

[0015] When the priority comparison result is the first comparison result and the first account authorization status is the second authorization status, determining that the task processing flow of the current target task is the second processing flow, the second processing flow is a flow for processing the current target task based on the account data of the second associated user account, and the second associated user account is a user account of the target user on other account platforms that is associated with the first associated user account;

[0016] When the priority comparison result is the second comparison result, the task processing flow of the current target task is determined to be the third processing flow, and the third processing flow is a process that records the data to be interacted of the current target task in the record data based on the task type, but does not process the current target task based on any account data.

[0017] Preferably, querying the first account authorization status of the first associated user account includes:

[0018] Generate an authorization code based on the authorization code generation rule corresponding to the first associated user account, and send the authorization code to the account platform corresponding to the first associated user account;

[0019] Receive feedback information sent by the account platform, and determine a first account authorization status of the first associated user account based on the feedback information.

[0020] Preferably, the method further comprises:

[0021] When the accumulated data corresponding to any of the task types in the recorded data is greater than the preset accumulated data, a third task is generated in the periodic task list based on the accumulated data, and the task priority of the third task is higher than the first preset priority.

[0022] Preferably, the method further comprises:

[0023] When the second account data is not less than the accumulated data, the accumulated data is processed based on the second account data.

[0024] Preferably, the method further comprises:

[0025] After any of the target tasks is processed and completed, a reminder message is generated and sent to a user terminal corresponding to the target user.

[0026] According to a second aspect, there is provided an intelligent interaction device for account data, the device comprising:

[0027] a determination module, configured to determine all unprocessed first tasks of a target user within a current time period, and lock first account data in a virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is a sum of each to-be-interacted data corresponding to each first task, and tasks of different task types correspond to different task priorities;

[0028] a first processing module, configured to retrieve target tasks in the task list of the day in order when the current moment reaches the preset interaction moment, and process the target tasks in order based on the current account data in the virtual account, wherein the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data;

[0029] The second processing module is used to determine the current task priority corresponding to the current target task and the first associated user account corresponding to the current target task when the second account data cannot process the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, and the second preset priority is less than the first preset priority.

[0030] According to a third aspect, there is provided an electronic device, comprising a processor and a memory;

[0031] The processor is connected to the memory;

[0032] The memory is used to store executable program code;

[0033] The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the steps of the method provided in the first aspect or any possible implementation manner of the first aspect.

[0034] According to a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and the computer-readable storage medium stores instructions, which, when the instructions are executed on a computer or a processor, cause the computer or the processor to execute the method provided in the first aspect or any possible implementation of the first aspect.

[0035] The method and device provided in the embodiments of this specification can intelligently monitor the user's contract status, assign corresponding payment processing tasks to each contract, and determine the task processing flow according to the priority of the task, the account authorization status, and the order of the task list when the task reaches the deadline, so as to actively obtain the corresponding account data from the user's virtual account or the first associated user account according to the task processing flow to complete the task. The whole process does not require the user to operate personally, and the task processing efficiency is higher, avoiding the situation of contract overdue due to user forgetfulness. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0037] Figure 1 It is a flowchart of an intelligent interaction method for account data in one embodiment of this specification.

[0038] Figure 2 It is a structural diagram of an intelligent interactive device for account data in one embodiment of the present specification.

[0039] Figure 3 It is a structural diagram of an electronic device in one embodiment of this specification. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0041] In the following introduction, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance. The following introduction provides multiple embodiments of the present application, and different embodiments can be replaced or combined, so the present application can also be considered to include all possible combinations of the same and / or different embodiments recorded. Therefore, if one embodiment includes features A, B, and C, and another embodiment includes features B and D, then the present application should also be considered to include embodiments containing one or more of all other possible combinations of A, B, C, and D, although the embodiment may not be clearly recorded in the following text.

[0042] The following description provides examples and does not limit the scope, applicability or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements described without departing from the scope of the present application. Various processes or components may be appropriately omitted, substituted or added to each example. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted or combined. In addition, features described in some examples may be combined in other examples.

[0043] See also Figure 1 , Figure 1 : is a flow chart of an intelligent interaction method for account data provided in an embodiment of the present application. In an embodiment of the present application, the method includes:

[0044] S101. Determine all unprocessed first tasks of a target user in a current time period, and lock first account data in a virtual account corresponding to the target user.

[0045] The first task is a task with a task priority higher than a first preset priority, the first account data is the sum of the to-be-interacted data corresponding to the first tasks, and the task priorities corresponding to tasks of different task types are different.

[0046] The executor of this application may be the cloud server corresponding to the platform on which the user signs the contract.

[0047] In the embodiment of the present specification, for each contract that requires the user to pay on the contract fulfillment date, a payment transaction task will be generated in the cloud server. Each task will be set with a corresponding deadline, and the cloud server will monitor each task according to the deadline. After the task reaches the deadline, the cloud server will add the task to the task list to actively process the task according to the actual situation of the task, that is, automatically obtain the balance data in the user account, and actively complete the payment transaction of the task according to the balance data. Among them, according to different contract types, tasks will also have different task types, and tasks of different task types will be set with different task priorities according to their importance. The cloud server should try to ensure that high-priority tasks can be completed as soon as possible when the deadline is reached. Therefore, in order to avoid the situation that the remaining account data, that is, the account balance is not enough to process subsequent high-priority tasks after the account processes other low-priority tasks, resulting in the inability to complete the task, or the need to spend extra time to obtain account data from other platform accounts, the cloud server will first determine all the first tasks that have not been processed within the current time period (for example, a week can be a time period). These first tasks are the aforementioned tasks that need to be prioritized to ensure that they can be completed efficiently. Next, the cloud server will determine the data to be interacted corresponding to each first task, that is, the transaction amount required to complete the task, and calculate the sum of the data to be interacted for all first tasks. The sum of these data to be interacted is the account balance required by the user's corresponding account to complete these first tasks within the current time period. Therefore, the cloud server will lock the account data that is the same as the sum of the data to be interacted from the virtual account of the target user, that is, the first account data, to ensure that when the first task reaches the deadline within the current time period, there is always enough account data in the virtual account to complete the first task. Among them, the virtual account can be an account created by the user on the platform where the contract is signed, and the user can store a certain amount of account data in the virtual account in advance to complete each task. In this way, when the task deadline arrives, the cloud server can directly process the task through the account data in the virtual account, without having to interact with the user's account in other banks, eliminating the cumbersome interaction processes such as verification, authorization, and cross-platform transactions.

[0048] As an example, taking a financial contract signed with a bank as an example, the task types of tasks may include: security deposit, handling fee, principal, rental interest, overdue business rent, down payment, penalty interest, nominal price, commission income, bank bill acceptance, etc. The task priorities of these task types may be ranked from high to low: security deposit > overdue business rent > handling fee > down payment > principal > rental interest > penalty interest > nominal price > commission income > bank bill acceptance.

[0049] S102: When the current moment reaches the preset interaction moment, the target tasks are retrieved in order from the task list of the day according to the sorting order, and the target tasks are processed in order based on the current account data in the virtual account.

[0050] Among them, the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data.

[0051] In an embodiment of the present specification, a daily task list is provided in the cloud server, and the daily task list stores tasks that will reach the deadline on the same day. Different tasks may have different specific contract performance times on the same day. In order to avoid the cloud server frequently monitoring the expiration of each task and increasing the server burden, at least one interaction time will be pre-set. When the cloud server reaches the interaction time at the current time of the day, it will batch process the various target tasks that appear in the daily task list in the sorting order. The various target tasks in the daily task list may be the first task or the second task. For the first task, the cloud server will complete the processing of the first task with the first account data locked in the aforementioned step. For the second task, the cloud server will complete the processing of the second task with the second account data remaining after removing the first account data from the virtual account.

[0052] In one possible implementation, the processing of the target tasks in sequence based on the current account data in the virtual account includes:

[0053] When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed;

[0054] When the target task is the second task, the target task is processed based on the second account data.

[0055] In the embodiment of the present specification, since the first account data is in a locked state, the cloud server will unlock the first account data only when it determines that the target task currently being processed is the first task, and complete the processing of the target task according to the first account data. Then, after completing the processing of the target task, in order to avoid accidentally deducting part of the data in the first account data during the subsequent processing of other second tasks, the cloud server will re-lock the first account data. For the second task, the cloud server will directly process the task according to the second account data.

[0056] S103. When the second account data cannot process the current target task, determine the current task priority corresponding to the current target task, and determine the first associated user account corresponding to the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow.

[0057] The priority comparison result is a comparison result between the current task priority and a second preset priority, the first account authorization status is the authorization status of the first associated user account, and the second preset priority is lower than the first preset priority.

[0058] In the embodiment of the present specification, the account data in the virtual account of the target user, that is, the account balance, after locking the first account data required to complete the first task, the remaining second account data may not be able to process the second task, that is, the second account data does not reach the amount required to complete the second task. In this case, the cloud server will determine the current task priority corresponding to the task type of the current target task, and determine the priority comparison result of the current task priority in combination with the second preset priority. According to the priority comparison result, the cloud server can determine whether the task is more urgent and important. For tasks with a lower priority, that is, less urgent and important, the cloud server may not immediately obtain account data from accounts on other platforms, but may adopt methods such as accounting but not actual deductions, waiting for the user to supplement the account data in the virtual account. At the same time, the cloud server will also determine the first associated user account corresponding to the current target task. The first associated user account can be understood as the bank account signed or specified in the contract corresponding to the current target task. That is, when the balance in the virtual account registered by the user on the platform is insufficient, the cloud server will determine the bank account actually corresponding to the user in the contract according to the contract corresponding to the task, so as to obtain the corresponding account data from the bank account to complete the processing of the target task. However, in actual situations, depending on the specific content of the contract, some contracts may not support the use of accounts on other platforms to complete payment, which will cause the cloud server to be unable to obtain account data from the first associated user account due to account authorization failure. Ultimately, the cloud server will use the priority comparison results and the authorization status of the first account to query the corresponding task processing flow in the pre-set database, and process the target task according to the task processing flow. Among them, the database can pre-set different priority comparison results and first account authorization status, and the mapping relationship between different task processing flows.

[0059] In one possible implementation, the task processing flow of determining the current target task based on the priority comparison result and the authorization status of the first account includes:

[0060] Comparing the current task priority with the second preset priority to generate a priority comparison result, the priority comparison result comprising a first comparison result indicating that the current task priority is greater than the second preset priority and a second comparison result indicating that the current task priority is not greater than the second preset priority;

[0061] querying a first account authorization status of the first associated user account, where the first account authorization status includes a first authorization status indicating a successful authorization and a second authorization status indicating a failed authorization;

[0062] When the priority comparison result is a first comparison result and the first account authorization status is a first authorization status, determining that the task processing flow of the current target task is a first processing flow, wherein the first processing flow is a flow for processing the current target task based on the account data of the first associated user account;

[0063] When the priority comparison result is the first comparison result and the first account authorization status is the second authorization status, determining that the task processing flow of the current target task is the second processing flow, the second processing flow is a flow for processing the current target task based on the account data of the second associated user account, and the second associated user account is a user account of the target user on other account platforms that is associated with the first associated user account;

[0064] When the priority comparison result is the second comparison result, the task processing flow of the current target task is determined to be the third processing flow, and the third processing flow is a process that records the data to be interacted of the current target task in the record data based on the task type, but does not process the current target task based on any account data.

[0065] In the embodiment of the present specification, the cloud server will compare the current task priority and the second preset priority to obtain the first comparison result or the second comparison result. At the same time, the cloud server will also query the first account authorization status of the first associated user account to obtain the first authorization status or the second authorization status. The cloud server will select different task processing procedures according to the priority comparison result and the first account authorization status.

[0066] Specifically, for the first comparison result and the first authorization status, it means that the task priority of the current target task is relatively high, and the account data should be obtained from the first associated user account to complete the task as soon as possible. At the same time, the authorization of the first associated user account has been successful, which means that the cloud server can establish a connection with the first associated user account of other platforms and interact with it for account data. Therefore, the cloud server will process the current target task from the account data in the first associated user account.

[0067] For the first comparison result and the second authorization status, it means that the task priority of the current target task is relatively high, and the account data should be obtained from the first associated user account to complete the task as soon as possible. However, since the authorization of the first associated user account failed, it means that the account data cannot be obtained from the first associated user account due to the content of the contract and other reasons. The first associated user account is only the default account filled in by the user when signing the contract. The failure of authorization of the first associated user account does not necessarily mean that the second associated user account of the user on other bank platforms will also fail to be authorized. Therefore, the cloud server will determine the second associated user account of the user on other platforms that has an associated relationship with the first associated user account, and determine the second account authorization status of each second associated user account, so as to determine a second associated user account whose second account authorization status is an authorized status, and complete the processing of the current target task based on the account data in the account.

[0068] For the second comparison result, it means that the task priority of the current target task is relatively low. Regardless of whether the first associated user account is authorized, the cloud server believes that it is not necessary to interact with accounts on other platforms to complete the target task. The cloud server will record the data to be interacted with in the record data according to the task type in a way of accounting but not actually deducting money, and regard the current target task as completed. After the target user interacts with new account data in the virtual account, the cloud server can actively complete the settlement of the account in the record data based on the account data in the virtual account.

[0069] In one possible implementation, querying the first account authorization status of the first associated user account includes:

[0070] Generate an authorization code based on the authorization code generation rule corresponding to the first associated user account, and send the authorization code to the account platform corresponding to the first associated user account;

[0071] Receive feedback information sent by the account platform, and determine a first account authorization status of the first associated user account based on the feedback information.

[0072] In the embodiments of this specification, different platforms may be pre-set with different authorization code generation rules. The cloud server will determine the corresponding authorization code generation rule based on the account platform of the first associated user account, and generate an authorization code based on the authorization code generation rule. Then, the cloud server will send the authorization code to the account platform for verification. The account platform will generate feedback information based on the verification situation and send the feedback information to the cloud server. The cloud server can determine whether the authorization is successful or not through the received feedback information.

[0073] As an example, the authorization code generation rule can be the PAY_ID ID number + two-digit code, or the bank account number + two-digit serial number, or other feasible methods. Among them, the two-digit code can be generated based on the ID number + bank account number to query the number of documents in the deduction authorization application node + 01. Different contracts correspond to different numbers of documents, so the generated codes are different. If the code cannot correspond to any code pre-stored in the code database, it means that the account cannot authorize the transaction of the contract and the authorization fails.

[0074] In one embodiment, the method further comprises:

[0075] When the accumulated data corresponding to any of the task types in the recorded data is greater than the preset accumulated data, a third task is generated in the periodic task list based on the accumulated data, and the task priority of the third task is higher than the first preset priority.

[0076] In the embodiment of the present specification, the cloud server monitors the accumulated data of each task type in the recorded data. If the accumulated data corresponding to a task type exceeds the preset accumulated data, it is considered that the task type has accumulated too much data, and if it continues to accumulate, there will be a greater risk of loss. At this time, the cloud server generates a third task based on the accumulated data, adds the third task to the periodic task list, and sets the task priority of the third task to be higher than the first preset priority, so that the third task, like the first task, will be prioritized and guaranteed to be processed in the current cycle.

[0077] In one embodiment, the method further comprises:

[0078] When the second account data is not less than the accumulated data, the accumulated data is processed based on the second account data.

[0079] In the embodiments of this specification, the target user can initiate an interaction request to the virtual account at any time through the user terminal used by the target user, so as to transfer account data to the virtual account according to the user account of other account platforms selected by the target user, thereby increasing the account data in the virtual account. If there is accumulated data in the recorded data, and the second account data in the virtual account becomes not less than the accumulated data, the cloud server will actively process the accumulated data according to the second account data to minimize the accumulated data in the recorded data.

[0080] In one embodiment, the method further comprises:

[0081] After any of the target tasks is processed and completed, a reminder message is generated and sent to a user terminal corresponding to the target user.

[0082] In the embodiments of this specification, since the cloud server will autonomously process each target task, the cloud server should remind the target user after processing the target task to inform the target user which tasks have been automatically processed. Therefore, each time the cloud server processes a task, it will generate a reminder message corresponding to the task and send the reminder message to the user terminal used by the target user. In order to avoid pop-up reminders that cause trouble to the user, the reminder message can be sent to a specified application on the user terminal, and the corresponding reminder message will only pop up when the user opens the application.

[0083] The following will be combined with the attached Figure 2 , the intelligent interactive device for account data provided in the embodiment of the present application is introduced in detail. Figure 2 The intelligent interactive device of the account data shown is used to execute this application Figure 1 For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Figure 1 The embodiment shown.

[0084] See also Figure 2 , Figure 2 Schematic diagram of a smart interactive device for account data provided by an embodiment of the present application. Figure 2 As shown, the device comprises:

[0085] The determination module 201 is used to determine all unprocessed first tasks of the target user in the current time period, and lock the first account data in the virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is the sum of the to-be-interacted data corresponding to the first tasks, and the task priorities corresponding to tasks of different task types are different;

[0086] The first processing module 202 is used to retrieve target tasks in the task list of the day in order when the current moment reaches the preset interaction moment, and process the target tasks in order based on the current account data in the virtual account, the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data;

[0087] The second processing module 203 is used to determine the current task priority corresponding to the current target task and the first associated user account corresponding to the current target task when the second account data cannot process the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, and the second preset priority is less than the first preset priority.

[0088] In one possible implementation, the first processing module 202 is specifically configured to:

[0089] When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed;

[0090] When the target task is the second task, the target task is processed based on the second account data.

[0091] In one possible implementation, the second processing module 203 is specifically used for:

[0092] Comparing the current task priority with the second preset priority to generate a priority comparison result, the priority comparison result comprising a first comparison result indicating that the current task priority is greater than the second preset priority and a second comparison result indicating that the current task priority is not greater than the second preset priority;

[0093] querying a first account authorization status of the first associated user account, where the first account authorization status includes a first authorization status indicating a successful authorization and a second authorization status indicating a failed authorization;

[0094] When the priority comparison result is a first comparison result and the first account authorization status is a first authorization status, determining that the task processing flow of the current target task is a first processing flow, wherein the first processing flow is a flow for processing the current target task based on the account data of the first associated user account;

[0095] When the priority comparison result is the first comparison result and the first account authorization status is the second authorization status, determining that the task processing flow of the current target task is the second processing flow, the second processing flow is a flow for processing the current target task based on the account data of the second associated user account, and the second associated user account is a user account of the target user on other account platforms that is associated with the first associated user account;

[0096] When the priority comparison result is the second comparison result, the task processing flow of the current target task is determined to be the third processing flow, and the third processing flow is a process that records the data to be interacted of the current target task in the record data based on the task type, but does not process the current target task based on any account data.

[0097] In one possible implementation, the second processing module 203 is further configured to:

[0098] Generate an authorization code based on the authorization code generation rule corresponding to the first associated user account, and send the authorization code to the account platform corresponding to the first associated user account;

[0099] Receive feedback information sent by the account platform, and determine a first account authorization status of the first associated user account based on the feedback information.

[0100] In one possible implementation, the second processing module 203 is further configured to:

[0101] When the accumulated data corresponding to any of the task types in the recorded data is greater than the preset accumulated data, a third task is generated in the periodic task list based on the accumulated data, and the task priority of the third task is higher than the first preset priority.

[0102] In one possible implementation, the second processing module 203 is further configured to:

[0103] When the second account data is not less than the accumulated data, the accumulated data is processed based on the second account data.

[0104] In one embodiment, the device further comprises:

[0105] The sending module is used to generate reminder information after any of the target tasks is processed and completed, and send the reminder information to the user terminal corresponding to the target user.

[0106] Those skilled in the art can clearly understand that the technical solutions of the embodiments of the present application can be implemented with the help of software and / or hardware. The "unit" and "module" in this specification refer to software and / or hardware that can independently complete or cooperate with other components to complete specific functions, where the hardware can be, for example, a field programmable gate array (FPGA), an integrated circuit (IC), etc.

[0107] Each processing unit and / or module of the embodiments of the present application may be implemented by an analog circuit that implements the functions described in the embodiments of the present application, or may be implemented by software that executes the functions described in the embodiments of the present application.

[0108] See also Figure 3 , which shows a schematic diagram of the structure of an electronic device involved in an embodiment of the present application, the electronic device can be used to implement Figure 1 The method in the embodiment shown. Figure 3 As shown, the electronic device 300 may include: at least one central processor 301 , at least one network interface 304 , a user interface 303 , a memory 305 , and at least one communication bus 302 .

[0109] The communication bus 302 is used to realize the connection and communication between these components.

[0110] The user interface 303 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 303 may also include a standard wired interface and a wireless interface.

[0111] The network interface 304 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0112] Among them, the central processing unit 301 may include one or more processing cores. The central processing unit 301 uses various interfaces and lines to connect various parts of the entire electronic device 300, and executes various functions and processes data of the terminal 300 by running or executing instructions, programs, code sets or instruction sets stored in the memory 305, and calling data stored in the memory 305. Optionally, the central processing unit 301 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The central processing unit 301 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the central processing unit 301, and it can be implemented separately through a chip.

[0113] Among them, the memory 305 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 305 includes a non-transitory computer-readable storage medium. The memory 305 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 305 may optionally be at least one storage device located away from the aforementioned central processor 301. As Figure 3 As shown, the memory 305 as a computer storage medium may include an operating system, a network communication module, a user interface module, and program instructions.

[0114] exist Figure 3In the electronic device 300 shown, the user interface 303 is mainly used to provide an input interface for the user and obtain the data input by the user; and the central processor 301 can be used to call the intelligent interactive application of the account data stored in the memory 305, and specifically perform the following operations:

[0115] Determine all unprocessed first tasks of the target user in the current time period, and lock first account data in the virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is the sum of each to-be-interacted data corresponding to each first task, and the task priorities corresponding to tasks of different task types are different;

[0116] When the current moment reaches the preset interaction moment, the target tasks are retrieved in order from the task list of the day in order, and the target tasks are processed in order based on the current account data in the virtual account, the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data;

[0117] When the second account data cannot process the current target task, determine the current task priority corresponding to the current target task, and determine the first associated user account corresponding to the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, and the second preset priority is less than the first preset priority.

[0118] In one possible implementation, the processing of the target tasks in sequence based on the current account data in the virtual account includes:

[0119] When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed;

[0120] When the target task is the second task, the target task is processed based on the second account data.

[0121] In one possible implementation, the processing of the target tasks in sequence based on the current account data in the virtual account includes:

[0122] When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed;

[0123] When the target task is the second task, the target task is processed based on the second account data.

[0124] In one possible implementation, querying the first account authorization status of the first associated user account includes:

[0125] Generate an authorization code based on the authorization code generation rule corresponding to the first associated user account, and send the authorization code to the account platform corresponding to the first associated user account;

[0126] Receive feedback information sent by the account platform, and determine a first account authorization status of the first associated user account based on the feedback information.

[0127] In one embodiment, the method further comprises:

[0128] When the accumulated data corresponding to any of the task types in the recorded data is greater than the preset accumulated data, a third task is generated in the periodic task list based on the accumulated data, and the task priority of the third task is higher than the first preset priority.

[0129] In one embodiment, the method further comprises:

[0130] When the second account data is not less than the accumulated data, the accumulated data is processed based on the second account data.

[0131] In one embodiment, the method further comprises:

[0132] After any of the target tasks is processed and completed, a reminder message is generated and sent to a user terminal corresponding to the target user.

[0133] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the above method are implemented. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a micro drive, and a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic card or an optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0134] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0135] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0136] In the several embodiments provided in the present application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0137] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0138] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0139] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, disk or optical disk and other media that can store program codes.

[0140] A person skilled in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by entering a program to instruct related hardware, and the program may be stored in a computer-readable memory, which may include a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0141] The above is only an exemplary embodiment of the present disclosure, and the scope of the present disclosure cannot be limited thereto. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the specification and practicing the disclosure here, those skilled in the art will easily think of the implementation scheme of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field not recorded in the present disclosure. The description and examples are regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.

Claims

1. An intelligent interaction method for account data, characterized in that: The method comprises: Determine all unprocessed first tasks of the target user in the current time period, and lock first account data in the virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is the sum of each to-be-interacted data corresponding to each first task, and the task priorities corresponding to tasks of different task types are different; When the current moment reaches the preset interaction moment, the target tasks are retrieved in order from the task list of the day in order, and the target tasks are processed in order based on the current account data in the virtual account, the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data; When the second account data cannot process the current target task, determine the current task priority corresponding to the current target task, and determine the first associated user account corresponding to the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, the second preset priority is less than the first preset priority, and the first associated user account is the bank account signed or specified in the contract corresponding to the current target task.

2. The method according to claim 1, characterized in that The processing of the target tasks in sequence based on the current account data in the virtual account includes: When the target task is the first task, unlocking the first account data, processing the target task based on the first account data, and re-locking the first account data after the target task is processed; When the target task is the second task, the target task is processed based on the second account data.

3. The method according to claim 1, characterized in that The task processing flow of determining the current target task based on the priority comparison result and the authorization status of the first account includes: Comparing the current task priority with the second preset priority to generate a priority comparison result, the priority comparison result comprising a first comparison result indicating that the current task priority is greater than the second preset priority and a second comparison result indicating that the current task priority is not greater than the second preset priority; querying a first account authorization status of the first associated user account, where the first account authorization status includes a first authorization status indicating a successful authorization and a second authorization status indicating a failed authorization; When the priority comparison result is a first comparison result and the first account authorization status is a first authorization status, determining that the task processing flow of the current target task is a first processing flow, wherein the first processing flow is a flow for processing the current target task based on the account data of the first associated user account; When the priority comparison result is the first comparison result and the first account authorization status is the second authorization status, determining that the task processing flow of the current target task is the second processing flow, the second processing flow is a flow for processing the current target task based on account data of a second associated user account, the second associated user account being a user account of the target user on other account platforms that is associated with the first associated user account; When the priority comparison result is the second comparison result, the task processing flow of the current target task is determined to be the third processing flow, and the third processing flow is a process that records the data to be interacted of the current target task in the record data based on the task type, but does not process the current target task based on any account data.

4. The method according to claim 3, characterized in that The querying the first account authorization status of the first associated user account includes: Generate an authorization code based on the authorization code generation rule corresponding to the first associated user account, and send the authorization code to the account platform corresponding to the first associated user account; Receive feedback information sent by the account platform, and determine a first account authorization status of the first associated user account based on the feedback information.

5. The method according to claim 3, characterized in that: The method further comprises: When the accumulated data corresponding to any of the task types in the recorded data is greater than the preset accumulated data, a third task is generated in the periodic task list based on the accumulated data, and the task priority of the third task is higher than the first preset priority.

6. The method according to claim 5, characterized in that The method further comprises: When the second account data is not less than the accumulated data, the accumulated data is processed based on the second account data.

7. The method according to claim 1, characterized in that The method further comprises: After any of the target tasks is processed and completed, a reminder message is generated and sent to a user terminal corresponding to the target user.

8. An intelligent interactive device for account data, characterized in that: The device comprises: a determination module, configured to determine all unprocessed first tasks of a target user within a current time period, and lock first account data in a virtual account corresponding to the target user, wherein the first task is a task with a task priority higher than a first preset priority, and the first account data is a sum of each to-be-interacted data corresponding to each first task, and tasks of different task types correspond to different task priorities; a first processing module, configured to retrieve target tasks in the task list of the day in order when the current moment reaches the preset interaction moment, and process the target tasks in order based on the current account data in the virtual account, wherein the target task includes at least one of the first task and the second task, the current account data includes the first account data and the second account data, the second task is a task whose task priority is not higher than the first preset priority, and the second account data is account data in the current account data except the first account data; The second processing module is used to determine the current task priority corresponding to the current target task and the first associated user account corresponding to the current target task when the second account data cannot process the current target task, determine the task processing flow of the current target task based on the priority comparison result and the authorization status of the first account, and process the current target task based on the task processing flow, the priority comparison result is the comparison result of the current task priority and the second preset priority, the authorization status of the first account is the authorization status of the first associated user account, the second preset priority is less than the first preset priority, and the first associated user account is the bank account signed or specified in the contract corresponding to the current target task.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, wherein the computer-readable storage medium has instructions stored therein, and when the instructions are executed on a computer or a processor, the computer or the processor executes the steps of the method according to any one of claims 1 to 7.

Images