IP Library Granted Patent US 12,206,660
Granted Patent B2
US 12,206,660 · App. 18/513,707 · Granted Jan 21, 2025

Access and messaging in a multi client network

Inventors: Mahender Reddy Vangati (San Jose, CA); Darrel Q. Pham (San Jose, CA); Daniel Dah Tai (San Jose, CA); Michael Edgar Larson (Los Gatos, CA)
Assignee: View, Inc.
H04L63/0823H04L51/214H04L63/0428H04L63/101H04L63/108H04L67/10H04L67/55
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,206,660
App. No.
18/513,707
Granted
Jan 21, 2025
Kind
B2
Abstract

A messaging system for exchanging messages between nodes in a network via a broker that uses a publish-subscribe message protocol, which nodes have object identifications (IDs). Messages between the nodes are routed using the object IDs of the nodes. Secure communication is provided using authentication according to digital certificates being used as first and second tiers by a commissioning broker and a data broker, respectively, in which the second tier certificate used by the data broker has a shorter lived expiration time.

Claims (22)

1. A method comprising:

delivering a message in a network configured for message communication using a publish-subscribe network protocol, wherein delivering the message includes:

(a) routing the message from a at least one requesting client node to a broker, wherein the message (i) is intended for at least one target client node having a unique object identification (ID) and (ii) comprises a string identification that comprises a topic string and the unique object ID of the at least one target client node, and/or a group ID with which the at least one target client node is associated;

(b) receiving the message by the broker; and

(c) using the broker to route the message to the at least one target client node based on the topic string and one or both of the unique object ID and/or the group ID comprised in the string ID of the message.

2. The method of claim 1 , wherein the message comprises (i) a routing address and (ii) a message data.

3. The method of claim 1 , wherein the at least one target client node and/or the at least one requesting client node is a device or a computer readable media.

4. The method of claim 3 , wherein the device comprises a sensor, an emitter, an antenna, or a tintable window.

5. The method of claim 1 , wherein the network comprises a building management system.

6. The method of claim 1 , wherein the network is disposed in an envelope of a building, an electrical shaft of the building, a communication shaft of the building, an elevator shaft of the building, and/or an electrical room of the building.

7. The method of claim 1 , wherein data of the message comprises (i) a message header having a first encryption level, and (ii) a message content that comprises a second encryption level higher than the first encryption level.

8. A non-transitory computer readable medium comprising instructions inscribed thereon which, when executed by one or more processors, cause the one or more processors to execute operations, comprising:

delivering a message in a network configured for message communication using a publish-subscribe network protocol, wherein delivering the message includes:

(a) routing the message from a at least one requesting client node to a broker, wherein the message (i) is intended for at least one target client node having a unique object identification (ID) and (ii) comprises a string identification that comprises a topic string and the unique object ID of the at least one target client node, and/or a group ID with which the at least one target client node is associated;

(b) receiving the message by the broker; and

(c) using the broker to route the message to the at least one target client node based on the topic string and one or both of the unique object ID and/or the group ID comprised in the string ID of the message.

9. The non-transitory computer medium of claim 8 , wherein the message comprises (i) a routing address and (ii) a message data.

10. The non-transitory computer medium of claim 8 , wherein the at least one target client node and/or the at least one requesting client node is a device or a computer readable media.

11. The non-transitory computer medium of claim 10 , wherein the device comprises a sensor, an emitter, an antenna, or a tintable window.

12. The non-transitory computer medium of claim 8 , wherein the network comprises a building management system.

13. The non-transitory computer medium of claim 8 , wherein the network is disposed in an envelope of a building, an electrical shaft of the building, a communication shaft of the building, an elevator shaft of the building, and/or an electrical room of the building.

14. The non-transitory computer medium of claim 8 , wherein data of the message comprises (i) a message header having a first encryption level, and (ii) a message content that comprises a second encryption level higher than the first encryption level.

Assignments (3)
MERGER AND CHANGE OF NAME Recorded Dec 19, 2024
From: VIEW, INC.; PVMS MERGER SUB, INC.; VIEW OPERATING CORPORATION
To: VIEW OPERATING CORPORATION
Reel/Frame 069743/0586 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: VANGATI, MAHENDER REDDY; PHAM, DARREL Q.; TAI, DANIEL DAH
To: VIEW, INC.
Reel/Frame 066116/0420 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: LARSON, MICHAEL E.
To: VIEW, INC.
Reel/Frame 066116/0438 →
Cited By (1)
US 12,615,229