Simplification of Enablement Procedure for TVWS band

Slides:



Advertisements
Similar presentations
tv Mi-Kyung Oh etc., ETRI Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TV White Space.
Advertisements

Doc.: IEEE /0544r0 May 2010 Padam Kafle, Nokia Submission Slide 1 Some Comments on White Space Map IE Authors: Date: May 14, 2010 NameCompanyAddressPhone .
Doc.: IEEE /0262r1 Submission March 2010 Ha-Nguyen Tran et al., NICTSlide 1 Requirements and Amendment Regarding TVWS Database Access Notice:
Doc.: IEEE /0175r2 Submission June 2011 Slide 1 FCC TVWS Terminology Date: Authors: Peter Ecclesine, Cisco.
Doc.: IEEE /1274r1 November 2011 Padam Kafle, Nokia Submission Neighboring Network Information Sharing through RLSS Authors: Date: Nov 7, 2011.
Doc.: IEEE /1393r1 Submission November 2011 Slide 1 OFCOM ECC TR 159 TVWS Terminology Date: Authors: Peter Ecclesine, Cisco.
Doc.: IEEE /0261r0 SubmissionSlide 1 Enabling Procedure of Communication in TVWS under FCC rules Notice: This document has been prepared to assist.
Submission November 2010 doc.: IEEE /1236r0 Enhancements to Enablement Procedure Slide 1 Santosh Abraham, Qualcomm Incorporated Date:
Doc.: IEEE /xxxxr0 July 2011 Padam Kafle, Nokia Submission Simplification of Enablement Procedure for TVWS Authors: Date: July 18, 2011 NameCompanyAddressPhone .
Submission doc.: IEEE af-11/1051r0 Dual band operation of TVBDs Date: July 20, 2011 Chen Sun, NICT Author(s): NameCompanyAddressPhone Chen SUNNICT+81.
Doc.: IEEE /0352r1 March 2011 Padam Kafle, Nokia Submission Simplification of Enablement Procedure for TVWS band Authors: Date: March 11, 2011.
Doc.: IEEE af Submission Distributed Measurement Report Period for Interference Detection in af MAC Mar Chang-Woo Pyo, NICTSlide.
Doc.: IEEE /0294r2 Submission March 2012 Jonathan Segev (Intel)Slide 1 Active Scanning Reply Window Date: Authors:
FILS Reduced Neighbor Report
Comparison Between and af
Requirements and Amendments Regarding TVWS Database Access
Operation With Small Batteries
Proposed SFD Text for ai Link Setup Procedure
Submission Title: Proposed Approach for MAC changes for TVWS
FCC TVWS Terminology Date: Authors: Month Year Month Year
White Space Map Notification
Proposal on system description, reference model and draft outline
FCC TVWS Terminology Date: Authors: Month Year Month Year
Channel list request/response for multiple geo-locations
Enabling signal and enablement
Multiple Locations Channel Availability Query
Multiple Locations Channel Availability Query
Multiple Locations Channel Availability Query
Multiple Frequency Channel Scanning
Low Rate Enabler Date: Authors: March 2011 Month Year
Multiple BSSID Set considerations
Interference Management for TVWS Networks
FILS Reduced Neighbor Report
FCC Regulations and Multi-band Operation
Secure Enablement and CVS without Persistent Association
Channel list request/response for multiple geo-locations
Enabling Procedure of Communication in TVWS under FCC rules
Low Rate Enabler Date: Authors: March 2011 Month Year
doc.: IEEE g-Trends-in-SUN-capacity
Channel list request/response for multiple geo-locations
Month Year doc.: IEEE yy/xxxxr0
Interference Management for TVWS Networks
TVWS WLAN Enablement- Review and Open Issues
Enabling signal and enablement
Low Rate Enabler Date: Authors: March 2011 Month Year
TVWS WLAN Enablement- Review and Open Issues
Identification Signal for Fixed devices
October 2010 On the new FCC second order memorandum opinion and order with regard to TVWS Date: Authors: Notice: This document has been prepared.
Fast Session Transfer Session Setup in TVWS
TVWS WLAN Enablement- Discussions and Open Issues
Examples of deployment scenarios
TVWS Enablement after New FCC Rules
Multiple Locations Channel Availability Query
11af architecture Date: Authors: May 2011 Month Year
Triggering the Broadcast Probe Response
Wireless Location Date: Authors: July 2007 Month Year
TVWS WLAN Enablement- Discussions and Open Issues
CR for CID 1115 Date: Authors: May 2019
Synchronization of Quiet Periods for Incumbent User Detection
Simplification of Enablement Procedure for TVWS band
Neighboring Network Information Sharing through RLSS
Scheduled Peer Power Save Mode for TDLS
Notification of available channel list in TVWS
Fast Session Transfer Session Setup in TVWS
Month Year doc.: IEEE yy/xxxxr0 May 2012
TVWS WLAN Enablement- Discussions and Open Issues
Month Year doc.: IEEE yy/xxxxr0
Format for Device Location Information in .11af
Enabling Procedure of Communication in TVWS under FCC rules
Date: Authors: February 2010 Month Year
Presentation transcript:

Simplification of Enablement Procedure for TVWS band Month Year doc.: IEEE 802.11-yy/xxxxr0 Simplification of Enablement Procedure for TVWS band Date: March 11, 2011 Authors: Name Company Address Phone email Padam Kafle Nokia 6021 Connection Drive, Irving, TX, 75039 +1 214 673 6232 Padam.kafle@nokia.com Mika Kasslin Itämerenkatu 11-13, 00180 Helsinki, Finland +358 50 4836294 Mika.kasslin@nokia.com Prabodh Varshney +1 469 9512745 Prabodh.varshney@nokia.com John Doe, Some Company

doc.: IEEE 802.15-<doc#> <month year> Summary There are many comments seeking clarification or changes on DSE enablement for TVWS band. This presentation try to cover the issues raised by the following CIDs on enablement in TVWS band: CIDs: 3, 136, 138, 162, 257, 321, 322, 326, 492, 502, 503, 505, 510, 511, 512, 513, 516, 519, 528, 529, 545, 553, 578, 579, 614, 804, 905, 982 Resolution: the resolution text to be provided in Doc: 11-11-0414r0. > Page 2

Contents Introduction Review of Enablement Procedure in 802.11af D1.0 Dependent STA, Enabling STA and Enabling Signal Enablement Procedure in TVWS band Network Architecture and Interfaces Backup slides Summary of FCC Rules Some Remarks on 802.11y Operation Miscellaneous Comments on Clause 10.12

doc.: IEEE 802.15-<doc#> <month year> Introduction The Dynamic Station Enablement (DSE) from 802.11y amendment has been adopted to 802.11af as a basis for controlling client stations However, there are many different requirements on network initiation and operation in TVWS band compared to licensed operation in 3650-3700 MHz band for which the existing DSE procedures were first introduced We believe, the task group should revisit the enablement requirements, along with reference architecture on entities, terms and definitions. It may be better to only keep the common DSE procedure details applicable for 3650 or TVWS band in clause 10.12, and detailed band specific text moved to Annexes. The enabling and dependent STAs behaviours in TVWS band should more closely resemble to FCC’s TVWS rules as a basis > Page 4

Review and discussion on enablement procedure doc.: IEEE 802.15-<doc#> <month year> Review and discussion on enablement procedure Current 802.11 baseline describes the Dynamic Station Enablement (DSE) by using enabling STA and dependent STA. Also registered STA and Fixed STA terms are related. In short: Enabling STAs are registered STAs allowed to enable other non-registered dependent STAs to operate but with hooks of DSE control procedures (DSE enablement/deenablement, enabling signal over the air) All Fixed STA and enabling STA are registered STA (broadcast their registered location information) Fixed STAs operate in standalone manner, they are not allowed to enable other dependent STAs Current clause 10.12 is very much tied with US 3650-3700 MHz operation. The TVWS operation with DSE looks far less from being complete Conflicts on STA types and behaviors Conflicts with regulatory requirements and DSE enablement rules > Page 5

Dependent STA, Enabling STA and Enabling Signal doc.: IEEE 802.15-<doc#> <month year> Dependent STA, Enabling STA and Enabling Signal Let’s review first the definitions and behaviors of dependent STA, enabling STA and Enabling signal. Dependent station (STA): A STA that is not registered and whose operational parameters are dictated by messages it receives from an enabling STA. Once enabled by the dynamic STA enablement (DSE) process, a dependent STA's continued operation becomes contingent upon being able to receive messages from its enabling STA over the air. In general, what does the word “dependent” means in .11af context? Is the dependency for initiating the first transmission in TVWS band ? Dependency related to enabling signal If so, Mode II or Fixed can also be a dependent STA (or dependent AP) until it receives its own channel list Or, is the dependency for operation of devices not capable of own geo-location ? Only Mode I devices are dependent to their master device Dependency to receive copy of available channels from master device Dependency to receive contact verification signal over the TVWS band (Note: .11y require same DSE procedures for dependent APs and dependent STAs) > Page 6

Dependent STA, Enabling STA and Enabling Signal .. doc.: IEEE 802.15-<doc#> <month year> Dependent STA, Enabling STA and Enabling Signal .. Enabling station (STA): A registered STA that has the authority to control when and how a dependent STA can operate. An enabling STA communicates an enabling signal to its dependents over the air. An enabling STA may choose for other dynamic STA enablement (DSE) messages to be exchanged over the air, over the distribution system (DS), or by mechanisms that rely on transport via higher layers. What is the key function of “enabling STA” in TVWS band ? In .11y, enabling STA had both functions: transmit enabling signal (with registered location) and also control with enablement/deenablement Enabling Signal: No definition as such in the baseline, except rules like “An enabling STA communicates an enabling signal to its dependents over the air” .11af has added an inband enabling signal for TVWS purpose. The “over the air” is limited to TVWS band > Page 7

Enabling Signal, CVS and FCC Rules doc.: IEEE 802.15-<doc#> <month year> Enabling Signal, CVS and FCC Rules What can be concluded about Enabling Signal (refer backup slide 18) ? Only a master device that has already obtained valid list of channels from database can start transmitting an enabling signal Devices not able to obtain channel list without using TVWS band must first hear enabling signal When Fixed or Mode II require to access Internet indirectly via another Fixed/Mode II TVBD Before a Mode I device can establish contact with Mode II/Fixed (to obtain channel list) Once a device receives valid channel list, there is no need to hear enabling signal What can be concluded about Contact Verification Signal (refer slide 19)? Mode II/Fixed device start CVS transmissions after it sends list of available channel to a Mode I The periodic reception requirement by Mode I devices is similar to enabling signal requirement in .11y DSE (at least once every 60 s) => Dependent STA state machine in 10.12.5 should be using “CVS” for TVWS operation > Page 8

Enablement Procedure in TVWS band doc.: IEEE 802.15-<doc#> <month year> Enablement Procedure in TVWS band What could be sufficient for enablement in TVWS band? Dependent STA/dependent AP must hear enabling signal if it requires to transmit in TVWS band before it can obtain a list of available channels i.e., enabling signal may not be needed if channel list can be acquired using some other band Dependent STA sends CAQ Request, The enabling STA/AP may perform authentication of the dependent STA (FCC ID verification result) The enabling STA/AP sends response to CAQ request with valid channel list During operation of dependent STA: Continue receiving CVS once at least every 60 s Dependent STA must perform channel and power changes as required by the master device. > Page 9

Enablement Procedure in TVWS band .. doc.: IEEE 802.15-<doc#> <month year> Enablement Procedure in TVWS band .. Apart from the above steps, do we additionally need DSE Enablement? Before Step 2 (DSE Enablement before obtaining channel list)? Can DSE Enablement be allowed in pre-associated state (as assumed for public action frame or GAS)? Benefit: “Enablement Identifier” for DSE, what else? Other Issues: The enablement rules for a dependent AP and dependent STA can be differentiated Dependent AP only need to hear “Enabling Signal” to use internet via another AP at the beginning, unless it becomes “Enabling AP” Different than .11y where an AP can hear a common tower (enabling STA) Dependent STAs need CVS dependency throughout > Page 10

Network Architectures and Interfaces doc.: IEEE 802.15-<doc#> <month year> Network Architectures and Interfaces Scenario 2: AP does not have direct connection to Internet, access is via another TVBD Scenario 1: AP has direct connection to Internet for DB access > Page 11

Network Architectures and Interfaces.. doc.: IEEE 802.15-<doc#> <month year> Network Architectures and Interfaces.. What about the above scenario ? > Page 12

doc.: IEEE 802.15-<doc#> <month year> Strawpolls: Do you agree on the simplification of enablement in TVWS band by using the 3 step procedure in slide 9 (without legacy .11y DSE)? Y: N: Do you agree to move the band specific details of DSE procedure (applicable for 3650 MHz and TVWS band) from clause 10.12 to Annexe E > Page 13

Backup Slides > doc.: IEEE 802.15-<doc#> <month year> Page 14

Summary of FCC Rules (for network initiation and operation) doc.: IEEE 802.15-<doc#> <month year> Summary of FCC Rules (for network initiation and operation) Fixed Device operation: Network Initiation: can initiate and operate network (can send enabling signal to other Fixed and PP TVBDs), but only after getting the channel list (for its own location) Geo-location capability: requires latitude, longitude coordinates (accuracy +/- 50 m) plus antenna height obtained by, Own geo-location capability Professional installation service Need to determine at the time of installation and first activation from power-off, then re-establish each time if its location has been changed Registration to FCC DB: Required to register: first time after installation, then each time if its location has been changed Detailed location and identifying information are required: Geo-location coordinates plus antenna height above ground level FCC ID, serial number by manufacturer, details of owner and responsible contact person > Page 15

Summary of FCC Rules .. Database access for channel query: doc.: IEEE 802.15-<doc#> <month year> Summary of FCC Rules .. Database access for channel query: Access by connecting to the internet: either directly or through another fixed TVBD that has a direct connection to the Internet Provides: location and identifying information Receives: available channel list, channel availability schedule info for next 48 hours, may receive separate available channel list for Mode I. At least once a day Other functions during operation: Must adjust the channel usage to comply with the channel availability schedule info obtained by the database for the 48 hour period since the time of last DB access Must transmit identification signal (device identity and geo-location) May accept contact initiation request from Mode I devices, and provide list of available channels (list valid for its own location or a separate list for Mode I obtained from DB) Requires to first provide FCC ID of Mode I device and receive successful verification back Must broadcast contact verification signal if it had provided a list of available channels for operation to a Mode I device must have the capability to display the lists of available channels and operating channels > Page 16

Summary of FCC Rules .. Personal/Portable Mode II Device: doc.: IEEE 802.15-<doc#> <month year> Summary of FCC Rules .. Personal/Portable Mode II Device: Network Initiation: can initiate and operate network (can send enabling signal to other Fixed and PP TVBDs), but only after getting the channel list (for its own location) Geo-location capability: requires latitude, longitude coordinates (accuracy +/- 50 m) by its own geo-location capability Need to determine its geographic position: each time after activation from power-off re-establish at least once every 60 s during operation (except while in sleep mode) Registration to FCC DB: not required Database access for channel query: Access by connecting to the internet: either directly or through another fixed or Mode II TVBD that has a direct connection to the Internet Provides: location (geographic latitude, longitude coordinates, accuracy +/- 50 m) and identifying information (FCC ID & Serial number by manufacturer) Receives: available channel list, may also receive channel availability schedule info for 48 hr May request and receive channel availability information for multiple locations > Page 17

Summary of FCC Rules .. Other functions during operation: > doc.: IEEE 802.15-<doc#> <month year> Summary of FCC Rules .. How often: At least once a day, each time after activation from power-off Once it moves by > 100 m distance since the location of last DB access, OR when moves outside from its currently valid channel availability zone for multiple locations Other functions during operation: Must adjust the channel usage to comply with the channel availability schedule information May accept contact initiation request from Mode I devices, and provide list of available channels Requires to first provide FCC ID of Mode I device and receive successful verification back from database Must broadcast contact verification signal if it had provided list of available channels for operation to a Mode I device Must signal Mode I devices to acquire new channel list if it looses power and obtains new channel list must have the capability to display the lists of available channels and operating channels > Page 18

Summary of FCC Rules .. Personal/Portable Mode I Device: doc.: IEEE 802.15-<doc#> <month year> Summary of FCC Rules .. Personal/Portable Mode I Device: Network Initiation: not allowed to initiate a network of other Fixed or PP TVBDs Geo-location capability: not required Registration to FCC DB: not required Database access for channel query: Not required, but must be in contact with a fixed/Mode II device to get available channel list Contact establishment with a Fixed or Mode II device for channel query: To initiate contact, it can transmit in an available channel used by Fixed or Mode II device, or on a channel indicated to be available for Mode I device on a signal seeking such contacts Provides: identifying information (FCC identifier) Receives: available channel list and info to decode the contact verification signal Contact verification process: Must re-check/re-establish contact with a Fixed or Mode II device if activated from power-off Must either receive and decode contact verification signal, at least once every 60 s (except while in sleep mode) originated from the same Fixed or Mode II device that had provided the current available channel list , OR contact a Mode II or fixed device to re-check/re-establish channel availability Must seize operation immediately if it can not perform the procedure above Other functions during operation: must have the capability to display the lists of available channels and operating channels > Page 19

doc.: IEEE 802.15-<doc#> <month year> Enabling Signal Rules Enabling signal/control signal/contact seeking signal look very similar In § 15.202 Certified operating frequency range. “ For the purposes of this section, a master device is defined as a device operating in a mode in which it has the capability to transmit without receiving an enabling signal. In this mode it is able to select a channel and initiate a network by sending enabling signals to other devices.” In § 15.703 (c) Fixed devices “ A fixed TVBD may select channels for operation itself from a list of available channels provided by a TV bands database, initiate and operate a network by sending enabling signals to one or more fixed TVBDs and/or personal/portable TVBDs.” In § 15.703 (g) Network initiation. “The process by which a fixed or Mode II TVBD sends control signals to one or more fixed TVBDs or personal/portable TVBDs and allows them to begin communications” In § 15.711 (b) (3) (iv), “To initiate contact with a fixed or Mode II device, a Mode I device may transmit on an available channel used by the fixed or Mode II TVBD or on a channel the fixed or Mode II TVBD indicates is available for use by a Mode I device on a signal seeking such contacts.” > Page 20

Contact Verification Signal Rules .. doc.: IEEE 802.15-<doc#> <month year> Contact Verification Signal Rules .. Contact Verification Signal: In § 15.703 (b) Contact verification signal: “An encoded signal broadcast by a fixed or Mode II device for reception by Mode I devices to which the fixed or Mode II device has provided a list of available channels for operation. Such signal is for the purpose of establishing that the Mode I device is still within the reception range of the fixed or Mode II device for purposes of validating the list of available channels used by the Mode I device and shall be encoded to ensure that the signal originates from the device that provided the list of available channels. A Mode I device may respond only to a contact verification signal from the fixed or Mode II device that provided the list of available channels on which it operates. A fixed or Mode II device shall provide the information needed by a Mode I device to decode the contact verification signal at the same time it provides the list of available channels.” § 15.711 (b) (3) (iv) Mode I Operation: “At least once every 60 seconds, except when in sleep mode, i.e., a mode in which the device is inactive but is not powered-down, a Mode I device must either receive a contact verification signal from the Mode II or fixed device that provided its current list of available channels or contact a Mode II or fixed device to re-verify/re-establish channel availability. A Mode I device must cease operation immediately if it does not receive a contact verification signal or is not able to re-establish a list of available channels through contact with a fixed or Mode II device on this schedule.” § 15.711 (f) (iii) Security: “Contact verification signals transmitted for Mode I devices are to be encoded with encryption to secure the identity of the transmitting device. Mode I devices using contact verification signals shall accept as valid for authorization only the signals of the device from which they obtained their list of available channels.” > Page 21

Some Remarks on 802.11y Operation doc.: IEEE 802.15-<doc#> <month year> Some Remarks on 802.11y Operation In 3650-3700 MHz band, the operation requires licensing: Licensing fee to each operator for nationwide permission to operate Additional fee for each high powered base station to be installed The enabling STA is a licensed base station that can transmit enabling signals to dependent STA or dependent AP over 3650 MHz or any other band The enablement requests and grants can also be exchanged through Internet or any other connectivity No concept of a dependent AP transmitting enabling signal (can not be relayed) Interference resolution is possible by means of unique identifiers assigned to each dependent STA and location of the enabling STA. Dependent STA only broadcast the location of the station that enabled it, plus the unique id they obtain from the enabling STA DSE service area boundary is controlled to the area where enabling signal can be received (initially, as well as, during operation) > Page 22

Some Remarks on 802.11y Operation doc.: IEEE 802.15-<doc#> <month year> Some Remarks on 802.11y Operation Dependent STA state machine from 802.11y > Page 23

Miscellaneous Comments on Clause 10.12 doc.: IEEE 802.15-<doc#> <month year> Miscellaneous Comments on Clause 10.12 Dependent station does not have to report the LCI of its enabling STA in TVWS band A dependent STA does not have to transmit “DSE Registered Location Announcement” frame to advertise the registered location of its enabling STA Enabling STA may not be “registered STA’ if they are personal/portable Mode II devices\ All dependent STA do not have to set: dot11LCIDSERequired and dot11LCIDSEImplemented, if they are not capable to determine their geo-location coordinates on their own. Based on current REVmb, when dot11LCIDSERequired is set, Beacon frames, probe response and association response frame contains DSERegisteredLocation element. However, this is not necessary for dependent STAs in TVWS band In TVWS band, only Fixed STA require to broadcast their ID and location information, not all registered STAs > Page 24