Update Maximum Duty Cycle information as per the EU regulations

[ymgupta]

Summary

The duty cycles regulations in Europe are defined in Table B.1 of the ETSI EN 300 220-2 V3.2.1 standard.

Why do we need this ?

To correct the duty cycle regulations of the g band in Europe as per the regulations.

What is already there? What do you see now?

The documentation here states that the duty cycle for the g band is 1%, but according to regulations, it is about 0.1%.

g (863.0 – 868.0 MHz): 1%

What is missing? What do you want to see?

Update the Duty Cycle of g band in the documentation according to the EU regulations.

How do you propose to document this?

...

Can you do this yourself and submit a Pull Request?

No.

[nejraselimovic]

@pradeeka7 does your PR address this too?

[pradeeka7]

I could not find the 'g-g4' naming scheme in this document, so we agreed to use the naming scheme (K-Q) specified in Table B.1." We now have to list 6 sub-bands instead of 5, as stated on the Duty Cycle page. I verified it with @adriansmares.

@ymgupta If we are wrong please correct us.

• K (863 MHz - 865 MHz): 0.1%, 25 mW ERP
• L (865 MHz - 868 MHz): 1%, 25 mW ERP
• M (868 MHz - 868.6 MHz): 1%, 25 mW ERP
• N (868.7 MHz - 869.2 MHz): 0.1%, 25 mW ERP
• P (869.4 MHz - 869.65 MHz): 10%, 500 mW ERP
• Q (869.7 MHz - 870 MHz): 1%, 25 mW ERP

PS - I still can't understand where the naming scheme 'g-g4' comes from, and many sources on the internet refer to it. After further searching, I found a document that mentioned frequency bands 'g-g4,' but it does not seem to match with LoRaWAN.

Page 10:

[pradeeka7]

@benolayinka, @nejraselimovic, @adriansmares please help me clarify this. I am still confused about these European sub-bands.

[adriansmares]

The G/G1-G4 naming scheme is a legacy naming scheme which I don't believe is in use any more. It is very likely that the old docs used it out of inertia (someone wrote them in 2014-2016, and then we've been carrying them ever since). The document linked about this scheme has been published in ~2011.

The ETSI EN 300 220-2 is published in ~2018 and is leading in this case. We use the K-Q band naming scheme, as well as restrictions, in The Things Stack today.

[pradeeka7]

@adriansmares - Thanks for the clarification. I used this K-Q naming scheme in this article (https://www.thethingsnetwork.org/docs/lorawan/regional-limitations-of-rf-use/). I remember we discussed the same for that.

I will update the page https://www.thethingsnetwork.org/docs/lorawan/duty-cycle/ and will submit a PR.

[pradeeka7]

@NicolasMrad can you assign this to me?

[pradeeka7]

@NicolasMrad - Now you can close this :)