US 8645562

I'll verify the patent's bibliographic data and litigation status through searches before summarizing.

Let me search for the specific claims and any 2026 CAFC activity.

Let me pin down the granted claim set and the PTAB outcome.

Verification note

I ran the requested searches (USPTO/PTAB materials, litigation aggregators, and Federal Circuit sources). Findings on the two limits of your request:

• CAFC 2026 dockets: I found no 2026 Federal Circuit docket or 2026 CAFC activity involving 8645562. The only Federal Circuit matter the authoritative patent record identifies is CAFC case 22-1626 (docketed 2022), consistent with an appeal arising from the 2019–2020 litigation wave. If a 2026 docket exists, my searches did not surface it — treat that as a gap, not a negative finding.
• Claims text: The full patent text supplied to me contains the specification, abstract, and figures but not the granted claims section. My claim description below is therefore reconstructed from the specification, the IPR record, and the abstract, and is flagged where uncertain. I have deliberately not substituted the near-identical claim 1 of US 10,027,736 (a separate patent in the same ETRI/Helios family) for the ’562 claims.

Bibliographic summary — US 8,645,562 B2

Assignee discrepancy worth flagging: Google Patents' authoritative text lists the original assignee as ETRI and the Industry-University Cooperation Foundation of Korea Aerospace University, but the PubChem patent record lists a co-assignee rendered as "UNIV SOGANG IND UNIV COOP FOUN" (i.e., a Sogang University industry-academia cooperation foundation). These cannot both be correct as literally stated; I am not auto-correcting either. The February–March 2013 assignment record on the face of the patent names ETRI plus the Korea Aerospace University foundation, so I treat the PubChem entry as likely a data-parsing artifact — but flagging it per the literal-interpretation rule.

Abstract (as granted)

"A method and apparatus for an adaptive Hypertext Transfer Protocol (HTTP) streaming service using metadata of content are provided. The metadata may include one or more BaseURL elements. Uniform Resource Locators (URLs) of segments forming media may be generated based on the BaseURL elements. Additionally, a URL of a segment may be generated by mapping a BaseURL element among the BaseURL elements to a sourceURL attribute of the segment. Segments indicated by generated URLs may be identical to each other."

Plain-language overview of the independent claims

The ’562 patent is an early MPEG-DASH-era filing directed to how an HTTP streaming client builds the URL of a media segment from "BaseURL" metadata — i.e., the base-URL resolution mechanism that underlies the DASH MPD. Points I can ground with confidence:

Claim structure. Per the IPR2020-01338 record, the independent claims are 1, 4, 7, and 10–12, with claims 2–3, 5–6, 8–9, and 13–20 in dependent/other positions. During prosecution, an Examiner's Amendment added to all independent claims the limitation that "the BaseURL element specifies one or more common locations for segments, and the segment is one of the segments." That "common locations" limitation is the feature the PTAB panel and the parties treated as central — indeed, Patent Owner argued the prior-art combination failed precisely because "a limitation goes to the heart of the [invention]" (citing Arendi v. Apple, 832 F.3d 1355, 1363 (Fed. Cir. 2016)).

Claim 1 (method / client side), reconstructed from the specification (uncertain as to exact language):

• receiving metadata of media, where the metadata includes an attribute with one or more BaseURL elements;
• resolving/generating a URL of a segment with respect to a selected BaseURL element;
• sending a request for the segment using that URL (specification says HTTP GET; metadata may carry a range attribute, and the request may ask for the designated bytes);
• receiving the segment and decoding/rendering the media data in it;
• the URL may be absolute or relative, and identical segments must be accessible at multiple locations indicated by URLs resolved against the respective BaseURL elements, with the first BaseURL element serving as the base URI and the others as alternatives.

Claim 4 (independent) — a method in the same family, distinguishing on the base-URL/resolution aspects (specification-level disclosures include the MPD / period / group / representation hierarchy, where a lower-level BaseURL element is resolved against a higher-level one, and the attribute/BaseURLs-element override behavior at lower description levels).

Claim 7 (independent) — the apparatus/terminal counterpart: an access engine that receives the metadata, forms and issues the segment requests using the resolved URL, receives segments and decodes the media data, plus a media engine that receives the media data from the access engine and outputs the media. The specification identifies the access engine as a DASH access engine and the metadata as an MPD (an XML document with a single MPD element).

Claims 10–12 (independent) — further independent claims in the set; based on the specification these concern the URL-generation mapping variant (mapping a BaseURL element to the sourceURL attribute of a segment, where the specification notes sourceURL was changed "from required to optional" because baseURL already provides a complete URL) and/or the multi-component/multi-location delivery variants (multiple UrlTemplate/Url instances per segment, with appearance order indicating importance, and nth InitialisationSegmentURL corresponding to nth location).

Plain-English summary of the inventive core: rather than hard-coding a segment's full address in metadata, the client is given one or more base locations and constructs the segment address from them — and the same segment is meant to be retrievable from any of the listed base locations, which is what makes CDN/caching and failover work in adaptive HTTP streaming. The claim breadth is narrowed by the prosecution-added "common locations" requirement.

Uncertainty statement

• I do not have the verbatim granted claim text of US 8,645,562 in the materials provided, so the plain-language claim descriptions above are reconstructions from the specification, the abstract, the IPR2020-01338 record, and Patent Owner's oral argument. Treat the independent-claim numbering (1, 4, 7, 10–12) and the Examiner's-Amendment "common locations" limitation as well-grounded, and the per-claim scope statements (especially for claims 4, 7, 10–12) as provisional.
• IPR2020-01338: the record confirms institution (2021-02-08) and a Final Written Decision terminating on 2022-02-07, and shows Patent Owner filed a contingent motion to amend (substitute claims 13–20, with 17–20 withdrawn at the hearing). I did not independently retrieve the FWD's operative holding on claims 1–9, so I cannot state with confidence whether the challenged claims were held unpatentable. Do not rely on my summary for that outcome.
• No 2026 CAFC docket for 8645562 was located; the only appellate docket tied to the patent in the authoritative record is 22-1626.

I'll research litigation involving US patent 8645562. Let me search multiple sources.

Let me get more detail on the specific district court cases and their outcomes.

Let me check the remaining cases: Vudu, Crackle outcomes, the CAFC appeal, and any newer campaigns.

Litigation Involving U.S. Patent No. 8,645,562

Important scope note: I interpreted the number literally as 8,645,562 ("the '562 patent," Apparatus and method for providing streaming content). I excluded results for similarly numbered patents (e.g., the many other '562 patents that surfaced in searches, and the related-but-distinct DASH patents asserted in the same campaign). Where available data concerned a different patent in the same portfolio, I've flagged that explicitly.

Bottom line: Yes — the '562 patent has been litigated. It was part of a multi-defendant MPEG‑DASH patent assertion campaign by Helios Streaming, LLC (exclusive licensee) and Ideahub, Inc. (owner), and it was separately challenged and held invalid at the PTAB.

1. District Court Litigation (asserting the '562 patent)

Supporting sources:

• Google Patents family-litigation listing for US8645562 (identifies the Delaware 1:19‑cv‑01978 and 1:19‑cv‑01818 cases, the C.D. Cal. 8:19‑cv‑02140 case, and the CAFC appeal 22‑1626): https://patents.google.com/patent/US8645562/en
• '562 identified in the Vudu complaint and notices: https://storage.courtlistener.com/recap/gov.uscourts.ded.70386/gov.uscourts.ded.70386.1.1_1.pdf
• Claim-narrowing letter listing "Claim 5 of U.S. Patent No. 8,645,562" in the Starz case (Feb. 18, 2021): https://www.docketalarm.com/cases/PTAB/IPR2020-01688/Vudu_LLC_v._Ideahub_Inc/docs/03-04-2021-Petitioner/Exhibit-1086-February_19,_2021_Letter_from_Helios_to_Starz_re_Narrowing_of_Claims.pdf
• Starz dismissal with prejudice (Dkt. 88, Apr. 21, 2021): https://www.courtlistener.com/docket/16435127/88/helios-streaming-llc-v-starz-entertainment-llc/
• Showtime termination date (2021‑08‑04): https://www.drugpatentwatch.com/p/alphasignals/litigation/casename/index.php?query=Helios+Streaming%2C+LLC+v.+Showtime+Digital+Inc.%7C1%3A19-cv-01978
• RPX campaign summary: https://litigation.rpxcorp.com/news/58668-new-video-streaming-campaign-hits-crackle-and-vudu-with-patent-portfolio-originating-with-etri

2. PTAB — Inter Partes Review of the '562 patent

• Proceeding: IPR2020‑01338
• Petitioner: Unified Patents, LLC
• Patent Owner / Respondent: Ideahub, Inc. (Helios Streaming, LLC named a real party-in-interest as exclusive licensing agent)
• Patent challenged: U.S. 8,645,562
• Filed: July 23, 2020
• Institution decision: Feb. 8, 2021
• Final Written Decision: Feb. 7, 2022 — the Board held all challenged claims of the '562 patent unpatentable and denied Patent Owner's motion to amend.
• Appeal: Notice of Appeal filed; Federal Circuit mandate entered June 30, 2022 (per PTAB docket).

Sources:

• IPR2020‑01338 case details: https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2020-01338
• Unified Patents announcement ("Helios Streaming/Ideahub patent held invalid," Feb. 10, 2022): https://www.unifiedpatents.com/insights/2022/2/10/helios-streamingideahub-patent-held-invalid
• Mandatory notice listing RPI and related matters: https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1539562](/patent/1539562)/download-documents

3. Federal Circuit Appeal

• Case No. 22‑1626, Court of Appeals for the Federal Circuit (listed in the Google Patents family-litigation data and referenced in the PTAB docket as a "fed circuit mandate" dated June 30, 2022).
• This appears to be the appeal from the IPR2020‑01338 final written decision. I could not confirm the disposition (e.g., whether affirmed under Rule 36) within the searches completed — treat the outcome as unconfirmed rather than assumed.

4. Related Campaigns — NOT the '562 patent (flagged for accuracy)

The same plaintiffs (Helios/Ideahub) filed additional suits and there is an active UPC campaign, but these assert different patents and should not be listed as '562 litigation:

• Fandango Media, LLC (C.D. Cal., filed Jan. 29, 2021) and NBCUniversal Media, LLC (filed Feb. 9, 2021) — asserted the '414, '830, and one/two other patents; '562 not identified in the retrieved materials.
• UPC cases (e.g., Helios Streaming v. DAZN, UPC_CFI_0001647/2025, filed Nov. 19, 2025; and Rakuten cases, 2026) involve EP 2 613 543 B1, not US 8,645,562. Source: https://ipverse.greyb.com/unified-patent-court/cases/case-details/helios-streaming-v.-dazn-group--upc-cfi-0001647-2025

5. Confidence / Limitations

• High confidence: the '562 patent was asserted in the four district-court cases listed above, and it was invalidated by the PTAB in IPR2020‑01338 (FWD Feb. 7, 2022).
• Medium confidence: exact final dispositions for the Vudu, Crackle, and Showtime cases. The Starz case is confirmed settled/dismissed with prejudice; the Showtime case shows terminated Aug. 4, 2021; the Vudu and Crackle final outcomes were not confirmed in the sources retrieved.
• Not confirmed: the outcome of CAFC appeal 22‑1626, and whether any additional cases named the '562 patent specifically. My final round of targeted searches (Fandango/NBC, Vudu dismissal, CAFC disposition) was cut off, so those points should be verified against PACER/PTAB before being relied upon.

If you want, I can attempt to confirm the Vudu/Crackle/Showtime dispositions and the 22‑1626 Federal Circuit result in a follow-up.

I'll start by researching the PTAB proceedings I can find for this patent, since the structured ODP data says "none" but the patent page itself references IPR2020-01338.

Found the key proceeding. Let me dig into the FWD details, the Federal Circuit appeal, and check for any other PTAB filings.

The Delaware filing references two more IPRs (IPR2020-01688, IPR2020-01689). Let me verify which patents those target and check for any other '562 proceedings.

PTAB / AIA Trial Proceedings — U.S. Patent No. 8,645,562

Data-integrity flag up front. The structured "PTAB proceedings on file" block in this prompt states that the USPTO ODP API returns no AIA trial proceedings for US 8,645,562. That ingest is stale/incorrect. There is at least one AIA trial on this patent — IPR2020-01338 — which is reflected both on the patent's own Google Patents page ("PTAB case IPR2020-01338 filed (Final Written Decision)") and in open PTAB records. I use the ODP list as the starting point but do not treat its "none" as the answer. Where I could not confirm a fact, I say so.

Proceedings overview

One AIA trial proceeding is confirmed on US 8,645,562: IPR2020-01338 — and it is an outright petitioner win with all challenged claims invalidated (breakdown: 1 total, 0 active, 1 with claims invalidated, 0 claims sustained, 0 settled, 0 institution-denied). Because claims 1–9 were all held unpatentable and the patent owner's motion to amend was denied, the bottom-line defensive posture is: the '562 is a dead patent as to the claims that matter — a demand letter or complaint built on claims 1–9 is asserting canceled claims, and the burden is now on Helios/Ideahub to point to some other, unchallenged claim (or a different member of the continuation family), not on you to re-litigate validity.

A second, related point for a defendant: the Federal Circuit appeal was voluntarily dismissed, so there is no appellate opinion either way — the FWD stands unreviewed. That is a final, but not "affirmed," loss for the patent owner.

IPR2020-01338 — Unified Patents, LLC v. Ideahub, Inc.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)

• Filed: 2020-07-23 (petition filed; Notice of Accord Filing Date 2020-08-07)

• Status: "Final Written Decision" (termination date 2022-02-07) — the panel found claims 1–9 unpatentable and denied the patent owner's motion to amend. Note: the verbatim status string in the structured ODP block is none / absent (stale ingest); the "Final Written Decision" label above is taken from the public PTAB docket aggregator.

• Judge panel: Moore, joined by Ullagaddi and Cygan (per Banner Witcoff's PTAB Highlights, identifying Paper 48, dated 2022-02-07, as the FWD). The panel composition is sourced from that secondary summary; I could not independently re-verify the individual APJ names against the E2E docket text.

• Petition grounds (challenging claims 1–9):

  • Claims 1, 2 — unpatentable under 35 U.S.C. § 103(a) over Chen in view of OAI.
  • Claims 3–9 — unpatentable under § 103(a) over Chen, OAI, and 3GPP.
  • Key references: U.S. Patent Application Publication No. 2011/0099594 ("Chen"), which claims benefit of U.S. Provisional 61/255,767 (filed 2009-10-28), relied on as § 102(e) prior art; "The Open Archives Initiative Protocol for Metadata Harvesting," Protocol v2.0 ("OAI"); and 3GPP adaptive HTTP streaming material.

• Institution decision: Instituted 2021-02-08 (Trial Instituted Document, Paper 16). Patent owner pressed a Fintiv/§ 314(a) discretionary-denial argument (parallel Delaware and C.D. Cal. litigations, overlap with Chen, investment by the district courts), but the Board declined to exercise discretion to deny and instituted on all nine challenged claims. Unified's RPI certification (sole RPI) was supported by the Jakel Declaration — relevant because Unified is a defensive aggregator and RPI/privity determines estoppel scope.

• Final Written Decision (2022-02-07): All challenged claims 1–9 held unpatentable. Verdict table from the FWD:

  Claims	Statute	References / Basis	Claims Shown Unpatentable	Claims Not Shown Unpatentable
  1, 2	§ 103(a)	Chen, OAI	1, 2	—
  3–9	§ 103(a)	Chen, OAI, 3GPP	3–9	—
  Overall			1–9	—

  The Board's disposition: "Petitioner establishes by a preponderance of the evidence that claims 1–9 are unpatentable."

• Motion to Amend (Patent Owner): Patent owner moved to substitute claims 13–20 for claims 1–9. The Board denied the motion as to substitute claims 13–16 (unpatentable under § 103(a) over Chen, OAI, 3GPP, and Brueck; substitute claims 15 and 16 additionally indefinite under § 112(b)) and dismissed as moot as to substitute claims 17–20, which the patent owner withdrew at the 2021-11-12 oral argument after conceding they may be broadening. Net effect: no amended claims issued — the '562 was not narrowed, it was invalidated.

• Procedural highlights: oral argument 2021-11-12; a patent-owner Motion to Exclude (directed in part at petitioner's expert, Dr. Didier J. LeGall) was denied; petitioner's expert opinion was credited over a hindsight-bias attack. The FWD expressly notes that if the patent owner wants to amend, it must pursue reissue or reexamination.

• Settlement / termination: No settlement of the IPR. The proceeding ran through a full FWD; the later appeal was dismissed by agreement (see below), and the settlement terms — if any — are not public.

• Appeal: Yes. Patent owner Ideahub, Inc. v. Unified Patents, Inc., No. 2022-1626 (Fed. Cir.), appealing the PTAB's IPR2020-01338 decision. By nonprecedential order dated 2022-04-21, the Federal Circuit DISMISSED the proceeding under Fed. R. App. P. 42(b) ("The parties having so agreed"), each side bearing its own costs; the mandate was docketed 2022-06-30. There is no merits opinion — no § 103 or claim-construction ruling from the court.

  • CAFC order: https://cafc.uscourts.gov/opinions-orders/22-1626.ORDER.4-21-2022_1939717.pdf

• Defensive value: Maximal for the challenged claims. Claims 1–9 — including independent claims 1 and 7 and their dependents — are canceled. An infringement theory built on any of claims 1–9 is built on claims that no longer exist, and res judicata/collateral estoppel plus the cancellation certificate make those claims unassertable. Because the appeal was dismissed rather than decided, there is no adverse appellate precedent to work around.

Primary sources / links

• PTAB E2E proceeding record (IPR2020-01338, U.S. Patent 8,645,562): https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1539562](/patent/1539562)
• FWD (Paper 48, 2022-02-07) — public copy: https://bannerwitcoff.com/wp-content/uploads/2022/02/IPR2020-01338.pdf
• Petitioner's background summary: https://www.unifiedpatents.com/insights/2022/2/10/helios-streamingideahub-patent-held-invalid
• Patent page (confirms IPR2020-01338 and CAFC 22-1626): https://patents.google.com/patent/US8645562/en

Strategic summary

Which claims are canceled vs. sustained vs. untested. The IPR reached exactly one claim set: claims 1–9 — all canceled. No claim of the '562 was sustained. Critically, the panel also refused to let the patent owner substitute new claims, so there is no surviving amended claim to fall back on. I could not verify the total claim count of the '562, so I will not assert that "all claims" of the patent are gone: what is certain is that claims 1–9 (the only claims challenged) are invalidated, and any claim of the '562 that was not part of this IPR is untested. Treat "untested claim" as an open question the patent owner must affirmatively establish — and note that if such claims depend from canceled claims 1–9, they fare no better.

Estoppel landscape. Because this was a fully instituted IPR that reached an FWD, 35 U.S.C. § 315(e)(2) bars Unified Patents, LLC (and its RPIs/privies) from asserting in a civil action or ITC proceeding any ground raised or that reasonably could have been raised in IPR2020-01338 (Chen, OAI, 3GPP, Brueck, and reasonable combinations). That estoppel attaches to Unified, not automatically to the streaming defendants (Vudu, Showtime, Crackle, Starz) — unless privity/RPI is established. For a defendant currently asserted against today, the practical reality is more favorable than estoppel: the claims themselves are gone, so the prior-art fight moves to whatever claims the patent owner asserts next. On those untested claims, no § 315(e) estoppel restricts you (subject to your own IPR filings), and the full universe of § 102/§ 103 art — including the Chen/OAI/3GPP/Brueck combination that killed claims 1–9 — remains available as persuasive (though non-binding) evidence.

Pattern signals.

• Petitioner type: Unified Patents, LLC — a defensive aggregator/subscription membership organization, not a defendant. Unified certified itself as the sole RPI, which limits how far estoppel reaches into its members. Unified also launched a crowdsourced invalidity bounty against the Chinese family member CN 103081504, the counterpart to the '562 — evidence of a coordinated campaign, not a one-off filing.
• Serial/companion filings: The Helios/Ideahub Delaware litigation put three PTAB proceedings in play — IPR2020-01338 plus IPR2020-01688 and IPR2020-01689 (Vudu, LLC v. Ideahub, Inc.), with the parties jointly moving to stay the district cases pending all three (institution decisions on '688/'689 expected mid-to-late April 2021). ⚠️ I could not confirm from the available sources which patents IPR2020-01688 and IPR2020-01689 target — the joint stay motion does not tie them to the '562, and the other IPRs in the family that surfaced in my search (IPR2020-01538, IPR2020-00702, PGR2022-00044) involve different patents (e.g., U.S. 10,588,554 and U.S. 11,122,274). Do not assume '688/'689 are '562 IPRs. This is the single biggest open item to verify on PTAB E2E.
• Patent-owner posture: Ideahub/Helios did appeal (No. 2022-1626) but then voluntarily dismissed — a pattern more consistent with a business decision or a negotiated resolution than with a principled merits challenge. They have not filed a reissue/reexamination to date on the '562 (no public record surfaced).
• Family is alive: Helios/Ideahub continue to prosecute and hold continuation patents in the same DASH/streaming family (e.g., U.S. 11,343,296; 11,082,470; 10,812,553; 10,645,136; 10,313,414; and the asserted '736, '830, '660, '413/414, '145, '130, '373, '805, '558, '493). Canceling the '562 does not end the campaign — expect assertion to migrate to these siblings.

Recommended next steps

1. If you are a defendant facing the '562 (or a demand letter citing it): cite IPR2020-01338's FWD and the resulting cancellation. The FWD states, verbatim in its disposition: "ORDERED that Petitioner establishes by a preponderance of the evidence that claims 1–9 are unpatentable; FURTHER ORDERED that Patent Owner's Motion to Amend is denied in part as it relates to proposed substitute claims 13–16; … dismissed in part as it relates to withdrawn proposed substitute claims 17–20." FWD (Paper 48, 2022-02-07): https://bannerwitcoff.com/wp-content/uploads/2022/02/IPR2020-01338.pdf. Any infringement count resting on claims 1–9 should be dismissed — those claims were canceled, and the appeal (No. 2022-1626) was dismissed under Rule 42(b) on 2022-04-21, leaving the FWD final.
2. Pin down the patent owner's theory of the case before doing anything else. Ask Helios/Ideahub to identify, in writing, which claim(s) of the '562 it still asserts — because claims 1–9 cannot be asserted. If it pivots to another family member, demand the specific patent and claim; then assess (a) whether that claim was challenged in any IPR tied to that patent (check E2E), and (b) whether you have your own § 315(b) one-year window and § 102/§ 103 grounds.
3. Verify the companion proceedings. Confirm on PTAB E2E whether IPR2020-01688 and IPR2020-01689 are '562 IPRs. Use the PTAB E2E search and the docket aggregator listing (https://www.docketalarm.com/cases/PTAB/IPR2020-01338/Unified_Patents_LLC_v._Ideahub_Inc/) to nail down target patents, institution outcomes, and any estoppel consequences for Vudu.
4. Track the family, not just this patent. Because Helios has been re-filing continuations, set monitoring on the assignee (Helios Streaming, LLC / Ideahub, Inc.) and on the ETRI / Korea Aerospace University priority lineage. New continuations are where the next assertion is most likely to come from.
5. No active proceedings to schedule around. There is no live PTAB trial on the '562 today — nothing has a pending institution-deadline, oral hearing, or statutory § 316(a)(11) one-year FWD due date. The relevant clock is now district-court (any suit on the sibling patents), not PTAB.

Confidence / caveats

• High confidence: IPR2020-01338 exists; Unified Patents was petitioner vs. Ideahub; claims 1–9 challenged and all held unpatentable under § 103(a) over Chen + OAI (claims 1–2) and Chen + OAI + 3GPP (claims 3–9); motion to amend denied (substitutes 13–16 unpatentable, 17–20 withdrawn); institution 2021-02-08; FWD 2022-02-07; CAFC No. 2022-1626 dismissed 2022-04-21.
• Medium confidence: individual APJ names for the panel (sourced from Banner Witcoff's PTAB Highlights: Moore, Ullagaddi, Cygan).
• Not verified / do not rely on: whether IPR2020-01688 and IPR2020-01689 target the '562; the total number of claims in the '562; the existence of any settlement between Unified and Ideahub underlying the Rule 42(b) dismissal; and whether any reissue or reexamination of the '562 is pending. These should be confirmed on PTAB E2E before use.

I'll reconstruct this from the authoritative Google Patents legal-events data provided plus live sources. Let me verify the ownership chain, litigation, and NPE details.

Strong results. Now let me pin down reel/frame numbers, the correspondent of record, and the litigation/appeal outcomes.

US 8645562 B2 — Ownership & Assignment Reconstruction

Scope note / data limitation (read first): The assignment events below are grounded in the Google Patents legal-events record supplied with this task (which is drawn from USPTO assignment data) plus litigation and PTAB filings. I was not able to retrieve the actual reel/frame numbers or the USPTO-recorded correspondent-of-record fields from Assignment Center during this session. Rather than fabricate reel/frame values, I flag each entry as [reel/frame not obtained] and give the correspondent evidence I can source. Verify each reel/frame at the Assignment Center search page before relying on it in a filing.

Inventors

All eight named inventors, per the front page and the complaints:

Patterns worth noting:

• The joint assignee Industry-University Cooperation Foundation of Korea Aerospace University on the issued face confirms that at least one inventor (most plausibly Jae Gon Kim, who later joined KAU's faculty) had a KAU affiliation at filing. Plaintiffs' complaints state only that "most inventors" were ETRI researchers — consistent with a mixed ETRI/KAU inventorship group.
• This is not a product-company invention team that dispersed; it is a government research institute team. Two inventors (Thang → University of Aizu, Japan; Jae Gon Kim → KAU) moved into academia, which is routine for a national lab and is not by itself a fire-sale precursor.
• The inventors assigned their rights to ETRI + KAU Foundation by an assignment recorded 2013-03-05 — roughly 18 months after the 2011-09-06 PCT filing and ~30 months after the 2010-09-06 priority date. Late recordation is common for Korean government-lab filings.

Original assignee

Electronics and Telecommunications Research Institute (ETRI) and Industry-University Cooperation Foundation of Korea Aerospace University (joint).

• ETRI — South Korea's government-funded national IT research institute (Daejeon). Primary line of business: publicly funded R&D, not product sales. Status: operating. It is a standards participant and a key contributor to MPEG-DASH (ISO/IEC 23009-1); its complaints describe 1,800+ research staff and 16,000+ patent filings. ETRI did not ship a commercial product embodying the claims — the "embodiment" of this patent family is the MPEG-DASH standard itself, which is precisely why the portfolio was monetized as standard-essential.
• Industry-University Cooperation Foundation of Korea Aerospace University — university technology-transfer foundation; operating. It held a minority co-owner interest (see the April 30, 2018 agreement revenue splits below).

Assignment timeline

Reel/frame values could not be verified in this session. Each entry below is sourced to the Google Patents legal-events record (event dates are as listed there; where Google lists only a recording date, the execution date is noted as unverified).

• 2011-09-06 (application filing) / recorded 2011-09-06 — [reel/frame not obtained]

  • Conveyance: Initial filing / priority to US13/820,955 (national-stage of PCT, KR priority 2010-09-06)
  • Assignor: Inventors (via PCT filing)
  • Assignee: ETRI and Industry-University Cooperation Foundation of Korea Aerospace University
  • Correspondent: not obtained
  • Context: Original filing by the government lab and its university co-owner.

• Execution date unverified / recorded 2013-03-05 — [reel/frame not obtained]

  • Conveyance: Assignment (Assignment of Assignors' Interest)
  • Assignor: KIM, Jae Gon; LEE, Jin Young; RYU, Won; PARK, Sang Taick; THANG, Truong Cong; BAE, Seong Jun; KANG, Jung Won; JUNG, Soon Heung (all eight inventors)
  • Assignee: Electronics and Telecommunications Research Institute + Industry-University Cooperation Foundation Korea Aerospace University
  • Correspondent: not obtained
  • Context: Inventor → institutional assignment; confirms the original joint ownership split.

• 2018-06-22 (recorded) — [reel/frame not obtained]

  • Conveyance: Assignment
  • Assignor: Industry-University Cooperation Foundation Korea Aerospace University
  • Assignee: IDEAHUB INC
  • Correspondent: Hyungseok "Harold" Ko (per RPX's reading of the recorded Ideahub→Helios agreement and the ETRI→Ideahub assignment; Ko also served as correspondent on the ETRI→Ideahub leg). Flag: Ko recurs across this chain and is the shared registered-agent contact for other litigating NPEs — see Signal 3.
  • Context: Transfer-to-monetizer — university co-owner's stake sold into the 2018 ETRI/Ideahub monetization deal.

• 2018-08-01 (recorded) — [reel/frame not obtained]

  • Conveyance: Assignment
  • Assignor: Electronics and Telecommunications Research Institute (ETRI)
  • Assignee: IDEAHUB
  • Correspondent: Hyungseok "Harold" Ko (same correspondent as the KAU leg above)
  • Context: Transfer-to-monetizer — the bulk of the portfolio moves to Ideahub under the April 30, 2018 "Patent Assignment Agreement" between ETRI and IDEAHUB. Per RPX's reading of the recorded agreement, ETRI, Intellectual Discovery Co., Ltd. (22% revenue share), and Korea Aerospace University each retained a royalty interest in assertion proceeds. Ideahub describes itself publicly as a Korean patent monetization firm.

• 2018-08-02 (recorded) — [reel/frame not obtained]

  • Conveyance: License
  • Assignor: IDEAHUB
  • Assignee: HELIOS STREAMING, LLC
  • Correspondent: Hyungseok "Harold" Ko (correspondent on the Ideahub-to-Helios agreement per RPX); Helios lists the same Delaware registered-agent address as Ko — 8 The Green, Suite A, Dover, DE (also the address of litigating NPE SynKloud Technologies, LLC) — recurrence flag.
  • Context: Exclusive license to a litigation vehicle. Per the recorded agreement (as reported by RPX), Helios funds the campaign with investment from Korea Patent Investment Corporation (KRW 2.5B) and Ideahub (KRW 1.8B), and must pay Ideahub 37.5% of Adjusted Net Royalties until KPIC recovers, then 100% until Ideahub recovers, then a residual share. This is a funded NPE assertion structure, not an ordinary IP transfer.

• 2022-01-11 (recorded) — [reel/frame not obtained]

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: IDEAHUB INC.
  • Assignee: HELIOS STREAMING, LLC
  • Correspondent: not obtained
  • Context: Title consolidation into the NPE. Note the timing tension: Helios was styled an "exclusive licensee" through the 2019–2021 litigation and the IPR2020-01338 mandatory notices (where Ideahub certified it was "the owner"), yet this 2022-01-11 record moves the underlying title to Helios. It was recorded one month before the 2022-02-07 PTAB final written decision and while the Federal Circuit appeal 22-1626 was pending. Google Patents now lists the current assignee as Helios Streaming LLC. Treat the exact execution date as unverified — only the recording date is in the record above.

Net recorded links: 6 (filing; inventor assignment 2013; KAU→Ideahub 2018-06-22; ETRI→Ideahub 2018-08-01; Ideahub→Helios license 2018-08-02; Ideahub→Helios assignment 2022-01-11). Plus the un-recorded-in-this-record April 30, 2018 Patent Assignment Agreement that RPX states was not attached to the assignment records.

Timeline diagram

timeline
    title Ownership of US 8645562
    2010 : Priority date 2010-09-06
    2011 : PCT application filed by ETRI and KAU Foundation
    2013 : Inventors assign to ETRI and KAU Foundation
    2014 : Patent issued 2014-02-04
    2018 : KAU Foundation stake to IdeaHub Inc
         : ETRI stake to IdeaHub
         : IdeaHub grants exclusive license to Helios
    2019 : Helios and IdeaHub sue Vudu Crackle Showtime Starz
    2022 : IdeaHub assigns title to Helios Streaming
         : PTAB invalidates claims 1 to 9

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
Patent moved from an operating/government research assignee (ETRI + KAU Foundation) into a licensing vehicle. Ideahub describes itself as a "patent monetization firm" (Seoul) with five "licensing programs"; Helios Streaming, LLC is a Delaware single-purpose LLC at 9880 Irvine Center Drive, Suite 200, Irvine, CA, with a Delaware registered-agent address (8 The Green, Suite A, Dover). No products in commerce for either. Supported by the 2018-06-22, 2018-08-01 and 2018-08-02 recordings. [reel/frame not obtained]

2. Known asserter in the chain — PRESENT.
Helios Streaming, LLC is publicly identified as an NPE by both Unified Patents and RPX ("licensed to and asserted by Helios Streaming, LLC, an NPE"; RPX: "Korean NPE launches offensive"). Ideahub shares management with Glocom, Inc., parent of litigating NPEs SIPCO LLC and Modern Telecom Systems, LLC. Supports 2018-08-02 and 2022-01-11 entries. [reel/frame not obtained]

3. Repeat correspondent across the chain — PRESENT.
Hyungseok "Harold" Ko appears as correspondent on both the ETRI→Ideahub assignment and the Ideahub→Helios license agreement, and Helios's registered-agent address (8 The Green, Suite A, Dover) is the same address Ko uses and the same address used by litigating NPE SynKloud Technologies, LLC (per RPX). This is recurrence across the chain and across unrelated NPE families — the hallmark tell. Caveat: because I could not pull the raw Assignment Center correspondent fields, this rests on RPX's reporting of the recorded documents rather than on a first-hand reel/frame read.

4. Cascading transfers — PRESENT.
Three recordings within six weeks (2018-06-22 KAU→Ideahub; 2018-08-01 ETRI→Ideahub; 2018-08-02 Ideahub→Helios), all effectively one coordinated transaction under the April 30, 2018 agreement, with the Helios leg recorded ~24 hours after the ETRI leg. A fourth leg (2022-01-11 Ideahub→Helios) completes the chain. Chained LLCs + shared correspondent (Ko) + shared address satisfy this signal.

5. Pre-litigation transfer — PRESENT (structure), but OUTSIDE the strict 6-month window on the license leg.
The Helios exclusive license was recorded 2018-08-02; the first suits naming this patent (Vudu 1:19-cv-01792; Crackle 1:19-cv-01818; Showtime 1:19-cv-01978; Starz 8:19-cv-02140) were filed 2019-09-24 onward — i.e. ~13.7 months later, so the literal "within 6 months" test is not met. However the chain was plainly arranged to enable assertion: Helios's notice letter to Vudu is dated 2018-08-23, three weeks after the license. The 2022-01-11 title consolidation to Helios, meanwhile, lands during the pending IPR and Federal Circuit appeal — worth noting as a standing/ownership cleanup rather than a pre-suit transfer.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 evidence for ETRI, the KAU Foundation, Ideahub, or Helios. The 2018 transfer was a monetization deal with retained royalties, not a distress sale.

7. Privateering — PRESENT in a non-classic form (research-institute monetization back-end).
ETRI (the original developer) did not itself sue; it transferred to Ideahub and retained a revenue share ("ETRI Distribution Share"; 22% to Intellectual Discovery Co., Ltd.; plus a KAU share) under the April 30, 2018 Patent Assignment Agreement, with further milestone payments from Helios to Ideahub. That is a monetization-back arrangement where the originator profits from assertion. It differs from textbook competitor-directed privateering (e.g. an operating company funding suits against rivals) because ETRI is a public research institute, not a market competitor of Vudu/Showtime/Starz.

8. Defensive aggregator (anti-NPE) — NOT PRESENT as an assignee; present only as an adversary.
The chain terminates at Helios Streaming, LLC (the asserter), not at RPX, AST, LOT, Unified Patents, or OIN. Unified Patents is a petitioner, not an assignee — it successfully invalidated the patent (IPR2020-01338, petition filed 2020-07-23; instituted 2021-02-08; final written decision 2022-02-07 holding claims 1–9 unpatentable and denying Helios's motion to amend). So the patent is neutralized in practical effect by judgment, not acquired into a defensive pool. Note the status: Google Patents lists "Expired – Fee Related," anticipated expiration 2031-09-06 — consistent with the portfolio being abandoned after the IPR loss.

Verdict

NPE — high confidence.

The '562 patent was moved out of a government research institute and its university co-owner into a Korean monetization firm (Ideahub, 2018-06-22 and 2018-08-01 recordings), then exclusively licensed the next day to a single-purpose Delaware LLC (Helios Streaming, 2018-08-02) that is publicly classified as an NPE by both Unified Patents and RPX, and finally had legal title transferred to that same LLC (2022-01-11) — with one repeat correspondent (Hyungseok "Harold" Ko) and a shared Dover registered-agent address linking the links and tying Helios to at least one other litigating NPE (SynKloud Technologies). The patent was asserted against Vudu, Crackle/Sony, Showtime/CBS, and Starz, and was held invalid on all challenged claims in IPR2020-01338 (FWD 2022-02-07), with the Federal Circuit appeal docketed as 22-1626. Signals 1–4 and 7 are present; only the strict 6-month pre-litigation window (Signal 5) and bankruptcy (Signal 6) fail.

Verification link: https://assignmentcenter.uspto.gov/ (search patent number 8645562; also indexed at https://assignment.uspto.gov/patent/index.html). Action item: pull reel/frame and the correspondent field for each of the six recordings above and replace the [reel/frame not obtained] placeholders — the correspondent recurrence in Signal 3 should be confirmed first-hand before it is relied on.

Caveats: Reel/frame numbers were not available to me in this session and are not asserted here. The April 30, 2018 ETRI↔IDEahub "Patent Assignment Agreement" and the revenue-share terms are drawn from RPX's reporting of recorded documents and are not independently verified. The 2022-01-11 assignment's execution date is unknown — only its recording date appears in the record.

I'll research US Patent 8645562 and its cited references. Let me start with searches to pin down the patent and its citation records.

Let me look for the specific "References Cited" / patent citation records for US8645562.

The patent text I have doesn't include the "References Cited" section. Let me search the IPR2020-01338 proceeding and other litigation records, which typically enumerate the prior art for this patent.

Analyst Response — US 8,645,562 B2

1. Patent identification (confirmed from the authoritative record)

This is the correct record; no similar-number substitution has been made.

2. Critical limitation on the requested citation list — please read

You asked me to identify each patent citation for US 8,645,562 and map each reference to the claim(s) it potentially anticipates under 35 U.S.C. § 102.

I could not retrieve the patent's "References Cited" (front-page (56)) list, and I will not fabricate it. Two specific reasons:

1. The authoritative full-text you supplied omits the citation section. The provided Google Patents extraction for US 8,645,562 runs from the bibliographic data, classification tree, definitions, description, and claims, but it does not include the "(56) References Cited" block or the "Cited By" list. Those lists are exactly what your request targets, and they are not present in the source I was given.

2. My searches did not surface the citation list. Queries against the patent number returned the abstract/description and litigation metadata (correctly, and only for US 8,645,562), but no page that enumerated the examiner-cited or applicant-cited references. Because the operating rule is to prefer retrieved results over recollection and to disclose uncertainty rather than invent specifics, I am flagging this gap rather than filling it with plausible-sounding but unverified patent numbers.

Therefore, any enumerated "full citation / date / description / anticipated claims" table I produced from memory right now would be unverified and potentially false, which would be worse than useless for a § 102 analysis. I will not do that.

3. What I can reliably tell you about the relevant prior art landscape

Grounding statements in the patent's own text (authoritative), the technology area is unambiguous: HTTP adaptive streaming (MPEG-DASH and its 3GPP precursor). This tells us precisely where the § 102 references will sit, even though I can't yet cite them by number:

• The specification repeatedly anchors to 3GPP adaptive HTTP streaming ("the term period may be used as a term of 3rd Generation Partnership Project (3GPP) adaptive HTTP streaming"; "the term segment may be used as a term of 3GPP adaptive HTTP streaming").
• It invokes RFC 2616 as the HTTP substrate (HTTP/1.1 GET and partial GET; byte-range requests).
• It references MPEG-21 DIA types extensively (the syntax tables extend dia:DIADescriptionType, dia:ReferenceType, dia:AdaptiveQoSType, dia:UFDataType, etc.), and ISO base media file format / ISO-IEC 14496-12 and MPEG-2 TS (ISO/IEC 13818-2).
• The claimed subject matter (see §4) is URL resolution against BaseURL elements in MPD metadata. So the anticipatory art you will be looking for is: (a) the 3GPP TS 26.234 adaptive HTTP streaming releases, (b) the ISO/IEC 23009-1 (MPEG-DASH) drafts, (c) MPEG-21 DIA documents, and (d) earlier HTTP-streaming patents/applications that describe base-URL + relative-segment-URL resolution.

I can state the field and category of the prior art with confidence; I cannot, without the actual (56) list, state that any specific reference "anticipates claim X."

4. Claim structure that any § 102 analysis must be run against

The anticipation mapping you requested must be keyed to the actual claims. From the authoritative text, the claim set includes at least:

• A method (independent) claim — the summary restates it: receiving metadata of media, the metadata including one or more BaseURL elements; sending a request for a segment of the media using a URL of the segment, the URL being resolved with respect to a BaseURL element; receiving the segment; and decoding and rendering data of the media included in the segment.
• Dependent features appearing in the summary/description that narrow the independent claim: HTTP GET method; a range attribute with a byte-range request; URL being absolute or relative; identical segments accessible at multiple locations via respective BaseURL elements; first BaseURL element as basic URI and others as alternative BaseURL elements; optional sourceURL attribute with a BaseURL element mapped to it; metadata being an MPD; media comprising a sequence of periods; MPD-level vs. period-level vs. group-level vs. representation-level BaseURL elements, each resolved against the higher level.
• An apparatus/terminal (independent) claim — an access engine (receives metadata, sends the request using a URL resolved with respect to a BaseURL element, receives the segment, decodes the data) and a media engine (receives the data and outputs the media).

For a rigorous § 102 chart, each of these limitations — especially the multiple-BaseURL / resolved-URL and sourceURL-mapping features — is the distinguishing element that the anticipatory reference must disclose. That is the correct analytic frame, but the identification of which reference does so cannot be responsibly asserted without the (56) records.

5. Litigation/enforcement context (verified from the authoritative record)

The provided record shows this patent has been heavily contested — useful because the IPR and district-court filings do contain the prior-art enumerations you want:

• PTAB: IPR2020-01338 — filed; listed as reaching a Final Written Decision (petitioner: Unified Patents).
• Delaware District Court: cases 1:19-cv-01978 and 1:19-cv-01818.
• California Central District Court: case 8:19-cv-02140.
• Court of Appeals for the Federal Circuit: case 22-1626.
• Family member noted in third-party reporting: CN 103081504 (the Chinese family member challenged by Unified Patents); reporting characterizes this family as "a video-on-demand patent based on the MPEG-DASH standard," used against Showtime, Vudu, Crackle, and Starz.

The IPR2020-01338 petition and its exhibit list (e.g., EX1001 patent, prior-art exhibits) are the single best source for the ground-truth prior-art set, because an IPR petitioner must identify the specific § 102/§ 103 references and map them to claims.

6. What I recommend to complete the exact request

To produce the verified per-reference table (full citation → date → description → anticipated claims), retrieve the following, none of which I was able to open in this session:

1. Google Patents → US8645562B2 → "Citations" / "Patent Citations" tab (examiner-cited and applicant-cited references with dates).
2. USPTO Patent Center / PatFT for US 8,645,562 — the front page "(56) References Cited" and "References Cited by Examiner" listings.
3. IPR2020-01338 papers (petition + exhibits) on the Unified Patents PTAB portal (portal.unifiedpatents.com/ptab/case/IPR2020-01338) — gives the applied prior-art references and claim mapping directly.
4. Espacenet / Global Dossier for the search report on the family (the WO/PCT search report for this family will list the X/Y-category references).

Bottom line

• Patent identified correctly: US 8,645,562 B2 (app. 13/820,955), priority 2010-09-06, granted 2014-02-04, now Helios Streaming, LLC; subject of IPR2020-01338 and multiple district-court suits.
• Technology / prior-art field identified with confidence: HTTP adaptive streaming (3GPP TS 26.234, ISO/IEC 23009-1 MPEG-DASH, MPEG-21 DIA, RFC 2616, ISO base media file format, MPEG-2 TS).
• The specific "each patent citation … which claim it anticipates" table could not be produced because the provided authoritative text omits the (56) citation block and my searches did not return the citation list. I am explicitly declining to invent those references or their § 102 mappings rather than present unverified citations.

If you can supply the patent's front-page "(56) References Cited" block (or the IPR2020-01338 exhibit list), I will construct the requested per-reference citation/date/description/anticipated-claim analysis against the actual claims.

I'll research the prior art actually at issue for this patent — particularly the IPR2020-01338 grounds — before building the § 103 analysis.

Now let me pin down the specific prior-art references and the FWD's claim-by-claim outcome.

Let me confirm the Chen reference identity and the FWD's ultimate holding on claims 1–9.

Obviousness Analysis — U.S. Patent No. 8,645,562 B2 under 35 U.S.C. § 103

Builds on: the prior bibliographic and litigation sections. Where those sections flagged open items, I resolve them below and mark the resolutions.

Note on "the Prior Art section of this page": the Google Patents page supplied to me renders only prior-art keywords ("media, segment, baseurl, url, metadata") and a prior art date of 2010-09-06 — the page text I was given does not include a "Citations / Cited By" listing. I therefore ground this analysis in the prior art that was actually adjudicated against these claims: the references relied on in IPR2020-01338. That is a narrower but far more probative set than a search-result list, and it has the advantage of being tested by an expert, cross-examined, and ruled on by the Board.

1. Legal framework applied

Claim 1 as construed by the Board is short and structural. The FWD reproduces it verbatim (element labels are Petitioner's, adopted by the Board):

1. [1.P] A method for providing media, the method comprising:
[1.a] receiving metadata of media, the metadata comprising one or more BaseURL elements;
[1.b] sending a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, the URL being resolved with respect to a BaseURL element;
[1.c] receiving the segment; and
[1.d] decoding and rendering data of the media that is included in the segment,
[1.e] wherein the request is sent using an HTTP GET method, the BaseURL element specifies one or more common locations for segments, and the segment is one of the segments.

Correction to my earlier summary: the earlier section stated that claim 1 "resolves/generates" a URL and did not have the verbatim text. I now have it. The two things that matter for § 103 are (i) the claims recite only "metadata … comprising one or more BaseURL elements" — not an MPD, not a hierarchy, not multiple BaseURLs — and (ii) element [1.e] is the prosecution-added "common locations" limitation. The earlier section separately flagged independent claims 1, 4, 7, 10–12; Patent Owner's Response confirms: "claims 1, 4, 7, 10, 11, and 12 are independent claims." The IPR challenged only claims 1–9.

2. The prior art actually at issue

Prior-art status notes (literal, no auto-correction): Chen's publication date (2011-04-28) postdates the 2010-09-06 priority date, so Chen is not § 102(b) art; it is available under pre-AIA § 102(e) on the strength of its 2009-10-28 provisional and 2010-05-24 non-provisional filing. Brueck's patent date (2010-10-19) likewise postdates the priority date; it is available under § 102(e) as of its own (earlier) filing. 3GPP (2010-03) and OAI (2002) are printed publications under § 102(b). MPEG DASH itself (ISO/IEC 23001-6) is not usable — the record shows it as an "ISO/IEC CD 23001-6, Oct. [2010]" draft, i.e., after the priority date; the family's own IDS cites it, but it does not qualify as prior art here.

3. The combinations and why a POSITA would have made them

The Board adjudicated exactly two grounds, and the same combinations carry the full claim set:

Motivation to combine Chen with 3GPP — the strongest and most specific rationale

Chen does not merely occupy the same field as 3GPP — Chen is expressly built on 3GPP files. The petition's showing for claim 3 quotes Chen: a server names "3GPP files of each presentation corresponding to a scene lasting from time T to time T+N using a naming convention similar to '[program]_preX_T_T+N'." A POSITA implementing Chen's MPD would therefore have consulted the very standard Chen's files are named and organized under — 3GPP TS 26.234 Release 9 — to learn the schema for the MPD, the level-specific baseURL attributes, and the URL composition rules. This is a reference-internal motivation, not hindsight: the artisan is not asked to import a stranger's disclosure, but to look up the spec that the primary reference invokes by name.

Motivation to combine Chen with OAI

1. Same field of endeavor / common problem. Dr. LeGall's declaration (¶¶ 141–142) frames all three as "techniques for providing media content," each supplying a client with metadata that identifies where resources live over HTTP. OAI's § 4.6 expressly describes syntax for retrieving information about video content.
2. It supplies the "element" form of the base URL. Chen uses URLs but does not frame the base URL as a discrete metadata element; OAI § 3.1.1 does — the base URL "specifies the Internet host and port, and optionally a path, of an HTTP server acting as a repository." Appending that well-known construct to an XML metadata document is a predictable, off-the-shelf combination of known elements (KSR).
3. A POSITA's own efficiency motivation. Once a manifest lists dozens or hundreds of segments, enumerating a full host+path per segment is wasteful and brittle; factoring out a single base location that the client composes against is the ordinary engineering response — and it makes the manifest portable across mirrors. That is exactly the "common locations" idea, arrived at without the claims.

Motivation to combine 3GPP, and Brueck — the PO's own arguments supply it

For the group / representation-level features (which appear only in Patent Owner's proposed substitute claims 14 and 18, and in the specification), Petitioner argued, and the Board accepted, that "it would have been a matter of routine optimization to insert Brueck's group level into 3GPP's hierarchy" (citing In re Aller), motivated by latency reduction and bitrate adaptation — "allowing a client to request varying bitrate streams depending upon network conditions" — with a reasonable expectation of success. Dr. LeGall: a POSITA "would have been motivated to experiment with adding Brueck's group level into 3GPP's hierarchy and had a reasonable expectation of success in adding an additional level … working with known prior art elements using known methods."

4. Element-by-element obviousness

Claim 1 — obvious over Chen + OAI (Ground 1)

Claims 2, 5, 8 — "+ the metadata is a Media Presentation Description (MPD)"

Chen uses the term MPD natively (¶ 82, ¶ 6: "form a media presentation description (MPD) file that lists multiple presentations").

Claims 3, 6, 9 — periods and MPD-level/period-level BaseURLs

3GPP Table 2 (annotated in the petition) lists MPD (root element), baseURL … "Base URL on MPD level", Period (1…N), baseURL … "Base URL on period level", SegmentInfo, InitialisationSegmentURL, sourceURL, range. And 3GPP p. 86–87 states the resolution rule:

"There may be a baseURL attribute on MPD level or in the SegmentInfoDefault element on Period level or the SegmentInfo element. If the baseURL supplied at any level is absolute, it gives the base URL for the levels below it. Otherwise the base URL for levels below it is formed from the base URL of the higher level composed with the value of the baseURL attribute. Normal URL composition may be used, using relative URLs which are composed against a base URL."

That single passage supplies claims 3, 6, 9 (level-specific BaseURLs + period-level resolution) and independently supplies claim 7's "absolute URL or a relative URL."

Claim 4 — "+ the metadata includes a range attribute"

3GPP p. 86: an http-URL "possibly restricted by a byte range … identifying a contiguous range of bytes"; 3GPP Table 2 lists a range attribute. Motivation (LeGall ¶ 143): to "provide client devices multiple options on how to access a media segment depending on what metadata is included."

Claim 7 — "+ the URL is an absolute URL or a relative URL"

Same 3GPP composition rule. The petition's reasoning is sound and mechanical: an MPD-level base URL with no lower-level base URL is absolute; a period-level base URL composed against an upper-level base URL is relative.

Claims 10–12 — never adjudicated

The IPR challenged only claims 1–9. That is an evidentiary gap, not a finding of validity — it means the most I can say is that the same Chen + OAI (+ 3GPP / Brueck) combinations are likely to reach them, subject to verification of their verbatim scope, which I do not have. Anyone relying on claims 10–12 should read the granted claims directly.

Proposed substitute claims 13–16 (the PO's narrowing attempt) — also obvious

This is analytically important: Patent Owner's best shot at survival was to add the features the specification treats as the invention's detail — "the media is divided into a plurality of segments," "identical segments are accessible at locations indicated by URLs resolved with respect to the one or more BaseURL elements," the group element, and "BaseURL elements … included at only the representation level." The Board found these also obvious over Chen + OAI + 3GPP + Brueck:

• "identical segments accessible at locations indicated by URLs resolved with respect to the one or more BaseURL elements" ← 3GPP (segment "uniquely referenced by an http-URL element in the MPD") + Brueck (identical content replicated on multiple servers, HTTP retrieval);
• group level ← In re Aller routine optimization inserting Brueck's group level into 3GPP's hierarchy;
• "BaseURL elements … at only the representation level" ← 3GPP's own rule contemplates a base URL at "only" a single level, so choosing the representation level is an arbitrary, unsupported design variation with no asserted unexpected result.

Strategic takeaway: the claim-narrowing that Patent Owner proposed in the IPR — i.e., the hierarchy the specification emphasizes — was held obvious too. The § 103 exposure is therefore not confined to the broad independent claims.

5. The teachings-away and hindsight defenses, and why they did not carry

These are the arguments any § 103 analysis of this patent must confront, since they were fully briefed:

6. Conclusion

Claims 1–9 of US 8,645,562 B2 are obvious under pre-AIA § 103(a).

• Claims 1 and 2: obvious over Chen (US 2011/0099594 A1) in view of OAI — HTTP delivery of segmented video under a metadata file that is itself fetched from a server, with a base URL element (OAI) identifying the common host/path from which the individually-stored, individually-retrieved segments are obtained.
• Claims 3–9: obvious over Chen in view of OAI and 3GPP TS 26.234 V9.2.0 (2010-03) — 3GPP expressly discloses an MPD with baseURL at the MPD level and the Period level, the composition rules that make a lower-level base URL resolve against a higher-level one, URL resolution that may be absolute or relative, and a range/byte-range restriction on the segment URL. The motivation is unusually direct: Chen names its files as 3GPP files, so the artisan is pointed at the standard by the primary reference itself.
• Proposed substitute claims 13–16 (the group/representation-level narrowing): also obvious over Chen + OAI + 3GPP + Brueck, as routine optimization (In re Aller) and design variation without asserted unexpected results.
• Claims 10–12: not adjudicated — no IPR ground, no validity finding, no confirmed claim text available to me. Treat as open.

Adjudicated outcome (resolving the open items in my earlier sections): the FWD of 2022-02-07 held all challenged claims 1–9 unpatentable and denied the contingent motion to amend. The earlier section's uncertainty on this point is now resolved — the Board's holding went against Patent Owner on every challenged claim. The earlier litigation section's unconfirmed CAFC outcome for 22-1626 is also resolved: the appeal was voluntarily dismissed under Fed. R. App. P. 42(b), order dated 2022-04-21, mandate 2022-06-30 — i.e., no appellate ruling on the merits, so the FWD's § 103 holding stands unreviewed.

Corroboration outside the IPR: the same Chen reference (US 2011/0099594 A1) appears in Defendants' invalidity contentions and in the '562/related-family district-court charts (e.g., the D. Del. exhibit listing "2011/0099594 A1 4/2011 Chen et al."). The § 103 attack was not an isolated PTAB theory.

7. Confidence, limits, and what I did not verify

• High confidence: the reference identities and dates; the two IPR grounds and their claim mapping; the "common locations" limitation in claim 1 as reproduced in the FWD; the FWD holding and motion-to-amend denial; the CAFC voluntary dismissal.
• Medium confidence: the exact verbatim text of claims 4, 7, and 9 (I have element-level fragments — 4[f], 7[e], 7[f], 9[b], 9[c] — from petition/FWD excerpts, not the full granted claim set); and the identity of the Lewis exhibit (Ex. 1017), for which no patent/document number surfaced in the material I retrieved. Per the literal-ID rule, I have not guessed one.
• Not verified / explicitly unknown: the text and scope of claims 10, 11, 12; the Board's adopted POSITA definition (I know Dr. LeGall's credentials were contested but not the recited skill level); whether secondary considerations (commercial success, licensing, copying) were ever proffered with a nexus — none appear in the material I have, so I do not treat their absence as an admission.
• Status caveat: the page lists the patent as "Expired – Fee Related" while also listing an anticipated expiration of 2031-09-06. Those two entries are in tension — a fee-related lapse would ordinarily produce an earlier expiration. I flag the discrepancy rather than reconciling it.
• No search-result/training-data conflict was encountered on any identifier in this analysis. The one prior "flag" I raised (the PubChem co-assignee rendered as a Sogang University foundation) is unaffected by the § 103 record and is neither confirmed nor resolved here.