1 / 9

TGad Architecture Discussion Topics

TGad Architecture Discussion Topics. Authors:. Date: 2012-01-04. Abstract. This document contains topics for discussion concerning the architectural models introduced by the 802.11ad Amendment, Draft 5.0. Outline. Multiple MAC (entities) sharing one PHY (sub-clause 4.9.3)

jamal
Download Presentation

TGad Architecture Discussion Topics

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. TGad Architecture Discussion Topics Authors: Date:2012-01-04 Mark Hamilton, Polycom, Inc.

  2. Abstract This document contains topics for discussion concerning the architectural models introduced by the 802.11ad Amendment, Draft 5.0 Mark Hamilton, Polycom, Inc.

  3. Outline • Multiple MAC (entities) sharing one PHY (sub-clause 4.9.3) • Multi-band operation (sub-clause 4.9.4) • Transparent FST • Non-transparent FST Mark Hamilton, Polycom, Inc.

  4. Multiple MAC (entities) sharing one PHY • Confirm the following advantages over completely separate STAs: • One Association exchange (but still individual security exchanges) • Power Save transitions (in/out) together, in one exchange • Single ADDTS exchange • Share beamforming • Single AID (and ATIM behavior) • Single MMAL Cluster setup and maintenance • Other (significant) advantages? Mark Hamilton, Polycom, Inc.

  5. Multiple MAC (entities) sharing one PHY (cont) • Advantages over single STA (single MAC entity, and one PHY): • ??? • Any importance/impact on FST? • Is this needed? • Note that this concept has very few references in the Draft: • Figure 4-16a • last sentence of the first paragraph of 4.9.3, and the paragraph at lines 21-23 in 4.9.3 • 7.3.5.16 • Three other minor references • Can keep MM-SME and related coordination concepts for multiple STAs Mark Hamilton, Polycom, Inc.

  6. Multi-band operation, transparent FST • Confirm: Multiple MACs can use separate PHYs, and be coordinated by MM-SME, and participate in an MMAL Cluster, and do FST (right?) • Is there an architecture of a single MAC using multiple PHYs? • See 4.9.4 (page 51 line 20), “A multi-band capable device _can_ also support multiple MAC addresses …” (emphasis added) • If the device does not use multiple MAC addresses, then this is meant to be multiple MAC entities which use the same MAC Address, right? (Not a single MAC entity with multiple PHYs?) Mark Hamilton, Polycom, Inc.

  7. Multi-band operation, transparent FST (cont) • Confirm: there are multiple MAC entities, but only one each of: • MAC Address • MAC_SAP • RSNA management • What is unique per MAC entity? Is that valuable, or more annoying than helpful (more state to move at FST, etc.)? • What is the advantage over a single MAC entity? Mark Hamilton, Polycom, Inc.

  8. Multi-band operation, transparent FST (cont) • How about a single MAC entity, with a single PHY, where the PHY can do multi-bands? • Similar to 802.11n’s PHY, which combined _and_ extended the 2.4GHz and 5GHz PHYs • Still need extensions to support dynamic mixing of successive frames (session operation in multiple bands and/or channels simultaneously), minor clarification that Association covers all PHYs at once, etc. • So, keep 11ad signaling to setup/manage the multi-band link (Multi-band element, On-channel tunneling, etc) • But, simplify the MAC architecture significantly Mark Hamilton, Polycom, Inc.

  9. Multi-band operation, non-transparent FST • What are the differences between this is other (existing) tunneling methods, 802.21, etc.? • If MAC Addresses change (at FST), upper layers need awareness of it, and methods to handle it. This is not a MAC function, but needs MAC facilities to support it (and optimize the speed of session transfers). • 802.11ad supplies those facilities. Needs upper layer to complete the solution (right?) Mark Hamilton, Polycom, Inc.

More Related