Disclosure of Invention
The invention aims to solve the technical problem of providing an RFID system which can reduce the cost and improve the compatibility and expandability of a scheme under the condition of meeting the delay of an RFID protocol.
In order to solve the technical problems, the embodiment of the invention provides the following technical scheme:
in one aspect, there is provided an RFID system comprising:
an exciter for receiving a RN16 message of a tag, starting a second timer, and transmitting an acknowledgement message of the RN16 message to the tag before the second timer times out, or transmitting a first queryrep message to the tag, the first queryrep message indicating that the session is not matched;
the tag is configured to send the RN16 message to the exciter, receive an acknowledgement message of the RN16 message sent by the exciter, report the EPC to the receiver, start a second timer, enter arbitrate a state after the second timer times out, and receive a select command sent by the receiver to switch a session state, or stop the second timer after receiving a first queryrep message of the exciter, start a first timer and a third timer, receive an acknowledgement message of the RN16 message sent by the receiver after the first timer and the third timer time out, report the EPC to the receiver, receive a second queryrep message sent by the receiver, the first queryrep message indicates that the session is not matched, and the second queryrep message indicates that the session is matched;
The receiver is configured to receive the EPC reported by the tag, start a second timer, and send a select command to the tag after the second timer times out, to instruct session state switching, or receive the EPC reported by the tag, send a second queryrep message to the tag, and instruct session state switching.
In some embodiments, the receiver is integrated in the exciter.
In some embodiments, if the EPC is not valid,
The tag is further configured to start a second timer after the EPC is reported to the receiver, and enter a arbitrate state after the second timer times out, without session state switching.
In some embodiments, the receiver is further configured to send a first query message to the exciter, indicating to perform a read-write operation;
the exciter is also used for receiving a first query message sent by the receiver, performing read-write operation, starting a second timer after receiving the EPC returned by the tag, and sending REQ_RN to the tag before the second timer is overtime;
the tag is used for sending EPC to the receiver, receiving REQ_RN sent by the exciter, and returning handle to the exciter.
In some embodiments, the exciter is specifically configured to receive only a preamble portion of the EPC, or to receive all of the EPC.
In some embodiments, if the EPC is not valid,
The receiver is also configured to send a first indication to the tag indicating that the tag returns to the EPC again, or
The receiver is also used for sending a second query message to the tag to trigger the next re-reading, or
The exciter is also used for sending a second indication to the tag when the tag is in an acknowledge state, indicating the tag to return to EPC again, or
The receiver is further configured to send a third indication to the tag indicating that the tag returns to the EPC again when the tag is in arbitrate states, or
The exciter is also used for sending a third query message to the tag to trigger the next rereading.
In some embodiments, the receiver is independent of the exciter.
In some embodiments, the exciter is further configured to send a fourth query message to the tag, after the tag enters a reply state, start a second timer, and send a third queryrep message to the tag before the second timer times out, indicating that the session does not match;
The tag is further configured to maintain a reply state after receiving the third queryrep message, stop the second timer, start the first timer and the third timer, and after the first timer and the third timer timeout, receive a confirmation message sent by the receiver, and send EPC to the receiver.
In some embodiments, if the EPC is not valid,
The tag is further configured to start a second timer after the EPC is reported to the receiver, and enter a arbitrate state after the second timer times out, without session state switching.
In some embodiments, the exciter is further configured to start a second timer after sending an acknowledgement message to the tag, and send a fourth queryrep message to the tag before the second timer expires, indicating that the session does not match;
The tag is further configured to, after receiving the fourth queryrep message, maintain the state of the acknowledged, stop the second timer, start the first timer and the third timer, and after the first timer and the third timer timeout, receive a fifth query message sent by the receiver, and perform a next round of inventory.
In some embodiments, the receiver is further configured to send a sixth query message to the exciter, indicating that the exciter sends a fifth queryrep message to the tag after sending the acknowledgement message to the tag, indicating that the session does not match;
The exciter is further used for starting a second timer after the confirmation message is sent to the tag, sending a fifth queryrep message to the tag before the second timer is overtime to indicate that the session is not matched, stopping the second timer, starting a first timer and a third timer, and after the first timer and the third timer are overtime, transmitting a REQ_RN command sent by the receiver to the tag.
The embodiment of the invention has the following beneficial effects:
In the scheme, the limitation of T2 (namely the second timer) time delay on the system design is eliminated, more flexible, more mature and lower-cost communication protocols such as WIFI, BT or other simplified short-distance communication protocols are adopted between the communication equipment and the exciter, the problem of limited transmission rate is solved, and higher rates such as 256K,320K and even 640K can be realized.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved by the embodiments of the present invention more apparent, the following detailed description will be given with reference to the accompanying drawings and the specific embodiments.
The existing architecture of the transceiver-separated RFID (Radio Frequency Identification, radio frequency identification technology) is shown in fig. 1, where a receiver is responsible for selecting and controlling an exciter and transmitting an excitation signal, for configuring various resources of the exciter, such as a frequency hopping frequency point sequence, time division, frequency division strategy, antenna configuration, transmitting power, and the like, and for receiving and demodulating a tag reflected signal. The exciter is responsible for transmitting the excitation signal to energize the tag, for transmitting various read control signaling such as select, inventory, access, etc., and for acknowledging the ACK to the command reply of the receiver. After the tag is charged, the information of the tag is carried on the reflected signal and is sent to the receiver.
The RFID protocol is particularly demanding in terms of latency, most importantly T2 (3.0 Tpri-20.0 Tpri) is a latency on the order of microseconds. In the existing RFID protocol flow, a limit point of T2 of an integrated reader-writer is shown in fig. 2, wherein the limit point 1 is between the 3 rd step and the 4 th step, the time delay requirement is T2, the limit point 2 is between the 5 th step and the 6 th step, the time delay requirement is T2, the limit point 2.1 is between the 5 th step and the 6 th step, the time delay requirement is T2, after the tag returns to a valid EPC, the tag is expected to receive a QueryRep within the time T2, the tag enters a ready state, the session state is from A- > B, the reading is completed, the limit point 2.2 is between the 5 th step and the 6.2 th step, the time delay requirement is T2, the tag is expected to receive NAK within the time T2, the tag enters the arbitrate th step and the session is kept A, the tag waits to be read again, the limit point 2.3 is expected to receive a Req_after the tag returns to the valid EPC within the time T2, the RN is expected to read, the other session is kept, and the time delay is kept in the tag is kept A.
For the architecture of receiving and transmitting separation, as the reader-writer is separated into two devices, new device time delay is introduced, so that the limitation of the time delay becomes prominent:
1. the running time delay (main time delay) of the equipment itself is that of only one reader-writer originally, and two time delays of the receiving equipment and the exciting equipment are introduced.
2. The transmission delay between the receiving device and the exciting device is that the RN16 generated by the tag needs to be sent to the receiving device first, then the receiving device sends the received signal to the exciting device, and the exciting device sends an ACK (carrying the RN 16) to the tag. The communication procedure of the RN16 between the receiving device and the exciting device is the newly introduced delay.
In the prior art, to meet the requirement of T2 time delay, the following aspects are improved:
1. Hardware aspects such as FPGA, ASIC chip, coupler, mixer, etc., introduce many limitations and increase design and device costs.
2. The bottom software is required to be designed for signals, optimized for data processing algorithm and the like, meets the time delay requirement, has great limitation on the selection of communication protocols, and has to select and design a protocol architecture with shorter symbols and short signaling and data transmission length, so that the short-distance protocol which is widely applied at present can not be basically met, and a set of private protocol needs to be redesigned to meet the time delay requirement.
3. In terms of transmission rate, due to delay constraints, it is assumed that the exciter and receiver delays can be controlled within 80us, and rates of 320K and even 640K cannot be achieved, and to achieve this, the transmission delay must be greatly increased again, increasing the cost.
In summary, the existing solutions have the following drawbacks:
1. the high hardware cost and the high software cost are required to be added, and the architecture design is more limited so as to meet the requirement of time delay;
2. The time delay requirement of the communication protocol between the receiver and the exciter is very high, common communication protocols such as WIFI, BT and 5G can not be met even some simple short-distance communication, the customized private protocol is needed to be relied on, the limitation is more, and the compatibility and the expandability of the scheme are greatly reduced.
3. The transmission rate is limited and can only be maintained at a lower rate, such as 40K, or 160K.
The embodiment of the invention provides an RFID system, which can reduce cost and improve compatibility and expandability of a scheme under the condition of meeting the delay of an RFID protocol.
An embodiment of the present invention provides an RFID system, including:
an exciter for receiving a RN16 message of a tag, starting a second timer, and transmitting an acknowledgement message of the RN16 message to the tag before the second timer times out, or transmitting a first queryrep message to the tag, the first queryrep message indicating that the session is not matched;
the tag is configured to send the RN16 message to the exciter, receive an acknowledgement message of the RN16 message sent by the exciter, report the EPC to the receiver, start a second timer, enter arbitrate a state after the second timer times out, and receive a select command sent by the receiver to switch a session state, or stop the second timer after receiving a first queryrep message of the exciter, start a first timer and a third timer, receive an acknowledgement message of the RN16 message sent by the receiver after the first timer and the third timer time out, report the EPC to the receiver, receive a second queryrep message sent by the receiver, the first queryrep message indicates that the session is not matched, and the second queryrep message indicates that the session is matched;
The receiver is configured to receive the EPC reported by the tag, start a second timer, and send a select command to the tag after the second timer times out, to instruct session state switching, or receive the EPC reported by the tag, send a second queryrep message to the tag, and instruct session state switching.
In the embodiment, the limitation of T2 time delay on system design is eliminated, more flexible, more mature and lower-cost communication protocols such as WIFI, BT or other simplified short-distance communication protocols are adopted between the communication equipment and the exciter, the problem of limited transmission rate is solved, and higher rates such as 256K,320K and even 640K can be realized.
In this embodiment, tag memory is divided into four independent memory blocks (banks) including Reserved EPC (electronic product code), TID (Tag identification number) and User (User). Reserved area, which stores Kill Password and Access Password. EPC field, store EPC number, etc. The TID field stores tag identification numbers, each of which should be unique. User area, storing User defined data. The tag may be in one of seven states, ready, arbitrate, reply, acknowledged, open, secured, protected, killed, inactivated. The commands supported by this embodiment include: select, query adjust, query rep, ACK (EPC answer), NAK (turn-to-cut), req_rn (random number request), read (Read), write, kill (Kill), lock (Lock).
In some embodiments, the receiver is integrated in the exciter. I.e. adding a receiving circuit to the exciter of the split architecture, which is responsible for directly processing the RN16, EPC reception, and returning an ACK or other command to the tag within a time delay of T2 (i.e. the second timer) to meet the time delay requirement. The exciter can be introduced into a self-interference elimination circuit, and meanwhile, as the RFID system separation architecture of the embodiment is distributed deployment, the exciter deployment is closer to the tag, and the influence is not great. While data reflected by the tag, such as EPC, is still received by the receiver, long-range reception due to the high sensitivity of the receiver can still be enjoyed.
In some embodiments, if the EPC is not valid,
The tag is further configured to start a second timer after the EPC is reported to the receiver, and enter a arbitrate state after the second timer times out, without session state switching.
In some embodiments, the receiver is further configured to send a first query message to the exciter, indicating to perform a read-write operation;
the exciter is also used for receiving a first query message sent by the receiver, performing read-write operation, starting a second timer after receiving the EPC returned by the tag, and sending REQ_RN to the tag before the second timer is overtime;
the tag is used for sending EPC to the receiver, receiving REQ_RN sent by the exciter, and returning handle to the exciter.
In some embodiments, the exciter is specifically configured to receive only a preamble portion of the EPC, or to receive all of the EPC.
In some embodiments, if the EPC is not valid,
The receiver is also configured to send a first indication to the tag indicating that the tag returns to the EPC again, or
The receiver is also used for sending a second query message to the tag to trigger the next re-reading, or
The exciter is also used for sending a second indication to the tag when the tag is in an acknowledge state, indicating the tag to return to EPC again, or
The receiver is further configured to send a third indication to the tag indicating that the tag returns to the EPC again when the tag is in arbitrate states, or
The exciter is also used for sending a third query message to the tag to trigger the next rereading.
The present embodiment is further described below with reference to the accompanying drawings.
In this embodiment, in the normal procedure of EPC inventory, as shown in fig. 3, the method includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
The tag sends the RN16 to the exciter;
the exciter sends the RN16 to the receiver;
the label starts up T2, and enters an acknowledge state after the T2 is overtime;
the exciter sends an ACK to the tag during time T2 (RN 16);
the tag sends the EPC to the receiver, starts T2, enters arbitrate state after T2 times out,
The receiver triggers a select command (mask current EPC tag, session state switch a- > B) after receiving EPC, the exciter passes through to the tag execution, and the tag completes the marking of the read tag at arbitrate state.
In this embodiment, in the RN16 collision flow, the receiver does not send ACK, but adjusts Q value by query/queryadjust or query command, and continues inventory.
In this embodiment, in the EPC invalidation procedure, as shown in fig. 4, the method includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
The tag sends the RN16 to the exciter;
the exciter sends the RN16 to the receiver;
the label starts up T2, and is in an acknowledge state after the T2 is overtime;
the exciter sends an ACK to the tag during time T2 (RN 16);
The tag sends EPC (invalid) to the receiver, starts T2, and after the T2 is overtime, the tag enters expired arbitrate state, the current tag session is not switched, and is kept in A, and the next round of inventory is waited;
The receiver sends a Query message to the exciter after receiving the EPC, the exciter transmits the message to the tag for execution, and the tag enters a reply state.
In this embodiment, in the subsequent EPC procedure, the receiver triggers a special Query (req_rn) to instruct the exciter to perform a read/write operation, and when the tag returns to the EPC, the exciter sends req_rn to the tag in a time T2, and the tag returns to handle. Wherein the reception of EPC by the exciter can be divided into two cases:
in case 1, only the preamble portion is received, that is, the EPC is determined to have been received, and the validity thereof cannot be determined, but the complexity of the reception of the exciter can be reduced.
Case 2, receiving all EPCs, can determine its validity.
When EPC is inactive:
For case 1, the exciter cannot determine the validity of EPC, so whether it is valid or not, req_rn will be sent, and the tag enters open state, then the receiver may send ACK to let the tag return to EPC again at this time, or discard the round of inventory, and send query to trigger the next round of rereading.
For case 2, the exciter may determine the validity of the EPC, may send an ACK to the tag when the tag is in the acknowledge state (T2 not timed out) to allow the tag to return to the EPC again, or may send an ACK to the tag when the tag is in the arbitrate state (T2 timed out) to allow the tag to return to the EPC again, or may discard the roulette, and the request triggers the next rereading.
Taking the exciter req_rn as an example, as shown in fig. 5, the method includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating the req_RN;
the exciter sends a query message to the tag, indicating the req_RN;
the tag enters a reply state;
The tag sends the RN16 to the exciter;
the exciter sends the RN16 to the receiver;
the label starts up T2, and enters an acknowledge state after the T2 is overtime;
the exciter sends an ACK to the tag during time T2 (RN 16);
The tag sends EPC to the receiver through the exciter, T2 is started, and the tag enters an open state after the T2 is overtime;
The exciter sends the req_rn to the tag in time T2, and the tag returns a handle.
Compared with the related art, the embodiment removes the limitation of T2 time delay on system design, redesigns part of flow, and can be compatible with the original protocol, and the architecture is beneficial to adopting more flexible, more mature and lower-cost communication protocols, such as WIFI, BT or other simplified short-distance communication protocols, and the like between the communication equipment and the excitation equipment.
In some embodiments, the receiver is independent of the exciter. The exciter does not need to add a receiving circuit, but the T2 limiting point is sent queryrep (session mismatch) command to the tag by the exciter in the T2 time delay, so that the tag stops T2 and remains in the current state (such as the reply/acknowledge state), and the tag can continue to respond to the ACK, or req_rn later, which also releases the T2 limitation.
In some embodiments, the exciter is further configured to send a fourth query message to the tag, after the tag enters a reply state, start a second timer, and send a third queryrep message to the tag before the second timer times out, indicating that the session does not match;
The tag is further configured to maintain a reply state after receiving the third queryrep message, stop the second timer, start the first timer and the third timer, and after the first timer and the third timer timeout, receive a confirmation message sent by the receiver, and send EPC to the receiver.
In some embodiments, if the EPC is not valid,
The tag is further configured to start a second timer after the EPC is reported to the receiver, and enter a arbitrate state after the second timer times out, without session state switching.
In some embodiments, the exciter is further configured to start a second timer after sending an acknowledgement message to the tag, and send a fourth queryrep message to the tag before the second timer expires, indicating that the session does not match;
The tag is further configured to, after receiving the fourth queryrep message, maintain the state of the acknowledged, stop the second timer, start the first timer and the third timer, and after the first timer and the third timer timeout, receive a fifth query message sent by the receiver, and perform a next round of inventory.
In some embodiments, the receiver is further configured to send a sixth query message to the exciter, indicating that the exciter sends a fifth queryrep message to the tag after sending the acknowledgement message to the tag, indicating that the session does not match;
The exciter is further used for starting a second timer after the confirmation message is sent to the tag, sending a fifth queryrep message to the tag before the second timer is overtime to indicate that the session is not matched, stopping the second timer, starting a first timer and a third timer, and after the first timer and the third timer are overtime, transmitting a REQ_RN command sent by the receiver to the tag.
The present embodiment is further described below with reference to the accompanying drawings.
An abnormal response link timing diagram of the RFID tag protocol is shown in fig. 6, in which the interval duration between messages, such as the duration of a first timer between queryrep and RN16, the duration of a second timer between RN16 and Ack, etc., is limited.
In this embodiment, in the normal procedure of EPC inventory, for the limit point 1, the problem that the tag enters a reply state after the exciter sends the query, the exciter sends queryrep (session mismatch) to the tag in the time T2, the tag remains in the reply state after receiving the request, stops T2, starts the T1 and T3 timers (any signaling is not expected to be processed in this time period), and after the time of t1+t3 is overtime, the receiver sends ACK (RN 16) and the ACK is transmitted to the tag by the exciter, and the tag returns to EPC correctly. To ensure time accuracy, the exciter may define a T-RN16 (the time the tag reflects RN16< T-RN16< T2), T-RN 16= (1/BLF) ×length (length is the length of RN 16)
For constraint 2, there are two solutions that can be resolved by EPC timing:
scheme one, the T2 timeout scheme, as shown in fig. 7, includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
the tag sends the RN16 to the receiver;
the exciter sends queryrep (session mismatch) to the tag during time T2;
after the label is received, the label is kept in a reply state, and stops T2, starts T1 (namely a first timer), and starts T3 (namely a third timer), wherein no signaling is expected to be processed in the time period;
After T1+ T3 times out, the receiver sends ACK (RN 16) and the ACK is transmitted to the tag by the exciter;
The tag enters an acknowledge state;
the tag sends EPC to the receiver, starts T2, and enters expired arbitrate state after T2 is overtime;
The receiver triggers a select command (mask current EPC tag, session state switch a- > B) after receiving EPC, the exciter passes through to the tag execution, and the tag completes the marking of the read tag at arbitrate state.
Scheme two, T2 is not a timeout scheme, as shown in fig. 8, comprising the steps of:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
the tag sends the RN16 to the receiver;
the exciter sends queryrep (session mismatch) to the tag during time T2;
after the label is received, the label is kept in a reply state, and stops T2, starts T1 (namely a first timer), and starts T3 (namely a third timer), wherein no signaling is expected to be processed in the time period;
after T1 and T3 are overtime, the tag enters an acknowledge state;
the receiver sends an ACK (RN 16) and is passed through to the tag by the exciter;
The tag sends EPC to the receiver, and starts T2;
The exciter sends queryrep (session mismatch) to the tag in the T2 time, the tag remains in the acknowledged state after receiving, and starts T1, T3, during which time period no signaling is expected to be processed;
After the time out of T1+T3, the receiver sends queryrep (session match) and is passed through to the tag by the exciter, at which point the tag will perform slot-correctly and switch the session from A to B.
To ensure time accuracy, the exciter may define a T-EPC (time of tag reflection EPC < T-EPC < T2), T-epc= (1/BLF) ×length (length is length of EPC).
In this embodiment, in the collision flow, the receiver does not send ACK, but adjusts Q value by query/queryadjust or query command, and continues inventory.
In this embodiment, the EPC invalidation procedure includes a T2 timeout scheme and a T2 non-timeout scheme.
For the T2 timeout scheme, as shown in fig. 9, the following steps are included:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
the tag sends the RN16 to the receiver;
The tag starts T2;
The exciter sends queryrep (session mismatch) to the tag during time T2, the tag stops T2 and starts T1, T3;
After T1 and T3 time out, the exciter sends an ACK to the tag (RN 16);
The tag enters an acknowledge state;
the tag sends EPC (invalid) to the receiver, starts T2, and after the T2 is overtime, the tag enters arbitrate state, the current tag session is not switched, and is kept in A, and the next round of inventory is waited;
The receiver sends a Query message to the exciter after receiving the EPC, the exciter transmits the message to the tag for execution, and the tag enters a reply state.
For the T2 non-timeout scheme, as shown in fig. 10, the method includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
The receiver sends a query message to the exciter, indicating SessionA;
The exciter sends a query message to the tag, indicating SessionA;
the tag enters a reply state;
the tag sends the RN16 to the receiver;
The tag starts T2;
The exciter sends queryrep (session mismatch) to the tag during time T2, the tag stops T2 and starts T1, T3;
The receiver sends an ACK to the tag through the exciter (RN 16);
after T1 and T3 are overtime, the tag enters an acknowledge state;
The tag sends EPC (invalid), start T2,
The exciter sends queryrep (session mismatch) to the tag during time T2, the tag stops T2 and starts T1, T3;
after T1 and T3 are overtime, the receiver sends a Query message to the exciter, the exciter transmits the Query message to the tag for execution, and the tag enters a reply state to carry out the next round of inventory.
In this embodiment, in the subsequent EPC procedure, as shown in fig. 11, the method includes the following steps:
the receiver sends PowerUp to the exciter, indicating to power up;
the exciter sends PowerUp to the tag, indicating to power up;
The tag enters a ready state;
the receiver sends a query message to the exciter to indicate the req_RN, so that the exciter actively sends queryrep (session mismatch) to the tag after sending the ACK;
the exciter sends a query message to the tag, indicating the req_RN;
the tag enters a reply state;
the tag sends the RN16 to the receiver;
The tag starts T2;
the exciter sends queryrep (session mismatch) to the tag during time T2;
stopping T2 after the tag receives the tag, and starting T1 and T3;
the receiver sends an ACK to the exciter (RN 16);
After T1 and T3 are overtime, the exciter sends ACK (RN 16) to the tag, and the tag enters an acknowledge state;
the tag sends EPC to the receiver through the exciter, and starts T2;
The exciter sends queryrep (session mismatch) to the tag in the time of T2, the tag remains in the acknowledged state after receiving, and stops T2, starts the T1 and T3 timers, and does not expect to process any signaling in the time period;
after the timeout of T1+T3, the receiver sends a REQ_RN command and is passed through to the tag by the exciter.
To ensure time accuracy, the exciter may define a T-EPC (time of tag reflection EPC < T-EPC < T2), T-epc= (1/BLF) ×length (length is length of EPC).
Compared with the related art, the embodiment removes the limitation of T2 time delay on system design, redesigns part of flow, and can be compatible with the original protocol, and the architecture is beneficial to adopting more flexible, more mature and lower-cost communication protocols, such as WIFI, BT or other simplified short-distance communication protocols, and the like between the communication equipment and the excitation equipment. In addition, the exciter does not need to introduce a receiving channel, only a transmitting channel, and the self-interference problem of the exciter is not introduced, so that the distance between the exciter and the tag is advantageous.
Aspects of the present embodiments may be implemented by computer-readable storage media, including both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices to be detected, or any other non-transmission medium which can be used to store information that can be accessed by a computing device to be detected. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.