Skip to content

To add VN_433 and VN_923 for Vietnam #7357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

IoTThinks
Copy link

This PR is to add VN_433 and VN_923 for Vietnam.

Main document: https://vanban.chinhphu.vn/default.aspx?pageid=27160&docid=204286 In Page 16: https://datafiles.chinhphu.vn/cpp/files/vbpq/2021/10/08-btttt.signed.pdf The accepted frequencies by Vietnam government is

  • Item 39: 433.05 - 434.79 MHz <=25 mW ERP
  • Item 45: 920 - 923 MHz <=25 mW ERP

This PR is to add VN_433 and VN_923 for Vietnam.

Main document: https://vanban.chinhphu.vn/default.aspx?pageid=27160&docid=204286
In Page 16: https://datafiles.chinhphu.vn/cpp/files/vbpq/2021/10/08-btttt.signed.pdf
The accepted frequencies by Vietnam government is

Item 39: 433.05 - 434.79 MHz <=25 mW ERP
Item 45: 920 - 923 MHz <=25 mW ERP
@IoTThinks
Copy link
Author

This is the related PR in protobufs: meshtastic/protobufs#730
Thanks a lot.

Copy link
Member

@caveman99 caveman99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to APPENDIX 19 of https://extendmax.vn/vietnam-mic-circular-08-2021-tt-btttt-list-of-equipment-exempt-from-frequency-license devices that want to use more than 10mW need to adhere to a duty cycle of 10% for base stations and 1% for clients. you can not operate meshtastic with these severe restrictions. Unfortunately we have to reject your request in the current form since it will violate local law.

@fifieldt
Copy link
Member

Original Appendix 19:
image

Translated version:

image

@IoTThinks
Copy link
Author

Let me double check and I may use another frequencies.
I will revisit this issue in a few days.
Thanks a lot.

@IoTThinks
Copy link
Author

IoTThinks commented Jul 17, 2025

Usually, we follow Singapore's guideline for LPWAN.
So let me compare the proposed VN_923 to SG_923.
This is to find a way and still comply to the local law.

In Meshtastic, SG_923 sets the duty cycle to 100% and power limit to 20dBm.
https://github.com/meshtastic/firmware/blob/master/src/mesh/RadioInterface.cpp#L151

image

In item 30c for LPWAN, the duty cycle for LPWAN is 1% too. Same as VN_923.

https://www.imda.gov.sg/-/media/imda/files/regulation-licensing-and-consultations/ict-standards/telecommunication-standards/radio-comms/imdatssrd.pdf

image

Meshtastic allows SG_923 to use 100% duty cycle because may be the proposer used item 30d to have no restriction to the duty cycle?
image

Then in the same way, VN_923 can use item 44 (instead of item 45) to have 100% duty cycle like SG_923?
https://datafiles.chinhphu.vn/cpp/files/vbpq/2021/10/08-btttt.signed.pdf
image

Item 44 in https://extendmax.vn/vietnam-mic-circular-08-2021-tt-btttt-list-of-equipment-exempt-from-frequency-license
image

What do you think?
Thanks a lot and have a nice day.

@fifieldt
Copy link
Member

Thanks for the work, I follow the logic.

I guess it depends on the definition of "Short Range Device". Based on what I've seen online, I think our devices could fit that, but I wouldn't be confident to make the call myself :) I'd like to get some more opinions.

@caveman99
Copy link
Member

The mentioned 'mitigation techniques' are not qualifierd here, but usually amount to CAD+AFA in other regulatory documents. We do CAD, but not AFA, so this usually does not apply.

@IoTThinks
Copy link
Author

IoTThinks commented Jul 22, 2025

If Meshtastic could have some LBT capabilities, then we could avoid a lot of regulation blockers.
Does Meshtastic have LBT (Listen before talk)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants