US 8836580

US Patent 8,836,580 — Summary (Searched as: 8836580 / US8836580B2)

Bibliographic Data (confirmed against the Google Patents record for US8836580B2 and the issued-patent PDF)

Independent Claims — Plain-Language Overview

The patent has 16 claims. Based on the issued text, there are two independent claims (1 and 15); claims 2–14 depend from claim 1. Claims 15–16 are truncated in the record I have (see uncertainty note below).

Claim 1 (independent): A method of determining where a display device (portable display, mobile phone, handheld/car navigation system, or other Bluetooth-enabled device) is located inside a facility and guiding the user on that device. Steps: (a) install/upload a navigation app; (b) download the facility's indoor floor-plan map to the device before arriving; (c) determine the device's current position by proximity to RF tags installed at known positions in the facility, where the tags emit Bluetooth or Wi-Fi signals — using the tag's known location as the reference when only one tag is heard, or triangulation when signals from multiple tags are received; (d) show a position marker for the device as an overlay on the facility map; (e) navigate using the displayed tag positions; (f) display additional local information about nearby elements/points of interest.

Claim 15 (independent, partially captured in the provided text): A method of determining a display device's current position and providing road sign information, using the device's proximity to RF tags installed at known positions in a regional area, where position is determined by (a) using the location reference of a single tag, or (b) another technique (text cuts off mid-sentence in the available record at "utilizing a location reference of s…"). The claim's purpose is to deliver road-sign-type information to the display device based on that tag-derived position.

Dependent claims 2–14 (from claim 1) add, in substance: delivering location-based services content tied to device location (2); an indoor local-services application suite including map/guide, directory, search-and-find, sales/specials with aisle navigation, parking-spot detection, return-to-parking, general info (events, restrooms, ATM, etc.), emergency navigation, and panic alert (3); real-time updated waypoint info such as store/department/sale/event/coupon (4); navigation between waypoints shown on the floor plan (5); indoor positioning without GPS (6); navigation software using an area map or floor plan (7); pedestrian navigation in enumerated facility types (mall, museum, subway, airport, stadium, cruise ship, parking facility, etc.) (8); parking-space detection and return-to-parking via a tag associated with the parked car (9); museum/show/conference exhibition guide keyed to RF tag ID (10); real-estate listing guide based on tag/device location (11); amusement-park waypoint guidance (show schedules, wait times, restrooms, food areas) (12); emergency exit-route navigation (13); and train/bus/subway location display on a route map with schedule/restroom/food/emergency info keyed to the nearby RF tag (14).

CAFC 2026 Docket Search

I searched for CAFC 2026 dockets involving patent 8,836,580 (and related search variants such as "8836580 Mendelson," "Gamba Group/Blue Umbrella litigation," etc.). No CAFC 2026 appeal, petition, or docket entry specifically referencing US 8,836,580 was found. The 2026 Federal Circuit matters surfaced by the searches (e.g., TrackTime v. Amazon, Constellation Designs v. LG, Innovaport v. Target, Bosch v. Westport) do not involve this patent. I could not confirm any pending district-court or Federal Circuit case naming this patent as of the search date.

Uncertainty Notes

• Claims 15–16: The supplied authoritative text cuts off mid-claim 15, so the full scope of claim 15's remaining limitations and all of claim 16's content could not be verified. I cannot state with confidence whether claim 16 is independent or dependent, or its full text.
• CAFC/docket status: Absence of a docket hit is not proof that no litigation exists; it reflects that my searches returned no specific 2026 CAFC record for this patent number. If you need definitive litigation status, the USPTO Patent Center and PACER (for district court) / the CAFC docket would be the authoritative sources.
• Priority-date discrepancy: Google Patents' "prior art date" field (2005-04-12) conflicts with the patent's own recitation of the May 9, 2005 provisional; I have treated the patent text as authoritative.

Based on the searches I was able to run, I could not identify any litigation involving U.S. Patent No. 8,836,580.

What I did:

• Searched "8836580" patent litigation, "US8836580" lawsuit, "8,836,580" patent case, and Gamba Group "8836580" litigation.
• Those queries returned no results specifically tied to patent 8836580 (the search engine returned empty result sets for several, and the non-empty results were unrelated patents such as 8,836,580-adjacent drug patents and other matters that do not involve this patent).

Important caveats:

• I was unable to complete a direct query of the Unified Patents litigation portal, PACER, CourtListener, or DocketNavigator before hitting the tool-call limit. My results are therefore based only on general web searches, and absence of results there is not conclusive proof that no litigation exists.
• I am not aware, from my own knowledge, of any reported district court case, ITC investigation, or Federal Circuit appeal naming U.S. Patent No. 8,836,580 ("RF proximity tags providing indoor and outdoor navigation and method of use") as a patent-in-suit. The patent's assignment history (Individual → Gamba Group Limited → Blue Umbrella LLC → Gamba Group Holdings LLC, with a 2025 security interest to Piccadilly Patent Funding LLC) shows downstream monetization activity, but an assignment chain alone does not indicate litigation.

Bottom line: Based on the searches performed, no known litigation involving U.S. Patent No. 8836580 was identified. To confirm definitively, you should check the USPTO Patent Center/assignment records, PACER (for district court dockets), the Unified Patents litigation caselist at https://portal.unifiedpatents.com/litigation/caselist, and RPX/DocketNavigator — those sources were not directly accessible in this session.

Proceedings overview

There are zero AIA trial proceedings (IPR/PGR/CBM) on file for U.S. Patent No. 8,836,580. The USPTO Open Data Portal ingest reflected in this prompt shows no proceedings, and live web searching surfaced no PTAB petition, institution decision, final written decision, or Federal Circuit appeal tied to this patent number. (Search hits for "IPR2021-01466" and a "'883 patent" concern a different patent — U.S. 10,531,883, an aspiration-thrombectomy patent — and are not this case.) Defensive posture for a defendant: the patent is completely untested at the PTAB — no claim has been canceled or even challenged, and every one of the 16 granted claims (independent claims 1 and 15, plus dependents) remains in full force.

No proceedings to report individually.

Strategic summary

Claim status — CANCELED vs. SUSTAINED vs. UNTESTED. Nothing has been canceled. Nothing has been sustained through an IPR trial (because none has been filed). Every claim of the '580 patent — independent claim 1 (RF-tag proximity positioning + floor-plan download + overlay navigation) and independent claim 15 (road-sign/RF-tag regional-area variant), with dependent claims 2–14 and 16 — is UNTESTED at the Board. All 16 claims are presumed valid and currently enforceable, subject only to the ordinary § 282 presumption and any district-court invalidity arguments.

Estoppel landscape. Because there are no completed or even instituted AIA trials, there is no § 315(e)(2) estoppel binding anyone. A defendant sued today is free to raise any prior-art ground under § 102/§ 103 (and any § 112 ground) in district court, and any petitioner would face no estoppel bar on future grounds. The corollary warning: the patent owner has also never been forced to defend the claims before the Board, so the claims' robustness is entirely untested — do not read "no IPR" as "strong patent." It more likely reflects that the patent (filed 2006, granted 2014, expiring 2027 after adjustment) has simply not been the target of a coordinated PTAB campaign to date.

Pattern signals. No repeat-petitioner pattern, no Unified Patents / defensive-aggregator involvement, and no patent-owner appellate behavior at the PTAB can be assessed — there is no history. One contextual note for diligence: the '580 patent is part of a large Ehud Mendelson/Gamba Group (now Gamba Group Holdings LLC) family of navigation/RF-beacon patents (e.g., 7,899,583; 8,896,485; 9,420,423; and others in the priority chain shown on the face of the patent). If you are being asserted against, check whether the demand cites related family members — those are separate patents with separate PTAB histories and may have been challenged even if '580 has not. The '580 patent itself shows a 2025-03-25 security-agreement assignment to Piccadilly Patent Funding LLC, which is consistent with monetization/assertion activity.

Recommended next steps

• No PTAB activity exists — say so plainly in any defense memo. There is no FWD to link and no disposition to quote. The absence of an IPR is not an invalidity data point; it is a blank slate. If you are facing a demand letter citing the '580 patent, the practical implication is that the patent owner has never had to defend the claim scope before the Board, so a well-prepared § 103/§ 101 challenge in district court (or a new IPR petition if you are outside the 1-year § 315(b) bar from service of a complaint) is the first test these claims will face.
• Verify timeliness for a future IPR. If a complaint has been served on you, the § 315(b) one-year bar from service runs regardless of the absence of prior PTAB activity — move quickly if an IPR is contemplated.
• Re-run the PTAB and district-court checks at assertion time. The ODP/PTAB E2E databases and the USPTO assignment records are the authoritative sources; this analysis reflects the USPTO ODP ingest date given in the prompt and web-search results as of 2026-09-05. Confirm there is no newly filed petition (e.g., check PTAB E2E by patent number) and no co-pending district court case that would create co-pendency/§ 315(b) or Fintiv considerations before any petition filing.
• Scope the family. Since assertion of "RF proximity tags / indoor-outdoor navigation" technology may be pursued through continuation/related patents (the priority-chain list on the '580 face includes applications through 2022), identify exactly which patent number(s) the demand cites. An IPR on a sibling does not touch '580, and vice versa — each must be analyzed separately.

Bottom line: U.S. 8,836,580 has never been through an AIA trial — no petitions, no institutions, no cancellations, no settlements, no appeals. For a defendant, that means every claim is presumed valid and untested; there is no "dead claim" to lean on, and conversely no estoppel preventing you from running the strongest available prior-art attack.

I hit the search-tool step limit and my live queries to the USPTO Assignment Center and secondary directories returned no usable records (empty result sets), so I could not verify reel/frame numbers, execution dates, or correspondents of record. Rather than fabricate those fields, everything dated below comes from the Google Patents legal-events feed reproduced in the full patent text supplied, which is itself an index of the USPTO assignment database. Where a field (reel/frame, correspondent) is unknown, I say so explicitly.

Inventors

• Ehud Mendelson — sole named inventor.
• Employer at filing: none determinable. The application was filed 2006-05-08 by Mendelson as an individual (Google Patents: "Application filed by Individual"; "Original Assignee: Individual"), claiming priority to provisional 60/678,947 (2005-05-09).
• Unusual pattern: single-inventor, individual-owned application that remained with the inventor for ~8 years until a pre-grant assignment (recorded 2014-05-19) to a company entity. Mendelson is a prolific inventor with a large family of related RF-proximity/location patents that have flowed through the same Gamba/Blue Umbrella entity chain (e.g., continuations US8896485, US7924149, US8866673, US9374673, US9602193, etc.), which is consistent with an inventor-typed patent monetization program rather than an employment-derived portfolio.

Original assignee

• On issue, the record shows the chain beginning with Ehud Mendelson, individually (Google Patents lists "Individual" as original assignee), with the first entity assignment to Gamba Group Limited recorded 2014-05-19 — four months before grant on 2014-09-16, so the patent in substance issued into the Gamba chain.
• Primary line of business: none for the individual; Gamba Group Limited/Holdings entities do not appear to ship any product embodying the claims (no operating-company product evidence exists in the record).
• Current status: Active (expires 2027-11-24); current assignee per Google Patents is Gamba Group Holdings LLC, subject to a 2025 Patent Security Agreement in favor of Piccadilly Patent Funding LLC, as security holder.

Assignment timeline

Note: USPTO reel/frame numbers, execution dates, and correspondents of record could not be retrieved in this session (Assignment Center live query returned no results before the step budget was exhausted). The entries below are the recorded assignment events as indexed in the Google Patents legal-events feed. Verify reel/frame at https://assignment.uspto.gov/patent/index.html#/patent/search.

• 2014-05-19 recorded (execution date not retrieved) — Reel/frame not retrieved

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Ehud Mendelson
  • Assignee: Gamba Group Limited
  • Correspondent: not retrieved
  • Context: Pre-grant transfer from the individual inventor into a company entity four months before issuance; establishes the monetization chain.

• 2019-10-06 recorded (execution date not retrieved) — Reel/frame not retrieved

  • Conveyance: Assignment (per Google Patents reassignment event)
  • Assignor: Gamba Group Limited
  • Assignee: Blue Umbrella LLC
  • Correspondent: not retrieved
  • Context: Transfer within the inventor's related-entity family (Blue Umbrella LLC appears as assignee on later Mendelson-family patents), consistent with an internal restructuring.

• 2023-11-29 recorded (execution date not retrieved) — Reel/frame not retrieved

  • Conveyance: Assignment (per Google Patents reassignment event)
  • Assignor: Blue Umbrella LLC
  • Assignee: Gamba Group Holdings LLC
  • Correspondent: not retrieved
  • Context: Transfer back into the Gamba-named family entity, again consistent with internal re-shuffling of the holding entities.

• 2025-03-25 recorded (execution date not retrieved) — Reel/frame not retrieved

  • Conveyance: Patent Security Agreement
  • Assignor/Grantor: Gamba Group Holdings LLC
  • Assignee/Secured party: Piccadilly Patent Funding LLC, as security holder
  • Correspondent: not retrieved
  • Context: Grant of a security interest in the patent to a patent-funding entity — a monetization-financing tell (borrowing against the asset), not a sale to an operating company or defensive aggregator.

If the Assignment Center ultimately shows additional records (e.g., corrections, releases), they are not reflected in the Google Patents feed I was given; the four events above are the complete recorded reassignment set visible in that feed.

Timeline diagram

timeline
    title Ownership of US 8836580
    2005 : Provisional filed
    2006 : Utility filed by Ehud Mendelson
    2014 : Patent issued
         : Assigned to Gamba Group Limited
    2019 : Assigned to Blue Umbrella LLC
    2023 : Assigned to Gamba Group Holdings LLC
    2025 : Security interest to Piccadilly Patent Funding

NPE / troll-pattern signals

1. Shell-entity transfer — present (weak). The patent moved from an individual inventor to Gamba Group Limited (recorded 2014-05-19), then through Blue Umbrella LLC (2019-10-06) to Gamba Group Holdings LLC (2023-11-29). All are non-operating, inventor-controlled holding entities, and no product embodying the claims is identifiable in the record. The tell is paired with the ownership structure (never an operating assignee) rather than naming alone, but I could not verify registered-agent addresses or absence-of-products beyond the record, so I weight this as weak.

2. Known asserter in the chain — unclear. Piccadilly Patent Funding LLC (security holder, 2025-03-25) has the profile of a patent-monetization finance vehicle, and Gamba Group entities are not operating companies. However, I could not in this session confirm either entity against the Unified Patents / RPX asserter directories, so I will not assert placement on a public NPE list.

3. Repeat correspondent across the chain — not determinable. Reel/frame numbers and correspondents of record were not retrievable in this session; no recurrence finding can be made without that data.

4. Cascading transfers — not present. The LLC-to-LLC transfers are ~4 years apart (2019 → 2023), not multiple chained transfers inside 24 months. The 2014 and 2019 and 2023 transfers do, however, all move within one inventor-controlled family, which is an internal-restructuring pattern rather than a cascading shell chain.

5. Pre-litigation transfer — not present / unverified. The 2014 assignment (2014-05-19) predates grant (2014-09-16), so it is a pre-issuance assignment, not a litigation-driven transfer. No infringement suit naming US 8836580 was identified in the available record.

6. Bankruptcy fire-sale — not present. The chain originates with an individual inventor; no Chapter 7/11 proceeding is in the record.

7. Privateering — not present. No operating company sits behind the chain transferring patents to an NPE to sue its competitors; the origin is the inventor himself.

8. Defensive aggregator (anti-NPE) — not present. The chain terminates at Gamba Group Holdings LLC with a security interest held by Piccadilly Patent Funding LLC; neither is RPX, AST, LOT, Unified Patents, or OIN.

Verdict

NPE — moderate confidence.

Two weak-to-moderate signals support this: (i) the patent was moved from the individual inventor into a set of non-operating holding LLCs (Gamba Group Limited → Blue Umbrella LLC → Gamba Group Holdings LLC; recorded 2014-05-19, 2019-10-06, 2023-11-29), with no product company ever in the chain; and (ii) the 2025-03-25 Patent Security Agreement naming Piccadilly Patent Funding LLC, as security holder is a monetization-financing arrangement — borrowing against the patent — which is characteristic of funded NPE assertion. The countervailing limitation is that I could not verify actual infringement litigation, public NPE-list placement, or the correspondents of record (reel/frame data unavailable in this session), so I stop short of high confidence. Verification link: https://assignment.uspto.gov/patent/index.html#/patent/search (search patent number 8836580) and the Google Patets legal-events page at https://patents.google.com/patent/US8836580/en.

Prior Art Analysis: U.S. Patent No. 8,836,580 B2

0. Patent identification (confirming the exact target)

I searched for US 8,836,580 / US8836580B2 — "RF proximity tags providing indoor and outdoor navigation and method of use" (Inventor: Ehud Mendelson; Appl. No. 11/429,864 filed 2006-05-08; published as US20070001904A1 on 2007-01-04; granted 2014-09-16). The searches returned only this patent and later patents citing it (e.g., EP1995987A2's family list, WO2013036657A2, JP6576434B2, U.S. Pat. No. 10,600,252 and U.S. Pat. No. 12,340,143 cite the published application US20070001904A1). I did not encounter any similarly numbered but different patent in the results — no auto-correction issue arose.

1. Important limitation on the requested analysis

The task asks me to "look at each patent citation for 8836580" — i.e., the USPTO References Cited (the examiner's and applicant's prior-art citations listed on the face of the patent / in the file wrapper). I must flag this clearly: the complete official citation list was not retrievable in this session.

• The full patent text provided to me (Google Patents fetch) contains the specification and claims but does not include the "Patent Citations" / "References Cited" sidebar that Google Patents normally renders.
• My searches for the citation list ("8836580" "References Cited", "20070001904" cited references, etc.) returned only (a) the patent's own full text, and (b) later patents citing this patent — not the list of references cited inside this patent's file wrapper.
• I hit the tool-call limit before I could query the USPTO Patent Public Search/Patent Center or pull the Google Patents citations tab directly.

Bottom line up front: From the material available to me, I can definitively identify one prior-art reference that the patent itself names and discusses: Ellenby et al., U.S. Pat. No. 7,031,875. I analyze that reference below. I will not fabricate an examiner-citation list I could not verify; instead I provide the analysis framework, the claim chart for what is verifiable, and precise instructions for retrieving the official citation list (Section 5).

2. Reference affirmatively identified in the patent's own text

(R1) Ellenby et al. — U.S. Patent No. 7,031,875

Where it appears in 8836580: In the BACKGROUND/PRIOR ART section the applicant states:

"U.S. Pat. No. 7,031,875 Ellenby et al. describe a pointing system for addressing objects, provide a system and method based on GPS and Internet/database communication, it is not exactly a navigation but a information based system that need the GPS to locate the user location so indoor services is likely out of the question and the need for communication as well with GPS limit its availability and accuracy."

Because it is discussed in the specification, Ellenby '875 is at minimum an applicant-identified reference that would appear in the file wrapper's citation record (and is the only patent the applicant chose to distinguish by number).

Anticipation (35 U.S.C. § 102) analysis — R1 vs. the independent claims

Independent claims 1 and 15 (and the unshown claim 16) are the relevant ones for an anticipation screen; dependent claims 2–14 add features (parking/RTP, emergency, NAV4 modes, train/subway, real estate, etc.).

Taking claim 1's elements in order:

Conclusion for R1: Ellenby '875 does not anticipate claim 1 under § 102: it lacks (i) RF tags at known positions emitting Bluetooth/Wi-Fi as the position-determination mechanism (it requires GPS), (ii) pre-arrival download of a facility indoor floor plan, and (iii) an overlay position/navigation display driven by tag proximity. The same deficiencies defeat § 102 against claims 2–14 and 15–16 to the extent those depend on the RF-tag position architecture. Ellenby is therefore best characterized as secondary reference — potentially combinable in an § 103 obviousness rejection (e.g., Ellenby's "point at object and get info" concept combined with an RF-beacon indoor-positioning reference), which is consistent with the applicant's decision to distinguish it affirmatively in the specification.

3. What the searches did establish about the citation ecosystem

• The published application US20070001904A1 (Mendelson) is itself cited as prior art in later patents — e.g., U.S. Pat. No. 10,600,252 ("Coarse relocalization using signal fingerprints," Justia citation list) and U.S. Pat. No. 12,340,143 ("Sharing neighboring map data across devices," Justia citation list) — confirming the publication date (2007-01-04) that governs prior-art status for this patent's own family filings.
• Later patents in Mendelson's own family list 8836580 as a domestic priority/continuity reference (e.g., EP1995987A2 family, WO2013036657A2, JP6576434B2 all show "US8836580B2 * 2005-05-09 … Ehud Mendelson … RF proximity tags providing indoor and outdoor navigation and method of use"). These are citing documents, not cited references, so they are not § 102 prior art against 8836580 (they post-date it) — but they confirm the claim-1 architecture (Bluetooth/Wi-Fi RF tags at known waypoints, tag-proximity position fix, no cellular/Internet needed) is the core the family repeatedly relies on.

4. Anticipation screening framework for the unverified examiner citations

When you obtain the official list, screen each reference against the pre-2005-05-09 priority date (Provisional Appl. 60/678,947, filed 2005-05-09; non-provisional filed 2006-05-08). For each cited patent, the elements to test for § 102 against claim 1 are:

1. Display device = portable phone / car nav / Bluetooth device with uploaded guidance application;
2. Indoor floor-plan of the facility downloaded before arrival;
3. Position fix by proximity to fixed RF tags (Bluetooth/Wi-Fi) at known locations — single-tag "nearest tag = location" or multi-tag triangulation;
4. No GPS required for the indoor fix;
5. Position marker as an overlay on the facility map;
6. Navigation display using tag positions as waypoints;
7. Push of facility/vicinity information to the device.

Any cited reference disclosing all of 1–7 in a single embodiment would be a prima facie § 102 anticipation; references missing one or more elements (typically the "direct RF-tag beacon, no network" architecture, or the "no-GPS" indoor fix) are § 103 combination fodder instead. Because the claims repeatedly recite "no GPS," "no cellular," and "direct tag-to-device" (spec, Summary; claims 1, 6), examiner citations from the 2006–2014 prosecution that are pure GPS/database systems (like Ellenby) or network-dependent RFID tracking systems will generally fail the anticipation test on those elements.

5. How to obtain the authoritative citation list (recommended next step)

The official References Cited for 8836580 is viewable at:

• USPTO Patent Center — https://patentcenter.uspto.gov (enter Appl. No. 11/429,864; open the "References Cited" / "Foreign References" / "NPL" tabs in the file wrapper); and
• Google Patents citations tab: https://patents.google.com/patent/US8836580B2/en (the "Patent Citations" and "Non-Patent Citations" sidebar sections — which were not present in the text fetch I was given).

When you can open those tabs, I can complete the element-by-element § 102 claim chart for every listed reference. Based on the material actually available in this session, the only reference I can analyze with confidence is Ellenby U.S. 7,031,875, which does not anticipate any claim of 8836580 under § 102 (GPS-dependent, database-communication pointing system lacking RF-tag waypoint navigation, indoor floor-plan pre-download, and overlay navigation).

Obviousness Analysis — U.S. Patent No. 8,836,580 B2

Under 35 U.S.C. § 103 (pre-AIA, application filed May 8, 2006)

1. Legal framework and applicable law

Because U.S. Application No. 11/429,864 was filed before March 16, 2013, pre-AIA § 103 applies, governed by Graham v. John Deere Co., 383 U.S. 1 (1966), as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). Under KSR, a patent claim is obvious when the prior art, taken as a whole, would have rendered the claimed subject matter predictable to a person of ordinary skill in the art (PHOSITA) — including where the combination is of known elements "according to known methods to yield predictable results," driven by "design need or market pressure." A challenger need not find a single reference that teaches every limitation; a combination with articulated reasons for combining is sufficient.

2. Person of ordinary skill in the art

A PHOSITA in early-to-mid 2005 would have been an engineer or scientist with a B.S./M.S. (or equivalent experience) in electrical engineering, computer science, or a related field, with 2–5 years of experience in: wireless communications (Bluetooth, IEEE 802.11/Wi-Fi, RFID), location/positioning technologies (GPS, cellular location, indoor RF positioning), and mobile application/embedded software development for cellular phones and handheld devices. The person would be familiar with Bluetooth inquiry/paging, RSSI-based positioning, proximity detection, and map/floor-plan rendering on mobile devices.

3. The claims at issue (scope)

Claim 1 is the sole independent method claim (claims 15 appears to be a second, truncated independent claim directed to "road sign information"; claim 16 is not visible in the available text). Claim 1 requires:

1. a display device selected from portable display, mobile phone, handheld navigation, car navigation, or Bluetooth-enabled device;
2. uploading a navigation/guidance application;
3. pre-arrival download of an indoor floor plan/mapping of the facility;
4. position determination by proximity to RF tags at known positions, the tags emitting Bluetooth or Wi-Fi, using either (a) single-tag location reference or (b) multi-tag triangulation;
5. displaying a position marker as an overlay on the facility map;
6. navigating via displayed tag positions; and
7. displaying additional local information about nearby elements.

Dependent claims 2–14 add: location-based content delivery (2); an indoor LBS "suite" (directory, search-and-find, sales/coupons with aisle navigation, parking-space detection, return-to-parking, facility info, emergency navigation, panic alert) (3); real-time waypoint info (4); waypoint-to-waypoint navigation (5); operation without GPS (6); floor-plan navigation software (7); enumerated pedestrian environments (8); parking/RTP (9); museum/venue guide via tag ID (10); real-estate listings (11); amusement-park waypoints/wait times (12); emergency-exit routing (13); and transit (train/bus/subway) location (14).

4. Prior-art record available for the analysis

The "Prior Art" portion of the patent itself — which constitutes applicant-admitted prior art under 37 C.F.R. § 1.104/MPEP § 2129 — is unusually rich and is the primary basis for this analysis:

A. Applicant-admitted prior art (from the specification)

• U.S. Pat. No. 7,031,875 (Ellenby et al.) — point-and-query information system combining GPS and Internet/database communication (discussed and distinguished in the Background).
• Indoor location methods generally: Proximity Detection (PD), Received Signal Strength (RSSI), Time of Arrival (TOA), Angle of Arrival (AOA) — each described in detail as known.
• WLAN (IEEE 802.11b) indoor location — "solutions do exist in the market, providing an accuracy of approximately two (2) meters," implemented by "adding a location server" to existing access-point infrastructure.
• Bluetooth (IEEE 802.15) indoor location, including:
  • "Binary location" (PD, one AP per waypoint, nearest-AP = location);
  • "Analog location" (RSSI, APs 10–15 m apart, triangulation);
  • the Inquiry and Paging mechanisms used for discovery and accurate location;
  • the admission that "[e]very Bluetooth device's tag has a unique ID. This ID can be used for locating the tag," and that Bluetooth alone gives "an approximate 2 meter error range";
  • the admission that RF (Bluetooth) tags attached to persons/assets and tracked by fixed readers is "the most common indoor navigation that exists today."
• Waypoint navigation / map matching — described as known concepts (waypoints mark destinations; routes consist of waypoints; systems compute great-circle routes, generate suggested routes, and "indicate the user's current location"), i.e., classic GPS-navigation functionality.
• Google Earth-type imagery services — known, but criticized as outdated (admitted prior art for map/imagery download).

B. Search-verified third-party reference

• JP 2001-116583 ("Destination Guidance System," published April 27, 2001, filed Oct. 20, 1999) — RFID tags attached to objects/locations (e.g., display shelves) in a facility; multiple reader/writer antennas with stepped transmit power determine each tag's distance range and thus its 2-D position; a user searching for a category (e.g., "snacks") causes the system to display the corresponding item's location superimposed on a floor map (verified via J-GLOBAL search results during this session). This teaches RF-tag-at-known-position location tied to a searchable facility directory with map overlay — albeit reader-centric rather than handset-centric.

C. Known background art a PHOSITA would have had (not individually file-verified here)

• Microsoft Research RADAR (Bahl & Padmanabhan, IEEE INFOCOM 2000) — in-building RF location via Wi-Fi RSSI (later including triangulation) on a mobile device with floor-plan display.
• Early commercial Wi-Fi/Bluetooth positioning engines (e.g., Ekahau, circa 2002–2004).
• Bluetooth SIG specifications (through version 1.2, 2003) defining inquiry/paging, device discovery, and unique device addresses.
• Conventional cellular "location-based services" and in-car navigation overlays.

Analyst caveat: I could not retrieve the examiner's "References Cited" list from the file wrapper or the USPTO Patent Center in this session, and the text of claims 15–16 is truncated in the provided source. The analysis below is therefore grounded in the applicant-admitted prior art and the search-verified JP reference. A complete challenge should be validated against the actual file wrapper and a full-text copy of all 16 claims.

5. Claim 1 — element-by-element obviousness map

Result: Claim 1 is a collection of known building blocks — Bluetooth/Wi-Fi proximity and RSSI positioning (admitted prior art), facility RF-tag waypoints (admitted), downloadable floor plans (admitted), map-overlay display (JP '6583 and navigation art), waypoint navigation (admitted), and location-based content (admitted/Ellenby). The claim does not require any server, database, or novel hardware; it simply reverses the reader/tag roles already described in the patent's own Background ("the disclosed method is the 'flip side' of this practice").

6. Proposed § 103 combinations and motivations

Combination 1: Bluetooth/Wi-Fi indoor location art (admitted) + JP 2001-116583 + conventional map/navigation display

• Primary references: (i) the Bluetooth "binary location" (PD) and "analog location" (RSSI triangulation) systems described in the patent's Background; (ii) WLAN IEEE 802.11b location-server art (~2 m accuracy, admitted); (iii) JP 2001-116583 (RFID tags at known positions in a facility with searchable directory and floor-map overlay).
• Combination: Place Bluetooth/Wi-Fi tags at known store/waypoint positions in a facility (as BT binary/analog art already does). Have the user's Bluetooth/Wi-Fi-enabled phone determine its position from the nearest tag (PD) or from multiple tags (RSSI triangulation) — precisely the two alternatives recited in claim 1(c). Download the facility floor plan to the phone in advance (JP '6583 map data; navigation-app practice). Render the user's position as an overlay on the floor plan (JP '6583; in-car nav) and navigate waypoint-to-waypoint (admitted waypoint art). Push store directory/info associated with each tag (JP '6583; Ellenby).
• Motivation to combine: The patent itself identifies the market problem — GPS fails indoors/urban canyons — and identifies existing Bluetooth/WLAN indoor-positioning solutions as the obvious substitute infrastructure. A PHOSITA seeking indoor navigation for cell phones would naturally combine (i) a known indoor positioning technology (Bluetooth/Wi-Fi tags at known locations) with (ii) a known display paradigm (floor-plan overlay with current-position marker, used in JP '6583 and in-car navigation) and (iii) known waypoint-routing. Under KSR, this is combining known elements to yield a predictable result driven by a recognized design need (indoor wayfinding). The claimed "flip side" arrangement — tags broadcasting, phone listening — is the inherent operating mode of Bluetooth device discovery (inquiry), and Bluetooth tags with unique IDs were admitted prior art ("[e]very Bluetooth device's tag has a unique ID. This ID can be used for locating the tag").
• No teaching away: Nothing in the admitted art discourages putting the position-calculation function in the mobile device; Bluetooth inquiry was designed for mobile discovery, and Wi-Fi client-side scanning was standard. The patent's touted advantages (no cellular/Internet needed, ~10-foot accuracy) are the same accuracy claims the patent attributes to known Bluetooth location systems (~2 m).

Combination 2: Ellenby '875 (POI information) + admitted Bluetooth/RF-tag positioning + floor-plan download

• Primary references: U.S. Pat. No. 7,031,875 (Ellenby) — addressing objects/POIs and retrieving associated information on a handheld pointing system; plus admitted Bluetooth-tag positioning and map-download art.
• Combination: Substitute Ellenby's GPS/Internet-dependent position fix with the admitted Bluetooth/Wi-Fi tag-positioning approach so the system works indoors; retain Ellenby's POI-information delivery to satisfy claim 1(f). Motivated by Ellenby's own limitation — which the patent acknowledges — that GPS dependence forecloses indoor use; the obvious fix is the known indoor-positioning alternative already described in the same field.

Combination 3 (for the dependent claims): known LBS "suite" features

• Claims 2–3, 9–14 add standard LBS features (directory, search, coupons/sales with aisle routing, parking-space detection, return-to-parking, museum audio guides, amusement-park wait times, emergency egress, transit location). Each was known in the art before 2005:
  • Museum/venue audio guides and POI content triggered by proximity/tag ID — well-established (IR/RF museum guide systems; JP '6583's per-shelf content association).
  • Parking-space detection and return-to-parking — known parking-guidance and "car-finder" systems; combining them with RF-tag location is a predictable application of the same positioning mechanism.
  • Emergency/egress navigation and map-matching — expressly described in the patent's Background as known concepts ("people … do not pass through walls… pass along corridors and through doorways"; "hotel exit floor map").
  • Real-estate, amusement-park, and transit information by location — mere intended-use recitations of location-tagged content delivery.
• Motivation: These are all the same known LBS feature categories the prior art already associated with proximity/positioning; the dependent claims merely enumerate applications, and "the mere recitation of an intended use or field of use" does not confer patentability.

7. Obviousness assessment by claim group

• Claim 1: Strong case for obviousness. Every structural limitation maps to admitted prior art or to JP 2001-116583. The claim is essentially a description of known Bluetooth/WLAN indoor-location practice with a conventional map-overlay navigation UI on a phone.
• Claims 2–5, 7, 10, 12–14: Very likely obvious — each adds a known LBS content type, a known waypoint-navigation feature, or a known environment, with no unexpected technical effect.
• Claim 6 (no GPS): Highlights rather than avoids the prior art — the entire point of the admitted Bluetooth/WLAN indoor-location art was operation without GPS.
• Claim 8: Purely a catalog of conventional venues ("mall … museum … subway … airport … covered structure") — an obvious field-of-use recitation.
• Claim 9 (parking/RTP): Obvious combination of known parking/car-locator functions with the admitted tag-positioning scheme; the specification itself describes these as conventional problems and solutions.
• Claim 11 (real estate): A predictable LBS content application; no new technical means beyond tag-ID-based location and content lookup.
• Claim 3(i) ("panic"): In addition to being obvious (emergency alerting was ubiquitous in mobile/security art), the claim text appears incomplete ("wherein said panic alert requests." — no object), which raises a separate § 112 definiteness issue.
• Claims 15–16: Text truncated in the available source; the visible portion of claim 15 (road-sign information delivered via RF-tag proximity on a display device) is the same tag-proximity method applied to outdoor roadside signage — an obvious extension of the same combination to regional/roadway tags, which the specification itself contemplates ("street or garage parking, inside or outside location," roadside beacons in the family's later patents). A definitive analysis requires full claim text.

8. Counterarguments the patentee would likely raise — and their weakness

1. "No communication needed" / direct tag-to-phone operation. While the combination of (a) fixed tags at known positions with (b) a phone computing its own position is not in any single reference, the KSR standard does not require a single reference. Bluetooth's inquiry mechanism inherently supports a phone discovering fixed tags, and the patent admits Bluetooth tags with unique IDs at known waypoints were already used for location. The "flip side" inversion is a design choice, not an inventive step.
2. Pre-arrival floor-plan download. The patentee may argue this is a distinct step. But pre-loading map data before entering an area was standard in vehicle navigation and in map/imagery download services (admitted art), and the claimed step of "downloading … prior to arriving" is simply scheduling a known download.
3. "Position marker overlay layered over the facility map." JP 2001-116583 and conventional navigation UIs already displayed location markers over maps; the admitted WLAN/BT location art was used with graphical client displays.
4. Secondary considerations. Based on the searches run for the litigation summary, no litigation, licensing, or industry copying of '580 was identified; the file history (filed 2006, granted 2014) suggests prolonged prosecution, consistent with claim narrowing. There is no evidence of long-felt need met, commercial success, or unexpected results that would overcome a prima facie obviousness showing.
5. Accuracy "within 10 feet." The patent itself attributes ~2 m (~6.5 ft) accuracy to known Bluetooth location systems, undermining any argument that the claimed accuracy is a new or unexpected result.

9. Bottom line

On the available record — dominated by the patent's own admissions — U.S. Patent No. 8,836,580's claims are vulnerable under § 103. Claim 1 reads as a straightforward application of admitted Bluetooth/Wi-Fi indoor-location technology (proximity detection and RSSI triangulation using fixed tags at known positions) to a cell-phone navigation display with a pre-downloaded floor plan and map overlay, each element traceable to pre-2005 art. The most powerful combination is the patent's own admitted Bluetooth/WLAN location art + JP 2001-116583 + conventional waypoint/map-overlay navigation, optionally with Ellenby '875 for POI content. Dependent claims 2–14 add conventional LBS feature sets and intended-use environments that a PHOSITA would have had ample motivation to add. Principal caveats: (i) I could not access the examiner-cited references or PTAB/PACER records in this session, so a complete challenge should confirm the file-wrapper citation list and full text of claims 15–16; (ii) any final opinion should be checked against the complete claim set and any prosecution-history estoppel from the 2006–2014 prosecution.