Doc.: IEEE 802.11-05/1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 1 Rx Sensitivity Metrics in Conductive Test Environment Notice: This document.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /1672 STA Provided Location November 2006 Donghee Shim, et alSlide 1 STA Provided Location Notice: This document has been prepared.
Advertisements

Doc: IEEE /0388r5November 2006 Submission Kwak, Rudolf, InterDigital 1 Extended Channel Switch Response Notice: This document has been prepared.
Doc.: IEEE /0085r2 Submission January 2005 Stephen McCann, Siemens Roke ManorSlide 1 TGu Closing Report Notice: This document has been prepared.
Doc.: IEEE /1116r0 Submission July 2006 Harry Worstell, AT&T.Slide 1 TGp Closing Report Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /2163r0 Submission July 2007 Cam-Winget, Smith, WalkerSlide 1 A-MPDU Security Issues Notice: This document has been prepared to assist.
Doc.: IEEE /0006r0 Submission March 2005 Steve Shellhammer, Intel CorporationSlide 1 What is a CA document? Notice: This document has been prepared.
Doc.: IEEE /0018r0 Submission June 2005 Tom Siep, Cambridge Silicon Radio PlcSlide a Coexistence Characteristics Notice: This document.
Doc.: IEEE /0028r0 Submission July 2006 Steve Shellhammer, QualcommSlide 1 Coexistence Scenario – A Pair of Unlicensed Wireless Networks Notice:
Doc.: IEEE /0029r0 Submission July 2006 Steve Shellhammer, QualcommSlide 1 Coexistence Scenario – A Pair of Unlicensed Wireless Networks, one.
Doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 1 Writing a Coexistence Assurance Document Notice: This document has.
Doc.: IEEE Submission 2/8/2014 Dee Denteneer, Philips et al.Slide 1 A BTE issue; also related to Beacon Bloat Notice: This document has.
Doc.: IEEE /0026r0 Submission Dec Luke Qian, Doug Smith Cisco Systems, IncSlide 1 BA Reordering for A-MPDU Notice: This document has been.
Doc.: IEEE /xxxxr0 Submission July 2006 Tom Siep, Cambridge Silicon Radio PlcSlide 1 Discussion of Definitions in 0023r2 Notice: This document.
Doc.: IEEE /0365r0 Submission July 2007 Monisha Ghosh, PhilipsSlide 1 Rate ¼ Convolution Code IEEE P Wireless RANs Date: Authors:
Doc.: IEEE /0077r0 Submission September 2007 Rich Kennedy, OakTree WirelessSlide 1 5GHz RLANs and the Spectrum Challenges from the Weather Radar.
Doc.: IEEE /0178r0 Submission January 2006 Clint Chaplin, Wi-Fi AllianceSlide 1 Wi-Fi Alliance Liaison Report Notice: This document has been prepared.
Doc.: IEEE /0132r0 Submission May, 2008 Gabor BajkoSlide 1 Proposal to define ES specific IEs Notice: This document has been prepared to assist.
Doc.: IEEE /0592r0 Submission May, 2008 Gabor BajkoSlide 1 ES Access Notice: This document has been prepared to assist IEEE It is offered.
Doc.: IEEE /1465r0 Submission September 2006 K. Kim et al.Slide 1 RA-OLSR Text Updates Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /1812r0 Submission November 2006 Eldad Perahia (Intel)Slide 1 More RX Procedure Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0797r0 Submission May 2006 Steve Whitesell for Ariel Sharon as TIA LiaisonSlide 1 Liaison to TIA TR-41.4 from IEEE Notice:
Doc.: IEEE /0202r1 Submission January 2007 Darwin Engwer, Nortel NetworksSlide 1 Introduction to IMT-Advanced Notice: This document has been prepared.
Doc.: IEEE /1007r0 Submission September 2005 Fred Haisch, Proxim WirelessSlide 1 Alternative Lock-up Solution Notice: This document has been prepared.
Doc.: IEEE /1013r0 Submission July 2006 Denis Kuwahara, BoeingSlide 1 [RR-TAG Liaison Heads Up] Notice: This document has been prepared to assist.
Doc.: IEEE /0040r0 Submission Sept 2005 Tom Siep, Cambridge Silicon Radio PlcSlide 1 Liaison Report From Coexistence TAG Notice: This document.
Doc.: IEEE /0789r2 Submission July 2008 RuiJun Feng, China Mobile Times of an AP refusing associated requirements Date: Authors: Notice:
Doc.: IEEE /1785r1 Submission November 2006 Kazuyuki SakodaSlide 1 Some editorial updates on broadcast and so on Notice: This document has been.
Doc.: IEEE /0023r0 Submission July 2005 Steve Shellhammer, Qualcomm Inc.Slide 1 Questions to the Contention-based Protocol (CBP) Study Group Notice:
Doc.: IEEE /0282r0 Submission March, 2006 B Aboba, M Lefkowitz, K SoodSlide 1 Fast Transition in Neighbor Reports Notice: This document has been.
Doc.: IEEE /1829r1 Submission November 2006 Assaf Kasher et al. (Intel)Slide 1 Heff Defintion Notice: This document has been prepared to assist.
Doc.: IEEE /0374r0 Submission March 2006 Stephen McCann & Vivek GuptaSlide 1 Liaison from IEEE Discussion Notice: This document has been.
Doc.: IEEE /2209r0 Submission July 2007 Qi Wang, Broadcom CorporationSlide 1 PICS table entry on co-located interference reporting Date:
Doc.: IEEE /0211 Submission March 2005 Richard Williams, Texas Instruments, et alSlide 0 Beamforming should be smooth Notice: This document has.
Doc.: IEEE /0083r0 Submission May 2013 Keat-Beng Toh, Hitachi Kokusai ElectricSlide 1 Schedule of IEEE b MAC Technical Items by Hitachi.
Doc.: IEEE /1381r0 Submission September 2006 Assaf Kasher, IntelSlide 1 No use of Identity Matrix when extension LTFs are used Notice: This document.
Doc.: IEEE /0022r0 Submission July 2005 Steve Shellhammer, Qualcomm Inc.Slide 1 Discussion on Contention-based Protocol (CBP) Study Group Notice:
Doc.: IEEE /0035r0 Submission Jan 2005 Jon Edney InTalk2kSlide 1 Retiring the DS – a proposal Notice: This document has been prepared to assist.
Doc.: IEEE /1731r0 Submission November 2006 Eldad Perahia (Intel)Slide 1 Green Field Compromise Notice: This document has been prepared to assist.
Doc.: IEEE /0756r0 Submission May 2006 Todor CooklevSlide 1 HD video and multimedia over : an update Notice: This document has been prepared.
Doc.: IEEE /1944r0 Submission January 2007 Na Shan, Huawei Technologies Co., LtdSlide 1 BB selection using Connectivity Reports Notice: This document.
Doc.: IEEE /1750r0 Submission November 2006 james woodyatt / Apple Computer, Inc.Slide 1 40 MHz Operation in 2.4G with Greenfield Notice: This.
Doc.: IEEE /0758r1 Submission Sep 2005 Kobayashi, Trachewsky, Victor, Broadcom CorpSlide 1 Garden Grove 05: Proposed Adjacent Channel Interference.
Doc.: IEEE /0661r0 Submission July 2005 Alexander Tolpin, IntelSlide 1 TGT Conductive Test Environment and Metrics Notice: This document has been.
Doc.: IEEE /0741r0 Submission May 2006 Avi Gabay, IntelSlide 1 Blue Tooth\WiFi coexistence Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Doc.: IEEE /0088r0 Submission January 2006 Neeraj Sharma, IntelSlide 1 Adjacent Channel Interference Metric for OTA Indoor LOS Test Environment.
Doc.: IEEE /0129r0 Submission January 2006 Don Berry, Wireless Enterprise ConsultingSlide 1 Non Noise Interference Testing Notice: This.
Doc.: IEEE /0651r0 Submission May 2006 Royce Fernald - Intel CorporationSlide 1 Video Delivery vs. Attenuation in a Conducted Environment Notice:
Doc.: IEEE /xxxxr0 Submission March 2007 M. Kobayashi, Broadcom CorpSlide 1 Proposed ACI Modifications Notice: This document has been prepared.
Doc.: IEEE /1212r0 Submission TGT and MEF Liaison Notice: This document has been prepared to assist IEEE It is offered as a basis for.
Doc.: IEEE /0039r1 Submission January 2007 Larry Green, Ixia Slide 1 TCP Parameters and Settings Notice: This document has been prepared to assist.
Doc.: IEEE /0477r0 Submission March 2007 C. Wright, AzimuthSlide 1 Proposal for fixing additional issues in some subclauses Notice: This document.
Doc.: IEEE /0451r0 Submission May 2005 Kobayashi, Trachewsky, Victor, Broadcom CorpSlide 1 Cairns: Proposed Over the Air Test Methodology Draft.
[ Interim Meetings 2006] Date: Authors: July 2005
Latency-sensitive Applications - metrics
Power Consumption Measurement
San Francisco: Proposed Adjacent Channel Interference Test Methodology
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
MIMO performance Test Methodology proposal
OTA Testing For MIMO Based Devices – Run-to-Run Variation in Data
[Performance of ACI for clients]
TGu-changes-from-d0-01-to-d0-02
TGy draft 2.0 with changebars from draft 1.0
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGT Conductive Test Environment
Proposed ACI Modifications
TGT Conductive Test Environment
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Presentation transcript:

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 1 Rx Sensitivity Metrics in Conductive Test Environment Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date: November 2005 Authors:

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 2 Abstract This document introduces the description of the measurement of the Receive Sensitivity metric in a Conductive Test Environment for performance testing of wireless LAN devices. This presentations corresponds to the document t-RX-Sensitivity-Metric-in-Conductive-Setup.doc and it extends the metrics covered by document t.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 3 Summary Purpose Test Equipment Typical setup Test description.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 4 Purpose of Rx sensitivity test This is a secondary metric that is defined in which helps understanding the DUT Receiver PER vs. Attenuation performance.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 5 Test Equipment DUT – any wireless device (AP or Client) that includes relevant SW running on the specific platform WLCP (WireLess CounterPart) - reference AP or a reference Client Shielded enclosure for DUTs and WLCPs in order to isolate from extraneous signals Cables –RF-cables – connected to antenna connectors. –Wired LAN cables –Control cables Attenuators – to control attenuation (which means path loss) and RF signal input power

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 6 Test Equipment (cont.) Calibrated combiners, splitters and couplers – to handle different RF path, including antennas entries. Power Meter Devices – to measure RF signal power per packet Wired Traffic Generator to generate data traffic from DUT to WLCP and from WLCP to DUT on top of layer 2. Wired Traffic Analyzer to gather delivered data payload over time through wired interface on top of layer 2.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 7 Test Equipment (cont.) Test controller Includes the following capabilities, likely automated and controlled by dedicated SW: –The ability to control TX rates and TX power of WLCP and DUT –The ability to control power meters. –The ability to control attenuators –The ability to control Wired Traffic Analyzer –The ability to control Wired Traffic Generator.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 8 Rx sensitivity conductive setup

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 9 Calibration and isolation of the setup The setup shall be properly isolated from external interference and other unwanted signals. Prior to beginning the specific test, the test equipment shall be calibrated, taking into account losses due to cables, couplers, splitters, etc. All test software shall be verified. The test setup may be monitored during the test to ensure that the test conditions do not change unintentionally.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 10 Rx sensitivity Test This secondary metric is the input signal level at the point –where the number of successfully transferred data payload packets vs. the overall sent data packets (from MAC SAP of WLCP to MAC SAP of DUT) –meets the threshold requirement as specified in the specs. The RX Power of the RF signal measured at the antenna connector of DUT is controlled by the Attenuation between the DUT and WLCP. Applicable for wireless clients, both IBSS and BSS Correlates with end-user experiences of TPT vs. range in a real life environment which is dependent on Rx sensitivity and rate scaling.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 11 RX PER calculation #_packets_sent is the number of broadcast data packets that were injected to WLCP through wired interface by Traffic Generator and transmitted by WLCP. –Each broadcast data packet is transmitted once and ACK is not required. –Multicast packet may be used instead of Broadcast packets. #_packets_delivered is the number of broadcast data packets that were injected to WLCP through wired interface by Traffic Generator, transmitted by WLCP and captured by Wired Traffic Analyzer via wired interface. PER = (#_packets_sent - #_packets_delivered ) / (#_packets_sent).

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 12 Procedure Setup DUT according to the initial configuration and associate with WLCP. Enforce WLCP to transmit broadcast data packets on the specific rate, measure PER vs. Attenuation and record PER per fixed rate. –Repeat for all relevant fixed rates. –Calculate the maximal Received signal level where the PER is above the threshold.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 13 Procedure - details Step 0: Setup DUT to the initial configuration and associate with WLCP. Step 1: Set attenuation current_value=min_value. Step 2: –Test controller generates data traffic such that WLCP generates the number of broadcast packets (1000) to DUT with specific rate. –packet size set as specified by spec (1000 or 1024). –The WLCP TX power is measured and recorded. –Test Controller counts the number of packets received by DUT and recorded. –Calculate PER=(#_packets_sent-#_packets_delivered)/#_packets_sent Step 3: Set attenuation current_value+=step_value Step 4: Repeat steps 2-3 until PER>10% (spec threshold 8% or 10%) Step 5: Repeat steps 0-4 for another channel Each attenuation value should be translated to DUT RX Power based on measured TX Power of WLCP, cables lost and attenuation values Optional modifier is Ambient temperature.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 14 Reporting The results can be summarized in the following table: Transmit Rate: rate Channel: channel Transmit Power (dBm)Attenuatio n (dB ) RX Power Level (dBm) Number of transmitted packets Number of received packets PER = 1-Recieved/Transmitted The results should be reported as a table or a graph of PER(RxPowerLevel) The Sensitivity should be calculated and reported as the point where the PER reaches percentage as define by the spec (10% OFDM, 8% CCK and DSSS)

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 15 Example of reporting table for one test Transmit Rate: 54MbpsChannel:11a, 5180MHz WLCP_TX_ Power [dBm] Attenuation [dB] Setup_Path _Loss [dB] RX_Input_Power [dBm] = WLCP_TX_Power – Attenuation - Setup_Path_Loss Number of transmitted packets Received packets RX PER [%]

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 16 Example of reporting graph with multiple units

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 17 Example Rx sensitivity summary report

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 18 Conclusions The Rx Sensitivity test has been proposed The proposal contains: –Purpose of the metric –Requirements for equipment –Requirements for test conditions –Description of the metric –Description of the setup –Procedure –Baseline, modifiers and test parameters –Reporting results requirements –Examples Recommendation: –Recommend TGT to adopt the content of document 11-05/XXXXr0 into the P draft.

doc.: IEEE /1158r0 Submission November 2005 Uriel Lemberger, IntelSlide 19 References [1] IEEE [2] IEEE /0661r0 TGT Conductive Test Environment and Metrics. Alexander Tolpin.