Frequency Bands and Module Selection
The fragmentation of global LTE/NR frequency bands is severe, and the band list supported by the module hardware determines the countries and operators where it can be deployed. IoT projects should specify target countries, indoor/in-vehicle scenarios, and roaming requirements during the requirements phase, and then select modules accordingly. If only a single domestic band module is purchased, future exports may require hardware redesign. Multi-band support usually comes with higher costs and more complex antenna design, requiring trade-offs between BOM and performance.
Major Certification Systems
The US FCC, Canada ISED, EU RED, Japan TELEC, China SRRC, etc., have different limits and testing setups for transmit power, spurious emissions, occupied bandwidth, and SAR. Module vendors often provide module-level certifications and guidance, but after integration into the final product, whole-device or series certifications may still be required. Using a certified module does not automatically make the final product compliant; changes to antennas or enclosures may invalidate the certification conclusions.
Carrier Certification Entry
Apart from regulations, large carriers often have their own certification tests (such as PTCRB, GCF, carrier-customized OTA), focusing on frequency band combinations, voice and data KPIs. IoT SIM cards combined with modules also need to match the carrier's certified list. Project schedules should allocate time for retesting and rectification, especially when integrating a new antenna structure for the first time.
Documentation and Change Management
Maintain a certification matrix: hardware version, firmware version, antenna model, power level, and applicable regions. Compliance re-evaluation should be triggered during engineering change processes to avoid "small board changes invalidating certificates." External communications should comply with certification labeling requirements and avoid overstating coverage for unsupported bands.
Engineering Practice Supplement
Regarding "Frequency Band and Certification Planning," it is recommended to architect separate real-time control links and non-real-time telemetry links: control and interlock should be as local closed-loop as possible, and cellular should be used for monitoring, configuration, and OTA. On the cloud platform side, metrics such as observability indicators (connection duration, message latency distribution, failure codes, reconnection reasons) should drive optimization, rather than just checking "connectivity." Documentation deliverables should include interface descriptions, error code tables, extreme operating conditions, and known limitations; testing deliverables should include test cases, data, and conclusions for third-party retesting or auditing.
Why a module certificate cannot stand in for the product
Band and certification planning means deciding, before tooling, which frequencies this product may legally transmit on and which tests it must pass before it can be sold. A module vendor’s module-level result only says the module meets a set of conditions on the reference design. After the customer’s own antenna, enclosure, feeder, and supply are fitted, radiation, spurious emissions, and human exposure can all change. The conditions are that the target countries, operators, and indoor or outdoor use are frozen, that the hardware bands cover those cases, and that the change process reopens the assessment when the antenna or the power level changes.
Building the mechanics first and filling in the bands later is the most expensive order. More bands buy roaming and also multiply antenna bandwidth and certification combinations. List the bands that must be supported and the bands that can be left out. Do not promise the market every band printed on the specification. If voice, data, and a high-power mode will all appear, the test plan needs a case for each. Do not test only standby.
Changing the antenna after the band list is frozen
A common mistake is marketing copy that names a band the hardware was matched only on domestic bands. Another is assuming that because the module is already approved, the product can skip the rest. Carrier entry looks at the combination of product, SIM, and antenna. A reference board passing does not mean the customer’s mechanics pass. Once the power class changes, the scope of the existing test data ends.
When correcting a failure, split it into transmit spurious, receiver blocking, and exposure assessment rather than repeating every item. The conducted stage can look at the amplifier and filtering first; see conducted spurious emissions. If the service depends on multiple carriers, also confirm the combination is on the module list; see carrier aggregation. External material should name only the regions and bands already covered. Do not describe an untested combination as supported.
Once the power class changes, the old report no longer applies
The same module often has several power classes and bandwidth settings. Production firmware should stay locked to the class that was submitted. Do not open the power in the field, for edge coverage, into a range that was never tested. Band combinations are the same: if the lab tested only one set, the documents cannot say every combination is supported. Changing antenna suppliers, even with the same outline, can change the feed point and the dielectric, so radiation and human exposure both have to be looked at again. If the report, the firmware version, and the antenna model do not match, a field correction has no baseline. External material should list only power classes and band combinations that were tested. Untested combinations do not belong in the delivery scope.