US 7237253

I'll search for the specific patent number and any CAFC 2026 docket activity.

Let me run additional targeted searches on litigation/appeal activity and the current assignee.

Search scope and method

I searched for the exact identifier 7,237,253 / US7237253 / US 7,237,253 B1 (and the literal strings "7,237,253" and "US-7237253") against patent databases surfaced via live web search (Google Patents, Unified Patents portal, uspto.report, PTAB/PTActs, courtlistener, govinfo CAFC dispositions) and against Adeia/Xperi SEC litigation disclosures. I did not have direct API access to USPTO PatentCenter or to the CAFC docket system, so the CAFC portion is a negative finding from search rather than a docket query.

Caveat up front: I found no CAFC 2026 docket entry, appeal, or oral-argument listing involving US 7,237,253, and no IPR/PTAB proceeding against it. Search hits that superficially matched were false positives and I am not treating them as this patent:

• JP 7237253 B1 — a Japanese patent (Mitsubishi Electric, "gas-insulated apparatus," registered 2023).
• A neuroscience citation to journal pages "7238 LP-7237253" (J. Neurosci. 25).
• Federal Circuit decisions on unrelated patents (e.g., the Spero v. Volkswagen line, Nos. 2025-1064/-1146/-1147, decided May 14, 2026 — U.S. Patent No. 10,894,503, not this patent).

This negative finding is consistent with the patent's status: it is recorded as Expired – Lifetime, with an anticipated expiration of 2020-04-27, so a 2026 CAFC appeal over this specific patent would be unusual (though not impossible, since appeals can outlast expiration). I cannot definitively rule out an unnoticed 2026 filing.

---

Identification

Family continuations/divisions (all sharing the 2000-04-27 priority): US 11/083,407 → US 7,506,352; US 11/083,722 → US 7,305,693; US 11/083,413 → US 7,523,478; US 11/171,747 → US 7,334,250; US 12/402,221 → US 7,818,768.

Prior art cited on the face (8 references): US 5,034,902; US 5,850,249; US 5,933,192; US 6,177,931; US 6,240,555; US 6,421,728; US 6,567,982; US 6,600,496.

---

Abstract (as issued)

"An interactive television system displays a television program having an associated channel. The system also displays an interactive television mode indicator if the displayed television program supports an interactive television mode. The interactive television mode is activated in response to a request from a viewer of the television program to activate the interactive television mode. The system updates a channel status list to indicate that the television program is being viewed in the interactive television mode. The system is also able to handle requests for activating an online television mode. When changing channels, the channel status list is used to restore a previously activated interactive television mode or online television mode for a particular television channel. Two different indicators may be displayed to indicate whether the television program supports an interactive television mode and/or an online television mode."

---

Plain-language overview of each independent claim

Claim 1 — Apparatus (interactive TV device with multi-tuner architecture).
An interactive TV device (e.g., set-top box) does four things: (a) displays a TV program; (b) shows an "interactive mode available" indicator when the program supports interactive TV mode; (c) when the viewer asks to go interactive, first checks a channel status list to see whether that program's channel is already in interactive mode — and only activates interactive mode if it is not; and (d) updates the channel status list to record that this program is now being viewed interactively. Hardware limitation: at least one video tuner for the displayed program plus a plurality of data tuners used to hold the interactive state of multiple channels at once.

Claim 2 — Apparatus (single video tuner + per-channel data tuners).
Same functional sequence as claim 1 (display → show indicator → on request, check the channel status list and activate only if not already interactive → update the list), but the hardware is recited differently: a video tuner for the current program and a plurality of data tuners, where each data tuner maintains the interactive state of a television program previously activated in interactive mode. In short: one video tuner, many data tuners, each data tuner preserving a different channel's prior interactive session.

Claim 3 — Computer-readable media (software claim).
A program on computer-readable media that causes a processor to: display a video program; display an interactive video mode indicator when supported, where a video tuner tunes the displayed program and separate data tuning devices maintain an interactive video status for each video channel; on a viewer request, check the channel status list and activate interactive mode only if the channel is not already in it; and update the channel status list. This is the software counterpart of claims 1/2, with the multi-tuner architecture folded into the mode-indicator step.

Claim 4 — Apparatus (video tuner + plural tuning devices per channel).
Functionally the same as claim 1 (indicator, check-list-before-activate, update list), but the hardware is stated more broadly: a video tuner to tune the displayed program plus "a plurality of tuning devices to maintain an interactive television status for each channel." Note the breadth difference: "tuning devices" rather than "data tuners," and "for each channel" rather than "multiple channels."

Claim 5 — Apparatus (near-duplicate of claim 2).
Textually almost identical to claim 2: display program → display indicator if supported → on request, check channel status list and activate if not already → update the list; hardware is a video tuner for the current program and a plurality of data tuners, each maintaining the interactive state of a program previously activated in interactive mode. The near-duplication of claims 2 and 5 (and the parallel 1/4 and 3/6 pairs) is consistent with a restriction requirement that later produced the four continuation/division filings listed above.

Claim 6 — Computer-readable media (near-duplicate of claim 3).
Display a video program; display an interactive video mode indicator when supported; on request, check the channel status list and activate if the channel is not already interactive; update the channel status list; where a video tuner tunes the displayed program and a separate data tuning device maintains an interactive video status for each video channel.

Common inventive thread across all six claims

1. Legacy persistence — interactivity state is remembered per channel in a "channel status list," so a viewer returning to a channel does not have to re-activate interactive mode (the problem expressly identified in the Background).
2. Activation independent of the on-screen indicator — the viewer can trigger interactive mode even after the indicator times out and disappears.
3. Multi-tuner maintenance — multiple data tuners (cheap) with a single video tuner (expensive) keep several channels' interactive sessions alive simultaneously. The specification's worked example: "one video tuner and ten data tuners ⇒ interactive state of eleven television channels simultaneously."

The specification also describes (unclaimed) subject matter: a separate "online TV mode" indicator for web page access, ATVEF 1.1 (draft) encoding of mode-availability data and indicator types, and automatic deactivation of interactive mode based on entry time (e.g., hourly).

---

Points of uncertainty / things I could not verify

1. No CAFC 2026 activity located for this patent. Reported as a search-based negative finding, not a docket-level confirmation.
2. Claim independence. I inferred that all six claims are independent from the absence of any "according to claim N" language in the claims as reproduced; independent verification against the USPTO full-text claims would be prudent.
3. Expiration date. The applied date (2020-04-27) implies no patent term adjustment, which is somewhat surprising for a 2000-filed/2007-issued patent. I did not verify a PTA certificate or any terminal disclaimer, so treat the exact expiration date as unconfirmed.
4. Current assignee. Both Microsoft/WebTV (original) and Adeia Technologies Inc. (current, per Google Patents) appear in the record; I did not verify the 2014 Rovi→Adeia corporate step in a primary assignment document.
5. A PTActs document (petition artifact ID referencing "US-7237253-") appeared in search results but could not be read in context; I cannot confirm what proceeding, if any, it relates to. I am not asserting a PTAB proceeding against this patent.

I'll search for litigation involving US patent 7237253.

Let me dig deeper with more targeted searches on litigation databases.

Summary of Findings

As of the search date, I was unable to identify any publicly documented litigation that specifically names U.S. Patent No. 7,237,253 ("User interface for interactive television systems") as an asserted patent-in-suit. I also found no CAFC appeal, IPR, or ITC proceeding in which US 7,237,253 is identified as the subject patent. I want to be explicit about the limits of this answer rather than fill the gap with speculation.

What I checked and found

Important distinction (so you don't over-read this)

• The frequently-returned cases — Rovi Guides, Inc. v. Comcast, No. 1:16-cv-09278 (S.D.N.Y.); Comcast Corp. v. Rovi Corp., No. 1:16-cv-03852 (S.D.N.Y.); Rovi Corp. v. Roku, Inc., No. 5:12-cv-02185 (N.D. Cal.); Rovi Corp. v. Hulu LLC, No. 2:12-cv-04756 (C.D. Cal.) — are Rovi-family litigations generally. I did not find confirmation that US 7,237,253 was among the asserted patents in any of them. Treating those as "litigation involving '253" would be an auto-correction-style inference, which the ground rules prohibit.
• The one hit that literally contains "US-7237253" (the IPR2019-01292 exhibit) is a prior-art search string, not an assertion of the patent.

Relevant ownership / status context (from the patent record)

• Original assignee: [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) / WebTV Networks, Inc. (filed 2000-04-27; granted 2007-06-26)
• Chain of title: reassigned to Microsoft Corp. (2014-06-04) → Rovi Technologies Corp. (2014-12-08) → current listed assignee Adeia Technologies Inc. (successor to Xperi/Rovi)
• Legal status: Expired – Lifetime, with an anticipated expiration of 2020-04-27. Any infringement action would have had to be filed before that date, and actively maintained to a decision — which shrinks the window for live litigation considerably.
• Family: continuation/division children US 7,506,352; US 7,305,693; US 7,523,478; US 7,334,250; US 7,818,768 (all sharing the 2000-04-27 priority date). If an '253 assertion exists, its siblings are worth checking for companion filings.

Bottom line

No known litigation against US 7,237,253 is confirmed on the public record I could access. If a case exists, it is likely (a) an older Rovi/Adeia assertion that pre-dates the 2020 expiration and is not well indexed by the portals, or (b) a sealed/consolidated docket where the patent is listed only in an exhibit.

Recommended next steps for a definitive answer

1. USPTO Patent Center / Assignment API — run a "patent → litigation" and "assignee → patent" cross-check to see which cases the '253 patent number was docketed in.
2. PACER Docket Search across the Rovi/Adeia parties (Rovi Guides, Rovi Technologies, United Video Properties, Adeia) filtered by 2014–2020, then pull complaints to confirm asserted patent numbers.
3. Unified Patents litigation caselist by party rather than patent number, since portal listings are sometimes keyed to the case, not the patent.
4. CAFC docket search for "7,237,253" and "7237253" to catch appeals.
5. Lex Machina / Docket Navigator (if you have access) — these index asserted-patent numbers directly and are the most reliable for "was this specific patent ever asserted?"

I should note two honest caveats: my web-search coverage of paywalled litigation databases (Lex Machina, Docket Navigator, PACER full-text) is incomplete, and I reached a tool-usage limit before exhausting all searches. So I can state with confidence that no litigation is readily findable for this patent, but I cannot positively rule out a sealed or poorly indexed case.

If you can provide access to PACER or Lex Machina, I can run the party-filtered searches and give you a definitive plaintiff/defendant/case-number/status table.

I'll verify the structured block's "no proceedings" default against live sources before writing anything up.

Search results are pulling up other "723" patents (10,263,723; 8,222,723; 8,243,723) rather than US 7,237,253. Let me run tighter queries to rule out PTAB activity before relying on the structured block's default.

Let me run two final confirmatory searches — one on litigation assertion history, one on any IPR naming this patent's owner family — before concluding.

Proceedings overview

One AIA trial proceeding count: zero (0). The structured PTAB block states that the USPTO Open Data Portal returns no AIA trial proceedings for US 7,237,253 as of the most recent ingest — no active IPRs, no claims-invalidated outcomes, no claims-sustained outcomes, no settlements, no institution denials — and my independent web searches surfaced no IPR, PGR, or CBM naming this patent. Bottom-line defensive posture for a defendant: the absence of PTAB activity is a data point, not a shield. Nothing has been canceled by the Board, so all 6 claims are nominally intact — but the far stronger defense here is temporal, not administrative: the patent expired on 2020-04-27, which means the § 286 six-year damages lookback (35 U.S.C. § 286) no longer reaches any date on which this patent was in force. As of today (2026-10-01), a complaint filed now can capture, at most, infringement occurring on or after 2020-10-01 — all of it post-expiration. That is a far more complete defense than any IPR could deliver.

No proceedings to itemize

There is no proceeding number to report, and I will not invent one. Instead, here is the verification record, because a negative finding is only as good as the search behind it.

Search performed: queries targeting the patent number paired with IPR/PTAB/petition terms, and queries targeting its title and its Rovi/Adeia owner family. Sources consulted: Google Patents (https://patents.google.com/patent/US7237253/en), the PTAB petition/documents repository at ptacts.uspto.gov, DocketAlarm PTAB case pages, and the Unified Patents patent portal (https://portal.unifiedpatents.com/patents/patent/US-[7237253](/patent/7237253)-B1).

High false-positive risk — do not confuse these with US 7,237,253. Every search returned look-alike patents, none of which is this patent:

A defendant's counsel vendor running a bare number-string search on "723" or "7253" will hit these. Confirm the full seven-digit number before relying on any of them.

Adjacent-but-not-this-patent. This patent sits in the WebTV/Microsoft → Rovi → Adeia family, and Rovi's portfolio was attacked heavily by Comcast (IPR2017-00941, IPR2017-00951, IPR2020-00787 through IPR2020-00798, IPR2020-00811, and the ITC 337-TA-1001 campaign). Those proceedings challenged other Rovi patents. I found no IPR naming 7,237,253 in any of them. The Unified Patents portal hosts a catalog profile page for US-7237253-B1; a portal profile is an indexing artifact, not a filed proceeding, and should not be treated as one.

Caveat on the negative finding. Web search and the ODP ingest are not complete historical indexes of every petition ever filed. If a petition was filed against this patent and terminated early (e.g., denied institution with minimal indexing, or settled pre-institution), it could be absent from both sources. I did not find one; I cannot prove one never existed.

Strategic summary

Claim status. No AIA trial has ever reached a Final Written Decision on US 7,237,253, so the Board has never canceled or sustained any of claims 1–6. All six claims — independent claims 1, 2, 3, 4, 5, and 6 as granted on 2007-06-26 — remain as issued. There are no "surviving claims narrowed by IPR" to list, because nothing was narrowed. The entire family (US 7,506,352, US 7,305,693, US 7,523,478, US 7,334,250, US 7,818,768) carries the same 2000-04-27 priority date and the same expired status.

Estoppel landscape. § 315(e)(2) estoppel is irrelevant here: estoppel attaches only after a Final Written Decision, and there has never been one. That cuts against a defendant in one narrow sense — no prior petitioner has burned any ground, so every § 102/§ 103 theory remains theoretically available. But it cuts against the patent owner in a much larger sense: the patent's 2020-04-27 expiration and the § 286 lookback have closed the damages window (as of 2026-10-01, the six-year reach extends only to post-expiration conduct), which moots the value of an IPR entirely. An IPR on an expired patent can still be instituted, but the Board cannot amend claims and the exercise is largely academic when no recoverable damages exist.

Pattern signals. No repeat petitioner exists because no petitioner exists. No defensive aggregator (Unified Patents, RPX, or similar) has filed here. The patent owner's family shows no PTAB appeal activity on this patent (nothing to appeal). The meaningful pattern signal is portfolio context: the same inventive family was commercialized by WebTV/Microsoft, monetized by Rovi, and is now held by Adeia Technologies Inc. — a large licensing operation whose patents do attract challenges. This particular patent escaping IPR while its siblings were litigated suggests it was either not asserted, not commercially central to the Rovi/Comcast and Rovi/Verizon campaigns, or was asserted in a forum with a resolution that never triggered an IPR.

Recommended next steps

First, check whether you have a case at all. Ask the asserting party for the accused acts and their dates. If every act postdates 2020-04-27, the patent is expired and 35 U.S.C. § 286 forecloses damages, and § 271(a) precludes injunctive relief for conduct occurring after expiration. A complaint filed on or after 2026-10-01 can reach only conduct from 2020-10-01 forward — entirely within the post-expiration period. This should be the lead argument in any responsive pleading, ahead of invalidity.

Second, do not spend IPR money first. There is no FWD to cite, no canceled claim to lean on, and an IPR cannot recover your fees when the real exposure is already extinguished by expiration. If the demand letter's economics are material and the expiration argument is somehow contested, the cheaper motions practice is a Rule 12 motion or summary judgment on the § 286 / expiration theory.

Third, if the patent owner nonetheless maintains a live theory, the art cited on the face of the patent is the natural starting set: US 5,034,902 (SRG), US 5,850,249 (Nielsen), US 5,933,192 (Hughes, multi-channel receiver with improved channel-changing response — directly on point for the "maintain interactive state across channels" claim element), US 6,177,931 (Index Systems), US 6,240,555 (Microsoft, supplemental interactive content with continuous video), US 6,421,728 (Intel), US 6,567,982 (BellSouth), and US 6,600,496 (Sun, interactive GUI for set-top box). Note that the multiple-tuner limitations in claims 1, 2, 3, 4, 5, and 6 are the structural heart of the claims and are the limitations most likely to be susceptible to § 103 attack — but pursue this only if the expiration defense fails, because it should not.

Fourth, verify the negative directly. Before treating "no PTAB activity" as settled for a filing, pull the patent's complete transaction history from USPTO Patent Center and run a PTAB E2E proceeding-number search by patent number, rather than relying on either the ODP ingest or a web search. Absence of PTAB activity is a weak signal standing alone; here it is dwarfed by the expiration and § 286 arguments, which are far more decisive.

I'll search for the recorded assignment data for this patent, focusing on reel/frame numbers and correspondents of record.

Let me try to pin down the specific reel/frame numbers and correspondents.

Let me pin down the specific reel/frame numbers and correspondents for the assignments in this chain.

Assignment Record — US 7,237,253 "User interface for interactive television systems"

Scope note / honesty flag. I was able to verify the post-2014 reel/frame entries and several correspondents from indexed USPTO assignment records (via Plainsite and mirrored Google Patents/Dimensions legal-event data). I could not retrieve the reel/frame numbers for the three earliest recordings (inventors→WebTV, WebTV→Microsoft, Microsoft→Rovi Technologies) before hitting tool limits. Where a reel/frame is not verified I say so explicitly rather than inventing one. This does not contradict the earlier litigation summary — it refines it: the earlier note that current assignee is "Adeia Technologies Inc." is consistent with the chain below.

Inventors

All four signed the original assignment to WebTV Networks, Inc., recorded 2000-10-16 (assignors listed on the record: BLACKKETTER, DEAN J.; WHITE, CHRISTOPHER M.; YAKSICK, JEFFREY D.; PARK, TIMOTHY F.).

Unusual-pattern note (flagged, not asserted): This is a WebTV-era engineering team, and WebTV was acquired by Microsoft in 1997 — i.e., the inventors were already employees of a parent-company subsidiary at filing. That is the opposite of a "founders depart before fire-sale" pattern, but it does mean the patent sat inside a large operating company (Microsoft) for ~14 years. I could not verify individual inventor departure dates; I am not going to guess them.

Original assignee

• Entity named on the issued patent: Microsoft Corp. (per Google Patents "Original Assignee"); the first recorded assignee was WebTV Networks, Inc., which was the assignee-of-record when the application was filed and prosecuted. The two are the same corporate control (Microsoft acquired WebTV in 1997 for ~$425–503M and ran it as a division, later MSN TV).
• Primary line of business: WebTV Networks built the WebTV Internet terminal / set-top box and ran the associated online service — a hardware + service operating company. Microsoft is a diversified software/hardware operating company.
• Did they ship a product embodying the claims? Yes, arguably: the spec itself states "the interactive television device is a WebTV® Internet terminal manufactured by WebTV Networks, Inc., a subsidiary of Microsoft Corporation" (FIG. 5 discussion), and the ATVEF 1.1 broadcast-data mechanism described is WebTV-era technology.
• Current status: WebTV/Microsoft operating business — Microsoft continues as a going concern; the WebTV brand was retired (MSN TV shut down 2013). The patent has since left Microsoft (see timeline).

Assignment timeline

Reel/frame entries marked "NOT VERIFIED" could not be pulled before I hit the tool-usage ceiling. All others are taken from indexed USPTO records.

• 2000-04-27 (executed ~filing) / recorded 2000-10-16 — Reel NOT VERIFIED

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Blackketter, Dean J.; Park, Timothy F.; White, Christopher M.; Yaksick, Jeffrey D. (joint inventors)
  • Assignee: WebTV Networks, Inc.
  • Correspondent: not captured (WebTV/Microsoft in-house or outside counsel of record — verify on Assignment Center)
  • Context: standard inventor→employer assignment at filing.

• 2014-06-04 (recorded) — Reel NOT VERIFIED

  • Conveyance: Merger (see document for details)
  • Assignor: WebTV Networks, Inc.
  • Assignee: Microsoft Corporation
  • Correspondent: not captured
  • Context: internal corporate reorg / merger of the WebTV subsidiary into the Microsoft parent — a change of name/ownership only, not a monetization event.

• 2014-12-08 (recorded) — Reel NOT VERIFIED

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Microsoft Corporation
  • Assignee: Rovi Technologies Corporation
  • Correspondent: not captured
  • Context: true divestiture — Microsoft transferred this patent (with a large WebTV/IPTV-related portfolio) to Rovi. This is the pivotal link: an operating company exiting a patent family into a company whose core business includes patent licensing.

• 2019-11-22 (executed) / recorded 2019-11-25 — Reel 051143/0468

  • Conveyance: Security Interest
  • Assignors: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
  • Assignee: HPS Investment Partners, LLC, as Collateral Agent (New York)
  • Correspondent: security-interest filings in this family went through Cogency Global Inc. (see recurrence note below)
  • Context: securitization — the patent pledged as collateral in a debt facility.

• 2019-11-22 (executed) / recorded 2019-11-25 — Reel 051110/0006

  • Conveyance: Patent Security Agreement
  • Assignors: same Rovi/TiVo group as above
  • Assignee: Morgan Stanley Senior Funding, Inc., as Collateral Agent (Maryland/NY)
  • Correspondent: Stewart Walsh, Cogency Global Inc., 1025 Vermont Ave NW, Suite 1130, Washington, DC 20005 (as recorded on assignment 051110/0006)
  • Context: securitization — parallel collateral pledge alongside the HPS interest.

• 2020-06-01 (effective) / recorded 2020-06-05 — Reel 053458/0749

  • Conveyance: Release by Secured Party
  • Assignor: HPS Investment Partners, LLC (collateral agent)
  • Assignees: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
  • Correspondent: Monique L. Ribando, Skadden Arps Slate Meagher & Flom LLP, One Manhattan West, New York, NY 10001-8602
  • Context: release of security interest (payoff/refinancing).

• 2020-06-01 (effective) / recorded 2020-06-05 — Reel 053481/0790

  • Conveyance: Release by Secured Party
  • Assignor: Morgan Stanley Senior Funding, Inc. (collateral agent)
  • Assignees: same Rovi/TiVo group
  • Correspondent: Skadden Arps Slate Meagher & Flom LLP (Monique L. Ribando)
  • Context: release of security interest.

• 2020-06-01 (effective) — Reel 053468/0001

  • Conveyance: Security Interest
  • Assignors: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; and others
  • Assignee: Bank of America, N.A. (North Carolina)
  • Correspondent: not captured
  • Context: securitization — new collateral pledge replacing the released HPS/Morgan Stanley facilities.

• 2022-08-15 (effective) / recorded — Reel 069085/0599

  • Conveyance: Change of Name
  • Assignor: Rovi Guides, Inc. — Assignee: Adeia Guides Inc.
  • Correspondent: not captured
  • Context: change of name only. ⚠️ Caveat: this recorded name change is for Rovi Guides, Inc., not for Rovi Technologies Corporation, which is the entity that holds '253 in this family. The Google Patents "current assignee" field for '253 lists Adeia Technologies Inc., implying a parallel Rovi Technologies → Adeia Technologies name change that I did not independently verify by reel/frame. Treat the "Adeia" end-state as corroborated by the assignee field but not by a specific reel/frame for the '253 holder.

If you want the three missing early reel/frames (2000, 2014×2): they are retrievable directly at the USPTO Assignment Center by searching patent number 7237253 — that query returns the full reel/frame set, which the indexed mirrors I reached do not expose for the pre-2014 entries.

Timeline diagram

timeline
    title Ownership of US 7237253
    2000 : Filed 27 Apr by four WebTV inventors
         : Assigned to WebTV Networks Inc
    2014 : WebTV merged into Microsoft Corp
         : Microsoft assigns to Rovi Technologies Corp
    2019 : HPS and Morgan Stanley take security interests
    2020 : Security interests released
         : Bank of America takes new security interest
    2022 : Rovi Guides renamed Adeia Guides Inc

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The patent moved owner-to-owner between real corporations (WebTV → Microsoft → Rovi Technologies). Rovi Technologies Corporation is an established, publicly documented operating/licensing corporation (Rovi/TiVo), with physical addresses of record (2830 De La Cruz Blvd, Santa Clara, CA) — not a registered-agent mail drop. No single-purpose Delaware/Texas LLC appears anywhere in the chain.

2. Known asserter in the chain — present (with a caveat). The 2014-12-08 assignee, Rovi Technologies Corporation, sits inside the Rovi/Rovi Guides litigation group that has been one of the highest-frequency patent plaintiffs in the interactive-TV/EPG space — asserting against Comcast, Hulu, Roku, Netflix, and Haier in dockets catalogued by Relecura and in ITC Inv. No. 337-TA-845. Those parties appear in public litigation datasets and in Unified Patents/RPX indexes as frequent filers. Caveat: I have not confirmed that '253 itself was ever asserted (consistent with the earlier litigation summary), and Rovi/Adeia is not on the classic enumerated NPE list (Acacia, Marathon, IV, Wi-LAN, Conversant, etc.). So this is a "known large-scale litigant/licensor" finding, not a "classic troll" finding.

3. Repeat correspondent across the chain — not present (but noted). Two correspondents recur within the 2019–2020 links: Stewart Walsh / Cogency Global Inc. (security-interest recordings, e.g. 051110/0006) and Skadden Arps (Monique L. Ribando) (the 53458/749 and 53481/790 releases). These are the same firms acting for the same corporate group across pledging and releasing, which is ordinary financing-housekeeping, not the "one lawyer running many unrelated shell LLCs" pattern the rubric targets. No low-profile attorney recurs across different assignee entities here.

4. Cascading transfers — not present. No run of consecutive assignments through chained LLCs in <24 months. The chain is short (three real transfers) and spread across 2000–2014.

5. Pre-litigation transfer — unclear. The Microsoft → Rovi Technologies transfer (2014-12-08) preceded Rovi's major 2016 Comcast suits and the earlier 2012 Netflix/Hulu suits. That timing is consistent with arranging a monetization vehicle, but because '253 is not confirmed as an asserted patent, I cannot tie this specific transfer to a specific suit. Marked unclear, not present.

6. Bankruptcy fire-sale — not present. Neither Microsoft nor Rovi/Adeia filed Chapter 7/11. The Microsoft → Rovi transfer was a negotiated portfolio sale, not a distressed sale, and no bankruptcy docket appears.

7. Privateering — unclear / worth flagging. Microsoft (a large operating company) divesting a WebTV-derived patent family to Rovi — a company whose business model includes large-scale patent licensing and which then litigated broadly in the same IPG/ITV space — has the shape of privateering. However, I could not verify the elements that would make it a finding: a revenue-share between Microsoft and Rovi, or targeting of Microsoft's own competitors. Do not treat this as proven.

8. Defensive aggregator (anti-NPE) — not present. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. It terminates in a licensing-side corporate family (Rovi Technologies / Adeia). The 2019–2020 security interests and their releases are financing, not neutralization.

Verdict

NPE — moderate confidence.

Justification (2–3 sentences, with the specific entries driving it): The chain shows a clean divestiture out of an operating company — Microsoft's 2014-12-08 assignment to Rovi Technologies Corporation — landing the patent in a corporate family (Rovi → Adeia) whose income derives materially from patent licensing and which is a documented high-frequency litigant in interactive-TV/EPG (Comcast, Hulu, Roku, Netflix dockets). That transfer plus the current licensing-company ownership is one strong and one weak signal, supporting "moderate" rather than "high." I am not calling it "high confidence" because there is no classic shell-LLC, no confirmed assertion of '253 itself, and Rovi/TiVo is a hybrid operating-plus-licensing entity rather than an anonymous shell — so the earlier "no confirmed litigation against '253" finding still stands and constrains the call.

Verify at: USPTO Assignment Center — https://assignment.uspto.gov/patent/index.html (search patent 7237253 or application 09/560,666). This is the authoritative source for the three reel/frames I could not confirm above (2000-10-16, 2014-06-04, 2014-12-08).

I'll work from the authoritative patent text (which lists the 8 face citations) and run targeted searches to verify each reference's details and relevance.

Let me verify the remaining four cited references.

Prior-Art Analysis — US 7,237,253 B1 ("User interface for interactive television systems")

Scope note. Per the operating rules, I worked from the authoritative patent text supplied in the user message (which reproduces the face of the patent, including its "Patent Citations (8)" list) and verified the individual references against USPTO-family data surfaced by live search. The identifier 7,237,253 / US 7,237,253 B1 / US09/560,666 resolves to this U.S. patent only — I am not importing the JP 7237253 B1 (Mitsubishi Electric, gas-insulated apparatus) hit, which is a false positive flagged in the earlier sections.

This section builds on the identification table and claim summary already produced; it does not repeat them. It also assumes the patent's Expired – Lifetime status (anticipated expiration 2020-04-27) that the earlier sections established.

---

1. Legal framework and the critical date

US 09/560,666 was filed 2000-04-27, i.e. pre-AIA (before 2013-03-16), so pre-AIA 35 U.S.C. § 102 governs. Because there is no earlier priority claim, the effective critical date is 2000-04-27 for most purposes, making:

• § 102(b) art = references patented or published before 1999-04-27 (more than one year before filing).
• § 102(e) art = U.S. patents/applications "by another" filed before the applicant's invention (here, effectively before 2000-04-27), even if they issued later.

Every one of the 8 face citations predates the filing date in its filing/priority event and therefore qualifies as prior art in some § 102 category. Two important structural facts drive the analysis:

1. Every claim (1–6) recites the same two functional limitations — (a) "checks a channel status list to see if a channel associated with the television program is currently in the interactive television mode, and if not, … activates," and (b) "updates a channel status list to indicate that the television program is being viewed in the interactive television mode."
2. Every claim (1–6) also recites a multi-tuner hardware limitation (video tuner + a plurality of data tuners/tuning devices).

As shown below, no single cited reference discloses the check-before-activate / channel-status-list logic combined with the multi-tuner architecture. Consequently, none of the 8 references appears to anticipate any claim in full; several are strong § 103 (combination) or § 102(e) references. I state that conclusion explicitly rather than over-mapping claims.

---

2. Master table of cited references

* The '982 has an earlier-issued BellSouth sibling, US 5,818,438 (Howe et al.), issued 1998-10-06, filed 1995-04-25 — which independently qualifies under § 102(b) (before 1999-04-27) and shares the same specification subject matter. I flag the sibling because it is arguably the more dangerous anticipatory reference for the same disclosure, and it is not separately listed on the '253 face.

---

3. Reference-by-reference analysis

1. US 5,034,902 — SRG (audience measurement)

• Full citation / dates: US 5,034,902 A; priority 1986-12-09; issued 1991-07-23. § 102(b).
• Description: System for ascertaining the viewing/consumption habits of a test population — a metering model, not an interactive-television system.
• Claims potentially anticipated (§ 102): None. It discloses no interactive-mode indicator, no channel status list, and no multi-tuner architecture.

2. US 5,850,249 — Nielsen Media Research (receiver monitoring with local encoding)

• Full citation / dates: US 5,850,249 A; priority 1995-10-12; issued 1998-12-15. § 102(b).
• Description: Monitors a receiver's tuning state and locally encodes the monitored data (audience-measurement lineage).
• Claims potentially anticipated (§ 102): None. It touches "monitoring which channel the receiver is tuned to," but discloses nothing about interactive mode activation, indicator display, or a channel status list of interactive modes.

3. US 5,933,192 — Hughes Electronics (multi-channel receiver) ★ key for the tuner limitation

• Full citation / dates: US 5,933,192 A; priority 1997-06-18; issued 1999-08-03. § 102(b).
• Description (verified): A multi-channel digital video receiver (DBS) with a tuning unit containing two (or more) tuner modules and an equal number of decoder modules. One tuner/decoder set processes the channel currently selected by the user; a microcontroller predicts the next channel and drives the other tuner/decoder set to pre-tune it so channel changes are faster. A third set can be added for a further predicted channel.
• Claims potentially relevant: This is the closest cited art to the multi-tuner hardware element that appears in every claim — "a plurality of data tuners to maintain an interactive state of multiple channels" (claims 1, 2, 5, 6), "separate data tuning devices [that] maintain an interactive video status for each video channel" (claims 3, 6), and "a plurality of tuning devices to maintain an interactive television status for each channel" (claim 4).
• § 102 assessment: Does not anticipate any claim. '192 is about video tuning for channel-change latency, not retaining interactive-session state per channel, and it discloses no channel status list, no interactive-mode indicator, and no viewer-triggered activation. It is a strong § 103 reference against the tuner clauses when combined with an interactive-content reference (e.g., '555 or '982).

4. US 6,177,931 B1 — Index Systems / Gemstar (EPG control interface)

• Full citation / dates: US 6,177,931 B1; Appl. No. 09/120,488 filed 1998-07-21; priority 1996-12-19; issued 2001-01-23. § 102(e) (filed by another before 2000-04-27).
• Description (verified): An advanced EPG providing improved viewer interaction, video-recording control of future programming, navigation features, parental control, program-information access, advertising windows, viewer profiles, and customized advertising — built on the Levine/WO 96/07270 EPG lineage.
• Claims potentially relevant: Background art for the indicator / program-information / advertising-display environment. Supports an obviousness case for displaying a mode indicator keyed to program metadata.
• § 102 assessment: Does not anticipate any claim. The '931 disclosure is an EPG/advertising/recording-control interface; it does not disclose a per-channel status list of active interactive modes checked before activation, nor multi-data-tuner maintenance of interactive state.

5. US 6,240,555 B1 — Microsoft (Shoff et al.) ★ closest overall

• Full citation / dates: US 6,240,555 B1; priority 1996-03-29; issued 2001-05-29. § 102(e) (different inventive entity; assigned to Microsoft).
• Description (verified): Interactive entertainment system that presents supplemental interactive content alongside continuous video. An EPG stores a data field indicating whether the program is interactive (with a pointer/URL to the target resource). When the viewer tunes to a channel, the viewer computing unit consults the EPG to determine whether the present program is interactive; if so it launches a browser, "depicts a small icon or other indicia to alert the viewer that the program is interactive," and the viewer clicks/activates the icon to enter the interactive mode and display the supplemental content (or the content auto-displays).
• Claims potentially relevant: This maps closely onto the first two functional steps common to all six claims — (i) display the program, and (ii) "displays an interactive television mode indicator if the displayed television program supports an interactive television mode," plus (iii) "in response to a request from a viewer … [enter] the interactive television mode." It is the single most on-point reference for the indicator + viewer-initiated activation concept, and it also shows the "consults stored metadata on tuning" behavior.
• § 102 assessment: Does not fully anticipate any claim, because it does not disclose (a) checking a channel status list to see whether the channel is already in interactive mode before activating, nor (b) updating a channel status list on activation, nor (c) the plurality of data tuners maintaining per-channel interactive state. It is the best § 103 primary reference, combinable with Hughes '192 (tuners) and/or BellSouth '982 (stored channel identity / re-tune) to reach the claim sets.

6. US 6,421,728 B1 — Intel (upstream/downstream device architecture)

• Full citation / dates: US 6,421,728 B1; priority 1997-12-31; issued 2002-07-16. § 102(e).
• Description: Architecture for communicating with and controlling separate upstream and downstream devices — network/device-control plumbing.
• Claims potentially anticipated (§ 102): None. No interactive-mode indicator, no channel status list, no multi-tuner interactive-state maintenance.

7. US 6,567,982 B1 — BellSouth (Howe et al.) ★ closest on "session + stored channel"

• Full citation / dates: US 6,567,982 B1; priority 1995-04-25; issued 2003-05-20. § 102(b) via the family (see note); sibling US 5,818,438 (issued 1998-10-06) is the § 102(b)-dated member.
• Description (verified): Provides interactive television services and switches between programs. Television programming is accompanied by a signal indicating the availability of other programming, such as an interactive television service related to the program being viewed, plus information for requesting it. The user, notified by this signal, inputs a request to the set-top box for the second (interactive) program. "The identity of the original program channel is stored," and a session is established; when the session is terminated the set-top box re-tunes to the original program channel. The related '438 disclosure adds the step of the STB overlaying a standard button over the broadcast image, setting a timer to remove the button, and after viewer selection storing the current broadcast channel and establishing the interactive session.
• Claims potentially relevant: Strongest cited art for: the interactive-mode indicator/notification, the viewer request to activate, and recording channel identity so state can be restored. It bears on the claims' "indicator" and "activation" steps (all claims) and on the concept of channel-associated state (claim 1/2/4/5 "channel status list" concept).
• § 102 assessment: Does not fully anticipate any claim. Critically, '982/'438 store the currently tuned channel for re-tune on session end — a single-channel bookmark, not a channel status list consulted to test whether a channel is currently in the interactive mode before activating, and it does not update a status list recording that the program "is being viewed in the interactive television mode." It also discloses no multi-data-tuner architecture. Very strong § 103 reference; partial § 102(b) mapping only.

8. US 6,600,496 B1 — Sun Microsystems (interactive GUI for STB)

• Full citation / dates: US 6,600,496 B1; priority 1997-09-26; issued 2003-07-29; published internationally as WO 99/17549 (1999-04-08). § 102(e).
• Description (verified): GUI for a set-top box with a web browser and Internet data connection. The GUI generates menu screens superimposed over TV video and "animated on-screen notifications of the presence of interactive content, such as hypertext links to World Wide Web pages, which may be associated with television content currently being received." Data indicating availability of interactive content may be carried in the VBI of the TV signal or on the data path; the user presses a remote button to open an information panel with "Get Info" to download the content; a two-state progress indicator shows download progress; a "Previous Info" button recalls prior interactive pages.
• Claims potentially relevant: Strong art for the "interactive/online mode indicator" and for the VBI-embedding of availability data and indicator/notification types — i.e., the unclaimed specification subject matter (separate online-mode indicator; indicator-type encoding) as well as the indicator step in all six claims. The progress/"Get Info" flow also parallels the '253 "bar display" activation-progress figure.
• § 102 assessment: Does not anticipate any claim. '496 discloses notification of available interactive content and user download, but not a channel status list checked to determine whether the channel is already in interactive mode, not updating such a list, and not multi-data-tuner state maintenance.

---

4. Synthesis — where the claims are actually vulnerable

No cited reference anticipates any claim, alone or as reproduced on the face. The patent's asserted point of novelty is a combination: (1) an indicator that the program supports an interactive mode + (2) viewer-initiated activation gated by a check of a per-channel status list + (3) updating that list + (4) a video tuner plus a plurality of data tuners / tuning devices maintaining interactive state across channels. The cited art splits cleanly across that combination:

Most probable § 103 combinations a challenger would run:

1. US 6,240,555 (indicator + viewer-activated interactive mode) + US 5,933,192 (plural tuners) → all claims 1–6.
2. US 6,567,982 / 5,818,438 (availability signal + request + stored channel + re-tune) + US 5,933,192 (plural tuners) → all claims 1–6.
3. Either of the above, further in view of US 6,600,496 for the indicator/notification and progress patterns, and US 6,177,931 for EPG metadata-driven display.

Claim groups: claims 1/2/4/5 (apparatus) and 3/6 (computer-readable media) rise and fall together on the same functional core; the only meaningful differentiators among them are the hardware recitations — claim 4's broader "plurality of tuning devices … for each channel" and claim 3/6's "separate data tuning devices maintain an interactive video status for each video channel." Because '192 already shows plural tuner/decoder modules, those hardware clauses are the weakest part of the claims; the check-before-activate / channel-status-list clauses are the strongest (no cited art discloses them).

---

5. Caveats and limits (stated explicitly)

1. Citations listed are only the face citations. USPTO's "References Cited" listing is examiner/attorney-selected and is not exhaustive. The BellSouth sibling US 5,818,438 (§ 102(b), issued 1998-10-06) is materially the same disclosure as '982 and is not separately listed — a reviewer should treat the '438/'982 BellSouth family as a single, serious art unit. Likewise, the Microsoft '555 family (e.g., published US 2005/0015815 A1 / US 7,757,254, identified in my verification search) shares the same specification.
2. "Potentially anticipates under § 102" is deliberately worded. I found no reference that anticipates any of claims 1–6 as a whole. Where I say a reference is "relevant to" a claim, that reflects element-level overlap and likely § 103 use, not full anticipation. I am not asserting anticipation where the record does not support it.
3. Date precision. For § 102(e) references (US 6,177,931; US 6,240,555; US 6,421,728; US 6,600,496), the operative date is the U.S. filing/priority date, which I took from family data rather than a certified file-history copy; a § 102(e) date can shift with provisional/CIP chains. Verify against the actual file wrappers before relying on these dates in a validity opinion.
4. Source. Bibliographic and claim data were taken from the authoritative patent text provided; reference descriptions were verified against Google Patents and USPTO/PTAB-hosted copies surfaced by search (e.g., US 6,240,555, US 6,567,982, US 6,600,496, US 5,933,192). I hit the tool-usage limit before completing independent verification searches for US 5,034,902, US 5,850,249, and US 6,421,728; my characterizations of those three rest on their titles/assignees and family data and should be read as provisional.
5. No error-correction of identifiers. Nothing in the '253 record required reinterpreting a patent number; the only superficially matching non-U.S. identifier (JP 7237253 B1) is excluded, consistent with the earlier sections.

If you want, I can build the element-by-element claim chart (claim 1 vs. '555 + '192, and claim 1 vs. '982/'438 + '192) in a formal two-column format for an invalidity-contentions appendix.

I'll ground the obviousness analysis in the actual disclosures of the cited prior-art references before mapping them to the claims.

Let me examine the remaining cited references, especially the multi-tuner and interactive-GUI ones.

Now the remaining references — the data-path/upstream architecture and the audience-measurement ones.

Obviousness Analysis — U.S. Patent No. 7,237,253 B1

"User interface for interactive television systems" (35 U.S.C. § 103)

---

0. Bottom line up front

The six claims of the '253 patent are, in my analysis, vulnerable to a § 103(a) challenge built from the eight references already of record — chiefly Shoff et al. (US 6,240,555) and/or the Sun Microsystems '496 reference (US 6,600,496, published as WO 99/17549) as the primary teaching of the "interactive mode indicator + viewer-activated interactive session," combined with:

• Crosby et al. (US 5,933,192) for the plural-tuner / simultaneous multiple-channel architecture, and
• Alexander et al. (US 6,177,931), Nielsen (US 5,850,249) and/or SRG (US 5,034,902) for the per-channel status record that is consulted and updated, and
• Intel (US 6,421,728) for the separate upstream/downstream (data) device architecture.

The single most important weakness in the claims is that the asserted point of novelty — check the channel status list before activating; activate only if not already interactive; then update the list — is a routine data-management step applied to a lookup that the primary references already perform on every channel change. Under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), that is a classic "predictable use of prior art elements according to their established functions."

I also flag one significant defensive caveat below (§ VII): US 6,240,555 is Microsoft-owned, and the '253 application was filed by Microsoft's WebTV Networks subsidiary, so pre-AIA § 103(c) may disqualify it as § 103 art to the extent it is only available under § 102(e). That caveat does not apply to the Sun, Hughes, Index Systems, or Intel references.

---

I. Legal framework and construction

Governing law. The application was filed 2000-04-27 and has never been amended into the AIA regime; the claims are governed by pre-AIA § 103(a). Obviousness is assessed as of the effective filing date (2000-04-27), from the perspective of a PHOSITA, using the Graham v. John Deere factors: scope and content of the prior art, differences between the prior art and the claims, level of ordinary skill, and secondary considerations. MPEP § 2143 supplies the four rationales applied below.

Procedural posture. Per the earlier sections of this analysis, the patent is Expired – Lifetime (anticipated expiration 2020-04-27) with no readily findable litigation or appeal. This § 103 study is therefore retrospective/defensive rather than tied to a live IPR — and it matters because a claim term in an expired patent is construed under Phillips v. AWH with no amendment-driven narrowing of the "broadest reasonable interpretation."

Key terms.

---

II. Level of ordinary skill in the art

A PHOSITA here would hold a B.S. in EE/CS (or equivalent) plus roughly 2–3 years of interactive-television/set-top-box development experience, or equivalent practical experience, and would be familiar with: (i) DBS/cable receiver and multi-tuner front-end design; (ii) EPG data structures (channel/program records, URLs/pointers); (iii) browser-based interactive TV transports (VBI-embedded data, ATVEF); and (iv) consumer remote-control interaction models. The art is highly predictable and incremental (GPAC factor 5) — which favors the obviousness case.

---

III. The prior art of record and how each is available

The "Prior Art"/Citations section of the page lists eight examiner-cited references. Treating each literally:

Anomaly (reported literally, not auto-corrected). The page also lists under "Family Cites Families (1)" the reference US5860249A — "Plant watering container," International Plant Breeding AG, priority 1996-06-12. Taken literally it is irrelevant to this art and is almost certainly a database artifact (note its adjacency to US 5,850,249). Under the operative rule I neither correct nor rely on it.

---

IV. Combination A — primary reference US 6,600,496 (Sun), published as WO 99/17549

This is the cleanest § 103 attack because the Sun reference is unambiguously § 102(b) art (PCT publication 1999-04-08) and is third-party, so no § 103(c) disqualification is available to the patentee.

Claim 1

Claims 2 and 5 (near-duplicates)

The added limitation is "each of the plurality of data tuners maintains an interactive state of a television program previously activated in the interactive television mode." Crosby's per-channel tuner/decoder modules supply the architectural capability (N tuner modules, N decoded channel streams, the non-displayed one kept tuned to a predicted channel); the '496/'555 session launches supply what is being maintained. Combining them yields a one-session-per-tuner mapping as a predictable, mechanical allocation — one tuner per live session. The specification's own worked example ("one video tuner and ten data tuners ⇒ … eleven television channels simultaneously") is not an unexpected result; it is arithmetic on Crosby's architecture.

Claims 3 and 6 (computer-readable-media counterparts)

These recite the same method with the added architecture clause folded in ("separate data tuning devices maintain an interactive video status for each video channel" — claim 3; singular "a separate data tuning device maintains" — claim 6). Where the underlying process is obvious, its implementation as a program on computer-readable media is likewise obvious (the Beauregard line; MPEP § 2106). Note the claim-3/claim-6 and claim-2/claim-5 near-duplication — a patentee argument that these separately define patentable subject matter is undermined by their text.

Claim 4 (broadest)

"a video tuner … and … a plurality of tuning devices to maintain an interactive television status for each channel." The narrower "data tuner" recitations are replaced by the broader "tuning devices," and the plurality is now expressly "for each channel." This is the easiest claim to invalidate: Crosby discloses per-channel tuner modules for multiple channels, and '496/'555 supply the interactive status that is maintained. Claim 4 reads on the combination almost directly.

---

V. Combination B — primary reference US 6,240,555 (Shoff/Microsoft)

Shoff is, in some respects, the closer reference: it expressly discloses the tune-to-channel → consult EPG → determine interactive → launch interactive session loop, plus the on-screen icon and viewer activation. It maps to the claims as follows:

• Indicator → "a small icon or other indicia to alert the viewer that the program is interactive."
• Activation → "the viewer can click on or otherwise activate the icon to enter the interactive mode."
• "Check the channel status list" → Shoff's unit consults the EPG each time the viewer tunes to a channel; the EPG holds the per-program interactive field and the target URL — exactly the data stored in the '253 channel table's columns 352/354.
• "Update the list" and multi-tuner → supplied by '931 / '249 / '902 and Crosby / '728, as above.

The § 103(c) problem. US 6,240,555 is assigned to Microsoft Corporation; the '253 application was filed by, and assigned to, WebTV Networks, Inc., and the record shows WebTV's artwork was merged into Microsoft's chain in 2014. If the '253 invention and the Shoff reference were "owned by the same person or subject to an obligation of assignment to the same person" when the invention was made (WebTV having been a Microsoft subsidiary since 1997), then pre-AIA § 103(c) removes US 6,240,555 as § 103 art to the extent it is available only under § 102(e)/(f)/(g) — which is the case, since it granted in 2001 and its only pre-2000 public disclosure is via its own later-filed divisionals.

Practical consequence: a challenger should lead with Combination A (Sun/WO 99/17549, pure § 102(b)) and use Shoff as a corroborating reference, not as the primary reference, unless it can first establish that common ownership did not exist at the time of invention (e.g., by showing the invention was made before Microsoft's acquisition, or that assignment obligations ran to different entities). This is an issue to verify against assignment records — I did not verify it.

Corroborating external evidence for Shoff as prior art (not involving the '253 patent). My search surfaced a February 13, 2026 PTAB filing — IPR2026-00213 (Samsung Electronics), Exhibit 1023 = "US Patent No. 6,240,555 'Shoff'" (gaeflexstaging-dot-docketupdate.appspot.com, case PTAB/IPR2026-00213). That confirms the Shoff reference is actively relied on as prior art in current proceedings — but it is not a proceeding against US 7,237,253, and I am not reporting it as such.

---

VI. Why a PHOSITA would have combined these references (KSR rationales)

MPEP § 2143's four rationales, each supported by the record:

(1) Combining prior art elements according to known methods to yield predictable results.
The claims are an aggregation of four independently known elements — (a) an on-screen availability indicator ('496, '555), (b) an EPG/state record consulted on channel change ('555, '931), (c) a per-channel memory that is written and re-read ('931, '249, '902), and (d) a multi-tuner front end ('192, '728). Each performs its own known function; the combination's result is the predictable sum of those functions. There is no claim of synergy or unexpected result in the specification.

(2) Simple substitution of one known element for another.
Shoff already re-derives interactivity by consulting the EPG on every tuning event. Substituting (or supplementing) that re-derivation with a stored per-channel flag — so an already-active session is not re-launched — is a substitution of a known memory technique for a known lookup technique, yielding the same information more cheaply. That is precisely the difference the '253 claims assert.

(3) Use of a known technique to improve similar devices in the same way.
Channel/viewing-state logging with timestamps was standard in receiver-monitoring art ('249: locally encoded records of what the receiver is tuned to; '902: per-population consumption records). Applying that known logging technique to a set-top box's interactive-mode state yields the '253 channel table (including its "time entered" column and auto-deactivation logic, which the specification derives directly from the timestamp — a routine expiry policy).

(4) "Obvious to try" over a finite, predictable set of solutions.
Crosby frames the problem (channel-change latency is "annoying") and offers multiple tuner modules as the solution. Given that framing, and given the known cost asymmetry between video and data front ends and the fact that maintaining a session requires data tuning rather than video tuning, the space of solutions (multiple video tuners; one video + multiple data tuners; one video + shared data tuner) is small, and the choice is dictated by cost. Picking the cheap option is not invention.

(5) Design incentives and market forces.
The Sun reference states the goal in terms a POSITA would adopt: "seamless transitions between viewing conventional television content and interactive (Web) content"; Shoff seeks to free the viewer from the rigid, paned Intercast model and dynamically launch/retain the browser; Crosby seeks to eliminate the annoyance of slow channel changes. Each reference supplies an express motivation pointing toward the '253 modification.

(6) Where the motivation comes from isn't dispositive. Even if no single reference states "store interactive state per channel," KSR permits the motivation to come from common sense, the nature of the problem, and market demand — and here the problem (re-activation tedium on every channel change) is stated in the '253 Background itself, i.e., an admission of the state of the art and of the problem the art faced, which is usable against the patentee.

---

VII. Anticipated rebuttals and secondary considerations

• "No single reference discloses the check-before-activate conditional." Correct, but irrelevant: § 103 permits combination. The conditional is a data lookup that the primary references already perform, plus a "don't redo it" test — the essence of routine programming.
• "The indicator-disappears-but-activation-still-works feature is the novelty." Shoff and the Sun reference both disclose remote-control activation paths that are not co-extensive with the on-screen icon (Sun's on-screen notification is tied to a remote button; Shoff's icon activation is optional and the browser may launch automatically), so the "activate even after the indicator times out" distinction supplies little.
• Secondary considerations (nexus problems). Any commercial-success evidence would need a nexus to the claimed combination. Because the claims cover a UI convention implemented on a conventional set-top-box architecture, and because the WebTV/MSN TV product embodied far more than the claims, nexus is likely to fail. No unexpected-results evidence appears in the specification; the only arguably surprising statement ("redisplaying the last page the viewer was viewing") is a routine session-restore.
• Teaching away — none identified. Nothing in Crosby, Sun, Shoff, Index Systems, or Intel discourages per-channel state retention; the references' stated goals point toward it.
• Additional, independent grounds worth noting (not § 103). (i) The three software-claim forms (claims 3 and 6) face a § 101/Alice exposure that the apparatus claims do not; and (ii) the claim pairs 1/4, 2/5, and 3/6 raise obviousness-type double patenting questions within the '253 family — the page shows four division/continuation children (US 7,506,352; US 7,305,693; US 7,523,478; US 7,334,250; US 7,818,768) sharing the 2000-04-27 priority, which is itself strong evidence the claims were treated as directed to a single inventive concept.

---

VIII. Strength ranking of the § 103 combinations

---

IX. Uncertainties, contradictions, and what I could not verify

1. Date discrepancy in my instructions. The task states "Current Date: April 26, 2026," while my operating environment reports 2026-10-01. Neither affects the substance (the analysis is keyed to the 2000-04-27 effective filing date), but I am flagging it per the standing instruction to surface contradictions.
2. § 103(c) common ownership. I did not verify, from primary assignment records, whether WebTV Networks and Microsoft were commonly owned at the time the '253 invention was made. This is decisive for whether US 6,240,555 can be used as § 103 art, and should be checked before relying on Combination B.
3. Reference-content verification limits. My maps of the '496, '555, '192, '931, and '728 disclosures are drawn from live search results (Google Patents, uspto.report, patentimages PDFs, a PTAB exhibit) — I read abstracts, summaries, and key paragraphs, not the full specifications line-by-line. Specific element locations (column/line cites) should be confirmed against the full texts before filing anything.
4. The "Family Cites Families" anomaly. The literal record lists US5860249A, "Plant watering container" (International Plant Breeding AG, 1996-06-12) as a family-cited reference. I have reported it as written, given the no-auto-correction rule, and do not rely on it. It does not affect the analysis.
5. No claim of a live proceeding. My searches surfaced IPR2026-00213 (Samsung), Exhibit 1023 = US 6,240,555 (Shoff) — evidence that the Shoff reference is currently being asserted as prior art — but nothing involving US 7,237,253 itself. This is consistent with (not proof of) the earlier sections' finding of no known litigation or appeal over the '253 patent.
6. Claim independence. As noted in the earlier sections, I inferred that all six claims are independent from the absence of dependency language. That inference holds throughout this analysis; if any claim were in fact dependent, the charting would need minor adjustment.
7. Non-record art not evaluated. I did not search for prior art beyond the eight references of record (e.g., ATVEF 1.1 draft publications, which the '253 specification itself invokes, and which — if publicly available before 2000-04-27 — would be additional § 102(b) printed-publication art bearing directly on the "mode indicator" and template teachings). A full validity study should include it.

---

X. Verification steps I would run before relying on this opinion

1. Pull the full texts of US 6,600,496 / WO 99/17549 and US 6,240,555 and pin down column/line support for the indicator, activation, and per-channel-record teachings.
2. Confirm the § 103(c) ownership timeline for WebTV Networks vs. Microsoft as of the '253 invention date (assignment records / corporate history), to fix the usable prior-art set.
3. Confirm the WO 99/17549 publication date (1999-04-08 as reported) and that it antedates 1999-04-27, establishing § 102(b) status independent of § 102(e).
4. Inspect the '192 patent's tuner/decoder claims and figures to anchor the "plurality of data tuners" reading, and confirm whether its second tuner is architecturally a "data" path or a second video path.
5. Review the '253 prosecution history (the page shows a web of division/continuation filings on 2005-03-18 and 2005-06-30, plus US 12/402,221 in 2009) for any restriction requirement and any examiner statements about the tuner limitations — the strongest source of prosecution-history estoppel or of an admission useful to a challenger.