Issue link: https://read.uberflip.com/i/1479525
LoRaWAN® Regional Parameters RP002-1.0.4 ©2022 LoRa Alliance ® Page 10 of 101 The authors reserve the right to change specifications without notice. 1 Introduction 336 337 This document describes the LoRaWAN regional parameters for different regulatory regions 338 worldwide. This document is a companion document to the various versions of the LoRaWAN 339 MAC Layer Protocol Specification [TS001]. Separating the regional parameters from the 340 protocol specification allows addition of new regions to the former document without impacting 341 the latter document. 342 343 The goal of the LoRa Alliance Regional Parameters Working Group is to allow the adoption of 344 the LoRaWAN technology across as many countries as possible. It is to the benefit of the 345 entire eco-system to minimize the number of distinct channel plan definitions. By re-using 346 existing channel plans for regulatory regions that are newly adopting LoRaWAN, the overall 347 effort and the time required for products to be available in the new market is minimized. The 348 Regional Parameters Working Group welcomes and encourages collaboration with local 349 companies and regulators when LoRaWAN is considered for introduction to a new country. 350 351 This document defines regional parameters described in all LoRaWAN Layer 2 Specifications 352 published prior to the publication of this document. Where differences exist between 353 LoRaWAN Layer 2 specification revisions, they are highlighted in the text. 354 355 Where various attributes of a transmission signal are stated with regard to a region or 356 regulatory environment, this document is not intended to be an authoritative source of regional 357 governmental requirements or regulations and we refer the reader to the specific laws and 358 regulations of the country or region in which they desire to operate in order to obtain 359 authoritative information. 360 361 It must be noted here that, regardless of the parameters specified or configured, at no time is 362 any LoRaWAN equipment allowed to operate in a manner contrary to the prevailing local rules 363 and regulations where it is operating. It is the responsibility of the LoRaWAN end-device or 364 gateway to ensure that compliant operation is maintained without any outside assistance from 365 a LoRaWAN network or any other external mechanism. 366 1.1 Conventions 367 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 368 "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in 369 this document are to be interpreted as described in BCP14 [RFC2119] [RFC8174] when, and 370 only when, they appear in all capitals, as shown here. 371 372 The tables in this document are normative. The figures and notes in this document are 373 informative. 374 375 Referenced document titles are written as LoRaWAN MAC Layer Protocol Specification and 376 referenced section titles within this document are written as "Physical Layer". 377 378 Commands are written NewChannelReq, parameters, bits, and bit fields are written 379 CFListType, constants are written RECEIVE_DELAY1, variables are written N. 380 In this document: 381 • The octet order for all multi-octet fields SHALL be little endian. 382 • EUI are 8-octet fields and SHALL be transmitted as little endian. 383 • By default, RFU bits are Reserved for Future Use and SHALL be set to 0 by the 384 transmitter of the packet and SHALL be silently ignored by the receiver. 385