Method and apparatus for internet of things (IoT) dynamic policy management

Patent metadata

Field	Value
Publication number	US-12003492-B2
Application number	US-202017018064-A
Country	US
Kind code	B2
Filing date	Sep 11, 2020
Priority date	Sep 11, 2020
Publication date	Jun 4, 2024
Grant date	Jun 4, 2024

Abstract

Some embodiments include a broker policy manager (BPM) comprising a transceiver and a processor, where the processor is configured to dynamically change a policy associated with an Internet of Things (IoT) client certificate based on an incident invitational model. In some embodiments the processor can determine that a first IoT client is a participant of an incident communications network corresponding to an incident, and transmit first instructions to a certificate-based IoT broker to change a first IoT policy associated with a first certificate of the first IoT client, to enable the first IoT client to publish or subscribe to a topic that corresponds to the incident. The first instructions can indicate a change to a second IoT policy associated with a second certificate of a second IoT client that enables the second IoT client to publish or subscribe to the topic that corresponds to the incident.

First claim

What is claimed is:

1. A system for a broker policy manager (BPM), comprising:
a transceiver; and
one or more processors coupled to the transceiver, configured to:
subscribe to a first topic the BPM;
receive from a certificate-based Internet of Things (IoT) broker, a first published message on the first topic comprising the BPM;
determine, based on the first topic comprising the BPM, that a first IoT client is a participant in an incident communications network corresponding to an incident;
transmit first instructions to the certificate-based IoT broker to change a first IoT policy associated with a first certificate of the first IoT client, to enable the first IoT client to publish or subscribe to a second topic corresponding to the incident;
receive a second indication that a second IoT client accepts an invitation from the first IoT client to join the incident communications network;
transmit second instructions to the certificate-based IoT broker to change a second IoT policy associated with a second certificate of the second IoT client that enables the second IoT client to publish or subscribe to the second topic corresponding to the incident; and
determine that a third IoT client has a third certificate associated with the first certificate of the first IoT client based on a third indication received from the first IoT client, wherein the first instructions transmitted to the certificate-based IoT broker change a third IoT policy associated with the third certificate of the third IoT client to enable the third IoT client to publish or subscribe to the first topic.

2. The system of claim 1 , wherein to determine that the first IoT client is the participant in the incident communications network, the one or more processors are configured to:
receive a first indication via the transceiver, directly or indirectly from the first IoT client, that the first IoT client has created the incident communications network, or that the first IoT client has been invited to join the incident communications network.

3. The system of claim 1 , wherein the published message on the first topic comprising the BPM indicates that the first IoT client created the incident.

4. The system of claim 1 , wherein to receive the published message is based on a real time publication-subscription, data-sync, or request-response protocol, comprising: HyperText Transfer Protocol (HTTP), Streaming Text Oriented Messaging Protocol (STOMP), Advanced Message Queuing Protocol (AMQP), Web Application Messaging Protocol (WAMP), Java Message Service (JMS), ZeroMQ Message Transport Protocol (ZMTP), or proprietary messaging protocols.

5. The system of claim 1 , wherein the first IoT client comprises: a software routine; a web browser; a map or a region of a map; a graphical user interface (GUI); an actuator; an artificial intelligence or analytics based object, event, or condition; a sensor; a sensor coupled to another device or module that causes an alarm, event notification, or warning signal to be transmitted to a rules-based or pre-designated recipient agent; a gas sensor; a smoke/fire detector; or a contact closure of a switch or panic button.

6. The system of claim 5 , wherein the first IoT client comprises a GUI of an interoperability work station (IWS) coupled to the incident communications network.

7. The system of claim 1 , wherein the one or more processors are further configured to:
determine that the third IoT client shares the first certificate with the first IoT client, wherein the first certificate enables the third IoT client to publish or subscribe to the second topic that comprises the incident.

8. The system of claim 1 , wherein to determine that the first IoT client is the participant of the incident communications network, the one or more processors are configured to:
receive, via the transceiver, a first indication on a multicast channel of a multicast-based communication system, that the first IoT client has been invited to join the incident communications network.

9. The system of claim 1 , wherein the first IoT client and the second IoT client are configured to exchange information via the incident communications network or via the certificate-based IoT broker.

10. The system of claim 1 , wherein the one or more processors are configured to:
determine that the first IoT client has left incident communications network; and
transmit a signal to dynamically adjust a policy of certificate corresponding to the first IoT client.

11. A method for a broker policy manager (BPM), comprising:
subscribing to a first topic comprising the BPM;
receiving, from a certificate-based Internet of Things (IoT) broker, a published message on the first topic corresponding to the BPM;
determining, based on the first topic comprising the BPM, that a first IoT client is a participant in an incident communications network corresponding to an incident;
transmitting first instructions to the certificate-based IoT broker to change a first IoT policy associated with a first certificate of the first IoT client, to enable the first IoT client to publish or subscribe to a second topic that corresponds to the incident
receiving a second indication that a second IoT client accepts an invitation from the first IoT client to join the incident communications network;
transmitting second instructions to the certificate-based IoT broker to change a second IoT policy associated with a second certificate of the second IoT client that enables the second IoT client to publish or subscribe to the first topic corresponding to the incident; and
determining that a third IoT client has a third certificate associated with the first certificate of the first IoT client based on a third indication received from the first IoT client, wherein the first instructions transmitted to the certificate-based IoT broker change a third IoT policy associated with the third certificate of the third IoT client to enable the third IoT client to publish or subscribe to the first topic.

12. The method of claim 11 , wherein the determining that the first IoT client is the participant in the incident communications network comprises:
receiving a first indication directly or indirectly from the first IoT client, that the first IoT client has created the incident communications network, or that the first IoT client has been invited to join the incident communications network.

13. The method of claim 11 , wherein the published message on the first topic corresponding to the BPM indicates that the first IoT client created the incident communications network.

14. The method of claim 11 , wherein the first IoT client comprises: a sensor coupled to another device or module that causes an alarm, event notification, or warning signal to be transmitted to a rules-based or pre-designated recipient agent; a gas sensor; a smoke/fire detector; or a contact closure of a switch or panic button.

15. The method of claim 14 , wherein the first IoT client comprises a GUI of an interoperability work station (IWS) coupled to the incident communications network and wherein the second IoT client comprises an actuator.

16. The method of claim 11 , further comprising:
determining that the third IoT client shares the first certificate with the first IoT client, wherein the first certificate enables the third IoT client to publish or subscribe to the second topic that comprises the incident.

17. The method of claim 11 , wherein the first IoT client and the second IoT client are configured to exchange information via the incident communications network or via the ce

Assignees

• Mutualink Inc

Inventors

• Wengrovitz Michael S
• Mazzarella Joseph R
• Setlur Anand

Classifications

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G16Y40/35

  Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives · CPC title

• G16Y30/00

  IoT infrastructure · CPC title

• G16Y40/10

  Detection; Monitoring · CPC title