RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)

[OTHER]

Oct 20, 2025 · RingConn · RingConn (Gen 2 / Gen 3) · China, Asia

Failure Mode

OTHER

Event Date

Oct 20, 2025

Primary Entity

RingConn

Robotic Platform

RingConn (Gen 2 / Gen 3)

Jurisdiction / Location

China, Asia

Audit Standard

Physical State Verified

Incident Abstract & Audit Findings

Named alongside Ultrahuman in the same Oura '178 ITC action (337-TA-1411), RingConn resolved it on ~Oct 20 2025 via a comprehensive settlement and multi-year patent license with royalty payments to Oura, and continues selling in the US. This is the load-bearing CONTRAST to Ultrahuman: same ITC case, opposite outcomes (RingConn licensed-and-selling vs Ultrahuman excluded). Corrects the common aggregator framing that RingConn was banned.

System & Fleet Architecture

Operating Manufacturer

Hardware Platform

RingConn (Gen 2 / Gen 3)

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

  • https://gadgetsandwearables.com/2025/10/20/ringconn-oura-lawsuit/

    https://gadgetsandwearables.com/2025/10/20/ringconn-oura-lawsuit/

  • https://www.businesswire.com/news/home/20250909387922/en/U.S.-International-Trade-Commission-Rules-in-Favor-of-URA-in-Patent-Case-Against-Ultrahuman-and-RingConn

    https://www.businesswire.com/news/home/20250909387922/en/U.S.-International-Trade-Commission-Rules-in-Favor-of-URA-in-Patent-Case-Against-Ultrahuman-and-RingConn

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?

Named alongside Ultrahuman in the same Oura '178 ITC action (337-TA-1411), RingConn resolved it on ~Oct 20 2025 via a comprehensive settlement and multi-year patent license with royalty payments to Oura, and continues selling in the US. This is the load-bearing CONTRAST to Ultrahuman: same ITC case, opposite outcomes (RingConn licensed-and-selling vs Ultrahuman excluded). Corrects the common aggregator framing that RingConn was banned.

When did this incident occur?

The incident is recorded as occurring on October 20, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

What robot was involved in RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?

RingConn (Gen 2 / Gen 3) by RingConn is the recorded robot involved in this incident at China, Asia.

Has anyone responded to RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

What is the current status of RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.