Granted Patent B2

US 12,291,196 · App. 18/217,511 · Granted May 6, 2025

Inventors: Lucas Smith (Frisco, TX); Jay Bartholomew (McKinney, TX)

Assignee: TOYOTA MOTOR NORTH AMERICA, INC.

B60W30/08B60W40/08B60W2030/082B60W2050/0004B60W2050/0075B60W2540/221B60W2556/45

Abstract

Claims (79)

1. A method, comprising:

sending, by a hardware-implemented server, an instruction to a transport to autonomously take an action based on a severity of an event that is determined by data from a primary device located in an interior of the transport and a consensus of data from a plurality of secondary devices remote from the transport and within a range of the transport;

wherein a first notification is sent to the primary device and a second notification containing content that is different than a content of the first notification is sent to the plurality of secondary devices.

2. The method of claim 1 , wherein the data from the primary device and the data from the plurality of secondary devices comprises:

sensor data relating to anomalous behavior of the transport from the plurality of secondary devices.

3. The method of claim 1 , further comprising:

identifying the consensus of data when the data provided by a majority of the plurality of secondary devices is within a common range corresponding to the severity of the event.

4. The method of claim 1 , further comprising:

identifying, by the hardware-implemented server, a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the data from the plurality of secondary devices relates to the severity of the event.

5. The method of claim 1 , further comprising:

identifying the action to take based on the severity of the event, the action comprising at least one of:

notifying the transport in response to the severity of the event is low;

notifying the plurality of secondary devices in response to the severity of the event is moderate; and

contacting one or more first responders in response to the severity of the event is high.

6. The method of claim 1 , comprising:

creating, by the hardware-implemented server, a blockchain transaction based on a smart contract and one or more of:

the data from the primary device;

the data from the plurality of secondary devices;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the data from the plurality of secondary devices;

a type of the severity of the event; and

a type of the action to take; and

storing, by the hardware-implemented server, the blockchain transaction in a blockchain ledger based on the smart contract.

7. A hardware-implemented server, comprising:

a memory storing one or more instructions; and

a processor that when executing the one or more instructions is configured to:

send an instruction to a transport to autonomously take an action based on a severity of an event that is determined by data from a primary device located in an interior of the transport and a consensus of data from a plurality of secondary devices remote from the transport and within a range of the transport;

wherein a first notification is sent to the primary device and a second notification containing content that is different than a content of the first notification is sent to the plurality of secondary devices.

8. The hardware-implemented server of claim 7 , wherein the data from the primary device and the data from the plurality of secondary devices comprises:

sensor data related to anomalous behavior of the transport from the plurality of secondary devices.

9. The hardware-implemented server of claim 7 , wherein, when the processor is configured to identify the severity of the event, the processor is further configured to:

identify the consensus when the data provided by a majority of the plurality of secondary devices is within a common range that corresponds to the severity of the event.

10. The hardware-implemented server of claim 7 , wherein the processor is further configured to:

identify a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the data from the plurality of secondary devices relates to the severity of the event.

11. The hardware-implemented server of claim 7 , wherein the processor is further configured to:

identify the action to take based on the severity, wherein the action comprises at least one of:

notify the transport in response to the severity of the event is low;

notify the plurality of secondary devices in response to the severity of the event is moderate; and

contact one or more first responders in response to the severity of the event is high.

12. The hardware-implemented server of claim 7 , wherein the processor is configured to:

create a blockchain transaction based on a smart contract and one or more of:

the data from the primary device;

the data from the plurality of secondary devices;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the data from the plurality of secondary devices;

a type of the severity of the event; and

a type of the action to take; and

store the blockchain transaction in a blockchain ledger based on the smart contract.

13. A non-transitory computer readable medium comprising one or more instructions that when executed by a processor of a server cause the processor to perform:

sending an instruction to a transport to autonomously take an action based on a severity of an event that is determined by data from a primary device located in an interior of the transport and a consensus of data from a plurality of secondary devices remote from the transport and within a range of the transport;

wherein a first notification is sent to the primary device and a second notification containing content that is different than a content of the first notification is sent to the plurality of secondary devices.

14. The non-transitory computer readable medium of claim 13 ,

wherein the data from the primary device and the data from the plurality of secondary devices comprises:

sensor data relating to anomalous behavior of the transport from the plurality of secondary devices.

15. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further causes the processor to perform:

identifying a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the data from the plurality of secondary devices relates to the severity of the event.

16. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further causes the processor to perform:

identifying the action to take based on the severity of the event, the action comprising at least one of:

notifying the transport in response to the severity of the event is low;

notifying the plurality of secondary devices in response to the severity of the event is moderate; and

contacting one or more first responders in response to the severity of the event is high.

17. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further cause the processor to perform:

creating a blockchain transaction based on a smart contract and one or more of:

the data from the primary device;

the data from the plurality of secondary devices;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the data from the plurality of secondary devices;

a type of the severity of the event; and

a type of the action to take; and

storing the blockchain transaction in a blockchain ledger based on the smart contract.

Assignments (1)

Continuity (2)

References Cited (167)