CN102073896A - Realization method of label side physical receiving - Google Patents
Realization method of label side physical receiving Download PDFInfo
- Publication number
- CN102073896A CN102073896A CN2009102286483A CN200910228648A CN102073896A CN 102073896 A CN102073896 A CN 102073896A CN 2009102286483 A CN2009102286483 A CN 2009102286483A CN 200910228648 A CN200910228648 A CN 200910228648A CN 102073896 A CN102073896 A CN 102073896A
- Authority
- CN
- China
- Prior art keywords
- preset time
- tari
- coding
- receiving
- rtcal
- 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
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a realization method of label side physical receiving, comprising the following step of: if sequentially receiving Tari, forward calibration RTCal and pulse interval PIE code within a preset time after receiving a locator, or sequentially receiving the Tari, the RTCal, reverse calibration TRCal and the PIE code within the preset time after receiving the locator by the label side, finishing receiving. Based on the technical scheme, signal receiving can be realized at the label side through software, and the realization method is simple and easy to operate.
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.
Step 305a: store this TRCal; Do not receive in Preset Time that afterwards the PIE coding then takes defeat, then continue execution in step 305b if in Preset Time, receive 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 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 |
---|---|---|---|
CN2009102286483A CN102073896A (en) | 2009-11-23 | 2009-11-23 | Realization method of label side physical receiving |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009102286483A CN102073896A (en) | 2009-11-23 | 2009-11-23 | Realization method of label side physical receiving |
Publications (1)
Publication Number | Publication Date |
---|---|
CN102073896A true CN102073896A (en) | 2011-05-25 |
Family
ID=44032430
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2009102286483A Pending CN102073896A (en) | 2009-11-23 | 2009-11-23 | Realization method of label side physical receiving |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN102073896A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109921860A (en) * | 2018-12-31 | 2019-06-21 | 浙江悦和科技有限公司 | A kind of PIE coded demodulation method of super low-power consumption |
-
2009
- 2009-11-23 CN CN2009102286483A patent/CN102073896A/en active Pending
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109921860A (en) * | 2018-12-31 | 2019-06-21 | 浙江悦和科技有限公司 | A kind of PIE coded demodulation method of super low-power consumption |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN100550033C (en) | A kind of many label identification methods that are used for radio-frequency (RF) identification | |
WO2010122520A3 (en) | Method and system of electronic payment transaction, in particular by using contactless payment means | |
WO2006020589A1 (en) | Rfid readers and tags transmitting and receiving waveform segment with ending-triggering transition | |
KR100845666B1 (en) | Bi-slotted tree based anti-collision protocols for fast tag identification in rfid systems | |
US20110273271A1 (en) | Method and system for radio frequency idenfication tag using reduced set communication protocol | |
WO2008079488A3 (en) | System and method for updating a transactional device | |
AU2003288594A8 (en) | Enhancing data integrity and security in a processor-based system | |
CN101174850B (en) | Short type partially matching fast-capturing correlator | |
JP4738771B2 (en) | Communication system and communication method | |
CN102129580B (en) | Data communication method from label to reader-writer based on Miller codes | |
CN102073896A (en) | Realization method of label side physical receiving | |
CN101819620A (en) | Implementation method for physical receiving at label side | |
CN109818713A (en) | Miller code coding/decoding method, device and the equipment and storage medium of subcarrier modulation | |
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 | |
CN103888158A (en) | Device and method with filtering for receiving low-frequency carrier waves | |
US7772963B2 (en) | System and method for synchronization of data streams | |
CN101616109A (en) | A kind of data transmission method | |
US8890660B2 (en) | Power saving method | |
EP2326022A1 (en) | Device for acquiring a spread spectrum signal | |
CN108021836B (en) | Dynamic Q value anti-collision method for filtering redundant time slots and reducing Q value adjustment times | |
CN102096834A (en) | Data communication method of FM0-code-based label and reader-writer |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110525 |