Category: Blog

Every ISP or telecom operator launching 5G Fixed Wireless Access faces the same early architectural question: should we deploy outdoor CPE, indoor CPE, or a mix of both? The answer is never universal — it depends on spectrum band, cell density, building construction materials, target subscriber density, and the operators installation cost model. This guide provides a detailed technical comparison to inform a data-driven deployment strategy.

The Fundamental Trade-Off

At the architectural level, the outdoor-vs-indoor CPE decision is a trade-off between RF performance and deployment simplicity:

• Outdoor CPE: Maximizes signal reception by placing the antenna outside the building envelope, eliminating penetration loss through walls, low-E glass, and reinforced concrete. The trade-off: professional installation is nearly always required, adding $150–$400 per site in labor and mounting hardware.
• Indoor CPE: Minimizes deployment friction — the subscriber can self-install in minutes by placing the unit near a window. The trade-off: signal loss from building penetration, suboptimal antenna placement, and interference from indoor RF noise sources (Wi-Fi, Bluetooth, microwave ovens).

The operators achieving the best FWA economics do not choose one or the other — they develop a tiered deployment matrix based on RF planning data.

Signal Performance: Quantifying the Gap

Building Penetration Loss

The RF penalty for indoor placement is significant and highly variable. Measured at 3.5 GHz (n78), typical building penetration losses are:

• Wood-frame construction with standard glass: 8–12 dB
• Brick or concrete block with standard glass: 15–22 dB
• Low-E coated glass (common in modern buildings): 25–35 dB
• Reinforced concrete with metal-framed windows: 30–40+ dB

A 20 dB penetration loss effectively reduces the usable cell radius by 40–60%, depending on the propagation model. For an operator deploying on 3.5 GHz with inter-site distances of 800–1200 meters, this is the difference between serving 80% of homes in a cell versus 40%.

Antenna Gain Comparison

Modern outdoor CPE units achieve 10–14 dBi of directional gain through phased-array or high-gain panel antenna designs. Indoor CPE units, constrained by form factor and the need for omnidirectional coverage, typically deliver 3–5 dBi per antenna element in a 4×4 MIMO configuration. The net advantage — combining penetration loss avoidance and higher antenna gain — can exceed 20–30 dB in challenging deployment scenarios. That margin frequently determines whether a subscriber receives 100 Mbps or 10 Mbps.

Installation and Operational Considerations

Outdoor CPE Installation

Outdoor CPE requires a trained technician visit for mounting, cable routing, grounding (essential for lightning protection), and alignment toward the serving gNodeB. The process typically takes 60–90 minutes per site. Key installation requirements:

• Mounting: Wall bracket or pole mount at 3–6 meters above ground. Must be structurally secure and compliant with local building codes.
• Cabling: Outdoor-rated Cat6A or Cat7 Ethernet cable for PoE power and data backhaul to the indoor router/switch. Cable runs of up to 100 meters are possible with 802.3bt (Type 4, 60W) PoE injectors.
• Grounding: Per IEC 62305 and local electrical codes. The outdoor unit, Ethernet surge protector, and PoE injector must all be properly bonded to the buildings earth ground.
• Alignment: Using the CPEs onboard signal strength indicator (LED or mobile app RSSI readout), the technician aligns the directional antenna to maximize SINR, not just RSSI. This 5–10 minute step has an outsized impact on long-term throughput stability.

Indoor CPE Installation

Indoor CPE is designed for subscriber self-installation. The unit is placed near a window facing the general direction of the cell site, plugged into mains power, and connected to the home network via Ethernet or Wi-Fi. Setup typically takes under 10 minutes. However, self-install success rates vary significantly: operators report 15–25% of indoor self-installs require a technician follow-up due to poor placement, leading to borderline signal quality and higher churn risk.

Weatherproofing and Environmental Durability

Outdoor CPE must withstand years of exposure to sun, rain, snow, dust, and temperature extremes. The minimum acceptable ingress protection rating for outdoor CPE is IP67 (dust-tight and protected against temporary immersion). Many carrier-grade units go further with IP68. Key environmental specifications to verify:

• Operating temperature: –40°C to +60°C (outdoor), 0°C to +45°C (indoor)
• UV resistance: Enclosure material should be UV-stabilized (UL 746C f1 rating for outdoor use)
• Wind loading: Specified survival wind speed (typically 200+ km/h for pole-mounted units)
• Salt fog / corrosion: Per IEC 60068-2-52 for coastal deployments

Indoor CPE has significantly relaxed environmental requirements, which contributes to its lower unit cost. However, operators should still verify that indoor units meet relevant safety standards (IEC 62368-1) and do not exceed acceptable surface temperatures under sustained load.

Power over Ethernet (PoE) Architecture

Outdoor CPE is almost exclusively PoE-powered, eliminating the need for mains power at the mounting location. The current standard is IEEE 802.3bt (PoE++, Type 4) delivering up to 60W at the PSE (Power Sourcing Equipment), with 51W available at the PD (Powered Device) after cable losses. This is sufficient for outdoor CPE with active beamforming arrays, onboard GPS/GNSS, and a companion 2.5GbE switch.

For operators, the PoE architecture creates an additional deployment consideration: the indoor PoE injector or PoE switch becomes a single point of failure for the entire CPE link. Operators should budget for PoE injector replacements at a rate of 1–2% annually, and consider managed PoE switches with SNMP monitoring for remote power-cycle capability.

Spectrum Band Considerations

The outdoor-vs-indoor decision is heavily influenced by the spectrum band used for FWA:

• Sub-1 GHz (n5, n8, n28): Excellent propagation and building penetration. Indoor CPE performs well in most environments. Outdoor CPE may be unnecessary except in the most challenging locations.
• Mid-band 3.5 GHz (n77, n78): The most common FWA band globally. Building penetration loss is meaningful — outdoor CPE should be planned for 40–60% of subscribers, varying by building stock.
• mmWave (n257, n258, n260, n261): Near-zero building penetration. Outdoor CPE with line-of-sight to the gNodeB is effectively mandatory. Indoor mmWave CPE is only viable with specialized window-mounted units incorporating external antenna passthrough.
• C-band / 4.7 GHz (n79): Similar penetration characteristics to 3.5 GHz but with slightly higher loss. Outdoor CPE penetration in the deployment mix should be 5–10% higher than for 3.5 GHz deployments.

Total Cost of Ownership Comparison

Comparing CPE unit prices in isolation is a common procurement mistake. A realistic 36-month TCO comparison for a mid-scale deployment (5,000 subscribers) looks approximately like this:

Cost Component	Outdoor CPE	Indoor CPE
CPE unit cost (volume pricing)	$180–$320	$90–$180
Installation labor + hardware	$150–$400	$0 (self-install)
Annual failure rate	1.5–3%	3–6%
Truck roll cost per incident	$80–$150	$80–$150
Subscriber churn risk (annual)	8–12%	15–25%
Estimated 36-month TCO/sub	$450–$700	$380–$620

Counterintuitively, the higher upfront cost of outdoor CPE is often justified by lower churn and fewer support calls. Operators that deploy outdoor CPE in medium-to-weak signal areas while using indoor CPE in strong-signal zones consistently report better unit economics than those using a single CPE type across the entire footprint.

Recommendations: Building a Tiered Deployment Strategy

Based on field data from multiple operator deployments, we recommend the following tiered approach:

1. Strong-signal zones (RSRP > –95 dBm): Indoor CPE with self-install. 30–50% of subscriber base typically falls here in urban/suburban deployments on mid-band spectrum.
2. Moderate-signal zones (RSRP –95 to –110 dBm): Outdoor CPE with professional install. 35–50% of subscriber base. This is where outdoor CPE delivers the strongest ROI: converting marginal-signal locations into reliable service addresses.
3. Weak-signal zones (RSRP –110 to –120 dBm): High-gain outdoor CPE with precise alignment, possibly supplemented by external high-gain antennas. 10–15% of subscriber base. These locations should be carefully vetted during the site survey to avoid chronic support issues.
4. No-service zones (RSRP < –120 dBm): Do not deploy. Prioritize these areas for future small-cell or infill site expansion.

The exact thresholds should be tuned based on your specific spectrum, gNodeB configuration, and target throughput SLA. The principle, however, is universal: match the CPE type to the RF environment, not the other way around.

Frequently Asked Questions

What is the main advantage of outdoor 5G CPE over indoor CPE?

Outdoor CPE avoids building penetration loss (8–40 dB depending on construction materials) and uses high-gain directional antennas (10–14 dBi vs 3–5 dBi for indoor units). The combined signal advantage can exceed 20–30 dB in challenging locations, which is often the difference between reliable service and no service.

Can subscribers self-install outdoor 5G CPE?

While technically possible for some wall-mounted units, professional installation is strongly recommended for outdoor CPE. Proper mounting, grounding (essential for lightning protection), cable routing, and antenna alignment require training and specialized tools. Operators that allow self-install of outdoor CPE typically see higher failure rates and support costs.

What PoE standard is required for outdoor 5G CPE?

Most current outdoor 5G CPE requires IEEE 802.3bt (PoE++, Type 4) delivering 60W at the power source. This provides sufficient power for the modem, active antenna array, onboard processing, and a companion Ethernet switch. Verify the specific power budget with your CPE supplier before committing to PoE infrastructure.

Does outdoor CPE work in extreme weather conditions?

Carrier-grade outdoor CPE with IP67 or IP68 rating is designed for –40°C to +60°C operating temperature, 200+ km/h wind survival, and salt-fog resistance for coastal deployments. Always verify the environmental specifications against your target deployment geography.

Which is more cost-effective: outdoor or indoor CPE?

The answer depends on the RF environment. Indoor CPE has a lower upfront unit cost but higher churn risk and more support calls in marginal-signal areas. Outdoor CPE costs more upfront but delivers lower churn and better throughput stability. Most operators achieve the best economics with a tiered strategy: indoor CPE in strong-signal zones, outdoor CPE in moderate and weak-signal zones.

Planning a 5G FWA deployment and need expert guidance on CPE selection? Honlly Telecom provides both indoor and outdoor 5G CPE solutions with OEM/ODM customization for operators worldwide. Contact our engineering team for a consultation →

For a telecom operator, ISP, or MVNO launching — or scaling — a 5G Fixed Wireless Access service, the CPE device is not a commodity. It is the primary touchpoint with the subscriber, the single largest hardware cost per connection, and the component most likely to generate support calls if it underperforms. A poor CPE decision can erase the margin on an otherwise well-engineered FWA deployment.

Yet many procurement teams rely on a narrow set of criteria — price per unit, peak throughput on a spec sheet, and perhaps a reference customer or two. This article presents a structured 15-point framework for evaluating 5G CPE suppliers, covering the full lifecycle: silicon selection, software maturity, manufacturing quality, and long-term partnership viability.

Part 1: Silicon & RF Performance (Points 1–4)

1. Chipset Platform Generation

Begin with the modem-RF platform. As of mid-2026, the baseline should be Qualcomm Snapdragon X75/X80 or MediaTek T830. These platforms support 5G-Advanced features including AI-enhanced beamforming, multi-carrier aggregation (up to 4CA on sub-6 GHz), and improved power efficiency. Suppliers still offering X65/X70-based designs are shipping hardware that is two generations behind — the performance gap in real-world deployments is measurable and growing.

Evaluation action: Request the exact modem model and firmware revision. Verify it against the chipset vendors current product roadmap. Ask whether the supplier has committed volumes with the chipset vendor — this affects both pricing and long-term availability.

2. Carrier Aggregation Combinations

A 5G CPE spec sheet may list “3CA” or “4CA” support, but the specific band combinations matter enormously. An operator deploying on n78 (3.5 GHz) with n28 (700 MHz) for uplink coverage needs the CPE to support that exact combination, not a theoretical maximum. Request the suppliers certified CA combination table — preferably with GCF/PTCRB validation — and cross-reference it against your planned spectrum holdings.

3. Antenna Architecture and Gain

The antenna system — not the modem — often limits real-world CPE performance. Evaluate:

• Indoor units: 4×4 MIMO with at least 3–4 dBi per element across operating bands. Look for polarization diversity, not just spatial diversity.
• Outdoor units: Directional or phased-array design delivering 10–14 dBi gain across the primary band. Ask for 3D radiation pattern plots, not just single-number gain figures.
• Self-install vs. professional install: If targeting the consumer self-install market, the antenna must be forgiving of suboptimal placement. Request chamber test data showing performance at ±30° misalignment from boresight.

4. 5G-Advanced Readiness

CPE deployed in 2026 will likely remain in the field for 3–5 years. During that time, operator networks will activate 3GPP Release 18 features including AI/ML-based CSI compression, multi-TRP coordination, and enhanced positioning. Confirm whether the suppliers CPE can support these features via field-upgradable firmware, or whether they require a hardware swap. Suppliers that have demonstrated OTA firmware upgrades in production networks should score higher.

Part 2: Software, Management & Interoperability (Points 5–8)

5. TR-369 USP Support

The Broadband Forums User Services Platform (USP, TR-369) is the successor to TR-069 and is now the expected device management protocol for greenfield FWA deployments. A CPE without a mature USP agent creates operational friction: manual provisioning, reactive troubleshooting, and inability to push configuration changes or firmware updates at scale.

Evaluation action: Ask for the suppliers USP Agent conformance test results (TP-469). Request a live demo of remote provisioning, parameter get/set, firmware upgrade, and factory reset via USP. Confirm support for the Device:2 data model with WiFi. and Cellular. objects fully populated.

6. Zero-Touch Provisioning (ZTP)

Can the CPE be dispatched directly from the manufacturer to the end subscriber without intermediate staging? ZTP requires the device to bootstrap securely, contact the operators ACS (Auto Configuration Server), and download its configuration automatically. Evaluate the suppliers ZTP flow end to end, including secure credential injection at the factory (SCEP/EST-based certificate enrollment, not hardcoded passwords).

7. Interoperability Testing History

A CPE that works perfectly in the lab can fail mysteriously on a live network due to subtle RAN implementation differences between Ericsson, Nokia, Samsung, and Huawei gNodeBs. The supplier should provide IOT (Interoperability Testing) reports from at least two major RAN vendors, ideally including results from your specific network equipment vendor.

8. IPv6 and Dual-Stack Readiness

Many enterprise and government RFPs now require full IPv6 support. The CPE must handle IPv6-only WAN (464XLAT/CLAT), dual-stack, and IPv4aaS transparently. Confirm DHCPv6-PD (Prefix Delegation) for downstream LAN, SLAAC, and DNS64/NAT64 support.

Part 3: Hardware Quality & Manufacturing (Points 9–12)

9. Thermal Design Validation

5G CPE, especially outdoor units in direct sunlight, must dissipate 15–25W of thermal load without throttling. Request the suppliers thermal chamber test report showing sustained throughput at 55°C and 65°C ambient. Look for evidence of heatsink design, airflow modeling (CFD simulation), and component derating analysis. A CPE that throttles at high temperature will generate disproportionate support calls in warm-climate deployments.

10. Manufacturing Capacity and Quality Certifications

Visit the factory if possible; if not, request documentation. Key certifications: ISO 9001 (quality management), ISO 14001 (environmental management), and ideally IATF 16949 if the supplier also serves automotive — this indicates a high maturity level in manufacturing process control. Ask about monthly production capacity, typical lead times, and surge capacity (can they double output within 60 days?).

11. Regulatory Compliance Portfolio

CPE must carry regional certifications: FCC (US), CE (EU), UKCA (UK), ANATEL (Brazil), IC (Canada), RCM (Australia), and others depending on target markets. A supplier that already holds certifications for your target regions can save 8–16 weeks and significant cost versus pursuing new certifications. Request a compliance matrix showing exactly which SKUs hold which certifications.

12. Supply Chain Transparency

Post-2023, supply chain resilience is a board-level concern. The CPE supplier should disclose their bill of materials (BOM) risk assessment: which components are single-source, which have qualified second sources, and what alternative components are pre-validated. Suppliers with deep relationships with Qualcomm and MediaTek, and with strategic buffer stock agreements, should be preferred.

Part 4: Commercial & Partnership (Points 13–15)

13. Total Cost of Ownership, Not Unit Price

A low unit price can be deceptive. Calculate TCO over a 36-month lifecycle including: CPE unit cost, shipping and logistics, installation labor (outdoor CPE installs cost 3–5× more than indoor), predicted failure rate × replacement cost, firmware maintenance fees, and technical support burden. A CPE with a 1% lower annual failure rate can save hundreds of thousands of dollars at scale, even at a higher unit price.

14. OEM/ODM Flexibility

Does the supplier offer white-label and custom branding options? Can they customize the industrial design, packaging, firmware UI, and default configuration for your operator brand? For larger deployments, operator-specific firmware builds with custom TR-069/USP data model extensions, branded WebUI, and pre-loaded APN settings reduce deployment friction significantly.

15. Long-Term Roadmap Alignment

The best CPE supplier relationship is a partnership, not a transaction. Evaluate whether the supplier has a published product roadmap covering the next 24–36 months. Does it align with your network evolution plans — for example, do they have a Wi-Fi 8 CPE on the roadmap, or a 3GPP Release 19-capable device planned? A supplier investing in continuous R&D is more likely to remain a viable partner through the deployment lifecycle.

Scorecard Approach

We recommend scoring each of the 15 points on a 0–3 scale (0 = unacceptable, 1 = below average, 2 = meets requirements, 3 = exceeds requirements), then weighting according to your specific deployment priorities. A minimum threshold of 30 out of 45 (weighted) is a reasonable starting filter before proceeding to lab testing and field trials.

The operators that invest disciplined evaluation effort upfront consistently report lower churn, fewer support calls, and better subscriber NPS than those that select CPE primarily on price. In a market moving toward 100 million FWA connections, CPE quality is not a cost center — it is a competitive moat.

Frequently Asked Questions

Which chipset should a 5G CPE use in 2026?

For new FWA deployments, Qualcomm Snapdragon X75/X80 and MediaTek T830 are the recommended baseline platforms. These support 5G-Advanced features including AI-enhanced beamforming, 4CA carrier aggregation, and improved power efficiency. Avoid X65/X70-based designs for new rollouts.

What is TR-369 USP and why is it critical for 5G CPE?

TR-369 (User Services Platform) is the Broadband Forums modern device management protocol, replacing the aging TR-069. It enables operators to remotely provision, monitor, troubleshoot, and upgrade CPE at scale with a secure, efficient architecture. For FWA deployments spanning thousands or tens of thousands of units, a mature USP agent is operationally essential.

How much does 5G CPE cost for operators?

Indoor 5G CPE typically ranges from $80–$200 per unit in operator volumes (1,000+ units), while outdoor CPE ranges from $150–$350 depending on antenna complexity and enclosure requirements. However, total cost of ownership — including installation, support, failure replacement, and firmware maintenance — should be the primary metric, not unit price alone.

What certifications should a 5G CPE have for global deployment?

Essential certifications include FCC (US), CE (EU), UKCA (UK), IC (Canada), ANATEL (Brazil), and RCM (Australia/NZ). Additional certifications may be required for specific markets — suppliers with a broad existing certification portfolio can reduce time-to-market by 8–16 weeks.

Should operators choose outdoor or indoor CPE for FWA?

Most successful FWA deployments use a mix: outdoor CPE with high-gain directional antennas in cell-edge and weak-signal locations, indoor CPE with omnidirectional antennas in strong-signal urban and suburban areas. The decision should be based on RF planning data, not a one-size-fits-all approach.

Evaluating 5G CPE suppliers for your next network deployment? Honlly Telecom offers carrier-grade 5G CPE, OEM/ODM manufacturing, and customized solutions for ISPs and operators worldwide. Speak with our solutions team →

The global telecom CPE supply chain is built on three distinct manufacturing partnership models — OEM, ODM, and JDM. Yet many telecom buyers enter factory negotiations without a clear understanding of how these models differ, what they imply for intellectual property, lead times, unit economics, and ongoing product support. This guide clarifies each model and provides a framework for selecting the right approach.

The Three Models Defined

OEM (Original Equipment Manufacturing)

In an OEM engagement, the buyer owns the product design, specifications, and intellectual property. The factory serves as a build-to-print manufacturing partner: it procures components per the buyer’s approved BOM, assembles the product according to the buyer’s engineering documentation, and executes quality control against the buyer’s acceptance criteria. The buyer retains full control over design, component selection, firmware, and branding.

Best for: Operators and enterprises with existing hardware engineering teams and proven reference designs who need capacity or cost optimization in manufacturing.

Typical MOQ: 10,000–50,000 units, depending on BOM complexity and component lead times.

Lead time: 16–24 weeks from PO to first shipment, assuming design is frozen and tooling is complete.

ODM (Original Design Manufacturing)

In an ODM model, the factory develops, designs, and manufactures a product that is sold under the buyer’s brand. The ODM owns the core hardware design, software platform, and sourcing relationships. The buyer selects from the ODM’s existing product portfolio (or commissions minor modifications) and applies branding, packaging, and go-to-market execution. This is the most common model in the CPE industry for operators seeking quick time-to-market with proven hardware.

Best for: Operators, MVNOs, and distributors who want to launch branded CPE products without investing in hardware R&D. Ideal for 4G MiFi, 5G FWA CPE, and indoor/outdoor routers.

Typical MOQ: 500–5,000 units for standard SKUs; 5,000+ for hardware modifications.

Lead time: 4–8 weeks for standard white-label products; 12–20 weeks with hardware modifications.

JDM (Joint Design Manufacturing)

JDM represents a collaborative middle ground. The buyer and manufacturer jointly define the product specification, share design responsibilities, and co-develop the solution. The buyer typically contributes system architecture, industrial design direction, and user experience requirements, while the manufacturer contributes hardware engineering, RF design, sourcing, and production engineering. IP ownership is negotiated and shared per the JDM agreement.

Best for: Operators and technology companies with domain expertise and specific performance requirements but without a full in-house hardware engineering team. Common for carrier-grade CPE, specialized outdoor units, and 5G mmWave devices.

Typical MOQ: 5,000–20,000 units, reflecting the shared investment in development.

Lead time: 20–36 weeks from joint specification freeze to first shipment.

Decision Framework: Choosing Your Model

Factor	OEM	ODM	JDM
IP Ownership	Buyer owns all	ODM owns design; buyer owns brand	Shared per agreement
Time to Market	Longest (16–24 weeks)	Fastest (4–8 weeks)	Medium (20–36 weeks)
NRE Cost	Highest (tooling, line setup)	Lowest (branding only)	Moderate (shared cost)
Per-Unit Cost	Lowest at scale	Standard ODM pricing	Competitive at volume
Design Control	Full buyer control	Limited (brand-level)	Shared (collaborative)
Best For	Own design, need scale	Quick launch, proven HW	Custom product, shared R&D

How to Evaluate an ODM/JDM Partner: Red Flags to Watch

Selecting the right manufacturing partner is as important as choosing the model itself. Based on Honlly’s experience working with operators across 30+ countries, here are the red flags procurement teams should watch for:

1. Undocumented design ownership: If the ODM cannot produce a clear bill of materials with component source traceability and design version history, walk away. This indicates poor engineering discipline that will manifest as quality problems downstream.
2. No in-house RF lab: CPE is fundamentally an RF product. A manufacturer without an anechoic chamber, vector network analyzer, and conducted/radiated test capability cannot properly validate antenna performance, TRP/TIS, or regulatory compliance.
3. Opaque firmware roadmap: Ask for the last 12 months of firmware release notes. A manufacturer with irregular or undocumented firmware updates will be a liability when security vulnerabilities or carrier certification updates are required.
4. Unclear certification ownership: Confirm who pays for and maintains certifications (FCC, CE, GCF, PTCRB). If a certification lapses, who bears the recertification cost? These terms must be explicit in the manufacturing agreement.
5. No regional support infrastructure: A factory that cannot provide local-language technical support, RMA handling, and spare parts logistics in your target market will create operational headaches that erode any per-unit cost advantage.

The Honlly Approach: Flexible ODM with JDM Capability

Honlly Telecom operates primarily as an ODM partner for 4G/5G CPE, MiFi, and FWA devices, but maintains in-house hardware and RF engineering teams that enable JDM-style collaboration for operators with specific performance or form-factor requirements. Our Shenzhen-based engineering center includes a full anechoic chamber, thermal testing lab, and software QA infrastructure that supports end-to-end product development from concept through mass production.

For operators evaluating manufacturing partnerships, we recommend starting with an ODM engagement on a proven platform to validate quality, delivery reliability, and support responsiveness. As the relationship matures, JDM collaboration becomes a natural next step for custom product development.

FAQ

What is the difference between OEM and ODM in CPE manufacturing?

In OEM, the buyer owns the product design and the factory builds to the buyer’s specifications. In ODM, the factory owns the design and the buyer brands and sells the product. ODM is the faster, lower-cost path to market for operators without in-house hardware engineering.

What is JDM manufacturing?

JDM (Joint Design Manufacturing) is a collaborative model where buyer and manufacturer jointly define specifications and share design responsibilities. It combines the buyer’s market and UX expertise with the manufacturer’s hardware engineering capabilities.

What MOQ should I expect for ODM CPE products?

Standard white-label ODM CPE typically requires 500–5,000 units minimum order quantity. Customized hardware modifications raise the MOQ to 5,000+ units. OEM builds generally require higher MOQs (10,000+).

How long does it take to bring an ODM CPE product to market?

Standard ODM white-label CPE can ship in 4–8 weeks. Products requiring hardware modifications typically take 12–20 weeks. JDM development adds 20–36 weeks from specification freeze.

4G MiFi devices remain the workhorse of enterprise mobile connectivity in 2026. Despite the rapid expansion of 5G networks, LTE-based mobile hotspots continue to serve the vast majority of field workforce deployments, fleet connectivity applications, and temporary site setups across global markets. The reasons are straightforward: mature coverage, predictable performance, lower device and service costs, and a deep ecosystem of certified hardware.

For telecom operators, ISPs, and enterprise procurement teams, selecting the right 4G MiFi device is not a trivial exercise. The market offers dozens of models from established ODMs and emerging manufacturers, each with different feature sets, frequency band support, and management capabilities. A poorly specified device can lead to increased support tickets, early hardware replacement cycles, and frustrated end users.

This checklist identifies the 12 features that procurement professionals should verify before signing a purchase order — organized by category for systematic evaluation.

Category 1: Radio Frequency and Network Performance

1. LTE Category and Carrier Aggregation Support

The LTE category defines the device’s theoretical peak throughput. For enterprise MiFi, Category 6 (300 Mbps down / 50 Mbps up) is the practical minimum in 2026. Category 12 (600/100 Mbps) or Category 16 (1 Gbps/150 Mbps) devices offer meaningful real-world improvements through 3x carrier aggregation and 256QAM, particularly in congested urban environments. Verify that the vendor specifies the supported CA band combinations relevant to your deployment region.

2. Frequency Band Coverage

At minimum, the device should support B1/B3/B5/B7/B8/B20/B28 for EMEA deployments, or B2/B4/B5/B12/B13/B14/B66/B71 for North America. For operators serving multiple regions, pan-regional SKUs with 12+ bands reduce inventory fragmentation. Always request a complete band list with 2CA and 3CA combination tables from the vendor.

3. MIMO and Antenna Configuration

2×2 MIMO is table stakes. Devices with external antenna ports (TS-9 or SMA) provide substantial throughput gains in fringe-coverage areas when paired with external LTE antennas. For fleet and vehicle-mounted applications, this feature is non-negotiable.

Category 2: Connectivity and Concurrent Users

4. Wi-Fi Specifications

Dual-band concurrent Wi-Fi (2.4 GHz + 5 GHz) with 802.11ac Wave 2 is the minimum standard. For higher-density deployments, seek 802.11ax (Wi-Fi 6) support which provides OFDMA-based efficiency gains when serving multiple simultaneous clients. Verify the maximum Wi-Fi connected client count — 16+ users is expected for enterprise MiFi.

5. Ethernet and USB Tethering

Many enterprise use cases require wired connectivity. A Gigabit Ethernet port (RJ-45) enables the MiFi to function as a primary WAN link for a small router or firewall. USB 3.0 tethering support with RNDIS/ECM driver compatibility ensures the device can connect to Linux-based edge gateways and industrial controllers.

Category 3: Power and Physical Design

6. Battery Capacity and Runtime

For field workforce devices, a minimum 3,000 mAh removable battery delivering 8+ hours of active use is expected. For always-on applications, devices supporting battery-bypass operation (powered via USB or DC while battery is removed) prevent battery swelling common in 24/7 plugged-in deployments.

7. Enclosure Durability and Environmental Rating

For indoor use, standard plastic enclosures suffice. For outdoor, industrial, or vehicle-mounted deployments, look for IP54 or higher ingress protection, operating temperature range of -10°C to +55°C, and vibration resistance compliance (MIL-STD-810G or equivalent).

Category 4: Device Management and Security

8. Remote Device Management Protocol Support

TR-069 (CWMP) remains the most widely deployed CPE management protocol; TR-369 (USP) is the emerging standard. Verify which protocol the device supports and confirm interoperability with your ACS platform (GenieACS, AVSystem, Friendly, etc.). At minimum, the device should support remote firmware upgrade, configuration push, parameter monitoring, and reboot via the management protocol.

9. VPN and Security Features

Enterprise MiFi devices should support IPsec and L2TP/IPsec VPN passthrough, WPA3-Personal Wi-Fi security, and a configurable firewall with ACL support. For regulated industries, verify FIPS 140-2 or equivalent cryptographic module validation.

10. SIM Management

eSIM (eUICC) support is increasingly important for operators managing large fleets across multiple MNO profiles. Physical SIM slot type (2FF/3FF/4FF) compatibility and dual-SIM capability for failover scenarios should also be specified in the RFP.

Category 5: Software and Customization

11. Branding and UI Customization

If the device will be sold under your operator brand, confirm that the ODM supports complete white-labeling: custom boot logo, Web UI branding (logo, color scheme, SSID prefix), packaging design, and firmware default configuration pre-loading. Ask for the MOQ threshold for each customization tier.

12. Regulatory Certification Portfolio

Verify that the device carries current certifications for your target markets: CE (EU), FCC (US), ISED (Canada), RCM (Australia), NCC (Taiwan), and any other market-specific requirements. For operators, GCF and PTCRB certification streamline network approval processes.

Procurement Evaluation Matrix

When evaluating multiple vendors, use a weighted scoring matrix. Recommended weights: RF performance and band coverage (25%), device management capabilities (20%), durability and power (15%), security features (15%), customization and branding (15%), and certifications (10%). This structured approach prevents procurement teams from being swayed by a single standout feature while overlooking critical gaps.

FAQ

What is the minimum LTE category for an enterprise-grade 4G MiFi?

Category 6 (300 Mbps down) is the practical minimum in 2026. Category 12 or higher provides meaningful real-world improvements through 3x carrier aggregation and is recommended for deployments in congested urban environments.

Does a 4G MiFi need external antenna ports?

For fleet, vehicle-mounted, and fringe-coverage applications, external antenna ports (TS-9 or SMA) are strongly recommended. They provide 3–6 dB signal improvement when paired with external LTE antennas, which directly translates to higher throughput and fewer dropped connections.

Should I choose a 4G MiFi with eSIM support?

If you manage a fleet of devices across multiple MNOs or plan to change carrier profiles remotely, eSIM (eUICC) support is highly valuable. It eliminates physical SIM swaps and enables over-the-air profile provisioning via GSMA-compliant RSP platforms.

What device management protocols should a 4G MiFi support?

TR-069 (CWMP) remains essential for compatibility with existing ACS platforms. TR-369 (USP) is the future direction and should be considered for new deployments. Both protocols enable remote configuration, firmware updates, and monitoring at scale.

One of the most consequential decisions in a 5G Fixed Wireless Access (FWA) deployment is the choice of radio spectrum specifically, whether to deploy in millimeter wave (mmWave) bands above 24 GHz or in sub-6 GHz bands below 6 GHz. Each spectrum type imposes fundamentally different requirements on the CPE hardware, the installation process, and the network planning methodology. This article provides a structured comparison to help ISPs, system integrators, and telecom operators make informed CPE procurement decisions.

The Physics of the Two Spectrum Worlds

Sub-6 GHz 5G operates in bands such as n1 (2100 MHz), n3 (1800 MHz), n7 (2600 MHz), n28 (700 MHz), and n78 (3500 MHz). These frequencies propagate well through walls, foliage, and moderate obstacles, with typical outdoor-to-indoor penetration loss of 10-18 dB. A sub-6 GHz CPE installed indoors near a window can often achieve usable signal quality without external antenna mounting. Range is measured in kilometers: a well-engineered n78 deployment with 4×4 MIMO and 256QAM can serve customers 3-5 km from the cell site in suburban environments.

mmWave 5G operates in bands such as n257 (28 GHz), n258 (26 GHz), n260 (39 GHz), and n261 (28 GHz, US). At these frequencies, propagation is fundamentally different. Free-space path loss is 20-30 dB higher than sub-6 GHz at equivalent distance, outdoor-to-indoor penetration through modern energy-efficient windows can exceed 25-30 dB of loss, and even foliage or heavy rain can attenuate the signal. A single tree between the cell site and the CPE can reduce mmWave throughput by 50% or more. The practical range for mmWave FWA is typically 300-800 meters in urban deployments and requires near-line-of-sight conditions.

However, mmWave compensates for propagation challenges with raw bandwidth. A single n257 carrier in the 28 GHz band can be up to 400 MHz wide four times the maximum 100 MHz carrier width available in n78 sub-6 GHz. This translates directly into multi-gigabit peak throughput: commercial mmWave CPE devices routinely deliver 2-4 Gbps downlink under good signal conditions, compared to 500 Mbps to 1.5 Gbps for sub-6 GHz CPE in typical deployments.

CPE Hardware: Different Requirements, Different Designs

The physical design of mmWave CPE differs substantially from sub-6 GHz CPE due to the antenna requirements. mmWave devices use phased-array antenna modules typically 16 to 64 antenna elements arranged in a flat panel to achieve beamforming gain that compensates for path loss. These modules are physically larger than sub-6 GHz antennas and must be mounted with a clear, unobstructed view of the serving cell, which almost always requires outdoor installation.

Outdoor mmWave CPE, such as Honlly Telecom HL-880U series, integrates the phased-array antenna, modem, and networking electronics into a single IP67-rated enclosure designed for pole, wall, or rooftop mounting. Power is delivered via Power over Ethernet (PoE), and the indoor unit connects through a single Ethernet cable. This architecture eliminates the RF cable loss that would be incurred by a split indoor-outdoor design a critical advantage at mmWave frequencies where every decibel of loss matters.

Sub-6 GHz CPE offers more deployment flexibility. Indoor desktop CPE with integrated antennas can serve a significant portion of the coverage footprint, especially in the lower bands (n28, n3, n1) where building penetration is adequate. For edge-of-coverage or rural deployments, outdoor sub-6 GHz CPE with high-gain directional antennas (8-12 dBi) can extend range and improve signal quality, trading some installation simplicity for better performance.

Deployment Scenarios: When to Choose Which

Urban and dense suburban FWA. In neighborhoods where cell sites are spaced 500-800 meters apart and subscribers are concentrated, mmWave FWA delivers fiber-like speeds that can compete directly with cable broadband. The CPE cost is higher (typically 2-3x a comparable sub-6 GHz device), but the capacity advantage per sector makes it viable where subscriber density justifies the investment. Operators such as Verizon have deployed mmWave FWA to over 40 million households in the US using this model.

Suburban and rural broadband. Where cell site spacing exceeds 1-2 km, sub-6 GHz FWA is the practical choice. The longer range and better non-line-of-sight (NLOS) performance of sub-6 GHz bands particularly when combining low-band carriers (n28, 700 MHz) for coverage with mid-band carriers (n78, 3500 MHz) for capacity via carrier aggregation provides a more cost-effective solution for lower-density areas. A single n78 cell site can cover an area 10-25 times larger than a mmWave site, dramatically reducing infrastructure cost per subscriber.

Enterprise and industrial fixed wireless. For enterprise customers requiring symmetric multi-gigabit throughput think video production studios, data center interconnects, or campus backbone links mmWave is the preferred option when line-of-sight conditions exist. For enterprise applications where reliability and availability outweigh peak throughput (e.g., retail point-of-sale, branch office connectivity, backup WAN), sub-6 GHz CPE with dual-SIM failover provides a more resilient solution.

Cost Comparison: Total Cost of Ownership

The per-device cost comparison tells only part of the story. A comprehensive TCO analysis for FWA deployments should account for multiple factors:

• CPE unit cost: mmWave CPE typically ranges from USD 300-600 per unit, compared to USD 120-350 for sub-6 GHz CPE
• Installation cost: mmWave requires professional outdoor mounting at USD 150-400 per site, while sub-6 GHz can often be self-installed indoors (USD 50-200 for outdoor installs)
• Site survey requirements: Essential for mmWave line-of-sight verification; recommended for edge-of-coverage sub-6 GHz only
• Cell site density: mmWave requires 300-800m spacing with more sites needed; sub-6 GHz works with 1-5 km spacing
• Capacity per sector: mmWave delivers 4-8 Gbps supporting high subscriber density; sub-6 GHz delivers 1-3 Gbps for moderate density

Decision Framework: Five Questions to Guide Your Choice

1. What is the target subscriber density? High-density urban areas with more than 500 potential subscribers per square kilometer favor mmWave. Rural areas with fewer than 50 subscribers per square kilometer almost always favor sub-6 GHz.
2. What throughput SLA are you offering? If the service tier requires more than 500 Mbps downlink consistently, mmWave becomes the primary candidate. For service tiers up to 100-300 Mbps, sub-6 GHz is typically sufficient.
3. Can you support professional truck-roll installations? If the business model relies on self-install, sub-6 GHz indoor CPE is the only practical option. mmWave FWA requires professional installation for antenna alignment and line-of-sight verification.
4. What spectrum do you have access to? This is often the decisive factor. Operators with substantial mmWave holdings can deploy mmWave FWA. Operators with primarily sub-6 GHz spectrum will naturally deploy sub-6 GHz FWA, potentially augmenting with mmWave in high-demand urban hotspots.
5. Is the deployment indoors or outdoors? Indoor CPE almost always operates in sub-6 GHz bands, as mmWave building penetration loss is prohibitive. Outdoor CPE can support either spectrum type, with the choice driven by the factors above.

The Hybrid Future: Multi-Band CPE

An emerging category of CPE combines sub-6 GHz and mmWave radios in a single device, using sub-6 GHz as an anchor for coverage and reliability while aggregating mmWave for capacity bursts. Qualcomm Snapdragon X80 modem-RF platform, announced in early 2026, supports concurrent sub-6 GHz + mmWave aggregation with intelligent traffic steering. While these multi-band devices currently command a premium, they represent a strategic option for operators planning long-term FWA infrastructure that can adapt to evolving spectrum availability and subscriber demand.

Frequently Asked Questions

Q: Can a single CPE support both mmWave and sub-6 GHz?
A: Yes, multi-band CPE devices with dual radio chains can support both spectrum types, though they are more expensive than single-band devices. These are increasingly common in the premium CPE segment and are well-suited for operators who want deployment flexibility across diverse coverage footprints.

Q: Does weather affect mmWave CPE performance?
A: Yes. Heavy rain causes attenuation of 5-10 dB/km at 28 GHz, snow accumulation on antenna enclosures, and even dense fog can reduce mmWave signal quality. Outdoor mmWave CPE should be specified with adequate link budget margin (typically 10-15 dB above the minimum usable signal) to maintain service during adverse weather conditions.

Q: Is sub-6 GHz 5G fast enough compared to mmWave?
A: For the vast majority of residential and small business FWA use cases, sub-6 GHz 5G delivering 100-500 Mbps is more than adequate supporting 4K streaming, video conferencing, cloud applications, and multiple simultaneous users. mmWave becomes relevant when service tiers exceed 500 Mbps or when very high per-sector capacity is needed to serve dense subscriber concentrations.

---

Looking for CPE solutions optimized for your spectrum strategy? Honlly Telecom supplies both sub-6 GHz and mmWave-ready CPE devices for fixed wireless access deployments worldwide, with carrier-grade TR-369 management and flexible OEM customization options. Contact our team to discuss your requirements.

When evaluating 4G and 5G CPE for procurement, one specification consistently correlates with real-world performance yet is often misunderstood by buyers: carrier aggregation (CA). A device CA capability directly determines peak throughput, cell-edge performance, and spectrum efficiency three metrics that translate into subscriber satisfaction and churn reduction for service providers. This guide provides a technical framework for evaluating CA in CPE, with practical criteria that procurement teams, network planners, and system integrators can apply when comparing products.

What Carrier Aggregation Actually Does

Carrier aggregation combines multiple component carriers discrete blocks of licensed spectrum into a single logical data pipe. In LTE-Advanced, CA was introduced in 3GPP Release 10 and initially supported aggregation of up to five component carriers (5CA), each up to 20 MHz wide. In 5G NR, the concept expands significantly: a single component carrier can span up to 100 MHz in sub-6 GHz (Frequency Range 1) or up to 400 MHz in mmWave (Frequency Range 2), and aggregation can combine carriers across both frequency ranges.

The throughput math is straightforward in principle. Aggregate two 20 MHz LTE carriers with 256QAM modulation and 4×4 MIMO, and you approach a theoretical peak of 400 Mbps downlink double what a single carrier can deliver. In practice, field conditions, backhaul constraints, and interference reduce these numbers, which is why understanding real-world CA behavior is essential for procurement decisions.

CA Class Ratings: What the Numbers Mean

Datasheets commonly list CA capability in shorthand that buyers should learn to decode:

• LTE Cat 4: No carrier aggregation. Single carrier, up to 150 Mbps DL. Suitable for basic M2M and low-bandwidth IoT applications not recommended for residential or enterprise broadband CPE.
• LTE Cat 6 / Cat 7: 2CA (two-carrier aggregation). Up to 300 Mbps DL. The baseline for acceptable fixed wireless access (FWA) in suburban and rural deployments where spectrum holdings are limited to two bands.
• LTE Cat 12 / Cat 13: 3CA, up to 600 Mbps DL. A solid mid-tier option that aggregates three carriers typically combining low-band for coverage with mid-band for capacity.
• LTE Cat 16 / Cat 18: 3CA to 5CA, up to 1.2 Gbps DL. These devices support 4×4 MIMO on multiple carriers and 256QAM, making them suitable for high-demand FWA services where LTE spectrum depth is available.
• LTE Cat 20: Up to 5CA, 2 Gbps DL theoretical. The highest LTE CA tier, often deployed in markets where 5G NR rollout is still underway but capacity demand is high.

For 5G NR CPE, CA capability descriptions are more nuanced. A device labeled NR CA: 2CC means it can aggregate two 5G NR carriers. Combined with LTE-NR Dual Connectivity (EN-DC) which aggregates LTE and NR carriers simultaneously a modern CPE might support configurations like LTE 4CA + NR 2CA, achieving multi-gigabit peak rates.

Evaluating CA Beyond the Spec Sheet

Datasheet numbers reflect controlled lab conditions. For procurement decisions, buyers should evaluate CA performance across four additional dimensions:

1. Band Combination Support. A CPE may support 5CA in theory, but the specific band combinations it can aggregate are what matter in the field. For example, a European operator with spectrum in B1 (2100 MHz), B3 (1800 MHz), B7 (2600 MHz), B20 (800 MHz), and n78 (3500 MHz) needs a CPE whose CA engine can combine those specific bands in the exact permutations required by the network carrier aggregation policy. Requesting the device supported CA band combination list (often documented in GCF/PTCRB certification reports) is a prudent due diligence step.

2. MIMO and Modulation per Carrier. Carrier aggregation throughput calculations assume each aggregated carrier achieves its peak spectral efficiency, which requires 4×4 MIMO and 256QAM (or higher) on each carrier. Some CPE devices support 4×4 MIMO only on the primary component carrier (PCC) and fall back to 2×2 MIMO on secondary component carriers (SCCs), reducing aggregate throughput by 15-30% under good signal conditions.

3. Inter-Band vs. Intra-Band CA. Intra-band contiguous CA aggregating adjacent carriers within the same frequency band is easier to implement and typically performs better than inter-band CA, which aggregates carriers from different bands. However, real-world spectrum holdings are often fragmented across bands, making inter-band CA support a critical requirement for many operators. CPE that supports inter-band CA with a wide set of band combinations provides better deployment flexibility.

4. Carrier Aggregation at Cell Edge. The most valuable CA performance gain occurs at the cell edge, where aggregating a low-band carrier (e.g., 700-800 MHz for coverage) with a mid-band carrier (e.g., 1800-2600 MHz for capacity) can deliver meaningful throughput improvements compared to a single-carrier configuration. Buyers evaluating CPE for rural or suburban deployments should prioritize devices with strong low-band + mid-band inter-band CA support.

Six-Point Evaluation Checklist for CA-Capable CPE

1. Verify the CA tier against your spectrum holdings. Match the device maximum CA configuration (e.g., 3CA, 5CA, NR 2CC) with the number of carriers your network can actually provide in target deployment areas.
2. Request the supported band combination list. Confirm that the device can aggregate your specific band combinations not just the bands individually. A CPE that supports B3, B7, and n78 separately does not necessarily support B3+B7+n78 aggregation.
3. Check MIMO support per carrier. Ensure that 4×4 MIMO is supported on secondary component carriers, not just the primary carrier. This detail is often omitted from summary datasheets but significantly impacts aggregate throughput.
4. Evaluate CA fallback behavior. Test or inquire about how the device behaves when a secondary carrier drops (e.g., during mobility or interference). A well-engineered CPE should seamlessly fall back to fewer carriers without service interruption or excessive throughput oscillation.
5. Review real-world throughput test data. Request field test results or third-party benchmarking data showing throughput distribution (not just peak rates) across a range of signal conditions relevant to your deployment.
6. Confirm management plane support. Ensure the CPE supports remote monitoring of per-carrier RSRP, RSRQ, and SINR via TR-069 or TR-369, enabling operators to optimize CA configurations across their device fleet.

The Trade-Off: CA Complexity vs. Cost

Higher CA tiers require more RF front-end components, additional antennas, and more powerful baseband processing all of which increase bill of materials (BOM) cost. A Cat 20 CPE with 5CA and 4×4 MIMO on multiple carriers may cost 40-60% more than a Cat 6 2CA device. For procurement teams, the key is matching CA capability to actual network requirements rather than buying the highest specification available. A Cat 12 3CA device may deliver 90% of the user experience of a Cat 20 5CA device in a network that only operates three carriers per sector making the extra investment in a higher CA tier a marginal gain at best.

Frequently Asked Questions

Q: Does carrier aggregation work the same way in 4G and 5G?
A: The principle is the same combining multiple carriers for higher throughput but the implementation differs. LTE CA aggregates carriers up to 20 MHz each, while 5G NR CA can aggregate carriers up to 100 MHz (sub-6 GHz) or 400 MHz (mmWave). Additionally, 5G supports EN-DC (E-UTRAN New Radio Dual Connectivity), which aggregates LTE and NR carriers simultaneously, providing a transitional path as networks migrate from NSA to SA architecture.

Q: How can I verify a CPE actual CA performance before bulk procurement?
A: Conduct field trials with engineering samples in target deployment environments. Measure throughput under multiple signal conditions (near-cell, mid-cell, cell-edge) and verify that all expected component carriers are actively aggregated by checking the device CA status reporting. Request GCF/PTCRB certification documents that confirm the supported CA combinations have passed conformance testing.

Q: Is higher CA always better for fixed wireless access deployments?
A: Not necessarily. For FWA deployments where the CPE is stationary, antenna placement can be optimized, and signal conditions are relatively stable, even 2CA or 3CA configurations can deliver excellent performance. The incremental benefit of moving from 3CA to 5CA is often modest in real-world conditions and should be weighed against the higher device cost.

---

Need help selecting the right CA-capable CPE for your network? Honlly Telecom engineering team provides detailed RF performance data, supported CA band combination matrices, and sample devices for field evaluation. Contact us to discuss your procurement requirements.

For telecom operators managing thousands—or hundreds of thousands—of customer premises equipment (CPE) devices, the device management protocol is not a technical footnote. It determines provisioning speed, diagnostic capability, firmware update reliability, and ultimately, operational cost per subscriber. The Broadband Forum’s TR-369 User Services Platform (USP) is the designated successor to the aging TR-069 (CWMP) protocol, and its adoption is accelerating across carrier-grade CPE deployments worldwide.

This guide provides a practical overview of TR-369 USP: what it does, why it matters, how to plan a migration from TR-069, and what procurement teams should verify when sourcing USP-compatible CPE.

What Is TR-369 USP and Why Is It Replacing TR-069?

TR-069 (CPE WAN Management Protocol, or CWMP) has been the workhorse of broadband CPE management since 2004. It enabled auto-configuration servers (ACS) to provision, monitor, and update CPE remotely. However, TR-069 was designed in an era of DSL modems and simple NAT routers. It struggles with modern deployment realities: multi-WAN CPE, mesh Wi-Fi systems, IoT gateways, containerized applications on CPE, and the low-latency telemetry that operators now expect.

TR-369 USP, first published in 2018 and now at version 1.3 (2023), addresses these limitations with a fundamentally modern architecture:

• REST/WebSocket-based messaging instead of SOAP/HTTP. This reduces overhead, supports real-time push notifications, and integrates naturally with cloud-native operator OSS/BSS stacks.
• Multi-controller support. A single CPE can be managed simultaneously by multiple controllers—for example, the operator’s ACS for provisioning, a separate analytics platform for telemetry, and an end-user mobile app for Wi-Fi optimization.
• Data model based on TR-181. USP reuses and extends the mature TR-181 Device Data Model (also used by TR-069), so operators can map existing parameter paths. But USP adds new objects for Wi-Fi 6/7, 5G NR, IoT sensors, and virtualized network functions.
• End-to-end security with TLS 1.3 and mutual certificate authentication. USP mandates encrypted transport and device-to-controller certificates, eliminating the plaintext HTTP provisioning vectors that vexed TR-069 deployments.
• Bulk data collection with USP’s “Trusted Broker” and “Subscription” mechanisms. Operators can define periodic telemetry subscriptions—for signal strength, throughput, and Wi-Fi channel utilization—without polling each device individually.

USP Architecture: Controllers, Agents, and the Message Transfer Protocol

USP defines a clean separation between three components:

1. USP Agent — embedded in the CPE firmware. Exposes the device’s data model (TR-181 objects) and executes commands from controllers.

2. USP Controller — the operator-side management system (ACS replacement). Sends commands, creates subscriptions, and processes notifications.

3. MTP (Message Transfer Protocol) — the transport layer. The primary binding is WebSocket with TLS 1.3, but USP also supports MQTT and CoAP bindings for constrained IoT devices—a flexibility TR-069 never offered.

This architecture enables a critical operational improvement: always-on connectivity. In TR-069, the ACS could only reach the CPE when the device initiated a session (typically via periodic inform messages). In USP, the WebSocket connection is persistent, allowing the controller to push commands instantly—vital for time-sensitive operations like firmware security patches or QoE remediation.

Checklist: What Operators Should Verify When Procuring USP-Compatible CPE

Not all CPE marketed as “USP-compatible” delivers the full operational benefit. Procurement teams should validate the following before committing to large-volume orders:

Verification Item	Why It Matters	How to Test
USP Agent version (≥1.2)	Version 1.2+ supports bulk data, trusted broker, and firmware management improvements	Request GetInstances on Device.LocalAgent.Controller.
WebSocket MTP with TLS 1.3	Mandatory for persistent connectivity; older MQTT-only implementations limit real-time control	Attempt WebSocket connection from controller to agent endpoint; verify TLS cert chain
TR-181 data model coverage (Device.WiFi., Device.Cellular., Device.Bridging.)	Full coverage enables Wi-Fi optimization, cellular signal monitoring, and VLAN configuration	Run GetSupportedDM to enumerate exposed objects; compare against TR-181 spec
Multi-controller registration	Enables concurrent management by operator ACS + end-user app + analytics platform	Register two controllers with different credentials; verify both can query
Firmware update with USP (DUStateChangeNotif)	USP-native firmware management is more reliable than TR-069 download methods	Push a test firmware image via USP; verify download, validation, and install notification
Subscription/Notify mechanism	Push-based telemetry eliminates polling overhead; critical for QoE monitoring at scale	Create a subscription for Device.Cellular.SignalStrength; verify periodic value-changed notifications

TR-069 to TR-369 Migration: A Phased Approach

Most operators cannot flip a switch and replace TR-069 overnight. A practical migration follows three phases:

Phase 1 — Dual-stack deployment (months 1–6). Deploy new CPE with both TR-069 and USP agents running. The existing ACS continues to manage day-to-day operations, while the USP controller is validated against a subset of devices for provisioning, telemetry, and firmware management. This is the lowest-risk entry point.

Phase 2 — Controller cutover (months 6–12). Once the USP controller has been validated against all critical workflows, begin routing new device activations exclusively through USP. Existing devices remain on TR-069 or dual-stack until natural hardware refresh occurs.

Phase 3 — TR-069 deprecation (months 12–24). As the installed base refreshes, the TR-069 ACS can be scaled down and eventually decommissioned. USP-native capabilities—bulk telemetry, multi-controller support, application lifecycle management—become the operational baseline.

Why USP Matters for the CPE Supply Chain

For distributors and system integrators, TR-369 compliance is becoming a hard requirement in operator RFPs—particularly in Europe, where Deutsche Telekom, BT Group, and Orange have all published USP roadmap requirements for CPE vendors. In North America, the Broadband Forum’s BBF.369 certification program is driving similar momentum. CPE models that lack USP support will face increasing procurement barriers in carrier tenders from 2026 onward.

When evaluating OEM/ODM partners, verify that the manufacturer has completed USP Agent implementation with a Broadband Forum-recognized test tool (such as the USP Agent Conformance Test or CDRouter USP), and that their roadmap includes support for upcoming USP 1.4 features, including enhanced IoT proxy capabilities and application container management.

Frequently Asked Questions

What is the difference between TR-069 and TR-369 USP?

TR-069 (CWMP) uses SOAP/HTTP for periodic device polling through an ACS. TR-369 USP uses REST/WebSocket for persistent, real-time bidirectional communication. USP supports multi-controller management, bulk data subscriptions, and modern encryption (TLS 1.3), while TR-069 is limited to a single ACS controller with periodic inform-based communication. USP also extends the TR-181 data model to cover Wi-Fi 6/7, 5G NR, and IoT functions that TR-069 cannot represent.

Does USP work with existing TR-069 ACS platforms?

No. USP requires a dedicated USP Controller, not a TR-069 ACS. However, many modern device management platforms (including those from Axiros, Friendly Technologies, and Incognito) now offer dual-protocol support, managing both TR-069 and USP devices from a single administrative interface. This dual-protocol capability is essential for operators managing a mixed installed base during migration.

Is USP mandatory for 5G FWA CPE?

USP is not a 3GPP requirement for 5G, but it is increasingly specified in operator procurement RFPs for 5G FWA CPE, particularly in Europe and parts of Asia-Pacific. The protocol’s ability to handle multi-WAN scenarios (cellular + fixed backup) and real-time signal quality telemetry makes it well-suited for 5G FWA management. Some operators accept TR-069 for initial deployments but require a USP roadmap within 12–18 months.

How does USP handle firmware upgrades at scale?

USP uses the DUStateChangeNotif (Download Update State Change Notification) mechanism for firmware management. The controller can push firmware images to device groups, monitor download progress in real time via WebSocket notifications, verify image integrity before installation, and schedule installations during maintenance windows. This is more reliable than TR-069’s download methods, which often relied on the device periodically polling for available updates.

Can USP manage non-Broadband CPE like industrial routers and IoT gateways?

Yes. USP’s flexible data model and MTP options (WebSocket, MQTT, CoAP) make it suitable for industrial routers, IoT gateways, and even constrained sensor devices. The protocol’s subscription mechanism is particularly valuable for industrial use cases where periodic sensor readings or equipment status updates need to flow to a central management platform without constant polling.

Plan Your TR-369 USP CPE Deployment

Honlly Telecom’s carrier-grade 4G/5G CPE and industrial routers support TR-369 USP alongside TR-069 for seamless migration. Our engineering team can provide USP Agent conformance test reports, data model coverage documentation, and integration support for your operator management platform. Contact us to discuss your USP CPE requirements and request a test sample.