US 7881730

I'll search for authoritative information on US 7,881,730, including any CAFC 2026 docket activity.

Let me check for litigation and any Federal Circuit activity involving this patent specifically.

Search scope and confidence

I searched for US 7,881,730 specifically (not neighboring numbers) and did not locate any Federal Circuit 2026 docket entry naming this patent. The Federal Circuit materials that surfaced for 2026 were unrelated matters (e.g., the Enanta petition for rehearing, Google v. Cellular South, No. 26-1519). I also could not confirm via the sources retrieved which district court cases actually asserted the '730 patent, even though Google Patents flags the family as having litigation. I flag both of these as unverified below rather than guessing.

The bibliographic and claim data below comes primarily from the Google Patents record (which you supplied, and which I treat as authoritative) and is corroborated by uspto.report's grant record.

Bibliographic summary — US 7,881,730 B2

Primary CPC classes: G01C 21/34, G01C 21/3415, G01C 21/367, G01C 21/30, G01S 19/42, G08G 1/202, G06Q 50/30. Primary examiner: Tuan A. Pham. Attorney/agent: William H. Bollman.

Discrepancy noted (not auto-corrected): a Unified Patents portal listing shows this patent with a "2002-04-09" date, whereas Google Patents and the patent's own cross-reference section both state the '941 provisional was filed Apr. 10, 2002. The Google Patents/patent-text value is used here.

Abstract (verbatim)

"The preferred embodiments of the present invention are directed to methods and systems for dynamic route estimation and prediction using discrete sampled location updates from various mobile devices for the purpose of providing a graphical representation of a mobile device's route along a known network path of map data. The embodiments also provide supplemental route metrics, such as traveled distance, elapsed time, etc., and the capability to assign destination points for the purpose of providing the ability to modify location update points in an application, such as a route planner, and/or to store the dynamically generated route based on various preferences for later retrieval."

Independent claims — plain-language overview

The patent has three independent claims: 1, 12, and 23, with dependent claims 2–11, 13–22, and 24 respectively (24 claims total).

Claim 1 — Method (the core claim). A method of dynamically predicting routes between an original location and a destination using a mobile communication device:

• (a) receive the device's position information;
• (b) set that received position as the "original location";
• (c) estimate the device's speed while traveling from the original location toward the destination;
• (d) generate a plurality of possible routes from origin to destination;
• (e) calculate a plurality of possible next positions along each of those possible routes;
• (f) display every one of those calculated possible next positions on the device's display;
• (g) receive an updated location of the device;
• (h) reset that updated location as the new "original location"; and
• (i) loop (c)–(h) until the updated location equals the destination.

In plain terms: while the vehicle is in motion and before the next GPS ping arrives, the system projects where it could be on every viable path, draws all of those projections, then throws away the ones the new fix rules out and re-projects from the new fix — repeating until arrival. Notably, the claim puts the display on the mobile device itself, and the "possible next positions" are the projected/predicted positions, not the raw location fixes.

Claim 12 — Computer-readable storage medium. The same (a)–(i) sequence as claim 1, recast as a program stored on a computer-readable medium that causes a processor to perform the predictive-route calculation and display the routes on a mobile communication device. It is essentially claim 1 in Beauregard form, with the same claim scope.

Claim 23 — Computer system programmed to provide predictive position information. Again the same (a)–(i) sequence, framed as a computer system programmed to execute those steps. Claim 24 (dependent) limits the computer system to being "a mobile communication device."

Key dependents worth noting:

• Claim 2 / 13: erasing from the display any possible next positions no longer on a viable route (this is the "prune the wrong branches" step described in FIG. 9).
• Claims 3–4 / 14–15: speed estimated from the posted road speed limit at the original location, or from the device's typical speed where it is attached to a vehicle.
• Claims 5–6 / 16–17: next positions computed at a predetermined time interval, which may be constant.
• Claim 7 / 18: origin, destination, next positions and routes shown on a graphical map.
• Claim 8 / 19: steps (c)–(h) performed in real time.
• Claim 9 / 20: destination settable and modifiable by the user of the mobile device.
• Claim 10 / 21: original and updated locations comprise GPS coordinates.
• Claims 11 / 22: storing the route segments between the original position and the selected next position (and onward to the updated location).

Practical observation: all three independent claims are directed to the predictive (between-updates) routing aspect, not to the estimated-route/back-office breadcrumb-reconstruction and dispatch-ranking aspects emphasized in the specification (snap-to-road, route metrics, route planner, satellite-to-central ranking of FIGs. 25–26). Those features are described but are largely absent from the granted independent claim set.

Related family (same priority, for context)

Continuations/divisionals in this family include US 7,565,155 (parent), 8,095,152; 8,577,390; 9,354,069; 9,607,346; 9,746,341; 9,921,077; 10,274,337; 10,502,583; 10,551,208; 10,677,608; 10,996,071; 11,346,684; 11,473,925; 11,619,513 — and post-grant publication US 2020/0256693 A1. Google Patents lists this family's expiration as adjusted to 2023-07-23.

Litigation / CAFC 2026 — what I could and could not verify

• No CAFC 2026 docket activity for US 7,881,730 was found. Searches for the patent number in combination with Federal Circuit / 2026 docket terms returned no matching case. I cannot state that none exists — only that my searches did not surface one.
• Google Patents flags this family with a "Family has litigation" indicator linking to a Darts-IP global litigation dataset (family 34395939), but the underlying case list was not retrievable in my searches. Treat any specific district court case number as unverified.
• Adjacent-but-not-confirmed: my searches surfaced TeleCommunication Systems, Inc. district court matters from the 2009–2013 period (e.g., TCS v. Cobra Electronics, D. Md. 1:13-cv-02174, which referenced US 8,515,414; TCS v. Escort/Beltronics, D. Md. 1:13-cv-02178; TCS v. Sybase 365; TCS v. TracBeam, D. Colo. 1:11-cv-02519, a DJ action) and TCS's 2009–2010 assignments and Silicon Valley Bank security interests. None of the retrieved documents expressly names US 7,881,730 as a patent-in-suit, so I am not attributing those cases to this patent.

Uncertainty summary

1. CAFC 2026 dockets: no result found for US 7,881,730; not confirmed either way.
2. District court assertions of the '730 patent: not confirmed from primary documents; the family's litigation flag is unattributed in my sources.
3. Assignee of record vs. current owner: Google Patents shows current assignee Bluestone Ventures Inc. (2015 assignment from TCS), while uspto.report's page (likely reflecting grant-time data) lists TeleCommunication Systems, Inc. The Bluestone assignment is the later, recorded transaction.
4. One priority-date variant (2002-04-09 vs. 2002-04-10) appears in an aggregator's metadata; the patent's own text and Google Patents both support 2002-04-10.

I'll research this systematically across patent litigation databases.

The initial searches returned other "'730" patents (e.g., Proxense's 8,352,730 and Whirlpool's 6,971,730). Let me target this specific patent and its known family/owners.

Let me dig into litigation databases and the known owner/assertion campaigns.

Summary answer

I found no litigation that specifically identifies U.S. Patent No. 7,881,730 as an asserted patent. My searches surfaced several cases involving similarly numbered "'730" patents — but those belong to different patents owned by different parties (e.g., U.S. 8,352,730 in Proxense v. Microsoft; U.S. 6,971,730 in the Whirlpool/LG dispute). Per your strict rule, I am not attributing those to 7,881,730. Within the limits of the tools available to me, I cannot report a case — number, court, parties, filing date — in which 7,881,730 is the patent-in-suit.

I want to be explicit that this is a negative finding from a bounded search, not proof that no such case exists.

What the record shows about the patent itself

Source: https://patents.google.com/patent/[US7881730B2](/patent/US7881730B2)/en

Two points worth flagging for your file:

1. The Google Patents page carries a Darts‑IP "family has litigation" indicator (family 34395939), with a link to the Darts‑IP litigation dataset. This tells us some member of the worldwide family has been litigated, but the page does not identify the asserting case, the patent member, or the parties. I could not resolve that indicator to a specific case for 7,881,730 with the tools available in this session.
2. The patent expired on 2023‑07‑23. Any infringement action would therefore have had to be filed on or before that date to capture ongoing infringement, subject to the six‑year damages lookback of 35 U.S.C. § 286.

Unified Patents' patent portal lists US‑7881730‑B2 with assignee "Bluestone Ventures Inc." (https://portal.unifiedpatents.com/patents/patent/US-7881730-B2), but no litigation entries appeared in the results returned to me.

Related cases I did find — explicitly NOT suits on 7,881,730

These are included only so you can see the neighborhood and rule them out. None of them asserts 7,881,730 based on the sources retrieved.

Search methodology and limitations (so you can calibrate reliance)

• I ran web searches against general litigation-indexed pages and CourtListener/PACER-derived dockets, targeting the literal strings "7881730" and "7,881,730" plus litigation terms.
• Limitations: (a) I could not query PACER directly or the Unified Patents litigation caselist filtered by patents=7881730 — results returned only the Unified patent page, not the case list; (b) I was cut off by a step limit before exhausting targeted queries on TCS's 2012–2013 assertion campaigns (which involved NIM/Sheha-family patents) and on any Bluestone Ventures assertion activity post‑2015; (c) Darts‑IP's "family has litigation" flag on the Google Patents page was not resolvable to a case in this session.
• A high false-positive rate is inherent here: "730" appears as the last three digits of many unrelated patents, and the retrieval engine repeatedly keyed on those.

Recommended next steps before you rely on this

1. Query the Unified Patents litigation caselist directly with the patent filter: https://portal.unifiedpatents.com/litigation/caselist?patents=7881730
2. Search PACER / CourtListener dockets for the patent number and for the assignees ("Bluestone Ventures Inc.", "Networks In Motion", "TeleCommunication Systems") across 2011–2023, focusing on E.D. Tex., D. Del., D. Md., C.D. Cal., and W.D. Tex.
3. Pull the Darts‑IP entry for family 34395939 to identify which family member(s) were litigated.
4. Check the prosecution/assignment file for the 2015 assignment to Bluestone Ventures Inc. for any related co-pending or asserted family members (the family includes US 8,095,152; 8,577,390; 9,354,069; 9,746,341; 9,921,077; 10,274,337; 10,502,583; 10,551,208; 10,677,608; 10,996,071; 11,346,684; 11,473,925; 11,619,513).

Bottom line: on the record I could retrieve, there is no confirmed litigation naming U.S. 7,881,730 as the patent-in-suit. I am not asserting that none exists — only that my searches did not identify one, and that the similarly numbered cases returned must not be treated as this patent.

I'll research this. Let me start with the structured data and verify against web sources.

Proceedings overview

No AIA trial proceedings on file. The USPTO Open Data Portal (ODP) structured feed returns zero IPR, PGR, or CBM proceedings for US 7,881,730 as of the most recent ingest, and my independent web checks (Google Patents, the Unified Patents litigation/patent portal entry for US-7881730-B2, and PTAB E2E / PTActs results) surfaced no proceeding, petition, or institution decision naming this patent — so the count is 0 active, 0 claims invalidated by PTAB, 0 settled, 0 institution denials. Bottom line for a defendant: the patent has never been tested at the PTAB, i.e., its claims are "untested," not "hardened." The more consequential defensive fact is not a PTAB outcome at all — Google Patents lists the patent as Expired – Lifetime, adjusted expiration 2023-07-23, well before today's date. An expired patent cannot support injunctive relief, and the runway for a retroactive damages case is bounded by the § 286 six‑year look‑back plus laches/limitations defenses.

Proceedings

None to report. Per the structured PTAB block supplied with this task, there are no AIA trial proceedings on US 7,881,730, and nothing found on the web contradicts that. I am not going to invent proceeding numbers, panels, or outcomes to fill this section — doing so would be worse than reporting the gap. If you have a specific petition number from a demand letter or a co‑defendant, I can verify it directly against PTAB E2E.

Two adjacent signals worth flagging honestly (not PTAB proceedings, and I could not fully verify them within my search budget):

• Litigation in the family: the Google Patents record carries the "Family has litigation" flag and a Darts‑IP family link, and the patent's chain of title runs TeleCommunication Systems, Inc. → Networks In Motion, Inc. → Bluestone Ventures Inc. (current assignee). That is a monetization/assertion posture, not a validity adjudication.
• No defensive‑aggregator IPR: nothing surfaced tying Unified Patents or a similar aggregator to this patent, even though the portal indexes the patent's basic bibliographic data. That is consistent with a patent that was never IPR'd rather than one that was quietly dispatched.

Strategic summary

Claim status — all untested. Every claim of 7,881,730 sits in the same bucket: never construed by the PTAB, never canceled, never confirmed in an AIA trial. There is no narrowed claim set to point to, no FWD to quote, and no § 315(e)(2) estoppel map to draw, because no IPR/PGR/CBM was ever instituted. The claims therefore retain whatever scope the original prosecution gave them, and the intrinsic record (2002‑04‑10 priority through the 2003‑04‑10 non‑provisional and the 2009‑06‑12 divisional filing) is the only construction anchor you have.

Estoppel landscape — wide open, but time‑barred. With no prior petitioner, nobody is estopped from anything, so in theory all prior‑art grounds (§ 102/§ 103 combinations, plus § 112 written‑description/enablement attacks) remain available in a district court or ITC forum. Practically, three constraints dominate: (1) the patent is expired (adjusted expiration 2023‑07‑23), which makes an IPR strategically pointless — you cannot get claims canceled in time to matter, and the Board has historically been reluctant to institute on patents where no amendment or SCOPE‑type relief is possible; (2) § 315(b) gives a defendant only one year from service of a complaint to file, so any IPR window likely closed long ago if this patent was asserted pre‑expiration; and (3) § 286 caps damages recovery at six years pre‑complaint, further shrinking exposure for a patent that has already lapsed.

Pattern signals. No petitioner repetition, no patent‑owner appeal history at the CAFC for this patent, and no aggregator chain — the defensible read is that this family was monetized through district‑court/ITC assertion rather than through PTAB combat, and that the patent simply ran out its term before attracting a coordinated validity challenge. The "well‑asserted patents eventually attract IPRs" heuristic cuts the other way here: the absence of IPRs, combined with the 2023 expiration, suggests the assertion campaign was either short‑lived, settled, or brought late in the term.

Recommended next steps

1. Confirm the expiration math first. Pull the patent term adjustment certificate and any terminal disclaimer from PatentCenter for US 7,881,730 (granted 2011‑02‑01; Google Patents shows adjusted expiration 2023‑07‑23). If that date holds, the strongest defensive position is not "invalidity" but "expired — no injunctive relief, six‑year damages cap, and the accused conduct must predate 2023‑07‑23."
2. If a demand letter cites this patent today, the letter is almost certainly chasing pre‑expiration conduct. Ask for the accused‑sales date range and the asserted claims in writing before doing any merits work.
3. If you still want a validity record and a live IPR window somehow exists, the absence of any prior PTAB art means you can select the best § 103 combinations with no § 325(d) baggage — but weigh that against the near‑certainty that an expired patent yields no meaningful IPR relief.
4. Monitor the family, not just this patent. The same specification/priority chain produced later continuations (e.g., US 8,095,152; US 8,577,390; US 9,354,069 in the Google Patents family listing) that are successors in the same assertion program. Those may still be within term, which is where a PTAB or invalidity defense would actually have teeth — that is where I'd spend the next research cycle.
5. Verify, don't assume. I could not run a complete PTAB E2E / PTActs docket pull before hitting my search limit. Before relying on "zero PTAB proceedings," have a paralegal confirm via PTAB E2E search on "7,881,730" and via the Darts‑IP family litigation link shown on the Google Patents page. If you send me a proceeding number or an E2E hit, I'll re‑run this analysis with full claim‑level and panel‑level detail.

I'll research this patent's assignment record and litigation/NPE history. Let me run several searches in parallel.

Let me dig deeper into the assignment records, the Bluestone entity, and TCS's corporate history.

Assignment & Ownership Analysis — US 7,881,730 B2

Data-source caveat (read first). I worked from the authoritative patent text you supplied (Google Patents, which mirrors the USPTO legal-events feed), plus Unified Patents, RPX Insight, CourtListener/PACER, FTC early-termination notices, and SEC/8-K filings on the corporate parents. Two fields you asked for are not retrievable from the sources I could reach and I will not invent them:

• Reel/frame numbers — the Google Patents legal-events view (which harvests the same Assignment Center records) strips reel/frame. I could not independently confirm reel/frame for any link. Each entry below is therefore dated and typed but marked reel/frame not retrieved.
• Recording correspondent (the attorney who filed each recording) — likewise absent from the mirror. I flag the litigation counsel of record separately, because he is the useful tell in this chain, but I have not confirmed he is the recorded assignment correspondent.

Verify reel/frame and correspondent directly at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (search patent number 7881730).

Inventors

Pattern note. All four inventors are named assignors on the same assignment to Networks In Motion, Inc. (recorded 2009-06-12), which is normal for an employee-inventor group at a single operating startup — not the "inventors departed within 12 months" fire-sale tell. The two co-founders (the Shehas) remained with the acquiring company after the 2009 TCS deal. Nothing here suggests inventor flight preceding a portfolio sale. The transfer decision was corporate (TCS), not inventor-driven.

Original assignee

Two layers, because the patent face and the record disagree in a way that matters:

• Applicant / first assignee of record: Networks In Motion, Inc., Aliso Viejo, CA — an operating company founded 2000 that shipped navigation and local-search software for mobile phones (carrier-deployed turn-by-turn/telematics products). It raised ~$17M from Mission Ventures, Redpoint Ventures and Sutter Hill Ventures, and had ~$75M revenue in 2009. It was an operating company whose products embodied the claimed subject matter.
• Assignor on the patent face ("Original Assignee: TeleCommunication Systems Inc"): TCS, a Maryland corporation (HQ Annapolis, MD), a public company (NASDAQ: TSYS) in 9-1-1 call routing, precision location and wireless data. TCS acquired NIM on 2009-12-15 for ~$170M (cash + notes + 2.24M TCS Class A shares) via a merger sub that merged into NIM, NIM surviving as a wholly-owned TCS subsidiary (TCS 8-K, 2009-12-16). The USPTO record for this was entered as a "CHANGE OF NAME" (recorded 2010-05-03), i.e. the NIM→TCS identity was papered as a name change, not an asset assignment.

Current status of the original chain. TCS was itself acquired by Comtech Telecommunications Corp. (agreement Nov 22, 2015; tender offer closed Feb 23, 2016), becoming a Comtech subsidiary. NIM/TCS therefore remain operating entities inside Comtech today. Critically, the '730 patent had already left TCS in July 2015, months before the Comtech deal was even signed.

Assignment timeline

Reminder: reel/frame not retrievable from accessible sources. Dates and conveyance types below are from the Google Patents legal-events feed (mirrors Assignment Center).

• 2009-06-12 (executed/recorded same date) — Reel not retrieved

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Arun Yarlagadda; Steven Petilli; Angie Sheha; Michael A. Sheha
  • Assignee: Networks In Motion, Inc.
  • Correspondent: not retrieved. (No recurrence determinable.)
  • Context: Ordinary inventor-to-company assignment at the operating startup on whose technology the divisional (12/484,091) was filed.

• 2010-01-29 (recorded) — Reel not retrieved

  • Conveyance: Security Agreement
  • Assignor: Longhorn Acquisition, LLC; Networks In Motion, Inc.; Quasar Acquisition, LLC; Solvern Innovations, Inc.; TeleCommunication Systems, Inc.
  • Assignee: Silicon Valley Bank, as Agent
  • Correspondent: not retrieved.
  • Context: Blanket securitization — SVB takes a lien over the TCS/NIM group IP, including '730.

• 2010-05-03 (recorded) — Reel not retrieved

  • Conveyance: Change of Name
  • Assignor: Networks In Motion, Inc.
  • Assignee: TeleCommunication Systems, Inc.
  • Correspondent: not retrieved.
  • Context: Internal reorg / entity-name cleanup after the 2009 NIM–TCS merger (NIM surviving subsidiary recorded under the TCS name).

• 2015-07-20 (recorded) — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Silicon Valley Bank, as Agent
  • Assignee: Networks In Motion, Inc.; TeleCommunication Systems, Inc.; MicroData GIS, Inc.; Olive Acquisition, LLC; NextGen Communications, Inc.; Solvern Innovations, Inc.; MicroData, LLC
  • Correspondent: not retrieved.
  • Context: SVB discharges its lien — the precondition that lets TCS convey '730 free and clear.

• 2015-07-29 (recorded) — Reel not retrieved

  • Conveyance: Assignment of Assignors' Interest ← the transfer-to-asserter
  • Assignor: TeleCommunication Systems, Inc.
  • Assignee: Bluestone Ventures Inc.
  • Correspondent: not retrieved. (Litigation counsel of record for later Bluestone campaigns is Raymond W. Mort III, The Mort Law Firm, PLLC — see below.)
  • Context: Transfer to a licensing-only entity, nine days after the SVB release; the operating company exits and an entity with no products acquires the asset.

• 2016-03-03 (recorded) — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Silicon Valley Bank
  • Assignee: Networks In Motion, Inc.; Quasar Acquisition, LLC; TeleCommunication Systems, Inc.; Solvern [sic] Innovations, Inc.; Longhorn Acquisition, LLC
  • Correspondent: not retrieved.
  • Context: Second SVB lien release across the TCS entity group; administrative cleanup, does not re-touch '730.

• 2018-11-16 (recorded) — Reel not retrieved

  • Conveyance: Security Interest
  • Assignor: Angels Acquisition Corp.; Armer Communications…; Comtech entities; MicroData GIS, Inc.; MicroData, LLC; Networks In Motion, Inc.; NextGen Communications, Inc.; Solvern Innovations, Inc.; TeleCommunication Systems, Inc.; and others
  • Assignee: Citibank, N.A.
  • Correspondent: not retrieved.
  • Context: Comtech group credit facility. Appears keyed to the assignor entities, not to '730 — Bluestone had owned the patent since 2015, so this lien should not encumber '730. Treat as a false-positive hit on the legal-events feed.

If the Assignment Center shows anything beyond the above — in particular a Bluestone→third-party transfer, a litigation-finance lien, or a re-recordation — that would change this analysis. I could not see one.

Timeline diagram

timeline
    title Ownership of US 7881730
    2002 : Priority application filed
         : Inventors assign rights to Networks In Motion
    2009 : Division filed for the 730 patent
         : Inventors assign rights to Networks In Motion
    2010 : Silicon Valley Bank takes security interest
         : Networks In Motion renamed TeleCommunication Systems
    2011 : Patent granted
    2015 : Bank lien released
         : Patent sold to Bluestone Ventures
    2021 : Bluestone sues Uber on family member
    2025 : Bluestone sues Google on seven family patents

NPE / troll-pattern signals

Verdict

NPE — high confidence.

Two strong signals stack: (a) the 2015-07-29 assignment moving '730 from operating company TeleCommunication Systems, Inc. to Bluestone Ventures Inc. — an entity with no products, classified by Unified Patents as "an NPE" — nine days after its 2015-07-20 SVB lien release; and (b) Bluestone's documented assertion behavior on this exact family, suing Uber (W.D. Tex. 6:21-cv-00685, June 2021) and Google (W.D. Tex. 7:25-cv-00569, filed 2025-12-12, asserting seven sibling patents — '341, '337, '208, '608, '071, '925, '513). No fire-sale, cascade, or defensive-aggregator facts cut the other way. Note the '730 patent itself expired 2023-07-23 (adjusted term) and is not among the patents Bluestone asserted against Google, so the residual assertion value sits in the live continuations, while '730's relevance to this analysis is the ownership pattern it records.

Verification link (Assignment Center, search "7881730"): https://assignmentcenter.uspto.gov/

I'll research US patent 7881730 and its cited prior art references.

Let me get the specific citation lists from the patent's front page.

Let me look for the patent's front-page citation lists from patent databases.

I was able to confirm the patent's identity and family, but I hit tool-call limits before retrieving the patent's front-page "References Cited" list. Here is what I can state with confidence, and what I could not verify, with no fabricated identifiers.

1. Patent identified (verified — do not auto-correct)

Family members in the same chain (verified from the Google Patents family timeline) include US 8,095,152; US 8,577,390; US 9,354,069; US 9,747,341; US 9,921,077; US 10,274,337; US 10,502,583; US 10,551,208; US 10,677,608; US 10,996,071; US 11,346,684; US 11,473,925; US 11,619,513 — all sharing the 2002-04-10 priority. Google Patents also flags "Family has litigation."

2. Important limitation on the prior-art list you asked for

I could not retrieve the authoritative "References Cited" / "Cited By" tables that appear on the printed face of US 7,881,730. The full patent text I was given contains the abstract, specification, and drawings list, but not the front-page U.S. patent documents, foreign patent documents, or non-patent references. My searches surfaced related material but not the 7,881,730 citation list itself.

Because of your strict no-fabrication rule, I will not invent patent numbers and attribute them to 7,881,730's face. Note specifically that one search hit showed an international search report listing US 6,480,783 (Myr), US 6,615,130 (Myr), US 2004/0249568 (Endo), WO 0031705 (Lang), US 6,028,553 (Oberstein), JP 2005-030873 (Nagase), and US 2003/0009277 (Fan). That ISR belongs to PCT/CA2005/000785 (WO 2006/125291), a different, unrelated application — it is NOT the citation list for US 7,881,730 and must not be treated as such.

To obtain the genuine list, the authoritative sources are:

• USPTO Patent Center / Patent Full-Text (patft) for US 7,881,730 — "References Cited" and "Referenced By."
• The file wrapper (Image File Wrapper) for application 12/484,091, which contains the examiner's PTO-892 forms.
• Google Patents or Espacenet "Citations" tabs for US7881730B2.

3. What the patent claims (from the specification, for framing the § 102 analysis)

The recurring inventive subject matter — i.e., the features a § 102 reference would have to disclose — is:

• Dynamic/predictive route generation from discrete, sampled location updates (position fixes that may arrive asynchronously at 0.5–2 Hz or at 30–60 s intervals) — see the abstract and the "predictive routing" description.
• Snapping each location fix to the nearest road segment on map data (the "circle test"/snap-to routine; Figs. 4A, 5).
• Calculating an estimated route between consecutive fixes using route preferences (driving speeds, fastest/shortest optimization, road/toll avoidance; Figs. 6–7).
• Predictive routing between updates using vector information (heading, speed) and, optionally, a known destination; and drawing all possible forks when no destination is known (Figs. 8–10).
• Real-time, incremental recalculation of only the newest route leg as updates arrive (Figs. 13–16).
• Route-planner interaction: re-designating discrete points as origin/via/stop/destination and editing/saving the route (Figs. 18–24).
• Dispatching/sorting metric: computing estimated routes from many "satellite" mobile devices to one "central" point and ranking vehicles by distance, time, or fuel (Figs. 25–26).

4. Prior-art categories a § 102 analysis must cover

Rather than misattribute citations, here is the defensible framework for where anticipatory art for these claims would live, based on the patent's own admitted background art (which is itself usable as § 102 prior art):

• AVL / fleet-tracking "breadcrumb" systems — the specification concedes these are well known and describes them as prior art (the Fig. 11 "breadcrumb history trail" is expressly labeled "prior art").
• Route-planning / navigation systems using map data networks — the specification concedes "conventional applications" use direct-line connections between discrete points.
• Map-matching (snap-to-nearest-segment) algorithms — discussed as known.
• Dispatching by line-of-sight distance — the specification expressly says LOS ranking "is currently used in the prior art," making LOS-based dispatch an admitted prior-art baseline.

Bottom line and recommendation

I have not produced a per-reference anticipation table because I could not verify US 7,881,730's actual cited references, and your rules forbid inventing them. The honest deliverable is: (a) the confirmed bibliographic record above, (b) the claim-feature map above, and (c) an explicit flag that the authoritative citation list must be pulled from the USPTO file wrapper (PTO-892s in application 12/484,091) or the Google Patents "Citations" tab.

If you can supply the face-page citation list (or authorize a direct fetch of the Google Patents citations section), I will produce the full per-reference table — full citation, publication/filing date, brief description, and the specific claims each reference potentially anticipates under § 102 — without altering any patent numbers or identifiers.

I'll start by gathering the pieces that the fetched page did not include — the issued claims and the actual prior-art citation list — since those are essential to a § 103 analysis.

The page text I was given omits two things critical to a § 103 analysis: the issued claims and the "Citations/Prior Art" tables. Let me pull both.

Obviousness Analysis — US 7,881,730 B2 under 35 U.S.C. § 103

0. Threshold caveats about the source material (read this first)

Two things you'd normally anchor a § 103 analysis on are absent from the page text supplied to me, and I will not fabricate them:

1. The issued claims are not in the provided text. The fetched page cuts off inside the "Detailed Description" ("The first architecture does not route its location updates, but only displays them on…"). There is no claim set. Google Patents renders claims in a tab that evidently did not come through.
2. There is no "Prior Art" / "Citations" table in the provided text. The only prior-art artifacts actually present are: Prior art date: 2002-04-10, Prior art keywords: location, mobile communication, communication device, route, information, the specification's own "Description of the Related Art," and FIGS. 11–12, which the patent itself labels "a prior art location history trail."

So the reference list I use below is reconstructed, and I flag the provenance of every reference. Specifically:

• The candidate reference set is drawn largely from the front pages of sibling/continuation patents in the same family (US 8,090,534; US 9,354,069), as reported by uspto.report / Justia — not verified against the '730 front page. Example URLs:
  • https://uspto.report/patent/grant/[8,090,534](/patent/8090534)
  • https://patents.justia.com/patent/[9354069](/patent/9354069)
• Prosecution history (from the PlainSite docket for parent application 10/410,740, of which '730 is a division — https://www.plainsite.org/dockets/28jdhq6ky/...) confirms multiple "892 – List of references cited by examiner" and "1449 – List of References cited by applicant" filings (6/13/2005, 1/19/2006, 6/20/2006, 12/5/2006, 5/31/2007, 5/22/2009). I could not retrieve the contents of those lists, and the searches I ran returned unrelated PTAB documents. Treat the reference set below as a working hypothesis requiring verification before filing anything.
• For claim scope I use the abstract + written description, plus one family member as a proxy: US 10,551,208 ("the '208 patent," same Sheha/Petilli/Yarlagadda family, descending from the '730 line per the page's priority chain), whose claim 1 was quoted in a court filing as requiring "determining a plurality of possible routes … by performing a route computation … using map data" and "display on the map a new possible route from the current location … and remove a previously displayed possible route," with claim 2 reciting "wherein the mobile computing device is a mobile communication device." (https://storage.courtlistener.com/recap/gov.uscourts.txwd.1172879830/gov.uscourts.txwd.1172879830.1.0.pdf). That is a proxy, not the '730 claim text.

Timeline: priority 2002-04-10 (prov. 60/371,941); non-provisional 10/410,740 filed 2003-04-10; '730 filed 2009-06-12 as a division; granted 2011-02-01; now assigned to Bluestone Ventures Inc.; expired – lifetime, adjusted expiration 2023-07-23; Darts-ip family litigation flag present on the page. Pre-AIA § 103 applies (filed 2003), so Graham/KSR with the classic TSM-plus-KSR framework governs.

1. Assumed claim scope (reconstructed)

From the abstract and FIGS. 1–26, the independent claims appear to cover a method/system in which (element labels mine):

• (A) discrete location updates are received from a mobile communication device (GPS/positioning device) at spaced intervals — including asynchronously (FIG. 4B);
• (B) each update is correlated/"snapped-to" the nearest pathway or segment of map data ("the point on the network pathways of the map data nearest to the actual mobile device's location");
• (C) an estimated route is computed along the road network between two updates, using route preferences (driving speeds, fastest/shortest, avoid highways/tolls);
• (D) the route and points are displayed on a map;
• (E) dependent: predictive route extrapolation between updates, including display of all possible branches at a fork (FIGS. 9–10);
• (F) dependent: route metrics — traveled distance, elapsed time, fuel usage;
• (G) dependent: points re-typed as origin/stop/via/destination in a route planner, modifiable and saveable;
• (H) dependent: ranking multiple mobile devices by estimated route (distance/time/fuel) to a central point (dispatch, FIGS. 25–26).

Diagnostic fact worth noting: the file history shows repeated non-final/final rejections (2005–2008) and allowance on a 3/12–3/13/2009 Examiner's Amendment (PlainSite docket, above). Allowance-on-Examiner's-Amendment means the granted scope was narrowed by examiner-drafted language — so the operative claims are likely narrower than the specification's ambition, and a § 103 attack must be built on the granted text, not the spec.

2. Level of ordinary skill (POSITA)

A bachelor's in EE/CS (or equivalent) plus ~2–3 years in digital mapping, vehicle location, or telematics; working familiarity with GPS/TOA position fixes, vector road-network map databases, shortest-path routing (Dijkstra/A*), client–server/wireless data transport, and AVL/fleet-tracking deployments. This is a low-to-moderate sophistication art in 2002.

3. The prior art, and what each reference supplies

(a) Admitted prior art from the patent's own text (§ 103 "admissions")

These are the strongest, cheapest hooks because they are the applicant's own words:

That is a substantial admission base: element (A) is conceded; element (C) is conceded as "true routing"; and element (H)'s LOS baseline is conceded.

(b) Candidate external references (provenance: sibling-patent front pages / family NPL — verify)

Availability caution: several candidates issued after 2002 (Kennedy 2003; Obradovich 2004; in the wider family, Staton 7,286,929, Scott 7,167,187, Wako 7,171,304). As pre-AIA § 102(e)/§ 103 art these only qualify if their effective filing dates predate 2002-04-10. Do not assume qualification; check filing dates.

4. The obviousness case: specific combinations and the motivation to combine

Ground I — Independent claim: AVL breadcrumb (admitted) + digital-map routing engine + map-matching, in view of route-preference art

Map to elements: (A) AVL/breadcrumb admissions + DeLorme '492; (B) map-matching literature / snap-to-road; (C) DeLorme '158 / Bechtolsheim '957 (and the applicant's own admission that "true routing applications" existed); (D) DeLorme '158 / McDonough '749; plus Obradovich '532 for the preference-based routing of the dependent claims.

Motivation (KSR-compliant):

• The problem is stated by the applicant itself. The Background identifies the exact deficiency: "'breadcrumb' trail does not provide the user with sufficient information about the mobile device's actual or estimated route … How the mobile device traveled along the underlying routable network infrastructure … is not provided in prior art," and "a method and system that can create a dynamic estimated route between various discrete locations would provide a number of improvements … extrapolating total driving distance … and … an ability to save the calculated estimated route." A reference that identifies the problem and points to the solution is itself motivation (In re Ratti logic; KSR endorses the "problem to be solved" as a motivation).
• Known technique for a known error. GPS error (2–15 m) and map error (2–50 m) were both well known; map-matching ("snapping") existed precisely to reconcile them. Applying it to breadcrumb points is a predictable use of a known technique to improve a similar device in the same way (KSR).
• Field of endeavor and reasonable expectation of success. Both AVL tracking and digital routing lived in the same telematics/mapping field, used the same map databases, and were routinely sold together; success was predictable because routing engines were mature and the data (ordered position fixes) already supplied origin/destination pairs implicitly.
• Market forces / design incentive. Fleet operators were already paying for AVL; billing on actual road miles (rather than LOS or odometer) and predicting arrival were recognized customer demands — and the '730 specification confirms the "fuel usage / total driving distance" business metric (FIG. 26). KSR expressly credits design incentives and market demand as motivations.

Ground II — Dependent claims on route preferences and metrics

DeLorme '158 (routing) + Obradovich '532 (user navigation preferences) + the AVL/breadcrumb base. "Fastest vs. shortest," "avoid highways/tolls," driving-speed classes, and distance/time totals are the ordinary configurable parameters of routing engines (and are expressly disclosed as preferences in DeLorme/Obradovich). Motivation: tailoring routes to vehicle class (truck vs. car) is a known routing requirement; converting a computed route into distance/time metrics is arithmetic on the route geometry.

Ground III — Predictive routing between updates (element E)

DeLorme '492 (heading sensing) + Oshizawa '381 (route guidance/off-route) + the base AVL/breadcrumb combination, or in the alternative simply the well-known dead-reckoning paradigm in vehicle navigation (position propagation by heading and speed between fixes is the standard technique dead-reckoning was invented for). Motivation: (i) the applicant's own framing — "predictive routing is calculated from the time an initial location update arrives to the time when the next location update arrives," i.e., it exists to bridge the latency gap created by 1 Hz, 0.5 Hz or 60-second update intervals; (ii) where the destination is known in advance, a best-path corridor to that destination is a trivial filter over the routing engine's existing output. Where the destination is unknown, displaying all branches at a fork (FIGS. 9–10) is the natural degenerate case of route expansion — a finite, identified set of alternatives (straight, left, right), i.e., KSR's "finite number of identified, predictable solutions."

Ground IV — Dependent claim on dispatch ranking (element H)

Admitted AVL/LOS dispatch art + DeLoe/Bechtolsheim routing engine + route-metric computation. Motivation is unusually explicit and comes from the patent itself: LOS distance is "currently used in the prior art," but LOS ignores one-way streets, turn restrictions, posted speeds, and stop lights — all of which the applicant identifies as things its improved ranking accounts for. Replacing an admitted, acknowledged-inaccurate proxy (straight-line distance) with the more accurate known computation (road-network travel distance/time) is the paradigm case of obviousness: a better-known metric substituted for a poorer one, with predictable improvement. Fuel usage is a fixed arithmetic function of distance/time × a vehicle compensation factor; once distance and time are computed, the add-on is routine.

Ground V — Dependent claim on the route planner / re-typing points (element G)

Route-planning UIs of the era (Microsoft Streets & Trips, MapQuest, DeLorme) already supported origin/via/stop/destination waypoints, reordering, and saving routes. The only delta in the '730 is that the points originate from a breadcrumb trail. Motivation: the applicant supplies it — "the estimated route information provides graphical information that would aid the user in modifying the location history information" (a design rationale, not a technical leap). This is a UI/data-model transfer of a known editing paradigm to a new data source, with predictable results.

5. The Graham factors, applied

• Scope and content of prior art: as in § 3–4; the art is crowded in the 1996–2002 window, and the applicant's own Background concedes the key elements.
• Differences: the only real differences over the combination are (i) directing a map-data routing engine at discrete sampled update pairs derived from a mobile device, (ii) incremental recomputation of only the newest route leg, and (iii) certain display details (simultaneously rendering all predicted branch paths at a fork).
• Level of ordinary skill: low-to-moderate; a competent routing/telematics engineer could implement the combination.
• Secondary considerations: Not established on the materials I have. This is a real gap in any final opinion, and it is the area most likely to decide the outcome. Points to develop: (a) the family carries a Darts-ip global litigation flag, and where a patent family has been litigated and licensed, evidence of nexus-based commercial success or industry licensing may be available; (b) any such evidence must have nexus to the granted claim scope, not just to the product (see the Federal Circuit's 2026 non-precedential Metrom decision, https://cafc.uscourts.gov//opinions-orders/24-2223.OPINION.5-11-2026_2691571.pdf, applying Fox Factory: no presumption of nexus where the product has important unclaimed features). Here, likely unclaimed features include the whole off-board/voice-prompt and position-transfer apparatus in the sibling patents.

6. Where the obviousness case is weakest (candidate non-obviousness arguments)

1. Incremental recomputation. The specification stresses: "it is not necessary to compute an entire new route for the entire breadcrumb trail, but only the portion of the estimated route that needs to be calculated … only the new additional estimated route segment 1401 needs to be calculated." If a granted claim requires not recomputing earlier legs, the strongest rebuttal is "routine optimization," but the patentee will argue this is the asserted point of novelty. This is the limitation to check first in the actual claim text.
2. Simultaneous display of all predicted branches at every fork (FIGS. 9–10, points 907/910/915 → 908/911/914 → 909/912/913, then erasing non-viable legs on the next real update). If claimed, this is a specific rendering-and-pruning behavior; the prior art I can identify is thinner here, and a patentee could argue the references teach one route, not a "diverge-then-prune" display.
3. Availability/qualification of the later-issued references (§ 3(b) caution) can be attacked on pre-AIA § 102(e) effective-filing-date grounds.
4. Claim-text mismatch. Because the '730 was allowed on an Examiner's Amendment, the granted language may differ materially from the description I have used to reconstruct scope. My element mapping (A)–(H) is a hypothesis, and any of it could be wrong. Obtain the granted claims from USPTO PatentCenter / the US2009/0287407A1 publication and the 3/13/2009 Examiner's Amendment before relying on this analysis.

7. Bottom line

On the materials available, the independent claims of US 7,881,730 are vulnerable to a strong prima facie § 103 case: the applicant's own Background concedes discrete-update tracking (AVL), breadcrumb display with numbered/arrowed points, LOS-based dispatch ranking, and "true routing applications" over a network of map paths; map-matching ("snap-to-road") was a known technique for the known GPS-vs-map error problem; and the motivation to combine is supplied by the problem the specification itself articulates (breadcrumbs don't show how the device traveled, nor yield mileage/time). KSR supports the combination as (a) a known technique improving a similar device in the same way, (b) a "finite number of identified, predictable solutions," and (c) a response to market/design demands in fleet tracking and telematics. The dependent claims read on conventional implementation choices (preferences, metrics, planner UI, ranking) each of which is either an admitted practice or an arithmetic/UI consequence of a computed route.

The most defensible non-obviousness foothold for the patentee is the specific incremental, only-new-leg recomputation and the diverge-and-prune predictive display — and those arguments only matter if the granted claims actually recite them.

Two things must be done before this analysis is actionable: (1) pull the literal granted claim text (the page I was given does not contain it), and (2) pull the '730 front-page "References Cited" / IDS-1449 and 892 lists (the page I was given does not contain them, and my reference set is reconstructed from sibling patents, not verified).

This is a technical patent analysis, not legal advice, and no attorney–client privilege attaches to it.