Label security interaction method and device, storage medium and electronic equipment

Abstract

The invention provides a label security interaction method and device, a storage medium and electronic equipment, and belongs to the technical field of label detection. The method comprises the following steps: in response to an interaction request of a user for a target tag, determining a tag feature associated with the target tag; wherein the tag features comprise tag attribute features and user address features; performing an interaction processing operation indicated by the interaction request on the tag feature to obtain a processing result; and setting the label state of the target label according to the processing result. According to the label security interaction method, the anti-cloning and anti-migration capabilities of the label are remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of label detection technology, and more specifically, to a label security interaction method, apparatus, storage medium, and electronic device. Background Technology

[0002] With the rapid development of IoT technology, Radio Frequency Identification (RFID), as one of the core sensing methods, is widely used in asset tracking, identity authentication, access control, supply chain management and other fields.

[0003] Currently, existing RFID systems typically use the tag's serial number for encrypted writing when performing interactive operations, which is easily tampered with and has a low security level. Summary of the Invention

[0004] To address the aforementioned problems, the present invention aims to provide a tag-based secure interaction method, apparatus, storage medium, and electronic device.

[0005] In a first aspect, embodiments of the present invention provide a tag-based secure interaction method, comprising: In some optional implementations, in response to a user's interaction request for a target tag, the tag features associated with the target tag are determined; wherein, the tag features include tag attribute features and user address features; Perform the interactive processing operation indicated by the interactive request on the label feature to obtain the processing result; Based on the processing result, the tag status of the target tag is set.

[0006] In some optional implementations, determining the tag features associated with the target tag in response to a user's interaction request for the target tag includes: In response to a user's interaction request for a target tag, determine the interaction type of the interaction request; When the interaction type is write type, the tag attribute features and unencrypted user address features associated with the target tag are determined as tag features associated with the target tag; When the interaction type is a modification type or an identification type, the tag attribute features associated with the target tag and the encrypted user address features are determined as the tag features associated with the target tag.

[0007] In some optional implementations, the tag feature further includes an unencrypted product code feature; when the interaction type of the interaction request is write type, the interaction processing operation performed on the tag feature as indicated by the interaction request to obtain the processing result includes: The tag attribute features are input into a preset unique code structure to obtain the unique code of the target tag; Based on the first and second parts of the user address characteristics, construct address encryption information; Based on the product coding characteristics, access password information is constructed, and the unique code, the address encryption information, the address key information, and the access password information are used as the processing result; The step of setting the tag status of the target tag based on the processing result includes: Based on the unique code, the address encryption information, the address key information, and the access password information, the tag status of the target tag is set to write status.

[0008] In some optional implementations, before setting the tag status of the target tag to a write state based on the unique code, the address encryption information, the address key information, and the access password information, the method further includes: Obtain the business data features associated with the target label; Based on the characteristics of the business data, construct business encryption information; The step of setting the tag status of the target tag based on the processing result includes: Based on the unique code, the address encryption information, the address key information, the access password information, and the business encryption information, the tag status of the target tag is set to write status.

[0009] In some optional implementations, the label feature further includes an encrypted product code feature; when the interaction type of the interaction request is a modification type, the interaction processing operation performed on the label feature according to the interaction request indication to obtain a processing result includes: Based on the tag attribute features, determine whether the unique code of the target tag matches the first matching result of the preset tag database; The user address features are decrypted using the user biometric signal input by the user and the address key configured for the target tag to obtain a first address decryption result. The product coding feature is decrypted using the access key configured in the target label to obtain a first coding decryption result. The first matching result, the first address decryption result, and the first coding decryption result are used as the processing result. The step of setting the tag status of the target tag based on the processing result includes: If the first matching result, the first address decryption result, and the first encoding decryption result all indicate that the target tag matches, the tag status of the target tag is set to modified status; If at least one of the first matching result, the first address decryption result, and the first encoding decryption result indicates that the target tag does not match, the tag status of the target tag is set to a rejected modification status.

[0010] In some optional implementations, when the interaction type of the interaction request is an identification type, the step of performing the interaction processing operation on the tag feature according to the interaction request indication to obtain the processing result includes: Based on the tag attribute features, a second matching result is obtained to determine whether the unique code of the target tag matches a preset tag database; The user address features are decrypted using the user biometric signal input by the user and the address key configured for the target tag to obtain a second address decryption result. The step of setting the tag status of the target tag based on the processing result includes: If both the second matching result and the second address decryption result indicate that the target tag matches, the tag status of the target tag is set to the recognition status; If at least one of the second matching result and the second address decryption result indicates that the target tag does not match, the tag status of the target tag is set to a rejection recognition status.

[0011] In some optional implementations, before determining the tag features associated with the target tag in response to a user's interaction request for the target tag, the method further includes: Determine the user's current configured permissions; Based on the current configured permissions, determine whether the interaction request corresponds to a restricted interaction type; If the interaction request corresponds to a restricted interaction type, a prompt message indicating that the interaction is refused is sent to the user.

[0012] Secondly, embodiments of the present invention also provide a tag security interaction device, comprising: A response module is used to respond to a user's interaction request for a target tag and determine the tag features associated with the target tag; wherein, the tag features include tag attribute features and user address features; The module is used to perform interactive processing operations on the tag features according to the interactive request indication, and obtain the processing result; The setting module is used to set the tag status of the target tag based on the processing result.

[0013] Thirdly, embodiments of the present invention also provide a computer storage medium storing computer-executable instructions for use in any of the above-described tag security interaction methods.

[0014] Fourthly, embodiments of the present invention also provide an electronic device, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform any of the tag security interaction methods described above.

[0015] In the solution provided by the first aspect of the present invention, when a user issues an interaction request for a target tag, the tag attribute features and user address features of the target tag are determined. When the interaction request is to write, the target tag can be encrypted and encrypted content can be written using the tag attribute features and user address features. When the interaction request is to modify, the target tag can be decrypted and the content stored in the target tag can be modified using the tag attribute features and user address features. Alternatively, when the interaction request is to identify, the target tag can be decrypted and the content stored in the target tag can be identified using the tag attribute features and user address features. This makes the tag difficult to tamper with and effectively improves its security level.

[0016] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

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

[0018] Figure 1 A flowchart of a tag-based secure interaction method provided by an embodiment of the present invention is shown; Figure 2 This diagram illustrates the structure of a tag security interaction device provided in an embodiment of the present invention. Figure 3 A schematic diagram of the structure of an electronic device for performing a tag-based secure interaction method is shown in an embodiment of the present invention. Detailed Implementation

[0019] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," and "counterclockwise," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0020] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0021] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0022] This invention provides a tag-based secure interaction method, see [link to relevant documentation]. Figure 1 As shown, the execution subject of this method can be a user's client, which can be the user's RFID reader / writer. The method includes: Step 101: In response to the user's interaction request for the target tag, determine the tag features associated with the target tag; wherein, the tag features include tag attribute features and user address features.

[0023] In this embodiment, the interaction request can have different interaction types, such as write, modify, and identify. The user identifies a tag through the client and inputs the content to be written for that tag into the client. That is, the client responds to the user's write-type interaction request by extracting the tag attribute features and user address features of the written content. The tag attribute features here can be a factory-issued unique identifier, and the user address features can include application identifiers, user environment identifiers, and business data.

[0024] In this embodiment, the user identifies a tag through the client, instructs the user to modify the tag, and inputs the modified content of the tag into the client. That is, the client responds to the user's modification-type interaction request by extracting the tag attribute features and user address features of the modified content. The tag attribute features here can be a factory-issued unique code, and the user address features can include application code encryption and user environment identifier encryption.

[0025] In this embodiment, the user identifies a tag through the client and instructs the client to identify the stored content of the tag. Specifically, the client responds to the user's interaction request for identification by extracting the tag attribute features and user address features of the stored content. The tag attribute features can be a factory-issued unique identifier, and the user address features can include encrypted application code and encrypted user environment identifiers.

[0026] Specifically, step 101 above, "in response to the user's interaction request for the target tag, determine the tag features associated with the target tag", includes steps A1 to A3.

[0027] Step A1: In response to the user's interaction request for the target tag, determine the interaction type of the interaction request.

[0028] In this embodiment, when a user scans the target tag and sends written content via the client, the client can determine that the interaction type of the interaction request is a write type. When a user scans the target tag and sends modified content via the client, the client can determine that the interaction type of the interaction request is a modify type. When a user scans the target tag and sends an instruction requiring identification via the client, the client can determine that the interaction type of the interaction request is an identification type.

[0029] Step A2: When the interaction type is write type, determine the tag attribute features and unencrypted user address features associated with the target tag, and use them as the tag features associated with the target tag.

[0030] In this embodiment, the tag attribute feature associated with the target tag is the factory-issued unique code for legitimacy, and the unencrypted user address feature may include application identifier, user environment identifier, and business data.

[0031] Step A3: When the interaction type is modification or identification, determine the tag attribute features and encrypted user address features associated with the target tag, and use them as the tag features associated with the target tag.

[0032] In this embodiment, the tag attribute feature associated with the target tag is the factory-issued unique code for legitimacy, and the encrypted user address feature may include application code ciphertext and user environment identifier ciphertext.

[0033] In this embodiment, by distinguishing the interaction type of the interaction request, it is determined whether the user address feature of the target tag is encrypted, so that the client can determine the user's interaction intent for the target tag and quickly decrypt the encrypted user address feature.

[0034] Step 102: Perform interactive processing operations on the tag features to indicate interactive requests, and obtain the processing results.

[0035] In this embodiment, different interaction types correspond to different interaction processing operations. These interaction processing operations may include decrypting or encrypting tag attribute features and user address features in accordance with the corresponding interaction type to obtain the processing result.

[0036] Step 103: Based on the processing results, set the tag status of the target tag.

[0037] In this embodiment, the tag state of a tag can include a write state, a write-reject state, a modify state, a modify-reject state, an identification state, and an identification-reject state. In the write state, the target tag indicates that the client will store the written content into the target tag; in the write-reject state, the target tag indicates that the client cannot write the written content into the target tag. In the modify state, the target tag's stored content is updated to the modified content; in the modify-reject state, the target tag's stored content is not updated to the modified content. In the identification state, the target tag's stored content can be identified by the client; in the identification-reject state, the target tag's stored content cannot be identified by the client.

[0038] Optionally, the label features also include unencrypted product code features; when the interaction type of the interaction request is write type, the above step 102 "performs the interaction processing operation of the label features as indicated by the interaction request, and obtains the processing result" includes steps B1 to B3.

[0039] Step B1: Input the tag attribute features into the preset unique code structure to obtain the unique code of the target tag.

[0040] In this embodiment, the unique code structure is a factory-issued legality unique code structure, which can be: tag type (2 bytes), serial number (10 bytes), and SM3 hash checksum (4 bytes). This unique code is written to the EPC storage area of ​​the target tag. Simultaneously, this unique code is registered in the tag database of the server's backend system, i.e., the whitelist database, for subsequent legality comparison. Target tags not in the whitelist or listed in the blacklist will be rejected from being written.

[0041] Step B2: Construct address encryption information based on the first and second parts of the user address characteristics.

[0042] In this embodiment, the first feature can be an application identifier feature. Based on this application identifier feature, an application identifier is constructed. The structure of the application identifier is as follows: an application ID (4 bytes) that can be read and written by the RFID reader, a valid start timestamp (6 bytes), a valid end timestamp (6 bytes), an access level (1 byte), and an SM3 checksum (4 bytes). The AAC is encrypted using the SM4 algorithm (CBC mode). The encryption key is dynamically generated by hashing the RFID reader's unit ID, the current timestamp, and the RFID tag's TID using SM3. The TID is added to the input when calculating the SM3 checksum, i.e., SM3(Application ID||Start Timestamp||End Timestamp||Access Level||TID). The encrypted AAC ciphertext is written into the application identifier area of ​​the target tag. This prevents the tag from being misused across applications.

[0043] In this embodiment, the second feature can be an environmental fingerprint identifier, which can be collected by a domestically developed terminal associated with the client. This terminal extracts the client's unique CPU ID, operating system installation fingerprint (SM3 hash), BIOS version, and motherboard model, combines them into an environmental data block, and calculates its SM3 hash value to form the environmental fingerprint. When calculating the environmental fingerprint, the RFID tag TID is added as input, i.e., SM3 (Environmental Data Block || RFID Tag TID). Using the SM4 device key built into the domestically developed terminal, the environmental fingerprint is encrypted in CTR mode. The encrypted plaintext input is the environmental fingerprint || RFID tag TID, and the encrypted environmental identifier is written to a designated area of ​​the tag.

[0044] Step B3: Based on the product coding characteristics, construct the access password information and use the unique code, address encryption information, address key information, and access password information as the processing result.

[0045] In this embodiment, an access password for the EPC area is set based on the unencrypted product coding characteristics (to prevent unauthorized tampering). The plaintext password is encrypted using the SM4 algorithm, and the encryption key is obtained by hashing the unit ID, timestamp, random number, and RFID tag TID using SM3. The encrypted password is stored in a secure area or backend system. Furthermore, if more than 5 consecutive failed attempts are made, the system automatically locks for 30 minutes to enhance resistance to brute-force attacks. During verification, the key needs to be reconstructed based on the current TID and compared. Here, the AAC ciphertext, environment identifier ciphertext, and EPC area access password constitute the constructed address encryption information.

[0046] Based on this, step 103 above, "set the tag status of the target tag according to the processing result", can be: Step B4: set the tag status of the target tag to write status according to the unique code, address encryption information, address key information and access password information.

[0047] In this embodiment, the AAC ciphertext, environment identifier ciphertext, and EPC area access password are written to the target tag to set the tag status of the target tag to the write state.

[0048] Optionally, before step B4 "sets the tag status of the target tag to write status based on the unique code, address encryption information, address key information and access password information", the method further includes steps C1 and C2.

[0049] Step C1: Obtain the business data features associated with the target label.

[0050] In this embodiment, the business data features include business data fields (total length ≥ 96 bytes), wherein the business data fields include unit code (16 bytes), department code (16 bytes), responsible person ID (16 bytes), type (8 bytes), serial number (24 bytes), and verification code (8 bytes).

[0051] Step C2: Construct encrypted business information based on the characteristics of the business data.

[0052] In this embodiment, the encryption process for business data features employs a two-layer encapsulation: the business data is encrypted using SM4 (CBC mode) to obtain ciphertext C1; the session key K_data is generated by hashing the unit information, timestamp, and RFID tag TID using SM3, and then encrypted using the SM2 public key algorithm to encapsulate K_data||RFID tag TID, resulting in ciphertext C2. When calculating the checksum of the business data, the TID is added to the input, i.e., SM3 (the first 88 bytes of business data||TID). Ciphertext C1||ciphertext C2 is concatenated to obtain concatenated ciphertext, which is then written into the user data area of ​​the target tag to achieve two-layer encryption protection.

[0053] Based on this, step 103 above, "set the tag status of the target tag according to the processing result", can be: Step C3: set the tag status of the target tag to write status according to the unique code, address encryption information, address key information, access password information and business encryption information.

[0054] In this embodiment, the AAC ciphertext, environment identifier ciphertext, EPC area access password, and concatenated ciphertext are written to the target tag to set the tag status of the target tag to the write state.

[0055] In this embodiment, the business data adopts a two-layer encapsulation structure (C1||C2) of "SM4 encrypted data + SM2 encrypted session key". This achieves separate protection for data confidentiality and secure key transmission, supporting centralized key management and flexible updates. Combining the advantages of symmetric and asymmetric encryption, it meets the requirements of high-security scenarios while ensuring performance.

[0056] In this embodiment, by processing tag attribute features, user address features, and product code features, the triple binding of physical tags, application permissions, and operating environment is integrated into the interactive operation of secure tag writing, which significantly improves anti-cloning and anti-migration capabilities.

[0057] Optionally, the label features also include encrypted product code features; when the interaction type of the interaction request is modification type, the above step 102 "performs the interaction processing operation of the label features in accordance with the interaction request and obtains the processing result" includes steps D1 to D3.

[0058] Step D1: Based on the tag attribute features, determine whether the unique code of the target tag matches the first matching result in the preset tag database.

[0059] Step D2: Using the user's biometric signal input by the user and the address key configured in the target tag, the user address features are decrypted to obtain the first address decryption result.

[0060] Step D3: Decrypt the product coding features using the access key configured in the target label to obtain the first coding decryption result. Use the first matching result, the first address decryption result, and the first coding decryption result as the processing result.

[0061] Based on this, step 103 above, "setting the tag status of the target tag according to the processing result," includes steps D4 and D5: Step D4: If the first matching result, the first address decryption result, and the first encoding decryption result all indicate that the target tag matches, set the tag status of the target tag to the modified state.

[0062] Step D5: If at least one of the first matching result, the first address decryption result, and the first encoding decryption result indicates that the target tag does not match, set the tag status of the target tag to the "reject modification" status.

[0063] In this embodiment, the tag attribute feature of the target tag is the factory-unique code in the tag EPC area of ​​the target tag. This code is compared with the background whitelist database; if the tag is not registered or is in the blacklist, the modification request is rejected.

[0064] In this embodiment, the application code ciphertext in the target tag is decrypted and parsed (using a key generated by hashing the unit ID, current timestamp, and TID using SM3). Verification is performed: whether the current time is within the validity period, whether the permission level allows the modification operation, and whether the application ID matches the current system. When verifying the internal SM3 code of the AAC after decryption, the input includes the TID, i.e., SM3(Application ID||Start Timestamp||End Timestamp||Permission Level||RFID Tag TID). If it does not conform, the modification is rejected.

[0065] In this embodiment, the current environmental characteristics are re-collected on the client initiating the modification to generate a new environmental fingerprint (SM3 (New Environmental Data Block || RFID Tag TID)). The environmental identifier ciphertext stored in the target tag is decrypted (using the terminal SM4 device key) to obtain the original environmental fingerprint and corresponding TID information. The old and new environmental fingerprints are compared for consistency: if they are inconsistent, it is determined that the device has been migrated or that the terminal is unauthorized, and the modification is rejected.

[0066] In this embodiment, if modifications to the EPC area content are required (such as changing the serial number), a correct encrypted password must be provided. A key is generated using SM3 hashing of the unit ID, timestamp, random number, and current tag TID. The password is then decrypted to verify permissions. A failure count limit is supported (locked for 30 minutes after 5 failures), and the count is independently statistically analyzed based on the RFID tag TID dimension to prevent brute-force attacks.

[0067] In this embodiment, by processing tag attribute features, user address features, and product code features, the triple binding of physical tags, application permissions, and operating environment is integrated into the interactive operation of tag security modification, which significantly improves anti-cloning and anti-migration capabilities.

[0068] Optionally, when the interaction type of the interaction request is an identification type, the above step 102 "performs an interaction processing operation on the tag feature to indicate the interaction request and obtains the processing result" includes steps E1 and E2.

[0069] Step E1: Based on the tag attribute features, determine whether the unique code of the target tag matches the second matching result of the preset tag database.

[0070] Step E2: Using the user biosignal input by the user and the address key configured in the target tag, the user address feature is decrypted to obtain the second address decryption result.

[0071] Based on this, step 103 above, "setting the tag status of the target tag according to the processing result," includes steps E4 and E5: Step E4: If both the second matching result and the second address decryption result indicate that the target tag matches, set the tag status of the target tag to the recognition status.

[0072] Step E5: If at least one of the second matching results and the second address decryption result indicates that the target label does not match, set the label status of the target label to the rejection state.

[0073] In this embodiment, the tag attribute feature of the target tag is the factory-unique code in the tag EPC area of ​​the target tag. This code is compared with the background whitelist database; if it is not registered or is in the blacklist, it is rejected for identification.

[0074] In this embodiment, the application code ciphertext in the tag is decrypted and parsed (using the current unit ID and timestamp to generate a key). Verification is performed: whether the current time is within the validity period, whether the permission level allows execution, and whether the application ID matches the current system; if they do not match, identification is rejected. Current environmental characteristics are re-collected on the terminal initiating identification to generate a new environmental fingerprint. It is then determined whether the device is of the same type; if not, identification is rejected.

[0075] In this embodiment, by processing the tag attribute features, user address features, and product code features, the physical tag, application permissions, and operating environment are triple-bound and integrated into the interactive operation of tag security identification, which significantly improves the anti-cloning and anti-migration capabilities.

[0076] Optionally, prior to step 101 above, the method further includes steps F1 to F3: Step F1: Determine the user's current configuration permissions.

[0077] In some examples, the user's client is configured with corresponding permission levels; for example, user A has permission level 1 and user B has permission level 2.

[0078] Step F2: Based on the current configured permissions, determine whether the interaction request corresponds to the restricted interaction type.

[0079] Continuing with the example above, the interaction types corresponding to permission level 1 are write, modify, and identify, while the interaction type corresponding to permission level 2 is identify. If user B's interaction request is a modify type, the target tag cannot be modified by user B.

[0080] Step F3: If the interaction request corresponds to a restricted interaction type, send a message to the user indicating that the interaction is refused.

[0081] In this embodiment, by setting corresponding permission levels for different users' clients, the flexibility of different users having different interactive operation permissions is adjusted.

[0082] In this embodiment, a unique legal identifier consisting of the tag type, serial number and SM3 check code can be written into the EPC area through factory unique code whitelist verification, and compared with the background whitelist database to realize access control of tag identity.

[0083] In this embodiment, application code encryption binding and access control are implemented. The application code contains information such as application ID, validity period, and permission level. After being encrypted with SM4, it is written into the tag to prevent the tag from being illegally reused across applications.

[0084] In this embodiment, terminal environment fingerprint binding is used to prevent migration. Hardware and system characteristics are collected on the domestically developed terminal to generate an environment fingerprint, which is then encrypted and written to the tag. When reading, a consistency comparison is performed to prevent the tag from being used on unauthorized devices.

[0085] In this embodiment, all encryption operations adopt the national commercial cryptography standards (SM2 / SM3 / SM4): SM3 is used for data integrity verification and key derivation, SM4 (CBC / CTR mode) is used for encryption of application code, business data, and environmental fingerprints, and SM2 is used for encrypted encapsulation of session keys to achieve secure key distribution. Key keys (such as the SM4 encryption key and K_data) are generated by hashing using dynamic parameters such as unit ID, timestamp, and random number, achieving key dynamism and avoiding the risk of static key leakage. This effectively implements a collaborative encryption mechanism based on national cryptographic algorithms with dynamic context parameters, improving the overall anti-cracking capability of the system.

[0086] This invention provides a secure tag interaction method. When a user issues an interaction request for a target tag, the method determines the tag attribute features and user address features of the target tag. If the interaction request is for writing, the method encrypts the target tag and writes encrypted content using the tag attribute features and user address features. If the interaction request is for modification, the method decrypts the target tag and modifies its stored content using the tag attribute features and user address features. Alternatively, if the interaction request is for identification, the method decrypts the target tag and identifies its stored content using the tag attribute features and user address features. This method is difficult to tamper with and effectively improves the security of the tag.

[0087] The above details the process of tag security interaction. This method can also be implemented using a corresponding device, the structure and function of which will be described in detail below.

[0088] Based on the same inventive concept, embodiments of the present invention also provide a tag security interaction device, see [link to relevant documentation]. Figure 2 As shown, the device includes: The response module 210 is used to respond to the user's interaction request for the target tag and determine the tag features associated with the target tag; wherein, the tag features include tag attribute features and user address features; Module 220 is used to perform interactive processing operations on the tag features to indicate interactive requests, and to obtain the processing results. The setting module 230 is used to set the tag status of the target tag based on the processing result.

[0089] In some optional implementations, the response module 210 is further configured to respond to a user's interaction request for a target tag and determine the interaction type of the interaction request; if the interaction type is a write type, determine the tag attribute features associated with the target tag and the unencrypted user address features as the tag features associated with the target tag; if the interaction type is a modification type or an identification type, determine the tag attribute features associated with the target tag and the encrypted user address features as the tag features associated with the target tag.

[0090] In some optional implementations, the obtaining module 220 is further configured to input the tag attribute features into a preset unique code structure to obtain the unique code of the target tag; construct address encryption information based on the first part and the second part of the user address features; construct access password information based on the product coding features, and use the unique code, address encryption information, address key information and access password information as the processing results.

[0091] The setting module 230 is also used to set the tag status of the target tag to the write state based on the unique code, address encryption information, address key information and access password information.

[0092] In some optional implementations, the device further includes an information acquisition module for acquiring business data characteristics associated with the target tag and constructing business encryption information based on the business data characteristics.

[0093] The setting module 230 is also used to set the tag status of the target tag to the write state based on the unique code, address encryption information, address key information, access password information and business encryption information.

[0094] In some optional implementations, the obtaining module 220 is further configured to obtain whether the unique code of the target tag matches a first matching result in a preset tag database through tag attribute features; to decrypt the user address features using the user biometric signal input by the user and the address key configured for the target tag, thereby obtaining a first address decryption result; to decrypt the product coding features using the access key configured for the target tag, thereby obtaining a first coding decryption result; and to use the first matching result, the first address decryption result, and the first coding decryption result as the processing result.

[0095] The setting module 230 is also used to set the tag status of the target tag to a modified state when the first matching result, the first address decryption result, and the first encoding decryption result all indicate that the target tag matches; and to set the tag status of the target tag to a rejected modification state when at least one of the first matching result, the first address decryption result, and the first encoding decryption result indicates that the target tag does not match.

[0096] In some optional implementations, the obtaining module 220 is further configured to obtain whether the unique code of the target tag matches a second matching result in a preset tag database through tag attribute features; and to decrypt the user address features using the user biometric signal input by the user and the address key configured for the target tag to obtain a second address decryption result.

[0097] The setting module 230 is also used to set the tag status of the target tag to the recognition status when both the second matching result and the second address decryption result indicate that the target tag matches; and to set the tag status of the target tag to the rejection recognition status when at least one of the second matching result and the second address decryption result indicates that the target tag does not match.

[0098] In some optional implementations, the device further includes a configuration module for determining the user's current configuration permissions; determining, based on the current configuration permissions, whether the interaction request corresponds to a restricted interaction type; and sending a prompt message to the user indicating that the interaction is refused if the interaction request corresponds to a restricted interaction type.

[0099] This invention also provides a computer storage medium storing computer-executable instructions, including a program for performing the above-described tag security interaction method, wherein the computer-executable instructions can execute the method in any of the above-described method embodiments.

[0100] The computer storage medium can be any available medium or data storage device that a computer can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical storage (e.g., CD, DVD, BD, HVD), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0101] Figure 3 A structural block diagram of an electronic device according to another embodiment of the present invention is shown. The electronic device 1100 may be a host server with computing capabilities, a personal computer (PC), or a portable computer or terminal, etc. The specific embodiments of the present invention do not limit the specific implementation of the electronic device.

[0102] The electronic device 1100 includes at least one processor 1110, a communications interface 1120, a memory array 1130, and a bus 1140. The processor 1110, the communications interface 1120, and the memory 1130 communicate with each other via the bus 1140.

[0103] The communication interface 1120 is used to communicate with network elements, including, for example, virtual machine management centers and shared storage.

[0104] Processor 1110 is used to execute programs. Processor 1110 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0105] Memory 1130 is used for executable instructions. Memory 1130 may include high-speed RAM memory and may also include non-volatile memory, such as at least one disk storage device. Memory 1130 may also be a memory array. Memory 1130 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules. The instructions stored in memory 1130 can be executed by processor 1110 to enable processor 1110 to execute the tag-secure interaction method in any of the above method embodiments.

[0106] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A tag-based secure interaction method, characterized in that, include: In response to a user's interaction request for a target tag, the tag features associated with the target tag are determined; wherein, the tag features include tag attribute features and user address features; Perform the interactive processing operation indicated by the interactive request on the label feature to obtain the processing result; Based on the processing result, the tag status of the target tag is set.

2. The method according to claim 1, characterized in that, The step of determining the tag features associated with the target tag in response to a user's interaction request for the target tag includes: In response to a user's interaction request for a target tag, determine the interaction type of the interaction request; When the interaction type is write type, the tag attribute features and unencrypted user address features associated with the target tag are determined as tag features associated with the target tag; When the interaction type is a modification type or an identification type, the tag attribute features associated with the target tag and the encrypted user address features are determined as the tag features associated with the target tag.

3. The method according to claim 1 or 2, characterized in that, The tag feature also includes an unencrypted product code feature; when the interaction type of the interaction request is write type, the interaction processing operation indicated by the interaction request on the tag feature to obtain the processing result includes: The tag attribute features are input into a preset unique code structure to obtain the unique code of the target tag; Based on the first and second parts of the user address characteristics, construct address encryption information; Based on the product coding characteristics, access password information is constructed, and the unique code, the address encryption information, the address key information, and the access password information are used as the processing result; The step of setting the tag status of the target tag based on the processing result includes: Based on the unique code, the address encryption information, the address key information, and the access password information, the tag status of the target tag is set to write status.

4. The method according to claim 3, characterized in that, Before setting the tag status of the target tag to the write state based on the unique code, the address encryption information, the address key information, and the access password information, the method further includes: Obtain the business data features associated with the target label; Based on the characteristics of the business data, construct business encryption information; The step of setting the tag status of the target tag based on the processing result includes: Based on the unique code, the address encryption information, the address key information, the access password information, and the business encryption information, the tag status of the target tag is set to write status.

5. The method according to claim 1 or 2, characterized in that, The label feature also includes an encrypted product code feature; when the interaction type of the interaction request is a modification type, the interaction processing operation indicated by the interaction request on the label feature to obtain the processing result includes: Based on the tag attribute features, determine whether the unique code of the target tag matches the first matching result of the preset tag database; The user address features are decrypted using the user biometric signal input by the user and the address key configured for the target tag to obtain a first address decryption result. The product coding feature is decrypted using the access key configured in the target label to obtain a first coding decryption result. The first matching result, the first address decryption result, and the first coding decryption result are used as the processing result. The step of setting the tag status of the target tag based on the processing result includes: If the first matching result, the first address decryption result, and the first encoding decryption result all indicate that the target tag matches, the tag status of the target tag is set to modified status; If at least one of the first matching result, the first address decryption result, and the first encoding decryption result indicates that the target tag does not match, the tag status of the target tag is set to a rejected modification status.

6. The method according to claim 1 or 2, characterized in that, When the interaction type of the interaction request is an identification type, the interaction processing operation performed on the tag feature according to the interaction request indication to obtain the processing result includes: Based on the tag attribute features, a second matching result is obtained to determine whether the unique code of the target tag matches a preset tag database; The user address features are decrypted using the user biometric signal input by the user and the address key configured for the target tag to obtain a second address decryption result. The step of setting the tag status of the target tag based on the processing result includes: If both the second matching result and the second address decryption result indicate that the target tag matches, the tag status of the target tag is set to the recognition status; If at least one of the second matching result and the second address decryption result indicates that the target tag does not match, the tag status of the target tag is set to a rejection recognition status.

7. The method according to claim 1, characterized in that, Before determining the tag features associated with the target tag in response to a user's interaction request for the target tag, the method further includes: Determine the user's current configured permissions; Based on the current configured permissions, determine whether the interaction request corresponds to a restricted interaction type; If the interaction request corresponds to a restricted interaction type, a prompt message indicating that the interaction is refused is sent to the user.

8. A tag-based security interaction device, characterized in that, include: A response module is used to respond to a user's interaction request for a target tag and determine the tag features associated with the target tag; wherein, the tag features include tag attribute features and user address features; The module is used to perform interactive processing operations on the tag features according to the interactive request indication, and obtain the processing result; The setting module is used to set the tag status of the target tag based on the processing result.

9. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions for executing the tag security interaction method according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the tag security interaction method according to any one of claims 1 to 7.

Images