1 / 11

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) ‏

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) ‏ Submission Title: [JPKG comment suggestions] Date Submitted: [19 March 2008] Source: [James P. K. Gilb] Company [SiBEAM, Inc.] Address [555 N. Mathilda, Suite 100, Sunnyvale, CA 94085]

anneke
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) ‏

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title: [JPKG comment suggestions] Date Submitted: [19 March 2008] Source: [James P. K. Gilb] Company [SiBEAM, Inc.] Address [555 N. Mathilda, Suite 100, Sunnyvale, CA 94085] Voice: [408-245-3120], FAX: [408-245-3120], E-Mail: [last name at ieee dot org] Re: [P802-15-3c-DF2_Draft_Amendment.pdf] Abstract: [Suggested resolution for various comments on the TG3c draft..] Purpose: [Proposal to TG3c for alternate PHY amendment] 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. Dr. James P. K. Gilb, SiBEAM

  2. Dr. James P. K. Gilb, SiBEAM Comment 3 • When is the LRP used? • Add paragraph to 12.4, “The LRP mode is used for the beacon, during CPs and in allocated CTAs, when needed. The HRP modes shall only be used in allocated CTAs and shall not be used during CPs.”

  3. Dr. James P. K. Gilb, SiBEAM Comment 5 • Do we need reserved stream indices for channel probing and beam forming? • Suggested solution: No, we can and should use the three methods for bi-directional communication that were introduced in 802.15.3b • Receive Status field in Imm-ACK (7.2.4)‏ • Implied ACK (8.8.3a)‏ • Relinquish channel time (8.4.3.8)‏ • Using these mechanisms will provide the functionality required for channel probing and beam forming without increasing complexity

  4. Dr. James P. K. Gilb, SiBEAM Comment 7 • Suggest add two octets to the optional header • First 8 bits are ACK/NAK or msb ACK • Second 8 bits are ACK/NAK (repeat) or lsb ACK • Advantages • Same frame format for Blk-ACK and compressed Blk-ACK • Makes bi-directional Blk-ACK straightforward • Having ACK information in header and a fixed length is better for hardware implementations • Shorter frame, send with more robust header MCS is more likely to get through.

  5. Dr. James P. K. Gilb, SiBEAM Comment 16 • Suggestions for feedback in channel probing • RSSI: use 4 bits, 2 dB steps relative to the receiver’s sensitivity, starting with 0000 – 0 dB, 0001 – 2 dB, ..., 1110 – 28 dB, 1111 - > 30 dB. • SNR: use 4 bits, 2 dB steps, from 0000 being SNR for BER of 0.1 for the PHY mode (actual SNR to be provided by PHY proposers). • Recommended PHY mode: Response is the PHY mode index recommended by the receiver.

  6. UEP field (comment 17) • 3 bit field in Capability IE is sufficient, no commands or extra IEs required. • Refers to the DEVs capability as a receiver • 000 – no UEP capability • 001 – Type 1 capable • 010 – Type 2 capable • 011 – Type 3 capable with MCS only • 100 – Type 3 capable with skewed constellation only • 101 – Type 3 capable with MCS and skewed constellation • 110-111 – Reserved

  7. Dr. James P. K. Gilb, SiBEAM Base rate clarification (comment 23) • Base rate is used in the MAC section to specify the data rate of certain frames • All broadcast and multicast frames • Association request • Association response • Disassociation request • There is no restriction in the MAC on the data rate used in the CAP.

  8. Dr. James P. K. Gilb, SiBEAM Suggested changes (comment 23)‏ • Base rate for PHY modes • SC: 50.6 Mb/s • HSI: • AV: LRP mode 0, 1, 2 or 3 • Add a new subclause to 12.1, “Allowed CP data rates” (CP = contention periods). “A DEV shall only send frames during a CP with the PHY modes listed in Table <xref>” (or similar text)‏ • New table: • SC: • HSI: • AV: LRP mode 0, 1, 2, or

  9. Dr. James P. K. Gilb, SiBEAM Channel probing (comment 38)‏ • Channel probing needs to be done not only at the start of a connection, but continuously during life of the connection. • Using Implied-ACK allows the quick response envisioned in the current channel probing proposal. • In this case, then no special stream index is required. • Only one channel time request is required, worst case is two, which is currently what is done.

  10. Dr. James P. K. Gilb, SiBEAM Suggested resolution (comment 38)‏ • Remove channel probing stream index, keep channel probe request and response frames. • Remove MLMEs for channel probe, this is handled by the MAC without intervention of the higher layers. The MAC has the best understanding of the medium. • Rewrite channel probing section to use the following process: • Allocate channel time for stream • Send channel probe and receive response • Re-calculate required channel time • If different than current allocation, request modification to current allocation (either increase or decrease)‏ • Repeat this process as necessary while the stream connection is alive • Suggest keep only DEV-DEV probing, determining the highest possible data rate is only required for active connections.

  11. Comment 89 <missing definition> • 7.4.7, p. 18: UEP field (comment 17)‏ • 7.5.11.1, p. 21: Number of Beams field (comment 15)‏ • 7.5.11.2, p. 21: Transmit Beam Number field, Received Beam Number field, Beam Status Information field (comment 15)‏ • 7.5.11.6, p. 23: Channel Status Information field (comment 16)‏

More Related