US 10425806

I'll verify the patent's identity and check litigation/docket sources before summarizing.

Let me check the CAFC/appeal and PTAB status specific to this patent.

US Patent 10,425,806 B2 — Verification and Summary

Source of record: the full patent text provided (Google Patents, fetched 2026-10-01), corroborated by Unified Patents' patent page, the Justia assignee listing, and PTAB/CAFC filings for family members. All identifiers below are reproduced literally; no numbers have been normalized.

1. Bibliographic data

Priority chain (per the '806 cross-reference section): continuation of 14/576,202 (now US 9,749,847) ← 14/503,401 ← 14/273,546 (now US 8,862,757) ← 14/172,913 (now US 8,798,539) ← 13/740,214 (now US 8,700,790) ← 12/333,303 (now US 8,392,591) ← provisional 61/017,202.

Child continuations of the '806: 16/532,507 (now US 11,234,121), 17/542,373 (now US 16,593,81/11,659,381), 18/193,686 (now US 12,058,779/12,058,779 — as listed, "US12058779B2").

⚠️ Date discrepancy noted, not corrected: the '806 specification's cross-reference paragraph states provisional 61/017,202 was "filed on Dec. 8, 2007," whereas the Google Patents family/priority field shows 2007-12-28 and Unified Patents shows 2007-12-27. The '806 background paragraph also describes some entries inconsistently (e.g., "whereas" for Jan–Feb 2008 provisional/utility filings). I am reporting these literally rather than harmonizing them.

2. Abstract (verbatim, as provided)

"Disclosed herein is a method and system for utilizing a digital data capture device in conjunction with a Bluetooth (BT) enabled mobile device for publishing data and multimedia content on one or more websites automatically or with minimal user intervention. A client application is provided on the BT enabled mobile device. In the absence of inbuilt BT capability, a BT communication device is provided on the digital data capture device. The BT communication device is paired with the BT enabled mobile device to establish a connection. The client application detects capture of data and multimedia content on the digital data capture device and initiates transfer of the captured data, multimedia content, and associated files. The digital data capture device transfers the captured data, multimedia content, and the associated files to the client application. The client application automatically publishes the transferred data and multimedia content on one or more websites."

3. Plain-language overview of the independent claims

Claim 1 — Method (camera side): A camera with short-range wireless capability does the following:

1. Pairs with a cellular phone that has internet access over a cellular data network — and the camera cryptographically authenticates the phone's identity, using an association protocol.
2. Captures new media (video and/or still images) after pairing.
3. Creates a new-media file and stores it in camera memory; the paired connection stays paired through this.
4. Receives a transfer request from a mobile app on the authenticated phone, over the paired connection, for that already-created file.
5. Transfers the file to the authenticated phone over the paired connection.
   The claim then recites what the phone-side app must be capable of: receiving and storing the file (connection remains paired), using HTTP to upload the file plus user information (stored in the app; used by the publishing website to publish the file) to a user media publishing website over the cellular data network, and providing a touch-based GUI for the received file that accepts input to delete the file and to select which publishing website to upload to.

Claim 4 — Apparatus (the camera itself): The same functional sequence expressed as a device claim — memory, processor, short-range wireless communication device, and data capture circuitry — covering pairing/authentication, post-pairing capture, file creation/storage, receiving the app-initiated transfer request, and transferring the file. The GUI limitation here recites receipt of input to select the publishing website (the delete input appears in claims 1 and 11, not claim 4).

Claim 7 — System (camera + phone app): A two-sided claim. The camera-side elements mirror claim 1's steps; the claim additionally recites the software application for the phone as executable instructions that (a) send the transfer request, (b) receive and store the file (connection remains paired), (c) provide the touch-based GUI for selecting the publishing website, and (d) use HTTP to upload the file along with user information to the publishing website over the cellular data network.

Claim 11 — Non-transitory computer-readable medium (camera side): Method steps stored as machine-executable instructions for the camera: post-pairing acquisition of video/image media, file creation and storage with the pairing preserved, receipt of the app-initiated transfer request, and transfer to the authenticated phone. The claim also carries the phone-side "wherein" clauses — receiving/storing the file, paired connection preserved, touch GUI with delete and website-selection inputs, and HTTP upload of the file plus app-stored user information to the publishing website over a cellular data network.

Dependent claims (quick map):

• 2 / 5 / 8 / 12 — create, store, and transfer an associated file (data associated with the new media) to the phone/into its memory.
• 3 / 6 / 10 / 13 — the paired wireless connection is one of Bluetooth, Wi-Fi, or other personal-area wireless networking technologies that use pairing.
• 9 — the software application is either stored on a non-transitory computer-readable medium and installable in phone memory, or downloadable from a remote server.

Notable scope observations (plain reading): the independent claims are camera-centric in their performance/structural elements, with the publishing-website upload and touch GUI recited as capabilities of the phone-side software rather than steps performed by the claimed device. The claims also appear to impose order/timing constraints — media must be captured after pairing, and the file must already exist in the camera before the transfer request is received.

4. Litigation and PTAB/CAFC posture (2026)

What the sources actually show for the '806 itself:

• District court: Google Patents' "Family has litigation" data lists three E.D. Tex. cases: 2:26-cv-00226, 2:25-cv-00949, and 2:23-cv-00227 (via Unified Patents Litigation Data). Note the 2026 case number in that list.
• PTAB: The TikTok IPR set (IPR2024-00757/-759/-760/-767/-768/-769/-770) challenged family patents 8,756,336; 8,862,757; 8,898,260; 11,659,381; 11,234,121; 9,900,766; and 8,904,030. US 10,425,806 is not among those listed challenged patents, though its direct continuation 11,234,121 (IPR2024-00768) is. Earlier, on 2026-03-31, Director Squires terminated seven TikTok CellSpin IPRs for failure to name all real parties in interest (foreign-government/RPI theory under Return Mail and Worlds v. Bungie); subsequently the PTAB agreed to review three CellSpin patents after the earlier TikTok challenges were rejected (Law360, 2026-04-17).
• Federal Circuit: I found no CAFC docket or appeal in 2026 that names US 10,425,806. The CellSpin CAFC activity I located concerns sibling patents, not the '806: the precedential CellSpin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306 (Fed. Cir. 2019) (§ 101 eligibility; patents 8,738,794 / 8,892,752 / 9,258,698 / 9,749,847) and the nonprecedential 2024 decisions in Nos. 22-2025 and 23-1526 (affirming summary judgment of noninfringement as to the '794, '752, and '847 patents), with certiorari denied 2025-05-05 in No. 24-944.

5. Uncertainty statements (explicit)

• I could not confirm any 2026 CAFC docket entry specifically captioned on US 10,425,806. Absence of evidence here is not evidence of absence; a CM/ECF-native docket query for the patent number would be needed to state this conclusively.
• The priority date is inconsistently reported across the sources retrieved (2007-12-27, 2007-12-28, and a specification-recited "Dec. 8, 2007" for provisional 61/017,202). I have not resolved this and it should be treated as an open factual question.
• Google Patents' "expires 2029-03-18" and Unified Patents' "expiration 2029-03-17" differ by one day. Google Patents states its legal status is an assumption and not a legal conclusion; the same caution applies to all litigation/status data above.
• The E.D. Tex. case numbers are reproduced as listed by Unified Patents Litigation Data, which itself disclaims legal-analysis accuracy; party names and asserted patents per case were not independently verified here.
• Claim characterizations above are my plain-language reading of the issued claim text as supplied; they are not claim constructions or legal opinions.

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

Let me dig deeper into the specific cases and the '806 patent.

Let me verify the remaining cases (Garmin, Fossil, and a possible 2026 case).

Litigation Involving U.S. Patent No. 10,425,806

Bottom line: US 10,425,806 ("the '806 patent," titled Automatic multimedia upload for publishing data and multimedia content, issued Sept. 24, 2019, assignee CellSpinSoft Inc.) has been asserted by Cellspin Soft, Inc. in the Eastern District of Texas. I identified one fully confirmed case (Panasonic) and one additional case confirmed by press reporting (SZ DJI). Several adjacent 2025–2026 cases likely involve the '806 patent but I could not confirm the asserted patent list before exhausting my search budget — flagged below.

A note on scope: the well-known 2017–2018 Cellspin Soft litigation against Fitbit, Nike, Under Armour, Fossil, Garmin, Nikon, TomTom, Canon, GoPro, Kodak, and JK Imaging (all N.D. Cal., 4:17-cv-05928 et seq.) asserted the '794, '752, '698, '539, and '847 patents — not the '806 patent, which did not issue until 2019. Those cases should not be listed as '806 litigation.

Confirmed cases asserting the '806 patent

1. Cellspin Soft, Inc. v. Panasonic Corporation, Panasonic Holdings Corporation, and Panasonic Corporation of North America

• Plaintiff: Cellspin Soft, Inc.
• Defendants: Panasonic Corporation; Panasonic Holdings Corporation; Panasonic Corporation of North America
• Jurisdiction: U.S. District Court for the Eastern District of Texas, Marshall Division (Judge Rodney Gilstrap; Magistrate Judge Roy S. Payne)
• Case No.: 2:23-cv-00227
• Filing date: May 22, 2023
• Patents asserted (per the AO 120 form filed with the USPTO): U.S. Pat. Nos. 11,234,121; 10,425,806; 9,900,766; 8,898,260; 8,862,757; and 8,756,336
• Outcome/status: Terminated. All deadlines were stayed (orders July 27, 2023 and Aug. 25, 2023), and on Oct. 3, 2023, Judge Gilstrap granted Cellspin's notice of voluntary dismissal, dismissing all claims with prejudice under Rule 41(a)(1)(A)(i). AO 120 termination notice filed Oct. 4, 2023.
• Sources: Justia docket 2:2023cv00227 · DocketAlarm AO 120 form

2. Cellspin Soft, Inc. v. SZ DJI Technology Co., Ltd. and DJI Europe B.V.

• Plaintiff: Cellspin Soft, Inc.
• Defendants: SZ DJI Technology Co., Ltd.; DJI Europe B.V.
• Jurisdiction: U.S. District Court for the Eastern District of Texas (Judge Rodney Gilstrap; Magistrate Judge Roy S. Payne)
• Case No.: 2:25-cv-00949
• Filing date: September 15, 2025
• Patents asserted: U.S. Pat. Nos. 9,900,766; 10,425,806; and 11,234,121 (per multiple press reports)
• Outcome/status: Pending. Defendants filed a Rule 12(b)(6) motion to dismiss (Feb. 9, 2026); Cellspin opposed (Feb. 23, 2026); DJI replied (Mar. 2, 2026); Cellspin sur-replied (Mar. 9, 2026). A scheduling/case-management conference was set for March 26, 2026. Cellspin seeks a permanent injunction and treble damages for alleged willful infringement (camera/drone products plus the DJI Mimo and DJI Fly apps).
• Sources: Justia docket 2:2025cv00949 · pconline report naming the three patents

Cases likely (but not confirmed) to involve the '806 patent

These follow the same Cellspin Soft E.D. Tex. campaign and are consistent with the three-patent family ('766 / '806 / '121), but I could not verify the asserted patents before running out of search steps. Treat the patent lists as unconfirmed:

• Cellspin Soft, Inc. v. Garmin Corporation — E.D. Tex., 2:25-cv-00950, filed Sept. 15, 2025 (Gilstrap/Payne). Docket shows three patent exhibits and a Rule 12(b)(12) motion to dismiss filed Jan. 9, 2026, with briefing through Feb. 6, 2026; conference set 3/26/2026. Likely the same three patents as the DJI case. Status: pending. (Justia docket)
• Cellspin Soft, Inc. v. Fossil Stores I, Inc. et al. (Fossil Group, Inc.) — E.D. Tex., 2:25-cv-00683, filed July 3, 2025 (Gilstrap). Reported as asserting "three patents related to bluetooth data transfer technology." Status: pending. (Law.com Radar)
• Unidentified 2026 case — E.D. Tex., 2:26-cv-00226. This case number appears in the "family has litigation" data on the patent's own Google Patents page, tagged to US 10,425,806. I could not retrieve party names or the asserted patents. (Google Patents US10425806B2)

Related PTAB proceedings (context, not district-court litigation)

The '806 patent does not appear as a challenged patent in the TikTok Inc. v. CellSpin Soft IPRs, which cover related family members only: IPR2024-00757 (8,756,336), -00759 (8,862,757), -00760 (8,898,260), -00767 (11,659,381), -00768 (11,234,121), -00769 (9,900,766), and -00770 (8,904,030). On March 30, 2026, Director Squires vacated institution and terminated all seven proceedings on real-party-in-interest grounds (TikTok allegedly failed to identify a foreign-government RPI). (NYIPLA PTAB summary)

Caveats

• I could not access the Unified Patents litigation portal, PACER, or the CAFC docket directly within my search limits, so the list above may be incomplete — particularly for the 2026 case (2:26-cv-00226) and the Fossil/Garmin patent lists.
• The 2019 Garmin Corp. v. Cellspin Soft Supreme Court cert. petition (No. 19-400) and the Fitbit/Nike etc. N.D. Cal. appeals involve the earlier family members ('794, '752, '698), not the '806 patent, and are excluded.
• For a definitive, current docket, I recommend pulling the case records directly from PACER/Unified Patents for 2:25-cv-00683, 2:25-cv-00950, and 2:26-cv-00226.

I'll start by verifying the structured data against public sources.

PTAB / AIA Trial Analysis — U.S. Patent No. 10,425,806 ("Automatic multimedia upload for publishing data and multimedia content")

Proceedings overview

As of 2026-10-01, there are zero AIA trial proceedings on U.S. Patent No. 10,425,806 — the USPTO Open Data Portal structured block returns no AIA trials, and independent web searches surfaced no IPR, PGR, or CBM petition naming the '806 patent. The bottom line for a defendant is unusual and cut both ways: the patent is untested at the PTAB (so no claim is canceled, no FWD exists to cite, and no § 315(e)(2) estoppel constrains you), but Cellspin's sibling patents in the same family have been through a multi-year, multi-petitioner PTAB gauntlet — including a 2026 Director-level wipeout of seven instituted TikTok IPRs — so the prior-art and § 101 roadmap for attacking the '806 is well developed even though the '806 itself has never been challenged.

Because the required per-proceeding format has no entries, I have substituted a verified "adjacent proceedings" table for context, followed by the strategic analysis.

Why the structured data is right — and what I verified

One flag, deliberately not overstated: Cellspin's own exhibit list in the TikTok IPRs references a "Cohen Declaration (as filed in IPR2021-00476 at Exh. 2004)" and a "Harrison Declaration (as filed in IPR2021-00476 at Exh. 2005)" (PO Exhibit List, IPR2024-00767). That tells me an IPR2021-00476 exists in the Cellspin orbit, but the sources I retrieved do not state which patent it targeted, and I will not assume it was the '806. Treat it as a research lead to pull directly from PTAB E2E, not as a finding.

Adjacent Cellspin Soft proceedings (context only — none involve the '806 patent)

IPR2024-00757, -00759, -00760, -00767, -00768, -00769, -00770 — TikTok Inc. (joined by LifeScan, Senseonics, Ascensia) v. Cellspin Soft, Inc.

• Type: Inter Partes Review (7 petitions, 7 different patents)
• Filed: 2024-04-01 and 2024-04-05 (per 2:23-cv-00496-JRG-RSP, No. 106)
• Status: Institution granted, then vacated and petitions denied. The Board denied Cellspin's motion to terminate on 2025-06-02 (Paper 32); Acting Director Stewart sua sponte initiated Director Review on 2025-06-05 and stayed all seven; on 2026-03-30 Director Squires vacated the institution decisions, denied the petitions, and terminated the trials for failure to identify all real parties-in-interest — specifically the alleged Chinese-government RPI — applying Tianma Microelectronics Co. v. LG Display Co., IPR2025-01579, Paper 12 (Director Mar. 18, 2026) (precedential). See Director Review Order in IPR2025-01061 describing the Cellspin Soft IPRs.
• Judge panel: Gregg I. Anderson, Cynthia M. Hardman, Michael A. Valek
• Defensive value: A pure procedural kill, not a merits win. No claim of any of these seven patents was held invalid or valid. If you are a Cellspin defendant, do not treat these as invalidating precedent — the art TikTok assembled was never adjudicated.

IPR2029-… (n/a) — Senseonics / LifeScan / Ascensia v. Cellspin Soft (IPR2024-00768/-769/-770 joinders vacated; independent petitions IPR2025-00102/-103/-104)

• Status (per Senseonics' 2026-03-31 10-Q): Board granted institution on all three patents 2026-04-15; final hearing set 2026-06-30; Cellspin's rehearing requests denied 2026-04-28. Law360 reports (2026-06-30) that the three challengers settled the disputes after institution. If so, there is no FWD. (Senseonics 10-Q)
• Patents: '121, '766, '030 — not '806.

IPR2019-00127 (Canon U.S.A.) and IPR2019-00131 (Panasonic) v. Cellspin Soft — U.S. Pat. No. 9,258,698

• Status: IPR2019-00131 instituted 2019-04-29 on claims 1, 3–5, 7, 8, 10–13, 15–20 (Institution Decision, Paper 11). Cellspin's briefs state all PTAB cases went up on CAFC appeal (Cellspin comments to USPTO, 2020-11-13).
• Highly relevant intelligence on the '806: Canon's petition expressly targeted the limitation that was added by Examiner's Amendment during prosecution — "the simple requirement of the cellular phone including a user interface to delete an image file created by the digital camera" — and asserted it was well known. Claim 1 of the '806 contains the same structural hook: "a touch based graphical user interface … configured to receive input to delete the created new-media file, and … to receive input to select a user media publishing platform." That is the narrowest, allowance-driving limitation in the '806, and it has a documented obviousness attack template.

Related civil litigation (not PTAB, but relevant posture)

• Cellspin Soft, Inc. v. Panasonic Corp. et al., No. 2:23-cv-00227 (E.D. Tex., filed 2023-05-22) — asserts the '806 along with '121, '766, '260, '757, '336 (AO 120 filing).
• Cellspin Soft, Inc. v. ByteDance Ltd. et al., No. 2:23-cv-00496 (E.D. Tex.) — stayed pending IPR; does not assert the '806.
• 2025 and 2026 E.D. Tex. filings (2:25-cv-00949; 2:26-cv-00226) are listed in the structured data as current family litigation.

Strategic summary

Claim status on the '806. Nothing is canceled; nothing is sustained; everything is untested. All 13 claims — independent claims 1 (method), 4 (camera device), 7 (system), 11 (CRM), and dependents 2–3, 5–6, 8–10, 12–13 — stand as issued. There is therefore no FWD to quote and no claim-level disposition to rely on. Any representation that a Cellspin FWD invalidated a claim of the '806 would be false; the vacated TikTok institutions produced no merits rulings at all.

Estoppel landscape. Because the '806 has never been the subject of an instituted IPR, 35 U.S.C. § 315(e)(2) estoppel does not attach to the '806 at all — not for you and not for any prior challenger. The full § 102/§ 103 prior-art universe of patents and printed publications, plus § 112 and § 101, is available. Two timing cautions, however: (i) § 315(b) bars an IPR petition filed more than one year after service of a complaint alleging infringement of the '806, so early-filed defendants (Panasonic, 2023) are already time-barred and any new defendant must count from its own service date; and (ii) the USPTO's October 2025 proposed rules would permit only one instituted IPR per patent and bar IPRs against patents that have survived a prior validity challenge, so first-mover advantage matters more than it used to.

Pattern signals. Cellspin is a serial, portfolio-wide assert-and-litigate patent owner that has never won a PTAB merits decision on this family — the outcomes have been procedural vacaturs, discretionary denials, settlements, and § 101 dismissals later reversed on appeal (Cellspin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306 (Fed. Cir. 2019), which held Alice step two can raise questions of fact and reversed dismissal and a fee award). Notably, the '806 skipped both the 2019 Canon/Panasonic wave and the 2024–2026 TikTok/LifeScan/Senseonics wave. No defensive aggregator (Unified Patents, RPX, etc.) appears in the chain for the '806 or its siblings based on the sources retrieved. The absence of an IPR against the '806 is a genuine signal, but a nuanced one: it has been asserted since at least 2023, it is a close sibling of patents that drew seven petitions, and it survived the PGR window untouched — consistent with it being the family member whose claims the § 101 assault (the family's preferred attack) disposed of first, rather than a hardened patent that earned its way past the Board.

Recommended next steps

1. Do not cite an '806 FWD — there isn't one. If you are defending and need an invalidity hook, build it independently from the sibling-patent record: the Examiner's Amendment limitation (delete-image UI), the Cryptographic-auth + HTTP-combination art TikTok assembled (Hiroishi, Aaltonen, Drescher, Mashita, Kahn, Feinberg), and the § 101 arguments that have repeatedly defeated this family in district court.
2. Pull IPR2021-00476 from PTAB E2E directly to confirm which Cellspin patent it targeted. If it targeted an '806-family patent, its grounds and outcome are directly reusable; my sources do not establish the patent number, so verify before relying on it.
3. If you are newly served with an '806 complaint, file within 12 months (35 U.S.C. § 315(b)) and note that under Director Squires' 2025-10-16 memorandum the Director — not an APJ merits panel — decides institution, which materially lowers institution rates and raises the value of a strong § 325(d) or Fintiv-type showing.
4. Track the pending Senseonics/LifeScan/Ascensia IPRs to see whether they truly settled without an FWD. A settlement means no estoppel and no invalidation; a reopened FWD on the '121/'766/'030 art could be used as persuasive authority against parallel '806 limitations.
5. For a § 101 defense, use the primary CAFC authority directly: Cellspin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306 (Fed. Cir. 2019) — available via CourtListener search — and be precise that it reversed the dismissal, so it is a burden/allocation precedent, not a holding that these claims are patentable.
6. On the § 101 cert track, note that Garmin et al. sought Supreme Court review in Garmin USA, Inc. v. Cellspin Soft, Inc., No. 19-400 (petition filed 2019-09-23, with a brief in opposition and reply brief on file). I could not confirm the disposition from the sources I retrieved — verify at the Supreme Court docket before citing it.

Sources

• Canon petition, IPR2019-00127 (U.S. Pat. No. 9,258,698): https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1520635](/patent/1520635)/download-documents
• Panasonic v. Cellspin, IPR2019-00131 institution decision and Patent Owner Response: https://www.docketalarm.com/cases/PTAB/IPR2019-00131/Inter_Partes_Review_of_U.S._Pat._9258698/
• TikTok v. Cellspin Order Denying Motion to Terminate (Paper 32, 2025-06-02): https://ipwatchdog.com/wp-content/uploads/2025/06/Order-Denying-Motion-to-Terminate-1.pdf
• Director Review order describing the seven Cellspin Soft IPRs (2026): https://www.uspto.gov/sites/default/files/documents/ipr2025-01061_tiktok_v_destefano_director_review_order.pdf
• E.D. Tex. stay order, Cellspin v. ByteDance, No. 2:23-cv-00496 (No. 106): https://www.docketalarm.com/cases/Texas_Eastern_District_Court/2--23-cv-00496/Cellspin_Soft_Inc._v._ByteDance_Ltd._et_al/docs/106.pdf
• Senseonics Holdings 10-Q (2026-03-31) describing IPR status: https://www.sec.gov/Archives/edgar/data/[1616543](/patent/1616543)/000110465926057233/sens-20260331x10q.htm
• Cellspin comments to USPTO (2020-11-13) on the family's PTAB history: https://www.uspto.gov/sites/default/files/documents/11132020CellSpinSoftInc.pdf
• AO 120 listing the '806 among patents asserted in 2:23-cv-00227: https://www.docketalarm.com/patentapps/US/14-109,972/AUTOMATIC_MULTIMEDIA_UPLOAD_FOR_PUBLISHING_DATA_AND_MULTIMEDIA_CONTENT/docs/LUVDRY5JXBLUEX4.pdf

Caveats: PTAB E2E party/proceeding-level data for the 2025–2026 Cellspin matters is partly drawn from secondary sources (Law360 headlines, SEC disclosures, NYIPLA committee summaries, PTAB petition exhibits) rather than a direct ODP AIA-trial pull; the ODP block in the prompt is authoritative for the '806 and reports nothing. Judge panels and FWDs quoted above apply to sibling patents only, not to the '806.

I'll research the assignment chain for US 10425806. Let me start with several searches in parallel.

Good data. Let me dig deeper into the specific assignment records and reel/frame numbers.

Assignment & Ownership Analysis — US 10,425,806 B2

Patent: US 10,425,806 B2 — "Automatic multimedia upload for publishing data and multimedia content"
Application: 15/659,637 (filed 2017-07-26; issued 2019-09-24) — a continuation in a long family descending from provisional 61/017,202 (2007-12-28) and non-provisional 12/333,303 (2008-12-11).
Priority date: 2007-12-28

A note on sourcing before the analysis: I could reconstruct the substance of every post-issuance event from the record images indexed by Google Patents, Docket Alarm, and PlainSite, but the indexed copies expose EPAS IDs and execution/record dates rather than full reel/frame numbers for the 2018 security-interest batch and the 2021 assignment. Those reel/frame cells are marked "not retrieved" below rather than guessed. Verify the exact reel/frame directly at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (search "10425806"; the Alternate Source is https://assignment.uspto.gov/patent/index.html).

Inventors

All three are listed on every member of the family, and all three executed the original assignment to CellSpinSoft (paperwork executed 2012-12-03) and again appeared as assignors on the 2021-12-09 confirmatory assignment back to CellSpinSoft Inc.

Unusual pattern? The opposite of the usual one. There was no inventor attrition. The "all inventors leave within 12 months of filing" fire-sale tell is not present — the founders stayed attached to the assignee for roughly 14 years and re-executed an assignment in its favor as late as December 2021. That longevity pattern is what you'd expect from a founder-owned company, not from a portfolio assembled and flipped by a broker. Note also that Singh and Klein appear on both sides of the 2018 security-interest filings — they are named inventors and secured lenders to the company (see below), a founder-financing fingerprint.

Original assignee

• CellSpinSoft Inc. (rendered "Cellspinsoft Inc." on some records), originally 4423 Fortran Drive, Suite #116, San Jose, CA 95134; later 1410 Mercy Street, Mountain View, CA 94041. California corporation. Claimed small-entity status.
• Line of business: the company was formed (2008) around the inventors' Bluetooth camera-to-phone auto-publish concept; its commercial footprint is essentially non-existent and its business is IP holding and enforcement.
• Product embodiment: No evidence that the original assignee ever shipped a product embodying the claims. Chinese litigation coverage characterizes CellSpinSoft as founded 2008, "with almost no actual products, yet holds 17 patents — a textbook NPE profile." Google Patents lists it as Current Assignee; the assignment chain never terminates in a defensive aggregator.
• Current status: Operating — actively litigating as of the September 2025 action against DJI, and defending a live PTAB/reexam front. Not dissolved, not in bankruptcy.

Assignment timeline

Two recordings of the original inventor → company assignment exist for this family (per-application recordings), plus an 11-way security-interest batch in 2018 and a 2021 confirmatory assignment. Recorded events follow chronologically.

• 2012-12-03 (executed) / recorded 2014-10-01 — Reel 33857/0990

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Singh, Gurvinder; Klein, Marcos; Laviano, Vince
  • Assignee: CellSpinSoft Inc. ("Cellspinsoft Inc."), 4423 Fortran Drive, Suite #116, San Jose, CA 95134
  • Correspondent: not surfaced in the indexed record
  • Context: Original inventor→company assignment; covers sibling application 14/503,401 (pub. US 2015/0019695 A1). Same executed instrument as the next entry — recorded per-application rather than per-patent.

• 2012-12-03 (executed) / recorded (updated) 2015-12-29 — Reel 34553/0037

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Singh, Gurvinder; Klein, Marcos; Laviano, Vince
  • Assignee: CellSpinSoft Inc.
  • Correspondent: not surfaced in the indexed record
  • Context: Second recording of the same instrument, this one covering sibling application 14/576,196 → US 9,226,138. Internal/administrative clean-up, not a change in beneficial ownership.

• 2018-07-24 to 2018-07-27 (executed) / recorded 2018-07-27 — Reel/Frame not retrieved (EPAS IDs PAT5071177, PAT5071311, PAT5071658, and eight further companion filings)

  • Conveyance: Security Interest (short-form "Intellectual Property Security Agreement")
  • Assignor: CellSpinSoft Inc. / "Cellspin Soft"
  • Assignee (Secured Party): eleven natural persons — Kessinger, James Bland; Singh, Gurvinder; Kastelic, John W.; Khan, Amir; Silverman, Neil; Klein, Marcos; Williams, Donald A.; Akella, Ram; Lin, David C.; Virmani, Rajeev; McSweenery, Eamonn.
    Each secured party is a natural person at a residential address (e.g., Gurvinder Singh, 151 Buckingham Drive #299, Santa Clara CA 95051; David C. Lin, 2195 Denise Drive, Santa Clara CA 95050; John W. Kastelic, 715 Flat Shoals Ave SE, Atlanta GA 30316).
  • Correspondent: JOHN W. KASTELIC, 715 Flat Shoals Ave SE, Atlanta, GA 30316, johnwkastelic@gmail.com — the same correspondent on every one of the eleven recordings, and himself one of the secured parties. This is the recurrence flag: the man recording the liens is a lienholder.
  • Covered property: a single 15-property collateral schedule that expressly includes Application No. 15/659,637 (i.e., this patent) plus US 9,226,138; 8,892,752; 8,904,030; 8,700,790; 8,738,794; 8,392,591; 8,762,560; 8,756,336; 8,862,757; 8,898,260; 8,798,539; 9,258,698; 9,747,847; 9,900,766.
  • Context: Securitization — CellSpinSoft pledged its entire patent family as collateral for pre-existing shareholder/convertible-note debt. The supplemental agreements recite underlying Security Agreements dated 2007-09-11 (Singh), 2007-09-21 (Lin), and a same-day agreement for Kastelic (2018-07-24) — i.e., the obligations reach back to the company's founding year.

• 2021-12-09 (recorded) — Reel/Frame not retrieved

  • Conveyance: Assignment of Assignors' Interest (see document for details)
  • Assignor: Klein, Marcos; Laviano, Vince; Singh, Gurvinder
  • Assignee: CellSpinSoft Inc.
  • Correspondent: not surfaced in the indexed record
  • Context: Chain-of-title clean-up. A confirmatory assignment from the three founders back to the company, executing roughly two months before this family's 2022-2023 assertion wave (Panasonic, TikTok/ByteDance). Likely executed to cure any residual cloud left by the 2018 security batch and to paper standing before suit.

No "Release by Secured Party" event specific to this patent's collateral schedule was found in the indexed sources. (A release recorded as reel 57969/0180 on 2021-10-18 exists, but it attaches to a different patent family — application 12/334,046 — and must not be conflated with this one. Whether the eleven 2018 liens were ever released of record for the '806 schedule is a genuine open item to confirm at the Assignment Center.)

Timeline diagram

timeline
    title Ownership of US 10425806
    2007 : Provisional filed by Singh Klein Laviano
    2008 : Parent application filed
         : Founders assign to CellSpinSoft
    2012 : Inventor assignment executed
    2014 : Assignment recorded reel 33857
         : Second recording reel 34553
    2017 : Continuation application 15 659 637 filed
    2018 : Eleven security interests recorded to lenders
         : Correspondent John W Kastelic
    2019 : Patent US 10425806 issued
    2021 : Confirmatory assignment to CellSpinSoft
    2023 : Suit against Panasonic
    2024 : Suits against TikTok and Senseonics
    2025 : Suit against DJI

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
There is no IP-holding LLC in this chain. The patent never left CellSpinSoft Inc., the original operating assignee, from the 2012 inventor assignment through the 2021 confirmatory assignment. No "IP / Patents / Holdings / Ventures" successor and no single-purpose Delaware/Texas LLC appears in any recorded link. The absence of a shell transfer is notable: this is a founder-owned NPE, not an assembled one.

2. Known asserter in the chain — PRESENT (strong).
CellSpinSoft is affirmatively classified as an NPE by Unified Patents, which states the '381 and '757/'260/'030 patents (same family as this one) are "owned and asserted by Cellspinsoft, Inc., an NPE." Unified's PTAB tracker labels the patent owner entity type "NPE (Small Company)" across IPR2019-00127/-00131 and IPR2019-01107/-01108. The Stanford NPE Litigation Database also carries CellSpin Soft cases. CellSpinSoft has asserted this family against Fitbit, Garmin, GoPro, Canon, Panasonic, Nikon, Under Armour, Fossil, Moov, Misfit, ByteDance/TikTok, Senseonics, Ascensia, LifeScan, and (Sept. 2025) DJI. It does not appear on the Acacia/Marathon/IV/Wi-LAN named lists, but the Unified/Stanford designations are dispositive on their own.

3. Repeat correspondent across the chain — PRESENT (strong within this chain).
John W. Kastelic, 715 Flat Shoals Ave SE, Atlanta, GA 30316, is the correspondent of record on all eleven 2018-07-27 security-interest recordings (EPAS PAT5071177 [Singh], PAT5071311 [Lin], PAT5071658 [Kastelic], and companions). He signed as both the submitting correspondent and a named secured party on his own filing. Same-name correspondence recurs across the entire collateral batch. The usual NPE reading of this signal is "one lawyer rides herd on a herd of shells"; the variation here is that the recurring figure is an insider creditor recording liens against the founder's company, not a shell operator. Flag it precisely: recurrence is real, characterization is insider-financing.

4. Cascading transfers — NOT PRESENT (in the classic form).
There is no <24-month chain of successive LLC-to-LLC conveyances. What exists instead is a mass simultaneous recording event: eleven security interests executed within 72 hours (2018-07-24 to 07-27) to eleven lenders sharing one correspondent. That is a debt-securitization cluster, not a cascading assignment chain.

5. Pre-litigation transfer — NOT PRESENT.
No ownership assignment sits within six months of a first-filed suit on this patent. The only ownership event proximate to litigation is the 2021-12-09 confirmatory assignment, which precedes the 2022-2023 campaigns by a year-plus — a standing-cure timing pattern (worth noting), but outside the six-month window.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 record for CellSpinSoft; the company is an active plaintiff as of late 2025.

7. Privateering — NOT PRESENT.
No operating company sits behind CellSpinSoft asserting through it against competitors. CellSpinSoft asserts its own founder-issued patents directly.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT, Unified, or OIN. The inverse is true: Unified Patents is the adversary here, having repeatedly petitioned against this family ('757, '260, '381, '030, and the '806 sibling set).

Verdict

NPE — high confidence.

Justification: two strong signals are present. (a) Known asserter — Unified Patents designates CellSpinSoft "an NPE" and scores its patent-owner entity type as "NPE (Small Company)" across the '806 family's PTAB dockets, corroborated by the Stanford NPE Litigation Database, with serial assertion against Fitbit, Garmin, GoPro, Panasonic, Nikon, Under Armour, Fossil, ByteDance/TikTok, Senseonics, LifeScan, and DJI. (b) Repeat correspondent — John W. Kastelic is the correspondent of record on all eleven 2018-07-27 security-interest recordings and is simultaneously a secured party, an insider-fingerprint recurrence. What makes the case clean is that the ownership chain itself shows none of the classic shell mechanics: the patent stayed with the original California assignee, the founder-inventors never left, and every post-issuance event is either a securitization (2018-07-27 collateral pledge of application 15/659,637, recorded under EPAS PAT5071177 et seq.) or a chain-of-title clean-up (2021-12-09). The NPE character therefore rests on the entity's conduct and absence of any product rather than on a shell-LLC transfer — and that evidence is documented, not inferred from naming.

Primary verification links: USPTO Assignment Center search for "10425806" — https://assignmentcenter.uspto.gov/ ; alternate — https://assignment.uspto.gov/patent/index.html ; litigation context — https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A23-cv-00227 ; Unified's NPE characterization — https://www.unifiedpatents.com/insights/2024/7/16/two-cellspinsoft-data-transfer-patents-challenges-instituted .

Open items to close at the Assignment Center (not resolvable from indexed sources): (i) exact reel/frame for the eleven 2018-07-27 security interests and for the 2021-12-09 assignment; (ii) whether any "Release by Secured Party" was recorded against the '806 collateral schedule after 2018; (iii) the correspondent of record on the 2012 and 2021 inventor assignments.

I'll research the USPTO record and prior-art citations for US 10,425,806.

Let me pull the citation lists directly from the patent record.

Let me locate the '806 front page and its cited references directly.

Prior-Art Analysis — US 10,425,806 B2

Scope note first (important): I must flag a hard limitation before any § 102 mapping. I was able to verify the patent record for 10425806 (literal), but I was unable to retrieve the enumerated "(56) References Cited" list printed on the face of US 10,425,806 B2 itself within my search budget. Google Patents' rendered text supplied for this patent omits the front-page citation table, and the Unified Patents record for this exact patent (https://portal.unifiedpatents.com/patents/patent/US-10425806-B2) shows only summary counts — "Patent Art (10)" / "Non-Patent Literature (14)" / "Referenced By (0)" — without exposing the individual references.

I will therefore do three things: (1) confirm the record; (2) report the citation lists I did retrieve, which come from other members of the same family, clearly labeled as such and not asserted to be the '806's own face citations; and (3) give a § 102 analysis that distinguishes what is grounded from what is inference. I will not invent reference numbers or dates.

1. Record verification (USPTO / public records)

The "Referenced By (0)" figure is notable: as of the retrieved record, no later patents cite the '806 in the forward-citation field. This is consistent with the fact that the '806 is itself a late-issued continuation in a family whose earlier members carry the bulk of the forward citations.

⚠️ Consistency with the previously generated sections: these bibliographic values match the earlier Patent Summary (including the recurring 2019-09-23 vs. 2019-09-24 and 2007-12-27 vs. 2007-12-28 one-day discrepancies). No new contradiction found. One item in the earlier Patent Summary was garbled by the source ("17/542,373 (now US 16,593,81/11,659,381)") — the correct literal is US 11,659,381, consistent with the IPR list in the Litigation Summary.

2. What the record tells us about the '806's art field

Because the '806 claims priority to 2007-12-28, every anticipating reference under § 102(a)/(b) must predate that date (or the contested 2007-12-08 provisional date). The 10 patent references the examiner cited are therefore necessarily pre-2007 art.

The examiner for the entire CellSpinSoft family is Sulaiman Nooristany (AU 2415) — the same examiner named on US 8,756,336, US 8,738,794, US 8,862,757, and (per PTAB record) US 11,234,121. That is useful: the family's citation lists are the best available proxy for what the examiner considered, and they overlap heavily across the continuation chain.

3. Citation lists retrieved from the same family (not confirmed as '806 face citations)

3a. US 11,234,121 B2 — direct continuation of the '806 (filed 2019-08-06)

Retrieved from the '121 front page (patentimages PDF). Grant dates as printed:

Source: US11234121B2 front page PDF

3b. Earlier family members — examiner-cited art (marked "* cited by examiner" on their faces)

US 8,756,336 B2 (Appl. 14/109,972; granted 2014-06-17):

• US 7,519,916 B1 — Hartwell et al. (4/2009)
• US 2002/0167932 A1 — McGowan
• US 2003/0157960 A1 — Kennedy
• US 2008/0109377 A1 — Singh
• US 2009/0023428 A1 — Behzad et al.

US 8,738,794 B2 (Appl. 13/922,227):

• US 2003/0157960 A1 — Kennedy
• US 2006/0264176 A1 — Hong
• US 2008/0163311 A1 — St. John-Larkin
• US 2009/0023428 A1 — Behzad et al.

US 8,862,757 B2 (Appl. 14/273,546):

• US 2003/0157960 A1 — Kennedy

Sources: Ex. 1001 in IPR2024-00757 (US 8,756,336) · Ex. 1013 in IPR2024-00757 (US 8,862,757) · Ex. 1011 (US 8,738,794)

Critical caveat on 3a–3b: these are several dozen references across different family members with different claim sets. The '806's own face carries only 10 patent references. I cannot tell you which 10 without the '806 front page, and I will not pretend the lists above are interchangeable. Treat them as candidate pools, not as the '806's citation list.

4. § 102 analysis

4a. The anticipation test applied to these claims

The '806's independent claims each require, in one reference, the union of:

(i) a digital camera device with short-range wireless capability;
(ii) a short-range paired connection to a cellular phone, where the camera cryptographically authenticates the phone's identity using an association protocol;
(iii) new-media acquisition occurring after pairing, then file creation and storage in camera memory;
(iv) a data transfer request initiated by a mobile app on the phone, over the paired link, for the already-created file;
(v) transfer of the file over the paired link;
(vi) phone-side app storing the file (pairing preserved), and using HTTP to upload the file plus app-stored user information to a user media publishing website over the cellular data network;
(vii) a touch-based GUI for the file accepting input to delete (claims 1, 11) and to select the publishing website (claims 1, 4, 7, 11).

Under § 102, all of this must be found in one reference, arranged as claimed. Nothing in the retrieved art lists suggests a single reference disclosing element (vii) in combination with (vi)'s "app-stored user information" limitation — that combination is the likely reason the examiner did not reject on § 102 and instead allowed these claims.

4b. Which references are plausible § 102 candidates, and for which claims

I want to be precise about my confidence level here. I have reference numbers, inventor surnames, and grant dates but I have not read the specifications of the individual references. Accordingly, the mapping below is an analyst triage by subject matter and timing, not a confirmed anticipation finding. Every reference listed in § 3 predates 2007 except the post-2007 grants (US 7,319,455; 7,327,981; 7,333,785; 7,340,766; 7,366,861; 7,424,267; 7,506,057; 7,509,118; 7,512,685; 7,515,937; 7,522,181; 7,551,210; 7,607,243; 7,633,524; 8,163,804; 8,774,072) — those are § 102(e)/§ 102(a)(2)-type art only as of their earlier effective filing dates, and post-2007 items are weak as § 102 art against a 2007 priority claim unless their filing predates 2007-12-28.

4c. Bottom line on § 102

• No reference in the retrieved material is identifiable as a single-reference anticipation of any of claims 1, 4, 7, or 11, on the strength of what I can actually verify. The claims' distinguishing limitations — post-pairing capture ordering, the camera-side cryptographically authenticated pairing with the phone, HTTP upload of the file plus app-stored user information over the cellular data network, and the touch GUI with both delete and website-selection inputs — are the elements most likely to have driven allowance, and I found no single pre-2007 reference disclosing them together.
• The dependent claims 2/5/8/12 (associated file) and 3/6/10/13 (Bluetooth / Wi-Fi / "other personal area wireless networking technologies that use pairing") are substantially weaker on their faces: the connection-type claims in particular recite alternatives that were, by 2007, conventional. If any claims in this patent are vulnerable to § 102, it is these dependents — but vulnerability to § 102 requires a single reference teaching the independent claim's full combination plus the dependent's added limitation, so the dependents inherit the independents' strength.
• Claim 9 (software installable from a CRM or downloadable from a remote server) is a conventional delivery-mode claim; a § 102 hit would require a reference expressly disclosing both alternatives as claimed.

4d. Non-patent literature

The record shows 14 NPL references. I could not retrieve the list, and I will not speculate about them. Given the 2007 priority, the likely candidates would be Bluetooth SIG profile specifications (OBEX/GOEP, which the '806 specification itself discusses at length) and contemporaneous camera-phone product literature — but that is inference, not a citation.

5. Explicit uncertainty statements

1. I did not obtain the face citations of US 10,425,806 B2. The "10 patent / 14 NPL" counts are from Unified Patents; the identity of those 24 documents is unknown to me on this evidence. This is the single most important gap in this analysis — the requested deliverable cannot be fully completed without the '806 front page or its file wrapper (PTO PatentCenter / Global Dossier, or the USPTO Patent Assignment/IFW record for 15/659,637).
2. The citation tables in § 3 are from US 11,234,121, US 8,756,336, US 8,738,794, and US 8,862,757 — different applications with different claim sets and different prosecution histories. They are proxies, not the '806's citations, and I have labeled them as such throughout.
3. I have not read the specifications of the individual cited references. The § 102 triage in § 4b is subject-matter-and-date based, not a claim-chart. Any of those characterizations could change on reading.
4. Inventor-name renderings ("Rezyani", "Kuritsko") are reproduced literally as printed; they may be misspellings of "Rezvani"/"Kurikko" in the source, and I have not corrected them per the operating rule.
5. The "US 8,774,072 B2 — 7/201…" row is truncated in the retrieved source; I do not have its full grant date.
6. I found no PTAB proceeding in which US 10,425,806 is the challenged patent — the TikTok IPRs cover family members only (8,756,336; 8,862,757; 8,898,260; 11,659,381; 11,234,121; 9,900,766; 8,904,030). Consequently there is no petitioner-filed § 102 ground against the '806 itself available in the public record I reached, which is itself a meaningful data point: no third party has yet publicly staked out a § 102 theory against this specific patent.

6. Recommended next step to complete this deliverable

To convert the above from triage to a definitive citation inventory, pull one of:

• the '806 front page via USPTO PatentCenter for application 15/659,637 (the "(56) References Cited" block plus the IDS/892/1449 listings), or
• Global Dossier for family 40799912, which will surface the examiner citations across the continuation chain in one view.

With that list in hand, each of the 10 patent references and 14 NPL items can be given the full treatment requested (citation, publication and filing dates, description, and per-claim § 102 analysis). I can complete that mapping immediately once the face-citation list is supplied or retrieved.

I'll gather the prior-art references relevant to this patent family before building the § 103 analysis.

Let me pin down the specific prior-art references (numbers, dates) used in the Cellspin prosecution and IPRs.

Obviousness Analysis — U.S. Patent No. 10,425,806 B2 under 35 U.S.C. § 103

Basis and a required caveat on the "Prior Art" section. The Google Patents page as fetched for this project includes only prior-art keywords ("short," "cellular phone," "new," "range," "media") and the prior-art date (2007‑12‑28); it does not reproduce the "References Cited" / "Citations" table. I therefore grounded this § 103 analysis in the prior-art record that the '806's own family generated in prosecution and in the related PTAB proceedings (Canon/Panasonic/Garmin/GoPro/JK Imaging IPRs; TikTok IPRs; LifeScan IPR2025‑00103), which is the same body of art that the examiners and the Board treated as the relevant art. Where I could not verify a reference's number or date to the level of a citation, I say so explicitly rather than guessing.

1. Legal framework and the level of ordinary skill

Framework. Obviousness asks whether the subject matter as a whole would have been obvious at the effective filing date to a person having ordinary skill in the art (POSITA), considering (1) the scope and content of the prior art, (2) the differences between the prior art and the claims, (3) the level of ordinary skill, and (4) secondary considerations. Graham v. John Deere Co., 383 U.S. 1 (1966). The inquiry is flexible; a claim is obvious where "the combination of familiar elements according to known methods … yield[s] predictable results." KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 416 (2007). A motivation to combine may come from the references themselves, the nature of the problem, or the ordinary creativity of a POSITA — it need not be expressly stated. Id. at 418–21.

POSITA. For the Cellspin family, the petitioner's expert in the related IPRs applied a December 28, 2007 invention date, and the Board's institution decisions adopted that framing. (Declaration language quoted in the IPR record: "I have applied a date of December 28, 2007, as the date of invention in my obviousness analyses.") The '806 specification's own cross-reference paragraph recites a provisional filing of Dec. 8, 2007 for application 61/017,202, while the Google Patents family data shows 2007‑12‑28 — a discrepancy already flagged in the earlier sections of this analysis. I treat the critical date as on or about late December 2007 and flag that if the claims were entitled to an earlier date, or denied the earlier date, the available art set shifts. That matters: the family's 2008 publications (Singh906 / Singh129, below) become prior art only if the claims lose the 2007 priority — a point TikTok litigated.

A POSITA here would have been someone with a bachelor's degree in electrical engineering or computer science and roughly 2–4 years of experience in wireless/mobile device software, image-capture devices, and network application protocols — consistent with the background the Board and the parties used in the family IPRs.

2. Scope of the claims (the limitations that must be met or shown obvious)

From claim 1 (and mirrored in claims 4, 7, 11), the technical content reduces to:

Claims 4, 7, 11 largely repeat this; claim 7 additionally recites the phone-side application as positively claimed subject matter; claim 4 omits the "delete" input and keeps the website-selection input; claim 11 tracks claim 1's GUI.

Dependents: 2/5/8/12 → create/store/transfer an associated file; 3/6/10/13 → connection is Bluetooth, Wi‑Fi, or other PAN technology that uses pairing; 9 → the app is installable from a non-transitory medium or downloadable from a remote server.

The patent's own specification is candid that its components are conventional: it describes Bluetooth pairing with a passkey exchange and cryptographic authentication, OBEX/GOEP/PTP/MTP/PictBridge transfer, HTTP or XML‑RPC transport, J2ME GUIs, and Flickr™/Picasa™/YouTube™/eBay® as publishing destinations. That admission cuts against any argument that the individual elements are non-conventional.

3. The prior-art landscape

Verified or well-attested references in the family's own record (all predating Dec. 2007 unless noted):

Note the structural point the Board repeatedly accepted: Kahn supplies the camera→phone→web-server architecture and HTTP-to-a-web-publishing-server, while Hiroishi/Feinberg/Bluetooth supply the short-range paired, authenticated link. The Board "reads Kahn too narrowly" language appears in the petitioner's replies (IPR2024‑00767/-769), and in IPR2024‑00767 the Board instituted on Hiroishi + Kahn + Bluetooth for the '381 sibling.

4. Grounds of rejection

Ground A — Kahn in view of Hiroishi and the Bluetooth 2.1 Specification (primary ground)

Reference mapping to claim 1:

• A (camera + phone with cellular internet): Kahn — camera captures; cellphone (host device) has the wireless/network connection; image management server is web-based.
• B (paired link; camera cryptographically authenticates the phone; association protocol): Bluetooth 2.1 Core Spec — pairing/bonding establishes a link key via an association model; authentication is a defined part of the pairing procedure. Hiroishi places Bluetooth in the camera and the phone specifically; Feinberg confirms the camera-phone Bluetooth pairing is a known configuration.
• C (media acquired after pairing): Hiroishi — images are captured and stored in camera memory and then transferred to the phone over the Bluetooth link.
• D (file created + stored in camera; stays paired): Hiroishi (camera memory) + Bluetooth (bond persists).
• E (transfer request initiated by the mobile app for an existing file): Hiroishi — the phone's program issues the instruction/request and "waits" for the thumbnail response; Kahn's phone-side application drives upload. This is the ordinary request/response ("pull") pattern.
• F (camera transfers the file): Hiroishi.
• G (HTTP upload of file + user info to a user media publishing website over the cellular data network): Kahn — HTTP between phone and the web-based image server; user authentication credentials and user ID/user profile keyed to the user. Kalajan independently confirms HTTP is the known protocol for phone→server photo upload.
• H (touch GUI with delete + website-selection): addressed in Ground C below.

Motivation to combine. Kahn supplies a camera/phone/server publishing system but is agnostic as to the local radio link; Hiroishi supplies exactly the short-range, in-camera radio (Bluetooth) to a phone, and the Bluetooth 2.1 spec supplies the paired/authenticated association that makes the camera-to-phone leg trustworthy and reusable. The motivation is (i) the nature of the problem — the camera has no WAN connectivity and must hand media to a phone that does; (ii) the express teaching of Hiroishi/Feinberg toward Bluetooth camera↔phone; and (iii) the ordinary desire for a secure, persistent link (pairing) so the user need not re-authorize each transfer. The combination yields no more than the predictable aggregation of Kahn's publishing flow with a known Bluetooth camera-phone link. KSR, 550 U.S. at 416.

Direction of cryptographic authentication (camera authenticates phone). This is the '806's most distinctive-sounding security recitation. Bluetooth authentication is a mutual key-based procedure, not one-way; the Core Spec's pairing/association establishes a shared link key used for authentication in both directions. A POSITA would read "the digital camera device cryptographically authenticating identity of the cellular phone" as satisfied by the ordinary paired/bonded Bluetooth association. CellSpin's contrary position in the sibling IPRs — that the art taught unpaired connections (Mashita, Onishi, Hiraishi; the AIRcable manual's "does not require pairing or bonding") — is a distinction of those specific references, not of the Bluetooth specification itself, and does not defeat a combination that expressly selects the paired/authenticated mode the spec defines.

Assessment: Strong. This ground mirrors the combination the Board already found sufficient to institute against the closely related '381 patent.

Ground B — Ground A further in view of Kalajan (or HTTP/1.1, appended as an alternative to Kahn's HTTP teaching)

Use this as a backstop if CellSpin argues (as it did for the '766/'767 siblings) that Kahn's media transfer runs over "WMPP" rather than HTTP and that HTTP in Kahn appears only in the location-API context.

Why it closes the gap. Kahn itself teaches HTTP between the phone and the image management server (the Board found, "for purposes of institution," that Petitioner adequately demonstrated Kahn teaches/suggests HTTP for images and the authentication credential, calling Patent Owner's reading "too narrow"). Independently, Kalajan (7,639,943) at 5:49–56 describes using HTTP to send images from a phone to a server, and the HTTP/1.1 RFC 2616 reference (1999) establishes HTTP's conventional use for web-server communication. A POSITA looking to publish to a web-based "user media publishing website" would have had every reason to use the protocol of the web. Motivation: the destination is a web server; HTTP is the protocol browsers and web servers speak; interoperability with existing web infrastructure follows as a predictable result.

Assessment: Strong. This cures the single element (HTTP) that generated the most argument in the siblings.

Ground C — Ground A/B in view of a phone-side image-management UI reference (Margalit, Montulli, Hunter, or MobShare) for the touch-based GUI

The gap: the touch-based GUI for the received file with input to delete the file and select the publishing website (claim 1/11; claim 4 keeps only the website-selection input).

Why it is obvious:

1. Kahn already discloses a user interface for the image-management service, including a "My Pictures" view and an "Account Info" tab, and a user profile used to drive the service; selecting a destination/account and managing one's own images are inherent in Kahn's system.
2. MobShare (2004) is directed to controlled and immediate sharing of mobile images — i.e., choosing where mobile images go and managing what is shared.
3. Margalit / Montulli / Hunter disclose camera/phone image handling and sharing UI flows that a POSITA would consult for the presentation layer.
4. By 2007 touch-based image galleries with a delete affordance and a "share/send to" chooser were ubiquitous on camera phones and PDAs; the '806 specification itself treats the GUI as an ordinary J2ME-rendered element.

Deleting a local copy and choosing an upload destination are non-technical, routine design choices that a POSITA would implement for any image-viewing application; KSR expressly credits such predictable design choices and market demand as motivations. The claim recites no particular gesture, no particular visual arrangement, and no algorithmic content for either input—so the GUI limitations add nothing that is not the predictable application of a conventional interface to Kahn's system.

Assessment: Moderate-to-strong. This is the element most vulnerable to a "the art doesn't expressly show a touch GUI with delete/select" argument; in the sibling cases the Board and the courts treated GUI limitations of this kind as weak. But this is where CellSpin's best (if narrow) non-obviousness argument lives — see § 6.

Ground D — Aaltonen in view of Drescher

The petitioner in the family IPRs asserted that claims of the '757 sibling are "obvious over Aaltonen in view of Drescher." Aaltonen (Bluetooth device discovery/connection) supplies the paired short-range link; Drescher supplies the media transfer/handling. Use this as an alternative structural ground for the camera-side elements (A–F), combined with Kahn/Kalajan for the publishing/HTTP elements (G).

Assessment: Moderate. Secondary/backup ground; depends on mapping Drescher to the media-creation-and-storage steps.

Ground E — Mashita + Onishi + Hiraishi (and/or the Singh906/Singh129 combination)

• Mashita/Onishi/Hiraishi: In IPR2019, CellSpin successfully argued these teach unpaired connections and thus do not render the paired claims obvious. As applied to the '806, this combination is weak on limitation B unless you add the Bluetooth 2.1 specification or Feinberg to supply pairing/authentication. Used alone, expect it to fail on the pairing/authentication element — exactly as CellSpin argued.
• Singh906 + Singh129: TikTok's Ground 1 for the '766 sibling ("a POSITA would have been motivated to add user authentication and HTTP transfer capabilities"). Caution: these are the patentee's own family publications (2008/2009). They are § 103 art only if the '806 claims are denied the Dec. 2007 priority — a contested point. Cite them only as a fallback tied to the priority challenge.

Assessment: Weak standing alone; usable only as supplements.

5. Dependent claims

Because each dependent claim adds a conventional, well-documented feature, the dependent claims rise or fall with the independents.

6. The honest counterpoints (what a patent owner will argue)

1. "Paired" vs. "unpaired." CellSpin's central family argument — that the cited camera-phone art teaches unpaired connections and therefore fails the paired/authenticated limitations — is the argument that succeeded at the preliminary stage in some sibling proceedings (Mashita/Onishi/Hiraishi) and that the CAFC ultimately credited at the pleadings stage under § 101 (Cellspin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306 (Fed. Cir. 2019), accepting as true the allegation that a "two-step, two-device structure" requiring a paired connection before transmission was unconventional). For § 103, however, the Bluetooth 2.1 Core Specification directly supplies the paired, cryptographically authenticated, association-model link — so the pairing element is met by the specification-of-record art rather than by references that disclose only unpaired operation.
2. Order/timing. The claims require capture after pairing and the file to pre-exist the transfer request. Hiroishi's capture-then-transfer flow and Kahn's upload-on-demand flow satisfy this ordering without inventing anything new.
3. Secondary considerations. CellSpin has asserted commercial/awards evidence (e.g., a 2008 Silicon India "Top Mobile Application Award," and the claim in its USPTO submission that YouTube/Flickr adopted HTTP mobile upload only "in or around 2009"). To carry weight, any such evidence must have a nexus to the specific claim elements — particularly to the camera-side authentication and the touch GUI — not merely to the general idea of camera→phone→website publishing. CellSpin's own framing ("not until many years after Cellspin's '698 Patent was filed") is a long-felt-need argument; it is countered by the fact that every structural element (Kahn's camera-phone-web-server HTTP flow; Hiroishi's in-camera Bluetooth; the Bluetooth spec's authenticated pairing) was in the art before the critical date.

7. Bottom line

• Primary § 103 combination: Kahn (U.S. 2004/0004737) + Hiroishi (JP 2003‑60953) + Bluetooth 2.1 + EDR Core Specification (optionally + Feinberg, U.S. 2007/0073937), and further in view of Kalajan (U.S. 7,639,943) and a phone-side image-UI reference (Margalit, Montulli, Hunter, or MobShare) for the touch GUI. On this record, each element of independent claims 1, 4, 7, and 11 is disclosed or would have been an obvious, predictable design choice, with a motivation rooted in the references themselves, the protocol specifications, and the nature of the problem (a network-less camera must hand media to a network-capable phone that then publishes to a web destination).
• Backstop combination: the same ground with Kalajan/HTTP‑1.1 substituted for Kahn's HTTP teaching, in case the WMPP-vs-HTTP dispute re-emerges.
• Weakest link: the touch-based GUI with delete + destination-selection (Ground C). That is where a genuine (if narrow) non-obviousness argument can be lodged, and it should be addressed with a UI reference or with the routine-design-choice rationale rather than left unmapped.
• Not to be relied on: Mashita/Onishi/Hiraishi alone (teach unpaired links — this is the exact deficiency CellSpin has successfully exploited), and Singh906/Singh129 (the patentee's own family publications; prior art only if the 2007 priority is denied).

Confidence / verification notes. (i) The reference numbers for Kahn (2004/0004737), Hiroishi (JP 2003‑60953), Feinberg (2007/0073937), and Kalajan (7,639,943) are taken from the PTAB exhibit lists and institution decisions quoted above; I reproduced them literally and did not normalize them. (ii) Kahn's teaching of HTTP for the image upload was disputed by CellSpin and found adequate "for purposes of institution" only — it is not a final merits finding, and a merits decision may differ. (iii) Kalajan's applicability depends on a pre‑Dec‑2007 filing date, which I did not independently verify. (iv) The effective priority date (Dec. 8 vs. Dec. 27 vs. Dec. 28, 2007) remains an open factual question flagged in the earlier sections; it controls whether the 2008–2009 Singh publications are available as art. (v) This is a technical obviousness assessment, not a legal opinion, and no claim construction is adopted beyond plain meaning.