Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first" and "second" in this application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
The application firstly provides a method for correcting the binding relationship of the electronic tag.
Fig. 1 is a schematic flowchart of an embodiment of a method for correcting an electronic tag binding relationship according to the present application. As shown in fig. 1, in the first embodiment, the electronic tag binding relationship correcting method may include the following steps:
step S11: and reading the target electronic tag to obtain a first code.
In this embodiment, the electronic tag is a carrier of an RFID (Radio Frequency Identification) technology, and a reader may be used to read the target electronic tag to obtain the storage content of the target electronic tag, and determine the obtained content as the first code.
Step S12: and judging whether the target binding relationship exists in the electronic tag binding relationship list or not.
And the target binding relationship is the binding relationship of the first code.
In this embodiment, the target binding relationship may be a binding relationship between the first code and a device, or a binding relationship between the first code and an account, which is not limited herein. The electronic tag binding relationship list comprises the binding relationships of all electronic tags in the electronic tag identification system, and correspondingly bound equipment or accounts can be inquired in the electronic tag binding relationship list according to corresponding codes.
If the binding relationship of the first code cannot be found in the electronic tag binding relationship list, it may be considered that an error (e.g., a transmission error) occurs in the process of acquiring the first code, so that the acquired first code is not a correct code stored in the target electronic tag, or that the acquired first code is a correct code stored in the target electronic tag, but when the code in the target electronic tag is bound to a device or an account, the read acquired code is not a correct code, so that the device or the account is bound to a wrong code.
If the determination result of step S12 is no, step S13 is executed.
Step S13: it is determined whether the first code and the second code are the same.
Wherein the second code is obtained by reading the target electronic tag again.
In this embodiment, the reader may be adopted to read the target electronic tag again to obtain the storage content of the target electronic tag, and the obtained content may be determined as the second code. And then judging whether the obtained first code and the second code are the same, wherein the error code obtained by each error reading is different even if the error code is obtained by reading the target electronic tag, so that if the first code and the second code are the same, the first code and the second code can be considered to be the correct codes stored in the target electronic tag.
If the determination result in the step S13 is the same, the step S14 is executed.
Step S14: and determining the unread binding relationship in the electronic tag binding relationship list, and correcting the unread binding relationship based on the first code or the second code.
In this embodiment, if it is determined that the binding relationship of the first code does not exist in step S12, and it is determined that the first code is the correct code in step S13, it may be determined that the code bound in at least one binding relationship in the electronic tag binding relationship list should be the first code, but an error code is actually bound, so that the binding relationship is not recorded in use. Therefore, the unread binding relationship in the electronic tag binding relationship list, that is, the binding relationship recorded in the electronic tag binding relationship list and never read can be determined, and the corresponding binding relationship can be corrected based on the correct first code.
Optionally, step S14 may specifically include:
and if only one unread binding relationship exists in the electronic tag binding relationship list, replacing the bound code in the unread binding relationship with the first code or the second code to finish the correction of the binding relationship.
Specifically, because at least one binding relationship in the electronic tag binding relationship list is incorrect, and the code that should be bound is the first code or the second code, only one unread binding relationship exists in the electronic tag binding relationship list, it can be ensured that the unread binding relationship that exists is the binding relationship that needs to be corrected, the code in the binding relationship can be replaced by the first code or the second code, the correction of the binding relationship is completed, and the efficiency of correcting the binding relationship is improved.
Optionally, step S14 may specifically include:
if more than two unread binding relations exist in the electronic tag binding relation list, prompting a user to determine a to-be-corrected binding relation in the more than two unread binding relations, and replacing a code bound in the to-be-corrected binding relation with a first code or a second code to finish correction of the binding relation.
Specifically, if more than two unread binding relationships exist in the electronic tag binding relationship list, which binding relationship needs to be corrected by the first code cannot be automatically determined, so that a user can be prompted to manually determine the binding relationship which needs to be corrected, that is, the binding relationship to be corrected is determined, and then the code in the binding relationship to be corrected is replaced by the first code or the second code, so that the correction of the binding relationship is completed, and the accuracy of correcting the binding relationship is improved.
Different from the prior art, based on the technical scheme of the application, the first code can be obtained by reading the target electronic tag, whether the binding relationship corresponding to the first code exists in the pre-stored electronic tag binding relationship list or not is judged, whether the first code is the same as the second code obtained by reading the target electronic tag again is judged when the binding relationship corresponding to the first code does not exist, the first code or the second code can be considered as the correct code corresponding to the target electronic tag when the first code is the same as the second code, and then the unread binding relationship can be corrected based on the correct first code or the correct second code. According to the technical scheme, the binding relation can be timely corrected in the using process of the electronic tag, and the reliability of the electronic tag is improved.
Fig. 2 is a flowchart illustrating another embodiment of the electronic tag binding relationship correction method according to the present application. As shown in fig. 2, in a second embodiment, the electronic tag binding relationship correcting method may include the following steps:
step S21: and reading the target electronic tag to obtain a first code.
Step S22: and judging whether the target binding relationship exists in the electronic tag binding relationship list or not.
If the determination result of step S22 is no, step S23 is executed.
Step S23: and reading the target electronic tag to obtain a second code.
Step S24: it is determined whether the first code and the second code are the same.
If the determination result in the step S24 is not the same, then step S25 is executed.
Step S25: and determining the unread binding relationship in the electronic tag binding relationship list, and correcting the unread binding relationship based on the first code or the second code.
In this embodiment, after it is determined that the target binding relationship does not exist in the electronic tag binding relationship list, the target electronic tag may be read for the second time to obtain the second code, so as to be used for subsequently determining whether the first code and the second code are the same. If the target binding relationship exists in the electronic tag binding relationship list, the first code can be directly determined to be the correct code stored in the target electronic tag, subsequent steps are not needed, and the efficiency of reading the target electronic tag is improved.
Optionally, step S21 may specifically include:
and reading the target electronic tag to obtain a first pending code.
And performing CRC on the first to-be-determined code.
And if the verification fails, returning to execute the step of reading the target electronic tag to obtain the first undetermined code and the subsequent steps. And if the verification is successful, determining the first code to be determined as the first code.
Optionally, step S23 may specifically include:
and reading the target electronic tag to obtain a second pending code.
And performing CRC on the second pending code.
And if the verification fails, returning to the step of executing the reading of the target electronic tag so as to obtain a second undetermined code and subsequent steps. And if the verification is successful, determining the second pending code as the second code.
Optionally, before step S21, the method for correcting the electronic tag binding relationship may further include:
and reading the target electronic tag to obtain a third code.
And binding the third code with the target equipment, and recording the binding relationship between the third code and the target equipment into an electronic tag binding relationship list.
Specifically, the step before step S21 may be a step of binding the target electronic tag and the target device in advance before handing the target electronic tag to the user for use, so as to facilitate the user to use.
Further, reading the target electronic tag to obtain the third code may include:
and reading the target electronic tag to obtain a third pending code.
And performing CRC check on the third pending code.
And if the verification fails, returning to execute the step of reading the target electronic tag to obtain a third undetermined code and subsequent steps. And if the verification is successful, determining the third pending code as the third code.
It should be noted that the code stored in the target electronic tag may include a specific CRC check code. If the CRC check code in the checked code (such as the first pending code, the second pending code and the third pending code) is found to be wrong during the CRC check, the checked code can be determined to be the wrong code. Therefore, when the CRC fails, namely when the CRC code in the checked code is wrong, the target electronic tag needs to be read again, and the checked code needs to be obtained again until the check is successful, so that the reliability of the electronic tag is improved.
Different from the prior art, based on the technical scheme of the application, the first code can be obtained by reading the target electronic tag, whether the binding relationship corresponding to the first code exists in the pre-stored electronic tag binding relationship list or not is judged, whether the first code is the same as the second code obtained by reading the target electronic tag again is judged when the binding relationship corresponding to the first code does not exist, the first code or the second code can be considered as the correct code corresponding to the target electronic tag when the first code is the same as the second code, and then the unread binding relationship can be corrected based on the correct first code or the correct second code. According to the technical scheme, the binding relation can be timely corrected in the using process of the electronic tag, and the reliability of the electronic tag is improved.
Fig. 3 is a flowchart illustrating a method for correcting an electronic tag binding relationship according to another embodiment of the present application. As shown in fig. 3, in a third embodiment, the electronic tag binding relationship correcting method may include the following steps:
step S31: and reading the target electronic tag to obtain a first code.
Step S32: and reading the target electronic tag to obtain a second code.
Step S33: and judging whether the target binding relationship exists in the electronic tag binding relationship list or not.
If the determination result of step S33 is no, step S34 is executed.
Step S34: it is determined whether the first code and the second code are the same.
If the determination result in the step S34 is not the same, then step S35 is executed.
Step S35: and determining the unread binding relationship in the electronic tag binding relationship list, and correcting the unread binding relationship based on the first code or the second code.
Different from the prior art, based on the technical scheme of the application, the first code can be obtained by reading the target electronic tag, whether the binding relationship corresponding to the first code exists in the pre-stored electronic tag binding relationship list or not is judged, whether the first code is the same as the second code obtained by reading the target electronic tag again is judged when the binding relationship corresponding to the first code does not exist, the first code or the second code can be considered as the correct code corresponding to the target electronic tag when the first code is the same as the second code, and then the unread binding relationship can be corrected based on the correct first code or the correct second code. According to the technical scheme, the binding relation can be timely corrected in the using process of the electronic tag, and the reliability of the electronic tag is improved.
The application also provides electronic tag binding relation correction equipment.
Fig. 4 is a schematic structural diagram of an embodiment of an electronic tag binding relationship correction device according to the present application. As shown in fig. 4, the electronic tag bindingrelationship correcting apparatus 40 of the present embodiment includes: aprocessor 41, amemory 42, and abus 43.
Theprocessor 41 and thememory 42 are respectively connected to thebus 43, thememory 42 stores program instructions, and theprocessor 41 is configured to execute the program instructions to implement the method for correcting the electronic tag binding relationship in the above embodiment.
In the present embodiment, theprocessor 41 may also be referred to as a CPU (Central Processing Unit). Theprocessor 41 may be an integrated circuit chip having signal processing capabilities. Theprocessor 41 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or theprocessor 41 may be any conventional processor or the like.
Different from the prior art, based on the technical scheme of the application, the first code can be obtained by reading the target electronic tag, whether the binding relationship corresponding to the first code exists in the pre-stored electronic tag binding relationship list or not is judged, whether the first code is the same as the second code obtained by reading the target electronic tag again is judged when the binding relationship corresponding to the first code does not exist, the first code or the second code can be considered as the correct code corresponding to the target electronic tag when the first code is the same as the second code, and then the unread binding relationship can be corrected based on the correct first code or the correct second code. According to the technical scheme, the binding relation can be timely corrected in the using process of the electronic tag, and the reliability of the electronic tag is improved.
The present application also provides a computer-readable storage medium.
Fig. 5 is a schematic structural diagram of an embodiment of an electronic tag binding relationship correction device according to the present application. As shown in fig. 5, the computerreadable storage medium 50 of the present embodiment has stored thereonprogram instructions 51, and when executed by a processor (not shown), theprogram instructions 51 implement the electronic tag binding relationship correction method in the above embodiment.
The computerreadable storage medium 50 of the embodiment may be, but is not limited to, a usb disk, an SD card, a PD optical drive, a removable hard disk, a high-capacity floppy drive, a flash memory, a multimedia memory card, a server, etc.
Different from the prior art, based on the technical scheme of the application, the first code can be obtained by reading the target electronic tag, whether the binding relationship corresponding to the first code exists in the pre-stored electronic tag binding relationship list or not is judged, whether the first code is the same as the second code obtained by reading the target electronic tag again is judged when the binding relationship corresponding to the first code does not exist, the first code or the second code can be considered as the correct code corresponding to the target electronic tag when the first code is the same as the second code, and then the unread binding relationship can be corrected based on the correct first code or the correct second code. According to the technical scheme, the binding relation can be timely corrected in the using process of the electronic tag, and the reliability of the electronic tag is improved.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.