IP Library › Patent Application 18391048
Patent Application
App. No. 18/391,048

BLOCKCHAIN BASED ACCESS TO DEVICES ON A NETWORK WITH LOCAL TOKEN ACQUISITION

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 None
App. No.
18/391,048
Abstract

An access control method and system that uses tokens on a blockchain which are used for subsequent access to a local network. The tokens are authenticated on the local network using blockchain. A client device can present a token to the local network from anywhere in the world in order to access at least one device on the local network. In an example, the method includes presenting, to a node of the local network, the token; and receiving, from the node, successful authentication of the token. The method can include, after the successful authentication of the token, authorizing the client device to access a device on the local network or removing access to the device for the client device.

Claims (104)

1 . An access control method performed by a client device, comprising:

receiving, from a local proximity interface of a token dispenser device on a local network, a token on a blockchain layer;

accessing the local network or a device on the local network; and

presenting, to a node of the local network, the token for authentication;

wherein, as a consequence to the authentication of the token, the device has removal of the access to the local network.

2 . The access control method as claimed in claim 1 , wherein the presenting is performed in response to receiving selection of a dedicated button on the client device.

3 . The access control method as claimed in claim 1 , wherein the authentication is proof of authority authentication.

4 . A client device, comprising:

a processor; and

memory containing instructions which, when executed by the processor, cause the processor to perform the access control method as claimed in claim 1 .

5 . An access control method, comprising:

sending, from a local proximity interface of a token dispenser device on a local network, to a client device, a token on a blockchain layer;

providing, from a node to the client device, access by the client device to the local network or a device on the local network;

receiving, at the node of the local network from the client device, presentation of the token;

requesting, from the node, authentication of the token;

removing, as a consequence to the authentication, the access by the client device.

6 . The access control method as claimed in claim 5 , wherein the authentication is proof of authority authentication.

7 . An access control method, comprising:

sending, via a local proximity interface of a token dispenser device to a client device, a token on a blockchain layer;

receiving, at a node of a local network from the client device, presentation of the token;

requesting, from the node, authentication of the token,

wherein the authentication authorizes access by the client device to the local network or a device on the local network;

receiving, from a user input device, an instruction for removal of the access of the client device on the local network; and

removing the access of the client device on the local network.

8 . The access control method as claimed in claim 7 , wherein the authentication is proof of authority authentication.

9 . The access control method as claimed in claim 7 , wherein the user input device is at the node or another node of the blockchain layer.

10 . The access control method as claimed in claim 7 , wherein the user input device is on the local network.

11 . A method, comprising:

receiving, by a node, an instruction to cancel a wallet for a blockchain layer;

receiving a transaction that is initiated by the wallet; and

refraining from performing the transaction on the blockchain layer.

12 . The method as claimed in claim 11 , wherein the wallet includes a private key with an associated public key, further comprising detecting that the public key is associated with the wallet for the refraining.

13 . The method as claimed in claim 11 , wherein the wallet includes a private key, wherein the node has access to the private key, further comprising detecting that the private key is associated with the wallet for the refraining.

14 . The method as claimed in claim 11 , wherein the wallet includes a wallet identifier, further comprising detecting the wallet identifier for the refraining.

15 . The method as claimed in claim 14 , further comprising detecting that a token of the transaction is associated with the wallet identifier for the refraining.

16 . The method as claimed in claim 11 , further comprising, in response to the receiving the instruction to cancel the wallet, cancelling all tokens associated with the wallet.

17 . The method as claimed in claim 11 , further comprising, in response to the receiving the instruction to cancel the wallet, returning all tokens associated with the wallet to a coinbase.

18 . The method as claimed in claim 11 , further comprising sending a communication to at least one other node to perform the refraining.

19 . The method as claimed in claim 18 , wherein at least one of the other nodes is an authority node.

20 . The method as claimed in claim 11 , wherein the node is an authority node.

21 . The method as claimed in claim 11 , wherein the blockchain layer is a currency blockchain layer, an Ethereum blockchain layer, or an Ethereum Request for Comment 20 (ERC-20) blockchain layer.

22 . The method as claimed in claim 11 , wherein the instruction is received through a user input device connected to the node or on a same local network as the node.

23 . The method as claimed in claim 11 , wherein the instruction is received through a client device, further comprising authenticating the client device as being authorized to send the instruction to cancel.

24 . A method, comprising:

receiving, by a node, an instruction to reverse a transaction on a blockchain layer, wherein the blockchain layer has a penultimate block on the blockchain layer associated with a private key; and

adding a new block on the blockchain layer which is associated with the private key of the penultimate block, wherein the node has access to the private key.

25 . The method as claimed in claim 24 , wherein the penultimate block is associated with a wallet, wherein the new block on the blockchain layer is associated with the wallet, wherein the node has access to the wallet.

26 . The method as claimed in claim 24 , wherein the node has access to the private key.

27 . The method as claimed in claim 24 ,

wherein the node is on a local network;

further comprising sending, via a physical proximity interface of a token dispenser device on the local network, to a client device, a token on the blockchain layer;

wherein the receiving the instruction includes receiving, at the node from the client device, presentation of the token;

further comprising requesting, from the node, authentication of the token; and

wherein the adding the new block is performed as a consequence to the authentication.

28 . The method as claimed in claim 24 , further comprising sending a communication to at least one other node to perform the adding the new block.

29 . The method as claimed in claim 28 , wherein at the least one of the other nodes is an authority node.

30 . The method as claimed in claim 24 , wherein the node is an authority node.

31 . The method as claimed in claim 24 , wherein the adding the new block is performed using proof of authority authentication.

32 . The method as claimed in claim 24 , wherein the blockchain layer is a currency blockchain layer, an Ethereum blockchain layer, or an Ethereum Request for Comment 20 (ERC-20) blockchain layer.

33 . The method as claimed in claim 24 , wherein the instruction is received through a user input device connected to the node.

34 . The method as claimed in claim 24 , wherein the instruction is received through a client device on a same local network as the node.

35 . The method as claimed in claim 24 , wherein the instruction is received through a client device, further comprising authenticating the client device as being authorized to send the instruction to cancel.

36 . The method as claimed in claim 24 , further comprising sending a communication to advise of the adding the new block.

37 . The method as claimed in claim 36 , wherein the sending the communication is to a master device or an authority node which maintains an off-chain record of the blockchain layer.

38 . A node comprising:

one or more processors; and

non-transitory memory containing instructions which, when executed by the one or more processors, cause the one or more processors to perform the method as claimed in claim 11 .

39 . A method, comprising:

receiving, by a client device, an instruction to cancel a wallet for a blockchain layer;

deleting all tokens stored on the client device in relation to the blockchain layer.

40 . The method as claimed in claim 39 , wherein the receiving is through a user input device or a user interface of the client device.

41 . The method as claimed in claim 39 , further comprising sending a communication to advise of the deleting.

42 . The method as claimed in claim 41 , wherein the sending the communication is to a master device or an authority node which maintains an off-chain record of the blockchain layer.

43 . The method as claimed in claim 39 , further comprising receiving, from a local proximity interface of a token dispenser device, the tokens on the blockchain layer, where the tokens, when presented to a node of a local network, provide access by the client device to the local network or a device on the local network.

44 . The method as claimed in claim 39 , wherein the blockchain layer is a currency blockchain layer, an Ethereum blockchain layer, or an Ethereum Request for Comment 20 (ERC-20) blockchain layer.

45 . A non-transitory memory containing instructions which, when executed by one or more processors, cause the one or more processors to perform the access control method as claimed in claim 1 .

46 . An access control method performed by a client device, comprising:

presenting, to a node of a local network, a token on a blockchain layer, wherein only the node or only one other node performs authentication of the token by way of proof of authority authentication.

47 . The access control method as claimed in claim 46 , further comprising accessing, after the authentication of the token, a device on the local network.

48 . The access control method as claimed in claim 46 , wherein, after the authentication of the token, the client device is authorized to access a device on the local network.

49 . The access control method as claimed in claim 48 , wherein the device is a camera or a network attached storage (NAS) device.

50 . The access control method as claimed in claim 48 , wherein the device is a switch, a breaker, a security monitoring device, a television, a lock, a light, a heating, ventilation and air conditioning (HVAC) device, an appliances, a vehicle, a personal computer, a server, a mobile communication device, a server, a mobile communication device, a robotic device, a sensor for the robotic device, and/or an air pressure control switch.

51 . The access control method as claimed in claim 46 , wherein the proof of authority authentication includes the client device starting a transaction on the blockchain layer using a private key.

52 . The access control method as claimed in claim 46 , further comprising, as a consequence to the authentication, authorizing access to the local network or any device on the local network.

53 . The access control method as claimed in claim 46 , wherein the presenting is performed via the Internet when the client device is remote from the local network.

54 . The access control method as claimed in claim 46 , wherein the authentication of the token does not require any identification or credentials of the client device.

55 . The access control method as claimed in claim 46 , the node or the only one other node is an authority node which maintains an off-chain record of the blockchain layer.

56 . The access control method as claimed in claim 46 , wherein the node or the only one other node is not a master device which had generated the token.

57 . An access control method, comprising:

receiving, at a node of a local network from a client device, presentation of a token on a blockchain layer;

performing, by only the node or by only one other node, authentication of the token using proof of authority authentication.

58 . The access control method as claimed in claim 57 , further comprising:

authorizing, after the authentication of the token, access of the client device to a device on the local network.

59 . The access control method as claimed in claim 58 , wherein the device is a network attached storage (NAS) device.

60 . The access control method as claimed in claim 57 , wherein the authentication authorizes the access to the local network or any device on the local network.

61 . The access control method as claimed in claim 58 , wherein the authentication authorizes the access to only the device and no other devices on the local network.

62 . The access control method as claimed in claim 58 , wherein the node is configured to control the device, wherein the authentication authorizes the access by the client device to control the device through the node.

63 . The access control method as claimed in claim 57 , wherein the presentation is performed via the Internet when the client device is remote from the local network.

64 . The access control method as claimed in claim 57 , wherein the authentication of the token does not require any identification or credentials of the client device.

65 . The access control method as claimed in claim 58 , wherein the access includes instruction from the client device to the device.

66 . The access control method as claimed in claim 57 , wherein the node or the only one other node is an authority node which maintains an off-chain record of the blockchain layer.

67 . The access control method as claimed in claim 57 , wherein the node or the only one other node is not a master device which had generated the token.

68 . The access control method as claimed in claim 46 , further comprising receiving, from the node, successful authentication of the token.

69 . The access control method as claimed in claim 57 , further comprising sending, from the node to the client device, successful authentication of the token.

Assignments (5)
CHANGE OF NAME Recorded Jan 26, 2026
From: ISHIELD TECH INC.
To: FORTIX INC.
Reel/Frame 074465/0818 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TITLE ON THE ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED AT REEL: 67298 FRAME: 0692. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT . Recorded Jul 25, 2024
From: BRAINWAVE RESEARCH CORPORATION
To: ISHIELD TECH INC.
Reel/Frame 068151/0111 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CLERICAL ERROR IN TITLE OF THE INVENTION ON THE ASSIGNMENT FROM PROOF OF AUTHORITY BASED ACCESS TO DEVICES ON A NETWORK WITH LOCAL TOKEN ACQUISITION TO BLOCKCHAIN BASED ACCESS TO DEVICES ON A NETWORK WITH LOCAL TOKEN ACQUISITION PREVIOUSLY RECORDED ON REEL 67298 FRAME 553. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 25, 2024
From: PARDO, RENE; RATHI, GHANSHYAM; RATHI, PRISHA
To: BRAINWAVE RESEARCH CORPORATION
Reel/Frame 070993/0465 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2024
From: PARDO, RENE; RATHI, GHANSHYAM; RATHI, PRISHA
To: BRAINWAVE RESEARCH CORPORATION
Reel/Frame 067298/0553 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2024
From: BRAINWAVE RESEARCH CORPORATION
To: ISHIELD TECH INC.
Reel/Frame 067298/0692 →