US 9715334

I'll run a couple of targeted searches, then synthesize with the authoritative patent text provided.

US Patent 9,715,334 B2 — Analyst Summary

Verified against the authoritative Google Patents full text and cross-checked with FreePatentsOnline (freepatentsonline.com/9715334.html) and Justia (patents.justia.com/patent/9715334). No result for a "similar" number was substituted.

1. Bibliographic data

Note on inventor city: Justia renders Cedric Fernandes' residence as "San Roman, CA"; Justia's own page for the sibling patent US 10,346,008 renders it "San Ramon, CA," and the specification gives no city for him. This appears to be a transcription typo in the Justia record rather than a substantive discrepancy. Flagging it because I am instructed not to silently correct identifiers.

2. Abstract (as issued)

"Described herein are techniques and mechanisms for personalized timeline presentation. Client devices may be presented with video content in association with a content management account. A video content item may be associated with more than one pause point, with each pause point indicating a time at which playback of the video content item was paused. Different profiles associated with the content management account may be associated with different pause points for the same video content item. Playback of the video content item may be resumed at one of the pause points when one of the profiles is selected."

3. Technical field and problem addressed

The disclosure is directed to pausing and resuming content playback (Technical Field). The stated problem: a content-management account is commonly shared by multiple users (e.g., a family). Under conventional single-bookmark behavior, only one pause point can exist per content item, so when several users share an account, "different users may wish to pause and resume playback at different points for the same content item." The invention's core concept is that more than one pause point may be created for a content item, each linked to a different profile of the account, and a UI lets a viewer pick which pause point to resume from.

The specification also covers: measuring pause time relative to content length (not wall-clock); detecting "pause events" that don't actually stop the shared playback (e.g., one viewer in a room "pausing" for themselves by selecting their profile while others keep watching); device-based pause events (e.g., an interruption or power-off); capturing a pause event from a second device (tablet/phone "connected UI" while content plays on a TV); storing pause info server-side or on the device; resuming from a different source than the original (cable → OTT VOD); and security measures (PIN or requiring input from a personal device) so a user cannot inadvertently overwrite/consume someone else's pause point.

4. Independent claims in plain language

There are three independent claims in the granted patent: claim 1 (method), claim 9 (system), and claim 16 (non-transitory computer-readable media). All three recite essentially the same four-step core.

Claim 1 — Method

A computing system performs:

1. Identify information characterizing multiple pause events for playback of a video content item tied to a content-management account. Each pause event (a) identifies a time the video was paused measured relative to the playback length of the item, and (b) is associated with a respective one of multiple profiles of that account.
2. Receive a selection of one of those profiles. The selected profile maps to a "designated" pause event, which identifies the designated pause time at which playback was paused in association with the selected profile.
3. Transmit an instruction to a client device to initiate playback of the item per that designated pause event — i.e., start playing at the designated time.
4. Transmit an instruction to present a timeline corresponding to the video item on the client device's display screen.

Key limitation: the multi-user/multi-pause-point data model PLUS the server-to-client instruction to resume at the profile-linked time PLUS the timeline presentation. Practically, step 3+4 mean the claim is written from the perspective of the server/system issuing playback and timeline instructions downstream to a client.

Claim 9 — System

A system comprising three elements doing the same operations:

• a storage medium storing the multiple-pause-event information (per-profile, time measured relative to playback length);
• a processor to receive the selection of a profile and resolve it to the designated pause event/time; and
• a communications interface to transmit the instruction to the client device to initiate playback at the designated time, and further to transmit an instruction to present the corresponding timeline on the client display.

Claim 16 — Non-transitory computer-readable media

One or more non-transitory CRM storing instructions that perform the same four-step method as claim 1 (identify per-profile pause events → receive profile selection → instruct client to play at the designated time → instruct presentation of the timeline).

Notable dependent claims

• 2 / 10 / 17: the timeline includes an indication of the designated pause event (pause-point marker on the scrub bar).
• 3 / 11: profiles are each associated with a respective device linked to the account. 6 / 14: profiles are each associated with a respective user.
• 4 / 12: also transmit an instruction to present a UI portion listing the plurality of profiles associated with the pause events for that item.
• 5 / 13: the video is streaming video transmitted via a network.
• 7 / 15: receiving the selection includes analyzing voice-based user input via a microphone.
• 8: the client device is selected from television, set-top box, laptop, desktop, tablet, mobile phone.

(For contrast: the pre-grant publication US 2014/0298175 A1 carried a different, broader 20-claim set in which the profile-association feature was a dependent claim; the granted claims recite the profile↔pause-event linkage directly in the independent claims. The sibling continuations US 10,346,008 B2 and US 10,346,009 B2 likewise recite a broader independent claim 1 in which profile association is moved to dependents. Anyone analyzing scope should use the granted 17-claim text of 9,715,334, which I have used here.)

5. Family / continuation chain (all priority 2012-08-22, all "Personalized timeline presentation")

6. Litigation posture (with explicit confidence caveats)

The Google Patents record for US 9,715,334 B2 carries a "Family has litigation" flag listing three U.S. cases in the Northern District of California (via Unified Patents litigation data):

• N.D. Cal. 5:26-cv-02811
• N.D. Cal. 3:25-cv-11048
• N.D. Cal. 3:26-cv-02811

What I could NOT confirm — stated explicitly rather than inferred:

• I found no CAFC 2026 docket or Federal Circuit appeal naming US 9,715,334. My searches did not surface any Federal Circuit activity for this patent. I do not have authoritative CAFC 2026 docket information for this patent, and I will not fabricate one.
• I could not independently verify the three N.D. Cal. case numbers, the parties, or their subject matter — I am relaying the litigation flags as they appear on the Google Patents page, which is a secondary aggregator, not a primary docket.
• Separately, current assignee Adeia has public 2026 infringement campaigns (e.g., against DISH Network, filed 2026-04-01 in D. Colo.; against DIRECTV; against FuboTV in D. Del.), and DIRECTV/DISH filed 2026 declaratory-judgment actions in N.D. Cal. I have no confirmation that US 9,715,334 is among the patents asserted in any of those specific complaints. The N.D. Cal. 2026 case numbers above are consistent in district/timing with that DJ activity, but that is an observation, not a verified link.

Recommendation if the litigation linkage matters: pull the primary N.D. Cal. complaints/PACER dockets and the Adeia 10-Q/10-K litigation disclosure directly; do not rely on the aggregated flag.

7. Bottom line

US 9,715,334 claims a server-side, profile-keyed multi-pause-point model for a shared content-management account, coupled with (a) transmitting a resume-playback instruction that starts the client at the profile-associated pause time and (b) transmitting an instruction to render the video timeline (with pause-point indications, per dependents). Its expiration is currently listed at 2034-06-19, and it is one of five family members sharing the 2012-08-22 priority date. Inventors are Kay Johansson and Cedric Fernandes; original assignee MobiTV, Inc., now held within the Adeia Media Holdings entity family.

I'll run targeted searches on the litigation databases and the specific case numbers flagged in the patent record.

The general searches returned mostly patent text and unrelated cases. Let me query the specific case numbers flagged in the record and the litigation portals directly.

The final query hit a step limit. Let me make one more focused attempt to confirm whether claim-bearing complaints actually name the '334 patent.

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

Let me confirm with a few more targeted checks before concluding on the "no PTAB activity" default.

AIA Trial Proceedings — US Patent 9,715,334 B2

Verification date: 2026-09-29. Sources: USPTO Open Data Portal "PTAB proceedings on file" block (canonical), plus live web searching for IPR/PGR/CBM filings, PTAB decisions, Docket Alarm/Unified Patents records, and Federal Circuit activity.

Proceedings overview

Total: zero (0) AIA trial proceedings on file. No IPR, PGR, or CBM petition has been filed against US 9,715,334 B2, and I found none against any of its four family members (US 8,793,582 B2 / Ser. No. 13/591,493; US 10,346,008 B2 / 15/622,275; US 10,346,009 B2 / 15/622,282; US 10,831,353 B2 / 16/419,447). There are consequently no institution decisions, no Final Written Decisions, no settlements, no § 315(e) estoppel, and no PTAB-to-CAFC appeals to report.

The bottom-line defensive posture is therefore neither of the two framing examples you gave. The patent has not been hardened by surviving IPRs, and no claims are canceled. It is un-tested at the PTAB — which, for a defendant today, means the validity fight is still entirely in front of you, but the odds of getting an IPR instituted now are materially worse than they were when this patent issued (see Strategic summary). Practically: assume claims 1–17 are all live and all presumptively valid, and price a district-court invalidity case as the realistic primary path rather than as a fallback.

What I verified and how

Confidence and residual uncertainty (stated rather than papered over): I did not have direct query access to PTAB E2E or Docket Alarm during this analysis, and search-engine coverage of the USPTO trial docket is incomplete. The USPTO ODP block is authoritative for what it covers, but a petition filed in the last few weeks may not yet be indexed in ODP or in search engines. Before relying on "zero" in a litigation posture statement, do a 60-second confirm at PTAB E2E (https://ptacts.uspto.gov/ptabweb) and the PTAB decisions page (https://www.uspto.gov/patents/ptab/decisions).

One aggregation trap to avoid

The Google Patents record for this patent displays a "Family has litigation" flag with Unified Patents / Darts-IP links pointing to N.D. Cal. cases 3:25-cv-11048, 5:26-cv-02811, and 3:26-cv-02811. That is a district-court litigation flag sourced from an aggregator — it is not evidence of any PTAB filing, and Unified Patents' litigation portal is not a PTAB registry. I could not independently verify the parties or subject matter of those three cases. Do not let the presence of a "Unified Patents" hyperlink on that page lead you to assume a Unified-filed IPR exists; none does.

Strategic summary

Claim status: all 17 claims UNTESTED. No claim of US 9,715,334 has ever been canceled, confirmed, or construed by the PTAB. Independent claim 1 (method), claim 9 (system), and claim 16 (non-transitory CRM) — each reciting the profile-keyed multi-pause-point model plus downstream instructions to (a) initiate client playback at the designated pause time and (b) present the timeline — stand unamended as granted on 2017-07-25. Dependents 2–8 and 10–15, and 17, are likewise untested. If a demand letter or complaint asserts claim 1, there is no SAS-style "this claim is already dead" argument available; your invalidity theory has to be built from scratch. On the flip side, because nothing has ever been construed or challenged, the prosecution history and any art of record were never stress-tested, and the claims have not been narrowed by amendment, so there is no prosecution-history estoppel cage built around the profile↔pause-event linkage.

Estoppel landscape: clean slate, but a closing § 315(b) window. No IPR has reached a Final Written Decision, so § 315(e)(2) estoppel has attached to no one — no petitioner, RPI, or privy is barred from raising any § 102/§ 103 ground in district court. Every prior-art ground remains available to a defendant with no estoppel overhang. The binding constraint is instead § 315(b)'s one-year clock: if you have been served with a complaint alleging infringement of 9,715,334, you have one year from service to petition, and that clock is the single most decisive date in your defense planning. Because a petition filed today would be the first challenge to this patent, there is also no § 325(d) "substantially the same art/arguments" problem and no serial-petition / General Plastic discretionary-denial exposure on the Board side.

Pattern signals: a dormant, late-asserted, aging patent — the profile that current PTAB policy disfavors challenging. Three points. (1) No repeated-petitioner pattern — there is no petitioner to pattern-match; this patent has never been challenged by anyone. (2) No patent-owner PTAB appeal history — the current owner has had no occasion to defend at the PTAB, so there is no track record of aggressive appellate behavior to calibrate against. (3) The owner lineage is MobiTV, Inc. → TiVo Corporation (2021-06-01) → TiVo LLC → Adeia Media Holdings LLC (both 2024-10-01 name changes), i.e., an operating-company asset now held within a licensing/assertion entity. Combined with a 2012-08-22 priority date and 2017-07-25 grant, this patent is now roughly 14 years from priority and 9 years from grant — squarely inside the window where the Board's 2025–2026 discretionary-denial regime has been denying institution on "settled expectations" grounds. That posture makes the IPR route harder now than at any prior point in this patent's life, and it cuts against a defendant rather than for one.

The current PTAB climate materially alters the calculus for this specific patent

You asked me to tell a defendant what actually happened. Here, the honest answer is that what has happened at the Board in 2025–2026 matters more to this patent than anything on its own docket:

• Director-controlled, bifurcated institution. Under the regime initiated in 2025, discretion is resolved first, and only petitions clearing that hurdle reach the merits — with the Director (rather than the merits panel) making the pivotal institution call. Reported effect: institution rates fell sharply, with a wave of terse or reason-free summary denials. See https://www.willkie.com/publications/2025/10/ptab-announces-new-institution-policy and https://irwinip.com (PTAB Year in Review, December 2025).
• "Settled expectations." Director-level decisions in mid-2025 began denying institution on patent age, with six-plus years in force treated as a strong denial factor; a study of petitions filed since 2012 reports that over 46% of IPR petitions challenged patents six or more years in force, and that those proceedings canceled at least one claim in over 80% of cases reaching FWD — a data point you can use to argue the doctrine is untethered from outcomes. Cited examples include Dabico Airport Solutions Inc. v. AXA Power Aps (2025-06-18, no bright-line age rule) and Embody Inc. v. Lifenet Health, where a younger related patent in the same family overcame the presumption. (All from the DeFosse/Smith/Kasai analysis hosted at https://fedcircuitblog.com — secondary source; pull the underlying Director decisions before quoting them in a brief.)
• Precedential 2026 authority against parallel-use petitions. Magnolia Medical Technologies, Inc. v. Kurin, Inc., IPR2026-00097 (PTAB May 14, 2026) (precedential) denied institution where the same patent and validity issues were being litigated in district court and the petition came late in that case. Secondary-source citation (NYIPLA PTAB Committee materials); verify against the PTAB decisions page before reliance.
• Proposed rulemaking that would codify bars. The October 2025 NPRM (Docket No. PTO-P-2025-0025, published 2025-10-15/17) proposes, among other things, a stipulation forfeiting §§ 102–103 challenges in other fora (proposed § 42.108(d)), a bar where the patent has survived a prior favorable validity determination (proposed § 42.108(e)), and a bar where a parallel proceeding will likely resolve first (proposed § 42.108(f)). If any version of these is final when you file, a patent that has been adjudicated valid in the N.D. Cal. cases flagged above may be statutorily off-limits to IPR. Monitor the Federal Register docket.

Net: for this patent, an IPR is not the cheap, reliable kill shot it would have been in, say, 2019. A defendant should model institution risk as substantial-to-high on discretionary grounds, and should preserve all invalidity theories for district court rather than banking on the Board thinning the claims.

Recommended next steps

1. Confirm the null result at the primary sources before you commit to a posture. The "zero PTAB proceedings" conclusion is well-supported by the ODP structured data and by independent searching, but it should be re-verified at:

• PTAB E2E: https://ptacts.uspto.gov/ptabweb
• PTAB decisions library: https://www.uspto.gov/patents/ptab/decisions
• The patent's own record: https://patents.google.com/patent/US9715334/en

If you find a petition filed in the last 30–60 days, treat this analysis as superseded and pull the preliminary response and any § 314(a) / Fintiv briefing immediately.

2. Calendar § 315(b) first. Determine the exact date each defendant/RPI was served with a complaint alleging infringement of 9,715,334 (check the three flagged N.D. Cal. matters, and confirm from PACER rather than from the aggregator). One year from service is a hard statutory bar with no good-cause extension (Thryv, Inc. v. Click-to-Call Techs., LP, 590 U.S. 45 (2020) — the bar determination is not appealable). If the window has closed, IPR is off the table entirely and your defense is a district-court invalidity case.

3. If you are inside the window, do a go/no-go on filing — with realistic institution odds. Because this patent is ~9 years from grant and has never been challenged, you are squarely in the fact pattern the Board has been using to deny on settled expectations. Before spending petition dollars, (a) run the prior art against the granted claim limitations (profile-keyed pause-event data model; time measured relative to playback length; downstream instruction to initiate playback at the designated time; downstream instruction to present the timeline), not against the broader 2014/0298175 pre-grant claim set; and (b) assess whether a Sotera-type stipulation would even help, given that Sotera stipulations are no longer dispositive under restored Fintiv practice.

4. Note that the family gives you five bites at the invalidity apple, but also five assertions. All five family members share the 2012-08-22 priority date, and the parent (US 8,793,582 B2) has an earlier expiration (2032-12-01) than this patent (2034-06-19) because of PTA/continuation effects. An invalidity theory that kills the parent's priority chain or the shared specification may be worth more than an IPR against 9,715,334 alone — and it is immune to PTAB discretionary denial. Coordinate the district-court invalidity case across all five patents rather than optimizing for one.

5. Preserve everything. With no FWD anywhere, no estoppel attaches, but also nothing has been teed up for you. Serve full § 282 contentions covering all 17 claims, keep product-art and system-art theories alive (these are outside IPR's § 311(b) patents-and-printed-publications limit and therefore cannot be duplicated into an IPR), and treat the IPR track — if you take it — as a supplement to, not a substitute for, the district-court case.

6. Watch for Adeia's own filings to self-limit your options. If the flagged N.D. Cal. matters produce a favorable validity determination for Adeia, proposed § 42.108(e) (if finalized) and Magnolia both point toward discretionary denial of a later IPR. That is an argument to file early, not late — if you intend to petition, a petition filed while the district case is young is materially better positioned than one filed on the courthouse steps.

I'll research the assignment record for US 9,715,334, starting with the USPTO assignment data and the corporate history of the parties involved.

Let me dig into the specific reel/frame records and the litigation/asserter context.

I hit my tool-call budget mid-research, so I'll be explicit below about what I could and could not retrieve. One important caveat up front: I was able to reconstruct the assignment chain and reel/frame numbers from the Google Patents legal-events feed (which mirrors the USPTO record), but I was NOT able to retrieve the "correspondent of record" field for those recordings from the Assignment Center. I will not fabricate attorney names. Where a field was unavailable, I say so.

Assignment & ownership analysis — US 9,715,334 B2 ("Personalized timeline presentation")

Verification note: Chain reconstructed from the recorded "reassignment" events on the Google Patents legal-events feed for US 9,715,334 B2 (which republishes USPTO Assignment Center reel/frame data), cross-checked against Xperi/Adeia SEC filings and bankruptcy-auction press coverage. I could not access the raw Assignment Center correspondent fields. Treat the reel/frame citations as accurate; treat the correspondent column as not retrieved.

Inventors

Pattern check: The inventorship is unremarkable — two career engineers on a company portfolio (Kay Johansson alone accounts for ~14 MobiTV patents). I found no evidence of inventors departing the assignee within 12 months of filing, and I found no inventor-held continuation or reversion of rights. The "inventors all leave right before a fire-sale" tell is not present. (I could not retrieve per-inventor employment start/end dates; that determination would require LinkedIn/8-K corroboration.)

Original assignee

• Entity on the issued patent: MobiTV, Inc., Emeryville, CA (incorporated in Delaware; HQ at 1900 Powell Street / formerly 6425 Christie Ave., Emeryville).
• Business: Operating company — an app-based IPTV/pay-TV software platform (live TV, VOD, network DVR, catch-up) sold to broadband and wireless operators. Named customers included T-Mobile (TVision), Cable One, and NCTC-member co-ops. It did ship products/services embodying the technology — the specification's FIGS. 2 and 5 describe MobiTV's actual fragment/segment streaming and VoD delivery architecture.
• Current status: Chapter 11 debtor → asset-acquired → defunct as an independent entity. MobiTV filed voluntary Chapter 11 on 2021-03-01 (assets $10–50M; liabilities $50–100M) in the U.S. Bankruptcy Court for the District of Delaware, with $15.5M debtor-in-possession financing. TiVo Corporation (an Xperi subsidiary) won the §363 auction on 2021-05-12 with an $18.5M bid ($17.4M cash), beating a competing Roku–RPX–Amino consortium ($18M combined). The court approved the sale (~2021-05-22), and the transaction closed by 2021-06-01. The business continued under Xperi/TiVo as the "TiVo Managed IPTV Service" (later rebranded; Evolution Digital named exclusive device partner in 2023). MobiTV as an operating company no longer exists.

Assignment timeline

The USPTO legal-events feed for this patent shows the following recorded events. Reel/frame and dates are as recorded; the "Correspondent" field was not retrievable in this session.

• 2017-02-03 (executed) / recorded 2017-02-15 — Reel 041718/0395

  • Conveyance: Security Interest (grant of security, not a title transfer)
  • Assignor: MobiTV, Inc.
  • Assignee: Ally Bank
  • Correspondent: not retrieved — recommend pulling the reel directly; I could not confirm the recording attorney.
  • Context: Securitization / secured lending — a lender lien over MobiTV's IP, an early marker of the balance-sheet stress that preceded the 2021 filing.

• 2018-08-03 (executed) / recorded 2018-08-10 — Reel 046761/0718

  • Conveyance: Security Interest
  • Assignor: MobiTV, Inc.
  • Assignee: Ally Commercial Finance LLC
  • Correspondent: not retrieved
  • Context: Securitization / secured lending — a second, successive Ally-affiliated lien, consistent with refinancing/distress financing.

• 2021-05-31 (executed) / recorded 2021-06-01 — Reel 056444/0076

  • Conveyance: Assignment of Assignor's Interest (the title transfer)
  • Assignors: MobiTV, Inc. and MobiTV Services, Inc.
  • Assignee: TiVo Corporation
  • Correspondent: not retrieved
  • Context: Bankruptcy fire-sale (§363 sale) — this is the operative transfer of title, recorded one day after the auction-close deadline fixed by the Delaware bankruptcy court. The same reel number is shared across the MobiTV portfolio (many patents transferred in one recorded bundle).

• 2023-05-19 (executed) / recorded 2023-05-19 — Reel 063707/0884

  • Conveyance: Security Interest
  • Assignors: Adeia Guides Inc.; Adeia Media Holdings LLC; Adeia Media Solutions Inc.; and others
  • Assignee: Bank of America, N.A., as Collateral Agent
  • Correspondent: not retrieved
  • Context: Securitization — a blanket collateral lien across the Adeia entity family (a credit-facility pledge), not a change of ownership. Useful only to confirm the patent sits inside the Adeia collateral pool.

• 2021-11-15 (effective) / recorded 2024-10-01 — Reel 069083/0260

  • Conveyance: Change of Name
  • Assignor: TiVo Corporation
  • Assignee: TiVo LLC
  • Correspondent: not retrieved
  • Context: Internal reorg / change of name only (no change in beneficial ownership).

• 2022-08-15 (effective) / recorded 2024-10-01 — Reel 069083/0332

  • Conveyance: Change of Name
  • Assignor: TiVo LLC
  • Assignee: Adeia Media Holdings LLC
  • Correspondent: not retrieved
  • Context: Internal reorg / change of name only — part of the Xperi separation in which the IP-licensing business was renamed Adeia Inc. (ticker ADEA, Nasdaq, from 2022-10-03) and the product business spun off as Xperi Inc. (XPER).

Gap flagged: The legal-events feed does not show the original inventor → MobiTV, Inc. assignment, which almost certainly exists on the Assignment Center (patents are routinely assigned at filing). I could not retrieve its reel/frame or date; do not treat its absence from this list as evidence that it does not exist. If you need it, query Assignment Center by patent number 9,715,334 directly.

Timeline diagram

timeline
    title Ownership of US 9715334
    2012 : Inventors file parent application
    2014 : Continuation filed by MobiTV Inc
    2017 : Patent issued July 25
         : Ally Bank security lien recorded
    2018 : Ally Commercial Finance lien recorded
    2021 : MobiTV files Chapter 11
         : TiVo wins asset auction
         : Title assigned to TiVo Corp
    2022 : Adeia spin off separates IP unit
    2023 : Bank of America lien recorded
    2024 : TiVo LLC name change recorded
         : Adeia Media Holdings name change

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The title moved from an operating company (MobiTV) to TiVo Corporation, a large operating/public company subsidiary, and then by change of name only (reel 069083/0260, eff. 2021-11-15; reel 069083/0332, eff. 2022-08-15) down to Adeia Media Holdings LLC. There is no anonymous single-member DE/TX shell and no registered-agent-service address in the record I retrieved. The current owner is non-practicing (Adeia Inc. is an IP-licensing-only company post-spin), but that is a licensing platform, not a shell — I mark the shell tell itself as absent.

2. Known asserter in the chain — not present (as to the enumerated lists). Neither MobiTV, TiVo, nor Adeia appears on the classic NPE lists called out (Acacia, Marathon, IV, IPNav, Wi-LAN/Mosaid-Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Spangenberg). Caveat: Adeia is a high-volume patent litigant (Adeia Guides Inc. campaigns against MVPD/OTT targets). I did not confirm in this session that US 9,715,334 is among the patents asserted in any specific 2026 complaint, and I will not assert it is.

3. Repeat correspondent across the chain — unclear / no data. The Assignment Center correspondent-of-record fields were not retrievable with my tooling. Do not treat "no repeat correspondent found" as a negative finding — it is simply unverified. This is the single most important field to pull manually, because the six recordings span three different recording eras (2017, 2018, 2021, 2023, 2024) and the correspondent identity is the cleanest tell.

4. Cascading transfers — not present. Only one genuine transfer of title occurs (reel 056444/0076, 2021). Everything after that is a name change (069083/0260, 069083/0332) or a lien (063707/0884). There is no chain of successive LLC-to-LLC hops within 24 months.

5. Pre-litigation transfer — not present. The title transfer executed 2021-05-31; the litigation flags on the patent are N.D. Cal. cases from 2025–2026 (3:25-cv-11048; 5:26-cv-02811; 3:26-cv-02811). That is ~4–5 years, far outside the 6-month window that indicates a venue/standing-arranging transfer.

6. Bankruptcy fire-sale — PRESENT (strong). MobiTV filed Chapter 11 on 2021-03-01; the patent portfolio was sold at §363 auction; TiVo Corporation was the winning bidder at $18.5M and the assignment recorded 2021-06-01 at reel 056444/0076 (assignors MobiTV, Inc. + MobiTV Services, Inc.). This is a textbook distressed-asset transfer, and it is the origin of the current ownership. The two prior Ally liens (reels 041718/0395 and 046761/0718) are corroborating distress markers.

7. Privateering — not present. MobiTV was a debtor, not an operating company weaponizing an NPE against competitors. There is no evidence the transfer was structured to assert on the seller's behalf; the buyer (TiVo/Xperi) was an industry participant running its own IP-licensing program.

8. Defensive aggregator — not present (the inverse occurred). Note the near-miss: RPX was a bidder — but only as a minority partner in the losing Roku–RPX–Amino consortium, and its $5M was earmarked for the patent assets. The defensive aggregator LOST. The patent therefore went to an asserting licensing owner, not a neutralizing one.

Verdict

NPE — moderate confidence. The classification is driven by a single strong, well-documented signal — the bankruptcy fire-sale at reel 056444/0076 (executed 2021-05-31) that moved the patent out of operating company MobiTV into the TiVo/Xperi IP machine — combined with the fact that the current owner of record, Adeia Media Holdings LLC (per name-change reels 069083/0260 and 069083/0332), sits inside Adeia Inc., an IP-licensing-only entity that does not make products embodying the claims and that actively litigates its media portfolio.

I deliberately stop short of "high confidence": the classic anonymous-shell tells (single-purpose LLC, registered-agent address, cascading LLC hops, a recurring troll lawyer) are absent, and the repeat-correspondent field — the field that would most likely turn this into a high-confidence call — was not retrievable in this session. This looks like monetization of a distressed operating company's portfolio by a legitimate, publicly-traded licensing platform, which is functionally an NPE posture but structurally not a "shell/troll" pattern.

Verification links:

• USPTO Assignment Center (search by patent number 9,715,334): https://assignmentcenter.uspto.gov/
• Legacy Assignment Search (same records): https://assignment.uspto.gov/patent/index.html
• Google Patents legal events for the cited reel/frame entries: https://patents.google.com/patent/US9715334/en

Recommended next pull (to close the gaps I flagged): (a) the Assignment Center correspondent-of-record for each of reels 041718/0395, 046761/0718, 056444/0076, 063707/0884, and 069083/0260–0332; and (b) the original inventor → MobiTV, Inc. assignment record, which is not in the legal-events feed I used. Both require direct Assignment Center access, which my search tooling could not reach.

I'll verify the patent and its cited references against live sources before building the prior-art analysis.

I confirmed the target record before analyzing. Here is the prior-art analysis for US 9,715,334 B2 ("Personalized timeline presentation," App. No. 14/306,221, filed 2014‑06‑16, priority 2012‑08‑22, granted 2017‑07‑25).

Prior-Art Analysis — US 9,715,334 B2

0. Scope, sources, and the legal framework I applied

Target verified: Google Patents /patent/US9715334/en returned US 9,715,334 B2 (App. 14/306,221), inventors Johansson & Fernandes, original assignee MobiTV, Inc. No similar number was substituted.

Reference set analyzed: the 16 references on the face of the patent ("Patent Citations (16)"), plus the 13 non‑patent citations. I did not treat the "Cited By" / "Family Cites Families" lists as citations of this patent — those are later documents that cite it, and most post‑date the 2012‑08‑22 priority.

§ 102 framework (this matters — it changes the answer): The application claims benefit of Ser. No. 13/591,493, filed 2012‑08‑22, and the granted claims are supported by that parent. Because the effective filing date is before 2013‑03‑16, pre‑AIA § 102 applies. That produces these reference dates:

(If the AIA applied instead, the effective date would still be 2012‑08‑22 and essentially the same documents survive as § 102(a)(2) art — the conclusions below do not turn on the distinction.)

Bottom line up front: No reference cited on the face of the '334 patent anticipates independent claim 1, 9, or 16. None discloses the asserted core — a plurality of pause events for one video item, each tied to a respective profile of a shared content-management account, with the server transmitting an instruction to resume the client at the profile-linked pause time. The single most limiting limitation ("each of the pause events being associated with a respective one of a plurality of profiles") is absent from every cited reference. The citations are § 103/background art, and several of them post-date the priority date and are not prior art at all. Details below.

1. Verdict table (relevance and prior-art status)

2. Reference-by-reference analysis

TIER 1 — Most relevant cited art (still only § 103-grade)

11. US 8,873,930 B2 — "Non-linear contextual video playback control"

• Assignee/inventors: Kilo, Inc.; Deglise & Lee (Kilo assignee page). Pre-grant pub. US 2014/0029914 A1.
• Dates: priority/filing 2012‑07‑24; granted/published 2014‑10‑28.
• Description (verified against FPO/Google): a controller receives user commands associating "path points" with frames of a video, generates metadata describing the path that associates states of the path with frames, so that future playback is controlled by user input along the path (touch/3‑D gestures); the video can be streamed server→device with non-adjacent frames sent first.
• Prior-art status: filed 2012‑07‑24, i.e., before the 2012‑08‑22 priority → available as a § 102(e) reference.
• Potentially anticipates: None. It is a playback-control reference (gestural, non-linear navigation), not a pause-bookmark-per-user reference. It has no notion of a "pause event," no pause time, and no account/profile linkage.
• Best use: § 103 combination on the "transmitting an instruction to present a timeline" limitation and marker placement (claims 1, 2, 4, 9, 16, 17), if paired with a bookmarking reference. Weak because the claim requires the timeline instruction in combination with the profile-keyed pause model.
• Flag: A secondary source (richardspatentlaw.com) lists US 8,873,930 as filed 2013‑03‑15 and issued 2018‑03‑21, which contradicts the Google citation (2012‑07‑24 / 2014‑10‑28). The discrepancy is likely a related/continuation family member. Pull the front page of US 8,873,930 itself before relying on the filing date, because if its operative filing date were 2013‑03‑15 it would fall out of § 102(e) entirely.

9. US 2013/0051754 A1 — "Video tagging system"

• Inventor: Ash K. Gilpin. Corresponding patent US 8,467,660 B2 (granted 2013‑06‑18).
• Dates: priority/filing 2011‑08‑23; published 2013‑02‑28.
• Description (verified): web-based video tagging; tags are timestamped and synchronized to the video timeline; markers/anchors are placed on the timeline; clicking a tag's "timestamp link" fast-forwards or rewinds the video to where that tag appears. Tags are maintained separately from the video data.
• Prior-art status: filed 2011‑08‑23 (and published after the priority date), so it is § 102(e) art, not § 102(a)/(b).
• Potentially anticipates: None of 1/9/16. The timeline-marker + "jump to a time" disclosure is real, but the timestamp is a tag location, not a pause point, and there is no per-profile association and no content-management-account model.
• Best use: § 103 on "the timeline includes an indication of the designated pause event" (claims 2, 10, 17) and on the general "present a timeline with markers" concept (claim 1 step 4). One of the two strongest of the cited references, but still short of the profile-keyed core.

8. US 2012/0239661 A1 — "Method and System for Meta-Tagging Media Content and Distribution"

• Inventor: Patrick Giblin. Corresponding patent US 8,543,622 B2 (granted 2013‑09‑24).
• Dates: priority 2007‑12‑07 (provisional 61/012,368); published 2012‑09‑20.
• Description (verified): user-generated meta-tags applied to a portion of a media stream while it is playing; the player "continually captures all tags up to the final 10 seconds (or some other designated time period) of media content played"; the user can pause the player to add tags; tags are matched to the clip and its location and transmitted to a remote server/community system.
• Prior-art status: published 2012‑09‑20, i.e., after the 2012‑08‑22 priority date, so it is not § 102(a)/(b). It is a § 102(e) reference (U.S. published application filed 2012‑02‑24 as 13/405,168, with 2007 provisional priority — both before 2012‑08‑22). Note the citation table's "2007‑12‑07" is the provisional date; the non-provisional was filed 2012‑02‑24. Either way, filed before the priority date → § 102(e).
• Potentially anticipates: None of 1/9/16. It discloses time-anchored data (tags) and a momentary pause, but not a pause event that is stored and later used to resume playback, not a plurality of per-item bookmarks, and not per-profile association.
• Best use: § 103 on the "pause … capture time … store … resume" concept and on voice/automatic metadata capture. Relevant to claim 1's "pause event … identifying a time," but the missing profile linkage is dispositive.

Additional Tier‑1 candidate the examiner did not cite (worth pursuing): the family itself is addressed by the later Rovi/Adeia filings, e.g., US 11,717,240 B2 and US 11,917,251 B2 (Rovi Guides, "Systems and methods for predictive selection of pause points," priority 2021‑10‑18) appear in the "Families Citing" list — these are later and cannot be prior art, but they confirm the "pause point" concept remained an active claim space. Also in the citing list is US 2016/0011743 A1 (Rovi, "media guidance in relation to previously-viewed media assets," priority 2014‑07‑11) — also later, not prior art here. I mention them only so these are not mistaken for anticipatory art.

TIER 2 — Background (§ 102(e) or § 102(b)), no anticipation

7. US 2012/0173980 A1 — "System and Method for Web Based Collaboration Using Digital Media"

• Inventor Dachs; priority/filing 2006‑06‑22; published 2012‑07‑05.
• Online collaboration/annotation over shared digital media. § 102(e) (filed 2006, by another). Relevant only as generic background on server-based time-anchored user annotations. Anticipates nothing in 1/9/16.

5. US 8,117,252 B2 — "Video-monitor/recording/playback system"

• Inventor Schaff; priority 2002‑12‑26; granted 2012‑02‑14.
• Surveillance/recording/playback system. Granted after 2011‑08‑22 so not § 102(b); § 102(e) (filed 2002). Background on the "recording/playback with resume" concept; no profile-based pause points. No anticipation.

10. US 2013/0205212 A1 — "Method and system for a universal remote control"

• Inventor Nishith Kumar Sinha; priority/filing 2012‑02‑07; published 2013‑08‑08.
• Universal remote / device-control. § 102(e) (filed 2012‑02‑07, before priority). Only conceivable use is § 103 against the user-input limitations — e.g., claim 7 / 15 ("analyzing voice-based user input provided via a microphone") and claim 8 (client device types). Does not touch the pause/profile core.

3. US 2003/0007663 A1 — "Caching graphical interface for displaying video and ancillary data from a saved video"

• Inventor Wixson; priority 2001‑06‑11; published 2003‑01‑09. § 102(b). Video GUI/caching background. No anticipation.

TIER 3 — Weak / editing-oriented (§ 102(b)); not anticipatory

• 1. US 6,628,303 B1 — "Graphical user interface for a motion video planning and editing system…," Avid Technology; priority 1996‑07‑29; granted 2003‑09‑30. § 102(b). An NLE (non-linear editing) GUI — timelines/tracks. Background only; editing ≠ playback pause/resume by user profile.
• 2. US 7,356,242 B2 — "Editing device, editing system and editing method," Sony; priority 1996‑12‑09; granted 2008‑04‑08. § 102(b). Editing background.
• 6. US 7,518,650 B2 — "Image reproducing method and image reproducing apparatus," Fujifilm; priority 2004‑03‑17; granted 2009‑04‑14. § 102(b). Digital-image reproduction; essentially irrelevant to video pause points.
• 4. US 2011/0116766 A1 — "Video advertising," Starz Entertainment; priority 2002‑06‑25; published 2011‑05‑19 (before 2011‑08‑22 → § 102(b)). Advertising/insertion; no pause-point or profile teaching.

NOT PRIOR ART — must not be used as § 102 art

• 12. US 2014/0059432 A1 (MobiTV, "Personalized timeline presentation," published 2014‑02‑27) and 13. US 2014/0298175 A1 (MobiTV, published 2014‑10‑02) are the applicant's own disclosures — 12 is the parent (Ser. No. 13/591,493) and 13 is the pre-grant publication of the '334 application itself. Because they are not "by another" under § 102(e) and share the same inventive entity/common ownership, neither is available as prior art. Treating 13 as art against '334 is a pure self‑collision; do not do it.
• 14. US 2014/0285717 A1 (Google, "Interpolated video tagging"): filed 2013‑03‑20 — after the 2012‑08‑22 priority. Not § 102(a), (b), or (e). Not prior art.
• 15. US 2017/0104707 A1 (Bonifay, "Multimedia Communication Platform"): filed 2015‑10‑08. Not prior art.
• 16. US 9,454,993 B1 (Sports Logic Group): filed 2015‑10‑09. Not prior art.

Caution: References 14–16 appear in the "Citations" table because they were cited in later family member prosecutions or are listed by the aggregator; they are not citable against the '334 priority date. Any invalidity contention that relies on them is facially defective.

3. Non-patent literature (13 items)

These were cited during prosecution (mostly by the examiner). Almost all are streaming/transport standards, not user-interface art, and none addresses multi-profile pause points:

• Akram, A., "RTP Media Stream Pause and Resume," IETF draft, July 16, 2012 — closest in name to the invention, but it is a transport-protocol mechanism for pausing/resuming a media stream (a network primitive), not a per-user/per-profile bookmark for a shared content-management account. Best used only as background showing pause/resume of streams was known.
• Pantos, R., "HTTP Live Streaming," draft-pantos-http-live-streaming-08, March 1, 2012; Schulzrinne, "RTSP," Feb. 1, 1998; "[MS-RTSP]," July 5, 2012; Schulzrinne, "RTP," (listed as 1905 — an apparent typo for 1996) — protocol/transport background.
• ATSC A/53 Part 4 (Aug. 7, 2009); "MPEG‑4 — The Media Standard" (Nov. 19, 2002); Siglin, "MP4 File Fragmentation…" (Nov. 16, 2011); Sullivan, "H.264/AVC…" (Aug. 1, 2004) — codec/container/streaming background; they support the specification's fragmentation discussion (FIGS. 2 and 5) but are irrelevant to the claims' novelty.
• The two entries for "U.S. Appl. No. 13/591,493, Non-Final Office Action (Jan. 31, 2014)" and "Notice of Allowance (Apr. 16, 2014)" are the applicant's own prosecution history, not prior art. They are, however, the most useful prosecution-history documents here — the parent's allowance rationale is the best clue to how the examiner viewed the pause-point/profile feature, and a defendant should read them closely.

4. Synthesis — what this means for an invalidity theory

1. The independent claims are not anticipated by anything on the face of the patent. Claim 1 (and its system/m CRM twins, claims 9 and 16) require, as an express limitation, that each pause event be "associated with a respective one of a plurality of profiles associated with the content management account." Not one cited reference — Avid, Sony, Wixson, Starz, Schaff, Fujifilm, Dachs, Giblin, Gilpin, Sinha, or Kilo — discloses a per-profile pause bookmark on a shared account. The claim is a genuine combination of (a) a multi-bookmark data model, (b) profile keying, and (c) server-issued resume + timeline instructions.

2. The strongest cited references attack the dependent limitations, not the independent ones. For a § 103 theory, the useful mapping is:

3. The broader sibling claims are the soft spot, not '334's independent claims. As flagged in the earlier summary, the sibling continuations US 10,346,008 B2 and US 10,346,009 B2 recite an independent claim 1 without the profile limitation (it is moved to dependent claims 2–5). Gilpin/Giblin/Kilo are materially more dangerous against those claims than against the '334 claims. If a defendant wants the best prior-art target, attack the broader sibling independent claims, not '334 claim 1.

4. What is genuinely missing from the cited art — and therefore what a defense must find independently. A reference that anticipates '334 claim 1 must show, in one document (or an obvious combination): (i) multiple stored pause points for one video; (ii) each keyed to a profile under a shared account; (iii) pause time measured relative to playback length; (iv) a server instruction to the client to start at that time; and (v) a server instruction to render the timeline. The cited art supplies at most (v). This is a strong non-anticipation posture for the patentee — and, honestly, a reason to expect that no single cited reference will carry an invalidity case.

5. Explicit caveats (stated rather than glossed)

1. Filing vs. priority column. Google's citation table labels its first date column "priority date." For old patents (e.g., US 6,628,303, US 7,356,242) that date is the filing date; for applications with provisional priority (e.g., Giblin) it is the provisional date, with the non-provisional filed later. Where the § 102(e) analysis is close, I noted the operative filing date, but verify each reference's actual U.S. filing date on its own front page before using it.
2. The US 8,873,930 date conflict flagged in §2.11 is unresolved and matters: if its operative filing date is 2013‑03‑15 rather than 2012‑07‑24, it drops out of § 102(e) entirely.
3. This analysis is limited to references cited on the face of the patent. It is not a prior-art search. The most likely fatal art (a true multi-user streaming bookmark system, e.g., a working DVR/OTT "profiles with resume points" product from before 2012, or product/system art outside § 311(b)) would not appear in this citation list at all — and such product art is precisely what is outside the scope of an IPR and must be pursued in district court.
4. Self-citation trap. References 12 and 13 are the applicant's own family documents. They must never be treated as § 102 art against '334.
5. I did not fabricate any reference, claim mapping, or date. Where a secondary source conflicted with the patent record (Kilo), I said so rather than picking one silently.

I'll verify the substance of the key prior-art references from the page's Prior Art section before mapping them to the claims.

Two more targeted checks on the streaming-protocol reference and the multi-user collaboration reference.

Obviousness Analysis — US 9,715,334 B2 under 35 U.S.C. § 103

Builds on the summary/PTAB sections above; does not repeat bibliographic or PTAB material. Patent text and claim language are taken from the authoritative Google Patents full text supplied in this engagement.

Two date/identity flags before I start.

1. Date inconsistency: this task states the current date as 2026-04-26; the system preamble says 2026-09-29, and the prior sections were verified as of 2026-09-29. I am treating the analysis date as on/after any of these, and nothing below turns on the difference. Flagging it because I was instructed not to silently reconcile inconsistencies.
2. The "Prior Art" section of the page contains several entries that are not prior art to this patent. This is addressed head-on in §2, because a §103 opinion that ignores it is worthless.

1. Legal standard and the hypothetical person of ordinary skill

Standard. A claimed invention is obvious "if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art." 35 U.S.C. § 103; KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). Obviousness is a question of law resting on factual predicates: scope and content of the prior art, differences between the prior art and the claims, and the level of ordinary skill. Graham v. John Deere Co., 383 U.S. 1 (1966).

Because the '334 issued from Application No. 14/306,221, filed 2014-06-16 as a continuation of Application No. 13/591,493, filed 2012-08-22 (see Cross-Reference in the specification, and the Family Applications table on the page), the claims are presumptively entitled to the 2012-08-22 effective filing date, and the prosecution was conducted under the pre-AIA § 102/§ 103 regime. This matters for one reference in particular (see §2).

The KSR / MPEP § 2143 rationales I rely on below. (A) combining prior-art elements according to known methods to yield predictable results; (C) use of a known technique to improve similar devices in the same way; (D) applying a known technique to a known device ready for improvement; and (F) design incentives / market forces. KSR, 550 U.S. at 416–17, 421; MPEP § 2143.

POSITA. For this record I would define the hypothetical artisan as a person with a bachelor's degree in computer science, computer engineering, or electrical engineering (or equivalent), plus 2–4 years of experience designing or building client-server streaming media systems and interactive media playback interfaces — or a correspondingly smaller team including a UI/interaction designer. Practically, this is the profile of someone who had worked on a DVR, OTT video client, or multi-screen video app.

Claim-construction anchors relevant to the §103 mapping.

• "pause event" / "time … measured relative to the playback length": a time-indexed position within the item (e.g., 1:15 into the program), not a wall-clock timestamp. The specification says so expressly (¶ describing operation 308: "a time of 1:15 may indicate that the first one hour, 15 minutes of the content item has already been presented").
• "a plurality of profiles associated with the content management account": user- or device-identity records subordinated to a single account; the specification frames the account as one "shared by several users such as members of the same family."
• Antecedent-basis note (a defense-side observation, not an obviousness point): claim 1 step 2 recites "receiving a selection of one of the profiles," then refers to "the selected user profile," whereas the specification's FIGS. 6–7 describe the user selecting a pause point. The intervening words "the selected user profile being associated with a designated one of the pause events" partially bridge this. A defendant could separately pursue a § 112(b) antecedent-basis / written-description theory. For § 103 purposes, the limitation is met by any art in which the identity (profile/user/device) selected drives which stored resume position is used.

2. Threshold: which entries in the page's "Prior Art" section are actually prior art

This is the single most important screening step. The page's citation furniture (sourced largely from the later continuations' prosecutions, 2017–2019) mixes genuine prior art with the family's own publications and with references that post-date the 2012-08-22 priority date.

2A. Usable prior art (effective date before 2012-08-22)

2B. Entries on the page that are NOT prior art to the '334 claims — do not use them in a §103 ground

One more literal-reading flag: the NPL citation list renders the RTP RFC as "Schulzrinne, H., 'RTP: A Transport Protocol for Real-Time Applications,' The Internet Society, Jun. 25, 1905." The year is plainly an OCR/transcription artifact (RFC 1889 dates to 1996). I am not treating it as a 1905 publication; but per instructions I am reporting it as it appears rather than silently correcting it.

Net: the usable §103 universe is narrower than the page suggests but stronger than it looks, because the two best references — Fuji Xerox '407 and Gilpin '754 — sit squarely on the two hardest limitations (multiple time-indexed bookmarks per item; per-user, server-stored, timeline-anchored timestamped positions).

3. Claim 1, element by element

The claim is written server-side (a system that transmits the resume instruction and the timeline-render instruction). That framing matters: a §103 ground does not need a reference that says "transmit an instruction" in those words; it needs the architecture — a server that supplies playback position and player UI to a client — which is the ordinary client-server streaming model taught by the NPL and confirmed by Gilpin's server/HTML/JS implementation.

4. Ground 1 (primary) — Fuji Xerox '407 + Gilpin '754 + Akram + Avid '303

4.1 Element-by-element mapping

4.2 Why the artisan would have combined these four

1. Same field, same problem, same solution shape. '407 and Gilpin are both about capturing time-indexed user artifacts into network-delivered media and letting a user navigate back to them. Combining is not cross-field borrowing; it is the ordinary aggregation of references "in the same field of endeavor." In re Keller; MPEP § 2143.01.
2. '407 supplies the multi-bookmark data model and the per-user session; Gilpin supplies the server-side per-user store, the timestamp→seek mechanism, and the timeline-with-markers presentation. Each reference performs in the combination precisely the function it performs alone — the hallmark of a proper combination (rationale (A), predictable results).
3. Adding the transport layer (Akram/RTSP/HLS) is a known technique applied to a known system ready for improvement (rationale (D)). '407 already contemplates network delivery; specifying that resume be effected by server-side pause/resume signalling is a routine implementation choice with no change in the principle of operation (In re Mouttet).
4. Design incentive / market force (rationale (F)): by 2012, cross-device "resume where you left off" was a recognized commercial requirement for multi-screen video services, and multi-user households sharing one account were the standard subscriber model. The '334's own specification concedes that the account is "shared by several users such as members of the same family" and frames the entire problem as the friction this creates — an administrative/usage condition, not a technical discovery. Indeed, the specification's own figures present the pause-point markers on a playback bar and a list of pause points as conventional UI constructs.
5. No teaching away, and no unexpected result. Aggregating several users' bookmarks into one account and surfacing them on one timeline yields exactly the predictable aggregate benefit (each user picks their own resume point). There is nothing in '407 or Gilpin that discourages multiple co-existing bookmarks/tags on the same item — '407 expressly encourages a collection of bookmarks.

5. Ground 2 (alternative) — Fuji Xerox '407 + Giblin '661 + Wixson '663 + Akram/HLS

• Giblin '661 expressly contemplates many viewers annotating the same media item at different points ("if 1,000 individuals watch a video … they will have different 'points of view'"), with those viewer-supplied, time-anchored artifacts stored against the content. That is limitation 1.3 with almost literal correspondence, and it supplies the motivation for Ground 1 by making the multi-viewer/multi-position premise explicit.
• Wixson '663 supplies the "saved video + associated ancillary data presented through a GUI" element, i.e., the timeline/interface half of limitation 1.6.
• Akram / HLS again supply server-controlled pause/resume and segment-level resume (1.5).
• Rationale: (A) and (C). Giblin was concerned with annotation, '334 with resume position; substituting a pause/resume position for an annotation position is "use of a known technique to improve a similar device in the same way." KSR, 550 U.S. at 417. Both are "a time-stamped, user-attributable marker on a media timeline."

Candid weakness of Ground 2: Giblin's markers are annotations for search/social discovery, not playback-resume bookmarks. A patent owner will argue a difference in purpose. That is why I rank Ground 1 above it: '407's bookmarks are expressly navigational ("provides an index into the multimedia document"; selecting a snapshot plays the associated portion), i.e., functionally the same use as the claimed pause event.

6. Ground 3 (secondary / backup) — Kilo '930 + Dachs '980 + Akram + Avid

• US 8,873,930 B2 (Kilo) discloses storing metadata that associates points with specific frames of a video, server-side, and controlling subsequent playback by user interaction with those stored points; it also discloses the server→client streaming stack. US 2012/0173980 A1 (Dachs) supplies multi-user collaboration over digital media. Akram supplies pause/resume; Avid '303 supplies the timeline.
• Two candid caveats. (i) Kilo's claimed subject matter is a non-linear path, not a pause position; it is a weaker fit for 1.1/1.2 than '407. (ii) Kilo's prior-art date is contestable. The page lists priority 2012-07-24 but the application was filed 2013-03-15. Under pre-AIA § 102(e), the reference date is the earliest U.S. filing to which it is entitled, including a provisional only if the provisional supports the relied-upon disclosure (MPEP § 2136.03). If the 2012-07-24 date is a provisional that supports the relied-upon point-association disclosure, Kilo is §102(e) art; if not, its 2013-03-15 filing date makes it post-priority and unusable. This must be verified from the Kilo file wrapper before the reference is put in any chart.

I would plead Grounds 1 and 2 first and hold Ground 3 in reserve.

7. Consolidated motivation-to-combine showing (what a petitioner/defendant must actually say)

The elements of the §103 case against claim 1 are, in order of difficulty:

1. Multiple, per-profile pause points on one content item (1.1–1.3). Met by '407 alone (collection of time-indexed, user-name-keyed bookmarks) and reinforced by Gilpin/Giblin/Dachs. Weakest sub-point: the word "profiles … associated with the content management account." Counter: '407's "user name" session and Gilpin's "log in" requirement are the same concept as the '334's profile/account; the '334's claim does not require any particular profile-management data structure.
2. Selection of the profile resolving to the stored position (1.4). Met by '407's snapshot selection and Gilpin's timestamp-link click.
3. Server transmission of the resume instruction (1.5). Met by '407's network delivery of the bookmark plus Akram/RTSP/HLS server-side resume. This limitation is where a §103 ground should be reinforced with system art (Schaff '252; Sinha '212 for the second-device case).
4. Server transmission of the timeline-presentation instruction (1.6). Met by Gilpin (server-built player with time bar and markers) and Avid (timeline GUI). Note the corroboration point: the page's own record shows that by early September 2012 Amazon had a "content delivery service … configured to support a resume functionality such that playback of video content may be stopped at a point … on one device and later resumed at that point on the same device or a different device," delivered alongside a timeline interface. US 9,113,128 B1 is nine days too late to be §103 art, but it is persuasive evidence that the claimed concept was within the ordinary skill level in the weeks surrounding the filing — usable rhetorically, in a § 282 notice of prior-art-as-evidence-of-skill posture, or in a KSR "state of the art" narrative, never in a formal § 103 ground.

Articulated motivation (rationale (F)): a POSITA in 2012, addressing an OTT/multi-screen video service whose subscribers share one account across a household and several devices, would have been motivated to (a) stop overwriting a single "last position" per title, (b) keep one resume position per household member — an objective the prior art had already met in the bookmarking (Fuji Xerox '407) and tagging (Gilpin '754, Giblin '661) contexts — and (c) surface those positions to the user where users already look for position information: the timeline/scrubber (Avid '303, and the server-built time bar of Gilpin). The combination improves the known device ('407's bookmarking system) in the same way the known technique had already improved analogous systems, with a predictable result. KSR.

8. Dependent claims

Claims 9 and 16 are the system and CRM counterparts of claim 1 and rise or fall with it: the storage medium maps to '407's bookmark file/Gilpin's tag database; the processor to '407's servlet; the communications interface to '407's network delivery to the client browser plus Akram/RTSP/HLS transport control.

9. Anticipated counterarguments, and the honest weaknesses

1. "The examiner already had these references." The page's record shows the parent (13/591,493) was allowed after a Non-Final Office Action (2014-01-31) and a Notice of Allowance (2014-04-16). That means the references of record were before the examiner. It does not mean the combinations were considered — the '407 and Gilpin references appear in the record of the later continuations, not necessarily in the '221 file, and the record contains no substantive rejection to review. The § 103 case must be built affirmatively. Verify the actual '221 file wrapper and the examiner's reasons for allowance before filing anything; the page does not surface them.
2. "Different purposes" attack. The strongest owner argument is that '407/Gilpin are annotation/bookmarking systems while '334 is about playback resumption. This is answerable (see §5), but it is the argument to prepare for, and it is why the '407 "index into the multimedia document / play the associated portion" language is the critical quotation.
3. "Profiles vs. user names." An owner could distinguish "profiles associated with a content management account" from '407's session-by-user-name. Weak on the merits (the claim imposes no data-structure requirement), but it is a claim-construction fight.
4. § 112 grenade. The claim-1 "profiles"/"selected user profile" antecedent issue (§1 above) is a separate validity theory, not an obviousness one.
5. Secondary considerations. I have found no evidence of nexus-bearing objective indicia for the granted claim set specifically: no unexpected results, no industry praise tied to the profile-keyed-pause-point feature, and no licensing or commercial-success evidence with a demonstrated nexus to the claimed combination. The fact that the family is now held by a licensing entity and appears in litigation flags (per the earlier sections) is not a secondary consideration. If the owner asserts commercial success, the burden shifts to them to show nexus; nothing on this page establishes it.
6. Reference-date landmines (§2B and Kilo in §6) will kill the ground if they are not screened first.

10. What to verify before relying on this analysis

Bottom line. Using only the references the page actually supplies and that qualify as prior art, claim 1 is vulnerable to a §103 combination whose backbone is Fuji Xerox US 7,730,407 B2 (multiple, time-indexed, user-keyed bookmarks selectable to replay an indexed portion) in view of Gilpin US 2013/0051754 A1 / US 8,466,660 B2 (per-user, server-stored, timestamped positions rendered as markers on a server-built timeline, with a click-to-seek mechanism), further in view of Akram's "RTP Media Stream Pause and Resume" (2012-07-16) and/or HLS/RTSP (server-controlled pause/resume of a streamed session), and Avid US 6,628,303 B1 (timeline GUI). Claims 2–6 and 8–14 track that combination with strong mappings. The two soft spots are claim 7/15 (voice input), which needs art outside this page, and the "profiles/account" vs. "user name" framing, which is a construction argument rather than a genuine technical difference.