1 / 6

IEEE 802.11ah Requirements Discussion

IEEE 802.11ah Requirements Discussion. Date: 2011-03-3. Authors:. This submission is intended as a follow up to submission 11-11/527 on requirements for IEEE 802.11ah . In particular, this submission follows up on the number of associations per AP and making range quantifiable . Abstract.

kellsie
Download Presentation

IEEE 802.11ah Requirements Discussion

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. IEEE 802.11ahRequirements Discussion Date: 2011-03-3 Authors: David Halasz, OakTree Wireless

  2. This submission is intended as a follow up to submission 11-11/527 on requirements for IEEE 802.11ah. In particular, this submission follows up on the number of associations per AP and making range quantifiable. Abstract David Halasz, OakTree Wireless

  3. PAR calls out range • In section 5.2 of 11-10-0001r13 • Issue : This is vague and should relate to link budget. • Suggestion • Agree on conditions and then use appropriate channel model to indicate range, conditions and link budget. Range discussion David Halasz, OakTree Wireless

  4. Range : distance based on separate discussion (1 or 2 km) AP antenna height = 30 feet Client antenna height = 2 feet Dense urban environment[2] MIMO 1x1 Transmit power = ? Receiver sensitivity = ? Range discussion David Halasz, OakTree Wireless

  5. In Specification Development process 11-11/239r2, “…The Task Group shall adopt, through a 75% approval in the Taskgroup, a Functional Requirements document that must be met by the proposed specification, including System Level Performance Targets and Simulation Scenarios for those Targets…” • Since number of associations will have an impact on the system design it should be reflected in the functional requirements document. • Suggestion • Include 6000 associations per AP or indicate beyond 2007. Number of associations David Halasz, OakTree Wireless

  6. 11-10-0001-13-0wng-900mhz-par-and-5c http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/PAP02_04122011_r2.pptx 11-11-0457-00-00ah-potential-compromise-of-802-11ah-use-case-document 11-11-0239-02-00ah-proposed-selection-procedure.docx References David Halasz, OakTree Wireless

More Related