NETWORKS, SYSTEMS AND METHODS FOR ENHANCED WILDFIRE MITIGATION, PROTECTION AND SUPPRESSION

Abstract

There is provided networks, systems and displays for providing derived data and predictive information for use in emergencies; and in particular for use in wildfire emergencies. More particularly, there is provided systems, equipment and networks for the monitoring and collecting of raw data regarding fire emergencies, both real time and historic. In embodiments, this raw data is then analyzed to provide derived data, predictive data, virtual data, and combinations and variations of this data, which depending upon the nature of this data may be packaged, distributed, displayed and used in various setting and applications to mitigate, avoid and manage the emergency, including a wildfire emergency.

Claims

1. A system for obtaining, evaluating and displaying in a predictive manner, information and data regarding fire emergencies, the system comprising: a. a plurality of units configured to provide raw data regarding a fire; i. wherein each unit comprises a communication node on a communication network; ii. wherein at least one of the plurality of units is a mobile unit, comprising a processor and a GUI; and, iii. wherein at least one of the plurality of units is a fixed unit comprising a processor and a GUI; b. a source of derived data regarding one or more of the fire location, a weather condition, a fire movement, a path of a fire, a traffic condition, available water, water usage, a power grid, and electrical usage; i. wherein the source of derived data comprises a communication node on the communication network; c. a processor comprising a communication node on the communication network, thereby placing the processor in communication with the source of derived data and at least one of the plurality of units; d. the processor capable of performing a first predictive computation to determine a change of state event from the raw data and the derived data; and, e. whereby the processor determines predictive information comprising a probability for the change of state event, and wherein the processer communicates the predictive information to the network, for display by one or more of the units.

2. The system of claim 1, wherein the raw data comprises one or more of a location of a fire, a location of smoke, a location of embers, a direction of movement of a fire, and an evacuation route.

3. The system of claim 2, wherein the at least one of the plurality of units is also a source of derived data.

4. The system of claim 3, wherein one of the fixed units is a EFMS.

5. (canceled)

6. (canceled)

7. (canceled)

8. (canceled)

9. The system of claim 1, wherein at least one of the plurality of units comprises a unit selected from the group consisting of cell tower, a traffic camera, a cell phone, an automobile navigation system.

10. (canceled)

11. The system of claim 1, wherein the plurality of fixed units comprising at least ten EFMS, wherein the at least ten EFMS are all located within a 10 mile radius, and thereby define a nodal area.

12. (canceled)

13. (canceled)

14. The system of claim 1, wherein the predictive information is specific to the nodal area.

15. (canceled)

16. The system of claim 1, wherein the predictive information is specific to the nodal area; wherein one or more of the mobile devices is associated with the nodal area; and wherein the nodal area specific predictive information is communicated to the mobile devices associated with the nodal area.

17. (canceled)

18. (canceled)

19. The system of claim 1, wherein the predictive information is specific to the nodal area; and wherein the specific predictive information comprises a notice to activate the EFMS; and wherein the EFMS is automatically activated by the system.

20. (canceled)

21. (canceled)

22. (canceled)

23. (canceled)

24. (canceled)

25. (canceled)

26. The system of claim 1, wherein at least one of the mobile units comprises a GUI configure to display at least one of the functionalities: a fire locations; I see fire; fire; heavy smoke; embers; fire danger; no fires in area; smoke in area; fire in area; fire nearby; track a wildfire; hotspots.

27. The system of claim 1, wherein at least one of the mobile units comprises a GUI configure to display at least one of the functionalities: emergency management alert; fire department alert; wildfire distance alert; and fire emergency checklist.

28. The system of claim 1, wherein at least one of the mobile units comprises a GUI configure to display at least one of the functionalities: EFMS status; EFMS system ready; EFMS sprinklers; activate systems; fire department alert; wildfire distance alert; and fire emergency checklist.

29. A system for obtaining, evaluating and displaying information and data regarding wildfires, EFMSs and mobile units, the system comprising: a. a plurality of mobile units configured to receive and transmit information, data or both regarding a wildfire, an EFMS or both, and over a network; i. wherein the units comprise a node on the network; ii. wherein the units comprise a means to determine the location of the unit; iii. wherein the unit comprising a processor, a memory device and a GUI; iv. wherein the information or data comprises one or more of a location of a fire, a location of smoke, a location of embers, a direction of movement of a fire, and an evacuation route; b. a plurality of fixed units configured to receive and transmit information and data over the network; i. wherein each unit comprises a node on the network; ii. wherein each units comprising a processor and a memory device; and, iii. wherein each unit is a component of an EFMS; and, c. wherein at least one of the mobile units is in control communication with at least one of the fixed units.

30. The system of claim 29, wherein the information or data comprises one or more of a location of a fire, a location of smoke, a location of embers, a direction of movement of a fire, and an evacuation route.

31. The system of claim 29, wherein the fixed units comprise a GUI.

32. (canceled)

33. (canceled)

34. (canceled)

35. The system of claim 29, comprising at least ten EFMS all located within a 5 mile radius and thereby define a nodal area.

36. (canceled)

37. (canceled)

38. (canceled)

39. (canceled)

40. (canceled)

41. The system of claim 29, wherein the information, data or both is specific to the nodal area; and wherein the specific information, data or both comprises a notice to activate the EFMS, and the activation notice appears on a mobile unit associated with the nodal area.

42. (canceled)

43. (canceled)

44. (canceled)

45. (canceled)

46. The system of claim 29, wherein at least one of the mobile units is configured for, and thereby in, direct communication with one or more predetermined unit; thereby defining a unit to unit communication pathway; wherein the unit to unit communication pathway is private.

47. (canceled)

48. (canceled)

49. (canceled)

50. (canceled)

51. A system for obtaining, evaluating and displaying in a predictive manner, information and data regarding an emergency, the system comprising: a. a plurality of units configured to provide raw data regarding the emergency; i. wherein each unit comprises a communication node on a communication network; ii. wherein at least one of the plurality of units is a mobile unit, comprising a processor and a GUI; and, iii. wherein at least one of the plurality of units is a fixed unit comprising a processor and a GUI; b. a source of derived data regarding one or more of a weather condition, a water level, a tidal condition, a seismic activity, a geologic condition, a river level, a traffic condition, water usage, an electrical usage, and an electric grid; i. wherein the source of derived data comprises a communication node on the communication network; c. a processor comprising a communication node on the communication network, thereby placing the processor in communication with the source of derived data and at least one of the plurality of units; d. the processor capable of performing a first predictive computation to determine a change of state event from the raw data and the derived data; and, e. whereby the processor determines predictive information comprising a probability for the change of state event, and wherein the processor communicates the predictive information to the network, for display by one or more of the units.

52. A system for obtaining, evaluating and displaying information and data regarding emergencies and mobile units, the system comprising: a. a plurality of mobile units configured to receive and transmit information, data or both regarding an emergency over a network; i. wherein the units comprise a node on the network; ii. wherein the units comprise a means to determine the location of the unit; iii. wherein the unit comprising a processor, a memory device and a GUI; iv. wherein the information or data comprises one or more of a weather condition, a water level, a tidal condition, a seismic activity, a geologic condition, a river level, a traffic condition, water usage, an electrical usage, and an electric grid; b. a plurality of fixed units configured to receive and transmit information and data over the network; i. wherein each unit comprises a node on the network; ii. wherein each units comprising a processor and a memory device; and, iii. wherein at least one of the fixed units is associated with a structure; and, c. wherein at least one of the mobile units is in control communication with at least one of the fixed units.

53. The system of claim 52, wherein the mobile unit is configure so that raw data is inputted by a user of the mobile unit.

54. The systems of any of the forgoing claims, wherein the raw data is automatically obtained from a sensor associated with the mobile unit.

55. An integrated system comprising a network having a plurality of nodes on the network, the integrated system comprising: a. a plurality of nodes on a network; b. a first node of the plurality of nodes associated with an EFMS, wherein the EFMS is associated with a structure; c. a second node of the plurality of nodes associated with a first mobile device having a first GUI; d. a third node of the plurality of nodes associated with a second mobile device having a second GUI; e. a fourth node of the plurality of nodes associated with a data processing assembly; whereby the data processing assembly is in communication with the EFMS, the first mobile device and the second mobile device; f. wherein the first and the second GUI comprises configurations to display an output, receive an input, or both of at least three of the functionalities of: fire location; I see fire; fire; heavy smoke; embers; fire danger; no fires in area; smoke in area; fire in area; fire nearby; track a wildfire; hotspots; and, g. wherein the second GUI comprises configurations to display an output, receive an input, or both of at least three of the functionalities of: EFMS status; EFMS system ready; EFMS sprinklers; activate systems; fire department alert; wildfire distance alert; and fire emergency checklist.

56. (canceled)

57. (canceled)

58. (canceled)

59. (canceled)

60. (canceled)

61. (canceled)

62. (canceled)

63. (canceled)

64. (canceled)

65. The system of claim 1, wherein the network is a pier to pier network having a plurality of EFMS control systems in direct communication with each other, using a communication protocol.

66. The system of claim 29, wherein the network is a pier to pier network having a plurality of EFMS control systems in direct communication with each other, using a communication protocol, wherein the protocol does not require the internet.

67. The system of claim 51, wherein the network is a pier to pier network having a plurality of EFMS control systems, having a local controller, in direct communication with each other, using a communication protocol, wherein the protocol LoRa.

68. The system of claim 52, wherein the network is a LoRaWAN® network architecture having a plurality of EFMS controllers in direct communication with each other, using a communication protocol, wherein the protocol LoRa.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG. 1A is a schematic of an embodiment of an emergency communications system in accordance with the present inventions.

[0045] FIG. 1B is a detailed schematic of an embodiment of a data processing assembly of the system of FIG. 1, in accordance with the present inventions.

[0046] FIG. 2 is a flow chart of an embodiment of approaches and a method to obtain predictive data in accordance with the present inventions.

[0047] FIG. 3 is a flow chart of an embodiment of approaches and a method to obtain predictive data in accordance with the present inventions.

[0048] FIG. 3A is a graph of an embodiment of uncertainty of an event over time in accordance with the present inventions.

[0049] FIG. 3B is a graph of the relative weight to be given different predictive information based upon the source of that predictive information over time in accordance with the present inventions.

[0050] FIG. 4 is a schematic of an embodiment of a EFMS in accordance with the present inventions, which can form a node on an embodiment of an emergency communications system in accordance with the present inventions.

[0051] FIG. 5 is a schematic of an embodiment of operations, log in, and options for units that are nodes on an embodiment of a network system in accordance with the present inventions.

[0052] FIG. 6 is an embodiment of an image of GUI display in accordance with the present inventions.

[0053] FIG. 7 is an embodiment of an image of GUI display in accordance with the present inventions

[0054] FIG. 8 is an embodiment of an image of GUI display in accordance with the present inventions.

[0055] FIG. 9 is an embodiment of an image of GUI display in accordance with the present inventions.

[0056] FIG. 10 is an embodiment of an image of GUI display in accordance with the present inventions.

[0057] FIG. 11A i is an embodiment of an image of GUI display in accordance with the present inventions.

[0058] FIG. 11B is an embodiment of an image of GUI display in accordance with the present inventions.

[0059] FIG. 11C is an embodiment of an image of GUI display in accordance with the present inventions.

[0060] FIG. 12 is a schematic plan view of an embodiment of an EFMS that forms a node on embodiments of an emergency communications system, such as the system of FIG. 1B, in accordance with the present inventions.

[0061] FIG. 13 is a schematic plan view of an embodiment of an EFMS that forms a node on embodiments of an emergency communications system, such as the system of FIG. 1B, in accordance with the present inventions.

[0062] FIG. 14 is a schematic side view of an embodiment of an under eave distribution head configuration of an EFMS in accordance with the present inventions.

[0063] FIG. 15 is a flow diagram schematic view of an embodiment of an EMFS and its operation in accordance with the present inventions.

[0064] FIG. 16 is a schematic of an embodiment of a universal power supply (UPS) for use with embodiments of an EFMS in accordance with the present inventions.

[0065] FIG. 17 is a flow diagram schematic view of an embodiment of an EMFS and its operation in accordance with the present inventions.

[0066] FIG. 18 is a schematic of an embodiment of a LoRa type system in accordance with the present inventions.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0067] The present inventions relate to networks, systems and the providing of derived data, predictive information, and adaptive strategies for use in multivariable component systems and activities, and in particular, for use in wildfire mitigation, management and suppression, including wildfire emergency response management. In particular, the present inventions relate to systems, networks and methods that provide derived data, predictive data, adaptive strategies, virtual data and combinations and variations of these, for multivariable component systems, such as for use in wildfire mitigation and management and suppression, including wildfire emergency response management.

[0068] More particularly, in embodiments, the present inventions relate to systems equipment and networks for the monitoring and collecting of raw data regarding wildfire responses, real time, historic and both. This raw data is then analyzed to provide derived data, predictive data, adaptive strategies, virtual data, and combinations and variations of this data, which depending upon the nature of this data may be packaged, distributed, displayed and used in various settings and applications.

[0069] The present inventions include the disclosure set forth in Appendix A, the entire disclosure of which is incorporated herein by reference, and becomes a part of this Specification. The present EMFS and communication systems provide, among other things, the hydration levels and operations set forth in Appendix A.

[0070] Turning to FIGS. 1A and 1B, there is provided an embodiment of a fire emergency communication system for a community. The communication system 100, has a network 101. The network 101 may be any type or combination of types of communication and data networks. Thus, for example, the network 101 can be a distributed network, a direct communication network, a control network, the internet, the world wide web, a wireless network, a cellular network, a Wi-Fi network, a hard wired network, an Ethernet network, a satellite network and combinations and variations of these, and other data and information communicate equipment and process that are presently known and may become known in the future.

[0071] The fire emergency communication system 100 has several nodes or communication points, each node or communication point having one or more receiving device, monitoring device, transmitting device and combinations and variations of these. There is a node 110 that is associated with a residential area, e.g., a nodal area. There is a node 105 that is associated with a rural area, e.g., a nodal area. There is a node 103 that is associated with an area having access to a limited access highway, e.g., an intersection nodal area. There is a node 104 that is associated with an urban area, e.g., an urban nodal area. Each of these nodes, also has a number of individual nodes within, or associated with them. The individual nodes within a node, form a nodal area, nodes that are mobile can move from one nodal area to another nodal area.

[0072] It is understood, that one, tens, and hundreds of nodal areas, each having one, tens and hundreds of nodes, can be associated with the communication system 100, and network 101. Moreover, multiple networks, such as network 101, can be associated with, or a part of, the communication system 100.

[0073] The number and types of nodal areas may vary, from situation to situation, community to community, from public services team/organization to public services team/organization and may vary before, during and after a wildfire.

[0074] The number and types of individual nodes, in any given nodal area, may vary, from situation to situation, community to community, from public services team/organization to public services team/organization and may vary before, during and after a wildfire.

[0075] In the embodiment of FIG. 1A, the network 101 of fire emergency communication system 100 has as individual nodes: dwelling (house, apartment building, condo building, hotel) 112, dwelling (house, apartment building, condo building, hotel) 114, mobile device (cell phone, On-star, apple watch, etc.) 115, mobile device (cell phone, On-star, apple watch, etc.) 116, First Responder (police, Ambulance, EMS (emergency medical services), Red Cross, National Guard, etc.) 117, school 118, first responder unit 120, fixed location monitoring station, data collection and transmission device (positioned on, e.g., cell town, power line pole, etc.) 121, dwelling (e.g., ranch, etc.) 122, airport 125, first responder 133, fixed location monitoring station, data collection and transmission device (positioned, e.g., on a traffic light, associated with a traffic camera, etc.) 136, cell tower (fixed data collection and transmission device) 137, monitoring station, fixed data collection and transmission device 138, mobile device (cell phone, On-star, apple watch, etc.) 140, Emergency Management (head quarter, command center, etc.) 143, police department 144, fire department 145, Ambulance 146, Hospital 147, business (office, retail shop, restaurant, manufacturing, etc.) 150, traffic camera/red light camera (fixed data collection and transmission device) 151, and fixed data collection and transmission device (e.g., positioned on or with a cell tower 152).

[0076] Further these nodes may be viewed as sub-nodes of a larger node. For example fire emergency communication system 101 could be included as a sub-node in a larger communication network, having one, tens, hundreds of similar fire emergency communications systems.

[0077] The individual nodes typically and preferably have GUI. They may have associated keyboards, key pads, touch screens, voice control, etc., and combinations and variations of these. The GUI have displays that among other things have graphics for providing information about traffic, fire location, evacuation, evacuation routes, location of gas stations, location of first responders, as well as, the ability to have user input of real time data, e.g., user location, presence of ambers, visibility, proximity to fire, traffic conditions. Preferably, icons, windows or screens are provided on the GUI by an application (app) that is loaded onto a mobile device, such as a smart phone, tablet or vehicle GPS/navigation system. The GUI may also be configured to provide real time, historic, derived, predictive, and virtual data. The GUI may be configured to have private access on the then network to another node on the network. For example, mobile device 140 may have a private communications path with dwelling 112, enabling mobile device to display real time raw data (e.g., images, temperature) of the conditions around dwelling 112 and send instruction to dwelling 112. For example, to activate a fire suppression system for dwelling 112. The monitoring unit of dwelling 112 may also have a processor, or be in communication (control communication) with the processing system to automatically activate the fire suppression system for dwelling 112, sent notifications to mobile device 140 recommending activation of the fire suppression system for dwelling 112, as well as, sending notice that the fire suppression system has been activated. The notices may also be broadcast over the entire network, only to the area where the node or dwelling is located, only to first responders (e.g., emergency services, fire, police, ambulance etc.) and combinations and variations of these.

[0078] The network 101, has several communication pathways. These pathways may be over the same routes, or portions of the network 101, they may share some but not all routes, they may be totally separate, and combinations and variations of these. Each route or pathway may have its own proprietary communication protocol, it may use a publicly available protocol. The protocols may include, but are not limited to CoAP, MQTT, AMQP, WAMP, LoRAWAN, LoRa, IPv4, or IPv6. The communication, e.g., the data and information set over the pathway may be encrypted, protected, or otherwise encoded, such that only an intended recipient can receive it, for example a predetermined recipient, e.g., an individual who has taken the necessary steps to rightfully receive information and data from the data processing assembly 139.

[0079] Each individual node preferably has the ability to receive and transmit data and information. However, a node only needs the ability to receive or transmit data or information. For example, in some embodiments of monitoring stations they may only transmit data and information.

[0080] Turning to the residential area 110, there is shown a schematic representation of an example of a residential area. (The residential area may be a part of, adjacent or far removed from the other areas in the system.) The residential area 110 has street 111. The various node in this area each have communication pathways: dwelling 112 has communication pathway 112a, mobile device 115 has communication pathway 115a, mobile device 116 (which is in dwelling 114) has communication pathway 116a, first responder 117 has communication pathway 117a, school 118 has communication pathway 118a. In addition, dwelling 114 has a private security system that has a communication pathway 114a to a private security provider. As discussed below, such nodes, e.g., 114, can be brought into the system 100, by the private security provider feeding, i.e., providing or transmitting, data and information from its network or customers to the processing system 139.

[0081] Turning to the rural area 105, there is shown a schematic representation of an example of a rural area. (The rural area may be a part of, adjacent or far removed from the other areas in the system.) The rural area 110 has winding, narrow country road 107, a large area 108 (shown by dotted line) that contains significant fuel sources for a wildfire, and power lines 106. The various nodes in this area each have communication pathways: first responder unit 120 has communication pathway 120a, monitoring station 121 has communication pathway 121a, dwelling 122 has communication pathway 122a, cell tower fixed data collection and transmission device 137 has communication pathway 137a, and monitoring station 138 has communication pathway 138a. And, airport 125, which is adjacent to residential area 110 and rural area 105 has communication pathway 125a,

[0082] Turning to the limited access highway area 103, there is shown a schematic representation of an example of a limited access highway and its surroundings. (The limited access highway area may be a part of, adjacent or far removed from the other areas in the system.) The limited access highway area 103 has a multilane limited access highway 131 having multiple on and off ramps, e.g., 132, and a street 130. The various nodes in this area each have communication pathways: monitoring station 136 has communication pathway 136a, mobile device 140 has communication pathway 140a, and first responder 133 has communication pathway 133a.

[0083] Turning to the urban area 104, there is shown a schematic representation of an example of an urban area. (The urban area may be a part of, adjacent or far removed from the other areas in the system.) The urban area 104 has a street 141 that intersects street 142. The various nodes in this area each have communication pathways: traffic camera/red light camera 151 has communication pathway 151a. And a fixed data collection and transmission device (e.g., positioned on or with a cell tower 152) adjacent to the urban area 104, has communication pathway 152a. In addition, business 150 has a private security system that has a communication pathway 150a to a private security provider. As discussed below, such nodes, e.g., 150, can be brought into the system 100, by the private security provider feeding, i.e., providing or transmitting, data and information from its network or customers to the processing system 139.

[0084] Emergency Management (head quarter, command center, etc.) 143, has communication pathway 143a, police department 144 has communication pathway 144a, fire department 145 has communication pathway 145a, ambulance service 146 has communication pathway 146a, and hospital 147 has communication pathway 147a.

[0085] The network 101 has pathway 102 that connects the network to processing system 139 (as shown in greater detail in FIG. 1B). Here one path way is shown, it being understood that multiple pathways to the processing system 139, multiple processing systems and combinations and variations of these can be used.

[0086] The network 100 can have multiple private pathways. For example, a dwelling can have an external fire protection system that has a control system, sensors, actuators and communication pathway. This external fire protection system has a private communication pathway with processing system 139, as well as, with one or more mobile devices that also connect to processing system 139 and directly or through the processing system to the control system of the dwelling's fire protection system. There may be tens, hundreds or more of these private pathways. As the processing system 139 receives more data and information it can determine if recommendations to start a particular dwelling's fire protection system should be sent, or if the command to start the system should be sent. This can also be done on an area by area basis.

[0087] Thus, for example, the processing system 139 is receiving real time raw data from multiple nodes in the network that provide real time information about, for example traffic patterns, location of fire, speed of fire, direction of movement of the fire, wind speed and direction, humidity, number and location of persons, location of first responders. The processing system 139 also has access to historic data, such as prior weather, prior fire patterns, prior traffic patterns, surveys of fuel sources for the fire, and geographic terrain. The processing system using the real time raw data, and preferably, but not necessarily, the historic data can provide derived data about fire movement, traffic patterns, resource allocation, preferably this derived data can be predictive data. Different forms, and types of this derived data and predictive data can then be transmitted out onto the network to different nodes. For example, the information a mobile device may receive could be limited to the status of a fire suppressions system linked to that device, the proximity of the fire, the predicted path of the fire, traffic and suggested evacuation routes. The information provided to first responders and emergency management HQ could be far more extensive. For example, historic data about the number of dwellings having external fire suppression systems in a particular area, the fuel sources in that area, coupled with real time raw data about the number of people in that area, could be used to determine the placement of first responders, and the need for evacuations.

[0088] Nodes, nodal areas, individual nodes may be organized and configured into various sub-nodes. These sub-nodes can be private or semi-private or public. For example, a company could have a private sub-node for its employees, and within that a sub-node for its fleet of vehicles. Similarly, a school could have a sub-node for its children and parents. A sub-node could include all of the nodes that are external fire management systems, and then have sub-nodes for particular types of system, e.g., by provider, level of services, etc.

[0089] Turning to FIG. 1B, there is shown a schematic of an embodiment of a data processing system or assembly 139. The data processing system 139 has a network 190 that provides communication pathways to the components of the data processing system 139. The data processing system has a network 190 for transferring information and data between the various components. Incoming information, from pathways 191, 192, 193, is received by unit 194. Pathways 191, 192 and 193 are other sources of raw data, historic data and even predictive and derived data. Processor 195, which may be a computer, has the algorithms and programs to provide the derived data and predictive information, as well as, provide adaptive responsive strategies. Processor 195 also preferably controls the network traffic with and between storage devices 196, 197,198 and unit 199. Unit 199 is for sending and receiving information to and from the network 101. It should be understood that system 139 may itself be distributed over a network, or reside on the cloud. Unit 194 and 199 may be the same unit, or they may be multiple separate or distributed units, and combinations and variations of these.

[0090] Unit 199 receives and provides information, data and control communication to and from the data processing system 190 to the network 101. Data to individuals is sent along pathways 180 for standard data and content, and along path 181 for premium data and content. For example, standard data may show only public service announcements and other official information from the authorities. Premium data, can show predicted fire movement, number and location of external fire management systems (and their status over time).

[0091] Both of these individual data streams, sets or packets, e.g., data for individuals, travels along pathway 102 of network 101. This data for individuals travels along pathway 102 to a smart phone, tablet, such as an iPad®, a GUI in an automobile (dash display), or other GUI, where one or more of raw data, derived data, adaptive strategy information and predictive data are presented on the display. Thus, for example, data may travel along pathway 181 to pathway 102 to one or more individual pathways (e.g., 113a) or to a nodal area, e.g., 110, or the entire network. The data is then displayed on the GUI associated with the node (e.g., 113) and information may be input into the GUI and then transmitted along the individual pathway to the network pathway 102, to a pathway, e.g., 181.

[0092] The other pathways from unit 199, e.g., pathway 182, 184, 186, etc., are for other custom or special communication or sub-networks. Thus, by way of example, pathway 182 can be for controlled communication for external fire management systems. Realtime raw data, derived data, adaptive strategy information and predictive data may be sent to a user's mobile node, a fixed node on the external fire management system and both. The user can then monitor the information and elect to send a command to the external fire management system to, for example, become read, to operate, or to operate upon a certain set of conditions. The system 139 can send predictive data, e.g., recommending that the external fire management system is activated. The system 139 can also send information, data, or a command to one or more external fire management systems that cause the system(s) to operate.

[0093] In this manner the system 139 can provide derived data and adaptive strategies, to individuals and entire areas, in a direct response to changing fire conditions. This provides the ability to save fire suppression resources (i.e., water, foam) until they are absolutely needed, to use them in the most efficient manner, both on a micro level (each individual system, or structure) and on a macho level, (most efficient use of systems, and activation/operation strategy to protect an area).

[0094] By way of example, pathway 184 can be non-public and exclusive to fire response teams. Pathway 185 can be non-pubic and exclusive to all first responders. Pathway 183 is for communication with network television and social media. This pathway allows specified data and information from the system 139 to be broadcast to a GUI 186, e.g., a TV or computer monitor, on public networks and social medial.

[0095] Generally, the sources for incoming raw data for use in, or to form a basis for, the algorithms and mathematical computations that a processor performs to provide derived data and predictive information and adaptive strategies, can come from various sources, including for example: individual mobile devices (e.g., input from persons, first responders, emergency services, satellites), fixed monitoring devices (e.g., cell tower mounted devices, external fire suppression system, fire services, weather services, traffic monitors, first responders, emergency services, etc.).

[0096] Because of the complexity and unpredictability of wild fires, fire emergency and the reactions of persons, although a single approach may be used, in an embodiment a multi-approach system approach is used, the multi-approach having two, three, four or more approaches performed at the same time to determine a set of approach values for a given event at a given point in the fire emergency. These approach values, e.g., probability of event occurring, are then given weightings based upon their individual accuracy for a particular point in the fire emergency, e.g., rural fire, fire size, population levels, population density in relation to ingress and egress routes, start (activation) of an external fire management system, number of EFMSs in a location, etc. The weighted approach values are then combined to provide a predicted value, i.e, derived data of a predictive nature, such as for example an adaptive strategy, a recommendation to activate a particular EFMS, a warning to evacuate, etc.

[0097] Turning to FIG. 2, there is shown a flow chart of an embodiment of a method of using a three-approach system 390 to provide derived data that is predictive of an event 300, e.g., fire reaching location A at time T. A mathematical approach 301 looks at real time raw data and historic derived data and determines a probability 301 for event 300 to occur. Another mathematical approach 302, uses calculations different from approach 301, and looks to real time raw and derived data and determines a probability 312 for event 300 to occur. Another approach 303, which may be the same mathematical approach as approach 301 or approach 302, or may be different from both, looks to other data, not relied upon in approaches 302, 303 and provides a probability 313 for event 300 to occur.

[0098] The time T, 325, or provided 326) when the prediction of even 300 is possible to occur is then selected by an individual, e.g., emergence services person, home owner, school principal, etc.

[0099] Weighting factors X, X′, X″ based upon T are then applied to the predicted values 311, 312, 313 to render weighted predicted values 321, 322, 323. Preferably the weighting facts are predetermined 326 for each value of T, or they may be determined based upon predetermined parameters at the time of use. The weight values can be any integer, or fraction. The weighted predictive values 321, 322, 323 are then combined to provide a predicted value 340 for event 300 at time Z, e.g., 80% chance that fire reaches “Shady Acers” in the next 90 minutes. The resulting predicted value 340 is then transmitted to, accessible by and combinations and variations of these a network (e.g, 101) of fire emergency communication system (e.g., 100)

[0100] Turning to FIG. 3, there is provided a flow chart for an embodiment of a two-approach system 400. A statistical approach 401 and a deterministic model approach 402 are used.

[0101] The statistical approach 401 uses real time raw data, real time derived data and historical derived data in an appropriate probability distribution, such as a gamma probability distribution, beta-binomial probability distribution, standard normal probability distribution, beta probably distributions, or the Dirichlet probability distribution. Thus, for example approach 401 can use current fire position, current humidity, current wind speed, and current wind direction, to project the probability of the fire reaching location A, over a period of time ΔT into the future.

[0102] The time T, 425, when the prediction of even 444 is possible to occur is then selected by an individual, e.g., emergence services person, home owner, school principal, etc.

[0103] Weighting factors X, X′, X″ based upon T are then applied to the predicted values 411, 412, to render weighted predicted values 421, 422. Preferably the weighting facts are predetermined 426 or each value of T, or they may be determined based upon predetermined parameters at the time of use. The weight values can be any integer, or fraction. The weighted predictive values 421, 422 are then combined to provide a predicted value 440 for event 444 at time Z, e.g., 80% chance that fire reaches “Shady Acers” in the next 90 minutes. The resulting predicted value 440 is then transmitted to, accessible by and combinations and variations of these, a network (e.g, 101) of fire emergency communication system (e.g., 100)

[0104] As ΔT becomes larger the uncertainty around probability value 411 increases. Thus, FIG. 3A shows a curve 493 of future uncertainty vs increasing ΔT. Similarly as ΔT increases, e.g., one is looking to predict further out into the future, the certainty, and thus the relative weight for certain data used in the approach change. Thus, as shown in FIG. 3B, the relative weight of the current fire position 490 decreases as the prediction is further out in time; while the relative weight of the historic trend data 491 increase when the point for the prediction is further out as time, e.g., increasing ΔT

[0105] The deterministic model approach 402 has higher certainty in predicting events that are not as far out into the future, i.e., smaller ΔT values. In particular the deterministic model approach 402 has greater certainty of its values as larger amount of data are acquired from the fire emergency.

[0106] Other forms of derived data use generalized machine learning algorithms such as Support Vector Machines to predict or classify fire emergency events. These predictions or classifications are forms of derived data. One possible prediction is the probability that a fire will jump a highway or natural barrier. Support Vector Machines may be trained on historical data to create a classifier that can predict the probability that fire will behave in a certain manner.

[0107] Inferential techniques can be used to determine traffic patterns and availability of ingress and egress routes. These techniques would take as input raw data and/or other pieces of derived data. Inference could be performed, for example, via use of heuristics based on traffic pattern knowledge, real time traffic information from waze, google maps etc., or statistical techniques for pattern recognition.

[0108] In some uses, derived and predictive data and virtual data are displayed to users through a client, e.g. a web browser. These data are sent to the client from a server, or from other clients. In some situations, the client will request new data constantly because it is difficult to know if a particular piece of data has been updated. Preferably, the client and/or server is able to determine which data are likely to have changed at a point in time, and therefore prioritize the communication of data that are likely to have changed. This scheme decreases unneeded communication between clients or between clients and servers. The server may determine that particular data are likely to have changed and push that data to the client, or the client may determine that particular data are likely to have changed and request those data from another client or a server.

EXAMPLES

[0109] The following examples are provided to illustrate various embodiments of systems, devices, methods, and uses and displays of derived, predictive “adaptative strategies and virtual data. These examples are for illustrative purposes, may be prophetic, and should not be view as, and do not otherwise limit the scope of the present inventions.

Example 1

[0110] FIG. 4 is a schematic of an embodiment of a EFMS 500. The controller 580 is connected to the network of a fire emergency communications system by one of two or both path ways, i.e., cellular and WiFi to home internet. One, two, ten or more structures in an area can have these EFMS 500. The EFMS can include a manifold 510, a foam system 520, a tie in 530, a pump kit 540, a point of connection 550, a satellite antenna 581, an solar kit 482, and a UPS (universal power supply). These components are associated with a structure (e.g., a house) 560.

Example 2

[0111] The EFMS and devices of US Patent Publication 2019/0262637, the entire disclosure of which is incorporated herein by reference, form a node or nodes on the fire emergency communications system. One, two, ten or more structures in an area can have these EFMS.

Example 3

[0112] An emergency management control network and system, e.g., the embodiment of FIG. 1, one, two, five, tens, hundreds and more EFMS that are on the emergency management control network and system. The network can have EFMS the configure of the embodiment of FIGS. 4, 11, as well as other configurations. The data processing assembly (e.g., 139), based upon raw data received from various nodes on the network, processes that raw data to provide predictive information about the location and movement of a wildfire. The predictive information is communicated over the network. The predictive information can be a control command to a particular EFMS system, such as to arm, to operate, and to stop operations. This control command information can be sent to a group of EFMS in a nodal area, e.g., a predetermined nodal area.

Example 4

[0113] Turning to FIG. 5. there is shown a schematic flow diagram 600 of operations for the log in of a unit having a GUI, (e.g., a smart phone, tablet, computer, watch, etc.) as a node on the network and the various options of information, data and communication (e.g., control communication) that are available for the unit. Thus, there is a splash screen 605 for GUI. From screen 605 the system determines if the user is logged in. If the user is not logged in the user is then sent to, e.g., shown, screen 602 which is a demo or demonstration screen 602. From the demonstration screen 605 there are two options. The user can be sent to the sign in screen 601, or the user can be sent to screen 603, where the user can view, experience the demonstration, e.g., anonymous browsing of the application. From screen 601 the information entered by the user, e.g., logged in as a specific type of user, or creates an account as a specific type of user, is processed and the user, depending upon whether logged in or not can be sent to the demo screen 602, the free version of the application screen 604, the premium version screen 606, or to a system owner screen 607. It being understood that there are many unique additional screens, information and materials that are contained within, or are available through, each of the screens 602, 603, 604. Further, it being understood that additional types of user screens, and corresponding information and materials can be used, e.g., public safety officials, building managers, first responders.

[0114] The anonymous browsing that is accessed through screen 603 can be for example: [0115] Intended to allow a zero-commitment test drive [0116] No account information • uses phone location as a default [0117] All free functionality except: [0118] Only one Push Notification whenever the app is entered in AB mode, a single push notification is sent that illustrates what could be received if signed in with an account (free or otherwise) [0119] Wherever a location is required for functionality, the phone's location is used by default, and the option to enter an address is offered [0120] Whenever any data is entered (address. Group name. Group Members. Follow a news source or fire event, etc.), a reminder is shown stating that no data will be saved for future use unless signed in

[0121] The free version of the application that is accessed through screen 604 can be for example: [0122] Becomes the “trial” version because it offers a ‘taste’ of every premium feature, but there is no expiration [0123] Partial account information—just email address and home address, mobile number [0124] All Premium features with the following limitations: [0125] Only one home location [0126] Only one Emergency Group with only two members [0127] Only 1-2 News sources [0128] Only (2 or 3) Push notifications/month [0129] When any feature limit above is reached, user is presented with option to have more with Premium

[0130] The premium version of the application that is accessed through screen 606 can be for example: [0131] All major features of the app [0132] Complete account information, including payment [0133] No limitations (we may want some limitations on number of groups, members, etc., but high enough that it full capacity is rarely used)

[0134] The system owner version of the application that is accessed through screen 607 can be for example: [0135] All premium features of the application [0136] Plus monitoring, control, and activation of a EFMS

Example 5

[0137] Turning to FIG. 6 there is shown a screen and functionality for a unit functioning as an anonymous user on a node on the network. This screen is available to premium users and systems owners, and can also be available to free users.

Example 6

[0138] Turning to FIG. 7 there shown is a screen and functionality for a unit functioning as an anonymous user on a node on the network. This screen is available to systems owners.

Example 7

[0139] Turning to FIG. 8 there is shown is a screen and functionality for a unit functioning as an anonymous user on a node on the network. This screen is available to systems owners.

Example 8

[0140] Turning to FIG. 9 is a screen and functionality for a unit functioning as an anonymous user on a node on the network. This screen is available to systems owners.

Example 9

[0141] Turning to FIG. 10 there is shown a screen and functionality for a unit functioning as an anonymous user on a node on the network. This screen is available to premium users and systems owners, and can also be available to free users.

Example 10

[0142] Turning to FIGS. 11A to 11C there is shown a screen and functionality for a unit functioning as an anonymous user on a node on the network. One or more of these screens is available to premium users and systems owners, but can also be available to free users.

Example 11

[0143] Screens and functionality for a unit functioning as an anonymous user on a node on the network can have access to and show maps, of the area, and these maps can contain information such as fire location, predicted path of fire, location of first responders, evacuation routes, etc. These screens are available to premium users and systems owners, and can also be available to free users.

Example 12

[0144] Turning to FIG. 12 there is shown a schematic of an EFMS 1200. One, two, five, tens, hundreds and more can be part of an emergency management control network and system. The network can have EFMS of other configurations as well. The data processing assembly based upon raw data received from various nodes on the network processes the raw data to provide predictive information about the location and movement of a wildfire. The predictive information is communicated over the network. The predictive information can be a control command to a particular EFMS system, to arm, to operate, and to stop operations. This control command information can be sent to a group of EFMS in a nodal area.

[0145] System 1200 provides an outer coverage zone 1201 that has an outer boundary 1221. The boundary 1221 is 30 ft from the walls 1224 of the house. The system 1200 provides an inner coverage zone 1220, that has an inner boundary 1222. Boundary 1222 is 5 ft from the walls 1224. The system 1200 has distribution heads 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209. When the system is activated, these distribution heads provide foam, water and combinations of foam and water to zone, 1220, zone 1201, and combinations and variations of these zones. The system is installed in a house that has an outer roof line 1203, that extend outwardly from the outer walls 1224, and thereby defines an eave. The zones 1201 and 1220 can be further subdivided into sub-zones. In this manner the system can be operated to provide water, foam, etc. to various sub-zones and combinations of sub-zones.

Example 13

[0146] In an embodiment there is provided an EFMS 1300 of the type shown in FIG. 13. System 1300 provides a coverage zone that has an outer boundary. The boundary is 5 ft from the walls of the house. The system 1300 has plurality of distribution heads. When the system is activated, these distribution heads provide foam, water and combinations of foam and water to the coverage zone and combinations and variations of these zones. The system is installed in a house that has an outer roof line, that extends outwardly from the outer walls, and thereby defines an eave. The zone can be further subdivide into sub-zones. In this manner the system can be operated to provide water, foam, etc. to various sub-zones and combinations of sub-zones.

Example 14

[0147] Turning to FIG. 14 there is a cross sectional schematic drawing of a distribution head 1410 installed under an eave 1420. There is also shown the outer roof line 1421, and a portion of the outer wall 1422.

Example 15

[0148] Turing to FIG. 15 there is shown a schematic flow diagram of an embodiment of an EFMS, which could be of the general type shown in the embodiments of FIG. 4, 12, or 13. In this system there are two controllers. A first controller (e.g., motor controller) having I/O connected to pumps valves and other sensors and device for the operation of the sprinklers and water, foam and both distribution. This first controller has a control program or control logic that controls the operation of the mechanical devices and sensors. The first control is in control communication with a second controller (e.g., Network Communication Device). This controller has a control program or control logic that can be an operating system. The second controller is configured for network communication to the cloud, pier to pier communication to other controllers in other EFMS, to make determinations based on fire, humidity, etc. sensors or other sources of data, and to provide instructions to the first controller. Thus, for example, the second controller based upon received information can make a determination to send an activation instruction to the first controller.

Example 16

[0149] Turing to FIG. 17 there is shown a schematic flow diagram of an embodiment of an EFMS which could be of the general type shown in the embodiments of FIG. 4, 12, or 13. In this system there are two controllers. A first controller (e.g., motor controller) having I/O connected to pumps valves and other sensors and device for the operation of the sprinklers and water, foam and both distribution. This first controller has a control program or control logic that controls the operation of the mechanical devices and sensors. The first control is in control communication with a second controller (e.g., Network Communication Device). This controller has a control program or control logic that can be an operating system. The second controller is configured for network communication to the cloud, pier to pier communication to other controllers in other EFMS, to make determinations based on fire, humidity, etc. sensors or other sources of data, and to provide instructions to the first controller. Thus, for example, the second controller based upon received information can make a determination to send an activation instruction to the first controller.

Example 17

[0150] In embodiments the systems, e.g., an EFMS, the second controller of a two controller embodiment, such as the embodiment of Examples 15 or 16, the servers and processors in the cloud (e.g., API) can perform, require or both, validations before an EFMS is activated to disperse water, foam or both. Thus, if information is received indicating that a fire is near by the structure, this information held, and then validated with other information to confirm the accuracy of the initial information. One, two, three or more validations can be performed before an activation. Because these systems can have a large number of related inputs, the time for this validation will be very short. For example, less than 1 minute, less than 30 seconds, less than 15 seconds, less than 10 second. Moreover, this information can be stored and shared between EMFSs, the API, or other memory devices. This information will be location based. Thus, in this manner, in an embodiment, the validations can take place in even shorter periods and time, and essentially be instantaneous.

Example 18

[0151] An embodiment of the present networks and systems can be configured and implemented to manage a hurricane emergency.

Example 19

[0152] In an embodiment, enhancements in speed can be achieved by inter controller communication on the network. For example, one controller can let another controller know that it has activated, and if a second controller lets other controllers know it has been activated, then there is logic that can be applied to activate the controller receiving the activate information. The communication path for communicating between controllers does not need to be via the cloud, but rather through radio communication, such as a LoRa type system, including LoRaWAN®. FIG. 18 provides a schematic of an example of an architecture for LoRa type system.

Example 20

[0153] An embodiment of an EMFS, systems of Examples 15 and 16 uses a LoRaWAN® network architecture. In an embodiment this architecture is deployed in a star-of-stars topology in which gateways relay messages between end-devices and a central network server. The gateways are connected to the network server via standard IP connections and act as a transparent bridge, simply converting RF packets to IP packets and vice versa. The wireless communication takes advantage of the Long Range characteristics of the LoRaO physical layer, allowing a single-hop link between the end-device and one or many gateways. All modes are capable of bi-directional communication, and there is support for multicast addressing groups to make efficient use of spectrum during tasks such as Firmware Over-The-Air (FOTA) upgrades or other mass distribution messages.

[0154] In an embodiment the EMFS, for use in this Example, is for instance one of the type of systems of Examples 15 and 16.

Example 21

[0155] An embodiment of the EMFS system has a UPS of the type shown in FIG. 16. The output from the UPS is always drawing from the batteries, and the AC is used to maintain and top off the batteries. The EMFS system in this Example, could be of the type in FIG. 4, 12 or 13.

[0156] It is noted that there is no requirement to provide or address the theory underlying the novel and groundbreaking performance or other beneficial features and properties that are the subject of, or associated with, embodiments of the present inventions. Nevertheless, various theories are provided in this specification to further advance the art in this important area, and in particular in the important area of lasers, laser processing and laser applications. These theories put forth in this specification, and unless expressly stated otherwise, in no way limit, restrict or narrow the scope of protection to be afforded the claimed inventions. These theories many not be required or practiced to utilize the present inventions. It is further understood that the present inventions may lead to new, and heretofore unknown theories to explain the operation, function and features of embodiments of the methods, articles, materials, devices and system of the present inventions; and such later developed theories shall not limit the scope of protection afforded the present inventions.

[0157] The various embodiments of networks, systems for providing and displaying data and information set forth in this specification may be used in the above identified fields and in various other fields. Additionally, these embodiments, for example, may be used with: existing networks, emergency systems, social media systems, alert systems, broadcast systems, as well as other existing equipment; future systems and activities; and such items that may be modified, in-part, based on the teachings of this specification. Further, the various embodiments set forth in this specification may be used with each other in different and various combinations. Thus, for example, the configurations provided in the various embodiments of this specification may be used with each other. For example, the components of an embodiment having A, A′ and B and the components of an embodiment having A″, C and D can be used with each other in various combinations, e.g., A, C, D, and A. A″ C and D, etc., in accordance with the teaching of this Specification. The scope of protection afforded the present inventions should not be limited to a particular embodiment, configuration or arrangement that is set forth in a particular embodiment, example, or in an embodiment in a particular Figure.

[0158] The invention may be embodied in other forms than those specifically disclosed herein without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive.