Lost tag searching method and device, related equipment and storage medium

Abstract

The invention discloses a lost tag searching method and device, first equipment, second equipment and a storage medium. The method comprises the following steps: allocating a first waveform code to second equipment in at least one first group; the second equipment comprises a label; the first waveform code comprises an identification code; sending first request information to the second equipment; the first request information carries a first identifier of the first group; receiving a first waveform sequence sent by a second device in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code; and identifying the first waveform sequence, and determining whether the tag is lost or not.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method, apparatus, related device, and storage medium for finding lost tags. Background Art

[0002] Currently, there are mainly two problems. The first problem is that in traditional Electronic Product Code (EPC) or Radio Frequency Identification (RFID) systems, only the inventory method of tags is designed, that is, when all tags are unknown, the EPC codes carried by all tags are obtained. When it is necessary to find lost tags or products, only the method of comparing after inventorying all tags can be used to obtain the lost tags. It is equivalent to knowing the specific information of the lost tag only after inventorying all tags, resulting in low efficiency in finding lost tags.

[0003] Another problem is the low performance of tags, which do not have the ability to precisely synchronize, generate complex signals, or use complex modulation methods, and also limit the efficiency of tag queries. Summary of the Invention

[0004] To solve the related technical problems, embodiments of this application provide a method, apparatus, related device, and storage medium for finding lost tags.

[0005] The technical solution of the embodiments of this application is implemented as follows:

[0006] Embodiments of this application provide a method for finding lost tags, which is applied to a first device and includes:

[0007] Allocating a first waveform code to at least one second device in a first group; the second device includes a tag; the first waveform code includes an identification code;

[0008] Sending a first request message to the second device; the first request message carries a first identifier of the first group;

[0009] Receiving a first waveform sequence sent by the second device in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code;

[0010] Identifying the first waveform sequence to determine whether the tag is lost.

[0011] In the above solution, the method further includes:

[0012] When receiving the Electronic Product Code (EPC) sent by at least two of the second devices, assign a second identifier to each of the second devices;

[0013] Group the at least two second devices based on the second identifier to obtain the number of the first group;

[0014] Determine the first identifier according to the second identifier and the number.

[0015] In the above solution, the first waveform code is any one in the orthogonal waveform sequence, and the corresponding positions in the orthogonal waveform sequence have target features; the method further includes:

[0016] Store the orthogonal waveform sequence.

[0017] In the above solution, the identifying the first waveform sequence to determine whether the tag is lost includes:

[0018] Determine whether the target feature exists at the position corresponding to the first waveform sequence;

[0019] When the target feature does not exist at the position corresponding to the first waveform sequence, determine that the tag is lost;

[0020] When the target feature exists at the position corresponding to the first waveform sequence, determine that the tag is not lost.

[0021] In the above solution, the target feature includes at least one of the following:

[0022] High level;

[0023] Rising edge;

[0024] Falling edge.

[0025] In the above solution, the search information for the lost tag further includes a fifth piece of information, and the fifth piece of information indicates the change priority of at least one change type of each candidate cell.

[0026] In the above solution, the width of the high level is greater than twice the time taken for the second device farthest away to send back the first waveform sequence or greater than twice the maximum distance covered by the first device.

[0027] In the above solution, the first request information further carries a first parameter related to the first waveform sequence; the receiving the first waveform sequence sent by the second devices in the first group includes:

[0028] Receiving the first waveform sequence sent by the devices in the first group based on the first parameter.

[0029] In the above solution, the first request information further carries the reply time for sending the first waveform sequence, and the method further includes:

[0030] Receiving the first waveform sequence sent by a second device within the first group within the reply time.

[0031] In the above solution, the method further includes:

[0032] Broadcasting a first identity (ID) of the first device to the second device; the first ID is used for the second device to compare with a stored second ID to obtain a comparison result;

[0033] Receiving an Electronic Product Code (EPC) sent by the second device when the comparison result indicates that the first ID is inconsistent with the second ID;

[0034] Sending the EPC to a network device; the EPC is used for the network device to determine whether the EPC has an association relationship with other second devices;

[0035] Receiving a second request information for deleting the association relationship sent by the network device when the EPC has an association relationship with other second devices.

[0036] In the above solution, the method further includes:

[0037] When the tag is lost, sending identification information corresponding to the lost tag to the network device; the identification information is used for the network device to delete the record information of the lost tag.

[0038] An embodiment of the present application further provides a method for finding a lost tag, which is applied to a second device and includes:

[0039] Storing a first waveform code assigned by a first device; the first waveform code includes an identification code;

[0040] Receiving first request information sent by the first device; the first request information carries a first identifier of a first group;

[0041] Sending a first waveform sequence to a second device based on the first identifier and the first waveform code; the first waveform sequence is used for the first device to perform identification to determine whether the tag is lost.

[0042] In the above solution, the method further includes:

[0043] Send an EPC to the first device; the EPC is used for the first device to allocate a second identifier for the first device; the second identifier is used to determine the first identifier.

[0044] In the above solution, the search information of the lost tag further includes first information, and the first information carries a first signaling for performing cell activation.

[0045] In the above solution, the first request information further carries a first parameter related to the first waveform sequence. Sending the first waveform sequence to the second device based on the first identifier and the first waveform code includes:

[0046] Sending the first waveform sequence to the second device based on the first identifier, the first waveform code, and the first parameter.

[0047] In the above solution, the first request information further carries a reply time for sending the first waveform sequence, and the method further includes:

[0048] Within the reply time, sending the first waveform sequence to the second device based on the first identifier and the first waveform code.

[0049] In the above solution, the method further includes:

[0050] Receiving a first identity identifier ID broadcast by the first device;

[0051] Comparing the first ID with a stored second ID to obtain a comparison result;

[0052] In the case where the comparison result indicates that the first ID is inconsistent with the second ID, sending an electronic product code EPC to the first device; the EPC is used for the second device to send to a network device so that the network device determines whether the EPC has an association relationship with other second devices; in the case where the EPC has an association relationship with other second devices, sending a deletion of the association relationship to the network device.

[0053] An embodiment of the present application further provides a method for finding a lost tag, which is applied to a network device and includes:

[0054] When a tag in the second device is lost, receiving identification information corresponding to the lost tag sent by the first device;

[0055] Deleting the record information of the lost tag based on the identification information.

[0056] In the above solution, the method further includes:

[0057] Receiving the EPC sent by the first device;

[0058] Determine whether the EPC is associated with other second devices;

[0059] When the EPC is associated with other second devices, send second request information for deleting the association to the first device.

[0060] An embodiment of the present application further provides a lost tag search device, which is set on a first device and includes:

[0061] An allocation unit, configured to allocate a first waveform code to second devices in at least one first group; the second devices include tags; the first waveform code includes an identification code;

[0062] A first sending unit, configured to send first request information to the second devices; the first request information carries a first identifier of the first group;

[0063] A first receiving unit, configured to receive a first waveform sequence sent by the second devices in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code;

[0064] An identification unit, configured to identify the first waveform sequence to determine whether the tag is lost.

[0065] An embodiment of the present application further provides a lost tag search device, which is set on a second device and includes:

[0066] A storage unit, configured to store the first waveform code allocated by the first device; the first waveform code includes an identification code; store the first waveform code allocated by the first device; the first waveform code includes an identification code;

[0067] A second receiving unit, configured to receive the first request information sent by the first device; the first request information carries a first identifier of the first group;

[0068] A second sending unit, configured to send a first waveform sequence to the second device based on the first identifier and the first waveform code; the first waveform sequence is used for the first device to identify whether the tag is lost.

[0069] An embodiment of the present application further provides a lost tag search device, which is set on a network device and includes:

[0070] A third receiving unit, configured to receive identification information corresponding to the lost tag sent by the first device when the tag in the second device is lost;

[0071] A deletion unit, configured to delete the record information of the lost tag based on the identification information.

[0072] An embodiment of the present application further provides a first device, including: a first processor and a first memory for storing a computer program that can run on the processor,

[0073] wherein, when the first processor is used to run the computer program, it executes the steps of any of the above methods on the first device side.

[0074] An embodiment of the present application further provides a second device, including: a second processor and a second memory for storing a computer program that can run on the processor,

[0075] wherein, when the second processor is used to run the computer program, it executes the steps of any of the above methods on the second device side.

[0076] An embodiment of the present application further provides a network device, including: a third processor and a third memory for storing a computer program that can run on the processor,

[0077] wherein, when the third processor is used to run the computer program, it executes the steps of any of the above methods on the network device side.

[0078] An embodiment of the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of any of the above methods on the first device side, or implements the steps of any of the above methods on the second device side, or implements the steps of any of the above methods on the network device side.

[0079] The method, device, related device and storage medium for finding lost tags provided by the embodiments of the present application, wherein the method includes: allocating a first waveform code to a second device in at least one first group; the second device includes a tag; the first waveform code includes an identification code; sending a first request message to the second device; the first request message carries a first identifier of the first group; receiving a first waveform sequence sent by the second device in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code; identifying the first waveform sequence to determine whether the tag is lost; adopting the solution of the present application, by grouping the second devices including tags and allocating different waveform sequences to the tags in the group, the first device can identify the waveform sequence to determine whether the tag is lost, and further distinguish the discarded tags, avoiding the situation of determining the lost tags only after inventorying all the tags, and improving the efficiency of finding tags. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] Figure 1 It is a schematic flowchart of a method for finding lost tags according to the present application;

[0081] Figure 2Another schematic flowchart of the method for finding a lost tag in an embodiment of the present application;

[0082] Figure 3 Another schematic flowchart of the method for finding a lost tag in an embodiment of the present application;

[0083] Figure 4 Schematic diagram of the positions of the server, reader / writer, and tag in the present application;

[0084] Figure 5 Interaction schematic diagram of the server, reader / writer, and tag in the present application;

[0085] Figure 6 Schematic diagram of the orthogonal waveform in the present application;

[0086] Figure 7 Schematic diagram of another waveform in the present application;

[0087] Figure 8 Schematic flowchart of the process for finding a lost tag in the present application;

[0088] Figure 9 Schematic flowchart of the process for determining whether a tag is lost in the present application;

[0089] Figure 10 Schematic structural diagram of a device for finding a lost tag in an embodiment of the present application;

[0090] Figure 11 Another schematic structural diagram of a device for finding a lost tag in an embodiment of the present application;

[0091] Figure 12 Another schematic structural diagram of a device for finding a lost tag in an embodiment of the present application;

[0092] Figure 13 Schematic structural diagram of the first device in an embodiment of the present application;

[0093] Figure 14 Schematic structural diagram of the second device in an embodiment of the present application;

[0094] Figure 15 Schematic structural diagram of the network device in an embodiment of the present application;

[0095] Figure 16 Schematic structural diagram of the system for finding a lost tag in an embodiment of the present application. Detailed implementation manners

[0096] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments.

[0097] In the related art, research projects on passive Internet of Things (Ambient Internet of Things, IoT) have been introduced, with the goal of designing a device that can collect ambient energy (radio, light, vibration, or other energy) for communication. Its complexity and energy consumption are much lower than those of Narrow Band Internet of Things (NB-IoT), and it uses backscatter-based technologies and networks for communication.

[0098] The most similar existing system is EPC C1G2, as well as the Ultra High Frequency Radio Frequency Identification Technology (UHF RFID) system, which also uses backscatter communication technology to achieve communication between tags and readers. It allows tags to randomly reflect signals sent by readers through the slotted Aloha method and interacts with the base station using load modulation.

[0099] In a traditional RFID system, it mainly consists of a radio frequency tag, a reader, and a backend application. The backend application is responsible for controlling the reader to issue commands and receiving the tag inventory results sent back by the reader. The reader is responsible for inventorying tags, and the tag stores a unique identification code, usually an EPC code. The reader and the tag communicate through backscatter, and the tag has a certain storage capacity and processing capacity.

[0100] The reader conducts an inventory of the tag by sending commands such as Select, Query, QueryRep, and QueryAdjust, and Acknowledgement (ACK) to the tag. The Select command is responsible for selecting a specific tag from a tag family; the Query command causes the selected tag to generate a random number; QueryRep and QueryAdjust respectively decrement and adjust the size of the random number; finally, when the random number becomes zero, the tag sends a new random number RN16 for identification to the reader; the reader replies with ACK and the RN16 of the corresponding tag. After receiving ACK and its own RN16, the tag sends its EPC. The reader then transmits the EPC back to the backend application or sends a handle for further communication. Generally, when the tag sends its EPC to the reader, it is considered that an inventory has been completed.

[0101] Based on the current standard progress, the 3rd Generation Partner Project Internet of Things (3GPP Ambient IoT) devices are most likely to choose to use and enhance technologies similar to UHF RFID or EPC C1G2.

[0102] At present, there are mainly two problems. The first problem is that in traditional EPC or RFID systems, only the inventory method of tags is designed, that is, when all tags are unknown, the EPC codes carried by all tags are obtained. And when it is necessary to find lost tags or goods, only the method of comparing them in the background after inventorying all tags can be used to obtain the lost tags. It is equivalent to knowing the specific information of the lost tags only after inventorying all tags, resulting in low efficiency in finding lost tags.

[0103] Another problem is the low performance of tags, which do not have the ability to accurately synchronize, generate complex signals or use complex modulation methods, and also limit the efficiency of tag query.

[0104] In addition, considering that the coverage target of 3GPP is the typical 3GPP site spacing, its coverage distance is greater than the about 10-meter range in UHF RFID, and there are also scenarios with extremely high tag density, so it is necessary to solve the method of inventorying lost tags.

[0105] Based on this, in various embodiments of the present application, by grouping the second devices including tags and assigning different waveform sequences to the tags within the group, the first device can identify the waveform sequences to determine whether the tags are lost, and then distinguish the discarded tags among them, avoiding the situation of determining the lost tags only after inventorying all tags and improving the efficiency of finding tags.

[0106] An embodiment of the present application provides a method for finding lost tags, which is applied to a first device. Figure 1 It is a schematic flowchart of a method for finding lost tags in the present application; as Figure 1 shown, the method includes:

[0107] Step 101: Assign a first waveform code to the second devices in at least one first group; the second devices include tags; the first waveform code includes an identification code;

[0108] Step 102: Send a first request message to the second devices; the first request message carries a first identifier of the first group;

[0109] Step 103: Receive a first waveform sequence sent by the second devices in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code.

[0110] Step 104: Identify the first waveform sequence to determine whether the tag is missing.

[0111] In this embodiment, the first device can be determined according to the actual situation, which is not limited herein. As an example, the first device can be a reader / writer; the reader / writer can be a network device or a terminal; the network device can be a base station. The reader / writer can interact with the server and the tag. The reader / writer can be denoted as interrogator.

[0112] In step 101, the second device can be determined according to the actual situation, which is not limited herein. As an example, the second device can be a tag; the tag can have a single EPC identifier and storage capacity and can interact with the reader / writer. The tag can be denoted as New Tag(s).

[0113] The first waveform code includes an identification code; wherein, the identification code can be determined according to the actual situation, which is not limited herein. As an example, the identification code can be an identification waveform sequence code (Sequence ID, SqID).

[0114] The second device includes a tag; the tag can have a single EPC identifier and storage capacity and can interact with the reader / writer.

[0115] Assigning the first waveform code to the second devices in at least one first group can be that the reader / writer assigns the first waveform code to the second devices in at least one first group. Wherein, the specific number of the at least one first group can be determined according to the actual situation, which is not limited herein. As an example, the at least one first group can be denoted as N first groups. In practical applications, the at least one first group can be denoted as Tag GroupA, Tag GroupB, Tag GroupC...

[0116] In step 102, the first request information carries the first identifier of the first group; the first identifier can be determined according to actual circumstances and is not limited herein. As an example, the first identifier can be a group identifier (Temporary Group ID, TgID). When receiving electronic product codes (EPCs) sent by at least two of the second devices, a second identifier is assigned to each of the second devices; the at least two second devices are grouped based on the second identifier to obtain the number of the first group; the first identifier is determined according to the second identifier and the number. In practical applications, for the search of lost tags, after the reader-writer receives the EPC sent by the terminal, a TID needs to be assigned to the terminal. The length of the TID is determined by the reader-writer, and the reader-writer needs to ensure that the TID assigned to the tag is unique. The tag needs to write the TID assigned by the reader-writer into its storage area. The number of temporary groups N can be obtained from the TID, and the parameter N broadcast by the reader-writer in the broadcast message needs to be used. The parameter N indicates that all the TIDs of the reader-writer can be divided into N temporary groups. Considering the implementation complexity of the tag. For simplicity of implementation, the TgID can be obtained by taking the remainder of the TID divided by N.

[0117] In step 103, the first waveform sequence is determined based on the first identifier and the first waveform code; wherein, the first waveform code can be determined according to actual circumstances and is not limited herein. As an example, the first waveform code is any one of the orthogonal waveform sequences, and the corresponding positions of the orthogonal waveform sequences have target features; wherein, the target features can be determined according to actual circumstances and are not limited herein. As an example, the target features can include at least one of the following: high level; rising edge; falling edge.

[0118] In step 104, the first waveform sequence is recognized to determine whether the tag is lost. The specific determination process can be determined according to the actual situation and is not limited herein. As an example, recognizing the first waveform sequence to determine whether the tag is lost may include determining whether the target feature exists at the position corresponding to the first waveform sequence; in the case where the target feature does not exist at the position corresponding to the first waveform sequence, it is determined that the tag is lost; in the case where the target feature exists at the position corresponding to the first waveform sequence, it is determined that the tag is not lost. The target feature can be determined according to the actual situation and is not limited herein. As an example, the target feature may include at least one of the following: high level; rising edge; falling edge. Determining whether the target feature exists at the position corresponding to the first waveform sequence may be determining whether a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence. In the case where the target feature does not exist at the position corresponding to the first waveform sequence, determining that the tag is lost may be determining that the tag is lost in the case where a high level, a rising edge, a falling edge, etc. do not exist at the position corresponding to the first waveform sequence; in the case where the target feature exists at the position corresponding to the first waveform sequence, determining that the tag is not lost may be determining that the tag is not lost in the case where a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence.

[0119] By adopting the solution of the present application, the second devices including tags are grouped, and different waveform sequences are assigned to the tags in the group, so that the first device can recognize the waveform sequence to determine whether the tag is lost, and further distinguish the discarded tags, avoiding the situation of determining the lost tag only after inventorying all the tags, and improving the efficiency of finding the tag.

[0120] In one embodiment, the method further includes:

[0121] When receiving the EPCs sent by at least two of the second devices, a second identifier is assigned to each of the second devices;

[0122] Based on the second identifier, the at least two second devices are grouped to obtain the number of the first group;

[0123] The first identifier is determined according to the second identifier and the number.

[0124] In this embodiment, when receiving the EPCs sent by at least two of the second devices, allocating a second identifier for each of the second devices may be that the reader allocates a second identifier for each of the second devices when receiving the EPCs sent by at least two of the second devices; wherein, the second device may be a terminal; the second identifier may be determined according to the actual situation and is not limited herein. As an example, the second identifier may be a temporary identifier (TemporaryID, TID). The length of the TID may be determined by the reader, and the reader needs to ensure that the TIDs allocated to the tags are unique. The tag needs to write the TID allocated by the reader into its own storage area.

[0125] Grouping the at least two second devices based on the second identifier to obtain the number of the first group; wherein, the number of the first group may be determined according to the actual situation and is not limited herein. As an example, the number of the first group may be denoted as N.

[0126] Determining the first identifier according to the second identifier and the number; wherein, the first identifier may be determined according to the actual situation and is not limited herein. As an example, the first identifier may be a grouping identifier. As an example, determining the first identifier according to the second identifier and the number may be understood as obtaining the grouping identifier after taking the remainder of the TID by N.

[0127] In practical applications, for finding lost tags, the reader needs to allocate a TID to the terminal after the terminal sends its EPC. The length of the TID is determined by the reader, and the reader needs to ensure that the TIDs allocated to the tags are unique. The tag needs to write the TID allocated by the reader into its own storage area.

[0128] The number of temporary groups N can be obtained from the TID, and the reader needs to broadcast the parameter N in the broadcast message. The parameter N indicates that all the TIDs of the reader can be divided into N temporary groups. Considering the implementation complexity of the tag. For simplicity, the grouping identifier (TgID) can be obtained by taking the remainder of the TID by N, and formula (1) can be referred to; the TgID is subsequently used to narrow down the range of lost tags.

[0129] Id Group = TID mod N (1)

[0130] In one embodiment, the first waveform code is any one of the orthogonal waveform sequences, and the corresponding positions of the orthogonal waveform sequences have target characteristics; the method further includes:

[0131] Storing the orthogonal waveform sequence.

[0132] In this embodiment, the first waveform code is any one of the orthogonal waveform sequences; wherein, the number of orthogonal waveforms in the orthogonal waveform sequence can be determined according to the actual situation and is not limited herein. As an example, the number of orthogonal waveforms in the orthogonal waveform sequence can be denoted as M. That the first waveform code is any one of the orthogonal waveform sequences can be understood as one of the M orthogonal waveform sequences. As an example, the first waveform code can be SqID; SqID corresponds to one of a group of predefined M orthogonal waveform sequences.

[0133] The corresponding positions of the orthogonal waveform sequence have target features; wherein, the target features can be determined according to the actual situation and are not limited herein. As an example, the target features can include at least one of the following: high level; rising edge; falling edge.

[0134] In one embodiment, the identifying the first waveform sequence to determine whether the tag is lost includes:

[0135] Determining whether the target feature exists at the position corresponding to the first waveform sequence;

[0136] In the case where the target feature does not exist at the position corresponding to the first waveform sequence, it is determined that the tag is lost;

[0137] In the case where the target feature exists at the position corresponding to the first waveform sequence, it is determined that the tag is not lost.

[0138] In this embodiment, the target features can be determined according to the actual situation and are not limited herein. As an example, the target features can include at least one of the following: high level; rising edge; falling edge.

[0139] Determining whether the target feature exists at the position corresponding to the first waveform sequence can be determining whether a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence.

[0140] In the case where the target feature does not exist at the position corresponding to the first waveform sequence, determining that the tag is lost can be determining that the tag is lost in the case where a high level, a rising edge, a falling edge, etc. do not exist at the position corresponding to the first waveform sequence;

[0141] In the case where the target feature exists at the position corresponding to the first waveform sequence, determining that the tag is not lost can be determining that the tag is not lost in the case where a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence.

[0142] In one embodiment, the target features include at least one of the following:

[0143] High level;

[0144] Rising edge;

[0145] Falling edge.

[0146] In one embodiment, the width of the high level is greater than twice the time taken for the second device farthest away to send back the first waveform sequence or greater than twice the maximum distance covered by the first device.

[0147] It should be noted that twice the time taken can be determined according to the actual situation and is not limited herein. As an example, twice the time taken can be denoted as 2 Round-Trip Time (2RTT).

[0148] In practical applications, the width of the high level of the waveform should be greater than twice the time taken for the farthest tag to send back a message (i.e., greater than 2RTT), or twice the maximum coverage distance of the reader-writer can also be selected. When needed, the tag needs to send a message according to a predefined waveform. When the reader-writer assigns SqID, it is necessary to ensure that the waveform codes assigned to the tags within the same temporary group are different.

[0149] In one embodiment, the first request information further carries a first parameter related to the first waveform sequence; receiving the first waveform sequence sent by the second device within the first group includes:

[0150] Receiving the first waveform sequence sent by the devices within the first group based on the first parameter.

[0151] It should be noted that the first parameter can be determined according to the actual situation and is not limited herein. As an example, the first parameter can be the waveform width, etc. The waveform width can be denoted as N; generally, the product of M and N should be greater than the total number of tags, and it is recommended that M be greater than N. Between a group of orthogonal waveforms, it is necessary to ensure that the superimposed waveform can also identify specific tags.

[0152] In one embodiment, the first request information further carries the reply time for sending the first waveform sequence, and the method further includes:

[0153] Receiving the first waveform sequence sent by the second device within the first group within the reply time.

[0154] In this embodiment, the reply time can be determined according to the actual situation and is not limited herein. As an example, the reply time can be immediate, that is, sent immediately after the Check command ends, or it can be delayed to give tags that need to be charged enough time to charge.

[0155] When in application, the reader can send a Check command to request the tags in the corresponding temporary group to send predefined waveforms. The Check command should at least contain the TgID and the tag reply timing, and can include the reader ID to prevent misdetection by other tags. The reply timing can be immediate, that is, sent immediately after the Check command ends, or delayed to give sufficient time for tags that need to be energized to be energized. The Check command can also contain some parameters related to the waveform sequence, such as the waveform width. After the reader sends the Check command, the tags with matching TgID need to send the orthogonal waveform sequence corresponding to the assigned SqID within the time window specified by the tag, and the reader then receives the identification sequences sent by all the tags in the group corresponding to the TgID. If necessary, the TID or EPC of the lost tag can also be used to perform a single inventory of the tag to determine whether the tag is lost.

[0156] In one embodiment, the method further includes:

[0157] Broadcasting the first identity ID of the first device to the second device; the first ID is used for the second device to compare with the stored second ID to obtain a comparison result;

[0158] When the comparison result indicates that the first ID is inconsistent with the second ID, receiving the electronic product code EPC sent by the second device;

[0159] Sending the EPC to a network device; the EPC is used for the network device to determine whether the EPC has an association relationship with other second devices;

[0160] When the EPC has an association relationship with other second devices, receiving the second request information sent by the network device to delete the association relationship.

[0161] In this embodiment, the first ID is used for the second device to compare with the stored second ID to obtain a comparison result, which can be understood as the second device comparing the first ID with the stored second ID to obtain a comparison result that the first ID is inconsistent with the second ID or the first ID is consistent with the second ID.

[0162] The network device can be determined according to the actual situation and is not limited here. As an example, the network device can be a network element; the network element can include a server. The server can store tag data and interact with the reader. The server can be denoted as Server.

[0163] In practical applications, the reader broadcasts its reader ID (at least different between adjacent readers, which can be assigned by the server), and the tag stores it in its own storage area. Subsequently, when the tag senses that the broadcast reader ID is different from the ID stored in itself, it is ready to send its EPC code to the reader. If they are the same, it does not respond. After the reader successfully receives the EPC code sent by the tag, it stores the EPC code locally and sends the EPC code to the server. The server internally stores the association relationship between reader A and the EPCs of the tags it senses. When the server receives a new EPC reported by reader A, it checks whether this EPC has been associated with other readers. If the server finds that it is associated with reader B, it notifies reader B to delete the association relationship with this tag. After the tag is deactivated or decommissioned during use, both the server and the corresponding reader need to delete the information related to this tag.

[0164] In one embodiment, the method further includes:

[0165] In the case where the tag is lost, sending identification information corresponding to the lost tag to the network device; the identification information is used for the network device to delete the record information of the lost tag.

[0166] It should be noted that since it is possible to directly determine whether a specific tag is lost according to the identification waveform sequence code in this application (for example, for the first waveform proposed, determining whether there is a high level at the corresponding position, or for the second waveform, determining whether there is a rising or falling edge at the corresponding position), the reader can directly obtain the SqID and TgID information of the lost tag, and then infer the TID and EPC of the lost tag.

[0167] After the reader senses the lost tag, it needs to send the EPC code of the lost tag to the server. The reader can also save the information of adjacent readers and directly send the information of the lost tag to the corresponding reader. At the same time, delete the local record of the lost tag and release the corresponding TID and SqID for potential new tags to use. The server needs to query whether this lost identification has been detected by other readers and make corresponding records. All the information mentioned in this application can be stored in the reader, or the information can be forwarded to the server for storage.

[0168] Correspondingly, an embodiment of this application also provides a method for finding a lost tag, Figure 2 which is another flowchart of a method for finding a lost tag according to an embodiment of this application, as Figure 2 shown; applied to a second device, including:

[0169] Step 201: Store a first waveform code assigned by a first device; the first waveform code includes an identification code;

[0170] Step 202: Receive the first request message sent by the first device; the first request message carries the first identifier of the first group.

[0171] Step 203: Send a first waveform sequence to the second device based on the first identifier and the first waveform code; the first waveform sequence is used for the first device to perform identification to determine whether the tag is lost.

[0172] In this embodiment, the second device can be determined according to the actual situation and is not limited herein. As an example, the second device can be a network device; the network device can be a network element; the network element can include a server.

[0173] In step 201, the first device can be determined according to the actual situation and is not limited herein. As an example, the first device can be a reader; the reader can be a network device or a terminal; the network device can be a base station.

[0174] The first waveform code includes an identification code; wherein, the identification code can be determined according to the actual situation and is not limited herein. As an example, the identification code can be an identification waveform sequence code (Sequence ID, SqID).

[0175] In step 202, the first request message carries the first identifier of the first group; the first identifier can be determined according to the actual situation and is not limited herein. As an example, the first identifier can be TgID. Receive the first request message sent by the first device. In practical applications, for finding lost tags, after the reader sends its EPC at the terminal, the reader needs to allocate a TID for the terminal. The length of the TID is determined by the reader, and the reader needs to ensure that the TID allocated for the tag is unique. The tag needs to write the TID allocated by the reader into its own storage area. The number of temporary groups N can be obtained from the TID, and the parameter N broadcast by the reader in the broadcast message needs to be used. The parameter N indicates that all the TIDs of the reader can be divided into N temporary groups. Considering the implementation complexity of the tag. For simplicity, TgID can be obtained by taking the remainder of TID divided by N.

[0176] In step 203, the first waveform code can be determined according to the actual situation and is not limited herein. As an example, the first waveform code is any one of the orthogonal waveform sequences, and the corresponding positions of the orthogonal waveform sequences have target features; wherein, the target features can be determined according to the actual situation and are not limited herein. As an example, the target features can include at least one of the following: high level; rising edge; falling edge.

[0177] The first waveform sequence is used for the first device to perform identification to determine whether the tag is lost. Among them, the specific determination process for the first device to perform identification on the first waveform sequence to determine whether the tag is lost can be determined according to the actual situation and is not limited herein. As an example, performing identification on the first waveform sequence to determine whether the tag is lost may include determining whether the target feature exists at the position corresponding to the first waveform sequence; in the case where the target feature does not exist at the position corresponding to the first waveform sequence, it is determined that the tag is lost; in the case where the target feature exists at the position corresponding to the first waveform sequence, it is determined that the tag is not lost. The target feature can be determined according to the actual situation and is not limited herein. As an example, the target feature may include at least one of the following: high level; rising edge; falling edge. Determining whether the target feature exists at the position corresponding to the first waveform sequence may be determining whether a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence. In the case where the target feature does not exist at the position corresponding to the first waveform sequence, determining that the tag is lost may be determining that the tag is lost in the case where a high level, a rising edge, a falling edge, etc. do not exist at the position corresponding to the first waveform sequence; in the case where the target feature exists at the position corresponding to the first waveform sequence, determining that the tag is not lost may be determining that the tag is not lost in the case where a high level, a rising edge, a falling edge, etc. exist at the position corresponding to the first waveform sequence.

[0178] By adopting the solution of the present application, by grouping the second devices including tags and assigning different waveform sequences to the tags within the group, the first device can perform identification on the waveform sequences to determine whether the tags are lost, and further distinguish the discarded tags, avoiding the situation of determining the lost tags only after inventorying all the tags, and improving the efficiency of finding tags.

[0179] Among them, in one embodiment, the method further includes:

[0180] Sending an EPC to the first device; the EPC is used for the first device to assign a second identifier to the first device; the second identifier is used to determine the first identifier.

[0181] In this embodiment, the second identifier can be determined according to the actual situation and is not limited herein. As an example, the second identifier may be a Temporary ID (TID). The length of the TID can be determined by the reader, and the reader needs to ensure that the TID assigned to the tag is unique. The tag needs to write the TID assigned by the reader into its own storage area.

[0182] Sending the EPC to the first device may be the second device sending the EPC to the first device; wherein, the second device may be a terminal.

[0183] The second identifier is used to determine the first identifier, which can be understood as grouping the at least two second devices based on the second identifier to obtain the number of the first group; determining the first identifier according to the second identifier and the number; wherein, the number of the first group can be determined according to the actual situation and is not limited herein. As an example, the number of the first group can be denoted as N. The first identifier can be determined according to the actual situation and is not limited herein. As an example, the first identifier can be a grouping identifier. As an example, determining the first identifier according to the second identifier and the number can be understood as obtaining the grouping identifier by taking the remainder of TID divided by N.

[0184] In practical applications, for the search of lost tags, after the reader sends its EPC to the terminal, the reader needs to allocate a TID to the terminal. The length of the TID is determined by the reader, and the reader needs to ensure that the TID allocated to the tag is unique. The tag needs to write the TID allocated by the reader into its storage area.

[0185] The number of temporary groups N can be obtained from the TID, and the parameter N broadcast by the reader in the broadcast message needs to be used. The parameter N indicates that all the TIDs of the reader can be divided into N temporary groups. Considering the implementation complexity of the tag. For simplicity, the grouping identifier (TgID) can be obtained by taking the remainder of TID divided by N, and formula (1) above can be referred to; the TgID is subsequently used to narrow down the range of lost tags.

[0186] In an embodiment, the first request information further carries a first parameter related to the first waveform sequence. Sending the first waveform sequence to the second device based on the first identifier and the first waveform code includes:

[0187] Sending the first waveform sequence to the second device based on the first identifier, the first waveform code, and the first parameter.

[0188] It should be noted that the first parameter can be determined according to the actual situation and is not limited herein. As an example, the first parameter can be the waveform width, etc. The waveform width can be denoted as N; generally, the product of M and N should be greater than the total number of tags, and it is recommended that M be greater than N. Among a group of orthogonal waveforms, it is necessary to ensure that the superimposed waveform can also identify specific tags.

[0189] In an embodiment, the first request information further carries the reply time for sending the first waveform sequence, and the method further includes:

[0190] Within the reply time, send a first waveform sequence to a second device based on the first identifier and the first waveform code.

[0191] In this embodiment, the reply time can be determined according to actual circumstances and is not limited herein. As an example, the reply time can be immediate, that is, sent immediately after the Check command ends, or it can be delayed to give sufficient time for tags that need to be charged to be charged.

[0192] In application, a reader can send a Check command to request tags in a corresponding temporary group to send predefined waveforms. The Check command should at least contain a TgID and the tag reply timing, and can include a reader ID to prevent misdetection by other tags. The reply timing can be immediate, that is, sent immediately after the Check command ends, or it can be delayed to give sufficient time for tags that need to be charged to be charged. The Check command can also contain some parameters related to the waveform sequence, such as the waveform width, etc. After the reader sends the Check command, tags with a matching TgID need to send the orthogonal waveform sequence corresponding to the SqID assigned to them within the time window specified by the tag, and the reader then receives the identification sequences sent by all tags in the group corresponding to the TgID. If necessary, the TID or EPC of the lost tag can also be used to perform a single inventory of the tag to determine whether the tag is lost.

[0193] In one embodiment, the method further includes:

[0194] Receive a first identity identifier ID broadcast by the first device;

[0195] Compare the first ID with a stored second ID to obtain a comparison result;

[0196] In the case where the comparison result indicates that the first ID is inconsistent with the second ID, send an electronic product code EPC to the first device; the EPC is used for the second device to send to a network device so that the network device can determine whether the EPC is associated with other second devices; in the case where the EPC is associated with other second devices, send a request to the network device to delete the association.

[0197] It should be noted that comparing the first ID with the stored second ID to obtain a comparison result can be understood as comparing the first ID with the stored second ID to obtain a comparison result indicating that the first ID is inconsistent with the second ID or the first ID is consistent with the second ID.

[0198] During application, the reader broadcasts its reader ID (at least different between adjacent readers, which can be assigned by the server), and the tag stores it in its own storage area. Subsequently, when the tag senses that the broadcast reader ID is different from the ID stored in itself, it is ready to send its EPC code to the reader. If they are the same, there is no response. After the reader successfully receives the EPC code sent by the tag, it stores the EPC code locally and sends the EPC code to the server. The server internally stores the association relationship between reader A and the EPCs of the tags it senses. When the server receives a new EPC reported by reader A, it checks whether this EPC has been associated with other readers. If the server finds that it is associated with reader B, it notifies reader B to delete the association relationship with this tag. After the tag is deactivated or decommissioned during use, both the server and the corresponding reader need to delete the information related to this tag.

[0199] Correspondingly, an embodiment of the present application further provides a method for finding a lost tag. Figure 3 Another flowchart of a method for finding a lost tag according to an embodiment of the present application is shown in Figure 3 as follows; applied to a network device, including:

[0200] Step 301: When a tag in the second device is lost, receive the identification information corresponding to the lost tag sent by the first device;

[0201] Step 302: Based on the identification information, delete the record information of the lost tag.

[0202] In this embodiment, the network device can be determined according to the actual situation and is not limited herein. As an example, the network device can be a network element; the network element can include a server. The server can store tag data and interact with the reader. The server can be denoted as Server.

[0203] In step 301, the first device can be determined according to the actual situation and is not limited herein. As an example, the first device can be a reader; the reader can be a network device or a terminal; the network device can be a base station. The reader can interact with the server and the tag. The reader can be denoted as interrogator.

[0204] The second device can be determined according to the actual situation and is not limited herein. As an example, the second device can be a tag; the tag can have a single EPC identifier and storage capacity and can interact with the reader. The tag can be denoted as New Tag(s).

[0205] In the case where a tag in the second device is lost, receive the identification information corresponding to the lost tag sent by the first device; wherein, the identification information can be determined according to the actual situation and is not limited herein. As an example, the identification information can be TgID.

[0206] In step 302, based on the identification information, delete the record information of the lost tag. Wherein, the record information can be determined according to the actual situation and is not limited herein. As an example, the record information can be the corresponding TID, SqID, EPC code, etc.

[0207] In practical applications, since it is possible to directly determine whether a specific tag is lost by following the identification waveform sequence code in this application (for example, for the first waveform proposed, determine whether there is a high level at the corresponding position, or for the second waveform, determine whether there is a rising or falling edge at the corresponding position), the reader can directly obtain the SqID and TgID information of the lost tag, and then infer the TID and EPC of the lost tag.

[0208] After the reader senses the lost tag, it is necessary to send the EPC code of the lost tag to the server. The reader can also save the information of adjacent readers and directly send the lost tag information to the corresponding reader. At the same time, eliminate the local record of the lost tag and release the corresponding TID and SqID for potential new tags to use. The server needs to query whether the lost identification has been detected by other readers and make corresponding records. All the information mentioned in this application can be stored in the reader, or the information can be forwarded to the server for storage.

[0209] In one embodiment, the method further includes:

[0210] Receive the EPC sent by the first device;

[0211] Determine whether the EPC is associated with other second devices;

[0212] In the case where the EPC is associated with other second devices, send a second request message for deleting the association to the first device.

[0213] It should be noted that the association can be determined according to the actual situation and is not limited herein. As an example, the association can be understood as the association of the EPC of the tag.

[0214] In actual application, the reader broadcasts the reader ID (at least different between adjacent readers, which can be assigned by the server), and the tag stores it in its own storage area. Subsequently, when the tag senses that the broadcast reader ID is different from the ID stored in itself, it is ready to send its EPC code to the reader. If they are the same, no response is made. After the reader successfully receives the EPC code sent by the tag, it stores the EPC code locally and sends the EPC code to the server. The server internally stores the association relationship between reader A and the EPCs of the tags it senses. When the server receives a new EPC reported by reader A, the server checks whether this EPC has been associated with other readers. If the server finds that it is associated with reader B, it notifies reader B to delete the association relationship with this tag. When the tag is deactivated or decommissioned during use, both the server and the corresponding reader need to delete the information related to this tag.

[0215] For easy understanding, an example is given here. The method for finding lost tags is specifically a method applicable to inventorying lost tags in Ambient IoT. The network elements involved include a server (storing tag data and interacting with readers), readers (which can be base stations or terminals, interacting with the server and tags), and tags (having a single EPC identifier and storage capacity, interacting with readers).

[0216] Its content includes the discovery of unknown tags, the normal deactivation and decommissioning of tags, and the discovery of lost tags. This content can be combined with Figure 4 for understanding. Figure 4 This is a schematic diagram of the positions of the server, reader, and tag in this application.

[0217] Discovery of unknown tags.

[0218] The reader broadcasts the reader ID (at least different between adjacent readers, which can be assigned by the server), and the tag stores it in its own storage area. Subsequently, when the tag senses that the broadcast reader ID is different from the ID stored in itself, it is ready to send its EPC code to the reader. If they are the same, no response is made.

[0219] After the reader successfully receives the EPC code sent by the tag, it stores the EPC code locally and sends the EPC code to the server.

[0220] The server internally stores the association relationship between reader A and the EPCs of the tags it senses. When the server receives a new EPC reported by reader A, the server checks whether this EPC has been associated with other readers. If the server finds that it is associated with reader B, it notifies reader B to delete the association relationship with this tag. This content can be combined with Figure 5 for understanding. Figure 5Schematic diagram of the interaction among the server, the reader / writer, and the tag in this application.

[0221] Normal cancellation and deactivation of the tag.

[0222] After the tag is cancelled or deactivated during use, both the server and the corresponding reader / writer need to delete the information related to this tag.

[0223] Querying lost tags.

[0224] In the 3GPP usage scenario, it is unnecessary and costly to perform a periodic full inventory of tags. Therefore, a reasonable approach should be to only inventory the newly added or disappeared tags within the coverage of the reader / writer, that is, to implement incremental inventory.

[0225] The inventory method for newly added tags can be achieved by the reader / writer broadcasting its reader / writer ID.

[0226] Allocation of TID and waveform code: For finding lost tags, after the reader / writer sends its EPC at the terminal, it needs to allocate a temporary identifier (Temporary ID, hereinafter referred to as TID) to the terminal. The length of the TID is determined by the reader / writer, and the reader / writer needs to ensure that the TID allocated to the tag is unique. The tag needs to write the TID allocated by the reader / writer into its storage area.

[0227] The number of temporary groups N can be obtained from the TID, and the parameter N needs to be broadcast by the reader / writer in the broadcast message. The parameter N represents that all the TIDs of the reader / writer can be divided into N temporary groups. Considering the implementation complexity of the tag. For simplicity, after taking the remainder of the TID by N, the group identifier (Temporary Group ID, hereinafter referred to as TgID) can be obtained, and the TgID is subsequently used to narrow down the range of lost tags:

[0228] Id Group = TID mod N

[0229] After allocating the TID, the reader / writer can also allocate an identification waveform sequence code (Sequence ID, hereinafter referred to as SqID) to the tag. The SqID corresponds to one of a group of pre-defined M orthogonal waveform sequences. The pre-defined orthogonal waveforms can be combined Figure 6 for understanding. Figure 6 Schematic diagram of the orthogonal waveform in this application; the width of the high level of the waveform should be greater than twice the time taken for the farthest tag to send back the message (i.e., greater than 2RTT), or twice the maximum coverage distance of the reader / writer can also be selected. When needed, the tag needs to send messages according to the pre-defined waveform. When allocating the SqID, the reader / writer needs to ensure that the waveform codes allocated to the tags within the same temporary group are different.

[0230] Generally, the product of M and N should be greater than the total number of tags, and it is recommended that M be greater than N. It is necessary to ensure that the superimposed waveform can also identify specific tags among a group of orthogonal waveforms. Similarly, it can also be combined with Figure 7 for understanding. Figure 7 This is a schematic diagram of another waveform in this application.

[0231] The reader searches by group: When the reader has completed at least one inventory of all tags and there is no response from newly added tags, the reader can search for lost tags in some or all of the groups in the group. The search for lost tags can be periodic or triggered by the server.

[0232] When there are many tags, if there are no lost tags in several groups corresponding to the randomly selected TgIDs during spot checks, it can be considered that there are no lost tags. In the next spot check, several TgIDs different from the previous ones can be selected for further screening. If there are lost tags, all TgIDs need to be spot-checked.

[0233] In addition, the reader can also obtain the probability of lost tags by sampling the loss situation of tags in some TgIDs, and estimate the proportion of overall lost tags. Specifically, in use, the reader can randomly select (sample) several TgIDs, and obtain the estimated proportion of lost tags by finding the number of lost tags in the sampled TgIDs. For example, the estimated tag loss proportion = (the number of lost tags in all sampled TgIDs / the total number of tags in all sampled TgIDs). Then the reader can consider this proportion as the loss proportion of all tags within the management range of this reader. When the number of lost tags found by the reader is close to (the total number of tags * the estimated loss proportion) (the definition of "close to" can be that the absolute value of the difference between the two is less than a certain range), the reader can consider that most of the lost tags have been found.

[0234] Subsequently, if lost tags still need to be searched, the groups with a high probability of loss among the previously searched tags and the groups that have not been sampled or have been sampled few times are preferentially selected, so as to take into account the overall loss situation. This content can be combined with Figure 8 for understanding. Figure 8 This is a schematic diagram of the process for searching for lost tags in this application.

[0235] Determination of lost tags: Since it is possible to directly determine whether a specific tag is lost according to the identification waveform sequence code in this application (for example, for the first waveform proposed, determine whether there is a high level at the corresponding position, or for the second waveform, determine whether there is a rising or falling edge at the corresponding position), the reader can directly obtain the SqID and TgID information of the lost tags, and then infer the TID and EPC of the lost tags.

[0236] During application, the reader can send a Check command to request the tags in the corresponding temporary group to send a predefined waveform. The Check command should at least include the TgID and the tag reply timing, and may include the reader ID to prevent misdetection by other tags. The reply timing can be immediate, i.e., sent immediately after the Check command ends, or delayed to give sufficient time for tags that need to be energized to be energized. The Check command can also include some parameters related to the waveform sequence, such as the waveform width, etc.

[0237] After the reader sends the Check command, the tags with matching TgID need to send the orthogonal waveform sequence corresponding to the assigned SqID within the time window specified by the tag, and the reader then receives the identification sequences sent by all the tags in the group corresponding to the TgID.

[0238] If necessary, the TID or EPC of the lost tag can also be used to perform a single inventory of the tag to determine whether the tag is lost. This content can be combined with Figure 9 for understanding, Figure 9 is the schematic diagram of the process for determining whether a tag is lost in this application.

[0239] After the reader senses the lost tag, it needs to send the EPC code of the lost tag to the server. The reader can also save the information of adjacent readers and directly send the information of the lost tag to the corresponding reader. At the same time, eliminate the local record of the lost tag and release the corresponding TID and SqID for potential new tags to use. And the server needs to query whether the lost identifier has been detected by other readers and make corresponding records.

[0240] All the information mentioned in this application can be stored in the reader, or the information can be forwarded to the server for storage.

[0241] In this embodiment, the method of grouping tags and assigning different orthogonal waveforms to the tags within the group enables the reader to distinguish the discarded tags among them, avoiding the situation of determining the lost tag only after inventorying all the tags, and improving the efficiency of finding tags. The reader uses a new signaling (Check) to make the tags send messages and determine the specific lost tag according to the previous grouping situation and the assigned waveform sequence. When using the case of inventorying some tag groups, estimate the overall loss situation of the tags. When the proportion of the found lost tags in the whole tags is the same as the proportion during sampling, stop looking for lost tags. Each time a new search for lost tags is carried out, select some groups with a high probability of lost tags and few sampling times in the previous sampling to ensure the reliability of the sampling samples. The reader broadcasts the ID to let the newly added tags know the process of sending the EPC.

[0242] The method in this application can adapt to longer jitters, recycle unused TO resources to improve resource utilization, and has smaller jitters after recycling TO resources.

[0243] This application can be used for querying lost tags in Ambient IoT. Currently, such problems have not been standardized or specifically discussed, and relevant signaling has not been introduced in similar systems. Moreover, it is simple to implement and has low requirements for tag complexity, so it has a promising future.

[0244] To implement the method of the embodiments of this application, the embodiments of this application also provide a device for finding lost tags, which is set on the first device. Figure 10 It is a schematic structural diagram of a device for finding lost tags according to an embodiment of this application; as Figure 10 shown, the device 1000 includes:

[0245] An allocation unit 1001, configured to allocate a first waveform code to a second device in at least one first group; the second device includes a tag; the first waveform code includes an identification code.

[0246] A first sending unit 1002, configured to send a first request message to the second device; the first request message carries a first identifier of the first group.

[0247] A first receiving unit 1003, configured to receive a first waveform sequence sent by the second device in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code.

[0248] An identification unit 1004, configured to identify the first waveform sequence to determine whether the tag is lost.

[0249] Wherein, in one embodiment, the allocation unit 1001 is further configured to, when receiving electronic product codes (EPCs) sent by at least two of the second devices, allocate a second identifier to each of the second devices; group the at least two second devices based on the second identifier to obtain the number of the first groups; and determine the first identifier according to the second identifier and the number.

[0250] In one embodiment, the first waveform code is any one of orthogonal waveform sequences, and corresponding positions of the orthogonal waveform sequences have target features; the device 1000 further includes a storage unit, configured to store the orthogonal waveform sequences.

[0251] In one embodiment, the recognition unit 1004 is further configured to determine whether the target feature exists at the position corresponding to the first waveform sequence; in the case where the target feature does not exist at the position corresponding to the first waveform sequence, it is determined that the tag is lost; in the case where the target feature exists at the position corresponding to the first waveform sequence, it is determined that the tag is not lost.

[0252] In one embodiment, the target feature includes at least one of the following:

[0253] High level;

[0254] Rising edge;

[0255] Falling edge.

[0256] In one embodiment, the width of the high level is greater than twice the time taken for the second device farthest away to send back the first waveform sequence or greater than twice the maximum distance covered by the first device.

[0257] In one embodiment, the first request information further carries a first parameter related to the first waveform sequence; the first receiving unit 1003 is further configured to receive the first waveform sequence sent by the devices within the first group based on the first parameter.

[0258] In one embodiment, the first request information further carries the reply time for sending the first waveform sequence, and the first receiving unit 1003 is further configured to receive the first waveform sequence sent by the second device within the first group within the reply time.

[0259] In one embodiment, the first sending unit 1002 is further configured to broadcast the first identity identifier ID of the first device to the second device; the first ID is used for the second device to compare with the stored second ID to obtain a comparison result;

[0260] The first receiving unit 1003 is further configured to receive the electronic product code EPC sent by the second device in the case where the comparison result indicates that the first ID and the second ID do not match;

[0261] The first sending unit 1002 is further configured to send the EPC to the network device; the EPC is used for the network device to determine whether the EPC has an association relationship with other second devices;

[0262] The first receiving unit 1003 is further configured to receive the second request information for deleting the association relationship sent by the network device in the case where the EPC has an association relationship with other second devices.

[0263] In one embodiment, the first sending unit 1002 is further configured to send, to the network device, identification information corresponding to a lost tag in case the tag is lost; the identification information is used for the network device to delete record information of the lost tag.

[0264] To implement the method on the first device side in the embodiments of the present application, the embodiments of the present application further provide a device for finding a lost tag, which is disposed on a second device. Figure 11 FIG. is a schematic structural diagram of another device for finding a lost tag in the embodiments of the present application; as Figure 11 shown, the device 1100 includes:

[0265] A storage unit 1101, configured to store a first waveform code assigned by a first device; the first waveform code includes an identification code and stores the first waveform code assigned by the first device; the first waveform code includes an identification code.

[0266] A second receiving unit 1102, configured to receive first request information sent by the first device; the first request information carries a first identifier of a first group.

[0267] A second sending unit 1103, configured to send a first waveform sequence to the second device based on the first identifier and the first waveform code; the first waveform sequence is used for the first device to perform identification to determine whether the tag is lost.

[0268] Wherein, in one embodiment, the second sending unit 1103 is further configured to send an Electronic Product Code (EPC) to the first device; the EPC is used for the first device to assign a second identifier to the first device; the second identifier is used to determine the first identifier.

[0269] In one embodiment, the second sending unit 1103 is further configured to send a first waveform sequence to the second device based on the first identifier, the first waveform code, and the first parameter.

[0270] In one embodiment, the first request information further carries a reply time for sending the first waveform sequence, and the second sending unit 1103 is further configured to send the first waveform sequence to the second device based on the first identifier and the first waveform code within the reply time.

[0271] In one embodiment, the device 1100 further includes a comparison unit; wherein,

[0272] the second receiving unit 1102 is further configured to receive a first identity identifier ID broadcast by the first device;

[0273] the comparison unit is further configured to compare the first ID with a stored second ID to obtain a comparison result;

[0274] The second sending unit 1103 is further configured to send an Electronic Product Code (EPC) to the first device when the comparison result indicates that the first ID is inconsistent with the second ID; the EPC is used for the second device to send to a network device, so that the network device determines whether the EPC is associated with other second devices; when the EPC is associated with other second devices, send a request to the network device to delete the association.

[0275] To implement the method on the first device side in the embodiments of the present application, the embodiments of the present application further provide a device for finding a lost tag, which is set on a network device. Figure 12 FIG. is a schematic structural diagram of another device for finding a lost tag in the embodiments of the present application; as Figure 12 shown, the device 1200 includes:

[0276] A third receiving unit 1201, configured to receive identification information corresponding to a lost tag sent by a first device when a tag in a second device is lost;

[0277] A deleting unit 1202, configured to delete record information of the lost tag based on the identification information.

[0278] Wherein, in one embodiment, the device 1200 further includes a judging unit and a third sending unit; wherein,

[0279] The third receiving unit 1201 is further configured to receive an Electronic Product Code (EPC) sent by the first device;

[0280] The judging unit is configured to judge whether the EPC is associated with other second devices;

[0281] The third sending unit is configured to send second request information for deleting the association to the first device when the EPC is associated with other second devices.

[0282] It should be noted that: when the above-mentioned device for finding a lost tag performs the method for finding a lost tag, only the above-mentioned division of each program module is used for illustration. In practical applications, the above-mentioned processing can be allocated to different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-mentioned processing. In addition, the above-mentioned device for finding a lost tag and the embodiment of the method for finding a lost tag belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0283] Based on the hardware implementation of the above program modules and to implement the method on the second device side in the embodiments of the present application, the embodiments of the present application further provide a first device. Figure 13 It is a schematic structural diagram of the first device in the embodiments of the present application; as Figure 13 shown, the first device 1300 includes:

[0284] A first communication interface 1301 capable of information interaction with the first device;

[0285] A first processor 1302, connected to the first communication interface 1301 to achieve information interaction with the first device, and when used to run a computer program, execute the method provided by one or more of the above technical solutions on the second device side. And the computer program is stored on the first memory 1303.

[0286] It should be noted that: The specific processing procedures of the first processor 1302 and the first communication interface 1301 can be understood with reference to the above method.

[0287] Of course, in actual application, the various components in the first device 1300 are coupled together through a bus system 1304. It can be understood that the bus system 1304 is used to achieve connection communication between these components. In addition to including a data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 13 all kinds of buses are labeled as the bus system 1304.

[0288] The first memory 1303 in the embodiments of the present application is used to store various types of data to support the operation of the first device 1300. Examples of these data include: any computer program for operating on the first device 1300.

[0289] The method disclosed in the embodiments of the present application above can be applied to or implemented by the first processor 1302. The first processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the first processor 1302 or the instructions in the form of software. The above first processor 1302 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1302 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, and this storage medium is located in the first memory 1303. The first processor 1302 reads the information in the first memory 1303 and combines its hardware to complete the steps of the foregoing method.

[0290] In an exemplary embodiment, the first device 1300 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components for executing the foregoing method.

[0291] Based on the hardware implementation of the above program module, and in order to implement the method on the first device side in the embodiments of the present application, the embodiments of the present application further provide a second device. Figure 14 Schematic structural diagram of the second device in the embodiments of the present application; as Figure 14 shown, the second device 1400 includes:

[0292] A second communication interface 1401 capable of interacting with the second device;

[0293] A second processor 1402, connected to the second communication interface 1401 to enable information interaction with a second device, is configured to execute the method provided by one or more of the foregoing technical solutions on the first device side when running a computer program. The computer program is stored in a second memory 1403.

[0294] It should be noted that the specific processing procedures of the second communication interface 1401 and the second processor 1402 can be understood with reference to the foregoing method.

[0295] Of course, in practical applications, the various components in the second device 1400 are coupled together through a bus system 1404. It can be understood that the bus system 1404 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 1404 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 14 all the various buses are labeled as the bus system 1404.

[0296] The second memory 1403 in the embodiments of the present application is used to store various types of data to support the operation of the second device 1400. Examples of these data include: any computer program for operating on the second device 1400.

[0297] The method disclosed in the foregoing embodiments of the present application can be applied to or implemented by the second processor 1402. The second processor 1402 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method can be completed by the integrated logic circuit in the hardware of the second processor 1402 or by instructions in software form. The foregoing second processor 1402 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1402 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the second memory 1403. The second processor 1402 reads the information in the second memory 1403 and combines its hardware to complete the steps of the foregoing method.

[0298] In an exemplary embodiment, the second device 1400 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components for executing the foregoing method.

[0299] It can be understood that the memories (the first memory 1303 and the second memory 1403) in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a sync link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0300] Based on the hardware implementation of the above program modules and in order to implement the method on the first device side in the embodiments of the present application, the embodiments of the present application further provide a network device. Figure 15 It is a schematic structural diagram of the network device in the embodiments of the present application; as Figure 15 shown, the network device 1500 includes:

[0301] A third communication interface 1501 capable of interacting with the first device for information.

[0302] A third processor 1502 is connected to the third communication interface 1501 to implement information interaction with the second device. When running a computer program, it executes the methods provided by one or more technical solutions on the network device side. And the computer program is stored on a second memory 1503.

[0303] It should be noted that the specific processing procedures of the third communication interface 1501 and the third processor 1502 can be understood with reference to the above methods.

[0304] Of course, in actual application, the various components in the network device 1500 are coupled together through a bus system 1504. It can be understood that the bus system 1504 is used to realize the connection and communication between these components. The bus system 1504 includes, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 15 all the various buses are labeled as the bus system 1504.

[0305] The second memory 1503 in the embodiments of the present application is used to store various types of data to support the operation of the access network device 1500. Examples of these data include: any computer program for operating on the network device 1500.

[0306] The method disclosed in the embodiments of the present application can be applied to or implemented by the third processor 1502. The third processor 1502 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method can be completed by the integrated logic circuit of the hardware in the third processor 1502 or instructions in the form of software. The above-mentioned third processor 1502 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 1502 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, and this storage medium is located in the third memory 1503. The third processor 1502 reads the information in the third memory 1503 and combines its hardware to complete the steps of the foregoing method.

[0307] In an exemplary embodiment, the third device 1500 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components for executing the foregoing method.

[0308] It can be understood that the memories (the first memory 1303, the second memory 1403, and the third memory 1503) in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache.By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), sync link dynamic random access memory (SLDRAM), direct rambus random access memory (DRRAM). The memories described in the embodiments of the present application are intended to include, but not be limited to, these and any other suitable types of memories.

[0309] To implement the method provided by the embodiments of the present application, the embodiments of the present application further provide a system for finding lost tags. Figure 16 Schematic diagram of the structure of the system for finding lost tags in the embodiments of the present application; as Figure 16 shown, the system includes: a first device 1601, a second device 1602, and a network device 1603.

[0310] Here, it should be noted that: the specific processing procedures of the first device 1601, the second device 1602, and the network device 1603 have been described in detail above and will not be elaborated here.

[0311] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it includes a first memory 1303 storing a computer program, and the above computer program can be executed by a first processor 1302 of a first device 1300 to complete the steps of the foregoing method on the first device side. Another example is a second memory 1403 storing a computer program, and the above computer program can be executed by a second processor 1402 of a second device 1400 to complete the steps of the foregoing method on the second device side. Another example is a third memory 1503 storing a computer program, and the above computer program can be executed by a third processor 1502 of a network device 1500 to complete the steps of the foregoing method on the network device side. The computer-readable storage medium can be a FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc.

[0312] It should be noted that: "first", "second", "third", etc. are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence.

[0313] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0314] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.

Claims

1. A method for finding a lost label, characterized in that, Applied to a first device, including: Allocating a first waveform code to a second device in at least one first group; the second device includes a tag; the first waveform code includes an identification code; Sending first request information to the second device; the first request information carries a first identifier of the first group; Receiving a first waveform sequence sent by a second device in the first group; the first waveform sequence is determined based on the first identifier and the first waveform code; Identifying the first waveform sequence to determine whether the tag is lost.

2. The method according to claim 1, characterized in that, The method further includes: When receiving electronic product codes (EPCs) sent by at least two of the second devices, allocating a second identifier to each of the second devices; Grouping the at least two second devices based on the second identifier to obtain the number of the first groups; Determining the first identifier according to the second identifier and the number.

3. The method according to claim 1, characterized in that, The first waveform code is any one of orthogonal waveform sequences, and corresponding positions of the orthogonal waveform sequences have target features; The method further includes: Storing the orthogonal waveform sequence.

4. The method according to claim 3, wherein The identifying the first waveform sequence to determine whether the tag is lost includes: Judging whether the target feature exists at a position corresponding to the first waveform sequence; When the target feature does not exist at the position corresponding to the first waveform sequence, determining that the tag is lost; When the target feature exists at the position corresponding to the first waveform sequence, determining that the tag is not lost.

5. The method according to claim 4, characterized in that The target feature includes at least one of the following: High level; Rising edge; Falling edge.

6. The method according to claim 5, wherein The width of the high level is greater than twice the time taken for the second device farthest away to send back the first waveform sequence or greater than twice the maximum distance covered by the first device.

7. The method according to claim 6, wherein The first request information further carries a first parameter related to the first waveform sequence; the receiving the first waveform sequence sent by a second device in the first group includes: Receiving the first waveform sequence sent by a device in the first group based on the first parameter.

8. The method according to claim 1, wherein The first request information further carries a reply time for sending the first waveform sequence, and the method further includes: Within the reply time, receiving the first waveform sequence sent by a second device in the first group.

9. The method according to claim 1, wherein The method further includes: Broadcasting a first identity identifier (ID) of the first device to the second device; the first ID is used for the second device to compare with a stored second ID to obtain a comparison result; When the comparison result indicates that the first ID is inconsistent with the second ID, receiving the electronic product code (EPC) sent by the second device; Sending the EPC to a network device; the EPC is used for the network device to judge whether the EPC has an associated relationship with other second devices; When the EPC has an associated relationship with other second devices, receiving a second request information sent by the network device to delete the associated relationship.

10. The method according to claim 9, wherein The method further includes: In case the label is lost, send the identification information corresponding to the lost label to the network device; the identification information is used for the network device to delete the record information of the lost label.

11. A method for finding a lost tag, characterized in that, Applied to a second device including a label, comprising: Store the first waveform code assigned by the first device; the first waveform code includes an identification code; Receive the first request information sent by the first device; the first request information carries the first identification of the first group; Send a first waveform sequence to the second device based on the first identification and the first waveform code; the first waveform sequence is used for the first device to perform identification to determine whether the label is lost.

12. The method according to claim 11, wherein The method further includes: Send the Electronic Product Code (EPC) to the first device; the EPC is used for the first device to assign a second identification to the first device; the second identification is used to determine the first identification.

13. The method according to claim 11, characterized in that, The first request information further carries a first parameter related to the first waveform sequence, and sending the first waveform sequence to the second device based on the first identification and the first waveform code includes: Send the first waveform sequence to the second device based on the first identification, the first waveform code, and the first parameter.

14. The method according to claim 11, wherein The first request information further carries the reply time for sending the first waveform sequence, and the method further includes: Within the reply time, send the first waveform sequence to the second device based on the first identification and the first waveform code.

15. The method according to claim 11, wherein The method further includes: Receive the first identity identification (ID) broadcast by the first device; Compare the first ID with the stored second ID to obtain a comparison result; In case the comparison result indicates that the first ID is inconsistent with the second ID, send the Electronic Product Code (EPC) to the first device; the EPC is used for the second device to send to the network device so that the network device determines whether the EPC has an association relationship with other second devices; in case the EPC has an association relationship with other second devices, send a request to the network device to delete the association relationship.

16. A method for finding a lost label, characterized in that, Applied to a network device, comprising: In case the label in the second device is lost, receive the identification information corresponding to the lost label sent by the first device; Delete the record information of the lost label based on the identification information.

17. The method according to claim 16, wherein The method further includes: Receive the Electronic Product Code (EPC) sent by the first device; Determine whether the EPC has an association relationship with other second devices; In case the EPC has an association relationship with other second devices, send a second request information for deleting the association relationship to the first device.

18. A device for finding a lost label, characterized in that, Disposed on the first device, comprising: An allocation unit, configured to allocate a first waveform code to second devices within at least one first group; the second devices include labels; the first waveform code includes an identification code; A first sending unit, configured to send first request information to the second devices; the first request information carries the first identification of the first group; A first receiving unit, configured to receive a first waveform sequence sent by a second device within the first group; the first waveform sequence is determined based on the first identifier and the first waveform code; An identifying unit, configured to identify the first waveform sequence to determine whether the label is missing.

19. A device for finding lost tags, characterized in that, It is provided on the second device and includes: A storage unit, configured to store a first waveform code assigned by the first device; the first waveform code includes an identification code and stores the first waveform code assigned by the first device; the first waveform code includes an identification code; A second receiving unit, configured to receive first request information sent by the first device; the first request information carries a first identifier of the first group; A second sending unit, configured to send a first waveform sequence to the second device based on the first identifier and the first waveform code; the first waveform sequence is used by the first device for identification to determine whether the label is missing.

20. A device for finding a lost tag, characterized in that, It is provided on the network device and includes: A third receiving unit, configured to receive identification information corresponding to the missing label sent by the first device when the label in the second device is missing; A deleting unit, configured to delete the record information of the missing label based on the identification information.

21. A first device, characterized in that, It includes: A first processor and a first memory for storing a computer program that can run on the processor, wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 10.

22. A second device, characterized in that, It includes: A second processor and a second memory for storing a computer program that can run on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 11 to 15.

23. A network device, characterized in that, It includes: A third processor and a third memory for storing a computer program that can run on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 16 to 17.

24. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 10, or implements the steps of the method according to any one of claims 11 to 15, or implements the steps of the method according to any one of claims 16 to 17.

Images