ALARM AND MONITORING SYSTEM AND METHOD OF OPERATION THEREOF

FIELD OF THE PRESENT SYSTEM

The present system relates to an alarm and monitoring system and, more particularly, to an alarm system with sound and/or vibrate mode and/or a monitoring system, which may be controlled by a primary device, such as a smartphone and/or other primary device, and a method of operation thereof.

BACKGROUND OF THE PRESENT SYSTEM

As smart phones become more pervasive, users rely upon an alarm function of the smart phone to generate an audible alarm. Unfortunately, audible alarms have a tendency of waking up more than their intended users. Accordingly, alarms which can vibrate to alert a user have become popular. However, current silent-type alarms must typically be worn by a user to be effective. For example, one common type of silent type alarm must be worn on a wrist of a user. Similarly, monitoring type systems, such as those that monitor sleep, blood pressure, pulse, blood gases, etc., must be worn, which may be of inconvenience to the user. Further, it has been difficult, if not, impossible to customize the prior alarm in accordance with user's settings. Accordingly, embodiments of the present system may overcome these and/or other disadvantages in prior systems.

SUMMARY OF THE PRESENT SYSTEM

The system(s), device(s), method(s), arrangements(s), user interface(s), computer program(s), processes, etc. (hereinafter each of which will be referred to as system, unless the context indicates otherwise), described herein address problems in prior art systems.

In accordance with embodiments of the present system, there is disclosed an alarm and monitoring system including a primary device and at least one secondary device, the alarm and monitoring system including at least one controller that determines whether at least one alarm event has occurred; establishes a wireless communication between a primary device and the secondary device, when it is determined that the alarm event has occurred; generates an alarm event signal including alarm information in accordance with the alarm event that is determined to have occurred; transmits the alarm event signal from the primary device to the secondary device; generates an alarm signal in accordance with at least the alarm information; renders the generated alarm signal on a rendering device of the secondary device. The controller generates the alarm event signal that causes the secondary device to render the generated alarm signal.

In accordance with embodiments of the present system, at least one controller may receive the transmitted alarm event signal at the secondary device which may generate the alarm signal. In operation, the at least one controller may determine capabilities of the secondary device and form the alarm event signal in accordance with the determined capabilities of the secondary device. When generating the alarm signal, the at least one controller may generate the alarm signal in accordance with a selected melody. The secondary device may control one or more other devices to generate the alarm signal. The one or more other devices may include auditory, visual and/or haptic rendering devices to generate the alarm signal.

In accordance with embodiments of the present system, there is disclosed a method of operating an alarm and monitoring system comprising a primary device and at least one secondary device, the method comprising acts performed by at least one controller of determining whether at least one alarm event is set; establishing a communication between a primary device and the secondary device when it is determined that the alarm event has been set; transmitting an alarm event signal including alarm information from the primary device to the secondary device in accordance with the alarm event that is determined to have been set; generating an alarm signal by the secondary device in accordance with at least the alarm information; and rendering the generated alarm signal on a rendering device. The act of establishing the communication may include an act of establishing a wireless communication between the primary and secondary devices. The method may include an act of generating the alarm signal at the secondary device.

In accordance with embodiments of the present system, the method may include an act of determining capabilities of the secondary device. The method may further include an act of forming the alarm event signal in accordance with the determined capabilities of the secondary device. The act of generating the alarm signal may include an act of determining whether communication is established between the primary and secondary devices. When it is determined that communication is established, the method may include an act of providing a user interface in accordance with the determined capabilities of the secondary device. The method may include one or more acts of generating the alarm signal in accordance with rendering information that is stored in a local memory, controlling one or more other devices to generate the alarm signal and the one or more other devices generating at least one of an auditory, visual and haptic alarm signal.

In accordance with embodiments of the present disclosure, an alarm and monitoring system is provided for communicating an actuator signal to a device. The alarm and monitoring system comprises: a receiver communicatively coupled and configured to receive an alarm event signal from an alarm event transducer; a controller communicatively coupled to the receiver and configured to generate an actuator control signal based on the received alarm event signal; and a transmitter communicatively coupled to the controller and configured to transmit the actuator control signal to an actuator, wherein the actuator is configured to adjust or restore a condition to a predetermined state. The alarm event transducer may comprise: a flood sensor that generates and sends the alarm event signal to the receiver; a camera that records an alarm event and transmits a video signal to the receiver; or a smoke detector and the alarm event signal comprises a smoke detection signal. The actuator may comprise: a wireless water valve that receives the actuator control signal and shuts off a water supply based on the actuator control signal; a lock that receives the actuator control signal and opens or closes based on the actuator control signal; a garage door opener that receives the actuator control signal and opens or closes a garage door based on the actuator control signal. The lock may be a smart door lock. The controller may be configured to determine when communication is established with at least one of the alarm event transducer and the actuator and/or to provide a user interface in accordance with determined capabilities of a secondary device. The secondary device may comprise a memory and the controller may be configured to generate an alarm signal in accordance with rendering information that is stored in the memory. The secondary device may be configured to control one or more other devices to generate an alarm signal. The one or more other devices may comprise at least one of an auditory, visual and haptic rendering device to generate the alarm signal. The haptic rendering device may generate a vibration to awaken a sleeping individual.

According to a non-limiting embodiment of the disclosure, the alarm and monitoring system may communicate an actuator signal to one or more devices to wake a sleeping individual. The individual may be hearing impaired (for example, deaf) or visually impaired (e.g., blind). The alarm and monitoring system comprises a receiver communicatively coupled and configured to receive an alarm event signal from an alarm event transducer such as, for example, a burglar alarm, a fire alarm, a carbon-monoxide alarm, or the like. The system comprises a controller communicatively coupled to the receiver and configured to generate an actuator control signal based on the received alarm event signal, and a transmitter communicatively coupled to the controller and configured to transmit the actuator control signal to an actuator such as, for example, a SmartShaker™, a speaker, an LED light bulb, or the like, to alert and awaken the sleeping individual.

In accordance with embodiments of the present disclosure, a method of operating an alarm and monitoring system to communicate an actuator control signal to a device is provided. The method comprises: receiving an alarm event signal from an alarm event transducer; generating an actuator control signal based on the received alarm event signal; transmitting the actuator control signal to an actuator to adjust or restore a condition to a predetermined state; and transmitting an alarm event signal including alarm information to a secondary device in accordance with an alarm event that is determined to have been set. The method may further comprise establishing a communication between at least one of the alarm event transducer and the actuator.

In accordance with embodiments of the present disclosure, a further method and system of operating an alarm and monitoring system to communicate an alarm event or actuator control signal to a device is provided. The system comprises an ecosystem that includes at least a primary device, a secondary device and a cloud. The ecosystem may further include one or more additional devices. The ecosystem may include an external service server and/or a linked device. The cloud may include an account server, a messaging server, and a push notification server. Using, for example, a primary device, a user may identify one or more other linked users, such as, e.g., an iLuv® account, Facebook® friends, Twitter® contacts, phone contacts, or the like. Once identified and a corresponding user account created or updated for the user with the linked user information, the secondary device may be activated outside of a home, or anywhere else practically, by a linked user. For instance, the cloud may receive a communication signal from the linked user device and send a notification signal when received to the secondary device to render an alarm event so as to, for example, alert the recipient user.

In accordance with embodiments of the present disclosure, a further alarm and monitoring system for rendering an alarm event signal at a user location is provided, the alarm and monitoring system comprising: a transceiver that receives a notification signal from a primary device or a secondary device, the notification signal including the alarm event signal; a controller coupled to the transceiver, the controller being configured to receive the notification signal from the transceiver and generate a rendering signal; and a rendering device coupled to the controller, the rendering device being configured to receive the rendering signal and render an alarm event, wherein the primary device receives the notification signal from a cloud system, and wherein the cloud system receives a communication signal from a linked user device or an external services server and forwards the notification signal to the primary device. The rendering device may comprise: a haptic device that generates a vibration signal based on the received notification signal; a speaker that generates a sound signal based on the notification signal; or a display that generates a display signal based on the notification signal.

The cloud system may comprise an account server that receives a linked device selection signal from the primary device or the secondary device, wherein the account server may communicate with the linked device and receives a linked device ID. The cloud system may further comprise a messaging server that receives the communication signal from the linked device or the external services server. The messaging server may send the notification signal to the primary device. The cloud system may further comprise a push notification server that receives the notification signal from the messaging server. The external services server may transmit or receive the alarm event signal from a camera, a thermostat, a fire detector, a burglar alarm, a carbon-monoxide detector, a gas sensor, or a motion detector.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is explained in further detail in the following exemplary embodiments and with reference to the figures, where identical or similar elements may be partly indicated by the same or similar reference numerals, and the features of various exemplary embodiments being combinable. In the drawings:

FIG. 1A shows a block diagram of a portion of an alarm and monitoring system in accordance with embodiments of the present system;

FIG. 1B shows block diagram of a device operating in accordance with embodiments of the present system;

FIG. 2A shows a partially cutaway top front perspective view illustration of a portion of a device in accordance with embodiments of the present system;

FIG. 2B shows a bottom front perspective view of a portion of a device in accordance with embodiments of the present system;

FIG. 3A shows a top planar view of a portion of a device in accordance with embodiments of the present system;

FIG. 3B shows a bottom planar view of a portion of a device in accordance with embodiments of the present system;

FIG. 3C shows a rear planar view of a portion of a device in accordance with embodiments of the present system;

FIG. 4 shows a partially exploded front perspective view of a device in accordance with embodiments of the present system;

FIG. 5 shows a functional flow diagram of a portion of a process performed in accordance with embodiments of the present system;

FIG. 6 shows a screen shot of portion of an alarm configuration graphical user interface (GUI) generated in accordance with embodiments of the present system;

FIG. 7 shows a screen shot of a portion of an alarm configuration GUI generated in accordance with embodiments of the present system;

FIG. 8 shows a screen shot of a portion of an alarm configuration GUI generated in accordance with embodiments of the present system;

FIG. 9A shows a portion of a graphical representation that may be rendered in accordance with embodiments of the present system;

FIG. 9B shows a portion of a graphical representation that may be rendered in accordance with embodiments of the present system;

FIG. 9C shows a portion of a graphical representation that may be rendered in accordance with embodiments of the present system;

FIG. 10 shows a portion of a system in accordance with embodiments of the present system;

FIG. 11 shows a functional flow diagram of a portion of an ecosystem process performed in accordance with embodiments of the present system;

FIG. 12 shows an example of an ecosystem constructed in accordance with the present system;

FIG. 13 shows a flow diagram that illustrates an example of a process that may be carried out by the ecosystem of FIG. 12;

FIGS. 14 and 15 show another example of an ecosystem constructed in accordance with the present system; and

FIG. 16 shows a flow diagram that illustrates an example of a process carried out by the ecosystem of FIGS. 14 and 15.

DETAILED DESCRIPTION OF THE PRESENT SYSTEM:

The following are descriptions of illustrative embodiments that when taken in conjunction with the following drawings will demonstrate the above noted features and advantages, as well as further ones. In the following description, for purposes of explanation rather than limitation, illustrative details are set forth such as architecture, interfaces, techniques, element attributes, etc. However, it will be apparent to those of ordinary skill in the art that other embodiments that depart from these details would still be understood to be within the scope of the appended claims. Moreover, for the purpose of clarity, detailed descriptions of well-known devices, circuits, tools, techniques, and methods are omitted so as not to obscure the description of the present system. It should be expressly understood that the drawings are included for illustrative purposes and do not represent the entire scope of the present system. In the accompanying drawings, like reference numbers in different drawings may designate similar elements.

The present system as described in more detail below may provide for a primary device that utilizes a user interface to enable setup and programming of a secondary device. In accordance with embodiments of the present system, the primary device may operate as a master device to the secondary device which in these embodiments operates as a slave device (e.g., master/slave relationship between devices). Other relationships between devices may be suitably utilized in accordance with embodiments of the present system and are intended to be encompassed by the simplified following discussion. For example, the present system as described in more detail below may provide a linked device that may utilize a user interface to enable setup and programming of the secondary device, either directly or via the primary device.

In operation the primary device (and/or linked device) may transfer alarm information to the secondary device that at an alarm time, may operate as an alarm device with sound and/or vibrate mode. Further, the secondary device may operate, such as using a wireless connection, to control other devices such as a haptic device (e.g., vibrating), light source (e.g., lamp turn on, gradually brighten and/or flashing) and/or speaker (e.g., render audio) for rendering the alarm. Further, the secondary device may operate to control other devices such as a haptic, visual, auditory, and/or environmental device such as a thermostat for example to respond to the alarm information such as to adjust an environment based on the alarm information (e.g., warm a room before a wake-up alarm is generated).

FIG. 1A shows a block diagram of a portion of an alarm and monitoring system (hereinafter system for the sake of clarity) 100A in accordance with embodiments of the present system. The system 100A may include a device 102 (which may be referred to herein as a primary device) and one or more secondary devices illustratively shown as secondary devices 110-1 through 110-P (generally secondary device 110-x).

The primary device 102 and the secondary device 110-x may communicate with each other over any suitable connection such as over the network 103 which may be accessed using wired and/or wireless communication links. For example, the primary device 102 and the secondary device 110-x may communicate over a network 103 using any suitable wireless, at least in part, communication method or protocols such as WiFi™, Bluetooth™, Internet Protocol, or the like. In addition or in place of a network-based communication, in accordance with embodiments of the present system, a partial hardwired communication connection, such as a home wired network, a direct wired connection, such as through a direct cable connection, and/or a direct wireless communication, such as one or more connections 103-x, such as Bluetooth™, etc., is also envisioned. The discussion of the network, such as the network 103 herein should be understood to include any one or more of the communication systems and/or others that may be suitably applied. For example, in accordance with an embodiment, the primary device may communicate with the secondary device over a Bluetooth™ connection while the secondary device communicates with another device (e.g., one or more other devices 140-x) using a WiFi™ connection. As appreciated, the same or different connections may be made between various devices which may also vary over time (e.g., WiFi™ connection at one time and Bluetooth™ connection at another time).

Further, one or more of the secondary devices 110-x may operate, such as using a wireless connection (e.g., network 103), to control the one or more other devices 140-x, such as a haptic device (e.g., vibrating), light device (e.g., lamp turn on, gradually brighten and/or flashing), speaker (e.g., render audio) and/or other device (e.g., a thermostat) for rendering the alarm information and/or otherwise responding. In accordance with embodiments of the present system, one or more of the rendering devices 140 may be a portion of the secondary device 110 such that the secondary device and/or the other device may respond to the alarm information.

In accordance with embodiments of the present system, the primary device 102 may include any suitable communication device such as smartphone (e.g., an IPhone™, etc.), laptop, tablet, etc., and may run one or more applications to provide functionality as described herein. However, it is also envisioned that the primary device 102 may include additional communication devices such as a dedicated alarm communication device and/or processor operating in accordance with embodiments of the present system.

With regard to the secondary device 110-x, each of these devices may include a unique identification (ID) which may be used to identify and/or otherwise communicate with the corresponding secondary device 110-x, as desired. The ID may include, for example, a media access control (MAC) address. With regard to the secondary devices 110-x, one or more of these devices may for example be similar to and/or differ (e.g., provide a different form and/or function) from each other and/or from the illustrative discussion herein. However, for the sake of clarity, only a single secondary device 110 is generally illustratively discussed unless the context indicates otherwise.

FIG. 1B shows block diagram 100B of a secondary device 210 operating in accordance with embodiments of the present system. The secondary device 210 may, for example, be similar to the secondary device 110 and may include one or more of a controller 202, a memory 204, one or more rendering devices, such as a display 206, a speaker (SPK) 212, and/or a haptic device such as a vibrator 216, a microphone (MIC) 214, a transmit/receive (Tx/Rx) portion 218, and/or one or more sensors 208, one or more of which may communicate with each other and/or to the controller 202. Power for the secondary device 210 may be provided by a power storage device 220 such as a battery. While each of the components of the secondary device 210 are separately depicted, it is envisioned that two or more of the components may also be integrated together. For example, the controller 202 may include a microprocessor and the transmit/receive (Tx/Rx) portion 218. Further, one or more of the rendering devices, such as one or more of the display 206, the speaker (SPK) 212, and/or the haptic device 216 may also or in place of being enclosed with the secondary device 210, be provided separate from the secondary device 210 yet be controlled (e.g., wirelessly) to operate as described herein such as one or more of the other devices 140-x (e.g., haptic device, light device, speaker, thermostat, etc.) illustratively shown in FIG. 1A. For example, the secondary device 210 may control other devices wirelessly, such as a heating/ventilation thermostat and/or other system to control the other system to respond (e.g., adjust heating/ventilation) to the alarm information as described herein. The controller 202 suitably configured may control the overall operation of the secondary device 210 and may include one or more logic devices such as switches, gates, micro-controllers, processors (e.g., micro-processors, etc.) and/or the like to process information in accordance with embodiments of the present system. The memory 204 may include any suitable memory such as local and/or distributed memory which may store application programs (e.g., Mobile Applications, etc.), user information (e.g., user settings, etc.), system settings, etc. The memory 204 may include a local and/or distributed memories, as desired. In accordance with embodiments of the present system, the memory 204 may store software such as applications which may configure the controller 202 to operate as a special purpose controller and/or processor in accordance with embodiments of the present system. In accordance with embodiments of the present system, the memory 204 may include non-transitory memory.

The Tx/Rx portion 218 may receive information from the controller 202 for transmission via any suitable wireless and/or wired system as described herein, via the antenna (ANT) and/or may receive information from any suitable wireless and/or wired system such as the antenna (ANT) and provide this information to the controller 202. The Tx/Rx portion 218 may for example further up convert and/or down convert information as may be suitable for operation as configured. In accordance with embodiments of the present system, the Tx/Rx portion 218 may communicate via any suitable communication method such as via a wireless network, and/or other network as described. In accordance with embodiments of the present system, the Tx/Rx portion 218 may communicate for example using any suitable communication protocol and/or system such as via WiFi™ and/or Bluetooth™ systems.

The one or more rendering devices including one or more of a visual, auditory and/or haptic rendering device may be a portion of the secondary device 210 and/or may be housed in an enclosure separate from the secondary device 210. In embodiments where there are one or more separate rendering devices, the controller 202 may communicate with the separate rendering devices for example utilizing the

Tx/Rx portion 218. The one or more rendering devices may operate to provide a user interface UI 206 that may include a display (DISP) (e.g., a touch-screen display) or the like which may render information such as a graphical user interface (GUI) for operation in accordance with embodiments of the present system. For example, the controller 202 may form a user interface (UI) such as a GUI and provide the GUI to the display for rendering in accordance with embodiments of the present system. Further, in accordance with embodiments of the present system the user interface (UI) 206 may provide illumination sources such as one or more light emitting diodes (LEDs) which may be lit individually and/or collectively (e.g., two or more) to indicate information for the convenience of the user. Operation of the rendering devices contained herein is understood to apply whether the rendering device is provided as a portion of the secondary device 210 or is enclosed separate from it.

In accordance with embodiments wherein the UI 206 includes an auditory portion, a speaker 212 may include one or more speakers which may render audio information, for example obtained from the controller 202, the memory 204, the Tx/Rx portion 218, etc., for the user. For example, the speaker 212 may provide auditory information to a user, such as an auditory alarm, sounds to facilitate relaxation (nature sounds, music, etc.), sleep, etc., under control of the controller 202. Similarly, the haptic device 216 may provide haptic information to a user, such as a haptic alarm, etc., under control of the controller 202. Such haptic and/or auditory information may be pre-stored locally in the memory and/or may be transmitted to the device 210-x in a suitable format prior to being rendered, such at the time of interaction with the primary device. In an embodiment wherein the haptic and/or auditory device are provided separate from the secondary device 210, the secondary device 210 may control (e.g., using a Bluetooth™ communication link) the separate haptic and/or auditory device to activate at the time of an alarm.

In an embodiment wherein the haptic and/or auditory device is operated to notify, awaken, or otherwise alert the user, the haptic device and/or speaker may render related information at a fixed and/or ascending (e.g., periodically increasing) level as programmed and/or otherwise set, desired, etc. For example, in an embodiment wherein an ascending haptic and/or auditory level is produced, the haptic and/or auditory level may start at a first level for a period of time, which in an event wherein the user does not operate to stop rendering, the controller may operate periodically to increase the haptic and/or auditory level to higher levels until a maximum level is reached or the user operates to stop the rendering. Similarly, in an embodiment wherein a descending haptic and/or auditory level is produced, the haptic and/or auditory level may start at a first level for a period of time, which in an event wherein the user does not operate to stop rendering, the controller may operate periodically to decrease the haptic and/or auditory level to lower levels until a minimum level is reached or the user operates to stop the rendering. In accordance with embodiments of the present system, the controller may operate through programming and/or construction to produce a fixed haptic and/or auditory level until the user operates to stop the rendering. The system may produce a corresponding haptic and/or auditory level for a period of time, at which time, the controller may operate to stop the rendering without user intervention.

In accordance with embodiments of the present system, the MIC 214 may acquire ambient sound and form corresponding audio information which may then be provided to the controller 202 for further processing. For example, the MIC 214 may detect ambient sounds such as sounds formed by a user (e.g., such as voice commands, sleeping sounds, etc.) and may correspondingly provide audio information to the controller 202 for storage, transmittal, and/or further processing. For example, the controller 202 after receipt may then further process this audio information and may transmit the audio information to the primary device (e.g., 100, FIG. 1A) for further processing. In accordance with embodiments of the present system, the controller 202 may store the audio in the memory 204 for later use, such as for later transmission, as desired, programmed, etc.

In accordance with embodiments of the present system, the MIC 214 may acquire sounds such as voice commands (requests), sleeping sounds, etc., from a user. The sounds may be received by the controller 202 which may store and/or transmit these sounds (e.g., voice commands) as raw and/or processed information to the primary device (e.g., 100, FIG. 1A) which may then process these sounds (e.g., using speech-to-text (STT) processing) for example to identify the sounds and take appropriate action. In accordance with embodiments of the present system, a user may, for example, provide a voice command, such as request a snooze operation of an alarm, answer a call, hang up on a call, create a text message, read or send a text message, etc. For example, the MIC 214 may acquire audio information which may for example be used by the controller 202 to initiate and/or terminate hands-free phone calls. In accordance with embodiments of the present system, the MIC 214 may be included as one of the sensors 208. Further, the present system may provide a hands-free functionality for the user by the secondary device 210 operating with the primary device (e.g., primary device 102) in accordance with embodiments of the present system. Further, the secondary device of the present system may acquire sleeping sounds for processing by or together with the primary device (e.g., primary device 102) in accordance with embodiments of the present system for example to enable sleep analysis and/or sleep recommendations.

The one or more sensors 208 may include one or more sensors which may detect sound, light, touch, temperature, humidity, pressure, orientation, motion, and/or acceleration and form corresponding sensor information including temporal data related to the sensor information (e.g., periodic sensor information and a time of the periodic sensor information) for example, to enable sleep analysis as described herein. For example, temporal sensor information may be utilized to determine an environment (e.g., sound, light, temperature, humidity and ambient pressure) of a user during sleep as well as the user response (e.g., snoring, motion, etc.) to the environment.

Further, in accordance with embodiments of the present system, touch sensors may include hard and/or soft switches/sensors which may for example detect motion, touch, etc., and form corresponding sensor information. The motion and/or acceleration sensors may detect motion and/or acceleration in (or along) one or more axes and may form corresponding sensor information (e.g. acceleration information). For example, in accordance with embodiments of the present system one or more acceleration sensors may form acceleration information corresponding to one or more axis. In accordance with embodiments of the present system, a drop sensor may be provided to detect a fall and form corresponding information.

In accordance with embodiments of the present system, orientation sensors may detect an orientation of the secondary device 210 and form corresponding orientation information. For example, in accordance with embodiments of the present system, the orientation sensors may detect a right-side or upside down orientation of the secondary device 210 and form corresponding information. In embodiments, it is envisioned that the orientation sensor(s) may detect an orientation of the secondary device 210 relative to a fixed orientation such as magnetic north and form corresponding sensor information (e.g., orientation information). For example, the sensor(s) may collect information related to a user's sleep habits (e.g., sounds, motion, etc.) and form corresponding sensor information which may then be transmitted to the primary device (e.g., primary device 102) for further processing by its controller, such as to provide recommendations to the user related to the sleep habits as described herein. For example, in embodiments wherein the secondary device 210 is positioned to monitor a user's sleep habits (e.g., positioned under a pillow and/or otherwise positioned, fastened, etc. with relation to a pillow, mattress, etc., of a user), the motion sensor(s) may collect (e.g., store) and/or transmit motion information to the primary device which may then be utilized to determine/track sleep quality using this information as discussed.

The haptic device 216 may include any suitable haptic device which may render haptic information. For example, in accordance with embodiments of the present system, the haptic device 216 may include any suitable vibrator (VIB) (e.g., a rotational or linear motor with an unbalanced mass) that may generate vibration which may be sensed by a user. The haptic device may be shaped, sized, and/or powered, etc., such that it may generate sufficient vibration to notify, wake, etc., a user even when placed, for example, under a pillow or the like. In accordance with embodiments of the present system, the VIB may be driven using a signal which may have a uniform, periodic (e.g., sinusoidal, etc.), and/or non-periodic drive signal so that, for example, the vibration may vary in accordance with the drive signal. The power device 220 may include any suitable power storage device which may store power such as a battery, a capacitor, and/or the like.

FIG. 2A shows a partially cutaway top front perspective view illustration of a portion of a device 200, such as a device 210-x (e.g., illustratively a secondary device), in accordance with embodiments of the present system. As readily appreciated, the device may take other forms including a form that may be fastened to a pillow, mattress, etc., of a user, etc. Any of these suitable forms are encompassed by the description herein. As described, one or more of the components, such as the rendering devices may be provided separate from the secondary device 200, yet still be operated as described herein. The secondary device 200 may for example be similar to the secondary device 110, 210 and may include a formed body 260 for example having an upper housing 262, a lower housing 264, a middle housing 266, and/or an interface portion 276. For example, the body 260 may define an interior cavity 261 and may contain one or more components in accordance with embodiments of the present system. The interface portion 276 may include one or more switches, connection ports for communicating with the secondary device 200, and/or a rendering device, such as a display (e.g., one or more light-emitting diodes (LEDs)), etc. For example, in accordance with embodiments of the present system, the interface portion 276 may include one or more switches, buttons, etc., (e.g., a button 268), such as a snooze button, a stop button (e.g., to stop rendering), a power switch 270, a battery charging port 272, and/or one or more MIC 274. As readily appreciated, any one or more of the switches, buttons, etc., may perform one or more operations in accordance with embodiments of the present system. For example, in one mode a button may operate as a snooze button to temporarily stop the rendering of an alarm while in a separate mode, such as during the establishment of a communication link, the button may operate to initiate the communication link.

The switches such as the button 268 and/or the power switch 270 may be situated for example around a periphery of the housing 266 so as to be shielded from accidental activation. However, in yet other embodiments, it is envisioned that one or more of the buttons, switches, etc., may be located elsewhere such as on one or more of the upper and lower housing 262 and 264, respectively. However, a cover such as a hinged cover, a locking mechanism, or other type of shielding (e.g., a wire protector) may be provided to shield one or more of the buttons, switches, etc., from accidental activation, intrusion, etc.

In accordance with embodiments of the present system, the button 268 and/or the power switch 270 may include any suitable switch type such as hard (e.g., pushbutton-type, slide-type, toggle-type) and/or soft (e.g., touch-sensitive-type, programmable, alterable display or indication of operation, etc.) switch of one or more types. For example, it is envisioned that the button 268 and/or the power switch 270 may be formed using one or more hard and/or soft type switches such as touch-sensitive-type switches. Further, in accordance with embodiments of the present system, a snooze and/or power operation may include one or more switches (e.g., a combination of switches actuated simultaneously and/or in sequence, such as press switch key 1 and key 2 together for snooze, etc.). In accordance with embodiments of the present system wherein more than one switch/sensor is utilized for an operation, this combination may be assigned by default, by the user by the system and/or otherwise programmed.

The power switch 270 may be for example hard-type switch such as a slide-type switch which may be activated (e.g., switched on) and/or deactivated (e.g., switched off) by sliding as illustrated by arrow 207. When, the power switch 270 is placed in the “on” position, the secondary-device 200 may be turned on for operation in accordance with the present system. When, the power switch 270 is placed in the “off” position, the secondary-device 200 may be turned off or otherwise be placed in an inactive state, such as in a low-power or no power usage state.

In accordance with embodiments of the present system, the button 268 may include a press-type switch and may generate for example a snooze signal which may be transmitted to a primary-device (e.g., primary device 102) for further processing. For example, depressing a snooze button may cause the primary device to suspend a rendering, such as an auditory alarm, for example for a period of time (e.g., 5 minutes, etc.). In accordance with embodiments of the present system, each time the button 268 is depressed, a controller of the system may extend (e.g., stack, add or otherwise extend a current delay time) and/or otherwise provide a delay time until the next alarm by a desired period of time such as 5 minutes, etc., as may be set by default, by the system, by a user and/or otherwise programmed.

The battery charging port 272 may include any suitable port for receiving a cable and/or device such as a universal-serial bus (USB)-type port or the like to provide power to the secondary device 200. However, in accordance with embodiments of the present system, it is envisioned that other types of ports and/or a wireless charge port may be provided, for example to wirelessly provide power to charge a battery and/or otherwise provide power to the secondary device 200. In accordance with embodiments of the present system, the port 272 may also operate as the transmit/receive (Tx/Rx) portion, such as the transmit/receive (Tx/Rx) portion 218, for transmitting and/or receiving programming instructions, such as alarm settings, monitoring settings, melodies, etc., as described herein.

FIG. 2B shows a bottom front perspective view of a portion of the secondary device 200 in accordance with embodiments of the present system. Caps 278 may be mounted within openings 280 that are configured to receive securing devices such as screws. The caps 278 may fit flush or may extend slightly past an exterior periphery of the lower housing 264 so as to act as mounting pads or cushions.

FIG. 3A shows a top planar view of a portion of the secondary device 200 in accordance with embodiments of the present system. As previously discussed, the body 260 may have any desired shape such as a round shape, ovoid, and/or partial ovoid. However, in accordance with embodiments of the present system other shapes are also envisioned as described herein. The upper housing 262 may have an outer peripheral rim 263 which extends slightly past an outer periphery of the middle housing 266 to protect for example the interface 276 or portions thereof such as switches from unintended activation such as due to accidental contact. Accordingly, the outer peripheral rim 263 may protect the interface 276 and portions thereof from for example accidental impact if, for example, the secondary device 200 is dropped unto a hard surface (e.g., a desktop, a floor, etc.) or is placed under a pillow.

FIG. 3B shows a bottom planar view of a portion of the secondary device 200 in accordance with embodiments of the present system. The lower housing 264 may have an outer peripheral rim 265 which extends slightly past an outer periphery of the middle housing 266 for example to protect the interface 276 from unintended contact. The outer peripheries 263 and 265 of the upper and lower housings 2652 and 264, respectively, may be the same as (e.g., in shape and/or size) or different from each other and may cooperate as described herein.

FIG. 3C shows a rear planar view of a portion of the secondary device 200 in accordance with embodiments of the present system. The middle housing 268 may include patterns and/or vents 282 to promote ventilation (e.g., cooling) and/or allow exiting of for example audio emissions (e.g., generated by a rendering by the speaker such as the SPK 212) from an interior cavity of the secondary device 200.

FIG. 4 shows a partially exploded front perspective view of a device 400 in accordance with embodiments of the present system. As discussed, the device may operate as a secondary device that may for example be similar to the secondary device 200 and may include a body 460 which is illustratively shown as similar to the body 260. The body 460 may enclose one or more of the components of the present system, such as the rendering devices however, as described, one or more of these components may also or alternatively be enclosed separate from the body 460. Accordingly, similar numerical designations may be used to designate the same or similar portions. However, it should be understood that these portions may, in accordance with embodiments of the present system, differ from those of the secondary device 200.

As discussed, the button 268 may operate as a snooze button and may be a hard-type switch including a cover portion 269 and one or more actuators such as press-type switches 267-1 and 267-N (generally 267-x) thus forming a combination switch which may be pressed singularly for corresponding functions and/or may be pressed in unison (e.g., two or more switches being depressed simultaneously and/or in sequence) for another function. For example, these functions and/or actuations may be assigned by default, by the system, by a user and/or may be otherwise programmed. The power switch 270 may include a cover 271 coupled thereto and with which a user may interact to move (e.g., by sliding, etc.) the power switch 270 to on or off positions.

An interface board 284 may be situated within the cavity 261 of the body 260 and may be coupled to and/or may couple together one or more of the snooze button 268, the power switch 270, the battery charging port 272, and the MIC 274. The middle housing 266 may include one or more openings through which one or more of the snooze button 268, the power switch 270, the battery charging port 272, and the MIC 274 may pass and/or be accessed. The speaker 238 and/or the vibrator 246 may be situated adjacent to the upper housing 262 and/or may be housed separate from the body 460 as described. A coupler such as screws 279 (or other suitable coupling method such as welding, friction fitting, etc.) may couple the upper housing 262 to the lower housing 264 so as to sandwich the middle housing 266 therebetween. Accordingly, the screws 279 may pass through openings 280 which are situated within the lower housing 264. Caps 278 may then be frictionally fit within at least a portion of the openings 280 so as to conceal the screws 279. The power storage device 220 may include any suitable power storage device which may provide power such as a rechargeable battery and/or a capacitor and may receive a charge for example from the battery charging port 272.

FIG. 5 shows a functional flow diagram of a portion of a process 500 performed in accordance with embodiments of the present system. The process 500 may be performed using one or more computers communicating over a network and may obtain information from, and/or store information to one or more memories which may be local and/or remote from each other. The process 500 may include one of more of the following acts. In embodiments of the present system, the acts of process 500 may be performed using one or more alarm systems operating in accordance with embodiments of the present system. Further, one or more of these acts may be combined and/or separated into sub-acts, if desired. Further, one or more of these acts may be skipped depending upon for example settings, embodiments, etc. In operation, the process may start during act 501 and then proceed to act 503.

During act 503, the user may for example download a corresponding application to a primary device, such as a smartphone. In accordance with embodiments of the present system, the Application may include programming portions that configure the primary device for operation as described herein such as by providing a user interface as described. Thereafter, the primary device may attempt to form a communication link with the secondary device during act 509 to enable further operation. For example, in a case wherein a Bluetooth™ communication link is utilized, turning on the secondary device may cause the secondary device to be discoverable on the smartphone. Thereafter the primary and secondary devices may attempt to communicate together (e.g., may attempt pairing by a Bluetooth™ communication link) during act 511 over any suitable connection and/or method. For example, in accordance with embodiments of the present system, a Bluetooth™ connection may be established (e.g., pairing) between the primary device and the selected secondary device. In accordance with embodiments of the present system, a user may select a preferred type of communication method (e.g., WiFi™, Bluetooth™, ZigBee™, proprietary, RFID, etc.) for communication when more than one system of communication is available between the devices. In accordance with embodiments of the present system, other operations may be utilized for initiating the communication link such as depressing a button on the secondary device to initiate a communication link with the primary device.

In an embodiment wherein one or more secondary devices are available, a communication link may be attempted between the primary device and the one or more available secondary devices. In accordance with embodiments of the present system, each device (e.g., primary and/or secondary devices) may have a unique identification (ID) (e.g., a unique identification). Thus, in accordance with embodiments of the present system, for example each secondary device may be assigned a unique number from 1 to P in a case wherein more than one secondary device is available. However, to simplify the discussion, only a primary and single secondary device (e.g., p=1) is discussed, for example having an ID of ID=1 for the sake of clarity.

After the communication link is confirmed between the primary device and the secondary device during act 511, the user may open the application to enable operation in accordance with the present system. For example, the application may be utilized to set the device (e.g., a secondary device 110-x) to operate in accordance with the present system as well as depicting on the primary device an operating state (e.g., communication link status such as connected, battery status, operating mode such as alarm, sleep monitoring, etc.) of the secondary device. In a case wherein the communication link is not confirmed, the process may continue to attempt communication (e.g., repeat act 509) until a communication link is established during act 509 and/or may return to act 503 for further configuration operations.

In a case wherein the communication link is established, the application on the primary device may be utilized for sending control information to the secondary device during act 513 such as to set an operating mode of the secondary device. In accordance with embodiments of the present system, the control information may include alarm information (e.g., date, time, alarm type, rendering device, etc.), operating mode information (e.g., sleep monitoring), rendering information, etc. For example, the process may configure alarm settings and/or alarm times (e.g., by date, day, time, etc.) for one or more alarm events. In operation, a user may set an alarm within the application on the primary device for a time (e.g., every Tuesday, this Tuesday, etc.) for a given alarm event and transmit this information to a memory of the system, such as within the secondary device, as alarm information during act 513 for later use (e.g., “later” as in at the time of a given alarm) by the secondary device. In this way, there is no need for the primary and secondary devices to have an operable communication link at the time when a given operating mode is intended (e.g., see act 519) such as at a given alarm time for the secondary device to produce the given alarm and/or to control external devices (e.g., other devices, such as a light, speaker, haptic device, thermostat, coffee maker, etc.) to perform an operation at the given alarm time and/or at a time related to the alarm time. For example, in accordance with embodiments of the present system, the secondary device may communicate with another device, such as a lamp, to increase a light brightness for example in intervals producing an increasing amount of light leading up to the alarm time. In other embodiments, the lamp may go from off to full brightness as desired. Further, at the alarm time one or more rendering devices (as a portion of the secondary device and/or separate from it) may for example vibrate and/or produce an auditory rendering.

The setup routine of the application may provide a user with a suitable interface such as a graphical user interface (GUI) with which a user may interact in accordance with the present system, such as for example to configure one or more of the primary and secondary devices. For example, the GUI may be utilized to set the alarm settings such as one or more alarm times for one or more corresponding alarm events. For example, FIG. 6 shows a screen shot 600 of a portion of an alarm configuration GUI 601 generated in accordance with embodiments of the present system. The GUI 601 may be rendered on any suitable device 691 such as a smart phone (e.g., an iPhone™ is illustratively shown), laptop, tablet and/or other device and the like. In accordance with embodiments of the present system, the GUI may be provided by an application, such as an app running on the device 691.

Referring to FIG. 6, the GUI 601 may include day/date information 603 that a user may select to set the day and/or date of a given alarm event (e.g., 3 P.M. on Monday, Wednesday and Friday, October 25, etc.). The GUI 601 may include a plurality of menu-items with which a user may select set and/or reset one or more alarm events. For example, a user may select the day/date information 603 (e.g., by selecting the day/date information 603 menu item) and the process upon determining that the user has selected day/date information may generate a text entry box and/or a calendar with which a user may enter information related to a selected day/date/year for a current alarm event. The current alarm event may be switched on or off using an alarm on/off icon 605 which may indicate whether the alarm is set to be activated (e.g., as illustrated by an “on” icon) or not activated (e.g., as may be illustrated by an “off” icon for example in place of the “on” icon) at the current alarm event time. For example, an “on” symbol may indicate that that the current event is an active event (e.g., in which an alarm signal is to be generated) while an “off” signal indicates that the current event is not an active event (e.g., is an inactive event in which an alarm signal will not be generated).

Alarm time information 607 may indicate a time at which current given indicated alarm event is to occur (e.g., an alarm time/date/condition setting). Alarm rendering information 621 may indicate whether vibration and/or sound modes (e.g., as represented by vibration and sound modes menu items 613 and 609, respectively) are to be used for rendering an alarm of the current alarm event as well as indicating desired rendering information (e.g., visual, auditory and/or haptic) and/or related devices (e.g., internal and/or external devices rendering devices), such as a desired melody for an auditory alarm to be produced by a given rendering device in an embodiment wherein different auditory information and/or devices are selectable. A user may tap on visual, vibration and/or sound modes menu items, such as vibration and/or sound modes menu items 613 and 609, respectively, to toggle the mode on or off (e.g., bright=on, dim=off) as may be desired.

A selected melody (e.g., a sound file for rendering) for a sound mode may be illustrated using by a melody menu item 611 (e.g., Melody 1, 2, 3, . . . m-1, M, etc.). In accordance with embodiments of the present system, there may be one or more selected melodies (e.g., M, where M is an integer) which may be stored for example as prerecorded and/or otherwise generated sound files (e.g., default memories stored prior to delivery of the secondary device to the user) in a memory of the system such as a memory of the primary and/or secondary device. Accordingly, a user may not have to load rendering information, such as melodies as separate files. For example, in accordance with embodiments of the present system, a user may select melodies from a stored plurality of melodies available on the secondary device thus simplifying a method of setting alarms. The rendering information such as melodies may be identified by name (e.g., melody 1, melody 2, etc.), genre (e.g., Rock, Classical, etc.), and/or by description (e.g., for a melody, by title, author, singer, band, etc.). In accordance with embodiments of the present system, the melodies may include songs, repeating patterns (e.g., in pitch and/or tone), white noise, etc. In accordance with embodiments of the present system, the melodies may also be utilized for operating the haptic device so that in effect, the melody may in place of or in addition to being utilized for auditory rendering, may be utilized for generating haptic rendering, such as following a baseline of a selected melody.00

It is further envisioned that the primary device and the secondary device may communicate with each other, for example, to identify melodies stored in a memory of the secondary device. During this communication, the primary device and the secondary device may synchronize with each other so that information such as sound files of the secondary device may be discovered by the primary device. Similarly, files of the primary device such as sound files may be transmitted to the secondary device. Further, the secondary device may communicate with one or more external devices (e.g., other devices) for example to determine the rendering capabilities of the one or more external devices (e.g., auditory, haptic, etc.).

In accordance with embodiments of the present system, the secondary device may include melodies such as from a given genre which may be pre-programmed at the factory. Thus, a Rock-type secondary device may include rock-type melodies while a Classical-type secondary device may include classical-type melodies. A user may then select a secondary device based upon the type of music desired for the alarm. Graphics and/or color of a secondary device may be customized so as to identify a type of secondary device. In accordance with embodiments of the present system, the user may load and/or otherwise alter previously stored files such as the sound files (e.g., melodies) into the primary device and/or the secondary device.

Referring back to FIG. 6, a user may select a rendering mode/menu item, such as the melody menu item 611 (e.g., by swiping through an open or closed (e.g., a last melody of the list connects to a first item of the list) of available melodies, etc. The system may display a plurality of available melodies (e.g., sound files) which a user may select to associate with the current alarm event. Then, the system may set this user-selected melody (e.g., sound file) as a selected melody as may be represented by menu item 611 (e.g., “MELODY 1”). Thus, in a case wherein the user selects MELODY 5, the system may set this melody as the selected melody. In a case wherein the sound mode is selected (e.g., see, sound modes menu item 609), the secondary device may transfer the sound mode such as an alarm event to the secondary device for subsequent rendering of the selected melody (e.g., audibly and/or haptically, see act 519 discussed further herein) when the corresponding alarm event is triggered for example at a set alarm time and/or date. An alarm event number 619 may indicate a number (e.g., in consecutive order) of a current alarm event (e.g., “1” next to the alarm bell). In accordance with embodiments of the present system, there may be a plurality (e.g., X) of alarm events as discussed.

For example, FIG. 7 shows a screen shot 700 of a portion of an alarm configuration GUI 701 generated in accordance with embodiments of the present system. Assuming that there are X current alarm events (where X is an integer), each of these X current alarm events may be represented by an alarm event window 701-1 through 701-X (generally 701-x) as shown. A user may select any of these alarm event windows 701-x (e.g., by swiping, double clicking, etc., as may be set by default, by the user and/or by the system) and the system may then display more detailed information about the selected alarm event and/or may provide a user with an interface with which the use may interact to change settings of the corresponding alarm event. Thus, in a case wherein X=3, the three alarm event windows 701-1, 701-2, and 701-X may be rendered by the process for the convenience of the user. Further, each alarm event may have a predetermined alarm duration value associated with it (e.g., see, alarm duration 625, shown in FIG. 6 which in the illustrative embodiment is set to 2 min). This value may be set by default, by the system and/or by a user and may correspond to a total alarm rendering time as discussed herein.

Referring back to FIG. 6, the process may generate a volume menu item such as a volume slider 617 with which a user may interact to view and/or set/reset a volume of the corresponding selected melody (e.g., see 611 MELODY 1 in FIG. 6). Accordingly, a user may slide the volume slider 617 to set a volume of the selected melody to be associated with the current alarm event. Similarly, a haptic menu item such as a vibration slider may be generated so that a user may select a haptic force, frequency and/or pattern (e.g., vibrate, stop, vibrate, stop, etc.) to associate with a corresponding vibration mode to associate with the current alarm event (e.g., be haptically rendered by the current alarm event). Similarly, a visual (e.g., lighting) menu item may be generated so that a user may select a brightness levels, frequency and/or pattern (e.g., turn on brightness, start dim and brighten in intervals, etc.) to associate with a corresponding alarm event. In accordance with embodiments of the present system, a single slider, such as the slider 617 may be utilized to set two or more of a volume, a haptic force and a brightness associated (e.g., rendered) with a given melody and/or alarm event.

A weekday menu item 615 may indicate a day of week selected for a current alarm (e.g., 7 day alarm). For example, in a case wherein a user would like the current alarm event to be generated each week on the same day and/or time (e.g., every Friday at 6:20 A.M.), a user may select one of the days in the weekday menu item 615 so as to associate the selected day of the week with the current alarm event. In accordance with embodiments of the present system, a device ID 623 may identify a device associated with the current alarm event. Thus, in a case wherein a device by ID 1 is identified with the current alarm event, when the current alarm event is determined to occur (e.g., at its alarm time, date, etc.), the alarm may be rendered using a device whose identification is ID 1. The process may then store these alarm settings as alarm information in a memory of the system such as a memory of the primary device and/or secondary device.

In accordance with embodiments of the present system, the primary device and the one or more secondary devices may be coupled (e.g., through a network, etc.) to determine capabilities of the one or more secondary devices and/or to transmit information, such as alarm information, therebetween. For example, in accordance with embodiments of the present system some secondary devices may include sensors, switches, ports, etc., of different types than other secondary devices. For example, some secondary devices may include motion sensors (e.g., acceleration sensors, gravity sensors, etc.) while other secondary devices may not and/or may include one or more other sensors. Thus, the capabilities of secondary devices may differ as desired. For example, a basic secondary device may be provided that has less features and/or programmable capabilities than a higher end (e.g., more expensive) secondary device. Accordingly, a primary device may query a given secondary device to identify the capabilities of the given secondary device. Then, the primary device may take into account the capabilities of the secondary device to form settings, menus, GUIs, etc., which may correspond with the capabilities of a specific secondary device. Thus, for example, a given secondary device may include a temperature sensor. Accordingly, the primary device may detect this capability, acquire stored and/or current temperature information from the temperature sensor and provide a suitable interface (e.g., GUI) for this secondary device, such as provide a display of temperature information, enable operating modes, etc., for the convenience of a user. Similarly, a secondary device may include capabilities to operate as a remote speaker phone (e.g., microphone and/or speaker) in concert which a phone application of the primary device. Accordingly, in these embodiments, the primary device may be operative to control the secondary device to act as a speaker phone and/or otherwise provide a GUI for use, setting, etc., of this capability. As may be readily appreciated, in a case wherein a secondary device does not have a given capability, the present system may adapt the provided GUI to delete and/or otherwise indicate that a given capability is not supported by a given secondary device. In accordance with embodiments of the present system, portions of the operating mode such as alarm information may be transmitted to one or more memories (e.g., a memory present on the secondary device) for storage.

Referring back to FIG. 5, after completing act 513, the secondary device may receive the information sent by the primary device during act 517. As discussed, during act 517, the secondary device may receive the control information from the primary device and process this signal to extract the control information, such as alarm information contained therein. The extracted control information may include information which indicates whether to, for example, turn on or off a current alarm, whether to enable or disable sound (e.g., turn sound on or off, respectively), whether to turn a vibrator on or off, whether to play a sound file (e.g., a sound file that is identified by the sound file ID and which may be stored in a memory of the secondary device), whether to control an external device at the time of an alarm, and/or otherwise set an operating mode of the secondary device as discussed herein After completing act 517, the process may continue to act 518.

During act 518, the secondary device may process the control information such as form an alarm signal based upon alarm information extracted from the control information. Accordingly, the secondary device may analyze the extracted alarm information and use this information to determine for example a response when rendering an alarm (e.g., see act 519). In accordance with embodiments, a secondary device may have available locally (e.g., in a memory such as the memory 1020 illustratively shown in FIG. 10) responses that are available to the secondary device (e.g., haptic, visual, auditory, etc.), though in accordance with embodiments of the present system, further responses may also be received for example as a portion of the alarm information. Based upon these determinations, the process may form the alarm signal at the secondary device. The alarm signal may include one or more continuous and/or discrete signals (e.g., stored, received, etc.) and may be transmitted to one or more corresponding rendering devices of the secondary device and/or separate from the secondary device which are determined to be operative or otherwise available (e.g., for a separate rendering device) when rendering the alarm. For example, in a case wherein it is determined to play a melody (e.g., stored and/or received such as from the primary device), the alarm signal may include this melody and, as such, may include audio information which may be transmitted to a rendering device such as a speaker when rendering the alarm. Further, the secondary device may determine that an external speaker is available, such as through a Bluetooth^™communication link and the audio information may be transmitted also or alternatively to the external speaker for rendering the alarm.

With regard to the haptic rendering device, such as a vibrator, in a case wherein it is determined to operate a vibrator, the alarm signal may include a signal which may cause the vibrator to operate when rendering the alarm. Accordingly, the alarm signal may include a signal to switch the vibrator on (e.g., toggle on) and/or may include a signal to drive the vibrator such that, after the end of the signal is rendered, the vibrator stops operating. In accordance with embodiments of the present system, this signal may be transmitted to the vibrator and may include a discrete signal (e.g., to toggle the vibrator on or off) or a constant signal (e.g., to drive the vibrator) when rendering the alarm.

Thus, in accordance with embodiments of the present system, the process may form one or more alarm signals configured to drive one or more rendering devices in accordance with the extracted alarm information. For example, in a case wherein the extracted alarm information requires vibration to be output but no melody to be played, the process may form an alarm signal to drive an internal vibrator of the secondary device and/or an external vibrator when rendering the alarm. During this act, in a case wherein a melody (e.g., sound file) is to be played during an alarm event, the process may obtain the corresponding sound file from a memory of the system such as a memory of the secondary device and may generate a corresponding alarm signal for example to drive the speaker. In this way, the melody may be rendered by the speaker. In accordance with embodiments of the present system, the sound file may be maintained locally. In this way, the process may for example conserve system resources by not having to stream the sound file from the primary device. After completing act 518, the process may continue to act 519.

During act 519, the secondary device may operate to set an operating mode such as to render the alarm signal at the time of a set alarm. Accordingly, the alarm signal may be provided to one or more rendering devices which may then render the alarm signal. During this act, the process may also start an alarm interval counter which may count a total time that the current alarm signal is being rendered by the secondary device and/or one or more other rendering devices.

In accordance with embodiments of the present system, when the secondary device is programmed to perform in accordance with an operating mode, one or more of the primary and secondary device may also communicate with one or more further devices (e.g., other devices) to control operation of the one or more other devices. For example, in a case wherein the secondary device is programmed to facilitate sleep of the user, such as by rendering a descending audio output, the secondary device may communicate with another device, such as a thermostat over a wireless coupling (e.g., Bluetooth™), to reduce a heat setting of the thermostat while controlling the internal and/or external rendering device. Similarly, in a case wherein the secondary device is programmed to facilitate waking of the user, such as by controlling a rendering device to render an ascending audio output, the secondary device may communicate with the other device at that time or some predetermined time before, to increase a heat setting of the thermostat, light setting of a lamp, etc. As readily appreciated, while external devices (e.g., one or more other devices) such as rendering devices, a thermostat, etc., are illustratively described as other devices, additional devices and device types may be suitably controlled.

In accordance with embodiments of the present system, the secondary device may attempt communication with the primary device at the alarm time. For example, at the alarm time the secondary device may though need not attempt to communicate with the primary device (e.g., such as over a Bluetooth™ connection) to determine whether the primary device is available. In accordance with embodiments of the present system, when the primary device is available (e.g., active, in a sleep state, etc.), the user interface may be produced on the primary device to facilitate operation, such as to control the alarm rendered during act 519 (e.g., see act 523 described below). As envisioned, whether or not the primary device is available when the alarm is rendered, stopped, etc., the secondary device will operate as described. After completing act 519, the process may continue to act 521.

During act 521 the process may determine whether an off and/or other control signal is generated. In accordance with embodiments of the present system, the off and/or other control signal may be generated at the secondary device directly, such as through operation of one or more of the buttons, switches, etc., present on the secondary device. In addition, the off and/or other control signal may be generated at the primary device (e.g., through operation of the application interface, such as the user interface provided by the application on the primary device) and be transmitted to the secondary device to directly control the secondary device when a communication link is present between the primary and secondary devices. For example, when an alarm event occurs on the secondary device, it may automatically search for a corresponding primary device, such as a smartphone. In a case wherein a corresponding smartphone for example is found, the secondary device may for example pair with the smartphone, bring up the corresponding user interface (e.g., application), etc., so that the operation of the secondary device may be controlled from the smartphone without requiring further intervention from the user (e.g., without requiring a manual pairing operation by the user). In this way, control of the secondary device may be performed directly on the primary device at the alarm time for example to make it easier to snooze/turn off the secondary device via the smartphone user interface. Accordingly, in a case wherein it is determined that the off and/or other control signal is generated, the process may continue to act 523 where it may respond accordingly. For example, the smartphone may be utilized to turn off the alarm by, for example, sending control information to the secondary device to terminate the alarm signal provided to the rendering device and/or other devices. Thereafter, the process may end during act 573.

However, in a case wherein it is determined that the off signal is not generated, the process may continue to act 525. During act 525, the process may determine whether a snooze signal is generated (e.g., in a case wherein a snooze switch is actuated) on the primary and/or secondary device as similarly described regarding the off signal. Accordingly, in a case wherein it is determined that a snooze signal is generated, the process may continue to act 527. However, in a case wherein it is determined that a snooze signal is not generated, the process may continue act 521 for example until an end alarm time interval is reached, an off switch is actuated or until a snooze button is actuated. For example, the alarm interval may be determined to elapse when an alarm interval counter has a value which is greater than or equal to a predetermined alarm duration value. The alarm duration value may be set to a value by default, by the system and/or by a user to represent a maximum alarm duration such as 120 seconds, etc. The alarm interval may be determined not to have elapsed when the alarm interval counter has a value which is less than the predetermined alarm duration value.

During act 527, the process may perform a snooze process using any suitable system. For example, the process may temporarily interrupt the current alarm (e.g., by interrupting the alarm signal) for a snooze period of time (e.g., 5 minutes, etc., as may be determined by default, by the system and/or by a user). Accordingly, the process may start a timer to determine when the snooze period of time elapses and may then resume the rendering of the alarm signal as before snoozing (e.g., see act 519). Further, it is envisioned that the process may suspend the alarm interval timer during the snooze period so that the alarm interval timer stops during the snooze period and starts (from the same count) when the snooze period of time elapses. After completing act 527, the process may repeat act 521. Accordingly, in a case wherein another command (e.g., snooze or off for one or more rendering devices) is received while already snoozing, the process may reset the snooze (e.g., start a new snooze interval) or turn off the one or more rendering devices as appropriate.

In accordance with embodiments of the present system, the snooze signal may be generated by selecting (e.g., by depressing, etc.) a snooze key (e.g., a snooze button, a user interface item, etc.) on the secondary device and/or on the primary device as described. Selection of the snooze key may generate a signal to inform the secondary device of the selection by, for example, transmitting the signal that the snooze key was selected to the secondary device. The secondary device in receipt of this signal may then take appropriate action. For example, the secondary device may temporarily interrupt the current alarm (as described above) for a threshold period of time as described above with respect to act 525. Similarly, the primary device when in communication with the secondary device during the alarm event may update a status of the corresponding alarm event, for example to indicate on the user interface that the secondary device was instructed to snooze and may render this updated status on a rendering device of the system, as desired. Accordingly, when a user selects (e.g., by depressing) a snooze button on the secondary device, the primary device may be informed of this and may render information indicating such (e.g., 5 min snooze on).

With regard to acts 519 and 523, the snooze and off buttons may be situated on the secondary device and/or primary device as described. For example, with regard to the primary device that is in communication with the secondary device when an alarm event occurs, the process may generate a GUI to indicate to a user a current status of the alarm event and on/off/snooze keys (e.g., user interface objects such as a display of selectable buttons provided on the UI) for a user to select. For example, FIG. 8 shows a screen shot 800 of a portion of an alarm configuration GUI 801 generated for example on a primary device in accordance with embodiments of the present system. A graphical representation 804 may illustrate a current status of the secondary device (e.g., vibrating). One or more menu items such as Stop and Snooze menu items, 806 and 808, respectively, may include menu-items generated in accordance with embodiments of the present system. The graphical representation 804 may be based upon the alarm information.

For example, FIG. 9A, FIG. 9B and FIG. 9C each show a portion of graphical representations 915A through 915C, respectively, that may be rendered in accordance with embodiments of the present system. For example, in a case wherein the alarm information is set for rendering an audible melody only, a melody only graphical representation as shown in FIG. 9A may be rendered on a primary device. Similarly, in a case wherein the alarm information is set to vibration only, a vibration only graphical representation of FIG. 9B may be rendered. Lastly, in a case wherein the alarm information is set to vibration and melody, a vibration and melody graphical representation may be rendered as shown in FIG. 9C. These representations may represent a current state of an alarm which is currently occurring on the secondary device and may be updated in real time and/or may represent a future state of a given alarm.

With regard to the snooze and/or off keys, in accordance with embodiments of the present system it is envisioned that one or more of these keys may be generated by moving the primary or secondary device in a desired pattern (e.g., a horizontal waving, etc.). In this way, movement sensors (e.g., accelerometers, motion sensors, etc.) may identify for example movement actions and then form corresponding alarm information. For example, the process may analyze the motion information to detect a corresponding motion. In a case wherein the corresponding motion is determined to match a predetermined pattern (e.g., where the patterns may be defined for each action such as an off pattern, a snooze pattern, etc. as may be defined by default, by the user and/or by the system), the process may take an appropriate action without further interaction with a corresponding user interface. For example, in accordance with embodiments of the present system, moving the primary or secondary device in a sideways pattern (e.g., laterally) may indicate a snooze command. Similarly, in accordance with embodiments of the present system, moving the primary or secondary device in an up and down pattern may indicate an off command. This motion may be sensed by one or more sensors of a corresponding device such as motion sensors and may be determined by a controller of the corresponding device or, for example in a case wherein the device is a secondary device, identified motion information may be communicated to the primary device for determination by a controller of the primary device. In this way, sensor data from the secondary device may be transmitted to the primary device in real time for analysis.

In accordance with embodiments of the present system, a user may shake or otherwise move the primary or secondary device in a desired pattern, the process may detect the desired pattern of motion (e.g., through an analysis of motion information from one or more sensors of the system), the process may then determine whether there is a command (or task) assigned to the detected pattern of motion, and in a case wherein it is determined that there is a command (or task) assigned to the detected pattern of motion, the process may perform this command or task.

FIG. 10 shows a portion of a system 1000 including a secondary device 1005 in accordance with embodiments of the present system. For example, a portion of the present system may include a processor 1010 (e.g., a controller) operationally coupled to a memory 1020, one or more rendering devices 1030 such as a display, haptic device, etc., one or more sensors 1040, one or more actuators 1060, a transmit/receive (Tx/Rx) portion 1080, and a user input device 1070. In accordance with embodiments of the present system, although each of the memory, the rendering device, the one or more sensors, the one or more actuators 1060, and the transmit/receive (Tx/Rx) portion 1080 are shown separately for clarity, one or more of these portions may be combined together with the processor. For example, the processor may include the transmit/receive (Tx/Rx) portion. Further, the portions shown may also be encompassed by one or more discrete devices (e.g., separate from the secondary device 1005) such as portions of the rendering device 1030, the user input device 1070 and/or other devices as described herein. For example, while the user input 1070 may form a portion of the secondary device 1005 (e.g., snooze key, etc.), the user input may also or alternatively be a portion of the primary device as described. Further, the transmit/receive (Tx/Rx) portion (transceiver) may be made up of two or more discrete portions, such as a transmitter/receiver portion and a discrete antenna. In addition, the memory 1020 may be any type of device for storing application data as well as other data (e.g., auditory, visual and haptic responses to alarm information) related to the described operation. The application data and other data are received by the processor 1010 for configuring (e.g., programming) the processor 1010 to perform operation acts in accordance with the present system. The processor 1010 so configured becomes a special purpose machine particularly suited for performing in accordance with embodiments of the present system.

The user input 1070 may include a keyboard, a mouse, a trackball, a motion-sensitive device or other device, such as a touch-sensitive display, which may be stand alone or be a part of a system, such as part of a personal computer, a personal digital assistant (PDA), a mobile phone (e.g., a smart phone), a monitor, a wearable display (e.g., smart glasses, etc.), a smart- or dumb-terminal or other device for communicating with the processor 1010 via any operable link. The user input device 1070 may be operable for interacting with the processor 1010 including enabling interaction within a user interface (e.g., GUI) as described herein. Clearly the processor 1010, the memory 1020, the rendering device 1030, and/or user input device 1070 may all or partly be a portion of a computer system or other device such as a primary, secondary and/or other device as described herein.

The actuators 1060 may be controlled by the processor 1010 in accordance with embodiments of the present system. The actuators 1060 may control one or more haptic devices such as one or more vibrators, motors, etc., of the system so as to generate a desired vibration under the control of the processor 1010. For example, in accordance with embodiments of the present system, the actuators 1060 may include a motor controller which may control the speed of a vibrator under the control of the processor 1010. In accordance with embodiments of the present system, the actuators may be a portion of an external haptic device that may operate under control of the processor 1010 such as through a wireless link.

The methods of the present system are particularly suited to be carried out by a computer software program, such program containing modules corresponding to one or more of the individual steps or acts described and/or envisioned by the present system. Such program may of course be embodied in a computer-readable medium, such as an integrated chip, a peripheral device or memory, such as the memory 1020 or other memory coupled to the processor 1010.

The program and/or program portions contained in the memory 1020 may configure the processor 1010 to implement the methods, operational acts, and functions disclosed herein. The memories may be distributed, for example between the primary and/or secondary devices, or local, and the processor 1010, where additional processors may be provided, may also be distributed (e.g., as a portion of one or more of the primary device, the secondary device, the rendering device and/or other devices that operate in accordance with embodiments of the present system) or local to a device. The memories may be implemented as electrical, magnetic or optical memory, or any combination of these or other types of storage devices. Moreover, the term “memory” should be construed broadly enough to encompass any information able to be read from or written to an address in an addressable space accessible by the processor 1010. The memory 1020 may include a non-transitory memory. With this definition, information accessible through a network such as the network 1080 is still within the memory, for instance, because the processor 1010 may retrieve the information from the network 1080 for operation in accordance with the present system.

The processor 1010 is operable for providing control signals and/or performing operations in response to input signals from the user input device 1070 as well as in response to other devices of a network (e.g., in response to signals received from a primary device) and executing instructions stored in the memory 1020. The processor 1010 may include one or more of a microprocessor, an application-specific or general-use integrated circuit(s), a logic device, etc. Further, the processor 1010 may be a dedicated processor for performing in accordance with the present system or may be a general-purpose processor wherein only one of many functions operates for performing in accordance with the present system. The processor 1010 may operate utilizing a program portion, multiple program segments, or may be a hardware device utilizing a dedicated or multi-purpose integrated circuit.

FIG. 11 shows a functional flow diagram of a portion of an ecosystem process 1100 performed in accordance with embodiments of the present system. The process 1100 may be performed using one or more computers communicating over a network and may obtain information from, and/or store information to one or more memories which may be local and/or remote from each other. The process 1100 may include one of more of the following acts. In embodiments of the present system, the acts of the ecosystem process 1100 may be performed using one or more devices operating in accordance with embodiments of the present system. Further, one or more of these acts may be combined and/or separated into sub-acts, if desired. Further, one or more of these acts may be skipped depending upon for example settings, embodiments, etc.

Referring to FIGS. 1A, 1B and 11 concurrently, the ecosystem process 1100 may be carried out by the secondary device 210 (shown in FIG. 1B) (or primary device 102, shown in FIG. 1A), and, more particularly, the controller 202 in the secondary device 210. In operation, the ecosystem process 1100 may initialize and proceed to establish a communication session 103-x with each of one or more devices 140-x (or secondary devices 110) over the network 103 (shown in FIG. 1A) via the Tx/Rx portion (transceiver) 218 (shown in FIG. 1B) (act 1105). The act 1105 establishing one or more communication sessions 103-x may include, for example, pairing the device 210 to one or more of the devices 140-x. The device 210 may monitor communication signals received from each of the connected devices 140-x (act 1110) and detect for an event signal (act 1115).

For instance, the device 210 may be communicatively connected to devices 140-x that may include an alarm event transducer such as for example, but not limited to, a sound sensor, a flood sensor, a carbon-monoxide (CO) sensor, a fire detector, a carbon dioxide (CO₂) sensor, a gas (e.g., methane, propane, kerosene, etc.) sensor, a moisture sensor, a humidity sensor, a temperature sensor, a thermostat, a light sensor, a force/pressure sensor, a position sensor, a direction sensor, a global position system (GPS) sensor, an altitude sensor, an atmospheric pressure sensor, an air quality sensor, a proximity sensor, an infrared (IR) sensor, a motion sensor, a velocity sensor, an acceleration sensor, a wind speed sensor, a wind direction sensor, an intrusion detector, a window breakage sensor, a burglar alarm, an antitheft device, an image sensor, a moving image pickup device, a voltage sensor, an ampere sensor, a resistance sensor, a radiation sensor, or the like. The alarm event transducer(s) may be configured to sense a wide range of different energy forms, including energy forms along the electromagnetic spectrum, magnetic energy, electrical energy, ambient conditions (e.g., temperature, pressure, humidity, CO, CO₂, O₂, etc.), or the like. The alarm event transducer(s) may be further configured to detect whether a sensed condition and/or level exceeds a predetermined threshold value (an alarm event), and, if so, to generate and transmit an alarm event signal to the device 210 (shown in FIG. 1B) and/or other devices 140-x. The alarm event transducer(s) may include a transmitter (not shown) or a transceiver (not shown) to facilitate unidirectional or bidirectional communication, respectively, with the primary device 102 (shown in FIG. 1A), secondary device 210 (shown in FIG. 1B), or another device 140-x (shown in FIG. 1A) over the network 103.

The connected devices 140-x may include an actuator such as for example, but not limited to, a switch, a relay, a potentiometer, a controller, a driver, or the like, that is configured to control an external device (not shown). The external device(s) may include, for example, but are in no way limited to, a thermostat, a valve, a fluid valve (e.g., wireless z-wave water valve), a heating system, a ventilating system, an air conditioner, a heating, ventilating and air conditioning (HVAC) system, a heating, ventilating, air conditioning and refrigeration (HVACR) system, a garage door opener, a camera, a door lock, a window lock, a window opener, a household appliance (e.g., a coffee maker, a refrigerator, a stove, a toaster, a vacuum, a washer, a dishwasher, a dryer, a cooktop, a range, a rendering device, a freezer, a blender, a mixer, etc.), a robot, a robotic arm, or any other device that may be controlled to adjust a condition to a desired state. The condition may include, but is not limited to, for example, ON/OFF, OPEN/CLOSED, slow/fast, forward/back, up/down, temperature, sound level, fluid flow, fluid direction, fluid flow velocity, fluid level, CO level, CO₂level, O₂level, moisture level, humidity level, light level, force/pressure level, GPS position, pressure, air quality, or the like. The actuator(s) may be configured to receive an actuator control signal from the secondary device 210 (shown in FIG. 1B) to control the external device (not shown) to adjust a condition to a predetermined state. The predetermined state may include, for example, but is not limited to, a preset temperature, a preset humidity, a preset locked/unlocked state, a preset open/closed state, or any other predetermined condition or state which may be adjusted to by the actuator.

As seen in FIG. 11, if an alarm event signal is received from the alarm event transducer (“YES” at act 1115), then the controller 202 (shown in FIG. 1B) may generate an alarm event signal (act 1120) and transmit the alarm event signal (act 1125) to a rendering device, otherwise the controller 202 may continue to detect for an alarm event signal (“NO” at act 1115).

The controller 202 may generate an actuator control signal based on the received event signal (act 1130) and transmit the actuator control signal to the appropriate actuator (act 1135) to control the actuator to adjust or restore a condition to a desired state.

In the case where the alarm event transducer 104-x includes, for example, a flood sensor and the external device includes a wireless z-wave water valve, the controller 202 may receive an event signal from the flood sensor when a flood condition is detected in a basement (“YES” at act 1115). The controller 202 may then generate and transmit an alarm event signal (acts 1120, 1125) to a rendering device to produce an alarm signal that may be heard (e.g., audible signal), felt (e.g., vibration signal or pressure signal), seen (e.g., light signal), smelled (e.g., an olfactory signal), or otherwise sensed by a user. The rendering device may include, for example, an iLuv® Impact™ light device, iLuv® Rainbow, light series, or the like, that may be activated to illuminate the flooded area. The rendering device may also include a camera device (not shown) that may be activated to record the area in the vicinity of the detected alarm condition. The controller 202 may further generate and transmit an actuator control signal (acts 1130, 1135) to the wireless z-wave water valve to drive and close the valve so as to prevent further flow of water into, for example, leaking pipes.

Where the alarm condition is, for example, a fire, the controller 202 may generate and transmit an actuator control signal (acts 1130, 1135) to, for example, a door lock (not shown) to unlock the door for easier escape from the premises and to a light device (not shown) to light the exit passageway. The actuator control signal (acts 1130, 1135) may be sent to a controller (not shown) to activate preventive or remedial measures, such as, for example, water sprinklers to extinguish the fire.

Where the alarm condition is, for example, a forced entry by a robber or intruder, the controller 202 may generate and transmit an actuator control signal (acts 1130, 1135) to, for example, a connected device 140-x to cause the device to emit an alarm signal (e.g., a sound signal, a light signal, a video signal, or the like). The actuator control signal may also be sent to, for example, a camera (not shown) that is located in the vicinity of the intrusion to cause the camera to target the intrusion area and record the video of the intrusion. The actuator control signal may be sent to the device 102 (shown in FIG. 1A), which may include, for example, a smartphone, a tablet, a computer, or the like, to manifested an alarm signal to the user.

The controller 202 may transmit an alarm event signal (acts 1120, 1125) to the device 102 (shown in FIG. 1A), which may include a smartphone, a tablet, a computer, or the like, to cause the device 102 to manifest an alarm signal to the user. The alarm signal may be manifested as a video message (e.g., an illustration of a flooded room, an image of the actual area where the alarm event transducer detected the alarm condition, or the like), a text message (e.g., a predetermined message such as “GAS LEAK IN BASEMENT,” “FLOOD,” or the like), a sound signal (e.g., a spoken message such as “gas leak in basement,” “flood in home,” or the like), or any combination of the foregoing.

After transmitting the actuator control signal to the actuator, the controller 202 may detect for an actuator response signal (act 1140) to confirm that the actuator control signal (“YES” at act 1140) was received by the actuator. In the above example, the actuator control signal may include an instruction (e.g., “CLOSE VALVE”) to drive the wireless z-wave water valve to a closed position and the actuator response signal may include, for example, the real-time condition of the actuator—for example, “VALVE IS CLOSING,” or “VALVE HAS BEEN CLOSED”. Act 1140 may be optionally provided where the actuator is configured to send an actuator response signal, or it may be omitted where it is not desirable or the actuator is incapable of transmitting a response signal.

If an actuator response signal is not received within a predetermined time period (“NO” at act 1140), the actuator control signal may be re-transmitted to the actuator (act 1135). The predetermined time period may be set to milliseconds, seconds, minutes, hours, days, etc., depending on the particular application, particular alarm event transducer, particular actuator, particular external device, or the like, as understood by those of ordinary skill in the art.

Based on the actuator response signal (“YES” at act 1140) (or on the actuator control signal (act 1135), where act 1140 is omitted), an actuator status signal may be generated and sent to the rendering device (shown in FIG. 1B) and/or the primary device 102 (shown in FIG. 1A) to render the actuator status signal that is indicative of the condition of the actuator (act 1145). The actuator status signal may be reproduced as a sound signal (e.g., a spoken message) on the speaker 212 (shown in FIG. 1B), an image signal (e.g., text/video/graphic/etc. message) on the display 206 (shown in FIG. 1B), a haptic signal (e.g., vibration) on the haptic device 216 (shown in FIG. 1B).

The alarm and monitoring system 100A (shown in FIG. 1A) may carry out the ecosystem process 1100 (shown in FIG. 11). Referring to FIG. 1A, the secondary device 110 may be positioned, for example, under a pillow and/or otherwise positioned, fastened, etc. with relation to a pillow, mattress, etc., of a user. The secondary device 110 may include the structure of the secondary device 210 (shown in FIG. 1B).

Referring to FIGS. 1A and 1B, according to a non-limiting embodiment of the disclosure, the secondary device 210 (or 110) may generate and communicate an actuator signal to one or more devices 140-x to wake or alert the user. As mentioned earlier, the devices 140-x may include a haptic device (e.g., vibrating), light device (e.g., lamp turn on, gradually brighten and/or flashing), speaker (e.g., render audio) and/or other device (e.g., a thermostat) for rendering the alarm information and/or otherwise responding. The user may be hearing impaired (for example, deaf) or visually impaired (e.g., blind). The secondary device 210 may comprise a receiver 218 communicatively coupled and configured to receive an alarm event signal from another one of the devices 140-x (shown in FIG. 1A) such as an alarm event transducer, which may include, for example, a burglar alarm, a fire alarm, a carbon-monoxide alarm, or the like. The controller 202 may be communicatively coupled to the receiver 218 and configured to generate an actuator control signal based on the received alarm event signal, and a transmitter 218 communicatively coupled to the controller 202 and configured to transmit the actuator control signal to the other device 140-x, such as an actuator (such as, for example, a SmartShaker™, a speaker, an LED light bulb, or the like) to alert or awaken the user. The actuator control signal may be sent to a plurality of devices 140-x simultaneously (or at different times) to cause the devices 140-x (such as, for example, SmartShaker™, haptic device, speaker, LED, light device, display, or the like) to operate and thereby provide, for example, a sleep eco-system. The secondary device 210 may be programmed or configured by the App 102 (shown in FIG. 1A), such as, for example, a smart phone, a tablet, a computer, or the like, to operate the devices 140-x in a desired manner. For instance, to awaken a hearing impaired user, the secondary device 210 may be configured to activate the SmartShaker™, LED and a coffee machine at substantially the same (or different) time based on a predetermined time.

FIG. 12 shows an example of an ecosystem 1200 constructed in accordance with the present system. The ecosystem 1200 includes a primary device 102, a secondary device 110 (or 210), a cloud system (or cloud service) 1220, and a linked device 1202. The ecosystem 1200 may further include one or more additional devices 140 (shown in FIG. 1A), which may be communicatively coupled to the secondary device 110. The linked device 1202 may be substantially the same as, or include the primary device 102 (shown in FIG. 1A) (or device 691, shown in FIG. 6) discussed above. For instance, the devices 102 and 1202 may each be, for example, a smartphone (such as, for example, an Apple iPhone, a Samsung Galaxy, or the like), a tablet (such as, for example, an

Apple iPad, a Samsung Galaxy Tablet, or the like), a laptop, or the like. In the ecosystem 1200, the secondary device 110 may be activated from outside of, for example, a home, or anywhere else practically. If included, one or more additional devices 140 may be activated, monitored and/or controlled via the secondary device 110, so as to produce and/or send a sound signal (e.g., an alarm), a visual signal (e.g., a displayed image, text, and the like), a haptic signal (e.g., a vibration), and an actuator (or control) signal (e.g., a thermostat control signal, an appliance control (ON/OFF/ADJUST) to control an appliance such as a stove, washer, refrigerator, coffee machine, microwave oven, toaster, and the like). In this regard, the cloud system 1220 may receive a communication signal from the linked device 1202 and send a notification signal to the secondary device 110, which may be sent directly or via the primary device 102. Accordingly, a friend, family member, third party service provider, or the like (hereinafter “linked user”), using for example the linked device 1202, may send a communication signal to the cloud system 1220, which in turn will send a notification signal to the secondary device 110. The notification signal may comprise an actuator control signal or an event signal to, for example, notify, awaken, inform, or otherwise alert a user, or monitor/control another device, such as, for example, a device 140, which, as previously noted, may include an appliance, or the like. The notification signal may include a message, such as alarm information. The secondary device 110 may include a SmartShaker™.

As previously discussed, the secondary device 110 may render related information at a fixed and/or ascending (e.g., periodically increasing) level as programmed and/or otherwise set, desired, etc. For example, in an embodiment wherein an ascending haptic and/or auditory level is produced, the haptic and/or auditory level may start at a first level for a period of time, which in an event wherein the user does not operate to stop rendering, the controller may operate periodically to increase the haptic and/or auditory level to higher levels until a maximum level is reached or the user operates to stop the rendering. Similarly, in an embodiment wherein a descending haptic and/or auditory level is produced, the haptic and/or auditory level may start at a first level for a period of time, which in an event wherein the user does not operate to stop rendering, the controller may operate periodically to decrease the haptic and/or auditory level to lower levels until a minimum level is reached or the user operates to stop the rendering. As noted previously, the controller in the secondary device 110 may operate through programming and/or construction to produce a fixed haptic and/or auditory level until the user operates to stop the rendering. The system may produce a corresponding haptic and/or auditory level for a period of time, at which time, the controller may operate to stop the rendering without user intervention.

According to a non-limiting example, the ecosystem 1200 may interact with one or more third party systems (for example, Facebook®, LinkedIn®, Twitter®, Instagram®, and the like), so as to associate one or more user accounts and/or linked devices 1202 (or linked user accounts) with a given secondary device 110. For instance, using the primary device 102, a user may select one or more linked users from the user's Facebook® friends, telephone contacts, LinkedIn® connections, Twitter® connections, or the like, to be associated with the secondary device 110, so that communication signals may be received from the respective accounts and/or devices of these linked users and notification signals sent to the secondary device(s) 110 (or 210, shown in FIG. 1B) to produce a haptic signal, an auditory signal, a visual signal, and/or a monitor/control signal. In this regard, an adult offspring user may, for example, select the offspring's parent as a linked user from the user's Facebook® friends and associate a secondary device 110 provided in the user's home to produce a haptic, auditory, visual, or actuator control signal when an alarm event occurs with the linked user, such as, for example, when a burglar alarm, fire alarm, CO₂alarm, and the like, is triggered at the parent linked user's location or by the linked user device 1202.

The ecosystem 1200 may have broad applications with respect to an individual's friends and family network, as well as third party service providers, such as, for example, alarm companies, on-line vendors (e.g., Amazon®), and the like. The ecosystem 1200 provides an interactive platform that may be implemented in, for example, a smart home, in which friends/family that may be invited and connected to monitor and share information and alert the user recipient via one or more secondary devices 110, or other devices 140, including sending notification signals to, for example, control appliances (e.g., turn off a stove when outside, turn on/off a heater/cooler via a smart thermostat (e.g., Nest® thermostat, Honeywell® thermostat, or the like)), send alarm settings to the recipient's primary device 102 and/or secondary device 110 while he or she is sleeping, and the like.

Referring to FIG. 12, the cloud system 1220 may include an account server 1224. The cloud system 1220 may further include a messaging server 1222 and a push notification server 1226. Using the primary device 102, a user may connect to the account server 1224 and set up an account on the server 1224 using, for example, the user's email account, Facebook® account, Twitter® account, Google® account, or the like. The account server 1224 may identify the primary device 102 and store identification (ID) information for the device, such as, for example, a media access control (MAC) address of the device 102. The account server 1224 may store identification information for the user, such as, for example the user's email account, iLuv® account, Facebook® account, Google® account, Twitter® account, or the like. The account server 1224 may store device ID information (e.g., MAC address, an IP address, and the like) of the secondary device 110 (and/or additional device 140) that is associated with the user and/or the primary device 102.

FIG. 13 shows a flow diagram that illustrates an example of a process 1300 that may be carried out by the ecosystem 1200. In addition to being able to carry out the processes 500 (shown in FIG. 5) and 1100 (shown in FIG. 11) described above, the ecosystem 1200 may carry out the process 1300 to facilitate interactive communication, set-up, and/or control of one or more secondary devices 110 (210) by one or more linked devices 1202 (or primary devices 102). Where include, the process 1300 may further facilitate interactive communication, set-up, and/or control of one or more additional devices 140 (shown in FIG. 1A).

Referring to FIGS. 12 and 13 concurrently, using the primary device 102, a user may initiate a communication session with the account server 1224 (act 1301) to register a user account. During act 1301, the user may create a user account, which may be registered using the user's email account, iLuv® account, Facebook® account, Google® account, Twitter® account, or the like. The account server 1224 may receive and store ID information of the primary device 102 in association with the user account. The user account may include login information such as, for example, login identification, password, and the like. During account registration (act 1301), the user may download/upload, add/delete/modify, search, and manage contact information for individuals (e.g., friends, family, colleagues, and the like) or entities (e.g., service providers, institutions, companies, government agencies, and the like). The user may search profiles, send/receive invitations, accept/reject invitations, add/remove contact information for individuals or entities. The user may also register and associate one or more devices 140, including, for example, smart appliances. Smart appliances may include, for example, residential and/or commercial appliances that are configured to communicate and be controlled remotely via communication links, such as, for example, a stove, dishwasher, washer, refrigerator, coffee maker, toaster, microwave oven, or the like, that may be controlled and/or monitored remotely via a communication link over a network such as the Internet.

The user may select and identify contact information for linked users, including those individuals and/or entities to be linked to a particular secondary device 110 that may be located, for example, at the user's home, office, or anywhere else (act 1303). The linked users may be selected, for example, from a list of “friends” in the Facebook® account of the registered user. The user account information on the account server 1224 may be updated and include ID information for the linked devices 1202 used by or associated with linked users. The user account information may also be updated and include ID information for the secondary device 110 (and/or additional devices 140). The ID information for the linked device(s) 1202 and/or secondary device(s) 110 may include, for example, MAC addresses, or any other information that may identify the devices and facilitate targeted transmission/reception of communication signals to/from the devices.

The account server 1224 may initiate communication and transmit a communication signal that includes a computer program, or a link to a site from which the computer program may be downloaded, to the linked devices 1202 of each of the linked users (act 1305). The computer program may be installed on each linked device 1202 (act 1307) and used to initiate transmission of communication signals to/from the primary device 102, secondary device 110, and/or additional device 140 associated with the user (acts 1309, 1311, 1313, 1315, 1317). The computer program, when executed on the linked user device 1202, may cause a graphic user interface to be displayed on the device, allowing the linked user to, for example, schedule an alarm date and time, select the alarm type (e.g., sound, visual, haptic, or the like), alarm intensity (e.g., amplitude level, frequency level, or the like), an alarm duration, and the like. The displayed graphic user interface may include GUI shown in FIGS. 6-8, discussed above.

According to an embodiment of the system, the linked device 1202 may communicate with the primary device 102 by initiating and carrying out communication with the primary device 102 via the messaging server 1222 (acts 1309, 1311 and 1313). In this regard, the primary device 102 may check and fetch a notification signal from the message server 1222. The communication may include sending a communication signal from the linked device 1202 to the message server 1222 (act 1309), the primary device 102 checking and fetching the notification signal from the message server 1222 (act 1311), and the primary device 102 transmitting the notification signal to the primary device 102 (act 1313). As noted earlier, the notification signal may comprise an actuator signal and/or an event signal to, for example, notify, awaken, inform, or otherwise alert the user, or to control a device 140.

The communication signal may include control information to, for example, set up a scheduled alarm, on-demand alert, and the like. As noted earlier, the scheduled alarm setup may include setting a date, day of week, time, sound type, sound level, haptic type, haptic intensity level, visual type, visual level, and the like for the secondary device 110 via a graphic user interface (e.g., shown in FIGS. 6-8) on the linked device 1202. The on-demand alert setup may include sound type, sound level, haptic type, haptic intensity level, visual type, visual level, and the like.

Alternatively (or additionally), the notification signal may be pushed to the primary device 102 by the push notification server 1226 (acts 1309, 1315, 1317) using, for example, Apple® Push Notification Services (APNS), Firebase Cloud Messaging (FCM), or the like. For instance, the communication signal may be received by the message server 1222 from the linked device 1202 (act 1309) and the notification signal forwarded to the push notification server 1226 (act 1315) to automatically push down to the primary device 102 (act 1317), which in turn may forward the notification signal to the secondary device 110 (act 1313).

As seen in FIG. 12, the notification signal may include a “Fire” alarm event signal that may be sent to the primary device 102 from the message server 1222 (act 1311, FIG. 13) or from the push notification sever 1226 (act 1317, FIG. 13). The primary device 102 may then send the “Fire” alarm event signal to the secondary device 110 (act 1313, FIG. 13). The notificaiton signal may be sent to the secondary device 110 directly over a communication link (e.g., Bluetooth, WiFi, or the like), or through the network 103 (shown in FIG. 1A), causing the secondary device 110 to render, for example, a haptic signal and/or an auditory signal (act 1319, FIG. 13).

FIGS. 14 and 15 show examples of an ecosystem 1200′. The ecosystem 1200′ includes the ecosystem 1200 (shown in FIG. 12) provided with an external service server 1228 (shown in FIGS. 14 and 15). As seen in FIG. 14, the ecosystem 1200′ may exclude the linked device 1202. Alternatively, as seen in FIG. 16, the ecosystem 1200′ may include both the external service server 1228 and linked device 1202.

Referring to FIGS. 14 and 15, the external service server 1228 may communicate with, or include one or more third party servers 1250, 1260, 1270, such as, for example, an Amazon® server 1250 using an Amazon® Echo Service API, a Nest® server 1260 using a Nest® API, or any other compatible server 1270 using an Internet-of-Things (IoT) service API. The external server 1228 may send communication signals to the account server 1224 or messaging server 1222. The transmitted communication signal may include, for example, a message that a linked user's house is empty, a message that a Nest® camera detected motion at the linked user's location, a message that Nest® Protect detected a fire condition at the linked user's location, or the like.

FIG. 16 shows a flow diagram that illustrates an example of a process 1500 that may be carried out by the ecosystem 1200′ in FIG. 14. In addition to carrying out the processes 500 (shown in FIG. 5), 1100 (shown in FIG. 11), and 1300 (shown in FIG. 13) described above, the ecosystem 1200′ may carry out the process 1500 to facilitate communication between the external service server 1228 and one or more secondary devices 110. Where included, the process 1500 may further facilitate communication between the external service server 1228 and one or more additional devices 140 (shown in FIG. 1A).

Referring to FIGS. 14 and 16 concurrently, after a user account is set up and registered (act 1301) and linked users selected and linked (act 1303) as described above, the account server 1224 may initiate a communication with the external services server 1228 (act 1505) using, for example, an appropriate API (e.g., Amazon® Echo Service API, Nest® API, IoT API, or the like). According to an embodiment of the system, the external services server 1228 may cause a notification signal to be sent to the secondary device 110 by initiating and carrying out communication with the primary device 102 via the messaging server 1222 (acts 1509, 1311 and 1313). In this regard, the primary device 102 may check and fetch a notification signal from the message server 1222 (act 1311). The communication may include sending a communication signal from the external services server 1228 to the message server 1222 (act 1509), the primary device 102 checking and fetching a notification signal from the message server 1222 (act 1311), and the primary device 102 transmitting the notification signal to the secondary device 110 (act 1313). The communication signal and the notification signal may be substantially the same signal. The communication signal may include the notification signal.

Alternatively (or additionally), the notification signal may be pushed to the primary device 102 by the push notification server 1226 (acts 1509, 1315, 1317) using, for example, Apple® Push Notification Services (APNS), Firebase Cloud Messaging (FCM), or the like. For instance, the communication signal may be received by the message server 1222 from the external services server 1228 (act 1509) and the notification signal forwarded to the push notification server 1226 (act 1315) to automatically push down to the primary device 102 (act 1317), which in turn may forward the notification signal to the secondary device 110 (act 1313).

As seen in FIG. 15, the notification signal may include a “Fire” alarm event signal that may be sent to the primary device 102 from the message server 1222 (act 1311, FIG. 16) or from the push notification sever 1226 (act 1317, FIG. 16). The primary device 102 may then send the notification signal, including the “Fire” event signal to the secondary device 110 (act 1313, FIG. 16). The notification signal may be sent to the secondary device 110 directly over a communication link (e.g., Bluetooth, WiFi, or the like), or through the network 103 (shown in FIG. 1A), causing the secondary device 110 to render, for example, a haptic signal and/or an auditory signal (act 1319, FIG. 16).

The ecosystem 1200′ in FIG. 15 may carry out either or both processes 1300 (shown in FIG. 13) and 1500 (shown in FIG. 16).

While the present invention has been shown and described with reference to particular exemplary embodiments, it will be understood by those skilled in the art that present invention is not limited thereto, but that various changes in form and details, including the combination of various features and embodiments, may be made therein without departing from the spirit and scope of the invention.

Finally, the above-discussion is intended to be merely illustrative of the present system and should not be construed as limiting the appended claims to any particular embodiment or group of embodiments. Thus, while the present system has been described with reference to exemplary embodiments, it should also be appreciated that numerous modifications and alternative embodiments may be devised by those having ordinary skill in the art without departing from the broader and intended spirit and scope of the present system as set forth in the claims that follow. In addition, the section headings included herein are intended to facilitate a review but are not intended to limit the scope of the present system. Accordingly, the specification and drawings are to be regarded in an illustrative manner and are not intended to limit the scope of the appended claims.

In interpreting the appended claims, it should be understood that:

a) the word “comprising” does not exclude the presence of other elements or acts than those listed in a given claim;

b) the word “a” or “an” preceding an element does not exclude the presence of a plurality of such elements;

c) any reference signs in the claims do not limit their scope;

d) several “means” may be represented by the same item or hardware or software implemented structure or function;

e) any of the disclosed elements may be comprised of hardware portions (e.g., including discrete and integrated electronic circuitry), software portions (e.g., computer programming), and any combination thereof;

f) hardware portions may be comprised of one or both of analog and digital portions;

g) any of the disclosed devices or portions thereof may be combined together or separated into further portions unless specifically stated otherwise;

h) no specific sequence of acts or steps is intended to be required unless specifically indicated;

i) the term “plurality of” an element includes two or more of the claimed element, and does not imply any particular range of number of elements; that is, a plurality of elements may be as few as two elements, and may include an immeasurable number of elements; and

j) the term and/or and formatives thereof should be understood to mean that only one or more of the listed elements may need to be suitably present in the system in accordance with the claims recitation and in accordance with one or more embodiments of the present system.

	Number	Date	Country
Parent	15266028	Sep 2016	US
Child	16531588		US

	Number	Date	Country
Parent	15067985	Mar 2016	US
Child	15266028		US
Parent	14937797	Nov 2015	US
Child	15067985		US

ALARM AND MONITORING SYSTEM AND METHOD OF OPERATION THEREOF

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Provisional Applications (1)

Continuations (1)

Continuation in Parts (2)