An agent tool migration method and storage medium

Abstract

The application discloses an agent tool migration method and a storage medium. The method comprises the following steps: in response to the storage medium accessing a first electronic device, starting a migration program in the storage medium on the first electronic device; reading to-be-migrated data of an agent tool from the storage medium through the migration program; the agent tool is generated by a second electronic device in response to a user operation and is written into the storage medium by the second electronic device; the agent tool is used for driving an agent to execute a first target task; and the to-be-migrated data is configured to the agent tool of the first electronic device.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for migrating intelligent agent tools and a storage medium. Background Technology

[0002] With the development of artificial intelligence technology, users can customize, debug, and iteratively evolve intelligent agent tools (such as Skills) locally on their terminal devices. Among these, how to achieve cross-device migration of personalized Skills locally on the terminal when users have cross-device migration needs is a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0003] The technical solution provided in this application is as follows:

[0004] The first aspect of this application provides a method for transferring intelligent agent tools, including:

[0005] In response to the access of the storage medium to the first electronic device, a migration program in the storage medium is initiated on the first electronic device;

[0006] The migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool; the intelligent agent tool is generated by the second electronic device in response to user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform a first target task;

[0007] Configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0008] In one possible implementation, reading the agent tool's migration data from the storage medium via the migration procedure includes:

[0009] The migration procedure establishes a migration operation entry point between the first electronic device and the storage medium.

[0010] In response to a migration command triggered by the user through the migration operation entry, the migration data of the intelligent agent tool is read from the storage medium.

[0011] In one possible implementation, the agent tool migration method further includes:

[0012] Read the first usage parameter from the storage medium; the first usage parameter is used to identify whether the usage permission of the intelligent agent tool data to be migrated is to be transferred or shared;

[0013] The intelligent agent tool for configuring the data to be migrated to the first electronic device includes:

[0014] If the first parameter identifier is shared, the storage area of ​​the intelligent agent tool of the first electronic device is divided into a first sub-storage area and a second sub-storage area. The first sub-storage area is used to store the private data of the intelligent agent tool of the first electronic device; the private data is used to configure the intelligent agent tool to perform a second target task; the second sub-storage area is used to store the data to be migrated.

[0015] In one possible implementation, the agent tool migration method further includes:

[0016] If the first usage parameter identifier is shared, read the second usage parameter from the storage medium;

[0017] The use of the data to be migrated is controlled based on the second usage parameter.

[0018] In one possible implementation, the second usage parameter includes at least one of the following:

[0019] Maximum allowed number of uses; valid deadline; control parameters for controlling whether secondary distribution is allowed.

[0020] In one possible implementation, controlling the use of the data to be migrated based on the second usage parameter includes at least one of the following:

[0021] The number of times the data to be migrated is called is accumulated. When the accumulated number of calls reaches the maximum number of uses, the data to be migrated is prohibited from being called.

[0022] When the current usage time of the data to be migrated exceeds the deadline, the data to be migrated shall not be accessed.

[0023] According to the control parameters, the data to be migrated is prohibited from being exported again and distributed to other electronic devices.

[0024] In one possible implementation, the agent tool migration method further includes:

[0025] In response to the first electronic device successfully reading the data to be migrated, a clearing command is generated on the first electronic device;

[0026] The first electronic device sends a clear command to the storage medium to clear the data to be migrated in the storage medium.

[0027] In one possible implementation, before reading the agent tool's migration data from the storage medium via the migration procedure, the method further includes:

[0028] The first electronic device performs identity authentication and verification on the storage medium.

[0029] If authentication is successful, the migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool.

[0030] In one possible implementation, the authentication verification of the storage medium by the first electronic device includes:

[0031] Read the hardware identifier from the storage medium; the hardware identifier uniquely identifies the storage medium.

[0032] Match the hardware identifier with the target storage medium identifier bound to the first electronic device;

[0033] If a match is found, the authentication is considered successful.

[0034] In another aspect, this application provides a storage medium, comprising:

[0035] The data to be migrated by the intelligent agent tool; the data to be migrated is generated by a second electronic device in response to a user operation and written into the storage medium; the intelligent agent tool is used to drive the intelligent agent to perform a first target task;

[0036] A migration procedure is used to initiate on the electronic device and enable the first electronic device to read the migration data of the intelligent agent tool from the storage medium. Attached Figure Description

[0037] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0038] Figure 1 This is a flowchart illustrating an agent tool migration method provided in Embodiment 1 of this application;

[0039] Figure 2 This is a flowchart illustrating an agent tool migration method provided in Embodiment 2 of this application;

[0040] Figure 3 A schematic diagram illustrating an implementation scenario of the intelligent agent tool migration method provided in this application;

[0041] Figure 4 A schematic diagram illustrating another implementation scenario of the intelligent agent tool migration method provided in this application;

[0042] Figure 5 This is a flowchart illustrating an agent tool migration method provided in Embodiment 3 of this application;

[0043] Figure 6 This is a flowchart illustrating an agent tool migration method provided in Embodiment 4 of this application;

[0044] Figure 7 This is a flowchart illustrating an intelligent agent tool migration method provided in Embodiment 7 of this application. Detailed Implementation

[0045] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0046] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0047] The terms "first," "second," etc., used in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0048] Reference Figure 1 This is a flowchart illustrating an agent tool migration method provided in Embodiment 1 of this application. Figure 1 As shown, the method may include, but is not limited to, the following steps:

[0049] Step S101: In response to the storage medium being connected to the first electronic device, a migration program in the storage medium is started on the first electronic device.

[0050] In this embodiment, the electronic device can be a terminal device with data processing capabilities, such as a personal computer, tablet computer, or smartphone.

[0051] The storage medium can be any removable storage device such as a USB flash drive, external hard drive, or SD card, and it contains a migration program and at least one intelligent agent tool pre-stored inside.

[0052] The agent tool can be used to drive the agent to perform target tasks. The agent tool may include, but is not limited to, business processes or skill tools.

[0053] In this context, a business flow can be understood as an automated task process consisting of multiple execution nodes connected in a preset logical order. Each execution node corresponds to a specific operation or subtask of the intelligent agent. The intelligent agent executes the nodes in the business flow in sequence to complete a complete business objective. For example, a business flow for hotel booking may include multiple sequential execution nodes such as "receiving user travel requests → querying hotels that meet the criteria → comparing prices and ratings → generating booking plans → submitting orders".

[0054] A Skil tool can be understood as a tool module that provides an agent with a specific function or capability. The agent can call the Skil tool as needed during operation to obtain the corresponding specific capability. For example, an image recognition Skil tool can enable the agent to recognize the content of uploaded images, and a calendar management Skil tool can enable the agent to create and query schedule events.

[0055] Both business processes and Skill tools are stored as independent data files on the storage medium. The adapter program reads and loads them into the target intelligent agent during the configuration process, enabling the target intelligent agent to obtain the corresponding task execution capabilities or functional expansion capabilities.

[0056] Once the storage medium is connected to the electronic device, the electronic device can automatically or be triggered by the user to start the migration program on the storage medium.

[0057] In an implementation that automatically initiates the migration process on the storage medium, a management application corresponding to the storage medium may be pre-installed on the electronic device. When the storage medium is connected to the electronic device, the operating system of the electronic device sends a storage medium access notification to the management application. Upon receiving the notification, the management application reads the pre-set identification information in the storage medium, such as a unique device identifier, digital signature certificate, or pre-set matching key, and compares and verifies it with the legitimate identification information pre-registered in the management application.

[0058] If the comparison matches, the storage medium is determined to be a legitimate storage medium matched with this management application. The management application can then retrieve and initiate the migration process from the storage medium. This identification mechanism ensures that the management application only responds to storage media that are paired with it, avoiding the accidental triggering of programs on non-target storage media.

[0059] In implementations where the user triggers the migration process on the storage medium, the user can initiate the adaptation process, but is not limited to doing so, in the following ways:

[0060] In the first method, the user browses the contents of the storage medium in the file management interface of the electronic device and directly double-clicks the migration program file in the storage medium to start it.

[0061] In the second method, the user opens the aforementioned management application on their electronic device and manually selects the connected storage medium through the import or configuration entry provided by the application. The management application then reads and launches the migration program on that storage medium. For example, assuming the user has already installed the management application A corresponding to the storage medium on their personal computer, after connecting the USB flash drive containing the migration program and the smart agent tools to the personal computer, management application A can be launched, and the interface of management application A can display the "Skill Migration" function entry.

[0062] Users can click the "Skill Migration" function entry on the interface. Management application A then scans the currently connected storage media and displays the identified media in a list on the interface, such as "USB drive (D:) - Skill Migration Disk". The user selects the USB drive from the list, and management application A reads the pre-installed identification information in the USB drive and completes the validity verification. After successful verification, management application A automatically extracts the migration program from the USB drive and starts its execution.

[0063] However, it should be noted that in this implementation, the management application A provides users with a visual operation entry point, so that users do not need to directly operate on the files in the storage medium, but can complete the selection of storage medium and start the migration process through the graphical interface of the management application A, thus reducing the complexity of the user's operation.

[0064] Step S102: Read the data to be migrated of the intelligent agent tool from the storage medium through the migration procedure; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform the first target task.

[0065] Users can independently create, modify, and debug workflows and skill tools on their second electronic devices according to their personal needs. After repeated iterations and optimizations, a final personalized intelligent tool is formed. For example, a user can gradually configure a skill tool for daily schedule management through a local debugging interface on the second electronic device, setting parameters such as prompt word templates, schedule creation rules, and reminder trigger conditions. After multiple debugging and optimizations to meet personal usage habits, the skill tool is generated on the second electronic device.

[0066] After the intelligent agent tool is generated on the second electronic device, when the user has a need for cross-device use, such as when the user changes to a new terminal device (i.e., the first electronic device) or wants to reuse the mature and customized Skill on multiple devices, the user can actively trigger the second electronic device to write the final and fully-formed intelligent agent tool data into the storage medium.

[0067] Specifically, the user operates a management application or file management interface on the second electronic device, selects one or more generated intelligent agent tools, and specifies that they be exported to a connected storage medium. In response to the user's export operation, the second electronic device packages the selected intelligent agent tools as structured data files (i.e., data to be migrated) and encrypts them before writing them to the storage medium, completing the local backup.

[0068] Before performing the export operation, the second electronic device can perform authentication and verification on the connected storage media to ensure that the data to be migrated is only written to storage media authorized by the second electronic device, preventing data from being accidentally written to or written to unauthorized storage media and thus causing leakage. Specifically, the second electronic device reads a hardware identifier from the connected storage media. This hardware identifier is used to uniquely identify the storage media, and may be, for example, the storage media's serial number, Device Unique Identifier (UDID), or a pre-installed digital certificate. The second electronic device then matches the read hardware identifier with a locally pre-installed target storage media identifier, which is the identifier of one or more storage media pre-stored on the second electronic device that are authorized to receive the exported data.

[0069] If a match is found, the storage medium is determined to be a legitimate storage medium authorized by the second electronic device, and the second electronic device allows the export operation to be performed on the storage medium; if a mismatch is found, the storage medium is determined to be an unauthorized storage medium, the second electronic device refuses to perform the export operation on the storage medium, and may prompt the user with "This storage medium is not in the authorized list, and data cannot be exported".

[0070] It should be noted that the aforementioned identity authentication verification is automatically performed by the second electronic device, without requiring manual triggering or intervention from the user. When the storage medium is connected to the second electronic device and the export process is triggered, the second electronic device automatically reads the hardware identifier of the storage medium and compares it with the locally preset list of target storage medium identifiers. The entire process is completed automatically in the background.

[0071] The target storage media identifiers pre-configured locally on the second electronic device are configured by the user. During routine use of the management application on the second electronic device, the user can proactively bind one or more storage media that they wish to use for exporting the intelligent agent tool to the second electronic device. Specifically, the user operates the management application on the second electronic device, selects the connected storage media, and performs the binding operation. The management application reads the hardware identifier of the storage media and writes it into the target storage media identifier list on the second electronic device, completing the pre-configuration. Subsequently, when the user initiates an export operation on the second electronic device, there is no need to specify the export target again. The second electronic device automatically reads the hardware identifier of the connected storage media and matches it with the user's pre-configured target storage media identifier list. If a match is found, the export is allowed; otherwise, the export is rejected, and the user is prompted.

[0072] Alternatively, the second electronic device can be pre-configured with a set of default target storage media identifiers at the factory. This default list can be pre-set by the device manufacturer according to the device's usage scenario. For example, it can pre-configure common hardware identifiers for storage media commonly used by other devices in the same product line as the device, or pre-configure standard storage media identifiers officially recommended by the management application. When the user uses the second electronic device for the first time, this pre-configured list is already built into the second electronic device and can be used directly without manual configuration by the user.

[0073] Once the migration process is started, it can automatically scan all agent tool data in the storage medium, identify each agent tool stored in the storage medium, and read all the data to be migrated corresponding to all agent tools into the memory of the first electronic device in one go.

[0074] The migration program can read the root directory of the storage medium or the preset data storage path, traverse all subdirectories and files, identify the intelligent agent tool data packets one by one according to the preset data format rules (such as file extensions, file header identifiers, etc.), and load all identified data packets into memory.

[0075] This method is suitable for scenarios where users have replaced their terminal devices (i.e., the first electronic device) and wish to completely replicate all the customized intelligent agent tools that have been fully debugged on the source device (i.e., the second electronic device) to the new device. For example, a user may have debugged multiple skills on their old laptop for daily office needs, including an automatic email categorization skill, a meeting minutes generation skill, and a document format conversion workflow. Now, the user has replaced their old laptop with a new one as their primary office device and wants to migrate all the fully debugged customized skills from the old laptop to the new laptop in one go. This eliminates the need for individual selection, making the operation simple and efficient, and ensuring that the new device immediately possesses the same intelligent office capabilities as the old device.

[0076] In this embodiment, the migration program can also parse all the intelligent agent tools identified in the storage medium before reading the data to be migrated, extract the summary information of each intelligent agent tool (such as name, type, creation time, function description, etc.), and display it to the user in the form of a visual list or card.

[0077] Users can browse summary information of each agent tool on the display interface and select one or more target agent tools according to their actual needs. The migration program responds to the user's selection operation by only reading the data to be migrated from the agent tools selected by the user. The data of the unselected agent tools is retained in the storage medium and is not read or migrated.

[0078] This approach is suitable for scenarios where users only need to migrate some of their agent tools to the target device. For example, a user may have already debugged multiple skills on their office computer, but when using a tablet while out and about, they only need to migrate work-related skills (such as email processing and document summarization skills), without needing to migrate entertainment-related skills (such as music recommendation and game assistance skills). This selective migration avoids redundant migration of irrelevant data, saves storage space and migration time, and enhances the flexibility and targeting of the migration operation, meeting users' differentiated migration needs in different scenarios.

[0079] It should be noted that, regardless of which reading method is used, the migration program can verify the integrity of the data after reading it (such as verifying whether the data file is complete or corrupted) to ensure that the read data is complete and usable, thereby ensuring that the intelligent agent tool configured to the first electronic device can operate normally.

[0080] Step S103: Configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0081] If the first electronic device does not yet have an intelligent agent tool corresponding to the data to be migrated, the data to be migrated is directly written into the file of the intelligent agent on the first electronic device, and the creation of the intelligent agent tool is completed from scratch through the data writing action.

[0082] If the first electronic device already has an agent tool corresponding to the data to be migrated, the data to be migrated is directly written into the agent file of the first electronic device. The data writing action overwrites the existing data of the agent tool in the agent file of the first electronic device, thereby completing the update or replacement of the agent tool and making its function consistent with that of the second electronic device.

[0083] Regardless of whether the intelligent agent tool already exists on the first electronic device, after configuration, the intelligent agent on the first electronic device can load the intelligent agent tool from its file, thereby obtaining the same task execution capability or functional expansion capability as the second electronic device.

[0084] In this embodiment, the data to be migrated can be parsed and written to a file of the local intelligent agent of the first electronic device through a management application pre-installed in the first electronic device and corresponding to the storage medium, thus completing the configuration. During the writing process, the management application can automatically perform data format verification and version compatibility checks to ensure that the data to be migrated can be correctly recognized and loaded by the intelligent agent of the first electronic device.

[0085] In this embodiment, the storage medium may also include an adapter program. When the storage medium is connected to the first electronic device, in addition to starting the migration program, the adapter program in the storage medium is started simultaneously. After the migration program reads the data to be migrated from the intelligent agent tool in the storage medium, the adapter program performs format conversion and environment adaptation processing on the data to be migrated, and writes the processed data into the intelligent agent's file in the first electronic device to complete the configuration.

[0086] In this embodiment, a storage medium is used as the data transfer carrier. The entire migration process is completed offline between the device and the storage medium. The data does not need to pass through any network link or cloud server, which eliminates the risk of data leakage of intelligent agent tools caused by attacks on cloud storage, interception of network transmission, or abuse of third-party server privileges. It is especially suitable for secure migration scenarios of intelligent agent tools involving personal privacy, trade secrets, or sensitive business logic. It can realize the secure transfer of intelligent agent tools between devices while ensuring that the data is not connected to the network throughout the process, effectively meeting users' needs for privacy protection and controllable data security during the migration of highly sensitive data.

[0087] Furthermore, based on the physical portability of the storage medium, this solution supports both migration and sharing modes. For example, in personal device switching scenarios, users can connect a storage medium containing well-tested intelligent agent tools to a new device and complete the offline import of all or part of the intelligent agent tools in one go through the migration program, achieving rapid replication of the new device's capabilities without relying on a network environment. In multi-person collaboration or temporary sharing scenarios, the same storage medium can be connected to different electronic devices sequentially, and the intelligent agent tools can be exported from the source device and shared with the target device user, thereby achieving secure transfer and reuse of intelligent agent tools among multiple people. This not only meets the needs of individual users for seamless switching across devices but also adapts to the commercial scenario of rapid distribution of skills and tools in team collaboration. Moreover, since the data is always transferred offline between the storage medium and the device, the sharing process does not create any network exposure surface, further ensuring the security of data during the transmission process.

[0088] As another optional embodiment of this application, refer to Figure 2 This is a flowchart illustrating an agent tool migration method provided in Embodiment 2 of this application. This embodiment is mainly an implementation of step S102 in Embodiment 1, such as... Figure 2 As shown, the specific steps may include, but are not limited to, the following:

[0089] Step S1021: Establish a migration operation entry between the first electronic device and the storage medium through the migration procedure.

[0090] Once the migration process is initiated, a migration operation entry point for data interaction with the storage medium can be generated on the first electronic device. This migration operation entry point can be, but is not limited to, the following forms:

[0091] In the first form, the migration program pops up a separate migration operation window on the desktop of the first electronic device. One side of the window displays summary information (such as name, type, function description, etc.) of all the intelligent agent tools identified in the storage medium in the form of a file list or cards, while the other side displays a list of intelligent agent tools that are already available on the first electronic device. Users can intuitively compare the intelligent agent tools of the source device and the target device in this window.

[0092] For example, such as Figure 3 As shown, assuming a user connects a USB drive containing intelligent agent tools to a newly replaced laptop (i.e., the first electronic device), after the migration program starts, an operation window titled "Skill Migration" pops up on the desktop. The left side of this window displays all the intelligent agent tools already recognized in the USB drive (i.e., one implementation of the storage medium) in card format, specifically including: "Automatic Email Classification Skill" (type: Skill), "Meeting Minutes Generation Skill" (type: Skill), "Document Format Conversion Workflow" (type: Workflow), and "Music Recommendation Skill" (type: Skill). The right side of the window displays the intelligent agent tools already present on the laptop, specifically including: "Schedule Management Skill" (type: Skill) and "Document Summary Skill" (type: Skill).

[0093] The bottom of the window contains an area with operation buttons. On the left side of the window, each agent tool card in the storage medium agent tool section has a checkbox to its left; by default, all agent tools on the USB drive on the left are checked. The right side of the window displays the locally available agent tools.

[0094] Users can manually select or deselect any intelligent agent tool according to their actual needs. For example, Figure 4As shown, users can keep the "Automatic Email Classification Skill", "Meeting Minutes Generation Skill" and "Document Format Conversion Business Flow" checked on the USB drive, while unchecking the "Music Recommendation Skill".

[0095] After the selection is completed, the user clicks the "Start Migration" button at the bottom of the window. The migration program responds to this click operation by reading only the data to be migrated from the smart agent tools selected by the user (i.e., "Automatic Email Classification Skill", "Meeting Minutes Generation Skill" and "Document Format Conversion Business Flow") and writing them sequentially into the smart agent file on the local device of the first electronic device to complete the configuration.

[0096] Through the intuitive comparison and interactive operation of this window, users can quickly grasp the differences between the intelligent agent tools between the source and target devices without having to open each file to view its contents. They can also efficiently complete the migration selection and execution by checking boxes and clicking buttons.

[0097] In the second form, the migration program creates a dedicated migration operation partition in the file manager of the first electronic device. This partition synchronously displays the agent tool data in the storage medium and the agent tool files on the first electronic device, allowing users to complete cross-device data selection and operation in a unified file browsing interface.

[0098] Regardless of the form used, the core function of this migration operation entry is to provide users with a visual and interactive data operation interface, enabling users to browse all the intelligent agent tools in the storage medium before officially reading the data to be migrated, and to decide which intelligent agent tools to migrate and the order of migration according to their own needs, rather than having the migration program automatically read the entire data or only read it based on preset rules.

[0099] Step S1022: In response to the migration command triggered by the user through the migration operation entry, read the migration data of the intelligent agent tool from the storage medium.

[0100] In this embodiment, the way users trigger migration instructions varies depending on the form of the migration operation entry.

[0101] For example, corresponding to the first form of the migration operation entry (i.e., a separate migration operation window that pops up on the desktop), the user can trigger the migration command in, but is not limited to, the following ways:

[0102] Method 1: Select and Trigger. After selecting one or more target intelligent agent tools in the storage media tool list on the left side of the window, the user clicks the "Start Migration" or "Import" button at the bottom of the window to trigger the migration command.

[0103] In response to this instruction, the migration process only reads the migration data of the intelligent agent tools selected by the user, while the data of unselected intelligent agent tools is kept in the storage medium and is not read or migrated.

[0104] Method 2: Drag and Drop Trigger. Users can drag and drop the target agent tool card from the storage medium on the left into the agent tool list area on the first electronic device on the right. The migration program responds to this drag-and-drop operation, reading the data to be migrated from the storage medium and writing it to the agent file on the first electronic device, completing the migration. This drag-and-drop method fully utilizes the advantages of the independent window's left-right split layout, allowing users to intuitively move tools from the source device on the left to the target device on the right, with a clear and natural operation logic.

[0105] For the second type of implementation where the migration operation entry point is a dedicated migration operation partition in the file manager, users can trigger migration commands in, but are not limited to, the following ways:

[0106] Method 1: Select-based Trigger. After selecting one or more target agent tools in the migration operation partition, the user clicks the "Import" button in the partition toolbar to trigger the migration command. The migration program responds to this command by reading only the data to be migrated from the agent tools selected by the user.

[0107] Method 2: Double-click trigger. The user double-clicks a data file of a specific agent tool in the migration operation partition. The migration program responds to this double-click by reading the data to be migrated from the storage medium and writing it to the agent file on the local machine of the first electronic device, completing a single migration. This method is suitable for scenarios where the user knows the name and location of the target agent tool and wants to quickly complete a single migration.

[0108] It should be noted that regardless of which method the user triggers the migration command, the migration program can verify the integrity of the data after reading it (such as verifying whether the data file is complete or corrupted) to ensure that the read data is complete and usable, thereby ensuring that the intelligent agent tool configured to the first electronic device can operate normally.

[0109] In this embodiment, a migration operation entry point is established between the first electronic device and the storage medium through the migration procedure, giving the user the initiative in data reading. The user can fully understand all the intelligent agent tools in the storage medium through the migration operation entry point, and then trigger migration commands as needed, in batches, and in an orderly manner. This is suitable for scenarios where the user has specific requirements for the content to be migrated, or where a phased migration is required. For example, a user may have completed the debugging of more than ten Skills on their office computer, but when using a tablet computer outside, they may want to migrate the three Skills directly related to the day's work first, and then migrate the remaining Skills later if needed. In this embodiment, the migration operation entry point allows for the triggering of migration commands in batches, flexibly controlling the migration pace and scope.

[0110] As another optional embodiment of this application, refer to Figure 5 This is a flowchart illustrating an agent tool migration method provided in Embodiment 3 of this application. Figure 5 As shown, the specific steps may include, but are not limited to, the following:

[0111] Step S201: In response to the storage medium being connected to the first electronic device, a migration program in the storage medium is started on the first electronic device.

[0112] Step S202: Read the data to be migrated of the intelligent agent tool from the storage medium through the migration procedure; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform the first target task.

[0113] For a detailed description of steps S201-S202, please refer to the relevant description of steps S101-S102 in Example 1, which will not be repeated here.

[0114] Step S203: Read the first usage parameter from the storage medium; the first usage parameter is used to identify whether the usage permission of the intelligent agent tool data to be migrated is to be transferred or shared.

[0115] When the second electronic device writes the intelligent agent tool to the storage medium, in addition to writing the data to be migrated for the intelligent agent tool, it can also simultaneously write the first usage parameters.

[0116] The first usage parameter can be set by the user when exporting the intelligent agent tool on the second electronic device. Specifically, when the user operates the management application or file management interface on the second electronic device, selects one or more generated intelligent agent tools and specifies that they should be exported to the storage medium, the management application will pop up an export configuration interface. This interface has a "Usage Permissions" option, through which the user can set the value of the first usage parameter individually for each intelligent agent tool to be exported.

[0117] For example, a user has spent considerable time debugging a "weekly report auto-generation skill" on an old laptop (i.e., a second electronic device). Now, the user has switched to a new laptop (i.e., a first electronic device) and wants to migrate the skill to the new computer for continued use and further modification and optimization. When the user exports the skill from the old computer to a USB flash drive (i.e., one implementation method using storage media), they select "Transfer" in the "Usage Permissions" option of the export configuration interface. At this time, the first usage parameter associated with the skill's data to be migrated is set to "Transfer," indicating that the skill is the user's personal private data. When the USB flash drive is connected to the new computer, the migration program reads that the first usage parameter is "Transfer," and directly writes the skill into the main storage directory of the new computer's intelligent agent tool, managing it as a private configuration on the new computer. The user can then perform complete operations such as editing, modifying, and adjusting parameters on the skill on the new computer.

[0118] For example, User A has completed a "Contract Terms Review Skill" on their work computer (i.e., a second electronic device). This skill contains review rules and prompt templates meticulously configured by User A based on years of legal experience. User A wants to share this skill with team members but does not want them to modify its internal review rules and prompt templates. When exporting this skill to a USB drive, User A selects "Share" in the "Usage Permissions" option of the export configuration interface. At this time, the first usage parameter associated with the data to be migrated for this skill is set to "Shared," indicating that this skill is shared data.

[0119] When the USB drive is connected to the computers of users B and C (i.e., the first electronic device), the migration program reads that the first usage parameter is "shared". Users B and C can call the Skill to perform the contract terms review task normally, but they cannot modify or delete the internal review rules and prompt word templates, thus ensuring the integrity of user A's original configuration and the protection of intellectual property rights.

[0120] For example, a user has already debugged five skills on their office computer. The "Automatic Email Sorting Skill" and "Meeting Minutes Generation Skill" are tools the user uses daily and wants to continue modifying and optimizing after migrating to a tablet. The "Contract Terms Review Skill" and "Competitive Analysis Skill" are shared tools obtained from colleagues and only need to be used temporarily on the tablet; accidental modification is not desired. During export, the user can set the first usage parameter to "Transfer" for "Automatic Email Sorting Skill" and "Meeting Minutes Generation Skill" in the export configuration interface, and set the first usage parameter to "Share" for "Contract Terms Review Skill" and "Competitive Analysis Skill." During subsequent configuration, the migration program will execute corresponding storage strategies based on the different values ​​of the first usage parameter associated with each skill, achieving differentiated processing of data with different permission attributes under the same export operation.

[0121] The first usage parameter can be encoded using a preset data format. For example, the first usage parameter can be stored in a structured format using key-value pairs, such as {usage_right: transfer} or {usage_right: share}. It can also be encoded using an enumerated integer format, such as "0" representing transfer and "1" representing sharing. Alternatively, it can be described using an extended markup language (such as XML or JSON), which carries auxiliary information such as permission type, data source identifier, and export timestamp.

[0122] Using a structured format for the first usage parameter allows the migration program to quickly and accurately identify permission attributes through standardized parsing logic during reading, avoiding misjudgments of permissions due to text ambiguity or inconsistent formats, and ensuring that the same first usage parameter can be processed consistently across different devices and different versions of the migration program.

[0123] Step S204: If the first use parameter identifier is shared, the storage area of ​​the intelligent agent tool of the first electronic device is divided into a first sub-storage area and a second sub-storage area. The first sub-storage area is used to store the private data of the intelligent agent tool of the first electronic device; the private data is used to configure the intelligent agent tool to perform a second target task; the second sub-storage area is used to store the data to be migrated.

[0124] When the migration program recognizes that the value of the first usage parameter is shared, it indicates that the intelligent agent tool to be migrated is shared data rather than the user's personal private data. When configuring the data to be migrated to the first electronic device, the migration program does not directly write it into the main storage directory of the intelligent agent tool of the first electronic device and store it together with the local private data. Instead, it first performs logical partitioning on the local intelligent agent tool storage area of ​​the first electronic device, dividing it into two independent sub-storage areas.

[0125] The first sub-storage area is used to store the private data of the intelligent agent tools locally on the first electronic device. The private data may include intelligent agent tool data that the user of the first electronic device independently creates, debugs, or imports from other channels. The user's access rights belong entirely to the current user of the first electronic device, and the user can perform complete management operations such as creation, editing, modification, deletion, and updating. This type of intelligent agent tool is used to drive the intelligent agent to perform a second target task, which can be any task defined by the user on the first electronic device.

[0126] The second sub-storage area is used to store data to be migrated from the storage medium and identified as shared by the first usage parameter. This second sub-storage area physically shares the same main storage directory for the agent tools as the first sub-storage area, but is logically isolated through independent subdirectory paths. That is, both shared imported agent tools and user-configured agent tools are stored in the main directory of the agent tools, but in different subdirectories.

[0127] Through the aforementioned partitioned and isolated storage mechanism, when the intelligent agent on the first electronic device is running, it can simultaneously identify and load private intelligent agent tools from the first sub-storage area and shared intelligent agent tools from the second sub-storage area. Users can normally call the shared intelligent agent tools to execute their corresponding first target tasks. However, since the data of the shared intelligent agent tools is stored in an independent second sub-storage area, the user's editing, modification, deletion, and other operations on the private data will not affect the shared data, and vice versa. Thus, secure isolation between private configuration and shared configuration is achieved on the same device.

[0128] It should be noted that step S204 is an implementation of step S103 in Embodiment 1. In this embodiment, step S204 further introduces a permission identification and partitioned storage mechanism based on the first usage parameter, on the basis of step S103. Partitioned isolation storage is only performed when the first usage parameter is identified as shared. If the first usage parameter is identified as transferred, the data to be migrated is directly written into the main storage directory of the first electronic device's intelligent agent tool in accordance with the method of step S103 in Embodiment 1, and is managed uniformly as private data without additional partitioning operations.

[0129] In this embodiment, the partitioned isolation storage mechanism based on the first usage parameter allows for the simultaneous use of personal private intelligent agent tools and externally shared intelligent agent tools on the same electronic device. This ensures complete management rights for the user's personal private configuration while preventing accidental modification or deletion of shared data. It is particularly suitable for scenarios where users temporarily use shared intelligent agent tools on their personal devices or where multiple users take turns using the same device in team collaboration while retaining their own private configurations. For example, a user imports a shared "Meeting Minutes Generation Skill" (identified as shared by the first usage parameter) onto their personal laptop via storage media. This Skill is automatically stored in the / Intelligent Agent Tools / Shared Import / subdirectory. The user can call the Skill to generate meeting minutes normally, but cannot modify its internal prompt templates and generation rules. This ensures the data integrity and privacy of the original configuration provider while enjoying the sharing capabilities.

[0130] As another optional embodiment of this application, refer to Figure 6 This is a flowchart illustrating an agent tool migration method provided in Embodiment 4 of this application. Figure 6 As shown, the specific steps may include, but are not limited to, the following:

[0131] Step S301: In response to the storage medium being connected to the first electronic device, the migration program in the storage medium is started on the first electronic device.

[0132] Step S302: Read the data to be migrated of the intelligent agent tool from the storage medium through the migration procedure; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform the first target task.

[0133] Step S303: Read the first usage parameter from the storage medium; the first usage parameter is used to identify whether the usage permission of the intelligent agent tool data to be migrated is to be transferred or shared.

[0134] Step S304: If the first use parameter identifier is shared, the storage area of ​​the intelligent agent tool of the first electronic device is divided into a first sub-storage area and a second sub-storage area. The first sub-storage area is used to store the private data of the intelligent agent tool of the first electronic device; the private data is used to configure the intelligent agent tool to perform a second target task; the second sub-storage area is used to store the data to be migrated.

[0135] For a detailed description of steps S301-S304, please refer to the relevant description of steps S201-S204 in Example 3, which will not be repeated here.

[0136] Step S305: If the first usage parameter identifier is shared, read the second usage parameter from the storage medium.

[0137] When data providers of intelligent agent tools export shared intelligent agent tools to storage media, simply identifying "shared" in the first usage parameter can only achieve storage isolation between shared and private data, but it cannot constrain the actual usage behavior of the shared data after it is imported into the target device. When sharing intelligent agent tools, data providers often have specific control intentions regarding the scope, method, and duration of the tool's use. For example, they may want the recipient to call the tool only a certain number of times, or use it only within a specific period, or allow only read-only access and prohibit modification.

[0138] If the second usage parameters are not written to the storage medium along with the data to be migrated, the target device will not be able to know the data provider's control intentions after the shared intelligent agent tool is imported into the target device. It can only open the tool with the default maximum permissions. This will cause the data provider to completely lose the ability to control the shared intelligent agent tool at the usage level, and its data privacy and configuration integrity will be at risk of being abused.

[0139] Therefore, the second usage parameter can be bound to the data to be migrated and written into the storage medium, so that the data provider's control intent can be transmitted to the target device synchronously with the data. This ensures that when the target device configures the shared intelligent agent tool, it can constrain the usage behavior according to the data provider's preset control intent, thereby ensuring the data provider's controllability over the use of the intelligent agent tool in a shared scenario.

[0140] Step S306: Control the use of the data to be migrated based on the second usage parameters.

[0141] With the first usage parameter already marked as "shared", the intelligent agent tool has been configured in the second sub-storage area of ​​the first electronic device, achieving physical isolation at the storage level from the user's local private data. The user's operations such as modifying or deleting the shared intelligent agent tool are restricted by the storage policy.

[0142] However, storage-level isolation can only prevent shared data from being tampered with, but it cannot restrict users' invocation behavior and methods of using shared intelligent agent tools. Without usage-level control, users can repeatedly invoke the shared intelligent agent tool on the target device without restriction, use the tool beyond the scope expected by the data provider, and even export and share the tool again with third parties. All of these behaviors may exceed the authorized scope of the data provider, resulting in damage to the data provider's interests.

[0143] Therefore, in addition to storage isolation, it is necessary to further control the usage behavior of shared intelligent agent tools based on a second usage parameter. This will enable the usage constraints preset by the data provider to be accurately executed on the target device. In this way, while ensuring the security of shared data storage, the usage behavior of shared data can be further controlled. This ensures that after the data provider shares the intelligent agent tool, it can still effectively constrain its usage method, scope, and duration, thus maximizing the protection of the data provider's control and rights over the shared intelligent agent tool.

[0144] As another optional embodiment of this application, the intelligent agent tool migration method provided in Embodiment 5 of this application is mainly an implementation of the second usage parameter in the above embodiments, and may include, but is not limited to, at least one of the following:

[0145] Maximum allowed number of uses; valid deadline; control parameters for controlling whether secondary distribution is allowed.

[0146] In this embodiment, the maximum allowed number of uses can be used to limit the total number of times the shared agent tool can be invoked on the target device. When exporting the shared agent tool, the data provider can set a maximum number of uses in the "Usage Control" sub-option of the export configuration interface. This maximum number of uses is the value of the second usage parameter.

[0147] For example, User A has completed the debugging of a "competitive analysis skill." This skill requires access to an industry analysis database interface that User A has purchased, but this interface has a daily call limit. User A wants to share this skill with team members but does not want to exhaust the interface quota due to repeated calls. When exporting the skill to a USB drive (i.e., one implementation using storage media), User A sets the maximum number of uses to "50" in the "Usage Control" sub-option of the export configuration interface. When the USB drive is connected to User B's computer, the migration program reads the second usage parameter as "50," thus controlling the number of times the skill can be called.

[0148] In this embodiment, the effective deadline can be used to limit the time range during which the shared agent tool can be used on the target device. When exporting the shared agent tool, the data provider can set an effective deadline in the "Usage Control" sub-option of the export configuration interface, and this effective deadline is the value of the second usage parameter.

[0149] For example, User A has completed the debugging of an "Event Plan Generation Skill," which is only applicable to a limited-time marketing campaign that User A is currently preparing. User A wants to temporarily share this Skill with an intern to assist in generating the event plan, but the Skill will become invalid after the event ends. When exporting the Skill to a USB drive (i.e., an implementation using a storage medium), User A sets the validity period to "7 days" in the "Usage Control" sub-option of the export configuration interface.

[0150] In this embodiment, the control parameter used to control whether secondary distribution is allowed can be used to limit whether the shared agent tool can be exported again by the user of the target device and shared with a third party. When exporting the shared agent tool, the data provider can set the secondary distribution control policy in the "Usage Management" sub-option of the export configuration interface. This control policy is the value of the second usage parameter.

[0151] If the second usage parameter is set to "Allow secondary distribution", the user can export the shared agent tool to other storage media again through the management application on the first electronic device, thus achieving secondary transfer of the tool. If the second usage parameter is set to "Disallow secondary distribution", when the user attempts to export the shared agent tool to other storage media through the management application on the first electronic device, the management application detects that the second usage parameter of the agent tool is "Disallow secondary distribution", automatically blocks the export operation, and may prompt the user "This shared agent tool prohibits secondary forwarding. Please contact the data provider for authorization".

[0152] For example, User A has completed the debugging of a "Customer Profiling Analysis Skill." This skill incorporates a customer classification model that User A has compiled through years of business experience, making it a core business asset. User A wants to share this skill with a specific colleague but does not want that colleague to export and distribute the skill to others. When exporting the skill to a USB drive, User A sets the secondary distribution control parameter to "Disable Forwarding" in the "Usage Control" sub-option of the export configuration interface. When the USB drive (i.e., one implementation of storage media) is connected to User B's computer, the migration program reads the second usage parameter as "Disable Forwarding," thus controlling the secondary distribution of the skill.

[0153] It should be noted that the three second usage parameters mentioned above can be used individually or in combination. For example, the data provider can simultaneously set the maximum number of uses to "30 times", the validity period to "15 days", and prohibit secondary distribution. When configuring the shared agent tool, the migration program will execute the above three control policies simultaneously. If any condition is triggered, the agent tool will be disabled, thereby achieving multi-dimensional and refined control over the use of the shared agent tool.

[0154] In this embodiment, through the specific implementation of the three second usage parameters described above, when sharing intelligent agent tools, the data provider can not only achieve storage isolation between shared data and private data through the first usage parameter, but also impose fine-grained constraints on the frequency of calls, usage duration, and distribution scope of shared data through the second usage parameter. This allows the data provider to effectively constrain the usage method, usage scope, and usage duration of the intelligent agent tools after sharing them, thereby maximizing the protection of the data provider's control and rights over the shared intelligent agent tools.

[0155] As another optional embodiment of this application, the intelligent agent tool migration method provided in Embodiment 6 of this application is mainly an implementation of step S306 in Embodiment 5 above, and may include, but is not limited to, at least one of the following:

[0156] Step S3061: Accumulate the number of times the data to be migrated is called. When the accumulated number of calls reaches the maximum number of uses, the data to be migrated is prohibited from being called.

[0157] When the value of the second usage parameter is the maximum allowed number of uses, the migration program can simultaneously write the maximum number of uses into the configuration information of the intelligent agent tool when configuring the shared intelligent agent tool to the second sub-storage area of ​​the first electronic device, and initialize a call counter with the initial value of the maximum number of uses.

[0158] Subsequently, each time the user invokes the shared agent tool to perform a task on the first electronic device, the management application decrements the invocation counter by 1 in the background. When the invocation counter reaches 0, it indicates that the cumulative number of invocations has reached the maximum number of uses set in the second usage parameter. The management application then automatically disables the shared agent tool and may prompt the user with "The shared agent tool has reached its invocation limit and cannot be used further."

[0159] For example, User A has completed the debugging of a "competitive analysis skill." This skill requires access to an industry analysis database interface that User A has purchased, but this interface has a daily call limit. User A wants to share this skill with team members but doesn't want to exhaust the interface quota due to repeated calls. When exporting the skill to a USB drive (i.e., one implementation using storage media), User A sets the maximum usage count to "50 times" in the "Usage Control" sub-option of the export configuration interface. When the USB drive is connected to User B's computer, each time User B uses the skill to perform a competitive analysis task, the background call counter is decremented by 1. When the cumulative number of calls reaches 50, the skill is automatically disabled, and User B can no longer use it. This ensures the security of User A's database interface quota while achieving fine-grained constraints on the frequency of shared skill usage.

[0160] Step S3062: When the current usage time of the data to be migrated exceeds the deadline, the data to be migrated is prohibited from being accessed.

[0161] When the second usage parameter is a valid deadline, the migration program can simultaneously record the import timestamp of the shared agent tool when configuring it to the second sub-storage area of ​​the first electronic device, and calculate the expiration time based on the validity period carried in the second usage parameter. The management application can continuously monitor the relationship between the current time and the expiration time in the background.

[0162] As long as the current time has not exceeded the expiration time, the user can use the shared intelligent agent tool normally. When the current time has exceeded the expiration time, it means that the usage time of the shared intelligent agent tool has exceeded the validity period set in the second usage parameter. The management application will automatically disable the shared intelligent agent tool and may prompt the user that "the shared intelligent agent tool has exceeded the usage period and cannot be used anymore".

[0163] For example, User A has completed the debugging of an "event plan generation skill," which is only applicable to a limited-time marketing campaign that User A is currently preparing. User A wants to temporarily share this skill with an intern to assist in generating event plans, but the skill will become invalid after the event ends. When exporting the skill to a USB drive (i.e., one implementation of a storage medium), User A sets the validity period to "7 days" in the "Usage Control" sub-option of the export configuration interface. When the USB drive is connected to the intern's tablet, the intern can normally use the skill to generate event plans for 7 days from the import date. From the 8th day onwards, the management application automatically disables the skill and prompts the intern "The shared skill has expired and cannot be used further," thereby ensuring that the skill is only used within the time frame expected by User A and preventing the skill from being abused after the event ends.

[0164] It should be noted that steps S3061 and S3062 can be executed individually or simultaneously. When both are executed simultaneously, the management application maintains a call counter and expiration time monitoring logic in the background. The shared agent tool is disabled if either condition is triggered. For example, the data provider can simultaneously set the maximum number of uses to "30 times" and the validity period to "15 days." Then, regardless of whether the user has called the skill 30 times within 15 days, or whether more than 15 days have passed before reaching 30 calls, the skill will be automatically disabled if either condition is triggered first, thus achieving multi-dimensional control over the use of the shared agent tool.

[0165] Step S3063: According to the control parameters, prevent the data to be migrated from being exported again and distributed to other electronic devices.

[0166] When the value of the second usage parameter is a control parameter used to control whether secondary distribution is allowed and the control parameter indicates "secondary distribution prohibited", the migration program can synchronously write the attribute flag of prohibiting secondary distribution into the configuration information of the intelligent agent tool when configuring the shared intelligent agent tool to the second sub-storage area of ​​the first electronic device.

[0167] Subsequently, when a user attempts to export the shared agent tool to other storage media via a management application on the first electronic device, the management application reads the second usage parameter of the agent tool before performing the export operation. If the value of the second usage parameter is detected as "prohibit secondary distribution," the management application automatically blocks the export operation and prompts the user with "This shared agent tool prohibits secondary forwarding; please contact the data provider for authorization," thereby ensuring that the shared agent tool cannot be exported again by the user of the target device and disseminated to third parties.

[0168] If the value of the second usage parameter is "Allow secondary distribution", the user can export the shared intelligent agent tool to other storage media again through the management application on the first electronic device to realize the secondary transfer of the tool, and the data provider does not restrict this.

[0169] For example, User A has completed the debugging of a "Customer Profiling Analysis Skill." This skill contains a customer classification model that User A has compiled through years of business experience, making it a core business asset. User A wants to share this skill with a specific colleague but does not want that colleague to export and distribute the skill to others. When exporting the skill to a USB drive, User A sets the secondary distribution control parameter to "Disable Forwarding" in the "Usage Control" sub-option of the export configuration interface. When the USB drive (i.e., one implementation of a storage medium) is connected to User B's computer, User B can normally call the skill to perform customer profiling analysis tasks. However, when User B attempts to export the skill to another storage medium, the management application automatically blocks the operation and prompts User B with "This shared intelligent agent tool prohibits secondary forwarding. Please contact the data provider for authorization." This ensures that the skill is only transmitted within the scope authorized by User A, preventing the further dissemination of core business assets.

[0170] It should be noted that step S3063 can be executed independently or in any combination with steps S3061 and S3062. For example, the data provider can simultaneously set the maximum number of uses to "30 times", the validity period to "15 days", and prohibit secondary distribution. When configuring the shared intelligent agent tool, the migration program will execute steps S3061, S3062, and S3063 simultaneously. The intelligent agent tool will be disabled if any condition is triggered, such as exhausting the number of calls, expiring the usage period, or attempting secondary export. This achieves multi-dimensional and refined control over the use of the shared intelligent agent tool, maximizing the protection of the data provider's control and rights over the shared intelligent agent tool.

[0171] As another optional embodiment of this application, refer to Figure 7 This is a flowchart illustrating an agent tool migration method provided in Embodiment 7 of this application. Figure 7 As shown, the method may include, but is not limited to, the following steps:

[0172] Step S401: In response to the storage medium being connected to the first electronic device, the migration program in the storage medium is started on the first electronic device.

[0173] Step S402: Read the data to be migrated of the intelligent agent tool from the storage medium through the migration procedure; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform the first target task.

[0174] Step S403: Configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0175] For a detailed description of step S403, please refer to the relevant description of steps S101-S103 in Example 1, which will not be repeated here.

[0176] Step S404: In response to the first electronic device successfully reading the data to be migrated, a clearing command is generated on the first electronic device.

[0177] In this embodiment, the clear command can be used to instruct the clearing of the data to be migrated that has been read from the storage medium, ensuring that this part of the data is no longer retained in the storage medium.

[0178] The generation of the clear command can be achieved, but is not limited to, through the following two methods:

[0179] The first method involves the first electronic device autonomously controlling the clearing process.

[0180] In this method, after the migration program completes the reading and configuration of the data to be migrated, it automatically generates a clearing command on the first electronic device without requiring any additional user intervention. The timing of this clearing command generation can be set to any of the following nodes:

[0181] Node 1: Once the migration program confirms that all data to be migrated has been completely read into the memory of the first electronic device and the data integrity verification has passed, it immediately generates a clear command.

[0182] Node 2: Once the management application confirms that all data to be migrated has been successfully written to the local smart agent file of the first electronic device and that there are no abnormalities in the configuration process, a clearing command is generated.

[0183] Node 3: When the user clicks the "Complete Migration" or "Confirm Import" button at the migration operation entry point to confirm the completion of this migration operation, a clearing command is generated.

[0184] In this method, the generation of the clearing command is automatically driven by the program logic on the first electronic device side, without the need for manual triggering by the user, making the operation process simple and efficient.

[0185] For example, a user connects a USB drive containing agent tools to a new laptop, selects three skills in the migration operation window, and clicks "Start Migration." The migration program automatically reads the migration data for those three skills and configures them to the new computer. Once the configuration is complete and verification is successful, the migration program automatically generates a cleanup command, requiring no further user intervention.

[0186] The second method involves the user triggering a clear command.

[0187] In this method, after the migration program completes the reading and configuration of the data to be migrated, it can send a prompt message to the user, asking whether to clear the migrated data from the storage medium. The user can choose whether to perform the clearing operation according to their own needs.

[0188] For example, after the migration program is configured, a prompt box will pop up in the migration operation window, displaying "The data to be migrated has been successfully imported into this machine. Do you want to clear the migrated data on the USB drive?", and providing two options: "Yes" and "No". If the user clicks "Yes", a clearing command will be generated; if the user clicks "No", the data to be migrated on the storage medium will be retained, and the clearing operation will not be performed.

[0189] This method is suitable for scenarios where users want to retain the data to be migrated on the storage medium for future migration to other devices. For example, after exporting multiple Skills that they have been debugging to a USB flash drive (i.e., one implementation of the storage medium), user A first connects the USB flash drive to their new computer to complete the migration, but wants to retain the data on the USB flash drive for future migration when connecting it to their office computer. In this case, user A can select "No" in the clearing prompt to retain a copy of the data on the USB flash drive.

[0190] It should be noted that, regardless of which method is used, the clearing command only clears the data to be migrated that has been successfully read and configured to the first electronic device. The clearing command does not affect the intelligent agent tool data that has not been selected or has failed to be read in the storage medium. This part of the data is still retained in the storage medium and can be used for subsequent migration.

[0191] Step S405: The first electronic device sends a clear command to the storage medium to clear the data to be migrated in the storage medium.

[0192] After the clearing command is generated, the first electronic device can send the clearing command to the storage medium through an established data communication channel (such as a USB protocol channel). Upon receiving the clearing command, the storage medium performs the corresponding data deletion operation, completely deleting the successfully migrated data from the storage medium.

[0193] The data deletion operation may include, but is not limited to, the following methods:

[0194] Method 1: Logical Deletion. The storage medium marks the storage area containing the migrated data as "overwhelmable." This data is logically invisible, but physically remains in the storage medium and will only be overwritten when new data is written. This method is fast and suitable for scenarios where timeliness of deletion is not critical.

[0195] Method 2: Physical erasure. The storage medium performs an overwrite operation on the storage area where the migrated data resides, repeatedly overwriting the physical storage unit where the original data is located with random data or fixed values, making the original data physically unrecoverable. This method offers higher security and is suitable for migration scenarios involving highly sensitive data.

[0196] In this embodiment, the clearing instruction may carry identification information of the data to be cleared (such as data file name, data path, data hash value, etc.). After receiving the clearing instruction, the storage medium will only perform the deletion operation on the data to be cleared pointed to by the identification information, and will not accidentally delete other data in the storage medium (such as the storage medium's own system files, other unmigrated intelligent agent tool data, etc.).

[0197] For example, if a user selects the "Automatic Email Sorting Skill" and "Meeting Minutes Generation Skill" in the migration operation window, the migration program will only read and configure the data to be migrated for those two Skills. After the clear command is generated, the identification information carried in the clear command only points to the data files of those two Skills. When the storage medium performs the clear, it only deletes the data of those two Skills, while other data in the storage medium (such as the "Music Recommendation Skill" and system files of the storage medium) remains unaffected.

[0198] In this embodiment, the aforementioned clearing mechanism can automatically or according to user instructions clear the migrated data in the storage medium after the agent tool completes the migration, ensuring that the storage medium no longer retains copies of the migrated agent tool after the migration is complete. For example, this mechanism can be applied to the following scenarios:

[0199] Scenario 1: When a user replaces their old device with a new one, a data erasure mechanism ensures that the agent tool data on the storage medium cannot be accessed by others, protecting the user's data privacy. For example, after a user completes the debugging of multiple skills on their old laptop, they can export them to a USB drive and migrate them to their new computer. After the migration is complete, the data on the USB drive is automatically erased, and even if the USB drive is subsequently lost, it will not lead to the leakage of agent tool data.

[0200] Scenario 2: When a user shares an agent tool with another user, a clearing mechanism ensures that no copy of the agent tool remains on the storage medium, preventing the data provider's agent tool from being further disseminated. For example, if user A shares the "Contract Terms Review Skill" with user B via USB drive, user B's computer will automatically send a clearing command to the USB drive after the migration is complete, erasing the data of the Skill on the USB drive. This ensures that the Skill only exists on user B's computer and will not be further disseminated to others via USB drive.

[0201] Scenario 3: When a user migrates different smart agent tools to multiple devices from the same storage medium, a clearing mechanism ensures that migrated data is not mixed with data to be migrated, preventing the data in the storage medium from becoming increasingly cluttered. For example, a user migrates Skills from a USB drive to a tablet and an office computer in batches. After each batch is completed, the data in that batch is cleared, ensuring that only the data to be migrated is always retained in the storage medium, making the operation logic clear and orderly.

[0202] In this embodiment, the above-mentioned clearing mechanism can promptly clear the migrated data in the storage medium after the intelligent agent tool is successfully migrated to the first electronic device, avoiding the formation of redundant copies of the migrated intelligent agent tool in the storage medium. This reduces the risk of data leakage in the storage medium, maintains the cleanliness and orderliness of the storage medium, and further improves the data security and controllability during the migration process of the intelligent agent tool.

[0203] As another optional embodiment of this application, a smart agent tool migration method provided in embodiment 8 of this application may include, but is not limited to, the following steps:

[0204] Step S501: In response to the storage medium being connected to the first electronic device, the migration program in the storage medium is started on the first electronic device.

[0205] For a detailed description of step S501, please refer to the relevant description of step S101 in Example 1, which will not be repeated here.

[0206] Step S502: The storage medium is authenticated and verified by the first electronic device.

[0207] During the cross-device migration of intelligent agent tools, the first electronic device performs identity authentication and verification on the connected storage medium after starting the migration program and before reading the data to be migrated, in order to prevent intelligent agent tools of unknown origin from being implanted into the first electronic device.

[0208] When the storage medium is connected to the first electronic device, the first electronic device automatically performs identity authentication and verification on the storage medium. The entire process is completed automatically in the background.

[0209] If authentication is successful, proceed to step S503. If authentication fails, the first electronic device refuses to perform subsequent data reading and configuration operations and may prompt the user with "This storage medium is not in the authorized list, and Skill migration operation cannot be performed."

[0210] Step S503: Read the data to be migrated of the intelligent agent tool from the storage medium through the migration procedure; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform the first target task.

[0211] Step S504: Configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0212] For a detailed description of steps S503-S504, please refer to the relevant description of steps S102-S103 in Example 1, which will not be repeated here.

[0213] In this embodiment, by forcibly inserting an identity authentication verification step before data reading, the first electronic device controls the range of storage media to which data can be input from the source, ensuring that only intelligent agent tool data from authorized storage media can be read and configured into the first electronic device. Whether individual users wish to prevent security risks caused by the implantation of intelligent agent tools from unknown sources into their devices, or enterprise users wish to achieve controlled and secure management of the inflow of intelligent agent tools, this identity authentication verification mechanism can provide effective access control, avoiding the possibility of unauthorized storage media inputting data into the first electronic device.

[0214] As another optional embodiment of this application, the intelligent agent tool migration method provided in Embodiment 9 of this application is mainly an implementation of the above-mentioned step S502, and may include, but is not limited to, the following steps:

[0215] Step S5021: Read the hardware identifier from the storage medium; the hardware identifier uniquely identifies the storage medium.

[0216] The first electronic device can read a hardware identifier from the connected storage medium. The hardware identifier is used to uniquely identify the storage medium, such as the storage medium's serial number, device unique identifier (UDID), or a pre-installed digital certificate.

[0217] Step S5022: Match the hardware identifier with the target storage medium identifier bound to the first electronic device.

[0218] The first electronic device can match the read hardware identifier with the locally preset target storage medium identifier, wherein the target storage medium identifier is the identifier of one or more storage media that are pre-stored on the first electronic device and authorized to participate in the intelligent agent tool migration operation.

[0219] If a match is found, authentication is successful, and the storage medium is deemed a legitimate storage medium authorized by the first electronic device. The first electronic device allows the storage medium to participate in the subsequent smart agent tool migration process. If a match is not found, the storage medium is deemed an unauthorized storage medium. The first electronic device rejects the data read request from the storage medium and may prompt the user that "this storage medium is not in the authorized list and cannot perform the Skill migration operation."

[0220] The target storage medium identifier pre-configured locally in the first electronic device can be obtained, but is not limited to, through the following methods:

[0221] The first method involves pre-binding by the user. During routine use of the management application on the first electronic device, the user can proactively bind one or more storage media they wish to use for migrating intelligent agent tools to the first electronic device. The management application reads the hardware identifier of the storage media and writes it into the target storage media identifier list locally on the first electronic device, completing the pre-configuration.

[0222] The second approach involves unified distribution through management policies. Taking an enterprise or organizational scenario as an example, the first electronic device, as a terminal device uniformly distributed by the enterprise or managed by the Enterprise Mobile Device Management (MDM) system, may have intelligent agent tools running on it that involve the enterprise's business processes, internal knowledge base, or sensitive business logic, thus forming part of the enterprise's digital assets. The enterprise IT administrator can configure a hardware identifier whitelist for storage media allowed to access enterprise devices in the MDM management console and push this whitelist to the first electronic device through management policies. Upon receiving the policy, the first electronic device writes the hardware identifiers into its local target storage media identifier list. This method is suitable for security control scenarios where enterprises need to prevent intelligent agent tools from being illegally exported to unauthorized storage media or from being implanted into enterprise devices.

[0223] The third method is factory default settings. When an electronic device leaves the factory, it can be pre-configured with a set of default target storage media identifiers. This default list can be pre-set by the device manufacturer according to the device's usage scenario. For example, it can pre-configure common hardware identifiers for storage media commonly used by other devices in the same product line, or pre-configure standard storage media identifiers officially recommended by the management application.

[0224] In this embodiment, by reading the hardware identifier from the storage medium and matching it with the target storage medium identifier pre-set locally on the first electronic device, accurate identification and strict access control of the accessible storage medium are achieved. The hardware identifier is unique and tamper-proof, ensuring that the identifier information read by the first electronic device is authentic and reliable, and cannot be forged or simulated, thus guaranteeing the accuracy of the identity authentication verification result. Through this method, the first electronic device establishes a security gate based on the hardware identifier before the data reading stage of the intelligent agent tool migration process, fundamentally eliminating the possibility of unauthorized storage media inputting data to the first electronic device. While ensuring the normal migration and flow of the intelligent agent tool, this effectively meets the data inflow security control needs of different user groups.

[0225] The intelligent agent tool migration device provided in this application will be described below. The intelligent agent tool migration device described below can be referred to in correspondence with the intelligent agent tool migration method described above.

[0226] Intelligent agent tool migration apparatus may include:

[0227] A startup module is configured to, in response to the access of a storage medium to a first electronic device, initiate a migration program in the storage medium on the first electronic device.

[0228] The first reading module is used to read the migration data of the intelligent agent tool from the storage medium through the migration program; the intelligent agent tool is generated by the second electronic device in response to the user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform a first target task.

[0229] A configuration module is used to configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0230] In this embodiment, the first reading module can be specifically used for:

[0231] The migration procedure establishes a migration operation entry point between the first electronic device and the storage medium.

[0232] In response to a migration command triggered by the user through the migration operation entry, the migration data of the intelligent agent tool is read from the storage medium.

[0233] In this embodiment, the intelligent agent tool migration device may further include:

[0234] The second reading module is used to read the first usage parameter from the storage medium; the first usage parameter is used to identify whether the usage permission of the intelligent agent tool data to be migrated is transferred or shared.

[0235] The configuration module can be used specifically for:

[0236] If the first parameter identifier is shared, the storage area of ​​the intelligent agent tool of the first electronic device is divided into a first sub-storage area and a second sub-storage area. The first sub-storage area is used to store the private data of the intelligent agent tool of the first electronic device; the private data is used to configure the intelligent agent tool to perform a second target task; the second sub-storage area is used to store the data to be migrated.

[0237] In this embodiment, the intelligent agent tool migration device may further include:

[0238] The third reading module is used to read the second usage parameter from the storage medium if the first usage parameter identifier is shared.

[0239] The management module is used to manage the use of the data to be migrated based on the second usage parameters.

[0240] In this embodiment, the second usage parameter may include at least one of the following:

[0241] Maximum allowed number of uses; valid deadline; control parameters for controlling whether secondary distribution is allowed.

[0242] In this embodiment, the management module controls the use of the data to be migrated based on the second usage parameter, and Jutai Spoken Language includes at least one of the following:

[0243] The number of times the data to be migrated is called is accumulated. When the accumulated number of calls reaches the maximum number of uses, the data to be migrated is prohibited from being called.

[0244] When the current usage time of the data to be migrated exceeds the deadline, the data to be migrated shall not be accessed.

[0245] According to the control parameters, the data to be migrated is prohibited from being exported again and distributed to other electronic devices.

[0246] The intelligent agent tool migration device may further include:

[0247] The generation module is used to generate a clearing command on the first electronic device in response to the first electronic device successfully reading the data to be migrated.

[0248] The sending module is used to send a clearing command from the first electronic device to the storage medium to clear the data to be migrated in the storage medium.

[0249] The intelligent agent tool migration device may also include:

[0250] The authentication module is used to perform identity authentication and verification on the storage medium through the first electronic device.

[0251] If authentication is successful, the migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool.

[0252] The authentication module can be used specifically for:

[0253] Read the hardware identifier from the storage medium; the hardware identifier uniquely identifies the storage medium.

[0254] Match the hardware identifier with the target storage medium identifier bound to the first electronic device;

[0255] If a match is found, the authentication is considered successful.

[0256] In another embodiment of this application, a storage medium is provided, which may include:

[0257] The data to be migrated by the intelligent agent tool; the data to be migrated is generated by the second electronic device in response to the user operation and written into the storage medium; the intelligent agent tool is used to drive the intelligent agent to perform a first target task.

[0258] A migration procedure is used to initiate on the electronic device and enable the first electronic device to read the migration data of the intelligent agent tool from the storage medium.

[0259] In another embodiment of this application, an electronic device is provided, which may include:

[0260] processor;

[0261] Memory;

[0262] Storage media interface, used to connect external storage media;

[0263] The memory stores a computer program, which, when executed by the processor, causes the electronic device to perform the following method steps:

[0264] In response to the access of the storage medium to the first electronic device, a migration program in the storage medium is initiated on the first electronic device;

[0265] The migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool; the intelligent agent tool is generated by the second electronic device in response to user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform a first target task;

[0266] Configure the data to be migrated to the intelligent agent tool of the first electronic device.

[0267] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0268] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0269] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0270] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

Claims

1. A method for transferring intelligent agent tools, comprising: In response to the access of the storage medium to the first electronic device, a migration program in the storage medium is initiated on the first electronic device; The migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool; the intelligent agent tool is generated by the second electronic device in response to user operation and written to the storage medium by the second electronic device; the intelligent agent tool is used to drive the intelligent agent to perform a first target task; Configure the data to be migrated to the intelligent agent tool of the first electronic device.

2. The intelligent agent tool migration method according to claim 1, wherein reading the data to be migrated from the storage medium through the migration program includes: The migration procedure establishes a migration operation entry point between the first electronic device and the storage medium. In response to a migration command triggered by the user through the migration operation entry, the migration data of the intelligent agent tool is read from the storage medium.

3. The agent tool migration method according to claim 1, further comprising: Read the first usage parameters from the storage medium; The first usage parameter is used to identify whether the usage permission of the intelligent agent tool data to be migrated is for transfer or sharing; The intelligent agent tool for configuring the data to be migrated to the first electronic device includes: If the first parameter identifier is shared, the storage area of ​​the intelligent agent tool of the first electronic device is divided into a first sub-storage area and a second sub-storage area. The first sub-storage area is used to store the private data of the intelligent agent tool of the first electronic device; the private data is used to configure the intelligent agent tool to perform a second target task; the second sub-storage area is used to store the data to be migrated.

4. The agent tool migration method according to claim 3, further comprising: If the first usage parameter identifier is shared, read the second usage parameter from the storage medium; The use of the data to be migrated is controlled based on the second usage parameter.

5. The agent tool migration method according to claim 4, wherein the second usage parameter includes at least one of the following: Maximum allowed number of uses; valid deadline; control parameters for controlling whether secondary distribution is allowed.

6. The intelligent agent tool migration method according to claim 5, wherein controlling the use of the data to be migrated based on the second usage parameter includes at least one of the following: The number of times the data to be migrated is called is accumulated. When the accumulated number of calls reaches the maximum number of uses, the data to be migrated is prohibited from being called. When the current usage time of the data to be migrated exceeds the deadline, the data to be migrated shall not be accessed. According to the control parameters, the data to be migrated is prohibited from being exported again and distributed to other electronic devices.

7. The agent tool migration method according to claim 1, further comprising: In response to the first electronic device successfully reading the data to be migrated, a clearing command is generated on the first electronic device; The first electronic device sends a clear command to the storage medium to clear the data to be migrated in the storage medium.

8. The agent tool migration method according to claim 1, further comprising, before reading the agent tool's migration data from the storage medium through the migration program: The first electronic device performs identity authentication and verification on the storage medium. If authentication is successful, the migration procedure reads the data to be migrated from the storage medium for the intelligent agent tool.

9. The data migration method for intelligent agent tools according to claim 8, wherein the first electronic device performs identity authentication verification on the storage medium, comprising: Read the hardware identifier from the storage medium; The hardware identifier uniquely identifies the storage medium; Match the hardware identifier with the target storage medium identifier bound to the first electronic device; If a match is found, the authentication is considered successful.

10. A storage medium, comprising: Data to be migrated from intelligent agent tools; The data to be migrated is generated by the second electronic device in response to the user's operation and written to the storage medium; The intelligent agent tool is used to drive the intelligent agent to perform the first target task; A migration procedure is used to initiate on the electronic device and enable the first electronic device to read the migration data of the intelligent agent tool from the storage medium.

Images