1 / 13

Response to 802.15.3 Coexistence Presentations

Response to 802.15.3 Coexistence Presentations. Date: 2009-05-12. Authors:. Outline. Motivation 802.15.3 Architecture and Frame Format 802.11 Architecture and Frame Format What are needed to support CMS sync frames? Conclusion. Motivation.

amora
Télécharger la présentation

Response to 802.15.3 Coexistence Presentations

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. Response to 802.15.3 Coexistence Presentations Date: 2009-05-12 Authors: Michelle Gong, Intel

  2. Outline • Motivation • 802.15.3 • Architecture and Frame Format • 802.11 • Architecture and Frame Format • What are needed to support CMS sync frames? • Conclusion Michelle Gong, Intel

  3. Motivation • In the March IEEE meeting, Common Mode Signaling (CMS) sync frame defined in 802.15.3c was introduced as an inter-system coexistence mechanism • IEEE 802.11-09/0370r1 • IEEE 802.11-09/0372r0 • The goals of this presentation are: • To give a high level overview of 802.15.3 and 802.11 architectures and frame formats • To explain why TGad shouldn’t be required to support CMS sync frame Michelle Gong, Intel

  4. 802.15.3 Architecture PNC: PicoNet Coordinator Neither PNC nor DEV bridges data for other DEVs. All data communications are within the piconet only Michelle Gong, Intel

  5. 802.15.3 MAC Frame Format Octets: 2 2 1 1 3 1 0 or 4 • 802.15.3 MAC general frame header is 10 octets • 2-octet PNID indentifies the piconet • PNID is generated by the PNC that starts the piconet • 1-octet DEVID, i.e. DestID and SrcID • PNC assigns a DEVID to a DEV upon association • 802.15.3 does not support data communication among different piconets • Therefore, a DEVID that can uniquely identify a DEV within the piconet is sufficient Fragmentation Control Stream Index Frame Control PNID DestID SrcID Frame Payload FCS MAC header Michelle Gong, Intel

  6. Frame Header for 15.3c CMS • PHY header and MAC header are combined together • The parity check is performed over the combined header Michelle Gong, Intel

  7. 802.11 Architecture BSS: Basic Service Set • Ad hoc networks such as IBSS, mesh, etc. define new sets of functionalities but they also maintain backward compatibility with the basic 802.11 architecture AP: Access Point ESS: Extended Service Set DS: Distribution System DSS: Distribution System Service IBSS: Independent BSS Michelle Gong, Intel

  8. 802.11 MAC data frame header is 30 or 36 octets long and increasing It contains various control fields, a duration/ID field, and three or four address fields (pre-TGs) The MAC address field contains the IEEE 802 48-bit address Each MAC address uniquely identifies a STA globally, which guarantees that each STA is uniquely addressable within the ESS BSSID, set to the MAC address of the AP, is a globally unique identifier too 802.11 MAC Frame Format 0 or Michelle Gong, Intel

  9. 802.11 PPDU Frame Format • In 802.11, the PHY header and MAC header are modulated and coded separately (a fully layered approach) • The PLCP header identifies the duration of the packet to aid CCA • The PLCP header has its own parity check bit or CRC FCS PLCP Preamble PLCP Header MAC Header Frame Body Sent at data rate Sent at basic rate Michelle Gong, Intel

  10. TGad Functional Requirements • Functional requirements of TGad: • [Req9] The TGad amendment must maintain the network architecture of the 802.11 system. • [Req10] The TGad amendment must maintain backward compatibility to 802.11 management plane. • 802.11 and its amendments define a rich set of management features that can be reused for 60GHz networks 802.11h/k/r/… 802.11 MAC 802.11/e/n 802.11 PHY 802.11/a/b/g/j/n/y Michelle Gong, Intel

  11. Decoding and Transmitting an 802.15.3c Sync frame requires a “dual-mode” device • In order to process the Sync frame, a TGad device would require • Support the CMS PHY • Support both the 15.3c and 802.11 addressing schemes • Support both the 15.3c and 802.11 frame formats • This is a “dual-mode” device Michelle Gong, Intel

  12. Distributed synchronization and scheduling are very hard problems • To utilize the sync frame solution, all co-located PNCs need to be synchronized and need to synchronize their schedules • Distributed synchronization is an NP-Complete problem • Centralized scheduling is an NP-Hard problem • Distributed scheduling is even more challenging due to the latency and overhead introduced by communication messaging and the fact that there is no single control entity • Directional transmission, the lossy nature of wireless media, and bursty traffic further complicate the problem • If associated DEVs do not support sync frames, coexistence is hard to achieve in some usage scenarios due to the hidden node problem • Need to evaluate the tradeoff between complexity and performance improvement in practical scenarios Michelle Gong, Intel

  13. Conclusion • As defined in TGad’s functional requirements, TGad needs to maintain the 802.11 frame format and addressing scheme • As an amendment to 802.11, the TGad amendment must maintain the network architecture of the 802.11 system, e.g. infrastructure basic service set, extended service set, access point, and station. • Furthermore the system must maintain backward compatibility to 802.11 management plane, e.g. association, authentication, security, measurement, capability exchange, and MIB. • Due to the differences in 802.11 and 802.15.3, architectures, frame formats and addressing schemes, TGad spec will be different from the 15.3c spec • TGad should not be required to support CMS sync frame Michelle Gong, Intel

More Related