Discussion on 6 GHz Band Support

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /0010r0 January 2015 Sho Furuichi, SonySlide 1 Coexistence Scenario and Use Cases Date: Authors: Notice: This.
Advertisements

Doc.: IEEE SubmissionSlide 1 Expectation for IEEE P system from a primary protection viewpoint Notice: This document has.
Doc.: IEEE /160r0 SubmissionSlide 1 Output power management for TVWS network coexistence Notice: This document has been prepared to assist IEEE.
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 /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 /0052r1 March 2016 Sho Furuichi, SonySlide 1 Supplemental document for text proposal on amendment to entity operations Date:
Amendment Proposal for TV White Spaces Operation
Date: Authors: February 2010 Month Year
Comparison Between and af
Requirements and Amendments Regarding TVWS Database Access
Proposed basis for PAR discussion
IEEE ac/af and Spectrum Sharing
White Space Map Notification
Requirements Discussion
2111 NE 25th Ave, Hillsboro OR 97124, USA
On the Objectives and Scope of the WS Coexistence PAR
IEEE ac/af and Spectrum Sharing
IEEE af and Spectrum Sharing
Investigation Report on
Enabling signal and enablement
2111 NE 25th Ave, Hillsboro OR 97124, USA
EHT Potential Enhancement Discussion
EXtreme Throughput (XT)
Discussion on EHT PAR Construction
View on EHT Candidate Features
IEEE af and Spectrum Sharing
Secure Enablement and CVS without Persistent Association
Enabling Procedure of Communication in TVWS under FCC rules
Functional Requirements for EHT Specification Framework
Discussion on Multi-AP Coordination Type
Enabling signal and enablement
Discussion on Multi-AP Coordination Type
Consideration on 320MHz Bandwidth and 16 Spatial Streams
EHT Feature Discussion
TG1 and System Design Document
April 24, Study Group 1 A Regulatory Framework for Use of TV Channels by Part 15 Devices John Notor, Cadence Design Systems, Inc.
TVWS Enablement after New FCC Rules
11af architecture Date: Authors: May 2011 Month Year
July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: FCC Comments Supporting MBANS ET Docket
120 MHz PHY Transmission Date: Authors: January 2010
11be Peak Data Rate Analysis
Enabling Persistent Allocation for EHT
Multi-link Operation Framework
Multi-link Operation Framework
Multi-link Operation Framework
Functional Requirements for EHT Specification Framework
Enabling Persistent Allocation for EHT
Discussion on 6 GHz Band Support
Consideration on Multi-AP Sounding
Enabling Procedure of Communication in TVWS under FCC rules
Discussion on Multi-band operation
Proposed basis for PAR discussion
SM Power Save for 11ay Date: Authors: August 2017
EHT Multi-AP Feature Discussion
Consideration on Multi-AP Sounding
Coordinated Spatial Reuse Performance Analysis
Multi-link Operation Framework
A unified transmission procedure for multi-AP coordination
Date: Authors: February 2010 Month Year
Consideration on Multi-AP Ack Protocol
Multi-link power save operation
Multi-Link Architecture and Requirement Discussion
Discussion on Multi-band operation
Coordinated Spatial Reuse Performance Analysis
Multi-link Operation Framework
Multi-link Operation Framework
Presentation transcript:

Discussion on 6 GHz Band Support September 2018 doc.: IEEE 802.11-18/1533r0 July 2019 Discussion on 6 GHz Band Support Date: 2019-7-15 Authors: Name Company Address Phone Email Yusuke Tanaka Sony Corporation Yusuke.YT.Tanaka@sony.com Sho Furuichi Sho.Furuichi@sony.com Kosuke Aio Kosuke.Aio@sony.com Ryuichi Hirata Ryuichi.Hirata@sony.com Naotaka Sato naotaka.sato@ieee.org Chen Sun Chen.Sun@sony.com William Carney William.Carney@sony.com Yusuke Tanaka (Sony Corporation) Yusuke Tanaka(Sony Corporation), et al.

July 2019 Introduction Frequency range described in IEEE P802.11be PAR includes 6 GHz band [1]. 6 GHz band (5,925 – 7,125 MHz (US) / 5,925 – 6,425 MHz (EU)) is now under regulatory discussion to opening up for Wireless Access System including Radio LAN (WAS/RLAN). This contribution proposes way forward on IEEE P802.11be specification development for 6 GHz band support, assuming regulatory rules proposed as of today is the premise. Note that, in the world as of today, FCC is the only national regulatory authority (NRA) which has issued proposed “rule” for shared use of 6 GHz band. If the other NRAs propose different rules, we need to consider them also. Yusuke Tanaka (Sony Corporation)

Motivations Of great benefit to IEEE P802.11be: July 2019 Motivations Of great benefit to IEEE P802.11be: Great contributions to prospective new features such as contiguous 320 MHz bandwidth and Multi-Band Operation and Aggregation using 6 GHz. Good path forward to achieve “a maximum throughput of at least 30 Gbps” that is a main scope of TGbe [1]. Reality of 6 GHz availability Availability is up to the incumbent system protection requirements Primary allocation to other radio systems such as Fixed Systems (FS), Fixed Satellite Systems (FSS) (earth-to-space), i.e. they are incumbent systems. Wireless LAN to operate on a secondary basis, i.e. incumbent protection requirements will likely be imposed by national regulatory authorities (not only FCC but also the others). Entire 6 GHz band will not necessarily be available to wireless LAN. Yusuke Tanaka (Sony Corporation)

Examples of Proposed Rules to Ensure Incumbent Protection July 2019 Examples of Proposed Rules to Ensure Incumbent Protection Notice of Proposed Rulemaking (NPRM) issued by FCC [2]: 15.403 (b): Automated Frequency Coordination (AFC) is a system that automatically determines and provides lists of which frequencies are available for use by access points operating in the 5.925-6.425 GHz and 6.525-6.875 GHz bands. 15.407 (d)(3): Operation in the 6.425-6.525 GHz and 6.875-7.125 GHz bands is limited to indoor locations. 15.407 (k)(1): Access points operating in the 5.925-6.425 GHz and 6.525-6.875 GHz bands shall access an AFC system to determine the available frequencies at their geographic coordinates prior to transmitting. Access points may transmit only on frequencies indicated as being available by an AFC system. U-NII-5 U-NII -6 U-NII-7 U-NII-8 5,925 6,425 6,525 6,875 7,125 Freq [MHz] 500 MHz 100 MHz 350 MHz 250 MHz Database required Low power and indoor devices only Yusuke Tanaka (Sony Corporation)

Observations on 6 GHz Availability under the Proposed Rules July 2019 Observations on 6 GHz Availability under the Proposed Rules Only 29% of 6 GHz band is available without database access. Contiguous 320 MHz is unavailable without database access. Utilization of Non-contiguous 320 MHz operation is limited. A combination of 5 GHz band + U-NII-8 only (e.g. 160 MHz + 160 MHz). This will cause congestion in U-NII-8 band, that leads inefficient utilization of U-NII-8 band and non-contiguous 320 MHz operation. Yusuke Tanaka (Sony Corporation)

Consequences for the TGbe Spec Development July 2019 Consequences for the TGbe Spec Development TGbe needs to consider and develop a specification to utilize the entirety of the 6 GHz band. This is a key requirement to achieve “a maximum throughput of at least 30 Gbps” that is a main scope of TGbe, and also realize “320MHz bandwidth and more efficient utilization of non-contiguous spectrum” that is a candidate technology of TGbe. If not considered or defined in 11be: 71% of 6 GHz band cannot be utilized. Contiguous 320 MHz operation cannot be supported in 11be. Non-contiguous 320 MHz operation will be inefficient. Yusuke Tanaka (Sony Corporation)

TGbe Potential Focus Areas for Complete 6 GHz Band Support July 2019 TGbe Potential Focus Areas for Complete 6 GHz Band Support Develop database access (AFC) capability as one of 11be key functionalities. Development or enhancement of Interface (SAP), Primitive and Entity necessary for database access. Frame exchange to indicate available channels, maximum allowable transmission power, etc. which are authorized by database. Up to the final rules. Yusuke Tanaka (Sony Corporation)

July 2019 Proposed Way Forward Reuse of defined functionalities in IEEE 802.11af (WLAN for TVWS, a part of IEEE 802.11-2016 [3]). 11af = 11n/ac PHY/MAC + Operation under GDB 11be = new PHY/MAC + Amendment of Operation under GDB Merits of this approach TGbe can develop both 1) the new PHY/MAC and 2) operation under 6 GHz database access in parallel. Parallel development of PHY/MAC specification and database amendment accommodates the current regulatory uncertainties and may be faster than creating new database specification from scratch. TGbe can continue developing PHY/MAC even if some regulatory authorities do not adopt database access for 6 GHz use. Note that “new PHY/MAC” here covers any PHY/MAC development to be done by TGbe. Yusuke Tanaka (Sony Corporation)

802.11af High Level Architecture [3] July 2019 802.11af High Level Architecture [3] GDB dependent (GDD) enabling STA: A STA that has the authority to control the operation of GDD dependent STAs after obtaining available spectrum for use at its own location. . Geolocation Database (GDB): A database whose operation is mandated or authorized by a regulatory authority and that organizes storage of information by geographic location. GDB dependent (GDD) dependent STA: A STA that is under the control of a GDD enabling STA. For 6GHz support: § 15.403 (g) defines that Client Device is generally under the control of an access point. For 6GHz support: § 15.407 (k)(1) requires access points operating in U-NII-5 and 7 to access an AFC system Yusuke Tanaka (Sony Corporation)

802.11af High Level Architecture [3] July 2019 802.11af High Level Architecture [3] registered location secure server (RLSS): An entity that accesses and manages a database that organizes storage of information by geographic location and securely holds the location and some operating parameters of one or more basic service sets (BSSs) RLSS can access to GDB on behalf of one or more GDD enabling STAs. RLSS can manage one or more GDD enabling STAs. Yusuke Tanaka (Sony Corporation)

Observations from the Architecture July 2019 Observations from the Architecture AFC can be considered as another form of “GDB” employing capability to manage use of 6 GHz band A definition of “GDD enabling STA” can be re-used for 11be access points to meet FCC’s proposed requirement. obtaining available spectrum for use at its own location A definition of “GDD dependent STA” well matches with the definition of client device. generally under the control of GDD enabling STA “RLSS” can be re-used as network proxy to access AFC on behalf of one or more “GDD enabling STAs”. It would be beneficial for professional use such as enterprise network administrators, etc. Yusuke Tanaka (Sony Corporation)

Registered Location Query Protocol (RLQP) [3] July 2019 Registered Location Query Protocol (RLQP) [3] The query protocol for registered location information that is received and transported by generic advertisement service (GAS) Public Action frames. Registered location is defined as “the geolocation of a station (STA) registered in accordance with the requirements for the regulatory domain.” The specific mechanisms are as follows: Channel availability query, used to obtain one or more WSMs of available channels for an area or a geolocation Channel schedule management, used to obtain start and ending times for each available white space channel Contact verification signal, used by a GDD dependent STA to verify it is still receiving frames from its GDD enabling STA GDD enablement, the procedure where a GDD enabling STA forms a network and maintains the network under the control of a GDB Network channel control, used to inform a local channel controller that has a view of nearby transmitters and their emissions footprints WSM (white space map), used to retrieve the available white space channels and their transmit power restrictions RLQP could also be re-used but how to utilize/modify RLQP for 6 GHz support is for further study. Yusuke Tanaka (Sony Corporation)

July 2019 Conclusion To develop functionalities for 6 GHz band support will be a key requirement to achieve “maximum throughput of at least 30 Gbps” that is a main scope of TGbe [1]. TGbe should consider database access as one of these 11be functionalities so that it can globally achieve 30 Gbps where permitted. TGbe should consider: Interface (SAP), Primitive, Entity Frame exchange to available channels, maximum allowable transmission power, etc. Reuse and enhancement of “Operation under GDB” defined for 11af Yusuke Tanaka (Sony Corporation)

Reference [1] 11-18-1231-01-0eht-eht-draft-proposed-par July 2019 Reference [1] 11-18-1231-01-0eht-eht-draft-proposed-par [2] FCC 18-147, “Notice of Proposed Rulemaking”, ET Docket No. 18-295 Unlicensed Use of the 6 GHz Band, October 24, 2018 [3] IEEE Std 802.11™-2016 Yusuke Tanaka (Sony Corporation)

July 2019 Straw Poll 1 Do you think that TGbe may need to consider the NRA proposed rules such as database access requirements and so on to support the entirety of the 6 GHz bands? Yes No Need more information Yusuke Tanaka (Sony Corporation)

July 2019 Straw Poll 2 Do you think that so-called IEEE 802.11af could be a potential baseline reference for TGbe to develop a database access specification to use 6 GHz band? Yes No Need more information Yusuke Tanaka (Sony Corporation)