Task processing method and device, electronic equipment and readable storage medium

Abstract

The invention discloses a task processing method and device, electronic equipment and a readable storage medium, and belongs to the technical field of communication. The method is executed by the electronic equipment and comprises the following steps: acquiring task information of a user; generating a task execution path according to the task information and the historical operation information; and performing task processing according to the task execution path.

Description

Technical Field

[0001] This application belongs to the field of electronic equipment technology, specifically relating to a task processing method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] Currently, the diversification of electronic device functions enables users to manage work and life more efficiently, bringing more convenience and saving time and energy. However, in multi-application, multi-device environments, users often need to manually complete repetitive tasks, such as copying and pasting content across applications, comparing prices across multiple platforms, and synchronizing meeting operations between mobile phones and computers. These operations are complex and reduce the ease of use of electronic devices. Summary of the Invention

[0003] The purpose of this application is to provide a task processing method, apparatus, electronic device, and readable storage medium that can improve the ease of use of electronic devices.

[0004] In a first aspect, embodiments of this application provide a task processing method, executed by an electronic device, comprising: Obtain the user's task information; Based on the task information and historical operation information, a task execution path is generated; The task is processed according to the task execution path.

[0005] Secondly, embodiments of this application provide a task processing apparatus, including: The acquisition module is used to acquire the user's task information; The first processing module is used to generate a task execution path based on the task information and historical operation information; The second processing module is used to process tasks according to the task execution path.

[0006] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0007] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0008] Fifthly, 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 as described in the first aspect.

[0009] In a sixth aspect, 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.

[0010] In this embodiment, by obtaining the user's task information and understanding the user's needs, a task execution path is generated by combining the task information and historical operation information. Finally, the task is processed according to the task execution path. This not only simulates human operation to achieve intelligent task processing and improves the ease of use of electronic devices, but also the task execution path generated with reference to historical operation information is more in line with user habits and has a higher degree of personalization. Attached Figure Description

[0011] Figure 1 This is a schematic diagram of the method flow of an embodiment of this application; Figure 2 This is one of the schematic diagrams of the anthropomorphic task interface in the embodiments of this application; Figure 3 This is the second schematic diagram of the anthropomorphic task interface in the embodiments of this application; Figure 4 This is the third schematic diagram of the anthropomorphic task interface in the embodiments of this application; Figure 5 This is the fourth schematic diagram of the anthropomorphic task interface in the embodiments of this application; Figure 6 This is the fifth schematic diagram of the anthropomorphic task interface in the embodiments of this application; Figure 7 This is a schematic diagram of the module structure of the device according to an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application; Figure 9 This is a schematic diagram of the structure of another electronic device according to an embodiment of this application. Detailed Implementation

[0012] 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.

[0013] 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 use of data can be interchanged 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.

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

[0015] like Figure 1 As shown, an embodiment of this application illustrates a task processing method executed by an electronic device, comprising: Step 101: Obtain the user's task information; Step 102: Generate a task execution path based on the task information and historical operation information; Step 103: Process the task according to the task execution path.

[0016] Following the steps described above, the electronic device learns about the user's needs by acquiring the user's task information. It then combines the task information with historical operation information to generate a task execution path. Finally, the task is processed based on this execution path. This not only simulates human operation to achieve intelligent task processing and improves the ease of use of the electronic device, but also makes the task execution path generated with reference to historical operation information more in line with user habits and more personalized.

[0017] Optionally, in some embodiments of this application, the task execution path can be understood as the operation flow of operable elements in various target interfaces associated with the task information. Example 1: If the task information is to navigate to an address in a communication application (App) 1, the task execution path is: ① Open the communication App 1 → ② Enter a chat → ③ Click the address → ④ Copy the address → ⑤ Open the map App 1 → ⑥ Search for the address → ⑦ Click navigation. Example 2: If the task information is to search for a certain brand of mobile phone, the task execution path is: ① Open the e-commerce App 1 → ② Click the search box → ③ Enter the keyword "certain brand of mobile phone" → ④ Select the first item.

[0018] Optionally, in some embodiments of this application, the specific method by which the electronic device performs task processing according to the task execution path includes: generating multiple operation instructions and execution order information of the multiple operation instructions according to the task execution path, and executing the multiple operation instructions sequentially according to the execution order information.

[0019] The process of handling tasks can be viewed as a manual task replacement, where the system simulates the user's "manual" operation path to replace the automated operation of manually executing tasks across applications and devices.

[0020] Optionally, in some embodiments of this application, the operation instructions may be tap, swipe, input, wait, etc. Each operation instruction carries coordinates, delay, target operation element identifier, etc.

[0021] Optionally, in some embodiments of this application, the task execution path supports adding buffering actions, such as simulating "human error" or waiting for the page to load; it also supports abnormal jump logic, such as executing an alternative path if a pop-up window is encountered.

[0022] Optionally, in some embodiments of this application, the task information includes at least one of the following: task object, task intent, and task result; obtaining the user's task information includes: The task information is obtained by parsing the user input; or... The task information is obtained by listening to specific events.

[0023] In this way, electronic devices can obtain task information by receiving user requests in response to user input; or, in response to event monitoring, automatically determine whether to execute the above steps 101-103 if the user does not actively express a request.

[0024] User input includes, but is not limited to, voice input, physical button input, and text input. Specifically, the electronic device uses voice recognition to analyze the user's voice input, such as "Help me check which of these two apps is cheaper," to obtain task information; the user presets a shortcut key 1 to trigger the task "automatic price comparison," and the electronic device analyzes the task "automatic price comparison" to obtain task information by recognizing the trigger command of shortcut key 1; the user presets a shortcut key 2 to trigger a saved task template, and the electronic device analyzes the task template to obtain task information by recognizing the trigger command of shortcut key 2. Optionally, in some embodiments of this application, the task template can be pre-set or stored after a human-like operation task. The task template includes one or more tasks, and multiple tasks can also be cross-device tasks. Of course, the task template stored after a human-like operation task can include a task execution path, so the electronic device does not need to generate a task execution path, but can directly process the task according to the task execution path of the task template.

[0025] Optionally, the task object can be understood as the operation target, such as an application, page, interface, or operation element. The task intent can be understood as the operation intention, such as searching, copying, or jumping. The task result can be understood as the outcome goal, such as retrieving prices or saving screenshots.

[0026] Optionally, in some embodiments of this application, generating a task execution path based on the task information and historical operation information includes: Analyze the structure of each target interface associated with the task information to determine the operable elements; Construct a behavioral model of the task information based on the historical operation information; The task execution path is generated based on the behavior model and the operable elements.

[0027] In this way, after identifying operable elements and constructing a behavioral model, the task execution path can be generated by combining the behavioral model and operable elements. This introduces a mapping mechanism between task information and task execution path, dynamically generating the task execution path without using dynamic scripts. The electronic device directly parses the structure of each target interface associated with the task information to determine the operable elements. Generating the task execution path does not rely on pre-coded task flows or application programming interfaces (APIs), significantly expanding the scope of applications that the electronic device can control. Furthermore, the electronic device constructs a behavioral model of the task information based on historical operation information, combining context, historical preferences, and the current state to achieve dynamic generation of the behavioral model. This allows the task execution path to closely align with user habits, possessing flexibility and fault tolerance, adapting to changes in application structure or user interface (UI) adjustments, reducing maintenance costs, and improving generalization capabilities.

[0028] Optionally, in some embodiments of this application, the behavior model can be understood as an operation flow model, such as a common flow like open → search → confirm → jump. Historical operation information is used to construct the behavior model of the task information, so that the resulting task execution path is realized as a human-like path, that is, a task execution path that simulates the user's habitual operation sequence and interaction method.

[0029] Optionally, in some embodiments of this application, the structural analysis of the target interface can employ graphical interface structure recognition to extract the interface hierarchy (e.g., through system auxiliary interfaces or layer abstraction modules); it can also use control anchor point positioning to analyze clickable areas, sliding areas, and input box positions; or it can use optical character recognition (OCR) to perform character recognition on the current page screenshot. For example, in an app, the positions of the "search box" and "add to cart" controls can be determined through image analysis. Even in an API-free, black-box app environment, operable elements can still be extracted and understood; breaking the limitations of automation relying on interfaces, and realizing "compliant simulation operation in unauthorized scenarios".

[0030] Optionally, in some embodiments of this application, an "operation anchor index" is established for the determined operable elements for subsequent path generation and execution.

[0031] Optionally, in some embodiments of this application, multiple candidate task execution paths can be generated based on the behavioral model and operable elements, and the final task execution path is confirmed by the user or other reference factors. Other reference factors include execution time, result satisfaction, etc.

[0032] Optionally, in some embodiments of this application, the step of processing tasks according to the task execution path includes: When the task information corresponds to multiple devices, each sub-node in the task execution path is determined, and sub-tasks for each sub-node are generated; wherein each sub-node corresponds to one of the multiple devices, and the sub-task includes at least one of the following: behavior flow, anchor coordinates, and expected state; The subtask is distributed to the corresponding child node.

[0033] In other words, when task information involves multiple devices, the task execution path will be divided into subtasks and distributed to other devices besides itself. These other devices are called child nodes. The child nodes perform task processing according to the subtasks and assist in completing the task corresponding to the task information. This breaks through the single-device architecture and realizes task decomposition and synchronous execution among multiple devices.

[0034] The task information involves multiple devices, meaning the task corresponds to cross-device operations. The electronic device itself can be considered the master device, and the devices corresponding to the child nodes can be considered auxiliary devices. For example, if the master device is a mobile terminal, its generated task execution path is "Open file manager → Find slideshow → Click projection button → Launch wireless projection App → Receive projection link → Confirm connection → Automatic full-screen playback." The system distributes path ②, "Launch wireless projection App → Receive projection link → Confirm connection → Automatic full-screen playback," to the TV, where the specified content is played. Alternatively, if the master device is a tablet, and login is required during the user's slideshow operation, the generated task execution path is "Mobile device initiates verification login." The system then distributes "Mobile device initiates verification login" to the mobile phone, which executes the sub-task to complete the verification login.

[0035] Optionally, in some embodiments of this application, it is possible to determine whether the task information corresponds to multiple devices by analyzing whether multiple devices appear in the task execution path. For example, if the task execution path "scan QR code with mobile phone → play video on TV" involves mobile phone and TV, the task information involves multiple devices; if the task execution path "view document on tablet → open subway app for navigation on mobile phone" involves mobile phone and TV, the task information involves multiple devices.

[0036] Optionally, in some embodiments of this application, it is possible to determine whether task information corresponds to multiple devices by checking whether the task object contains content that is not executed on the local machine.

[0037] Optionally, in some embodiments of this application, a defined auxiliary device is marked as a child node, that is, a distribution node.

[0038] Optionally, in some embodiments of this application, the distribution of subtasks can be carried out using local area network broadcasting, Bluetooth pairing, or cloud synchronization protocols to distribute them to the corresponding devices.

[0039] Optionally, in some embodiments of this application, the behavior flow of a subtask can be understood as the task steps to be executed by the corresponding device, the anchor coordinates can be understood as the coordinates of the operable elements corresponding to each behavior in the behavior flow, and the expected state can be understood as the expected subtask completion result, thereby realizing asynchronous confirmation and task callback of path distribution.

[0040] Optionally, in some embodiments of this application, after the auxiliary device performs the sub-task, it will also return the execution status to the main control device.

[0041] In this way, the main control device can understand the task execution process through the execution status, which facilitates subsequent adjustments or updates.

[0042] Optionally, in some embodiments of this application, distributing the subtask to the corresponding child node includes: An execution request is sent to the child node. The execution request includes the subtask and authorization information, and the authorization information includes the effective time and scope of action.

[0043] In this way, child nodes can execute subtasks based on authorization information, avoiding the long-term occupation of child node resources by subtasks, and can also restrict the behavior of child nodes to ensure the security of the main control device.

[0044] Optionally, in some embodiments of this application, the method further includes: If the task execution path is generated, display the path tree of the task execution path; The task execution path is updated based on the user's adjustments to the path tree.

[0045] That is, the generated task execution path will be made visible through a path tree, and users can operate on the path tree to adjust the task and update the task execution path.

[0046] Optionally, in some embodiments of this application, the method further includes: Generate an execution result summary of the task information, the execution result summary including at least one of the following: result data, execution process screenshot, and task suggestions.

[0047] In this way, the generated execution result summary can achieve at least one of the following analyses: whether the task execution process has achieved the expected results; users can choose to save it as a template, roll back and redo it, or provide feedback on the result deviation.

[0048] Optionally, in some embodiments of this application, the method further includes: Record the execution information for each action.

[0049] By recording the execution information of each action of the electronic device during task processing according to the task execution path, the automatic execution process is recorded as a visual trajectory, enhancing the interpretability of the system and user trust; it also supports rollback mechanisms and multi-version comparison, providing enhanced security capabilities.

[0050] Optionally, the execution information includes snapshots and / or logs.

[0051] During task processing according to the task execution path, the electronic device automatically generates a snapshot after each action, recording at least one of the following: current page screenshot, operation element, location information, return status code, and execution time. The current page screenshot may include a timestamp.

[0052] When the execution information includes logs, the logs support encrypted storage and are used for at least one of the following: user rollback operations; error diagnosis and task failure retry; subsequent learning and task template optimization.

[0053] Optionally, in some embodiments of this application, the methods of the embodiments of this application are implemented through the interaction between the user and the anthropomorphic task interface of the electronic device, such as... Figure 2 As shown, the anthropomorphic task interface 21 allows users to input text to indicate their needs. The electronic device then responds to this input, parses it to obtain task information, and generates a task execution path based on this task information and historical operation information. During this process, the anthropomorphic task interface 21 will display "Task decomposition and analysis in progress," as shown below. Figure 3 As shown; then, the electronic device processes the task according to the task execution path. During this process, the anthropomorphic task interface 21 will display "Operating for you in the background," as shown. Figure 4 Therefore, the specific operation is a background process. After the task is completed, the anthropomorphic task interface 21 will display a summary of the execution results, such as... Figure 5 As shown. Of course, during the task processing according to the task execution path, the anthropomorphic task interface 21 can also display sub-interfaces 22 to show various operation pages for task processing. Users can also switch back to background operations using controls, such as... Figure 6 As shown; during background operations, the user can also switch to sub-interface 22 via a control to view the foreground.

[0054] Scenario 1: The user wants the system to automatically complete the following composite task: "Copy the address information sent by the customer from WeChat → Open Amap to search → Cast the location to the TV at home for navigation → Save the screenshot on the phone." Devices involved: Mobile phone (main control device): running WeChat and Gaode Map; Smart TV (auxiliary device): receiving screen mirroring and displaying the map navigation interface.

[0055] Step 201: The user says "Put the address in WeChat into the TV and cast it to the TV" via voice. The main control device's system recognizes the task information: "Extract address → Map search → Cast to screen". This involves multiple devices and is broken down into sub-intentions.

[0056] Step 202: The system uses OCR to recognize the address field in the chat history, locates the "address card" anchor point, determines the clickable area, and identifies the operable element.

[0057] Step 203: Combining task information and historical operation information, generate the task execution path: ① Open WeChat → ② Enter a chat → ③ Click the address card → ④ Copy → ⑤ Open Amap → ⑥ Search → ⑦ Click navigation → ⑧ Send to TV → ⑨ Cast to the navigation page. The system calls historical operation information, i.e., the user's historical behavior, to generate a dynamic path and automatically fills in the necessary operation sequence.

[0058] Step 204: Because of the presence of the "screen projection" instruction, the system identifies it as a cross-device task and determines the sub-task.

[0059] In step 205, the system assigns the "cast to the navigation page" option to the smart TV. The TV, as a cooperating terminal, executes the sub-task, automatically opens the Gaode Casting App, and waits for the casting process to begin.

[0060] Step 206: The system automatically completes its own tasks on the phone (which can be understood as preliminary operations): copy the address → open the map → enter and search → arrive at the navigation page. This simulates the user's manual route, with each step completed through touch simulation.

[0061] Step 207: The system records screenshots of all operation steps, the interface status of each step, the address text, and the screen mirroring status code. Examples include screenshots of the original chat, the Gaode navigation page, and the TV response results.

[0062] Step 208, the system returns a summary: Map navigation has been sent to the TV. Do you want to save the screenshot to your notes? After the user confirms, the system saves the screenshot and prompts that the task was successful.

[0063] Therefore, by actively receiving user operation intentions, parsing the application interface structure, generating operation paths that conform to user habits, and completing task execution by simulating human operation without opening APIs, the limitations of traditional automation methods in black-box Apps and cross-application collaboration scenarios are effectively solved.

[0064] Specific beneficial effects include: 1. Improve operability for applications using non-open APIs. By using graphical interface structure recognition, control anchor point positioning, and OCR technology, operable elements such as "buttons," "input boxes," and "labels" on a page can be identified without relying on publicly available application interfaces. This significantly expands the scope of applications that the system can control.

[0065] 2. Automatically construct human-like operation paths to improve the naturalness and adaptability of task execution. A historical operation information modeling mechanism is introduced to dynamically generate task execution paths based on context, past preferences, and current state. This closely aligns with user habits, offers flexibility and fault tolerance, and can adapt to changes in application structure or UI adjustments. It achieves truly "intelligent, human-like operation" rather than pre-set scripts, reducing maintenance costs and enhancing generalization capabilities.

[0066] 3. Enable task path coordination and distribution across multiple devices. It supports distributing certain operation steps in a task to other authorized devices for execution via LAN, Bluetooth, or cloud synchronization (such as using a mobile phone to control TV screen mirroring); the execution status between devices is kept synchronized in real time, and master-slave control, segmented execution, or distribution confirmation mechanisms are supported. This enhances the collaborative capabilities of task automation in multi-terminal environments and realizes a "manual substitution across devices" mechanism.

[0067] 4. User task paths are visualized, editable, and reversible, enhancing user control. The system-generated path can be displayed as a draft of the steps, which users can insert, delete, or edit before execution. During execution, if the process fails or an error occurs, users can choose to roll back or retry from a specific step. This ensures that the system's behavior is transparent, reliable, and controllable, enhancing user trust and debuggability.

[0068] 5. Execution process snapshots are recorded, supporting review and learning. During task execution, the operation status, interface screenshots, click coordinates, and response results of each step are logged to facilitate post-event review, template optimization, or continuous iterative training of AI models. This achieves a "traceable," "verifiable," and "learnable" task proxy mechanism, enhancing the system's self-evolution capabilities.

[0069] 6. Possesses modular versatility and horizontal scalability. Each step of the method in this application embodiment can be embedded as a general task agent module into an operating system, AI assistant, or browser plugin, and is widely used in scenarios such as personal assistants, enterprise process automation, smart office terminals, accessibility assistive devices, and IoT control panels. It possesses broad commercial adaptability potential and can form an independent, general-purpose platform capability module.

[0070] Scenario 2, unlike Scenario 1 which focuses on "user-initiated tasks", involves the system automatically determining whether to perform simulated human operation tasks after listening to specific events, and completing intelligent response behaviors across applications or devices, even when the user does not actively issue operation instructions.

[0071] Step 301: The electronic device listens for external events and acquires trigger signals.

[0072] Electronic devices continuously monitor system-level or application-level event channels, including but not limited to: Notification bar information, such as SMS, WeChat, and App notifications; System broadcasts, such as network status changes and app behavior; Third-party signaling, such as Bluetooth or IoT device triggering.

[0073] Once an event that meets the criteria is identified, i.e., a specific event, the system records the event content and the triggering source, and proceeds to the next step.

[0074] Step 302: Parse the trigger event content and identify task information.

[0075] The system performs content parsing on the information contained in the event, such as OCR text extraction, keyword matching, and natural language understanding, and compares it with predefined operation templates or semantic intent databases.

[0076] If the event content meets a certain preset logic, such as containing keywords like "verification code", "express delivery", or "screen projection", then preliminary information is generated.

[0077] Step 303: Determine whether an anthropomorphic task needs to be performed.

[0078] The system determines whether to trigger task execution based on user settings, task category, and current status, including: whether the current device is the main control device; whether the current app is running; and whether the user has set "automatic execution" or "pending confirmation" mode, etc. If the execution conditions are met, the preliminary information is confirmed as task information, and the system continues to the path generation process.

[0079] Step 304: Analyze the target App's interface structure and identify operable elements to serve as operable anchor points.

[0080] After opening the target application, the system uses the following techniques to identify interactive elements on the interface: OCR recognition of key text and button positions; control tree structure crawling; and gesture area determination, such as swipe areas and input boxes. Specifically, the system constructs an interactive structure diagram of the current page for path analysis.

[0081] Step 305: Generate the task execution path.

[0082] Based on task information, current app status, and user history, the system automatically constructs a task execution path that conforms to the user's operating habits. This path includes, but is not limited to: clicking a button, filling in / copying content, swiping to a certain area, submitting, jumping to, or confirming. This path can be a process within a single app or span multiple applications.

[0083] Step 306: Determine whether cross-device execution is involved.

[0084] If the task includes the intention of multi-device collaboration, such as "mobile phone controls TV playback" or "mobile phone scans QR code → tablet display", the system determines whether task distribution is required. If yes, proceed to step 307; otherwise, skip.

[0085] Step 307: Distribute the subtasks in the task execution path to the child nodes.

[0086] The system dispatches part of the task path to other authorized devices via local area network communication, Bluetooth, or cloud synchronization protocols, and completes the necessary status synchronization, including: subtask identifier; operation parameters and anchor points; execution success / failure status feedback.

[0087] Step 308: The electronic device simulates user operations according to the path.

[0088] The system simulates operations sequentially according to the path generated in step 305, including touch, swipe, input, delay, screenshot, pop-up handling, etc. Each operation is anchored based on the identified GUI structure.

[0089] Step 309: Record operation snapshots and logs during the execution process.

[0090] Upon completion of each operation step, the system generates the following records: a screenshot of the current interface (including a timestamp), operation node information (control type and location), action type and feedback status, device ID, and network status.

[0091] This data will be stored in the task log for users to view or for use in subsequent AI model learning and path optimization.

[0092] Step 210: Generate and output a task execution summary.

[0093] The system integrates task execution results and generates summary feedback, including: whether the execution was successful, snapshot view (as shown in the text and image review), and user behavior suggestions (such as saving as a template, rolling back, etc.). If the execution fails, the system can automatically analyze the failure points and prompt the user to adjust the path or retry.

[0094] By listening to external events, automatically identify the potential operation intentions of users, and combine the interface structure analysis and anthropomorphic path generation capabilities to complete a series of simulated user operation processes across apps or even across devices. Without the user actively issuing task instructions, it can automatically respond to notifications or environmental changes, achieving intelligent, efficient, and low-intervention automated task execution.

[0095] 1. Implement the automatic response ability of tasks driven by passive events; By listening to system notifications (such as express delivery reminders, verification code text messages, video conference invitations) or device broadcasts (such as Bluetooth connections, NFC identifications, etc.), it can actively identify operation scenarios without user intervention; combined with semantic analysis and context judgment, the system can independently identify task objectives and execution paths. Upgrade automation from "responding to commands" to "understanding events", with stronger real-time performance and task discovery capabilities.

[0096] 2. It can complete the semantic extraction and instruction mapping of notification content without opening the API; Support OCR recognition, NLP semantic understanding, and keyword extraction for unstructured notification texts; it can extract key information from "pickup notice", "payment reminder", "verification code" and map it to a series of operation paths.打通“系统级通知”与“用户拟人操作”之间的链路,使通知可执行、可响应。

[0097] 3. Dynamically generate task execution paths to adapt to the actual app structure in different notification scenarios; According to the notification event type and the target app status, the system generates an adapted path in real time; support "different processing logics for the same type of event", such as SMS verification code → automatically copy and input; express delivery reminder → open the app to check the express delivery / scan the code to pick up the package, etc. Improve the scenario matching degree and adaptation ability of the task path, and enhance the intelligence and fault tolerance ability.

[0098] 4. It can optimize the path and user confirmation mechanism in combination with user habits; If the user is configured as the "confirmation required mode", the system will pop up a prompt after generating the path, and the user can modify or confirm it; support "learning-based path optimization", and dynamically adjust the subsequent task generation preferences according to whether the user retains / backs off. Retain the user's intention control right in automated execution, taking into account both intelligence and security.

[0099] 5. Support cross-application / cross-device linked task processing triggered by multiple types of events; For example: SMS verification code auto-fill → form submission; express delivery notification → open the display app → automatic input of pickup code. It can automatically switch devices based on event type (e.g., displaying content on a TV, scanning a code to log in on a tablet); it can adapt to multiple scenarios: message notification processing, IoT control, payment operations, system-level reminder responses, etc. It achieves a complete leap from "passively viewing notifications" to "actively executing and completing tasks."

[0100] 6. Operation snapshots and task logs are recorded throughout the entire process to ensure that system behavior is controllable and traceable; The system retains screenshots, operation logs, and status markers at each task stage; it allows traceability of notification sources, execution paths, data extraction results, and final status; these can be reviewed by users or used for training subsequent task templates. This significantly improves the system's interpretability, security, and audit compliance capabilities.

[0101] Scenario 3: Task plan generation and execution method for multi-user / organizational collaboration. Compared with the previous two scenarios, this method focuses on task collaboration, unified team operation and authorization execution mechanism. It is suitable for enterprise-level / multi-person workflow environment and demonstrates the "hand-substitute system" in terms of organizational collaboration and intelligent agent authorization control.

[0102] Step 401: The electronic device obtains the task information configured by the main user.

[0103] The primary user (such as the team leader) defines task templates, such as task objectives and workflows, through natural language, a graphical interface, or batch import. For example: The team leader configures a template for a "content review + upload" manual task; Main user: A content operations manager; expects team members to complete the following tasks every morning: 1. Open the designated channel in the WeChat group for your business; 2. Download the documents to be published that day; 3. Open the backend management system; 4. Log in to your account → Enter the content upload page; 5. Upload document → Fill in title → Select publishing platform (Xiaohongshu / Weibo); 6. Click "Submit for Review"; 7. Take a screenshot of the published result and send it back to the group.

[0104] Master user "Define Task Template" process: Method 1: Natural Language Approach The main user directly said in the task assistant: "Help me create a task template for 'daily content publishing process' that automatically completes the following operations: downloading files from the group, opening the backend system to upload, taking a screenshot after publishing, and sending feedback to the group." The system parses this "human-language instruction" to obtain the user's task information; based on the task information and historical operation information, it generates a task execution path.

[0105] Method 2: Graphical approach The main user enters the "Task Editing Interface" and manually drags and drops the following modules: Open the app (WeChat) → Enter the channel → Download the file; Open the webpage (operations backend) → Log in → Upload file → Check the options → Click publish; Take a screenshot → Open WeChat → Paste the screenshot and send.

[0106] The interface also allows you to set which steps are editable, which devices will perform the steps, and whether confirmation is required.

[0107] Method 3: Batch Import The main user uploads a .csv or .json file, which defines: [ {"step": "open_app", "target": "WeChat"}, {"step": "download_file", "target": "content channel"}, {"step": "open_browser", "url": "https: / / cms.example.com"}, {"step": "upload_file", "field": "document"}, {"step": "submit"}, {"step": "screenshot"}, {"step": "send_to_wechat", "target": "workgroup"} ] The system automatically parses these task definitions to obtain the user's task information; based on the task information and historical operation information, it generates a task execution path.

[0108] Once the task execution path is complete, it can be used for: One-click execution (allowing the system to perform tasks on behalf of employees); Assigned to different people (some steps in the task flow are assigned to Xiao Wang, Xiao Li, and Xiao Liu); Set it as a scheduled task to run at 9 AM every day; The main user will be automatically notified if the execution fails.

[0109] The system automatically abstracts the task execution path into a "task plan draft" object, which includes, but is not limited to: Execution step sequence (path), target application and operation anchor point, data fields (to be filled in, replaced, or copied), and list of executable roles / terminal devices.

[0110] Step 402: The electronic device parses the task execution path structure and generates a path tree.

[0111] The system performs a structured decomposition of the task execution path, generating a number of paths including "main path", "alternate path" and "user-insertable steps"; The path tree supports personalized adjustments (for example, some steps can be handled by device A and others by user B); the path map marks the points requiring collaboration, permission boundaries, and task switching conditions.

[0112] Step 403: Based on the organizational hierarchy or task allocation strategy, determine the sub-tasks corresponding to each sub-node and distribute them to different devices.

[0113] The system combines organizational structure (such as roles like master user, executor, and reviewer) with endpoint capabilities to map task paths to execution nodes; for example: Mobile phone 1 executes steps ①②③, tablet terminal executes steps ④⑤, and PC device processes and uploads step ⑥.

[0114] Allocation methods supported: role mapping (e.g., "financial specialist processes expense reports and uploads"), priority strategies (load scheduling, priority for idle devices).

[0115] Step 404: Issue task execution authorization and establish an execution channel across users / devices.

[0116] The master control device sends an execution request to the auxiliary device, along with: an authorization token (valid time and operation scope), operable anchor points and operation parameters, feedback requirements, and operation log path.

[0117] The auxiliary device needs to verify permissions. Once verified, it will automatically be added to the task execution path "execution chain" and enter the standby / execution state.

[0118] Step 405: Each device simulates human operation based on the path segment it receives.

[0119] The device completes cross-App and cross-UI component operation processes according to the received sub-tasks; it supports collaborative point feedback status (such as "operation completed → notify the main controller → issue the next task").

[0120] Step 406: The system records the task execution status and snapshot logs on each node.

[0121] The execution records of each user or terminal are integrated into the central "task log pool"; the logs support unified management, version rollback, and execution exception reporting; facilitating auditing by the main user, replay of task processes, and accountability.

[0122] Step 407: The system generates a summary of the completion of the multi-user collaborative task. This includes: execution completion status (success / failure / abortion), time taken for each operation, user / device signature confirmation, snapshot list, and log overview.

[0123] If the task has an "approval step", the system will automatically call the main user or designated role to conduct the final review and confirmation.

[0124] In this scenario, the specific implementation The task information corresponds to the enterprise approval task. The main user configures the "leave application process", which is filled in by the employee, confirmed by HR, and automatically entered by the system. Alternatively, tasks can be posted with corresponding content, editors can write the content, and reviewers can review them before the system publishes them to different platforms. Alternatively, the task information can correspond to content publishing tasks executed on multiple terminals: mobile phones collect information, tablets edit content, and TVs display content. Alternatively, the task information corresponds to a smart meeting, and the user device generates a task execution path: Open document → Open presentation → Start camera → Project to meeting device.

[0125] For multi-user, multi-terminal, and multi-role environments, the traditional "single-user automated operation" capability is expanded into an "organization-level collaborative automated execution system" through a task contingency plan mechanism and permission distribution system, and a complete system with controllable path, clear authorization boundaries, and traceable operation in the execution chain is achieved.

[0126] 1. Achieve pre-arrangement capability for collaborative task paths for multiple roles. It supports breaking down a complex task into multiple subtasks executable by multiple roles / devices; it supports setting path branches, collaboration nodes, and backup plans in preset stages; and it provides a task execution path management mechanism that can be distributed as a standard template. This improves task execution efficiency and adapts to team-based and organized operational processes.

[0127] 2. Supports role-level permission distribution and device mapping for task paths. By employing role binding and a token mechanism, the executable boundaries of each task are clearly defined. The system supports dynamic mapping and distribution based on organizational structure, terminal status, and policy weights. It also supports setting permission expiration times, reversing operations, and manual intervention. This ensures operational security and process clarity in multi-user collaboration scenarios, reducing the risk of accidental operations.

[0128] 3. Supports synchronous scheduling and status feedback of task execution paths across multiple terminal devices. After each task is executed, its status is reported to the main control device or central task scheduling module in real time; it supports multiple task node linkage methods such as "sequential", "concurrent", and "conditional" tasks; when an execution failure occurs, the system can automatically switch to a backup path or reschedule the execution end according to the path plan. This significantly improves the resilience and real-time performance of collaborative task flows and adapts to complex collaborative environments.

[0129] 4. Provide auditable, traceable, and archiveable task execution logs and snapshot mechanisms. Supports recording: screenshots of each operation step; operator / device ID; timestamp, execution status, context parameters, etc.

[0130] Centralized log management supports task-level, user-level, and device-level audit analysis. This enhances system compliance and security, and provides data support for fault traceability and process review.

[0131] 5. Provide a mechanism for reusing task plan templates to improve organizational-level execution efficiency. The main user or administrator can save a type of operation process as a task template; the template supports field placeholders, role customization, and path inheritance; it is suitable for high-frequency repetitive scenarios (such as approval workflows, content delivery workflows, form distribution workflows, etc.). It significantly reduces repetitive work in cross-person and cross-team task handover and improves the standardization of team operations.

[0132] 6. Adaptable to complex B2B / team-level application scenarios, with platform-level scalability. When integrated with SaaS business platforms (such as ERP, CRM, OA), it can be used as an "intelligent path execution engine"; it supports access to the enterprise account system to achieve unified identity authentication and permission issuance; it can be encapsulated as a system underlying capability for orchestration by various business modules.

[0133] The task processing method provided in this application can be executed by a task processing device. This application 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.

[0134] like Figure 7 As shown, a task processing device 700 according to an embodiment of this application includes: Module 710 is used to obtain user task information; The first processing module 720 is used to generate a task execution path based on the task information and historical operation information; The second processing module 730 is used to process tasks according to the task execution path.

[0135] This device acquires user task information to understand user needs, and then combines task information with historical operation information to generate a task execution path. Finally, it processes the task according to the task execution path. This not only simulates human operation to achieve intelligent task processing and improves the ease of use of electronic devices, but also makes the task execution path generated with reference to historical operation information more in line with user habits and more personalized.

[0136] Optionally, the task information includes at least one of the following: task object, task intent, and task result; the acquisition module is specifically used for: The task information is obtained by parsing the user input; or... The task information is obtained by listening to specific events.

[0137] Optionally, the first processing module is specifically used for: Analyze the structure of each target interface associated with the task information to determine the operable elements; Construct a behavioral model of the task information based on the historical operation information; The task execution path is generated based on the behavior model and the operable elements.

[0138] Optionally, the second processing module is specifically used for: When the task information corresponds to multiple devices, each sub-node in the task execution path is determined, and sub-tasks for each sub-node are generated; wherein each sub-node corresponds to one of the multiple devices, and the sub-task includes at least one of the following: behavior flow, anchor coordinates, and expected state; The subtask is distributed to the corresponding child node.

[0139] Optionally, the second processing module is specifically used for: An execution request is sent to the child node. The execution request includes the subtask and authorization information, and the authorization information includes the effective time and scope of action.

[0140] Optionally, the device further includes: The display module is used to display the path tree of the task execution path when the task execution path is generated; The update module is used to update the task execution path based on the user's adjustment of the path tree.

[0141] Optionally, the device further includes: The third processing module is used to generate an execution result summary of the task information, which includes at least one of the following: result data, execution process screenshot, and task suggestions.

[0142] Optionally, the device further includes: The fourth processing module is used to record the execution information of each action.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] Optionally, such as Figure 8As shown, this application embodiment also provides an electronic device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instructions that can run on the processor 801. When the program or instructions are executed by the processor 801, 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.

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

[0148] Figure 9 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0149] The electronic device 900 includes, but is not limited to, components such as: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0150] Those skilled in the art will understand that the electronic device 900 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 910 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. 9 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.

[0151] The processor 910 is used for: Obtain the user's task information; Based on the task information and historical operation information, a task execution path is generated; The task is processed according to the task execution path.

[0152] By acquiring user task information and understanding user needs, a task execution path is generated by combining task information with historical operation information. Finally, the task is processed according to the task execution path. This not only simulates human operation to achieve intelligent task processing and improves the ease of use of electronic devices, but also makes the task execution path generated with reference to historical operation information more in line with user habits and more personalized.

[0153] Optionally, the task information includes at least one of the following: task object, task intent, and task result; the processor 910 is used for: The task information is obtained by parsing the user input; or... The task information is obtained by listening to specific events.

[0154] Optionally, the processor 910 is used for: Analyze the structure of each target interface associated with the task information to determine the operable elements; Construct a behavioral model of the task information based on the historical operation information; The task execution path is generated based on the behavior model and the operable elements.

[0155] Optionally, the processor 910 is used for: When the task information corresponds to multiple devices, each sub-node in the task execution path is determined, and sub-tasks for each sub-node are generated; wherein each sub-node corresponds to one of the multiple devices, and the sub-task includes at least one of the following: behavior flow, anchor coordinates, and expected state; The subtask is distributed to the corresponding child node.

[0156] Optionally, the processor 910 is used for: An execution request is sent to the child node. The execution request includes the subtask and authorization information, and the authorization information includes the effective time and scope of action.

[0157] Optionally, the processor 910 is used for: If the task execution path is generated, display the path tree of the task execution path; The task execution path is updated based on the user's adjustments to the path tree.

[0158] Optionally, the processor 910 is used for: Generate an execution result summary of the task information, the execution result summary including at least one of the following: result data, execution process screenshot, and task suggestions.

[0159] Optionally, the processor 910 is used for: Record the execution information for each action.

[0160] It should be understood that, in this embodiment, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042. The GPU 9041 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 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 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.

[0161] The memory 909 can be used to store software programs and various data. The memory 909 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 909 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 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0162] Processor 910 may include one or more processing units; optionally, processor 910 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 910.

[0163] 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.

[0164] 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.

[0165] 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.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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 in that, include: Obtain user task information; Based on the task information and historical operation information, a task execution path is generated; The task is processed according to the task execution path.

2. The method according to claim 1, characterized in that, The task information includes at least one of the following: task object, task intent, and task result; the task information obtained from the user includes: The task information is obtained by parsing the user input; or... The task information is obtained by listening to specific events.

3. The method according to claim 1, characterized in that, The step of generating a task execution path based on the task information and historical operation information includes: Analyze the structure of each target interface associated with the task information to determine the operable elements; Construct a behavioral model of the task information based on the historical operation information; The task execution path is generated based on the behavior model and the operable elements.

4. The method according to claim 1, characterized in that, The step of processing tasks according to the task execution path includes: When the task information corresponds to multiple devices, each sub-node in the task execution path is determined, and a sub-task for each sub-node is generated; wherein each sub-node corresponds to one of the multiple devices, and the sub-task includes at least one of the following: behavior flow, anchor coordinates, and expected state; The subtask is distributed to the corresponding child node.

5. The method according to claim 4, characterized in that, The step of distributing the subtask to the corresponding child node includes: An execution request is sent to the child node. The execution request includes the subtask and authorization information, and the authorization information includes the effective time and scope of action.

6. The method according to claim 1, characterized in that, The method further includes: If the task execution path is generated, display the path tree of the task execution path; The task execution path is updated based on the user's adjustments to the path tree.

7. The method according to claim 1, characterized in that, The method further includes: Generate an execution result summary of the task information, the execution result summary including at least one of the following: result data, execution process screenshot, and task suggestions.

8. A task processing device, characterized in that, include: The acquisition module is used to acquire the user's task information; The first processing module is used to generate a task execution path based on the task information and historical operation information; The second processing module is used to process tasks according to the task execution path.

9. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the task processing method as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the task processing method as described in any one of claims 1-7.

Images