2 April 2011AbstractThis submission is intended as a follow up to submission 11-11/527 on requirements for IEEE ah. In particular, this submission follows up on the number of associations per AP and making range quantifiable.David Halasz, OakTree Wireless
3 Range discussion PAR calls out range April 2011Range discussionPAR calls out rangeIn section 5.2 of r13Issue : This is vague and should relate to link budget.SuggestionAgree on conditions and then use appropriate channel model to indicate range, conditions and link budget.David Halasz, OakTree Wireless
4 April 2011Range discussionRange : distance based on separate discussion (1 or 2 km)AP antenna height = 30 feetClient antenna height = 2 feetDense urban environmentMIMO 1x1Transmit power = ?Receiver sensitivity = ?David Halasz, OakTree Wireless
5 Number of associations April 2011Number of associationsIn 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.SuggestionInclude 6000 associations per AP or indicate beyond 2007.David Halasz, OakTree Wireless
6 References 11-10-0001-13-0wng-900mhz-par-and-5c April 2011Referenceswng-900mhz-par-and-5cah-potential-compromise-of ah-use-case-documentah-proposed-selection-procedure.docxDavid Halasz, OakTree Wireless
Your consent to our cookies if you continue to use this website.