Published On : July 2026
What regulatory and certification requirements govern 60GHz PtMP deployments across regions? The starting point for that question is understanding what license-free actually means in this context. The 57-71 GHz band is designated license-free, or unlicensed, in most major markets, meaning operators do not need to apply for spectrum usage rights the way they would for traditional licensed microwave frequencies. This is a core reason the 60GHz mmWave PtMP market has grown as quickly as it has, since removing the licensing step can shave months off a deployment timeline.
License-free, however, does not mean unregulated. Every jurisdiction still requires equipment to be certified against specific technical standards covering maximum transmit power, out-of-band emissions, and in many cases beam characteristics, before that equipment can be legally installed and operated. These requirements differ enough from region to region that a hardware platform certified in one market cannot simply be shipped and installed in another without going through that market's own certification process.
The practical effect for operators is a two-track evaluation whenever they consider a new market: one track assesses spectrum availability, which is generally favorable given the license-free status of the band, and a second, entirely separate track assesses equipment certification status, which varies by vendor and by jurisdiction. Conflating the two tracks is a common early mistake among teams new to this category, since a favorable spectrum environment says nothing about whether a specific piece of hardware is cleared to operate in it.
In the United States, 60GHz PtMP equipment is regulated under the FCC's Part 15 rules, which govern unlicensed radio frequency devices generally, alongside specific technical rules for the 57-71 GHz band that set maximum permitted power levels and antenna gain limits. Equipment intended for the US market must carry FCC certification confirming it meets these technical parameters before it can be marketed or deployed. This certification requirement applies uniformly regardless of whether the equipment is destined for a residential fixed wireless access rollout or an enterprise campus network, since the FCC's rules are use-case agnostic. Buyers evaluating hardware for a US deployment alongside its underlying beamforming-enabled hub radios and CPE should confirm current FCC certification status directly with the vendor rather than assuming certification carries over from a prior product generation.
Europe governs 60GHz equipment primarily through ETSI EN 302 217, a harmonized standard that, in principle, allows a single certification to apply across European Union member states. In practice, national telecommunications regulators still retain some latitude in how they implement and enforce the harmonized framework, which means operators expanding across multiple European countries should not assume a single certification eliminates all country-level administrative steps.
This regional patchwork matters most for operators running deployments that span several European markets simultaneously, since applications requiring cross-border consistency often involve municipal or multi-city contracts where a delay in one jurisdiction's paperwork can hold up an entire regional rollout schedule.
Operators that have run multi-country European rollouts generally recommend building a country-by-country compliance checklist early in project planning rather than assuming ETSI harmonization eliminates the need for one. National regulators in several markets require supplementary local filings even when the underlying hardware already holds ETSI EN 302 217 certification, and treating that step as optional has been a recurring source of schedule slippage for operators expanding into new European territories.
Japan's Ministry of Internal Affairs and Communications, commonly referred to as MIC, and Taiwan's National Communications Commission, or NCC, each maintain their own certification regimes for 60GHz equipment, distinct from both the FCC and ETSI frameworks. Vendors seeking to sell into these markets must pursue MIC or NCC certification specifically, and equipment certified only for the US or European markets cannot be deployed in Japan or Taiwan without going through this separate process. This creates a meaningful go-to-market consideration: vendors with vendors with regional certification coverage already spanning MIC and NCC hold a practical advantage when bidding into Asia-Pacific opportunities compared to vendors that would need to pursue new certification before they could compete.
Timelines for MIC and NCC certification can extend the overall procurement timeline for operators sourcing new hardware for these markets, which is one reason many system integrators in the region maintain relationships with a small, pre-vetted set of already-certified vendors rather than issuing open tenders that might introduce certification delays.
South Korea, Southeast Asian markets, and India each maintain their own equivalent certification bodies with requirements that broadly parallel the MIC and NCC frameworks but are not identical to either, meaning operators expanding across the wider Asia-Pacific region should expect to manage certification as a market-by-market workstream rather than a single regional approval.
|
REGULATORY UPDATE Regional certification remains fragmented rather than converging: FCC, ETSI, MIC, and NCC each maintain independent technical requirements, and operators expanding across borders should budget certification lead time as a distinct project milestone rather than an administrative afterthought. |
A certified deployment environment is one where every piece of installed hardware carries valid regulatory approval for that specific jurisdiction, verified and documented before installation. Non-certified environments, where equipment is installed without confirming local approval, expose operators to enforcement action, forced equipment removal, and reputational risk with regulators that can complicate future licensing or certification efforts.
This distinction becomes especially important during vendor selection and procurement planning, since certification status functions as a hard gate rather than a negotiable specification. A hardware platform that scores well on every other evaluation criterion is still not a viable choice if it lacks current certification for the deployment's specific jurisdiction, and buyers who confirm this early avoid discovering the gap only after equipment has already been shipped and scheduled for installation.
System integrators managing multi-country rollouts increasingly build certification verification into their standard procurement checklist, treating a vendor's current certification status in the target jurisdiction as a pass/fail gate rather than a secondary consideration weighed against price or delivery timeline. This is a meaningful shift from earlier practice, when certification status was sometimes assumed rather than independently confirmed before installation.
Insurance and liability considerations reinforce this shift as well. Enterprises and municipalities increasingly ask installation contractors to warrant, in writing, that every deployed unit carries valid local certification, shifting compliance risk explicitly onto the integrator rather than leaving it as an implicit assumption baked into the purchase order.
|
MARKET SHIFT Certification verification is moving from an assumed formality to an explicit, documented gate in enterprise and government procurement processes, reflecting growing regulatory scrutiny of unlicensed-spectrum deployments in dense urban environments. |