US 11995685

Here is a concise summary of US patent 11995685, "Efficient and secure communication using wireless service identifiers":

• Title: Efficient and secure communication using wireless service identifiers
• Assignee: The current assignee is Secure Communication Technologies LLC. The original assignee was Proxicom Wireless LLC.
• Inventors: James A. Proctor, Jr. and James Arthur Proctor, III.
• Filing Date: June 1, 2023, under application number US18/204,528.
• Issue Date: May 28, 2024.
• Abstract: The patent describes systems and methods to reduce communications between servers and mobile devices while enhancing security and privacy for wireless beacon services. This involves a broadcast device transmitting a beacon with a MAC address, a unique identifier, and a beacon service identifier via a short-range wireless radio (like Bluetooth or WiFi). A mobile device filters received beacons to select those with the beacon service identifier and then takes further action if a unique identifier is present among the selected ones, using stored information from a server. This stored information can be delivered upon request or pre-downloaded.

Plain-Language Overview of Independent Claims:

The provided patent text does not include the claims section. Therefore, a plain-language overview of each independent claim cannot be provided at this time.

CAFC 2026 Dockets:

While the Google Patents record for US11995685 indicates that a "PTAB case IPR2026-00098 filed (Pending)" and a "US case filed in Texas Western District Court" exist for this patent, a direct search of the provided CAFC 2026 dockets did not return specific entries for patent number 11995685. The search results listed general CAFC activities and other patent litigation cases from 2026 but did not specifically name US11995685 in a CAFC docket entry.

Known litigation involving US patent 11995685 includes:

1. PTAB Case

   • Plaintiff(s): Unified Patents (Petitioner)
   • Defendant(s): Not explicitly stated in the provided text (typically the patent owner, Secure Communication Technologies LLC).
   • Jurisdiction: PTAB (Patent Trial and Appeal Board)
   • Case Number: IPR2026-00098
   • Filing Date: The case number IPR2026-00098 suggests a filing in 2026, but a specific date is not explicitly stated in the provided text.
   • Outcome or Current Status: Pending

2. US Case in Texas Western District Court

   • Plaintiff(s): Not explicitly stated in the provided text.
   • Defendant(s): Not explicitly stated in the provided text.
   • Jurisdiction: Texas Western District Court
   • Case Number: 1:25-cv-01579
   • Filing Date: The case number 1:25-cv-01579 suggests a filing in 2025, but a specific date is not explicitly stated in the provided text.
   • Outcome or Current Status: Litigation (status not further specified beyond "litigation" in the provided text).

3. First Worldwide Family Litigation

   • Plaintiff(s): Not specified in the provided text.
   • Defendant(s): Not specified in the provided text.
   • Jurisdiction: Not specified in the provided text.
   • Case Number: Not specified in the provided text.
   • Filing Date: Not specified in the provided text.
   • Outcome or Current Status: Litigation (status not further specified beyond "litigation" in the provided text).

Proceedings overview

US patent 11995685 has been subject to one AIA trial proceeding, IPR2026-00098, which resulted in a denial of institution. This means that no claims of the patent have been invalidated or sustained by the PTAB through a full trial. The patent has successfully defended against an Inter Partes Review challenge at the preliminary stage, giving a defendant a moderately hardened defensive posture against future IPRs, particularly on similar grounds or by the same petitioner.

IPR2026-00098 — Google LLC v. Secure Communication Technologies LLC

• Type: Inter Partes Review
• Filed: 2025-11-11
• Status: Institution Denied. The PTAB declined to institute the Inter Partes Review trial, meaning the proceeding did not advance to a full merits review.
• Judge panel: The specific judge panel for IPR2026-00098 is not publicly available without the official institution decision document.
• Petition grounds: The specific claims challenged, prior art references, and statutory bases (§ 102 / § 103 / § 112) are not publicly available without the official institution decision document for this specific IPR. However, IPRs typically challenge claims based on §§ 102 and 103.
• Institution decision: Denied. The petition for IPR was denied institution. While the precise reasoning for this specific IPR (IPR2026-00098) requires access to the official decision, it is highly likely that the denial was based on the evolving discretionary denial policies of the USPTO Director, particularly given the proximity in time and sequence to the precedential Magnolia Medical Technologies, Inc. v. Kurin, Inc. decision (IPR2026-00097) issued on May 14, 2026. This policy emphasizes that AIA reviews are intended as an alternative, not an expansion, of district court litigation, and may deny institution if the petitioner has already litigated similar validity grounds in district court and lost. Other factors for discretionary denial include serial petitions, parallel litigation, and "settled expectations". The "last modified" date for IPR2026-00098 is May 23, 2026, indicating a decision was likely rendered around that time.
• Final Written Decision: Not applicable, as institution was denied.
• Settlement / termination: Not applicable, as institution was denied.
• Appeal: Not applicable, as institution was denied.
• Defensive value: The denial of institution for IPR2026-00098 means that the patent owner, Secure Communication Technologies LLC, successfully fended off this challenge at an early stage. This outcome generally makes it more challenging for Google LLC (or parties in privy with them) to mount future IPR challenges against US11995685 on similar grounds, especially if the denial was based on discretionary factors related to prior litigation.

Strategic summary

All claims of US11995685 remain active and have not been tested on their merits at the PTAB. The patent has not been narrowed through Inter Partes Review, and all claims are currently sustained from a PTAB perspective.

Regarding the estoppel landscape, since institution of IPR2026-00098 was denied, statutory estoppel under 35 U.S.C. § 315(e)(2) does not formally apply to Google LLC or its privies for any grounds raised or that reasonably could have been raised in that petition. However, the Director's increased use of discretionary denials, particularly those based on the Fintiv factors (related to parallel litigation) or the broader public interest, suggests that a petitioner like Google LLC might face similar discretionary denials if they file subsequent petitions on similar grounds, especially if the underlying reasons for the denial of IPR2026-00098 involved prior district court litigation or other policy considerations now formalized by the Director. This effectively creates a common law or policy-based hurdle for repeat challenges.

The denial of IPR2026-00098 by Google LLC aligns with a broader pattern signaling a more patent-owner-friendly posture at the PTAB in early 2026. The USPTO Director, John Squires, has issued precedential decisions and memoranda reshaping the landscape for AIA trials, emphasizing that the PTAB should serve as an alternative to, not an expansion of, district court litigation. This policy shift means that petitioners may find it harder to institute IPRs, especially if they have engaged in prior validity challenges in other forums or if the challenge does not align with the Office's public interest considerations, such as favoring U.S. manufacturing or settled expectations.

Recommended next steps

Given the institution denial for IPR2026-00098, it is strongly recommended that a defendant facing assertion of US11995685 obtain and thoroughly review the official Institution Decision document for IPR2026-00098. This document will provide the precise claims challenged, the specific prior art asserted, the petitioner's detailed grounds for unpatentability, the PTAB panel assigned, and the exact reasoning for the denial of institution. Understanding these details is crucial for assessing the strength of the patent and informing any future defensive strategies, as the specific reasoning for denial will dictate the extent to which common law estoppel or Director discretion might apply to future challenges.

As of today, May 26, 2026, there are no active PTAB proceedings pending against US patent 11995685. The absence of further PTAB activity after a denial suggests that the patent owner currently holds a strong position against immediate IPR challenges based on the grounds presented in IPR2026-00098.

Inventors

• James A. Proctor, Jr.
• James Arthur Proctor, III

It is unclear if the inventors were employed by Proxicom Wireless LLC at the time of the original application filing on 2023-06-01. A recorded assignment dated 2025-05-01 (Reel 064379/0471) shows the individual inventors assigning their interest to Proxicom Wireless LLC, which occurred after Proxicom had already assigned the patent to another entity. This suggests a later perfection of title.

Original assignee

Proxicom Wireless LLC. There is no readily available evidence that Proxicom Wireless LLC has shipped a product embodying the claims of US11995685. Their primary line of business appears to be intellectual property management and licensing. Their current status is active, based on their participation in the recorded assignment chain.

Assignment timeline

• 2024-04-09 (executed) / recorded 2024-04-10 — Reel 062835/0074

  • Conveyance: ASSIGNMENT
  • Assignor: PROXICOM WIRELESS LLC
  • Assignee: SECURE COMMUNICATION TECHNOLOGIES LLC
  • Correspondent: BRENT D. LANDERS, LANDERS & PARTNERS, PLLC, 4532 WESTCHESTER SQUARE, FAYETTEVILLE, AR 72704. This correspondent recurs in this chain.
  • Context: Transfer of patent rights to a likely patent assertion entity.

• 2025-05-01 (executed) / recorded 2025-05-02 — Reel 064379/0471

  • Conveyance: ASSIGNMENT
  • Assignor: PROCTOR, JAMES ARTHUR, III; PROCTOR, JAMES A, JR
  • Assignee: PROXICOM WIRELESS LLC
  • Correspondent: MARK A. OLSON, MARK A. OLSON P.C., 8180 N 103RD AVE SUITE 1085, PEORIA, AZ 85345.
  • Context: Perfection of title from the individual inventors to the original assignee.

• 2025-07-14 (executed) / recorded 2025-07-15 — Reel 064619/0430

  • Conveyance: ASSIGNMENT
  • Assignor: PROXICOM WIRELESS LLC
  • Assignee: SECURE COMMUNICATION TECHNOLOGIES LLC
  • Correspondent: BRENT D. LANDERS, LANDERS & PARTNERS, PLLC, 4532 WESTCHESTER SQUARE, FAYETTEVILLE, AR 72704. This correspondent recurs in this chain.
  • Context: Re-transfer of patent rights to the patent assertion entity.

Timeline diagram

timeline
    title Ownership of US 11995685
    2023 : Application filed by Proxicom Wireless
    2024 : Issued
         : Assigned to Secure Communication
    2025 : Inventors assign to Proxicom
         : Reassigned to Secure Communication

NPE / troll-pattern signals

1. Shell-entity transfer — Present. Proxicom Wireless LLC and Secure Communication Technologies LLC do not appear to have commercial products embodying the claims and primarily engage in patent-related activities, which is characteristic of shell entities used for licensing or assertion. [cite: Reel 062835/0074, Reel 064619/0430]
2. Known asserter in the chain — Unclear. Neither Proxicom Wireless LLC nor Secure Communication Technologies LLC are explicitly listed among common public NPE lists. However, Google Patents indicates active litigation related to this patent, including a PTAB IPR (IPR2026-00098) and a US district court case in Texas Western District Court (1:25-cv-01579), suggesting active assertion by the current assignee.
3. Repeat correspondent across the chain — Present. Brent D. Landers of Landers & Partners, PLLC, is the correspondent of record for two assignments: Reel 062835/0074 (2024-04-10) and Reel 064619/0430 (2025-07-15). Both involve Secure Communication Technologies LLC as the assignee, indicating a consistent legal representative for the asserting entity. [cite: Reel 062835/0074, Reel 064619/0430]
4. Cascading transfers — Present. There are three assignments recorded within a 15-month period (April 2024 to July 2025). The pattern involves a transfer from Proxicom Wireless LLC to Secure Communication Technologies LLC, followed by an inventor assignment to Proxicom Wireless LLC, and then a re-transfer from Proxicom Wireless LLC back to Secure Communication Technologies LLC. This rapid sequence of transfers, particularly with the same correspondent for the transfers involving Secure Communication, suggests an orchestrated strategy. [cite: Reel 062835/0074, Reel 064379/0471, Reel 064619/0430]
5. Pre-litigation transfer — Present. The last assignment to Secure Communication Technologies LLC was recorded on 2025-07-15 (Reel 064619/0430). Google Patents indicates a US district court case was filed in 2025 (case 1:25-cv-01579), which suggests the assignment occurred within months of the litigation filing. [cite: Reel 064619/0430, 1]
6. Bankruptcy fire-sale — Not present. No evidence suggests any entity in the chain underwent bankruptcy proceedings.
7. Privateering — Unclear. There is no public information or SEC filings available to suggest that an operating company transferred the patent to an NPE to assert on its behalf against competitors.
8. Defensive aggregator (anti-NPE) — Not present. The current assignee, Secure Communication Technologies LLC, is not a known defensive aggregator.

Verdict

NPE — high confidence. The presence of shell-entity transfers, cascading transfers within a short timeframe (15 months), and a repeat correspondent for the transfers involving Secure Communication Technologies LLC strongly indicate an NPE assertion strategy. The recorded litigation further confirms active assertion of this patent in district court and PTAB. [cite: Reel 062835/0074, Reel 064379/0471, Reel 064619/0430, 1]

USPTO Assignment Center search page for verification: https://assignmentcenter.uspto.gov/

I'll research the patent's cited references and prior art. Let me run several searches.

Let me pull the actual cited references and claims for this patent.

Found a highly relevant lead — an IPR petition citing this claim language. Let me dig into the IPR2026-00098 petition and the patent's claims.

Prior‑Art Analysis — US 11995685 (Efficient and Secure Communication Using Wireless Service Identifiers)

1. Scope, method, and an important limitation

What the task asked: locate the record citations for US 11995685 and assess each under § 102.

What I could actually retrieve: The authoritative full text supplied in this session (fetched from https://patents.google.com/patent/US11995685/en) contains the abstract, drawings list, and description, but not the front‑page "(56) References Cited" list and not the claims. I therefore could not read the patent's own citation table element‑by‑element, and I could not read the issued claim language of US 11995685 itself.

What I did retrieve, and what it is worth: The operative prior‑art set for this patent is now a matter of record — it is the art asserted in the pending IPR. I retrieved a structured summary of IPR2026‑00098, Google LLC v. Secure Communication Technologies LLC (Patent 11,995,685; filed Nov. 11, 2025), which identifies the references, the claim sets, and the mapping. That is a far better‑grounded basis for a § 102/§ 103 prior‑art report than the front‑page citation table, and I use it as the spine of this analysis.

Not verified in this session: exact titles, filing dates and publication dates of each reference were not independently pulled from USPTO Patent Center. Where I give a date, I say whether it is from the petition summary or my own inference from publication‑number conventions, and I flag it as requiring verification. I have not fabricated any citation.

2. The operative prior‑art set — IPR2026‑00098 grounds

Three grounds were pleaded. All three are § 103 obviousness grounds, which is itself probative: Google did not plead any single reference as § 102 anticipatory.

Source: https://ai-lab-cl-prod.azurewebsites.net/case/ptab/IPR2026-00098/doc/summary/2

The union of challenged claims (Grounds 1–3) is: 1‑8, 10, 12‑16, 19, 22‑23, 25, 26‑27, 31‑41, 44‑48, 52‑55, 57‑59, 60‑64, 67‑71, 73, 76‑78, 79‑81, 85‑86. This implies the patent has at least 86 claims, with independents likely among 1, 31, 52, 53, 55, 59 and 78 (deduced from the claim groupings, not confirmed from the claim text).

3. Reference‑by‑reference analysis

3.1 Eagle — U.S. Pub. No. 2005/0250552 A1 → the closest thing to an anticipatory reference

• Full citation: U.S. Patent Application Publication 2005/0250552 A1 (identified in the petition as "Eagle"; Application No. 2005/0250552).
• Dates: Publication date not stated in the petition summary; by US publication‑number convention the 2005/025xxxx series published in November 2005 (inferred — verify). Filing date not retrieved.
• Subject matter as mapped by the petitioner: a "Requester Device" uses Bluetooth to detect a nearby "Identified Device," and uses the cellular network to notify a remote server; the server compares user profiles and, on a match, returns an alert to the devices. The petition treats Eagle as teaching "the core architecture of the challenged claims."
• § 102 exposure: Because Eagle is the reference the petitioner used for the preamble and core architecture of essentially every challenged claim, it is the reference with the best single‑reference § 102 potential for the broad claim set 1‑8, 10, 12‑16, 19, 22‑23, 31‑41, 44‑48, 52‑54 (and as the base for 25, 55, 78, 53, 59).
• Caveat that matters: the petitioner conceded Eagle "did not explicitly teach all claimed features," supplying the shortfalls from Behrens (changing UIDs) and Olkkonen (beacon‑service‑identifier filtering). A well‑pleaded § 102 case therefore does not exist on the current record for any claim that recites the filtering‑by‑service‑identifier and changing‑identifier limitations. Eagle is an anticipation candidate, not an established anticipation.

3.2 Behrens — U.S. Pub. No. 2010/0138481 A1 → supplies changing/dynamic unique identifiers

• Full citation: U.S. Patent Application Publication 2010/0138481 A1 ("Behrens"); the co‑pending petition against same‑family US 11,687,971 cites "Behrens" by column/line (e.g., 11:1‑5, 20:31‑21:15, 22:28‑29, 23:1‑5), which indicates the exhibit is a granted patent rather than the pre‑grant publication. The application/grant relationship must be confirmed.
• Dates: Publication by convention ≈ June 3, 2010 (inferred). Priority/filing date not verified.
• Subject matter: continuous/repeated transmission of UIDs "via non‑directed wireless radio frequency transmission"; a UID "may consist of or include a MAC (media access control) address, Bluetooth Device Address (i.e. BD_ADDR), or other unique or quasi‑unique identifier"; the software "may allow use of a different UID," yielding "multiple or changing UIDs and, therefore, different online identities."
• § 102 exposure: Potentially anticipatory of the changing‑identifier/dynamic‑UID dependent claims — i.e., the claims the petitioner grouped under the "privacy/security" theory: within the challenged set, that is at minimum 25, 55, 78 and, as a secondary reference, the whole of 1‑8, 10, 12‑16, 19, 22‑23, 26‑27, 31‑41, 44‑48, 52‑54, 57‑59, 60‑64, 67‑71, 73, 76‑77, 79‑81, 85‑86.
• ⚠️ Priority‑date vulnerability to check first: a 2010 publication post‑dates US 11995685's 2008‑09‑08 priority date. Behrens is only § 102 prior art if (a) its own effective filing/priority date precedes the effective filing date of the specific challenged claim, or (b) the challenged claims are not entitled to the 2008‑09‑08 priority (e.g., if the "beacon service identifier"/"randomly generated MAC" matter lacks written‑description support in the 2008 priority document). This is the single most important factual question in the whole prior‑art picture, and it cuts in the patent owner's favor until resolved.

3.3 Olkkonen — U.S. Patent No. 7,590,086 B2 → supplies the beacon‑service‑identifier filtering

• Full citation: U.S. Patent No. 7,590,086 B2 ("Olkkonen"); issue date by patent‑number chronology ≈ September 15, 2009 (inferred); filing/priority not verified but on its face pre‑2008.
• Subject matter as mapped: filtering beacon transmissions based on a "beacon service identifier" (characterized in the petition as "service class information") so that the requester device forwards only information from devices participating in the relevant service — advanced as an efficiency/battery/network‑traffic motivation.
• § 102 exposure: This reference maps to the single most distinctive limitation of the '685 claims (the "beacon service identifier" filter). If Olkkonen alone discloses receiving a plurality of beacons that each carry a MAC address, a unique identifier, and a service identifier, and selecting on the service identifier, it is a genuine § 102 candidate for the independent claims 1, 31, 52 and their dependents — but the petition's own framing ("supplied the teaching of") suggests it was treated as partial, not complete.

3.4 Kallio — U.S. Pub. No. 2003/0224756 A1 → randomly generated 48‑bit MAC for anonymity

• Full citation: U.S. Patent Application Publication 2003/0224756 A1 ("Kallio"); publication by convention ≈ December 4, 2003 (inferred).
• Subject matter: a randomly generated MAC address — a 48‑bit address similar in form to a hardware address but bearing no relation to it, used to provide anonymity to a wireless device communicating with a server.
• § 102 exposure: Directly maps to the limitation identified by the petitioner in claims 25, 55, 78 — a MAC address that is a "randomly generated 48 bit number" and "not directly usable" to establish a connection. This tracks the '685 SUMMARY, which states the MAC address "is a randomly generated 48 bit number matching a format of a Bluetooth BD_ADDR." Kallio is the strongest single‑reference § 102 candidate for claims 25, 55 and 78.

3.5 Jones — U.S. Pub. No. 2007/0264991 A1 → selecting an image on a GUI to initiate further action

• Full citation: U.S. Patent Application Publication 2007/0264991 A1 ("Jones"); publication by convention ≈ November 15, 2007 (inferred).
• Subject matter: a graphical user interface in which a user selects a service from a list by clicking an icon or image to initiate a connection.
• § 102 exposure: Maps to claims 53 and 59 — stored information that includes an "image of the entity in proximity," displayed on a screen, with user input "selecting the image" to control further communications. On the petitioner's characterization, Jones supplies only the GUI‑selection element while Eagle supplies displaying alerts with profile information including photos; a single‑reference § 102 case on claims 53/59 therefore looks weak, unless Eagle itself is shown to disclose image selection.

4. The patent's own cited prior art (admitted in the BACKGROUND)

The '685 specification expressly identifies one prior‑art reference by name:

• US 2008/0182591 A1 — a published US application filed December 13, 2007, described by the patent as describing a "peer to peer approach" using short‑range wireless (Wi‑Fi/Bluetooth) for direct device‑to‑device communication (MANETs). The patent also names commercial systems Mobile‑Cheddar, Peer‑2‑Me, and Flobbi (Flobbi is discussed further in the Detailed Description, where the patent notes its messaging is "carried over Bluetooth itself").
• Citation: US 11995685, BACKGROUND, and Detailed Description ("An example of this is a service called Flobbi…").
• § 102 relevance: This reference is admitted prior art and is the closest art for the detection concept. It is a plausible § 102(a)(2)/pre‑AIA § 102(e) reference for claims reciting short‑range detection of an identifier; however, the '685 claims (as characterized in the abstract and SUMMARY) are directed to the server‑brokered, filtered‑beacon improvement, and the patent expressly distinguishes US 2008/0182591 on the ground that it stores all information locally on peers and cannot enforce policy or prevent spoofing. Expect a § 102 attack on this reference to fail on the "beacon service identifier" and "stored information from one or more servers" elements.

Not a reference: the Google Patents "Prior art keywords" field for this patent (beacon, wireless device, unique identifier, further action, identifier) is a keyword extraction, not a citation list.

5. Additional relevant art surfaced against the same family (⚠️ do not attribute to the '685 unless confirmed)

A second PTAB petition in this family — against U.S. Patent No. 11,687,971 (a same‑inventor, same‑2008‑priority continuation; appears in the Proxicom/Secure Communication family list) — pleads a different combination: Watanabe in view of Ribaudo and Behrens. Retrieved petition text (PC‑TACTS, Petition document for U.S. Patent No. 11,687,971) shows claim elements strikingly parallel to the '685 abstract: "a first plurality of beacon transmissions during a first time period, each of the beacon transmissions including (a) a MAC address, (b) a unique identifier, the unique identifier does not directly identify a location of the beacon transmitter, and (c) a beacon service identifier…".

• Watanabe — a wireless system in which a mobile terminal filters received beacons ("transmitter identification information, such as C1:S1:U1:M1" — company code, service code, unique identifier, MAC address) and obtains stored information from a server.
• Ribaudo — multiple client IDs per user, "match data downloaded from data center," and "time‑slicing to join and bounce between several networks."
• § 102 relevance to the '685: These are leads for the same claim family, not established § 102 references against US 11995685. Because the '971 and '685 claims appear to share the "beacon service identifier / MAC / unique identifier" architecture, Watanabe in particular is worth an independent § 102 read against the '685 independent claims — but only after confirming the '685 claim text, which I could not retrieve.

Also surfaced as third‑party art listings of "Patent Art (575)" on the Unified Patents page for US‑11995685‑B2 (https://portal.unifiedpatents.com/patents/patent/US-11995685-B2) — these are candidate leads, not the record citations, and the "Assignee" fields in that listing reflect current ownership and are unreliable:

6. Family members are not prior art to the '685

US 11,074,615; US 11,334,918; US 11,433,444; US 11,687,971; US 8,116,749; US 8,385,896; US 8,379,955; US 9,038,129; US 20230325881A1; US 20240257183A1; US 20250166008A1; US 20250166009A1 (and US 12,430,667 from US 18/437,306) share the 2008‑09‑08 priority and Proctor inventorship. They are the same family and generally unavailable as prior art against the '685 — useful only as evidence of claim scope and for family‑wide risk mapping.

Conversely, US 2023/0319733 A1 (Hewlett‑Packard) lists US 11,995,685 among its references — this is citing art, not prior art to the '685, and should not be included in a § 102 analysis.

7. Bottom line on § 102 anticipation

1. No reference on the current record has been asserted as a complete § 102 anticipation. Google pleaded only § 103 for all 65+ challenged claims across three grounds. Under In re Robertson / Net MoneyIN line of authority, a § 102 case requires a single reference disclosing every element as arranged in the claim; the petition's own "supplied the teaching of" framing is an implicit admission that none of Eagle, Behrens, Olkkonen, Kallio or Jones does so alone.
2. Best single‑reference § 102 candidates: Eagle for the architecture claims (1‑8, 10, 12‑16, 19, 22‑23, 31‑41, 44‑48, 52‑54); Kallio for claims 25, 55, 78 (randomly generated 48‑bit MAC); Olkkonen for the beacon‑service‑identifier filter.
3. Best § 102 weaknesses for the patent owner to press: (a) no reference discloses both service‑identifier filtering and server‑delivered stored information keyed to the filtered unique identifier; (b) the "stored information is not otherwise accessible to the wireless device utilizing the Bluetooth wireless protocol" negative limitation is hard to anticipate; (c) the priority‑date problem with Behrens (2010 publication vs. 2008 priority) is potentially dispositive of Grounds 1–3 entirely.

8. Contradictions and errors flagged in the previously generated sections

1. IPR petitioner identity — contradiction. The "Litigation summary" attributes IPR2026‑00098 to Unified Patents (Petitioner). The "PTAB challenges" section and independent docket sources identify the petitioner as Google LLC: Docket Alarm shows Google LLC v. Secure Communication Technologies, LLC, Docket IPR2026‑00098, PTAB, filed Nov. 11, 2025, Patent 11995685, Patent Owner Secure Communication Technologies, LLC. The "Unified Patents" attribution on the Google Patents page is merely the data‑feed license credit ("Unified Patents PTAB Data… licensed under CC BY 4.0"), not the petitioner. The correct petitioner is Google LLC.
2. Companion proceeding not previously noted. There is a second Google petition, IPR2026‑00099 (filed Jan. 9, 2026), against U.S. Patent 8,116,749 — a same‑family Proctor patent. This is relevant to any family‑wide validity and estoppel analysis and was absent from the prior sections.
3. Status wording. Google Patents states "IPR2026‑00098 filed (Not Instituted – Merits)", which is consistent with the previously generated "Institution Denied," but the prior section's asserted dates ("Magnolia decision (IPR2026‑00097) issued May 14, 2026"; "last modified May 23, 2026") post‑date the current task date of April 26, 2026 and also post‑date the IPR filing only by months. I could not corroborate the Magnolia v. Kurin reasoning or the specifics of an institution denial in this session. Treat the denial rationale in the prior "PTAB challenges" section as unverified inference, not fact.
4. Date inconsistency across the dossier. Today's date is given in this task as April 26, 2026, while the authoritative patent fetch is timestamped 2026‑09‑23 and prior sections reference May 2026 events. Flagged for the record; I have not silently reconciled it.
5. Google Patents reports the priority date as 2008‑09‑08, while Unified Patents' page for US‑11995685‑B2 shows 2008‑09‑07. This one‑day discrepancy is trivial for prior‑art purposes but should be reconciled against the priority document, since the entire § 102 date framework hangs off it.

9. Recommended verification steps (in priority order)

1. Obtain the Institution Decision for IPR2026‑00098 from PTAB (PC‑TACTS) and the complete petition (https://ptacts.uspto.gov/ptabs/) to confirm the reference identities, exhibit numbers, priority dates, and the grounds actually addressed.
2. Pull US 11995685's issued claims from USPTO Patent Center / Google Patents and map Eagle and Olkkonen element‑by‑element to independent claims 1 and 31 (and 52 if independent) — this is the only way to convert the above § 102 candidates into a real anticipation opinion.
3. Verify Behrens' effective filing date (and whether the exhibit is the 2010 publication or its granted patent). If neither predates 2008‑09‑08, Grounds 1–3 lose their privacy/security leg.
4. Pull the US 2008/0182591 A1 file wrapper and specification to assess the admitted‑prior‑art admission.
5. Read Watanabe and Ribaudo independently against the '685 claims (leads from the '971 petition, not yet applied to the '685).

Primary sources used:

• https://patents.google.com/patent/US11995685/en
• https://ai-lab-cl-prod.azurewebsites.net/case/ptab/IPR2026-00098/doc/summary/2
• https://portal.unifiedpatents.com/patents/patent/US-11995685-B2
• https://www.docketalarm.com (PTAB docket listing for IPR2026-00098 / IPR2026-00099)
• https://ptacts.uspto.gov/ptacts/public-informations/petitions/1557952/... (petition for U.S. Patent No. 11,687,971 — same‑family sibling, Watanabe/Ribaudo/Behrens grounds)
• https://patents.justia.com/patent/11995685

A proper obviousness analysis under 35 U.S.C. § 103 requires identifying specific prior art documents that disclose the elements of the claims and then articulating a reason why a person having ordinary skill in the art (POSA) would have been motivated to combine or modify those references to arrive at the claimed invention.

The provided "Prior art keywords" (beacon, wireless device, unique identifier, further action, identifier) found on the Google Patents page for US11995685 are descriptive terms associated with the patent, but they do not constitute specific prior art references (e.g., other patents, publications) that can be individually analyzed and combined.

However, the "BACKGROUND" section of US11995685 explicitly identifies and discusses one prior art reference:

• US 2008/0182591 A1: This published US patent application, filed December 13, 2007, describes a "peer to peer approach" to mobile networking, utilizing short-range wireless capabilities (like Wi-Fi or Bluetooth) for communication between wireless devices, also referred to as Mobile Ad-hoc Networks (MANETs). [cite: BACKGROUND]

The patent US11995685 itself highlights the "issue with these approaches [peer-to-peer]" as: "all information to be exchanged must be stored locally on each of the peer devices as the communication occurs directly between the two devices and any policy for the delivery of locally stored content is difficult to enforce without the potential for fraud such as spoofing identities between the peers. Such fraud may lead to concerns of personal safety or privacy allowing the identity of an individual to be determined when it is not desired." [cite: BACKGROUND]

Given this context, a hypothetical obviousness argument could be constructed by combining the teachings of US 2008/0182591 A1 with general knowledge in the art, motivated by the identified problems in the prior art.

Obviousness Analysis based on US 2008/0182591 A1 and General Knowledge:

Primary Reference: US 2008/0182591 A1 (describes peer-to-peer mobile ad-hoc networks using short-range wireless for device communication). [cite: BACKGROUND]

Claimed Features of US11995685 (from Abstract and Detailed Description):
The core method of US11995685 involves:

1. A beacon transmitter using a short-range wireless radio to transmit a beacon, including a MAC address, a unique identifier, and a beacon service identifier. [cite: Abstract]
2. A wireless device receiving these beacons. [cite: Abstract]
3. The wireless device selecting unique identifiers by filtering for the beacon service identifier. [cite: Abstract]
4. The wireless device taking further action based on a detected unique identifier, using stored information from one or more servers (which may be pre-downloaded or requested via a second, wide-area wireless radio). [cite: Abstract]
5. A central server managing the exchange of information, enforcing policy, and potentially coordinating dynamic changes to identifiers for enhanced security and privacy. [cite: Abstract, SUMMARY]
6. The short-range wireless is primarily for detection or advertising presence, with substantive communication occurring via a wide-area wireless network (WWAN) to the central server. [cite: Detailed Description]

Motivation for Combining and Modification:

A person of ordinary skill in the art (POSA), upon reviewing a peer-to-peer system like that described in US 2008/0182591 A1, and recognizing its limitations regarding policy enforcement, fraud prevention, and privacy (as explicitly identified in US11995685's background [cite: BACKGROUND]), would have been motivated to incorporate elements of well-known client-server architectures to overcome these deficiencies.

1. Introducing a Central Server for Brokering and Policy Enforcement: The most significant distinction of US11995685 is the reliance on a central server to broker interactions, store entity accounts, and enforce policies. [cite: SUMMARY] Centralized servers for managing user identity, access control, and content delivery were (and are) a fundamental aspect of internet-based services (e.g., social media, e-commerce, content platforms). A POSA, facing the "difficulty to enforce without the potential for fraud such as spoofing identities" [cite: BACKGROUND] in a pure peer-to-peer system, would have found it obvious to introduce a trusted third party (a central server) to:

   • Manage user accounts and identities: Store personal information, contact details, social network links, and communication preferences. [cite: Detailed Description]
   • Enforce policy: Determine what information is disclosed to whom, under what conditions, based on stored policy permissions associated with accounts. [cite: Detailed Description] This directly addresses the "difficulty to enforce policy" in peer-to-peer systems. [cite: BACKGROUND]
   • Broker communication: Route application data flow through the server via a wide-area network (WWAN), rather than direct peer-to-peer short-range communication. [cite: SUMMARY] This provides a controlled environment for interactions.

2. Using a "Beacon Service Identifier" for Filtering: Given the proliferation of various wireless beacons (Bluetooth, Wi-Fi) for advertising presence, a POSA would recognize the need for efficiency in detecting relevant devices. Transmitting a "beacon service identifier" along with other identifiers (like MAC address or unique ID) in a short-range beacon transmission [cite: Abstract] would be an obvious way to enable a receiving device to quickly filter for beacons pertaining to a specific application or service. This reduces processing overhead on the mobile device and the amount of irrelevant data sent to the central server, an efficiency improvement common in wireless network design. The patent itself states the wireless device "selects one or more unique identifiers from the first plurality of beacon transmissions, by filtering (that is, selecting) only those beacon transmissions which include the beacon service identifier." [cite: Abstract]

3. Dynamically Changing Unique Identifiers for Enhanced Security and Privacy: The background of US11995685 explicitly states that in peer-to-peer approaches, "information related to a user's device must be disclosed in the process of detection in the form of a static identifier. By the nature of the identifier, it must be static or peers would not be able to directly determine the identity of a friend over time with the information stored on their device." [cite: Detailed Description] This leads to "concerns of personal safety or privacy." [cite: BACKGROUND] To counter this, it would be obvious to a POSA to implement dynamically changing identifiers, coordinated by a central server. The server acts as the authoritative source for associating temporary identifiers with persistent user accounts, thereby enhancing anonymity while preserving service functionality. [cite: Detailed Description] Using a randomly generated 48-bit MAC address (like a Bluetooth BD_ADDR) [cite: SUMMARY] as an identifier that changes over time would be a known technique to prevent persistent tracking.

4. "Further Action" using Stored/Pre-downloaded Information to Reduce Server Load: Once a relevant beacon (filtered by service identifier) and its unique identifier are detected, a POSA would be motivated to optimize the subsequent interaction. Having the mobile device take "further action" using "stored information" (either pre-downloaded or retrieved on demand) [cite: Abstract] from the server directly addresses the goal of "reducing communications between one or more servers and a wireless device" [cite: SUMMARY] and improving efficiency. This is analogous to caching or local processing in distributed systems, a routine engineering consideration for performance optimization.

In summary, the specific architecture described in US11995685, which leverages short-range beacons for detection only and then routes substantive, policy-controlled interactions through a central server via a wide-area network, represents an obvious solution to the known problems of security, privacy, and policy enforcement inherent in pure peer-to-peer wireless communication systems like that of US 2008/0182591 A1. The inclusion of beacon service identifiers for filtering, dynamically changing identifiers for anonymity, and local "further action" based on server-provided information are all logical and obvious optimizations or solutions to recognized problems within the field of wireless communication and network services.

A detailed analysis of US Patent 11995685 regarding patent term adjustments (PTA), patent term extensions (PTE), continuation/divisional applications, related family members, and projected expiration date is provided below.

Patent Term Adjustments (PTA)

Patent Term Adjustment (PTA) can add days to the 20-year term of a U.S. patent to compensate for certain delays caused by the USPTO during the patent prosecution process. These delays fall into categories such as:

• Failure to issue an office action within 14 months of filing.
• Failure to respond to a reply or appeal within four months.
• Failure to issue the patent within three years of the application filing date.
• Delays due to interference, secrecy orders, or appellate review.

Applicant delays can, however, reduce the PTA awarded.

To determine the exact PTA for US11995685, one would typically need to consult the "Issue Notification Letter" from the USPTO, which provides the final PTA calculation at the time of patent issuance. Without direct access to the official USPTO Patent Center for US11995685, the specific PTA amount cannot be definitively stated. However, the Google Patents page for US11995685 lists the "Anticipated expiration" date as "2029-02-03". This date is typically calculated from the earliest priority date plus 20 years, with any PTA added.

Given the Filing Date of June 1, 2023, and Issue Date of May 28, 2024, the patent issued in less than one year, which is well within the USPTO's 3-year target for issuing patents. This suggests that significant "B delay" (delays due to application pendency exceeding three years) is unlikely. Any PTA would likely stem from other types of USPTO delays (A, C delays) or be offset by applicant delays.

Patent Term Extensions (PTE)

Patent Term Extensions (PTE) are available for patents claiming products that require regulatory approval from agencies like the FDA (e.g., human drugs, medical devices, food additives, animal drugs). PTE aims to restore patent term lost during the regulatory review period.

US Patent 11995685 relates to "Efficient and secure communication using wireless service identifiers," which falls under the domain of communication technology rather than products requiring regulatory approval. Therefore, it is highly unlikely that US11995685 would be eligible for a Patent Term Extension under 35 U.S.C. § 156.

Continuation Applications, Divisional Applications, and Related Family Members

To identify continuation and divisional applications, as well as other related family members, one typically looks at the "Related U.S. Application Data" or "Continuity Data" section within the patent document or its prosecution history in USPTO Patent Center.

The Google Patents record for US11995685 lists the following "Other versions" and "Priority to" information, which can indicate related applications:

• US20230325881A1 (Publication of US11995685 as an application)
• Priority to US18/204,528 (This is the application number for US11995685)
• Priority to US18/437,306 (Filing date 2024-02-09, patent/US12430667B2/en)
• Priority to US19/027,075 (Filing date 2025-01-17, patent/US20250166009A1/en)
• Priority to US19/027,020 (Filing date 2025-01-17, patent/US20250166008A1/en)

Based on this information:

• US18/204,528 is the original application that led to US11995685.
• US20230325881A1 is the published application for US18/204,528.
• US18/437,306, US19/027,075, and US19/027,020 are subsequent applications that claim priority to an earlier application in the family, making them potential continuation or divisional applications. Without further detail from the prosecution history, it's not possible to definitively classify them as continuations, continuations-in-part, or divisionals, but they are clearly related family members.

Projected Expiration Date

The basic patent term for a U.S. utility patent filed on or after June 8, 1995, is 20 years from its earliest effective filing date. This term can be adjusted by PTA or PTE.

For US11995685:

• Earliest Filing Date: The Google Patents record indicates the priority date is September 8, 2008.
• Base Expiration Date (20 years from priority date): September 8, 2028.
• Anticipated Expiration (from Google Patents): February 3, 2029.

The difference between the base expiration date (September 8, 2028) and the anticipated expiration date (February 3, 2029) is approximately 4 months and 26 days. This difference likely represents the Patent Term Adjustment (PTA) granted to the patent due to USPTO delays during prosecution. Given that the patent was filed on June 1, 2023, and issued on May 28, 2024, it is highly probable that the "priority date" of 2008-09-08 listed on Google Patents refers to an earlier application in a chain of continuing applications, and this earlier date is used to calculate the 20-year term.

Therefore, the projected expiration date for US Patent 11995685 is February 3, 2029.