IP Library Granted Patent US 12,408,037
Granted Patent B2
US 12,408,037 · App. 17/320,728 · Granted Sep 2, 2025

Using a blockchain to determine trustworthiness of messages within a telecommunications network for a smart city

Inventor: Ahmad Arash Obaidi (Issaquah, WA)
Assignee: T-Mobile USA, Inc
H04W12/106G06F16/1824H04L63/123H04W4/40H04W4/90H04W12/06
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,408,037
App. No.
17/320,728
Granted
Sep 2, 2025
Kind
B2
Abstract

Systems and methods are described herein for configuring vehicles and infrastructure (e.g., buildings, smart homes, traffic devices, utilities and associated systems, emergency response systems, and so on) to include blockchain nodes, so a smart city or area of the various devices can be supported by a blockchain network, with some or all devices and systems provisioned with nodes acting as distributed nodes for the blockchain network.

Claims (42)

1. A method performed by a telecommunications network, the method comprising:

receiving, at a blockchain node of a computing device, blockchain transaction information comprising a message from an infrastructure device,

wherein the infrastructure device is a device that monitors a current condition at a structure, location, or utility, and

wherein the message identifies the current condition at the infrastructure device;

determining, via a blockchain operation performed by the blockchain node, whether the infrastructure device is verified on a blockchain associated with a telecommunications network that facilitates communications between the computing device and the infrastructure device, wherein determining whether the infrastructure device is verified includes comparing identification information for the infrastructure device included in contents of the message received from the infrastructure device with identification information for the infrastructure device included in contents of at least one previous message received from the infrastructure device;

when the infrastructure device is determined to be verified by the blockchain operation, performing an action to respond to the current condition at the infrastructure device; and

when the infrastructure device is determined not to be verified by the blockchain operation, performing an action to mitigate the infrastructure device from transmitting additional messages to other computing devices, wherein the action comprises at least one of: sending messages to the computing devices to ignore messages from the infrastructure device or generating an alert that the infrastructure device is transmitting erroneous or nefarious messages.

2. The method of claim 1 , wherein the blockchain node of the computing device includes a Javascript script that acts as a blockchain agent for the computing device and is configured to operate as a distributed node for the blockchain associated with the telecommunications network.

3. The method of claim 1 , further comprising:

performing, by the blockchain node of the computing device, a transaction to the blockchain that includes a hash of a previous block in the blockchain, a timestamp for the transaction, and transaction data that identifies the action performed to respond to the message from the infrastructure device.

4. The method of claim 1 , wherein determining, via a blockchain operation performed by the blockchain node, whether the infrastructure device is verified includes comparing credential information within the message received from the infrastructure device with credential information maintained for the infrastructure device by the blockchain.

5. The method of claim 1 , wherein the infrastructure device is a utility meter that monitors use of a utility at a location, and wherein the computing device is an automated meter reading (AMR) device that automatically collects data from the utility meter.

6. The method of claim 1 , wherein the infrastructure device is an emergency alert device for a location, and wherein the computing device is a mobile device configured to alert an emergency responder of an emergency at the location.

7. A non-transitory computer-readable medium whose contents, when executed by a computing system, cause the computing system to perform a method, the method comprising:

receiving, at a blockchain node of a computing device, blockchain transaction information comprising a message from an infrastructure device,

wherein the infrastructure device is a device that monitors a current condition at a structure, location, or utility, and

wherein the message identifies the current condition at the infrastructure device;

determining, via a blockchain operation performed by the blockchain node, whether the infrastructure device is verified on a blockchain associated with a telecommunications network that facilitates communications between the computing device and the infrastructure device, wherein determining whether the infrastructure device is verified includes comparing identification information for the infrastructure device included in contents of the message received from the infrastructure device with identification information for the infrastructure device included in contents of at least one previous message received from the infrastructure device;

when the infrastructure device is determined to be verified by the blockchain operation, performing an action to respond to the current condition at the infrastructure device; and

when the infrastructure device is determined not to be verified by the blockchain operation, performing an action to mitigate the infrastructure device from transmitting additional messages to other computing devices, wherein the action comprises at least one of: sending messages to the computing devices to ignore messages from the infrastructure device or generating an alert that the infrastructure device is transmitting erroneous or nefarious messages.

8. The non-transitory computer-readable medium of claim 7 , wherein the blockchain node of the computing device includes a Javascript script that acts as a blockchain agent for the computing device and is configured to operate as a distributed node for the blockchain associated with the telecommunications network.

9. The non-transitory computer-readable medium of claim 7 , wherein the method further comprises:

performing, by the blockchain node of the computing device, a transaction to the blockchain that includes a hash of a previous block in the blockchain, a timestamp for the transaction, and transaction data that identifies the action performed to respond to the message from the infrastructure device.

10. The non-transitory computer-readable medium of claim 7 , wherein determining, via a blockchain operation performed by the blockchain node, whether the infrastructure device is verified includes comparing credential information within the message received from the infrastructure device with credential information maintained for the infrastructure device by the blockchain.

11. The non-transitory computer-readable medium of claim 7 , wherein the infrastructure device is a utility meter that monitors use of a utility at a location, and wherein the computing device is an automated meter reading (AMR) device that automatically collects data from the utility meter.

12. The non-transitory computer-readable medium of claim 7 , wherein the infrastructure device is an emergency alert device for a location, and wherein the computing device is a mobile device configured to alert an emergency responder of an emergency at the location.

13. A system comprising:

at least one hardware processor; and

at least one non-transitory memory storing instructions which, when executed by the at least one hardware processor, cause the system to:

receive blockchain transaction information comprising a message from an infrastructure device,

wherein the infrastructure device is a device that monitors a current condition at a structure, location, or utility, and

wherein the message identifies the current condition at the infrastructure device;

determine, via a blockchain operation, whether the infrastructure device is verified on a blockchain associated with a telecommunications network that facilitates communications between the system and the infrastructure device, wherein determining whether the infrastructure device is verified includes comparing identification information for the infrastructure device included in contents of the message received from the infrastructure device with identification information for the infrastructure device included in contents of at least one previous message received from the infrastructure device;

when the infrastructure device is determined to be verified by the blockchain operation, perform an action to respond to the current condition at the infrastructure device; and

when the infrastructure device is determined not to be verified by the blockchain operation, performing an action to mitigate the infrastructure device from transmitting additional messages to other computing devices, wherein the action comprises at least one of: sending messages to the computing devices to ignore messages from the infrastructure device or generating an alert that the infrastructure device is transmitting erroneous or nefarious messages.

14. The system of claim 13 , wherein system includes a JavaScript script that acts as a blockchain agent for the system and is configured to operate as a distributed node for the blockchain associated with the telecommunications network.

15. The system of claim 13 , wherein the instructions are further configured to cause the system to:

perform a transaction to the blockchain that includes a hash of a previous block in the blockchain, a timestamp for the transaction, and transaction data that identifies the action performed to respond to the message from the infrastructure device.

16. The system of claim 13 , wherein to determine whether the infrastructure device is verified, the system is configured to:

compare credential information within the message received from the infrastructure device with credential information maintained for the infrastructure device by the blockchain.

17. The system of claim 13 , wherein the infrastructure device is a utility meter that monitors use of a utility at a location, and wherein the system is an automated meter reading (AMR) device that automatically collects data from the utility meter.

18. The system of claim 13 , wherein the infrastructure device is an emergency alert device for a location, and wherein the system is a mobile device configured to alert an emergency responder of an emergency at the location.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 17, 2021
From: OBAIDI, AHMAD ARASH
To: T-MOBILE USA, INC.
Reel/Frame 056261/0164 →
Continuity (2)
Continuation 16237626 · Dec 31, 2018
Related Publication 20210274350A1 · Sep 2, 2021
References Cited (133)
US 8918645B2 · Evans et al. · 2014 [cited by applicant]
US 9516053B1 · Muddu et al. · 2016 [cited by applicant]
US 9985984B1 · Chavez et al. · 2018 [cited by applicant]
US 10310505B1 · Hanson et al. · 2019 [cited by applicant]
US 10805068B1 · Leise et al. · 2020 [cited by applicant]
US 10937009B1 · O'Brien · 2021 [cited by examiner]
US 11039317B2 · Obaidi · 2021 [cited by applicant]
US 11088854B2 · El Abed et al. · 2021 [cited by applicant]
US 11159945B2 · Obaidi · 2021 [cited by applicant]
US 11329982B2 · Obaidi · 2022 [cited by applicant]
US 11416942B1 · Leise · 2022 [cited by examiner]
US 11601787B2 · Obaidi · 2023 [cited by applicant]
US 11843950B2 · Obaidi · 2023 [cited by applicant]
US 20050188072A1 · Lee et al. · 2005 [cited by applicant]
US 20060230289A1 · Fox et al. · 2006 [cited by applicant]
US 20070291945A1 · Chuang et al. · 2007 [cited by applicant]
US 20110169654A1 · Ketari · 2011 [cited by applicant]
US 20130154853A1 · Chen · 2013 [cited by applicant]
US 20140220966A1 · Muetzel et al. · 2014 [cited by applicant]
US 20150006018A1 · Tesanovic et al. · 2015 [cited by applicant]
US 20150135283A1 · Tofighbakhsh · 2015 [cited by applicant]
US 20160261686A1 · Onishi et al. · 2016 [cited by applicant]
US 20160283920A1 · Fisher et al. · 2016 [cited by applicant]
US 20160330748A1 · Bindrim · 2016 [cited by applicant]
US 20170236094A1 · Shah · 2017 [cited by applicant]
US 20170243212A1 · Castinado et al. · 2017 [cited by applicant]
US 20170302626A1 · Yan · 2017 [cited by applicant]
US 20170331635A1 · Barinov et al. · 2017 [cited by applicant]
US 20170353496A1 · Pai et al. · 2017 [cited by applicant]
US 20170364698A1 · Goldfarb et al. · 2017 [cited by applicant]
US 20180091596A1 · Alvarez et al. · 2018 [cited by applicant]
US 20180122237A1 · Nascimento et al. · 2018 [cited by applicant]
US 20180219893A1 · Li et al. · 2018 [cited by applicant]
US 20180225693A1 · Postrel · 2018 [cited by applicant]
US 20180248896A1 · Challita et al. · 2018 [cited by applicant]
US 20180287780A1 · Safford et al. · 2018 [cited by applicant]
US 20180293557A1 · Kim et al. · 2018 [cited by applicant]
US 20180330125A1 · Gray · 2018 [cited by applicant]
US 20180337769A1 · Gleichauf · 2018 [cited by applicant]
US 20180342036A1 · Zachary · 2018 [cited by applicant]
US 20180365397A1 · Viscarola et al. · 2018 [cited by applicant]
US 20180372502A1 · Rønnow et al. · 2018 [cited by applicant]
US 20180376305A1 · Ramalho De Oliveira · 2018 [cited by examiner]
US 20190005469A1 · Dhupkar · 2019 [cited by examiner]
US 20190019168A1 · Wu · 2019 [cited by applicant]
US 20190058697A1 · Chang et al. · 2019 [cited by applicant]
US 20190093215A1 · Kang et al. · 2019 [cited by applicant]
US 20190104196A1 · Li et al. · 2019 [cited by applicant]
US 20190165949A1 · Ramos et al. · 2019 [cited by applicant]
US 20190172282A1 · Patel · 2019 [cited by applicant]
US 20190173666A1 · Ardashev et al. · 2019 [cited by applicant]
US 20190182284A1 · Signorini et al. · 2019 [cited by applicant]
US 20190199756A1 · Correnti et al. · 2019 [cited by applicant]
US 20190215159A1 · Notani · 2019 [cited by examiner]
US 20190230114A1 · Grebovich · 2019 [cited by applicant]
US 20190245680A1 · Boutaba et al. · 2019 [cited by applicant]
US 20190245697A1 · El Abed et al. · 2019 [cited by applicant]
US 20190259274A1 · Avery et al. · 2019 [cited by applicant]
US 20190261433A1 · Turner · 2019 [cited by examiner]
US 20190268284A1 · Karame · 2019 [cited by examiner]
US 20190268466A1 · Inoue · 2019 [cited by applicant]
US 20190303942A1 · Balaraman · 2019 [cited by examiner]
US 20190305932A1 · Townsend · 2019 [cited by examiner]
US 20190312831A1 · Gupta · 2019 [cited by examiner]
US 20190332586A1 · Wang · 2019 [cited by applicant]
US 20190340269A1 · Biernat · 2019 [cited by examiner]
US 20190342095A1 · Simons · 2019 [cited by applicant]
US 20190361917A1 · Tran · 2019 [cited by examiner]
US 20190373472A1 · Smith et al. · 2019 [cited by applicant]
US 20190380037A1 · Lifshitz et al. · 2019 [cited by applicant]
US 20190386969A1 · Verzun et al. · 2019 [cited by applicant]
US 20190392536A1 · Rice · 2019 [cited by examiner]
US 20200004854A1 · Inturi · 2020 [cited by examiner]
US 20200014720A1 · Giura · 2020 [cited by examiner]
US 20200020038A1 · Haile · 2020 [cited by examiner]
US 20200042012A1 · Zander · 2020 [cited by applicant]
US 20200045119A1 · Weldemariam · 2020 [cited by examiner]
US 20200099531A1 · Chidambaram · 2020 [cited by examiner]
US 20200099698A1 · Kundu et al. · 2020 [cited by applicant]
US 20200112432A1 · Iwama · 2020 [cited by examiner]
US 20200117690A1 · Tran · 2020 [cited by examiner]
US 20200118131A1 · Diriye et al. · 2020 [cited by applicant]
US 20200136808A1 · Chasko et al. · 2020 [cited by applicant]
US 20200145191A1 · Qi et al. · 2020 [cited by applicant]
US 20200145234A1 · Nishijima · 2020 [cited by examiner]
US 20200160330A1 · Yan · 2020 [cited by examiner]
US 20200186527A1 · Delson · 2020 [cited by examiner]
US 20200186607A1 · Murphy et al. · 2020 [cited by applicant]
US 20200195495A1 · Parker et al. · 2020 [cited by applicant]
US 20200200824A1 · Narayanaswami · 2020 [cited by applicant]
US 20200213305A1 · Obaidi et al. · 2020 [cited by applicant]
US 20200213826A1 · Obaidi · 2020 [cited by examiner]
US 20200213852A1 · Obaidi · 2020 [cited by examiner]
US 20200213857A1 · Obaidi · 2020 [cited by examiner]
US 20200322130A1 · Rajagopal et al. · 2020 [cited by applicant]
US 20200380156A1 · Garg et al. · 2020 [cited by applicant]
US 20200389294A1 · Soundararajan · 2020 [cited by examiner]
US 20210021424A1 · Punal et al. · 2021 [cited by applicant]
US 20210037013A1 · Salkintzis · 2021 [cited by examiner]
US 20210049477A1 · Sakae et al. · 2021 [cited by applicant]
US 20210182849A1 · Davies et al. · 2021 [cited by applicant]
US 20210209483A1 · Bose et al. · 2021 [cited by applicant]
US 20220014922A1 · Obaidi · 2022 [cited by applicant]
US 20230199451A1 · Obaidi · 2023 [cited by applicant]
CA 2947936A1 · 2014 [cited by examiner]
CN 104854893A · 2015 [cited by applicant]
CN 107450981A · 2017 [cited by applicant]
CN 107508859A · 2017 [cited by applicant]
CN 108234456A · 2018 [cited by applicant]
CN 108681965A · 2018 [cited by applicant]
CN 108833081A · 2018 [cited by applicant]
CN 108881233A · 2018 [cited by applicant]
CN 108961047A · 2018 [cited by applicant]
CN 109542883A · 2019 [cited by examiner]
CN 111164530A · 2020 [cited by examiner]
CN 111210345A · 2020 [cited by examiner]
CN 113167075A · 2021 [cited by examiner]
CN 108830601B · 2022 [cited by applicant]
EP 3285248A1 · 2018 [cited by applicant]
EP 3488556B1 · 2020 [cited by examiner]
JP 2020528695A · 2020 [cited by examiner]
JP 2020537471A · 2020 [cited by examiner]
KR 20180072325A · 2018 [cited by examiner]
RU 2735235C1 · 2020 [cited by examiner]
WO 2018014123A1 · 2018 [cited by applicant]
WO 2018033309A1 · 2018 [cited by applicant]
WO 2018126029A2 · 2018 [cited by applicant]
WO WO2019015856A1 · 2019 [cited by examiner]
European Patent Office, Extended European Search Report, EP Patent Application 19907507.8, mailed Aug. 11, 2022, 10 pages. [cited by applicant]
Jover, Roger Piqueras et al. “dHSS—Distributed Peer-to-Peer Implementation of the LTE HSS Based on the Bitcoin / Namecoin Architecture,” 2016 IEEE International Conference on Communications Workshops, May 23, 2016, pp. … [cited by applicant]
Supplemental European Search Report for EP19907420.4 mailed Dec. 5, 2022, 11 pages. [cited by applicant]
International Searching Authority, International Search Report and Written Opinion, PCT Patent Application PCT/US2019/068429, mailed May 1, 2020, 11 pages. [cited by applicant]
International Searching Authority, International Search Report and Written Opinion, PCT Patent Application PCT/US2019/068433, mailed Apr. 29, 2020, 9 pages. [cited by applicant]