1. Discussion Topics Date: 2011-03-17 Authors: March 2011 Month Year
doc.: IEEE yy/xxxxr0
March 2011
Discussion Topics
Date:
Authors:
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 < 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 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
Mika Kasslin, Nokia
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
March 2011
Introduction
This slide set is used in TG1 as a working document to facilitate discussions on selected key items and topics of a white space coexistence system
The slide set is updated based on the input from the task group members
Mika Kasslin, Nokia
John Doe, Some Company

3. Discussion topics for the TG1
Month Year
doc.: IEEE yy/xxxxr0
March 2011
Discussion topics for the TG1
Coexistence scenario
Spectrum etiquette, co-channel sharing
Scalability
Discovery
Firewall traversal
How to address the following issues in the specification?
Propagation (topography, obstacles, etc.)
Power disparity
Convergence, stability
What are parameters a coexistence system can configure?
Mika Kasslin, Nokia
John Doe, Some Company

4. Coexistence solutions
Month Year
doc.: IEEE yy/xxxxr0
March 2011
Coexistence solutions
First, select a non-overlapping TVBD operating channel to avoid co-channel interference or performance degradation.
”Seek and avoid” (AGREED THAT NEEDED)
If not possible, then we go to the next level down which is to try to put together similar systems: Homogeneous grouping.
”PHY/MAC aggregation” (AGREED THAT NEEDED)
If the homogeneous grouping is not possible, we fall back to the generalized coexistence problem.
As an example, TVBD operating channel splitting (time, frequency, code, space domain) (AGREED THAT NEEDED)
The assumption in all these is that a CM/CDIS has knowledge about TVBD capabilities
Mika Kasslin, Nokia
John Doe, Some Company

5. Coexistence scenario March 2011 Month Year doc.: IEEE 802.11-yy/xxxxr0
Mika Kasslin, Nokia
John Doe, Some Company

6. Scalability Coexistence system discovery Firewall traversal Trust
Month Year
doc.: IEEE yy/xxxxr0
March 2011
Scalability
Coexistence system discovery
Coexistence system availability. How a CE finds out a CM to connect?
How a CM finds a CDIS?
How a CDIS finds other CDISs?
Firewall traversal
How to provide communication links between entities behind firewalls?
Trust
How to build and maintain trust?
How to anonymyze sensitive information?
Mika Kasslin, Nokia
John Doe, Some Company

7. Propagation, Power disparity, Convergence, Stability
Month Year
doc.: IEEE yy/xxxxr0
March 2011
Propagation, Power disparity, Convergence, Stability
Propagation
What kind of propagation models should be used in the coexistence system as an example in neighbor discovery?
Free space propagation model is the extreme. As accurate and realistic models as possible should be used.
How to accomodate factors like building penetration loss and indoor/outdoor operating environment?
A related question is what infomration a CE needs to provide on the associated TVBD to the coexistence system for propagation model calculations.
Power disparity is to be taken into account in estimations and calculations
Convergence, stability
Mika Kasslin, Nokia
John Doe, Some Company

8. Month Year
doc.: IEEE yy/xxxxr0
March 2011
What are the parameters a coexistence system can configure (i.e. knobs to turn)?
Parameter
Notes
Carrier frequency
Bandwidth
Range of Tx power levels (TxP_Min, TxP_Max)
Synchronization
Mika Kasslin, Nokia
John Doe, Some Company

9. Month Year
doc.: IEEE yy/xxxxr0
March 2011
What are parameters a coexistence system can get from a CE about a TVBD (1/2)?
Parameter
Notes
Rx sensitivity
In dBm
Minimum SNR
TVBD location
FCC ID, Serial number (Regulatory ID)
Tx antenna HAAT, altitude, orientation, directivity
Rx antenna HAAT, factor, altitude, orientation, directivity
Geo-location database information: Available channels list, etc. and when the information was last updated
TVBD technology / standard
Mika Kasslin, Nokia
John Doe, Some Company

10. Month Year
doc.: IEEE yy/xxxxr0
March 2011
What are parameters a coexistence system can get from a CE about a TVBD (2/2)?
Parameter
Notes
TVBD capabilities
List of carrier frequency (with preference order)
List of bandwidths (with preference)
Synchronization
EIRP Tx power range (TxP_Min, TxP_Max)
Indoor/Outdoor/Device class
Intended range
Mode of operation
AP / BS/ client / CPE / etc.
Backup channel of system
Mika Kasslin, Nokia
John Doe, Some Company