This dataset identifies 42 published patent families that combine Open RAN or O-RAN architecture terms with resilience-specific language such as network resilience, high availability, fault tolerance or service continuity, filed between 2015 and mid-2026. That is a narrow, precisely defined subset of the much larger overall Open RAN patent corpus, focused specifically on how disaggregated radio networks keep running through component failure rather than on general configuration or performance optimisation. Because publication lags filing by roughly 18 months, the true current total is somewhat higher than what has published so far.

The assignees with tracked activity in this corpus include Intel, Parallel Wireless, Rakuten Symphony's Japan and USA entities, EdgeQ, and Dish Wireless, among others. None of these shows filing growth in the latest tracked year, and several show a full year-over-year drop from prior activity, which is consistent with the corpus-wide peak in 2022 rather than any single company scaling back. Rakuten Symphony is the one filer with a visible joint-filing pattern, sharing several families across its US and Japan entities.

The filing trend rises from zero in 2017 to a peak of 12 families in 2022 before falling back, a shape typical of a wave in which early-moving applicants stake out foundational architecture claims — redundant O-CU/O-DU/O-RU deployment, HA manager designs, failover coordination — within a short window. It does not necessarily mean interest in the underlying problem has declined; publication lag means 2024–2026 filings are still underrepresented in the published data. A re-check of this trend after another publication cycle would clarify whether the 2022 peak was a one-off or part of a longer cycle.

US11863393B1, assigned to EdgeQ, claims a high-availability architecture for O-RAN deployed across cloud tiers, with O-CU on a regional cloud, O-DU at the edge and O-RU at the cell site, using redundant instances monitored by local and central HA managers for failure prediction and failover. It is a useful reference for how this class of claim is structured, but whether it blocks a specific new filing depends on the exact redundancy mechanism, monitoring architecture and tier placement claimed — a claim-by-claim comparison is needed rather than a title-level read. Designing around it typically means changing where redundancy is instantiated or how failure state is monitored and escalated.

The corpus concentrates heavily in H04W and H04L, meaning most claimed mechanisms sit at the radio-access and transport layers; areas like cross-vendor RIC failover coordination, AI-driven fault prediction inside xApps, and fronthaul link degradation compensation show comparatively thin direct coverage. These adjacent branches sit close to the dense core but are not fully occupied by it, making them worth a dedicated prior-art search before drafting new claims. The low number of co-assignee filings across the dataset also suggests multi-vendor interoperability fault handling has not been heavily claimed through joint filings, which is itself a gap.