Scribd Logo
Upload

Welcome to Scribd!

  • 26 views

    Doc.: IEEE 802.11-12/0838r0: Regular Beacon

    Uploaded by

    Abid Jan
    The document proposes a short beacon format for 802.11 to reduce overhead compared to regular beacons. It suggests the short beacon can carry optional fields but not full BSS information, while the AP may still send full beacons periodically. It discusses allowing full beacons to use the same format as short beacons but including all necessary fields, and indicates STAs waiting for full beacons need to distinguish beacon types. It asks for a straw poll on supporting a unified beacon format based on the existing short beacon.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Doc.: IEEE 802.11-12/0838r0: Regular Beacon

    Uploaded by

    Abid Jan
    26 views4 pages
    The document proposes a short beacon format for 802.11 to reduce overhead compared to regular beacons. It suggests the short beacon can carry optional fields but not full BSS information, while the AP may still send full beacons periodically. It discusses allowing full beacons to use the same format as short beacons but including all necessary fields, and indicates STAs waiting for full beacons need to distinguish beacon types. It asks for a straw poll on supporting a unified beacon format based on the existing short beacon.

    Original Description:

    Details of comm

    Original Title

    Bea

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document proposes a short beacon format for 802.11 to reduce overhead compared to regular beacons. It suggests the short beacon can carry optional fields but not full BSS information, while the AP may still send full beacons periodically. It discusses allowing full beacons to use the same format as short beacons but including all necessary fields, and indicates STAs waiting for full beacons need to distinguish beacon types. It asks for a straw poll on supporting a unified beacon format based on the existing short beacon.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    26 views4 pages

    Doc.: IEEE 802.11-12/0838r0: Regular Beacon

    Uploaded by

    Abid Jan
    The document proposes a short beacon format for 802.11 to reduce overhead compared to regular beacons. It suggests the short beacon can carry optional fields but not full BSS information, while the AP may still send full beacons periodically. It discusses allowing full beacons to use the same format as short beacons but including all necessary fields, and indicates STAs waiting for full beacons need to distinguish beacon types. It asks for a straw poll on supporting a unified beacon format based on the existing short beacon.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 4

    doc.: IEEE 802.

    11-12/0838r0

    Regular beacon:

    Short beacon:

    • Compared with regular beacon in current 802.11 spec, short beacon eliminates several
    MAC header fields that are not useful
    • Short beacon needs not carry full BSS information
    • AP may choose to send a full beacon periodically or from time to time to advertise full
    BSS information
    • The Time of Next Full Beacon field shall be always present in the short Beacon frame if
    an AP transmits full (long) Beacon frames periodically
    Submission
    doc.: IEEE 802.11-12/0838r0

    • either
    • The current short beacon format allows a short beacon to
    carry optional IEs
    • Full beacon can use the same short beacon format, but
    should include a full set of fields/IEs needed to advertise
    the full BSS information

    Submission Slide 2
    doc.: IEEE 802.11-12/0838r0

    Full n

    • STAs may choose (or be forced) to wait for a full beacon to obtain the full
    BSS information
    • Since a short beacon can also carry some optional fields/IEs (but may not be
    the full set of fields/IEs), a STA waiting for a full beacon should be able to tell
    whether a received beacon is a short beacon or a full beacon
    • How to indicate a full beacon is TBD:
    – One example is to set the value of the Time of Next Full Beacon equal to the higher 3 bytes of
    the Timestamp field
    Submission Slide 3
    doc.: IEEE 802.11-12/0838r0

    Straw poll / Pre-Motion

    • Do you support the concept of a unified beacon format


    for short beacon and full beacon based on the short
    beacon format already present in SFD?

    Submission Slide 4

    You might also like