July 2010
doc.: IEEE 802.19-10/0096r1
Coexistence in the TV White Space
Date: 2010-07-12
Authors:
Name
Company
Steve Shellhammer Qualcomm
Address
Phone
5775 Morehouse Dr
San Diego, CA 92121
3-4 Hikarino-oka
Yokosuka
Itamerenkatu 11-13, 00180
Helsinki, Finland
(858) 658-1874 Shellhammer@ieee.org
610-878-5784
Tuncer Baykas
NICT
Mika Kasslin
Nokia
Alex Reznik
InterDigital
781 Third Ave.,
King of Prussia, PA 19406
Paivi Ruuska
Nokia
Itamerenkatu 11-13, 00180 Helsinki,
Finland
Chin-Sean Sum
NICT
Hyunduk Kang
ETRI
Hiroshi Harada
NICT
3-4 Hikarino-oka
Yokosuka
138 \Gajeong\dong
Yuseong\gu, Daejeon
3-4 Hikarino-oka
Yokosuka
Submission
Slide 1
E-mail
tbaykas@ieee.org
mika.kasslin@nokia.co
m
alex.reznik@interdigita
l.com
Paivi.ruuska@nokia.co
m
sum@nict.go.jp
henry@etri.re.kr
harada@nict.go.jp
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
Disclaimer
• “At lectures, symposia, seminars, or educational
courses, an individual presenting information on IEEE
standards shall make it clear that his or her views
should be considered the personal views of that
individual rather than the formal position, explanation,
or interpretation of the IEEE.”
• IEEE-SA Standards Board Operation Manual
(subclause 5.9.3)
Submission
Slide 2
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
Tutorial Outline
• Introduction
– Brief overview of FCC rules
– Standards activities in TVWS
• Need for Coexistence
– The Coexistence Problem
– TVWS Use Cases
• IEEE 802.19.1 Project
– Project Title, Scope and Purpose
– Project Timeline
– System Design Document
• Possible Coexistence Solutions
– Leverage incumbent protection mechanisms for TVWS
coexistence
– Modify network/device parameters to improve coexistence
Submission
Slide 3
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
FCC Rules on TVWS
• In November 2008 the FCC issued a Report and Order (R&O) on
unlicensed wireless use of unused TV channels, called TV white
space (TVWS)
– A number of petitions for reconsiderations were filed and the FCC still needs to
respond to the petitions. Current forecasts are for the FCC to respond by the end
this year.
• In any given location in the US there are a number of TV channels
unused by the broadcast industry. The number varies
significantly from location to location
• Each channel is 6 MHz wide
• Channels are in the VHF and UHF frequency bands
– Details in a subsequent slide
• FCC defines two classes of TVWS devices
– Fixed
– Portable
Submission
Slide 4
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
FCC Rules on TVWS
TV Channel
Frequency Band
Frequency (MHz)
Allowed Devices
2
VHF
54 – 60
Fixed
5–6
VHF
76 – 88
Fixed
7 – 13
VHF
174 – 216
Fixed
14 – 20
UHF
470 – 512
Fixed
21 – 35
UHF
512 – 602
Fixed & Portable
36
UHF
602 – 608
Portable
38
UHF
614 – 620
Portable
39 – 51
UHF
620 – 698
Fixed & Portable
Permissible TV Channels
Submission
Slide 5
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
FCC Rules on TVWS
• Fixed devices use outdoor antenna
• Between 10 and 30 meters above ground
• Permitted TX Power
• Fixed – 30 dBm with up to 6 dBi antenna gain
• Portable – 20 dBm with no antenna gain
• Adjacent TV Channels
• Fixed – Not permitted
• Portable – Reduce power to 16 dBm
• Strict Out-of-band Emissions
• Classes of Portable Devices
• Mode I – Client
• Mode II – Access Point
Submission
Slide 6
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
FCC Rules on TVWS
• Geo-location & Database access
• Must be supported in both Fixed and Portable Mode II devices
• Accuracy of 50 meters
• FCC will certify the official databases
• Spectrum Sensing
•
•
•
•
ATSC and NTSC TV signals
Wireless microphones
Sensing down to -114 dBm (approx -15 dB SNR)
Will consider “sensing-only” devices but with much more stringent
testing required
Submission
Slide 7
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
Non-US TVWS Rules
• Other regulatory regions are also preparing TVWS rules
• Some of the regulatory regions working on TVWS rules include
–
–
–
–
–
Canada
United Kingdom
Singapore
Nederland Antilles
Finland
• The rules in these regions are likely to have some similarities with
the US rules but will likely not be exactly the same
• In other parts of the world the TV channel bandwidths are 6, 7
and 8 MHz. So TVWS support for these different bandwidth is
expected
Submission
Slide 8
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
TVWS Related Standard Projects
Standard/Project
Summary
Status
IEEE 802.11af
WLAN in TVWS
Task Group working on draft
IEEE 802.19.1
Coexistence in TVWS
Open Call for Proposals
IEEE 802.22
WRAN in TVWS
WG Letter Ballot
IEEE 802.22.1
Beacon for Protection of Wireless
Microphones
Sponsor Ballot
IEEE 802.22.2
WRAN Installation & Deployment
Developing Draft
ECMA 392
MAC/PHY in TVWS
Standard December 2009
IEEE 1900.4a
Mobile wireless access in TVWS.
Above MAC/PHY
Close to WG Letter Ballot
IEEE 1900.6
Logical Interface between
spectrum sensors
In Sponsor Ballot
ETSI RRS
Reconfigurable Radio Systems
Four active WGs
ITU-R WP1B
Preparing for WRC 2012
Developing definitions of CR & SDR
Submission
Slide 9
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
TVWS Related Standard Projects
Standard/Project
Summary
Status
ECC PT SE43
European regulators group looking
at Spectrum Engineering issues
associated with cognitive use in
the TVWS.
Looking to complete draft report
for public enquiry in September
2010.
ECC RA WSCG
European regulators group looking
at Regulatory and Enforcement
issues associated with cognitive
use in the TVWS.
Just started working by
correspondence. Looking to
complete a draft report for public
consultation by Jan 2011.
ECC FM CRCG
European regulators group looking
at Frequency Management issues
associated with general cognitive
radio use.
Just started working by
correspondence.
EU RSPG CR group
European Union regulators group
looking at forming an opinion on
the future of CR radio use in the
EU.
Working on high level look at the
issues around encouraging and
enabling Cognitive radio use in
the EU. Plan to complete opinion
by November 2010
Submission
Slide 10
Steve Shellhammer, Qualcomm
July 2010
doc.: IEEE 802.19-10/0096r1
Coexistence in TVWS: What is it?
• TVWS presents a complex regulatory environment
– Licensed devices: allowed to use the spectrum whenever,
following appropriate rules
– Unlicensed devices: permitted to use the spectrum when it is not
occupied by licensed devices
• Licensed and unlicensed devices do not coexist
– Licensed devices make no special allowances for unlicensed
devices
– Unlicensed device must “protect” licensed operation by regulation
• Protection of licensed devices is a medium access
problem
– Thou shall not access access spectrum when these guys are around
Submission
Slide 11
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Coexistence in TVWS: So what is it then?
•
Coexistence happens between peers
– In TVWS, these are unlicensed devices and networks
– Not mandated by regulations
– Impetus must come from mutual benefit consideration: higher spectrum efficiency
for all involved
•
Why do they need to coexist
– Once available channels are known, the various networks and users need to decide
– who goes where
– This cannot be static – channel availability will change
•
Who specifies how this can be done
– Some (not all) standards specify how different networks using same technology
coexist
• 802.11, 802.15 do this
• Do they do it well??
– Some standards don’t even do that
• cellular standards do not specify how different operators use the same spectrum
– No MAC/PHY standard specifies how other MAC/PHY standards should behave
• Nor should one MAC/PHY do it – it would rule over all the others
• This void is filled by standards such as 802.19.1 in TVWS
Submission
Slide 12
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
The Coexistence Problem: #1
“… you know you could help me
out here. If you are on WiFi, if
you could just get off…”
“… we figured out why my demo
crashed. Because there are 570
WiFi base stations operating in
this room…”
Steve Jobs
see e.g.
http://www.youtube.com/watch?v
=yoqh27E6OuU
• So many talkers …
• … and no common language to discuss sharing
Submission
Slide 13
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
The Coexistence Problem: #2
• So little spectrum …
802.11
• So many ways to use it …
Bluetooth
Bluetooth
•
802.22
How we addressed in ISM bands
– “Smart hopping” by Bluetooth
–
•
More robust (lower) bit rate by WiFi
“Autonomous” approaches may not
work in TVWS
–
–
Submission
Much larger dynamic range in power
(4W / 100 mW / 50mW / 40mW)
Potentially incompatible medium
access techniques
Slide 14
802.11
802.11
802.11
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
The Coexistence Problem :#3
Source: Mishra and Sahai, IEEE Comm. Letters, 2009
• Few people – many channels …
Source: Gerami, Mandayam, Greenstein.
Report by Winlab, Rutgers U., 2010
• Many people – few channel …
Submission
Slide 15
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Operation in TV Bands:
Why Deal With the Headache?
•
TV Band Spectrum presents unique opportunities and possibilities
•
Potentially a lot of spectrum
– But availability not guaranteed
•
Excellent propagation characteristics
– Cover large distances
– Penetrate walls, obstacles
•
So what could this be used for
– Find additional bandwidth for data networks (in those areas where TV channels are
many)
– Offload to free up valuable (licensed) spectrum
– Quick and cheap network deployment: cover a large area with few access points
and little planning
– Cheap spectrum for applications requiring only intermittent communication
Submission
Slide 16
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 1:
Rural/Suburban Home/Small Office
Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010
Submission
Slide 17
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 1:
Rural/Suburban Home/Small Office
• Potential Uses
–
–
–
–
Device-to-Device (Machine-to-Machine)
WLAN Access
Backhaul
Cellular offload
• Characteristics
– Single operator controls much of the network and controls the space
– Limited interference from like networks
– Requires high data rates/no critical usage applications
• Is this a good fit for white spaces
– Yes, if the channels are available
– Yes, if the operator (home owner) can automate the channel selection
and coexistence of the various technologies he owns
Submission
Slide 18
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 2: Apartment
•
Similar usage to the home use case,
but very different environment
•
Multiple operators
–
–
–
WLAN AP
Cellular
Femtotell
•
Little spatial separation between the
operators
–
WLAN
HotSpot
–
Celullar
Fixed WWAN
•
Submission
Slide 19
Lots of networks crammed into a small
spaces
Opens the possibility of the iPhone4 demo
problem
Is this a good fit for white spaces
–
Source: Paine et. al., IEEE doc. 802.19-09/26r4,
Whitespace Coexistence Use Cases, 07/2009
Each resident operates own network
No incentive to cooperate/coordinate
WWAN network may be overlayed into
this space
Maybe – but the inter-network
coexistence problem will definitely need
to be solved.
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 3: Utility Grid
Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010
Submission
Slide 20
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 3: Utility Grid
• Potential uses
– Collection of metered data
– Reporting of aggregated data over the backhaul
– SCADA support
• Characteristics
– Relative low-rate, can deal with intermittent outages
– Single network operator, but spanning a large distance
– High likelihood of interference with different network – this interference
varies in nature and spectral location throughout the network
• Is this a good fit for white spaces?
–
–
–
–
Submission
Absolutely
Covers large areas
Meters may need to penetrate obstacles
Requires only intermittent connectivity
Slide 21
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 4: Public Safety
Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010
Submission
Slide 22
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
Example Use Case 4: Public Safety
• Potential Usage
–
–
–
–
Rapid deployment of emergency personnel networks
Inter-personnel communication
Network backhaul
Communication to the main office
• Characteristics
– High-rate data rate services
– Multi-media and conversational services
– Creating an “instant network” where there was none
• Is this a good match for white spaces
–
–
–
–
Submission
Yes, IF spectrum can be found, need to have backup plans.
Yes: need to create a network with few APs and no ability to plan
Yes: need penetration through obstacles
Yes: need the reach the main office
Slide 23
Alex Reznik
(InterDigital)
July 2010
doc.: IEEE 802.19-10/0096r1
802.19.1 PAR
•
Title: IEEE 802 … Part 19: TV White Space Coexistence Methods
•
Scope: The standard specifies radio technology independent methods for coexistence
among dissimilar or independently operated TV Band Device (TVBD) networks and
dissimilar TV Band Devices.
•
Purpose: The purpose of the standard is to enable the family of IEEE 802 Wireless
Standards to most effectively use TV White Space by providing standard coexistence
methods among dissimilar or independently operated TVBD networks and dissimilar
TVBDs. This standard addresses coexistence for IEEE 802 networks and devices and
will also be useful for non IEEE 802 networks and TVBDs.
•
•
Study Group was established in March 2009.
The PAR was approved by Nescom in December 2009 and task group has been
established.
Submission
Slide 24
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
802.19 TG1 Timeline
Task Group Formed
SDD completed
Order of Clauses determined
Call for Proposals issued
Contribution presentations with straw polls
Proposal presentations
2010
2011
2012
1 3 5 7 9 11 1 3 5 7 9 11 1 3 5 7 9 11
x
x
x
x
x x x x
x x
x
Round of votes on proposals in clause order
Create candidate draft document
Comment ballot on the candidate draft
x
x x
x
x
Comment resolutions on the candidate draft
Adoption of draft normative text (Draft 1.0)
•Contribution
A submission on an issue relevant to the task group that may be in Powerpoint format. Contributions are
expected to be submitted on issues that contributors are planning to submit as proposals later on in the draft
development process.
•Proposal
A submission that provides a solution proposal to a clause as defined in the System Design Document. The
proposal shall include a document in Microsoft Word format that contains draft normative text proposal for a
clause.
September 2010: System description
September 2010: The 802.19.1 reference model
September 2010-November 2010: Procedures and protocols
September 2010-November 2010: Coexistence mechanisms and algorithms
Submission
Slide 25
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
System Design Document
802.19.1 created system design document to assist standardization process.
It provides,
System Requirements (What is expected from 802.19.1 system?)
802.19.1 System Architecture (How 802.19.1 will provide coexistence?)
SDD does not put any limitation on future contributions and proposals.
http://ieee802.org/19/pub/TG1.html
Submission
26
Tuncer Baykas,
NICT
802.19.1 Architecture Logical
Entities
doc.: IEEE 802.19-10/0096r1
July 2010
What is expected from 802.19.1 system?
Requirement 1 (Discovery)
802.19.1 system shall enable discovery for 802.19.1
compliant TVBD networks and devices.
Requirement 2 (Communication)
802.19.1 system shall be able to obtain and update
information required for TVWS coexistence.
802.19.1 System
Discovery
R2
TVWS DB
R2
R1
R3 TVWS DB
R4
Algorithm
Requirement 3 (Communication)
802.19.1 system shall have means to exchange
obtained information.
TVBD
network
or
device
Communication
R5
R6
R7
General
R8
R9
Requirement 4 (Communication)
802.19.1 system shall be able to provide reconfiguration requests and/or commands as well as corresponding
control information to 802.19.1 compliant TVBD networks and devices to implement TVWS coexistence
decisions.
Submission
27
Tuncer Baykas,
NICT
802.19.1 Architecture Logical
Entities
doc.: IEEE 802.19-10/0096r1
July 2010
What is expected from 802.19.1 system?
Requirement 5 (Algorithm)
802.19.1 system shall analyze obtained information.
802.19.1 System
Discovery
Requirement 6 (Algorithm)
802.19.1 system shall be capable of making TVWS
coexistence decisions.
Requirement 7 (Algorithm)
802.19.1 system shall support different topologies of
decision making for TVWS coexistence (e.g.
centralized, distributed and autonomous).
R2
TVWS DB
R2
R1
TVBD
network
or
device
Communication
R3 TVWS DB
R4
Algorithm
R5
R6
R7
General
R8
R9
Requirement 8 (General)
802.19.1 system shall support appropriate security mechanisms. This shall include user/device authentication,
integrity and confidentiality of open exchanges, and data privacy and policy correctness attestation and
enforcement.
Requirement 9 (General)
802.19.1 system shall utilize a set of mechanisms to achieve coexistence of TVBD networks and devices.
Submission
28
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
802.19.1 Architecture
Submission
29
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
Entities communicating with the 802.19.1 system
TV Band Device or TV
Band Device Network
TVWS Database
Unlicensed operation in the broadcast
television spectrum at locations where
that spectrum is not being used by
licensed services.
Provides list of channels occupied
by primary users.
Submission
30
Operator Management
Entity
Provides operator provided
information such as policies/
limitations.
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
Entities belonging to 802.19.1 System
Coexistence Manager
Coexistence decision making
This includes generating and providing
corresponding coexistence
requests/commands and control
information to Coexistence Enabler(s)
Discovery of and communication
with other Coexistence Managers
Assist network operators in
management related to TVWS
coexistence
Submission
Coexistence Enabler
Coexistence Discovery
and Information Server
Communication between
Coexistence Manager and
TVBD network or device
Providing coexistence related
information to Coexistence
Managers
Obtaining information, required
for coexistence, from TVBD
network or device
Supporting discovery of Coexistence
Managers and opening interfaces
between Coexistence Managers
Translating reconfiguration
requests/commands and control
information received from the
Coexistence Manager into TVBDspecific reconfiguration requests/
commands
Collecting, aggregating information
related to TVWS coexistence.
31
Coexistence Discovery and
Information Server may connect to
TVWS database to obtain primary
users information.
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
Deployment of Entities
Coexistence Enabler (CE)
CEs can be deployed inside TV Band Devices or Network.
Coexistence Manager (CM)
CMs can be deployed inside the TV Band Device or Network. Also CMs can be deployed
outside TV Band Networks.
Coexistence Discovery and Information Server (CDIS)
CDISs can be deployed outside TV Band Networks.
Submission
32
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
Possible Approach
• TVBD networks and
devices have mechanisms
that are designed for e.g.
interference management
purposes
• CM and CE can and
should use those
mechanisms for
coexistence purposes
– 802.19.1 builds upon existing
mechanisms in the radio
systems and has control
functions for that purpose
Submission
Slide 33
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Possible Control Parameters
• Possible reconfiguration parameters in the TVBD
networks
–
–
–
–
–
–
Operating channel
Maximum transmit power
Modulation and coding rate
Bandwidth
OFDMA uplink client sub-band
Transmit scheduling
• CSMA parameters
• Transmit duty cycle limit
– Antenna configurations
Submission
Slide 34
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Possible Control Functions
• CM’s tool box in coexistence management comprises of
tools in three main domains that form the main control
functions
– Time domain control
• Recommendations, commands related to e.g. Transmit scheduling,
Transmit duty cycle limit, Modulation and coding rate
– Frequency domain control
• Recommendations, commands related to e.g. Operating channel,
Bandwidth, OFDMA uplink client sub-band
– Spatial control
• Recommendations, commands related to e.g. Antenna configuration,
Maximum transmit power
• The 802.19.1 system uses those tools to configure TVBD
operations
Submission
Slide 35
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Possible Decision Making Topologies
• Not sure whether we can rely on one decision making
model that can be applied in all the situations and
deployments
• We need to be prepared to provide means for all three
topologies
– Centralized
• One CM serves all the neighboring networks and provides coexistence
services for them
– Distributed
• Neighboring networks are served by different CMs
– Autonomous
• Information related to coexistence management is exchanged but
that’s all
Submission
Slide 36
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Possible Decision Making Topologies
(cont.)
• All the topologies have common solution elements
– Information exchange between entities is needed
– We need to provide security and trust
• The few main differences are
– Is there information exchange between CMs?
• In centralized case the CMs have less need if any to exchange information
while in the other two cases it is essential for the CMs to exchange information
about environment, resource usage, etc.
– What is the role of CM?
• Centralized and Distributed
– CMs are true coexistence managers that run coexistence control functions
– In a distributed case the CM may have power over a CM of a neighboring network
• Distributed vs. Autonomous
– In autonomous case the CM may be only facilitating communication between CEs
Submission
Slide 37
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Guiding Questions for the System
Development
• CE as defined in the SDD
– Request and obtain information, required for coexistence, from
TVBD network or device
• What information we need from TVBD networks and
devices?
• How do we get the information?
– Translate reconfiguration requests/commands and control
information received from the CM into TVBD-specific
reconfiguration requests/commands and send them to the TVBD
network or device
• What are the possible coexistence mechanisms?
• How they are used in various TVBD networks?
• How do we interface to various TVBD networks?
Submission
Slide 38
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Guiding Questions for the System
Development (cont.)
• CM as defined in the SDD
– Coexistence decision making
• What are the control functions?
• What’s needed to support different decision making
topologies?
– Support exchange of information required for coexistence among
CMs
• How to exchange coexistence information between decision
making entities?
Submission
Slide 39
Mika Kasslin,
Nokia
July 2010
doc.: IEEE 802.19-10/0096r1
Workshop Coexistence for TVWS
•
•
•
•
•
•
•
Free Workshop on Friday 1:00PM to 6:00PM
Open to all
Industry centric participants
Outside 802 speakers and panelists
4 presentations and 3 Panels
Open periods for discussion and Q&A
Agenda available at:
http://ieee802.org/19/pub/workshop.html
Submission
Slide 40
Tuncer Baykas,
NICT
July 2010
doc.: IEEE 802.19-10/0096r1
802.19 TG1 Timeline
Task Group Formed
SDD completed
Order of Clauses determined
Call for Proposals issued
Contribution presentations with straw polls
Proposal presentations
2010
2011
2012
1 3 5 7 9 11 1 3 5 7 9 11 1 3 5 7 9 11
x
x
x
x
x x x x
x x
x
Round of votes on proposals in clause order
Create candidate draft document
Comment ballot on the candidate draft
Comment resolutions on the candidate draft
Adoption of draft normative text (Draft 1.0)
x
x x
x
x
Deadline for proposal intentions is 29th of August 2010 for September proposals.
For details please check:
Call for Proposals 802.19-10/0057r2
Submission
Slide 41
Tuncer Baykas,
NICT