Data processing methods, devices and electronic equipment
By setting up a target interface layer between the operating system and command-line tools, intercepting and detecting operation commands, and identifying and displaying source information, the problem of users being unable to identify the background behavior of intelligent agents in existing technologies is solved, thereby improving operational transparency and security.
Patent Information
- Application Number
- CN202611342206.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-11-17
AI Technical Summary
Existing operating systems and command-line environments lack mechanisms to distinguish and indicate the source of command calls, making it impossible for users to perceive the background behavior of intelligent agents in real time, which poses a security risk.
By setting up a target interface layer between the operating system and command-line tools, the system intercepts and detects operation commands, determines the source based on the matching degree between user operation information and commands, and displays the source information during command execution.
It enables accurate differentiation of the source of operation instructions, improves the transparency of human-machine collaborative operation, reduces security risks, and provides operation audit records to facilitate post-event traceability and security review.
Smart Images

Figure CN123114892A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a data processing method, apparatus and electronic device. Background Technology
[0002] Currently, an increasing number of AI agents (hereinafter referred to as agents) are being deployed on electronic devices. These agents can run independently within the operating system as background processes, autonomously calling command-line tools to execute various operation commands. In practical applications, when agents automatically execute operation commands in the background, users find it difficult to perceive the agent's behavior in real time. This is especially true after the agent is granted full operational privileges, making it impossible for users to effectively monitor its background behavior, posing security risks in human-machine collaborative operation scenarios. Existing operating systems and command-line environments lack mechanisms at the architectural level to distinguish and indicate the source of command calls, failing to provide users with identification information about the source of operation commands. Summary of the Invention
[0003] This application provides a data processing method, comprising: if an operation instruction is received through a target interface layer, detecting user operation information; the target interface layer is used to intercept the operation instruction sent to the operating system; determining the source information of the operation instruction based on the matching degree between the user operation information and the operation instruction; and displaying the source information during the execution of the operation instruction.
[0004] In some embodiments, determining the source information of an operation instruction based on the matching degree between the user's operation information and the operation instruction includes: determining an operation event sequence based on the user's operation information; the operation event sequence represents at least one operation event performed by the user within a preset time period; if there is an event in the operation event sequence that matches the operation instruction, the source information indicates that the operation instruction originates from the user; if there is no event in the operation event sequence that matches the operation instruction, the source information indicates that the operation instruction originates from the intelligent agent.
[0005] In some embodiments, detecting user operation information includes at least one of the following methods: acquiring user input data through the operating system's input event application programming interface; acquiring user input data through a human-machine interface device driver; or acquiring user input data through data interaction with an external input device.
[0006] In some embodiments, displaying source information includes at least one of the following: displaying source information overlaid on a graphical user interface element via a main display unit, the graphical user interface element including at least one of text labels, graphic identifiers, or color indicators; and indicating the source attribution of an operation command via an auxiliary indicator device independent of the main display unit, using the state of the light emission color or the flashing rhythm.
[0007] In some embodiments, after determining the source information of the operation instruction, the method further includes: obtaining permission information, which records a set of instructions that are prohibited from being executed by the agent; and intercepting the execution of the operation instruction when the matching degree indicates that the operation instruction originates from the agent and the operation instruction belongs to the permission information.
[0008] In some embodiments, the method further includes storing operation instructions with attached source information in the storage area corresponding to the target interface layer to form an operation audit record.
[0009] In some embodiments, displaying source information includes at least one of the following display states: displaying the agent in an operation execution state alone; displaying the user in an operation execution state alone; and displaying the agent and user in a parallel operation execution state simultaneously.
[0010] This application also provides a data processing apparatus, comprising: a detection module, which detects user operation information if an operation instruction is received through a target interface layer; the target interface layer is used to intercept operation instructions sent to the operating system; a determination module, which determines the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; and a display module, which displays the source information during the execution of the operation instruction.
[0011] This application provides an electronic device, including an input component for receiving user input operations; a display component for displaying information; a processor for detecting user operation information if an operation instruction is received through a target interface layer; the target interface layer for intercepting operation instructions sent to the operating system; determining the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; and displaying the source information during the execution of the operation instruction.
[0012] In some embodiments, the processor operates a target interface layer, a source determination layer, a tagging layer, a display control layer, and an instruction execution layer. The target interface layer is used to intercept operation instructions sent to the operating system and receive the operation instructions. The source determination layer is used to detect the user's operation information through an input component after the target interface layer receives the operation instructions, and determine the source information of the operation instructions based on the matching degree between the user's operation information and the operation instructions. The tagging layer is used to attach a source identifier to the operation instructions according to the source information determined by the source determination layer. The display control layer is used to control the display component to display the source information during the execution of the operation instructions. The instruction execution layer is used to execute the operation instructions.
[0013] The beneficial effects of the data processing method in this application are as follows: By setting a target interface layer between the operating system and command-line tools, all operation commands can be uniformly intercepted and received, providing a reliable data collection entry point for subsequent source identification and preventing commands from bypassing the detection mechanism; by detecting user operation information and matching it with operation commands, it is possible to accurately distinguish whether the operation command originates from the user's manual operation or from the automatic invocation of the intelligent agent, filling the gap in the existing operating system and command-line environment's mechanism for distinguishing the source of command invocation. During the execution of operation commands, source information is displayed synchronously, allowing users to know in real time whether the currently executed command originates from their own operation or from the intelligent agent, effectively improving the transparency of the intelligent agent's background behavior and reducing security risks in human-machine collaborative operation scenarios. Attached image description: Figure 1 This illustration shows a flowchart of a data processing method according to an embodiment of this application; Figure 2 A flowchart illustrating step S120 of an embodiment of this application is shown schematically; Figure 3 A flowchart illustrating another embodiment of the data processing method of this application is shown schematically; Figure 4 This illustration schematically shows a scenario diagram of a data processing apparatus according to an embodiment of the present application; Figure 5 A schematic diagram illustrating the structure of an electronic device according to an embodiment of this application is shown. Figure 6 The diagram illustrates the functional layers operated by the processor in an embodiment of this application. Detailed Implementation
[0014] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings to enable those skilled in the art to implement them more readily. Furthermore, for clarity, portions unrelated to the description of exemplary embodiments have been omitted from the drawings. In this disclosure, it should be understood that terms such as "comprising" or "having" are intended to indicate the presence of features, numbers, steps, behaviors, components, portions, or combinations thereof disclosed in this specification, and are not intended to exclude the possibility of the presence or addition of one or more other features, numbers, steps, behaviors, components, portions, or combinations thereof. It should also be noted that, without conflict, embodiments and features in the embodiments of this disclosure can be combined with each other. The present disclosure will now be described in detail with reference to the accompanying drawings and embodiments.
[0015] With the rapid development of artificial intelligence technology, more and more intelligent agents are being deployed on electronic devices. These agents can run independently in the background of the operating system, autonomously calling command-line tools to execute various operation commands without real-time user intervention. For example, an intelligent agent can automatically execute system commands according to preset scheduled tasks, or call corresponding tool programs in response to external triggering conditions.
[0016] In the aforementioned human-machine collaborative operation scenarios, the background behavior of the intelligent agent is often invisible to the user. When the intelligent agent and the user operate simultaneously on the same electronic device, the operating system may contain both manual operation commands from the user and automatic commands invoked by the intelligent agent. However, existing operating systems and command-line environments lack a mechanism at the architectural level to distinguish and indicate the source of these two types of command invocations. This prevents the user from knowing whether the currently executing command was triggered by their own input or automatically invoked by the intelligent agent in the background. This problem not only reduces the transparency and user experience of human-machine collaborative operations but also potentially introduces security risks. For example, when an intelligent agent is granted full operational privileges, it may execute certain sensitive commands without the user's knowledge, leaving the user unable to take appropriate intervention measures due to the lack of timely notification.
[0017] In view of this, this application provides a data processing method and related apparatus, aiming to solve or at least partially solve the above-mentioned technical problems. The technical solution of this application will be described in detail below with reference to the accompanying drawings and specific embodiments.
[0018] Figure 1 The flowchart illustrating an embodiment of the data processing method of this application is shown. Figure 1 As shown, the data processing method includes steps S110 to S130.
[0019] In step S110, if an operation instruction is received through the target interface layer, the user's operation information is detected; the target interface layer is used to intercept operation instructions sent to the operating system.
[0020] For example, the target interface layer, as a logical functional layer, is set up between the operating system and command-line tools to intercept all operation commands sent to the operating system. This target interface layer does not change the instruction execution logic of the operating system itself, but provides a unified interception and reception entry point before the instructions reach the operating system kernel.
[0021] Specifically, the target interface layer is implemented through a customized command-line interpreter. Taking the Windows operating system as an example, the PowerShell source code can be obtained, and command receiving hook functions and command forwarding functions can be embedded within it to compile a customized version of PowerShell. Subsequently, by modifying system environment variables or registry configurations, the system's default command-line interpreter can be set to this customized version, ensuring that all terminal application calls are directed to this customized version, thereby achieving unified interception and reception of operation commands.
[0022] In this embodiment, the operation instructions received by the target interface layer may come from the following two sources: First, it originates from manual user input. Users manually enter commands in the command-line interface and press Enter. These commands are then submitted to the operating system via the command-line interpreter. Since the target interface layer intercepts all instructions sent to the operating system, this command is received first by the target interface layer.
[0023] Second, there are automatic invocations originating from intelligent agents. As a software process, an intelligent agent can submit commands to the operating system through system call interfaces or application programming interfaces when running in the background. These invocations are also intercepted and received by the target interface layer.
[0024] When the target interface layer receives one or both of the above operation instructions, the target interface layer itself does not know whether the instruction comes from the user or the intelligent agent, so it needs to trigger the subsequent operation source identification process.
[0025] In this embodiment, to determine the source of the operation command, the target interface layer triggers an operation source identification process upon receiving the command. This process calls an external detection module to request the current user's operation information. For example, the external detection module obtains the user's operation information by listening to operation events generated by input devices. Specifically, when using electronic devices, users perform various operations through input devices (such as keyboards, mice, touchscreens, microphones, etc.). These operations are captured by the operating system and converted into corresponding input events. By receiving these input events, the external detection module can determine whether the user is currently performing an input operation and what kind of input operation has been performed.
[0026] In step S120, the source information of the operation instruction is determined based on the matching degree between the user's operation information and the operation instruction.
[0027] For example, user manual operations and automatic invocation by intelligent agents generate different operation event characteristics on electronic devices. When a user actively performs an operation through an input device, the electronic device records the corresponding input event; when an intelligent agent automatically invokes instructions in the background, there is no accompanying user input event. Therefore, by detecting user operation information and matching it with the operation instructions received by the target interface layer, the source of the operation instruction can be determined.
[0028] Specifically, matching refers to the correlation between an operation event and an operation command in terms of input actions. For operation commands originating from a user, the user will inevitably generate a series of input events corresponding to the command content during the process of entering the command in the command-line interface. For example, when a user presses the character keys of a command on the keyboard in sequence, the operating system will record the corresponding key event sequence. When the target interface layer receives the command, it can determine that the character sequence of the command and the user's key sequence are highly consistent in content and time by comparing the command content with the user's operation event sequence, thus determining that the operation command originated from the user. For operation commands originating from an agent, since they are automatically submitted by the software process through the system call interface, the user has not performed the corresponding input operation when the target interface layer receives the operation command. Therefore, there are no operation events in the operation event sequence that match the operation command, thus determining that the operation command originated from the agent.
[0029] In step 130, during the execution of the operation instructions, the source information is displayed.
[0030] For example, after determining the source information of an operation command, this source information needs to be presented in a user-perceptible manner during the execution of the command. The purpose is to allow the user to know the origin of the currently executing command in real time, thereby improving the transparency and security of human-machine collaborative operations. It should be noted that displaying the source information "during the execution of the operation command" means that the display of the source information is synchronous with the execution of the operation command, rather than appearing only after the command is completed. This synchronous display method allows the user to perceive the source of the command in real time, enabling timely intervention when the intelligent agent executes sensitive commands.
[0031] The method in this embodiment, by setting up a target interface layer between the operating system and command-line tools, can uniformly intercept and receive all operation commands, providing a reliable data collection entry point for subsequent source identification and preventing commands from bypassing the detection mechanism. By detecting user operation information and matching it with operation commands, it can accurately distinguish whether the operation command originates from the user's manual operation or from the automatic invocation of the intelligent agent, filling the gap in the existing operating system and command-line environment's command invocation source differentiation mechanism. During the execution of operation commands, source information is displayed synchronously, allowing the user to know in real time whether the currently executed command originates from their own operation or from the intelligent agent, effectively improving the transparency of the intelligent agent's background behavior and reducing security risks in human-machine collaborative operation scenarios.
[0032] In some embodiments, the method further includes storing operation instructions with attached source information in the storage area corresponding to the target interface layer to form an operation audit record.
[0033] For example, an operation audit log refers to a data set that systematically records operational behaviors occurring in electronic devices. Its purpose is to provide a basis for post-event traceability, security review, and problem investigation. By storing operation instructions and their source information together, users can clearly understand which operation instructions were executed by the user themselves and which operation instructions were executed by the intelligent agent in the background during a certain period of time, thus forming a complete chain of operation behavior traceability.
[0034] Specifically, the storage area corresponding to the target interface layer can be a non-volatile storage medium in an electronic device, such as a hard drive, solid-state drive, embedded flash memory, or a specified directory or file in an external storage card. Audit records in the non-volatile storage medium are retained even after the electronic device is powered off or disconnected from power, allowing users to review and analyze them after the device restarts. Alternatively, the storage area can be in the form of a log file, where audit records are appended to a log file as lines of text, with each line corresponding to an audit record of an operation instruction. The log file can use a common text format (such as TXT or CSV) or a structured data format (such as JSON or XML) to facilitate subsequent parsing and analysis.
[0035] This embodiment persistently stores operation instructions and their source information in a storage area, ensuring that every operation, whether originating from a user or an agent, is fully recorded and saved. Users can review historical operation records at any time to understand which operation instructions the agent executed within a specific time period, the source of each instruction, and the execution result. The resulting operation audit records serve as objective data evidence and can be used for periodic security audits. Users or system administrators can review these audit records to confirm whether the agent performed operations as expected, whether there were any abnormal operations or unauthorized behaviors, thereby promptly identifying potential security risks and taking appropriate measures. The immutability of the audit records (once written, they cannot be tampered with) guarantees the authenticity and credibility of the audit results.
[0036] Figure 2 A flowchart illustrating step S120 of an embodiment of this application is shown schematically.
[0037] like Figure 2 As shown, step S120 may specifically include steps S210 to S220.
[0038] In step S210, an operation event sequence is determined based on the user's operation information; the operation event sequence represents at least one operation event performed by the user within a preset time period.
[0039] For example, to accurately determine the source of operation instructions received by the target interface layer, it is necessary to quantify the user's operation behavior into an analyzable and matchable data structure, namely, an operation event sequence. This operation event sequence is a structured record of the user's operation behavior performed through an input device within a specific time period, representing at least one operation event performed by the user within a preset time period. For instance, when a user operates on an electronic device, each key press, each mouse click, and each touchscreen touch is captured and recorded as an operation event by the electronic device. These operation events are arranged in chronological order of occurrence, thus forming an operation event sequence. This sequence is essentially an "electronic footprint" of the user's operation behavior, which can be used to compare with subsequently received operation instructions to determine whether the instruction was triggered by the user's active operation.
[0040] Specifically, an operation event is a raw data unit that can be quantified and recorded by an electronic device when a user performs a physical operation through an input device connected to the electronic device. Each operation event may contain at least the following information: Event type information indicates the type of operation event, such as keyboard events (key pressed, key released), mouse events (click, double-click, move, scroll wheel), touch screen events (touch start, touch move, touch end), etc.
[0041] Event content information is used to indicate the specific input content carried by the operation event, such as the key value corresponding to the keyboard event (character "a", function key "Enter", etc.), the click position coordinates corresponding to the mouse event, and the touch point coordinates and pressure value corresponding to the touch event.
[0042] The timestamp information indicates the specific time when the operation event occurred. This information is used to subsequently construct the operation event sequence and perform time correlation matching.
[0043] In this embodiment, after the target interface layer receives the operation command, the electronic device triggers the operation source identification process. The external detection module extracts operation events within a preset time period from the buffer area and constructs an operation event sequence. The preset time period can be flexibly set according to the actual application scenario. For example, the preset time period is a time window of N milliseconds backward from the moment the operation command is received from the target interface layer. The value of N can be set according to the response speed of the input device and the input time of the operation command. For example, it can be set to 500 milliseconds or 1000 milliseconds. This method can capture the user operation event that is closest to the current operation command in time. After determining the preset time period, the external detection module extracts all operation events within this time period from the buffer area and arranges them in chronological order of occurrence to form an operation event sequence. This sequence is ordered, that is, the order of operation events in the sequence strictly follows the ascending order of their timestamps.
[0044] In step S220, if there is an event in the operation event sequence that matches the operation instruction, the source information indicates that the operation instruction originated from the user; if there is no event in the operation event sequence that matches the operation instruction, the source information indicates that the operation instruction originated from the agent.
[0045] For example, a user's physical operation via an input device generates a series of operation events, which correspond in content to the input operation command. When an agent automatically submits an operation command through a system call interface, no corresponding user operation event occurs. Therefore, by determining whether an operation event matching the operation command exists in the operation event sequence, it is possible to distinguish whether the operation command originated from the user or the agent. For instance, if a user presses the keys "p", "i", "n", and "g" sequentially on the keyboard, these key events will be recorded in the operation event sequence. When the target interface layer receives a "ping" command, it compares the command content with the key content in the operation event sequence. If they match, it means the command was manually entered by the user; otherwise, if the command is submitted silently by the agent in the background, no corresponding key record will be left in the operation event sequence, and a match will not be possible.
[0046] Specifically, after constructing the operation event sequence, the electronic device matches and compares the operation instructions received by the target interface layer with the operation event sequence. The basic rules for matching are as follows: If an operation event matching the operation instruction exists in the sequence of operation events, the source information indicates that the operation instruction originated from the user. If no operation event matching the operation instruction exists in the sequence of operation events, the source information indicates that the operation instruction originated from the agent.
[0047] It is important to emphasize that the above matching is bidirectional. It requires that the content of the operation event corresponds to the content of the operation instruction at the character level, and that the time of the operation event corresponds to the time when the operation instruction is received. Only when both content and time matching conditions are met is a matching operation event considered to exist. Of these two conditions, content matching establishes the content association between the operation event and the operation instruction, i.e., whether the operation performed by the user on the input device matches the received operation instruction; time matching eliminates mismatches that are not temporally relevant, i.e., whether the user's operation occurred near the time the operation instruction was received by the target interface layer.
[0048] Based on the matching logic described above, the electronic device generates a judgment result indicating the source of the operation command. When an operation event matching the operation command exists in the operation event sequence, the electronic device determines that the operation command originates from the user and outputs this information to the tagging module. When no operation event matching the operation command exists in the operation event sequence, the electronic device determines that the operation command originates from the agent and outputs this information to the tagging module. The source information can be appended to the operation command in the form of an identifier. For example, a source field can be set in the data structure of the operation command, represented by a text label of "user" or "agent," or by a Boolean value of "0" or "1."
[0049] In some embodiments, detecting user operation information includes at least one of the following methods: obtaining the user's input data through the operating system's input event application programming interface; obtaining the user's input data through a human-machine interface device driver; or obtaining the user's input data through data interaction with an external input device.
[0050] For example, user operation information refers to the raw data generated when a user performs a physical operation through an input device connected to an electronic device. This data reflects the user's input behavior and serves as the basis for constructing an operation event sequence. To acquire user operation information, the electronic device needs to collect data from the transmission link of the input signal. From the time the user operates the input device until it is recognized by the operating system, the input signal needs to pass through multiple stages, including the hardware layer (the input device itself), the firmware layer (the embedded microcontroller of the input device), the driver layer (the human-machine interface device driver), and the operating system layer (the operating system's input event management subsystem). The electronic device can collect user input data at any one or more of these stages, thereby enabling the detection of user operation information.
[0051] Specifically, electronic devices obtain user input data through the operating system's input event application programming interface (API). Operating systems typically provide standardized APIs for upper-level applications to access input events. Taking Windows as an example, the operating system provides the Windows message mechanism, allowing applications to listen for keyboard and mouse input events. Furthermore, Windows provides a lower-level Raw Input API, through which applications can directly obtain unprocessed raw input data from input devices, offering higher accuracy and lower latency.
[0052] Human-machine interface (HMI) device drivers are software interfaces between the operating system and input devices, used to convert hardware signals from input devices into a standard format recognizable by the operating system. External detection modules can establish communication with input device drivers to obtain raw input events from the driver level. For example, an external detection module can act as a filter driver or hook program in the operating system kernel layer, attached to the data channel of the input device driver. When a user operates the input device, the input device transmits electrical signals to the driver. Before passing the processed data to the upper-level operating system, the driver first passes the raw data to the external detection module through a registered callback interface. The external detection module obtains this data, parses and processes it, and then continues to pass the data upwards without affecting the normal input processing flow of the operating system.
[0053] External input devices (such as keyboards, mice, touchscreens, microphones, handwriting input devices, gesture recognition sensors, etc.) typically contain embedded microcontrollers. These microcontrollers are responsible for scanning the state changes of the input elements, performing signal processing and analog-to-digital conversion, and interacting with the main processor of the electronic device through a communication interface. An external detection module can directly communicate with the embedded microcontroller of the external input device through the electronic device's communication interface (such as a Universal Serial Bus interface or an Integrated Circuit Bus interface) to acquire the raw signal data generated when the user operates the input device at the hardware level. For example, the external detection module sends a data read request to the embedded microcontroller of the external input device. The microcontroller responds to this request and sends the currently acquired input signal data back to the external detection module through the communication interface. The external detection module then parses the returned data to extract the user's operation information. Taking a keyboard as an example, the embedded microcontroller inside the keyboard continuously scans the on / off state of each key in the keyboard matrix. When a user presses a button, the microcontroller detects that the circuit corresponding to that button is activated, generates a corresponding button scan code, and sends the scan code data to the electronic device through a universal serial bus interface. An external detection module can obtain the scan code data by communicating with the microcontroller, thereby knowing which button the user has pressed.
[0054] This embodiment provides three methods for acquiring user input data: acquisition through the operating system input event application programming interface, acquisition through the human-machine interface device driver, and acquisition through data interaction with external input devices. These three methods cover the complete input signal chain from the upper layer of the operating system to the lower layer of the hardware, enabling electronic devices to flexibly select the most suitable detection method according to different system environments, hardware configurations, and application requirements, significantly improving the adaptability and feasibility of the technical solution.
[0055] In some embodiments, displaying source information includes at least one of the following: displaying source information overlaid on a graphical user interface element via a main display unit, the graphical user interface element including at least one of text labels, graphic identifiers, or color indicators; and indicating the source attribution of an operation command via an auxiliary indicator device independent of the main display unit, using the state of the light emission color or the flashing rhythm.
[0056] For example, after determining the source information of the operation command, the source information is presented in a user-perceptible manner through the output device of the electronic device. The display methods of this source information fall into two main categories: one is display through the main display unit of the electronic device, and the other is indication through an auxiliary indicating device independent of the main display unit. These two methods can be used individually or in combination.
[0057] The main display unit is the primary visual output interface of an electronic device (such as a laptop screen or desktop monitor), typically used to present rich graphical information. Displaying source information through the main display unit allows for the use of graphical user interface elements to convey more detailed and intuitive status information. Auxiliary indicators are additional indicating components independent of the main display unit (such as indicator lights, status light strips, and digital displays), typically used to convey simple status signals. Indicating source information through auxiliary indicators allows for a concise way to convey the origin of an operation command to the user without occupying the main display unit's display resources.
[0058] Specifically, "overlay display" refers to overlaying the source information as a layer on top of the currently displayed user interface of the main display unit, rather than replacing or changing the original display content. This display method allows the source information to be presented simultaneously with the command-line interface or other application interfaces that the user is currently operating. Users can know the source information of the operation command without switching interfaces or leaving the current operation, ensuring the continuity and smoothness of the user experience.
[0059] In this embodiment, the graphical user interface elements are in the form of text labels, which are graphical interface elements that directly present the source information in text form. For example, when the operation command comes from the user, the electronic device displays "User is operating" or "Current command is being executed by the user" overlaid on the title bar, status bar, near the command prompt, or at the edge of the command output area of the command line window. When the operation command comes from the agent, the electronic device displays "Agent is operating" or "Current command is being executed by the agent" overlaid on the above-mentioned locations.
[0060] In this embodiment, the graphical user interface elements adopt the form of graphical identifiers, which are interface elements that present source information in the form of graphic symbols or icons. For example, when the operation command comes from the user, the electronic device displays a human-shaped icon or a graphic symbol representing "user" next to the command line prompt; when the operation command comes from the intelligent agent, the electronic device displays a robot icon, chip icon, or a graphic symbol representing "intelligent agent" in the corresponding position. Graphical identifiers are more concise and intuitive than text labels, enabling users to quickly identify the source of the current operation command without reading text.
[0061] In this embodiment, the graphical user interface elements are presented as color indicators. These color indicators use color changes in specific areas of the display screen to indicate the source of the information. For example, when the operation command originates from a user, the electronic device sets the border, title bar, or command prompt of the command line window to a first color (e.g., blue); when the operation command originates from an agent, the color of the aforementioned areas is set to a second color (e.g., red or orange). The user can determine the source of the current operation command by observing the color changes.
[0062] In this embodiment, the three graphical user interface elements (text labels, graphical identifiers, and color indicators) can be used individually or in combination. For example, the electronic device uses a red border (color indicator) on the edge of the command line window to indicate that the current operation command originates from an intelligent agent, while displaying a robot icon (graphical identifier) in the status bar along with the text "AI in progress" (text label). This multi-dimensional visual cues ensure that the user can obtain the source information in the most efficient way.
[0063] In this embodiment, the electronic device uses an auxiliary indicator device independent of the main display unit to indicate the source of the operation command through the color state or flashing rhythm of the emitted light. The auxiliary indicator device is a visual prompt component independent of the main display unit on the electronic device, located on the surface of the device's casing, such as in the keyboard area, screen bezel, near the touchpad, or on the side of the device—positions easily observed by the user. The auxiliary indicator device typically includes one or more light-emitting elements, such as LEDs or LED strips. Specifically, when the operation command originates from the user, the light-emitting element of the auxiliary indicator device emits a first color, such as green or blue; when the operation command originates from an intelligent agent, the light-emitting element emits a second color, such as red, orange, or yellow; when the operation command originates from the user, the light-emitting element operates with a first flashing rhythm, such as low-frequency slow flashing (e.g., flashing once per second) or remaining constantly lit; when the operation command originates from an intelligent agent, the light-emitting element operates with a second flashing rhythm, such as high-frequency rapid flashing (e.g., flashing five times per second) or using a specific flashing pattern (e.g., double flashing, triple flashing, etc.).
[0064] Based on the method described in the above embodiments, by overlaying source information onto the main display unit in the form of graphical user interface elements (text labels, graphical identifiers, color indicators), users can instantly determine whether the currently executed command originates from themselves or the intelligent agent without switching interfaces or interrupting their current operation while operating the electronic device. Graphical user interface elements are highly intuitive and have a large information capacity, enabling the transmission of source information with minimal user cognitive cost, thus improving the transparency and user experience of human-machine collaborative operation. A scheme using an auxiliary indicator device independent of the main display unit to indicate source attribution is also employed. This auxiliary indicator device transmits source information through the state of emitted light color or flashing rhythm, allowing users to perceive the background operation status of the intelligent agent through peripheral vision or ambient light even when the main display unit is off, the user is not looking at the screen, or the user is engaged in other activities. This effectively solves the limitation of traditional solutions where users must look at the screen to know the operation status, achieving 24 / 7 monitoring of the intelligent agent's background behavior.
[0065] In some embodiments, displaying source information includes at least one of the following display states: displaying the agent in an operation execution state alone; displaying the user in an operation execution state alone; and displaying the agent and user in a parallel operation execution state simultaneously.
[0066] For example, the source information of the operation command can be presented to the user in a visual manner through a display component. For instance, based on the current operating scenario of the electronic device and the user's information needs, the displayed content of the source information may include at least one of three display states: displaying the agent alone in the operation execution state, displaying the user alone in the operation execution state, and displaying the agent and user simultaneously in a parallel operation execution state. These three display states correspond to three different human-machine collaborative operation scenarios, such as only the agent performing the operation, only the user performing the operation, and both the agent and the user performing the operation simultaneously. The electronic device can adaptively select the corresponding display state based on the actual detected operation situation to most accurately reflect the current operating status of the electronic device.
[0067] Specifically, when the electronic device detects that only the agent is executing operation commands in the background, and the user has not executed any operation commands, the display component separately shows that the agent is in operation execution state. For example, when the target interface layer continuously receives operation commands from the agent, and no operation commands from the user are detected within a corresponding preset time period, the electronic device determines that the current state is "agent operating alone". In this state, the main display unit displays graphical user interface elements to indicate that the agent is performing an operation, or the auxiliary indicator device indicates the operation with a light color or flashing rhythm corresponding to the agent. Specifically, on the main display unit, the border of the command line window is displayed in red (color indicator), and a robot icon (graphical identifier) and a text label "Agent is performing an operation" (text label) are displayed in the window status bar. On the auxiliary indicator device, LED indicators are displayed in a solid red or rapidly flashing manner to indicate that the agent is performing an operation.
[0068] When the electronic device detects that only the user is actively executing operation commands, while the intelligent agent is not executing any operation commands, the display component separately indicates that the user is in an operation execution state. For example, when the target interface layer receives an operation command from the user, and no operation command submitted by an intelligent agent is currently being executed, the electronic device determines that the current state is "user-only operation". In this state, the main display unit displays graphical user interface elements to indicate that the user is performing an operation, or auxiliary indication devices indicate the user with a light color or flashing rhythm corresponding to the user. Specifically, on the main display unit, the border of the command line window is displayed in blue (color indicator), and a human-shaped icon (graphical identifier) is displayed next to the command prompt along with a text label stating "user is performing an operation" (text label). On the auxiliary indication device, LED indicators are displayed in a solid blue light or in a low-frequency, slow flashing manner to indicate that the user is performing an operation.
[0069] When an electronic device detects that an agent and a user are simultaneously executing operation commands, the display component simultaneously shows that the agent and the user are in a parallel operation execution state. In real-world human-machine collaborative operation scenarios, the agent's automatic background operation and the user's manual foreground operation may occur simultaneously. For example, while the user manually enters a command in the command-line interface, the agent automatically triggers the execution of another command in the background according to a preset timed task. In this parallel operation scenario, the electronic device's operating system simultaneously contains operation commands from two different entities. In this state, the display component can simultaneously present the status information from both operation sources. For example, the main display unit can display both source information simultaneously in a segmented manner, such as displaying the user's source identifier in the left area of the command-line window and the agent's source identifier in the right area; or, multiple currently executing commands can be distinguished by different colors, with user-executed commands marked in blue and agent-executed commands marked in red.
[0070] In this embodiment, the main display unit can also display two sources of information simultaneously in a dynamic switching manner. For example, the display component can quickly switch between displaying the agent's operating state and the user's operating state, or simultaneously list all currently executed commands and their respective sources in the form of an information list.
[0071] Existing operating systems and command-line environments present the execution process and results in a uniform manner when executing commands, regardless of whether the command originates from the user or the intelligent agent. They do not distinguish or display the source of the command, nor do they possess the ability to display different states based on different operational conditions (individual operation, parallel operation). The above embodiment provides three differentiated display states, enabling electronic devices to present different display content according to different operational conditions. This achieves refined and differentiated visual feedback on the source state of the operation in command-line execution scenarios, significantly improving the transparency and user experience of human-machine collaborative operations.
[0072] Figure 3 A flowchart illustrating another embodiment of the data processing method of this application is shown schematically.
[0073] like Figure 3 As shown, after determining the source information of the operation instruction, the method further includes steps S310 and S320.
[0074] In step S310, permission information is obtained, which records a set of instructions that are prohibited from being executed by the intelligent agent.
[0075] For example, after determining the source information of the operation command, the electronic device can further manage the permissions of the operation command originating from the intelligent agent. For instance, a user can pre-configure a list of commands that the intelligent agent is not authorized to execute, based on their own security needs. When the intelligent agent attempts to execute a command from this list in the background, the electronic device will prevent the actual execution of the command, thereby effectively preventing the intelligent agent from performing sensitive operations without the user's knowledge. In this embodiment, the permission information can be presented in the form of a blacklist, i.e., a list of commands that are prohibited from execution.
[0076] Specifically, permission information is pre-configured by the user and stored in the electronic device. This permission information can be configured as a set of instructions, which records the identifiers of instructions that are prohibited from being executed by the intelligent agent. Users can customize the set of instructions that the intelligent agent is prohibited from executing based on their own security needs and operating habits. For example, users can configure the intelligent agent to be prohibited from executing commands involving modifications to critical system configurations (such as modifying the registry, modifying system file protection, changing system security policies, etc.), commands involving data deletion (such as deleting user files, formatting disks, etc.), commands involving network-sensitive operations (such as opening firewall ports, modifying network proxy settings, etc.), and commands involving privacy data (such as accessing files or directories containing sensitive personal information, etc.).
[0077] In this embodiment, permission information can be stored in a non-volatile storage medium of the electronic device, such as a hard disk, solid-state drive, or embedded storage chip. The storage format of the permission information can be various, including configuration files, database tables, XML files, or JSON files. When permission verification is required, the electronic device reads the permission information from the storage medium. The electronic device can also provide a user interface for users to view and modify the permission information. Users can add new prohibition commands, delete existing prohibition commands, or modify the configuration parameters of commands through this user interface. Modifications to the permission information take effect immediately without requiring a restart of the electronic device or a reload of the configuration.
[0078] In step S310, when the matching degree indicates that the operation instruction originates from the agent and the operation instruction belongs to the permission information, the execution of the operation instruction is intercepted.
[0079] For example, after determining the source of the operation command and acquiring and matching permission information, the electronic device executes corresponding control actions based on the determination and matching results. For instance, when the matching degree indicates that the operation command originates from an agent and the operation command belongs to the prohibited command set recorded in the permission information, the electronic device intercepts the execution of the operation command. In this embodiment, the two conditions of "source determination" and "permission matching" are logically ANDed, meaning that the interception action is triggered only when both conditions are met simultaneously (the command originates from an agent and the command is in the prohibited list). If the command originates from the user, no interception is triggered regardless of whether the command is in the permission information; if the command originates from an agent but is not in the prohibited list of the permission information, no interception is triggered either, and the command is executed normally. Through the above logic, the normal operation of the agent is not affected, and the agent is effectively prevented from executing sensitive commands that are explicitly prohibited by the user.
[0080] Specifically, if the operation instruction originates from the user, the electronic device will not intercept it, regardless of whether the instruction belongs to the prohibited instruction set recorded in the permission information. Instead, it will allow the instruction to execute normally because the user has full operational permissions, and the command they actively input should be executed. If the operation instruction originates from the agent, but does not belong to the prohibited instruction set recorded in the permission information, the electronic device will not intercept it and will allow the agent to execute it normally. This is because the instruction is not on the user's prohibited list and falls within the scope of operations that the agent can perform. If the operation instruction originates from the agent, and the instruction belongs to the prohibited instruction set recorded in the permission information, the electronic device will intercept the execution of the operation instruction, preventing it from being sent to the operating system's command execution engine.
[0081] It should be noted that in some other embodiments, different operation permissions can be assigned to different users. For example, in an enterprise environment or public equipment scenario where multiple users share an electronic device, different users may have different levels of operation permissions. Ordinary users may only be allowed to perform basic operations, while administrator users may have full system operation permissions. Therefore, in other embodiments of this application, for operation instructions originating from users, the electronic device can also control the execution of the operation instruction based on user permissions to determine whether to allow the execution of the operation instruction.
[0082] Specifically, electronic devices can verify user identity through password authentication. For example, when a user logs into an electronic device, the device prompts the user to enter a password. The entered password is compared with the password stored in the system. If they match, the user's identity is confirmed as a pre-defined legitimate user. In this embodiment, the electronic device can also verify user identity through biometric technologies (such as facial recognition, fingerprint recognition, iris recognition, etc.).
[0083] In this embodiment, the electronic device assigns different operation permission levels to different users. These operation permission levels limit the types and scope of operation commands that a user can execute within the operating system. For example, users can be divided into administrator and regular user levels. Administrator-level users have full operation permissions and can execute all operation commands, including modifying system configurations, installing and uninstalling software, accessing sensitive files, and managing system services. Regular user-level users only have basic operation permissions and are only allowed to execute operation commands necessary for daily office work and application use, such as opening, editing, and saving files, and running regular applications. They cannot execute operation commands involving core system configuration or security-sensitive operations.
[0084] Based on the above embodiments, after obtaining the user's identity and corresponding permission level, the electronic device compares the operation command received by the target interface layer with the set of allowed or prohibited execution commands corresponding to that permission level to determine whether the user is allowed to execute the operation command. In this embodiment, the electronic device stores a set of command permissions corresponding to each permission level. The set of command permissions may include a set of allowed execution commands (whitelist), i.e., a list of operation commands that a user of that permission level can execute; or it may include a set of prohibited execution commands (blacklist), i.e., a list of operation commands that a user of that permission level cannot execute. When the target interface layer receives an operation command from a user, the electronic device first determines the user's identity and permission level, and then matches and compares the operation command with the set of command permissions corresponding to that permission level: if a whitelist is used, if the operation command belongs to the set of allowed execution commands, it is determined that execution is allowed; if the operation command does not belong to the set of allowed execution commands, it is determined that execution is blocked. If a blacklist is used, if the operation command belongs to the set of prohibited execution commands, it is determined that execution is blocked; if the operation command does not belong to the set of prohibited execution commands, it is determined that execution is allowed.
[0085] This embodiment assigns different operation permission levels to different users, ensuring that different users have different scopes of operation permissions on the same electronic device. Administrator users have full operation permissions, allowing them to execute high-privilege commands such as modifying system configurations and accessing sensitive files; ordinary users only have basic operation permissions, enabling them to execute only basic commands required for daily operations. This achieves fine-grained permission control over user behavior, ensuring that users can only use the electronic device within their authorized scope. In scenarios where multiple users share an electronic device, user identity is confirmed through authentication methods such as password verification, facial recognition, fingerprint recognition, iris recognition, or voiceprint recognition. Based on the permission level corresponding to that identity, the system determines whether to allow the execution of operation commands. This effectively prevents unauthorized users or users with low privileges from exceeding their authority to execute high-privilege commands, improving the security and controllability of electronic devices in multi-user scenarios.
[0086] In this embodiment, the electronic device performs an interception operation to prevent the operation instruction from actually being executed in the operating system. For example, after the target interface layer completes permission matching and determines that interception is necessary, it no longer forwards the operation instruction to the operating system's command execution engine. Specifically, the target interface layer has an instruction forwarding switch internally. When the interception condition is triggered, this switch cuts off the forwarding path of the current operation instruction, causing the operation instruction to be discarded and unable to reach the system kernel's execution module. By using the above method, the execution of the instruction in the operating system is prevented at the physical level, ensuring security.
[0087] This application also provides a data processing apparatus, comprising: a detection module, which detects user operation information if an operation instruction is received through a target interface layer; the target interface layer is used to intercept operation instructions sent to the operating system; a determination module, which determines the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; and a display module, which displays the source information during the execution of the operation instruction.
[0088] Figure 4 This diagram schematically illustrates an application architecture of a data processing device according to an embodiment of this application. The diagram shows, at the system level, the interaction relationships between various functional modules and the data flow when the data processing device operates in an electronic device. The following is in conjunction with… Figure 4 The data processing apparatus of this application is described in detail.
[0089] like Figure 4 As shown, from the perspective of the flow of operation commands, the system has two parallel command input paths: one path comes from the user's manual operation (User Action), that is, the user manually inputs operation commands in the command-line interface using input devices such as keyboard, mouse, and touch screen; the other path comes from intelligent agents (AI Agents), that is, intelligent agents automatically submit operation commands in the background through system call interfaces. Operation commands from both paths are uniformly received by the target interface layer ("Command Receiving" module), and after subsequent source determination, marking, and display processing, are finally executed by the command execution module. Throughout the entire processing flow, the user action detection module continuously listens for the user's operation information, and the status display module presents the source of the operation command to the user in real time.
[0090] Specifically, such as Figure 4As shown, the "Command Reception" module is positioned between the operating system and the command-line tool, connecting to both the user's operation path and the agent's operation path. It intercepts all operation commands sent to the operating system and serves as a unified command reception entry point. When a user enters an operation command through an input device in the command-line interface, the command is submitted to the operating system via the command-line interpreter, and is first intercepted and received by the "Command Reception" module before reaching the operating system. Similarly, when the agent automatically submits operation commands in the background through a system call interface, these commands are also intercepted and received by the "Command Reception" module.
[0091] There is a two-way interaction between the user action detection module and the "command receiving" module (represented in the diagram as "triggering action confirmation" and "returning confirmation result" (AI or human)). Specifically, when the "command receiving" module receives an operation instruction, it triggers the action confirmation process and sends an authentication request to the user action detection module. In response to this request, the user action detection module obtains the current user's operation information by listening to the operation events generated by the input device, matches and compares the operation instruction with the user's operation information, generates a judgment result indicating whether the operation instruction comes from an intelligent agent or from the user, and returns the result to the "command receiving" module.
[0092] The user action detection module can acquire user operation information in various ways. In this embodiment, the user action detection module acquires user input data through the input event application programming interface provided by the operating system; the user action detection module acquires user input data through the human-machine interface device driver; the user action detection module acquires user input data by directly interacting with the embedded microcontroller of external input devices (such as keyboard, mouse, touch screen, microphone, etc.).
[0093] The "Command Marking / Display" module is connected to both the "Command Receiving" and "Command Execution" modules. Based on the judgment result returned by the user action detection module, this module adds source identification information to the operation command (the "AI Command Filing / Storage" in the diagram indicates filing and marking the source of operation commands originating from the intelligent agent), and then sends the marked operation command to the "Command Execution" module. For example, when the judgment result returned by the user action detection module indicates that the operation command originates from the user, the "Command Marking / Display" module adds a source identifier indicating "originating from the user" to the operation command; when the judgment result indicates that the operation command originates from the intelligent agent, the "Command Marking / Display" module adds a source identifier indicating "originating from the intelligent agent" to the operation command. After adding the source identifier, the "Command Marking / Display" module transmits the marked operation command and its source information to the "Command Execution" module, and simultaneously sends a command to the status display module (as shown in the diagram, "Send command to display module, display status to user") to trigger the status display module to visualize the source information of the current operation command.
[0094] The status display module is connected to both the "command label / display" module and the user (shown as "User" in the diagram). This module is used to display the source information of the operation command to the user in a perceptible manner during the execution of the command. When the "command label / display" module sends the source information to the status display module, the status display module controls the display components to present the corresponding display status based on the received information. This display status can be overlaid on the main display unit as graphical user interface elements (text labels, graphic identifiers, or color indicators), or it can be indicated by an auxiliary indicator device independent of the main display unit, using luminous color status or flashing rhythm.
[0095] The "Command Execution" module is located at the end of the processing flow and is connected to the "Command Marking / Display" module. It is used to execute operation instructions that have been marked with a source. During the execution of operation instructions by the "Command Execution" module, the status display module synchronously displays the source information of the instruction, ensuring that the presentation of the source information and the execution of the instruction are consistent in time.
[0096] based on Figure 4The application architecture of the data processing device shown forms a complete closed-loop processing link from instruction reception to source presentation through the rational division and collaborative interaction of five functional modules (command receiving module, user action detection module, command marking / display module, status display module, and command execution module). For example, the command receiving module uniformly intercepts and receives operation commands from users and intelligent agents; the user action detection module obtains user operation information in real time through a triggering mechanism and returns the source determination result; the command marking / display module attaches a source identifier to the operation command and sends the source information to the status display module; and the status display module synchronously presents the source information during the execution of the operation command by the command execution module, forming a complete closed-loop processing link of instruction interception → source determination → marking display → synchronous execution. This architecture, through the loose coupling design between modules and the triggering collaborative working mechanism, achieves real-time identification and transparent presentation of the source of all operation commands, effectively improving the transparency of human-machine collaborative operation and the security of electronic devices. It can also flexibly adapt to different types of input devices and display methods, filling the architectural gap in existing operating systems in terms of distinguishing and prompting the source of command calls.
[0097] Figure 5 A schematic block diagram of an electronic device according to an embodiment of this application is shown.
[0098] like Figure 5 As shown, the electronic device 5 in this embodiment includes: a screen, a processor 501, a memory 502, and a computer program 503 stored in the memory 502 and executable on the processor 501. When the processor 501 executes the computer program 503, it implements the steps in the various method embodiments described above. Alternatively, when the processor 501 executes the computer program 503, it implements the functions of each module in the various device embodiments described above. In this embodiment, the electronic device 5 may further include an input component for receiving user input operations; the screen of the electronic device 5 can serve as a display component for displaying information, such as source information. Specifically, the processor 501 of the electronic device 5 is used to detect user operation information if an operation instruction is received through a target interface layer; the target interface layer is used to intercept operation instructions sent to the operating system; based on the matching degree between the user's operation information and the operation instruction, it determines the source information of the operation instruction; and during the execution of the operation instruction, it displays the source information.
[0099] Electronic device 5 can be a desktop computer, laptop, handheld computer, cloud server, or other electronic device with a screen. Electronic device 5 may include, but is not limited to, processor 501 and memory 502. Those skilled in the art will understand that... Figure 5 This is merely an example of electronic device 5 and does not constitute a limitation on electronic device 5. It may include more or fewer components than shown, or different components.
[0100] The processor 501 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0101] The memory 502 can be an internal storage unit of the electronic device 5, such as a hard disk or RAM of the electronic device 5. The memory 502 can also be an external storage device of the electronic device 5, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc., equipped on the electronic device 5. The memory 502 can also include both internal and external storage units of the electronic device 5. The memory 502 is used to store computer programs and other programs and data required by the electronic device.
[0102] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0103] refer to Figure 6The processor 601 described above operates a target interface layer 601, a source determination layer 602, a tagging layer 603, a display control layer 604, and an instruction execution layer 605. Specifically, the target interface layer 601 intercepts and receives operation instructions sent to the operating system; the source determination layer 602, after receiving the operation instruction at the target interface layer, detects the user's operation information through an input component and determines the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; the tagging layer 603 adds a source identifier to the operation instruction based on the source information determined by the source determination layer; the display control layer 604 controls the display component to display the source information during the execution of the operation instruction; and the instruction execution layer 605 executes the operation instruction. The specific implementation logic of the target interface layer 601, source determination layer 602, tagging layer 603, display control layer 604, and instruction execution layer 605 in this embodiment can be found in the relevant description of the data processing method described above, and will not be repeated here.
[0104] This application provides a computer program product that stores a computer program, which, when executed by a processor, implements the steps in the above method embodiments.
[0105] If the integrated module is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.
[0106] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0107] The units or modules described in the embodiments of this disclosure can be implemented in software or programmable hardware. The described units or modules can also be located in a processor, and the names of these units or modules do not necessarily constitute a limitation on the unit or module itself.
[0108] In another aspect, this disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or computer system described above; or it may be a standalone computer-readable storage medium not assembled into a device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to execute the methods of the embodiments of this disclosure.
[0109] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.
Claims
1. A data processing method, comprising: If an operation command is received through the target interface layer, detect the user's operation information; The target interface layer is used to intercept the operation instructions sent to the operating system; Based on the matching degree between the user's operation information and the operation command, the source information of the operation command is determined; During the execution of the operation instructions, the source information is displayed.
2. The data processing method according to claim 1, wherein determining the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction includes: Based on the user's operation information, determine the sequence of operation events; The sequence of operation events represents at least one operation event performed by the user within a preset time period; If there is an event in the sequence of operation events that matches the operation instruction, the source information indicates that the operation instruction originated from the user; If the operation event sequence does not match the operation instruction, the source information indicates that the operation instruction originated from the agent.
3. The data processing method according to claim 1, wherein detecting the user's operation information includes at least one of the following methods: The user's input data is obtained through the operating system's input event application programming interface; The user's input data is obtained through the human-machine interface device driver. The user's input data is obtained by interacting with external input devices.
4. The data processing method according to claim 1, wherein displaying the source information includes at least one of the following: The source information is displayed overlaid in the form of graphical user interface elements through the main display unit, and the graphical user interface elements include at least one of text labels, graphic identifiers, or color indicators. The source of the operation command is indicated by the color state of the light emitted or the flashing rhythm through an auxiliary indicator device independent of the main display unit.
5. The data processing method according to claim 1, further comprising, after determining the source information of the operation instruction: Obtain permission information, which contains a set of instructions that are prohibited from being executed by the intelligent agent; When the matching degree indicates that the operation instruction originates from an agent and the operation instruction belongs to the permission information, the execution of the operation instruction is intercepted.
6. The data processing method according to claim 1 further includes: The operation instructions with the source information attached are stored in the storage area corresponding to the target interface layer to form an operation audit record.
7. The data processing method according to claim 1, wherein displaying the source information includes at least one of the following display states: Display the agent in the operation execution state separately; The user is displayed separately as being in an operation execution state; Simultaneously, it is displayed that the intelligent agent and the user are in a state of parallel operation execution.
8. A data processing apparatus, comprising: The detection module detects the user's operation information if it receives an operation command through the target interface layer. The target interface layer is used to intercept the operation instructions sent to the operating system; The determination module determines the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; The display module displays the source information during the execution of the operation instructions.
9. An electronic device, comprising Input component, used to receive user input; Display components are used to display information; The processor is used to detect user operation information if an operation instruction is received through the target interface layer. The target interface layer is used to intercept the operation instructions sent to the operating system; Based on the matching degree between the user's operation information and the operation command, the source information of the operation command is determined; During the execution of the operation instructions, the source information is displayed.
10. The electronic device according to claim 9, wherein the processor comprises a target interface layer, a source determination layer, a tagging layer, a display control layer, and an instruction execution layer; The target interface layer is used to intercept operation commands sent to the operating system and to receive the operation commands; The source determination layer is used to detect the user's operation information through the input component after the target interface layer receives the operation instruction, and determine the source information of the operation instruction based on the matching degree between the user's operation information and the operation instruction; The tagging layer is used to attach a source identifier to the operation instruction based on the source information determined by the source determination layer; The display control layer is used to control the display component to display the source information during the execution of the operation instruction; The instruction execution layer is used to execute the operation instructions.
