ITRI Proposal Response to Comparison Criteria

August 2004 doc.: IEEE 802.11-04/0930r0

IEEE P802.11 Wireless LANs ITRI Proposal Response to Comparison Criteria

Date: August 13, 2004

Author: Yung-Yih Jian(1), Pangan Ting, Wei-Ping Chuang, Chun-Chun Kuo, Chang-Lung Hsiao

Wei-De Wu(2)

Chih-Kai Chen(3)

(1)Industiral Technology Research Institute (ITRI) Computer and Communications Research Laboratories (CCL) Bldg.14, 195 Sec. 4, Chung Hsing Rd. Chutung, Hsinchu, Taiwan 310, R.O.C Phone : +886-3-5914707 Fax : +886-3-5820371 e-Mail: {yyjian, pating, joeChuang, godeman, clhsiao}@itri.org.tw

(2)National Tsing Hua University Institute of Communications Engineering [email protected]

(3)Stanford University Department of Electrical Engineering chihkai@ stanford.edu

Abstract This document contains responses to the comparison criteria (IEEE 802.11-03/814r31) for ITRI’s proposal (partial proposal; preamble design) to TGn. The responses are summarized in the following tables.

Submission page 1 August 2004 doc.: IEEE 802.11-04/0930r0

1 Additional Disclosures

Numb Name Definition Status of Notes Responses er this AD AD1 Reference A list of related IEEE submissions, both ITRI preamble submissions documents and presentations. spec. ITRI CC response ITRI FR response AD2 TCP Model Include a reference to the TCP protocol N/A Parameters type (e.g. Reno) and the parameter values associated with that protocol used for all MAC simulations. AD3 MAC Include a description of the simulation N/A simulation methodology used for MAC simulations, methodology including a description of how the PHY and its impairments are modeled. AD4 MAC For each MAC simulation, report the total N/A simulation channel width occupied. occupied channel width AD5 Justification of For each application with a PLR < 10^-4, 17/1 on 10 N/A low PLR rates proposal shall justify that the proposed May, 2004 achieved PLR could be met.

2 Response to Comparison Criteria

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional CC2 Regulator The proposal shall state any known problems with None Mandator Textual N/A (In this y regulatory compliance with at least the following required y Statemen proposal, we complian domains: USA, Japan, Europe, China. t ce adopt the same frequency band and channalization as 802.11a) CC3 List of List the goodput results (CC20, metric 1) for Scenarios Mandator List of N/A (PHY partial goodput scenarios 1,4 and 6. 1,4,6 y Goodput proposal, results results. for usage Impairments preamble design ) models as defined for 1,4 and 6. CC20

CC6 PHY Give an indication of the PHY complexity, relative None Optional Numeric N/A (PHY partial complexi to current 802.11a PHYs (e.g. gate counts, MIPS, required value in proposal, ty filtering, clock rate, etc.). any suitable preamble design ) form CC7 MAC Give an indication of the MAC processing None Optional Numeric N/A (PHY partial processin complexity, relative to implementations of 802.11- required value in proposal, g 1999 (Rev 2003), and published amendments any complexi (e.g. gate counts, MIPS, memory, clock rate, etc.) suitable preamble design ) ty form CC11 Backwar Provide a summary description of the means, if None Mandator Bullet- With the proposed d any, by which backward compatibility with 802.11- required y point preamble design, compatib 1999 (Rev 2003) and 802.11g is achieved in the summary ility with band(s) covered by the proposal, including and the system is 802.11- references to the sections in the technical proposal reference backward 1999 document where the complete details are given. to section compatible with (Rev in 802.11a. 2003) technical and specificat Please refer to 802.11g ion. Section 3.2.1 of “ITRI preamble spec.”. CC15 Sharing Goodput of legacy device in HT network and Simulation Mandator Report N/A (PHY partial of impact of legacy device on the goodput of the HT scenarios 17- y values of proposal, medium devices. 19. metrics with No T1-T4. preamble design ) legacy Report the following measurements : impairments devices --T1: the goodput reported in simulation scenario 17. --T2: the goodput reported in simulation scenario 18. --T3: the goodput reported for STA1 in simulation scenario 19. --T4: the goodput reported for STA2 in simulation scenario 19. CC18 HT This metric relates to the ability of the proposal to Simulation Mandator For each N/A (PHY partial Usage support the non-QoS application service level of Scenarios 1, y simulated proposal, Models each usage model, as defined by its simulation 4, and 6. scenario Supporte scenario. Note, this is report preamble design ) d (non measured results as QoS) For each simulated scenario: with QoS defined Report Goodput per non-QoS flow. flows turned in this Report aggregate goodput for non-QoS flows. on. CC. Report the ratio of aggregate Goodput for non-QoS flows to the total offered load for non-QoS flows. IM1,5,6 Note, a flow that transits through an AP (i.e. is

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional relayed within the BSS) is not counted as goodput Simulations at the AP. A flow that terminates at the AP is should be counted as goodput. conducted using perfect Note, backward TCP Ack flows shall be counted as synchronizati non-QoS flows. on and perfect channel estimation

CC19 HT This metric relates to the ability of the proposal to Simulation Mandator For each N/A (PHY partial Usage support the QoS application service level of each Scenarios 1, 4 y simulated proposal, Models usage model, as defined by its simulation scenario. and 6. scenario Supporte Note, this is (Vote in report preamble design ) d (QoS) For each QoS flow, the proposal shall report the measured TGn 10 results as packet loss rate (defined below) and compare it to with non- May defined the specified QoS objective. QoS flows 2004) in this turned on. CC. The proposal shall also report the number of these IM1,5,6 flows that satisfy their QoS objective . Also report the fraction of QoS flows that satisfy their QoS Simulations objective. should be conducted For the purpose of this criterion, packet loss rate using perfect (PLR) for a QoS flow is defined as the number of synchronizati MSDUs that are not delivered at the Rx MAC SAP on and perfect within the specified delay bound, divided by the channel total number of MSDUs offered at the Tx MAC estimation SAP for that flow during the simulation . CC20 BSS Three aggregate goodput metrics are to be reported. Simulation For each N/A (PHY partial Aggregat Scenarios 1, 4 Mandator simulated proposal, e Metric 1 is defined as the sum of goodput across all and 6. y scenario, Goodput flows in the simulation scenario. IM1,5,6 report preamble design ) at the values of MAC Metric 2 is defined as the aggregate number of bits Simulations metrics data SAP in MSDUs that are delivered at the Rx MAC SAP should be 1-3 within the specified delay bound of the flow’s conducted defined defined QoS, divided by the simulation duration. using perfect in here synchronizati Metric 3 is defined as the sum of goodput across all on and perfect flows that meet their QoS objective in the channel simulation scenario. estimation

Notes: Metric 1 includes flows that fail to meet their QoS objectives. Metric 2 excludes MSDUs that exceed the delay bound. Metric 3 excludes all MSDUs from flows that fail to meet their QoS objectives.

Note, a flow that transits through an AP (i.e. is relayed within the BSS) is not counted as goodput at the AP. A flow that terminates at the AP is counted as goodput.

CC24 MAC MAC efficiency is defined as the aggregate Metric Simulation For each N/A (PHY partial Efficienc 2 goodput in CC20 divided by the average physical Scenarios 1, Mandator simulated proposal, y layer data rate. 4, and 6. y scenario, IM1,5,6 Report preamble design ) Let r(n) denote the rate at which the nth successful MAC Data MPDU is transmitted. Simulations efficienc Let t(n) denote the PPDU transmission time of the should be y metric nth successfully transmitted Data MPDU (i.e. conducted defined including preamble, PLCP header). using perfect in here synchronizati Define the average PHY data rate r as on and perfect channel r = ∑ r(n)t(n)/ ∑t(n) estimation

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional

CC27 Throughp Report curves of Goodput (bps) vs. range (m). Simulation For the N/A (PHY partial ut / Scenario 16 Mandator simulated proposal, Range Also provide all MAC parameters and settings IM1,5,6 y channel (e.g., interframe spacings, fragmentation thresholds models, preamble design ) etc.) and all PHY parameters and settings used to Simulations Present obtain the curves. should be the conducted required For the following channel models using perfect curves. from [4]: synchronizati Model B Residential on and perfect Also Model D Typical Office channel provide, estimation textual descriptio n of paramete r and setting values.

CC28 Throughp Report curves of Goodput (bps) vs. range (m) , Simulation For the N/A (PHY partial ut / when operating in a 20 MHz bandwidth. scenario 16 Mandator specified proposal, Range in IM1,5,6 y channel 20MHz Also provide all MAC parameters and settings models preamble design ) (e.g., interframe spacings, fragmentation thresholds Simulations from [3]: etc.) and all PHY parameters and settings used to should be Present obtain the curves. conducted curves of using perfect Goodput For the following channel models synchronizati (bps) vs. from [4]: on and perfect range Model B Residential channel (ml, Model D Typical Office estimation when operating in a 20 MHz bandwidt h.

Disclose all MAC paramete rs and settings (e.g., interfram e spacings, fragment ation threshold s etc.) and all PHY paramete rs and settings used to obtain the curves. CC46 MAC Provide a list of optional features of None Mandator Text list N/A (PHY partial Compatib 802.11a/b/d/e/g/h/i/j that are required for HT required y of proposal, ility and operation, and a summary description of the features paramete manner in which they are used. Include references plus preamble design ) rs. to the sections in the technical proposal document reference where the complete details are given. s to sections in proposed technical specificat

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional ion document . CC47 MAC Provide a summary description of MAC extensions None Mandator Text list N/A (PHY partial extension beyond 802.11a/b/d/e/g/h/i/j that are required for required y of proposal, s HT operation. Include references to the sections in features the technical proposal document where the plus preamble design ) complete details are given. reference s to sections in proposed technical specificat ion document . CC51 Data A list of PHY layer data rates, and for each data None Mandator Text list N/A (PHY partial rates rate, specify the used modulation techniques, required y of rates proposal, number of Tx antennas, coding rate and bandwidth. supported , marked preamble design ) Specify which of the rates are mandatory and mandator which are optional. y or optional For adaptive rate proposals, specify the range of plus achievable rates or, if possible, state the achievable additiona rates in a closed form expression. l paramete rs as described in this CC.

For adaptive rate proposals , the range of achievabl e rates. CC42 Preamble Specify the proposed preambles. None Mandator Referenc In this report, we s Summarize the important properties of each part required y e to propose a novel the proposed preambles. section in Include references to the sections in the technical technical preamble structure proposal document where the complete details are specificat for IEEE 802.11n given. ion standard. The defining proposed Specify how the use of any new preamble affects preamble reception by legacy STA. s. preamble structure For each is compliant with preamble the FRCC type documents and supported : has good Mean properties for and std of frame detection peak to sidelobe and channel ratio of estimation. The the structure consists autocorre of 10 periods of lation function 32-sample short PAPR training symbols values. (STSs), and 4 Descripti periods of 64- on and evaluatio sample long n of training symbols cross-

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional correlatio (LTSs). n propertie s. For details please refer to “ITRI Preamble spec.”

CC51 Channeli Specify the channelization – i.e. the adjacent None Mandator Minimu The same as the .5 zation channel spacing. required y m specification of channel spacing 802.11a. for all operation al modes CC52 Spectral Define the transmit spectral mask requirements for None Mandator For each The same as the Mask each channelization of the proposal. This must be required y channeliz specification of under the same PA backoff used for performance ation: simulations. IM1 graph of 802.11a. spectral output (dBm) vs. frequenc y offset from center frequenc y (MHz).

CC58 HT The number of bps/Hz during the PSDU carrying a Mandator The N/A (PHY partial Spectral Data MPDU when demonstrating a goodput value Using y number proposal, Efficienc of at least 100Mbps. Specify the phy data rate simulation of bps/Hz y used during this test. scenario 16 and preamble design ) defined in [3]. specified IM1,5,6 data rate. CC59 AWGN Identify the performance in an idealized channel for None Mandator For N/A (PHY partial PER a PSDU length of 1000B. The rows or columns of required y proposals proposal, performa the channel shall be orthogonal to each other as which nce follows: take the first Nr x Nt elements of the have any preamble design ) Fourier matrix with dimension max(Nr,Nt). Show None mode PER versus SNR curves for 5 supported data rates generatin representative of the proposal's rate set, including Simulations g 2 or the maximum and minimum rates. If the proposal should be more supports fewer than 5 data rates, all supported data conducted independ rates should be shown. using perfect ent synchronizati streams, Averaging should occur over a minimum of 100 on and perfect show 4 packet errors down to 1% PER channel graphs estimation for the Refer to [7] for a definition of the Fourier matrix. values Nr=Nt Note: SNR is defined in section 2. from 1 to 4. For proposals that do not have any mode generatin g 2 or more independ ent streams, show a single graph for Nr=Nt=1.

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional For each graph: Plot a curve of log PER vs. SNR (dB) for each of 5 supported data rates on the same axes. CC67 PER Show either or both of the following two sets of None Mandator For each N/A (PHY partial performa performance curves: required y of proposal, nce in IM1-6 channel non 1.) Show the PER curves for 5 supported data rates models preamble design ) AWGN representative of your rate set including your B, D and channels maximum and minimum rates. If the proposal E: supports fewer than 5 data rates, all supported data rates should be shown. Plot PER versus SNR Plot a averaged over time per receive antennas for curve of PSDUs of length 1000B. Averaging should occur log PER over a minimum of 100 MPDU errors down to 1% vs. SNR PER. Each packet should use an independent (dB) for channel realization. each of 5 supported 2.) Show curves for both achieved average physical data layer data throughput and PER, as a function of rates. total SNR for 1000B PSDUs. These results should be generated with a rate selection algorithm active. Addition Data throughput is defined as the total number of ally, for bits successfully received in the data portion of the channel PPDU, divided by total transmission time, not model D: including overheads such as preamble and backoff. Plot a The throughput shall be averaged over at least 100 curve of independent realizations of the channel, each log PER realization long enough to allow simulation of rate vs. SNR adaptation with subsequent transmission of one or (dB) for more PPDUs while the Doppler process evolves. the The same number of PPDUs shall be simulated for highest each channel realization. In addition a minimum supported number of PPDUs, equal to 100 divided by the data rate target FER, shall be simulated to determine incorpora throughput. ting the Fluoresce Total received signal power is summed over all nt effect transmit antennas. There shall not be any a priori on the knowledge of the channel or synchronization at the same receiver or transmitter. This should be simulated graph as for channel models B, D, and E. The simulations the other should all include the Doppler effect as specified in curve for the text of the channel model document. channel model D. All models should be run without the fluorescent effect but additionally model D should be run with the fluorescent effect on the highest data rate. The interferer to carrier energy ratio of the fluorescent effect shall be equal to its average value (0.0203).

The shadowing variance should be 0.

These simulations are performed using the NLOS version of the specified channel models.

Note: SNR is defined in section 2. CC67 Offset Provide the impact on PER of carrier frequency None Numeric N/A (PHY partial .2 Compens offset and symbol clock offset by comparing to the required Mandator results proposal, ation PER achieved at the lowest average SNR that IM1-5 y achieves a 10% PER for PSDUs of length 1000 preamble design ) bytes in channel E (NLOS) with no carrier and

Num Name Definition Simulation Mandato Disclosu Response ber Scenario / ry / re Impairments optional symbol clock offset. The symbol clock shall have the same relative frequency offset as the carrier frequency offset.

Also, provide that same impact on PER using an SNR of 50dB in channel E (LOS). The carrier offset difference at the receiver relative to the transmitter shall be -40ppm and +40ppm.

The results shall be presented in such a manner that it is clear whether there are specific values of offset for which the proposed system has better or worse performance relative to no offset.

Simulations shall be performed under the same conditions as those in CC 59 & 67. CC80 Required Give a summary description of changes to a legacy None Mandator A bullet- N/A (PHY partial changes 802.11 PHY. Give references to sections in your required y point list proposal, to 802.11 specification that give the complete details. of main PHY features preamble design ) with reference to the section in the technical specificat ion.

Submission page 9