Multiple Locations Channel Availability Query

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0262r1 Submission March 2010 Ha-Nguyen Tran et al., NICTSlide 1 Requirements and Amendment Regarding TVWS Database Access Notice:
Advertisements

Doc.: IEEE /0256r0 Submission March 2010 Zhou Lan NICTSlide 1 Proposal of Synchronized Quiet Period for Incumbent User Detection Date: 2010-March.
Doc.: IEEE /0175r2 Submission June 2011 Slide 1 FCC 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 November 2010 doc.: IEEE /1237r0 Over the Air Database Access for Mode 2 Capable Devices Slide 1 Santosh Abraham, Qualcomm Incorporated.
Date: Authors: February 2010 Month Year
Requirements and Amendments Regarding TVWS Database Access
ANQP-SD Response When Service Mismatches
FCC TVWS Terminology Date: Authors: Month Year Month Year
White Space Map Notification
September 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: PIB Coordination in g Date Submitted:
<January 2002> doc.: IEEE <02/139r0> July, 2008
FCC TVWS Terminology Date: Authors: Month Year Month Year
IEEE Liaison Report to IEEE
Channel list request/response for multiple geo-locations
Enabling signal and enablement
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested changes for channel scan and scan related.
Multiple Locations Channel Availability Query
P System Architecture Date: Authors: March 2010
Multiple Locations Channel Availability Query
Submission Title: [Comment Resolutions for #309, #310, and #314]
March 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comment Resolution Suggestions Date Submitted:
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
Coexistence Transport SAP Description
Secure Enablement and CVS without Persistent Association
Channel list request/response for multiple geo-locations
CID#102 - Channel Allocation
FCC rules and design Date: Authors: October 2010
Submission Title: [Comment Resolutions for #309, #310, and #314]
Enabling Procedure of Communication in TVWS under FCC rules
CID#102 - Channel Allocation for P2P
P System Architecture Date: Authors: March 2010
doc.: IEEE g-Trends-in-SUN-capacity
Channel list request/response for multiple geo-locations
<month year> <doc.: IEEE doc> Julyl 2015
Radio Resource Measurement for TVWS application under FCC rules
Enabling signal and enablement
Coexistence Media Service Access Point (COEX_MEDIA_SAP)
Submission Title: Rogue Resolutions from kivinen
Channel Allocation March 2008 Authors: Date: Month Year
doc.: IEEE /XXXr0 Sep 19, 2007 July 2010
March 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comment Resolution Suggestions Date Submitted:
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.
Simplification of Enablement Procedure for TVWS band
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
<month year> <doc.: IEEE doc> Julyl 2015
Data types definition directions
TVWS Enablement after New FCC Rules
Multiple Locations Channel Availability Query
11af architecture Date: Authors: May 2011 Month Year
doc.: IEEE <doc#1>
CR for CID 1115 Date: Authors: May 2019
Block Addressed WUR Frame
Synchronization of Quiet Periods for Incumbent User Detection
Neighboring Network Information Sharing through RLSS
Notification of available channel list in TVWS
P System Architecture Date: Authors: March 2010
Timing Measurement Date: Authors: Jan 2010 November 2007
Submission Title: Rogue Resolutions from kivinen
P System Architecture Date: Authors: March 2010
AP Connection Period in TDLS
Representation of Transmitter Characteristics
doc.: IEEE /XXXr0 Sep 19, 2007 July 2010
Timing Measurement Date: Authors: Jan 2010 November 2007
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Discussion and Conclusion of Conference Call on February19]
Enabling Procedure of Communication in TVWS under FCC rules
Date: Authors: February 2010 Month Year
Presentation transcript:

Multiple Locations Channel Availability Query March 2011 doc.: IEEE 802.11af-11/xxxx March 2011 Enhancing Channel Availability Query to support database query for multiple locations based on multiple-point locations Date: 2011-03-30 Authors: Multiple Locations Channel Availability Query Date: 2011-03-12 Author(s): Name Company Address Phone Email Yohannes D. Alemseged NICT 3-4, Hikarino-oka, Yokosuka, Kanagawa, Japan, 239-0847 +81 45 847 5097 yohannes@nict.go.jp Padam Kafle Nokia Steve Shelhammer Qualcomm Hiroshi Harada Yohannes Alemseged, NICT TexPoint fonts used in EMF. Read the TexPoint manual before you delete this box.: AAAAA Yohannes Alemseged, NICT

March 2011 Abstract This Presentation provides comment resolution for comments related with multiple locations channel availability query. The comments in general refer to the lack of the current TG 802.11af D1.0 draft to address the provision in the FCC 10-174 document that allows loading of channel lists for multiple locations so that mode II devices can operate in commonly available channels without contacting the database frequently. What is stated in the rule “A Mode II personal/portable device may load channel availability information for multiple locations around, i.e., in the vicinity of, its current location and use that information in its operation. A Mode II TVBD may use such available channel information to define a geographic area within which it can operate on the same available channels at all locations, for example a Mode II TVBD could calculate a bounded area in which a channel or channels are available at all locations within the area and operate on a mobile basis within that area”. FCC 10-174 Appendix B Final Rule, Yohannes Alemseged, NICT

Comments to be addressed in this presentation March 2011 Comments to be addressed in this presentation CIDs 117,119,120,121,122,123,124,125, 518, 946 CID Comment Resolution proposed by commenter 117 as it stands out the "Channel Availability Query" is a generic channel availability request applicable for a particular location. For personal portable devices that support to define a geographic area (an area formed from multiple locations) within which they can operate based on availability of channel information for multiple locations, a separate query frame like "Multiple Locations Channel Availability Query" should be sent. The September FCC release 10-174 states " Mode II personal/portable device may load channel availability information for multiple locations around, i.e., in the vicinity of, its current location and use that information in its operation. A Mode II TVBD may use such available channel information to define a geographic area within which it can operate on the same available channels at all locations, for example a Mode II TVBD could calculate a bounded area in which a channel or channels are available at all locations within the area and operate on a mobile basis within that area." The current channel availability query doesn't have the provision to exploit the above concept. Include an MLME service primitive exchange for a new frame "Multiple Locations Channel Availability Query". Details of such query is described in a comment resolution file DCN 11-11-0259-00-00af Yohannes Alemseged, NICT

Comments to be addressed in this presentation March 2011 Comments to be addressed in this presentation CID Comment Resolution provided by the commenter 119 Table 8-51 should include Multiple Location Channel Availability Query information element Include Multiple Chanel Availability Query in Table 8-51. The detail is desrcibed in a comment resolution file DCN DCN 11-11-0259-00-00af 120 Table 8-88 should include Multiple Location Channel Availability Query information element capability Include Multiple Channel Availability Query capacility description in Table 8-88. The detail is described in a comment resolution file DCN 11-11-0259-00-00af 121 The information elements in this section should include "multiple locations channel availability query" Include Multiple Channel Availability Query information element as section 8.4.2af7. The detail is described in a comment resolution file DCN 11-11-0259-00-00af 122 Section 8.4.5 should address / include "multiple location channel availability query" Include Multiple Channel Availability Query information element ID in Table 8-45af1, and include Channel availability query information element format in section 8.4.5. The detail is described in a comment resolution file DCN 11-11-0259-00-00af 123 Section 8.5 should address / include action frame format for "multiple location channel availability query" Include Multiple Channel Availability Query action field value in Table 8-131, and include Channel availability query public action frame format in section 8.5. The detail is described in a comment resolution file DCN 11-11-0259-00-00af 124 Section 8.5.11 should address / include protected dual of public action frame for "multiple location channel availability query" Include Multiple Channel Availability Query protected dual of public action field value in Table 8-143, and include Channel availability query protected dual of public action frame description in section 8.5.11 The detail is described in a comment resolution file DCN 11-11-0259-00-00af 125 Section 10.12.1 should include procedure for multiple location channel availability query Include multiple channel availability query procedure. The detail is described in a comment resolution file DCN 11-11-0259-00-00af Yohannes Alemseged, NICT

Comments to be addressed in this presentation March 2011 Comments to be addressed in this presentation CID Comment Resolution provided by the commenter 518 Current specification does not support mobility for devices while operating in TVWS band. For example, as per FCC's rules, a Mode II devices can obtain list of available channel for multiple locations to utilize such information for their operation while moving. Other regulatory consultations currently ongoing (e.g. Ofcom, CEPT SE43) are also supportive of mobility of TV band devices. Include the options as stated in the comment. 946 According to the FCC rule, a Mode II device may load channel availability information for multiple locations around, i.e., in the vicinity of, its current location and use that information in its operation. Describe how channel available query protoco obtains the channel availability information for multiple locations. The device location information may includes the vincity information by extending resolution value of the location information. Yohannes Alemseged, NICT

March 2011 Resolution provided to the comments CIDs 117,119,120,121,122,123,124,125, 518, 946 Resolution: Agree in principle, modify the current channel availability query to include the possibility of requesting for common channel list applicable to a bounded region by two points in addition to the channel list for the current location. 1- Add reason result code values in the CAQ reason result code table to represent success to provide common channel list 2- Use one bit in the CAQ information field serving as a flag during request for the common channel list applicable to a bounded region 3- Include option for multiple locations in the CAQ request frame to create a bounded region of interest 4-WSM field in the CAQ response frame either contains available common channel list for the bounded region depending on the CAQ information field Yohannes Alemseged, NICT

Assumptions in the proposed resolution March 2011 Assumptions in the proposed resolution TVWS data base can identify commonly available channels for a given volume (bounded by multiple point-locations) When applicable TVWS data responds to location information with multiple point-locations by looking at the device type, and location information All TVWS databases might not be capable to process and respond with a common channel to location information with multiple point-locations Yohannes Alemseged, NICT

March 2011 Explanation: How to determine a bounded region by using two or more location points X Illustrative example II (elevation info is omitted for presentation purpose) Location A and B are the two point locations (each with +-50 meter coordinates accuracy). The geographic volume between the two locations (A & B) defines the required available channel list. A: point geo-location (X0+σ1 , Y0+σ2) σ1 ≤ |50|m σ2 ≤ |50|m Y B: point geo-location (X0+σ1 , Y0+σ2) σ1 ≤|50|m σ2 ≤ |50|m Yohannes Alemseged, NICT

March 2011 Explanation: Channel Availability Query modified to support multiple locations channel load Extended CAQ Can be repeated to indicate multiple locations Info ID Length Requester STA Address Responder STA Address Reason Result Code Channel Query Info Device Class Device Identification Information Device Location Information WSM element body fields 1 2 6 variable Octets Yohannes Alemseged, NICT

Indication is done in the channel query info field March 2011 Explanation: Channel Availability Query modified to support multiple locations channel load Remarks: When a Mode II device, uses extended CAQ to request channel availability for multi-location purpose Indication is done in the channel query info field Multiple locations are provided. The multiple locations are used to define a bounded region for which common channel list is computed and returned Yohannes Alemseged, NICT

March 2011 Explanation: Channel Availability Query modified to support multiple locations channel load Remarks: When a Mode II device, uses extended CAQ to obtain channel availability for multi-location purpose, success to provide common channel list is indicated in the reason result code success to provide current location channel list is indicated in the reason result code Yohannes Alemseged, NICT

March 2011 Explanation: The Reason Result Code Table is modified to support multiple locations channel load Add Reason Result Code field value (4) with description Common Available Channel List result returned Modify the result code for success (3) with description Current Location Available Channel List returned Yohannes Alemseged, NICT

March 2011 Explanation: The channel query info field format is modified to support multiple locations channel load B2: Common channel request for multiple locations channel list present. If the bit of this field set to 1, channel availability query applies to the region of geo-location bounded by the multiple locations supplied Modify the reserved field B3-B7 B0 B1 B2 B3 B7 Device Identification Information Present Device Location Information Present Common channel request for multiple locations channel list is present Reserved Bits: 1 5 Yohannes Alemseged, NICT