Label data reporting method, device and system, storage medium, program product and computer equipment

Abstract

The invention discloses a label data reporting method, device and system, a storage medium, a program product and computer equipment. The method comprises the steps that a label receives an inventory message from a read-write end; in response to the inventory message, reporting a first message of the tag to the read-write end at least based on parameter information under the condition of determining that the tag type of the tag corresponds to a first reporting mode, the parameter information being suitable for indicating a parameter of the tag matched with the first reporting mode, the first message carrying data of the tag, and the tag type of the tag corresponding to the first reporting mode; therefore, the label with a high requirement on data reading synchronism can select to adopt the first reporting mode, namely, the reporting of the label data is completed according to the parameter information which is pre-configured in the label and corresponds to the first reporting mode, so that the probability of time slot collision occurring in the label adopting the first reporting mode can be reduced; and thus, the data reading synchronism of the target tag can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a tag data reporting method, apparatus, system, storage medium, program product, and computer equipment. Background Technology

[0002] In Internet of Things (IoT) systems, readers are typically needed to read the tag data of each tag, such as the tag data of RFID (Radio Frequency Identification) tags.

[0003] In related technologies, when a reader requests each tag to report tag data, each tag typically randomly selects a Slot Count (SC) for that reporting process and reports its data when it reaches its selected SC, allowing the reader to read the tag's data. However, if different tags randomly select the same SC, slot conflicts and collisions can occur between tags sharing the same SC. Since the reader generally cannot complete data reading from multiple tags within a single SC, it becomes difficult for the reader to complete data reading from tags sharing the same SC during a single reporting process. However, in some application scenarios, there are high requirements for the synchronization of data reading from certain tags, requiring the reader to complete data reading from these tags within the same reporting process. Related technologies clearly struggle to solve this problem. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application propose a tag data reporting method, apparatus, system, storage medium, program product, and computer equipment, which can improve the data reading synchronization of target tags.

[0005] In a first aspect, embodiments of this application provide a tag data reporting method, applicable to tags, the method comprising:

[0006] Receive inventory messages from the read / write end;

[0007] In response to the inventory message, if it is determined that the tag type of the tag corresponds to the first reporting mode, the first message of the tag is reported to the read / write terminal based at least on parameter information, wherein the parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0008] Optionally, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0009] At least based on the time slot parameters, determine the time slot counter;

[0010] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0011] Optionally, the inventory message carries a first time slot number matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0012] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0013] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0014] Optionally, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0015] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0016] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0017] Optionally, the inventory message carries a first time slot number matching the first reporting mode, and the method further includes:

[0018] In response to the inventory message, if it is determined that the tag type of the tag corresponds to the second reporting mode, a time slot counter is determined based on the first time slot quantity, and based on the time slot counter, the second message of the tag is reported to the read / write terminal, the second message carrying the data of the tag.

[0019] Optionally, determining the time slot counter based on the first time slot number includes:

[0020] Based on the first number of time slots, determine the random time slot interval;

[0021] The time slot counter is selected within the random time slot interval.

[0022] Optionally, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0023] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0024] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0025] Optionally, the read / write terminal is configured with management list information that matches the first reporting mode;

[0026] The first message also carries service type information of the tag that matches the first reporting mode. The first message is adapted to instruct the read / write terminal to perform verification based on the management list information and the service type information of the tag.

[0027] Optionally, the read / write terminal performs verification based on the management list information and the business type information of the tag, including:

[0028] The read / write terminal determines whether the tag is a newly added tag corresponding to the first reporting mode based on the management list information and the business type information of the tag. If so, it verifies whether the tag group corresponding to the tag is complete and valid based on the business type information.

[0029] Optionally, the first message is also adapted to instruct the read / write terminal to update the management list information based on the service type information.

[0030] Optionally, at least a portion of the inventory message is determined by the management list information;

[0031] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0032] Optionally, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0033] Secondly, embodiments of this application provide a tag data reporting method, applicable to a read / write end, the method comprising:

[0034] Send inventory message to the tag;

[0035] in,

[0036] The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode;

[0037] The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0038] Optionally, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0039] At least based on the time slot parameters, determine the time slot counter;

[0040] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0041] Optionally, the inventory message carries a first time slot number matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0042] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0043] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0044] Optionally, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0045] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0046] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0047] Optionally, the inventory message carries a first time slot number that matches the first reporting mode;

[0048] The inventory message is also adapted to instruct the tag, when it is determined that the tag type corresponds to the second reporting mode, to determine a time slot counter based on the first time slot quantity, and to report the second message of the tag to the read / write terminal based on the time slot counter, wherein the second message carries the data of the tag.

[0049] Optionally, determining the time slot counter based on the first time slot number includes:

[0050] Based on the first number of time slots, determine the random time slot interval;

[0051] The time slot counter is selected within the random time slot interval.

[0052] Optionally, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0053] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0054] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0055] Optionally, the read / write terminal is configured with management list information matching the first reporting mode, and the first message also carries business type information of the tag matching the first reporting mode. The method further includes:

[0056] In response to the first message, verification is performed based on the management list information and the business type information of the tag.

[0057] Optionally, the verification based on the management list information and the business type information of the tag includes:

[0058] Based on the management list information and the business type information of the tag, determine whether the tag is a newly added tag corresponding to the first reporting mode. If so, verify whether the tag group corresponding to the tag is complete and valid according to the business type information.

[0059] Optionally, the method further includes:

[0060] Update the management list information based on the business type information.

[0061] Optionally, at least a portion of the inventory message is determined by the management list information;

[0062] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0063] Optionally, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0064] Optionally, the management list information is adapted to indicate a first time slot matching the first reporting pattern, the number of tags is one or more, and the method further includes:

[0065] Based on all the first messages reported in response to the inventory message, the time slot occupied by each of the first messages in the first time slot during the reporting process is detected to obtain the detection result;

[0066] Based on the detection results, update the management list information.

[0067] Optionally, the first time slot includes at least one time slot, the management list information includes parameter information for at least one tag whose tag type corresponds to the first reporting mode, the at least one tag corresponds one-to-one with the at least one time slot, and updating the management list information based on the detection result includes:

[0068] If the detection result indicates that there is an unoccupied time slot in the at least one time slot, the management list information is updated based on the parameter information of the tag corresponding to the unoccupied time slot;

[0069] And / or,

[0070] If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, the management list information is updated based on the repeatedly occupied time slot.

[0071] Optionally, the method further includes:

[0072] If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, a reset disk storage message is generated based on the repeatedly occupied time slot.

[0073] Thirdly, embodiments of this application provide a tag data reporting device, applicable to tags, the device comprising:

[0074] The command receiving module is used to receive disk storage messages from the read / write end;

[0075] The first reporting module is configured to, in response to the inventory message, report a first message of the tag to the read / write terminal based at least on parameter information, provided that the tag type of the tag corresponds to the first reporting mode. The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0076] Fourthly, embodiments of this application provide a tag data reporting device suitable for a reader / writer, the device comprising:

[0077] The command sending module is used to send inventory messages to the tags;

[0078] in,

[0079] The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode;

[0080] The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0081] Fifthly, embodiments of this application provide a tag data reporting system, including:

[0082] The label is configured to perform the method described in any one of the first aspects above; and,

[0083] The read / write end is configured to perform the method described in any one of the second aspects above.

[0084] In a sixth aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0085] In a seventh aspect, embodiments of this application provide a computer program product, including computer instructions that, when executed by a processor, implement the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0086] Eighthly, embodiments of this application provide a computer device including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0087] In summary, the embodiments of this application have at least the following beneficial effects:

[0088] By adopting the embodiments of this application, tags with high data reading synchronization requirements (i.e., target tags) can choose to use the first reporting mode, that is, to complete the reporting of tag data according to the parameter information pre-configured in the tag corresponding to the first reporting mode. This can reduce the probability of time slot conflicts and collisions of tags using the first reporting mode, thereby improving the data reading synchronization of the target tags. Attached Figure Description

[0089] Figure 1 This is a schematic diagram of the RFID tag data reporting process in related technologies;

[0090] Figure 2 This is a schematic diagram of UHF RFID wireless sensing provided in an embodiment of this application;

[0091] Figure 3 This is a flowchart illustrating the tag data reporting method provided in an embodiment of this application;

[0092] Figure 4 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0093] Figure 5 This is a schematic diagram of the label EPC structure provided in the embodiments of this application;

[0094] Figure 6 This is a flowchart illustrating the tag data reporting method provided in an embodiment of this application;

[0095] Figure 7 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0096] Figure 8 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0097] Figure 9 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0098] Figure 10 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0099] Figure 11 This is a schematic diagram of the time slots provided in the embodiments of this application;

[0100] Figure 12 This is a schematic diagram of the tag data reporting device provided in the embodiments of this application;

[0101] Figure 13 This is a schematic diagram of the tag data reporting device provided in the embodiments of this application;

[0102] Figure 14 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application. Detailed Implementation

[0103] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0104] In the description of this application, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first," "second," "third," etc., may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more. In the description of this application, the term "comprising" and its variations are open-ended, meaning "including but not limited to." The term "based on" means "at least partially based on." The term "according to" means "at least partially according to." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments."

[0105] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0106] In the description of this application, it should be noted that, unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the application. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0107] In some cases, see Figure 1Let's take RFID (Radio Frequency Identification) tags as an example. In related technologies, RFID tag data reporting typically employs a random collision reporting mechanism based on the Aloha protocol. After the reader (interrogator) issues a Query inventory command, this command instructs the RFID tag to randomly select a SC (Slot Count), for example, selecting 5 from 0-15. RFID tags with a SC of 0 will directly return / report RN16 (a 16-bit random number) to the reader. At this point, multiple RFID tags may simultaneously report RN16. If the reader successfully demodulates the RN16 of an RFID tag, it reads the EPC (Electronic Product Code) of that RFID tag via the Ack command. At this point, the reader has successfully completed reading an RFID tag (i.e., completed Single Tag Reply). From a link timing perspective, the reader then sends a QueryRep command, which instructs all RFID tags to have a SC value of -1. Similarly, tags with a SC of 0 will report RN16. If the EPC is valid, the reader will continue to send the QueryRep command to repeat the above process until all time slots are finished. If the EPC is invalid, the reader can send a NAK (negative acknowledgment) signal.

[0108] As can be seen, in this case, it may not be possible to read all RFID tags within a single Query inventory command. Even if the RFID tags can respond normally to the Query inventory command / QueryRep command, it cannot be guaranteed that every time slot will have an RFID tag reporting (randomly selected time slots may have some time slots that are not selected by any tag). Therefore, the application layer of the reader needs to repeatedly call multiple Query inventory commands to achieve inventory of all tags.

[0109] In some applications, UHF RFID (Ultra High Frequency Radio Frequency Identification) wireless sensing is used. (See [link to relevant documentation]). Figure 2UHF RFID wireless sensing is a wireless sensing mechanism based on channel state information. It achieves target sensing by analyzing changes in the uplink signal characteristics (signal strength and phase) of the passive tags backscattered by the reader, including location tracking, behavior recognition, and vital sign monitoring. For example, when a person wears clothing with tags, the reader periodically reads the tags to obtain the signal characteristic data of the signals returned by each tag, and identifies the person's breathing and heart rate by analyzing changes in the signal characteristic data. In this sensing system, the sensing data is obtained by reading each tag, therefore it is necessary to continuously and periodically read the EPC signals of all sensing tags and obtain the carrier signal strength and phase corresponding to each EPC signal.

[0110] Passive IoT wireless sensing services can generally be divided into two categories: non-binding and binding.

[0111] Non-binding sensing involves deploying a fixed number of pre-configured tags in the environment and identifying people or objects passing by by observing changes in the tag signal characteristics. For example, deploying single tags at 2-meter intervals in a passageway can be used to identify people passing by; deploying a 3x4 tag array on a wall can be used to identify the gait and behavior of people passing by.

[0112] Binding sensing involves attaching a certain number of tags to each sensing object and identifying the state of the sensing object by changes in the characteristics of the tag signals. For example, deploying 3 tags on a human body can detect physiological characteristics such as breathing and heartbeat; deploying 4 tags on a cargo box can detect the orientation of the cargo box.

[0113] In non-bound sensing, the sensing tags are fixed, and the system can know the tag ID (IdentityDocument) in advance and configure it accordingly. Bound sensing is different. Because the sensing tags are bound to the sensing objects, they can dynamically enter and leave the system's working area. For example, in a warehousing scenario, goods with tags affixed may enter and leave the warehouse inventory area, making it impossible for the system to predict the number and IDs of sensing tags within its working area in advance.

[0114] For the aforementioned application scenarios of passive IoT wireless sensing services, the relevant technologies can typically be based on UHF RFID wireless sensing to read the sensing tags. For example:

[0115] 1. The reader continuously stores all tags through the Query inventory command and identifies the sensor tags that have been counted by comparing the tags with the EPC.

[0116] 2. The reader selects all sensor tags using the select command, and then uses the Query command to read the previously selected sensor tags.

[0117] However, if we consider a scenario where bound sensing and inventory counting operations coexist in the system, such as 5 sensing boxes and 10 regular boxes, with each sensing box affixed with 4 sensing tags to identify its orientation, and each regular box affixed with only a single regular tag for inventory counting, the sensing tags need to be periodically counted every 200ms for tag signal feature sampling to identify box orientation. Simultaneously, the system also needs to perform inventory counting tasks for the regular tags. During system operation, each box may dynamically enter and exit the system's working area.

[0118] In the first scheme, the reader continuously stores all tags without distinguishing between sensing and ordinary tags using the Query storage command. Since sensing tags need to be read frequently, ordinary tags will also compete for time slot resources through random competition while being read. Therefore, when there are too many ordinary tags, the sampling rate requirement of sensing tags cannot be met.

[0119] In the second scheme, the reader selects the sensing tag first and then stores it. However, since multiple sensing tags still compete for time slots through a random collision protocol, even if the tags can respond normally, there are still cases where multiple storage operations are required to sample all tags, which affects the synchronization of multi-sensor tag sampling.

[0120] For ease of description, the tags whose tag type corresponds to the first reporting mode are called perception tags, and the tags whose tag type corresponds to the second reporting mode are called ordinary tags.

[0121] Firstly, see [the following] Figure 3 The diagram illustrates a flowchart of a tag data reporting method provided in an embodiment of this application. This method is applicable to tags and includes steps S301-S302, as detailed below:

[0122] S301, receives disk storage messages from the read / write end;

[0123] S302, in response to the inventory message, if it is determined that the tag type of the tag corresponds to the first reporting mode, the first message of the tag is reported to the read / write terminal based at least on parameter information, wherein the parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0124] In this embodiment, tags with high data reading synchronization requirements (i.e., target tags) can choose to adopt the first reporting mode, that is, to complete the reporting of tag data according to the parameter information pre-configured in the tag corresponding to the first reporting mode. This can reduce the probability of time slot conflicts and collisions between tags using the first reporting mode, thereby improving the data reading synchronization of the target tags. For example, the time slot selection can be based on the parameter information of each tag, rather than directly and randomly selected, thus reducing the probability of different tags selecting the same time slot.

[0125] In one example, the tag's parameter information may include the pre-configured initial value SC0 of the time slot counter in the tag. SC0 ​​can be used to indicate the time slot selected by the tag after each receipt of a disk storage message from the reader / writer. Thus, different parameter information may refer to different SC0 values. For example, in the above-mentioned non-binding sensing service, sensing tags that are fixedly deployed in the environment do not dynamically enter or leave the sensing range of the reader / writer, so different SC0 values ​​can be assigned to all sensing tags that are fixedly deployed in the environment. Furthermore, in the above-mentioned binding sensing service, different SC0 values ​​can also be assigned to sensing tags that have entered the sensing range of the reader / writer and have been sensed. When the two types of services are combined, the SC0 values ​​of the sensing tags of the two types of services can also be different.

[0126] In one example, the parameter information for the label may not directly include the SC0 configured for that label. In this case, the parameter information may include some other related parameters that can be used to determine / calculate the SC0 configured for that label (e.g., by calculating SC0 through some predefined functions), thereby achieving the same effect as the previous example.

[0127] In one optional implementation, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0128] At least based on the time slot parameters, determine the time slot counter;

[0129] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0130] In one example, the time slot parameter included in the parameter information can be used to indicate the initial value SC0 of the pre-configured time slot counter in the tag. In this case, the corresponding time slot counter SC can be selected directly according to SC0 to complete the reporting.

[0131] It is understood that the initial value SC0 of the time slot counter described in any embodiment of this application, and the corresponding value (i.e., a certain time slot), can be directly used as the time slot to be selected by the tag. For example, if SC0 = 5, then the time slot counter SC selected by the tag in response to the inventory message is 5. However, the value corresponding to SC0 may not be directly used as the time slot to be selected by the tag, but rather the time slot counter SC selected by the tag in response to the inventory message may be obtained by performing some preset calculations on the value corresponding to SC0. This is not specifically limited here.

[0132] In one optional implementation, the inventory message carries a first number of time slots matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0133] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0134] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0135] It should be noted that the number of first time slots carried in the above inventory message matches the first reporting mode and can be used to indicate the number of time slots reserved for the first reporting mode in this inventory. Since the reader knows the value of the time slot parameter of each sensing tag sensed in the previous inventory (or knows the time slot selected by each sensing tag in the previous inventory) during each inventory, the number of reserved time slots indicated by the number of first time slots is usually not less than the maximum value of the time slots selected by each sensing tag in the previous inventory.

[0136] In one example, the value corresponding to the slot parameter can be the initial value SC0 of the slot counter mentioned above. In this case, the above valid value can refer to a valid slot. Since the tag usually reports data when the slot is 0, the invalid value NULL can be a negative number (e.g., -1).

[0137] In one example, if the value corresponding to the time slot parameter is determined to be a valid value, determining the time slot counter based on the value corresponding to the time slot parameter and the first time slot quantity may include: determining the time slot counter based on the comparison result between the value corresponding to the time slot parameter and the first time slot quantity.

[0138] In one optional implementation, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0139] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0140] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0141] It is understandable that if the value corresponding to the time slot parameter is less than the number of the first time slot, it means that the value corresponding to the time slot parameter of the tag is less than the number of time slots reserved for the first reporting mode as indicated by the number of the first time slot. In other words, the SC0 of the tag is less than the number of time slots reserved for the first reporting mode. At this time, the tag can directly determine the time slot counter by selecting the time slot corresponding to SC0. Correspondingly, when the value of the time slot parameter is not less than the number of the first time slots, that is, when the SC0 of the tag is greater than or equal to the number of time slots reserved for the first reporting mode, it means that the read / write end has not reserved the time slots corresponding to the first reporting mode for the tag to report data. This may be because the tag did not report data during the previous inventory process of the read / write end, resulting in the read / write end not reserving the corresponding time slots for the tag. It may also be that for the read / write end, the data of the tag does not need to be reported through the time slots reserved for the corresponding first reporting mode. For example, for the same tag, the data requirements of different read / write ends may be different. For example, there may be an overlapping reading range between two read / write ends. For a tag in the overlapping area, it may be specified that only one read / write end needs to reserve the time slots corresponding to the first reporting mode for the tag to report.

[0142] In an optional implementation, the inventory message carries a first time slot number matching the first reporting mode, and the method further includes:

[0143] In response to the inventory message, if it is determined that the tag type of the tag corresponds to the second reporting mode, a time slot counter is determined based on the first time slot quantity, and based on the time slot counter, the second message of the tag is reported to the read / write terminal, the second message carrying the data of the tag.

[0144] In one example, since there may be ordinary tags (i.e., tags whose tag type corresponds to the second reporting mode) within the read range of a read / write terminal, ordinary tags can select appropriate time slots for reporting based on the number of first time slots. For example, they can select time slots greater than or equal to the maximum time slot corresponding to the number of first time slots, thereby avoiding time slot conflicts with sensing tags. However, it should be understood that it is not always necessary to select time slots greater than the maximum time slot corresponding to the number of first time slots. In some cases, time slots slightly smaller than the maximum time slot corresponding to the number of first time slots can be selected. Although this cannot completely avoid time slot conflicts with sensing tags, it can avoid a large number of sensing tags, thereby reducing the effect of time slot conflicts with sensing tags. This is not specifically limited here.

[0145] In one optional implementation, determining the time slot counter based on the first time slot number includes:

[0146] Based on the first number of time slots, determine the random time slot interval;

[0147] The time slot counter is selected within the random time slot interval.

[0148] In one example, for a sensing tag whose tag type corresponds to the first reporting mode, if the value of the time slot parameter is invalid, it means that the reader / writer has not reserved the time slot corresponding to the first reporting mode for the sensing tag. In this case, the sensing tag can report through the time slot counter determined based on the number of first time slots, just like ordinary tags.

[0149] In one example, determining random time slot intervals based on the first number of time slots may include: determining at least one random time slot interval based on the first number of time slots, wherein the lower limit of each random time slot interval may be greater than or equal to the maximum time slot corresponding to the first number of time slots; furthermore, the random time slot intervals may not overlap with each other, so that each tag can first randomly select a random time slot interval from different random time slot intervals when reporting, and then randomly select a time slot from the selected random time slot interval for reporting. In this way, the possibility of time slot conflict collisions during tag reporting can be reduced to a certain extent without reserving specific time slots for these tags.

[0150] In an optional implementation, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0151] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0152] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0153] It should be noted that the number of time slots dedicated to the first reporting mode, indicated by the first time slot number, is denoted as SQ, which can be understood as the number of time slots reserved for the first reporting mode. The number of ordinary time slots, indicated by the second time slot number, is denoted as Q, and can be used to indicate all available time slots during this inventory process.

[0154] In one example, the lower limit of the random time slot interval can be the maximum time slot corresponding to the first number of time slots, and the upper limit of the random time slot interval can be 2. Q -1, thus, the random time slot interval in this embodiment can be [SQ, 2 Q -1].

[0155] Furthermore, in one example, see Figure 4 Perceptual tags can use time slots 1-5, while ordinary tags can use time slots after 5.

[0156] In one optional implementation, the read / write terminal is configured with management list information that matches the first reporting mode;

[0157] The first message also carries service type information of the tag that matches the first reporting mode. The first message is adapted to instruct the read / write terminal to perform verification based on the management list information and the service type information of the tag.

[0158] In one example, the aforementioned management list information can be generated and updated by the reader / writer based on the information of each tag read in the previous inventory process (e.g., the last inventory). The management list information may include relevant information of at least some of the tags (e.g., each sensing tag) read in the previous inventory process by the reader / writer. Thus, the tag can be verified by querying the management list information to see if there is relevant information that matches the business type information of the tag. For example, it can be verified whether the tag is a newly added / newly entered sensing tag within the sensing range of the reader / writer.

[0159] In one optional implementation, the read / write terminal performs verification based on the management list information and the service type information of the tag, including:

[0160] The read / write terminal determines whether the tag is a newly added tag corresponding to the first reporting mode based on the management list information and the business type information of the tag. If so, it verifies whether the tag group corresponding to the tag is complete and valid based on the business type information.

[0161] It should be noted that the aforementioned newly added tags can refer to newly added / newly entered sensing tags within the sensing range of the reader / writer.

[0162] In one example, multiple tags using the first reporting mode can form a tag group. For instance, in the aforementioned bound sensing service, multiple tags deployed on the same sensing object (such as four sensing tags affixed to a sensing container to identify the container's orientation) typically require joint analysis of the data from each tag within the same tag group. Therefore, it is generally considered that the data of a tag group is only valid when the data of each tag within it is complete and valid. Here, the service type information can be used to indicate the tag group to which the tag belongs, enabling the reader / writer to determine which tags are included in the tag group. However, it should be understood that the service type information of a tag can also be used to characterize that the tag does not form a tag group with other tags; that is, the tag group to which the tag belongs may contain only that tag.

[0163] In an optional implementation, the first message is further adapted to instruct the read / write terminal to update the management list information based on the service type information.

[0164] In one example, if the tag is determined to be a newly added tag corresponding to the first reporting mode, and the tag group corresponding to the tag is verified to be complete and valid, the business type information corresponding to the tag group can be added to the management list information, thereby updating the management list information. In this embodiment, it is convenient for the read and write terminals to store the relevant information of each newly added and complete tag group in real time.

[0165] In one alternative implementation, at least a portion of the inventory message is determined by the management list information;

[0166] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0167] In one example, the management list information configured on the read / write end can also store parameter information of each sensing tag or the initial value SC0 of the time slot counter of each sensing tag, thereby determining at least the number of first time slots included in each disk storage message sent. Thus, the management list information can also be used to indicate the time slot order of each sensing tag (which can be sorted by SC0). In other words, the management list corresponding to this management list information also records the time slot order of different sensing tags. Further, for the tag group in the above related embodiments, the time slot order of each tag within the same tag group can be continuous. Furthermore, when adding the service type information corresponding to the tag group (i.e., the service type information of each tag within the tag group) to the management list information, the service type information corresponding to the tag group can be uniformly added to the end of the management list corresponding to this management list information. The size relationship (corresponding time slot order) between the initial values ​​SC0 of the time slot counters of each tag within the tag group can be the same as the order of each tag in the management list.

[0168] In one optional implementation, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0169] In one example, the reader / writer can read the tag's EPC from the first message, see [link to example]. Figure 5 In the read EPC, TYPE can be used to represent the service type identifier, and N can be used to represent the service sequence number. At this time, verifying whether the tag group corresponding to the tag is complete and valid based on the service type information can include: verifying whether the tag group corresponding to the tag is complete and valid based on the service type identifier and the service sequence number corresponding to the service type identifier. For example, if the service corresponding to TYPE specifies that three tags need to be affixed to the sensing object, then the completeness and validity of the tag group can be verified by checking whether the received first message corresponding to that TYPE contains a first message with three tags N=1, 2, and 3.

[0170] Furthermore, the sensing tag can have a service type field TYPE, which can be used to indicate whether it is a regular tag or a sensing tag (in other words, the TYPE of the corresponding tag can also be carried in the second message), as well as the sensing service type of the sensing tag (i.e., service type identifier, such as: TYPE=0 for regular tag, 1 for orientation sensing service, and 2 for vital sign sensing service). It can also have a service sequence number field N (e.g., vital sign monitoring sensing service requires 3 tags to be affixed to specific locations on the human body, and should be set to 1, 2, and 3 in a fixed order). TYPE and N can be part of the tag EPC. In the same sensing service, the EPCs of multiple tags required to be affixed to a sensing object should generally be the same except for N. Therefore, the reader can identify how many tags are needed for each sensing object in the sensing service based on the tag's service type field TYPE (e.g., orientation sensing service requires 4 tags, vital sign monitoring sensing service requires 3 tags), and determine whether the group of sensing tags meets the service conditions based on the N value. The reader then uniformly configures the initial value SC0 of the time slot counter for sensing tags that meet the service conditions.

[0171] Secondly, see Figure 6 The diagram illustrates a flowchart of a tag data reporting method provided in an embodiment of this application. The method is applicable to a read / write end and includes step S601, as follows:

[0172] S601, send an inventory message to the tag;

[0173] in,

[0174] The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode;

[0175] The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0176] In one optional implementation, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0177] At least based on the time slot parameters, determine the time slot counter;

[0178] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0179] In one optional implementation, the inventory message carries a first number of time slots matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0180] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0181] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0182] In one optional implementation, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0183] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0184] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0185] In one optional implementation, the inventory message carries a first time slot number that matches the first reporting mode;

[0186] The inventory message is also adapted to instruct the tag, when it is determined that the tag type corresponds to the second reporting mode, to determine a time slot counter based on the first time slot quantity, and to report the second message of the tag to the read / write terminal based on the time slot counter, wherein the second message carries the data of the tag.

[0187] In one optional implementation, determining the time slot counter based on the first time slot number includes:

[0188] Based on the first number of time slots, determine the random time slot interval;

[0189] The time slot counter is selected within the random time slot interval.

[0190] In an optional implementation, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0191] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0192] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0193] In one optional implementation, the read / write terminal is configured with management list information matching the first reporting mode, and the first message also carries service type information of the tag matching the first reporting mode. The method further includes:

[0194] In response to the first message, verification is performed based on the management list information and the business type information of the tag.

[0195] In one optional implementation, the verification based on the management list information and the business type information of the tag includes:

[0196] Based on the management list information and the business type information of the tag, determine whether the tag is a newly added tag corresponding to the first reporting mode. If so, verify whether the tag group corresponding to the tag is complete and valid according to the business type information.

[0197] In one optional implementation, the method further includes:

[0198] Update the management list information based on the business type information.

[0199] In one alternative implementation, at least a portion of the inventory message is determined by the management list information;

[0200] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0201] In one optional implementation, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0202] It is understood that, for specific explanations of the various embodiments of the second aspect, reference can be made to the corresponding embodiments of the first aspect, and the relevant embodiments executed by the read / write end are further explained below.

[0203] In an optional implementation, the management list information is adapted to indicate a first time slot matching the first reporting pattern, the number of tags being one or more, and the method further includes:

[0204] Based on all the first messages reported in response to the inventory message, the time slot occupied by each of the first messages in the first time slot during the reporting process is detected to obtain the detection result;

[0205] Based on the detection results, update the management list information.

[0206] In one optional implementation, the first time slot includes at least one time slot, the management list information includes parameter information for at least one tag whose tag type corresponds to the first reporting mode, the at least one tag corresponds one-to-one with the at least one time slot, and updating the management list information based on the detection result includes:

[0207] If the detection result indicates that there is an unoccupied time slot in the at least one time slot, the management list information is updated based on the parameter information of the tag corresponding to the unoccupied time slot;

[0208] And / or,

[0209] If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, the management list information is updated based on the repeatedly occupied time slot.

[0210] In this embodiment, since the at least one tag corresponds one-to-one with the at least one time slot, each of the at least one tag has a separate time slot for reporting, thereby enabling collision-free reporting of sensing tags in a fixed order.

[0211] In one example, the management list information includes parameter information for at least one tag whose tag type corresponds to the first reporting mode. Here, at least one tag may be a series of sensing tags read by the read / write end during the last inventory process, and the read / write end may assign different SC0s to each sensing tag read, so that the parameter information can be used to indicate the corresponding SC0.

[0212] In some cases, it's easy to understand that some sensing tags can dynamically enter and exit the read range of the read / write terminal. Since at least one tag corresponds one-to-one with at least one time slot, if there is an unoccupied time slot, it indicates that one of the at least one tags has not reported the first message for the inventory message, meaning it usually indicates that one of the at least one tags has left the read range of the read / write terminal. In this case, the tag's parameter information can be deleted from the management list information. Similarly, if there is a time slot that is repeatedly occupied, it means that at least two sensing tags have selected the same time slot (i.e., a repeatedly occupied time slot). Obviously, only one of these at least two sensing tags is included in the at least one tag; that is, the management list information may not include the parameter information of the other sensing tags among these at least two sensing tags, and the SC0 used by the other sensing tag and the read / write terminal has not been mutually defined. In this case, a corresponding SC0 can be assigned to the other sensing tag to add its parameter information to the management list information.

[0213] In one optional implementation, the method further includes:

[0214] If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, a reset disk storage message is generated based on the repeatedly occupied time slot.

[0215] In one example, if there is a time slot that is repeatedly occupied in the at least one time slot, it means that at least two sensing tags have selected the same time slot (i.e., the time slot that is repeatedly occupied), that is, the SC0 used by the at least two sensing tags is the same. This is usually because the other sensing tags among the at least two sensing tags have not mutually defined the SC0 used by the other sensing tags with the read / write end.

[0216] Here, in order to notify the other sensing tag of the SC0 allocated to it, and / or to read all the data of at least two sensing tags using the same time slot, the read / write end can achieve this by resetting the inventory message. Specifically, the number of the repeatedly occupied time slot can be set to the first time slot quantity, and a reset inventory message can be generated to re-initiate the inventory. At the same time, different SC0s can be allocated to at least two sensing tags using the same time slot.

[0217] The various embodiments of this application will be further explained below through specific examples.

[0218] Consider 3 sensing objects and 5 ordinary objects, with TYPE 7 and N values ​​of 1, 2, and 3. Each sensing object is affixed with 3 sensing tags, and the tag EPC is 64 bits. According to... Figure 5 The structure shown has the following EPC settings:

[0219] 1# Perceived Object:

[0220] 1# Perception Tag: 0xFFFF0001 0001 07 01

[0221] #2 Perception Tag: 0xFFFF0001 0001 07 02

[0222] 3# Perception Tag: 0xFFFF0001 0001 07 03

[0223] 2# Perceived Object:

[0224] 1# Perception Tag: 0xFFFF0001 0002 07 01

[0225] 2# Perception Tag: 0xFFFF0001 0002 07 02

[0226] 3# Perception Tag: 0xFFFF0001 0002 07 03

[0227] 3# Perceiving Object:

[0228] 1# Perception Tag: 0xFFFF0001 0003 07 01

[0229] 2# Perception Tag: 0xFFFF0001 0003 07 02

[0230] 3# Perception Tag: 0xFFFF0001 0003 07 03

[0231] The effect of the above configuration is as follows:

[0232] (1) Only objects 1# and 2# exist:

[0233] See Figure 7 The SQ of the sensing tag is 6. The sensing tags of sensing objects #1 and #2 are reported in the sensing time slot in sequence, while ordinary tags are reported in the ordinary time slot.

[0234] (2) The 3# sensing object enters the working area (the reading range of the read / write terminal) and is detected:

[0235] See Figure 8 The SQ of the sensing tag is still 6. Since the sensing tag of sensing object #3 is not configured in SC0, it is randomly reported in the normal time slot, and sensing object #3 is discovered by the reader.

[0236] (3) The tag of the #3 sensing object has been assigned a sensing time slot.

[0237] See Figure 9 The SQ of the sensing tag is changed to 9, and sensing objects #1, #2, and #3 are all reported through the sensing tag time slot.

[0238] (4)2# The sensing object leaves the working area

[0239] See Figure 10 The SQ of the sensing tag is still 9, and the sensing time slots used by the three tags of the #2 sensing object are empty.

[0240] (5) The system removes the sensing time slot configured for sensing object #2.

[0241] See Figure 11 The SQ of the sensing tag is changed to 6, and the sensing tags of sensing objects #1 and #3 are reported in the sensing time slot in sequence.

[0242] In summary, the embodiments of this application can achieve coordinated reporting of EPC data from both sensing tags and ordinary tags when they coexist, ensuring the required time interval and order of sensing tag data sampling. The embodiments of this application can also ensure the priority of sensing tag reporting in some situations, supporting synchronous sampling and dynamic entry / exit management of multiple sensing tags.

[0243] Thirdly, correspondingly, the embodiments of this application also provide a tag data reporting device, which can implement all the processes of the tag data reporting method provided in any of the embodiments of the first aspect above.

[0244] See Figure 12 The diagram shows a schematic representation of a tag data reporting device provided in an embodiment of this application. This device is applicable to tags and includes:

[0245] Command receiving module 1201 is used to receive disk storage messages from the read / write end;

[0246] The first reporting module 1202 is configured to, in response to the inventory message, report a first message of the tag to the read / write terminal based at least on parameter information when it is determined that the tag type of the tag corresponds to the first reporting mode, wherein the parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0247] In one optional implementation, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0248] At least based on the time slot parameters, determine the time slot counter;

[0249] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0250] In one optional implementation, the inventory message carries a first number of time slots matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0251] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0252] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0253] In one optional implementation, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0254] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0255] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0256] In an optional implementation, the inventory message carries a first time slot number matching the first reporting mode, and the device further includes:

[0257] The second reporting module is used to respond to the inventory message, and when it is determined that the tag type of the tag corresponds to the second reporting mode, determine a time slot counter based on the first time slot quantity, and report the second message of the tag to the read / write terminal based on the time slot counter, wherein the second message carries the data of the tag.

[0258] In one optional implementation, determining the time slot counter based on the first time slot number includes:

[0259] Based on the first number of time slots, determine the random time slot interval;

[0260] The time slot counter is selected within the random time slot interval.

[0261] In an optional implementation, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0262] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0263] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0264] In one optional implementation, the read / write terminal is configured with management list information that matches the first reporting mode;

[0265] The first message also carries service type information of the tag that matches the first reporting mode. The first message is adapted to instruct the read / write terminal to perform verification based on the management list information and the service type information of the tag.

[0266] In one optional implementation, the read / write terminal performs verification based on the management list information and the service type information of the tag, including:

[0267] The read / write terminal determines whether the tag is a newly added tag corresponding to the first reporting mode based on the management list information and the business type information of the tag. If so, it verifies whether the tag group corresponding to the tag is complete and valid based on the business type information.

[0268] In an optional implementation, the first message is further adapted to instruct the read / write terminal to update the management list information based on the service type information.

[0269] In one alternative implementation, at least a portion of the inventory message is determined by the management list information;

[0270] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0271] In one optional implementation, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0272] Fourthly, correspondingly, the embodiments of this application also provide a tag data reporting device, which can implement all the processes of the tag data reporting method provided in any of the embodiments of the second aspect above.

[0273] See Figure 13 The diagram shows a schematic of the tag data reporting device provided in an embodiment of this application. This device is suitable for a read / write terminal and includes:

[0274] Command sending module 1301 is used to send inventory messages to the tag;

[0275] in,

[0276] The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode;

[0277] The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

[0278] In one optional implementation, the parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes:

[0279] At least based on the time slot parameters, determine the time slot counter;

[0280] Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

[0281] In one optional implementation, the inventory message carries a first number of time slots matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes:

[0282] If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots;

[0283] If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

[0284] In one optional implementation, determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes:

[0285] If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter;

[0286] If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

[0287] In one optional implementation, the inventory message carries a first time slot number that matches the first reporting mode;

[0288] The inventory message is also adapted to instruct the tag, when it is determined that the tag type corresponds to the second reporting mode, to determine a time slot counter based on the first time slot quantity, and to report the second message of the tag to the read / write terminal based on the time slot counter, wherein the second message carries the data of the tag.

[0289] In one optional implementation, determining the time slot counter based on the first time slot number includes:

[0290] Based on the first number of time slots, determine the random time slot interval;

[0291] The time slot counter is selected within the random time slot interval.

[0292] In an optional implementation, the inventory message further carries a second time slot quantity, wherein the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots, and the step of determining a random time slot interval based on the first time slot quantity includes:

[0293] Based on the first number of time slots, determine the lower limit of the random time slot interval;

[0294] Based on the second number of time slots, the upper limit of the random time slot interval is determined.

[0295] In one optional implementation, the read / write terminal is configured with management list information matching the first reporting mode, and the first message also carries service type information of the tag matching the first reporting mode. The device further includes:

[0296] The verification module is used to perform verification based on the management list information and the business type information of the tag in response to the first message.

[0297] In one optional implementation, the verification based on the management list information and the business type information of the tag includes:

[0298] Based on the management list information and the business type information of the tag, determine whether the tag is a newly added tag corresponding to the first reporting mode. If so, verify whether the tag group corresponding to the tag is complete and valid according to the business type information.

[0299] In one alternative embodiment, the device further includes:

[0300] The first update module is used to update the management list information based on the business type information.

[0301] In one alternative implementation, at least a portion of the inventory message is determined by the management list information;

[0302] At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

[0303] In one optional implementation, the service type information includes a service type identifier and a service sequence number corresponding to the service type identifier.

[0304] In one optional implementation, the management list information is adapted to indicate a first time slot matching the first reporting pattern, the number of tags is one or more, and the device further includes:

[0305] The time slot detection module is used to detect, based on all first messages reported for the disk storage message, the time slot occupied by each of the first messages in the first time slot during the reporting process, and obtain the detection result;

[0306] The second update module is used to update the management list information based on the detection results.

[0307] In one optional implementation, the first time slot includes at least one time slot, the management list information includes parameter information for at least one tag whose tag type corresponds to the first reporting mode, the at least one tag corresponds one-to-one with the at least one time slot, and updating the management list information based on the detection result includes:

[0308] If the detection result indicates that there is an unoccupied time slot in the at least one time slot, the management list information is updated based on the parameter information of the tag corresponding to the unoccupied time slot;

[0309] And / or,

[0310] If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, the management list information is updated based on the repeatedly occupied time slot.

[0311] In one alternative embodiment, the device further includes:

[0312] The reset inventory module is used to generate a reset inventory message based on the repeatedly occupied time slot when the detection result indicates that there is a repeatedly occupied time slot in the at least one time slot.

[0313] Fifthly, embodiments of this application provide a tag data reporting system, including:

[0314] The label is configured to perform the method described in any one of the first aspects above; and,

[0315] The read / write end is configured to perform the method described in any one of the second aspects above.

[0316] In a sixth aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0317] In a seventh aspect, embodiments of this application provide a computer program product, including computer instructions that, when executed by a processor, implement the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0318] Eighthly, embodiments of this application provide a computer device including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the steps of the method described in any one of the first aspects above, or the steps of the method described in any one of the second aspects above.

[0319] See Figure 14 The computer device in this embodiment includes a processor 1401, a memory 1402, and a computer program stored in the memory 1402 and executable on the processor 1401, such as a tag data reporting program. When the processor 1401 executes the computer program, it implements the steps in the various tag data reporting method embodiments described above, for example... Figure 3 Steps S301-S302 shown, or, Figure 6 The step S601 shown.

[0320] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 1402 and executed by the processor 1401 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the computer device.

[0321] The computer device may be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device may include, but is not limited to, a processor 1401 and a memory 1402. Those skilled in the art will understand that the schematic diagram is merely an example of a computer device and does not constitute a limitation on the computer device. It may include more or fewer components than shown, or combine certain components, or different components. For example, the computer device may also include input / output devices, network access devices, buses, etc.

[0322] The processor 1401 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor 1401 can be any conventional processor. The processor 1401 is the control center of the computer device, connecting various parts of the entire computer device through various interfaces and lines.

[0323] The memory 1402 can be used to store the computer programs and / or modules. The processor 1401 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 1402 and calling the data stored in the memory 1402. The memory 1402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 1402 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0324] Wherein, if the modules / units integrated into the computer device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 1401, it can implement the steps of the various method embodiments described above. Wherein, the computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0325] In summary, the embodiments of this application have at least the following beneficial effects:

[0326] By adopting the embodiments of this application, tags with high data reading synchronization requirements (i.e., target tags) can choose to use the first reporting mode, that is, to complete the reporting of tag data according to the parameter information pre-configured in the tag corresponding to the first reporting mode. This can reduce the probability of time slot conflicts and collisions of tags using the first reporting mode, thereby improving the data reading synchronization of the target tags.

[0327] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary hardware platforms, or it can be implemented entirely by hardware. Based on this understanding, all or part of the technical solutions of this application that contribute to the background technology can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM (Read-Only Memory) / RAM (Random Access Memory), magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0328] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications are also considered to be within the scope of protection of this application.

Claims

1. A method for reporting tag data, characterized in that, Applicable to labels, the method includes: Receive inventory messages from the read / write end; In response to the inventory message, if it is determined that the tag type of the tag corresponds to the first reporting mode, the first message of the tag is reported to the read / write terminal based at least on parameter information, wherein the parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

2. The method according to claim 1, characterized in that, The parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes: At least based on the time slot parameters, determine the time slot counter; Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

3. The method according to claim 2, characterized in that, The inventory message carries a first time slot number matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes: If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots; If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

4. The method according to claim 3, characterized in that, The step of determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes: If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter; If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

5. The method according to claim 1, characterized in that, The inventory message carries a first time slot number that matches the first reporting mode, and the method further includes: In response to the inventory message, if it is determined that the tag type of the tag corresponds to the second reporting mode, a time slot counter is determined based on the first time slot quantity, and based on the time slot counter, the second message of the tag is reported to the read / write terminal, the second message carrying the data of the tag.

6. The method according to any one of claims 3-5, characterized in that, The step of determining the time slot counter based on the first time slot number includes: Based on the first number of time slots, determine the random time slot interval; The time slot counter is selected within the random time slot interval.

7. The method according to claim 6, characterized in that, The inventory message also carries a second time slot quantity, whereby the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots. The step of determining a random time slot interval based on the first time slot quantity includes: Based on the first number of time slots, determine the lower limit of the random time slot interval; Based on the second number of time slots, the upper limit of the random time slot interval is determined.

8. The method according to claim 1, characterized in that, The read / write terminal is configured with management list information that matches the first reporting mode; The first message also carries service type information of the tag that matches the first reporting mode. The first message is adapted to instruct the read / write terminal to perform verification based on the management list information and the service type information of the tag.

9. The method according to claim 8, characterized in that, The read / write terminal performs verification based on the management list information and the business type information of the tag, including: The read / write terminal determines whether the tag is a newly added tag corresponding to the first reporting mode based on the management list information and the business type information of the tag. If so, it verifies whether the tag group corresponding to the tag is complete and valid based on the business type information.

10. The method according to claim 8, characterized in that, The first message is also adapted to instruct the read / write terminal to update the management list information based on the service type information.

11. The method according to claim 8, characterized in that, At least a portion of the inventory message is determined by the management list information; At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

12. The method according to any one of claims 8-11, characterized in that, The business type information includes a business type identifier and a business sequence number corresponding to the business type identifier.

13. A method for reporting tag data, characterized in that, Applicable to both read and write ends, the method includes: Send inventory message to the tag; in, The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode; The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

14. The method according to claim 13, characterized in that, The parameter information includes time slot parameters, and the step of reporting the first message of the tag to the read / write terminal based at least on the parameter information includes: At least based on the time slot parameters, determine the time slot counter; Based on the time slot counter, the first message of the tag is reported to the read / write terminal.

15. The method according to claim 14, characterized in that, The inventory message carries a first time slot number matching the first reporting mode, and determining the time slot counter based at least on the time slot parameters includes: If the value corresponding to the time slot parameter is determined to be a valid value, a time slot counter is determined based on the value corresponding to the time slot parameter and the number of the first time slots; If the value corresponding to the time slot parameter is determined to be invalid, the time slot counter is determined based on the number of the first time slots.

16. The method according to claim 15, characterized in that, The step of determining the time slot counter based on the value corresponding to the time slot parameter and the number of the first time slots includes: If the value corresponding to the time slot parameter is less than the first number of time slots, the time slot counter is determined based on the value corresponding to the time slot parameter; If the value corresponding to the time slot parameter is not less than the number of the first time slots, the value corresponding to the time slot parameter is reset to an invalid value.

17. The method according to claim 13, characterized in that, The inventory message carries a first time slot number that matches the first reporting mode; The inventory message is also adapted to instruct the tag, when it is determined that the tag type corresponds to the second reporting mode, to determine a time slot counter based on the first time slot quantity, and to report the second message of the tag to the read / write terminal based on the time slot counter, wherein the second message carries the data of the tag.

18. The method according to any one of claims 15-17, characterized in that, The step of determining the time slot counter based on the first time slot number includes: Based on the first number of time slots, determine the random time slot interval; The time slot counter is selected within the random time slot interval.

19. The method according to claim 18, characterized in that, The inventory message also carries a second time slot quantity, whereby the first time slot quantity is adapted to indicate the number of time slots dedicated to the first reporting mode, and the second time slot quantity is adapted to indicate the number of ordinary time slots. The step of determining a random time slot interval based on the first time slot quantity includes: Based on the first number of time slots, determine the lower limit of the random time slot interval; Based on the second number of time slots, the upper limit of the random time slot interval is determined.

20. The method according to claim 13, characterized in that, The read / write terminal is configured with management list information matching the first reporting mode, and the first message also carries business type information of the tag matching the first reporting mode. The method further includes: In response to the first message, verification is performed based on the management list information and the business type information of the tag.

21. The method according to claim 20, characterized in that, The verification based on the management list information and the business type information of the tag includes: Based on the management list information and the business type information of the tag, determine whether the tag is a newly added tag corresponding to the first reporting mode. If so, verify whether the tag group corresponding to the tag is complete and valid according to the business type information.

22. The method according to claim 20, characterized in that, The method further includes: Update the management list information based on the business type information.

23. The method according to claim 20, characterized in that, At least a portion of the inventory message is determined by the management list information; At least a portion of the inventory message includes a first time slot number that matches the first reporting mode.

24. The method according to any one of claims 20-23, characterized in that, The business type information includes a business type identifier and a business sequence number corresponding to the business type identifier.

25. The method according to any one of claims 20-23, characterized in that, The management list information is adapted to indicate a first time slot matching the first reporting pattern, the number of tags is one or more, and the method further includes: Based on all the first messages reported in response to the inventory message, the time slot occupied by each of the first messages in the first time slot during the reporting process is detected to obtain the detection result; Based on the detection results, update the management list information.

26. The method according to claim 25, characterized in that, The first time slot includes at least one time slot, and the management list information includes parameter information for at least one tag whose tag type corresponds to the first reporting mode. The at least one tag corresponds one-to-one with the at least one time slot. Updating the management list information based on the detection result includes: If the detection result indicates that there is an unoccupied time slot in the at least one time slot, the management list information is updated based on the parameter information of the tag corresponding to the unoccupied time slot; And / or, If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, the management list information is updated based on the repeatedly occupied time slot.

27. The method according to claim 26, characterized in that, The method further includes: If the detection result indicates that there is a time slot that is repeatedly occupied in the at least one time slot, a reset disk storage message is generated based on the repeatedly occupied time slot.

28. A tag data reporting device, characterized in that, Suitable for labels, the device includes: The command receiving module is used to receive disk storage messages from the read / write end; The first reporting module is configured to, in response to the inventory message, report a first message of the tag to the read / write terminal based at least on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode. The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

29. A tag data reporting device, characterized in that, Suitable for read / write terminals, the device includes: The command sending module is used to send inventory messages to the tags; in, The inventory message is adapted to instruct the tag to report the first message of the tag to the read / write terminal, at least based on parameter information, when it is determined that the tag type of the tag corresponds to the first reporting mode; The parameter information is adapted to indicate the parameters of the tag that match the first reporting mode, and the first message carries the data of the tag.

30. A tag data reporting system, characterized in that, include: The label is configured to perform the method described in any one of claims 1-12; as well as, The read / write end is configured to perform the method described in any one of claims 13-27.

31. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1-12, or the method according to any one of claims 13-27.

32. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the method according to any one of claims 1-12, or the method according to any one of claims 13-27.

33. A computer device, characterized in that, The method includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-12, or the method of any one of claims 13-27.

Images