Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal.

Similar presentations


Presentation on theme: "Doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal."— Presentation transcript:

1 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [PHY Header Discussion] Date Submitted: [July 14, 2009] Source: [René Struik] Company [Certicom Research] Address [5520 Explorer Drive, Fourth Floor, Mississauga, ON, L4W 5L1, Canada] Voice: [+1 (905) 501-6083], FAX: [+1 (905) 507-4230], E-Mail: [rstruik@certicom.com] Re: [ ] Abstract:[This document discusses how to add PHY header error correction capabilities with low implementation cost and without data expansion. This presentation uses 802.15.4-2006 formats, due to pending merging process 802.15nan.] Purpose:[Improve energy efficiency and early error detection with 802.15.4g PHYs.] Notice:This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 2 IEEE 802.15.4g PHY Header Discussion René Struik (Certicom Research)

3 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 3 PHY Header Considerations (1) 802.15.4-2006 PHY (2.4 GHz) Modulation scheme (2.4 GHz) – Bit-to-symbol mapping:4 bits  symbol (16-ary value) – Symbol-to-chip mapping: symbol  32-bit codeword (chipping sequence) 802.15.4-2006 MAC Source: 802.15.4-2006, §6.3, Fig. 16, p. 43 Source: 802.15.4-2006, §6.3.2, Fig. 17, p. 44  127 octets Source: 802.15.4-2006, §6.5.2.2 and §6.5.2.3, p. 47

4 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 4 PHY Header Considerations (2) 802.15.4-2006 PHY (2.4 GHz) Modulation scheme (2.4 GHz) – Bit-to-symbol mapping:4 bits  symbol (16-ary value) – Symbol-to-chip mapping: symbol  32-bit codeword (chipping sequence) 802.15.4-2006 MAC Source: 802.15.4-2006, §6.3, Fig. 16, p. 43 Source: 802.15.4-2006, §6.3.2, Fig. 17, p. 44  127 octets Source: 802.15.4-2006, §6.5.2.2 and §6.5.2.3, p. 47 Channel coding: – intra-symbol demodulation – MAC error detection – no PHY header error control

5 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 5 PHY Header Considerations (3) Idealized 802.15.4-2006 PHY (2.4 GHz) Modulation scheme (2.4 GHz) – Bit-to-symbol mapping:4 bits  symbol (16-ary value) – Symbol-to-chip mapping: symbol  32-bit codeword (chipping sequence) Assumptions – Actual octet pattern of the 4-octet PHY preamble does not matter for synchronization: The chipping sequence takes care of that; – The "comma" octet pattern is fixed, to indicate where the preamble stops; – The "length of MPDU" field is not part of the synchronization process. Source: 802.15.4-2006, §6.3, Fig. 16, p. 43  127 octets Channel coding: – intra-symbol demodulation – MAC error detection – no PHY header error control

6 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 6 PHY Header Considerations (4) Idealized 802.15.4-2006 PHY (2.4 GHz) Modulation scheme (2.4 GHz) – Bit-to-symbol mapping:4 bits  symbol (16-ary value) – Symbol-to-chip mapping: symbol  32-bit codeword (chipping sequence) Assumptions – Actual octet pattern of the 4-octet PHY preamble does not matter for synchronization: The chipping sequence takes care of that; – The "comma" octet pattern is fixed, to indicate where the preamble stops; – The "length of MPDU" field is not part of the synchronization process. Result – Error correcting code on PHY header without data expansion – Low-cost implementation, to degree implementer wants Source: 802.15.4-2006, §6.3, Fig. 16, p. 43  127 octets Channel coding: – intra-symbol demodulation – MAC error detection – no PHY header error control Channel coding: – intra-symbol demodulation – MAC error detection – PHY header error correction

7 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 7 PHY Header Considerations (5) Idealized 802.15.4-2006 PHY (2.4 GHz) Details – Code with symbols from Galois field GF(16), i.e., 16-ary symbols – 802.15.4-2006: [2,2,1] 16-ary code preceded by 10 fixed symbols 4-octet = 8 symbol all-zero synch sequence 1-octet = 2-symbol fixed SFD sequence (“comma”) 1-octet = 2-symbol variable length field Alternative view: coset of [12,2,1] code – with error correction: [12,2,11] MDS code over GF(16) 4-octet = 8-symbol redundancy information (parity-checks) 1-octet = 2-symbol redundancy information (more parity-checks) 1-octet = 2-symbol information set (length info) Source: 802.15.4-2006, §6.3, Fig. 16, p. 43  127 octets Channel coding: – intra-symbol demodulation – MAC error detection – PHY header error control

8 doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 8 PHY Header Considerations (6) Idealized 802.15.4-2006 PHY (2.4 GHz) Details – Code with symbols from Galois field GF(16), i.e., 16-ary symbols – with error correction: [12,2,11] MDS code over GF(16) 4-octet = 8-symbol redundancy information (parity-checks) 1-octet = 2-symbol redundancy information (more parity-checks) 1-octet = 2-symbol information set (length info) Implementation considerations: – Erasure decoding. If one does not see part of preamble, simply decode punctured code Example #1: [12,2,11]  [4,2,3] (throw away 4-octet preamble) Example #2: [12,2,11]  [2,2,1] (only read information set, i.e., length info) – Flexible implementation. Trade-off decoding logic and error control capabilities Example: if one does not wish to implement encoding, simply ignore redundancy bits – More coding gain possible. Combine demodulation and MDS error control (ML, soft-decision, etc.) Source: 802.15.4-2006, §6.3, Fig. 16, p. 43  127 octets Channel coding: – intra-symbol demodulation – MAC error detection – PHY header error control


Download ppt "Doc.: IEEE 802.15-04-0547-00-004g Submission July 14, 2009 René Struik (Certicom Research)Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal."

Similar presentations


Ads by Google