US 8220027

Summary of U.S. Patent No. 8,220,027 (literal ID: 8220027 / US8220027B1)

I searched the USPTO/Google Patents records, district-court dockets, and CAFC 2026 coverage for the exact number 8220027. Findings below; where information is not authoritative I flag it.

Bibliographic data

• Title: Method and system to convert conventional storage to an audio/video server
• Patent / publication no.: US8220027B1
• Application no.: US12/126,396
• Filing date: May 23, 2008
• Issue (grant) date: July 10, 2012
• Priority date: May 23, 2008 (single, same-family application; no foreign filings in family)
• Inventors: Vadim Dagman, Yaroslav Lisitsyn (recorded in assignment as "Yarslav Lisitsyn" in one event), Kevin Roe
• Original assignee: Monsoon Multimedia Inc.
• Current assignee (per Google Patents assignment chain): VIDEOLABS Inc. (assignment recorded Oct. 16, 2024, effective Sept. 17, 2024, from Zing Communications Inc., which had acquired it from Clyp Engines Private Limited). Chain includes Monsoon Multimedia India Limited → Marton Distribution Private Ltd. → Clyp Engines Private Limited → Zing Communications Inc. → VideoLabs, Inc.
• Legal status: Active – Reinstated (lapsed Aug. 17, 2020 for failure to pay maintenance fees; reinstated Feb. 2021; 12th-year maintenance fee paid June 2024; entity status set to large/undiscounted Dec. 2024). Adjusted expiration listed as Aug. 8, 2029.

Abstract (condensed)

A method and system to use an audio/video server to store real-time, previously recorded, or otherwise obtained media data to one or more conventional storage devices and make that stored media available to playback devices on a network. A first embodiment is a method including recording audio/video data to a storage module coupled to the video server through at least one standardized port module, determining a need to provide a video file to playback devices, reading the video file from the storage module through the standardized port module, and providing a version of the video file (optionally trans-coded — new format, compression, bitrate, or combination) to the playback devices. A second embodiment is a system including such a storage module, video server, and playback devices.

Independent claims in plain language

The patent has 25 claims; the independent claims are 1, 10, 18, and 25 (dependents are 2–9, 11–17, 19–24). All four independent claims share the same core limitation set, phrased as method, system, method, and machine-readable medium respectively:

• Claim 1 (method): A method of operating a video server that (a) detects the presence of playback devices on a network with the video server; (b) determines a need to provide a video file to those devices; (c) reads the video file from a storage module that is attached to the video server through a standardized port (e.g., USB); and (d) provides an optionally trans-coded version of the file over the network, where any trans-coding is done in the video server and the entire trans-coded version is stored in the storage module for later retrieval — expressly "avoiding the need for the playback devices to wait for real-time trans-coding" — before the file is delivered, so the version better matches network/device limitations and capabilities.
• Claim 10 (system): The corresponding system claim — a storage module having at least one standardized port module; a video server coupled to that storage module through the port; and playback devices coupled to the video server through a network — with the same stored-whole-file, no-real-time-transcoding-wait, better-match limitation as claim 1.
• Claim 18 (method): Substantially identical to claim 1, but framed around "outputting" the optionally trans-coded version (rather than "providing"), with the same trans-coding-stored-whole-file limitation.
• Claim 25 (machine-readable storage medium): A non-transitory machine-readable storage medium with executable modules performing the claim-1 steps — detection, need determination, reading from the storage module via the standardized port, and providing the optionally trans-coded, fully pre-stored version — with the same limitation.

Key dependent limitations (2–9, 11–17, 19–24): acquiring/storing video from a video source (2, 20); storage module as a disk drive with a standardized port (3, 21); trans-coded version provided (4, 13); trans-coding actions being format change, format compression, and/or bitrate change (5, 14, 19); USB port embodiment (6, 15, 22); playback devices being UPnP Control Points (7, 16, 23); video server storing a version on a network storage device (8); trans-coded version previously stored in the storage module (9, 17, 24).

Litigation / CAFC 2026 docket check

• District court: The patent is asserted in VideoLabs, Inc. v. TCL Technology Group Corp. et al., 2:25-cv-00161 (E.D. Tex., Marshall Div., Judge Rodney Gilstrap). The complaint (filed Feb. 10, 2025) lists '027 among seven asserted patents and states at least independent claim 10 is asserted. Per Docket Alarm records, the case was stayed (Mar. 2025) and then dismissed with prejudice by joint motion, Nov. 14, 2025 (settlement) — consistent with the "litigation" flag on the Google Patents page.
• CAFC 2026 dockets: I found no CAFC appeal specific to patent 8220027 as of the search date. The case in which 8220027 was asserted ended in a district-court dismissal with prejudice, and I located no Federal Circuit notice of appeal or 2026 CAFC docket tied to this patent number. Note: an August 2026 IPWatchdog article covers a CAFC affirmance in VL Collective IP, LLC v. Netflix, Inc., but that appeal concerns patent 7,440,559, not 8220027 — do not conflate the two.

Uncertainty caveats

• The CAFC search returned no direct hit; my conclusion that no 2026 CAFC matter exists for 8220027 is based on the absence of results plus the settlement dismissal, not on a definitive court-docket query.
• Assignee/ownership data comes from Google Patents assignment event records, which carry their own caveat ("listed assignees may be inaccurate").
• The inventor middle name discrepancy ("Yaroslav" vs. assignment "Yarslav Lisitsyn") mirrors the record; I flag it rather than auto-correcting it.

I'll search for litigation involving US Patent 8,220,027 across multiple sources.

I found one case. Let me search for any other litigation involving this patent, including earlier cases by prior owners (Monsoon, CLYP Engines, Zing).

Let me check the Unified Patents portal and search for any other district court cases or PTAB proceedings mentioning this patent.

Based on my searches across Unified Patents, Docket Alarm, Ex Parte, PACER-derived sources, and USPTO PTAB records, here is what is known regarding litigation involving US Patent 8,220,027 ("Method and System to Convert Conventional Storage to an Audio/Video Server").

Known Litigation

VideoLabs, Inc. v. TCL Technology Group Corporation et al.

• Case No.: 2:25-cv-00161-JRG-RSP
• Jurisdiction: U.S. District Court for the Eastern District of Texas, Marshall Division (Judge Rodney Gilstrap; Magistrate Judge Roy S. Payne)
• Plaintiff: VideoLabs, Inc. (identified as an NPE / patent assertion entity)
• Defendants: TCL Technology Group Corporation; TCL Electronics Holdings, Ltd. (f/k/a TCL Multimedia Technology Holdings, Ltd.); TCL Industries Holdings Co., Ltd.; T.C.L. Industries Holdings (H.K.) Limited; TTE Corporation; TCL Moka International Ltd.; TCL Moka Manufacturing S.A. de C.V.; Manufacturas Avanzadas S.A. de C.V.; TCL Smart Device (Vietnam) Co., Ltd.; Shenzhen TCL New Technology Co., Ltd.; TCL Optoelectronics Technology (Huizhou) Co., Ltd.; and TCL Overseas Marketing Ltd.
• Filing date: February 9–10, 2025 (Unified Patents portal lists 2025-02-09; the complaint, Docket No. 1, and Docket Alarm list filing as Feb. 10, 2025)
• Patents asserted: '027 was one of seven patents asserted (U.S. Patent Nos. 7,525,535; 7,769,238; 7,970,059; 8,139,878; 8,220,027; 8,291,236; 8,667,304). For the '027 patent, at least independent claim 10 was asserted, and the accused instrumentality was the infrastructure/equipment comprising TCL's "TCLtv+" service.
• Outcome/Current status: Closed — dismissed with prejudice. Docket No. 27 (Order Dismissing Case with Prejudice) was entered Nov. 14, 2025; Unified Patents records a termination date of Nov. 13, 2025 and status "Closed." (Earlier in the case, TCL moved to dismiss — with a proposed order dismissing without prejudice for improper service and failure to plead knowledge for indirect infringement — but the final disposition was dismissal with prejudice.)

Notes on other potential proceedings

• The Google Patents page for the '027 patent flags this same Texas Eastern District Court case (linked to Unified Patents portal case 2:25-cv-00161) as the "US case" and Darts-ip flags the first worldwide family litigation via family ID 46396050 — both point to the VideoLabs v. TCL case above.
• I found no other district-court case, ITC investigation, or PTAB inter partes review specifically naming the '027 patent. The PTAB documents I encountered (e.g., IPR2025-01329 and related petitions) concern different patents in the same portfolio (e.g., '238, '236) and merely list the VideoLabs v. TCL case as a related matter; they do not challenge the '027 patent.

Bottom line: As of April 26, 2026, the only known litigation involving US Patent 8,220,027 is VideoLabs, Inc. v. TCL Technology Group Corporation et al., No. 2:25-cv-00161-JRG-RSP (E.D. Tex.), which has been dismissed with prejudice and closed.

Sources: Unified Patents litigation portal (case 2:25-cv-00161); Docket Alarm case/docket pages; Ex Parte case page and complaint analysis; USPTO PTACTS petition documents (IPR2025-01329 related-matters disclosures).

Proceedings overview

Zero AIA trial proceedings exist for US 8,220,027. The USPTO Open Data Portal (PTAB proceedings on file) returns no IPR, PGR, or CBM for this patent, and targeted web searches corroborate that result — the only PTAB cases involving the current patent owner's portfolio (e.g., IPR2025-01329, Hisense USA Corp. v. VideoLabs, Inc.) challenge different patents such as the '238 patent, not 8,220,027. The bottom line for a defendant: the '027 patent is completely untested at the PTAB — no claim has been canceled, no claim has been sustained, and no estoppel has been generated against anyone. The earlier assertion against TCL (2:25-cv-00161, E.D. Tex.) settled and was dismissed with prejudice in November 2025 without any IPR being filed on this patent.

Proceedings list

None on file

• Type: N/A
• Filed: N/A
• Status: The structured USPTO ODP data states: "The USPTO ODP API returns no AIA trial proceedings for this patent as of the most recent ingest." Plain-English gloss: no IPR / PGR / CBM petition has been filed against 8,220,027.
• Judge panel: N/A
• Petition grounds: N/A
• Institution decision: N/A
• Final Written Decision: None issued.
• Settlement / termination: N/A
• Appeal: N/A
• Defensive value: With zero PTAB challenges on file, there is no FWD to cite, no canceled claim to lean on, and no estoppel bar to worry about — but equally, the patent has never been stress-tested, so its validity is unproven before the Board.

Search-integrity notes (do not conflate):

• A search hit for "IPR2025-00631, Revvo Technologies v. Tire Stickers LLC" discusses a different "'027 patent" (a tire-repair-patch patent, claims over "Wilson") — that is not 8,220,027 and is irrelevant.
• The VideoLabs portfolio IPRs surfaced in searches (e.g., IPR2025-01329, Hisense v. VideoLabs, against U.S. Patent 7,769,238, terminated-settled Nov. 25, 2025) challenge other patents from the same litigation family. None names 8,220,027 as the challenged patent.

Strategic summary

Claim status. All 25 claims of 8,220,027 — including the four independent claims (1, 10, 18, and 25) — remain in force and completely UNTESTED at the PTAB. No claim has been canceled or even institution-challenged. The only known litigation, VideoLabs, Inc. v. TCL Technology Group Corp., No. 2:25-cv-00161 (E.D. Tex.), asserted at least claim 10 against TCL's "TCLtv+" service, but that case settled and was dismissed with prejudice on 2025-11-14 without any IPR having been filed. If a defendant is facing a demand letter citing the '027 patent today, there is no FWD or estoppel to rely on — the validity fight would be a clean slate.

Estoppel landscape. Because no petition has ever been filed against 8,220,027, there is no § 315(e)(2) estoppel binding anyone. Every § 102/§ 103 ground reasonably available remains open to any future petitioner, including grounds already tested against sibling patents in the portfolio (the '027 specification's "standardized port module + pre-stored trans-coded file" combination is distinctive and was not at issue in the Hisense/other portfolio IPRs). One practical caveat: the one-year IPR deadline under § 315(b) runs from service of a complaint, so a defendant served today must decide quickly whether to petition or waive that route.

Pattern signals. There is no pattern of repeated IPRs on this patent — the pattern is on the portfolio: VideoLabs' related patents ('238, '236, etc.) have drawn IPRs from multiple petitioners (Hisense and others) that largely settled. VideoLabs, the current assignee, is a monetization entity with an active licensing program (per IAM coverage of its ~17 licensees and acquisitions), and the TCL case was one of several district-court assertions (e.g., VideoLabs v. Giga-Byte, 2:25-cv-00704 E.D. Tex., also pending per PO mandatory notices). Notably, no defensive aggregator such as Unified Patents has filed against '027 to date, despite the TCL litigation having ended in 2025. The absence of any IPR through a full lifecycle of district-court assertion is unusual for a well-asserted patent and may reflect that accused products (smart-TV "media server" features) are licensed, that parties settle early, or that challengers see the claim set as harder to knock out — a signal that a validity attack needs careful prior-art development around the stored-whole trans-coded file and standardized port limitations of claims 1, 10, 18, and 25.

Recommended next steps

• If you are a defendant facing 8,220,027 today: There is no FWD to cite because none exists — say so plainly in any invalidity contentions. The absence of PTAB activity means your § 102/§ 103 prior-art search is unconstrained by any estoppel, but it also means the patent has never been narrowed; expect VideoLabs to assert it aggressively (independent claims 1, 10, 18, 25 all carry the same core limitations).
• Consider filing an IPR promptly if you have been served: The § 315(b) one-year bar runs from service. Given VideoLabs' history of settling portfolio IPRs (e.g., IPR2025-01329 terminated-settled 2025-11-25), a well-pleaded petition can create settlement leverage even if it never reaches a FWD. Focus art on: (i) external USB/IEEE 1394/Ethernet-attached storage to a media server/PVR, and (ii) pre-transcoding entire files and storing them to avoid real-time trans-coding wait — the latter being the claim language added to distinguish prior art.
• Monitor the portfolio IPRs for claim-construction and § 325(d) signals: While none touches '027, the pending/terminated IPRs against VideoLabs' related patents reveal how the Board and VideoLabs litigate (e.g., VideoLabs' discretionary-denial arguments citing its licensing program). USPTO PTAB E2E (https://ptab.uspto.gov) is the authoritative tracker for any new petition against '027.
• If no petition is ever filed, that absence itself is evidence for your invalidity narrative in district court — but only in the sense that validity remains fully contested; do not over-read silence as weakness, because early settlements (as with TCL) can simply mean the economics favored a license.

I attempted live verification against the USPTO Assignment Center and public indexes, but the search tool returned no retrievable records in this session (empty results across five queries). The assignment events below therefore come from the USPTO assignment records as mirrored in the Google Patents legal-events feed for US8220027 (reel/frame numbers included there are the official USPTO reel/frame identifiers). The one field I could not retrieve is the correspondent of record for each conveyance — I flag that explicitly rather than guessing attorney names.

Inventors

• Vadim Dagman — assignor on reel 021274/0569 (recorded 2008-07-22), assigning to Monsoon Multimedia Inc.
• Yaroslav Lisitsyn — recorded on reel 021274/0569 as "Yarslav Lisitsyn" (USPTO/Google record spelling; not auto-corrected)
• Kevin Roe — assignor on reel 021274/0569

Employer at filing: not independently verified, but the July 2008 assignment of all three inventors' rights to Monsoon Multimedia Inc. is consistent with employment/consulting assignments to that company (Monsoon was the applicant). No evidence located of a coordinated post-filing departure of all three inventors; that pattern is not established here.

Original assignee

• Monsoon Multimedia Inc. (California) — named original assignee; the issued patent's assignment chain and Google's "Original Assignee" field both point to it (the 2008 record styles it "MONSOON MULTIMEDIA, CALIFORNIA").
• Business: consumer-electronics maker of placeshifting/streaming media devices (the "Vulkano" line — Slingbox-type TV-to-PC/mobile products). The Vulkano devices carried USB storage ports and streamed recorded content to remote players, which is consistent with the '027 claims; whether a shipped product literally embodied claim 1/10 is not something I verified from teardowns or marketing literature.
• Current status: the US entity's patent rights were transferred out to Monsoon Multimedia India Limited effective 2013-02-26 (reel 030537/0355). No Chapter 7/11 filing for Monsoon Multimedia was found in my search sources; I found no evidence it still operates as a going concern, but I could not confirm dissolution.

Assignment timeline

Chronological list from the USPTO assignment records (via Google Patents legal-events mirror). Correspondent-of-record: not retrievable in this session — marked unknown on each entry rather than fabricated.

• 2008-07-17 to 2008-07-21 (executed) / recorded 2008-07-22 — Reel 021274/0569

  • Conveyance: Assignment (of inventors' rights)
  • Assignor: Vadim Dagman; Yaroslav Lisitsyn ("Yarslav"); Kevin Roe
  • Assignee: Monsoon Multimedia Inc.
  • Correspondent: unknown (not retrievable)
  • Context: Original vesting of the application (filed 2008-05-23) from the named inventors to the corporate applicant/employer.

• 2013-02-26 (effective) / recorded 2013-03-05 — Reel 029923/0428

  • Conveyance: Assignment (as originally recorded)
  • Assignor: Prabhat Jain (as recorded)
  • Assignee: Monsoon Multimedia, Inc. (as recorded)
  • Correspondent: unknown
  • Context: This record was later corrected (see next entry); it appears to be an erroneous vesting of the transfer in an individual officer (Jain) rather than the corporate assignor.

• 2013-02-26 (effective) / recorded 2013-06-03 — Reel 030537/0355

  • Conveyance: Corrective Assignment
  • Assignor: Monsoon Multimedia, Inc. (corrected)
  • Assignee: Monsoon Multimedia India Limited (corrected)
  • Correspondent: unknown
  • Context: Corrects reel 029923/0428; true transfer is parent/subsidiary or related-entity transfer from the US company to its India affiliate — first step out of the original operating entity.

• 2014-05-08 (effective and recorded) — Reel 032850/0446

  • Conveyance: Assignment
  • Assignor: Monsoon Multimedia India Limited
  • Assignee: Marton Distribution Private Ltd. (India)
  • Correspondent: unknown
  • Context: Transfer from the (former) operating company's Indian arm to an India private limited company — a monetization/exit step, not an operating-company consolidation.

• 2014-05-08 (effective) / recorded 2014-06-18 — Reel 033198/0862

  • Conveyance: Security Interest
  • Assignor: Marton Distribution Private Ltd.
  • Secured party / assignee: Kanzatec LLC (Kansas)
  • Correspondent: unknown
  • Context: Third-party lender/investor (Kanzatec) takes a security interest over the patent ~6 weeks after Marton acquired it — a financing/assertion-funding pattern.

• 2014-09-01 (effective) / recorded 2014-09-02 — Reel 033787/0036

  • Conveyance: Release by Secured Party
  • Assignor of record: Marton Distribution Private Ltd.
  • Correspondent: unknown
  • Context: The Kanzatec security interest from reel 033198/0862 was released ~3 months later.

• 2015-02-11 (effective and recorded) — Reel 034957/0955

  • Conveyance: Security Interest
  • Assignor: Marton Distribution Private Ltd., India
  • Secured party / assignee: Kanzatec LLC (Kansas)
  • Correspondent: unknown
  • Context: A second, identical security interest in favor of Kanzatec was placed on the same asset after the first was released.

• 2016-05-06 (effective) / recorded 2016-05-10 — Reel 038664/0804

  • Conveyance: Assignment
  • Assignor: Marton Distribution Private Limited
  • Assignee: CLYP Engines Private Limited (India)
  • Correspondent: unknown
  • Context: Second hop through an India private limited entity — another name change/restructuring step in the holding chain.

• 2016-05-06 (effective) / recorded 2016-05-10 — Reel 038700/0853

  • Conveyance: Declaration of Invalid Security Interest
  • Declarant: Prabhat Jain (same individual who appeared as erroneous assignor in 2013)
  • Correspondent: unknown
  • Context: Declaration that the Kanzatec security interest(s) (reels 033198/0862, 034957/0955) were invalid, clearing the chain as it moved to CLYP Engines. Same principal (Jain) appearing in 2013 and 2016 links the Monsoon-era management to the holding-company chain.

• 2021-02-05 (effective and recorded) — Reel 055168/0123

  • Conveyance: Assignment
  • Assignor: CLYP Engines Private Limited
  • Assignee: Zing Communications Inc. (California)
  • Correspondent: unknown
  • Context: Transfer to a US entity two days after the patent's maintenance-fee reinstatement was granted (petition granted 2021-02-02, following lapse 2020-08-17) — the patent was revived and moved in the same week.

• 2024-09-17 (effective) / recorded 2024-10-16 — Reel 068916/0055

  • Conveyance: Assignment
  • Assignor: Zing Communications Inc. (recorded with USPTO/Google spelling "ZING COMMUNCATIONS")
  • Assignee: VideoLabs, Inc. (California)
  • Correspondent: unknown
  • Context: Transfer to the entity that filed the first (and only known) infringement suit on this patent ~5 months later (VideoLabs v. TCL, filed 2025-02-10).

Timeline diagram

timeline
    title Ownership of US 8220027
    2008 : Filed by Monsoon Multimedia
         : Inventors assign to Monsoon
    2012 : Patent issued
    2013 : Assigned to Monsoon India
    2014 : Assigned to Marton Distribution
         : Kanzatec security interest filed
         : Kanzatec security interest released
    2015 : Second Kanzatec security interest
    2016 : Assigned to CLYP Engines
         : Security interest declared invalid
    2021 : Patent reinstated
         : Assigned to Zing Communications
    2024 : Assigned to VideoLabs Inc
    2025 : VideoLabs sues TCL in Texas

NPE / troll-pattern signals

1. Shell-entity transfer — present (moderate evidence). The patent moved from an operating company (Monsoon Multimedia, a device maker) through two India private limited entities with no known products — Marton Distribution Private Ltd. (reel 032850/0446) and CLYP Engines Private Limited (reel 038664/0804) — before reaching the asserting entity. I could not confirm registered-agent addresses or absence of products from public filings, so this rests on the operating-to-non-operating chain plus the security-interest financing pattern rather than on address evidence.

2. Known asserter in the chain — present. VideoLabs, Inc. (reel 068916/0055) is the plaintiff in VideoLabs v. TCL, No. 2:25-cv-00161 (E.D. Tex.), the only litigation naming '027; that case is tracked by Unified Patents (which flagged it on the Google Patents record) and by Darts-ip as the family's first litigation. The prior summary in this analysis already identified VideoLabs as "an NPE / patent assertion entity."

3. Repeat correspondent across the chain — unclear / unverifiable in this session. The correspondent-of-record fields could not be retrieved from the Assignment Center with the tools available, so I decline to name any attorney. This is the key missing datum for the Jain/Marton/Clyp/Zing/VideoLabs web. Note, however, that the non-attorney name Prabhat Jain recurs as a principal: erroneous assignor in 2013 (reel 029923/0428) and declarant in 2016 (reel 038700/0853).

4. Cascading transfers — present (weak-to-moderate). Four ownership events plus two Kanzatec security interests plus one invalidity declaration occurred between 2013 and 2016 (reels 030537/0355 → 032850/0446 → 033198/0862 → 033787/0036 → 034957/0955 → 038664/0804 → 038700/0853), i.e., a burst of chained transfers through related private entities within ~3 years, followed by two more transfers in 2021 and 2024. The <24-month cascade criterion is only partially met (the dense cluster spans ~37 months), but the chained-entity pattern is clear.

5. Pre-litigation transfer — present (strong). The VideoLabs assignment is effective 2024-09-17 (recorded 2024-10-16, reel 068916/0055); the first infringement suit asserting '027 was filed 2025-02-10 (2:25-cv-00161). That is ~5 months — inside the 6-month window — and gives VideoLabs clean standing and venue for the assertion campaign.

6. Bankruptcy fire-sale — not present (no evidence of a Chapter 7/11 sale for Monsoon Multimedia; the transfers were ordinary conveyances, not bankruptcy-court orders).

7. Privateering — unclear. No SEC filing or press coverage surfaced showing Monsoon (or its successors) directing VideoLabs to sue specific competitors; the TCL suit targets a TV maker, and the accused instrumentality (TCLtv+) is not a Monsoon product line. Absent evidence of a retained interest or revenue share, I do not call this privateering.

8. Defensive aggregator (anti-NPE) — not present. The chain terminates at VideoLabs, Inc., an asserting plaintiff, not at RPX, AST, LOT, Unified Patents, or OIN.

Verdict

NPE — high confidence

Two strong signals drive this: (1) a pre-litigation transfer — VideoLabs, Inc. took title effective 2024-09-17 (reel 068916/0055) and filed the first suit asserting '027 on 2025-02-10 in E.D. Tex. (2:25-cv-00161), inside the 6-month window; and (2) a known asserter — VideoLabs is the Unified Patents-tracked plaintiff in the only litigation on this patent. Supporting context: the asset was moved out of operating company Monsoon Multimedia through chained holding entities (Marton Distribution, CLYP Engines; reels 032850/0446 and 038664/0804) with third-party security interests (Kanzatec LLC, reels 033198/0862 and 034957/0955) declared invalid on transfer to CLYP Engines (reel 038700/0853) — a monetization, not product-consolidation, chain. The correspondent-of-record analysis, which would strengthen or weaken the shell-entity call, could not be completed because the Assignment Center fields were not retrievable in this session.

Verification: https://assignmentcenter.uspto.gov/ (search patent no. 8220027) and https://patents.google.com/patent/US8220027/en (Legal Events tab, reels 021274/0569 through 068916/0055).

I'll research the prior art cited against US Patent 8,220,027. The patent's own record lists four examiner-cited references; I'll verify each and check for additional relevant prior art.

I have detailed data on all four face citations. Let me do a couple more targeted checks — the USPTO record for any additional references considered during prosecution, and verification of the exact bibliographic data.

Based on the USPTO record as reflected in the patent's face citations (Google Patents / USPTO data), US 8,220,027 B1 cites exactly four prior-art references, all marked "Cited by examiner". All are U.S. documents, and because the '027 application was filed May 23, 2008 (pre-AIA), any § 102 analysis is governed by pre-AIA 35 U.S.C. § 102(a), (b), and (e). All four qualify as prior art (three published before the 2008 filing; the fourth, US 7,764,863, is prior art only under § 102(e) via its 2003/2002 effective filing dates).

For the claim-mapping below, the key limitations of the independent claims (1, 10, 18, 25) are: (i) detect presence of playback devices on a network including a video server; (ii) determine a need to provide a video file; (iii) read the video file from a storage module coupled to the video server through at least one standardized port module (e.g., USB); and (iv) provide an optionally trans-coded version, trans-coded in the video server, whose entire transcoded output is pre-stored in the storage module for later retrieval — expressly "avoiding the need for the one or more playback devices to wait for real-time trans-coding" — before network delivery, to match network/device limitations.

Prior-art references cited on the face of US 8,220,027 B1

1. US 2001/0047517 A1 — "Method and apparatus for intelligent transcoding of multimedia data"

• Full citation: Christopoulos, Charilaos; US Patent Application Publication US 2001/0047517 A1; published Nov. 29, 2001; earliest priority Feb. 10, 2000 (per the USPTO family record on the '027 citation list).
• Brief description: Discloses intelligent transcoding of multimedia data between network elements (client-server or client-to-client). Transcoding "hints" are stored at a network element; capabilities of a destination network element are obtained; transcoding is then performed using the hints and capabilities (bitrate, resolution, frame size, color, motion vectors, etc.) "in a manner suited to the capabilities of the network element." It expressly discusses two design alternatives: (a) storing multiple versions of content in a server database to match client capabilities (and notes the storage-cost problem of that approach), and (b) performing conversions in real time at the server/gateway upon delivery. This is the closest disclosure in the record to claim element (iv)'s transcode-to-match-capabilities concept.
• Potential § 102 relevance: The reference is the most relevant to the trans-coding language of claims 1, 4, 5, 10, 13, 14, 18, 19, 25 — specifically the "better match one or more limitations and capabilities of the network or the playback devices" clause and the trans-coding-actions of claims 5/14/19 (format change, compression, bitrate change). However, it does not disclose: detecting playback-device presence on the network, reading from a storage module through a standardized port module (USB), or the distinguishing limitation that the entire trans-coded file is stored in the storage module before delivery to avoid a real-time trans-coding wait. In fact, the reference teaches the opposite of that last limitation — real-time transcoding at delivery time (and criticizes the multiple-pre-stored-versions approach for excessive storage). On its own it would therefore not fully anticipate any single claim, but it is the strongest § 102 reference against the trans-coding/format/bitrate limitations if the pre-stored-entire-file clause is not given patentable weight.

2. US 6,711,741 B2 — "Random access video playback system on a network"

• Full citation: Yeo, Boon-Lock; assigned to Intel Corporation; U.S. Patent No. 6,711,741 B2; issued Mar. 23, 2004; filed Apr. 7, 1999 (Appl. No. 09/288,047); prior publication US 2003/0088646 A1 (May 8, 2003).
• Brief description: A client-server method for random-access (VCR-like) video playback over a network. The server supplies "temporal snapshots" of source video; the client organizes snapshots hierarchically into scenes, requests and stores segments of source video frames, and plays back the stored segments; subsequent temporally related segments are requested as playback proceeds. Claim 1 of the patent (as issued) is the full client-server playback/storage method quoted in the record.
• Potential § 102 relevance: Relevant to the general framework of claims 1, 8, 10, 18, 25 — a server providing stored video over a network to a playback device, with the client-side storing of retrieved video segments. It does not disclose the video-server-side elements of the '027 claims: detecting playback-device presence, reading from an externally attached storage module through a standardized port module (USB/IEEE 1394/Ethernet), or server-side trans-coding with the entire trans-coded file pre-stored to avoid a real-time wait. Anticipation of the full method/system would fail on those elements; the reference is best characterized as background art on networked video servers/playback.

3. US 7,023,924 B1 — "Method of pausing an MPEG coded video stream"

• Full citation: Keller, Sebastian; Gardere, Daniel; Wang, Jie; Noury, Michel; Faibish, Sorin; assigned to EMC Corporation; U.S. Patent No. 7,023,924 B1; issued Apr. 4, 2006; filed Dec. 28, 2000 (Appl. No. 09/750,540).
• Brief description: Discloses server/streaming-side manipulation of an MPEG video stream to implement a pause function. An I-frame is extracted from the original stream and a "pause GOP" is constructed containing that I-frame plus "frozen" P-frames and padding; the pause GOP is seamlessly inserted and played in a loop until resume. The work is performed on the coded stream (in the DCT domain in some claims), with PTS/DTS/continuity-counter restamping — i.e., generating a modified/stored variant of a coded video stream at a media server.
• Potential § 102 relevance: Weakest of the four against the '027 claims. It is server-side video-stream processing/transmission art and could be cited for the general notion of a server producing and delivering a modified "version" of a stored coded video stream (claim elements (iii)/(iv) at a high level). It lacks: network playback-device detection, need determination, standardized-port-module storage, capability-matching transcoding, and the entire-file-pre-stored-to-avoid-real-time-transcoding limitation. It would not anticipate any independent claim and has at most marginal bearing on the dependent claims (none of which it cleanly reads on).

4. US 7,764,863 B1 — "System and method for providing trick modes"

• Full citation: Strasman, Nery; Yassouline, Lior (recorded as "Yassouline" in family data); assigned to Bigband Networks Inc. (now Bison Patent Licensing LLC per assignment data); U.S. Patent No. 7,764,863 B1; issued Jul. 27, 2010; continuation of Appl. No. 10/339,527 (filed Jan. 8, 2003, abandoned), claiming priority to Provisional Appl. 60/362,344 (filed Mar. 6, 2002).
• Brief description: A memory-efficient system/method for VOD trick modes. A server receives and stores a normal-play media stream and generates an indexing file (pointers to I-frames). On a request to change display mode (FF/REW/etc.), the system fetches the indexing file and generates a trick-play media stream on the fly — retrieving selected I-frames, modifying timing information, adding duplicating frames — "without a need to previously store" the trick-play stream, and transmits it over an HFC/broadband network to end users.
• Potential § 102 relevance: Relevant to claims 1, 4, 10, 13, 18, 25 insofar as it discloses a video server providing a modified "version" of a stored video stream over a network to playback clients in response to a request, to suit the requested playback mode/network. Critically, it teaches generation of the alternative stream "on-the-fly" with no need to store it — the direct antithesis of the '027 limitation that the entire trans-coded version be stored in the storage module before delivery to avoid a real-time trans-coding wait. It also lacks playback-device "presence" detection and the standardized-port-module storage coupling. As a § 102(e) reference (effective 2003/2002 filing dates vs. the '027's May 23, 2008 filing), it qualifies as prior art despite its 2010 issue date, but it would not anticipate any full claim.

Analysis notes and caveats

• Only these four references appear on the face of the patent as "Cited by examiner." The separate "Cited By" list on the record (e.g., US 2011/0055341 A1, WO 2016/106087 A1, US 2016/0360285 A1, US 9,596,183 B2, US 11,122,305 B2) consists of later-filed documents that cite the '027 patent — they are not prior art and cannot anticipate.
• No single reference anticipates any full independent claim. The recurring gaps across all four: (1) the standardized port module (USB/IEEE 1394/Ethernet) coupling between the video server and an external/conventional storage module — none of the four disclose an external storage module attached through a standardized port; (2) detecting the presence of playback devices on the network; and (3) the prosecution-distinguishing clause requiring the entire trans-coded file to be pre-stored in the storage module before supply so playback devices do not wait for real-time trans-coding — references 1 and 4 in particular teach real-time/on-the-fly transcoding or stream generation, the opposite of that limitation.
• Under § 102 status: US 2001/0047517 A1, US 6,711,741 B2, and US 7,023,924 B1 are prior art under pre-AIA § 102(a)/(b)/(e) (published/issued well before May 23, 2008). US 7,764,863 B1 issued after the '027 filing date and is prior art only under § 102(e) via its Jan. 8, 2003 continuation / Mar. 6, 2002 provisional filing dates — the examiner's "* Cited by examiner" designation confirms it was applied that way.
• I could not retrieve the non-public USPTO file-wrapper "Notice of References Cited" or any office-action art rejections via web search (the USPTO query returned no results), so this analysis is limited to the face citations, which are the authoritative USPTO citation list printed on the patent.

Bottom line: The most relevant prior art for the trans-coding and capability-matching limitations of claims 1, 4, 5, 10, 13, 14, 18, 19, and 25 is US 2001/0047517 A1 (Christopoulos); for the "provide a version of a stored video file to networked playback devices" framework it is US 6,711,741 B2 (Intel) and US 7,764,863 B1 (Bigband); US 7,023,924 B1 (EMC) is peripheral MPEG-stream-processing art. None of the four, individually, discloses the full combination — particularly the standardized-port external storage module and the fully pre-stored trans-coded file (no real-time trans-coding wait) — that defines the independent claims.

Obviousness Analysis of US Patent 8,220,027 (US8220027B1) Under 35 U.S.C. § 103

Analyst date: April 26, 2026. Pre-AIA § 103 applies because the application was filed May 23, 2008 (US12/126,396).

A note on scope and ground rules before the analysis. The "Prior Art" materials available on the Google Patents page for the '027 patent consist of (i) the four examiner-cited references in "Patent Citations (4)," (ii) the prior-art systems the patent itself describes in its Background (TiVo-style PVR with built-in storage; a "Dedicated Device Interface" such as the NSLU2 that converts a USB disk into a UPnP AV Media Server; and NAS-drive servers), and (iii) the "Similar Documents" list (which is a Google-generated similarity list, not a verified prior-art list — several entries post-date the May 23, 2008 critical date, e.g., US8437624B2 (2013), CN112752115B (2023), US7589852B2 (2009), and I therefore do not rely on them without independent verification). My analysis below is grounded on the four cited references and the admitted background art, each of which qualifies as prior art: US6711741B2 (issued 2004), US20010047517A1 (published 2001), US7023924B1 (issued 2006), and US7764863B1 (filed as a continuation of a January 8, 2003 application claiming a March 6, 2002 provisional — prior art under § 102(e) even though it issued July 27, 2010).

I. Legal framework

Obviousness under § 103 asks whether the claimed invention, as a whole, would have been obvious to a person having ordinary skill in the art (POSITA) at the time of invention, applying the Graham factors (scope/content of prior art; differences between prior art and claims; level of ordinary skill; secondary considerations). Under KSR Int'l Co. v. Teleflex Inc. (2007), the analysis is flexible: a combination of known elements that yields a predictable result, or the application of a known technique to a known device ready for improvement, can be obvious even absent an explicit teaching-suggestion-motivation. "Obvious to try" from a finite set of identified, predictable solutions is also cognizable.

II. The claimed invention and level of ordinary skill

All four independent claims — 1 (method), 10 (system), 18 (method), 25 (machine-readable medium) — share one core combination:

1. A video server on a network;
2. detecting playback devices coupled to that network;
3. determining a need to provide a video file to them (the specification gives UPnP Media Server Control Point discovery/protocol as the example);
4. reading a video file from a storage module coupled to the video server through at least one standardized port module (spec: USB of any version, IEEE 1394/FireWire, Ethernet; claim 6: USB);
5. providing an "optionally trans-coded" version over the network "to better match one or more limitations and capabilities of the network or the one or more playback devices"; and
6. the key distinguishing clause — the version "is trans-coded in the video server and the entire optionally trans-coded version of the video file is stored in at least one storage module for later retrieval, avoiding the need for the one or more playback devices to wait for real-time trans-coding, before the ... version ... is supplied through the network."

Dependent claims add: acquiring/storing video from a video source (2, 20); disk drive with standardized port (3, 21); the trans-coded version is what is provided (4, 13); trans-coding = format change, compression, and/or bitrate change (5, 14, 19); USB (6, 15, 22); playback devices are UPnP Control Points (7, 16, 23); storing a version on a network-coupled storage device (8); trans-coded version "previously stored" in the storage module (9, 17, 24).

POSITA profile: an engineer with a bachelor's degree in electrical engineering/computer science and 2–4 years' experience in networked consumer video, familiar with MPEG encoding/transcoding, home-network media sharing (UPnP AV / DLNA), and standard storage interfaces (USB/FireWire/Ethernet). All of the operative technologies — UPnP AV (specifications circa 2002–2006), USB/FireWire disk drives, MPEG-2/4 encoders, DVRs, and NAS — were mature well before May 2008.

III. Prior-art reference summaries and element mapping

US6711741B2 (Intel, "Random access video playback system on a network"; filed Apr. 7, 1999). A client–server network video system in which a server provides segments ("temporal snapshots") of source video frames; the client organizes them hierarchically, requests and stores segments, and plays back stored segments with random access. Verbatim claim 1 discloses requesting from the server, "storing a requested segment of source video frames," and "playing back ... a stored segment of source video frames." This teaches a video server reading video from storage and providing it over a network to playback devices on request — elements 1–4 of the claim combination.

US20010047517A1 (Christopoulos, "Method and apparatus for intelligent transcoding of multimedia data"; priority Feb. 10, 2000, published Nov. 29, 2001). Expressly directed to "universal access" — delivering rich multimedia "regardless of the limitations imposed by a client device, client device capabilities, characteristics of the communication link or characteristics of the communication network." The reference discloses two known implementation strategies: (a) storing multiple versions of content at a server, each tailored to a class of client capabilities, which it criticizes for "excessive storage requirements"; and (b) server- or gateway-side transcoding to client/network capabilities (e.g., CIF→QCIF), with transcoding hints (bitrate, resolution, frame size, etc.). This maps directly to the claim's "better match one or more limitations and capabilities of the network or the one or more playback devices" language and to dependent claims 5/14/19 (format/compression/bitrate). Critically for the counter-analysis (Part VI), Christopoulos describes server transcoding as being performed "in real time" at delivery and steers away from storing every possible rendition.

US7023924B1 (EMC, "Method of pausing an MPEG coded video stream"; filed Dec. 28, 2000, issued 2006). A video-file-server environment that streams stored MPEG-2 assets to clients over a network, schedules client requests in "play lists," and (relevant here) discloses that "different clients may present different bandwidth access requests for video from nonscalable MPEG-2 [streams]" and that the server can reduce bitrate/alter video quality to produce a "lower-quality presentation" suited to that client's bandwidth. This teaches server-side creation of reduced-bitrate variants of a stored file keyed to a client's network limitations — overlapping claims 1/4/5/13/14/19 and the "limitations and capabilities of the network" language.

US7764863B1 (BigBand, "System and method for providing trick modes"; parent filed Jan. 8, 2003; provisional Mar. 6, 2002). A network (HFC) media-server architecture in which a server stores a normal-play media stream, builds an index of independently decodable frames, and a "video pump" generates variant (trick-mode) media streams. The patent's abstract confirms it "provides a media stream that complies with the requested display mode." Notably, its innovation is generating trick streams on the fly without previously storing them — again relevant to the counter-analysis, because it, like Christopoulos, points away from storing complete pre-generated variants.

Admitted background art (patent's own FIGS. 1–3 and text). (a) PVRs (TiVo) that record live TV to built-in storage; (b) a Dedicated Device Interface (e.g., NSLU2) with a USB-attached disk that "converts the Storage Module into an UPnP AV Media Server" — i.e., standardized-port-attached conventional storage serving media to UPnP Control Points over a LAN was admittedly known; and (c) NAS appliances serving media files to UPnP Control Points. The '027 inventors' stated problem is not that these functions were unknown; it is that no single box combined (i) cheap, replaceable, standardized-port-attached storage, (ii) recording of live A/V, and (iii) serving/streaming to network playback devices without real-time transcoding delay.

Element-by-element coverage. Detecting playback devices / determining a need (UPnP discovery and browse/select): admitted in the NSLU2-as-UPnP-AV-server and NAS background art, and standard UPnP AV behavior. Reading a video file from a standardized-port-attached storage module: NSLU2-type art (USB) plus Intel '741 (server reading stored segments). Providing a version matched to device/network capabilities: Christopoulos and EMC '924. Server-side transcoding: Christopoulos, EMC '924. Recording of live A/V to the storage: TiVo/PVR background art, optionally combined. The only limitation not squarely met by any single reference is the final clause — the entire pre-transcoded file stored for later retrieval to avoid a real-time transcoding wait.

IV. Proposed obviousness combinations

Combination A — NSLU2-type USB-to-UPnP-server (admitted background) + PVR recording capability (admitted background) + Christopoulos (server transcoding)

• Primarily renders obvious elements 1–5 and 7–8 of claim 1: take the admittedly known "Dedicated Device Interface + USB disk → UPnP AV Media Server" system (FIG. 2 art) and add the admittedly known PVR function of recording a live Video Source (FIG. 1 art) to that USB-attached disk. The result is a video server that records live A/V to conventional USB storage and later serves stored files to UPnP Media Server Control Points on a LAN — the plain reading of claim 1's non-transcoding branch ("optionally trans-coded," as construed in Part VI).
• Christopoulos supplies the capability-matching transcoding: transcode in the server to the target device/network's format, compression, or bitrate (dependent claims 5, 14, 19).
• Motivation: The patent itself articulates the design need — TiVo's built-in disk adds cost, limits capacity, and cannot be replaced without replacing the unit; the NSLU2 approach cannot record or transcode. A POSITA seeking a cheaper, upgradeable, replaceable-storage DVR/media server would naturally graft the PVR's capture/encode path onto the already-available USB-disk UPnP server, using Christopoulos's known transcoding techniques. These are "known elements" combined "in a way that yields a predictable result" (KSR): attaching commodity USB disks and running media-server software were established practices by 2005–2008.

Combination B — Intel '741 (network video server with stored segments) + Christopoulos (intelligent transcoding) + common knowledge of standardized-port storage/UPnP

• Intel '741 supplies the network video server that stores video and provides it to playback clients on request (claim 1 elements: server, network, stored file, providing to playback devices).
• Christopoulos supplies server-side transcoding "suited to the capabilities of the network element"/client (bitrate, resolution, frame size), i.e., the "better match limitations and capabilities" clause and claims 4/5.
• Standard knowledge (and the NSLU2-type admitted art) supplies the "conventional storage attached through a USB/FireWire/Ethernet standardized port" and UPnP detection/browse (claims 3, 6, 7). Replacing Intel's dedicated server storage with commodity USB/FireWire disks was an obvious cost-driven substitution — NAS and NSLU2 devices had made exactly that substitution in home media servers.
• Motivation: A POSITA combining a network video playback server with an "intelligent transcoder" would do so for the reason Christopoulos itself states: heterogeneous clients (TV, PC, phone) and variable networks cannot all decode one bitstream. Intel supplies "video served from storage over a network"; Christopoulos supplies "adapt it server-side." The combination is complementary, not conflicting.

Combination C — EMC '924 (per-client reduced-bitrate server variants) + Christopoulos and/or Intel '741

• EMC '924 teaches a video file server that, facing "different clients [with] different bandwidth access requests," produces reduced-bitrate/reduced-quality versions of a stored nonscalable MPEG stream at the server — closer than any other cited reference to the '027 "match network/device limitations" concept. Combining EMC's server-side bitrate adaptation with Christopoulos's generalized transcoding (format, compression, resolution) and Intel's stored-segment playback yields the full transcoding feature set of claims 1, 4, 5, 13, 14, 19.
• Motivation: Same as Combination B — the known, persistent problem of heterogeneous clients; EMC and Christopoulos are two solutions to the same problem and would naturally be read together.

Combination D — BigBand '863 (network media server generating display-mode-specific streams) + Christopoulos

BigBand teaches a server that stores one program and, per client request, produces a media stream that "complies with the requested display mode" — e.g., different trick-mode renditions with modified timing. Replacing "trick mode" with "transcoded format/bitrate suited to the client," using Christopoulos's transcoding hints, is a straightforward application of a known technique to a known device. This supports obviousness of the capability-matching and server-side-generation concepts.

V. Motivation to combine under KSR — the "entire file stored to avoid real-time transcoding" limitation

The decisive question is whether the final clause — pre-transcode the whole file, store it, then serve it, "avoiding the need for the ... playback devices to wait for real-time trans-coding" — is an obvious design choice. A challenger's best argument:

1. The tradeoff was known and binary. Christopoulos itself frames the design space: either store multiple pre-encoded versions (which it criticizes only for storage cost, not for concept) or transcode at delivery. EMC '924 likewise discloses generating lower-bitrate variants at the server. BigBand's Background concedes that prior methods "generat[ed] and stor[ed] multiple streams." A POSITA facing the well-known problem of startup latency and CPU contention during real-time transcoding would recognize the obvious remedy already present in the art: perform the transcoding earlier (at recording time, during idle time, or while copying from a network storage device — the '027 specification itself admits this "could be performed while the one or more video files are copied ... and stored on the Storage Module") and store the completed rendition for later retrieval. That is "obvious to try" from a finite set of identified, predictable options (KSR).
2. Background/batch transcoding was routine. By 2008, media managers routinely transcoded files in the background into device-specific libraries (e.g., multiple-bitrate VOD libraries, portable-device sync folders). Applying that known pre-processing habit to a home media server with cheap USB storage — where disk space is abundant and the penalty of real-time transcoding (delay, dropped frames, server CPU load) is manifest — yields exactly claim 1's solution.
3. The specification's own admitted art supplies every non-transcoding element, and dependent claims 2–9, 11–17, and 19–24 add only conventional details (recording a source, disk drive, USB, UPnP, previously stored transcode) each of which is individually taught by the references above or by admitted background.

On this view, the combination of (i) the NSLU2-type USB-storage UPnP server (admitted), (ii) PVR recording (admitted), and (iii) Christopoulos/EMC transcoding, plus the well-known practice of completing processor-intensive transcodes before playback rather than during it, renders independent claims 1, 10, 18, and 25 obvious. The "avoiding ... wait for real-time trans-coding" clause reads as the routine engineering rationale for that pre-storing choice, not as a new inventive concept.

VI. The countervailing case (why the claims may survive § 103)

Intellectual honesty requires flagging the significant weaknesses in the obviousness case:

1. The cited art points the other way on the dispositive clause. Christopoulos expressly disparages storing multiple full versions ("excessive storage requirements") and describes server transcoding as performed "in real time." BigBand's entire premise is memory efficiency achieved by generating variant streams on the fly "without a need to previously store them." The '863 specification stresses that prior solutions were costly because they required "generat[ing] and stor[ing] multiple streams." A challenger must overcome the argument that the primary references teach away from pre-storing whole transcoded files — the exact feature the '027 claims were drafted to capture (and the feature the examiner allowed these claims over).
2. No single cited reference, and no obvious pair, squarely teaches the combination. The examiner had all four references before him and still granted the claims. Intel '741 is a browsing/random-access client-server system with no transcoding and no standardized-port storage concept; EMC '924 and BigBand '863 are cable/broadcast VOD infrastructure with dedicated server storage, not consumer "conventional storage" attached by USB; Christopoulos is a general transcoding method with no home-network/media-server context and affirmatively prefers real-time transcoding. The whole-claim combination — consumer video server + commodity standardized-port disk + record + fully pre-transcoded file stored for later retrieval — is not the kind of "predictable variation" of one reference, and assembling it requires selecting and reorienting teachings from disparaging sources.
3. Claim breadth cuts both ways on the "optionally" branch. The phrase "optionally trans-coded version" means the claim must be satisfied whether or not transcoding occurs; the "stored in at least one storage module" and "avoiding ... wait" clauses are conditions on the transcoded alternative. Under that construction the admitted NSLU2-type/UPnP art may well read on the non-transcoded branch — which helps the obviousness challenger. Under a narrower construction requiring the entire pre-transcoded file to have been stored, the challenger needs the pre-storing teaching the cited art resists. Either way, both sides have a plausible reading, and this ambiguity weakens a clean § 103 win for either party.
4. Secondary considerations. The patent survived to assertion (VideoLabs v. TCL, 2:25-cv-00161, E.D. Tex.) and its maintenance fees have been paid through year 12; a challenger would face possible arguments of commercial success of the licensed portfolio and copying, though no such evidence is in the record before me.

VII. Bottom line

• Strongest § 103 case: A POSITA would have found it obvious, by May 2008, to build a video server that (a) records live A/V to cheap, replaceable, standardized-port-attached conventional storage (TiVo/NSLU2 background art), (b) serves stored files to UPnP playback devices over a LAN (NSLU2/NAS background art; Intel '741), and (c) transcodes server-side to match network/device capabilities (Christopoulos '517; EMC '924). The dependent limitations (USB, disk drive, UPnP Control Points, trans-coding actions of format/compression/bitrate) are all individually known.
• Decisive vulnerability: the "entire ... trans-coded version ... stored ... for later retrieval, avoiding ... real-time trans-coding" clause. The cited references either teach real-time/on-the-fly transcoding (Christopoulos, BigBand) or are silent on pre-storing complete renditions. The examiner allowed the claims over exactly these references. Whether a challenger can bridge that gap depends on locating additional pre-2008 art disclosing server-side completion and storage of full transcoded renditions before delivery (e.g., background/offline transcoding libraries or multiple-rendition VOD servers) — art not present in the four citations on the face of the patent and which I did not verify in this analysis.

Sources: US8220027B1 full text and claim set (Google Patents); US6711741B2 claim text (Indiana University virtual library / Google Patents); US20010047517A1 specification and abstract (patentimages / USPTO.report); US7023924B1 abstract and specification (Google Patents / USPTO.report); US7764863B1 abstract and specification (FreePatentsOnline / Google Patents / Eureka-Patsnap). I flag that I did not review the '027 prosecution history (file wrapper), which would show what the examiner and applicants treated as the point of distinction; that history could materially change the obviousness assessment.