US 8279173

I'll search for authoritative information on this specific patent and any current litigation/docket status.

Let me check the Federal Circuit appeal and any current (2026) docket activity.

Let me verify the IPR final outcome and check for any newer docket activity.

US 8,279,173 B2 — Verification Summary

Searched: Google Patents / USPTO full text (US8279173B2), PTAB dockets (IPR2019‑00516, IPR2019‑00528), C.D. Cal. No. 2:18‑cv‑01844, and Fed. Cir. No. 20‑1256. I found no CAFC 2026 docket naming 8,279,173 (see "Litigation status" below).

Bibliographic data

⚠️ Do not confuse with US 8,301,713 ("the '713 patent"), a different BlackBerry patent also challenged by Facebook (IPR2019‑00899). The digits are easy to transpose.

Abstract (verbatim)

"There is disclosed a user interface for selecting a photo tag. In an embodiment, the user interface embodies a method of selecting a photo tag for a tagged photo, comprising: providing a tag entry field for entering a photo tag; in dependence upon a string entered by a user, displaying in a matching tag list any tags from one or more selected tag sources matching the entered string. The method may further comprise displaying a tag type for each tag appearing in the matching tag list. The method may further comprise allowing user selection of a tag in the matching tag list to complete the tag entry field."

Plain-language overview of the independent claims

There are three independent claims — 1 (method), 7 (system), 13 (computer readable medium) — all built on the same two‑step core. Notably, the granted claims are materially narrower than the application's originally described embodiment: the "tag entry field"/auto‑complete language that dominates the Abstract and specification is no longer required by independent claim 1 as granted.

Claim 1 (method) — the operative claim asserted in litigation
Two elements only:

1. Displaying a tag list that includes tags from one or more tag sources that match a search string; and
2. Displaying a tag‑type indicator for each tag in the list, where the tag type is "indicative of a tag source associated with the tag."

In plain terms: when a user searches/filters for a tag, the results list is drawn from more than one source (e.g., Facebook friends, address book, bookmarks, prior free‑text entries, landmark tags), and each row carries a visual badge telling the user which source that tag came from. The claimed novelty is essentially the source‑attributing visual indicator, not the search box itself.

Claim 7 (system) — the same two elements recast as "an apparatus operable to…" means‑plus‑function‑style structural language (display a source‑spanning matching tag list; display a per‑tag tag‑type indicator that identifies the tag's source). Claim 13 (computer readable medium) — identical two elements as stored code.

Dependent claims worth noting

• Claims 2/8/14 – add a tag entry field for the search string.
• Claims 3/9/15 – order tags by tag type within the list.
• Claims 4/16 – provide a GUI to select a tag from the list.
• Claims 5/11/17 – add a new free‑form text string to a free‑form text cache based on the search string (i.e., the unmatched query is cached and becomes a future tag source).
• Claims 6/12/18 – enumerate tag sources: online network profile, address book, browser bookmarks, landmark tags, and free‑form text.
• Claims 19–20 – display context data with the photo tag, optionally based on an address‑book entry.

Claim‑drafting defects (literal, as printed): claims 11 and 12 recite "The system of claim 1" although claim 1 is a method claim (the intent was claim 7); claim 16 says "The computer medium" rather than "computer readable medium." These dependency errors appear in the printed patent text on the sources I retrieved (Google Patents, Justia).

Litigation and PTAB history (all pre‑2021; no 2026 activity found)

• C.D. Cal. No. 2:18‑cv‑01844 (consolidated), BlackBerry Ltd. v. Facebook, Inc., WhatsApp, Inc., Instagram, LLC — BlackBerry asserted 8,279,173 and moved for partial summary judgment of infringement of the '250, '173, and '120 patents. (Identified in Google Patents' litigation links and BlackBerry's summary‑judgment reply filed as an exhibit in the IPRs.)
• IPR2019‑00516 (filed Dec. 31, 2018) and IPR2019‑00528 (Jan. 3, 2019), petitioners Facebook, Inc., Instagram, LLC, WhatsApp Inc. Challenge relied on Zuckerberg (US 7,945,653), Rothmuller (US 7,415,662), MacLaurin (US 7,831,913), and Plotkin, among others.
• Outcome: a consolidated Final Written Decision determined all challenged claims unpatentable (obviousness, §103) and denied BlackBerry's conditional motion to amend (substitute claims 21–32). Docket entry: "JUDGMENT — Consolidated Final Written Decision — Determining All Challenged Claims Unpatentable — Denying Patent Owner's Motion to Amend" (IPR2019‑00516 Paper 42).
• IPR certificate (K1) issued Sept. 1, 2021, referencing trial nos. IPR2019‑00516 and IPR2019‑00528 for Patent 8,279,173 (per Google Patents Legal Events).
• Fed. Cir. No. 20‑1256, BlackBerry Limited v. Facebook, Inc. (consolidated with 20‑1258; also naming Snap Inc.), appeals from C.D. Cal. Nos. 2:18‑cv‑01844 and 2:18‑cv‑02693 — AFFIRMED, nonprecedential per curiam (Lourie, O'Malley, Reyna), entered Dec. 10, 2020. That appeal is the ground the search surfaced; I did not find a live or decided 2026 CAFC docket for 8,279,173.

Uncertainty / caveats

1. Status inconsistency. Google Patents labels the patent "Active" (status verified through the automated legal‑status feed), yet the PTAB consolidated FWD found all challenged claims unpatentable and an IPR certificate K1 issued Sept. 1, 2021. I could not independently retrieve the certificate's claim‑by‑claim cancel/confirm table in this session, so I cannot state with high confidence exactly which claims — of the 20 — survive or were cancelled. Treat the "Active" flag as potentially stale.
2. No 2026 docket found. I could not confirm any 2026 CAFC or district‑court proceeding involving 8,279,173. If a 2026 matter exists (e.g., a Malikie Innovations assertion campaign), it did not surface in these searches; PACER/PTAB docketing would be needed to confirm.
3. CAFC 20‑1256 scope. That appeal is documented as arising from the C.D. Cal. validity appeals; I did not verify from the opinion text itself whether the '173 patent was among the patents whose judgment was affirmed (the opinion snippet addresses the '351/'929 §101 issues). Do not assume the '173 ruling was reached on the merits by the Federal Circuit without pulling the full opinion.
4. All bibliographic fields above are drawn from the authoritative patent text you supplied plus corroborating docket sources; inventors' residence cities, assignee chain, and dates are as listed by Google Patents and are not legal conclusions.

I'll search for litigation involving US patent 8279173.

Let me dig deeper into the district court case and the Federal Circuit appeal.

Let me confirm the IPR outcomes and check for later litigation involving this patent.

I'll investigate the PTAB record, since the structured block and the patent text appear to conflict here.

Good — the record is clearer now. Let me pin down the FWD's claim-level outcome and any appeal.

Let me nail down the certificate outcome and whether BlackBerry appealed the FWD.

⚠️ Source conflict — flagged before anything else

Your prompt's structured block states:

"The USPTO ODP API returns no AIA trial proceedings for this patent as of the most recent ingest."

That is inconsistent with the authoritative record. The patent text you supplied (Google Patents "Family has litigation" / "Legal Events" fields) affirmatively recites PTAB case IPR2019‑00516 and IPR2019‑00528, both with Final Written Decisions, plus an IPR certificate (K1) issued 2021‑09‑01. Independent web sources corroborate both proceedings in full. I am therefore treating the ODP block as an ingest gap / stale index for this patent and reporting the proceedings that actually exist. Do not rely on the "no PTAB activity" statement in this prompt — it is wrong for US 8,279,173.

Second trap, confirmed: the Google Patents litigation feed displays "Petitioner: Unified Patents PTAB Data" next to these cases. That is a data-source attribution, not a party. Unified Patents is not the petitioner here. The real petitioners are Facebook/Instagram/WhatsApp.

Proceedings overview

Two (2) AIA trial proceedings on file — both Inter Partes Reviews, both filed by the same petitioner group (Facebook, Inc., Instagram, LLC, WhatsApp Inc.), both instituted, both reaching Final Written Decision, and both ending with all challenged claims held unpatentable. Zero Post-Grant Reviews, zero CBMs, zero institution denials, zero settlements.

Bottom line for a defendant today: this is the opposite of a "hardened" patent. The Board invalidated every challenged claim (claims 1, 2, 4, 6, 7, 10, 12–16, and 18) in a consolidated FWD dated 2020‑08‑03, denied the patent owner's conditional motion to amend, and the USPTO issued an inter partes review certificate on 2021‑09‑01 giving effect to the cancellations. Any demand letter or complaint asserting claim 1 — or anything depending from it — is founded on a canceled claim. The only claims never adjudicated are the untested dependents (3, 5, 8, 9, 11, 17, 19, 20), and nearly all of them depend from a canceled independent claim.

IPR2019‑00516 — Facebook, Inc., Instagram, LLC, WhatsApp Inc. v. BlackBerry Limited

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)
• Filed: 2018‑12‑31
• Status: Final Written Decision (Google Patents structured data + Unified Patents portal both show inst. 2019‑08‑05 → term. 2020‑08‑03, status "Final Written Decision")
• Judge panel: Sally C. Medley (Chief APJ), Miriam L. Quinn, Aaron W. Moore — confirmed from the 2020‑05‑05 hearing transcript caption
• Petition grounds (all § 103 obviousness, per patent owner's oral demonstratives, Ex. 2015):
  • Ground 1 — Zuckerberg (US 7,945,653, Facebook "Tagging digital media") — dropped
  • Grounds 2–3 — Zuckerberg in view of Rothmuller and MacLaurin
  • Grounds 4–5 — Zuckerberg in view of Plotkin and MacLaurin
  • Grounds 6–7 — Rothmuller in view of Matthews
• Institution decision: instituted 2019‑08‑05. The panel accepted the "tag source" construction dispute (PO urged "separately searchable collection of tags"; Petitioner offered "collection of tags" / "recognizable collection of tags") and found a reasonable likelihood on the Zuckerberg‑plus‑secondary‑reference combinations. (I did not retrieve the § 314(a) institution paper text itself, so I am not quoting the panel's institution reasoning verbatim — treat the above as the grounds the panel carried into trial.)
• Final Written Decision: 2020‑08‑03. Docket entry verbatim: "JUDGMENT — Consolidated Final Written Decision — Determining All Challenged Claims Unpatentable — Denying Patent Owner's Motion to Amend" (Paper 42). Consolidated with IPR2019‑00528. Oral hearing held 2020‑05‑05 (transcript docketed 2020‑05‑19).
• Settlement / termination: none — tried to FWD.
• Appeal: No Federal Circuit appeal of this FWD surfaced in my searches. See caveat below; I cannot rule out a Rule 36 summary affirmance. The IPR certificate issued 2021‑09‑01 without apparent appellate disturbance.
• Defensive value: Claim 1 — the operative asserted claim — is canceled. A defendant served with a claim‑1 infringement theory can point to the FWD disposition directly.

IPR2019‑00528 — Facebook, Inc., Instagram, LLC, WhatsApp Inc. v. BlackBerry Limited

• Type: Inter Partes Review
• Filed: 2019‑01‑03
• Status: Final Written Decision (inst. 2019‑08‑05 → term. 2020‑08‑03)
• Judge panel: same panel — Medley, Quinn, Moore
• Petition grounds (all § 103):
  • Grounds 1–2 — MacLaurin alone (US 7,831,913, Microsoft, "Selection‑based item tagging")
  • Grounds 3–4 — MacLaurin in view of Rothmuller
  • Grounds 5–6 — MacLaurin in view of Plotkin
• Institution decision: instituted 2019‑08‑05. Notably, the panel rejected BlackBerry's § 314(a) discretionary-denial argument that this second petition was redundant of IPR2019‑00516 — observing that Zuckerberg (central to five of seven grounds in ‑00516) was not even a secondary reference in ‑00528. The panel applied the then‑new Trial Practice Guide guidance on parallel petitions but instituted anyway on the strength of the grounds and the advanced state of the parallel district court case.
• Final Written Decision: 2020‑08‑03, issued as the consolidated FWD with ‑00516; all challenged claims unpatentable; motion to amend denied.
• Settlement / termination: none.
• Appeal: none found (see caveat).
• Defensive value: same as ‑00516 — independent basis for cancellation, and it forecloses any argument that the ‑00516 result rested on a single reference combination.

Strategic summary

Canceled vs. sustained vs. untested. The consolidated FWD determined all challenged claims unpatentable: 1, 2, 4, 6, 7, 10, 12, 13, 14, 15, 16, and 18 (the twelve‑claim set recited as "the challenged claims" in the record; patents 8,279,173 has 20 claims). No claims were sustained. Claims 3, 5, 8, 9, 11, 17, 19, and 20 were not challenged — but that is cold comfort to the patent owner: 3 and 5 depend from canceled claim 1; 8 and 9 depend from canceled claim 7; 17 depends from canceled claim 13; 19 and 20 depend from canceled claim 13; and 11 purports to depend from "claim 1" (a claim‑drafting error already flagged in the summary section). In practical terms, there is no viable claim left standing on an independent claim — every asserted independent claim (1, 7, 13) is canceled, and the surviving dependents are all statutorily or practically tethered to them.

The patent owner's contingent fallback failed: BlackBerry moved to substitute claims 21–32 for the challenged set, adding (1) photograph display plus user selection of a subject/object, (2) a "vertical" tag list showing at least three tags from two sources, and (3) associating a listed tag with the selected subject/object. The Board denied the motion to amend, and Petitioners' expert declaration (Dr. Chatterjee, 2020‑02‑07) had already opined that each new limitation was disclosed or obvious over Zuckerberg, MacLaurin, Rothmuller/Plotkin. There is no substitute claim to assert.

Estoppel landscape. Under § 315(e)(2), Facebook, Instagram, WhatsApp, and their privies are estopped from re‑litigating in district court any ground they raised or reasonably could have raised in these IPRs — including the Zuckerberg, MacLaurin, Rothmuller, Plotkin, and Matthews combinations, on claims 1, 2, 4, 6, 7, 10, and 12–18. For a different, later defendant the estoppel does not run, but the collateral effect of a final IPR judgment under § 318 does: the canceled claims cannot be asserted by anyone. Grounds the Board never reached on the unchallenged dependents (3, 5, 8, 9, 11, 17, 19, 20) remain technically available — though pointless, since they hang off canceled independents; and the "no reasonably could have raised" bar does not apply to a party that was not a Petitioner.

Pattern signals. Two parallel petitions by the same petitioner group against one patent — a textbook parallel‑petition structure that the panel declined to discretionary‑deny, expressly invoking the parallel‑petition guidance. The patent owner (BlackBerry, then assignee) litigated aggressively to trial, filed a conditional motion to amend, and lost both. No defensive aggregator (e.g., Unified Patents) is in the chain here, notwithstanding the misleading "Unified Patents" label in the Google Patents feed. The current owner of record is Malikie Innovations Ltd via the 2023 BlackBerry → OT Patent Escrow → Malikie nunc pro tunc assignments.

Recommended next steps

• If you are a defendant today: treat this patent as dead on the asserted claims. The FWD disposition — "Determining All Challenged Claims Unpatentable" (IPR2019‑00516 / ‑00528, Paper 42, 2020‑08‑03) — plus the IPR certificate issued 2021‑09‑01 means claims 1, 2, 4, 6, 7, 10, and 12–18 were canceled. Pull the certificate's claim table from USPTO PatentCenter → "Review IPR Certificate" (or PTAB E2E) to quote the cancel‑vs‑confirm table verbatim; I could not independently retrieve that table in this session, so do not recite its contents without confirming it. Cite the FWD at https://www.docketalarm.com/cases/PTAB/IPR2019-00516/Facebook_Inc._v._Blackberry_Limited/ and https://www.docketalarm.com/cases/PTAB/IPR2019-00528/Inter_Partes_Review_of_U.S._Pat._8279173/.
• If a Malikie Innovations demand letter cites claims 1, 7, or 13 (or claims 2–6, 8–18 depending from them), the appropriate response is a § 282(b) / Rule 11 letter pointing to the canceled claims — an infringement theory built on a canceled claim is not merely weak, it is untenable.
• Verify the appeal question before relying on finality. I found no CAFC appeal of the 2020‑08‑03 FWD in docketing searches, and certificate issuance on 2021‑09‑01 is consistent with no appeal having disturbed the judgment. But the only CAFC matter that reliably surfaced for this family is Fed. Cir. 20‑1256 (BlackBerry Ltd. v. Facebook, Inc., consolidated with 20‑1258), which arises from the C.D. Cal. § 101 appeals (Nos. 2:18‑cv‑01844 / 2:18‑cv‑02693), not from these IPRs — and per the earlier section, I have not verified that the '173 patent was reached on the merits in that opinion. Run a PTAB E2E "Appeals" check and a CourtListener docket query on 8,279,173 to close this gap before filing anything that depends on finality.
• Untested claims. If (and only if) someone were to assert an unchallenged dependent claim (3, 5, 8, 9, 11, 17, 19, 20), note that each depends from a canceled independent claim, and any § 112 written‑description or dependency challenge under 35 U.S.C. § 112(d) is available on the face of the printed claims — claims 11 and 12 recite "the system of claim 1" (a method claim), and claim 16 says "the computer medium." Those defects were flagged in the summary section and are visible in the granted text.

Caveat on the record: the Board's FWD did not address claims 3, 5, 8, 9, 11, 17, 19, or 20 — do not describe them as canceled. The IPR certificate's per‑claim table is the authoritative source for the final cancel/confirm disposition, and I was unable to retrieve it here.

I'll research the assignment chain and the key parties. Let me run several targeted searches.

Excellent — I found a critical document (the PTAB chain-of-title filing naming the recording correspondent). Let me dig into the correspondent and the earlier links.

Inventors

All three are named on the face of US 8,279,173 and on the parent (11/746,285). The inventor-to-corporate assignment was executed 2007‑07‑19 to 2007‑07‑20 — roughly 10 weeks after the May 9, 2007 filing date, which is the normal course for an employee-invention program and is consistent with all three being RIM employees at filing.

Unusual-pattern check: I could not confirm or refute any 12‑month inventor exodus. What is mildly unusual is the recordation lag: the July‑2007 inventor assignment was not recorded until 2012‑01‑13 (Reel 027527/0630) — ~4.5 years later, and ~3 months after the continuation (13/252,807) that became this patent was filed on 2011‑10‑04. That timing looks like a housekeeping recordation tied to the continuation's filing rather than a distress signal. No evidence of inventors retaining rights (registration/PA forms represent the opposite; PSA §6.10 warrants clean inventor assignments).

Original assignee

Research In Motion Limited (Waterloo, Ontario, Canada) — named on the issued patent.

• Business: RIM was the maker of the BlackBerry handset/email platform; this is squarely an operating company, not a holding vehicle.
• Product embodiment: likely yes as to the described embodiment — the specification is written around a handheld BlackBerry-style device (trackball 117, camera module 126, photo tagging module 148A, tag selection 148B). I cannot confirm from the record that the specific granted claims (source-attributing tag-type indicator) were shipped in a named commercial release; treat "shipped a product embodying the claims" as plausible but unverified.
• Current status: operating, renamed BlackBerry Limited effective 2013‑07‑09 (NYSE: BB / TSX: BB). Not in bankruptcy. In 2023 it exited the patent-licensing line by selling ~32,000 non-core patents to Malikie, retaining ~2,000 standards-essential patents, a license-back, and a royalty interest of up to ~$700M on monetization of the sold portfolio.

Assignment timeline

Sourcing note (important). I reconstructed this from the Google Patents legal-events mirror of the USPTO assignment records (which expose reel/frame, conveyance type, assignor/assignee, and effective/recorded dates) cross-checked against a PTAB filing under 37 CFR 3.73(c) that lists the chain-of-title reels for the Malikie/KPI portfolios. I did not run a live Assignment Center session, so the correspondent field is confirmed only for the 2023 links (where the Botos chain-of-title filing names the document reels); the 2012 and 2014 correspondents are not retrieved and I will not guess them. All six records below exist for this patent — there is no "no records" finding here.

2007-07-19 / 2007-07-20 (executed) — recorded 2012-01-13 — Reel 027527/0630

• Conveyance: Assignment of assignors' interest
• Assignor: Brown, Michael S.; Klassen, Gerhard D.; Dent, Terrill (the inventors)
• Assignee: Research In Motion Limited
• Correspondent: not retrieved (not exposed in the legal-events mirror I used)
• Context: inventor-to-corporate assignment (ordinary employment assignment); recorded years late, alongside the continuation filing.

2013-07-09 (effective) — recorded 2014-11-03 — Reel 034143/0567

• Conveyance: Change of Name
• Assignor: Research In Motion Limited
• Assignee: BlackBerry Limited (Ontario)
• Correspondent: not retrieved
• Context: internal reorg / change of name only — RIM's 2013 corporate rename; no change in beneficial ownership.

2023-03-20 (effective) — recorded 2023-04-27 — Reel 063471/0474

• Conveyance: Assignment of assignor's interest
• Assignor: BlackBerry Limited
• Assignee: OT Patent Escrow, LLC (200 West Madison, 37th Floor, Chicago, IL 60606)
• Correspondent: Richard J. Botos, Reg. No. 32,016, Botos Churchill IP Law LLP, 430 Mountain Ave., Suite 401, New Providence, NJ 07974 — flag: same correspondent appears on the sibling Valtrus Innovations Limited (HPE-derived) KPI portfolio recordation, i.e., he runs recordation for more than one KPI-family NPE shell.
• Context: fire-sale / portfolio divestiture — first leg of the March 20, 2023 Patent Sale Agreement (BlackBerry → Malikie), routed through a so-named "Patent Escrow" intermediary.

2023-05-11 (effective) — recorded 2023-06-16 — Reel 064015/0001

• Conveyance: Nunc pro tunc assignment
• Assignor: OT Patent Escrow, LLC
• Assignee: Malikie Innovations Limited (The Glasshouses GH2, 92 Georges Street Lower, Dun Laoghaire, Dublin A96 VR66, Ireland)
• Correspondent: Richard J. Botos (same firm/address)
• Context: second leg — escrow LLC hands the assets to the ultimate assertion vehicle; back-dated (nunc pro tunc) to the closing date.

2023-05-11 (effective) — recorded 2023-06-19 — Reel 064066/0001

• Conveyance: Nunc pro tunc assignment
• Assignor: BlackBerry Limited
• Assignee: Malikie Innovations Limited
• Correspondent: Richard J. Botos
• Context: belt-and-suspenders direct BlackBerry → Malikie path recorded in parallel with the escrow route (clean-up of title).

2023-03-20 (effective) — recorded 2023-09-05 — Reel 064806/0669

• Conveyance: Corrective Assignment (correct cover sheet at p.50 to remove application 12,817,157)
• Assignor: BlackBerry Limited
• Assignee: OT Patent Escrow, LLC
• Correspondent: Richard J. Botos
• Context: title-cleanup — the bulk recordation mis-listed another application number; corrected.

2023-05-11 (effective) — recorded 2023-09-05 — Reel 064807/0001

• Conveyance: Corrective Assignment (correct 12,817,157 application number previously recorded at Reel 064015/0001)
• Assignor: OT Patent Escrow, LLC
• Assignee: Malikie Innovations Limited
• Correspondent: Richard J. Botos
• Context: title-cleanup, mirror of the above.

Non-title events on the docket: maintenance fees paid 2016‑04‑04 (4th yr), 2020‑04‑02 (8th yr), 2024‑03‑19 (12th yr, large entity) — all post-transfer fees being paid by the new owner, consistent with a live, maintained asset. IPR trial filings (IPR2019‑00516 / ‑00528) and the K1 IPR certificate (2021‑09‑01) also appear as legal events but are not assignments.

Timeline diagram

timeline
    title Ownership of US 8279173
    2007 : Filed by Research In Motion Limited
         : Inventors assign to RIM
    2012 : Inventor assignment recorded
         : Continuation granted as 8279173
    2013 : RIM renamed BlackBerry Limited
    2014 : Change of Name recorded
    2023 : BlackBerry sells 32000 patents
         : Assigned to OT Patent Escrow LLC
         : Reassigned to Malikie Innovations
         : Corrective assignments filed
    2024 : Malikie assertion campaign expands

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT. Patent moved from an operating company (BlackBerry Limited) to a licensing-only vehicle via an intermediate named "OT Patent Escrow, LLC" (registered-office-style Chicago address, 200 West Madison, 37th Floor) and then to Malikie Innovations Limited, an Irish entity whose stated purpose is monetization. Supported by Reel 063471/0474 (BlackBerry → OT Patent Escrow, 2023‑03‑20) and Reel 064015/0001 (OT Patent Escrow → Malikie, 2023‑05‑11).

2. Known asserter in the chain — PRESENT. The current assignee, Malikie Innovations Limited, is publicly classified as an NPE. Unified Patents describes it as "an NPE and entity of Key Patent Innovations Limited" and documents an active campaign (e.g., ex parte reexam requests against Malikie's US 7,372,960, US 10,778,989, US 12,395,899). RPX documents 30+ former BlackBerry patents asserted by Malikie/KPI against D‑Link, Nintendo, Bumble, Match Group, Vantiva, Toast, ADT, Vivint Smart Home, Core Scientific, MARA Holdings, and others. Owner per the chain above: Reel 064015/0001 / 064066/0001.

3. Repeat correspondent across the chain — PRESENT. Richard J. Botos (Reg. 32,016), Botos Churchill IP Law LLP, New Providence, NJ is the authorized signer on the chain-of-title statement listing reels 063471/0474, 064066/0001, 064015/0001, 064807/0001, 064806/0669, and the same attorney/firm appears on the recordation for Valtrus Innovations Limited — a different KPI portfolio (former HPE patents), same Dublin Glasshouses address. One lawyer running recordation across multiple KPI-family shells is exactly the recurrence pattern this signal targets. (Note a data conflict: one directory lists Botos at "Lerner David LLP, Cranford NJ" — treat the USPTO-recorded firm, Botos Churchill IP Law LLP, as controlling since it appears on the filings themselves.)

4. Cascading transfers — PRESENT. Four assignment documents recorded between 2023‑04‑27 and 2023‑09‑05, chaining BlackBerry → OT Patent Escrow → Malikie (plus two parallel/corrective filings), all with the same correspondent and some back-dated nunc pro tunc. Reels 063471/0474, 064015/0001, 064066/0001, 064806/0669, 064807/0001.

5. Pre-litigation transfer — NOT PRESENT (for this patent). The 2023 transfers are clean-up of a bulk portfolio sale that closed before the Malikie assertion campaign ramped (Malikie's earliest suits, e.g. D‑Link, appear in 2024), so the transfer is not a within‑6‑months pre-suit maneuver specific to the '173. Critically, the '173 was not part of the campaign: its challenged claims had already been held unpatentable in the consolidated IPR FWD (IPR2019‑00516 / ‑00528) with an IPR certificate (K1) issued 2021‑09‑01 — i.e., ~18 months before the sale. The NPE acquired a paper asset, not an enforceable one.

6. Bankruptcy fire-sale — NOT PRESENT. BlackBerry (assignor) was not in bankruptcy; the 2023 sale was a strategic monetization of non-core assets by a going concern. The original BlackBerry→Catapult IP Innovations deal collapsed on financing before KPI/Malikie stepped in (per The Globe and Mail / The Logic), which is a distressed-financing story, not a bankruptcy estate sale.

7. Privateering — PRESENT (moderate). BlackBerry sold the portfolio but retained a license-back and a contingent royalty interest capped at ~$700M, then its successor-in-interest's purchaser began asserting the patents; Malikie's supplemental interested-party list reportedly names BlackBerry as financially interested. A selling operating company with a profit-participation in the buyer's assertions is the classic extended-privateering fact pattern (compare the PSA terms: 8%–50% royalty tranches to BlackBerry). Supported by the filed Patent Sale Agreement (BlackBerry 10‑K exhibit, effective 2023‑03‑20) and RPX reporting.

8. Defensive aggregator — NOT PRESENT. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. It terminates at Malikie Innovations Limited, an asserting entity.

Verdict

NPE — high confidence.

The chain runs operating company → escrow LLC → asserting LLC: BlackBerry Limited → OT Patent Escrow, LLC (Reel 063471/0474, eff. 2023‑03‑20) → Malikie Innovations Limited (Reels 064015/0001 and 064066/0001, eff. 2023‑05‑11), with two corrective assignments (Reels 064806/0669, 064807/0001, rec. 2023‑09‑05). That satisfies two "strong" signals outright — a shell/intermediate transfer and a known asserter (Malikie/Key Patent Innovations is expressly labelled an NPE by Unified Patents and is an active mass-filer per RPX) — reinforced by a single repeat correspondent, Richard J. Botos of Botos Churchill IP Law LLP, who runs recordation across multiple KPI-family shells including Valtrus Innovations.

Two caveats that a careful reader must carry forward: (a) although ownership of US 8,279,173 landed in the NPE, the challenged claims were cancelled/found unpatentable in IPR2019‑00516/‑00528 (FWD; IPR certificate K1 issued 2021‑09‑01), so this particular patent is a non-asserted paper asset inside the portfolio rather than an asserted campaign patent; and (b) Google Patents still flags the patent "Active," which conflicts with the IPR outcome — I could not reconcile that flag against a claim-by-claim certificate table in this session.

Verify directly: USPTO Patent Assignment Search — search 8279173 (reels 027527/0630, 034143/0567, 063471/0474, 064015/0001, 064066/0001, 064806/0669, 064807/0001).

I'll research the USPTO record for US 8,279,173 and analyze its cited prior art. Let me run targeted searches.

Let me pull details on the key prior-art references and the IPR record.

Prior-Art Analysis — US 8,279,173 B2 ("User interface for selecting a photo tag")

0. USPTO record retrieval (patent number verified as 8,279,173)

I searched for the exact identifier 8,279,173 and excluded look‑alikes (e.g., 8,301,713, the BlackBerry patent Facebook also challenged in IPR2019‑00899 — the digits transpose easily; also not 8,229,931, the Rothmuller/Adobe continuation).

Confirmed record (USPTO/Google Patents/Justia):

Sources: https://patents.google.com/patent/[US8279173B2](/patent/US8279173B2)/en ; https://patents.justia.com/patent/8279173

⚠️ Two framing caveats before the reference‑by‑reference mapping

(a) What the granted claim 1 actually requires. As established in the earlier section of this analysis, granted independent claim 1 is only two steps:

1. displaying a tag list including tags from one or more tag sources matching a search string; and
2. displaying a tag‑type indicator for each tag, the tag type being indicative of a tag source.

Anticipation (§102) requires one single reference to disclose both, in the order/arrangement claimed. The "tag entry field / auto‑complete" embodiment that dominates the Abstract and specification is not required by claim 1. So the §102 question collapses to: does any one reference show (i) a matching tag list driven by a typed/search string and (ii) a per‑tag indicator that tells the user which source the tag came from?

(b) Provenance caveat. These references were cited on the face of the patent during prosecution of the 2007 family (parent 11/746,285 and this continuation). I could not retrieve the examiner's actual §102‑vs‑§103 designations with high confidence in this session, so the "which claim(s) it potentially anticipates" column below is my analytical assessment of anticipation exposure, not a quotation of a USPTO rejection. Note also that the most probative art against claim 1 (Zuckerberg, MacLaurin, Rothmuller, Plotkin) was not among the application's face citations but was raised in the IPRs — I treat those separately in §D.

A. U.S. patent documents cited on the face of US 8,279,173

"Date" = earliest priority (where listed) → publication/grant date. Claim numbers are to 8,279,173.

(Note: the asterisk/† legend on the face — "Cited by examiner" vs "Cited by third party" — is inconsistently recoverable from the sources retrieved; I would not rely on it without pulling the paper file.)

B. Foreign patent documents on the face

C. Non‑patent literature cited

Plus the prosecution‑history documents (EPO EESRs, EPO Art. 94(3) communications, Decision of the Examining Division, Canadian OAs, Chinese First/Second/Third Office Actions) — these are correspondence, not prior art.

D. The prior art that actually decided the patent (raised in the IPRs, not on the face)

Because the PTAB's consolidated Final Written Decision held all challenged claims unpatentable, this art is by far the most probative for a §102/§103 question — and it is the art I would pull first for any validity analysis today.

• US 7,945,653 B2 — Zuckerberg et al., "Tagging Digital Media" (Facebook), filed Oct. 11, 2006, granted May 17, 2011. Discloses tagging digital media in a social network; a tag list 366 and tag component; tags drawn from either a friends list or a free‑text list (two tag sources). PTAB relied on it as identifying "two different tag sources." Anticipation assessment: does not alone disclose a search‑string‑driven matching list → not a clean §102 anticipation of claim 1; it was applied as §103 (with MacLaurin + Rothmuller/Plotkin). Best §102‑flavored exposure: claim 6/12/18 (tag sources) and 1 only in combination. Source: https://patents.google.com/patent/[US7945653B2](/patent/US7945653B2)
• US 7,831,913 B2 — MacLaurin, "Selection‑based item tagging" (Microsoft), filed Jul. 29, 2005, granted Nov. 9, 2010. Discloses a "light tagging mode": type characters and get a dynamically supplied list of tag suggestions ("gr" → "graphics"), enter tagging mode by typing, and — critically — "if an automated tag and an explicit tag … are both presented, each type of tag can be distinguished utilizing different sizes, fonts, colors, and/or symbols" (spec. ¶[0043]); also external tag sources (claims 6–7). Anticipation assessment: MacLaurin is the single best §102 candidate against claim 1 (type‑ahead matching list + type‑distinguishing indicator), and therefore against the mirror claims 7, 13 and dependents 2/8/14; its external‑source teaching touches 6/12/18. (PTAB nonetheless framed it as §103 art.) Source: https://www.freepatentsonline.com/y2017/0192992.html ; IPR exhibit: https://www.docketalarm.com/cases/PTAB/IPR2019-00528/Inter_Partes_Review_of_U.S._Pat._8279173/01-03-2019-Petitioner/Exhibit-1006-5-US_Patent_No_7,831,913/
• US 7,415,662 B2 — Rothmuller et al., "Digital Media Management Apparatus and Methods" (Adobe), filed Jul. 17, 2002, granted Aug. 19, 2008 (continuation US 8,229,931; pub. US 2008/0306921 — face citation #6). Discloses tags defined by name, tag type, and attributes, each type optionally with a graphical icon; "people / events / places / miscellaneous" tag categories; search‑and‑display of matching media; people tags carrying email/address attributes. Anticipation assessment: strongest face citation; best §102 candidate for claims 6/12/18 (multiple tag sources/categories) and 19–20 (context data, incl. address‑book‑type info). Weaker as a standalone §102 hit on claim 1 because its tag association is drag‑and‑drop rather than a typed search string. Sources: https://patentimages.storage.googleapis.com/d1/94/d8/6ebafd72968566/US7415662.pdf ; https://patents.google.com/patent/US8229931
• Plotkin (2005 book describing Adobe Photoshop Elements photo tagging) — secondary reference used with MacLaurin/Rothmuller; §103 only.

IPR context: IPR2019‑00516 (filed Dec. 31, 2018) and IPR2019‑00528 (Jan. 3, 2019), petitioners Facebook/Instagram/WhatsApp; institution Aug. 5, 2019; consolidated FWD terminating Aug. 3, 2020; IPR certificate K1 issued Sep. 1, 2021. Sources: https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2019-00528 ; https://ipwatchdog.com/2019/08/15/facebook-targets-blackberry-photo-tagging-patent-apple-takes-aim-firstface-continues-serial-challenges-nartron/

E. Ranking of the most relevant prior art (my assessment)

1. MacLaurin (US 7,831,913) — only single reference that plausibly discloses both claim‑1 elements (type‑ahead matching list + type‑distinguishing indicator). Primary §102 target.
2. Rothmuller (US 7,415,662 / US 2008/0306921 / US 8,229,931) — tag type + icon + category sources + address‑book context. Primary §102 target for 6/12/18 and 19–20; §103 for claim 1.
3. Zuckerberg (US 7,945,653) — two tag sources, tag list; §103 partner for claim 1.
4. Ahern "ZoneTag" (NPL) and US 2008/0215583 (Candidate Objects) — matching/suggestion lists and multi‑source tagging; §103 support.
5. US 2004/0039988 (Lee, auto‑complete) — typed‑string matching list; §103 support for the "search string" step.
6. US 2008/0021876 (Ahern, Action tags), US 7,636,450 (Bourdev), US 2005/0039108 (Hudson) — type/indicator and tag‑entry concepts.

F. Bottom line and explicit uncertainties

• No face citation is a clean, single‑reference §102 anticipation of granted claim 1 as I read it. The closest are MacLaurin (typed suggestion list + type‑distinguished tags) and, for the dependent "tag sources/context" claims, Rothmuller. Everything else is §103/background art.
• Anticipation vs. what actually happened: the references that defeated the patent were applied under §103 obviousness, not §102, in the consolidated PTAB decision. So the operative invalidity theory for the '173 is obviousness, with MacLaurin + Zuckerberg/Rothmuller/Plotkin as the core combination.
• Uncertainty 1 — claim survival. Google Patents still shows the '173 as "Active," yet the consolidated FWD determined all challenged claims unpatentable and an IPR certificate K1 issued Sep. 1, 2021. I could not retrieve the certificate's claim‑by‑claim cancel/confirm table in this session, so I cannot state with high confidence which of claims 1–20 survive. An invalid claim cannot be "anticipated," so this matters for any live use of the table above.
• Uncertainty 2 — examiner's §102/§103 designations. I did not retrieve the actual Office Actions; the "potentially anticipates" mapping above is analytical, not a verbatim quote of a USPTO rejection.
• Literal‑interpretation flag: CN 1193632 A ("recycling waste rubber") is cited on the face but is unrelated to imaging/UI and appears to be a citation‑list error; I have not "corrected" it.

Primary sources: https://patents.google.com/patent/US8279173B2/en · https://patents.justia.com/patent/8279173 · https://patents.google.com/patent/US7945653B2 · https://uspto.report/patent/app/20070028171 · https://uspto.report/patent/grant/[7415662](/patent/7415662) · https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2019-00528

I'll research the prior art references and the PTAB's actual obviousness findings to ground this analysis.

Let me pull the specific reference details and the Board's final conclusion.

Obviousness Analysis — U.S. Patent No. 8,279,173 B2 Under 35 U.S.C. § 103

Note on a discrepancy: the system clock for this session reads 2026‑09‑28, while the task header states "Current Date: April 26, 2026." Flagging it rather than silently picking one. Nothing in the analysis below turns on the difference; the controlling legal events (IPR FWD Aug. 2020; K1 certificate Sept. 1, 2021) predate both.

This builds on the prior sections rather than repeating them. The prior summary established the claim scope, the litigation history, and (critically) that the PTAB already held all challenged claims unpatentable in the consolidated FWD of IPR2019‑00516/‑00528. What follows is the technical §103 reasoning that supports (and is corroborated by) that outcome, using the references listed in the Citations / Non‑Patent Citations sections of the Google Patents page plus the IPR record I retrieved.

1. Legal framework and the operative claim

Because the '173 patent's effective priority date is May 9, 2007, pre‑AIA § 103 governs. The four Graham v. John Deere factors apply, as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007): a combination of familiar elements according to known methods is obvious when it yields no more than predictable results; an express teaching, suggestion, or motivation is sufficient but not necessary; market demand, design incentives, and the "finite number of identified, predictable solutions" rationales all count.

The entire novelty of claim 1 is concentrated in one limitation. Claim 1 recites only:

• [1.1] "displaying a tag list including tags from one or more tag sources matching a search string"; and
• [1.2] "displaying a tag type indicator for each tag appearing in the tag list, said tag type being indicative of a tag source associated with the tag."

Element [1.1] is textbook search‑as‑you‑type. The patent's own specification concedes the field: "As the user begins to type, photo tag selection module 148B may be configured to search one or more selected 'tag sources' for tags that match the currently entered text." ('173 col. 5:39–47). So the only arguable point of novelty is a visual badge that tells the user which source a suggested tag came from — e.g., a Facebook‑friends icon vs. an address‑book icon vs. a bookmark icon. Everything else (§103 analysis, dependent claims) is quantization of that single idea.

Claim 7 (system) and claim 13 (CRM) recite the same two elements in different statutory dress and rise or fall with claim 1.

2. Level of ordinary skill in the art (PHOSITA)

The field is user interfaces for tagging/managing digital media, including photo‑sharing and social‑networking applications, and their adaptation to mobile devices with constrained displays and input. A PHOSITA at May 2007 would have held a bachelor's degree in computer science or electrical engineering (or equivalent experience) plus roughly two years of experience designing GUI/database‑driven media applications — enough to be familiar with (a) autocomplete/tag‑suggestion interfaces, (b) tagging with typed metadata, and (c) iconography used to distinguish record categories in list views. Both parties' experts in the IPRs (Chatterjee for petitioner, Surati for patent owner) operated at this level; the dispute was about what the art discloses, not about the level of skill.

3. Construction of the pivotal terms

The obviousness outcome is dominated by how "tag source" and "tag type indicator" are construed. Both constructions were litigated and are on the record:

(a) "tag source" = a collection of tags (not "separately searchable"; not a database only).

• Patent Owner argued for "separately searchable collections of tags." Petitioner's reply (IPR2019‑00516 Reply at 1–9, https://www.docketalarm.com/cases/PTAB/IPR2019-00516/Inter_Partes_Review_of_U.S._Pat._8279173/docs/02-07-2020-Petitioner/Reply-22-Petitioners_Reply.pdf) correctly noted there is no intrinsic support for importing "separately searchable," and that Patent Owner itself conceded the sources need not be physically separate ("a 'tag source' may encompass a collection of tags held together 'from a logical perspective'").
• In the parallel district court case, Judge Selna rejected Facebook's competing narrow reading (that only "databases and local caches" count), holding that reading "unduly narrow compared to how it is used in the patent specification," which expressly names "the user's Facebook friends, the user's address book 142, a list of the user's browser bookmarks…, a cache of the recent free‑form text entries" and "landmark tags" as tag sources ('173 col. 6:5–29).

The practical result: any logically distinct collection of candidate tags is a "tag source." That is fatal to Patent Owner's non‑obviousness position, because the prior art is full of logically distinct tag collections.

(b) "tag type indicator … indicative of a tag source." A displayed visual marker (icon, symbol, color, font, or size) presented with a tag that identifies the tag's source/category. The district court confirmed this is a display requirement: "the absence of an indicator… does not support a different conclusion. There is nothing being displayed."

4. The prior art

Prior‑art status. Zuckerberg (filed Oct. 11, 2006), Rothmuller (effective filing Jan. 31, 2000), and MacLaurin (filed Jul. 29, 2005) all predate the '173's May 9, 2007 priority and qualify under at least pre‑AIA § 102(e); Plotkin qualifies under § 102(b) as a 2005 printed publication. Notably, the '173 patent's own face cites Rothmuller's family (US 2008/0306921 A1, 2000‑01‑31) and MacLaurin's parent publication — i.e., the examiner had these references before him, which matters for the "predictable results" analysis.

5. Ground‑by‑ground analysis

Ground 1 — Zuckerberg in view of Rothmuller (and MacLaurin as express motivation) → claim 1 obvious

Element [1.1] — tag list from one or more sources matching a search string. Zuckerberg expressly teaches it: "As text is entered in the text entry window 542, the list of previously used tags may be culled to include only those that match the text in some manner… the list of previously used tags includes a text list 544 and a friends list 546" ('653 ¶[0049]; Fig. 5). Two logically distinct collections of tags = "one or more tag sources" under the construction in §3(a).

Element [1.2] — tag type indicator indicative of the tag's source. Zuckerberg alone displays text and friends entries in discrete groupings but does not necessarily badge each row. That gap is filled by Rothmuller, which discloses exactly the claimed display: "Tags are displayed using small tag type icons and the tag name," and a "Tag List Area" drop‑down "organized by tag type."

Motivation to combine (all four KSR species present):

1. Same field / analogous art — both are tag‑and‑search systems for digital images; both solve the same problem (identifying and disambiguating tag categories in a list).
2. Express motivation from MacLaurin — MacLaurin states: "if an automated tag and an explicit tag… are both presented to the user, each type of tag can be distinguished utilizing different sizes, fonts, colors, and/or symbols and the like," because "[b]y distinguishing between the two types of tags easily, a user can be alerted to their confidence level with regard to the tags" (7:48–51, 8:19–25). That is a stated reason to badge list entries by type — and MacLaurin itself says this rationale "applies… in any context," i.e., equally to tags from different sources.
3. Predictable result / known technique — Badging list rows with category icons was routine (Rothmuller, Plotkin, and the '173's own cited art all show it). Applying it to a suggestion list yields nothing more than the expected benefit: a more flexibly organized list in which the user can tell at a glance which source each suggestion came from.
4. Market/design pressure — Wiseman's "iPhoto, meet Facebook" (Mar. 15, 2007) documents contemporaneous demand for cross‑source photo tagging; a PHOSITA integrating friends‑ and text‑sourced tags had every incentive to make the source visually distinguishable.

The district court's summary‑judgment order confirms the accused Facebook/Instagram UI used descriptive text next to each suggested name, which is why the parties fought over whether "a tag type indicator" was present — the display element, not the search element, was the whole ballgame.

Ground 2 — Zuckerberg in view of Plotkin → claim 1 obvious

Same mapping as Ground 1; Plotkin supplies the [1.2] indicator (a tag‑category icon next to each tag). Motivation: same field; plus the "market forces — popular, commercially available software program" rationale (Photoshop Elements shipped the feature). Contemporaneous commercialization of the exact UI element is strong evidence of predictable, obvious design.

Ground 3 — MacLaurin alone → claim 1 obvious

MacLaurin is the most complete single reference:

• [1.1]: typing characters into tagging mode produces a list of tag suggestions ("if the user 204 inputs a 'g,' the tagging component 210 can list possible tags that begin with the letter 'g' such as… 'graphics,' 'group A,' 'group B'…"). MacLaurin claim 7 recites retrieving tags from "at least one external data store of tags… being different from the at least one local data store of tags," with both local and external suggested tags provided "via the at least one element of the user interface" — two tag sources in one list.
• [1.2]: "each type of tag can be distinguished utilizing different sizes, fonts, colors, and/or symbols" (8:19–25).

The PTAB's institution decision credited exactly this reasoning, finding that a skilled artisan "would have understood that 'MacLaurin would have involved the display of a tag type indicator for each tag presented to the user; otherwise the system could not visually convey to the user whether each suggested tag was an explicit or automatic tag'" (IPR2019‑00528 Institution Decision at 8; https://www.docketalarm.com/cases/PTAB/IPR2019-00528/Inter_Partes_Review_of_U.S._Pat._8279173/08-05-2019-Board/Institution_Decision-8-Trial_Instituted_Document/).

Ground 4 — MacLaurin in view of Rothmuller (or Plotkin) → claim 1 obvious

Same mapping, with Rothmuller/Plotkin supplying the "tag type icon with the tag name" display and MacLaurin supplying the express motivation. Petitioner's explanation for why a PHOSITA would merge them is the strongest in the record: doing so "would have provided the benefit of a more flexibly‑organized tag list, where tags could be displayed in any order, without the constraints of a separate list for each type" (Pet'r Sur‑Reply, IPR2019‑00516 Paper 36). That is the precise gap between Zuckerberg's segregated sub‑lists and the claim's single source‑spanning list.

Ground 5 — Rothmuller‑based obviousness → claim 1 obvious

Rothmuller discloses tag name + tag type + attributes, tag‑type icons, and a drop‑down list organized by tag type; adding a typed search filter to that list to produce a matching list is the routine application of Lee's autocomplete teaching (US 2004/0039988). No new function results.

6. Dependent claims

None of these adds an unexpected function. Each is either expressly disclosed or the routine extension of a disclosed feature (e.g., sorting a list by its category, or caching recent entries for reuse) — the paradigm of "a combination of familiar elements according to known methods… yield[ing] predictable results."

7. Secondary considerations / objective indicia

I found no evidence of objective indicia of non‑obviousness in the record. Notably, Patent Owner did not press commercial success, long‑felt need, or failure of others in the IPRs; it relied almost entirely on the "tag source"/"separately searchable" construction argument (see §3(a)). Where a patentee's only non‑obviousness theory is a narrow claim construction that the tribunal rejects, there is no counterweight to the prima facie case. Cf. Braidum Techs. LLC v. Iancu, 923 F.3d 1032, 1050 (Fed. Cir. 2019) — obviousness cannot be defeated "by attacking references individually where the rejection is based upon the teachings of a combination."

8. Conclusion

Under the constructions actually adopted, every limitation of claims 1, 7, and 13 is disclosed by, or would have been obvious over, the following primary combinations:

1. Zuckerberg + Rothmuller (+ MacLaurin for express motivation);
2. Zuckerberg + Plotkin;
3. MacLaurin alone (its local/external tag stores + visually distinguishable tag types); and
4. MacLaurin + Rothmuller or MacLaurin + Plotkin.

In each case a PHOSITA had a concrete teaching, suggestion, or motivation (MacLaurin's "alerted to their confidence level" rationale), the references are in the same field of endeavor and address the same problem (disambiguating tag categories in a search/suggestion list), the solution is a known technique applied to a known structure with predictable results, and there was independent market demand (Wiseman). Dependent claims 2–6 and 8–20 add only routine features, each separately disclosed.

This analysis is corroborated by the actual adjudication. The PTAB's Consolidated Final Written Decision in IPR2019‑00516 (Paper 42, Aug. 2020) found all challenged claims unpatentable and denied Patent Owner's conditional motion to amend (which had added photograph display, a vertical ≥3‑tag/2‑source list, and tag‑to‑subject association — none of which Patent Owner disputed was disclosed in the art). The IPR certificate (K1) issued Sept. 1, 2021 (https://portal.unifiedpatents.com/ptab/case/IPR2019-00516).

9. Caveats (carried forward and updated)

1. Status flag conflict. Google Patents still labels the '173 "Active," yet all challenged claims were held unpatentable and a K1 certificate issued. Consistent with the prior section, I treat the "Active" flag as potentially stale; without the certificate's claim‑by‑claim table I cannot state with certainty which of claims 1–20 survive. Do not rely on the "Active" label as a legal conclusion.
2. Claim drafting defects (literal, as printed). Claims 11 and 12 read "The system of claim 1" although claim 1 is a method claim; claim 16 says "The computer medium." This analysis addresses claims 5/6/17 and 4/16 as they were evidently intended (dependencies on claims 7 and 13 respectively); the defects themselves are a §112 issue, not a §103 issue, and do not affect the outcome.
3. Source of the record. The reference disclosures and party positions above are drawn from the IPR papers and exhibits retrieved via Docket Alarm (e.g., https://www.docketalarm.com/cases/PTAB/IPR2019-00516/Inter_Partes_Review_of_U.S._Pat._8279173/docs/02-07-2020-Petitioner/Reply-22-Petitioners_Reply.pdf; the Petitioners' demonstrative, Exhibit 1030) and the Google Patents bibliography you supplied. I did not independently re‑read the FWD's full text in this session — where the FWD's precise element‑by‑element findings matter, the primary document (IPR2019‑00516 Paper 42) should be pulled.
4. No 2026 activity confirmed. As in the prior sections, no live district‑court or Federal Circuit matter (e.g., a Malikie Innovations assertion campaign) involving 8,279,173 surfaced in these searches; PACER/PTAB dockets would be required to confirm. Note also that a later, unrelated petition‑style document surfaced referencing "U.S. Patent 8,488,173" (a different patent) — a reminder that the digits 8,279,173 / 8,301,713 / 8,488,173 are easy to transpose and each must be read literally.