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 Canada (CA)
Date: Wed, 11 May 2022 09:39:56 -0500 [thread overview]
Message-ID: <YnvKvFu/QL8ty1vX@ubuntu-x1> (raw)
In-Reply-To: <CAPRryQoEAf+RUZh76tdb-_bLhc2VZpBNSp=9cd8mz8AQiB6iKg@mail.gmail.com>
On Wed, Apr 20, 2022 at 08:40:51PM -0600, Dennis Bland wrote:
> With the 6 GHz band (U-NII-5, U-NII-6, U-NII-7, U-NII-8) in Canada, ISED
> introduces the concept of a fixed PSD (Power Spectral Density) for all
> supported 6 GHz channel widths. 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.
>
> Clause 4.6.2 requires non-client (AP devices to have a maximum PSD of 5
> dBm/MHz and a maximum EIRP of 30 dBm. Clause 4.6.3 requires client (STA)
> devices to have a maximum PSD of -1 dBm/MHz. Clause 4.4 specifies a
> maximum channel width of 320 MHz. Clause 4.9 specifies indoor use only.
> Operation on oil platforms, vehicles, boats, trains, and drones is
> prohibited except on commercial aircraft above 10,000 feet altitude.
> There is no IR (Initiate Radiation) restriction mentioned in the 6 GHz
> specification.
>
> 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.
>
> signed-off-by: Dennis Bland <dennis@dbperformance.com>
Sorry for the delayed response. Thanks for the patch and the detailed
explanation. Everything here looks good to me.
The patch itself was corrupted. I fixed it up by hand, but for future
patches you might try 'git send-email', or if that won't work with your
email provider you can use 'git format-patch' and attach the patch file.
Also note that Signed-off-by should be capitalized. I fixed that when
applying.
Applied, 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 1:41 [wireless-regdb] Regulatory update for 6 GHz operation in Canada (CA) Dennis Bland
2022-04-19 19:53 ` Seth Forshee
2022-04-21 2:40 ` [wireless-regdb] [PATCH] " Dennis Bland
2022-05-11 14:39 ` 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=YnvKvFu/QL8ty1vX@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