WO2016151061A1

WO2016151061A1 - Wearable-based health and safety warning systems

Info

Publication number: WO2016151061A1
Application number: PCT/EP2016/056474
Authority: WO
Inventors: John Cronin; Seth Cronin; Christopher HUFFINES
Original assignee: Koninklijke Philips N.V.
Priority date: 2015-03-24
Filing date: 2016-03-24
Publication date: 2016-09-29

Abstract

Wearable-based health and safety warning systems and methods associated with the same are provided. A wearable-based health and safety warning system may include a beacon (105, 300) and a wearable device (110, 200). The beacon uses a sensor (325-345) to record a first set of data associated with an environment in which the beacon is positioned. In some embodiments, the beacon may also receive a second set of data from a third party over a network (120). The second set of data is associated with a geography in which the beacon is positioned. The beacon may create a warning notification for a user of the wearable device based on the recorded first set of data and the received second set of data. The beacon may then broadcast the warning notification over the network, which the wearable device may receive and convey to the user.

Description

WEARABLE-BASED HEALTH AND SAFETY WARNING SYSTEMS TECHNICAL FIELD

[0001] This disclosure concerns wearable technology. More particularly, the present disclosure concerns wearable-based health and safety warning systems and methods associated with the same.

BACKGROUND

[0002] Wearable electronic devices, or as sometimes used herein, "wearable technology," is a new class of electronic systems that may be worn by a user and that provide data acquisition through a variety of unobtrusive sensors. The sensors gather information, for example, about the environment, the user's activity, or the user's health status. However, there are significant challenges related to the coordination, computation, communication, privacy, security, and presentation of the collected data. Additionally, there are challenges related to power management given the current state of battery technology. Furthermore, analysis of the data is needed to make the data gathered by the sensors useful and relevant to end-users. In some cases, additional sources of information may be used to supplement the data gathered by the sensors. The many challenges that wearable technology presents require new designs in hardware and software.

[0003] Wearable technology may include any type of mobile electronic device that can be worn on the body, attached to or embedded in clothes and accessories of an individual, and currently existing in the consumer marketplace. Processors and sensors associated with the wearable technology can display, process, or gather information. Such wearable technology has been used in a variety of areas, including monitoring health of the user as well as collecting other types of data and statistics. These types of devices may be readily available to the public and may be easily purchased by consumers. Examples of some wearable technology in the health arena include the FitBit Flex™, the Nike Fuel Band™, the Jawbone Up™, and the Apple Watch™.

[0004] Smart beacons are systems featuring transmitters that communicate with nearby devices. Although smart beacons like the iBeacon™ produced by Apple Inc. of Cupertino, California have many applications relating to health and safety, they are not currently used in a ubiquitous way to inform users of wearable devices about safety hazards. Smart beacons can function as health and safety beacons. For instance, smart beacons can be fitted with a wide range of sensors, such as those that can detect ice, air pollutants, fire, ultraviolet radiation, fire, heavy traffic, and other hazards. Smart beacons can also be programmed to broadcast any type of message, including severe weather alerts or pertinent health and safety information. Despite these capabilities, there is presently no way for wearable technologies to receive broadcasts from a health and safety beacon.

SUMMARY OF THE DISCLOSURE

[0005] It is an object of the present disclosure to provide wearable-based health and safety warning systems, and methods associated with the same are also provided.

[0006] A first aspect of the present disclosure includes a wearable-based health and safety warning system. The system may include a beacon and a wearable device. In some embodiments, the beacon may include: a sensor to detect a first set of data associated with an environment in which the beacon is positioned, the first set of data including data pertaining to one or more sensed physical attributes of an environment in which the beacon resides, a processor to create a warning notification for a user of a wearable device based on the first set of data, and a beacon network interface to broadcast the warning notification over a communication network. In some embodiments, the wearable device may include: a wearable device network interface to receive the warning notification broadcast over the communication network by the beacon, and a user interface to convey the warning notification to a user of the wearable device.

[0007] A second aspect of the present disclosure includes a method for notifying a wearable device user of a health and safety hazard. The method may include: detecting, at a wireless communication module of a wearable device, a presence of a beacon based on a network broadcast range associated with the beacon; establishing a wireless network connection between the wearable device and the beacon; receiving, at the wearable device via the wireless network connection, a warning notification from the beacon based on a first set of data recorded by a sensor of the beacon, wherein the first set of data is associated with an environment in which the beacon is positioned; and conveying, by the wearable device, the warning notification to a user of the wearable device by way of a graphical user interface.

[0008] A third aspect of the present disclosure relates to a non-transitory computer- readable storage medium including a computer program that, when executed by a processor, performs a method for notifying a wearable device user of a health and safety as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 illustrates an example wearable-based health and safety warning system, according to an embodiment of the present disclosure.

[0010] FIG. 2 illustrates an example wearable device, according to an embodiment of the present disclosure.

[0011] FIG. 3 illustrates an example beacon, according to an embodiment of the present disclosure.

[0012] FIG. 4 illustrates an example settings graphical user interface of a wearable device, according to an embodiment of the present disclosure.

[0013] FIG. 5 illustrates an example notifications graphical user interface of a wearable device, according to an embodiment of the present disclosure.

[0014] FIG. 6 illustrates an example computing device architecture, according to an embodiment of the present disclosure.

[0015] FIG. 7 illustrates an example operational process of a base software module stored in memory and executed by a processor of a wearable device, according to an embodiment of the present disclosure.

[0016] FIG. 8 illustrates an example operational process of a beacon software module stored in memory and executed by a processor of a beacon, according to an embodiment of the present disclosure.

[0017] FIG. 9 illustrates an example operational process of a network software module stored in memory and executed by a processor of a safety network device or system, according to an embodiment of the present disclosure.

[0018] FIG. 10 illustrates an example operational process of a third-party data software module stored in memory and executed by a processor of a beacon, according to an embodiment of the present disclosure.

[0019] FIG. 11 illustrates an example operational process of notifications software stored in memory and executed by a processor of a wearable device, according to an embodiment of the present disclosure.

[0020] FIG. 12 illustrates an example operational process of a warning software module stored in memory and executed by a processor of a beacon, according to an embodiment of the present disclosure. [0021] FIG. 13 illustrates an example operational process of a broadcast software module stored in memory and executed by a processor of a beacon, according to an embodiment of the present disclosure.

[0022] FIG. 14 illustrates an example location database stored in memory of a safety network system or device, according to an embodiment of the present disclosure.

[0023] FIG. 15 illustrates an example warning database stored in memory of a beacon, according to an embodiment of the present disclosure.

[0024] FIG. 16 illustrates an example method for sending health and safety warning notifications to a wearable device, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

[0025] Wearable-based health and safety warning systems, and methods associated with the same, are described herein. In various embodiments, a system configured with selected aspects of the present disclosure may include a wearable technology and a smart beacon communicatively coupled by a network. The system may include, for instance, a wearable device communicatively coupled to a health and safety beacon. The wearable device may be any kind of wearable device, such as one primarily intended to be worn around a user's neck (e.g. , a necklace), arm (e.g. , an armband), head (e.g. , hat, helmet, headband, or headlamp), leg, wrist (e.g., a watch), chest, or waist (e.g., a belt or body band), foot (e.g., a shoe or sock), ankle or knee (e.g., a knee brace), or any other area of a user's body. The wearable device may also be a device that is primarily intended to be held in a user's hand or stored in a user's pocket. The wearable device may also be a device meant to be worn over the skin (e.g. , a patch) or under the skin (e.g. , an implant).

[0026] The health and safety beacon may include one or more sensors that detect data related to health and safety considerations (e.g. , data pertaining to nearby ice, air pollutants, fire, ultraviolet radiation, heavy traffic, and other hazards). By collecting data locally using one or more sensors, rather than relying on data stored in a remote database, the health and safety beacon may gather and subsequently transmit data to wearable device users as quickly as possible. In doing so, the health and safety beacon may ensure that the messages it transmits are current and relevant to the wearable device user.

[0027] The health and safety beacon may also receive and store data originating from a third-party source, such as a severe weather network, a crime report network, or a medical alerts network. The health and safety beacon may include executable instructions stored in memory that, when executed by a processor, broadcast a message over a network. The wearable device may receive the message from the health and safety beacon via the network. The message may include data, alerts, notifications, warning, or other types of information related to health and safety hazards (e.g., severe weather alerts, crime alerts, or medical alerts). The wearable device may receive the message from the health and safety beacon in real-time or near real-time. The wearable device may receive passively and without having to affirmatively access known databases or other sources of information. Rather, the wearable device may rely on one or more beacons (e.g., a network of dispersed health and safety beacons) to transmit messages as appropriate based on various contextual considerations.

[0028] FIG. 1 illustrates an example wearable-based health and safety warning system

100. In one embodiment, system 100 may include a beacon 105 that obtains data from various sensors (See FIG. 3) and other sources. Beacon 105 may be a smart beacon and, in some cases, may be a health and safety beacon or a "safety health bacon" as labeled in FIG. 1. As will be shown in more detail in FIG. 3, beacon 105 may include a processor, memory, and a network interface that sends and receives data over a network. Beacon 105 may further include one or more sensors that detect external data, such as data indicative of a nearby health or safety hazard. In various embodiments, obtaining the data may include detecting the data with a sensor disposed in the beacon 105 and/or receiving the data from a third-party source 1 15 (e.g., a safety network, which may include data from a severe weather network, a crime report network, a medical alerts network, or another type of network). Beacon 105 may include memory that stores executable instructions. Execution of the instructions by the processor of beacon 105 may cause the beacon 105 to broadcast and/or transmit the data it obtains from one or more sensors or third-party sources 1 15.

[0029] System 100 may further include a wearable device 1 10 communicatively coupled to beacon 105 over a communications network 120. Network 120 may include one or more of a wide area network, a local area network, the Internet, a cloud-based network, a personal area network, a combination of the foregoing, or any other suitable network.

Communication between wearable device 1 10, beacon 105, and in some embodiments third- party source 1 15, may be wireless and may include the use of near field communication (NFC), Wi-Fi, Bluetooth (e.g., low powered Bluetooth), 4GLTE, ZigBee, or other suitable communication infrastructures or protocols. Wearable device 1 10 may include one or more antennae 125 or other network interface by which wearable device 1 10 may communicate over network 120. As will be shown in FIG. 2, wearable device 1 10 may include executable instructions stored in memory. Execution of the instructions by a processor of wearable device 1 10 may cause wearable device 1 10 to receive the data broadcast or transmitted by beacon 105 (e.g., in the form of notifications) and convey the data to a user of wearable device 1 10. Wearable device 1 10 may convey the data by to the user by rendering and displaying the data in the form of a graphical user interface ("GUI") (e.g., where the data is text, image, video, or other visual data) or by other suitable means (e.g., by playing the data back through a speaker where the data is audio data, or with haptic feedback).

[0030] In some embodiments, third-party source 1 15 from which beacon 105 may receive data may be a health network and/or safety network. As shown in the example of FIG. 1 , third-party source 1 15 is portrayed for illustrative purposes as a safety network. While not depicted in FIG. 1 , safety network 1 15 may include a processor, a network interface, and memory. The memory of safety network 1 15 may store executable network software 130, a location database 135, a network database 140, and an executable application programming interface ("API") module 145. API module 145 may allow one or more third- party networks 150 (e.g., a severe weather network 155, a crime report network 160, a medical alerts network 165, etc.) to update network database 140 with localized third-party data. The localized third-party data may be a severe weather alert, an alert about crime in the area, an alert about medical emergencies in the area, or other types of information. Persons of ordinary skill in the art will readily recognize and appreciate that the types of data described in the present disclosure are merely exemplary and that the disclosed system suggests the use of many other possible types of data.

[0031] As shown in FIG. 1 , third-party data 170 flows from the one or more third- party networks 150 to safety network 1 15, from safety network 1 15 to beacon 105, and from beacon 105 to wearable device 1 10. In some cases, beacon 105 may edit, alter, manipulate, or supplement the data before broadcasting or transmitting the data to wearable device 1 10 as one or more notifications 175. Beacon 105 may, for instance, combine the received data 170 with data locally detected using sensor-based detection methods. Wearable device 1 10 may then receive the data (whether comprising solely third-party data 170 in original or edited form, or also comprising locally-detected sensor data) and convey the data to the user of wearable device 1 10. Wearable device 1 10 may, for instance, display the data as a visual notification. Additionally or alternatively, notifications may take the form of audio, video, and/or haptic notifications. As a result, where the data is health and safety data, the user may become better informed about his or her local circumstances and any nearby health and safety hazards.

[0032] In some embodiments, system 100 may include a plurality of smart beacons

105 communicatively coupled by network 120 or one or more subnetworks (e.g., an internal network dedicated to communication between beacons 105 that is communicatively coupled to network 120). Smart beacons 105 may be health and safety beacons. Health and safety beacons 105 may obtain health and safety information by sensor-based detection methods, from one or more third parties sources 1 15 (e.g., a third-party weather network), or through other suitable means. Smart beacons 105 may include executable instructions stored in memory that, when executed by a processor, broadcasts or transmits the health and safety information to wearable device 1 10 positioned within the broadcast proximity of the networked health and safety beacons 105.

[0033] A user wearing an example wearable device 1 10 may, for instance, be walking on foot. The user may walk into the network broadcast range of the one or more health and safety beacons 105. The wearable device 1 10 of the user may then automatically detect and establish a connection with the one or more health and safety beacons 105. One or more health and safety beacon 105 may then broadcast or transmit relevant health and safety information to wearable device 1 10, such as a text-based notification 175 that reads:

"Warning! Beacon sensors detect ice on the sidewalk ahead. Please walk carefully." The text data may also read, for example, "SEVERE WEATHER ALERT! Blizzard conditions in this area expected today from 5 PM to 10 PM." Smart beacon 105 may determine which health and safety information to send to wearable device 1 10 based on time considerations (e.g., the current time of day, the amount of time left until a detected hazard, the season of the year, etc.). The text data may read, for example, "SEVERE WEATHER ALERT! Blizzard conditions in this area expected today from 5 PM to 10 PM. The current time is 7 PM. Seek shelter." In some embodiments, broadcasting the warning notification over the network may include addressing and transmitting the warning notification directly to wearable device 1 10 as opposed to broadcasting the notification generally over the network. The user of wearable device 1 10 may then adjust his or her behavior accordingly.

[0034] In some embodiments, wearable device 1 10 may transmit user-specific data collected by way of one or more sensors (e.g., 230-250 in FIG. 2) to beacon 105. Beacon 105 may then issue warning notifications tailored to the user-specific data. For instance, where a body temperature sensor of wearable device 1 10 detects that the core body temperature of the user is lower than normal, wearable device 1 10 may transmit the temperature data to beacon 105. Beacon 105 may then take the user-specific temperature data received from wearable device 1 10 into account when determining which warning notifications to transmit to that particular user of that particular wearable device 1 10. If faced which a choice between transmitting a cold front warning notification and a crime safety alert notification, for instance, beacon 105 may give higher priority to the cold front warning notification in light of the lower than normal body temperature already experienced by the user of wearable device 1 10.

[0035] The wearable-based health and safety warning system described herein may be applied in a diverse array of scenarios. System 100 may, for instance, allow community organizers to have an API to access health and safety beacon 105 and to notify a plurality of users of wearable devices 1 10 of health, fitness, and safety events.

[0036] In some embodiments, upon receiving a notification 175 from beacon 105, wearable device 1 10 may further transmit, broadcast, or relay the received notification 175 to a second wearable device 1 10, even when out of range of originating beacon 105 or when originating beacon 105 has gone offline. A plurality of wearable devices 1 10 may relay notifications 175 and other beacon data between one another so as to form a wearable device notification network. The relay of beacon notifications 175 or data between wearable devices 1 10 may, in some embodiments, be automatic and may not require any affirmative user action (e.g., the relay functionality may automatically turn on when a connection with beacon 105 is detected as having been lost). In other embodiments, the user of wearable device 1 10 may manually select one or more notifications 175 or portions of beacon data and one or more specific wearable device users to which notifications 175 or other data should be transmitted. Wearable device 1 10 may include an executable software module that, when executed, determines what other wearable devices 1 10 may be proximate to the user and to which a received beacon notification 175 or data may likewise be relevant to the users of those other wearable devices 1 10. The software module may utilize GPS, other proximity tracking functionality, or network-related data to determine whether any other wearable devices 1 10 are proximate to the user.

[0037] In various embodiments, system 100 may incorporate a crowd-sourced network that permits a user of wearable device 1 10 to receive a unique identification number associated with a nearby health and safety beacon 105. The user may then report to the crowd-sourced network information pertinent to the user's location, which in turn maybe rebroadcast from beacon 105 to other wearable device users. A user might, for instance, receive a notification 175 concerning heavy car traffic near the user. The user may later report that he or she witnessed an accident one mile up the road from where the user received the original notification 175 about the heavy traffic. Beacon 105 may then notify the next wearable device that establishes a connection with beacon 105 not only about the heavy traffic nearby, but also about the accident reported earlier by the other wearable device user.

[0038] In some embodiments, system 100 may involve personal, modular beacons

105 that allow a user to attach sensors specific to their needs. A user may, for example, want his or her personal beacon 105 to have an ice sensor in the winter, a UV sensor during the summer, and/or a wind speed sensor year round.

[0039] In one embodiment, system 100 may incorporate general purpose beacons 105 that store and broadcast one or more predefined notification. A beacon 105 may, for instance, store a notification that reads "Construction in this area 8 AM to 6 PM, Tuesday 3/2— Seek alternative route." The beacon may broadcast that single message to users of wearable devices 1 10 in proximity of the construction area throughout the week leading up to the date "3/2." As noted above, a first wearable device 1 10 may rebroadcast the notification to a second wearable device 1 10 over network 120. Doing so may allow wearable device users to obtain important notifications and beacon data even when an originating beacon 105 is out of network range or has become unavailable (e.g., gone offline).

[0040] In some embodiments, a first wearable device 1 10 communicatively coupled to beacon 105 may detect when beacon 105 becomes unavailable. In response, first wearable device 1 10 may automatically scan for and detect one or more other wearable devices 1 10 that subsequently connect to network 120 or attempt to establish a connection with unavailable beacon 105. First wearable device 1 10 may then automatically rebroadcast the last warning notification 175 received from beacon 105 (or a predetermined number of most recent notifications 175) to any detected one or more other wearable devices 1 10. In such embodiments, first wearable device 1 10 may effectively act as a surrogate beacon 105 to ensure that any subsequently connecting wearable devices 110 at least receive any

notifications beacon 105 was able to broadcast before it became unavailable.

[0041] In some embodiments, beacon 105 may include sensors (e.g., 325-345 in FIG.

3) that detect data related to a user of wearable device 1 10. Beacon 105 may include, for instance, a radar gun that detects the velocity of a moving person or object. A user may, in one possible scenario, run past beacon 105. In response, beacon 105 may detect the user running speed and update its broadest in real time to notify the user of his or her running speed (e.g., 10 miles per hour). In one embodiment, system 100 may include mobile beacons 105 used for special events (e.g., marathon runs). Mobile beacons 105 may communicate with wearable devices 110 to inform users about their current distance, time, etc. (e.g., distance to the next water station).

[0042] In a further embodiment, system may include functionality responsible for transmitting audio broadcasts (i.e., notifications 175) regarding crosswalks and street obstructions for the blind or visually impaired. In such cases, the warning notifications 175 may concern closed sidewalks, uneven terrain, and other health and safety considerations relevant to the blind and visually impaired.

[0043] Persons of ordinary skill in the art will readily recognize and appreciate that the foregoing embodiments have merely been described for illustrative purposes and that they are in no way limiting. In view of the present disclosure, persons will appreciate that many other embodiments and implementations are possible.

[0044] FIG. 2 schematically illustrates an example wearable device 200. As illustrated in FIG. 2, an example wearable device 200 may include a plurality of components. In some embodiments, the components may be connected by a single bus 205, as illustrated in FIG. 2. In other embodiments, the components may be connected through multiple buses 205. The plurality of components may include a processor 210, memory 215, a power supply 220, a display 225, one or more sensors (e.g., an activity sensor 230, blood pressure sensor 235, heart rate sensor 240, temperature sensor 245, or another type of sensor 250), a wired or wireless communications module 255 (e.g., a USB port module, a Fire Wire port module, a Lightnight port module, a Thunderbolt port module, a Wi-Fi connection module, a

3G/4G/LTE cellular connected module, a Bluetooth connection module, a lower powered Bluetooth connection module, a near field communication module, etc.). In some

embodiments, wearable device 200 may further include a global position system ("GPS") module 260.

[0045] Memory 215 may be operable to store, and processor 210 of wearable device

200 may be operable to execute, a wearable device operating system ("OS") 265, a wearable device base software module 270, and a notifications software module 275. The OS may be a Microsoft Windows™ OS, a Google Android™ OS, an Apple™ OS, or any other suitable OS. Wearable device 200 may store in memory 215 one or more sets of executable instructions that, when executed by the processor of the wearable device, render and display a GUI. Wearable device 200 may store, for instance, executable instructions operable to render and display a settings GUI (e.g., a settings GUI module 280). Wearable device 200 may also store in memory 215 executable instructions operable to render and display a notifications GUI (e.g. , a notifications GUI module 285). The wearable device 200 may further store one or more databases in memory (e.g. , a settings database 290, a wearable database 295, etc.).

[0046] FIG. 3 illustrates an example beacon 300. Beacon 300 (e.g. , a health and safety beacon) may include a plurality of components. In some embodiments, the

components may be connected by a single bus 305, as illustrated in FIG. 3. In other embodiments, the components may be connected through multiple buses 305. The plurality of components may include a processor 310, memory 315, a power supply 320, and one or more sensors (e.g., an ice sensor 325, an ultraviolet radiation sensor 330, an air quality sensor 335, a temperature sensor 340, or any other suitable sensor 345 that detects local

environmental data). The components may further include a global position system ("GPS") module 350 and a wired or wireless communications module 355 (e.g., a USB port module, a Fire Wire port module, a Lightnight port module, a Thunderbolt port module, a Wi-Fi connection module, a 3G/4G/LTE cellular connected module, a Bluetooth connection module, a lower powered Bluetooth connection module, a near field communication module, etc.).

[0047] Memory 315 may store, and processor 310 of beacon 300 may be operable to execute, a beacon operating system ("OS") 360. Memory 315 may further be operable to store, and processor 310 of beacon 300 may further be operable to execute, one or more sets of instructions or routines (e.g. , software modules or applications), such as beacon software module 365, broadcast software module 370, warning software module 375, or third-party data software module 380. Beacon 300 may further store one or more databases in memory (e.g., a beacon database 385, a warnings database 390, or a third-party database 395). When communicatively coupled to safety network 1 15 of FIG. 1 or other form of third-party network service, beacon 300 may receive updated health and safety data. One or more of databases 385, 390, and 395 may then be automatically updated with the received data.

[0048] FIG. 4 illustrates an example settings GUI 400 (e.g., indicated at 280 in FIG.

2). Settings GUI 400, which a wearable device (e.g. , wearable device 300 of FIG. 3) may render and display by way of executing instructions stored in memory, may include a plurality of user-selectable fields (e.g., buttons, checkboxes, free form tillable fields, etc.). Settings GUI 400 may, for instance, include selectable elements 410 through which the wearable device may receive a user's selection to either receive or not receive health and safety data (e.g., in the form of notifications) from the beacon. Settings GUI 400 may also include selectable elements 420 through which the wearable device may receive a user's selection to either receive or not receive health and safety data from the beacon that originated from a third-party network. Settings GUI 400 may further include selectable elements 430 through which the wearable device may receive a user's selection to either receive or not receive health and safety data originating from certain specific networks (e.g. , a severe weather network, a crime report network, a medical alerts network, or other networks.). Settings GUI 400 may include a selectable element 440 through which the wearable device may receive a user's instruction save the configured settings to a settings database (e.g., 290 in FIG. 2) stored in memory of the wearable device.

[0049] FIG. 5 illustrates an example notifications GUI 500 (e.g., indicated at 285 in

FIG. 2). A wearable device (e.g., wearable device 200 of FIG. 2) may render and display notifications GUI 500 by way of executing instructions stored in memory. Notifications GUI 500 may include displayed health and safety notifications. The notifications may specify whether the health and safety data was obtained locally through a sensor-detection method or whether the data was received over a network from a third-party source (e.g. , a severe weather network). As shown in FIG. 5, for instance, notifications GUI 500 may display the following health and safety notifications 510: "Warning," "Beacon sensors detect ice on the sidewalk, please walk carefully." Notifications GUI 500 may further display a health and safety notification 520 based on data received from a third-party source, such as "SEVERE WEATHER ALERT: Blizzard conditions in this area expected from 5 PM to 10 PM today. Seek shelter." Notifications GUI 500 may specify that the latter data originated from a third- party source by displaying a label 530 reading "3^rd Party Data from Severe Weather

Network" or the like. Notifications GUI 500 may further include a selectable element 540 that, when selected by the user, displays additional information to the user. In some instances, selectable element 540 may be a hyperlink to a website run by the third-party network. The hyperlink may, for example, direct a user to a webpage that displays the current radar map of the user's geographic area. In other embodiments, the selection of selectable element 540 may cause notifications GUI 500 to display a secondary GUI displaying the information.

[0050] FIG. 6 illustrates an example computing device architecture 600 that may be utilized to implement the various features and processes described herein. For example, computing device architecture 600 could be implemented in wearable device 1 10, beacon 105, or a computer system of safety network 1 15. Architecture 600 as illustrated in FIG. 6 may include memory interface 602, processors 604, and peripheral interface 606. Memory interface 602, processors 604 and peripherals interface 606 may be separate components or may be integrated as a part of one or more integrated circuits. The various components may be coupled by one or more communication buses or signal lines.

[0051] Processors FIG. 6 illustrates an example computing device architecture 600 as illustrated in FIG. 6 is meant to be inclusive of data processors, image processors, central processing unit, or any variety of multi-core processing devices. Any variety of sensors, external devices, and external subsystems can be coupled to peripherals interface 606 to facilitate any number of functionalities within the architecture 600 of the exemplar mobile device. For example, motion sensor 610, light sensor 612, and proximity sensor 614 can be coupled to peripherals interface 606 to facilitate orientation, lighting, and proximity functions of the mobile device. For example, light sensor 612 could be utilized to facilitate adjusting the brightness of touch surface 646. Motion sensor 610, which could be exemplified in the context of an accelerometer or gyroscope, could be utilized to detect movement and orientation of the mobile device. Display objects or media could then be presented according to a detected orientation (e.g., portrait or landscape).

[0052] Other sensors (not specifically depicted in FIG. 6, but generally referenced at

616) may be coupled to peripherals interface 606, such as a temperature sensor, a biometric sensor, or other sensing device to facilitate corresponding functionalities. A location processor (e.g., a global positioning transceiver) can be coupled to peripherals interface 606 to allow for generation of geo-location data thereby facilitating geo-positioning. An electronic magnetometer such as an integrated circuit chip could in turn be connected to peripherals interface 606 to provide data related to the direction of true magnetic North whereby the mobile device could enjoy compass or directional functionality. Camera subsystem 620 and an optical sensor 622 such as a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor can facilitate camera functions such as recording photographs and video clips.

[0053] Communication functionality can be facilitated through one or more communication subsystems 624, which may include one or more wireless communication subsystems. Wireless communication subsystems 624 can include 802.x or Bluetooth transceivers as well as optical transceivers such as infrared. Wired communication system can include a port device such as a Universal Serial Bus (USB) port or some other wired port connection that can be used to establish a wired coupling to other computing devices such as network access devices, personal computers, printers, displays, or other processing devices capable of receiving or transmitting data. The specific design and implementation of communication subsystem 624 may depend on the communication network or medium over which the device is intended to operate. For example, a device may include wireless communication subsystem designed to operate over a global system for mobile

communications (GSM) network, a GPRS network, an enhanced data GSM environment (EDGE) network, 802.x communication networks, code division multiple access (CDMA) networks, or Bluetooth networks. Communication subsystem 624 may include hosting protocols such that the device may be configured as a base station for other wireless devices. Communication subsystems can also allow the device to synchronize with a host device using one or more protocols such as TCP/IP, HTTP, or UDP.

[0054] Audio subsystem 626 can be coupled to a speaker 628 and one or more microphones 630 to facilitate voice-enabled functions. These functions might include voice recognition, voice replication, or digital recording. Audio subsystem 626 in conjunction may also encompass traditional telephony functions.

[0055] I/O subsystem 640 may include touch controller 642 and/or other input controller(s) 644. Touch controller 642 can be coupled to a touch surface 646. Touch surface 646 and touch controller 642 may detect contact and movement or break thereof using any of a number of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, or surface acoustic wave technologies. Other proximity sensor arrays or elements for determining one or more points of contact with touch surface 646 may likewise be utilized. In one implementation, touch surface 646 can display virtual or soft buttons and a virtual keyboard, which can be used as an input/output device by the user.

[0056] Other input controllers 644 can be coupled to other input/control devices 648 such as one or more buttons, rocker switches, thumb-wheels, infrared ports, USB ports, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of speaker 628 and/or microphone 630. In some implementations, device 600 can include the functionality of an audio and/or video playback or recording device and may include a pin connector for tethering to other devices.

[0057] Memory interface 602 can be coupled to memory 650. Memory 650 can include high-speed random access memory or non- volatile memory such as magnetic disk storage devices, optical storage devices, or flash memory. Memory 650 can store operating system 652, such as Darwin, RTXC, LINUX, UNIX, OS X, ANDROID, WINDOWS, or an embedded operating system such as Vx Works. Operating system 652 may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system 652 can include a kernel.

[0058] Memory 650 may also store communication instructions 654 to facilitate communicating with other mobile computing devices or servers. Communication instructions 654 can also be used to select an operational mode or communication medium for use by the device based on a geographic location, which could be obtained by the GPS/Navigation instructions 668. Memory 650 may include graphical user interface instructions 656 to facilitate graphic user interface processing such as the generation of an interface; sensor processing instructions 658 to facilitate sensor-related processing and functions; phone instructions 660 to facilitate phone-related processes and functions; electronic messaging instructions 662 to facilitate electronic-messaging related processes and functions; web browsing instructions 664 to facilitate web browsing-related processes and functions; media processing instructions 666 to facilitate media processing-related processes and functions; GPS/Navigation instructions 668 to facilitate GPS and navigation-related processes, camera instructions 670 to facilitate camera-related processes and functions; and instructions 672 for any other application that may be operating on or in conjunction with the mobile computing device. Memory 650 may also store other software instructions for facilitating other processes, features and applications, such as applications related to navigation, social networking, location-based services or map displays.

[0059] Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 650 can include additional or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.

[0060] Certain features may be implemented in a computer system that includes a back-end component, such as a data server, that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of the foregoing. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Some examples of communication networks include LAN, WAN and the computers and networks forming the Internet. The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0061] One or more features or steps of the disclosed embodiments may be implemented using an API that can define on or more parameters that are passed between a calling application and other software code such as an operating system, library routine, function that provides a service, that provides data, or that performs an operation or a computation. The API can be implemented as one or more calls in program code that send or receive one or more parameters through a parameter list or other structure based on a call convention defined in an API specification document. A parameter can be a constant, a key, a data structure, an object, an object class, a variable, a data type, a pointer, an array, a list, or another call. API calls and parameters can be implemented in any programming language. The programming language can define the vocabulary and calling convention that a programmer will employ to access functions supporting the API. In some implementations, an API call can report to an application the capabilities of a device running the application, such as input capability, output capability, processing capability, power capability, and communications capability.

[0062] FIG. 7 illustrates an example operational process 700 of a base software module stored in memory and executed by a processor of a wearable device (e.g., wearable device 1 10 of FIG. 1). In an example embodiment, the base software module may, at block 710, poll any sensors present in the wearable device for sensor data. At block 720, the base software module may then store the sensor data in a wearable database. The base software module may allow a user to input settings by way of a settings GUI at block 730. At block 740, the settings may be stored in a settings database stored in memory of the wearable device. The base software module may then, at block 750, open or establish wearable device communications functionalities. At block 760, the base software module may poll one or more beacons for data that the wearable may potentially receive from the one or more beacons. At block 770, when a beacon connects to the wearable device, the wearable device may then execute a notifications software module stored in memory of the wearable device (e.g., notifications software module 275 of FIG. 2). By way of the executing the notifications software module, the wearable device may receive notifications (e.g., health and safety information) form the one or more beacons and, at block 780, convey the notifications to the user of the wearable device. The wearable device may, for instance, display the notifications through a GUI (e.g., notifications GUI 500 of FIG. 5).

[0063] FIG. 8 illustrates an example operational process 800 of a beacon software module stored in memory and executed by a processor of a beacon (e.g., health and safety beacon 105 of FIG. 1). In an example embodiment, the beacon software module may, at block 810, poll any sensors present in the beacon for sensor data. Among other things, at least some of these sensors may provide data about one or more physical attributes of an environment in which the beacon resides, such as temperature, presence of ice, ultraviolet light, air quality, traffic, and so forth.

[0064] At block 820, the beacon software module may then store any resulting sensor data in a beacon database stored in memory of the beacon. The beacon may execute third- party data software stored in memory at block 830. Upon executing the third-party data software, the beacon may determine that a third-party network notification (e.g., a network warning) is available. When a third-party network notification is available, the beacon may execute broadcast software stored in memory of the beacon. Upon executing the broadcast software, the beacon may broadcast or transmit the third-party network notification to the wearable device. At block 840, the beacon may also execute warning software stored in memory. Upon executing the warning software, the beacon may determine that a beacon sensor data indicates a health and/or safety hazard. When the sensor data indicates that a health and/or safety hazard is present, the beacon may execute broadcast software stored in memory of the beacon. Upon executing the broadcast software, the beacon may broadcast or transmit a notification concerning the health and/or safety hazard to the wearable device. The beacon may then repeat the foregoing operational flow, looping back to polling operation 810.

[0065] FIG. 9 illustrates an example operational process 900 of a network software module stored in memory and executed by a processor of a safety network device or system (e.g., safety network 1 15 of FIG. 1 , or one or more other servers or computing devices). In an example embodiment, the network software module may, at block 910, allow third-party networks to populate a network database with third-party data (e.g., severe weather warnings, crime reports, geolocations, etc.) via an API. Geolocations may be geolocations associated with the third-party data such that, at block 920, the network software module may match the geolocation of third-party data in the network database with geolocations of beacons (e.g., health and safety beacons) stored in a location database. At block 930, the network software module may then transmit the third-party data to beacons with matched geo locations. The safety network or device may transmit the data over a wide area network, a local area network, the Internet, a cloud-based network infrastructure, or other type of network. By matching geo locations, the safety network device or system may ensure that third-party data only goes to appropriate beacons that are located in a suitable location to which the data is contextually relevant.

[0066] FIG. 10 illustrates an example operational process 1000 of a third-party data software module stored in memory and executed by a processor of a beacon (e.g., health and safety beacon 105 of FIG. 1). In an example embodiment, the third-party data software may, at block 1010, open or establish beacon communications functionality. The software may, for instance, establish a connection with a network (e.g. , wide area network, a local area network, the Internet, a cloud-based network infrastructure, or other type of network). At block 1020, the software may then receive third-party data from a safety network device or system. At block 1030, the software may store any received third-party data in a third-party database.

[0067] FIG. 1 1 illustrates an example operational process 1 100 of a notifications software module stored in memory and executed by a processor of a wearable device (e.g., wearable device 1 10 of FIG. 1). Upon being executed, the notifications software module may, at block 1 1 10, retrieve one or more settings from a settings database stored in memory of the wearable device. At block 1 120, the wearable device may determine whether the retrieved one or more settings allow the wearable device to receive beacon notifications. As illustrated at block 1 130, when the one or more settings do not permit the wearable device to receive beacon notifications, the wearable device may close any communication links (e.g., by disabling its communications functionality) and execute a base software module stored in memory. As illustrated at block 1 140, when the one or more settings permit the wearable device to receive beacon notifications, the wearable device may receive notifications from a beacon (e.g., health and safety beacon 105 of FIG. 1). At block 1 150, in response to receiving a notification from a beacon, further execution of the notifications software module may cause the wearable device to determine whether the notification contains third-party data (e.g., received from a safety network device or system communicatively coupled to one or more third-party network sources). If the answer is no, then at block 1 190, the wearable device may the notification. However, if the answer at block 1 150 is yes, then at block 1 160, the notifications software module may determine whether one or more settings stored in the settings database permit the wearable device to display notifications containing third-party data. The wearable device may also determine from which specific third-party networks the wearable device may receive third-party data. In some embodiments, the type of notification permitted may further be determined (e.g., push notifications versus other types of notifications). When the settings permit such notifications, at block 1 170, the notifications software module may display the notification to the user (e.g., via notifications GUI 500 of FIG. 5). Having displayed the notification, the wearable device may, at block 1 180, end the communication link with the beacon and execute a base software module stored in memory.

[0068] Back at block 1 160, if the settings do not permit the wearable device to display notifications containing third-party data, the wearable device may display a notification that omits any third-party data at block 1 190. Then method 1 100 may proceed to block 1 180, and notifications software module (275 in FIG. 2) may then close the communication link and execute a base software module.

[0069] FIG. 12 illustrates an example operational process 1200 of a warning software module stored in memory and executed by a processor of a beacon (e.g., health and safety beacon 105 of FIG. 1). Upon being executed, the warning software module may, at block 1210, retrieve beacon sensor data from a beacon database stored in memory of the beacon (or, in some embodiments, in a separate and distinct device communicatively coupled to the beacon). The beacon sensor data may be associated with a particular sensor disposed in the beacon. At block 1220, the beacon may then determine whether the beacon sensor data matches a hazard range specified in a warnings database stored in memory of the beacon. As illustrated at block 1230, when the retrieved beacon data does not match the hazard range specified in the warnings database, the beacon may determine whether all sensors have been checked for beacon data. When all sensors have been checked for data, the beacon may execute a beacon software module stored in memory at block 1240.

[0070] Back at block 1220, when the beacon sensor data does match the hazard range, then at block 1250 the beacon may retrieve warning message data associated with the beacon sensor data. At block 1260, the beacon may then pass the warning message data to a broadcast software module stored in memory of the beacon, which may subsequently act upon the warning message data when executed. The beacon may then determine whether all sensors have been checked for beacon sensor data as described in the context of block 1230. When all sensors have been checked for data, the beacon may execute a beacon software module stored in memory at block 1240. When all sensors have not been checked for beacon data yet, the operational process may loop back around to block 1220 and may repeat the process for the next sensor disposed in the beacon.

[0071] FIG. 13 illustrates an example operational process 1300 of a broadcast software module stored in memory and executed by a processor of a beacon (e.g., health and safety beacon 105 of FIG. 1). Upon being executed, the broadcast software module may, at block 1310, receive one or more warning messages (i.e., warning message data) from a warning software module stored in memory and executed by a processor of the beacon. At block 1320, the beacon may then receive third-party data from a third-party data software module stored in memory and executed by a processor of the beacon. The third-party data may, as described above, concern health and safety considerations relevant to the user of a wearable device. At block 1330, the beacon may generate one or more beacon messages. The one or more beacon messages may include health and safety information, including warning messages and any third-party data. The beacon may then, at block 1340, broadcast or transmit the beacon message over a network to a wearable device. The beacon may execute a base software module stored in memory at block 1350.

[0072] FIG. 14 illustrates an example location database 1400 stored in memory of a safety network system or device (e.g. , safety network 1 15 of FIG. 1). More particularly, FIG. 12 illustrates a table displaying five columns labeled "Beacon ID" 1410, "MAC Address" 1420, "Geolocation" 1430, "City" 1440, and "State" 1450, respectively. From left to right, first column 1410 may include beacon identification information (e.g., an identification number unique to each beacon catalogued in the location database). Second column 1420 may include message authentication check ("MAC") address information for each beacon. The MAC addresses may permit one or more software-enabled devices to communicate with one another (e.g., two beacons) by using their respective MAC addresses as a location or address by which to contact each other. Third column 1430 may include geolocation data (e.g., coordinate data). Fourth column 1440 and fifth column 1450 may each include location data, such as the city and state in which each beacon is located. As portrayed in FIG. 14 for illustrative purposes, a beacon may have an ID of "iBeaconl ," a MAC address of

"00:0a:95 :9d:68: 16," and a geolocation of 44.4758 degrees north, 73.21 19 degrees west. The beacon may be located in Burlington, Vermont. The table structure shown in FIG. 14 is merely illustrative. In various embodiments, the table structure and overall database architecture may vary as needed to suit the various design considerations in play at the time the system is being implemented.

[0073] FIG. 15 illustrates an example warning database 1500 stored in memory of a beacon (e.g., health and safety beacon 105 of FIG. 1). As described above, a warning software module stored in memory and executed by a processor of the beacon may access the warning database and determine whether current sensor data matches a hazard range of each warning. The warning software module then may then retrieve a warning message associated with that hazard range. FIG. 13 illustrates a table of database 1500 displaying three columns labeled "Sensor" 1510, "Hazard Range" 1520, and "Warning Message" 1530, respectively. From left the right, first column 1510 may include information about each sensor. The information may identify a sensor as an ice sensor, an ultraviolet radiation sensor, an air quality sensor, a temperature sensor, or the like. Second column 1520 may include hazard range data for each sensor, while third column 1530 includes a corresponding warning message to be transmitted to a wearable device when sensor data matches the listed hazard range data. For an ice sensor identified in first column 1510, for instance, the hazard range identified in second column 1520 may be "ICE = YES." Thus, when the ice sensor data indicates the presence of ice, the sensor data will match the specified hazard range of "ICE = YES," which may then cause the beacon to transmit the corresponding warning "Beacon sensors detect ice on the sidewalk, please walk carefully" stored in third column 1530.

[0074] For an ultraviolet ("UV") radiation sensor identified in first column 1510, the hazard range may be identified in second column 1520 as a UV index reading of 3 to 5. When the UV sensor data indicates a UV index reading within the range of 3 to 5, the beacon may determine a match between the current sensor data and the specified hazard range. In response, the beacon may transmit a corresponding warning message specified in third column 1530: "Beacon sensors detect UV at a MODERATE risk from unprotected sun exposure. Stay in shade, wear protective clothing, and apply broad spectrum sunscreen every two hours." The hazard ranges shown in FIG. 13 are merely exemplary and may vary in various embodiments. For instance, the UV hazard range may be identified in second column 1520 as a UV index reading of 6 to 1 1. When the UV sensor data indicates a UV index reading within the range of 6 to 1 1 , the beacon may determine a match between the current sensor data and the specified hazard range. In response, the beacon may transmit a corresponding warning message specified in third column 1530: "Beacon sensors detect UV at a HIGH risk from unprotected sun exposure. Reduce time in sun, wear protective clothing, and apply broad spectrum sunscreen every two hours."

[0075] The specified hazard range for an air quality sensor identified in first column

1510 could, as identified in second column 1520, be one of several index value ranges (e.g. 51 to 100, 101 to 300, 301 to 500, etc.). When the air quality sensor data indicates an index value within a given range, the beacon may determine a match between the current sensor data and the specified hazard range. In response, the beacon may transmit a corresponding warning message specified in third column 1530. For instance, where the quality sensor data falls within the specified hazard range of an air quality index value of 51 to 100, the beacon may transmit the warning message "Beacon sensors detect MODERATE risk of air quality. Unusually sensitive individuals should consider limiting prolonged outdoor exertion." Where the quality sensor data is higher and falls within the specified hazard range of an air quality index value of 101 to 300, the beacon may instead transmit the corresponding warning message for that particular hazard range: "Beacon sensors detect HIGH risk of air quality. Children, active adults, and people with respiratory diseases, such as asthma, should limit prolonged outdoor exertion." Where the quality sensor data is even higher and falls within the specified hazard range of an air quality index value of 301 to 500, the beacon may transmit the corresponding warning message for that hazard range: "Beacon sensors detect VERY HIGH risk of air quality. Children, active adults, and people with respiratory diseases, such as asthma, should avoid outdoor exertion; everyone else should limit outdoor exertion." [0076] The specified hazard range for a temperature sensor identified in first column

1510 could likewise be, as identified in second column 1520, one of several threshold temperatures or temperate ranges (e.g. 30 to 10 degrees F, 9 to -20 degrees F, any

temperature below a threshold of -21 degrees F, etc.). When the temperature data indicates a value within a specified range or above or below a specified threshold, the beacon may determine a match between the current sensor data and the specified hazard range. In response, the beacon may transmit a corresponding warning message specified in third column 1530.

[0077] Where the temperature data falls within the specified hazard range of 30 to 10 degrees F, for instance, the beacon may transmit the warning message "Beacon sensors detect MODERATE risk of low temperatures, limit exposed skin and exposure to cold to two hours." [0078] Where the temperature data falls within the specified hazard range of 9 to -20 degrees F, the beacon may instead transmit the corresponding warning message for that particular hazard range: "Beacon sensors detect HIGH risk of low temperatures, limit exposed skin and exposure to cold to one hour. Frostbite and hypothermia can be caused by prolonged exposure." Where the temperature data falls below the specified threshold temperature less than -21 degrees F, the beacon may transmit the corresponding warning message for that particular hazard range: "Beacon sensors detect VERY HIGH risk of low temperatures, limit exposed skin and exposure to cold to thirty minutes. Frostbite and hypothermia can be caused by prolonged exposure."

[0079] FIG. 16 illustrates an example method 1600 for sending health and safety warning notifications to a wearable device. At block 1605, the method may include providing a wearable device. As discussed in the context of FIG. 2, the wearable device may include a plurality of components. At block 1610, the method may further include a step of providing a health and safety beacon. As discussed in the context of FIG. 2, the health and safety beacon may include a plurality of components.

[0080] The method may further include, at block 1615, providing a safety network system or device. As discussed in the context of FIG. 1 , the safety network system or device my include network software, a location database, a network database, and an application API module. The API module may allow third-party networks (e.g., a severe weather network, a crime report network, a medical alerts network, etc.) to update the network database with localized third-party data (e.g., data associated with a geography in which the beacon is positioned). The localized third-party data may be a severe weather alert, an alert about crime in the area, an alert about medical emergencies in the area, other types of information. At block 1620, the method may include providing one or more such third-party networks.

[0081] The method may include, by way of executing a third-party data software module at block 1625, allowing the health and safety beacon to receive third-party data from the safety network. At block 1630, the method may further include polling the beacon sensors for beacon sensor data. The method may include, by way of executing a warning software module at block 1635, matching the polled sensor data with hazard ranges and corresponding warning messages stored in a warning database stored in memory of the beacon. The method may further include, by way of executing a broadcast software module at block 1640, broadcasting or transmitting warning messages and third-party data from the health and safety beacon to the wearable device. At block 1645, the method may also include receiving settings from a user by way of a GUI displayed at the wearable device.

[0082] At block 1650, the method may include storing the received settings in a settings database stored in memory of the wearable device. The method may further include, by way of executing a base software module at block 1655, allowing the wearable device to receive broadcasts or transmissions from the health and safety beacon. At block 1660, the method may include, by way of executing a notifications software module stored in memory of the beacon, sending notifications to the wearable device in accordance with stored settings. The method may further include conveying the notification to the wearable device at block 1665. Where the notification is composed of text, image, video, or other visual data, conveying the notification may include rendering and displaying the notification at a GUI of the wearable device. Where the notification is partially or wholly of audio data, conveying the notification may include playing the audio data back through a speaker of the wearable device.

[0083] The foregoing detailed description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to enable others skilled in the art to best utilize it in various embodiments and with various modifications as suited to the particular design considerations at issue (e.g., cost, availability, preference, etc.). The scope of the technology should be defined only by the claims appended to this description.

Claims

CLAIMS:

1. A wearable-based health and safety warning system, the system comprising:

a beacon (105, 300) comprising:

a sensor (325-345) to detect a first set of data associated with an environment in which the beacon is positioned, the first set of data including data pertaining to one or more sensed physical attributes of an environment in which the beacon resides, a processor (310) to create a warning notification for a user of a wearable device based on the first set of data, and

a beacon network interface (355) to broadcast the warning notification over a communication network (120); and

a wearable device (110, 200) comprising:

a wearable device network interface (255) to receive the warning notification broadcast over the communication network by the beacon, and

a user interface (285) to convey the warning notification to a user of the wearable device.

2. The system of claim 1, further comprising a third party source (150) configured for sending a second set of data over the communication network to the beacon.

3. The system of claim 2, wherein the third party source is a safety network communicatively coupled to the communication network.

4. The system of claim 2, wherein the second set of data is associated with a geographic area in which the beacon is positioned.

5. The system of claim 2, wherein the warning notification is further based on the second set of data received from the third party source.

6. The system of claim 1 , wherein the warning notification is further based on a time of day.

7. The system of claim 1, wherein the wearable device is configured for transmitting user-specific sensor data to the beacon.

8. The system of claim 7, wherein the warning notification is further based on the user-specific sensor data, and wherein the beacon is configured for assigning a priority to the warning notification based on the user-specific sensor data.

9. The system of claim 1, wherein the wearable device is configured for retransmitting the warning notification to one or more other wearable devices

communicatively coupled to the communication network.

10. The system of claim 1, wherein the wearable device is configured for automatically detecting whether the wearable device has come within broadcast range of the beacon and has established a network connection with the beacon.

11. A computer-implemented method for notifying a wearable device user of a health and safety hazard, the method comprising:

detecting, at a wireless communication module (255) of a wearable device (110, 200), a presence of a beacon (105, 300) based on a network broadcast range associated with the beacon;

establishing a wireless network connection between the wearable device and the beacon;

receiving, at the wearable device via the wireless network connection, a warning notification from the beacon based on a first set of data recorded by a sensor (325- 345) of the beacon, wherein the first set of data is associated with an environment in which the beacon is positioned; and conveying, by the wearable device, the warning notification to a user of the wearable device by way of a graphical user interface (285).

12. The method of claim 11 , wherein the warning notification is further based on a second set of data obtained from a third party source (150), and wherein the second set of data is associated with a geographic area in which the beacon is positioned.

13. The method of claim 11 , further comprising transmitting, by the wearable device over the network connection, wearable device sensor data sensed by one or more sensors (230-250) of the wearable device, and wherein the warning notification is further based on the wearable device sensor data.

14. The method of claim 11 , further comprising retransmitting, by the wearable device, the warning notification to one or more other wearable devices communicatively coupled to the communication network.

15. A non-transitory computer-readable storage medium having a computer program stored thereon, the computer program executable by a wearable device (110, 200) to perform a method for notifying a wearable device user of a health and safety hazard, the method comprising:

detecting a presence of a beacon (105, 300) based on a network broadcast range associated with the beacon;

establishing a network connection between the wearable device and the beacon;

receiving, through the network connection, a warning notification from the beacon based on a first set of data recorded by a sensor (325-345) of the beacon wherein the first set of data is associated with an environment in which the beacon is positioned; and conveying the warning notification to a user of the wearable device by way of a graphical user interface (285).