asked if there are any objections to proceed with this agenda – no objections. agenda approved. Presentations Straw Polls on 11-14-1161 and 11-14-1162 by Eric Wong (Apple) Straw Poll #1.1: Do you agree, in principle, to add metrics corresponding to energy efficiency to the evaluation methodology document (11-14/571r3)? Discussion: No discussion. Result: Approved with no objection. Straw Poll #1.2: Do you support adding the following definition for Energy Efficiency Ratio (EER) to the evaluation methodology document (11-14/571r3)? Energy efficiency ratio is defined as the ratio of average energy consumed for one bit of data successfully exchanged between STAs using any new proposed power save mechanism over the baseline power save mechanism Discussion: No discussion. Result: Approved with no objection. Straw Poll #1.3: Do you support adding these metrics to evaluation methodology document (11-14/571r3)? Metric Units Definition Per-STA energy per TX bit Joules/bit Total energy consumed by a STA divided by the total number of successful data bits transmitted by the STA Per-STA energy per RX bit Joules/bit energy consumed by a STA divided by the total number of successful data bits received by the STA Discussions Energy is implementation dependent and it may be difficult to the number. Result: Approved with no objection. Straw Poll #2.1: Do you support adding standardized power tables for the purpose of computing energy consumption to the simulation scenario document (11-14/980r2)? Discussions How to the result – use the common table. Discussed if the in straw poll 2.2 is enough. Result: Approved with no objection. Poll #2.2: Do you support adding the following power table (whose entries are TBD) to the simulation scenario document (11-14/980r2)? Power State Average Power Consumption (mW) Bandwidth = { 20 MHz }, Band = { 2.4 GHz, 5 GHz }, NSS = { 1 }, Number of TX/RX antennas = { 1 }, TX power per antenna = { 15 dBm } Transmit
Confused to hear the presentation. While assuming that it is LTE system to have some coexisting mechanism, the presenter proposes a solution. like to know how much the duty cycle approach scales. What if more than one LTE systems and Wi-Fi system are operating in proximity. TG Motions Motion on Functional Requirements (14/1167r2) Motion #1: Move to add the following text to the TGax Functional Requirement document : 2.x Latency Requirements TGax Rx: The 802.11ax amendment shall bring latency to a desirable level to meet QoS requirement in Moved by Yonggang Fang (ZTE), Discussions Requirement for the latency is not quantified. Suggested removal of the latecy. QoS requirement. Result: Y/N/A = 30/7/30, motion passes. Motion #2: Move to add the following text to the TGax Functional Requirement document : 2.x Robustness Requirements TGax Rx: The 802.11ax amendment shall bring PER to a desirable level to make the link robust in high dense deployment scenario. Moved by Yonggang Fang (ZTE), Seconded by Sun Bo (ZTE) Discussions This is not something that should be in the functional requirement. It be a part of link adaptation. It is not clear how it will be addressed. Result: Y/N/A = 7/48/21, motion fails. Recess @ 10:00 AM until PM1 (13:30) today. Thursday, September 18th, 2014, PM1 Session (13:30-15:30) The meeting called to order by Osama Aboul-Magd (Huawei Technologies), the chairperson of the TGax, @ 13:30. About 160 people are in the room at the beginning of the session. Agenda Doc.11-14/1033r4 is on the server. Rev 5 is the working document Reminder and Announcements Chairperson reminded IEEE 802 and 802.11 IPR P&P. Chair asked people to announce name and affiliation when addressing for the first time in the session. Chairperson reminded attendance. Agenda for this session Thursday PM1