CN101819620A - Implementation method for physical receiving at label side - Google Patents
Implementation method for physical receiving at label side Download PDFInfo
- Publication number
- CN101819620A CN101819620A CN200910118676A CN200910118676A CN101819620A CN 101819620 A CN101819620 A CN 101819620A CN 200910118676 A CN200910118676 A CN 200910118676A CN 200910118676 A CN200910118676 A CN 200910118676A CN 101819620 A CN101819620 A CN 101819620A
- Authority
- CN
- China
- Prior art keywords
- preset time
- tari
- coding
- rtcal
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Input From Keyboards Or The Like (AREA)
Abstract
The invention provides an implementation method for physical receiving at a label side, which comprises the following steps: if the label side orderly receives Tari, forward calibration RTcal and a pulse interval PIE code, or Tari, RTcal and reverse calibration RTcal and the PIE code within the preset time after receiving a locator, receiving is completed. The technical scheme can realize signal receiving at the label side by software. The implementation method is simple and feasible.
Description
Technical field
The present invention relates to RFID (radio-frequency (RF) identification claims electronic tag again) technology, be specifically related to the implementation method that a kind of label-side physics receives.
Background technology
In the RFID The Application of Technology, the physics of label-side receives to refer to and receives the signal that reading device side sends, and this signal comprises lead code (Preamble) (as shown in Figure 1) and PIE coding (as shown in Figure 2).Lead code comprises finger URL (Delimeter), forward direction calibration (RTCal), oppositely calibration (TRCal) (only having in the Query order).
Tari: i.e. PIE (pulse-spacing coding) coding " 0 ", the i.e. data among Fig. 10 of forward direction transmission.
PW (Pulse Wide): low level time span among the Tari.
RTCal: time span is PIE coding " 0 " and " 1 " time span addition that forward direction sends, and is low level in last PW, and all the other times are high level.
TRCal: be used for characterizing the speed that label sends to reader.
Generally speaking, the physics reception generally all is hard-wired.
Summary of the invention
The technical problem to be solved in the present invention provides the implementation method that a kind of label-side physics receives, can be in label-side by the reception of software realization to signal.
In order to address the above problem, the invention provides the implementation method that a kind of label-side physics receives, comprise: if label-side is received Tari, forward direction calibration RTCal and recurrent interval PIE coding after receiving finger URL successively in Preset Time, or receive and in Preset Time, receive Tari, RTCal behind the finger URL successively, oppositely calibrate TRCal and PIE coding, then finish receiving.
Further, do not receive that after receiving described finger URL if in Preset Time Tari then takes defeat;
The Tari of described Preset Time during greater than 1 times 40k.
Further, the described Tari of record after receiving described Tari is not if receive that in Preset Time RTCal then takes defeat;
Described Preset Time is greater than 1 times Tari.
Further, do not receive that after receiving described RTCal if in Preset Time next code then takes defeat;
Described Preset Time is greater than 3 times RTCal.
Further, after receiving described RTCal if in Preset Time, receive next code, then judge described type of coding and store this coding.
Further, the method for described judgement type of coding is, if the code length of described coding is less than 3 times Tari, then described coding is the PIE coding, otherwise is TRCal.
Further, do not receive that after receiving TRCal if in Preset Time the PIE coding then takes defeat;
Described Preset Time is greater than 2 times Tari.
Further, if described PIE encodes less than half of forward direction calibration code length, then the value of this PIE coding is 0, otherwise the value of this PIE coding is 1.
Tari when further, described Preset Time is 4 times 40k.
Further, described Preset Time is 4 times Tari.
Further, described Preset Time is 4 times RTCal.
Further, described Preset Time is 3 times Tari.
Further, overtime timer is set, its time-out time is described Preset Time, does not receive next code in Preset Time, and described overtime timer triggers and interrupts, and takes defeat.
In sum, the invention provides the implementation method that a kind of label-side physics receives, can be in label-side by the reception of software realization to signal, implementation method is simple.
Description of drawings
Fig. 1 a and Fig. 1 b are the lead code oscillograms;
Fig. 2 is the PIE code pattern;
Fig. 3 is the inventive method operational flowchart.
Embodiment
The invention provides the implementation method that a kind of label-side physics receives, if label-side is received Tari, RTCal and PIE coding after receiving finger URL successively; Or receive Tari, RTCal, TRCal and PIE coding successively after receiving finger URL, then finish receiving.
The implementation method that present embodiment provides a kind of label-side physics to receive as shown in Figure 3, may further comprise the steps:
Step 301: do not receive that after label-side receives finger URL if in Preset Time Tari then takes defeat, if in Preset Time, receive then execution in step 302 of Tari;
The Tari of (this moment, Tari value was maximum, was 25 μ s) when this Preset Time should be greater than 1 times 40k (be forward direction send PIE0 encode time of " 0 "), preferably, the Tari when this Preset Time is set to 4 times 40k;
It can be to be provided with after receiving finger URL that Preset Time is set, and also can be that label-side begins to set in advance before the received signal;
Further, overtime timer can also be set, its time-out time is above-mentioned Preset Time, triggers when not receiving Tari in the Preset Time and interrupts, and shows to take defeat.
Step 302: write down Tari after receiving Tari, if in Preset Time, do not receive RTCal, then take defeat afterwards, if in Preset Time, receive then execution in step 303 of RTCal;
This Preset Time should be greater than 1 times Tari, and preferably, this Preset Time is set to 4 times Tari;
Be provided with Preset Time can but to be not limited to be to be provided with after receiving Tari; If Preset Time is set after receiving Tari, record Tari and the operation that Preset Time is set can be referred to as capture interrupt and handle.
Overtime timer can also be set, and its time-out time is above-mentioned Preset Time, triggers when not receiving RTCal in the Preset Time and interrupts, and shows to take defeat.
Step 303: label-side is stored RTCal after receiving RTCal, and calculates and storage RTCal Half (be RTCal half), as the criterion of later PIE decoding; Afterwards if do not receive that in Preset Time next code then takes defeat, if in Preset Time, receive then execution in step 304 of next code;
This Preset Time should be greater than 3 times RTCal, and preferably, time-out time is set to 4 times RTCal (staying some surpluses).
Be provided with Preset Time can but to be not limited to be to be provided with after receiving RTCal; Further, overtime timer can also be set, its time-out time is above-mentioned Preset Time, triggers when not receiving next code in the Preset Time and interrupts, and shows to take defeat.
Step 304: receive and judge this type of coding behind the next code, if this receives is then execution in step 305a of TRCal, if that receive is the PIE then execution in step 305b that encodes;
The method of judging type of coding is, the coding of receiving afterwards because of RTCal might be TRCal, it also might be the PIE coding, because TRCal is greater than 1.1 times RTcal, 1.1RTcal=1.1*3=3.3Tari, if so the code length that receives, is just thought the PIE coding less than 3Tari, otherwise be TRCal.
This Preset Time should be greater than 2 times Tari, and preferably, this Preset Time is set to 3 times Tari, be provided with Preset Time can but to be not limited to be to be provided with after receiving TRCal;
Further, overtime timer can also be set, its time-out time is above-mentioned Preset Time, triggers when not receiving the PIE coding in the Preset Time and interrupts, and shows to take defeat.
Receive continuous this step of carrying out of PIE encodes subsequent afterwards,, enter the upper strata and handle if certain does not continue in Preset Time to receive that the PIE coding then finishes receiving after receiving the PIE coding.
This Preset Time should be greater than 2 times Tari, and preferably, this Preset Time is set to 3 times Tari, be provided with Preset Time can but to be not limited to be to receive that PIE coding back is provided with;
Further, overtime timer can also be set, its time-out time is above-mentioned Preset Time, triggers when not receiving the PIE coding in the Preset Time and interrupts, and shows to finish receiving.
Further, behind storage PIE coding, judge whether buffer zone has exceeded its capacity, is then to finish receiving, promptly no longer receive subsequent P IE coding.
Claims (13)
1. the implementation method that receives of a label-side physics, comprise: if label-side is received Tari, forward direction calibration RTCal and recurrent interval PIE coding after receiving finger URL successively in Preset Time, or receive and in Preset Time, receive Tari, RTCal behind the finger URL successively, oppositely calibrate TRCal and PIE coding, then finish receiving.
2. the method for claim 1 is characterized in that:
Do not receive that after receiving described finger URL if in Preset Time Tari then takes defeat;
The Tari of described Preset Time during greater than 1 times 40k.
3. the method for claim 1 is characterized in that:
The described Tari of record after receiving described Tari is not if receive that in Preset Time RTCal then takes defeat;
Described Preset Time is greater than 1 times Tari.
4. the method for claim 1 is characterized in that:
Do not receive that after receiving described RTCal if in Preset Time next code then takes defeat;
Described Preset Time is greater than 3 times RTCal.
5. method as claimed in claim 4 is characterized in that:
After receiving described RTCal if in Preset Time, receive next code, then judge described type of coding and store this coding.
6. method as claimed in claim 5 is characterized in that:
The method of described judgement type of coding is, if the code length of described coding is less than 3 times Tari, then described coding is the PIE coding, otherwise is TRCal.
7. method as claimed in claim 6 is characterized in that:
Do not receive that after receiving TRCal if in Preset Time the PIE coding then takes defeat;
Described Preset Time is greater than 2 times Tari.
8. method as claimed in claim 6 is characterized in that:
If described PIE encodes less than half of forward direction calibration code length, then the value of this PIE coding is 0, otherwise the value of this PIE coding is 1.
9. method as claimed in claim 2 is characterized in that:
Tari when described Preset Time is 4 times 40k.
10. method as claimed in claim 3 is characterized in that:
Described Preset Time is 4 times Tari.
11. method as claimed in claim 4 is characterized in that:
Described Preset Time is 4 times RTCal.
12. method as claimed in claim 6 is characterized in that:
Described Preset Time is 3 times Tari.
13., it is characterized in that as claim 2,3,4 or 7 described methods:
Overtime timer is set, and its time-out time is described Preset Time, does not receive next code in Preset Time, and described overtime timer triggers and interrupts, and takes defeat.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910118676A CN101819620A (en) | 2009-02-27 | 2009-02-27 | Implementation method for physical receiving at label side |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910118676A CN101819620A (en) | 2009-02-27 | 2009-02-27 | Implementation method for physical receiving at label side |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101819620A true CN101819620A (en) | 2010-09-01 |
Family
ID=42654717
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN200910118676A Pending CN101819620A (en) | 2009-02-27 | 2009-02-27 | Implementation method for physical receiving at label side |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN101819620A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111597834A (en) * | 2020-05-11 | 2020-08-28 | 山西众烁微电子有限公司 | PIE decoding method only judging high level |
-
2009
- 2009-02-27 CN CN200910118676A patent/CN101819620A/en active Pending
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111597834A (en) * | 2020-05-11 | 2020-08-28 | 山西众烁微电子有限公司 | PIE decoding method only judging high level |
CN111597834B (en) * | 2020-05-11 | 2023-08-01 | 山西众烁微电子有限公司 | PIE decoding method only for judging high level |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2569911B1 (en) | Method and system for radio frequency identification tag using reduced set communication protocol | |
EP1787235A1 (en) | Rfid readers and tags transmitting and receiving waveform segment with ending triggering transition | |
EP1380955A3 (en) | System and method for tracking utilization data for an electronic device | |
WO2010122520A3 (en) | Method and system of electronic payment transaction, in particular by using contactless payment means | |
ZA200801897B (en) | A dynamic transaction card and a method of writing information to the same | |
CN103716270A (en) | Data sending and receiving method and device | |
EP2192522A3 (en) | Radio communication method | |
AU2003288594A8 (en) | Enhancing data integrity and security in a processor-based system | |
CN108171304A (en) | A kind of ultra-high frequency RFID label digital baseband low-power dissipation system based on EPC/C-1/G-2 standards | |
CN102129580B (en) | Data communication method from label to reader-writer based on Miller codes | |
CN101699533B (en) | Coding and decoding method applicable to remote controller | |
JP2007234001A5 (en) | ||
JP2006040184A (en) | Reader-writer and communication method and system using the same | |
CN101819620A (en) | Implementation method for physical receiving at label side | |
CN102073896A (en) | Realization method of label side physical receiving | |
US8570159B2 (en) | Manifest integrity management via radio frequency identification (RFID) | |
CN104392600A (en) | Method for storing by collecting different infrared frequencies | |
CN102496055A (en) | RFID demodulation mode automatic identification method and automatic identification circuit thereof | |
CN105743826B (en) | A kind of Miller subcarrier coding/decoding method | |
EP2299597A1 (en) | Data transmission method | |
CN204595905U (en) | RFID tag, label recognizer, label reader | |
CN201903901U (en) | RFID e-tag for petroleum drilling tool | |
EP2068266A3 (en) | Reading method, responder, and interrogator | |
US8890660B2 (en) | Power saving method | |
CN109784434A (en) | A kind of Intelligent cargo cabinet and its RFID label tag inquiry, checking method and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100901 |