Setting method of robot NFC chip intelligent body

Abstract

The invention provides a method for setting a robot NFC chip agent, and relates to the technical field of robot agent configuration and near field communication, and the method comprises the steps: responding to user selection, and generating an agent parameter configuration package containing a behavior rule, a voice library and task logic; after encrypting the configuration packet by adopting an asymmetric encryption algorithm, writing the configuration packet into the NFC tag in a near field communication mode; and the robot senses and reads encrypted data in the tag through a built-in reader-writer, and loads parameters after decryption verification, so that seamless dynamic switching of the intelligent agents is realized. According to the method and the system, 'touch-and-play 'type intelligent agent switching in a complete offline environment is realized, the problems that in the prior art, operation depends on a network and professional equipment, the configuration process is tedious, security risks exist in data transmission and the like are effectively solved, and the convenience, the security and the individuation degree of use are remarkably improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of robot agent configuration and near field communication technology, in particular to a method for setting a robot NFC chip agent. BACKGROUND

[0002] With the rapid development of artificial intelligence and robot technology, robots are gradually integrated into many fields such as family service, education and entertainment, security inspection, etc. Its core capability is largely determined by its "agent", i.e. the software parameter system that controls its behavior pattern, interaction logic and task execution strategy. At present, there are several mainstream schemes for the configuration of the agent. The most traditional one is the factory preset method, in which the behavior pattern of the robot is fixed in the internal memory when it leaves the factory, and the user cannot adjust it later according to the actual use scene, which greatly limits the applicability and flexibility of the robot.

[0003] To solve this problem, some schemes introduce wired or wireless connection configuration methods, which modify the robot parameters through special software on PC or mobile devices. However, this method has a complicated operation process, usually requires users to have certain professional knowledge, and must rely on specific external devices, which is not user-friendly, and cannot realize quick and convenient mode switching. Another gradually emerging way is cloud synchronization, in which the agent configuration is stored in a remote server, and the robot downloads and updates through the network. This method can realize dynamic configuration to some extent, but it highly depends on stable network environment and cannot be used in poor network or completely offline scenarios. At the same time, uploading a large amount of robot behavior logic and possible user privacy data to the cloud also brings significant data security and privacy leakage risks.

[0004] In summary, the existing technology faces many challenges in realizing flexible, safe and convenient configuration of robot agent, such as complicated operation, dependence on external devices or network, response delay and data security risk, which restricts the popularization of robots and the improvement of user experience. SUMMARY

[0005] In order to solve the technical problems of complicated operation, dependence on network, poor flexibility and security risks in the configuration of robot agent in the prior art, the present application provides a method for setting a robot NFC chip agent.

[0006] The technical scheme provided by the present application is as follows:

[0007] The method for setting a robot NFC chip agent provided by the present application comprises:

[0008] S10: In response to the user's selection of the agent mode, an agent parameter configuration package corresponding to the mode is generated, the agent parameters including behavior rules for controlling the robot behavior mode, a voice interaction library, and task execution logic;

[0009] S20: After the agent parameter configuration package is encrypted, it is written into an NFC tag through near field communication (NFC) mode;

[0010] S30: The robot senses and reads the encrypted configuration package in the NFC tag through its built-in NFC reader / writer, decrypts and verifies the encrypted configuration package, and loads the obtained agent parameters to realize dynamic switching of its robot agent.

[0011] Further, the step S10 specifically includes:

[0012] The behavior rules include dialogue flow control strategies based on interaction protocols, content filtering rules based on ethical constraints, and optional response style settings; the voice interaction library includes timbre parameters, tone and speed parameters, and multi-language support configurations; the task execution logic includes workflow design, decision tree or state machine configuration, and external API integration parameters.

[0013] Further, the step S20 specifically includes:

[0014] S201: The agent parameter configuration package is encrypted using an asymmetric encryption algorithm to generate an encrypted configuration package;

[0015] S202: The encrypted configuration package is written into the NDEF record of the NFC tag through the NFC protocol conforming to the ISO 14443 standard.

[0016] Further, the asymmetric encryption algorithm used in step S201 is the RSA algorithm, and its encryption process includes:

[0017] Convert the agent parameter configuration package to an integer m, where 0≤m<n;

[0018] Calculate the ciphertext: c≡m^e mod n

[0019] Where n is the modulus, which is the product of two large prime numbers p and q, and e is the public key exponent.

[0020] Further, the decryption and verification of the encrypted configuration package in step S30 include:

[0021] S301: Obtain the RSA private key from the robot's local secure storage unit;

[0022] S302: using the private key to perform a decryption operation on the read encrypted configuration package, to restore the original agent parameter configuration package;

[0023] S303: performing an integrity check on the decrypted configuration package, and loading the configuration package to the agent running environment of the robot after the check is passed.

[0024] Further, the decryption operation in the step S302 is:

[0025] Calculate plaintext: m≡c^d mod n

[0026] wherein c is ciphertext, d is a private key index, and n is a modulus.

[0027] Further, in the step S30, the NFC reader / writer of the robot detects the proximity of the NFC tag in a polling manner, and automatically triggers the reading and decryption loading process after sensing the tag.

[0028] Further, before the step S20, the method further comprises:

[0029] providing an agent parameter template library, wherein at least two agent parameter templates for different application scenarios are pre-stored in the library; and wherein the agent parameter configuration package generated in the step S10 is generated based on a template selected from the template library.

[0030] Further, S40: after the agent parameter loading is successful, the type, time and result of the current switching operation are recorded in the security log of the robot.

[0031] Further, the private key is stored in a hardware security module (HSM) built in the robot, and the decryption operation is performed by the hardware security module.

[0032] The technical solution provided by the application has at least the following beneficial effects:

[0033] (1) In the application, the user only needs to select a mode through a mobile terminal and touch an NFC tag to complete the writing, and the robot can instantly load and switch the agent by sensing the same tag, and the entire process is completed offline within a few seconds, completely eliminating the dependence on PC professional software and stable network connection, making the mode switching as simple and convenient as card swiping, greatly improving the user experience and operation efficiency;

[0034] (2) In the application, the configuration package is encrypted by using an asymmetric encryption algorithm, and the decryption key is isolated and protected by a hardware security module, ensuring the confidentiality and integrity of the agent parameters during transmission and loading, effectively preventing the data from being intercepted or tampered with in close-range communication, and providing a solid security guarantee for the personalized setting of the robot;

[0035] (3) In the present application, by pre-setting the intelligent agent parameter template library optimized for different scenes, the user can one-key generate the configuration package of the required mode and write into the label without starting from zero complex configuration, which not only meets the user's individual customization demand for the robot behavior style, but also greatly reduces the technical threshold and time cost of configuration, realizes the unity of efficiency and individualization. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0037] Figure 1 A flowchart of a robot NFC chip intelligent agent setting method provided by the embodiment of the present application is shown in the figure.

[0038] Figure 2 A flowchart of step S20 in the robot NFC chip intelligent agent setting method provided by the embodiment of the present application is shown in the figure.

[0039] Figure 3 A flowchart of decryption and verification of the encrypted configuration package in the robot NFC chip intelligent agent setting method provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0040] The technical solutions in the present application will be described below with reference to the drawings.

[0041] In the embodiments of the present application, the words such as "example", "for example" are used to represent as an example, illustration or description. Any embodiment or design scheme described as "example" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the word "example" is intended to present the concept in a specific way. In addition, in the embodiments of the present application, the meaning expressed by "and / or" can be both, or can be one of the two.

[0042] In the embodiments of the present application, "image" and "picture" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are consistent. "Of", "corresponding" and "corresponding" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are consistent.

[0043] In the embodiments of the present application, sometimes the subscript such as W1 may be mistakenly written in the form of non-subscript such as W1, and when the difference is not emphasized, the meanings expressed are consistent.

[0044] To make the technical problems, technical solutions and advantages to be solved by the present application clearer, the following will be described in detail in conjunction with the drawings and specific embodiments.

[0045] Referring to the accompanying drawings Figure 1 , a flowchart of a setting method of a robot NFC chip agent provided by the embodiments of the present application is shown.

[0046] The embodiments of the present application provide a setting method of a robot NFC chip agent, and the processing flow can include the following steps:

[0047] S10: In response to the selection of an agent mode by a user, an agent parameter configuration package corresponding to the mode is generated, and the agent parameters include behavior rules for controlling the behavior mode of the robot, a voice interaction library and task execution logic.

[0048] In the specific implementation process, this step is usually completed on a mobile terminal or computer configuration tool with a graphical user interface (GUI). The user selects from a plurality of predefined agent modes (for example, "home care", "reception guide", "security inspection", etc.) provided by the interface. Once the user confirms the selection, the configuration tool will call the preset template or automatically generate a structured data package, i.e. the agent parameter configuration package, according to the user's historical settings. The configuration package is essentially a structured data set, which is usually organized in a parsable data format such as JSON, XML or binary, to facilitate subsequent transmission, storage and processing. The generation process includes calling and integrating three types of core parameters from the resource library: behavior rules, voice interaction library and task execution logic, thereby forming a configuration file that defines the personality and ability of the robot for a specific work.

[0049] S20: After the agent parameter configuration package is encrypted, it is written into the NFC tag through near field communication (NFC) mode.

[0050] This step is performed by the same mobile terminal or a dedicated tag writing device. First, the system encrypts the original agent parameter configuration package generated in step S10 to ensure data security. The encryption process uses an asymmetric encryption algorithm to operate on the configuration package data using a pre-generated public key to convert it into ciphertext that cannot be directly read, forming an encrypted configuration package. Subsequently, the device activates its built-in NFC read-write function and establishes a near-field communication connection with a blank or repeatedly readable and writable NFC tag (compliant with ISO 14443 Type A / B standard). After the communication is established, the device encapsulates the encrypted configuration package data into specific NDEF records according to the standard protocol of NFC data exchange format (NDEF), and writes it into the storage area of the NFC tag through the NFC radio frequency field. After completion, the NFC tag becomes a physical carrier carrying encrypted robot identity data.

[0051] S30: The robot senses and reads the encrypted configuration package in the NFC tag through its built-in NFC reader, decrypts and verifies the encrypted configuration package, and loads the obtained agent parameters to realize dynamic switching of its robot agent.

[0052] This step is automatically completed on the robot side. The robot is internally integrated with an NFC reader module that continuously or intermittently emits a radio frequency field to detect whether there is an NFC tag close to it in a polling manner. When the user brings the NFC tag with written data close to the sensing area on the robot, the robot's NFC reader will recognize the tag and automatically establish a communication link. Then, the reader reads all the data from the NDEF record of the tag, i.e., the aforementioned encrypted configuration package. After successful reading, the robot's main control system calls the decryption algorithm and corresponding private key in its security unit to decrypt the encrypted configuration package, restoring it to the original, plaintext agent parameter configuration package. To ensure data integrity and security, the system can verify the decrypted plaintext data. After verification, the robot operating system or runtime environment parses the configuration package and dynamically updates the core configurations of its behavior control engine, speech synthesis module, and task scheduler according to the parameters in the package, thereby realizing seamless switching from the current agent mode to a new mode.

[0053] In one possible implementation, step S10 specifically includes:

[0054] The behavior rules include dialogue flow control strategies based on interaction protocols, content filtering rules based on ethical constraints, and optional response style settings; the voice interaction library includes timbre parameters, tone and speed parameters, and multi-language support configurations; the task execution logic includes workflow design, decision tree or state machine configuration, and external API integration parameters.

[0055] In a specific implementation, the behavior rule, the voice interaction library and the task execution logic include the following details. The behavior rule is defined by a set of machine-readable configuration files, in which the interaction protocol is specifically represented as a finite state machine or a decision tree that defines the dialogue trigger words, response content and multi-round dialogue flow; the ethical constraints are embodied as a data table containing a list of sensitive words and content filtering rules, which are called by the interaction processing module of the robot in real time; the response style controls the characteristics of text generation or voice output through a set of adjustable parameters (such as sentence complexity, sentiment tendency value). The core of the voice interaction library is a series of pre-set Speech Synthesis Markup Language (SSML) scripts and corresponding parameter sets, which customize voice output by adjusting the rules of voice ID, fundamental frequency (intonation), phoneme duration (speech rate) and inserted silence segment (pause); multilingual support is achieved by calling different text-to-speech (TTS) engines and corresponding language packs. The task execution logic usually exists in the form of flowchart or script in the configuration package, for example, a series of sequential, branching or loop execution action instructions (such as "move to point A", "play audio B", "call API C") are defined using JSON format; the decision tree configuration explicitly defines the logic of jumping to different task nodes based on specific sensor input (such as detecting a face); the external API integration parameters include the URL address, request format, authentication key and other information of the target service, enabling the robot to interact with external systems.

[0056] In a possible implementation, as shown in Figure 2 S20 specifically includes:

[0057] S201: encrypt the agent parameter configuration package using an asymmetric encryption algorithm to generate an encrypted configuration package;

[0058] S202: write the encrypted configuration package into the NDEF record of the NFC tag through the NFC protocol conforming to the ISO 14443 standard.

[0059] A preferred implementation of step S20 divides it into two ordered sub - steps. In S201, the encryption process starts with a configuration tool on the mobile terminal. This tool either has the public key required for encryption built - in or obtains it from the server. Using an asymmetric encryption algorithm such as RSA, an encryption operation is performed on the agent parameter configuration package (usually serialized into a byte stream) to be transmitted. After encryption, the originally readable plain - text configuration package is converted into a block of ciphertext data, that is, the encrypted configuration package. Immediately afterwards, in S202, the mobile terminal communicates with the NFC tag through its NFC controller, following the ISO / IEC 14443 Type A standard. The encrypted configuration package is encapsulated in the NDEF (NFC Data Exchange Format) format specified by the NFC Forum, usually created as an NDEF record with a MIME type of application / octet - stream or a custom type. Subsequently, through NFC read - write operations, this NDEF record is written into the user - writable storage area of the NFC tag, completing the transformation of the physical carrier of the data.

[0060] In a possible implementation, the asymmetric encryption algorithm used in step S201 is the RSA algorithm, and its encryption process includes:

[0061] Convert the agent parameter configuration package to an integer m, where 0 ≤ m < n;

[0062] Calculate the ciphertext: c ≡ m^e mod n

[0063] Where n is the modulus, which is the product of two large prime numbers p and q, and e is the public - key exponent.

[0064] The asymmetric encryption algorithm is specifically the RSA algorithm. Its encryption process is implemented mathematically and computationally as follows: First, the agent parameter configuration package (a binary data block) generated in step S10 is converted into an integer m representing the plaintext through an encoding function (such as the encoding method defined in PKCS#1 v1.5), ensuring that this integer satisfies the condition 0 ≤ m < n, where n is the RSA algorithm modulus. Subsequently, the core encryption calculation is performed: c ≡ m^e mod n. Here, c is the ciphertext integer obtained after calculation; e is the public - key exponent pre - selected and paired with the modulus n, and a common value is 65537; n is part of the RSA public key, which is a very large number obtained by multiplying two secret large prime numbers p and q (i.e., n = p * q). Finally, the obtained ciphertext integer c is converted back to binary format and combined with other possible protocol data to form the final encrypted configuration package.

[0065] In a possible implementation, as Figure 3 shown, the decryption and verification of the encrypted configuration package in step S30 includes:

[0066] S301: Obtain the RSA private key from the robot's local secure storage unit;

[0067] S302: Perform decryption operation on the read encrypted configuration package using the private key, and restore the original agent parameter configuration package;

[0068] S303: Perform integrity check on the decrypted configuration package, and load it to the robot's agent running environment after passing the check.

[0069] The decryption and verification process in step S30 can be further divided into three consecutive detailed steps. In S301, after the decryption process is started, the robot's main control processor sends a request to a local secure storage unit (such as a dedicated security chip or TPM module). The secure storage unit securely stores the RSA private key paired with the encryption public key. Access to the private key usually requires permission authentication, and the private key itself is not exposed to the main processor in plaintext form. In S302, after obtaining the private key access permission, the encrypted configuration package (binary ciphertext data) read from the NFC tag is decrypted using the private key. This operation restores the ciphertext data to the binary format of the original agent parameter configuration package before encryption. In S303, the system also performs integrity check on the decrypted data package. A common approach is to attach a hash value (such as SHA-256) to the original data package before encryption, and after decryption, the hash value is recalculated and compared; or verify the digital signature of the encrypted data. Only after passing the check, proving that the data has not been tampered with during transmission and storage, will the configuration package be loaded into the robot's agent running environment.

[0070] In a software implementation, the decryption operation can be performed by a program running on the robot's master system. An exemplary decryption function is implemented as follows: First, import necessary cryptography libraries (e.g. base64, Crypto.PublicKey.RSA, Crypto.Cipher.PKCS1_v1_5). The decryption process starts by reading a PEM-formatted RSA private key file from a specified secure storage path (e.g. 'private.pem') and parsing it into a usable key object using the RSA.import_key() method. Then, use this private key object to create a decrypter (Cipher) object that follows the PKCS#1 v1.5 padding standard. Next, Base64-decode the Base64-encoded encrypted data payload (encrypted_payload) read from the NFC tag to restore it to its original encrypted byte stream (encrypted_bytes). Finally, call the decrypter's decrypt() method with the encrypted byte stream as input to perform the decryption operation. If successful, return the original agent parameter configuration package plaintext data; if not, enter an exception handling process, return an error message, and do not load the configuration, thus ensuring system robustness. In actual industrial deployment, a more secure OAEP padding scheme should be considered, and the private key should be placed in a hardware security module (HSM) rather than in the file system.

[0071] In a more preferred embodiment, to improve security and performance, a hybrid encryption mechanism can be used instead of pure RSA encryption. That is, in step S201, the configuration tool first generates a random symmetric encryption key (e.g. an AES-256 key), uses the symmetric key to encrypt the agent parameter configuration package to obtain ciphertext A; then uses the RSA public key to encrypt the symmetric key to obtain ciphertext B; and the final encrypted configuration package is composed of ciphertext A and ciphertext B. In step S302, the HSM on the robot side first decrypts ciphertext B using the RSA private key to restore the symmetric key, then uses the symmetric key to decrypt ciphertext A to obtain the original configuration package. This method not only takes advantage of the secure key distribution of asymmetric encryption, but also overcomes the performance bottleneck of RSA algorithm that is not suitable for directly encrypting large data blocks, and is particularly suitable for application scenarios where the agent parameter configuration package is large.

[0072] In a possible embodiment, the decryption operation in step S302 is:

[0073] Calculate plaintext: m≡c^d mod n

[0074] where c is the ciphertext, d is the private key exponent, and n is the modulus.

[0075] The calculation is completed inside the security unit. Among them, c is the ciphertext integer parsed from the encryption configuration package; d is a key component of the RSA private key, that is, the private key exponent, which is a large secret integer closely related to the public key exponent e and the modulus n in mathematics; n is the same as the modulus used in encryption. The operation uses the number theory principle to perform power operation on the ciphertext c using the private key exponent d and take the modulus, thereby uniquely recovering the original plaintext integer m. Thereafter, the integer m is converted back to the binary data of the original agent parameter configuration package through the decoding rule (corresponding to the encoding rule during encryption, such as PKCS # 1v1.5 decoding).

[0076] In a possible implementation, in step S30, the NFC reader / writer of the robot detects the proximity of the NFC tag in a polling manner, and automatically triggers the reading and decryption loading process after sensing the tag.

[0077] In the sensing reading phase of step S30 performed by the robot, the built-in NFC reader / writer chip is usually configured in a low-power continuous detection mode. Specifically, the reader / writer actively emits an electromagnetic field (radio frequency field) at a certain periodic interval (for example, several times per second). Once an active or passive NFC tag enters the effective range of the electromagnetic field (usually within a few centimeters), the tag will be activated and communicate with the reader / writer (following the REQA / WUPA wake-up process of ISO 14443A). After the reader / writer detects the response of the tag, it sends an interrupt signal or event notification to the main control system of the robot, thereby automatically triggering the subsequent complete data reading, decryption and parameter loading process, without the need for the user to perform any manual "reading" operation through the robot software interface, realizing the true "one-touch use".

[0078] In a possible implementation, step S20 further includes:

[0079] A library of agent parameter templates is provided, and at least two agent parameter templates for different application scenarios are pre-stored in the library; wherein the agent parameter configuration package generated in step S10 is generated based on the template selected from the template library.

[0080] Before the configuration package is generated in step S10, a high-level preparatory function is provided by the system. In a specific implementation, a library of agent parameter templates is maintained in the configuration tool of the mobile terminal or on an accessible server. The library pre-stores at least two sets of agent parameter templates optimized and configured for completely different application scenarios, such as an "elderly companion mode" template (containing slow speech, medication reminder logic, and emergency call API) and a "child education mode" template (containing cartoon voice, story telling logic, and arithmetic problem generation logic). When the user selects a mode, the user is essentially selecting a target template from the graphically presented template library. The "generation" operation in step S10 is thus not created from scratch, but is instantiated based on the selected template. The template itself can include some adjustable options, but the core parameter structure is pre-defined, greatly simplifying user operations and ensuring configuration quality.

[0081] In a possible implementation, S40: after the agent parameters are successfully loaded, the type, time, and result of the current switching operation are recorded in the security log of the robot.

[0082] After the agent parameters are successfully loaded, the method further includes an additional step S40. This step is performed by the system log service of the robot. Once the parameters are loaded and the new agent is confirmed to be running normally, the system generates a security log record. This record usually includes several key fields: the operation type (such as "NFC agent switching"), the NFC tag ID that triggered this switching (if readable), the timestamp (accurate to milliseconds) when the switching occurred, the loaded agent mode name or ID, and the operation result (such as "success" or "failure" and error code). This log record is then written to a protected, only appendable write area (security log area) of the internal memory of the robot, for subsequent audit, fault diagnosis, and security event tracking.

[0083] To improve the security of the overall scheme, in a specific implementation, multiple security measures need to be considered. The protection of the private key is crucial, and it should be ensured that it is never transmitted over the network, and it is preferentially stored and operated in a hardware security module (HSM), completely avoiding exposure of the private key to the software environment. Before decryption, the encrypted configuration package can be digitally signed to prevent tampering after writing to the tag. At the same time, the NFC reading frequency of the robot should be limited, for example, by setting a minimum reading time interval to prevent replay attacks. After successful decryption and obtaining the plaintext configuration package, the subsequent processing includes: parsing the data structure (such as JSON or XML format) of the configuration package, performing update operations on the device function modules according to the parsed parameters, and recording the type, timestamp, and other key information of the successful switching operation in a protected security log area of the device for audit tracking.

[0084] In a possible implementation, the private key is stored in a hardware security module (HSM) built in the robot, and the decryption operation is performed by the HSM.

[0085] The RSA private key is never stored in any form in the normal file system or memory of the robot, but is pre-injected and permanently stored inside a dedicated hardware security module (HSM). The HSM can be a separate secure chip (such as a smart card chip) or a secure enclave integrated in the processor (such as ARM TrustZone). More importantly, the decryption operation (calculating m≡c^d mod n) is not performed by the host CPU, but is completed inside the HSM. The host CPU only passes the encrypted configuration package (ciphertext c) to the HSM and requests decryption service. After the HSM completes the operation using its hardware-protected private key internally, it only returns the decrypted plaintext data result to the host CPU. This way ensures that the private key cannot be extracted or stolen by software throughout its entire life cycle, greatly improving the overall security of the system.

[0086] The technical scheme provided by the embodiment of the application has at least the following beneficial effects:

[0087] In the application, the user only needs to select the mode through the mobile terminal and touch the NFC tag to complete the writing, and the robot can load and switch the agent instantly by sensing the same tag. The entire process is completed offline in a few seconds, completely breaking the dependence on PC professional software and stable network connection, making the mode switching as simple and convenient as card swiping, greatly improving the user experience and operation efficiency.

[0088] (2) In the application, the configuration package is encrypted by using an asymmetric encryption algorithm, and the decryption key is isolated and protected by a hardware security module, ensuring the confidentiality and integrity of the agent parameters during transmission and loading, effectively preventing data from being intercepted or tampered with in close-range communication, and providing a solid security guarantee for the personalized setting of the robot.

[0089] (3) In the application, by pre-setting an agent parameter template library optimized for different scenarios, the user can one-key generate the configuration package of the required mode and write it into the tag without complex configuration from scratch, which not only meets the user's personalized customization needs for the behavior style of the robot, but also greatly reduces the technical threshold and time cost of configuration, realizing the unity of efficiency and personalization.

[0090] The above merely provides a specific implementation of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0091] The following points need to be explained:

[0092] (1) The attached drawings of the embodiments of the present application only involve the structures involved in the embodiments of the present application, and other structures can refer to the general design.

[0093] (2) In order to be clear, the thickness of the layer or region is enlarged or reduced in the drawings used for describing the embodiments of the present application, that is, the drawings are not drawn according to the actual proportion. It can be understood that when an element such as a layer, a film, a region or a substrate is referred to as being located "on" or "under" another element, the element can be "directly" located on or under another element or there can be an intermediate element.

[0094] (3) In the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other to obtain new embodiments.

[0095] The above merely provides a specific implementation of the present application, but the protection scope of the present application is not limited thereto, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for setting up a robot NFC chip intelligent agent, characterized in that, include: S10: In response to the user's selection of the agent mode, generate an agent parameter configuration package corresponding to the mode, wherein the agent parameters include behavior rules for controlling the robot's behavior mode, a voice interaction library, and task execution logic; S20: After encrypting the intelligent agent parameter configuration package, write it to the NFC tag via near field communication (NFC). S30: The robot senses and reads the encrypted configuration package in the NFC tag through its built-in NFC reader, decrypts and verifies the encrypted configuration package, and loads the obtained intelligent agent parameters to realize the dynamic switching of its robot intelligent agent.

2. The method for setting up a robot NFC chip intelligent agent according to claim 1, characterized in that, Step S10 specifically includes: The behavioral rules include dialogue flow control strategies based on interaction protocols, content filtering rules based on ethical constraints, and optional response style settings; the voice interaction library includes timbre parameters, tone and speed parameters, and multilingual support configuration; the task execution logic includes workflow design, decision tree or state machine configuration, and external API integration parameters.

3. The method for setting up a robot NFC chip intelligent agent according to claim 1, characterized in that, Step S20 specifically includes: S201: The agent parameter configuration package is encrypted using an asymmetric encryption algorithm to generate an encrypted configuration package; S202: Write the encrypted configuration package into the NDEF record of the NFC tag using the NFC protocol conforming to ISO 14443.

4. The method for setting up a robot NFC chip intelligent agent according to claim 3, characterized in that, include: The asymmetric encryption algorithm used in step S201 is the RSA algorithm, and its encryption process includes: Convert the agent parameter configuration package into an integer m, where 0 ≤ m <n; Calculate the ciphertext: c ≡ m^e mod n Where n is the modulus, which is the product of two large prime numbers p and q, and e is the public key exponent.

5. The method for setting up a robot NFC chip intelligent agent according to claim 4, characterized in that, The decryption verification of the encrypted configuration package in step S30 includes: S301: Obtain the RSA private key from the robot's local secure storage unit; S302: Use the private key to decrypt the read encrypted configuration package and restore the original intelligent agent parameter configuration package; S303: Perform integrity verification on the decrypted configuration package. If the verification passes, load it into the robot's intelligent agent operating environment.

6. The method for setting up a robot NFC chip intelligent agent according to claim 5, characterized in that, include: The decryption operation in step S302 is as follows: Calculate plaintext: m ≡ c^d mod n Where c is the ciphertext, d is the private key exponent, and n is the modulus.

7. The method for setting up a robot NFC chip intelligent agent according to claim 1, characterized in that, include: In step S30, the robot's NFC reader detects the proximity of the NFC tag in a polling manner, and automatically triggers the reading and decryption loading process after sensing the tag.

8. The method for setting up a robot NFC chip intelligent agent according to claim 1, characterized in that, The procedure before step S20 also includes: A smart agent parameter template library is provided, wherein at least two smart agent parameter templates for different application scenarios are pre-stored in the library; wherein the smart agent parameter configuration package generated in step S10 is generated based on the template selected from the template library.

9. The method for setting up a robot NFC chip intelligent agent according to claim 1, characterized in that, Also includes: S40: After the agent parameters are successfully loaded, record the type, time and result of this switching operation in the robot's safety log.

10. The method for setting up a robot NFC chip intelligent agent according to claim 5, characterized in that, include: The private key is stored in the robot's built-in hardware security module (HSM), and the decryption operation is performed by this hardware security module.

Images