TGT Definitions Ad Hoc Report

Slides:



Advertisements
Similar presentations
Coexistence Motions for LB84 Comment Resolution
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE WG Status Report – July 2005
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
TGu Closing Report Date: Authors: May 2006 May 2006
JTC1 Ad Hoc Closing Report
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
Doc.: IEEE /1006r0 July 2006 July 2006 Supporting information for eliminating Section 5.7 "OTA Shielded Enclosure Environment" Date:
November Opening Report
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGu Timeline Date: Authors: January 2005 January 2005
TGv Redline D0.06 Insert and Deletion
ADS Study Group Mid-week Report
TGu Closing Report Date: Authors: March 2006 March 2006
Joint Wireless Groups Architecture AdHoc
Selection Procedure Recommendation
TGu-changes-from-d0-01-to-d0-02
Joint Wireless Groups Architecture AdHoc
LB73 Noise and Location Categories
PHY Ad Hoc September Opening Report
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
Attendance for July 2006 Date: Authors: July 2006
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
May 2005 CAPWAP AHC Closing Report
Traceable OTA Performance Testing Presentation
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
TGT Conductive Test Environment
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
TGT Conductive Test Environment
WNG SC Closing Report Date: Authors: November 2005
TGu Timeline Date: Authors: May 2005 May 2005
TGu Timeline Date: Authors: July 2005 July 2005
IEEE White Space Radio First Call for Contributions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
Selection Procedure Recommendation
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

TGT Definitions Ad Hoc Report Doc.: IEEE 802.11-05/0232r00 March 2005 March 2005 TGT Definitions Ad Hoc Report Date: 2005-3-15 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuart.kerry@philips.com> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Dr. Michael D. Foegelle, ETS-Lindgren Dr. Michael D. Foegelle, ETS-Lindgren

Doc.: IEEE 802.11-05/0232r00 March 2005 March 2005 Abstract At the Monterey meeting, and Ad Hoc group was formed to review definitions presented in 11-05/0003r1 and 11-05/0004r1 and work towards a common set of definitions that would be formatted suitable for direct inclusion into the Recommended Practice and would facilitate a common language to be used in submissions for continued work in TGT. The Ad Hoc had several phone conferences and e-mail updates throughout the period since Monterey, and the results to date are presented here. The overall task remains incomplete. Dr. Michael D. Foegelle, ETS-Lindgren Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment Since concepts of environment (real-world measurements, controlled laboratory environment, etc.) were of primary concern, we began by attempting to define a common set of terms starting from a root definition. The dictionary definition for Environment (from dictionary.com) is given as: Environment: The circumstances or conditions that surround one; surroundings. Dr. Michael D. Foegelle, ETS-Lindgren

Environment From this, we defined a Test Environment as: March 2005 Environment From this, we defined a Test Environment as: Test Environment refers to the set of external physical circumstances and conditions surrounding or influencing the wireless performance of the 802.11 device or system under test.  Building on that, a Controlled Test Environment is: Controlled Test Environment any test environment where the circumstances and conditions surrounding or influencing the DUT/SUT is controlled to provide a known level of uncertainty. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment The definition of a Conducted Test Environment led to considerable discussion over several teleconferences. Several versions of the definition are given below. Conducted Test Environment refers to a controlled test environment where RF test signals are directly injected into and received from the radio of the device under test using a cable. This implies that all external signals reaching the DUT at a level sufficient to affect the test result propagate through the cable. Before that, the last sentence was: This implies that no un-desired external signals that would interfere with the measurement to be performed are allowed to reach the DUT by any mode of propagation, radiated or conducted. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment One source of confusion was in the assumption that simply, “conducted” = “cabled”. This is not the case, since, while a conducted test uses a cable to introduce or measure signals, a “cabled” test does not necessarily imply the same requirement that is understood in the industry for a conducted test, which is that those signals being introduced or measured occur only in a conducted manner. Since we’re defining conducted as a controlled environment, it necessitates that a method be made to control signals. This led to the development of a set of signal definitions to work back into the environment definitions. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Signals We started by defining several types of intentional signals as different RF Test Signals RF Test Signals:  All signals introduced to the DUT/SUT  for the purpose of testing its performance under a given set of conditions. Communication Test Signals:  RF Test signals to or from the DUT/SUT conforming to the 802.11 PHY specification under test in the intended communication band and carrying the communication payload. This could be shortened to: Communication Test Signals: RF Test signals carrying the communication payload to or from the DUT/SUT. Dr. Michael D. Foegelle, ETS-Lindgren

Signals RF Test Signals (continued) March 2005 Signals RF Test Signals (continued) Interference Test Signals:  RF Test signals introduced or present at the DUT/SUT producing known levels and types of interference with the communication test signal. Other signals that are important: Unintentional Internal Signals:  Platform noise or other similar signals that are internal to the DUT/SUT rather than externally applied as part of the test. Extraneous  Signals:  Any signal external to the test set-up. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment Returning to the definition of a Conducted Test Environment, it could then be modified as. Conducted Test Environment refers to a controlled test environment where RF test signals are directly injected into and received from the radio of each DUT using a cable. This implies that any extraneous signals reaching the DUT/SUT are at a level such that they do not affect the test result. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment Another test environment that was in the process of being defined: Over-The-Air (OTA) Test Environment refers to a test environment where RF test signals propagate to and from the antenna of the device under test.  - or - Over-The-Air (OTA) Test Environment refers to a test environment where RF test signals propagate to and from the radio of the device under test through an antenna. Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Environment Other test environments that were in the process of being defined or clarified include: Shielded Enclosure refers to a shielded box, screen room, or chamber used to RF isolate a test environment from the outside world.  Screen Room Shielded Room Anechoic Chamber (Fully Absorber Lined Room, Fully Anechoic Chamber, Microwave Chamber) Semi-Anechoic Chamber (Partially Absorber Lined Room, EMC Chamber) Dr. Michael D. Foegelle, ETS-Lindgren

March 2005 Conclusion The ad hoc group made some progress towards making a uniform basis for several definitions with a general consensus. Process has not been completed. 802.11-05/0206r0 contains portions of these definitions, but doesn’t necessarily represent the final consensus of the ad hoc as a whole. Depending on how review of the above document proceeds, the ad hoc can continue to review the definitions contained to make them self consistent and reach an overall consensus. Dr. Michael D. Foegelle, ETS-Lindgren