From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH v2 5/5] wireless-regdb: Add regulatory info for Namibia (NA) for 2023
Date: Fri, 19 Jul 2024 11:23:26 +0800 [thread overview]
Message-ID: <20240719032326.7353-5-pkshih@gmail.com> (raw)
In-Reply-To: <20240719032326.7353-1-pkshih@gmail.com>
From: Ping-Ke Shih <pkshih@realtek.com>
COMMUNICATIONS REGULATORY AUTHORITY OF NAMIBIA released NOTICE IN TERMS OF
THE REGULATIONS REGARDING THE SUBMISSIONS OF INTERCONNECTION AGREEMENTS
AND TARIFFS on 3 April 2023 [1].
* 2400-2483.5 MHz
100 mW e.i.r.p.
* 5150-5350 MHz
200 mW mean e.i.r.p.
Restricted to indoor use
The maximum mean e.i.r.p. density shall be limited to 10 mW/MHz
(ETSI [2]: 200mW (23dBm) -3 dBm to be 20 dBm; DFS 5250-5350)
* 5470-5725 MHz
250 mW e.i.r.p.
Indoor as well as outdoor use allowed.
The maximum mean e.i.r.p. density shall be limited to 50 mW/MHz
(ETSI [2]: 250mW (24dBm) -3 dBm to be 21 dBm; DFS)
* 5725-5875 MHz
PTP/PTMP: max mean e.i.r.p = 4 W
Mesh/AP-MP: max mean e.i.r.p = 2 W
(ETSI [3]: The FWA device shall have the capability to reduce the
operating mean EIRP level to a level not exceeding 24 dBm for
ChS = 20 MHz and 21 dBm for ChS = 10 MHz. 24 dBm is adopted; DFS)
* 5925-6425 MHz
- 23 dBm (200mW) mean e.i.r.p
Restricted to indoor use only.
Mean e.i.r.p density for in-band emissions = 10 dBm/MHz
- 14 dBm (25) e.i.r.p mW
Very Low Power (VLP) indoor outdoor use.
Maximum mean e.i.r.p. for inband emissions = 1 dBm/MHz
* 57-66 GHz
40 dBm (10W) mean e.i.r.p
23 dBm/MHz e.i.r.p. density
Indoor use only
The EN 301 893 [2] specifies reduced power limit of 23 and 27 dBm for
5150-5350 MHz and 5470-5725 MHz respectively for devices that don't
implement TPC. Also reduced TPC requires being able to reduce TX power by
up to 3 dB. The DFS applicable frequency range are 5250-5350 MHz and
5470-5725 MHz.
[1] https://www.cran.na/yglilidy/2023/04/GG-8060-dated-3-April-2023.pdf
[2] EN 301 893 https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
[3] EN 302 502 https://www.etsi.org/deliver/etsi_en/302500_302599/302502/02.01.01_60/en_302502v020101p.pdf
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
v2:
- join to the same patchset
- 5150-5350 and 5470-5725 only reduce 3dB due to TPC
- 5725-5875 requires DFS
- fix wording in commit message:
* '5725-5 875 MHz' --> '5725-5875 MHz'
* '10 dBM/MHz' --> '10 dBm/MHz'
* 'Maximum meand e.i.r.p.' --> 'Maximum mean e.i.r.p' (drop extra 'd')
---
db.txt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/db.txt b/db.txt
index b5e40e038d77..4eaeaae616d8 100644
--- a/db.txt
+++ b/db.txt
@@ -1355,6 +1355,17 @@ country MY: DFS-FCC
(5735 - 5835 @ 80), (1000 mW)
(5925 - 6425 @ 320), (200 mW), NO-OUTDOOR
+# Source:
+# https://www.cran.na/yglilidy/2023/04/GG-8060-dated-3-April-2023.pdf
+country NA: DFS-ETSI
+ (2400 - 2483.5 @ 40), (100 mW)
+ (5150 - 5250 @ 80), (20), AUTO-BW, NO-OUTDOOR
+ (5250 - 5350 @ 80), (20), DFS, AUTO-BW, NO-OUTDOOR
+ (5470 - 5725 @ 160), (21), DFS
+ (5725 - 5875 @ 80), (24), DFS
+ (5925 - 6425 @ 320), (23), NO-OUTDOOR
+ (57000 - 66000 @ 2160), (40), NO-OUTDOOR
+
country NG: DFS-ETSI
(2402 - 2482 @ 40), (20)
(5250 - 5330 @ 80), (30), DFS
--
2.25.1
next prev parent reply other threads:[~2024-07-19 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 3:23 [PATCH v2 1/5] wireless-regdb: Update regulatory info for New Zealand (NZ) for 2022 Ping-Ke Shih
2024-07-19 3:23 ` [PATCH v2 2/5] wireless-regdb: Update regulatory info for Peru (PE) on 6GHz Ping-Ke Shih
2024-07-19 3:23 ` [PATCH v2 3/5] wireless-regdb: Update regulatory info for El Salvador (SV) " Ping-Ke Shih
2024-07-19 3:23 ` [PATCH v2 4/5] wireless-regdb: Update regulatory info for Togo (TG) for 2022 Ping-Ke Shih
2024-08-02 6:07 ` Chen-Yu Tsai
2024-08-02 7:11 ` Ping-Ke Shih
2024-07-19 3:23 ` Ping-Ke Shih [this message]
2024-08-02 6:06 ` [PATCH v2 1/5] wireless-regdb: Update regulatory info for New Zealand (NZ) " Chen-Yu Tsai
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=20240719032326.7353-5-pkshih@gmail.com \
--to=pkshih@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).