A data processing method and device, electronic equipment and storage medium

Abstract

The present application relates to the technical field of artificial intelligence, and particularly relates to a data processing method and device, electronic equipment and storage medium. The data processing method comprises the following steps: obtaining a task description input by a user; performing an analysis operation on the task description to generate an execution strategy; the execution strategy comprises at least one atomic operation; determining a permission type of the atomic operation; executing the atomic operation based on the permission type of the atomic operation, and obtaining an action type of the atomic operation; in the case that the action type of the atomic operation is a change operation, generating a withdrawal strategy of the atomic operation, and displaying a withdrawal control of the withdrawal strategy in a preset area corresponding to the atomic operation in a target page. Thus, the atomic level withdrawal of the task can be realized, which not only facilitates the user to perform the withdrawal operation, but also greatly improves the system security.

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence technology, and in particular to a data processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] Currently, autonomous decision-making AI agents can invoke external tools, modify data, and initiate network communications based on user natural language commands. In the field of security management, existing technologies primarily focus on pre-execution permission verification (such as single-confirmation pop-ups, pre-set blacklists and whitelists) and post-execution development-state link tracing. Their management granularity remains at the global task level, exhibiting a one-time decision characteristic. This makes authorization confirmations made by users due to insufficient information or judgment errors irreversible. Once misauthorization occurs, the resulting side effects such as data tampering, state corruption, and external communication disruptions cannot be accurately eliminated, constituting a significant system security vulnerability. Summary of the Invention

[0003] To address the problems of the prior art, embodiments of this application provide a data processing method, apparatus, electronic device, and storage medium. The technical solution is as follows: On the one hand, a data processing method is provided, which is applied to an intelligent agent; the method includes: Obtain the task description input by the user; The task description is parsed to generate an execution strategy; the execution strategy includes at least one atomic operation. Determine the permission type of the atomic operation; Execute the atomic operation based on the permission type of the atomic operation, and obtain the action type of the atomic operation; When the action type of the atomic operation is a change operation, a reversal strategy for the atomic operation is generated, and the reversal control of the reversal strategy is displayed in the preset area corresponding to the atomic operation on the target page.

[0004] In one exemplary implementation, performing the atomic operation based on the permission type of the atomic operation includes: The atomic operation is executed when the permission type of the atomic operation is the first permission type; the first permission type indicates that the agent is always allowed to execute it directly. When the permission type of the atomic operation is the second permission type, a permission pop-up window is displayed; in response to the user's permission operation in the permission pop-up window, the atomic operation is executed; the second permission type indicates that the agent needs user authorization for each execution. When the permission type of the atomic operation is the third permission type, the security risk status of the atomic operation is obtained; the atomic operation is executed based on the security risk status of the atomic operation; the third permission type indicates that user authorization is required when the atomic operation is a highly sensitive type.

[0005] In one exemplary implementation, performing the atomic operation based on the security risk situation of the atomic operation includes: Determine whether the atomic operation is a sensitive or high-risk operation. If so, display a permission pop-up. In response to the user's permission in the permission pop-up, execute the atomic operation. If not, execute the atomic operation directly.

[0006] In one exemplary implementation, the execution strategy includes at least two atomic operations; the action type of the at least two atomic operations is a change operation; the target page displays a batch undo control; the method further includes: In response to the user's selection of the batch recall control, a batch recall page is generated; the batch recall page displays at least two atomic operations that can be recalled and a total recall control; In response to the user's selection of any one of the at least two atomic operations or the selection of the overall undo control, the undo strategy of the target atomic operation is obtained; and the target atomic operation is restored based on the undo strategy of the target atomic operation.

[0007] In one exemplary implementation, the target page displays a plurality of the atomic operations listed in order of execution time; the method further includes: In response to the user's selection operation on the undo control, the undo strategy of the atomic operation is obtained; and the atomic operation is restored based on the undo strategy of the atomic operation.

[0008] In one exemplary implementation, it further includes: In response to the user's selection of the undo control, update the display state of the atomic operation corresponding to the undo control on the target page.

[0009] In one exemplary implementation, it further includes: Determine the time limit for the reversibility of the atomic operation and display it on the target page.

[0010] On the other hand, a data processing apparatus is provided, the apparatus comprising: The acquisition module is used to acquire the task description input by the user. The parsing module is used to parse the task description and generate an execution strategy; the execution strategy includes at least one atomic operation. A determination module is used to determine the permission type of the atomic operation; An execution module is configured to execute the atomic operation based on its permission type, and to obtain the action type of the atomic operation. The generation module is used to generate a reversal strategy for the atomic operation when the action type of the atomic operation is a change operation, and to display the reversal control of the reversal strategy in a preset area corresponding to the atomic operation on the target page.

[0011] On the other hand, an electronic device is provided, including a processor and a memory; The memory stores at least one instruction or at least one program segment, which is loaded and executed by the processor to implement any of the above-described data processing methods.

[0012] On the other hand, a computer-readable storage medium is provided, wherein at least one instruction or at least one program is stored therein, the at least one instruction or the at least one program being loaded and executed by a processor to implement the data processing method as described in any of the above aspects.

[0013] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the data processing method described above.

[0014] This application embodiment obtains a task description input by the user; parses the task description to generate an execution strategy; the execution strategy includes at least one atomic operation; determines the permission type of the atomic operation; executes the atomic operation based on the permission type, and obtains the action type of the atomic operation; if the action type of the atomic operation is a change operation, generates a reversal strategy for the atomic operation, and displays a reversal control of the reversal strategy in a preset area corresponding to the atomic operation on the target page. This enables atomic-level reversal of tasks, which not only facilitates reversal operations for users but also greatly improves system security. Attached Figure Description

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

[0016] Figure 1 This is a flowchart illustrating a data processing method provided in an embodiment of this application; Figures 2 to 11 This is a visual page diagram illustrating a data processing method provided in this application embodiment.

[0017] Figure 12 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application; Figure 13 This is a hardware structure block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

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

[0020] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0021] Please see Figure 1The diagram shown is a flowchart illustrating a data processing method provided in an embodiment of this application. The method may specifically include: S101: Obtain the task description input by the user.

[0022] For example, the task description can be content entered on the agent's input page, and its format can be text, images, videos, or a combination of these. After the agent receives the task description entered by the user, it can subsequently generate pre-executed operations and an operation context. For example, please refer to... Figure 2 The user inputs a task description of "deleting duplicate photos from last year's business trip". The agent performs reasoning to determine the tools to be called, specific parameters, target objects (photos), and reasoning summary (e.g., after scanning 1,286 photos in the album, 10 high-confidence duplicates have been moved to the recycle bin, and 22 photos with similarity boundaries are still kept in the original album).

[0023] The task title, initiation time, user-inputted task description, and task summary can be archived and stored, and then displayed on the target page (e.g., ...). Figure 2 (as shown on the page).

[0024] For example, the intelligent agent can be deployed on a client or a server. Optionally, the intelligent agent can include multiple processing modules that can work collaboratively. Optionally, the processing modules of the intelligent agent can be deployed on the same device (terminal or server), or they can be deployed on different devices. Optionally, the intelligent agent can include a visualization module, a permission management module, a risk assessment module, a file management module, and a recovery module. The visualization module can be used to generate visual content (such as highlighting text), the permission association module is used to manage various permissions, the risk assessment module can assess the risk of atomic operations, the file management module is used to obtain the task-related information to be stored, and the recovery module is used to reverse the undone atomic operations.

[0025] It should be noted that the server involved in the embodiments of this application can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, and big data and artificial intelligence platforms.

[0026] S103: Perform a parsing operation on the task description to generate an execution strategy; the execution strategy includes at least one atomic operation.

[0027] For example, please continue reading Figure 2 "Clustering by similarity and marking candidates" is an atomic operation. By dividing the execution strategy into atomic-level operations, it is easier to manage independently later (such as atomic-level retraction).

[0028] For example, depending on the task type, the inferred execution strategy may include one atomic operation or multiple atomic operations, as long as they are the finest-grained execution operations.

[0029] S105: Determine the permission type of the atomic operation.

[0030] For example, users can configure permissions in the configuration interface, thereby generating a corresponding table of operations and permissions. Subsequently, the corresponding permission type can be found from the table based on the identifier of the atomic operation.

[0031] For example, please refer to Figure 3 The capabilities that an agent can execute can be grouped and managed according to the dimension of "operation domain," including at least four primary groups: System Control and Settings (including system settings and device control, AI voice and personalization, screen understanding and screenshots, location access, etc.), Communication (including contacts, calls and call logs, messages and notifications, etc.), Personal Data Management (including schedules and to-dos, photo albums and media, recording and speech recognition, notes and document understanding, files and workspaces, application management and clipboard, etc.), and Networking and Automation (including networking and information retrieval, automation and scheduled tasks, conversations and agent collaboration, Shell and code execution, cross-device control, system and gateway management, etc.). Each specific permission item can be independently configured by the user into one of the following three permission types: First permission type: The first permission type indicates that the agent is always allowed to execute directly; such as "allow" (no further questioning, direct access).

[0032] Second permission type: The second permission type indicates that the agent needs user authorization for each execution; such as "each time you ask" (each execution requires user authorization).

[0033] Third permission type: The third permission type indicates that user authorization is required when the atomic operation is a highly sensitive type; such as "prompt for sensitive operation" (an authorization request will only pop up when an operation that is judged to be sensitive or risky in this domain is executed).

[0034] S107: Execute the atomic operation based on the permission type of the atomic operation, and obtain the action type of the atomic operation.

[0035] In an exemplary implementation, step S107, which involves executing the atomic operation based on the permission type of the atomic operation, may specifically include: executing the atomic operation when the permission type of the atomic operation is a first permission type; the first permission type indicates that the agent is always allowed to execute directly; displaying a permission pop-up when the permission type of the atomic operation is a second permission type; executing the atomic operation in response to the user's permission operation on the permission pop-up; the second permission type indicates that the agent needs user authorization for each execution; obtaining the security risk status of the atomic operation when the permission type of the atomic operation is a third permission type; and executing the atomic operation based on the security risk status of the atomic operation; the third permission type indicates that user authorization is required when the atomic operation is a highly sensitive type.

[0036] Understandably, when multiple atomic operations are involved, this solution can first determine the permission type of each atomic operation. If multiple atomic operations require user authorization, an authorization pop-up can be displayed before executing multiple atomic operations, and no authorization pop-up needs to be displayed when executing the atomic operations, thereby improving processing efficiency.

[0037] For example, please refer to Figure 4 Before an agent performs an operation in the dialogue flow, this layer primarily determines the operation based on the authorization policy of the corresponding permission item in the preset permission layer. When the preset is "Allow," the operation is allowed directly without a pop-up authorization window. When the preset is "Ask on every request," an authorization pop-up appears as a floating card regardless of the risk level. When the preset is "Ask on sensitive operations," the authorization pop-up appears only when the current operation is deemed risky, taking into account the risk level of the atomic operation. The authorization pop-up includes the name of the requested permission, a description of the permission's function, and three authorization options: "Always Allow" (simultaneously updating the corresponding operation's permission to "Allow"), "Allow only this time," and "Deny." When the current operation is determined to be "High Risk" by the risk level assessment module, a red label (such as a "High Risk" label) is added to the pop-up to highlight the risk; other risk levels are not visually emphasized. If the user selects "Always Allow" or "Allow only this time," the process proceeds to step S109; selecting "Deny" terminates the current operation, allowing the user to simply record the data without execution.

[0038] For example, highlighting the "high-risk" label can also be achieved by changing the overall color of the pop-up window or using a red border, or by gradually increasing the screen occupancy ratio or adding interactive friction.

[0039] In an exemplary implementation, step S107, which involves executing the atomic operation based on its security risk status, may specifically include: determining whether the atomic operation is a sensitive or high-risk operation; if so, displaying a permission pop-up window; and executing the atomic operation in response to the user's permission action in the permission pop-up window; otherwise, directly executing the atomic operation.

[0040] For example, sensitive operations are specifically defined by the sensitivity of the data, which can be categorized according to data type as follows: 1- Device status data (low level); 2- General personal data (medium level); 3- Highly sensitive personal data (high level); 4- Critical sensitive data (high level). Therefore, when executing a task, based on dual verification of permission and data sensitivity, it is determined whether the task is dangerous, requires user confirmation, and needs to support reversal.

[0041] Specifically, based on the information about the operation the agent is about to execute (including the target tool, the object of the operation, the operation parameters, and the task description input by the user), and according to a preset rule set or risk model, the risk level and corresponding behavioral attribute label for each operation can be output. The risk level is divided into at least three levels: low, medium, and high; please refer to [link / reference]. Figure 5 Behavioral attribute tags include, but are not limited to, "Irreversible" (such as batch deletion that has already been issued), "Intercepted" (such as the system refusing to execute due to high risk), "Autonomous" (non-interactive steps that the agent automatically completes within the authorized scope), and "Batch" (operations that affect multiple objects at once), which can be displayed in the preset area of ​​the corresponding atomic operation, such as below.

[0042] For example, the risk levels and labels mentioned above are directly attached to the corresponding atomic operations in the form of color markers on the behavior recording interface (e.g., "intercepted" is presented in red, "autonomous" in blue, and "batch" in cyan), so that end users can intuitively identify the risk nature of each behavior.

[0043] For example, the risk level assessment method can be based on a preset rule set (a combination of white / black lists of tools and operation types), or it can be implemented by an independent risk classification model, or it can be implemented by calling the agent's own self-reflection ability; or it can be any two or three of the above three methods combined.

[0044] Understandably, it's also possible to statistically analyze the selections made in the authorization pop-ups corresponding to each atomic operation, and adjust the risk level or permissions for that atomic operation accordingly. For example, if a user consistently selects "allow" in the authorization pop-up for a specific atomic operation, its risk level can be lowered, or the permission type can be adjusted to the highest permission type. This adjustment process can be implemented based on a model or through statistical processing using preset functions.

[0045] S109: When the action type of the atomic operation is a change operation, generate the reversal strategy of the atomic operation and display the reversal control of the reversal strategy in the preset area corresponding to the atomic operation on the target page.

[0046] In this embodiment, the change operation can specifically include operations that modify or move objects, such as deletion, modification, and movement.

[0047] For example, the target page can be like this Figure 5 The secondary page shown can also be like... Figure 2 The main page shown here is not limited to any specific actions. Specifically, to facilitate user organization and review, historical actions can be filtered by three dimensions: "All / Blocked / Reversible"; related actions can be grouped by "Task" (e.g., "Spam Delete," "Organize Travel Photos in Gallery"), with each task displaying its specific action pages in a timeline format. Each action page includes execution time, action description, action attribute tags (e.g., irreversible, blocked, autonomous, batch, etc.), and necessary image or data previews; for reversible actions still within the recovery window (i.e., effective immediately), please refer to [link to relevant documentation]. Figure 6 Batch revocation control can be directly embedded below the corresponding behavior page, such as the "Revoke this operation" button. After the user clicks the button, the "Agent Risk Behavior Recovery Module" is invoked to perform subsequent recovery operations.

[0048] In one exemplary implementation, the target page displays a plurality of atomic operations listed in order of execution time; the method further includes: in response to a user's selection of the undo control, obtaining an undo strategy for the atomic operation; and performing a redo operation on the atomic operation based on the undo strategy. For example, when a user clicks the "Undo this operation" control, the atomic operation can be redone.

[0049] In one exemplary implementation, the method further includes: determining the revocable validity period of the atomic operation and displaying it on the target page.

[0050] For example, the revocable period is at least one week, and can also be configured with different durations such as 30 days and 90 days. Users can also customize the upper limit of the duration according to the operation type, or the system can make adaptive adjustments based on the user's historical revocable behavior; but the duration is at least 1 day.

[0051] For example, please refer to Figure 2 The remaining time and the revocable status of each atomic operation (such as "Some risky operations are revocable, with 17 days and 6 hours remaining") can be displayed in a prominent color below the summary on the target page.

[0052] After the period for revocability has expired, please refer to Figure 7 The system can display an expiration message (e.g., "Time window expired, operation cannot be undone" in blue text) in the corresponding location, replacing the original button. The behavior will only be presented on the timeline in an "audit-only" state, clearly informing the user that the behavior has expired and cannot be undone. At the same time, the timestamp, behavior description, behavior attribute label, image or data preview and other file content of the behavior will still be completely retained on the timeline for users to audit and trace in the long term, and will not be lost due to window expiration.

[0053] For example, please refer to Figure 8 The security management page can also display operation statistics for different time ranges, such as "today / last 7 days / last 1 month" as dimensions, and intuitively present the overall behavior of the agent within the current period using three core indicators: "number of operations / intercepted / can be revoked". Below, a bar chart shows the density of behavior occurrences, helping users quickly identify abnormal clusters. This security management page also provides two interfaces: "All Behavior Records" and "Agent Permission Management". Subsequent actions by the user selecting the "All Behavior Records" control can redirect to... Figure 5 The page shown, in response to the user's selection of the "Intelligent Agent Permission Management" control, can redirect to, as follows: Figure 3 The page shown.

[0054] It should be noted that when revoking an atomic operation, the reverse operation or compensatory notification of each selected operation should be executed in reverse chronological order of the occurrence of the operation to avoid conflicts caused by dependencies between reverse operations (for example, the revocation of "creating a new group for duplicate photos" should be performed after the revocation of "deleting photos" to ensure that the photos are returned to their original positions before the group is removed). After all selected operations have been processed, the security profile is unified, and a "restored" mark is added to each revoked operation, and the visual status change of the corresponding operation page is updated.

[0055] In another exemplary embodiment, the execution strategy includes at least two atomic operations; the action type of the at least two atomic operations is a change operation; the target page displays a batch undo control; the method further includes: generating a batch undo page in response to a user's selection of the batch undo control; the batch undo page displays at least two undoable atomic operations and a total undo control. In response to a user's selection of any one of the at least two atomic operations or the total undo control, the undo strategy of the target atomic operation is obtained; and a restoration operation is performed on the target atomic operation based on the undo strategy of the target atomic operation. This enables batch undo operations of multiple atomic operations, improving undo efficiency.

[0056] For example, please refer to Figure 6 The "Cancel All N Operations" option can be displayed as a floating button at the bottom of the task details page, where N is the number of actions that can still be canceled under this task. At the same time, each cancelable action under this task still retains its own "Cancel This Operation" button, allowing users to freely choose between "batch cancellation" and "single cancellation" granularity.

[0057] After the user clicks "Cancel all N operations", please refer to [link / reference]. Figure 9 This feature allows for a secondary confirmation pop-up for batch recall. The pop-up lists all revocable actions for the task, with each action displayed in a separate area. Each area can include an action title (e.g., "Delete 12 highly similar photos," "Delete 5 highly similar photos," "Create a new group for duplicate photos 'Business Trip'," etc.), an image or data preview of the action, a text description of the recall result, and a separate checkbox. The pop-up defaults to selecting all actions; users can uncheck items they don't want to recall. The bottom of the pop-up displays a confirmation message. The "Recall" button displays the number of currently selected behaviors in parentheses in real time (e.g., "Recall (3)"), and is highlighted in red; the user clicks the button to proceed to the actual execution. Optionally, the default selection state of the batch recall secondary confirmation pop-up can be "Select All" (as in this solution), "Deselect All" or "Smart Pre-selection Based on Behavior Attributes" (e.g., by default, all behaviors with the "Batch" tag are selected but behaviors with the "Autonomous" tag are not selected); the execution order of the reverse operation can be in reverse chronological order, or it can be executed after topological sorting based on the dependency graph pre-registered in the file.

[0058] Understandably, please refer to Figure 10 When a user attempts to undo a single atomic operation, a secondary confirmation pop-up will still appear to remind the user and prevent accidental operation.

[0059] In one exemplary implementation, the method further includes: updating the display state of the atomic operation corresponding to the undo control on the target page in response to the user's selection operation on the undo control.

[0060] For example, please refer to Figure 11 After the user clicks "Withdraw" in the secondary confirmation pop-up, the "Restored" mark is written back after the operation is completed, and the status of the corresponding behavior changes visually—the original behavior title is presented with a strikethrough or grayed out, and a red withdrawal result description is added below (e.g., "This operation was withdrawn on April 20, and the photo has been returned to its original position"), providing the user with clear feedback on the recovery result and auditable traceable evidence.

[0061] Understandably, once the failure ends or the operation is restored, the atomic operation will be permanently stored in an "audit-only" state. The operation information in the archive can be recorded according to risk level, operation type, affected objects, time, and other dimensions, facilitating user filtering and review. Operation types can include "delete," "pay," and "move," etc.; affected objects can include "photos," "videos," "contacts," etc.

[0062] This solution records the state of the object before and after execution, the user-input task description, reasoning summary, and scope of impact, making it easy for users to review and trace back. At the same time, it determines and labels the reversibility of the operation—reversible (such as local data modification, state changes that can be restored by reverse API) and irreversible (such as deductions of funds that have already occurred, data that has been written to a third-party irreversible system). For reversible operations, a pre-reverse operation description (including state snapshot, reverse API call, and compensatory notification) is created and temporarily stored. At the same time, a recovery window with a unified reversible validity period (e.g., 30 days) is opened, and the file remains in an "active and recoverable" state within the validity period.

[0063] Recorded files can be stored locally on the client (suitable for privacy-sensitive scenarios), stored on the server (suitable for multi-device synchronization scenarios), or a combination of both.

[0064] As can be seen from the above technical solutions of the embodiments of this application, the embodiments of this application integrate the three major mechanisms of pre-warning, in-process security archive, and post-event reversal into a unified security control link. Specifically, the archive entries generated during pre-authorization, the operation snapshots and reverse operation descriptions supplemented during in-process execution, and the reversal operations triggered by the user in the retrospective interface after the event are all maintained and scheduled by the same security archive and the same recovery module. Users can directly initiate reversal or compensation from any historical behavior on the timeline after the event, eliminating the problem of isolated security mechanisms and inability to directly access recovery operations from behavior records in existing solutions. Moreover, for expired originally reversible behaviors—that is, behaviors that have changed from "active and recoverable" to "auditable only"—their current recoverability status is clearly conveyed through "removing the reversal entry + explicitly indicating the expiration text," avoiding users having incorrect expectations about historical behaviors.

[0065] By maintaining a relatively long and uniform security recovery window for reversible actions after execution, users can make more thorough judgments and trigger rollbacks based on the complete operational context within this window. Risky behaviors can be perceived, attributed, and traced by end users. The security profile module binds "pre-operation state—user intent—reasoning—post-operation state—scope of impact—risk level" into a structured profile and presents it in a way that is understandable to end users through the backtracking interface; users can independently complete the attribution review of risky behaviors within the product interface without relying on developer-side debugging logs.

[0066] Corresponding to the data processing methods provided in the above embodiments, this application also provides a data processing apparatus. Since the data processing apparatus provided in this application corresponds to the data processing methods provided in the above embodiments, the implementation methods of the aforementioned data processing methods are also applicable to the data processing apparatus provided in this embodiment, and will not be described in detail in this embodiment.

[0067] Please see Figure 12 The diagram shown is a structural schematic of a data processing device provided in an embodiment of this application. This device has the function of implementing the data processing method described in the above-described method embodiments. This function can be implemented by hardware or by hardware executing corresponding software. Figure 12 As shown, the data processing device 1200 may include: Module 1210 is used to obtain the task description input by the user; Parsing module 1220 is used to parse the task description and generate an execution strategy; the execution strategy includes at least one atomic operation; The determination module 1230 is used to determine the permission type of the atomic operation; The execution module 1240 is used to execute the atomic operation based on the permission type of the atomic operation, and to obtain the action type of the atomic operation; The generation module 1250 is used to generate a reversal strategy for the atomic operation when the action type of the atomic operation is a change operation, and to display the reversal control of the reversal strategy in a preset area corresponding to the atomic operation on the target page.

[0068] In one exemplary embodiment, the execution module is configured to execute the atomic operation when the permission type of the atomic operation is a first permission type; the first permission type indicates that the agent is always allowed to execute directly. When the permission type of the atomic operation is the second permission type, a permission pop-up window is displayed; in response to the user's permission operation in the permission pop-up window, the atomic operation is executed; the second permission type indicates that the agent needs user authorization for each execution. When the permission type of the atomic operation is the third permission type, the security risk status of the atomic operation is obtained; the atomic operation is executed based on the security risk status of the atomic operation; the third permission type indicates that user authorization is required when the atomic operation is a highly sensitive type.

[0069] In one exemplary implementation, the execution module is configured to determine whether the security risk of the atomic operation is a sensitive or high-risk operation. If so, a permission pop-up window is displayed; in response to the user's permission operation in the permission pop-up window, the atomic operation is executed; otherwise, the atomic operation is executed directly.

[0070] In one exemplary embodiment, the execution strategy includes at least two atomic operations; the action type of the at least two atomic operations is a change operation; the target page displays a batch undo control; the device further includes: The first page generation module is used to generate a batch recall page in response to the user's selection operation of the batch recall control; the batch recall page displays at least two atomic operations that can be recalled and a total recall control; The first strategy acquisition module is used to acquire the withdrawal strategy of the target atomic operation in response to the user's selection operation of any one of the at least two atomic operations or the selection operation of the total withdrawal control; and to perform a recovery operation on the target atomic operation based on the withdrawal strategy of the target atomic operation.

[0071] In one exemplary embodiment, the target page displays a plurality of the atomic operations listed in order of execution time; the apparatus further includes: The second strategy acquisition module is used to acquire the revocation strategy of the atomic operation in response to the user's selection operation of the revocation control; and to perform a revocation operation on the atomic operation based on the revocation strategy of the atomic operation.

[0072] In one exemplary embodiment, the apparatus further includes: The second page generation module is used to update the display state of the atomic operation corresponding to the undo control on the target page in response to the user's selection operation on the undo control.

[0073] In one exemplary embodiment, the apparatus further includes: The timeliness determination module is used to determine the revocable timeliness of the atomic operation and display it on the target page.

[0074] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0075] This application provides an electronic device including a processor and a memory. The memory stores at least one instruction or at least one program segment, which is loaded and executed by the processor to implement any of the data processing methods provided in the above method embodiments.

[0076] Memory can be used to store software programs and modules. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory. Memory can primarily include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for the functions, etc.; the data storage area can store data created based on the use of the device, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.

[0077] The method embodiments provided in this application can be executed in a computer terminal, server or similar computing device, that is, the above-mentioned electronic device may include a computer terminal, server or similar computing device. Figure 13 This is a hardware structure block diagram of an electronic device that runs a data processing method, as provided in an embodiment of this application.

[0078] The electronic device includes: a processor 1310, a memory 1320, an input / output interface 1330, a communication interface 1340, and a bus 1350.

[0079] The processor 1310 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this disclosure. The memory 1320 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1320 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1320, and the processor 1310 calls and executes the cache parameter determination method of the embodiments of this disclosure. The input / output interface 1330 is used to implement information input and output; The communication interface 1340 is used to enable communication and interaction between this device and other devices. Communication can be achieved via wired means (e.g., USB, Ethernet cable) or wireless means (e.g., mobile network, Wi-Fi, Bluetooth). Bus 1350 transmits information between various components of the device (e.g., processor 1310, memory 1320, input / output interface 1330, and communication interface 1340); The processor 1310, memory 1320, input / output interface 1330 and communication interface 1340 are connected to each other within the device via bus 1350.

[0080] Embodiments of this application also provide a computer-readable storage medium, which can be disposed in an electronic device to store at least one instruction or at least one program related to implementing a data processing method. The at least one instruction or the at least one program is loaded and executed by the processor to implement any of the data processing methods provided in the above-described method embodiments.

[0081] Embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform any of the data processing methods provided in the above-described method embodiments.

[0082] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0083] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0084] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0085] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0086] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A data processing method, characterized in that, Applied to intelligent agents; the method includes: Obtain the task description input by the user; The task description is parsed to generate an execution strategy; the execution strategy includes at least one atomic operation. Determine the permission type of the atomic operation; Execute the atomic operation based on the permission type of the atomic operation, and obtain the action type of the atomic operation; When the action type of the atomic operation is a change operation, a reversal strategy for the atomic operation is generated, and the reversal control of the reversal strategy is displayed in the preset area corresponding to the atomic operation on the target page.

2. The data processing method according to claim 1, characterized in that, Executing the atomic operation based on the permission type of the atomic operation includes: The atomic operation is executed when the permission type of the atomic operation is the first permission type; the first permission type indicates that the agent is always allowed to execute it directly. When the permission type of the atomic operation is the second permission type, a permission pop-up window is displayed; in response to the user's permission operation in the permission pop-up window, the atomic operation is executed; the second permission type indicates that the agent needs user authorization for each execution. When the permission type of the atomic operation is the third permission type, the security risk status of the atomic operation is obtained; the atomic operation is executed based on the security risk status of the atomic operation; the third permission type indicates that user authorization is required when the atomic operation is a highly sensitive type.

3. The data processing method according to claim 2, characterized in that, Performing the atomic operation based on the security risk situation of the atomic operation includes: Determine whether the atomic operation is a sensitive or high-risk operation. If so, display a permission pop-up. In response to the user's permission in the permission pop-up, execute the atomic operation. If not, execute the atomic operation directly.

4. The data processing method according to claim 1, characterized in that, The execution strategy includes at least two atomic operations; the action type of the at least two atomic operations is a change operation; the target page displays a batch undo control; the method further includes: In response to the user's selection of the batch recall control, a batch recall page is generated; the batch recall page displays at least two atomic operations that can be recalled and a total recall control; In response to the user's selection of any one of the at least two atomic operations or the selection of the overall undo control, the undo strategy of the target atomic operation is obtained; and the target atomic operation is restored based on the undo strategy of the target atomic operation.

5. The data processing method according to claim 1, characterized in that, The target page displays multiple atomic operations listed in order of execution time; the method further includes: In response to the user's selection operation on the undo control, the undo strategy of the atomic operation is obtained; and the atomic operation is restored based on the undo strategy of the atomic operation.

6. The data processing method according to any one of claims 1-5, characterized in that, Also includes: In response to the user's selection of the undo control, update the display state of the atomic operation corresponding to the undo control on the target page.

7. The data processing method according to any one of claims 1-5, characterized in that, Also includes: Determine the time limit for the reversibility of the atomic operation and display it on the target page.

8. A data processing apparatus, characterized in that, The device includes: The acquisition module is used to acquire the task description input by the user. The parsing module is used to parse the task description and generate an execution strategy; the execution strategy includes at least one atomic operation. A determination module is used to determine the permission type of the atomic operation; An execution module is configured to execute the atomic operation based on its permission type, and to obtain the action type of the atomic operation. The generation module is used to generate a reversal strategy for the atomic operation when the action type of the atomic operation is a change operation, and to display the reversal control of the reversal strategy in a preset area corresponding to the atomic operation on the target page.

9. An electronic device, characterized in that, Including processor and memory; The memory stores at least one instruction or at least one program segment, which is loaded and executed by the processor to implement the data processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the data processing method as described in any one of claims 1 to 7.

Images