A communication method and related equipment

Abstract

The present invention discloses a communication method for a radio frequency identification (RFID) communication system, including a reader and tags connected to the reader. The method includes: receiving, by the reader, a first message from a tag, where the first message is the first message received by the reader from the tag during an inventory; and identifying, by the reader, different types of tags during the inventory process based on the capabilities proactively reported by the tags.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a communication method and related equipment. Background Art

[0002] In recent years, radio frequency identification (RFID) technology, as an automatic identification technology, has developed rapidly at home and abroad. RFID technology has the advantages of fast reading speed and wide range of application, and is widely used in various fields.

[0003] RFID is a contactless automatic identification technology. An RFID system consists of a reader / writer and tags, leveraging the spatial coupling and transmission characteristics of radio frequency signals to automatically identify stationary or moving objects. RFID can be used to track and manage objects in a wide range of fields. Its high accuracy, long read range, large data storage capacity, and durability make it widely used in production, logistics, and sales.

[0004] However, the reader's interaction process with multiple tags is the same, and during the inventory process, the reader cannot identify different types of tags. Summary of the Invention

[0005] An embodiment of the present application provides a communication method. After a reader receives first information, the reader can determine the capability of the tag based on the first information, and then distinguish the tag from other tags.

[0006] In a first aspect, embodiments of the present application provide a communication method that can be executed by a reader or a component of the reader (e.g., a processor, chip, or chip system). The method is applied to a radio frequency identification communication system, which includes a reader and a tag connected to the reader. The method includes: the reader receiving a first message sent by the tag, where the first message is the first message received by the reader from the tag during an inventory process; and the reader determining the tag's capabilities based on the first message, where the capabilities are used to distinguish the tag from other tags.

[0007] In the embodiment of the present application, after receiving the first information, the reader can determine the capabilities of the tag based on the first information, thereby distinguishing the tag from other tags. The reader can identify different types of tags during the inventory process based on the capabilities actively reported by the tag.

[0008] Optionally, in a possible implementation of the first aspect, the classification corresponding to the capabilities of the tag in the above steps includes at least one of the following: whether the tag is an energy-saving tag; whether the tag is a tag with a transmission distance greater than a threshold; whether the tag is a tag that supports channel coding; whether the tag is a tag that supports modulation; whether the tag is a tag that supports sharing memory with a sensor.

[0009] In this possible implementation, multiple situations of categories corresponding to a tag are provided to facilitate the reader to manage tags of different categories.

[0010] Optionally, in a possible implementation of the first aspect, the capabilities of the tag in the above steps include at least one of the following: commands issued by the reader supported by the tag; channel coding methods supported by the tag; modulation methods supported by the tag; sensor types supported by the tag; the number of sections supported by the tag, sections are used for the reader to manage multiple tags; and the size of the storage space in the tag.

[0011] In this possible implementation, the reader can distinguish the tag from other tags based on the above specific capabilities.

[0012] Optionally, in a possible implementation of the first aspect, the first information in the above steps includes a 16-bit random number and capability information, the 16-bit random number is used for information sent by the tag identification reader to the tag, and the capability information is used to indicate the capability of the tag.

[0013] In this possible implementation, the reader can directly determine the capability of the tag based on the capability information.

[0014] Optionally, in a possible implementation of the first aspect, the first information in the above steps is a 16-bit random number, the 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used for the tag to identify information sent by the reader to the tag; the reader determines the capability of the tag based on the first information, including: the reader determines the capability of the tag based on the first target bit.

[0015] In this possible implementation, the reader determines the capability of the tag according to the first target bit in RN16, and bits including random number information can be saved in subsequent interaction processes.

[0016] Optionally, in a possible implementation manner of the first aspect, the above steps further include: the reader / writer sends second information to the tag, and the random number in the second information does not have the first target bit.

[0017] In this possible implementation, information bits are saved by subtracting the first target bit from the random number.

[0018] Optionally, in a possible implementation manner of the first aspect, the above steps further include: the reader / writer sends second information to the tag, where the second information includes a 16-bit random number.

[0019] Optionally, in a possible implementation of the first aspect, the second information in the above steps includes at least one of the following: confirmation information, which is used by the reader to obtain the factory number of the tag; and random number request information, which is used by the reader to obtain a new 16-bit random number.

[0020] In this possible implementation, the first target bit can be reduced in the confirmation information and random number request information sent by the reader to the tag, thereby reducing the size of the information.

[0021] Optionally, in a possible implementation of the first aspect, the first information in the above steps includes a leading header; and the reader determines the capability of the tag based on the first information, including: the reader determines the capability of the tag based on the leading header.

[0022] In this possible implementation, the reader can determine the capability of the tag based on the leading header of the received information.

[0023] Optionally, in a possible implementation manner of the first aspect, the above steps further include: the reader / writer sends query information to the tag, where the query information is used by the reader / writer to obtain the capability of the tag.

[0024] In this possible implementation, the tag may passively report its capabilities. The tag reports its capabilities to the reader only after the reader sends query information to the tag.

[0025] Optionally, in a possible implementation manner of the first aspect, the above steps further include: if the reader receives multiple first information sent by the tag, the reader merges the multiple first information to improve the coverage of the reader.

[0026] In this possible implementation, the coverage of the reader is improved by repeatedly sending the first information.

[0027] A second aspect of an embodiment of the present application provides a communication method, which can be executed by a tag or a component of the tag (e.g., a processor, chip, or chip system). The method is applied to a radio frequency identification communication system, which includes a reader and a tag connected to the reader. The method includes: the tag sending a first message to the reader, where the first message is the first message sent by the tag to the reader during an inventory process. The first message is used by the reader to determine the tag's capabilities, which are used by the reader to distinguish the tag from other tags.

[0028] In the embodiment of the present application, the tag can actively report the tag's capabilities to the reader, so that the reader can distinguish the tags based on their capabilities.

[0029] Optionally, in a possible implementation of the second aspect, the classification corresponding to the capabilities of the tag in the above steps includes at least one of the following: whether the tag is an energy-saving tag; whether the tag is a tag with a transmission distance greater than a threshold; whether the tag is a tag that supports channel coding; whether the tag is a tag that supports modulation; whether the tag is a tag that supports sharing memory with a sensor.

[0030] In this possible implementation, multiple situations of categories corresponding to a tag are provided to facilitate the reader to manage tags of different categories.

[0031] Optionally, in a possible implementation of the second aspect, the capabilities of the tag in the above steps include at least one of the following: commands issued by the reader supported by the tag; channel coding methods supported by the tag; modulation methods supported by the tag; sensor types supported by the tag; the number of nodes supported by the tag, which are used by the reader to manage multiple tags; and the size of the storage space in the tag.

[0032] In this possible implementation, the reader can distinguish the tag from other tags based on the above specific capabilities.

[0033] Optionally, in a possible implementation of the second aspect, the first information in the above steps includes a 16-bit random number and capability information, the 16-bit random number is used for information sent by the tag identification reader to the tag, and the capability information is used to indicate the capability of the tag.

[0034] In this possible implementation, the reader determines the capability of the tag according to the first target bit in RN16, and bits including random number information can be saved in subsequent interaction processes.

[0035] Optionally, in a possible implementation of the second aspect, the first information in the above steps is a 16-bit random number, the 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used for the tag to identify information sent by the reader to the tag.

[0036] In this possible implementation, information bits are saved by subtracting the first target bit from the random number.

[0037] Optionally, in a possible implementation manner of the second aspect, the above steps further include: the tag receiving second information sent by the reader / writer, and the random number in the second information does not have the first target bit.

[0038] In this possible implementation, information bits are saved by subtracting the first target bit from the random number.

[0039] Optionally, in a possible implementation manner of the second aspect, the above steps further include: the tag receiving second information sent by the reader, where the second information includes a 16-bit random number.

[0040] In this possible implementation,

[0041] Optionally, in a possible implementation of the second aspect, the second information in the above steps includes at least one of the following: confirmation information, which is used by the reader to obtain the factory number of the tag; and random number request information, which is used by the reader to obtain a new 16-bit random number.

[0042] In this possible implementation, the first target bit can be reduced in the confirmation information and random number request information sent by the reader to the tag, thereby reducing the size of the information.

[0043] Optionally, in a possible implementation manner of the second aspect, the first information in the above step includes a leading header, and the leading header is used by the reader to identify capability information of the tag.

[0044] In this possible implementation, the reader can determine the capability of the tag based on the leading header of the received information.

[0045] Optionally, in a possible implementation manner of the second aspect, the above steps further include: the tag receiving query information sent by the reader, where the query information is used by the reader to obtain the capability of the tag.

[0046] In this possible implementation, the tag may passively report its capabilities. The tag reports its capabilities to the reader only after the reader sends query information to the tag.

[0047] Optionally, in a possible implementation manner of the second aspect, the above steps further include: the tag repeatedly executing the step of sending the first information to the reader / writer to increase the transmission range of the first information.

[0048] In this possible implementation, the transmission range of the first information is improved by repeatedly sending the first information.

[0049] A third aspect of an embodiment of the present application provides a reader / writer, which is applied to a radio frequency identification communication system. The radio frequency identification communication system includes a reader / writer and a tag connected to the reader / writer. The reader / writer includes: a receiving unit for receiving a first information sent by the tag, where the first information is the first piece of information sent by the tag received by the reader / writer during an inventory process; and a determination unit for determining a capability of the tag based on the first information, where the capability is used by the reader / writer to distinguish the tag from other tags.

[0050] Optionally, in a possible implementation of the third aspect, the classification corresponding to the capabilities of the above-mentioned tags includes at least one of the following: whether the tag is an energy-saving tag; whether the tag is a tag with a transmission distance greater than a threshold; whether the tag is a tag that supports channel coding; whether the tag is a tag that supports modulation; whether the tag is a tag that supports sharing memory with a sensor.

[0051] Optionally, in a possible implementation of the third aspect, the capabilities of the above-mentioned tag include at least one of the following: commands issued by the reader supported by the tag; channel coding methods supported by the tag; modulation methods supported by the tag; sensor types supported by the tag; the number of sections supported by the tag, sections are used for the reader to manage multiple tags; and the size of the storage space in the tag.

[0052] Optionally, in a possible implementation of the third aspect, the first information includes a 16-bit random number and capability information, the 16-bit random number is used for information sent by the tag identification reader to the tag, and the capability information is used to indicate the capability of the tag.

[0053] Optionally, in a possible implementation of the third aspect, the above-mentioned first information is a 16-bit random number, the 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used for the tag to identify the information sent by the reader to the tag; the determination unit of the above-mentioned reader is specifically used to determine the capability of the tag based on the first target bit.

[0054] Optionally, in a possible implementation manner of the third aspect, the reader / writer further includes: a sending unit, configured to send second information to the tag, wherein the random number in the second information does not have the first target bit.

[0055] Optionally, in a possible implementation manner of the third aspect, the reader / writer further includes: a sending unit, configured to send second information to the tag, where the second information includes a 16-bit random number.

[0056] Optionally, in a possible implementation of the third aspect, the above-mentioned second information includes at least one of the following: confirmation information, which is used by the reader to obtain the factory number of the tag; and random number request information, which is used by the reader to obtain a new 16-bit random number.

[0057] Optionally, in a possible implementation manner of the third aspect, the first information includes a leading header; and the determining unit is specifically configured to determine the capability of the tag according to the leading header.

[0058] Optionally, in a possible implementation manner of the third aspect, the reader / writer further includes: a sending unit, configured to send query information to the tag, where the query information is used by the reader / writer to obtain capabilities of the tag.

[0059] Optionally, in a possible implementation of the third aspect, the reader further includes: a merging unit, configured to merge multiple pieces of first information if the reader receives multiple pieces of first information sent by the tag, so as to improve the coverage of the reader.

[0060] A fourth aspect of an embodiment of the present application provides a tag, which is applied to a radio frequency identification communication system. The radio frequency identification communication system includes a reader and a tag connected to the reader. The tag includes: a sending unit, which is used to send first information to the reader, the first information being the first piece of information sent by the tag to the reader during an inventory process. The first information is used by the reader to determine the capability of the tag, and the capability is used by the reader to distinguish the tag from other tags.

[0061] Optionally, in a possible implementation of the fourth aspect, the classification corresponding to the capabilities of the above-mentioned tags includes at least one of the following: whether the tag is an energy-saving tag; whether the tag is a tag with a transmission distance greater than a threshold; whether the tag is a tag that supports channel coding; whether the tag is a tag that supports modulation; whether the tag is a tag that supports sharing memory with a sensor.

[0062] Optionally, in a possible implementation of the fourth aspect, the capabilities of the above-mentioned tag include at least one of the following: commands issued by the reader supported by the tag; channel coding method supported by the tag; modulation method supported by the tag; sensor type supported by the tag; the number of sections supported by the tag, sections are used for the reader to manage multiple tags; and the size of the storage space in the tag.

[0063] Optionally, in a possible implementation of the fourth aspect, the first information includes a 16-bit random number and capability information, the 16-bit random number is used for information sent by the tag identification reader to the tag, and the capability information is used to indicate the capability of the tag.

[0064] Optionally, in a possible implementation of the fourth aspect, the above-mentioned first information is a 16-bit random number, the 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used for the tag to identify the information sent by the reader to the tag.

[0065] Optionally, in a possible implementation manner of the fourth aspect, the above-mentioned tag further includes: a receiving unit, configured to receive second information sent by the reader / writer, wherein the random number in the second information does not have the first target bit.

[0066] Optionally, in a possible implementation manner of the fourth aspect, the tag further includes: a receiving unit, configured to receive second information sent by the reader, where the second information includes a 16-bit random number.

[0067] Optionally, in a possible implementation of the fourth aspect, the above-mentioned second information includes at least one of the following: confirmation information, which is used by the reader to obtain the factory number of the tag; and random number request information, which is used by the reader to obtain a new 16-bit random number.

[0068] Optionally, in a possible implementation manner of the fourth aspect, the first information includes a leading header, and the leading header is used by the reader to identify capability information of the tag.

[0069] Optionally, in a possible implementation manner of the fourth aspect, the above-mentioned tag further includes: a receiving unit, configured to receive query information sent by a reader / writer, where the query information is used by the reader / writer to obtain capabilities of the tag.

[0070] Optionally, in a possible implementation manner of the fourth aspect, the above-mentioned sending unit is further used to repeatedly execute the step of the tag sending the first information to the reader / writer to improve the transmission range of the first information.

[0071] According to a fifth aspect of an embodiment of the present application, a tag is provided, which is applied to a radio frequency identification communication system. The state machine supported by the tag includes: ready, arbitration, response, confirmation, and safe states, but does not include open and / or inactivated states.

[0072] According to a sixth aspect of an embodiment of the present application, there is provided a tag, which is applied to a radio frequency identification communication system, and the storage space of the tag does not store an access password and / or an inactivation password.

[0073] A seventh aspect of an embodiment of the present application provides a tag, which is applied to a radio frequency identification communication system. The tag supports 2 of the 4 sections, and the sections are used for a reader to manage multiple tags.

[0074] An eighth aspect of an embodiment of the present application provides a reader / writer, wherein the reader / writer or a component of the reader / writer (such as a processor, a chip or a chip system) executes the method in the aforementioned first aspect or any possible implementation of the first aspect.

[0075] A ninth aspect of the embodiments of the present application provides a tag, wherein the tag or a component of the tag (such as a processor, a chip, or a chip system) executes the method in the aforementioned second aspect or any possible implementation of the second aspect.

[0076] The tenth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the method in the aforementioned first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

[0077] The eleventh aspect of the embodiments of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method in the aforementioned first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

[0078] The twelfth aspect of an embodiment of the present application provides a reader / writer, comprising: a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the programs or instructions are executed by the processor, the reader / writer implements the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0079] A thirteenth aspect of an embodiment of the present application provides a tag, comprising: a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the tag implements the method in the above-mentioned second aspect or any possible implementation of the second aspect.

[0080] Among them, the technical effects brought about by the third, eighth, tenth, eleventh, and twelfth aspects or any possible implementation methods thereof can be referred to the technical effects brought about by the first aspect or different possible implementation methods of the first aspect, and will not be repeated here.

[0081] Among them, the technical effects brought about by the fourth, fifth, sixth, seventh, tenth, eleventh, and thirteenth aspects or any possible implementation methods thereof can be referred to the technical effects brought about by the second aspect or different possible implementation methods of the second aspect, and will not be repeated here.

[0082] As can be seen from the above technical solution, the embodiments of the present application have the following advantages: after the reader receives the first information, the reader can determine the capabilities of the tag based on the first information and thus distinguish the tag from other tags. Based on the capabilities actively reported by the tag, the reader can identify different types of tags during the inventory process. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] Figure 1 Schematic diagram of a communication system in an embodiment of the present application;

[0084] Figure 2 A schematic diagram of reader / tag operation and tag status in the prior art;

[0085] Figure 3This is a schematic diagram of the inventory process in RFID;

[0086] Figure 4 A schematic diagram of a tag state machine and signaling operation in the prior art;

[0087] Figure 5 A schematic diagram of the storage space division of a tag in the prior art;

[0088] Figure 6 A flow chart of a communication method provided in an embodiment of the present application;

[0089] Figure 7 Schematic diagram of reader / tag operation and tag status provided in the embodiment of the present application;

[0090] Figure 8 Schematic diagram of the tag state machine and signaling operation provided in the embodiment of the present application;

[0091] Figure 9 A schematic diagram of the storage space division of a tag provided in an embodiment of the present application;

[0092] Figure 10 This is a structural diagram of a reader / writer in an embodiment of the present application;

[0093] Figure 11 This is another structural diagram of the reader / writer in the embodiment of the present application;

[0094] Figure 12 This is a structural diagram of a label in an embodiment of the present application;

[0095] Figure 13 This is another structural diagram of a label in an embodiment of the present application;

[0096] Figure 14 This is another structural diagram of the reader / writer in the embodiment of the present application;

[0097] Figure 15 This is another structural diagram of the label in the embodiment of the present application. DETAILED DESCRIPTION

[0098] An embodiment of the present application provides a communication method. After a reader receives first information, the reader can determine the capability of the tag based on the first information, and then distinguish the tag from other tags.

[0099] The following will describe in detail the implementation principle, specific implementation methods and corresponding beneficial effects of the technical solution of this application in conjunction with the accompanying drawings.

[0100] First, some terms or concepts involved in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0101] RFID technology refers to an automatic identification technology that uses induction, radio waves or microwaves for non-contact two-way communication for the purpose of identification and data exchange. This technology can be used to track and manage all physical objects.

[0102] Figure 1 FIG2 shows an example of an RFID system architecture. The RFID system includes an RFID reader / writer (also referred to as a reader / writer, card reader, etc., hereinafter referred to as a reader / writer) 101 and an RFID tag (hereinafter referred to as a tag) 1102. The RFID reader / writer 101 and the RFID tag 102 can communicate with each other via radio frequency (RF) signals.

[0103] The RFID reader 101 can transmit an inquiry RF signal. The RFID tag 102 located near the RFID reader 101 can detect the inquiry RF signal sent by the RFID reader 101 and return a response RF signal to the RFID reader 101. The response RF signal can carry the relevant information of the RFID tag 102 itself.

[0104] The RFID reader / writer 101 can detect and interpret the response RF signal.

[0105] The tag 102 in the embodiment of the present application can be divided into passive tags, active tags and semi-active tags according to the energy supply method. If the tag 102 is a passive tag, that is, the tag 102 does not have its own power supply, the tag 102 can obtain energy from the interrogation RF signal.

[0106] Active tags, also known as active tags, use an internal battery to power the microchip in whole or in part, but do not provide energy for data transmission between the tag and the transponder. They have a long recognition range (up to 10 meters), but a limited lifespan (3 to 10 years) and are relatively expensive. An active RFID reader can monitor all active tags within a 100-meter range.

[0107] The battery within a semi-passive tag only provides auxiliary support for the voltage required to maintain data within the tag or the operation of the tag chip, and only powers the tag circuits, which consume very little power themselves. Before the tag enters the operating state, it remains dormant, equivalent to a passive tag. The tag's internal battery consumes very little energy, allowing the battery to remain effective for several years, or even up to 10 years. When the tag enters the reader's readout area, it is stimulated by the reader's RF signal. When the tag enters the operating state, the energy supply for information exchange between the tag and the reader is primarily the RF energy supplied by the reader (reflection modulation). The tag's internal battery primarily compensates for the insufficient RF field strength at the tag's location; the energy within the tag's battery is not converted into RF energy.

[0108] Passive tags do not contain batteries. When out of the reader's range, the tag is passive. When within range, it draws power from the RF energy emitted by the reader. Passive tags generally use reflection modulation to transmit tag information to the reader. The practical range of passive tags is approximately 10 centimeters to several meters. While lightweight and compact, they have a long service life, but their transmission range is limited and require high reader / writer transmission power and low transponder operating circuit power consumption.

[0109] It's understandable that RFID tags can be categorized in other ways: active, passive, and semi-active based on their modulation methods. They can be divided into read-only and read-write tags based on whether the stored information can be rewritten. And based on their packaging, they can be divided into credit card tags, linear tags, paper tags, glass tube tags, circular tags, and special-purpose, shaped tags.

[0110] It should be understood that Figure 1 An RFID reader 110 and an RFID tag 120 are shown as examples. Figure 1 In the architecture, one RFID reader 110 can communicate with multiple RFID tags 120, and the RFID system 100 can include multiple RFID readers 110, which is not limited in this embodiment of the present invention.

[0111] The current protocol processing flow of tag 102 is as follows Figure 2 As shown, the labeling work is mainly completed through the state machine jump plus signaling mode.

[0112] Among them, the reader manages the tag group (i.e., multiple tags) through three basic operations: selection, inventory, and access. The tags in the RFID system support seven states: ready, arbitrate, reply, acknowledge, open, secured, and killed.

[0113] The following describes the three basic operations and seven states:

[0114] 1. Selection process.

[0115] The reader selects the number of tags to be inventoried and accessed. The reader issues a select command, which can continuously select a specific number of tags based on user-specified criteria.

[0116] 2. Inventory process.

[0117] There is no difference in the inventory process for the above-mentioned tags 102 of different categories.

[0118] The interrogator identifies the operation of a tag. The interrogator initiates an inventory round by sending a query command in one of four sessions. One or more tags may respond. Responding tags must meet the collision slot 0 to respond to the received inventory command. The response message carries the tag's own RN16. The interrogator detects a single tag response and requests the tag's PC, EPC, and CRC-16.

[0119] like Figure 3 As shown, the inventory includes multiple commands, and the inventory cycle operation can only be performed in one section at a time.

[0120] The inventory includes steps 301 to 307. The following describes each step:

[0121] Step 301: The reader sends a query command to the tag, such as query, adjust query, and repeat query.

[0122] Step 302: The tag sends a 16-bit random number (RN16) to the reader.

[0123] The tag sends RN16 to the reader based on the received query command.

[0124] Step 303: The reader sends an acknowledgement (ACK) message to the tag. The ACK message may carry RN16.

[0125] Step 304: If the RN16 in the ACK message is the same as the RN16 stored in the tag, the tag determines that the ACK message is valid and sends the factory serial number, such as the personal computer (PC) number, extended protocol control (XPC), and electronic product code (EPC), to the reader.

[0126] Step 305: The reader sends a random number request (Req_RN) message to the tag. The Req_RN message may carry RN16.

[0127] Step 306: After the tag receives the Req_RN message, if the access password of Req_RN is not 0, the tag will send a new RN16, ie, a handle, to the reader.

[0128] Step 307: After receiving the new RN16, the reader will carry the new RN16 when sending a command to the tag.

[0129] 3. Access process.

[0130] Communication between a reader and a tag (reading from or writing to a tag). A single tag must be uniquely identified before it can be accessed. Access involves multiple commands, some of which use one-time masking codes based on the reader-to-tag link.

[0131] Currently, the tag 102 supports 7 states. Different reader commands trigger state transitions. The specific signaling and state transition correspondence is as follows: Figure 4 shown.

[0132] The signaling for the reader managing a tag group described above is further explained as follows: When a tag is powered on and unkilled, its state machine is in the Ready state. The tag remains in this state until it receives a query command, and its inventory parameters (the section specified by the query command) and the sel in the query command match the tag's current flag state. A matching tag extracts a bit of data from its random number generator (RNG) and loads it into its slot counter. It then transitions to the Arbitrate state when the slot counter is non-zero and to the Reply state when the slot counter is zero. When a tag enters the Reply state, it responds with an RN16. If the tag receives a valid ACK, it transitions to the Acknowledge state and responds with its PC, EPC, and cyclic redundancy check (CRC)-16. If the tag fails to receive an ACK or receives an invalid ACK, it returns to the Arbitrate state. Tags and reader must meet timing requirements.

[0133] When a tag in the Confirmed state receives a Req_RN command, if its access password is non-zero, it should transition to the Open state and respond with a new RN16 (i.e., handle). The reader will use this handle in subsequent commands, and the tag will use this handle in subsequent responses. A tag in the Open state can execute all access commands except the Lock command. A tag in the Open state can transition to any state except the Confirmed state.

[0134] When a tag in the confirmed state receives a Req_RN command, if its acsess password is zero, it should transition to the secure state and respond with a new RN16, i.e., handle. The reader will use this handle in subsequent commands, and the tag will use this handle in subsequent responses. When a tag in the open state receives a valid access command, if its acsess password is non-zero, it should transition to the secure state and maintain the handle it responded with when it transitioned from the confirmed state to the open state. Tags in the secure state can execute all access commands. Tags in the secure state can transition to any state except the open state and the confirmed state.

[0135] Tags must implement a kill state. When a tag in the open or secure state receives a kill command with a valid, non-zero kill password and a valid handle, it enters the kill state. Killing permanently disables the tag. When entering the kill state, the tag must notify the reader that the kill operation was successful and no longer respond to reader commands. A killed tag must remain in the kill state in all environments and immediately enter the kill state upon power-up. The kill operation is irreversible.

[0136] In the above process, the EPC, access password and other acquisition methods involved are stored in the designated storage space on the tag. Logically, the tag's storage area is divided into four different storage areas, each of which consists of more than one storage word. The logical storage mapping table is as follows: Figure 5 As shown, these memory areas are:

[0137] 1. Reserved storage area (reserved area).

[0138] Used to store passwords required for the kill and access functions (e.g., kill password, access password, etc.). Storage addresses 00h to 1Fh store the kill password, and 20h to 3Fh store the access password. Tags that have not executed the kill password and / or access password are treated as if they have a zero password and are permanently read / write locked. Therefore, there is no need to store a zero password in the password storage area within the reserved memory area.

[0139] 2. Electronic product code storage area (EPC area).

[0140] Addresses 00h to 0Fh store the CRC-16, addresses 10h to 1Fh store the protocol control bits (PC), and addresses 20h and above store the code used to identify the tag's attached object (e.g., the EPC code). The PC is subdivided into sub-bytes: addresses 10h to 14h store the EPC length, 15h to 17h store the RFU, and 18h ​​to 1Fh store the numeric system identifier (NSI). The CRC-16, PC, and EPC are stored with the most significant bit first (the most significant bit of the EPC code is stored at address 20h).

[0141] 3. Tag identification number storage area (TID area).

[0142] An 8-bit class identifier assigned by the International Organization for Standardization (ISO) / International Electrotechnical Commission (IEC) 15693 (EPC global's code is 11100010_2) is stored at addresses 00h to 07h. The TID memory area above address 07h should contain sufficient identifying information to allow the interrogator to uniquely identify the custom commands and / or optional commands supported by the tag. For tags assigned the ISO / IEC 15693 class number 11100010_2, this identifying information consists of a 12-bit tag mask designer identifier (free for EPC global members) and a 12-bit tag model code. The mask designer identifier is stored at addresses 08h to 13h, and the model number is stored at addresses 14h to 1Fh. Tags can store tag- and vendor-specific data (e.g., the tag's serial number) in the TID area above address 1Fh.

[0143] 4. User storage area (user area).

[0144] Allows storage of user-specific data. The storage organization structure of this storage area is defined by the user.

[0145] Tags and readers that comply with the EPC Class 1 Gen 2 (G2) protocol should support eleven essential commands: select, query, queryAdjust, queryRep, ACK, NAK, Req_RN, read, Write, Kill, and Lock.

[0146] Tags and readers that comply with the G2 protocol may or may not support three optional commands: Access, BlockWrite, and BlockErase.

[0147] For the RFID system described above, the reader processes multiple tags in the same way, that is, the reader cannot distinguish between the tags.

[0148] In order to solve the above problem, the present application enables a reader to distinguish a tag from other tags based on the tag's capabilities by reporting its capabilities.

[0149] The following combination Figure 1 communication systems and Figure 3The communication method in the embodiment of the present application is described as follows:

[0150] See also Figure 6 The communication method provided in the embodiments of the present application can be applied to an RFID communication system. An embodiment of the communication method includes:

[0151] Step 601: The reader sends query information to the tag. This step is optional.

[0152] Optionally, to avoid RN16 collisions when there are multiple tags, the reader can classify them by their capabilities. This can reduce the probability of RN16 collisions when tags of different categories approach the reader. Alternatively, the reader can obtain the specific capabilities of the tags to distinguish between tags with different capabilities, facilitating subsequent tag management.

[0153] The reader sends query information to the tag, which is used by the reader to obtain the tag's capabilities.

[0154] There are many ways to classify the capabilities of tags in the embodiments of this application. The following are a few examples for schematic description:

[0155] 1. Whether the label is an energy-saving label;

[0156] Optionally, an energy-saving tag can be understood as at least one of the following: the tag reduces certain unnecessary commands (explained below), the tag state machine has no open and / or kill state, the tag's reserved storage area is empty, the number of tag support nodes is less than 4 (described in detail below), etc.

[0157] 2. Whether the tag has a transmission distance greater than the threshold;

[0158] Alternatively, a tag with a transmission distance greater than a threshold can be understood as a tag with a wide transmission range, and the tag can increase the coverage of the reverse link by channel coding the information or repeatedly sending the information. The reverse link is the link from the tag to the reader.

[0159] Optionally, for capabilities that the tag can actively turn on or off (for example, channel coding capabilities), if the reader does not turn on these capabilities at the beginning, the reader does not perceive the tag's channel coding capabilities. The tag can add a specific leading header to the information to allow the reader to know the channel coding method used for the information.

[0160] Optionally, for capabilities that the tag can actively enable or disable, these capabilities may be enabled with a delay. Whether the tag uses the capability after sending the first information may be a default setting or may depend on the configuration of the tag by the reader.

[0161] If the information is sent repeatedly, the reader can perform blind detection and merge multiple messages, thereby improving the coverage of the reader.

[0162] 3. Whether the tag supports channel coding;

[0163] 4. Whether the tag supports modulation;

[0164] 5. Check whether the tag supports sharing memory with the sensor.

[0165] Optionally, the sensor can be a light sensor, a thermal sensor, or other different types of sensors. For example, using a thermal sensor, the reader can monitor and trigger an alarm based on the tag's attached object. Specifically, upon learning that the tag supports shared memory with the sensor, the reader can configure a threshold for the tag. When the temperature value stored in the tag exceeds the threshold, an alarm is triggered.

[0166] Optionally, the memory shared by the tag and the sensor can be the above Figure 5 At least one of the four storage areas shown, for example, the memory shared by the tag and the sensor is a user storage area (user area).

[0167] It is understandable that the above-mentioned classification methods are only examples. In actual applications, other classification methods corresponding to label capabilities can be set as needed, and the specifics are not limited here.

[0168] In the embodiment of the present application, the capabilities of the tag can be divided into the capability to support the protocol stack, the capability of the PHY layer, the capability of storage, etc., which are not specifically limited here.

[0169] The specific capabilities of the tags in the embodiments of this application include various capabilities, which are briefly described below with a few examples:

[0170] 1. The tags support the commands issued by the reader (which can also be understood as capabilities related to the air interface);

[0171] Optionally, the command includes mandatory commands and optional commands.

[0172] Among them, the necessary commands may include: select, query, queryAdjust, queryRep, ACK, NAK, Req_RN, read, Write, Kill, Lock, etc., which are not limited here.

[0173] Optional commands may include: Access, BlockWrite, BlockErase, etc., which are not specifically limited here.

[0174] A tag may support mandatory commands but not optional commands, or may support mandatory commands and at least one of the optional commands.

[0175] Optionally, if the first information sent by the tag to the reader is RN16, the first target bit in RN16 is used to indicate the tag's capabilities. The first target bit can be reduced in subsequent information including random numbers transmitted between the reader and the tag. That is, compared to the 16-bit first target bit in the prior art, the first target bit can be reduced by 1 bit or less, thereby saving the amount of information transmitted over the air interface.

[0176] 2. Channel coding method supported by the tag;

[0177] Optionally, the channel coding method may include a low-density parity-check (LDPC) code, a polar code, or other coding methods, which are not specifically limited here.

[0178] 3. Modulation methods supported by the tag;

[0179] Optionally, the modulation method may include amplitude modulation, frequency modulation, phase modulation, and may also include specific modulation methods such as differential phase shift keying (DPSK) or quadrature amplitude modulation (QAM), which are not specifically limited here.

[0180] 4. Sensor types supported by the tag;

[0181] Optionally, the type of the sensor may be a light sensor, a thermal sensor, etc., which is not specifically limited here.

[0182] 5. The number of sections supported by the tag. Sections are used by the reader to manage multiple tags.

[0183] Currently, the tag supports two sections, which can be session0 and session2, session1 and session3, session0 and session1, session2 and session3, etc. There is no specific limitation here.

[0184] That is, the reader can know which section the tag supports, and thus can make tags supporting different sections be inventoried separately, reducing collisions between tags.

[0185] 6. Storage space in tags.

[0186] Optionally, the storage space in the tag may refer to whether the storage space in the tag is as described above. Figure 5 As shown, the tag includes several storage areas. The storage space in the tag can also refer to whether the storage space in the tag stores an access password and / or an inactivation password, etc. If the tag does not support certain sections, the storage space in the tag can also not store the flag bits of certain sections. The specific details are not limited here.

[0187] 7. State machine states supported by the tag.

[0188] Optionally, the state machine state supported by the tag may refer to whether the tag supports a certain state, or whether the tag does not support a certain state.

[0189] Illustratively, the state machine state that the tag does not support may be the Open state and / or the Killed state.

[0190] It is understandable that the several specific capabilities of the above-mentioned tags are only examples. In actual applications, tags may also include other forms of specific capabilities, which are not specifically limited here.

[0191] Step 602: The tag sends first information to the reader.

[0192] The tag can actively report the first information (for example, reporting the first information once at a certain interval) or passively report the first information (ie, the tag sends the first information to the reader after receiving the query information sent by the reader), which is not limited here.

[0193] In the embodiment of the present application, the first information has multiple forms, which are described below:

[0194] 1. The first information includes RN16, which is used to indicate the classification of the tag or the specific capabilities of the tag (it can also be understood that the reader can identify the capabilities of the tag based on the first information). The RN16 is used by the tag to identify its own information from the broadcast information of the reader (it can also be understood that RN16 is used by the tag to identify the information sent to it by the reader).

[0195] Optionally, the first information may include RN16 and capability information, where the capability information is used to indicate the classification of the tag or the specific capability of the tag.

[0196] Optionally, the first information sent by the tag is a user-specific control command.

[0197] Optionally, if the first information is used to indicate the classification of a tag, the tag can be divided into different categories based on the minimalist characteristics of the tag. For example, category 0 and category 1 are divided into categories, where category 0 represents a normal tag and category 1 represents a minimalist tag. The capability of the minimalist tag can be at least one of the multiple capabilities described in step 602. The specific classification of the tag is not limited here.

[0198] Illustratively, a format of the first information may be as shown in Table 1:

[0199] Table 1

[0200]

[0201] The tag type is indicated by adding 1 bit, 0 represents a normal tag, and 1 represents a minimalist tag. Of course, 0 can also represent a minimalist tag and 1 represents a normal tag, which is not limited here.

[0202] In the embodiment of the present application, the category of the tag can also be indicated in a multi-bit manner, which is not limited here.

[0203] Optionally, if the tag is classified as whether it supports channel coding capability, the first information may indicate to the reader whether the tag supports channel coding capability in the form of one or more bits. For example, tags are divided into tags that support channel coding capability (support) and tags that do not support channel coding capability (not support).

[0204] Illustratively, another format of the first information may be as shown in Table 2:

[0205] Table 2

[0206]

[0207] Among them, by adding 1 bit to indicate whether the tag supports channel coding capability, 0 indicates no support for channel coding capability, and 1 indicates support for channel coding capability. Of course, 0 can also indicate support for channel coding capability and 1 indicates no support for channel coding capability, which is not limited here.

[0208] In the embodiment of the present application, whether the tag supports channel coding capability can also be indicated in a multi-bit manner, which is not limited here.

[0209] Optionally, if the first information is used to indicate the specific capabilities of the tag, the first information may identify the capabilities of the tag by one or more bits. The capabilities of the tag may be at least one of the multiple capabilities described in the aforementioned step 602, and the details will not be repeated here.

[0210] 2. The first information is RN16, which includes a first target bit and a second target bit. The first target bit is used to indicate the tag's capability, and the second target bit is used for the tag to identify its own information from the reader's broadcast information (it can also be understood that the second target bit is used for the tag to identify the information sent to it by the reader).

[0211] In the embodiment of the present application, the number of bits occupied by the first target bit and the second target bit can be one or more. The following is a schematic illustration using only one bit as an example, and no specific limitation is made here.

[0212] Optionally, one or several bits in RN16 are used to indicate the category information of the label.

[0213] For example, the first bit in RN16 is used to indicate whether the tag is a normal tag or a minimalist tag, 0 for a normal tag and 1 for a minimalist tag. Of course, 0 can also indicate a minimalist tag and 1 for a normal tag.

[0214] Exemplarily, the second bit in RN16 is used to indicate whether the tag supports channel coding capability, 0 indicates that the tag does not support the channel coding capability, and 1 indicates that the tag supports the channel coding capability.

[0215] Optionally, the first bit in RN16 is used to indicate the specific capability of the tag, 0 indicates that the capability of a certain category is not supported, and 1 indicates that the capability of a certain category is supported. The capability of the category can refer to the description of the capability in step 601 above, and will not be repeated here.

[0216] In the embodiments of the present application, the first information has multiple forms, and the above forms are just examples. In actual applications, the first information may have other forms, which are not specifically limited here.

[0217] In one possible design, the reader / writer can increase the transmission range of the first information. In the embodiment of the present application, there are multiple ways for the tag to increase the transmission range of the first information, which are described below:

[0218] 1. The tag supports channel coding capabilities.

[0219] Optionally, the leading headers of the first information sent by the tag supporting the channel coding capability and the tag not supporting the channel coding capability are different.

[0220] For example, the first message is encoded using a supported capability, such as polar coding. The preamble of the first message is different from the preamble of tags that do not support channel coding capabilities, allowing the reader to identify that the message uses a different encoding method. The reader and tag capabilities can be aligned by default, or the reader can indicate in broadcast commands such as Select and Query that specific channel coding capabilities are required or that only tags with certain capabilities can use a special preamble. Alternatively, multiple preambles can be indicated to support different channel coding capabilities.

[0221] Optionally, for tags with certain capabilities, after the tags report the capabilities, they may be enabled by default, or the reader may send a start indication command through proprietary signaling in subsequent communications with the reader.

[0222] For example, when the capability is channel coding capability, a feature of the command may be as shown in Table 3:

[0223] Table 3

[0224]

[0225] The commands between the reader and the tag can include ChannelENcode and ChannelENcodeRely. ChannelENcode is the control information sent by the reader to the tag, and ChannelENcodeRely is the tag's response to this control information. Code is the code, Length is the length (e.g., number of bits), Mandatory Command indicates whether the information is mandatory, and ReplyType indicates whether the message requires a delayed reply, among other characteristics. These are not specifically defined here.

[0226] For example, the format of the control information sent by the reader to the tag may be as shown in Table 4:

[0227] Table 4

[0228]

[0229] The "various" field indicates a variable length. The "various" field may include channel coding parameters, such as bit rate, coding mode, and configuration, which are not specifically defined here. The value "0" indicates disabled, and the value "1" indicates enabled. Alternatively, the value "0" may indicate enabled, and the value "1" may indicate disabled, which are not specifically defined here.

[0230] For example, the reply message sent by the tag to the reader can carry a new RN16 as a new handle for subsequent processing of messages with channel coding. The format of the reply message can be as shown in Table 5:

[0231] Table 5

[0232]

[0233] Here, various indicates a variable length, and the various length content may include channel coding parameters, such as code rate, coding mode, configuration, etc., which are not specifically limited here.

[0234] 2. The tag does not support the channel coding capability or the tag does not enable the channel coding capability, that is, the first information is sent repeatedly.

[0235] In the embodiment of the present application, there are multiple situations in which the first information is repeatedly sent, which are described below respectively:

[0236] 1. The tag repeatedly sends the first information to the reader, that is, the tag sends the first information to the reader multiple times.

[0237] 2. The tag repeats the data of the first information and sends it to the reader / writer. That is, the first information includes multiple repeated data, which can be bit-level repetitions or block repetitions.

[0238] In the embodiment of the present application, there are many situations in which the reader can improve the transmission range of the first information. The above are just examples. In actual applications, there are other ways in which the reader can improve the transmission range of the first information, which are not limited here.

[0239] Step 603: The reader determines the capability of the tag according to the first information.

[0240] After receiving the first information, the reader / writer can determine the capability of the tag according to the first information.

[0241] Optionally, the reader can instruct the tag how to report the tag's capabilities through preset rules or through broadcast commands such as Select and Query.

[0242] If the format of the first information is as in the first case above, that is, the first information includes RN16 and capability information, since the capability information is used to indicate the capability of the tag, the reader can determine the capability of the tag according to the capability information.

[0243] If the format of the first information is as in the second case above, that is, the first information is RN16, which includes a first target bit and a second target bit, the reader can determine the capability of the tag according to the first target bit.

[0244] Optionally, the reader can also determine the capability of the tag based on the leading header of the first information. For example, only tags that support a certain capability can use a specific leading header in the first information sent.

[0245] Exemplarily, the preamble of the first information sent by the tag supporting the channel coding capability is different from the preamble of the first information sent by the tag not supporting the channel coding capability.

[0246] Optionally, if the reader receives multiple first information sent by the tag and the first information is not encoded, the reader performs blind detection and merges the multiple first information to improve the coverage of the reader.

[0247] Optionally, if the tag reports a category classification, the reader can also configure the tag to instruct the tag which specific capability to use.

[0248] For example, if the reader determines that the tag supports channel coding capability and the tag supports LDPC code and polar code, the reader can configure the tag to instruct the tag to use LDPC code or polar code.

[0249] Step 604: The reader sends the second information to the tag.

[0250] After the reader / writer determines the capability of the tag, it may send the second information to the tag.

[0251] In the embodiment of the present application, the second information may include confirmation information (i.e., ACK information), random number request information (i.e., Req_RN), etc. The confirmation information is used by the reader to obtain the tag's factory serial number (e.g., PC, XPC, EPC, etc.). The random number request information is used by the reader to obtain a new 16-bit random number (also called a handle).

[0252] Alternatively, if the tag reports its capability in an implicit manner, the second information may include RN16, or the random number in the second information may not include the first target bit (ie, the first information includes an incomplete RN16).

[0253] Equivalently, if the first target bit in RN16 is used to indicate the capability of the tag, after receiving the first information, the reader can determine whether the first target bit is 0 or 1. When the reader subsequently sends information to the tag, or when the tag sends information to the reader, the first target bit can be saved, thereby saving energy consumption.

[0254] Optionally, after the reader distinguishes the categories of tags, it can achieve multi-functional management of multiple tags through the combination of some commands. For example, it can select a certain type of tag through Select, and then inventory the tags of this type through Query, thereby achieving multi-functional management of the tag group.

[0255] In the embodiment of the present application, the reader can determine the capabilities of the tag based on the first information reported by the tag, and can then distinguish multiple tags and perform different operations on tags with different capabilities. This avoids the existing technology where the interaction process between the reader and all tags is the same, which prevents tags that can save energy from saving energy.

[0256] The embodiment of the present application also provides a tag (which may be called an energy-saving tag), which is applied to an RFID system. The state machine supported by the tag includes: ready, arbitration, response, confirmation, and safe states, but does not include open and / or inactivated states.

[0257] The embodiment of the present application further provides a tag (which may be called an energy-saving tag), which is applied to an RFID system, and the storage space of the tag does not store an access password and / or an inactivation password.

[0258] like Figure 7 As shown in the figure, some optional signaling is no longer supported, such as Access. After the open state is no longer available, there will be no command from Open to Secured. Some alternative signaling is no longer supported, such as Kill. Among them, Open and Killed states are not supported in energy-saving tags, which reduces two state machine jumps on the tag and reduces at least two types of air interface message logic processing. After the state machine is trimmed, Figure 8 When the tag is in the confirmation state, if the received Req_RN is valid, it will directly enter the safe state. If the received Req_RN is invalid, it will not respond.

[0259] Of course, at least one of the two state machines (Open state and Killed state) may also be cut, and the specific details are not limited here.

[0260] If the energy-saving tag is switched to the Open state, the access password does not need to be saved. If the energy-saving tag is switched to the Killed state, the deactivation password does not need to be saved. This saves the tag's storage space.

[0261] Optionally, if the tag cuts out the Open state and Killed state, that is, there is no need to save the access password and the kill password, the storage space of the energy-saving tag is as follows: Figure 9 shown.

[0262] The embodiment of the present application further provides a tag (which may be called a minimalist tag), which is applied to an RFID system. The tag supports two of the four sessions, which are used by a reader to manage multiple tags.

[0263] Minimalist tags or support one of session0 and session2, session1 and session3, session0 and session1, session2 and session3, etc.

[0264] Optionally, the two bits in the Session field of the response Query can be used to indicate which two sections the minimalist tag supports. For example, 00 in the Session field of the Query indicates session 0, 01 indicates session 1, 10 indicates session 2, and 11 indicates session 3. Therefore, a Session of X0 indicates that the energy-saving tag supporting session 0 and session 2 is selected. That is, the last digit of both session 0 and session 2 is 0.

[0265] When a tag identifies a session it does not support, it does not need to query its own session status flag and can directly wait for the next inventory message, thereby saving the tag's energy consumption.

[0266] The communication method in the embodiment of the present application is described above. The reader / writer in the embodiment of the present application is described below. Figure 10 , an embodiment of the reader / writer in the embodiment of the present application includes:

[0267] The receiving unit 1001 is configured to receive first information sent by a tag, where the first information is the first piece of information received by the reader during the inventory process.

[0268] The determining unit 1002 is configured to determine the capability of the tag according to the first information. The capability is used by the reader to distinguish the tag from other tags.

[0269] In this embodiment, the operations performed by each unit in the reader are the same as those described above. Figure 6 The description in the illustrated embodiment is similar and will not be repeated here.

[0270] In this embodiment, after the receiving unit 1001 receives the first information, the determining unit 1002 may determine the capability of the tag according to the first information, and further distinguish the tag from other tags.

[0271] See also Figure 11 Another embodiment of the reader / writer in the embodiment of the present application includes:

[0272] The receiving unit 1101 is configured to receive first information sent by a tag, where the first information is the first piece of information received by the reader during the inventory process.

[0273] The determining unit 1102 is configured to determine the capability of the tag according to the first information. The capability is used by the reader to distinguish the tag from other tags.

[0274] The reader / writer in this embodiment also includes:

[0275] The sending unit 1103 is configured to send second information to the tag, where the random number in the second information does not have the first target bit.

[0276] The sending unit 1103 is configured to send second information to the tag, where the second information includes a 16-bit random number.

[0277] The sending unit 1103 is used to send query information to the tag, and the query information is used by the reader to obtain the capability of the tag.

[0278] The merging unit 1104 is configured to merge the plurality of first information sent by the tag if the reader receives a plurality of first information, so as to improve the coverage of the reader.

[0279] In this embodiment, the operations performed by each unit in the reader are the same as those described above. Figure 6 The description in the illustrated embodiment is similar and will not be repeated here.

[0280] In this embodiment, after the receiving unit 1101 receives the first information, the determining unit 1102 can determine the capability of the tag according to the first information, thereby distinguishing the tag from other tags. The sending unit 1103 can enable the tag to report the capability of the tag.

[0281] The following describes the labels in the embodiment of the present application. Figure 12 , an embodiment of the label in the embodiment of the present application includes:

[0282] The sending unit 1201 is used to send first information to the reader. The first information is the first information sent by the tag to the reader during the inventory process. The first information is used by the reader to determine the capability of the tag, and the capability is used by the reader to distinguish the tag from other tags.

[0283] In this embodiment, the operations performed by each unit in the tag are the same as those described above. Figure 6 The description in the illustrated embodiment is similar and will not be repeated here.

[0284] In this embodiment, the sending unit 1201 can report the capabilities of the tags to the reader, so that the reader can distinguish the tags according to their capabilities.

[0285] See also Figure 13 Another embodiment of the label in the embodiment of the present application includes:

[0286] The sending unit 1301 is used to send first information to the reader. The first information is the first information sent by the tag to the reader during the inventory process. The first information is used by the reader to determine the capability of the tag, and the capability is used by the reader to distinguish the tag from other tags.

[0287] The tags in this embodiment also include:

[0288] The receiving unit 1302 is configured to receive second information sent by the reader / writer, wherein the random number in the second information does not have the first target bit.

[0289] The receiving unit 1302 is configured to receive second information sent by the reader / writer, where the second information includes a 16-bit random number.

[0290] The receiving unit 1302 is used to receive query information sent by the reader, and the query information is used by the reader to obtain the capability of the tag.

[0291] In this embodiment, the operations performed by each unit in the tag are the same as those described above. Figure 6 The description in the illustrated embodiment is similar and will not be repeated here.

[0292] In this embodiment, the sending unit 1301 can report the tag capabilities to the reader, so that the reader can distinguish tags according to their capabilities. Further, after receiving the query information, the sending unit 1301 can report the tag capabilities to the reader.

[0293] See also Figure 14 , is a possible schematic diagram of the reader / writer 1400 involved in the above-mentioned embodiments provided in an embodiment of the present application. The reader / writer 1400 can specifically be the reader / writer in the aforementioned embodiments. The reader / writer 1400 can include but is not limited to a processor 1401, a communication port 1402, a memory 1403, and a bus 1404. In the embodiment of the present application, the processor 1401 is used to control and process the actions of the reader / writer 1400.

[0294] In addition, processor 1401 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0295] It should be noted that Figure 14 The reader / writer shown can be used to implement Figure 6 The functions of the steps performed by the reader / writer in the corresponding method embodiment and the corresponding technical effects of the reader / writer are achieved. Figure 14 The specific implementation of the reader can refer to Figure 6 The descriptions in the corresponding method embodiments will not be repeated here one by one.

[0296] See also Figure 15 , is a possible schematic diagram of the tag 1500 involved in the above-mentioned embodiments provided in an embodiment of the present application. The tag 1500 can specifically be the tag in the aforementioned embodiment. The tag 1500 can include but is not limited to a processor 1501, a communication port 1502, a memory 1503, and a bus 1504. In the embodiment of the present application, the processor 1501 is used to control and process the actions of the tag 1500.

[0297] In addition, processor 1501 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0298] It should be noted that Figure 15 The tags shown can be used to implement Figure 6 The functions of the steps performed by the labels in the corresponding method embodiments and the technical effects corresponding to the labels are achieved. Figure 15 For the specific implementation of the tags shown, please refer to Figure 6 The descriptions in the corresponding method embodiments will not be repeated here one by one.

[0299] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0300] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0301] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0302] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0303] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Claims

1. A communication method, characterized in that: The method is applied to a radio frequency identification communication system, the radio frequency identification communication system including a reader and a tag connected to the reader, and the method includes: The reader receives first information sent by the tag, where the first information is the first piece of information sent by the tag received by the reader during the inventory process; the first information includes a 16-bit random number, which is used by the tag to identify the information sent by the reader to the tag; The reader / writer determines the capability of the tag according to the first information, and the capability is used by the reader / writer to distinguish the tag from other tags.

2. The method according to claim 1, characterized in that The capabilities of the tag are classified into at least one of the following categories: whether the tag is an energy-saving tag; Whether the tag is a tag with a transmission distance greater than a threshold; Whether the tag is a tag that supports channel coding; Whether the tag is a tag that supports modulation; Whether the tag supports sharing memory with the sensor.

3. The method according to claim 1, characterized in that The tag's capabilities include at least one of the following: The tag supports commands issued by the reader; The channel coding mode supported by the tag; The modulation mode supported by the tag; The sensor types supported by the tag; The number of sections supported by the tag, the sections being used by the reader to manage multiple tags; The amount of storage space in the tag.

4. The method according to claim 1, wherein The first information includes the 16-bit random number and capability information, where the capability information is used to indicate the capability of the tag.

5. The method according to claim 1, wherein The 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used by the tag to identify the information sent by the reader to the tag; The reader determines the capability of the tag according to the first information, including: The reader / writer determines the capability of the tag according to the first target bit.

6. The method according to claim 5, characterized in that The method further comprises: The reader / writer sends second information to the tag, where the random number in the second information does not have the first target bit, or the second information includes the 16-bit random number.

7. The method according to claim 6, characterized in that The second information includes at least one of the following: Confirmation information, the confirmation information is used by the reader to obtain the factory serial number of the tag; Random number request information, where the random number request information is used by the reader to obtain a new 16-bit random number.

8. The method according to any one of claims 1 to 7, characterized in that The first information includes a leading header; The reader determines the capability of the tag according to the first information, including: The reader / writer determines the capability of the tag according to the leading header.

9. The method according to any one of claims 1 to 7, characterized in that Before the reader receives the first information sent by the tag, the method further includes: The reader sends query information to the tag, where the query information is used by the reader to obtain the capability of the tag.

10. The method according to any one of claims 1 to 7, characterized in that The method further comprises: If the reader receives multiple pieces of the first information sent by the tag, the reader combines the multiple pieces of the first information to improve the coverage of the reader.

11. A communication method, characterized in that: The method is applied to a radio frequency identification communication system, the radio frequency identification communication system including a reader and a tag connected to the reader, and the method includes: The tag sends first information to the reader / writer. The first information is the first information sent by the tag to the reader / writer during the inventory process. The first information is used by the reader / writer to determine the capability of the tag. The first information includes a 16-bit random number. The 16-bit random number is used by the tag to identify the information sent by the reader / writer to the tag; the capability is used by the reader / writer to distinguish the tag from other tags.

12. The method according to claim 11, characterized in that The capabilities of the tag are classified into at least one of the following categories: whether the tag is an energy-saving tag; Whether the tag is a tag with a transmission distance greater than a threshold; Whether the tag is a tag that supports channel coding; Whether the tag is a tag that supports modulation; Whether the tag supports sharing memory with the sensor.

13. The method according to claim 11, characterized in that The tag's capabilities include at least one of the following: The tag supports commands issued by the reader; The channel coding mode supported by the tag; The modulation mode supported by the tag; The sensor types supported by the tag; The number of sections supported by the tag, the sections being used by the reader to manage multiple tags; The amount of storage space in the tag.

14. The method according to claim 11, characterized in that The first information includes the 16-bit random number and capability information, where the capability information is used to indicate the capability of the tag.

15. The method according to claim 11, characterized in that The 16-bit random number includes a first target bit and a second target bit, the first target bit is used to indicate the capability of the tag, and the second target bit is used by the tag to identify information sent by the reader to the tag.

16. The method according to claim 15, characterized in that The method further comprises: The tag receives second information sent by the reader / writer, where the random number in the second information does not have the first target bit, or the second information includes the 16-bit random number.

17. The method according to claim 16, characterized in that The second information includes at least one of the following: Confirmation information, the confirmation information is used by the reader to obtain the factory serial number of the tag; Random number request information, where the random number request information is used by the reader to obtain a new 16-bit random number.

18. The method according to any one of claims 11 to 17, characterized in that The first information includes a leading header, and the leading header is used by the reader to identify capability information of the tag.

19. The method according to any one of claims 11 to 17, characterized in that Before the tag sends the first information to the reader, the method further includes: The tag receives the query information sent by the reader / writer, and the query information is used by the reader / writer to obtain the capability of the tag.

20. The method according to any one of claims 11 to 17, characterized in that The method further comprises: The tag repeatedly performs the step of sending the first information to the reader / writer to increase the transmission range of the first information.

21. A reader / writer, characterized in that: The reader / writer is applied to a radio frequency identification communication system, which includes the reader / writer and a tag connected to the reader / writer. The reader / writer includes: a receiving unit, configured to receive first information sent by the tag, the first information being the first piece of information received by the reader from the tag during an inventory process; the first information comprising a 16-bit random number, the 16-bit random number being used by the tag to identify information sent by the reader to the tag; A determining unit is configured to determine a capability of the tag according to the first information, wherein the capability is used by the reader to distinguish the tag from other tags.

22. A label, characterized in that: The tag is applied to a radio frequency identification communication system, the radio frequency identification communication system including a reader and the tag connected to the reader, the tag including: A sending unit is used to send first information to the reader / writer, where the first information is the first information sent by the tag to the reader / writer during the inventory process, and the first information is used by the reader / writer to determine the capability of the tag. The first information includes a 16-bit random number, and the 16-bit random number is used by the tag to identify the information sent by the reader / writer to the tag; the capability is used by the reader / writer to distinguish the tag from other tags.

23. A reader / writer, characterized in that: The method comprises a processor coupled to a memory, wherein the memory is used to store computer programs or instructions, and the processor is used to execute the computer program or instructions in the memory, so that the method according to any one of claims 1 to 10 is performed.

24. A label, characterized in that: The method comprises a processor coupled to a memory, wherein the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions in the memory, so that the method according to any one of claims 11 to 20 is performed.

25. A label, characterized in that: The tag is applied to a radio frequency identification communication system. The state machine supported by the tag includes: ready, arbitration, response, confirmation, and secure states, but does not include open and / or inactivated states. The tag is applied to the method described in any one of claims 1 to 20.

26. A label, characterized in that: The tag is applied to a radio frequency identification communication system, the storage space of the tag does not store an access password and / or an inactivation password, and the tag is applied to the method according to any one of claims 1 to 20.

27. A label, characterized in that: The tag is applied to a radio frequency identification communication system, the tag supports two of four sections, the sections are used for a reader to manage multiple tags, and the tag is applied to the method according to any one of claims 1 to 20.

28. A chip, characterized in that: The chip includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a computer program or instruction so that the method according to any one of claims 1 to 10 is executed.

29. A chip, characterized in that: The chip includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a computer program or instruction so that the method according to any one of claims 11 to 20 is executed.

30. A communication system, characterized in that: include: The reader / writer according to claim 23, and / or the tag according to claim 24.

31. A computer storage medium, characterized in that The computer storage medium stores instructions, which, when executed on a computer, enable the computer to perform the method according to any one of claims 1 to 10, or enable the computer to perform the method according to any one of claims 11 to 20.

Images