I'll search for information about US Patent 11,656,742 and any related CAFC 2026 docket activity.

The initial searches surfaced unrelated patents (e.g., 11,656,422 — a CommScope fiber optic patent) and no CAFC results. Let me refine the searches for the exact patent and any federal litigation.

The Golden wiki confirms the basic bibliographic data. Let me check for any CAFC or district-court docket activity tied to this patent number specifically.

Summary — U.S. Patent No. 11,656,742 B1

Bibliographic data

Abstract (verbatim)

"A selection interface and method for a user in a virtual reality environment to select a software application for launch or a virtual reality system setting for activation by directly touching and interacting with an application or setting icon displayed to the user that appears closer to the user than a selection interface displayed when the user is using a physical controller."

Independent claims (plain-language overview)

The patent has three independent claims: 1, 8, and 12 (with dependent claims 2–7, 9–11, and 13–20).

Claim 1 (apparatus — single app icon): A VR selection interface with a first software-application icon shown to a user wearing VR hardware. The first icon appears closer to a user body part (e.g., hand, tracked by a camera of the VR device) than a second software-application icon that is displayed when the user is using a physical controller. The first icon launches its software application when the user directly interacts with it by pushing, pulling, tapping, pressing, or sliding a body part on the icon. Notably, the first and second icons are both linked to launch the same software application — i.e., the same app is reachable via either interface, but positioned differently.

Claim 8 (apparatus — app icon + system-setting icon): A VR selection interface displaying both a first software-application icon and a first VR-platform system-setting icon together. Both appear closer to the user's tracked body part than a corresponding second application icon and second system-setting icon shown during physical-controller use. The system-setting icon activates a setting, and the app icon launches a software application, each upon direct push/pull/tap/press/slide interaction with the body part. (Note: the claim's wording refers to interaction "directly on the first icon" for the setting and "directly on the second icon" for the app — slightly awkward drafting, but the plain meaning is that each icon responds to direct body-part interaction.)

Claim 12 (method): A method comprising: (1) detecting that a user is not using or has discontinued use of a physical device controller; (2) after that detection, displaying a "body interactive icon" (app icon and/or system-setting icon) that appears closer to a tracked body part than a "physical controller icon" that was displayed when the controller was in use, with both icons linked to launch/activate the same application or setting; (3) receiving a control input selecting the body interactive icon that appears as a direct touching body interaction; (4) launching the linked software application if the icon represents an app; and (5) activating the linked VR-platform system setting if the icon represents a setting.

Dependent claims add details such as 3D-button presentation of icons (claims 2, 9, 13), up/down scroll arrows as pushable 3D buttons (claims 3, 4, 14), and distance determination based on arm length, user height, or average arm length values (claims 15–20).

Litigation status (as of today's date)

• District court: CurioXR, Inc. v. Meta Platforms, Inc., Case No. 7:26-cv-00123 (W.D. Tex., Midland Division), filed April 2, 2026; Judge David Counts; Magistrate Judge Derek T. Gilliland; nature of suit 830 (patent), cause 35:271. Per complaint-analysis sources, the plaintiff asserts independent claim 1 of the '742 patent (along with claims of the related '448 patent, US 11,531,448), accusing Meta Quest headsets (Quest 2, Pro, 3, 3S) running the "Direct Touch" feature. Case is open/active; no rulings identified.
• CAFC 2026 docket: No CAFC (Federal Circuit) docket was found in my searches for this patent number. As of now the matter appears to be at the district-court stage only.

Sources and uncertainty notes

• Bibliographic data and full text come from the authoritative Google Patents page (fetched 2026-08-27, provided in the prompt) and are corroborated by the Golden wiki entry for "US Patent 11656742."
• Searches for the number "11656742" surfaced an unrelated PTAB exhibit for US 11,656,422 (CommScope fiber-optic patent) — that is a different patent and is not the subject patent; I have excluded it per the instruction not to return similar numbers.
• I could not directly query the USPTO database or PACER in this session; litigation details are drawn from third-party docket/complaint-analysis pages and should be verified against PACER/CM-ECF for authoritative docket entries.

Based on my searches (April 26, 2026), there is one known district-court case asserting U.S. Patent 11,656,742 B1. No CAFC appeal, IPR/PTAB proceeding, or ITC investigation involving this patent was found.

Known litigation involving US 11,656,742 B1

1. CurioXR, Inc. v. Meta Platforms, Inc.

Key allegations (from complaint coverage): CurioXR alleges Meta's Direct Touch interface displays icons near the user's tracked body part and permits direct-touch interaction (tap, push, etc.), which the complaint maps to the claimed "first grouping" of icons appearing closer to the user than the controller-based interface, with both interfaces linked to launch the same applications. CurioXR alleges it contacted Meta in January 2024 about its VR/AI patent portfolio and proposed a license before suing. The complaint also cites Meta CEO Mark Zuckerberg's 2023 Instagram post promoting Direct Touch as evidence of the feature's significance.

Litigation status summary

• District court: 1 case (W.D. Tex.), filed April 2, 2026 — early stage, no outcome yet.
• CAFC (Federal Circuit): No appeal docket found as of today.
• PTAB (IPR/PGR): No inter partes review or other AIA proceeding found.
• ITC: No Section 337 investigation found.

Caveats: Docket details are drawn from third-party docket/complaint-analysis aggregators and news coverage (April 3–8, 2026); I could not access PACER/CM-ECF directly in this session. The case number, parties, court, filing date, and judges are corroborated across multiple independent sources. For authoritative docket entries (e.g., service, answer deadlines, early motions), PACER or the court's public CM/ECF should be consulted. I found no litigation involving any patent number similar to but different from 11,656,742 (e.g., the unrelated 11,656,422), and I have excluded such results per your instruction.

Proceedings overview

There is one AIA trial proceeding on file for US 11,656,742 B1: IPR2026-00460, filed by Meta Platforms, Inc. et al., which is pending (institution not yet decided). No claims have been invalidated, no claims have been sustained in a Final Written Decision, nothing has settled, and no institution denial exists. The defensive posture for a defendant today: the patent is fully intact — all 20 claims are alive and untested by the PTAB — and the single pending IPR is at its earliest possible stage (filed 2026-08-26, i.e., yesterday), so no IPR-based ammunition exists yet, though the mere filing by the co-defendant signals that serious prior art is being developed.

IPR2026-00460 — Meta Platforms, Inc. et al. v. CurioXR Inc. (VR-EDU, Inc.)

• Type: Inter Partes Review
• Filed: 2026-08-26
• Status: Pending (verbatim from the USPTO Open Data Portal ingest; last modified 2026-08-26). Plain-English gloss: the petition was docketed yesterday; the Board has not even set the patent-owner preliminary response deadline in any publicly visible way yet.
• Judge panel: Not yet designated. PTAB panels for an IPR are typically announced at or around the institution decision, and none has been named publicly as of today (2026-08-27).
• Petition grounds: Not yet publicly available. The petition was filed 2026-08-26 and my searches surfaced no PTAB E2E docket entries, no press coverage of the grounds, and no published petition. Which claims are challenged, which prior-art references are asserted, and the statutory bases (§ 102/§ 103/§ 112) are therefore unknown at this time. What is known from the structured data: petitioner is "Meta Platforms, Inc. et al." (the "et al." indicates at least one additional named petitioner — most plausibly a Meta affiliate such as Meta Platforms Technologies, LLC, but that is inference, not verified fact), and the inventor is Ethan Fieldman.
• Institution decision: None — not due yet. Under 35 U.S.C. § 314(b), the Director decides whether to institute within 3 months after the patent owner's preliminary response (or the date the response was due if none is filed). The POPR is due roughly 3 months after the petitioner's notice of filing (37 C.F.R. § 42.107), placing the realistic institution-decision window around February–March 2027.
• Final Written Decision: None. No trial has been instituted, so no claim has been canceled or sustained. All 20 claims of the '742 patent (independents 1, 8, 12 and dependents 2–7, 9–11, 13–20) remain in force.
• Settlement / termination: None. No settlement, no request for adverse judgment, no termination — the case is one day old.
• Appeal: None. No FWD exists, so there is nothing to appeal; no CAFC docket tied to this proceeding was found.
• Defensive value: For the defendant who is also the petitioner (Meta), this is a fresh, aggressive validity attack filed ~4.8 months after being sued (suit filed 2026-04-02; IPR filed 2026-08-26 — comfortably inside the 35 U.S.C. § 315(b) one-year bar). For any other defendant facing assertion of '742, the patent is not yet weakened by the PTAB in any way — no claim is dead, and an infringement theory built on claims 1/8/12 is fully enforceable until a FWD says otherwise. What the filing does signal is that Meta believes there is citable prior art; that petition (once public) is worth mining.

Strategic summary

Claims status — CANCELED vs. SUSTAINED vs. UNTESTED. All 20 claims of US 11,656,742 B1 are UNTESTED. No AIA trial has been instituted, so no claim has been canceled and no claim has been sustained by a Final Written Decision. The independent claims asserted in the W.D. Tex. litigation — claim 1 of '742 (and claims 1 and 12 of the parent '448 patent) — remain presumed valid and fully in force. The single pending IPR (IPR2026-00460) challenges something, but the claim set is not yet public; do not assume it covers all asserted claims.

Estoppel landscape — § 315(e)(2). No estoppel has attached because no FWD has issued. Once a FWD issues, Meta Platforms, Inc. and its privies (including any "et al." co-petitioners and corporate affiliates that are real parties in interest or privies) will be barred from raising in district court or ITC any § 102/§ 103 ground that they raised or reasonably could have raised in the IPR. For a non-Meta defendant currently being asserted against, all grounds remain available today — including any art Meta's petition develops — because § 315(e)(2) estoppel binds only the petitioner and its privies, not strangers. That said, a non-Meta defendant must watch its own § 315(b) bar: an IPR must be filed within one year of service of that defendant's complaint.

Pattern signals. One petitioner, one IPR — no pattern of repeat filings on this patent yet. The petitioner is the litigation defendant (Meta), not a defensive aggregator; no Unified Patents or similar entity appears in the chain for this proceeding. The patent owner side shows signs of active monetization/enforcement: CurioXR sued Meta in W.D. Tex. (7:26-cv-00123) on 2026-04-02, and the '742 patent received two certificates of correction (2025-12-16 and 2026-02-24) — consistent with a patent owner polishing its enforcement asset. Meta's countermove (IPR within five months of service, well within the § 315(b) bar) is the textbook response of a defendant that intends to fight rather than license.

Recommended next steps

• There is no FWD to link — no claims have been invalidated, so there is nothing yet to quote as a disposition. If you are a non-Meta defendant, do not tell a court or an adversary that this patent has been "weakened by IPR"; that would be false. All 20 claims are enforceable.
• Monitor IPR2026-00460 on PTAB E2E (https://developer.uspto.gov/ptab-web/ — search "IPR2026-00460"). Key near-term milestones: patent owner preliminary response due ~2026-11-26 (3 months from filing); institution decision due ~2027-02/03 (3 months after POPR per § 314(b)); if instituted, the Final Written Decision is due within 12 months of institution (§ 316(a)(11)), i.e., roughly early-to-mid 2028 absent extension.
• If you are Meta (or in privity): file the motion to stay the W.D. Tex. case pending the IPR promptly after institution (or even now), and coordinate the IPR ground selection with the claims actually asserted (claim 1 of '742; claims 1 and 12 of '448) so § 315(e)(2) estoppel covers the litigation grounds.
• If you are a non-Meta defendant: as soon as the Meta petition becomes public (typically visible on PTAB E2E shortly after docketing), review its art — it is likely highly relevant to your own invalidity position — and independently assess your § 315(b) bar date before deciding whether to file your own petition or join Meta's. Do not rely on Meta's estoppel to protect you; it does not.
• Verify against PTAB E2E directly: the petition's grounds, real-parties-in-interest, and any early procedural orders were not visible in public web sources as of 2026-08-27 (the proceeding is one day old). PACER/PTAB E2E are the authoritative sources for the docket entries that will appear over the coming weeks.

The initial searches surfaced the inventor's corporate affiliations but not the USPTO reel/frame numbers. Let me dig deeper into the assignment records and the corporate background.

I was unable to pull the USPTO Assignment Center reel/frame records or correspondent names directly in this session (searches returned the Google Patents legal-event descriptions but not the underlying reel/frame/correspondent data). Rather than fabricate those fields, I'm reporting the assignment record as evidenced by the authoritative Google Patents legal-events feed for US 11656742 (provided in the prompt), cross-correlated with the corporate records surfaced in searches, and flagging every unverified field explicitly.

Inventors

Fieldman is the sole inventor of US 11,656,742 and of essentially the entire VR-EDU/CurioXR portfolio. Public inventor-profile data (patents-review.com, PatentGuru) show his assignees over time as: VR-EDU, Inc.; Study Social Inc.; CurioXR, Inc.; CurioXR, Inc. (f/k/a VR-EDU, Inc.); Curio XR (VR EDU); VR EDU LLC; and Study Edge, Inc. (Wilmington, DE).

Unusual pattern check: The "all inventors depart the original assignee within 12 months" pattern is not present — Fieldman is the founder/principal of the VR-EDU/CurioXR cluster (and of Gainesville education company Study Edge), not a departing employee. He continued filing new applications assigned to the renamed CurioXR entity through at least 2026 (e.g., US 2026/0003471, applicant "CurioXR, Inc. (f/k/a VR-EDU, Inc.)"), i.e., he remains with the assignee ~4 years post-filing.

Original assignee

• Entity named on the issued patent: VR Edu Inc. (also recorded as VR-EDU, Inc.), Gainesville, FL.
• Primary line of business: Virtual reality / extended reality education software — VR classroom, tutoring and assessment content (affiliated with Study Edge, Inc., a Gainesville education company). The company filed trademarks for "CURIOXR" (2023) and "CURIO" (2024), indicating an active consumer-facing brand.
• Did they ship a product embodying the claims? Likely yes, but not publicly documented in detail. The company's stated business is VR education content delivered on headsets (e.g., Meta Quest), which necessarily includes in-VR application/setting selection interfaces of the type claimed; it also continued prosecuting a large family of related VR-interface patents (US 11,900,559; US 11,983,837; US 12,033,293; US 12,288,302; etc.) through 2024–2026. I found no evidence of a shipped product specifically practicing claim 1 of '742, so this is inferential.
• Current status: Operating. Renamed CurioXR, Inc. (change of name recorded 2024-12-04); still filing patents as of 2026; not dissolved, not in bankruptcy, not acquired by a third party.

Assignment timeline

The USPTO Assignment Center could not be queried directly this session; the following is the complete assignment record as reflected in Google Patents legal events (which draw from the USPTO assignment database). No security agreements, licenses, mergers, or releases appear in the record — only the two entries below.

• Executed: not shown on public record / recorded 2022-12-15 — Reel/frame not verified (USPTO Assignment Center; no reel/frame surfaced in session searches)

  • Conveyance: Assignment of Assignor's Interest ("ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: Ethan Fieldman
  • Assignee: VR-EDU, Inc.
  • Correspondent: Not verifiable this session — no correspondent name available; flagging as unverified rather than guessing.
  • Context: Standard inventor-to-company assignment, recorded same-day as the continuation application (US 18/066,796) was filed. This is the only assignment into the original assignee; it is the origin of the chain, not an NPE transfer.

• Executed: not shown on public record / recorded 2024-12-04 — Reel/frame not verified

  • Conveyance: Change of Name ("CHANGE OF NAME (SEE DOCUMENT FOR DETAILS)")
  • Assignor: VR-EDU, Inc.
  • Assignee: CURIOXR, INC.
  • Correspondent: Not verifiable this session — flagging as unverified.
  • Context: Pure corporate name change — same entity, same Gainesville, FL business; not a transfer to a separate LLC, not an acquisition, not a securitization, not a fire-sale.

Bottom line: The Assignment Center record for this patent is minimal — one inventor→company assignment and one name change. The original assignee (now CurioXR, Inc.) still owns the patent. No transfer to any third-party holding company, NPE, or aggregator has been recorded.

Timeline diagram

timeline
    title Ownership of US 11656742
    2022 : Filed by Ethan Fieldman
         : Assigned to VR-EDU Inc
    2023 : Patent issued May 23
    2024 : Name change to CurioXR Inc
    2026 : CurioXR sues Meta in W Texas

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. The only post-issuance transfer is a Change of Name (VR-EDU, Inc. → CURIOXR, INC., recorded 2024-12-04), not a transfer to a licensing-only LLC. CurioXR retains the same Gainesville, FL identity, continues filing patents (e.g., US 2026/0003471, "CurioXR, Inc. (f/k/a VR-EDU, Inc.)") and holds live trademarks (CURIOXR 2023; CURIO 2024). No "IP / Patents / Licensing / Holdings" suffix, no registered-agent-service address, no single-purpose LLC in the chain.

2. Known asserter in the chain — NOT PRESENT. Neither VR-EDU nor CurioXR appears in any NPE directory surfaced in searches (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Round Rock, Document Generation Corp, Spangenberg entities, or Unified/RPX high-frequency plaintiff lists). CurioXR is a plaintiff — CurioXR, Inc. v. Meta Platforms, Inc., 7:26-cv-00123 (W.D. Tex., filed 2026-04-02), asserting claim 1 of '742 — but being a plaintiff is not the same as being a listed NPE, and it is the renamed original assignee suing in its own name.

3. Repeat correspondent across the chain — UNCLEAR / UNVERIFIED. I could not obtain the correspondent-of-record for either recording (no reel/frame data in any search result this session). Per instructions I will not guess. This is the one signal that remains genuinely open; a check of the two USPTO reel/frame pages (search patent 11656742 at assignmentcenter.uspto.gov) is the recommended verification step.

4. Cascading transfers — NOT PRESENT. Exactly two recorded events over ~24 months, and the second is a name change of the same entity. No chained LLCs, no shared-address shell sequence, no rapid-fire conveyances.

5. Pre-litigation transfer — NOT PRESENT. The name change (recorded 2024-12-04) predates the first infringement suit (2026-04-02) by ~16 months — outside the 6-month window. The inventor assignment (recorded 2022-12-15) predates suit by ~40 months and is the routine filing-time assignment. The chain was not rearranged to enable the suit or set venue.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 for VR-EDU or CurioXR found; the company is active (patent filings through 2026, maintenance-fee petition granted 2025-12-30, two certificates of correction 2025-12-16 and 2026-02-24 — the latter pair consistent with an owner actively polishing an enforcement asset, not a liquidating one).

7. Privateering — NOT PRESENT. No evidence CurioXR asserts on behalf of a third-party operating company, and no SEC filing or press coverage suggests a revenue-sharing arrangement with a hidden beneficiary. The patent owner is suing directly in its own name as the renamed original assignee.

8. Defensive aggregator (anti-NPE) — NOT PRESENT. The chain terminates at CurioXR, Inc. (operating company). RPX, AST, LOT, Unified Patents, and OIN are nowhere in the chain; the patent has not been neutralized. (Note the inverse activity: Meta filed IPR2026-00460 on 2026-08-26 challenging the patent — a validity attack by the defendant, not defensive aggregation.)

Verdict

Operating-company assertion.

The chain is a straight line — Fieldman → VR-EDU, Inc. (assignment recorded 2022-12-15) → CURIOXR, INC. (change of name recorded 2024-12-04) — so the current assignee is the renamed original assignee, an active Gainesville, FL VR-education company (affiliated with Study Edge; CURIOXR/CURIO trademarks; continuing patent filings through 2026), which sued Meta in W.D. Tex. (7:26-cv-00123, filed 2026-04-02) asserting claim 1 of this patent. No shell transfer, no cascading LLC chain, no bankruptcy, no privateering, and no defensive-aggregator endpoint appears anywhere in the record, and the only "transfer" is a pure name change — so none of the NPE signals are present (the single unverified item is correspondent identity, which cannot alone flip this verdict). The one caveat is that I found no public documentation that CurioXR's shipped products specifically practice claim 1; that is inferential from its VR-education business, but the ownership pattern is unambiguously that of an operating company asserting its own patent against a VR-platform competitor.

Verify at: https://assignmentcenter.uspto.gov/ (search patent 11656742) — confirm the two reel/frame records above (Fieldman → VR-EDU, 2022-12-15; VR-EDU → CURIOXR, change of name, 2024-12-04) and capture the correspondent names, which were the one field I could not verify this session.

I'll research the prior art citations for US 11,656,742. Let me start by verifying the key references against the patent's citation list and gathering details on the most relevant ones.

I have solid detail on several key Meta/Apple references. Let me continue researching the other significant citations.

I have gathered sufficient detail on the key references. Before presenting the prior-art analysis, two housekeeping notes:

• ID hygiene: I searched for patent 11656742 only. Consistent with the earlier sections, I excluded the unrelated US 11,656,422 (CommScope fiber-optic patent) — a different patent that surfaces in searches for similar numbers. Nothing below is a "similar number" artifact; every reference is one of the 30 citations (plus 5 family citations) listed on the Google Patents page for US 11,656,742 B1 provided in the prompt.
• Date discrepancy flagged: The task header states "Current Date: April 26, 2026," while the previously generated sections were authored under "Today's date: 2026-08-27." The prior-art analysis below is unaffected because the effective filing date of the '742 patent (June 1, 2022) is fixed; I note the conflict for consistency-checking purposes only.

Prior-Art Analysis — US 11,656,742 B1 ("Hand control interfaces and methods in virtual reality environments")

1. § 102 framework and the date screen

The '742 patent's effective filing date is June 1, 2022 (filing of parent US 17/830,109). Under the AIA:

• § 102(a)(1) — prior art includes patents and printed publications available to the public before June 1, 2022.
• § 102(a)(2) — prior art includes US patents and US application publications effectively filed before June 1, 2022, naming another inventor.

Every one of the 30 cited references and 5 family citations clears at least one of these screens (each has an effective filing date before 2022-06-01, even where publication postdates it — e.g., US 2022/0197277 A1, filed 2020-12-23 but published 2022-06-23, qualifies only under § 102(a)(2), not (a)(1)).

2. Claim-element map used for the anticipation analysis

Anticipation requires a single reference disclosing every element of a claim (expressly or inherently). The tables below rate each reference's potential to do so; the recurring weak spot across nearly all references is element C/D (the controller-vs-hands distance comparison for the same app icon) — which is the feature the specification emphasizes as the improvement over the conventional Quest "laser hands" interface. All references below were considered by the examiner, who nonetheless allowed all 20 claims; the ratings are therefore litigation-oriented potential, not a finding that any reference is a proven anticipatory disclosure.

3. Tier 1 — Closest art (hand-tracking VR interfaces with direct interaction and/or mode switching)

3.1 US 2021/0405760 A1 — "Integration of artificial reality interaction modes"

• Citation: US 2021/0405760 A1; applicant Facebook Technologies, LLC (Meta); inventor Hayden Schoen; filed 2020-06-29; published 2021-12-30; later issued as US 11,256,336 B2 (Feb. 22, 2022).
• Description: Meta's interaction-mode system for artificial reality (incl. VR HMDs) with automatic, context-specific transitions between interaction modes — no-hands 3DoF, no-hands 6DoF, gaze-and-gesture, and ray-casting. Hand tracking is performed by HMD cameras; actions include pinch, air tap, air swipe, grab; context factors (e.g., whether hand tracking is enabled, lighting, "ready state" of hands) drive transitions. This is the closest Meta disclosure to the accused "Direct Touch"/hand-tracking functionality in the W.D. Tex. case.
• Elements met: A (VR HMD with cameras), E (gesture/direct-air-tap selection of objects), and the detect-hands-instead-of-controller switching of claim 12.
• § 102 potential: Claim 12 (method) — medium-high potential, primarily on the detect-no-controller → different-interaction-mode prong; claim 1 — medium potential. Key gaps: no verified disclosure that the same application icon is displayed closer to the hand in hand mode than in controller mode (elements C–D).

3.2 US 11,086,406 B1 — "Three-state gesture virtual controls"

• Citation: US 11,086,406 B1; Facebook Technologies, LLC; inventors Ravasz et al.; filed 2019-09-20; issued 2021-08-10.
• Description (verified from patent PDF): A hand-interaction system using a three-state model (neutral → tracking → active) to gate hand input so ordinary reaching motions aren't interpreted as commands. In the tracking state the system identifies selection of target objects; in the active state it identifies actions on the selected objects. Transition gestures include pinches, fist poses, and palm-up postures.
• Elements met: A, E (hand-based selection/action on target objects via tracked hand postures).
• § 102 potential: Claim 1 / 12 — medium on E; claims 2–4, 13–14 — low-medium. Key gaps: the reference is about gesture gating, not about icon placement nearer the hand than a controller-based icon, and not about the same-app dual-position concept (C–D); no system-setting icon pairing (claim 8).

3.3 US 2022/0091722 A1 — "Devices, methods, and graphical user interfaces for interacting with three-dimensional environments"

• Citation: US 2022/0091722 A1; Apple Inc.; inventors Faulkner, Lemay, Sorrentino, Ive, Bauerly et al.; filed 2020-09-23; published 2022-03-24 (family members later issued as US 11,561,596 B2, US 11,567,625 B2, US 12,175,010 B2).
• Description (verified from PDF/analysis pages): Computer-generated 3D environments in which a virtual object containing selectable controls is displayed at a position corresponding to the user's hand location (invoked by a preset hand movement), the hand representation moves relative to the virtual object, and the user directly interacts with the virtual controls. Also covers virtual menus anchored to physical-environment portions and gaze-based control placement.
• Elements met: A, B, and — importantly — E plus a version of C (controls placed at the hand's position, i.e., within direct reach), and menus tied to physical locations.
• § 102 potential: Claim 1 — medium-high; claim 8 — medium (selectable controls can be menus/settings, but not clearly "VR-platform system setting" icons); claim 12 — medium. Key gaps: no verified disclosure of the same app icon presented at one distance for hands and a different distance for a physical controller (C–D); the Apple reference is hand-centric and does not appear to compare against a controller-driven layout of the same icon.

3.4 WO 2022/047436 A1 — "3D launcher with 3D app icons"

• Citation: WO 2022/047436 A1; applicant Innopeak Technology, Inc.; filed 2021-10-13; published 2022-03-03.
• Description: A 3D launcher displaying 3D app icons — the single most on-point title in the citation list for claim 2's "3-dimensional button" app icon in a selection/launcher interface. Publication (2022-03-03) precedes the June 1, 2022 effective filing date, so it is § 102(a)(1) art. (I could not retrieve the full text this session; description is based on the title and citation metadata.)
• Elements met: A/B (app icons in a 3D launcher), F (3D app icons — claim 2).
• § 102 potential: Claim 2 — medium-high (3D app icon); claim 1 — medium, contingent on whether the PCT disclosure includes camera-tracked hand interaction and any controller-vs-hands distance variation (C–D), which I could not verify this session. This is the top verification priority among non-Meta references.

3.5 US 10,101,803 B2 — "Dynamic switching and merging of head, gesture and touch input in virtual reality" (family citation)

• Citation: US 10,101,803 B2; Google LLC; filed 2015-08-26; issued 2018-10-16.
• Description: A VR system that dynamically switches between and merges input modalities — head gaze, hand gestures, and touch/controller input — so a user can move fluidly between controller and body-based interaction in the same session.
• Elements met: A; the claim 12 prong of detecting a change in input device usage and responding with a different interaction paradigm.
• § 102 potential: Claim 12 — medium (mode-switching prong); claim 1 — low-medium. Key gaps: no verified disclosure of the same icon being repositioned closer for hand use vs controller use (C–D); no system-setting icon pairing.

4. Tier 2 — Direct-hand/direct-touch VR and 3D-icon art

4.1 US 2019/0026004 A1 — "Three Dimensional Icons for Computer Applications" (family citation)

• Citation: US 2019/0026004 A1; Chicago Labs, LLC; filed 2017-07-18; published 2019-01-24.
• Description: Computer-application icons rendered as 3D objects that users can manipulate in a 3D environment.
• § 102 potential: Claim 2 / 9 / 13 (3D-button presentation) — medium; claim 1 — low-medium. Key gaps: no verified hand-tracking/direct-press interaction or controller-comparison distance element (C–E).

4.2 US 2016/0004300 A1 — "System, Method, Device and Computer Readable Medium for Use with Virtual Environments"

• Citation: US 2016/0004300 A1; PinchVR Inc.; filed 2014-07-07; published 2016-01-07.
• Description: Interaction with virtual environments, including gesture-based selection/activation of virtual objects (PinchVR's core "pinch" interaction technology for VR).
• § 102 potential: Claim 12 — medium on E; claim 1 — low-medium. Key gaps: C–D (distance comparison / same-app dual icons) not evident from the title-level disclosure.

4.3 US 2020/026814 A1 — "Holographic palm raycasting for targeting virtual objects"

• Citation: US 2020/026814 A1; Microsoft Technology Licensing, LLC; filed 2019-01-11; published 2020-07-16.
• Description: A ray cast from the user's palm to target and interact with virtual objects — a hand-centric alternative to controller targeting in mixed reality.
• § 102 potential: Claim 12 — low-medium on E (hand-based targeting, but raycasting rather than direct push/press on the icon); claim 1 — low. Key gaps: ray-based targeting is not the claimed direct touch/press on the icon (E); no C–D distance-comparison disclosure.

4.4 US 2017/0336882 A1 — "Virtual/augmented reality input device"

• Citation: US 2017/0336882 A1; Google Inc.; filed 2016-05-17; published 2017-11-23.
• Description: Input devices for VR/AR including hand/wearable tracking for interacting with virtual content.
• § 102 potential: Claim 12 — low-medium. Key gaps: no verified disclosure of C–D (icon distance comparison tied to input mode for the same app).

4.5 US 2022/0086205 A1 — "Artificial reality collaborative working environments"

• Citation: US 2022/0086205 A1; Facebook Technologies, LLC; filed 2020-09-15; published 2022-03-17.
• Description: Collaborative artificial-reality workspaces with virtual content and app-related objects, hand/controller interaction.
• § 102 potential: Claim 1/8 — low-medium. Key gaps: no verified disclosure of the controller-vs-hand same-icon distance comparison (C–D).

4.6 US 11,086,392 B1 — "Devices, systems, and methods for virtual representation of user interface devices"

• Citation: US 11,086,392 B1; Facebook Technologies, LLC; inventors Ravasz, Butt, Witthuhn, Asemani, Pualuan, Ellis, Sztuk, Tickner; filed 2019-04-09; issued 2021-08-10.
• Description (verified from PDF): Communicatively coupling a UI device (e.g., smartphone/controller) to a VR device; displaying a virtual representation of the UI device and mirroring its content in VR so the user can interact with the physical device through the headset.
• § 102 potential: Claim 12 — low. The reference concerns virtualizing a physical UI device, not repositioning app icons for hand interaction; C–D and E (direct body-part push on a virtual app icon) are not disclosed.

5. Tier 3 — Older hand/body-part tracking and scrolling art (secondary, mostly dependent claims)

5.1 US 6,346,929 B1 — "Display apparatus which detects an observer body part motion in correspondence to a displayed element used to input operation instructions to start a process"

• Citation: US 6,346,929 B1; Canon Kabushiki Kaisha; filed 1994-04-22; issued 2002-02-12.
• Description: A display apparatus that detects motion of an observer's body part in correspondence with a displayed element to input an operation instruction (e.g., starting a process).
• § 102 potential: Claim 12 — low-medium (body-part-driven activation of a displayed element, element E in embryonic form). Key gaps: no VR environment, no controller-comparison distance (C–D), no app-launch/setting-activation specificity.

5.2 US 6,337,694 B1 — "Method and system for variable speed scrolling within a data processing system"

• Citation: US 6,337,694 B1; IBM; filed 1999-09-07; issued 2002-01-08.
• Description: Variable-speed scrolling in a GUI.
• § 102 potential: Only a secondary element — claims 3, 4, 14 (scrolling of a grouping of icons) as part of a combination; cannot alone anticipate any independent claim.

5.3 US 2013/0054319 A1 — "Methods and systems for presenting a three-dimensional media guidance application"

• Citation: US 2013/0054319 A1; United Video Properties, Inc.; filed 2011-08-29; published 2013-02-28.
• Description: A 3D media-guidance application presenting selectable content items in 3D.
• § 102 potential: Claim 1 — low (3D selectable content, but no VR hardware, no hand tracking, no C–D distance comparison).

5.4 US 2019/0146578 A1 — "Image display system, and control apparatus for head-mounted display and operation method therefor"

• Citation: US 2019/0146578 A1; Fujifilm Corporation; filed 2016-07-12; published 2019-05-16.
• Description: An HMD image-display system with a control apparatus — relevant as general HMD/VR context.
• § 102 potential: Low for all claims; no verified disclosure of the claimed hand-vs-controller icon-distance feature.

5.5 US 2020/0133453 A1 — "Near-viewing notification techniques" (Apple; filed 2018-10-31; pub. 2020-04-30)

• Description: Notification display for HMDs. § 102 potential: low.

5.6 US 10,943,395 B1 — "Dynamic integration of a virtual environment with a physical environment" (Virtex Apps, LLC; filed 2014-10-03; issued 2021-03-09)

• Description: Blending virtual and physical environments. § 102 potential: low.

6. Tier 4 — Peripheral GUI/display art (unlikely to anticipate any claim alone)

7. Remaining family citations (per "Families Citing this family" / family-cites list)

8. Overall ranking and litigation relevance

Most likely § 102 anticipation candidates (single-reference, claim-by-claim):

1. US 2022/0091722 A1 (Apple) — strongest for claims 1/8/12's direct hand interaction with a virtual control placed at the hand's location (elements A, B, E, and a partial C). Fails or is unverified on the same-app controller-vs-hands dual-placement concept (C–D).
2. US 2021/0405760 A1 (Meta; = US 11,256,336 B2) — strongest for claim 12's detect-no-controller → switch interaction mode prong; fails or is unverified on C–D.
3. WO 2022/047436 A1 (Innopeak) — strongest title-level match for claim 2's 3D app-icon button; full-text content unverified this session — highest verification priority.
4. US 11,086,406 B1 (Meta) — strongest for claim 1's direct hand-selection gesture element (E); no C–D.
5. US 10,101,803 B2 (Google, family) — strongest for input-mode-switching (claim 12 prong); no C–D.

Universal gap: No cited reference was verified to disclose the core distinguishing feature — the same application icon displayed at a different (closer) distance for camera-tracked hand interaction than for physical-controller interaction (claims 1, 8, 12 elements C–D), or the arm-length/height-based distance determination (claims 15–20). That is consistent with the examiner allowing all 20 claims over this exact citation set.

IPR2026-00460 tie-in (flagged per prior sections): Meta filed IPR2026-00460 (2026-08-26) against this patent, but the grounds are not yet public. The three Meta/Facebook references cited on the face of the '742 patent — US 2021/0405760 A1, US 11,086,406 B1, US 11,086,392 B1 — are the most probable candidates for the petition's § 102/§ 103 ground art, and should be the first references checked against PTAB E2E when the petition becomes public.

Verification caveats (explicit, per operating rules): Full-text verification this session covered US 11,086,406 B1, US 11,086,392 B1, US 2021/0405760 A1, and US 2022/0091722 A1 (PDF/analysis pages). For WO 2022/047436 A1, US 2019/0026004 A1, US 2016/0004300 A1, US 10,101,803 B2, and the Tier 3/4 references, descriptions rely on the citation metadata in the patent's own reference list and title-level knowledge; element-level anticipation conclusions for those should be confirmed against the full documents before being relied on in any IPR or § 102 argument. The authoritative source for the complete citation list is the Google Patents page for US 11656742 (provided in the prompt); USPTO Patent Center is the authoritative source for the examiner's search history and the NPL/patent citations as recorded.

I have strong detail on the Google '803, Meta '406, and Canon '929 references. Let me verify a few more key references before drafting the analysis.

I have sufficient verified detail on the dispositive references (Google '803, Meta '406, Canon '929) plus title-level detail on the launcher/3D-icon references. Below is the § 103 obviousness analysis, built exclusively from the prior-art pool cited on the face of US 11,656,742 B1.

Obviousness Analysis — US 11,656,742 B1 (35 U.S.C. § 103)

1. Scope of the claims (recap, for the § 103 analysis)

The three independent claims all share one core inventive predicate: the same selectable VR element (app icon and/or system-setting icon) is displayed at a different, closer distance for direct body-part (hand) interaction than the distance at which it is displayed for physical-controller interaction, and the element is activated by direct push/pull/tap/press/slide contact rather than by laser-pointing.

• Claim 1 — single app icon; closer for hand interaction than for controller interaction; direct-contact launch; both icons launch the same app.
• Claim 8 — app icon + VR-platform system-setting icon, same closer-position/direct-contact dual-mode scheme.
• Claim 12 — method: detect controller non-use/disuse → display body-interactive icon closer than the controller-mode icon → receive direct-touch input → launch app or activate setting.
• Dependents add: 3D-button presentation (2, 9, 13); up/down scroll arrows as pushable buttons (3, 4, 14); "within an apparent distance of a user's arm length" (5–7, 10–11); and distance determination from arm length, height, or average values (15–20).

2. Person having ordinary skill in the art (PHOSITA)

A PHOSITA at the June 1, 2022 priority date is a developer with a B.S./M.S. (or equivalent experience) in computer science/HCI and 2–4 years designing VR/AR input systems: headset-based camera hand tracking, controller input, gesture recognition, and spatial UI layout. Such a person would be intimately familiar with the Oculus/Meta Quest platform SDK (the patent's own background), Google Daydream/Cardboard toolkits, and the academic and patent literature on reach/touch interaction in VR.

3. The prior-art pool, by role

All references below are examiner-cited ("*") on the face of the '742 patent (or its family), so all are prior art under both pre-AIA and AIA frameworks (all published/granted well before June 1, 2022):

4. Combinations rendering the independent claims obvious

4.1 Claim 1 — Combination A: Google '803 + Meta '406 + Innopeak '436 (+ Canon '929)

Element mapping:

Motivation to combine (developed in § 6 below): Google '803 already supplies the entire architecture — same objects, two display distances keyed to input modality, direct-touch selection, camera-based hand tracking. The only gap is that '803's example objects are movie/book/game titles rather than "software application icons." Filling that gap with a VR app launcher (Innopeak '436; Chicago Labs '004) is an express, predictable substitution — launchers and media-selection lists are the same genus of selectable-icon interface, and Google '803 itself describes its list as "objects" to be selected and launched. Adding Meta '406's three-state gesture gating (or Canon '929's fingertip-trigger) to map a "pressing" hand motion to activation of the 3D icon is the textbook application of a known gesture-activation technique to a known icon object. Claim 1 is obvious over Google '803 + Innopeak '436 + Meta '406; Canon '929 is a strong alternative/backup primary for the direct-touch-to-launch element (it is an HMD + camera + fingertip-tracking reference dating to 1994).

4.2 Claim 8 — Combination B: Combination A + a settings-icon disclosure

Claim 8 adds only: (i) a VR-platform system-setting icon displayed together with the app icon, and (ii) the same closer/direct-touch treatment for both.

• VR launchers that display app icons and system settings (Wi-Fi, Bluetooth, brightness) in the same grid are routine; the '742 specification itself admits the setting-button embodiment ("a Wi-Fi settings button might change from a 2D to 3D display"). In the prior-art pool, US 2019/0384460 A1 (Microsoft, "Surfacing application functionality for an object") teaches surfacing application functionality (settings/actions) in an interface, and Meta '060 (integration of interaction modes) and US 2013/0054319 A1 (3D media guidance) teach heterogeneous selectable items (content + controls) in one 3D interface.
• Applying Combination A's identical closer-position/direct-touch logic to a settings icon is a one-step extension: there is no new inventive step in treating a settings button the same as an app button once the interface architecture is in place. Claim 8 is obvious over Combination A + Microsoft '460 (and/or Meta '060).

4.3 Claim 12 — Combination C: Google '803 as a near-anticipating primary

Claim 12's steps map almost one-for-one onto Google '803:

The only arguable delta is the trigger — '803 switches on a hand/arm gesture drawing the objects closer, whereas claim 12 detects controller disuse. But '803 already teaches that controller disengagement changes the active input mode (¶[0044]), and the patent's own background describes Quest 2 hand tracking auto-activating when the controller is set down. Selecting "controller set-down" as the trigger for a mode switch that the reference already performs is a predictable design choice, not an inventive step. Claim 12 is obvious over Google '803 alone, and a fortiori over Google '803 + Meta '406 + Innopeak '436.

4.4 Dependent claims

5. Motivation to combine — Graham/KSR framework

5.1 Same field, same problem. All primary references are analogous art in VR/AR input and spatial UI (USPC/CPC G06F 3/01, 3/048). Google '803, Meta '406, and Canon '929 all address the identical problem the '742 patent identifies: making selection of displayed objects in an immersive environment accurate and natural when the user's input modality changes (controller vs. hand). Meta '406's specification even opens by criticizing existing gesture systems for "inaccurately and often mistakenly interpret[ing] hand postures as input" — the same motivation recited in the '742 Background (slow/unreliable "laser hands").

5.2 KSR rationales that apply:

• Predictable combination of known elements (KSR, 550 U.S. at 416): Google '803 supplies the mode-aware far/near display architecture; Innopeak '436 supplies the app-launcher icons; Meta '406/Canon '929 supply direct-contact activation. Each element performs its known function in the combination. The result — an app launcher whose icons move closer and become directly touchable when the user drops the controller — is the predictable union of these three known functions.
• Simple substitution (KSR at 417): substituting "software application icons" for '803's title objects, and substituting direct-touch press (Meta '406; Canon '929) for '803's laser/beam selection, are substitutions of known elements for the same purpose, yielding predictable results.
• Obvious to try: once direct physical contact is the interaction metaphor, placing the contact targets within arm's reach is one of a finite number of identified, predictable solutions; the '742 dependent claims confirm the designer's latitude (arm length, height, average — "other distances… may be implemented… including user-selected distances," per the specification).
• Design need/market pressure: the Quest 2 hand-tracking launcher's poor laser-pointing UX (acknowledged in the '742 Background) is a known design need; the market-acknowledged fix — bring the buttons to the hand — is precisely what Google '803's reach/touch near-field mode already does.

5.3 No teaching-away. Nothing in Google '803, Meta '406, or Canon '929 discourages combining hand-tracking with a closer UI. To the contrary, Google '803 affirmatively teaches moving objects closer when switching to reach/touch mode ("to facilitate user interaction… the user may wish to draw the object(s) closer"), which is the very feature the '742 claims.

6. Secondary considerations

None are present in the record. There is no evidence of long-felt need, unexpected results, industry skepticism, copying, or commercial success tied to the claimed features. (The pending W.D. Tex. litigation and the two certificates of correction show the patent is being enforced, but enforcement activity is not an objective indicium of non-obviousness.) The strongest non-obviousness argument available to CurioXR would be an unexpected-results/nexus argument around the specific "closer than the controller-mode icon" placement — but that is precisely the feature Google '803 discloses in its far-field→near-field morphing, so the argument is weak.

7. Where the obviousness case is strongest and weakest

Strongest: Claims 12 and 15–20 (method + distance determination). Google '803 is nearly anticipatory: same objects, far/near display distances keyed to input mode, controller-disengagement changing modes, direct reach/touch selection, and distance chosen to put objects "within reach."

Weakest (the patent owner's best foothold): the claim-1/8 apparatus phrasing tying the closer display specifically to "a body part of the user that is tracked by a camera… to interact with the icon." Google '803's near-field mode is triggered by a user gesture rather than by continuous camera tracking of the body part for the interaction itself, although '803 does track the hand by camera 180 for the reach/touch interaction and Canon '929 is an explicit HMD-camera-tracks-fingertip reference. A challenger should combine Canon '929 (camera-tracked fingertip corresponding to the displayed element) with Google '803 (distance shift + mode switch) to close that gap squarely.

Caveat on two references: WO 2022/047436 A1 and US 2019/0026004 A1 were relied on for their disclosed subject matter (3D launcher/app icons; 3D app icons) based on their titles and examiner citation; I could not pull their full texts in this session. Their teachings are corroborated by independent references (United Video '319, Intel '129, Google '803) for the same limitations, so the combinations do not stand or fall on either one.

8. Practical tie-in (litigation/IPR posture)

This analysis matters today because of two live proceedings:

1. CurioXR v. Meta Platforms, Inc., 7:26-cv-00123 (W.D. Tex.) — Meta is accused of infringing claim 1 via the Quest "Direct Touch" hand interface. The accused feature (icons pulled closer to the hand and directly tapped) is the same design space as Google '803 + Meta '406 + Canon '929 — i.e., Meta's own and Google's earlier art is squarely on-point for the asserted claim.
2. IPR2026-00460 (Meta, filed 2026-08-26, pending) — the petition's grounds are not yet public, but the prior-art pool above is the natural source for its § 102/§ 103 grounds. The strongest § 103 ground available is the Google '803 + Canon '929 (+ Innopeak '436 / Meta '406) combination for claim 1, and Google '803 alone (or with Meta '406) for claim 12 of the parent '448 patent. Because no Final Written Decision exists, all 20 claims remain in force, and a non-Meta defendant should independently evaluate its own § 315(b) bar before relying on Meta's petition.

Bottom line: Independent claims 1, 8, and 12 are each vulnerable under § 103 on combinations drawn from the examiner-cited record — most powerfully Google '803 + Canon '929 + Innopeak '436 (+ Meta '406) for claims 1/8, and Google '803 (alone or + Meta '406) for claim 12 — with the "closer-to-the-tracked-body-part" limitation being the only claim element that requires a careful two-reference combination (Google '803's distance-shift plus Canon '929's camera-tracked fingertip) rather than a single-reference disclosure.