Doc.: IEEE 802.19-09/0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 1 Writing a Coexistence Assurance Document Notice: This document has.

Slides:



Advertisements
Similar presentations
Doc.: IEEE nan Submission September 2008 Phil BeecherSlide SG-NAN closing report for Waikoloa, HI, Sept 2008 Date: 11-sept-2008.
Advertisements

Sg-whitespace-09/0019r0 Submission January 2009 Steve Shellhammer, QualcommSlide 1 Impact of FCC R&O on IEEE 802 Date: Authors: Notice: This.
Doc.: /0008r0 SubmissionSlide 1 08/02/2014 Slide 1 IEEE White Space Radio P&P Discussion 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 /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 /xxxxr0 Submission July 2006 Tom Siep, Cambridge Silicon Radio PlcSlide 1 Discussion of Definitions in 0023r2 Notice: This document.
Doc.: IEEE /0008r2 Submission March 2006 Steve Shellhammer, QualcommSlide 1 EC Summary of PAR Development Notice: This document has been prepared.
Doc.: IEEE /0009r1 Submission March 2006 Steve Shellhammer, QualcommSlide 1 March 2006 Opening Report Notice: This document has been prepared.
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 /0023r0 Submission July 2005 Steve Shellhammer, Qualcomm Inc.Slide 1 Questions to the Contention-based Protocol (CBP) Study Group Notice:
Doc.: IEEE /0024r0 Submission May 2006 Steve Shellhammer, QualcommSlide 1 Discussion of Coexistence Scenarios Notice: This document has been prepared.
Doc.: IEEE /0094r0 Submission November 2009 Steve Shellhammer, QualcommSlide 1 Comments on PAR Notice: This document has been prepared.
Doc.: IEEE /0020r2 Submission July 2008 Steve Shellhammer, QualcommSlide 1 Wireless Coexistence TAG Overview Notice: This document has been prepared.
Doc.: IEEE /0022r0 Submission May 2006 Steve Shellhammer, QualcommSlide 1 May 2006 Opening Report Notice: This document has been prepared to assist.
[ Interim Meetings 2006] Date: Authors: July 2005
Wireless Coexistence TAG Overview
March 2013 Opening Report Date: Authors: March 2013
LB73 Noise and Location Categories
LB73 Noise and Location Categories
SG CUB Tentative Timeline
Waveform Generator Source Code
March 2014 Election Results
TV White Space Coexistence Plan
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
[ Policies and Procedure Summary]
San Francisco Liaison Report
November Opening Report
Motion to accept Draft p 2.0
November 2013 Opening Report
TGp Motions Date: Authors: November 2005 Month Year
March Opening Report Date: Authors: March 2010
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
Wireless Coexistence TAG Overview
November Opening Report
San Francisco Liaison Report
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
July 2014 Opening Report Date: Authors: July 2014
July 2012 Opening Report Date: Authors: July 2012
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
September Opening Report
November 2005 Liaison Report to P1900.2
LB73 Noise and Location Categories
March 2012 Opening Report Date: Authors: March 2012
Addressing White Spaces Across all of IEEE 802
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
TGr Proposed Draft Revision Notice
What is a CA document? Date: Authors: March 2005 March 2005
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
November 2012 Opening Report
September 2012 Opening Report
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
Motion to go to Letter Ballot
TGu-changes-from-d0-03-to-d0-04
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
July 2013 Opening Report Date: Authors: July 2013
TGp Motions Date: Authors: January 2006 Month Year
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 1 Writing a Coexistence Assurance Document 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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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 TAG 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 TAG. If you have questions, contact the IEEE Patent Committee Administrator at. Date: Authors:

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 2 Abstract A coexistence assurance (CA) document shows how well two wireless networks This presentation provides an overview of how to write a CA document

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 3 Steps in Writing a CA Document 1.Specify a set of coexistence scenarios 2.Specify a set of coexistence metrics 3.Compute the value of the coexistence metrics 4.Draft the CA document 5.Review of CA document by TAG (formal or informal)

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 4 Coexistence Scenarios A coexistence scenario specifies the following items –What networks are present –Physical geometry of devices –Type of network traffic on each network –Type of usage in each network (downloading data, voice or video traffic, etc.) –Description of physical scenario including whether it is indoor, outdoors, between walls, etc. –Any other specifications to describe the scenario

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 5 Coexistence Metrics A coexistence metric is something you measure to evaluate how well two (or more) networks coexist The specific coexistence metrics are typically a function of how the network is being used –Change in mean throughput when second network is present versus no other network being present –Change in latency –Packet error rate –Distance between network at which packet error rate reaches a specified threshold –Etc.

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 6 Coexistence Metrics Coexistence network are to be provided on both networks Let us say there are two networks –Network A –Network B Some metrics will measure the impact of Network A on Network B Others will measure the impact of Network B on Network A These metrics may be the same or may be different, most likely based on the use of each network

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 7 Computing Value of Coexistence Metrics There are multiple methods of computing the value of the coexistence metrics –Simulations –Analytical Models –Hybrid Simulation/Analysis Typically the coexistence metrics are plotted as a function of an independent parameter –Network separation –Network traffic loading –Etc.

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 8 Drafting a CA Document The WG (or TG) prepares a document including –Description of the scenarios –Description of the coexistence metrics –Description of simulation/analysis method –Simulation/Analysis results showing value of the coexistence metrics as a function of various independent parameters –Conclusions about the coexistence of the two networks –Possible recommendations about under what conditions the two networks coexist well and when the coexist poorly

doc.: IEEE /0001r0 Submission January 2009 Steve Shellhammer, QualcommSlide 9 Working with the TAG The WG is encouraged to work with the TAG Prior to WG Letter Ballot –Schedule joint meeting with TAG to discuss coexistence scenarios, metric, methods of calculations –Provide early versions of CA document to TAG for review During WG Letter Ballot –CA document is to be provide with draft to entire ballot pool and TAG –TAG will provide comments back to WG on CA document