From: Seth Forshee <sforshee@kernel.org>
To: Dennis Bland <dennis@dbperformance.com>
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [PATCH] Regulatory update for 6 GHz operation in United States (US)
Date: Wed, 11 May 2022 09:40:31 -0500 [thread overview]
Message-ID: <YnvK3xt+1Reemaes@ubuntu-x1> (raw)
In-Reply-To: <CAPRryQp6j4UKvLZCkMAuQdaxepMBETQUJ1eNULJSh3ZWXC0f5Q@mail.gmail.com>
On Wed, Apr 20, 2022 at 08:56:38PM -0600, Dennis Bland wrote:
> With the 6 GHz band (U-NII-5, U-NII-6, U-NII-7, U-NII-8) in USA, the FCC
> introduces the concept of a fixed PSD (Power Spectral Density) for all
> supported 6 GHz channel widths for LPI (Low Power Indoor) environments.
> Wider channel widths have a higher noise floor, therefore specifying a
> fixed PSD allows wider channels to operate at a higher EIRP to maintain
> the same S/N ratio as smaller channel widths.
>
> While the 6 GHz specification also allows a "Standard" power mode with
> higher EIRP and PSD limits, these devices are also required to employ
> AFC (Automatic Frequency Coordination) which normally requires GNSS.
> Currently there is no way to specify different EIRP and PSD levels for
> APC and non-APC devices. Therefore, only LPI mode is considered here.
>
> LPI requires non-client (AP) devices to have a maximum PSD of 5 dBm/MHz
> and a maximum EIRP of 30 dBm. LPI requires client (STA) devices to have
> a maximum PSD of -1 dBm/MHz. The maximum channel width is 320 MHz.
>
> The following equation is used to calculate the EIRP from the PSD and
> channel width:
>
> EIRP = PSD + 10*log(channel width in MHz)
>
> Using the maximum PSD values of 5 and -1 for APs and STAs respectively,
> the EIRP in dBm for a given channel width can be calculated:
>
> Channel Width (MHz) AP STA
> ------------------------------------------------
> 20 18 12
> 40 21 15
> 80 24 18
> 160 27 21
> 320 31 (max 30) 25 (max 24)
>
> For channel widths up to 160 MHz, the maximum PSD is the limiting factor.
> For the 320 MHz channel width, the maximum EIRP is the limiting factor.
>
> Unfortunately, because there is currently no mechanism to specify
> different power levels for AP and STA modes, and for different channel
> widths, the smallest value has to be selected, which is 12 dBm. This
> will likely cause connectivity problems with larger channel widths until
> these additional parameters can be added.
>
> 6 GHz operation on oil platforms, vehicles, boats, trains, and drones is
> prohibited except on commercial aircraft above 10,000 feet altitude.
> An IR (Initiate Radiation) restriction is mentioned in the 6 GHz
> specification.
>
> signed-off-by: Dennis Bland <dennis@dbperformance.com>
Applied, with the same notes as with the other patch. Thanks!
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
prev parent reply other threads:[~2022-05-11 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 5:15 [wireless-regdb] Regulatory update for 6 GHz operation in United States (US) Dennis Bland
2022-04-19 19:59 ` Seth Forshee
2022-04-21 2:56 ` [wireless-regdb] [PATCH] " Dennis Bland
2022-05-11 14:40 ` Seth Forshee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YnvK3xt+1Reemaes@ubuntu-x1 \
--to=sforshee@kernel.org \
--cc=dennis@dbperformance.com \
--cc=wireless-regdb@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox