Author: openclaw-Lisa-New

  • Global MVNO Market Surpasses $100 Billion Valuation in 2026: CPE Customization Requirements for Virtual Network Operators Scaling Enterprise Services

    Global MVNO Market Surpasses $100 Billion Valuation in 2026: CPE Customization Requirements for Virtual Network Operators Scaling Enterprise Services

    The global Mobile Virtual Network Operator (MVNO) market has crossed the $100 billion valuation threshold in 2026, driven by enterprise digital transformation, IoT connectivity demand, and the expanding 5G wholesale access market. For CPE manufacturers, this milestone signals a fundamental shift in device requirements: MVNOs need customizable, brand-ready customer premises equipment that can be rapidly deployed across multiple host operator networks.

    The MVNO Growth Trajectory: $100B and Accelerating

    According to GSMA Intelligence and multiple industry analyst reports, the global MVNO market reached an estimated $102 billion in revenue during the first half of 2026, with a compound annual growth rate exceeding 8.5% since 2023. Key growth drivers include:

    • Enterprise MVNOs: Large corporations launching private-branded mobile services for employees and IoT fleets, requiring customized CPE with enterprise-grade management features.
    • IoT-Focused MVNOs: Specialized operators serving smart metering, fleet telematics, and industrial sensor networks, demanding ruggedized routers with low-power wide-area connectivity.
    • 5G Wholesale Expansion: MNOs increasingly opening 5G Standalone (SA) cores to MVNO partners, enabling differentiated network slicing and QoS-tiered CPE offerings.
    • Regulatory Support: Markets including the EU, Southeast Asia, and Latin America continue mandating MVNO access as a competition-enhancing measure.

    CPE Implications: What MVNO Buyers Need from Device Suppliers

    Unlike traditional MNOs that order CPE in standardized, carrier-branded configurations, MVNOs present distinct device requirements that CPE manufacturers must address:

    1. Multi-IMSI and Multi-PLMN Support

    MVNOs frequently operate across multiple host networks and geographies. CPE must support multi-IMSI profiles — ideally with eSIM/eUICC capability — allowing devices to switch between host operator profiles based on coverage, cost, or service-level agreements. This requires modem firmware flexibility and GSMA SGP.02/SGP.22 compliant eSIM architectures.

    2. White-Label Branding and Customizable UI

    MVNOs sell under their own brand identity, not the host MNO’s. CPE must support white-label device firmware with customizable web UI branding, logo placement, SSID defaults, and packaging design. Manufacturers offering OEM/ODM flexibility with low minimum order quantities for branded firmware gain significant competitive advantage in the MVNO segment.

    3. Remote Provisioning and Zero-Touch Deployment

    MVNOs typically lack the field engineering resources of MNOs. CPE must support TR-069/TR-369 auto-configuration server (ACS) integration, allowing subscriber devices to be provisioned remotely upon first power-on. Zero-touch onboarding reduces operational costs and subscriber churn — critical metrics for margin-sensitive MVNOs.

    4. Flexible APN and PDP Context Configuration

    MVNOs often use their own Access Point Name (APN) configurations that route traffic through MVNO core network elements before reaching the host MNO’s packet gateway. CPE must support multiple APN profiles, dynamic PDP context activation, and VLAN tagging for service differentiation — features that enable MVNOs to offer tiered data plans and managed SD-WAN services.

    5. Cost-Optimized Hardware Platforms

    MVNOs operate on thinner margins than facility-based operators. CPE hardware must balance performance with aggressive BOM cost targets. Cat-4 and Cat-6 LTE platforms remain dominant in MVNO deployments, with Cat-12 gaining traction in markets where 5G wholesale access remains cost-prohibitive. Modular RF design — allowing the same enclosure to serve 4G and 5G variants — is increasingly valued.

    Regional Hotspots for MVNO CPE Demand

    • Europe: Mature MVNO ecosystem; eSIM-capable CPE demand driven by cross-border IoT and roaming-intensive enterprise services.
    • Southeast Asia: Rapidly growing MVNO segment in Indonesia, Philippines, and Thailand; demand for affordable LTE Cat-4/Cat-6 fixed wireless CPE.
    • Latin America: Regulatory-driven MVNO expansion in Brazil and Mexico; need for multi-band LTE routers supporting regional frequency bands (B2, B4, B5, B7, B28).
    • Middle East & Africa: MVNOs serving migrant communities and enterprise connectivity; demand for portable MiFi and desktop CPE with long battery life.

    Strategic Outlook for CPE Manufacturers

    The MVNO segment represents a high-volume, recurring-revenue opportunity for CPE suppliers. To capture this market, manufacturers should invest in: flexible firmware platforms supporting multi-tenant branding, eSIM-ready hardware designs, simplified TR-069/TR-369 provisioning profiles, and SKU rationalization that serves both MNO and MVNO requirements from common hardware platforms. As 5G SA wholesale access matures through 2027-2028, MVNOs will increasingly demand 5G CPE with network slicing awareness — a capability that early-moving manufacturers can build into their product roadmaps today.

    Frequently Asked Questions

    What types of CPE do MVNOs typically purchase?

    MVNOs primarily purchase LTE Cat-4 and Cat-6 fixed wireless CPE, portable MiFi devices, and USB dongles. Enterprise-focused MVNOs also procure industrial-grade routers with multi-WAN failover. The common requirement across all categories is support for multiple host operator profiles and remote device management.

    How does MVNO CPE differ from standard MNO CPE?

    The key differences are: white-label branding capability, multi-IMSI/eSIM support for host operator switching, simplified zero-touch provisioning, and cost-optimized hardware designs. MVNOs also require more flexible APN and data routing configurations than single-operator MNOs.

    What is the minimum order quantity for MVNO-branded CPE?

    Minimum order quantities vary by manufacturer. Honlly Telecom offers flexible OEM/ODM programs with competitive MOQs for MVNO customers, including customized firmware branding and packaging. Contact our sales team for a project-specific quotation.

    Looking for MVNO-optimized CPE solutions? Contact Honlly Telecom to discuss your device requirements — from customized firmware to flexible order quantities. Get in touch with our team →

  • 5G FWA and WiFi 7: Installation Architecture

    5G FWA and WiFi 7: Installation Architecture

    The convergence of 5G Fixed Wireless Access and Wi-Fi 7 represents the most significant architectural shift in broadband CPE design since the introduction of integrated DOCSIS-Wi-Fi gateways. For operators deploying FWA services to multi-dwelling units (MDUs), enterprise campuses, and dense urban environments, the end-to-end interaction between the 5G WAN link and the Wi-Fi 7 indoor distribution layer determines whether subscribers experience the multi-gigabit performance that 5G-Advanced networks can deliver. This analysis examines the architectural considerations, trade-offs, and deployment strategies for converged 5G FWA + Wi-Fi 7 CPE platforms.

    The Bottleneck Problem: Why Wi-Fi 6E Is Not Enough for 5G-Advanced FWA

    5G-Advanced networks based on 3GPP Release 18 specifications are delivering peak downlink speeds of 5-8 Gbps in commercial FWA deployments, with 10 Gbps expected as carrier aggregation configurations expand to 6-8 component carriers and 256-QAM modulation becomes standard on the downlink. However, the indoor distribution layer — traditionally a Wi-Fi 6E access point operating in 160 MHz channels with 1024-QAM — caps per-client throughput at approximately 1.2-1.8 Gbps under ideal conditions. For a single-user scenario where the subscriber’s primary device needs to access the full WAN capacity, Wi-Fi 6E becomes the binding constraint.

    For a proposed WiFi 7 access network, confirm supported features on both the gateway and client devices, the locally available spectrum and the installation layout. Test end-to-end throughput with the selected equipment instead of assuming the local radio matches the WAN rate.

    Architectural Models for Converged 5G FWA + Wi-Fi 7 CPE

    Model 1: Integrated Single-Box CPE

    An integrated gateway places cellular, local WiFi and Ethernet functions in one enclosure. Compare that arrangement with separate outdoor and indoor units against mounting, power, coverage and servicing requirements.

    Advantages: Lowest BOM cost, simplest installation (single power supply, single device to provision), unified device management via TR-369 USP or TR-069, and simplified subscriber support. The integrated thermal design can share heatsink and ventilation resources between the 5G modem and Wi-Fi 7 subsystems.

    Disadvantages: Fixed physical placement — the optimal location for 5G reception (typically near a window with line-of-sight to the gNodeB) may not be the optimal location for Wi-Fi coverage (typically central to the living or working space). Single-box designs also face thermal density challenges, with combined modem + Wi-Fi 7 power consumption reaching 35-45W in premium implementations, requiring active cooling in some form factors.

    Model 2: Split Architecture (Outdoor CPE + Indoor Wi-Fi 7 Unit)

    The split architecture places the 5G modem and high-gain directional antenna in an outdoor unit (ODU), typically IP67-rated and pole or wall-mounted, connected to an indoor Wi-Fi 7 unit via Power over Ethernet (PoE) or fiber. This architecture is increasingly specified for MDU and enterprise FWA deployments where outdoor antenna placement significantly improves 5G signal quality.

    Advantages: The ODU can be placed at the optimal 5G reception point (rooftop, balcony, exterior wall) while the Wi-Fi 7 indoor unit can be centrally located for optimal coverage. Outdoor antenna placement typically improves RSRP by 8-15 dB and SINR by 5-10 dB compared to indoor antenna placement — a difference that can translate to 2-4x throughput improvement in cell-edge scenarios. Thermal design is simplified as the 5G modem and Wi-Fi 7 subsystem have separate thermal budgets.

    Disadvantages: Higher total solution cost (two enclosures, two power subsystems, interconnect cable), more complex installation requiring external cable routing, and additional points of potential failure. The interconnect between ODU and indoor unit becomes a new specification requirement: operators must ensure adequate bandwidth (typically 2.5G or 5G Ethernet, or 10G SFP+ for future-proofing) and power delivery.

    Model 3: Distributed Mesh Architecture

    For larger MDU and enterprise deployments, a distributed mesh architecture uses a primary 5G FWA gateway (which may be outdoor-mounted) feeding multiple Wi-Fi 7 mesh nodes throughout the premises via wired or wireless backhaul. This architecture is gaining traction for garden-style MDU complexes, multi-floor enterprise offices, and hospitality deployments where a single Wi-Fi 7 access point cannot provide adequate coverage.

    Advantages: Scalable coverage — additional mesh nodes can be added to eliminate dead zones without replacing the primary gateway. Wi-Fi 7’s MLO capability significantly improves mesh backhaul performance compared to Wi-Fi 6E mesh systems, with STR-MLO enabling simultaneous 5 GHz front-haul and 6 GHz backhaul operation without time-sharing penalties.

    A mesh design adds backhaul and placement considerations. Test the planned node locations, client load, coverage and recovery behaviour with the selected system before agreeing performance criteria.

    Key Engineering Considerations for Converged Deployments

    Thermal Design in High-Density Enclosures

    Review the complete device power and thermal specification under the intended load and ambient conditions. Ask for sustained-operation tests for the ordered configuration rather than applying an assumed percentage of throttling.

    Best practices for thermal management in converged CPE include: die-cast aluminum enclosures with integrated heatsink fins rather than plastic enclosures with internal heatsinks; vertical orientation for natural convection; separation of 5G modem and Wi-Fi 7 thermal zones with thermal barriers to prevent heat migration; and, for premium outdoor/indoor split architectures, separate thermal budgets for ODU and indoor unit.

    WAN-to-LAN Data Path Optimization

    The internal data path between the 5G modem and the Wi-Fi 7 subsystem must be engineered to avoid introducing a new bottleneck. Key considerations:

    • PCIe lane allocation: PCIe Gen3 x2 (approximately 1.9 GB/s effective) is sufficient for current 5G-Advanced peak rates. For future-proofing against 10+ Gbps 5G WAN speeds, specify PCIe Gen4 x2 or Gen3 x4 interfaces.
    • Hardware flow control and QoS mapping: The CPE should map 5G QoS flows (5QI values) to Wi-Fi 7 QoS mechanisms (802.11be TID-to-link mapping) to ensure end-to-end quality of service. Voice and video flows from the 5G network should maintain priority through the Wi-Fi distribution layer.
    • Buffer management: Adequate packet buffer memory (typically 512 MB to 1 GB DDR4 for premium CPE) prevents bufferbloat and maintains low latency under concurrent high-throughput and latency-sensitive traffic scenarios.

    Antenna Coexistence: 5G and Wi-Fi 7 in the Same Enclosure

    In integrated single-box CPE, the proximity of 5G antennas (operating at 600 MHz to 6 GHz for sub-7 GHz 5G bands, or 24-47 GHz for mmWave) and Wi-Fi 7 antennas (operating at 2.4 GHz, 5 GHz, and 6 GHz) creates significant coexistence challenges. Without adequate isolation, 5G transmission can desensitize Wi-Fi receivers, and vice versa, leading to throughput degradation on both links.

    Key coexistence strategies include: physical antenna separation of at least 50-70 mm between 5G and Wi-Fi antenna elements; polarization diversity (using orthogonal polarizations for 5G and Wi-Fi antennas); frequency-domain filtering with high-Q bandpass filters on both 5G and Wi-Fi RF paths; and time-domain coexistence coordination through the SoC’s shared coexistence manager — a feature increasingly integrated into platforms from both Qualcomm and MediaTek.

    Deployment Scenarios and Architecture Recommendations

    Single-Family Residential FWA: Integrated single-box CPE with STR-MLO Wi-Fi 7 is the optimal architecture. The subscriber expects a simple, self-installable device. Window or wall placement near the optimal 5G reception point is typically acceptable for indoor Wi-Fi coverage in apartments and small homes. Operators should include a companion smartphone app for optimal placement guidance using real-time RSRP and SINR readings.

    MDU (Apartment Buildings): Split architecture with rooftop or balcony-mounted ODU and central indoor Wi-Fi 7 unit is recommended. For buildings with 4-8 units, a single ODU serving a Wi-Fi 7 mesh system distributed across common areas or individual units via Ethernet backhaul provides the best cost-performance ratio. The ODU should support carrier aggregation across all available 5G bands to maximize backhaul capacity for multi-tenant scenarios.

    Enterprise/SME Deployment: Distributed mesh architecture with outdoor 5G modem as primary WAN, optionally combined with wireline failover (fiber or DOCSIS) in a multi-WAN configuration. Wi-Fi 7 mesh nodes with wired Ethernet backhaul where structured cabling exists, wireless mesh backhaul for legacy buildings. The CPE platform must support enterprise-grade features including VLAN segmentation, RADIUS authentication, and centralized management via TR-369 USP.

    The Path Forward: Wi-Fi 7 as the Universal Indoor Distribution Layer

    As 5G-Advanced FWA deployments scale through 2026-2027 and the first 6G FWA trials begin in 2028-2029, Wi-Fi 7 is positioned to become the universal indoor distribution layer for all fixed broadband access technologies — FWA, fiber, cable, and satellite. The architectural decisions operators make today in specifying converged 5G FWA + Wi-Fi 7 CPE platforms will define subscriber quality of experience for the next 5-7 years.

    For procurement teams, the key strategic principle is straightforward: the indoor Wi-Fi layer should never be the bottleneck. With Wi-Fi 7 silicon now price-competitive and carrier-certified platforms available from established ODMs, there is no technical or economic justification for deploying 5G-Advanced FWA services behind anything less than a Wi-Fi 7 indoor distribution layer.


    Frequently Asked Questions

    What is the optimal CPE architecture for 5G FWA + Wi-Fi 7 convergence?

    The optimal architecture depends on the deployment scenario. Single-family residential FWA is best served by integrated single-box CPE. MDU and enterprise deployments benefit from split architecture (outdoor 5G modem + indoor Wi-Fi 7 unit) which optimizes both 5G reception and Wi-Fi coverage. Large enterprise deployments may require distributed mesh with multiple Wi-Fi 7 nodes.

    Does Wi-Fi 7 eliminate the indoor bottleneck for 5G FWA?

    Yes, for all current and near-term 5G-Advanced FWA deployments. A triband Wi-Fi 7 CPE with STR-MLO can deliver 4.5-5.2 Gbps to a single client, matching or exceeding the peak downlink capacity of current 5G-Advanced networks. Wi-Fi 7’s theoretical maximum of 46 Gbps provides headroom for future 5G and 6G FWA evolution.

    What are the thermal challenges of integrated 5G + Wi-Fi 7 CPE?

    Confirm the ordered enclosure, operating limits and cooling arrangement. Test sustained traffic at representative ambient conditions before approving installation.

    How does outdoor 5G antenna placement improve FWA + Wi-Fi 7 performance?

    Outdoor antenna placement typically improves 5G RSRP by 8-15 dB and SINR by 5-10 dB compared to indoor placement. Combined with centralized Wi-Fi 7 indoor unit placement, split architecture can deliver 2-4x total end-to-end throughput improvement in cell-edge FWA scenarios compared to integrated single-box CPE.


    Deploying 5G FWA with Wi-Fi 7 for your subscriber base? Honlly Telecom offers integrated and split-architecture 5G FWA + Wi-Fi 7 CPE solutions with STR-MLO, outdoor ODU options, and full TR-369 USP device management. Contact our engineering team to discuss your convergence architecture requirements and schedule a technical consultation.

  • A Telecom Operator’s Guide to Wi-Fi 7 CPE Specifications: Evaluating Multi-Link Operation, 320 MHz Channels, and 4K-QAM for Next-Generation Gateways

    A Telecom Operator’s Guide to Wi-Fi 7 CPE Specifications: Evaluating Multi-Link Operation, 320 MHz Channels, and 4K-QAM for Next-Generation Gateways

    As telecom operators and ISPs plan their next-generation CPE procurement cycles, Wi-Fi 7 (IEEE 802.11be) has moved from an emerging technology to a deployment-ready standard. With silicon shipments tripling in H1 2026 and Tier-1 operators across Europe and North America actively deploying Wi-Fi 7 gateways, the procurement question has shifted from “if” to “how.” This guide provides a structured framework for evaluating Wi-Fi 7 CPE specifications, helping procurement teams and network engineering departments make informed vendor selection decisions.

    1. Multi-Link Operation (MLO): The Architecture Decision That Defines Performance

    Multi-Link Operation is the signature feature of Wi-Fi 7 and the single most important specification to evaluate when comparing CPE platforms. However, not all MLO implementations are equal. Operators must understand the architectural trade-offs between different MLO modes.

    MLO Modes: STR vs. NSTR vs. EMLSR

    Simultaneous Transmit and Receive (STR-MLO) represents the highest-performance MLO implementation, where the CPE can simultaneously transmit and receive on multiple frequency bands without any scheduling constraints. STR-MLO requires independent RF chains per band and is typically found in premium triband (2.4 GHz + 5 GHz + 6 GHz) CPE platforms based on Qualcomm Networking Pro 1620 or Broadcom BCM6765 silicon. STR-MLO delivers the full throughput aggregation and latency reduction benefits of Wi-Fi 7, with typical operator lab results showing 4.8-5.2 Gbps aggregate throughput under realistic multi-client conditions.

    Non-Simultaneous Transmit and Receive (NSTR-MLO) is a lower-cost implementation where the CPE can receive on multiple links simultaneously but can only transmit on one link at a time. NSTR-MLO is common in dual-band (5 GHz + 6 GHz) CPE designs using MediaTek Filogic 380 or entry-level Qualcomm platforms. While NSTR-MLO still provides latency benefits through redundant link availability, aggregate throughput gains are limited to approximately 15-25% over equivalent single-link operation.

    Enhanced Multi-Link Single Radio (EMLSR) is a transitional implementation where a single radio dynamically switches between bands. EMLSR provides the reliability benefits of multi-link operation without the cost of multiple RF chains, but throughput is limited to single-link performance. This mode is primarily found in cost-optimized CPE targeting emerging markets.

    Procurement Recommendation: For carrier-grade FWA and fiber gateways serving premium subscriber tiers, specify STR-MLO capability as a mandatory requirement. For mid-tier and entry-level CPE, NSTR-MLO represents a reasonable cost-performance balance. EMLSR-only implementations should be limited to ultra-low-cost segments where Wi-Fi 6E represents the primary competitive alternative.

    2. Channel Bandwidth: 320 MHz Support and Spectrum Strategy

    Wi-Fi 7 doubles the maximum channel bandwidth from 160 MHz (Wi-Fi 6E) to 320 MHz, theoretically doubling peak throughput. However, the practical availability of 320 MHz channels varies significantly by regulatory domain and deployment scenario.

    In the 6 GHz band, 320 MHz channel operation requires access to the full 5925-7125 MHz range. In the United States, the FCC has made the entire 1200 MHz of 6 GHz spectrum available for unlicensed use, enabling three non-overlapping 320 MHz channels. In Europe, where only the lower 500 MHz (5925-6425 MHz) is currently available for unlicensed Wi-Fi under the European Commission’s harmonized framework, operators are limited to a single 320 MHz channel. The UK’s Ofcom and Germany’s BNetzA have both indicated potential expansion to the upper 6 GHz band (6425-7125 MHz) in 2027, but this remains uncertain for near-term CPE procurement decisions.

    Key Specification Questions for Vendors:

    • Does the CPE support 320 MHz channel operation in the target regulatory domain?
    • If 320 MHz operation is not available (e.g., European deployments limited to 5925-6425 MHz), can the CPE operate in 160+80 MHz or 240 MHz modes?
    • What is the AFC (Automated Frequency Coordination) implementation for 6 GHz standard-power operation, and has it been certified by the relevant regulatory body?

    3. 4K-QAM Modulation: Real-World Gains and SNR Requirements

    Wi-Fi 7 introduces 4096-QAM (4K-QAM) modulation, up from 1024-QAM in Wi-Fi 6/6E. This represents a 20% increase in theoretical data rate per spatial stream. However, 4K-QAM requires significantly higher signal-to-noise ratio (SNR) — approximately 35-36 dB compared to 30-31 dB for 1024-QAM — which limits its practical range to approximately 5-8 meters in typical indoor environments with consumer-grade antennas.

    For carrier CPE deployment, the pragmatic benefit of 4K-QAM is most pronounced in “same-room” scenarios where the CPE and client device are in close proximity — for example, an FWA CPE placed near a home office desk serving a single primary laptop. In multi-room deployments where the CPE serves clients through walls and floors, the SNR typically drops below the 4K-QAM threshold, and the modulation rate falls back to 1024-QAM or 256-QAM.

    Procurement Consideration: While 4K-QAM support is a checkbox requirement for most operator RFPs, procurement teams should not weight it heavily in vendor evaluation. The real-world throughput improvement from 4K-QAM in typical residential and SMB deployment scenarios is 5-10% at most. MLO implementation quality, antenna design, and RF front-end performance have far greater impact on end-user experience.

    4. Spatial Streams and Antenna Architecture

    Wi-Fi 7 CPE antenna configurations typically fall into three tiers that directly correlate with target subscriber segments:

    Triband 10-Stream (4×4 + 4×4 + 2×2): The premium configuration specified by European Tier-1 operators for high-end FWA gateways. Typically configured as 4×4 MIMO on 6 GHz, 4×4 MIMO on 5 GHz, and 2×2 MIMO on 2.4 GHz. This configuration maximizes MLO throughput and multi-client capacity but requires significant PCB real estate, antenna isolation engineering, and power budget (typically 25-30W for the Wi-Fi subsystem alone).

    Dual-Band 6-Stream (4×4 + 2×2 or 2×2 + 2×2 + 2×2): The mainstream configuration for mid-tier operator gateways. Provides good MLO performance at accessible price points, with platform cost approximately 40-50% below triband 10-stream designs.

    Dual-Band 4-Stream (2×2 + 2×2): Entry-level Wi-Fi 7 configuration suitable for cost-sensitive markets and SOHO deployments. While technically Wi-Fi 7 compliant, the limited spatial stream count constrains both MLO throughput and multi-user MIMO (MU-MIMO) capacity.

    5. Backhaul Interface and WAN Integration

    For FWA CPE, the integration between the 5G modem and the Wi-Fi 7 subsystem is architecturally critical. Key considerations include:

    Internal Interface Bandwidth: PCIe Gen3 x2 (8 GT/s, approximately 1.9 GB/s effective throughput) is sufficient for most 5G-Advanced FWA deployments with peak downlink speeds up to 5-7 Gbps. For future-proofing against 5G-Advanced Release 18 enhancements that may deliver 10+ Gbps, PCIe Gen4 x2 or USB 3.2 Gen2x2 interfaces should be specified.

    Integrated vs. Discrete Architecture: Integrated platforms combining the 5G modem and Wi-Fi 7 on a single SoC (e.g., Qualcomm’s upcoming “FWA Fusion” platform) can reduce BOM cost by 15-20% and simplify thermal design compared to discrete modem + Wi-Fi designs. However, discrete architectures offer greater flexibility for operators with multi-modem or multi-WAN requirements.

    6. Testing and Certification: Beyond the Datasheet

    Datasheet specifications tell only part of the story. For operator procurement, real-world testing under representative deployment conditions is essential. Key test scenarios should include:

    • Multi-client throughput under load: Test with 16-32 simultaneous clients representing a typical household or SMB deployment, measuring both aggregate throughput and per-client fairness.
    • MLO stability over time: Run sustained 24-hour throughput tests to verify MLO link stability — early Wi-Fi 7 implementations exhibited MLO link drops under thermal load that required firmware updates.
    • Interference coexistence: Test in environments with neighboring Wi-Fi 6/6E networks to verify that Wi-Fi 7 preamble puncturing and coordinated OFDMA scheduling work effectively.
    • 6 GHz AFC compliance: For standard-power 6 GHz operation, verify AFC geolocation database integration and automatic power reduction in protected-frequency scenarios.

    Procurement Checklist Summary

    When evaluating Wi-Fi 7 CPE for carrier deployment, operators should prioritize the following specifications in order of impact on subscriber experience:

    1. MLO implementation quality — STR-MLO for premium tiers, NSTR-MLO minimum for mid-tier
    2. Antenna and spatial stream configuration — Match to target deployment density and range requirements
    3. WAN backhaul interface bandwidth — Ensure no bottleneck between 5G modem and Wi-Fi subsystem
    4. 6 GHz regulatory compliance — Verify AFC and channel availability in target markets
    5. Thermal design robustness — Sustained throughput under thermal load, not just peak benchmarks

    By focusing on these architectural specifications rather than marketing-driven peak throughput numbers, operator procurement teams can select Wi-Fi 7 CPE platforms that deliver measurable improvements in subscriber quality of experience across real-world deployment conditions.


    Frequently Asked Questions

    What is the most important Wi-Fi 7 specification for carrier CPE?

    Multi-Link Operation (MLO) implementation quality is the single most impactful specification. STR-MLO with independent RF chains per band delivers 2-3x throughput improvement over Wi-Fi 6E under real-world multi-client conditions. Operators should prioritize MLO architecture over peak throughput numbers.

    How much more does Wi-Fi 7 CPE cost compared to Wi-Fi 6E?

    As of H1 2026, Wi-Fi 7 CPE platforms carry approximately 15-20% BOM cost premium over equivalent Wi-Fi 6E designs at volume. This gap is expected to narrow to 5-10% by 2027 as silicon volumes scale and reference designs mature. For new service launches, the performance improvement justifies the marginal cost increase.

    Do operators need 6 GHz spectrum access to deploy Wi-Fi 7 CPE?

    Wi-Fi 7 can operate on 2.4 GHz and 5 GHz bands without 6 GHz access, but the most impactful features — 320 MHz channels and STR-MLO across wide channel pairs — require 6 GHz spectrum. Operators in markets without 6 GHz availability should evaluate whether Wi-Fi 7’s 5 GHz-only benefits (4K-QAM, improved OFDMA) justify the upgrade from Wi-Fi 6E.

    What is AFC and why does it matter for Wi-Fi 7 CPE?

    Automated Frequency Coordination (AFC) is a spectrum management system required for standard-power (36 dBm EIRP) Wi-Fi 7 operation in the 6 GHz band. AFC queries a geo-location database to ensure Wi-Fi devices do not interfere with incumbent fixed microwave links. CPE must integrate AFC client functionality and obtain regulatory certification for each target market.


    Procuring Wi-Fi 7 CPE for your operator network? Honlly Telecom provides carrier-grade Wi-Fi 7 gateways with STR-MLO, triband 10-stream antenna architecture, and full AFC certification for European and North American markets. Contact our solutions team to discuss your Wi-Fi 7 CPE requirements and request engineering samples.

  • Wi-Fi 7 in CPE: MLO, Client Compatibility and Backhaul Testing

    Wi-Fi 7 in CPE: MLO, Client Compatibility and Backhaul Testing

    When buying a Wi-Fi 7 gateway, ask how the proposed implementation will improve the customer’s actual connection. Silicon announcements and shipment forecasts do not show the performance of a complete CPE on the intended cellular service.

    Separate Wi-Fi capability from cellular speed

    The local Wi-Fi connection, wired interfaces and cellular backhaul form different parts of the path. A Wi-Fi PHY rate is not an internet-service speed. Test each segment and the complete connection with the intended clients before interpreting a result.

    Define the MLO requirement

    Multi-Link Operation is a Wi-Fi 7 capability. Confirm the modes, radio configuration and client combinations supported by the exact gateway build. A Wi-Fi 7 label alone does not specify every implementation option. Check applicable regional spectrum rules before planning use of a frequency range.

    Choose representative client devices

    Prepare a mix of current customer devices, including clients that use earlier Wi-Fi generations. Record driver versions, security settings and placement. Compare link establishment, roaming where relevant, latency under load and recovery after an interruption. Test the service experience as well as a short peak-rate benchmark.

    Measure the actual bottleneck

    1. Establish local wired and wireless baselines with suitable test equipment.
    2. Measure the cellular or other upstream service separately.
    3. Run the intended household or enterprise workload through the full gateway.
    4. Repeat with representative interference and distance conditions.
    5. Record active links and device telemetry where available so the result can be reproduced.

    Procurement evidence to request

    Ask for supported bands, radio configuration, wired-interface rates, enabled MLO modes, applicable certification evidence and firmware support. Record the exact SKU. Neither the HL-850UE’s WiFi 6 AX1800 specification nor a portfolio-wide marketing statement should be relabelled Wi-Fi 7.

    The earlier article’s numerical shipment-growth and market-share claims were not accompanied by verifiable report references. This guide focuses on testable product requirements instead. Use independently sourced, dated market reports if shipment analysis is needed.

    Related product and planning resources

    Sources and further reading

  • TR-369 User Services Platform Gains Traction in 2026 Carrier CPE Deployments: The Transition Away from TR-069 for Next-Generation Device Management

    TR-369 User Services Platform Gains Traction in 2026 Carrier CPE Deployments: The Transition Away from TR-069 for Next-Generation Device Management

    The Broadband Forum’s TR-369 User Services Platform (USP) is experiencing its steepest adoption curve to date in 2026, as telecommunications operators across Europe, North America, and Asia-Pacific accelerate their migration away from the aging TR-069 (CWMP) protocol. With over 40 million USP-capable CPE devices now in active deployment globally, the industry is reaching a decisive inflection point in device management architecture.

    TR-069 served the broadband industry capably for nearly two decades, providing basic provisioning, firmware updates, and diagnostics for residential gateways. But as operator networks evolve toward virtualized, multi-service, and AI-driven operations, CWMP’s limitations—synchronous request-response architecture, limited security model, and inability to support complex IoT and multi-tenant scenarios—have become untenable at scale.

    What Makes TR-369 Fundamentally Different

    TR-369 USP represents a complete architectural redesign rather than an incremental upgrade. Built around a microservices-oriented, event-driven architecture, USP uses a message bus paradigm where devices, controllers, and applications communicate asynchronously through a common data model derived from TR-181 Device:2. This enables operators to push configuration changes simultaneously across thousands of devices, receive real-time telemetry without polling, and implement zero-touch provisioning at wire speed.

    Key technical advantages over TR-069 include: native TLS 1.3 encryption with mutual certificate-based authentication; MQTT and WebSocket transport protocols replacing unreliable HTTP sessions; multi-controller support allowing a single CPE to be managed by both the operator and enterprise IT simultaneously; and a subscription-notification mechanism that eliminates the bandwidth overhead of periodic CWMP Inform messages.

    Carrier Adoption Milestones in 2026

    Several Tier-1 operators have made public commitments to full USP migration in 2026. Deutsche Telekom has mandated USP support in all new CPE procurement tenders for its European subsidiaries. BT Group’s Openreach network now requires USP compliance for any FTTP CPE connecting to its wholesale fiber platform. In North America, three major cable MSOs have begun USP field trials for their next-generation DOCSIS 4.0 gateways, targeting production deployment by Q4 2026.

    For CPE manufacturers, this shift carries significant implications. Devices must now support the full USP 1.3 agent specification, including the Software Module Management (SMM) service for containerized application deployment and the IoT data model extensions standardized in TR-181. Carriers are increasingly evaluating CPE vendors not just on radio performance and price, but on the maturity of their USP implementation—including certification status from BBF.067 compliance testing.

    Market Implications for CPE Procurement

    Industry analysts project that USP-capable CPE will account for 65% of all new carrier gateway shipments by 2027. The immediate procurement impact is twofold: operators must dual-stack their ACS (Auto Configuration Server) environments to support both TR-069 and TR-369 during the multi-year transition, while CPE manufacturers face increased software development costs to implement, test, and certify USP agents across their product lines.

    For operators still in the RFP stage for 5G FWA and next-gen broadband CPE, USP compliance should be a mandatory line item in technical specifications. The protocol’s support for bulk provisioning, real-time performance monitoring, and multi-tenancy directly influences operational OPEX and customer experience KPIs. Waiting until 2027 to mandate USP risks deploying a fleet of devices that will require costly software upgrades or premature replacement within 18-24 months.

    The TR-369 ecosystem continues to mature rapidly. Open-source USP agent implementations are now available from prpl Foundation and RDK-B, reducing integration barriers. Commercial ACS/controller platforms from Axiros, Friendly Technologies, and Incognito have all released production-grade USP support. The industry consensus at Broadband World Forum 2025 was unambiguous: TR-069 is in its final chapter, and the operators moving fastest on USP adoption will gain measurable operational advantages in device lifecycle management, security posture, and service agility.

    Frequently Asked Questions

    Q: What is TR-369 USP and how does it differ from TR-069?

    TR-369 User Services Platform (USP) is the Broadband Forum’s next-generation device management protocol that replaces TR-069 (CWMP). Unlike TR-069’s synchronous HTTP-based request-response model, USP uses an asynchronous message bus architecture with MQTT/WebSocket transport, TLS 1.3 encryption, multi-controller support, and real-time telemetry subscriptions. It enables operators to manage devices more efficiently at scale and supports modern use cases like IoT, multi-tenancy, and containerized application deployment.

    Q: When should operators mandate USP support in CPE RFPs?

    Operators should include USP 1.3 compliance as a mandatory requirement in all new CPE procurement tenders starting in 2026. Major carriers including Deutsche Telekom and BT Group have already done so. Delaying USP requirements until 2027-2028 risks deploying devices that will require premature replacement or costly software upgrades within the typical 3-5 year CPE lifecycle.

    Q: Can USP and TR-069 coexist during the transition period?

    Yes. Operators typically dual-stack their ACS/controller environment to support both protocols simultaneously during the multi-year migration. Many CPE vendors now offer devices with both TR-069 and USP agents, allowing gradual fleet migration. The USP specification also defines a proxy mechanism for managing legacy TR-069 devices through a USP controller.

  • Enterprise 4G MiFi Selection: Field Work and Backup Connectivity

    Enterprise 4G MiFi Selection: Field Work and Backup Connectivity

    A portable hotspot for field staff must be evaluated against the places and workloads where it will operate. A radio-category label, maximum user count or battery capacity cannot by itself establish service quality for an enterprise fleet.

    Write the field-use brief

    Record countries, operators, expected travel, applications, client devices and daily working pattern. Distinguish a device carried between stationary jobs from one required to maintain service while moving. Confirm coverage and service-plan restrictions before choosing a radio variant.

    Compare the complete radio implementation

    Check LTE bands and any required aggregation combinations on the exact model. Category numbers describe capabilities under defined conditions; they do not establish a site’s achievable throughput. Ask for network qualification evidence rather than treating chipset support as complete-device validation.

    Measure battery use with the actual workload

    Battery capacity is an input to a runtime assessment, not a runtime guarantee. Test the required applications, client count, signal conditions and power-saving policy. Record ambient conditions, battery age and charging equipment. Include time spent idle or reconnecting where these are part of the working day.

    Test local access and administration

    • Connection and reconnection for the required client mix.
    • Security settings and configuration access needed by the enterprise.
    • Firmware update and recovery procedures supported by the specific model.
    • Visibility of service status and useful diagnostics.
    • Returned-device handling and removal of customer credentials.

    Do not assume every MiFi supports an operator’s remote-management system or unattended power recovery. Specify mandatory behaviour and demonstrate it on samples.

    Plan spares and lifecycle support

    Compare the quoted device configuration, accessories, service plan, provisioning work and support arrangements. Keep replacement criteria and warranty conditions explicit. Evaluate 4G and 5G portable options according to the deployment need rather than assuming the newer generation is always the better purchase.

    Related product and planning resources

  • Carrier Aggregation in 5G CPE Explained: How Multi-Component Carrier Bonding Delivers Multi-Gigabit Throughput for Fixed Wireless Access Networks

    Carrier Aggregation in 5G CPE Explained: How Multi-Component Carrier Bonding Delivers Multi-Gigabit Throughput for Fixed Wireless Access Networks

    Carrier aggregation (CA) is not a new concept—LTE-Advanced introduced it to 4G networks over a decade ago. But in the 5G era, carrier aggregation has evolved into a fundamentally more powerful and complex technology that directly determines whether a fixed wireless access (FWA) CPE delivers 300 Mbps or 3 Gbps. For telecom operators and ISPs deploying 5G FWA at scale, understanding the mechanics and procurement implications of 5G CA is essential to making infrastructure investments that match service-level commitments.

    The Mechanics: How 5G Carrier Aggregation Works

    At its core, carrier aggregation combines multiple frequency carriers—each an independent radio channel—into a single, wider logical data pipe. In 5G NR (New Radio), the aggregated bandwidth can span low-band (sub-1 GHz, e.g., n5, n28), mid-band (1–6 GHz, e.g., n77, n78, n79), and high-band/mmWave (24–47 GHz, e.g., n257, n258, n260, n261) spectrum simultaneously. A 5G CPE with robust CA capabilities can bond a 100 MHz n78 channel, a 40 MHz n5 channel, and a 400 MHz n260 mmWave carrier into a single 540 MHz effective bandwidth.

    This cross-band aggregation is what makes 5G FWA commercially viable at scale. The mid-band carrier provides the capacity layer for sustained high throughput, the low-band carrier provides the coverage layer for uplink reliability and indoor penetration, and the mmWave carrier—where available—provides the extreme-capacity layer for peak throughput. The CPE’s modem and antenna system must handle all three simultaneously, which is why CA configuration directly impacts bill of materials cost and thermal design complexity.

    CA Combinations: What Operators Should Specify in RFPs

    Not all CA combinations are created equal, and the combinations a CPE supports must match the operator’s spectrum holdings. The 3GPP specifications define hundreds of permitted CA combinations across FR1 (sub-7 GHz) and FR2 (mmWave), but practical CPE implementations support a meaningful subset. For operator procurement in 2026, the following CA configurations represent the minimum viable specification for carrier-grade FWA CPE:

    Essential FR1 CA combinations for mid-band FWA: n77+n77 (intra-band contiguous and non-contiguous) for markets with 80–100 MHz of C-band spectrum; n78+n78 for markets using the 3.3–3.8 GHz range; and n77+n5 or n78+n28 for mid-band plus low-band aggregation. These combinations ensure the CPE can aggregate the operator’s primary capacity band with supplementary low-band for uplink and coverage.

    FR1+FR2 (mmWave) CA: n77+n260 and n78+n257 combinations are critical for operators with mmWave holdings who want to deliver multi-gigabit peak speeds in dense urban and suburban deployments. The CPE modem must support EN-DC (E-UTRAN New Radio Dual Connectivity) for 4G anchor plus 5G data paths, as well as NR-CA within 5G standalone mode for future-proof SA architectures.

    Modem Selection: Qualcomm, MediaTek, and the CA Landscape

    The CPE’s modem chipset is the primary determinant of CA capability. In the current generation (2025–2026), the Qualcomm Snapdragon X75 and X80 modem-RF systems support up to 10 carrier aggregation across sub-7 GHz and mmWave, with 5× CA on sub-7 GHz alone. MediaTek’s T800 and forthcoming T830 platforms offer comparable CA density with slightly different band combination priorities—particularly strong in Asian and European band configurations where MediaTek’s market share is highest.

    For operators, the modem selection decision has cascading implications. Qualcomm-based CPE generally offers broader carrier certification coverage in North America and Europe. MediaTek-based CPE often delivers better price-performance ratios for price-sensitive markets in Southeast Asia, Africa, and Latin America. The key procurement question is not “which modem is better” but “which modem supports the CA combinations that match our deployed spectrum and target throughput.”

    Antenna Design: The Silent CA Enabler

    Carrier aggregation multiplies the antenna design challenge. Each aggregated band requires independent antenna paths with adequate isolation to prevent inter-band interference. A CPE supporting 3× CA across n77+n77+n5 needs at minimum 4×4 MIMO on n77 (four antenna elements) plus 2×2 MIMO on n5 (two elements)—a total of six independent antenna paths that must coexist within a compact enclosure while maintaining 15–20 dB of isolation between bands.

    This antenna density requirement is a key reason why outdoor CPE units consistently outperform indoor units in CA scenarios. The larger physical enclosure allows better antenna separation, while outdoor placement eliminates building penetration loss that disproportionately affects higher-frequency bands. When evaluating CPE for CA-heavy deployments, operators should strongly consider outdoor or window-mounted form factors for the primary FWA device.

    Procurement Checklist: CA Evaluation Criteria

    When evaluating 5G CPE for carrier aggregation capability, operators should require vendors to provide: (1) a complete list of supported CA combinations as tested and certified, not just modem chipset theoretical capabilities; (2) throughput test results under controlled conditions for each supported CA configuration, including performance at cell edge (-115 to -120 dBm RSRP); (3) thermal performance data under sustained CA load—devices that throttle after 15–20 minutes of full CA throughput are not suitable for FWA use cases; and (4) carrier certification status for the operator’s specific network, including IOT (Interoperability Testing) completion reports.

    Carrier aggregation capability is not a binary yes/no specification—it is a multi-dimensional performance characteristic that directly determines the end-user experience, network efficiency, and service tier differentiation. Operators who invest the time to specify CA requirements precisely in their CPE RFPs will deploy FWA networks that deliver on their throughput promises, while those who treat CA as an afterthought will field a steady stream of “why is my internet slow” support tickets.

    Frequently Asked Questions

    Q: What is carrier aggregation in 5G and why does it matter for FWA CPE?

    Carrier aggregation (CA) combines multiple 5G frequency carriers into a single wider data pipe, dramatically increasing throughput. For FWA CPE, CA enables bonding low-band (coverage), mid-band (capacity), and mmWave (peak speed) simultaneously. A CPE with robust CA might deliver 1.5-3 Gbps where a non-CA device on the same network achieves 300-500 Mbps.

    Q: How many CA combinations should a carrier-grade 5G CPE support?

    A carrier-grade 5G FWA CPE should support at minimum: intra-band contiguous and non-contiguous CA on mid-band (n77+n77, n78+n78); mid-band plus low-band CA (n77+n5, n78+n28); and ideally FR1+FR2 CA (n77+n260, n78+n257) for operators with mmWave spectrum. The exact combinations must match the operator’s deployed spectrum holdings.

    Q: Does carrier aggregation affect CPE thermal design?

    Yes, significantly. Each additional aggregated carrier increases modem power consumption by 15-25%. A CPE running 3× CA with 4×4 MIMO can consume 8-12W, requiring active cooling solutions. Operators should require vendors to provide sustained throughput data (not just peak) and thermal throttling thresholds. Passive cooling is usually only adequate for 2× CA configurations.

    Q: Qualcomm vs MediaTek modems: which is better for carrier aggregation?

    Both offer comparable CA density in their 2025-2026 generation platforms. Qualcomm X75/X80 provides broader carrier certification in North America and Europe. MediaTek T800/T830 offers competitive CA at lower cost, particularly strong in Asian and European bands. The decision should be based on which modem supports the specific CA combinations that match your spectrum, not brand preference.

  • TR-369 User Services Platform Gains Traction in 2026 Carrier CPE Deployments: The Transition Away from TR-069 for Next-Generation Device Management

    TR-369 User Services Platform Gains Traction in 2026 Carrier CPE Deployments: The Transition Away from TR-069 for Next-Generation Device Management

    The Broadband Forum’s TR-369 User Services Platform (USP) is experiencing its steepest adoption curve to date in 2026, as telecommunications operators across Europe, North America, and Asia-Pacific accelerate their migration away from the aging TR-069 (CWMP) protocol. With over 40 million USP-capable CPE devices now in active deployment globally, the industry is reaching a decisive inflection point in device management architecture.

    TR-069 served the broadband industry capably for nearly two decades, providing basic provisioning, firmware updates, and diagnostics for residential gateways. But as operator networks evolve toward virtualized, multi-service, and AI-driven operations, CWMP’s limitations—synchronous request-response architecture, limited security model, and inability to support complex IoT and multi-tenant scenarios—have become untenable at scale.

    What Makes TR-369 Fundamentally Different

    TR-369 USP represents a complete architectural redesign rather than an incremental upgrade. Built around a microservices-oriented, event-driven architecture, USP uses a message bus paradigm where devices, controllers, and applications communicate asynchronously through a common data model derived from TR-181 Device:2. This enables operators to push configuration changes simultaneously across thousands of devices, receive real-time telemetry without polling, and implement zero-touch provisioning at wire speed.

    Key technical advantages over TR-069 include: native TLS 1.3 encryption with mutual certificate-based authentication; MQTT and WebSocket transport protocols replacing unreliable HTTP sessions; multi-controller support allowing a single CPE to be managed by both the operator and enterprise IT simultaneously; and a subscription-notification mechanism that eliminates the bandwidth overhead of periodic CWMP Inform messages.

    Carrier Adoption Milestones in 2026

    Several Tier-1 operators have made public commitments to full USP migration in 2026. Deutsche Telekom has mandated USP support in all new CPE procurement tenders for its European subsidiaries. BT Group’s Openreach network now requires USP compliance for any FTTP CPE connecting to its wholesale fiber platform. In North America, three major cable MSOs have begun USP field trials for their next-generation DOCSIS 4.0 gateways, targeting production deployment by Q4 2026.

    For CPE manufacturers, this shift carries significant implications. Devices must now support the full USP 1.3 agent specification, including the Software Module Management (SMM) service for containerized application deployment and the IoT data model extensions standardized in TR-181. Carriers are increasingly evaluating CPE vendors not just on radio performance and price, but on the maturity of their USP implementation—including certification status from BBF.067 compliance testing.

    Market Implications for CPE Procurement

    Industry analysts project that USP-capable CPE will account for 65% of all new carrier gateway shipments by 2027. The immediate procurement impact is twofold: operators must dual-stack their ACS (Auto Configuration Server) environments to support both TR-069 and TR-369 during the multi-year transition, while CPE manufacturers face increased software development costs to implement, test, and certify USP agents across their product lines.

    For operators still in the RFP stage for 5G FWA and next-gen broadband CPE, USP compliance should be a mandatory line item in technical specifications. The protocol’s support for bulk provisioning, real-time performance monitoring, and multi-tenancy directly influences operational OPEX and customer experience KPIs. Waiting until 2027 to mandate USP risks deploying a fleet of devices that will require costly software upgrades or premature replacement within 18-24 months.

    The TR-369 ecosystem continues to mature rapidly. Open-source USP agent implementations are now available from prpl Foundation and RDK-B, reducing integration barriers. Commercial ACS/controller platforms from Axiros, Friendly Technologies, and Incognito have all released production-grade USP support. The industry consensus at Broadband World Forum 2025 was unambiguous: TR-069 is in its final chapter, and the operators moving fastest on USP adoption will gain measurable operational advantages in device lifecycle management, security posture, and service agility.

    Frequently Asked Questions

    Q: What is TR-369 USP and how does it differ from TR-069?

    TR-369 User Services Platform (USP) is the Broadband Forum’s next-generation device management protocol that replaces TR-069 (CWMP). Unlike TR-069’s synchronous HTTP-based request-response model, USP uses an asynchronous message bus architecture with MQTT/WebSocket transport, TLS 1.3 encryption, multi-controller support, and real-time telemetry subscriptions. It enables operators to manage devices more efficiently at scale and supports modern use cases like IoT, multi-tenancy, and containerized application deployment.

    Q: When should operators mandate USP support in CPE RFPs?

    Operators should include USP 1.3 compliance as a mandatory requirement in all new CPE procurement tenders starting in 2026. Major carriers including Deutsche Telekom and BT Group have already done so. Delaying USP requirements until 2027-2028 risks deploying devices that will require premature replacement or costly software upgrades within the typical 3-5 year CPE lifecycle.

    Q: Can USP and TR-069 coexist during the transition period?

    Yes. Operators typically dual-stack their ACS/controller environment to support both protocols simultaneously during the multi-year migration. Many CPE vendors now offer devices with both TR-069 and USP agents, allowing gradual fleet migration. The USP specification also defines a proxy mechanism for managing legacy TR-069 devices through a USP controller.

  • Open RAN and 5G CPE: What Interoperability Testing Must Cover

    Open RAN and 5G CPE: What Interoperability Testing Must Cover

    An operator can deploy a multi-vendor radio access network while using ordinary standards-based customer devices. CPE evaluation should identify the network and radio features actually required, rather than treating an Open RAN label as a new universal customer-device interface.

    Correctly identify the interface

    O-RAN ALLIANCE’s Open Fronthaul work concerns the interfaces between radio-access infrastructure functions such as the O-DU and O-RU. A customer CPE connects through the cellular radio interface. It is not normally an O-DU or O-RU and should not be required to implement infrastructure fronthaul solely because the serving network uses Open RAN.

    Build a concrete capability matrix

    Ask the operator which bands, network modes, carrier combinations, voice features and mobility behaviour are required. Identify any optional features being trialled. The network’s equipment release does not establish which functions a specific CPE modem, radio implementation and firmware support.

    Test the intended service

    • Registration and authentication using the intended SIM and service plan.
    • Data-session establishment, APN settings and addressing requirements.
    • Uplink, downlink, latency and loss across representative radio conditions and network load.
    • Cell reselection, recovery from service interruption and required mobility scenarios.
    • Voice or special service features only where explicitly included in the project.

    Record the network configuration, device variant and firmware for each result. Repeat relevant tests after material network or device changes. Successful attachment in one lab does not establish compatibility across every commercial deployment.

    Ask for useful evidence

    Use operator acceptance records or a jointly agreed test report that identifies the actual equipment and test scope. Do not interpret participation in a general industry event, a chipset feature list or a supplier’s infrastructure partnership as approval of a particular retail CPE model.

    For procurement, share the target operator and deployment configuration with the supplier. The appropriate outcome is a versioned, testable compatibility statement and a defined support path.

    Related product and planning resources

    Sources and further reading