13.07.2015 Views

NFC Digital Protocol - CWI

NFC Digital Protocol - CWI

NFC Digital Protocol - CWI

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>NFC</strong>-B Technology5.2 Bit Level Coding5.2.1 Poll→Listen Coding SchemeThe patterns L and H are used to code the digital alphabet Logic “0” and Logic “1”.Requirements 41: Bit Level Coding Poll→Listen – <strong>NFC</strong>-BPoll Mode5.2.1.1 The <strong>NFC</strong> Forum Device MUSTcode Logic “0” and Logic “1” asfollows:• Logic “0”: pattern L• Logic “1”: pattern HListen Mode5.2.1.2 The <strong>NFC</strong> Forum Device MUSTdecode Logic “0” and Logic “1” asfollows:• If the <strong>NFC</strong> Forum Devicedetects pattern L, then it MUSTdecode this as Logic “0”.• If the <strong>NFC</strong> Forum Devicedetects pattern H, then itMUST decode this as Logic“1”.Invalid patterns MAY be treated asTransmission Errors, or the device MAY useimplementation dependent methods to decodean invalid pattern into a Logic “0” or Logic“1”.5.2.2 Listen→Poll Coding SchemeUse patterns N and M to code the digital alphabet Logic “0” and Logic “1”.Requirements 42: Bit Level Coding Listen→Poll – <strong>NFC</strong>-BPoll Mode5.2.2.1 The <strong>NFC</strong> Forum Device MUSTdecode Logic “0” and Logic “1” asfollows:• If the <strong>NFC</strong> Forum Devicedetects pattern N, then it MUSTdecode this as Logic “0”.• If the <strong>NFC</strong> Forum Devicedetects pattern M, then itMUST decode this as Logic“1”.Invalid patterns MAY be treated asTransmission Errors or the device MAY useimplementation dependent methods to decodean invalid pattern into a Logic “0” orLogic “1”.Listen Mode5.2.2.2 The <strong>NFC</strong> Forum Device MUSTcode Logic “0” and Logic “1” asfollows:• Logic “0”: pattern N• Logic “1”: pattern M<strong>NFC</strong> <strong>Digital</strong> <strong>Protocol</strong> Page 50

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!