doc.: ieee 802.11-10/0262r1 submission march 2010 ha-nguyen tran et al., nictslide 1 requirements...
TRANSCRIPT
March 2010
Ha-Nguyen Tran et al., NICTSlide 1
doc.: IEEE 802.11-10/0262r1
Submission
Requirements and AmendmentRegarding TVWS Database Access
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.
Date: 2009-03-15Authors:
Name Company Address Phone emailHa Nguyen Tran NICT 3-4, Hikarino-oka, Yokosuka,
Kanagawa, Japan, 239-0847 [email protected]
Chen Sun NICT
Yohannes Alemseged NICT
Chin Sean Sum NICT
Zhou Lan NICT
Hiroshi Harada NICT
March 2010
Ha-Nguyen Tran et al., NICTSlide 2
doc.: IEEE 802.11-10/0262r1
Submission
Abstract
• This document introduces requirements about TVWS DB access
• The intent is for the discussion of possible amendment to support TVWS DB access
March 2010
Ha-Nguyen Tran et al., NICTSlide 3
doc.: IEEE 802.11-10/0262r1
Submission
Summary of FCC rulesregarding TVWS database access
• Fixed and Mode II TVBD must access the TVWS database, where TVWS DB is implemented in the Internet
• DB access frequency– Fixed TVBD: at least once a day– Mode II TVBD:
• Each time it is activated from a power-off condition• After location change during operation
• Information exchange– From TVBD to database
• FCC Identifier• Serial number assigned by the manufacturer• geo-location information (latitude and longitude, NAD83)
– From database to TVBD: available channels for secondary use
March 2010
Ha-Nguyen Tran et al., NICTSlide 4
doc.: IEEE 802.11-10/0262r1
Submission
Interference avoidance mechanism fora TVBD without direct Internet connection
• Section 15.711 Interference avoidance mechanisms– (f) If a fixed TVBD device does not have a direct connection to
the Internet and has not yet been initialized and registered with the TV bands database, consistent with Section 15.713, but can receive the transmissions of another fixed TVBD, the device needing initialization may transmit on either a channel that the other TVBD has transmitted on or on a channel which the other TVBD indicates is available for use to access the database to register its location and receive a list of channels that are available for it to use. Subsequently, the newly registered TVBD must only use the television channels that the database indicates are available for it to use. Such client fixed devices must re-contact their master device to review their list of available channels at least once every 60 seconds. A fixed device may not operate as a client to another fixed device.
March 2010
Ha-Nguyen Tran et al., NICTSlide 5
doc.: IEEE 802.11-10/0262r1
Submission
Discussion topics
• Does the current IEEE 802.11 (2007) and subsequent amendments specs provide means to1. Access the TVWS DB in the Internet?
2. Access the TVWS DB regularly according to FCC rules?
3. Obtain the device’s FCC ID, serial number, and its current geo-location information?
4. Send the above information to TVWS DB?
5. Obtain available channels information from TVWS DB?
• If NOT1. Shall 802.11af provide the means to support TVWS DB access?
March 2010
Ha-Nguyen Tran et al., NICTSlide 6
doc.: IEEE 802.11-10/0262r1
Submission
Requirement and Amendment (1)
• Requirement 1: Access the TVWS DB in the Internet– Means to obtain IP address(es) of the TVWS DB
– Security mechanisms, etc.
• Amendment:– Interface to obtain IP address
– Information element for IP address(es) of TVWS DB
March 2010
Ha-Nguyen Tran et al., NICTSlide 7
doc.: IEEE 802.11-10/0262r1
Submission
Requirement and Amendment (2)
• Requirement 2: Access the TVWS DB regularly according to FCC rules– A counter which supports the counting of 86400 sec (1 day)
– Procedures for TVWS DB access
• Amendment: add the following procedures
TVWS DBAccess
Counter < 86400
Counter +1
Fixed TVBD
TVWS DBAccess
OFF ONLocation change
CheckingPower
and Location
Yes
No Counter = 0
Yes
No
Mode II
March 2010
Ha-Nguyen Tran et al., NICTSlide 8
doc.: IEEE 802.11-10/0262r1
Submission
Requirement and Amendment (3)
• Requirement 3: Obtain device’s ID and geo-location– Interface to obtain FCC ID, serial number, geo-location from
TVWS device
• Geo-location information is available– In 802.11k
• Location request/report pairs are component of 802.11 architecture
– In 802.11u D8.0• AP STA: Generic Advertisement Services (GAS)
– A STA having dot11InterworkingServiceEnabled set to true, may retrieve an AP's Geospatial location using Native-GAS procedures.
– dot11APGeoLocation element of AP MIB
• Non-AP STA Location information– Non-AP location is approximated using AP’s location information
• Amendment– Interface to obtain FCC ID and serial No.
March 2010
Ha-Nguyen Tran et al., NICTSlide 9
doc.: IEEE 802.11-10/0262r1
Submission
Requirement and Amendment (4)
• Requirement 4: Send ID and geo-location to TVWS DB
• Amendment– Information elements for FCC ID, Serial number
March 2010
Ha-Nguyen Tran et al., NICTSlide 10
doc.: IEEE 802.11-10/0262r1
Submission
Requirement and Amendment (5)
• Requirement 5: Obtain list of available channels from TVWS DB
• Amendment– Information element for list of available channels
March 2010
Ha-Nguyen Tran et al., NICTSlide 11
doc.: IEEE 802.11-10/0262r1
Submission
Conclusions
• This document showed technical requirements to support TVWS DB access
• This document proposed the following amendment– interfaces to obtain FCC ID and serial number of TVBD, and IP
address of the TVWS DB
– modification of existing timer to accommodate long-time counting (e.g. 1 day)
– information elements for the following information
• FCC ID
• Serial number
• List of available channels