Task processing method and device, electronic equipment and medium

Abstract

The invention discloses a task processing method and device, electronic equipment and a medium. Belongs to the technical field of communication. The method comprises the following steps: receiving task participant information and task description information sent by a first user in a group; based on the task participant information and the task description information, virtual nodes corresponding to the task participants are created, and the virtual nodes comprise task state information and task parameters; after an information confirmation message of a second user in the group for the target virtual node is received, a task is issued to the second user based on the task parameters in the target virtual node; and updating task state information in the target virtual node based on a task execution result of the second user, and synchronizing the task state information to the first user.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to task processing methods, apparatus, electronic devices, and media. Background Technology

[0002] With the development of mobile devices, more and more users are organizing activities through groups in social applications. The organization and management of group activities typically involves tasks such as attendance tracking and fee collection.

[0003] In existing technologies, group tasks usually require manual management by the organizer, such as manually entering the list, manually taking attendance, confirming the identity of the transferor, and checking the transaction records in the group one by one. This method is inefficient, prone to errors, and cannot keep track of the task status of each group member in a timely manner. Summary of the Invention

[0004] The purpose of this application is to provide a task processing method, apparatus, electronic device, and medium that improves the efficiency and accuracy of task processing and realizes automated task management.

[0005] In a first aspect, embodiments of this application provide a task processing method, the method comprising: receiving task participant information and task description information sent by a first user in a group; creating virtual nodes corresponding to each task participant based on the task participant information and the task description information, the virtual nodes including task status information and task parameters; after receiving an information confirmation message from a second user in the group regarding a target virtual node, issuing a task to the second user based on the task parameters in the target virtual node; updating the task status information in the target virtual node based on the task execution result of the second user, and synchronizing the task status information with the first user.

[0006] Secondly, embodiments of this application provide a task processing method, the method comprising: receiving a first input from a first user; in response to the first input, acquiring task participant information and task description information; sending the task participant information and the task description information to a server, so that the server creates virtual nodes corresponding to each task participant based on the task participant information and the task description information, and issues a task to the second user after receiving an information confirmation message from a second user in a group for a target virtual node; receiving task status information of the second user sent by the server, and displaying the task status information.

[0007] Thirdly, embodiments of this application provide a task processing apparatus, comprising: a receiving unit for receiving task participant information and task description information sent by a first user in a group; a creating unit for creating virtual nodes corresponding to each task participant based on the task participant information and the task description information, wherein the virtual nodes include task status information and task parameters; a sending unit for sending a task to the second user based on the task parameters in the target virtual node after receiving an information confirmation message from a second user in the group regarding a target virtual node; and a synchronization unit for updating the task status information in the target virtual node based on the task execution result of the second user and synchronizing the task status information with the first user.

[0008] Fourthly, embodiments of this application provide a task processing apparatus, comprising: a receiving unit for receiving a first input from a first user; an acquiring unit for acquiring task participant information and task description information in response to the first input; a sending unit for sending the task participant information and the task description information to a server, so that the server creates virtual nodes corresponding to each task participant based on the task participant information and the task description information, and issues a task to the second user after receiving an information confirmation message from a second user in a group for a target virtual node; and a display unit for receiving task status information of the second user sent by the server and displaying the task status information.

[0009] Fifthly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0010] In a sixth aspect, embodiments of this application provide a readable storage medium on which a computer program is stored, and when executed by a processor, the computer program implements the steps of the method described in the first aspect above.

[0011] In a seventh aspect, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method described in the first aspect.

[0012] Eighthly, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0013] In this embodiment, after receiving task participant information and task description information sent by the first user in the group, virtual nodes corresponding to each task participant are created based on the task participant information and task description information. The virtual nodes include the task status information and task parameters of the aforementioned task. After receiving a confirmation message from the second user in the group regarding the target virtual node, the task is issued to the second user based on the task parameters in the target virtual node. Finally, based on the second user's task execution result, the task status information in the target virtual node is updated, and the task status information is synchronized to the first user. In the above process, by creating virtual nodes, the organizer's preliminary work of manually entering information is eliminated, errors introduced by manual operation are eliminated, and an accurate data foundation is provided for subsequent processes. By introducing a mechanism for group members to confirm information regarding virtual nodes, group members can be accurately associated with task parameters, eliminating the need for the organizer to manually call out names and verify identities, ensuring that tasks are accurately distributed to the correct group members, and improving the accuracy of task processing. By automatically monitoring task execution and synchronizing the task status to the first user, the organizer's process of manually calculating task status is eliminated, allowing the organizer to grasp the progress of the entire task in real time and achieving automated task management. Attached Figure Description

[0014] Figure 1 This is a flowchart of the task processing method provided in the embodiments of this application; Figure 2 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 3 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 4 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 5 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 6 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 7 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 8 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 9 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 10 This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 11This is a schematic diagram illustrating an application scenario of the task processing method provided in the embodiments of this application; Figure 12 This is a flowchart of the task processing method provided in the embodiments of this application; Figure 13 This is a schematic diagram of the structure of the task processing device provided in the embodiments of this application; Figure 14 This is a schematic diagram of the structure of the task processing device provided in the embodiments of this application; Figure 15 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application; Figure 16 This is a schematic diagram of the hardware structure of an electronic device suitable for implementing the embodiments of this application. Detailed Implementation

[0015] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0016] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0017] The task processing method and apparatus provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0018] Please refer to Figure 1 This illustrates one of the flowcharts of a task processing method provided in an embodiment of this application. The task processing method provided in this application can be applied to a server.

[0019] The task processing method provided in this application includes the following steps: Step 101: Receive task participant information and task description information sent by the first user in the group.

[0020] In this embodiment, a group refers to a virtual space created based on specific applications such as instant messaging applications for multi-person communication and collaboration. The first user refers to a user with specific permissions in the group, such as the group owner or administrator, who is responsible for initiating and monitoring tasks.

[0021] The task participant information is a structured or unstructured data collection containing relevant information about the task participants. It can be in the form of images, documents, or tables, such as screenshots of the task participant list or spreadsheet files. In practice, the task participant information may include, but is not limited to, the task participant's ID, name, and task parameters. The name mentioned above can be the same as or different from the group member's nickname; there is no restriction here.

[0022] The task description information is text information used to describe the task objectives and requirements. It can be a message or instruction sent by the first user in the group. For example, "Please pay the remaining balance for the event" or "Please complete the sign-in by this Friday." This information can reflect the core intent and type of the task set by the first user, such as information confirmation task, sign-in task, payment task, course check-in task, club activity task, material distribution task, volunteer activity task, etc.

[0023] Step 102: Based on the task participant information and task description information, create virtual nodes corresponding to each task participant. The virtual nodes include task status information and task parameters.

[0024] In this embodiment, a virtual node can refer to a data structure created in a computer system, serving as a unique mapping of task participants in the digital space. Each virtual node is an independent data entity used to encapsulate and maintain the task parameters and task status information of a task participant.

[0025] Task parameters describe the attributes of the task itself and can be derived from task participant information and task description information. For example, they may include task type, amount to be paid, and task deadline. Task status information describes the task's processing status, such as not started, not completed, in progress, or completed.

[0026] It should be noted that, in addition to task parameters and task status information, virtual nodes can also contain other information as needed, which is not specifically limited here. For example, each virtual node contains the following information: a basic identifier, used to bind the virtual node to its group to avoid cross-group interference, which may include, but is not limited to, the virtual node identifier and group identifier; member association information, used to associate group member identities to ensure the uniqueness of the association, which may include, but is not limited to, the task participant's number, name, account identifier, etc.; task parameters, used to clarify the core requirements of the task, which may include, but is not limited to, the final payment amount, task type, etc.; status management information, used to reflect the current status of the node in real time, including but not limited to the virtual node's association status information, task status information, timestamp, etc. The initial value of the association status information is "not associated," and the initial value of the task status information is "not started"; and access control information, whose initial value can be set by the first user and subsequently adjusted by the group members associated with the virtual node, used to set the visible objects of the information in the virtual node, such as visible only to the group member, visible to some group members, visible to all group members, etc.

[0027] In this embodiment, after obtaining the task participant information and task description information, the artificial intelligence service module can be automatically activated to parse the task description information and task participant information. Specifically, the task description information can be parsed first to understand the task intent. For example, the keyword "payment" can be identified through natural language processing technology to determine the task type as a "payment task". Next, the task participant information is parsed to extract the identification information of each participant, such as name and number, and to retrieve the task-related parameters for each participant, such as the amount to be paid. This parsing process can employ basic image processing and text matching algorithms. Finally, a virtual node can be created for each task participant in the task participant information. The virtual node can include task parameters and task status information. Task parameters can include parameters extracted from the task participant information, such as the amount to be paid, and the task type determined from the task description information. The task status information can be initialized to default values, such as an association status of "not associated" and a task status of "not started".

[0028] Optionally, after creating a virtual node for each task participant in the task participant information, the task participant can be automatically associated with a group identifier to ensure that each virtual node is effective only for that group. In practice, the virtual node identifier can adopt the following format: Group Identifier - Task Identifier - Task Participant Number.

[0029] Optionally, if a virtual node has missing fields, such as omitting participant names or having unclear amount identification, the virtual node can be marked as a node to be completed, highlighted in the virtual node query interface, and a notification to the first user to complete the information, along with the virtual node query interface, can be pushed. Simultaneously, a manual completion entry can be provided to the first user, allowing them to upload supplementary screenshots or directly input the missing information. It should be noted that for virtual nodes with missing fields, when pushing association notifications to group members, they can be excluded from being listed as bindable virtual nodes to avoid members binding virtual nodes with incomplete information. Alternatively, if the virtual node is already associated with a group member, a completion notification can also be pushed to that group member associated with the virtual node.

[0030] Step 103: After receiving the information confirmation message from the second user in the group regarding the target virtual node, a task is sent to the second user based on the task parameters in the target virtual node.

[0031] In this embodiment, the second user can be any group member other than the first user, and is the specific executor of the task. In practice, a message can be pushed to the second user to confirm the task and trigger a reminder. The reminder can be displayed on the second user's client interface, and the second user can click to view and complete the message confirmation task. Alternatively, the first user can send a specific message in the group to trigger a reminder. The format of the specific message can be "@everyone[specific instruction]", such as "@everyone[check-in]", "@everyone[pay the balance]", etc., and is not limited here.

[0032] The aforementioned to-do reminders can be used to guide a second user to access the virtual node query interface by clicking on a link or entry point, find their corresponding virtual node, confirm their personal information, and thus establish an association with the virtual node. The target virtual node is the virtual node to be associated with the second node, which can be selected by the second user after browsing the virtual node query interface.

[0033] As an example, see the to-do reminders section. Figure 7 As shown in reference numeral 701, the entry point for the virtual node query interface is shown in reference numeral 702. After clicking the aforementioned link or entry point 701, the second user can display the virtual node query interface, see [link / reference]. Figure 8As shown in reference numeral 801, the second user can quickly find their target virtual node by entering their name, ID, mobile phone number, or a record from the search list in the virtual node query interface 801. Afterwards, they can choose whether to establish a relationship with the target virtual node. If they choose to establish a relationship, for example, by clicking the "Confirm" control, the relationship will be established. If they choose not to establish a relationship, they can try again later. If the second user finds any errors in the target virtual node information, they can click the "Feedback" control to report them to the system. After receiving the feedback, the system can notify the group owner to verify and modify it. Optionally, when establishing a relationship, the second user can also choose the visibility range of the relationship, such as visible only to themselves, visible to the group owner, visible to designated personnel, or visible to all group members, to ensure privacy protection.

[0034] In this embodiment, after receiving the information confirmation message from the second user regarding the target virtual node—that is, after the second user completes the aforementioned information confirmation task—it can be verified whether the name in the target virtual node matches the second user's real-name authentication name in the group, or the second user can input a number and verify whether that number matches the number corresponding to the target virtual node. If they match, the second user can be associated with the target virtual node indicated by the association request, and the association status information of the target virtual node can be updated to "associated." A task can then be issued to the second user based on the task parameters in the target virtual node.

[0035] As an example, see Figure 9 As shown, a group includes group owner A and group members Xiao Wang, Xiao Liu, and Xiao Wu. After Xiao Wang, Xiao Liu, and Xiao Wu complete the information confirmation task, i.e., after they are all associated with the corresponding virtual nodes, they can receive subsequent tasks to be executed, namely, the check-in task and the payment task. In addition, after the second user completes the above information confirmation task, a message can be pushed to the first user, who can click to view the details of the information confirmation task.

[0036] It should be noted that for group members who have not completed information confirmation, a confirmation reminder can be pushed at preset intervals until a confirmation message is received from the group member or the task ends. This operation can prevent group members from being missed. In addition, if a second user cannot find their corresponding virtual node, they can provide feedback. After receiving feedback, an empty virtual node can be created for them, waiting for the first user to confirm and correct.

[0037] Furthermore, to prevent others from impersonating a second user and using their account to fraudulently associate virtual nodes, the following operations can also be performed: Operation trajectory verification. First, the backend records the behavior trajectory of each second user after clicking the first user's @ message. This includes, for example, the time taken to navigate from the group chat interface to the virtual node query interface, the duration of page dwell, and whether the "View Virtual Node Details" control was clicked. Next, anomaly detection is performed. If the behavior trajectory matches abnormal behavior characteristics, such as a navigation time of less than 3 seconds, a dwell time of less than 5 seconds, or direct association without viewing virtual node details, a secondary verification is automatically triggered. This involves displaying a question temporarily generated based on group messages, such as, "What was the meeting time posted by the group owner in the group 10 minutes ago?", with the correct answer derived from group history messages.

[0038] Tiered authorization optimization. For a second user who joined the group less than 24 hours ago, the first user needs to verify their identity and authorize their association privileges to prevent new accounts from impersonating others and associating with virtual nodes. If the first user does not authorize within 10 minutes, authorization progress information can be automatically pushed to the second user, such as "Group owner has viewed, pending confirmation (5 / 10 minutes)". At the same time, an authorization timeout reminder can be pushed to the first user, which can include an authorization shortcut button to reduce the second user's waiting time.

[0039] The association relationships are stored encrypted. Specifically, an encryption algorithm is used to encrypt the second user's account information, virtual node identifier, and association time, and the encrypted data is stored in a distributed database. Only the authenticated first user and the authenticated second user with viewing permissions are allowed to decrypt and view the data, preventing data leakage and subsequent tampering with the association relationships.

[0040] Step 104: Based on the task execution result of the second user, update the task status information in the target virtual node and synchronize the task status information with the first user.

[0041] In this embodiment, after the second user establishes an association with the target virtual node, a task can be issued immediately or at a set time. The task issued can be the task indicated in the task description information above, such as a check-in task or a payment task.

[0042] As an example, a personalized task card can be pushed to each second user who has completed information confirmation and is associated with a virtual node. This card may include, but is not limited to, at least one of the following: task type, virtual node number, task requirements, and security verification identifier. Task requirements may include task parameters, such as, "Please complete the check-in before 08:00 on 2025-09-10," or "Final payment of 50 yuan, transfer remarks 'Number 05' are supported." The virtual node number is the same as the task participant's number.

[0043] In this embodiment, after the task is issued, the task status information in the target virtual node is updated based on the task execution result of the second user.

[0044] As an example, the tasks to be performed by the second user include a check-in task and a final payment task. The group chat interface can display reminders for these tasks.

[0045] For the check-in task, after the second user clicks the "Check-in" control on the interface to check in, the system can automatically verify whether the current time is within the check-in window and whether the associated status is normal and not frozen. After the verification is passed, the check-in time and device information can be recorded, and a check-in certificate containing the task code and check-in timestamp can be generated. Then, the task status information corresponding to the check-in task in the target virtual node can be updated to "Completed".

[0046] For final payment tasks, a payment note guide can be pushed, such as "Please note 'Virtual Node 05 + Name'" to facilitate automatic matching by the system. The second user can make the final payment through the transfer function provided in the group interface. After the second user completes the payment, the system automatically verifies whether the payment amount matches the information in the virtual node and whether the note contains the node identifier. If the verification is successful, the task status is updated. If the amount is inconsistent or there is no note, a payment error reminder can be pushed to the second user, guiding them to add a note or pay the difference, while simultaneously notifying the first user to intervene and verify. If the amount matches and there is a note, the task status information corresponding to the final payment task in the target virtual node can be updated to "Completed," and the payment amount and time can be recorded. Furthermore, if the transfer note contains the target virtual node's number, the system can automatically match the target virtual node corresponding to that number; if the transfer note does not contain the aforementioned number, the system can match the real-name authentication information of the transferring account with the name and other information in the virtual node to associate it with the corresponding target virtual node.

[0047] In this embodiment, after updating the task status information in the target virtual node, the task status information can also be synchronized with the first user. As an example, during the task's active period, when any second user completes a task, a task completion notification can be pushed to the first user, see [link to relevant documentation]. Figure 10 As shown in reference number 1001. Optionally, this notification may include, but is not limited to, information such as the virtual node's number, task type, completion time, and security verification result. The first user can click on this notification to jump to the task details page and view the second user's information and task credentials.

[0048] Optionally, if a security anomaly is triggered during task execution, such as an abnormal payment amount or an unfamiliar check-in device, an anomaly warning notification can be pushed to the first user, along with an analysis of the cause of the anomaly, such as "Node 05's payment amount of 45 yuan does not match the final payment of 50 yuan". The first user can initiate a secondary verification with one click and push verification requests to members.

[0049] The method provided in the above embodiments of this application, after receiving task participant information and task description information sent by the first user in the group, creates virtual nodes corresponding to each task participant based on the task participant information and task description information. The virtual nodes include the task status information and task parameters of the task. After receiving a confirmation message from the second user in the group regarding the target virtual node, the method issues the task to the second user based on the task parameters in the target virtual node. Finally, based on the task execution result of the second user, the method updates the task status information in the target virtual node and synchronizes the task status information with the first user. In the above process, by creating virtual nodes, the organizer's preliminary work of manually entering information is eliminated, errors introduced by manual operation are eliminated, and an accurate data foundation is provided for subsequent processes. By introducing a mechanism for group members to confirm information regarding virtual nodes, group members can be accurately associated with task parameters, eliminating the need for the organizer to manually call out names and verify identities, ensuring that tasks are accurately distributed to the correct group members, and improving the accuracy of task processing. By automatically monitoring the task execution status and synchronizing the task status to the first user, the organizer's process of manually calculating the task status is eliminated, enabling the organizer to grasp the progress of the entire task in real time and achieving automated task management.

[0050] In some optional embodiments, step 102 above may include the following sub-steps: Sub-step 1021 involves using Optical Character Recognition (OCR) technology to identify the information of the task participants and obtain structured data.

[0051] Specifically, after receiving the task participant information and task description information, an OCR recognition task can be created. This task processes the received task participant information using OCR, extracting the ID, name, and final payment amount fields. This information is then broken down to establish corresponding relationships and form structured data. An example of the structured data format is: {"ID": "01", "Name": "Zhang San", "Final Payment Amount": "50 Yuan", "Mobile Number": "166", "Binding Status": "0-Unbound / 1-Binded", "Group Nickname": "**", ...}. Field matching algorithms, such as keywords like "ID" and "Name", can be used to locate specific fields to ensure accurate information extraction.

[0052] It should be noted that if recognition fails, such as due to a blurry screenshot or incomplete text, an error message will be returned to the first user, prompting them to re-upload clear task participant information, such as a clear screenshot.

[0053] Sub-step 1022: Determine the task type based on the task description information.

[0054] Specifically, the task description information is first analyzed, and the task intent of the first user is understood through natural language processing technology to obtain the task type. For example, the task type is extracted as "payment task" from "Please pay the balance of the activity".

[0055] Sub-step 1023: Based on structured data and task type, create virtual nodes corresponding to each task participant.

[0056] Specifically, a virtual node can be created for each structured data record, following the rule of one virtual node per task participant. Then, based on the task type, relevant fields are extracted from the structured data and populated into the task parameters of the virtual node; for example, the outstanding payment amount is entered as the pending payment amount. Finally, task status information is initialized.

[0057] Optionally, based on the task description information, a task result summary and output task can also be created. Task result summary and output tasks may include, but are not limited to, information confirmation tasks, online check-in tasks, and final payment tasks. Information confirmation tasks are used to instruct group members to confirm their personal information, specify their assigned number, and provide feedback on the results. Online check-in tasks are used to periodically send check-in and check-out notifications, enabling one-click check-in and synchronization. Final payment tasks are used to periodically send final payment notifications, status updates, and payment access information.

[0058] By employing OCR technology to convert task participant information into structured data, the workload of manual data entry by the first user is eliminated, while avoiding potential errors from manual input and providing high-quality data input for subsequent processing. Furthermore, specific participants and parameters are extracted from the structured data, and the task type and overall requirements are determined from the task description information. These two elements together constitute the complete data for each virtual node, ensuring that each virtual node contains all the information needed to execute the task and remains consistent with the first user's intent, providing a reliable data foundation for subsequent task assignment and execution.

[0059] In some optional embodiments, after performing step 102, a virtual node update operation can also be performed if the virtual node update conditions are met. The virtual node update conditions include at least one of the following: a first user modifies task participant information, at least one second user changes their identity information, task parameters change, virtual node association conflicts occur, at least one second user leaves the group or task, the task is paused or canceled, the virtual node creation method changes, or at least one second user's account is abnormal. The virtual node update operation includes at least one of the following: modifying task parameters in at least one virtual node, adding at least one virtual node, or marking at least one virtual node as invalid. Specific scenarios may include, but are not limited to, the following: The first user modifies task participant information, such as adding / deleting task participants or adjusting payment amounts. Triggering conditions may include, but are not limited to: the first user editing virtual node information in the task management interface, uploading new task participant information, or manually entering modified content. The process is as follows: First, permission verification: Verify if the operator is the first user. If not, the process is blocked and a permission denied message is displayed. Second, information comparison: If new task participant information is uploaded, it is identified and compared with the original information, marking differences. For example, "The final payment amount for participant number 03 has been changed from 50 yuan to 60 yuan," or "New member number 08, Li Si," etc. If manually modified, the modified fields are directly marked. Fourth, node update: For changes to payment amounts or names, the corresponding virtual node's task parameter attributes or task participant identity information can be directly updated. For new task participants, a new virtual node can be generated according to the initial creation rules, automatically assigned a new virtual node identifier, associated with the current group's identifier, and its task status information initialized. For deleted task participants, the task status information in the corresponding virtual node is marked as "invalid," and their information is hidden in the second user's virtual node query interface, but the group owner retains viewing access for subsequent verification. Fifth step, notification synchronization. Push virtual node information update notifications to the second user, clearly indicating the changes, such as "The final payment amount for number 03 has been adjusted to 60 yuan; please reconfirm the association information." If a new second user is involved, trigger an association reminder by individually @ing the new member. Sixth step, targeted push. Only push virtual node association reminders to new members to avoid disturbing existing second users. Simultaneously, the new virtual node is specially marked in the first user's virtual node query interface, indicating that it needs to be associated.

[0060] At least one second user's identity information has changed, such as a change in group nickname or an update of real-name authentication information. Triggering conditions may include, but are not limited to: the second user modifying their identity information in their personal center, or the system detecting a change in the second user's account identifier, such as their phone number or WeChat ID. The processing steps are as follows: First, identity matching. The system associates the new identity information with the task participant's identity information within the virtual node by linking the old account identifier to the associated virtual node. Second, association update. If only the nickname has changed, the system directly updates the task participant's name field in the virtual node, retaining the original ID and association relationship; if the account identifier has changed, an identity change credential containing the old and new account association records is generated and synchronized to the virtual node to ensure that subsequent task operations can still match the original virtual node. Third, verification notification. A confirmation notification indicating that the identity information has been synchronized to the virtual node is pushed to the second user, and a reminder of the second user's identity change is pushed to the first user.

[0061] Task parameter changes, such as extending check-in time or modifying payment deadlines, can be triggered by various factors, including but not limited to: the first user modifying the task time in the task management interface or receiving a task adjustment request from the first user. The process is as follows: First, parameter synchronization. Directly update the task parameters of all virtual nodes, such as changing the payment deadline from 2025-09-10 to 2025-09-12, and add a parameter change record to the virtual node, including the value before the change, the value after the change, and the reason for the change. Second, status adaptation. If a second user has already completed the task before the adjustment, and some members have already paid, their task status information will be retained as completed, and the new parameters will only apply to virtual nodes with incomplete tasks; if the check-in time is extended, the "in progress" duration of the virtual node's task status information will be automatically extended. Third, notification to all members. Push notifications for task parameter adjustments via both group announcements and private messages, clearly stating the new parameters and effective time to prevent members from experiencing task delays due to information lag. Fourth, tiered notification. The first step involves sending a notification to the second user who hasn't paid, including both the original and new amounts, to adjust the final payment. The second user who has already paid will receive a notification to pay the difference. The fifth step adds time overlap verification. If the adjusted check-in time overlaps with other group task times, a time conflict notification will be sent to the first user, suggesting an adjustment to the time slot. The sixth step adds overdue task activation. If the payment deadline is extended, the payment entry point on the virtual node will be automatically activated for the second user who has not paid by the deadline, and a payment extension notification with the new deadline will be sent.

[0062] Virtual node association conflicts, such as multiple virtual nodes associated by the same second user, or duplicate virtual node numbers, can occur. Triggering conditions may include, but are not limited to, detecting conflicts during virtual node creation or association, such as OCR errors leading to duplicate numbers, or a second user mistakenly associating another user's virtual node. The handling process is as follows: First, conflict detection. Conflicts are identified in real-time through unique verification of virtual node numbers and one-to-one association verification between the second user account and the virtual node. Second, conflict resolution. For duplicate virtual node numbers: a new number is automatically assigned to the later-created virtual node, in the format of the original number + suffix, such as 03-1, and the first user is notified to modify the corresponding number in the task participant list, synchronously updating the information in the virtual node. For multiple virtual nodes associated by the same second user, a conflict reminder is pushed to the second user, displaying information about the already associated virtual nodes and the virtual nodes to be associated, guiding them to select the correct virtual node; simultaneously, incorrectly associated virtual nodes are automatically unbound, preserving the correct association. Third, log retention. All conflict handling processes are recorded in the virtual node operation log for the first user to review later. Fourth, handling conflicts that cannot be automatically resolved. If a complex conflict is detected, such as two virtual nodes associated with the same second user both having payment records, a manual intervention process will be automatically triggered. A conflict resolution work order will be pushed to the first user, which includes details of the conflicting nodes, suggested solutions, etc. The first user can manually choose to keep the virtual nodes and simultaneously perform unbinding and data merging.

[0063] At least one second user leaves the group or task. Triggering conditions may include, but are not limited to: the second user leaving the group before or after the task is completed, or actively submitting a task exit request. The process is as follows: First, status determination. First, determine the task status information of the virtual node associated with the second user. If the task status information is "completed," mark the virtual node as "archived," retain all task records for the first user to check later, and hide the virtual node on the second user's end. If the task status information is incomplete, mark the virtual node as "exited - pending processing," and push a notification to the first user that the second user has exited, including the node number and the incomplete task item. Second, task linkage. If payment is not completed, automatically cancel the second user's payment task and remove the pending payment amount from the virtual node in the group payment statistics. If check-in is not completed, mark the second user as "exited" in the check-in list to avoid the first user's mistaken check. Third, notification synchronization. Send a task exit confirmation notification to the second user who has exited, which includes details of completed and / or incomplete tasks. Send a task handling suggestion to the first user who has exited the second user, such as whether a second user needs to be recruited to fill the gap.

[0064] Task paused or canceled. Triggering conditions may include, but are not limited to: the first user triggering task cancellation or pause in the task management interface, and selecting the reason for cancellation or pause, such as weather reasons, insufficient participants, etc. The processing is as follows: First, update the status of all nodes. If the task is canceled, all virtual nodes are marked as "Task canceled - terminated", and unfinished task items are automatically cleared, such as canceled payment tasks, check-in tasks, etc. If the task is paused, the task status information in all virtual nodes is frozen to the current status, such as "Associated - Paid", and the check-in or payment entry is hidden, to be unlocked after the first user resumes the task. Second, process paid members. If the task is canceled and some second users have paid the balance, a refund list is automatically generated and pushed to the first user's end, supporting the first user to initiate batch refunds with one click, and the refund status is synchronized to the virtual nodes, such as pending refund or refunded. Third, notify all members. Task cancellation or pause notification is pushed through group announcements and private messages, clarifying the reason and subsequent arrangements, such as refund time, re-registration time, etc., and providing an entry to query the current status of virtual nodes.

[0065] The method for creating virtual nodes has changed. Triggering conditions may include, but are not limited to: previously, the principle was one virtual node per secondary user; now, it's one virtual node per natural person. For example, if a member has family members and their attendance or payment status needs to be tracked separately, a single virtual node needs to be split into two or more. The process is as follows: First, rule verification. If virtual node splitting is allowed by default during creation, the operation is permitted; otherwise, a prompt will appear indicating that the rules need to be modified and updated before execution. Second, splitting and generation. The first user selects the virtual node to be split, such as number 01, and enters the information for the new virtual node after splitting, such as number 01-1, name "Zhang San (family member)", and final payment amount of 50 yuan. This generates two virtual nodes, both associated with the current group. Third, data synchronization. The association status and task status information of the original virtual node remain unchanged after splitting. The association status information of the new virtual node is "Not associated - Split and added". A notification about the new node association is pushed to the family member, and a notification about the virtual node splitting is pushed to the original secondary user.

[0066] At least one second user's account is abnormal. Triggering conditions may include, but are not limited to: the second user's account being frozen or retrieved after creation, preventing the association of virtual nodes. The process is as follows: First, status marking. After detecting an account abnormality through the group interface, the corresponding virtual node is marked as "Account Abnormal - Pending Unlocking," hiding the association entry. Second, notifying the first user. A notification about the second user's account abnormality is pushed to the first user, including the virtual node's number, abnormality type, etc., and a temporary unbinding option is provided. For example, if the account is frozen for more than 24 hours, the node can be unbound for other second users to associate. Third, account recovery. After the account is retrieved, the abnormal mark on the virtual node is automatically removed, and a notification that the virtual node can be re-associated is pushed to the second user, retaining the virtual node information from creation, such as the number and name.

[0067] It should be noted that after all virtual node update operations are completed, they can be synchronized to the task management interface on the first user's end and the virtual node query interface on each second user's end, ensuring that the node information seen by all parties is consistent. In addition, the three most recent update records for each virtual node can be retained, including update time, update content, and operator, and both the first and second users can view historical versions to avoid information loss. Furthermore, if a system anomaly occurs during the update process, such as network interruption or data error, the system can automatically roll back to the virtual node state before the update and push an update anomaly notification to the first user, guiding them to repeat the operation.

[0068] It is understandable that during the execution of temporary group tasks, factors such as participant information and task requirements frequently change. Traditional static management methods cannot adapt to this dynamic nature. This application's embodiments establish comprehensive processing logic for different scenarios, ensuring that any changes are captured promptly and trigger corresponding virtual node update operations. This comprehensive monitoring mechanism guarantees that virtual nodes always reflect the latest actual situation, providing data assurance for accurate task management. Furthermore, the processing flow for various change scenarios is automated. The first user only needs to trigger a change or confirm the system suggestion; subsequent node updates, status synchronization, and notification pushes are all automatically completed by the system, significantly improving management efficiency while reducing human error.

[0069] In some optional embodiments, step 103 above may include the following sub-steps: Sub-step 1031: After receiving the information confirmation message from the second user in the group regarding the target virtual node, the second user is authenticated. The authentication includes at least one of the following: generating a verification question based on the information in the task participant information, and performing a question-and-answer verification on the second user based on the verification question; sending a verification code to the second user's pre-stored contact information for verification; and verifying whether the second user's time in the group meets the time requirement.

[0070] Sub-step 1032: If the authentication is successful, the second user is associated with the target virtual node, and a task is sent to the second user based on the task parameters in the target virtual node.

[0071] As an example, non-sensitive task information from the registration can be automatically extracted to generate verification questions, such as "What is the meeting point you registered for?" and "How many people are traveling with you?". The second user needs to enter the same answer as during registration. The correct answer can be generated by parsing the task participant information or provided by the first user. If the verification accuracy is ≥80%, step 1032 can be executed.

[0072] As another example, a 6-digit dynamic verification code can be sent to the mobile phone number reserved by the second user when registering, and the duration of the second user's current account in the group can be verified. After both are verified, step 1032 can be executed.

[0073] It should be noted that if the verification fails a set number of times consecutively, such as three consecutive failures, the associated entry point can be automatically locked for a specified duration, such as 15 minutes. Simultaneously, an identity verification anomaly alert will be sent to the first user; for example, only the node number can be displayed to avoid exposing the privacy of the second user. The first user must manually unlock the entry, or the second user must contact the first user for assistance with verification.

[0074] Through a multi-level authentication mechanism, unauthorized access and identity theft are effectively prevented, ensuring that tasks are accurately assigned to the correct executors and guaranteeing the accuracy and security of task assignment.

[0075] In some optional embodiments, after associating the second user with the target virtual node, the following operations may also be performed: initializing the trust value of the second user; adjusting the trust value based on the second user's task completion status; and updating the authentication method for the second user according to the adjusted trust value.

[0076] The trust score refers to the credit rating assigned to the second user based on their information, used to quantitatively assess the credibility of the user's behavior. Task completion status may include, but is not limited to, the quality, accuracy, timeliness of task completion, and behavioral data.

[0077] As an example, the initial trust value can be set to 60. Completing a task without any issues increases the trust value by 20 points. Matching the payment amount with the pending payment amount in the task parameters of the target virtual node increases the trust value by 20 points, with no further increases after reaching a maximum of 200 points. If a task execution error occurs, such as a mismatched payment amount or an unfamiliar check-in device, the trust value decreases by 30 points.

[0078] In addition, for high-frequency operations, such as initiating at least 3 consecutive unassociation and reassociation operations within a short period of time, it is judged as abnormal, the trust value is reduced by 50 points, the target virtual node is frozen for 30 minutes and the first user is notified. If the second user's account is marked as a risk account, such as if the account is stolen and a complaint is filed, the status of the target virtual node will be automatically set to risk lock, the trust value will be reduced by 100, and the second user's task execution permission will be suspended until the first user verifies the account security and then unlocks it.

[0079] If the trust score is greater than or equal to 80, the second user is considered highly trustworthy, and subsequent tasks only require basic verification of the second user, such as verifying only the time for check-in and only the amount for payment. If the trust score is greater than or equal to 60 but less than 80, identity verification can be performed when the second user performs critical tasks such as payment, such as through SMS verification codes. If the trust score is less than 60, all operations of the second user require not only identity verification but also confirmation from the first user, and their unbinding privileges are frozen to prevent untraceability after a risky account is unbound.

[0080] If the trust value drops to 0, the association between the second user and the target virtual node will be automatically terminated, the task permissions of the target virtual node will be frozen, and a high-risk account alert will be sent to the first user, such as "This account has attempted to associate from Beijing and Shanghai within 30 minutes". The account can only be restored after the first user manually verifies the information.

[0081] Traditional identity verification systems use a uniform standard for all users, failing to reflect individual differences. This implementation initializes a trust value immediately after a user's successful association, comprehensively considering multiple factors such as group membership duration and real-name authentication status to establish a personalized trust benchmark for each user. By monitoring task completion, it ensures that the trust value accurately reflects the user's current trust status, overcoming the subjectivity and lag in trust assessment in traditional systems. For high-trust users, cumbersome verification steps are eliminated, significantly improving the efficiency of second-user operations; for low-trust users, enhanced verification is implemented, effectively controlling security risks.

[0082] In some optional embodiments, the task includes a payment task, the target virtual node includes task participant identity information, and the task parameters include the amount to be paid. Task participant identity information refers to data stored in the virtual node used to identify the task participant, and may include name, ID, mobile phone number, etc. Step 104 above, which updates the task status information in the target virtual node based on the second user's task execution result, further includes: Sub-step 1041: Obtain the second user's payment information, which includes the payer's identity information and the payment amount. The payer's identity information refers to the payer's information in the payment transaction record, such as the real-name authentication name and account name.

[0083] Sub-step 1042: Match the payment information with the identity information of the task participants, and match the payment amount with the amount to be paid to obtain the matching result.

[0084] Sub-step 1043: Based on the matching results, update the task status information in the target virtual node.

[0085] Specifically, if the payment information matches the task participant's identity information and the payment amount matches the amount to be paid, the task status information in the target virtual node can be updated to "Completed". If the payment information matches the task participant's identity information and the payment amount does not match the amount to be paid, the task status information in the target virtual node can be updated to "Payment Anomaly - Amount Mismatch", a price difference reminder will be pushed to the second user, and an anomaly handling notification will be pushed to the first user. If the payment information does not match the task participant's identity information but the payment amount matches the amount to be paid, the task status information in the target virtual node can be temporarily left unupdated, and an identity confirmation notification will be pushed to the first user. If the payment information does not match the task participant's identity information and the payment amount does not match the amount to be paid, the task status information in the target virtual node can be left unupdated, and an alarm notification will be pushed to the first user for verification.

[0086] By establishing an automated payment information collection, matching, and status update mechanism, the entire payment task processing process has been automated and made more accurate. This has completely solved the problem of manual verification in group payment management, significantly improved the efficiency and accuracy of payment statistics, and provided reliable payment processing capabilities for the group task management system.

[0087] In some optional embodiments, after synchronizing the task status information with the first user, the following operations can also be performed: generating task status statistics based on the task status information in each virtual node; and sending the task status statistics to the first user. The task status statistics refer to information generated based on virtual node status data, which visually displays the overall progress of the task. The task status statistics may include, but are not limited to, at least one of the following: number of participants who have checked in, number of participants who have not checked in, number of participants who have paid the final payment, number of participants who have not paid the final payment, and total amount paid. See also, as an example. Figure 11 As shown in the reference number 1011.

[0088] Furthermore, the task status of each virtual node can be displayed in list or chart format, allowing the group owner to quickly grasp the overall situation. Once a task ends, the status of all virtual nodes can be automatically locked, prohibiting further binding, check-in, and payment operations. For nodes that have not completed their tasks, a reminder list can be generated and pushed to the primary user. The deadline can be set by the primary user or automatically triggered by the default activity schedule.

[0089] Furthermore, during the information synchronization process, issues such as synchronization delay and network instability may arise. Synchronization delay refers to insufficient network bandwidth or peak server load causing the synchronization time to exceed a threshold. Network instability can lead to network interruptions, resulting in data transmission failure or loss. To address these issues, the following measures can be taken: First, dual-channel data transmission. Prioritize the primary channel for data transmission; if the primary channel disconnects or the delay exceeds a threshold, data will be transmitted via a backup channel. Second, when the network signal is weak, encrypt and cache data locally; automatically re-transmit it once the network signal improves. Third, remind the first user of the synchronization time elapsed, using different colors to indicate the duration. Once a certain threshold is exceeded, a reminder will be pushed to the first user to prompt them to refresh. Fourth, set a priority queue. Prioritize data to be synchronized according to task importance. Fifth, compare server and client data at set intervals to automatically calibrate and synchronize data. If calibration fails, trigger manual synchronization by the first user.

[0090] This enables visualized, real-time, and refined management of group task progress, completely freeing the primary user from tedious information organization work, significantly improving the efficiency and quality of task management, and providing powerful situational awareness and decision support capabilities for the group task management system.

[0091] In some optional embodiments, if a message from a second user to unassociate a target virtual node is received, the association between the two users can be severed after the second user's authentication is successful, and the first user is simultaneously notified, while resetting the association status information of the target virtual node. At the same time, task records prior to unbinding can be retained for data recovery after subsequent rebinding.

[0092] Please refer to Figure 12 This illustrates one of the flowcharts of a task processing method provided in an embodiment of this application. The task processing method provided in this embodiment can be applied to the user terminal of a first user.

[0093] The task processing method provided in this application includes the following steps: Step 1201: Receive the first input from the first user.

[0094] In this embodiment, the first user refers to a user with specific permissions in the group, such as the group owner or administrator, who can be responsible for initiating and monitoring tasks.

[0095] The first input can be used to trigger the acquisition of task participant information and task description information. The first input can be touch input, voice command, a specific gesture input by the user, or other feasible input methods; the specific method can be determined according to actual usage needs, and this application embodiment does not limit it. The specific gesture in this application embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture. The click input in this application embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input.

[0096] Step 1202: In response to the first input, obtain task participant information and task description information.

[0097] In this embodiment, in response to the first input, task participant information and task description information can be obtained. The task participant information and task description information can be found in the descriptions of the above embodiments, and will not be repeated here to avoid repetition.

[0098] In some optional implementations of this embodiment, step 1201 may include: receiving a first input from a first user to the group chat interface, wherein the first input includes keyword instructions. Step 1202 may include: in response to the first input, obtaining a target message sent by the first user in the group chat interface, identifying the target message as task participant information, identifying the keyword instructions as task description information, wherein the target message includes at least one of the following: an image or a file.

[0099] Keyword commands can be messages with a specific format, such as "@everyone [Task: XX]". For example, the first user can trigger the automatic task management function by entering a keyword command, such as "@everyone [Task: Final Payment]", in the group chat interface. At this time, the electronic device used by the first user can automatically associate it with recently sent target messages, such as images or files, and use them as task participant information. Simultaneously, the aforementioned keyword command can be used as task description information. Finally, the task participant information and task description information can be uploaded.

[0100] In some optional implementations of this embodiment, step 1201 may include: receiving a first input from the first user to the task function control in the group chat interface. Step 1202 may include: in response to the first input, displaying a new task interface, which includes a task intent keyword input control and a resource upload function control; receiving a second input from the user to the task intent keyword input control; in response to the second input, obtaining task description information; receiving a third input from the user to the resource upload function control; and in response to the third input, obtaining task participant information.

[0101] The second input can be used to trigger the acquisition of task description information, and the third input can be used to trigger the acquisition of task participant information. The second and third inputs can be touch input, voice commands, specific gestures input by the user, or other feasible inputs. The specific inputs can be determined according to actual usage needs, and this application embodiment does not limit them.

[0102] As an example, the group chat interface of the electronic device used by the first user can display task function controls, see [link to example]. Figure 2 Number 201. When the first user clicks this task function control, the new task interface will be displayed. See [link / reference]. Figure 3 As shown. The new task interface may include a task intent keyword input control 301 and a resource upload function control 302. The task intent keyword input control 301 may include prompts to prompt the user to upload task participant information and enter task intent keywords, which can serve as task description information. The resource upload function control 302 provides the upload method or type for task participant information. When the first user uploads task participant information and clicks the "Send" control, a task creation request is triggered. In addition, the new task interface may also support selecting key information fragments from the current dialogue record as task description information, as shown in label 303.

[0103] In some optional implementations of this embodiment, step 1201 may include: receiving a first input of a target resource, wherein the target resource includes at least one of the following: an image or a file. Step 1202 may include: responding to the first input, using the target resource as task participant information; obtaining task description information from a message sent by the first user in the group chat interface; or displaying a task addition prompt and receiving task description information input by the first user based on the task addition prompt.

[0104] Specifically, when the first user performs an operation on target resources such as images and files, the automatic task management function can be automatically triggered, using the target resource as task participant information, and prompting the user to select or enter task description information.

[0105] As an example, see Figure 4 When the first user selects a resource from the album or files, a prompt message as shown in label 401 can be displayed to prompt the user to enable intelligent task management. After the first user clicks on this prompt message, they can be further prompted to add task description information. After the first user adds task description information, such as "Pay the final payment," the automatic task management function can be triggered, and the resource selected by the first user will be used as task participant information. The task participant information and task description information will then be uploaded.

[0106] As yet another example, see Figure 5When the first user sends images, files, or other resources in the group chat interface, a prompt message as shown in label 501 can be triggered. After the first user clicks on this prompt message, the system automatically associates it with the messages the first user recently sent in the group chat to obtain the task description information. Then, the resource selected by the first user can be used as task participant information, and the task participant information and task description information can be uploaded.

[0107] In some optional implementations of this embodiment, see [link to relevant documentation]. Figure 6 The first user can select one or more message records containing task participant information and task description information in the group chat interface through multi-selection. Then, a specific triggering method can be used to activate the automatic task management function, thereby uploading the task participant information and task description information. The aforementioned specific triggering method includes, but is not limited to, specific gestures.

[0108] Step 1203: Send task participant information and task description information to the server so that the server can create virtual nodes corresponding to each task participant based on the task participant information and task description information, and issue tasks to the second user after receiving the information confirmation message from the second user in the group for the target virtual node.

[0109] In this embodiment, the operation of the server can be referred to the description in the above embodiments, and will not be repeated here to avoid repetition.

[0110] Step 1204: Receive the task status information of the second user sent by the server and display the task status information.

[0111] In this embodiment, the process of generating task status information can be referred to the description in the above embodiments, and will not be repeated here to avoid repetition.

[0112] In some optional implementations of this embodiment, at least one of the following may also be performed: Step 1205: Receive and display the task status statistics information sent by the server. The task status statistics information is generated based on the task status information in each virtual node.

[0113] Task status statistics refer to information generated based on virtual node status data, which visually displays the overall progress of the task. Task status statistics may include, but are not limited to, at least one of the following: number of participants who have checked in, number of participants who have not checked in, number of participants who have paid the final payment, number of participants who have not paid the final payment, and total amount paid. See [example example]. Figure 11 As shown in the reference number 1011.

[0114] Step 1206: Receive and display the task exception notification sent by the server. The task exception notification is generated based on the task execution result of the second user.

[0115] Specifically, the task status of each virtual node can be displayed in list or chart format, allowing the primary user to quickly grasp the overall situation. Once the task ends, the status of all virtual nodes can be automatically locked, preventing further binding, check-in, and payment operations; for nodes that have not completed their tasks, a task exception notification can be displayed. The deadline can be set by the primary user or automatically triggered by default according to the activity's scheduled time.

[0116] Step 1207: Receive and display the virtual node update notification sent by the server. The virtual node update notification is triggered based on virtual node update conditions, which include at least one of the following: modification of task participant information, change of second user identity information, change of task parameters, virtual node association conflict, second user leaving the group or task, or task paused or canceled. The above virtual node update conditions can be found in the description of the above embodiments; to avoid repetition, they will not be repeated here.

[0117] In this embodiment, after receiving the first input from the first user, the task participant information and task description information are first obtained. Then, the task participant information and task description information are sent to the server so that the server can create virtual nodes corresponding to each task participant based on the task participant information and task description information. After receiving the information confirmation message from the second user in the group regarding the target virtual node, the server issues the task to the second user. After receiving the task status information of the second user sent by the server, the task status is displayed. In the above process, the organizer's preliminary work of manually entering information is eliminated, errors introduced by manual operation are eliminated, and an accurate data foundation is provided for subsequent processes. By introducing a mechanism for group members to confirm information regarding virtual nodes, group members can be accurately associated with task parameters, eliminating the need for the organizer to manually call out names and verify identities, ensuring that tasks are accurately distributed to the correct group members and improving the accuracy of task processing. By automatically monitoring the task execution status and synchronizing the task status to the first user, the organizer's process of manually calculating the task status is eliminated, allowing the organizer to grasp the progress of the entire task in real time and realize automated task management.

[0118] It should be noted that the task processing method provided in this application embodiment can be executed by a task processing device. This application embodiment uses the execution of the task processing method by a task processing device as an example to illustrate the task processing device provided in this application embodiment.

[0119] like Figure 13As shown, the task processing device 1300 of this embodiment includes: a receiving unit 1301, used to receive task participant information and task description information sent by a first user in a group; a creation unit 1302, used to create virtual nodes corresponding to each task participant based on the task participant information and the task description information, wherein the virtual nodes include task status information and task parameters; a sending unit 1303, used to send a task to the second user based on the task parameters in the target virtual node after receiving an information confirmation message from the second user in the group regarding the target virtual node; and a synchronization unit 1304, used to update the task status information in the target virtual node based on the task execution result of the second user, and synchronize the task status information to the first user.

[0120] In some optional implementations of this embodiment, the creation unit 1302 is further configured to: identify the task participant information using optical character recognition technology to obtain structured data; determine the task type based on the task description information; and create virtual nodes corresponding to each task participant based on the structured data and the task type.

[0121] In some optional implementations of this embodiment, the device further includes an update unit, configured to: perform a virtual node update operation when virtual node update conditions are met; wherein the virtual node update conditions include at least one of the following: the first user modifies the task participant information, the identity information of at least one second user changes, the task parameters change, virtual node association conflict occurs, at least one second user leaves the group or task, the task is paused or canceled, the virtual node creation method changes, or at least one second user's account is abnormal; the virtual node update operation includes at least one of the following: modifying the task parameters in at least one virtual node, adding at least one virtual node, or marking at least one virtual node as invalid.

[0122] In some optional implementations of this embodiment, the sending unit 1303 is further configured to: after receiving the information confirmation message from the second user in the group regarding the target virtual node, authenticate the second user, the authentication including at least one of the following: generating a verification question based on the information in the task participant information, performing a question-and-answer verification on the second user based on the verification question; sending a verification code to the contact information pre-stored by the second user for verification; verifying whether the second user's time in the group meets the time requirement; and if the authentication is successful, associating the second user with the target virtual node, and issuing a task to the second user based on the task parameters in the target virtual node.

[0123] In some optional implementations of this embodiment, the device further includes an adjustment unit, configured to: initialize the trust value of the second user; adjust the trust value based on the task completion status of the second user; and update the authentication method for the second user according to the adjusted trust value.

[0124] In some optional implementations of this embodiment, the task includes a payment task, the target virtual node includes task participant identity information, and the task parameters include an amount to be paid; the synchronization unit 1304 is further configured to: obtain the payment information of the second user, the payment information including payer identity information and payment amount; match the payment information with the task participant identity information, and match the payment amount with the amount to be paid to obtain a matching result; and update the task status information in the target virtual node based on the matching result.

[0125] In some optional implementations of this embodiment, the device further includes a sending unit, configured to: generate task status statistics based on task status information in each virtual node; and send the task status statistics to the first user.

[0126] The apparatus provided in the above embodiments of this application, by creating virtual nodes, eliminates the organizer's preliminary work of manually entering information, eliminates errors introduced by manual operation, and provides an accurate data foundation for subsequent processes. By introducing a mechanism for group members to confirm information about virtual nodes, group members can be accurately associated with task parameters, eliminating the need for organizers to manually take attendance and verify identities, ensuring that tasks are accurately distributed to the correct group members, and improving the accuracy of task processing. By automatically monitoring task execution and synchronizing task status to the first user, the process of organizers manually compiling task status is eliminated, allowing organizers to grasp the progress of the entire task in real time and achieving automated task management.

[0127] like Figure 14 As shown, the task processing device 1400 of this embodiment includes: a receiving unit 1401, used to receive a first input from a first user; an acquiring unit 1402, used to acquire task participant information and task description information in response to the first input; a sending unit 1403, used to send the task participant information and the task description information to a server, so that the server creates virtual nodes corresponding to each task participant based on the task participant information and the task description information, and sends a task to the second user after receiving an information confirmation message from the second user in the group for the target virtual node; and a display unit 1404, used to receive the task status information of the second user sent by the server, and display the task status information.

[0128] In some optional implementations of this embodiment, the receiving unit 1401 is further configured to: receive a first input from a first user to the group chat interface, the first input including keyword instructions; the obtaining unit 1402 is further configured to: in response to the first input, obtain a target message sent by the first user in the group chat interface, determine the target message as the task participant information, determine the keyword instructions as the task description information, and the target message includes at least one of the following: an image or a file.

[0129] In some optional implementations of this embodiment, the receiving unit 1401 is further configured to: receive a first input from a first user to the task function control in the group chat interface; the obtaining unit 1402 is further configured to: in response to the first input, display a new task interface, the new task interface including a task intent keyword input control and a resource upload function control; receive a second input from the user to the task intent keyword input control; in response to the second input, obtain the task description information; receive a third input from the user to the resource upload function control; and in response to the third input, obtain the task participant information.

[0130] In some optional implementations of this embodiment, the receiving unit 1401 is further configured to: receive a first input of a target resource, the target resource including at least one of the following: an image, a file; the obtaining unit 1402 is further configured to: in response to the first input, use the target resource as task participant information; obtain the task description information from the message sent by the first user in the group chat interface, or display a task addition prompt and receive the task description information input by the first user based on the task addition prompt.

[0131] In some optional implementations of this embodiment, the display unit is further configured to perform at least one of the following: receiving task status statistics sent by the server and displaying the task status statistics, wherein the task status statistics are generated based on the task status information in each virtual node; receiving a task exception notification sent by the server and displaying the task exception notification, wherein the task exception notification is generated based on the task execution result of the second user; receiving a virtual node update notification sent by the server and displaying the virtual node update notification, wherein the virtual node update notification is triggered based on virtual node update conditions, wherein the virtual node update conditions include at least one of the following: modification of task participant information, change of second user identity information, change of task parameters, virtual node association conflict, second user leaving the group or task, task paused or canceled.

[0132] In this embodiment, after receiving the first input from the first user, the task participant information and task description information are first obtained. Then, the task participant information and task description information are sent to the server so that the server can create virtual nodes corresponding to each task participant based on the task participant information and task description information. After receiving the information confirmation message from the second user in the group regarding the target virtual node, the server issues the task to the second user. After receiving the task status information of the second user sent by the server, the task status is displayed. In the above process, the organizer's preliminary work of manually entering information is eliminated, errors introduced by manual operation are eliminated, and an accurate data foundation is provided for subsequent processes. By introducing a mechanism for group members to confirm information regarding virtual nodes, group members can be accurately associated with task parameters, eliminating the need for the organizer to manually call out names and verify identities, ensuring that tasks are accurately distributed to the correct group members and improving the accuracy of task processing. By automatically monitoring the task execution status and synchronizing the task status to the first user, the organizer's process of manually calculating the task status is eliminated, allowing the organizer to grasp the progress of the entire task in real time and realize automated task management.

[0133] The task processing device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0134] The task processing device in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0135] The task processing device provided in this application embodiment can achieve... Figure 1 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0136] Optionally, such as Figure 15 As shown, this application embodiment also provides an electronic device 1500, including a processor 1501 and a memory 1502. The memory 1502 stores a program or instructions that can run on the processor 1501. When the program or instructions are executed by the processor 1501, they implement the various steps of the above-described task processing method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0137] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0138] Figure 16 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application. The electronic device 1600 includes, but is not limited to, components such as: radio frequency unit 1601, network module 1602, audio output unit 1603, input unit 1604, sensor 1605, display unit 1606, user input unit 1607, interface unit 1608, memory 1609, and processor 1610.

[0139] Those skilled in the art will understand that the electronic device 1600 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1610 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 16 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here. The processor 1610 is configured to receive task participant information and task description information sent by a first user in the group; create virtual nodes corresponding to each task participant based on the task participant information and task description information, wherein the virtual nodes include task status information and task parameters; after receiving a confirmation message from a second user in the group regarding a target virtual node, issue a task to the second user based on the task parameters in the target virtual node; update the task status information in the target virtual node based on the task execution result of the second user, and synchronize the task status information with the first user.

[0140] By creating virtual nodes, organizers are spared the preliminary work of manually entering information, eliminating errors introduced by manual operation and providing an accurate data foundation for subsequent processes. By introducing a mechanism for group members to confirm information about virtual nodes, group members can be precisely associated with task parameters, eliminating the need for organizers to manually take attendance and verify identities, ensuring tasks are accurately distributed to the correct group members and improving task processing accuracy. By automatically monitoring task execution and synchronizing task status to the primary user, organizers are freed from manually compiling task status statistics, enabling them to monitor the entire task's progress in real time and achieving automated task management.

[0141] In some optional implementations of this embodiment, the processor 1610 is further configured to identify the task participant information using optical character recognition technology to obtain structured data; determine the task type based on the task description information; and create virtual nodes corresponding to each task participant based on the structured data and the task type.

[0142] In some optional implementations of this embodiment, the processor 1610 is further configured to perform a virtual node update operation when the virtual node update conditions are met; wherein, the virtual node update conditions include at least one of the following: the first user modifies the task participant information, the identity information of at least one second user changes, the task parameters change, the virtual node association conflict occurs, at least one second user leaves the group or task, the task is paused or canceled, the virtual node creation method changes, or at least one second user's account is abnormal; the virtual node update operation includes at least one of the following: modifying the task parameters in at least one virtual node, adding at least one virtual node, or marking at least one virtual node as invalid.

[0143] In some optional implementations of this embodiment, the processor 1610 is further configured to, after receiving an information confirmation message from the second user in the group regarding the target virtual node, authenticate the second user, wherein the authentication includes at least one of the following: generating a verification question based on the information in the task participant information, performing a question-and-answer verification on the second user based on the verification question; sending a verification code to the second user's pre-stored contact information for verification; verifying whether the second user's group membership duration meets the duration requirement; and if the authentication is successful, associating the second user with the target virtual node and issuing a task to the second user based on the task parameters in the target virtual node.

[0144] In some optional implementations of this embodiment, the processor 1610 is further configured to initialize the trust value of the second user; adjust the trust value based on the task completion status of the second user; and update the authentication method for the second user according to the adjusted trust value.

[0145] In some optional implementations of this embodiment, the task includes a payment task, the target virtual node includes task participant identity information, and the task parameters include an amount to be paid; the processor 1610 is further configured to obtain the payment information of the second user, the payment information including payer identity information and payment amount; match the payment information with the task participant identity information, and match the payment amount with the amount to be paid to obtain a matching result; based on the matching result, update the task status information in the target virtual node.

[0146] In some optional implementations of this embodiment, the processor 1610 is further configured to generate task status statistics based on the task status information in each virtual node; and send the task status statistics to the first user.

[0147] In addition, the processor 1610 can also be used to receive a first input from a first user through the user input unit 1607; in response to the first input, obtain task participant information and task description information; send the task participant information and the task description information to the server, so that the server creates virtual nodes corresponding to each task participant based on the task participant information and the task description information, and issues a task to the second user after receiving a confirmation message from the second user in the group for the target virtual node; receive the task status information of the second user sent by the server, and display the task status information through the display unit 1606.

[0148] In some optional implementations of this embodiment, the processor 1610 may also be used to receive a first input from a first user to the group chat interface via the user input unit 1607, the first input including keyword instructions; in response to the first input, to obtain a target message sent by the first user in the group chat interface, to determine the target message as the task participant information, and to determine the keyword instructions as the task description information, wherein the target message includes at least one of the following: an image or a file.

[0149] In some optional implementations of this embodiment, the processor 1610 can also be used to receive a first input from a first user to the task function controls in the group chat interface via the user input unit 1607; in response to the first input, display a new task interface via the display unit 1606, the new task interface including a task intent keyword input control and a resource upload function control; receive a second input from the user to the task intent keyword input control via the user input unit 1607; in response to the second input, obtain the task description information; receive a third input from the user to the resource upload function control via the user input unit 1607; and in response to the third input, obtain the task participant information.

[0150] In some optional implementations of this embodiment, the processor 1610 may also be used to receive a first input of a target resource through the user input unit 1607, the target resource including at least one of the following: an image, a file; in response to the first input, to use the target resource as task participant information; to obtain the task description information from a message sent by the first user in the group chat interface, or to display a task addition prompt through the display unit 1606 and receive the task description information input by the first user based on the task addition prompt.

[0151] In some optional implementations of this embodiment, the processor 1610 may also be used to perform at least one of the following: receiving task status statistics sent by the server and displaying the task status statistics through the display unit 1606, wherein the task status statistics are generated based on the task status information in each virtual node; receiving a task exception notification sent by the server and displaying the task exception notification through the display unit 1606, wherein the task exception notification is generated based on the task execution result of the second user; receiving a virtual node update notification sent by the server and displaying the virtual node update notification through the display unit 1606, wherein the virtual node update notification is triggered based on virtual node update conditions, wherein the virtual node update conditions include at least one of the following: modification of task participant information, change of second user identity information, change of task parameters, virtual node association conflict, second user leaving the group or task, task paused or canceled.

[0152] It should be understood that, in this embodiment, the input unit 1604 may include a graphics processing unit (GPU) 16041 and a microphone 16042. The GPU 16041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1606 may include a display panel 16061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1607 includes at least one of a touch panel 16071 and other input devices 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include a touch detection device and a touch controller. Other input devices 16072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0153] The memory 1609 can be used to store software programs and various data. The memory 1609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1609 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0154] Processor 1610 may include one or more processing units; optionally, processor 1610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1610.

[0155] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described task processing method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0156] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0157] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described task processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0158] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0159] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the task processing method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0162] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A task processing method characterized by, The method comprises: receiving task participant information and task description information sent by a first user in a group; based on the task participant information and the task description information, creating a virtual node corresponding to each task participant, the virtual node including task state information and task parameters; after receiving an information confirmation message of a second user in the group for a target virtual node, issuing a task to the second user based on the task parameters in the target virtual node; based on the task execution result of the second user, updating the task state information in the target virtual node, and synchronizing the task state information to the first user.

2. The method of claim 1, wherein, The method comprises: identifying the task participant information through optical character recognition technology to obtain structured data; determining the task type based on the task description information; based on the structured data and the task type, creating a virtual node corresponding to each task participant.

3. The method of claim 1, wherein, After creating the virtual node corresponding to each task participant, the method further comprises: if the virtual node update condition is met, performing a virtual node update operation; wherein the virtual node update condition comprises at least one of the following: the first user modifies the task participant information, at least one second user's identity information changes, task parameters change, virtual node association conflict, at least one second user exits the group or the task, task suspension or cancellation, virtual node creation method changes, at least one second user's account is abnormal; the virtual node update operation comprises at least one of the following: modifying the task parameters in at least one virtual node, adding at least one virtual node, marking at least one virtual node as invalid.

4. The method of claim 1, wherein, After receiving the information confirmation message of the second user in the group for the target virtual node, the method further comprises: after receiving the information confirmation message of the second user in the group for the target virtual node, performing identity verification on the second user, the identity verification comprising at least one of the following: generating a verification question based on the information in the task participant information, conducting a question and answer verification on the second user based on the verification question; sending a verification code to the second user's pre-stored contact information for verification; checking whether the second user's entry duration in the group meets the duration condition; if the identity verification is passed, associating the second user with the target virtual node, and issuing a task to the second user based on the task parameters in the target virtual node.

5. The method of claim 4, wherein, After associating the second user with the target virtual node, the method further comprises: initializing the trust value of the second user; adjusting the trust value based on the second user's task completion; updating the identity verification method for the second user according to the adjusted trust value.

6. The method of claim 1, wherein, The task includes a payment task, the target virtual node includes task participant identity information, and the task parameter includes a to-be-paid amount; The task state information in the target virtual node is updated based on the second user's task execution result, including: Obtaining payment information of the second user, the payment information including payment party identity information and a payment amount; Matching the payment information with the task participant identity information and matching the payment amount with the to-be-paid amount to obtain a matching result; Based on the matching result, updating the task state information in the target virtual node.

7. A task processing method characterized by, The method includes: Receiving a first input of a first user; In response to the first input, obtaining task participant information and task description information; Sending the task participant information and the task description information to a server, so that the server creates virtual nodes corresponding to each task participant based on the task participant information and the task description information and issues a task to a second user in a group after receiving an information confirmation message of the second user for a target virtual node; Receiving the task state information of the second user sent by the server and displaying the task state information.

8. The method of claim 7, wherein, The receiving of the first input of the first user includes: Receiving a first input of a first user to a group chat interface, the first input including a keyword instruction; The obtaining of the task participant information and the task description information in response to the first input includes: In response to the first input, obtaining a target message sent by the first user in the group chat interface, determining the target message as the task participant information, and determining the keyword instruction as the task description information, the target message including at least one of the following: a picture and a file.

9. The method of claim 7, wherein, The receiving of the first input of the first user includes: Receiving a first input of a first user to a task function control in a group chat interface; The obtaining of the task participant information and the task description information in response to the first input includes: In response to the first input, displaying a new task interface, the new task interface including a task intent keyword input control and a resource upload function control; Receiving a second input of a user to the task intent keyword input control; In response to the second input, obtaining the task description information; Receiving a third input of a user to the resource upload function control; In response to the third input, obtaining the task participant information.

10. The method of claim 7, wherein, The receiving of the first input of the first user includes: Receiving a first input of a target resource, the target resource including at least one of the following: a picture and a file; The obtaining of the task participant information and the task description information in response to the first input includes: In response to the first input, taking the target resource as the task participant information; Obtaining the task description information from a message sent by the first user in a group chat interface, or displaying a task addition prompt and receiving task description information input by the first user based on the task addition prompt.

11. The method of claim 7, wherein, The method further includes at least one of the following: receive the task state statistical information sent by the server and display the task state statistical information, the task state statistical information being generated based on the task state information in each virtual node; receive the task exception notification sent by the server and display the task exception notification, the task exception notification being generated based on the task execution result of the second user; receive the virtual node update notification sent by the server and display the virtual node update notification, the virtual node update notification being triggered based on a virtual node update condition, the virtual node update condition including at least one of the following: task participant information modification, second user identity information change, task parameter change, virtual node association conflict, second user exit from a group or task, task suspension or cancellation.

12. A task processing apparatus characterized by comprising: The apparatus comprises: a receiving unit configured to receive task participant information and task description information sent by a first user in a group; a creating unit configured to create a virtual node corresponding to each task participant based on the task participant information and the task description information, the virtual node including task state information and task parameters; a sending unit configured to, after receiving an information confirmation message sent by a second user in the group for a target virtual node, issue a task to the second user based on the task parameters in the target virtual node; a synchronizing unit configured to update the task state information in the target virtual node based on a task execution result of the second user, and synchronize the task state information to the first user.

13. A task processing apparatus characterized by comprising: The apparatus comprises: a receiving unit configured to receive a first input of a first user; a receiving unit configured to receive a first input of a first user; a sending unit configured to send the task participant information and the task description information to a server, so that the server creates a virtual node corresponding to each task participant based on the task participant information and the task description information, and issues a task to a second user in a group after receiving an information confirmation message sent by the second user for a target virtual node; a display unit configured to receive task state information of the second user sent by the server, and display the task state information.

14. An electronic device, comprising: A processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the task processing method according to any one of claims 1-11.

15. A readable storage medium, characterized by, The readable storage medium stores programs or instructions, the programs or instructions being executed by the processor to implement the steps of the task processing method according to any one of claims 1-11.

Images