public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: "tavio.wong" <tavio.wong@proton.me>
Cc: "wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] wireless-regdb: Regulatory rules for Hong Kong (HK)
Date: Sat, 15 Apr 2023 19:00:32 -0500	[thread overview]
Message-ID: <ZDs6oG9jbKnJIDBS@ubuntu-x1> (raw)
In-Reply-To: <6r700jK10O2cquA_KXGtCw4lJFqxCnyvoY_1qcTfCcY-v0ncai7qKGIP4jAGBWeK2A8PoGKGtDDMxWhNP4S2oleHRvAEINXQ2BnP1aUM6KI=@proton.me>

On Wed, Mar 22, 2023 at 03:14:41PM +0000, tavio.wong wrote:
> Thanks for the feedback.
> 
> I have adjusted the rules as follows based on your suggestions and further research on FCC rules:
> 
> country HK: DFS-ETSI
> 	(2400 - 2483.5 @ 40), (30)
> 	(5150 - 5250 @ 80), (23), AUTO-BW, NO-OUTDOOR
> 	(5250 - 5350 @ 80), (23), DFS, AUTO-BW, NO-OUTDOOR
> 	(5470 - 5725 @ 160), (24), DFS
> 	(5725 - 5850 @ 80), (30)
> 
> 1. The ranges have been adjusted to align with HK regulations.
> 
> 2. For 2400-2483.5 MHz, max power is set to 1 W (30 dBm) based on [1] 47 CFR 15.247(b)(3).
> 
> 3. For 5470-5725 MHz, max power is set to 250 mW (24 dBm) based on [2] 47 CFR 15.407(a)(2).
> 
> 4. For 5725-5850 MHz, max power is set to 1 W (30 dBm) based on [3] 47 CFR 15.407(a)(3)(i).
> 
> 5. 5725-5730 MHz (Channel 144) is already covered by the last range (5725-5850 MHz) so no changes are necessary.
> 
> I have also cross-checked the limits to make sure they don't exceed those in the rules for US. The only difference in limits is in 5250-5350 MHz where HK regulations further restrict it to 200 mW (23 dBm).

Since explicit power limits are given I think we should be able to use
those. The reference to the US rules probably refers to other
requirements. So for 3 we can use 27 dBm and for 4 we can use 36 dBm.

> 
> One last suggestion: I noticed 6 GHz band is allowed for outdoor use at a max of 14 dBm (Section 3.2 of [4]) though it's only for licensed devices. Can it also be added to the rules as below?
> 	(5925 - 6425 @ 160), (14)

Yes, we could do it this way, or use the 24 dBm limit with NO-OUTDOOR.

Thanks,
Seth

> 
> Thanks again for your time.
> 
> [1] https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-C/subject-group-ECFR2f2e5828339709e/section-15.247#p-15.247(b)(3)
> 
> [2] https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-E/section-15.407#p-15.407(a)(2)
> 
> [3] https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-E/section-15.407#p-15.407(a)(3)(i)
> 
> [4] https://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkca1081.pdf
> 
> Best Regards,
> Tavio

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2023-04-16  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 14:37 [wireless-regdb] wireless-regdb: Regulatory rules for Hong Kong (HK) tavio.wong
2023-03-21 17:12 ` Seth Forshee
2023-03-22 15:14   ` tavio.wong
2023-04-16  0:00     ` Seth Forshee [this message]
2023-04-16 16:14       ` tavio.wong
2023-05-03 14:17         ` Seth Forshee

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=ZDs6oG9jbKnJIDBS@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=tavio.wong@proton.me \
    --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