Method and apparatus for deploying an agent, and pluggable device

Abstract

The application discloses an agent deployment method and device and a pluggable device. The method comprises the following steps: a memory is used for storing an environment deployment file corresponding to an agent; a controller is used for providing a display interface to an electronic device in response to the pluggable device being connected to the electronic device; at least a deployment control corresponding to a first agent is displayed in the display interface; in response to the electronic device receiving a triggering operation on the deployment control corresponding to the first agent, the environment deployment file corresponding to the first agent is provided to the electronic device; the environment deployment file comprises a file generated by executing an installation package corresponding to the first agent, so that a running environment of the first agent is deployed in the electronic device.

Description

Technical Field

[0001] This application relates to the field of artificial intelligence technology, and in particular to a method, apparatus and pluggable device for deploying intelligent agents. Background Technology

[0002] Currently, the deployment of the intelligent agent operating environment for artificial intelligence (AI) requires manual online downloading and installation of the package, execution of the package, and configuration of the operating environment. This process is cumbersome and time-consuming, and ordinary users cannot build it independently. Summary of the Invention

[0003] In view of this, this application provides a method, apparatus, and pluggable device for deploying intelligent agents, as follows:

[0004] A pluggable device, comprising:

[0005] The storage device is used to store at least the environment deployment files corresponding to the intelligent agent.

[0006] A controller is configured to provide a display interface to an electronic device in response to the pluggable device being connected to the electronic device; the display interface at least displays a deployment control corresponding to a first intelligent agent; and to provide an environment deployment file corresponding to the first intelligent agent to the electronic device in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent.

[0007] The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

[0008] Optionally, in the aforementioned pluggable device, the memory is an independently allocated encrypted partition within the pluggable device;

[0009] The encrypted partition is used to store the environment deployment file; the environment deployment file includes at least one of the following: the runtime framework file corresponding to the agent, the dependent component file, the configuration file, the underlying driver file, and the startup execution program.

[0010] Optionally, in the aforementioned pluggable device, a running program is stored in the memory; the controller initiates the running program in response to the pluggable device being connected to the electronic device.

[0011] The running program is used to provide a display interface to the electronic device and to provide the electronic device with an environment deployment file corresponding to the first intelligent agent.

[0012] Optionally, the pluggable device may determine the first intelligent agent based on the stored environment deployment file and the device data detected by the electronic device.

[0013] The first intelligent agent is an intelligent agent that is adapted to the electronic device but is not deployed in the electronic device.

[0014] Optionally, in the aforementioned pluggable device, the controller provides the electronic device with an environment deployment file corresponding to the first intelligent agent, including:

[0015] Read the environment deployment file of the first intelligent agent stored in the memory;

[0016] Write the environment deployment file of the first intelligent agent into the corresponding directory in the electronic device;

[0017] Configure the first intelligent agent into the system configuration items of the electronic device.

[0018] Optionally, in the aforementioned pluggable device, after the controller provides the electronic device with the environment deployment file corresponding to the first agent, it provides the first agent with a lexical authorization key, enabling the electronic device to use the corresponding target lexical through the lexical authorization key.

[0019] Optionally, in the aforementioned pluggable device, the controller outputs a first prompt message on the display interface when it detects that the lexical authorization key has expired; the first prompt message is at least used to indicate that the lexical authorization key has expired.

[0020] When the controller detects an error in the lexical authorization key, it outputs a second prompt message on the display interface and responds to the erroneous operation confirmation operation for the second prompt message by re-providing the lexical authorization key to the first agent, or re-providing the electronic device with the environment deployment file corresponding to the first agent.

[0021] When the controller detects an abnormality in the operating environment of the first agent, it re-provides the electronic device with the environment deployment file corresponding to the first agent.

[0022] Optionally, in the aforementioned pluggable device, the controller, in response to the electronic device receiving a trigger operation on the delete control corresponding to the first intelligent agent, reclaims the environment deployment file corresponding to the first intelligent agent in the electronic device.

[0023] A method for deploying intelligent agents, applied to a pluggable device, the method comprising:

[0024] In response to the pluggable device being connected to the electronic device, a display interface is provided to the electronic device; the display interface displays at least the deployment controls corresponding to the first intelligent agent.

[0025] In response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent, the electronic device is provided with an environment deployment file corresponding to the first intelligent agent;

[0026] The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

[0027] Optionally, before providing a display interface to the electronic device, the above method further includes:

[0028] The device data of the electronic device is detected; the device data represents the software and hardware information deployed in the electronic device and the operating information of the electronic device.

[0029] Based on the device data and the deployment environment file stored in the pluggable device, intelligent agent detection information is obtained; the intelligent agent detection information at least characterizes a first intelligent agent that is adapted to the electronic device but is not deployed in the electronic device.

[0030] Optionally, the above method obtains agent detection information based on the device data and the deployment environment file stored in the pluggable device, including at least one of the following:

[0031] Determine whether the operating environment of any intelligent agent in the pluggable device has been deployed in the electronic device;

[0032] Determine whether the version information of the operating environment of the intelligent agent already deployed in the electronic device matches the corresponding intelligent agent in the pluggable device;

[0033] Determine whether the hardware and software information of the electronic device matches the operational requirements of any intelligent agent in the pluggable device.

[0034] Optionally, the above method includes providing the electronic device with an environment deployment file corresponding to the first intelligent agent, including:

[0035] Read the environment deployment file corresponding to the first intelligent agent from the pluggable device;

[0036] Write the environment deployment file into the corresponding directory in the electronic device;

[0037] Configure the first intelligent agent into the system configuration items of the electronic device.

[0038] Optionally, after providing the electronic device with the environment deployment file corresponding to the first intelligent agent, the method further includes:

[0039] Read the token authorization key stored in the pluggable device;

[0040] The lexical authorization key is written into the directory corresponding to the first intelligent agent, so that the electronic device can use the corresponding target lexical through the lexical authorization key.

[0041] Optionally, the above method may further include:

[0042] If the token authorization key is detected to have expired, a first prompt message is output; the first prompt message is used at least to indicate that the token authorization key has expired.

[0043] If the token authorization key is detected to be incorrect, a second prompt message is output; the second prompt message is at least used to confirm the erroneous operation.

[0044] In response to the erroneous operation confirmation operation for the second prompt information, return to the step of: providing the first agent with a lexical authorization key, or return to the step of: providing the electronic device with the environment deployment file corresponding to the first agent;

[0045] If an abnormality is detected in the operating environment of the first intelligent agent, the process returns to the step of providing the electronic device with the environment deployment file corresponding to the first intelligent agent.

[0046] Optionally, the above method may further include a delete control corresponding to the second intelligent agent displayed on the display interface; the second intelligent agent is an intelligent agent already deployed in the electronic device.

[0047] The method further includes:

[0048] In response to a trigger operation on the delete control corresponding to the second agent, the environment deployment file corresponding to the second agent in the electronic device is reclaimed.

[0049] Optionally, in the above method, the environment deployment file corresponding to the first intelligent agent is stored in an encrypted partition defined in the pluggable device.

[0050] The environment deployment file corresponding to the first intelligent agent includes at least one of the following: the runtime framework file, dependent component file, configuration file, underlying driver file, and startup execution program corresponding to the first intelligent agent.

[0051] A deployment device for an intelligent agent, disposed in a pluggable device, the device comprising:

[0052] An interface providing unit is configured to provide a display interface to the electronic device in response to the pluggable device being connected to the electronic device; the display interface displays at least a deployment control corresponding to the first intelligent agent.

[0053] The file providing unit is configured to provide the electronic device with an environment deployment file corresponding to the first intelligent agent in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent;

[0054] The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

[0055] As can be seen from the above technical solutions, in the intelligent agent deployment method, apparatus, and pluggable device disclosed in this application, when the pluggable device is connected to an electronic device, the pluggable device can provide a display interface to the electronic device, allowing the user to perform corresponding trigger operations on the intelligent agent to be deployed. Based on this, the pluggable device can provide its stored environment deployment files to the electronic device. The environment deployment files provided by the pluggable device include files generated by executing the installation package corresponding to the intelligent agent, thereby enabling the deployment of the corresponding intelligent agent's operating environment on the electronic device. It is evident that this application can achieve offline one-click deployment of the intelligent agent's operating environment. Relying on the environment deployment files corresponding to the intelligent agent stored in the pluggable device, a display interface automatically pops up when the pluggable device is connected to the electronic device. The user only needs to trigger the corresponding deployment controls, without manually downloading the installation package online, manually performing installation, or configuring the operating environment item by item. Therefore, this application can significantly simplify the operation process, reduce manual intervention, and allow ordinary users to independently complete the construction of the intelligent agent's operating environment. Moreover, this application can overcome the limitations of online deployment, quickly completing the deployment of the operating environment even offline, significantly shortening the deployment time and thus significantly improving the deployment efficiency of the intelligent agent's operating environment. Attached Figure Description

[0056] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the 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.

[0057] Figure 1 This is a schematic diagram of the structure of a pluggable device provided in an embodiment of this application;

[0058] Figure 2 This is an example diagram illustrating the connection of a pluggable device to an electronic device in an embodiment of this application;

[0059] Figure 3 This is an example diagram of the display interface provided by the pluggable device to the electronic device in the embodiments of this application;

[0060] Figure 4 This is a flowchart illustrating the implementation of a pluggable device providing an environment deployment file to an electronic device in an embodiment of this application.

[0061] Figure 5 This is an example diagram showing the output of a delete control in the display interface in an embodiment of this application;

[0062] Figure 6 A flowchart illustrating a method for deploying an intelligent agent, as provided in an embodiment of this application;

[0063] Figure 7 This is a schematic diagram of the structure of a deployment device for an intelligent agent provided in an embodiment of this application. Detailed Implementation

[0064] 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 skilled in the art without creative effort are within the scope of protection of this application.

[0065] refer to Figure 1 The diagram shown is a structural schematic of a pluggable device provided in an embodiment of this application. This pluggable device can be a portable terminal capable of connecting to an electronic device via a specific interface, such as a USB flash drive with a Universal Serial Bus (USB) interface or a USB Type-C (Type-C) interface. Figure 2 As shown in the figure. The pluggable device in this embodiment relies on hardware-integrated storage and control capabilities to achieve offline one-click deployment of the intelligent agent's operating environment, which helps to reduce manual complexity and improve the deployment efficiency of the intelligent agent's operating environment.

[0066] Specifically, the pluggable device in this embodiment may include the following structure:

[0067] The memory 101 is used to store at least the environment deployment files corresponding to the intelligent agent.

[0068] Among them, the memory 101 is a hardware storage unit integrated inside the pluggable device, which has data read and write and persistent storage capabilities, and is used to store at least the environment deployment files corresponding to the intelligent agent.

[0069] It should be noted that the environment deployment files stored in the memory 101 include, but are not limited to, the environment deployment files corresponding to large model intelligent agents, task automation intelligent agents, and industry-specific business intelligent agents. These environment deployment files do not require electronic devices to connect to the network to obtain them.

[0070] In one implementation, the memory 101 can be a flash memory chip;

[0071] In another implementation, memory 101 can be an embedded multi-media card (eMMC).

[0072] In another implementation, memory 101 can be a solid-state drive micro storage chip;

[0073] In other implementations, the memory 101 can also be implemented using a hardware encrypted storage chip, a USB flash drive controller integrated storage unit, or other similar methods.

[0074] The controller 102 is configured to provide a display interface to the electronic device in response to a pluggable device being connected to the electronic device; the display interface displays at least a deployment control corresponding to the first intelligent agent; and in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent, provide the electronic device with an environment deployment file corresponding to the first intelligent agent.

[0075] The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, which enables the deployment of the operating environment of the first intelligent agent in the electronic device.

[0076] It should be noted that the controller 102, as the main control processing chip built into the pluggable device, is used to realize the logic control, peripheral interaction, interface push and file distribution of the pluggable device.

[0077] In one implementation, the controller 102 can be a micro controller unit (MCU).

[0078] In another implementation, the controller 102 can be a system on chip (SoC).

[0079] In another implementation, controller 102 can integrate a host chip for a universal serial bus (USB).

[0080] Electronic devices are terminal devices with data interaction and program execution capabilities, such as laptops and servers. The display interface provided by pluggable devices can be output to the corresponding display of the electronic device. Specifically, it can be a pop-up graphical interactive interface used to carry functional controls (such as deployment controls, deletion controls, configuration controls, etc.) and operation entry points.

[0081] Specifically, there are several ways to connect pluggable devices to electronic devices, as follows:

[0082] In one implementation, the pluggable device can connect to an electronic device via a USB interface or a USB Type-C interface;

[0083] In another implementation, pluggable devices can be connected to electronic devices via Thunderbolt interfaces or general peripheral interfaces.

[0084] For example, a pluggable device can be a USB Type-C flash drive. When the flash drive is plugged into electronic devices such as desktop computers, laptops, industrial control computers, and edge computing terminals, the controller in the flash drive automatically recognizes the connection event to the electronic device and provides a display interface to the electronic device, thereby popping up a graphical display interface in the display screen of the electronic device.

[0085] Specifically, the first intelligent agent to which the deployment control displayed in the display interface belongs refers to the intelligent agent that needs to be deployed in the electronic device's operating environment, while the deployment control refers to the interactive components such as graphic buttons, text options, and pop-up menus that can be clicked and triggered by the user in the display interface.

[0086] In one implementation, the deployment control can be a visual button, drop-down menu option, or checkbox in the display interface.

[0087] For example, such as Figure 3 As shown in the image, the display interface shows dedicated deployment controls for first-level intelligent agents such as "Agent A" and "Agent B," allowing users to make intuitive selections.

[0088] Based on this, when the pluggable device recognizes that the electronic device has received a user's trigger operation on the deployment control corresponding to the first intelligent agent on the display interface, it can provide the electronic device with the environment deployment file corresponding to the first intelligent agent.

[0089] It should be noted that user actions triggering the deployment control can include manual interactions such as mouse clicks, touch clicks, and keyboard shortcut selection. Based on this, when a pluggable device detects that such a triggering action has been received on an electronic device, it can transmit and write the corresponding environment deployment file to a specified path within the electronic device. The pluggable device can provide the environment deployment file to the electronic device in at least one of the following ways:

[0090] In one implementation, the controller 102 can silently transmit environment deployment files through a data transmission channel implemented via a USB interface, without popping up a visual transmission window or progress interface, and complete the file writing in a seamless manner.

[0091] In another implementation, the controller 102 can grant access permissions to the environment deployment file to the electronic device through virtual drive letter mapping, so that the electronic device can read the environment deployment file corresponding to the first intelligent agent from the memory 101;

[0092] In another implementation, the controller 102 can proactively push environment deployment files to the electronic device in the background and write them to the system-specified directory of the electronic device, without the need for manual file selection and copying operations, thus achieving proactive delivery of environment deployment files.

[0093] For example, after the user clicks the deployment control for "Agent A" in the display interface, the pluggable device (such as a USB flash drive) automatically reads the environment deployment file corresponding to Agent A from the storage device. Without manual copying, it automatically transfers the environment deployment file corresponding to Agent A to the laptop connected to the USB flash drive, so that the running environment corresponding to Agent A can be deployed on the laptop.

[0094] It should be noted that the environment deployment file is a complete set of files generated after the installation package of the intelligent agent has been decompressed, installed, and configured. After the controller 102 provides the environment deployment file to the electronic device, the electronic device can deploy the operating environment of the first intelligent agent based on these environment deployment files without having to run the installation package again, and can directly run the first intelligent agent.

[0095] In one implementation, the environment deployment file may include at least one of the following: the runtime framework file corresponding to the agent, dependent component files (also known as dependent library files), configuration files (also known as configuration parameter files), underlying driver files, startup execution programs (also known as startup execution scripts), and environment variable configuration files. Based on this, the environment deployment file allows electronic devices to directly rely on these files to complete the setup of the first agent's runtime environment, eliminating the need for manual operations such as online downloads, manual installation, and item-by-item configuration.

[0096] For example, in this embodiment, the installation package of a certain business intelligence agent is pre-compressed, installed, and configured during the production stage. The generated runtime framework file, dependent component file, configuration file, underlying driver file, startup execution program, and other files are combined into an environment deployment file and stored in the storage of the USB flash drive. After the laptop connected to the USB flash drive obtains the environment deployment file, it can directly complete the construction of the intelligence agent's runtime environment.

[0097] In another implementation, this embodiment can pre-configure the cloud access path for the environment deployment file in the memory 101 of the pluggable device. Based on this, when the pluggable device is connected to the network, the controller 102, in response to the electronic device receiving a trigger operation for the deployment control corresponding to the first intelligent agent, obtains the environment deployment file corresponding to the first intelligent agent according to the pre-configured cloud access path, and provides the environment deployment file corresponding to the first intelligent agent to the electronic device, thereby realizing one-click deployment of the first intelligent agent.

[0098] In another implementation, this embodiment can pre-configure a cloud access path for the environment deployment file in the memory 101 of the pluggable device. Based on this, the controller 102 can respond to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent by providing the pre-configured cloud access path to the electronic device. The electronic device can then obtain the environment deployment file corresponding to the first intelligent agent from the cloud according to the cloud access path, thereby realizing one-click deployment of the first intelligent agent.

[0099] As can be seen from the above solution, in the pluggable device provided in this application embodiment, the pluggable device integrates a memory and a controller, and the environment deployment file corresponding to the intelligent agent is pre-stored on the hardware carrier. When the pluggable device is connected to an electronic device, the display interface automatically pops up. The user only needs to trigger the corresponding deployment control, without having to manually download the installation package online, manually perform the installation, and configure the running environment item by item. Thus, this application can realize one-click deployment of the intelligent agent, which can greatly simplify the operation process, reduce manual intervention, and allow ordinary users to independently complete the construction of the intelligent agent's running environment. Moreover, this application can get rid of the limitation of online deployment and can quickly complete the deployment of the running environment even without a network, which can greatly shorten the deployment time and thus significantly improve the deployment efficiency of the intelligent agent's running environment.

[0100] In one implementation, memory 101 can be an independently allocated encrypted partition in a pluggable device.

[0101] An independently allocated encrypted partition refers to a dedicated storage area within the physical storage space of a pluggable device, which is separately partitioned through partitioning logic, physically or logically isolated from ordinary storage areas, and possesses encryption protection capabilities. This encrypted partition can store the core resources related to the intelligent agent, distinct from the public readable storage area within the pluggable device.

[0102] In one implementation, the encrypted partition can be a logical encrypted partition. The main control program in the processor 102 divides the independent logical storage space, and the encrypted partition is also configured with an access key. Only electronic devices with the access key can access the environment deployment files stored in the encrypted partition, or only the main control program with the access key can read the environment deployment files stored in the encrypted partition and write them to the corresponding directory in the electronic device.

[0103] In another implementation, the encrypted partition can be a physical hardware encrypted partition, which is physically partitioned into the memory before it leaves the factory and equipped with a hardware encryption engine. The hardware encryption engine is integrated within the processor or memory of the pluggable device, and is a dedicated cryptographic operation hardware unit independent of the processor. It is used to independently perform security operations such as data encryption, decryption, hash verification, key storage, and partition permission control, without relying on any software encryption program on the electronic device.

[0104] In another implementation, the encrypted partition can be a hidden encrypted partition. A hidden encrypted partition is an independent storage area within the pluggable device's memory, formed through partitioning logic and permission configuration. It is neither actively displayed as a drive letter in the electronic device's system resource manager nor does it possess encryption protection capabilities. Ordinary users cannot directly browse or access this partition through the electronic device's folder or disk list; only the pluggable device's own controller can selectively identify, decrypt, and read the internal data.

[0105] In other implementations, the encrypted partition can also be implemented as a read-only encrypted partition, or a dedicated encrypted partition with permissions bound to the device serial number.

[0106] For example, a pluggable device can be a USB hardware peripheral, such as a USB flash drive, which has its internal flash memory storage space divided into a hidden encrypted partition. This encrypted partition does not show a drive letter to the outside world and can only be legally read by the USB flash drive's own controller. This can prevent external copying or tampering with the deployment resources of the intelligent agent, i.e., the environment deployment files.

[0107] The encrypted partition is used to store the environment deployment files corresponding to one or more smart agents. It can refuse to store irrelevant ordinary files, thereby achieving the isolation and security protection of core deployment resources.

[0108] In one implementation, the encrypted partition can allow only reading and prohibit writing and deletion, thus permanently storing the environment deployment files corresponding to each agent and preventing accidental damage to the agent's deployment resources.

[0109] In another implementation, the encrypted partition can support encrypted read-only access, allowing environment deployment files to be retrieved only if the verification password of the controller of the currently pluggable device is matched.

[0110] In another implementation, encrypted partitions can support incremental updates to storage, allowing for silent updates of environment deployment files to higher versions while in an encrypted and isolated state.

[0111] For example, in the encrypted partition of the USB drive, the complete set of environment deployment files for each intelligent agent is stored exclusively, without storing irrelevant data such as documents, pictures, and installation packages, so as to keep the resources in the partition pure and dedicated to the offline deployment of intelligent agents.

[0112] In specific implementation, the environment deployment file includes at least one of the following: the runtime framework file corresponding to the intelligent agent, dependency component files, configuration files, underlying driver files, and startup execution program. The runtime framework file refers to the basic kernel and framework architecture file that supports the normal scheduling and logical operation of the intelligent agent. The dependency component files refer to the class libraries, plugins, runtime libraries, and third-party supporting component files that the intelligent agent depends on for operation. The configuration file refers to the configuration class file that records the intelligent agent's running parameters, path configuration, authorization associations, and interface parameters. The underlying driver file refers to the driver adaptation files that adapt to the hardware interfaces of electronic devices and the underlying system. The startup execution program refers to the executable script used to trigger the loading of the intelligent agent's environment deployment file and initiate the deployment process with one click.

[0113] For example, the encrypted partition of the USB flash drive stores the kernel file of the "Office Automation Intelligent Agent" runtime framework, Python dependency component libraries, initialization parameter configuration files, serial port low-level adapter driver files, and a one-click deployment startup program. Based on this, when the user triggers the deployment control of the "Office Automation Intelligent Agent" on the display interface, the controller in the USB flash drive reads at least one of the above types of files from the encrypted partition and provides them to the laptop computer, completing the rapid setup of the intelligent agent runtime environment on the laptop computer.

[0114] As can be seen, this embodiment achieves isolated and encrypted storage of the environment deployment files of the intelligent agent by setting the memory as an independently allocated encrypted partition. This helps to prevent the environment deployment files from being tampered with or leaked, and improves the resource security of pluggable devices and the integrity of offline deployment of intelligent agents.

[0115] Based on the above implementation scheme, the memory 101 can contain a running program (specifically, the startup execution program mentioned above). The controller 102 can start the running program in response to a pluggable device being connected to the electronic device.

[0116] The program provides a display interface to the electronic device and an environment deployment file corresponding to the first intelligent agent.

[0117] It should be noted that the program embedded in the memory 101 refers to the program code with autonomous operation, interface rendering, and file scheduling functions being pre-burned and fixedly stored in the memory 101 of the pluggable device. It is built in at the factory and cannot be arbitrarily deleted, tampered with, or replaced by the user, without the need for additional download and installation by the electronic device.

[0118] In one implementation, the running program can be stored in a read-only memory area of ​​the memory, allowing only reading and calling, and prohibiting writing, deletion, and formatting modifications;

[0119] In another implementation, the program can be embedded inside the aforementioned hidden encrypted partition, making it invisible to the outside world and only accessible from the controller of the pluggable device.

[0120] In another implementation, the program can be a lightweight embedded executable program, compiled with a reduced instruction set, which occupies a small storage size and has a low startup latency;

[0121] In other implementations, the executable program can also be implemented as firmware, or as a tamper-proof executable program that is bound to a hardware encryption engine for verification.

[0122] For example, when pluggable devices such as USB flash drives are manufactured, a dedicated lightweight operating program deployed by the intelligent agent is burned into a read-only block of the memory. Ordinary users cannot find the operating program through electronic devices, nor can they manually delete or tamper with it, thus ensuring the integrity and security of the operating program.

[0123] It should be noted that the controller starting the running program refers to the following: after the pluggable device and the electronic device establish physical and communication links, the controller in the pluggable device detects connection events in real time. When a connection event is detected, it automatically loads and wakes up the running program embedded in memory, or, in response to a trigger operation performed by the user through the electronic device, loads and wakes up the running program embedded in memory. Here, a trigger operation refers to the electronic device outputting corresponding prompt information for the pluggable device when it detects a connection event, such as a pop-up prompt or a double-click by the user on the prompt.

[0124] In one implementation, the pluggable device can be connected to the electronic device via a Universal Serial Bus Type-C interface (USB Type-C). The controller in the pluggable device automatically triggers the program to start automatically upon power-up.

[0125] In another implementation, the controller in the pluggable device can detect the device mounting (the pluggable device is connected to the electronic device) based on bus enumeration and then automatically start the running program after a preset delay.

[0126] In another implementation, after the controller in the pluggable device completes hardware identity verification and encrypted partition verification, it allows the startup of the fixed program to prevent unauthorized device impersonation.

[0127] For example, when a USB flash drive is inserted into the USB port of a laptop, the controller in the flash drive detects that the bus enumeration is complete and the link with the device is established. Without any manual operation by the user, it automatically loads and starts the program embedded in the memory.

[0128] Therefore, the running program that is launched provides a display interface to the electronic device, meaning that the running program has the ability to render interfaces and interact with pop-ups, and can generate a graphical interactive window (i.e., a display interface) on the upper layer of the electronic device's operating system. The display interface can at least be used to display the deployment controls and other functional controls of the intelligent agent, realizing human-computer visual interaction.

[0129] In one implementation, the running program can generate an independent pop-up floating display interface and provide it to the electronic device for display. The deployment entry point of the intelligent agent, i.e., the deployment control, is displayed at the top of the display interface.

[0130] In another implementation, the program can call the electronic device's native system window component, which generates the display interface of an embedded standard dialog box.

[0131] For example, once the program embedded in the USB drive is launched, a graphical interface automatically pops up on the desktop of the electronic device. The interface neatly displays the deployment controls, function descriptions, and other content corresponding to the first intelligent agent, allowing users to intuitively click and select without the need for additional interface software installation.

[0132] The provision of environment deployment files by the running program means that the running program embedded in the pluggable device has the ability to schedule files and distribute data. It can read the environment deployment file corresponding to the first intelligent agent in the memory and complete the transmission and writing of the environment deployment file to the electronic device.

[0133] In one implementation, the running program can control the bus channel to use a silent transmission method, seamlessly sending the environment deployment file corresponding to the first intelligent agent to the electronic device.

[0134] In another implementation, the running program can grant access to the encrypted partition, allowing the electronic device to actively read the environment deployment files of the first intelligent agent.

[0135] For example, after the user triggers the deployment control of the first intelligent agent in the display interface, the running program in the pluggable device automatically reads the corresponding runtime framework file, dependent component file and other environment deployment files in the encrypted partition, and silently sends them to the electronic device through the USB data interaction channel, automatically completing directory writing and environment configuration, without any manual copying or folder operation.

[0136] As can be seen, in this embodiment, a dedicated running program can be embedded in the memory. When a pluggable device is connected, the controller automatically starts the running program, without requiring any third-party software to be pre-installed on the electronic device. Based on this, the embedded running program can be used to automatically push the display interface and automatically distribute the intelligent agent environment deployment files, which can further reduce manual intervention and achieve plug-and-play and one-click offline deployment. At the same time, the embedded running program has anti-deletion and anti-tampering characteristics, thereby improving the operational stability of pluggable devices and the deployment security of intelligent agents.

[0137] Based on the above implementation scheme, the pluggable device can determine the first intelligent agent based on the stored environment deployment files and the device data detected by the electronic device. The first intelligent agent is an intelligent agent that is adapted to the electronic device but is not deployed in the electronic device.

[0138] Furthermore, the pluggable device can also determine a second intelligent agent based on the device data of the electronic device. The second intelligent agent is an intelligent agent already deployed in the electronic device, and the pluggable device also stores the environment deployment file corresponding to the second intelligent agent. For example, the pluggable device can scan the electronic device's processes, system configuration items (such as registry information), and other device data to determine the second intelligent agent already deployed in the electronic device.

[0139] Based on this, the display interface also shows the configuration controls corresponding to the second intelligent agent. Users can trigger operations on the configuration controls corresponding to the second intelligent agent in the display interface. The controller in the pluggable device can respond to the trigger operation received on the electronic device and trigger the display interface to output the configuration interface corresponding to the second intelligent agent. Users can configure the second intelligent agent in the configuration interface.

[0140] It should be noted that device data of electronic devices refers to information such as the hardware and software configuration, system version, installed software, and operating environment status of electronic devices that are automatically detected and collected after pluggable devices are connected to the electronic devices.

[0141] Based on this, the pluggable device determines the first intelligent agent, which can be specifically: based on the intelligent agents belonging to the environment deployment files stored in the pluggable device, the first intelligent agent with exclusive adaptation rules that match the device data of the electronic device is selected.

[0142] The agent-specific adaptation rules can be stored in the encrypted partition of the pluggable device. Each agent-specific adaptation rule is a set of structured adaptation constraint parameters uniquely bound to each type of agent. These rules are factory-preset operational access conditions for the agent, limiting the deployment conditions required for the agent to function properly, including the system version, hardware resources, dependent environment, architecture type, and interface protocols of the electronic device. In this embodiment, the agent-specific adaptation rules of the environment deployment file stored on the pluggable device can be compared line by line with the device data of the electronic device to select the first agent.

[0143] Specifically, the dedicated adaptation rules can include rules across multiple dimensions, such as system adaptation rules, hardware resource rules, runtime dependency rules, system architecture rules, and interface adaptation rules, among others. System adaptation rules specify the operating system type, system bitness, and minimum system version number supported by the agent. Hardware resource rules specify the minimum processor clock speed, minimum memory capacity, storage space threshold, and graphics card computing power requirements for the agent. Runtime dependency rules specify the required dependency library versions, runtime framework versions, and compatible versions of underlying components. System architecture rules specify the processor architecture adaptation type. Interface adaptation rules specify the interface protocol adaptation requirements for serial ports, network interfaces, USB interfaces, etc. Deployment status rules are preset locally unique deployment identifier rules used to determine whether the electronic device has pre-installed the agent's runtime environment.

[0144] For example, the specific adaptation rules for "Agent A" are: only compatible with Windows 10 and above 64-bit systems, with at least 8GB of memory, Python 3.8 or above as a dependency, and x86 architecture, etc.

[0145] Based on this, the pluggable device can determine the first intelligent agent through at least one of the following implementation methods:

[0146] In one implementation, the pluggable device can compare the system version and system bitness parameters in the dedicated adaptation rules with the system information in the device data of the electronic device, and select the first intelligent agent among the intelligent agents to which the environment deployment file provided by the pluggable device belongs that is compatible with the electronic device in terms of system.

[0147] In another implementation, the pluggable device can compare the memory, CPU, and minimum hardware configuration thresholds in the exclusive adaptation rules with the hardware parameters in the device data of the electronic device to select the first intelligent agent whose hardware resources meet the standards.

[0148] In another implementation, the pluggable device can compare the dependency framework version requirements in the dedicated adaptation rules with the runtime library versions already deployed in the device data of the electronic device to select the first intelligent agent whose dependency environment matches the electronic device.

[0149] For example, if an electronic device is a 64-bit Windows 11 system with 16GB of memory and a configured Python 3.9 runtime environment, but Agent A is not installed locally; and if Agent A's specific adaptation rules are matched against the above device data and all matches are successful, and no deployment record is found locally (process keywords and registry information do not match Agent A), then the pluggable device will automatically identify Agent A as the first agent and display the corresponding deployment controls for the first agent on the display interface. If the specific adaptation rules do not match the electronic device's hardware system, or if an agent is already deployed locally, the deployment controls will not be displayed to avoid invalid deployment operations. However, the configuration controls for Agent B will still be displayed on the display interface; Agent B has been deployed on the electronic device, and its environment deployment file is stored on the pluggable device.

[0150] As can be seen, this embodiment uses pluggable devices to link locally pre-stored environment deployment files with real-time collected device data from electronic devices, adaptively selecting the first intelligent agent that is compatible and not deployed on electronic devices. It can automatically adapt to different electronic devices, shield incompatible and already deployed intelligent agents, reduce user selection costs, and improve the intelligence and accuracy of offline one-click deployment of intelligent agents.

[0151] Based on the above implementation scheme, the controller 101 in the pluggable device provides the electronic device with the environment deployment file corresponding to the first intelligent agent, which may specifically include the following processes, such as... Figure 4 As shown:

[0152] Step 401: Read the environment deployment file of the first agent stored in the memory;

[0153] The controller in the pluggable device can locate the corresponding storage path in the memory or the corresponding storage location in the encrypted partition based on the agent identifier of the first agent, and then read the environment deployment file of the first agent from the located storage path or storage location.

[0154] In one implementation, the controller in the pluggable device can directly read the environment deployment files stored in a separate encrypted partition in the pluggable device based on the identifier of the first intelligent agent.

[0155] In another implementation, the controller in the pluggable device can call the hardware encryption engine to decrypt the environment deployment files stored in the encrypted partition, and then read the environment deployment files in the encrypted partition.

[0156] Step 402: Write the environment deployment file of the first intelligent agent into the corresponding directory in the electronic device.

[0157] The directory containing the environment deployment files for the first intelligent agent in the electronic device refers to the preset program installation directory, dependency library directory, application configuration directory, and custom working directory in the electronic device's operating system. Based on this, the controller in the pluggable device silently transmits and stores the environment deployment files to a specified path in the electronic device through the data interaction channel between the controller and the electronic device, forming a complete local file structure.

[0158] In one implementation, the controller can write the environment deployment file to the default application installation directory of the electronic device system; or, write the environment deployment file to a custom dedicated working directory on a non-system disk of the electronic device; or, write the files according to their file types, such as writing framework files to the main program directory, dependent components to the public library directory, and configuration files to the hidden configuration directory.

[0159] In another implementation, the controller can automatically create a brand new dedicated directory in the electronic device and neatly write all the environment deployment files into the newly created dedicated directory.

[0160] Step 403: Configure the first intelligent agent into the system configuration items of the electronic device.

[0161] Among them, system configuration items specifically refer to the core system configuration items in the operating system used to uniformly store hardware information, software installation information, path mapping, environment variables, startup items, and service configurations, such as the registry.

[0162] Specifically, in this embodiment, configuring the first intelligent agent into the system configuration item means that the controller writes configuration information such as intelligent agent identifier, installation path, version information, startup item and service registration to the designated system configuration item of the electronic device, so that the operating system can recognize, schedule and start the first intelligent agent normally.

[0163] For example, the controller can write the following behaviors to the system configuration items of the electronic device: write the agent registration information of agent A to the application uninstall list key value to realize system recognition and management; write the agent path of agent A to the system environment variable key value to make the agent program globally callable; write the registration information of agent A to the startup item key value to support the agent to start automatically with the system; register the background service of agent A to the service management configuration item key value to realize background persistent operation.

[0164] As can be seen, in this embodiment, the pluggable device sequentially executes the standardized process of file reading, directory writing, and system configuration item configuration. Relying on the integrated operation of targeted reading of encrypted partitions, automatic writing of categorized directories, and automatic configuration of system configuration items, the entire process is completed silently in the background without manual intervention, which significantly improves the deployment efficiency and environmental adaptability stability of the intelligent agent.

[0165] Based on the above implementation scheme, the controller in the pluggable device can provide the first intelligent agent with a lexical authorization key after providing the first intelligent agent with the environment deployment file corresponding to the first intelligent agent, so that the electronic device can use the corresponding target lexical through the lexical authorization key.

[0166] The lexical authorization key, also known as a token encryption credential, is an encrypted credential string that is pre-stored in the memory of a pluggable device (specifically, within an encrypted partition) and has a validity verification function. The lexical authorization key can be used to characterize the lexical quota, interface access permissions, and eligibility to use computing power services (i.e., computing power permissions) that an agent can access.

[0167] For example, once the operating environment of agent A is deployed, the controller in the USB flash drive can read the pre-set token from the encrypted partition of the pluggable device and automatically write it into the authentication configuration folder of agent A in the electronic device via the USB data interaction channel in a silent transmission manner, without requiring the user to manually import the key or manually enter the authorization code.

[0168] It should be noted that the controller in the pluggable device can transmit the token authorization key in an encrypted manner and distribute the token authorization key in ciphertext form, which can prevent key leakage.

[0169] The target lexical unit refers to the character unit of text processing that the intelligent agent can call, the token computing power quota for dialogue interaction, the calling quota for model inference, and the interface service resources, etc.

[0170] Based on this, in this embodiment, the first intelligent agent in the electronic device uses the target lexical through the lexical authorization key. This means that after the first intelligent agent starts up, it automatically loads the lexical authorization key and completes the legality verification. After the verification is passed, it can call the corresponding amount of lexical computing power resources such as model reasoning, dialogue interaction, and task processing in accordance with regulations.

[0171] For example, when agent A runs on a laptop, it automatically loads the locally written token authorization key. After the legality verification is passed, it can normally call the corresponding amount of token computing power resources such as dialogue interaction, text generation, and task parsing. No additional network activation or repeated purchase of computing power authorization is required. Once deployed, the full functionality of the agent can be used directly.

[0172] As can be seen, in this embodiment, after the first agent's operating environment is deployed, the controller automatically configures the lexical authorization key to the first agent, realizing an integrated process of offline environment deployment and automatic lexical authorization configuration. There is no need for manual input or import of authorization credentials, which can reduce the user's operating threshold and help improve the security of the lexical authorization key and the convenience of using the agent's computing power.

[0173] Furthermore, the controller in the pluggable device can also monitor the status of the token authorization key and the status of the agent's operating environment in real time, and execute self-healing processing logic such as interface prompts, key re-issuance, or environment deployment file re-issuance for various abnormal scenarios such as key expiration, key error, and abnormal operating environment.

[0174] In one implementation, the controller outputs a first prompt message on the display interface when it detects that the lexical authorization key has expired. The first prompt message serves at least to indicate that the lexical authorization key has expired.

[0175] It should be noted that the expiration of a lexical authorization key means that the key's built-in validity period, usage cycle, or computing power limit has been exhausted, exceeding the preset legal usage period or quota limit, and thus it no longer has the legal right to access the target lexical. Based on this, the first notification message can be: text, highlighted icons, or voice prompts displayed in a pop-up window on the pluggable device's display interface, used to intuitively inform the user of the lexical authorization key's expiration and invalidation status.

[0176] For example, when the controller in the USB drive detects that the key usage period has expired (the system real-time time exceeds the key's built-in timestamp) or the model lexical call quota has been exhausted (the consumed lexical quota of the statistical agent has reached the quota limit bound to the key), it immediately pops up the first prompt message on the laptop's display interface, such as "The current agent lexical authorization key has expired. Please renew the authorization in time," clearly informing the user of the reason for the authorization failure in text form.

[0177] In another implementation, if the controller detects an error in the lexical authorization key, it outputs a second prompt message on the display interface and, in response to a confirmation operation for the erroneous operation of the second prompt message, re-provides the lexical authorization key to the first agent, or re-provides the environment deployment file corresponding to the first agent to the electronic device.

[0178] The term authorization key error refers to an abnormal state where the term authorization key issued to the first agent has been tampered with, the file is corrupted, the key does not match, the verification signature is invalid, or it is incompatible with the agent version, resulting in authentication failure. Correspondingly, the second prompt message is a message specifically displayed on the interface for key anomalies, informing the user of the key verification failure and guiding the user to perform a confirmation and repair operation. The erroneous operation confirmation operation refers to the user's click-based interactive operation triggered by the second prompt message on the display interface, such as confirming repair, resetting adaptation, or restarting configuration. If the user performs a confirmation and repair operation, the controller can respond to this erroneous operation confirmation operation by re-providing the term authorization key to the first agent, or re-providing the environment deployment file corresponding to the first agent to the electronic device.

[0179] For example, if the controller in the USB drive detects that the lexical authorization key loaded by agent A has been tampered with, the signature verification failed, or the key is incompatible with the current agent version, it will display a second prompt message on the laptop screen, such as "Lexical authorization key verification error, confirm repair and reset?" The interface will also provide a clickable confirmation control for incorrect operation. After the user clicks the confirmation control, the controller in the USB drive can reread the valid lexical authorization key from the hidden encrypted partition and silently write it to the corresponding directory of agent A to complete the reset; or it can directly redeploy the complete set of environment deployment files for agent A, overwrite the abnormal files, and reconfigure them in the system configuration items to achieve one-click self-healing repair.

[0180] In another implementation, when the controller detects an anomaly in the operating environment of the first agent, it re-provides the electronic device with the environment deployment file corresponding to the first agent.

[0181] Among them, the abnormal operating environment of the first intelligent agent refers to the abnormal state in which the first intelligent agent cannot start normally or reports an error due to missing operating directory files, damaged dependent components, invalid system configuration items, incorrect environment variable configuration, program crashing on startup, or disordered configuration files.

[0182] In one implementation, the controller can determine whether the first agent's operating environment is abnormal by detecting the integrity of its key runtime files, monitoring the agent's startup logs and error return codes, and periodically checking registry entries and environment variable configurations. Accordingly, if the first agent's operating environment is abnormal, the controller will re-provide the electronic device with the corresponding environment deployment files for the first agent.

[0183] For example, when the controller in the USB drive detects abnormal operating conditions of the operating environment such as startup failure, missing core framework files, or missing registry entries for agent A, it automatically rereads the environment deployment files in the encrypted partition of the USB drive without requiring the user to manually uninstall and reinstall, and silently writes them to the corresponding directory on the laptop. Then, it reconfigures the system configuration items, thereby repairing the operating environment faults of agent A with one click.

[0184] As can be seen, in this embodiment, the controller can monitor the validity period of the token authorization key, the integrity of the key, and the status of the agent's operating environment around the clock. For the three scenarios of key expiration, key error, and abnormal operating environment, it can realize intelligent interface prompts, interactive confirmation and repair, and automatic reinstallation and self-healing, which can reduce the manual operation cost of agent deployment and subsequent maintenance.

[0185] Based on the above implementation scheme, the controller in the pluggable device can respond to the electronic device receiving a trigger operation on the delete control corresponding to the first intelligent agent and reclaim the environment deployment file corresponding to the first intelligent agent in the electronic device.

[0186] As can be seen, in this embodiment, the pluggable device can set a deletion control in the display interface provided to the electronic device. The controller in the pluggable device responds to the user's trigger operation on the deletion control, automatically reclaims and cleans up the environment deployment files of the first intelligent agent deployed in the electronic device, and realizes one-click undo deployment and uninstallation without residue.

[0187] For example, such as Figure 5 As shown, after agent A is deployed to the laptop, a delete control for agent A (no longer a deployment control) is displayed on the laptop's screen provided by the USB drive. The delete control can be implemented in any of the following ways: an embedded text button control, a combination of a checkbox and batch delete buttons, an uninstall option control in the right-click menu, or a floating function icon control. Each delete control corresponds independently to each deployed agent. Users can click or check the delete control to trigger the agent's uninstallation process. The controller on the USB drive captures this triggering operation in real time and can further prompt a second time with a pop-up window asking "Are you sure you want to uninstall this agent and clean up all deployment files?" After user confirmation, the environment deployment file recycling process is officially initiated.

[0188] Specifically, when the controller executes the recycling process, it can automatically traverse the main program directory, dependency library directory, and configuration hidden directory corresponding to the first intelligent agent in the electronic device, and delete all environment deployment files such as runtime framework files, dependency component files, and startup execution programs in batches. At the same time, it deletes the corresponding application registration key values, startup items, and custom environment variables in the system configuration items, stops the persistent background process of the intelligent agent, and completely completes one-click uninstallation and cleanup without residue, without requiring users to manually delete folders or manually modify system configuration items.

[0189] As can be seen, in this embodiment, the deployment of an intelligent agent can be undone with one click through the delete control in the display interface, eliminating the need for manual uninstallation. This improves the cleanliness, convenience, and automation of intelligent agent deployment and uninstallation.

[0190] refer to Figure 6 This is a flowchart illustrating the implementation of a method for deploying an intelligent agent according to an embodiment of this application. This method can be applied to pluggable devices, such as... Figure 2 As shown in the figure, the pluggable device in this embodiment relies on hardware integrated storage and control capabilities to realize offline one-click deployment of the intelligent agent's operating environment, which helps to reduce manual complexity and improve the deployment efficiency of the intelligent agent's operating environment.

[0191] Specifically, the method in this embodiment may include the following steps:

[0192] Step 601: In response to the pluggable device being connected to the electronic device, provide a display interface to the electronic device.

[0193] The display interface should at least show the deployment controls corresponding to the first intelligent agent;

[0194] Step 602: In response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent, provide the electronic device with the environment deployment file corresponding to the first intelligent agent.

[0195] The environment deployment file includes the files generated by executing the installation package corresponding to the first intelligent agent, which enables the deployment of the first intelligent agent in the electronic device.

[0196] As can be seen from the above scheme, in the deployment method of an intelligent agent provided in this application embodiment, the environment deployment file corresponding to the intelligent agent is pre-stored in the hardware carrier through a pluggable device. When the pluggable device is connected to an electronic device, the display interface automatically pops up. The user only needs to trigger the corresponding deployment control, without having to manually download the installation package online, manually perform the installation, and configure the running environment item by item. Thus, this application can realize one-click deployment of intelligent agents, which can greatly simplify the operation process, reduce manual intervention, and allow ordinary users to independently complete the construction of the intelligent agent's running environment. Moreover, this application can get rid of the limitation of online deployment and can quickly complete the deployment of the running environment even without a network, which can greatly shorten the deployment time and thus significantly improve the deployment efficiency of the intelligent agent's running environment.

[0197] Based on the above implementation scheme, in this embodiment, before providing a display interface to the electronic device, the device data of the electronic device can be detected first, and then the intelligent agent detection information can be obtained according to the device data and the deployment environment file stored in the pluggable device.

[0198] The device data represents the hardware and software information deployed in the electronic device and the device's operational information, specifically including: the electronic device's hardware and software configuration, system version, installed software, and operating environment status. The agent detection information represents at least a first agent that is compatible with the electronic device but not deployed there. The agent detection information also represents a second agent already deployed in the electronic device, with the pluggable device storing an environment deployment file matching the second agent (containing the second agent's specific adaptation rules).

[0199] In one implementation, when the pluggable device obtains agent detection information based on device data and deployment environment files stored in the pluggable device, it can achieve this through at least one of the following:

[0200] In one specific implementation, a pluggable device can determine whether the runtime environment of any intelligent agent within the pluggable device has been deployed in an electronic device. For example, if the process key and registry information in the electronic device do not match that of a certain intelligent agent in the pluggable device, it can be determined that the intelligent agent has not been deployed in the electronic device.

[0201] In another specific implementation, the pluggable device can determine whether the version information of the operating environment of an agent already deployed in the electronic device matches the version of the corresponding agent in the pluggable device. For example, if the version information of the operating environment of an agent already deployed in the electronic device does not match the current version of that agent in the pluggable device, then it can be assumed that that version of the agent is not deployed in the electronic device.

[0202] In another specific implementation, the pluggable device can determine whether the hardware and software information of an electronic device matches the operational requirements of any intelligent agent within the pluggable device. For example, if the hardware and software information of the electronic device matches the operational requirements of a particular intelligent agent within the pluggable device, it can be determined that the intelligent agent is compatible with the electronic device.

[0203] Based on this, this embodiment can determine the first intelligent agent that is compatible with electronic devices but not deployed in electronic devices, the second intelligent agent that has been deployed in electronic devices but is an outdated version, and other intelligent agents that are not compatible with electronic devices through the above-mentioned specific implementation methods. It can automatically adapt to different electronic devices and shield incompatible and deployed intelligent agents. As a result, the required intelligent agents can be deployed with one click under the user's trigger operation, reducing the user's selection cost and improving the intelligence level and adaptation accuracy of offline one-click deployment of intelligent agents.

[0204] Based on the above implementation scheme, in step 602 of this embodiment, when providing the environment deployment file corresponding to the first intelligent agent to the electronic device, the following processing can be used:

[0205] First, read the environment deployment file corresponding to the first intelligent agent from the pluggable device;

[0206] Then, the environment deployment file of the first intelligent agent is written into the corresponding directory in the electronic device;

[0207] Finally, the first agent is configured into the system configuration items of the electronic device.

[0208] As can be seen, in this embodiment, the pluggable device sequentially executes the standardized process of file reading, directory writing, and system configuration item configuration. Relying on the integrated operation of targeted reading of encrypted partitions, automatic writing of categorized directories, and automatic configuration of system configuration items, the entire process is completed silently in the background without manual intervention, which significantly improves the deployment efficiency and environmental adaptability stability of the intelligent agent.

[0209] Based on the above implementation scheme, in this embodiment, after providing the electronic device with the environment deployment file corresponding to the first intelligent agent in step 602, the token authorization key stored in the pluggable device can also be read and written into the directory corresponding to the first intelligent agent, so that the electronic device can use the corresponding target token through the token authorization key.

[0210] The token authorization key can also be called a token certificate.

[0211] As can be seen, in this embodiment, after the first agent's operating environment is deployed, the controller automatically configures the lexical authorization key to the first agent, realizing an integrated process of offline environment deployment and automatic lexical authorization configuration. There is no need for manual input or import of authorization credentials, which can reduce the user's operating threshold and help improve the security of the lexical authorization key and the convenience of using the agent's computing power.

[0212] Furthermore, this embodiment can also monitor the status of the lexical authorization key and the status of the agent's operating environment, specifically including the following processes:

[0213] If the token authorization key is detected to have expired, a first prompt message is output; the first prompt message is used at least to indicate that the token authorization key has expired.

[0214] If the token authorization key is detected to be incorrect, a second prompt message is output; the second prompt message is at least used to confirm the erroneous operation.

[0215] In response to the erroneous operation confirmation operation for the second prompt information, return to the step of: providing the first agent with a lexical authorization key, or return to the step of: providing the electronic device with the environment deployment file corresponding to the first agent;

[0216] If an abnormality is detected in the operating environment of the first intelligent agent, the process returns to the step of providing the electronic device with the environment deployment file corresponding to the first intelligent agent.

[0217] As can be seen, this embodiment can monitor the validity period of the token authorization key, the integrity of the key, and the status of the agent's operating environment around the clock. For the three scenarios of key expiration, key error, and abnormal operating environment, it can realize intelligent interface prompts, interactive confirmation and repair, and automatic reinstallation and self-healing, which can reduce the manual operation cost of agent deployment and subsequent maintenance.

[0218] Based on the above implementation scheme, the display interface also shows a delete control corresponding to the second intelligent agent. The second intelligent agent is an intelligent agent already deployed in the electronic device. Furthermore, the second intelligent agent stores corresponding exclusive adaptation rules in the pluggable device.

[0219] Based on this, in this embodiment, the environment deployment file corresponding to the second intelligent agent in the electronic device can also be reclaimed in response to the triggering operation of the deletion control corresponding to the second intelligent agent.

[0220] As can be seen, in this embodiment, the pluggable device can set a deletion control in the display interface provided to the electronic device. The pluggable device responds to the user's trigger operation on the deletion control, automatically reclaims and cleans up the environment deployment files of the first intelligent agent deployed in the electronic device, and realizes one-click undo deployment and uninstallation without residue.

[0221] Based on the above implementation scheme, the environment deployment file corresponding to the first intelligent agent is stored in an encrypted partition within the pluggable device. The environment deployment file corresponding to the first intelligent agent may include at least one of the following: the runtime framework file, dependent component files, configuration files, underlying driver files, and startup executable program.

[0222] As can be seen, this embodiment achieves isolated and encrypted storage of the environment deployment files of the intelligent agent by deploying an independent encrypted partition in the pluggable device. This helps prevent the environment deployment files from being tampered with or leaked, and improves the resource security of the pluggable device and the integrity of the offline deployment of the intelligent agent.

[0223] It should be noted that the specific implementation of each step in this embodiment can be found in the corresponding content above, and will not be described in detail here.

[0224] refer to Figure 7 This is a schematic diagram of a deployment device for an intelligent agent provided in an embodiment of this application. The device can be installed in a pluggable device and may include the following units:

[0225] The interface providing unit 701 is configured to provide a display interface to the electronic device in response to the pluggable device being connected to the electronic device; the display interface displays at least the deployment controls corresponding to the first intelligent agent.

[0226] The file providing unit 702 is configured to provide the electronic device with an environment deployment file corresponding to the first intelligent agent in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent;

[0227] The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

[0228] As can be seen from the above solution, in the deployment device for an intelligent agent provided in this application embodiment, a memory and controller are integrated through a pluggable device, and the environment deployment file corresponding to the intelligent agent is pre-stored on the hardware carrier. When the pluggable device is connected to an electronic device, the display interface automatically pops up. The user only needs to trigger the corresponding deployment control, without having to manually download the installation package online, manually perform the installation, and configure the running environment item by item. Thus, this application can achieve one-click deployment of intelligent agents, which can greatly simplify the operation process, reduce manual intervention, and allow ordinary users to independently complete the construction of the intelligent agent's running environment. Moreover, this application can get rid of the limitation of online deployment and can quickly complete the deployment of the running environment even without a network, which can greatly shorten the deployment time and thus significantly improve the deployment efficiency of the intelligent agent's running environment.

[0229] It should be noted that the specific implementation of each unit in this embodiment can be referred to the corresponding content above, and will not be described in detail here.

[0230] Taking the scenario of deploying an intelligent agent to a laptop computer with one click via a pluggable device such as a USB flash drive as an example, the technical solution of this application is illustrated below. Specifically, this application has the following functions:

[0231] 1. Pre-installed runtime libraries and other environment deployment files in pluggable devices: The lightweight framework of the intelligent agent and its dependent components are embedded in the isolated storage area of ​​the pluggable device, and compatibility testing is completed at the factory.

[0232] 2. Intelligent Environment Detection: Pluggable devices automatically identify the local intelligent agent environment of the laptop, provide reminders for blank devices (laptops without deployed intelligent agents), and trigger the one-click deployment process of the intelligent agent by the user's click.

[0233] 3. Offline deployment without network: The intelligent agent's operating environment is deployed to electronic devices by relying on local resources (environment deployment files) in pluggable devices, without the need for network download, enabling rapid setup even when the network is disconnected.

[0234] 4. Local lightweight deployment: The intelligent agent's operating environment is deployed directly to the user's local device (such as a laptop), without relying on the cloud, and the running permissions are uniformly managed by a pluggable device.

[0235] 5. Deployment and Authorization Linkage: After the intelligent agent's operating environment is deployed, pluggable devices can automatically read the Token encryption certificate and complete the computing power permission configuration in batches with one click (that is, provide the token encryption certificate to the intelligent agent in the laptop).

[0236] In summary, this application incorporates a private storage area (i.e., an encrypted partition) within the USB flash drive and pre-packages lightweight intelligent agent runtime libraries and other environment deployment files. It leverages the built-in application (i.e., the running program) to achieve one-click offline deployment of intelligent agents and automatically authorizes computing power through the Token encryption certificate inside the USB flash drive, thus constructing a non-intrusive and portable intelligent agent operating system.

[0237] It is evident that the technical solution adopted in this application has the following advantages:

[0238] 1. Hardware pre-loaded offline runtime library: The environment deployment files of the lightweight intelligent agent are embedded inside the pluggable device, eliminating the need for online download and enabling rapid deployment in a network-free environment.

[0239] 2. Deployment and authorization linkage: The environment deployment file and computing power authorization (token encryption certificate) are bound into a single process. The token encryption certificate is automatically written after deployment is completed, eliminating the manual configuration link.

[0240] 3. Lightweight and non-intrusive deployment: It adopts lightweight installation logic and abandons heavy container architecture, so that the environment deployment files of the intelligent agent can be deployed to ordinary local directories without intruding on the core system path.

[0241] 4. Hardware adaptive adaptation: Built-in multi-architecture dependency resources automatically identify the laptop's hardware parameters and dynamically match the corresponding smart agent version, reducing the device compatibility threshold.

[0242] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0243] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0244] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0245] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A pluggable device, comprising: The storage device is used to store at least the environment deployment files corresponding to the intelligent agent. A controller is configured to provide a display interface to an electronic device in response to the pluggable device being connected to the electronic device; the display interface at least displays a deployment control corresponding to a first intelligent agent; and to provide an environment deployment file corresponding to the first intelligent agent to the electronic device in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent. The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

2. The pluggable device according to claim 1, wherein the memory is an independently allocated encrypted partition within the pluggable device; in, The encrypted partition is used to store the environment deployment files; The environment deployment file includes at least one of the following: the runtime framework file corresponding to the agent, the dependency component file, the configuration file, the underlying driver file, and the startup execution program.

3. The pluggable device according to claim 1, wherein a running program is stored in the memory; the controller initiates the running program in response to the pluggable device being connected to the electronic device; in, The running program is used to provide a display interface to the electronic device and to provide the electronic device with an environment deployment file corresponding to the first intelligent agent.

4. The pluggable device according to claim 1, wherein the pluggable device determines the first intelligent agent based on the stored environment deployment file and the device data detected by the electronic device; in, The first intelligent agent is an intelligent agent that is adapted to the electronic device but is not deployed in the electronic device.

5. The pluggable device according to claim 1, wherein the controller provides the electronic device with an environment deployment file corresponding to the first intelligent agent, comprising: Read the environment deployment file of the first intelligent agent stored in the memory; Write the environment deployment file of the first intelligent agent into the corresponding directory in the electronic device; Configure the first intelligent agent into the system configuration items of the electronic device.

6. The pluggable device according to claim 1, wherein after the controller provides the electronic device with an environment deployment file corresponding to the first agent, it provides the first agent with a lexical authorization key, so that the electronic device can use the corresponding target lexical through the lexical authorization key.

7. The pluggable device according to claim 6, wherein the controller outputs a first prompt message on the display interface when it detects that the lexical authorization key has expired; The first prompt message is used at least to indicate that the token authorization key has expired; When the controller detects an error in the lexical authorization key, it outputs a second prompt message on the display interface and responds to the erroneous operation confirmation operation for the second prompt message by re-providing the lexical authorization key to the first agent, or re-providing the electronic device with the environment deployment file corresponding to the first agent. When the controller detects an abnormality in the operating environment of the first agent, it re-provides the electronic device with the environment deployment file corresponding to the first agent.

8. The pluggable device according to claim 1, wherein the controller, in response to the electronic device receiving a trigger operation on the delete control corresponding to the first agent, reclaims the environment deployment file corresponding to the first agent in the electronic device.

9. A method for deploying an intelligent agent, applied to a pluggable device, the method comprising: In response to the pluggable device being connected to an electronic device, a display interface is provided to the electronic device; The display interface displays at least the deployment controls corresponding to the first intelligent agent; In response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent, the electronic device is provided with an environment deployment file corresponding to the first intelligent agent; The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

10. The method of claim 9, further comprising, before providing a display interface to the electronic device: Detect device data of the electronic device; The device data represents the software and hardware information deployed in the electronic device and the operating information of the electronic device; Based on the device data and the deployment environment file stored in the pluggable device, intelligent agent detection information is obtained; the intelligent agent detection information at least characterizes a first intelligent agent that is adapted to the electronic device but is not deployed in the electronic device.

11. The method according to claim 10, wherein obtaining agent detection information based on the device data and the deployment environment file stored in the pluggable device includes at least one of the following: Determine whether the operating environment of any intelligent agent in the pluggable device has been deployed in the electronic device; Determine whether the version information of the operating environment of the intelligent agent already deployed in the electronic device matches the corresponding intelligent agent in the pluggable device; Determine whether the hardware and software information of the electronic device matches the operational requirements of any intelligent agent in the pluggable device.

12. The method according to claim 9, providing the electronic device with an environment deployment file corresponding to the first intelligent agent, comprising: Read the environment deployment file corresponding to the first intelligent agent from the pluggable device; Write the environment deployment file into the corresponding directory in the electronic device; Configure the first intelligent agent into the system configuration items of the electronic device.

13. The method according to claim 9, after providing the electronic device with the environment deployment file corresponding to the first intelligent agent, the method further includes: Read the token authorization key stored in the pluggable device; The lexical authorization key is written into the directory corresponding to the first intelligent agent, so that the electronic device can use the corresponding target lexical through the lexical authorization key.

14. The method according to claim 13, further comprising: If the token authorization key is detected to have expired, a first prompt message will be output; The first prompt message is used at least to indicate that the token authorization key has expired; If the token authorization key is detected to be incorrect, a second prompt message will be output. The second prompt message is at least used to confirm the erroneous operation; In response to the erroneous operation confirmation operation for the second prompt information, return to the step of: providing the first agent with a lexical authorization key, or return to the step of: providing the electronic device with the environment deployment file corresponding to the first agent; If an abnormality is detected in the operating environment of the first intelligent agent, the process returns to the step of providing the electronic device with the environment deployment file corresponding to the first intelligent agent.

15. The method according to claim 9, wherein the display interface further displays a delete control corresponding to the second intelligent agent; the second intelligent agent is an intelligent agent already deployed in the electronic device; in, The method further includes: In response to a trigger operation on the delete control corresponding to the second agent, the environment deployment file corresponding to the second agent in the electronic device is reclaimed.

16. The method according to claim 9, wherein the environment deployment file corresponding to the first intelligent agent is stored in an encrypted partition partitioned within the pluggable device; in, The environment deployment file corresponding to the first intelligent agent includes at least one of the following: the runtime framework file, dependent component file, configuration file, underlying driver file, and startup execution program corresponding to the first intelligent agent.

17. A deployment device for an intelligent agent, disposed in a pluggable device, the device comprising: An interface providing unit is configured to provide a display interface to the electronic device in response to the pluggable device being connected to the electronic device; The display interface displays at least the deployment controls corresponding to the first intelligent agent; The file providing unit is configured to provide the electronic device with an environment deployment file corresponding to the first intelligent agent in response to the electronic device receiving a trigger operation on the deployment control corresponding to the first intelligent agent; The environment deployment file includes files generated by executing the installation package corresponding to the first intelligent agent, thereby deploying the operating environment of the first intelligent agent in the electronic device.

Images