IP Library › Granted Patent US 12,732,293
Granted Patent B2
US 12,732,293 · App. 18/605,422 · Granted Sep 8, 2026

Systems and methods for watermarking time, place and identity of events

Inventor: Richard Hoptroff (London, GB)
Assignee: Hoptroff London Limited
H04J3/0655G06N20/00H04J3/0644H04J3/065H04J3/0667H04W4/029H04W56/0015
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,732,293
App. No.
18/605,422
Filed
Mar 14, 2024
Granted
Sep 8, 2026
Kind
B2
Examiner
DUONG, FRANK
Art Unit
2474
USPC
370/503
Abstract

The present disclosure provides systems and methods for proving an event. The system comprises a network of one or more beacon nodes and each beacon node is configured to: receive a request over the network for proving a time and location for an event, and the request comprises event data generated by a requesting entity; create a timestamp for the event using a clock of the beacon node, wherein the clock is synchronized to a trusted time source; generate a hash code for the timestamp and the event data and record the hash code to a ledger at the beacon node.

Claims (31)

1 . A computer-implemented method for proving an event comprising:

(a) receiving, at a beacon node, a request for proving a time and location for an event, wherein the request comprises event data generated by a requesting entity;

(b) creating a timestamp for the event using a clock of the beacon node, wherein the clock is synchronized to a trusted time source to establish a proof of the time for the event;

(c) generating an estimated location of the requesting entity to establish a proof of location for the event;

(d) generating a hash code for the timestamp and the event data; and

(e) recording the hash code to a ledger at the beacon node.

2 . The computer-implemented method of claim 1 , wherein the request further comprises a location data about the event.

3 . The computer-implemented method of claim 2 , wherein the proof of the location for the event is established by determining a probability that the location data is correct based on the estimated location.

4 . The computer-implemented method of claim 3 , wherein the probability is generated using a machine learning algorithm trained model.

5 . The computer-implemented method of claim 1 , wherein the proof of location for the event is based on multiple estimated locations generated by multiple beacon nodes.

6 . The computer-implemented method of claim 1 , wherein the estimated location is an estimated distance or location vector that is obtained using a route probing method or based on the Received Signal Strength Indication (RSSI).

7 . The computer-implemented method of claim 6 , wherein the estimated distance or location vector is obtained from multiple of the beacon nodes that receive the request from the requesting entity.

8 . The computer-implemented method of claim 2 , wherein the trusted time source comprises a grandmaster clock receiving a GNSS or GPS time signal.

9 . The computer-implemented method of claim 2 , wherein the clock is synchronized using a PTP or NTP protocol.

10 . The computer-implemented method of claim 2 , wherein the event data comprises hashed data of an event document.

11 . The computer-implemented method of claim 2 , wherein the timestamp is generated at the time of receiving the request.

12 . The computer-implemented method of claim 1 , wherein the hash code is generating by combing previously hashed events data.

13 . The computer-implemented method of claim 2 , further comprising creating, by the requesting entity, a watermark based on the timestamp, the estimated location and the hashed event data sent from the beacon node.

14 . The computer-implemented method of claim 1 , wherein the requesting entity is configured to record a hashed value of the event data to a hash-chain managed by the requesting entity.

15 . A system for proving an event comprising:

a network of beacon nodes, wherein at least one of the beacon nodes is configured to:

a) receive, at a beacon node, a request for proving a time and location for an event, wherein the request comprises event data generated by a requesting entity;

b) create a timestamp for the event using a clock of the beacon node, wherein the clock is synchronized to a trusted time source to establish a proof of the time for the event;

c) generate an estimated location of the requesting entity to establish a proof of location for the event;

d) generate a hash code for the timestamp and the event data; and

e) record the hash code to a ledger at the beacon node.

16 . The system of claim 15 , wherein the event data includes hashed data of an event document.

17 . The system of claim 15 , wherein the request further comprises a location data about the event.

18 . The system of claim 17 , wherein the proof of the location for the event is established by determining a probability that the location data is correct based on the estimated location.

19 . The system of claim 15 , wherein the proof of location for the event is based on multiple estimated locations generated by the network of beacon nodes.

20 . The system of claim 15 , wherein the estimated location is an estimated distance or location vector that is obtained using a route probing method or based on the Received Signal Strength Indication (RSSI).

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED ON REEL 66779 FRAME 227. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Oct 4, 2024
From: HOPTROFF, RICHARD
To: HOPTROFF LONDON LIMITED
Reel/Frame 069761/0719 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2024
From: HOPTROFF, RICHARD
To: HOPTROFF LONDON LIMITED
Reel/Frame 066779/0227 →
Priority Claims (1)
GB 1907677 · May 30, 2019 · national
Continuity (3)
Continuation 17459035 · Aug 27, 2021
Continuation PCTUS2020034844 · May 28, 2020
Related Publication 20240430028A1 · Dec 26, 2024
References Cited (28)
US 11042612B2 · Li · 2021 [cited by examiner]
US 11121879B2 · Bianzino · 2021 [cited by examiner]
US 11281796B2 · Pratt et al. · 2022 [cited by applicant]
US 11290884B2 · Kim · 2022 [cited by applicant]
US 11962402B2 · Hoptroff · 2024 [cited by applicant]
US 12245040B2 · Palyutina · 2025 [cited by examiner]
US 20160283920A1 · Fisher et al. · 2016 [cited by applicant]
US 20170041148A1 · Pearce · 2017 [cited by examiner]
US 20180197007A1 · Thirion · 2018 [cited by applicant]
US 20190065709A1 · Salomon · 2019 [cited by applicant]
US 20190068384A1 · Morimoto · 2019 [cited by applicant]
US 20190130416A1 · Boudville et al. · 2019 [cited by applicant]
US 20190132138A1 · Finlow-Bates et al. · 2019 [cited by applicant]
US 20190312941A1 · Maccini et al. · 2019 [cited by applicant]
EP 3379440A1 · 2018 [cited by applicant]
KR 20190038561A · 2019 [cited by applicant]
WO WO2019144978A2 · 2019 [cited by applicant]
WO WO2020243250A1 · 2020 [cited by applicant]
EP20815008.6 Extended European Search Report dated May 8, 2023. [cited by applicant]
Gao, et al., A decentralized trusted timestamping based on blockchains. IEEJ Journal of Industry Applications 2017. vol. 6 No. 4 pp. 252-257, DOI: 10.154/ieejjia.6.252. [cited by applicant]
Gipp, et al., Decentralized trusted timestamping using the crypto currency bitcoin. iConference 2015, pp. 1-5. [cited by applicant]
Levesque et al., ‘A Survey of Clock Synchronization Over Packet-Switched Networks’, In: IEEE Communications Surveys & Tutorials, pp. 2926-2947, Jul. 12, 2016 p. 2930. [cited by applicant]
PCT/US2020/034844 International Preliminary Report on Patentability dated Nov. 16, 2021. [cited by applicant]
PCT/US2020/034844 International Search Report & Written Opinion dated Sep. 9, 2020. [cited by applicant]
Shrestha et al. Blockchain-based Message Dissemination in VANET. IEEE 3rd International Conference on Computing, Communication and Security (ICCCS), IEEE:161-166 (2018). [cited by applicant]
Stavrou et al. Verified Time. IEEE Computer Society, IEEE 50(3):78-82 (2017). [cited by applicant]
U.S. Appl. No. 17/459,035 Notice of Allowance dated Jan. 23, 2024. [cited by applicant]
U.S. Appl. No. 17/459,035 Office Action dated Oct. 12, 2023. [cited by applicant]