Source: https://patents.google.com/patent/US20160261824A1/en
Timestamp: 2018-12-11 03:24:23
Document Index: 79788793

Matched Legal Cases: ['Application No. 62', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804', 'arty 2804']

US20160261824A1 - Light socket surveillance systems - Google Patents
Light socket surveillance systems Download PDF
US20160261824A1
US20160261824A1 US15060282 US201615060282A US2016261824A1 US 20160261824 A1 US20160261824 A1 US 20160261824A1 US 15060282 US15060282 US 15060282 US 201615060282 A US201615060282 A US 201615060282A US 2016261824 A1 US2016261824 A1 US 2016261824A1
US15060282
A light socket surveillance system can be used to enable a first party to communicate with a second party. The light socket surveillance system can be used to detect an audible notification from the first party. In response to detecting the audible notification from the first party, the light socket surveillance system can initiate a communication session with a remote computing device of the second party.
This application claims the benefit and is a non-provisional of U.S. Provisional Patent Application No. 62/129,816; filed Mar. 7, 2015; and entitled LIGHT SOCKET SURVEILLANCE SYSTEMS; the entire contents of which are incorporated herein by reference.
The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/549,548; filed Nov. 21, 2014; and entitled LIGHT SOCKET CAMERAS.
The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/549,545; filed Nov. 21, 2014; and entitled LIGHT SOCKET CAMERAS.
The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/534,588; filed Nov. 6, 2014; and entitled LIGHT SOCKET CAMERAS.
The entire contents of the following application are incorporated by reference herein: U.S. Nonprovisional patent application Ser. No. 14/849,513; filed Sep. 9, 2015; and entitled LIGHT SOCKET CAMERAS.
The disclosure describes methods for using a light socket surveillance system to enable a first party to communicate with a second party. The light socket surveillance system can include an outer housing defining a proximal end, a distal end that is opposite the proximal end, and a sidewall that extends between the proximal end and the distal end. In some embodiments, the light socket surveillance system includes a detection system having a camera, a speaker, and a microphone. The light socket surveillance system can include a screw thread contact located adjacent the proximal end of the outer housing. In some embodiments, the method includes detecting, via the microphone, an audible notification from the first party. In response to detecting the audible notification from the first party, the method can include initiating a communication session with a remote computing device of the second party.
The audible notification can comprise a voice command instructing the light socket surveillance system to contact the second party. Methods can include enabling, via the speaker and the microphone, the first party and the second party to audibly communicate with each other.
The audible notification can comprise a distress notification indicating that the first party requires assistance. The communication session can comprise an indication of the distress notification.
Methods can include recording a noise with the microphone; recording an image with the camera; and initiating a communication session with the remote computing device of the second party. The communication session can comprise an indication of at least one of the noise and image.
The sidewall can comprise a first portion and a second portion that is rotatable with respect to the first portion. The camera can be coupled to the second portion. Methods can further include determining whether the first party is located within a field of view of the camera. In response to detecting the audible notification and in response to determining that the first party is not located within the field of view of the camera, methods can include automatically rotating the second portion until the first party is located within the field of view of the camera. In response to determining that the first party is located within the field of view of the camera, methods can include recording the image with the camera.
In some embodiments, the method includes detecting an indication suggestive of a visitor's presence. In response to detecting the indication suggestive of the visitor's presence, methods can include determining a number of visitors present within a vicinity of the light socket surveillance system.
The light socket surveillance system can be located inside a home of a homeowner, and the vicinity can be a room located inside the home. The light socket surveillance system can be located outside a home of a homeowner, and the vicinity can be an area of an outer premise where the home is located.
In some embodiments, detecting an indication suggestive of a visitor's presence comprises detecting an infrared signature of the visitor. The light socket surveillance system can comprise an infrared camera. Accordingly, detecting the infrared signature of the visitor can comprise detecting the infrared signature of the visitor with the infrared camera.
In response to detecting the indication suggestive of the visitor's presence, the method can further include recording, by the camera, at least one of a video and image of the visitor; and initiating a communication session with a remote computing device. In some embodiments, the communication session comprises at least one of the video and image of the visitor.
Methods can include determining an identity of a first visitor. Methods can also include determining an identity of a second visitor. Methods can even include initiating a communication session with a remote computing device. The communication session can comprise the identity of the first visitor and the identity of the second visitor. The communication session can comprise the number visitors present within the vicinity of the light socket surveillance system. The remote computing device can be operated by a party associated with a building in which the light socket surveillance system is coupled.
The disclosure also a light socket surveillance system that can comprise an outer housing defining a proximal end, a distal end that is opposite the proximal end, and a sidewall that extends between the proximal end and the distal end. The light socket surveillance system can also include a screw thread contact coupled to the proximal end of the outer housing. The screw thread contact can be rotatably attached to a light socket. The light socket surveillance system can also include a detection system coupled to the outer housing. The detection system can comprise a camera configurable to record images, a speaker configurable to emit noise, and a microphone configurable to detect sound.
The outer housing can include a first outer housing and a second outer housing rotatable with respect to the first outer housing. The detection system can be coupled to the second outer housing such that the detection system is rotatable with respect to the first outer housing.
The light socket surveillance system can further include a motion detector coupled to the outer housing. The motion detector can be configured to detect an indication suggestive of a visitor's presence.
The light socket surveillance system can be configurable to determine an identity of a visitor based upon the second noise as detected by the microphone. The light socket surveillance system can even be configurable to detect a presence of a remote computing device. In such embodiments, the light socket surveillance system can be configured to determine an identity of a visitor associated with the remote computing device.
FIGS. 28b-28f illustrate various responses to detecting the sound from FIG. 28a , according to various embodiments.
FIGS. 31b-31f illustrate various responses to detecting the audible instruction from FIG. 31a , according to various embodiments.
Communication systems can provide a secure and convenient way for a remotely located individual to see and/or communicate with a person who is within the field of vision of a camera and/or within the range of a microphone. Communication systems can include a camera that is attached to a light socket to couple the camera to a wall and to provide electricity to the camera. It should be appreciated that communication systems can be referred to as security systems, light socket cameras, light socket surveillance systems, surveillance systems, and the like.
Referring now to FIG. 1a , communication systems 200 can be a portion of a smart home hub. Communication systems 200 can facilitate home automation. In some cases, cameras 208 are electrically coupled to a light socket of a building 300 and are integrated into a holistic home automation system and/or home security system. Various systems described herein enable home surveillance and/or complete home automation. Cameras 208 threadably screwed into an interior light socket can enable a remote user to see events inside of a building 300 (shown in FIG. 3). As well, cameras 208 threadably screwed into exterior light sockets can enable a remote user to see events outside of a building 300.
Now with added reference to FIG. 1b , the security system 202 c can include a proximal end 280 and a distal end 282 that is opposite the proximal end 280. The camera assembly 208 can be located at the distal end 282 of the security system 202 c. However, it should be appreciated that the camera assembly 208 can be positioned at any location on the security system 202 c, such as the sidewall 680. The security system 202 c can also include a foot contact 618 located at the proximal end 280 of the security system 202 c.
As shown in FIG. 1a , the security system 202 c can include a diagnostic light 216 and a power indicator light 220. In some embodiments, the diagnostic light 216 is a first color (e.g., blue) if the security system 202 c and/or the communication system 200 is connected to a wireless Internet network and is a second color (e.g., red) if the security system 202 c and/or the communication system 200 is not connected to a wireless Internet network. In some embodiments, the power indicator 220 is a first color if the security system 202 c is connected to a power source. The power source can be power supplied by the building 300 to which the security system 202 c is attached. The security system 202 c can receive electricity via the light socket to which the security system 202 c is attached. In some embodiments, the power indicator 220 is a second color or does not emit light if the security system 202 c is not connected to the power source.
The computing device 204 can run software with a graphical user interface. The user interface can include icons or buttons. In some embodiments, the software is configured for use with a touch-screen computing device such as a smartphone or tablet. The security system 202 c can include a motion detector 218 configured to detect the presence of people (e.g., in the outdoor area or room in which the security system 202 c is located) or objects. The security system 202 c can also be placed outdoors to detect people or objects outside. The motion detector 218 can be an infrared motion detector.
It should also be appreciated that the security system 202 may be implemented with a theft prevention system (not shown). The theft prevention system may be a lock that only authorized users may be able to unlock to thereby remove the security system 202 from the light socket 650. The lock may be mechanical or electrical, thus allowing the security system 202 to prevent theft.
Referring now to FIG. 1a , in some embodiments, if the security system 202 c loses power, loses connectivity to the computing device 204, loses connectivity to the Internet, and/or loses connectivity to a remote server, a remote server 206 transmits an alert (e.g., phone call, text message, image on the user interface 240) regarding the power and/or connectivity issue. In several embodiments, the remote server 206 can manage communication between the security system 202 c and the computing device 204. In some embodiments, information from the security system 202 c is stored by the remote server 206. In several embodiments, information from the security system 202 c is stored by the remote server 206 until the information can be sent to the computing device 204, uploaded to the computing device 204, and/or displayed to the remotely located person via the computing device 204. The remote server 206 can be a computing device that stores information from the security system 202 c and/or from the computing device 204. In some embodiments, the remote server 206 is located in a data center.
In some embodiments, the computing device 204 and/or the remote server 206 attempt to communicate with the security system 202 c. If the computing device 204 and/or the remote server 206 is unable to communicate with the security system 202 c, the computing device 204 and/or the remote server 206 alerts the remotely located person via the software, phone, text, a displayed message, and/or a website.
Referring now to FIG. 1a , in some embodiments, the server 206 controls communication between the computing device 204 and the security system 202 c, which can include a camera, a microphone, and a speaker. In several embodiments, the server 206 does not control communication between the computing device 204 and the security system 202 c.
FIG. 4 illustrates a perspective view of a light socket 650. The light socket 650 can include a screw thread contact 652 configured to mechanically and electrically couple with the screw thread contact 614 of the security system 202 c (shown in FIG. 1a ). The light socket 650 can also include a foot contact 654 configured to electrically couple with the foot contact 618 of the security system 202 c (shown in FIG. 1a ). The foot contact 654 of the light socket 650 can be located at the distal end of the light socket 650.
In embodiments, the light socket 650 may be compatible with any number of standards for socket sizes. For example, the light socket 650 may use the Edison screw E26 or E27 standard or a bayonet mount. Various voltages may be carried to provide electrical power to the security system (e.g., 100V to 240V) depending on the local electrical standards.
FIG. 7a illustrates the security system 202 c screwed into the light socket 650. In this configuration, the security system 202 c is electrically coupled to a power supply of the building 300. The light socket 650 can be located indoors or outdoors.
FIGS. 9 and 10 illustrate a security system 202 d that can include any of the features described in the context of the security system 202 c shown in FIGS. 1a, 1b and 3-8. The security system 202 d, as shown in FIG. 9, can also be configured to screw into the light socket 650. In this manner, the security system 202 d can be rotated in a direction of rotation 690 about a first axis 266 to thereby attach the security system 202 d to the light socket 650. The security system 202 d can include a camera assembly 208 d that faces a radial direction that is perpendicular to the first axis 266.
FIG. 13a illustrates a side view of a security system 202 e with a dome camera assembly 208 e. The dome camera assembly 208 e can have a shape that is half of a sphere. In some embodiments, the dome camera assembly 208 e includes an outer cover 228 that has a curved and/or spherical shape (e.g., half of a sphere). The cover 228 can be a translucent material such as plastic and/or polycarbonate.
The field of vision 238 of the dome camera assembly 208 e can include half of a sphere. In some embodiments, the field of vision 238 includes approximately 360 degrees around the base of the cover 228 and/or around a central axis 266 of the screw thread contacts 614. In several embodiments, the field of vision 238 includes at least 330 degrees around the base of the cover 228. In some embodiments, the field of vision 238 is approximately 180 degrees in a plane that includes the central axis 266 of the screw thread contacts 614 (e.g., in the plane represented by the page on which FIG. 13a appears). In several embodiments, the field of vision 238 is at least 140 degrees and/or less than 260 degrees in a plane that includes the central axis 266.
FIGS. 13b-13e further illustrate the field of vision in various embodiments. With specific reference to FIG. 13b , the field of vision 238 g can be defined by a vertical field of vision 692 g and a horizontal field of vision 694 g. The vertical field of vision 692 g can be any angle less than 180 degrees (as shown by the distal plane 693), such as 140 degrees. Because FIGS. 13b-13e are side views, the horizontal field of vision 692 g and the vertical field of vision 694 g are actually radial, meaning that they extend 360 degrees around the perimeter of the camera assembly 208 g. This 360 degree periphery is further illustrated in FIG. 13e . FIG. 13e is a top down view, looking from above the security system (when it is mounted to the light socket 650) to the ground below the security system. FIG. 13e shows that the horizontal field of vision 694, 694 g actually covers 360 degrees around the perimeter of the security system and the axis 266. While the vertical field of vision is not illustrated in FIG. 13e , the vertical field of vision is also radial, in that it covers the 360 degree area around the security system.
The security system 202 h illustrated in FIG. 13c may define a 180 degree vertical field of vision, which means that the camera assembly 208 h is able to see anything that is level with or below the distal plane 693.
Furthermore, as shown in FIG. 13d , the security system 202 j may be configured to achieve a vertical field of vision 692 j that is greater than 180 degrees. For example, some embodiments may have a vertical field of vision equal to at least 250 degrees, up to 250 degrees, up to 280 degrees, and in some embodiments, up to 300 degrees. (It should be appreciated that in some embodiments that utilize multiple cameras, a vertical field of vision of up to 360 degrees may be achieved.) In the embodiment shown in FIG. 13d , to accomplish a vertical field of vision greater than 180 degrees, the camera assembly 208 j may be configured to move vertically downward. Specifically, the camera assembly 208 j may be configured to move along a camera assembly direction of movement 209 j, as shown in FIG. 13d . In this regard, the camera assembly 208 j may thereby gain separation from the distal end of the security system 202 j. This may allow the camera assembly 208 j to achieve a greater line of sight past the sidewalls in the upward, or proximal, direction.
As well, it should be appreciated that the camera assembly 208 h may be vertically moved along the direction of movement 209 h in response to any command or manual movement. For example, the camera assembly 208 h may be moved in response to a command from a remote computing device 204. As well, the camera assembly 208 h may be moved along the direction of movement 209 h in response to detecting a visitor. For example, the camera assembly 208 h may be positioned in a retracted position, whereby the camera assembly 208 h is located substantially within the security system as shown in FIGS. 13c and 13d . Accordingly, in response to the motion detector 218 detecting a visitor, the camera assembly 208 h may then move to an extended position (as shown in FIG. 13d ) to capture a greater vertical field of vision than in the retracted position. Moreover, the camera assembly 208 h may be manually moved by a user.
FIG. 14 illustrates a perspective view of the security system 202 e from FIG. 13a . The dome camera assembly 208 e can be used with any of the security systems described herein. The security system 202 e can include lights (e.g., LEDs) on an end that is opposite the end that includes the screw thread contacts 614.
Many embodiments may utilize the visitor identification abilities of the person using the remote computing device 204 (shown in FIG. 1a ). Various technologies, however, can be used to help the user of the remote computing device 204 to identify the visitor. Some embodiments use automated visitor identification that does not rely on the user, some embodiments use various technologies to help the user identify the visitor, and some embodiments display images and information (e.g., a guest name) to the user, but otherwise do not help the user identify the visitor.
Referring now to FIG. 1a , the camera assembly 208 can be configured to visually identify visitors through machine vision and/or image recognition. For example, the camera assembly 208 can take an image of the visitor. Software run by any portion of the system can then compare select facial features from the image to a facial database. In some embodiments, the select facial features include dimensions based on facial landmarks. For example, the distance between a visitor's eyes; the triangular shape between the eyes and nose; and the width of the mouth can be used to characterize a visitor and then to compare the visitor's characterization to a database of characterization information to match the visitor's characterization to an identity (e.g., an individual's name, authorization status, and classification). Some embodiments use three-dimensional visitor identification methods.
As illustrated in FIGS. 28a, 28b , 29 and 30, the disclosure includes a method for detecting an adverse sound 2800 (at step 2900). In response to detecting 2801 the adverse sound 2800, the method may include using the security system 202 to notify a party 2804 (at step 2902). The party 2804 to be notified may be any party that a user of the security system 202 may wish to contact, such as the user herself, or any contact listed on the user's contact list, such as a contact list stored within the user's remote computing device 204. As well, the party 2804 may be an emergency dispatcher, such as a 9-1-1 dispatcher (in the U.S.) or a dispatcher who responds to any emergency (in the U.S. or any other country). Generally, it should be appreciated that the party 2804 may be any party who may be interested in the occurrence of the adverse sound 2800.
The security system 202 may notify the party 2804 by sending a notification from the security system 202 to a computing device 204 associated with the party 2804. The security system 202 may transmit the notification through any wireless or wired technology. For example, the computing device 204 may receive the notification via a wireless technology such as radio frequency, WiFi (e.g., wireless local area network), cellular, Internet, Bluetooth, telecommunication, electromagnetic, infrared, light, sonic, and microwave. In this manner, the security system 202 may wirelessly communicate with the computing device 204 via the communication module 262 of the security system 202, which may be configured to connect to a wireless communication network. Furthermore, the security system 202 may transmit the notification through a wired technology, such as through the copper wires within the building 300, which may comprise a wired network. As well, the wired technology may include fiber-optics, Ethernet, telephone (e.g. digital subscribe line “DSL”), cable, and the like. In various embodiments, the wired technology can include Power-line communications through a home network. Various standards may be used such as IEEE 1901 or HomePlug AV.
As well, in response to detecting the adverse sound 2800, the method may further include using the camera 208 of the security system 202 to record one of an audio and video of an area adjacent the security system 202. As shown in FIG. 28c , upon the security system 202 detecting the adverse sound, the security system 202 may then capture a video or an audio recording 2812 of an event 2814 in an area adjacent the adverse sound 2800. The video and/or audio may be entered as evidence for a criminal investigation, or to determine liability in the event of a personal injury lawsuit. Upon capturing one of the audio and/or video, the method may further include transmitting the audio and/or video to the remote computing device 204.
The security system 202 may also be configured to determine logistical information, which may be helpful to an emergency dispatcher. For example, in response to the adverse sound 2800, the security system 202 may determine a location of the adverse sound 2800 with respect to its location inside or outside of the building 300. In response to determining the location of the adverse sound 2800, the security system 202 may transmit a notification of the location 2818 of the adverse sound 2800 to the party 2804. This may be helpful to emergency personal in order to locate the site of the adverse sound 2800, which may indicate the location of the victim, perpetrator, etc. In another example, the security system 202 may interface with existing law enforcement gunshot location systems to better triangulate the position of a gunshot for law enforcement authorities, even if the gunshot did not occur within the vicinity. Components of the security system 202 may be customized depending on the primary application. For example, if detecting gunshots, then the microphone 234 may need increased microphone sensitivity in lower frequencies.
With reference to FIG. 28e , the method may include determining a type of the adverse sound 2800, such as determining whether the adverse sound 2800 comprises a gunshot, scream, etc. In this regard, the security system 202 may include an internal processor to digitally analyze the adverse sound 2800 to determine the type of adverse sound. In some embodiments, the security system 202 may transmit a digital signal, which represents the adverse sound 2800, to an external processor to be digitally analyzed to determine the type of adverse sound. Upon determining the type of adverse sound 2800, the type of adverse sound 2800 may then be communicated to the party 2804, via the remote computing device 204. It should be appreciated that the notification as sent to the remote computing device 204 may be a text message, a phone call (such as a pre-recorded message), or any type of communication that notifies the party 2804 of the adverse sound 2800 and/or the type of the adverse sound.
As illustrated in FIG. 28f , methods may include interaction between two security systems, whereby a first security system 202 notifies a second security system 203 of the adverse sound 2800. For example, in response to detecting the adverse sound 2800, the method may include using the first security system 202 to initiate an event at a second security system 203 communicatively coupled to the first security system 202.
Detecting Audible Notifications
Methods may include detecting audible notifications and establishing communication between two parties via the security system 202. The security system 202 may also be configured to respond to communication between the two parties in the event of a distress notification.
In some embodiments, the security system 202 may have a detection system that uses the microphone 234 to record a noise and to monitor for an audible notification. The security system 202 may monitor the environment for the audible notification as a passive activity. For example, the security system 202 uses the microphone 234. The microphone 234 may record sounds at a particular sampling frequency (i.e., the number of times within a defined window of time that a sound is recorded) for a particular duration. The sampling frequency and duration for monitoring the environment may change depending on the preferences of a user. For example, the security system 202 can monitor for an audible notification every second in order to be responsive to a first party. The monitoring may also be restricted during times of the day to save resources. The security system 202 may reduce the sampling during times when residents are not present. For example, when most residents are not at home (e.g., between the hours of 9 AM to 5 PM), the security system 202 can collect audio data less (e.g., every 2 minutes for 10 seconds) frequently than time periods when residents are at home.
The audible notification may include multiple parts such as an audible prompt and a voice command. The audible prompt can be a phrase that prompts the security system 202 to receive the voice command. The audible prompt can also be a series of non-word sounds such as the humming of a song. The audible notification can also include a voice command. One possible voice command can include instructions for the light socket surveillance system to contact the second party. This voice or audible command can be a phrase that is a series of commands that instruct the security system 202 for further action. For example, the voice command can be “call for help”, and the security system 202 may call a number associated with the voice command, for example, an emergency dispatch (e.g. 911) or an emergency contact (e.g. a spouse). The voice commands can be responsive to commands selected from a dictionary of defined commands or can be interpreted based on the context. For example, message, call, and phone, may be used interchangeably. Other synonyms can be determined based on a language thesaurus.
The dictionary of defined commands may be preassigned. For example, the dictionary may be static depending on the security system 202. In embodiments, the dictionary is dynamic and can incorporate new commands based on usage. For example, if a first party typically uses the command “Phone second home”, then the security system 202 can ask the first party if the first party desires to add the word “phone” to the voice command dictionary. The security system 202 can then ask whether the “phone” command is equivalent to the “call” command. Each instance of these preferences from the first party may be added to a configuration profile of the first party.
Generally, the audible notification may be various frequencies of a human voice. For example, the audible notification may include a person speaking a selected sequence of words. For example, the sequence of words, “Hi Max,” may be the audible prompt. The selected sequence of words may be predetermined upon a setup of the security system 202. The security system 202 may have various profiles selected for members of a household. The security system 202 can have selected sequences of words and voice recognition for each profile. For example, the security system 202 may be configured to detect an audible prompt from a first resident that has the word “Max”, while the audible prompt from the second resident may have the word “Jimmy”. As well, the security system 202 may be configured to respond to one name or word from any resident. For example, the first and second residents may use the phrase, “Hi Max,” which triggers the security system 202 to respond. Generally, it should be appreciated that any word or sequence of words can be used to prompt the security system 202.
As a security precaution, speaker recognition may be implemented by the security system 202. For example, the security system 202 may utilize a combination of frequency estimation, hidden Markov models, Gaussian mixture models, pattern matching algorithms, neural networks, matrix representation, vector quantization, or decision trees.
Additionally, the security system 202 may determine whether the audible notification is present. The security system 202 may have a margin of error in both the speaker identity and the speech recognition. In various implementations, the security system 202 may utilize a threshold for both the speaker identity and speech recognition. For example, if the security system 202 determines a 90% match for the word “Computer”, but only a 20% match for the identity of the speaker for the profile, and the threshold is a 60% match for identity, then the security system 202 determines that there is no audible notification. In embodiments, the audible notification can be interchangeable for different profiles. For example, the first resident may have an audible prompt of “Max” while the second resident may have an audible prompt of “Jimmy”. The first resident may use the same audible prompt as the second resident and the security system 202 may recognize the audible prompt for both.
The security system 202 may determine whether there is a secondary notification present. The secondary notification may be determined by any input, for example, auditory, visual, chemical sensing, or tactile. Thus, the secondary notification may be a hand waving motion sensed by a camera assembly 208. For example, the secondary notification can be an image of the first party reaching up at the camera or gesturing to call the second party. Various gestures may be programmed into the security system and calibrated by the first party. The secondary notification may include various smells determined by a chemical sensor (e.g., perfume to detect the presence of a particular person, or a carbon monoxide sensor to detect fire). The secondary notification may include the first party striking a wall multiple times which may cause pressure-sensitive sensor assembly of the security system 202 to read a particular pattern of the striking.
The secondary notification may also be audio-based. An audio-based notification may be different than an audible notification in that the secondary notification is not a recognized voice command or audible prompt. For example, the secondary notification can be a distress call (e.g., a groan, moan, scream, or crying). The secondary notification can also be calibrated with environmental sounds. For example, a baby crying may be vocally distinguishable from a cry for help from an adult. The security system 202 can use calibrated settings from the first party or a library of sound profiles that indicate distress. Certain words, when used in repetition, may also indicate a secondary notification such as “Help help help!” The security system 202 may store the sound profiles locally for fast access or access the sound profiles remotely.
The security system 202 can further determine whether the first party is in distress. This step may be optional depending on the configuration on the security system 202. In embodiments, a distress notification is an indication that the first party is injured and requires assistance. The distress notification can be in addition to the audible notification and may be part of the audible notification. The security system 202 may determine that a party is in distress based on elevated vital signs that typically indicates stress in humans. For example, an elevated pulse may indicate stress of a party. An elevated pulse may be monitored through an infrared camera on the security system 202 that is configured to monitor pulse rates and body temperatures. An elevated pulse may be monitored through a tracking device worn by the party. The tracking device can be configured to measure pulse rates and may sync the information over the wireless communication (e.g., Bluetooth™). Alternatively, the tracking device may be configured to communicate a medical emergency when the first party pushes a button. The tracking device may use existing wireless signals in the Industrial, Scientific, and Medical bands of frequencies (e.g., 916 Megahertz).
The security system 202 can also determine that a party is in distress based on the audio-based secondary notification. For example, if the secondary notification is a scream, which typically indicates distress, then the security system 202 can determine that the first party is in distress. The security system 202 may determine that a party is in distress based on fluctuations in the voice of the first party. For example, variations in tone or cadence of a voice may indicate distress at any point in the audible notification. In embodiments, the security system 202 may also monitor the volume, pitch, and cadence of speech in a time period before the party attempts an audible notification. As mentioned herein, the secondary notification may also indicate distress via certain words or sounds. The distress of a party may also be determined by the lack of activity. For example, if the pulse rate or blood pressure of the first party is reduced, then the security system 202 may determine the first party is distressed. Alternatively, the security system 202 may also use the camera to analyze the environment. If the party is lying face down on the floor versus a couch, then this may indicate that the party is in distress.
The security system 202 may trigger the recording of the environment as discussed further herein. In embodiments, the security system 202 may continuously record data from the security system 202 whether the first party is in distress or not. Otherwise, the security system 202 recording may be triggered by the party being in distress.
The security system 202 may use the camera to record at least one of an image and video. For instance, the detection system of the security system 202 includes the camera 208. Various implementations of the security system 202 include a camera 208 mounted on a sidewall. For example, the sidewall may include a first portion and a second portion that is rotatable with respect to the first portion and the camera 208 is coupled to the second portion. The security system 202 may determine whether the first party is located within a field of view of the camera. The security system 202, in response to detecting the audible notification and in response to determining that the first party is not located within the field of view of the camera may use the light socket surveillance system to rotate the second portion until the first party is located within the field of view of the camera. Once in the field of view of the camera, the security system 202 can use the camera 208 to record at least one of an image and video and initiate a transmission of at least one of the image and video to a remote computing device associated with the security system 202.
In response to detecting the audible notification from the first party, the security system 202 may contact a second party. The security system 202 can use various protocols to connect the first party with the second party. For example, telephone communications, cellular network communications, and Voice over IP may be utilized to connect the audio between the first party and the second party. The security system 202 may also be configured to establish both video and audio communications between the first party and the second party. The video can utilize a different communication channel than the audio channel. For example, the audio communication can occur over a wired telephone network while the video communication can occur over a wireless network that further connects to the Internet. In embodiments, communication can be performed over the Internet via data packets using various schemes (e.g., H.264 Scalable Video Coding, cloud-based video conferencing, etc.).
In some embodiments, the security system 202 may exchange the readings of the security system 202 with a second party. The detection system of the security system 202 can use the speaker and the microphone to allow the first party and the second party to audibly communicate in real-time. The second party can further ask questions to more accurately determine the status of the first party. For example, the first party and the second party can hold a conversation discussing the events of the day or the second party can inquire as to the state of well-being of the first party if the security system 202 detected distress. The second party can be notified whether the user was in distress and what secondary notifications were present.
In embodiments, the security system 202 can initiate a transmission of the noise to a remote computing device associated with the second party. Thus, the second party may also be a remote computing device. The remote computing device may be a computer that monitors various video and audio streams of the security system 202. For example, the second party may be a security monitoring company, and the remote computing device can be a server that alerts security officers via an application mobile device. The remote computing device can initiate a transmission of at least one of the image and video to a remote computing device associated with the second party. The remote computing device can further respond to image and video. For example, the remote computing device can receive the determination of distress from the security system 202 and dispatch emergency responders immediately to the home with the security system. The remote computing device may have additional capabilities beyond that of the security system 202 such as remote storage, facial recognition, and voice recognition.
The security system 202 can monitor the communication between the first party and the second party. The security system 202 may be configured to detect whether a notification is present from the second party. The notification can be either an audible notification or a secondary notification as discussed herein. If the second party is a human, such as a relative or friend of the first party, then the second party may ascertain the state of health of the first party. The security system 202 can monitor the communication for various audible notifications in order to make it easier for the second party to take actions. For example, if the first party says, “I'm having chest pain and it's difficult to breath” with a second party, then the second party can indicate a variety of audible notifications such as the voice command “Call Ambulance” in order to trigger an action. The security system 202 may initiate a variety of actions. The security system 202 can notify the emergency services, but other types of actions are contemplated. For example, the security system 202 can also notify a neighbor or security officer to inquire further.
The security system 202 can also be configured to determine an identity of a party based upon any physical attribute, any noise, or any type of device that is associated with the person of the party. For example, the security system 202 can be implemented with any type of identity recognition system, such as voice recognition, which can be used to determine the identity of the party from a noise, such as a speech, scream, etc. Embodiments may be configured to detect and determine the identity of a remote computing device (e.g. Bluetooth™). In determining the identity of a remote computing device, this may determine the identity of the person associated with the remote computing device.
The first party can adjust the permission levels to account for emergency override of audible notifications for security system 202 users without a configuration profile (e.g., an emergency contact). In embodiments, the presence of the first party may allow the second party to initiate audible notifications. In the event of a non-speaking first party, a camera can verify the identity of the first party and contact a second party on an emergency contact address list. Thus, the emergency contact address list may also be a list of permitted individuals to use voice commands. It should be appreciated that the second party can be any party described herein such as a security officer, emergency dispatch, a friend, a family member (e.g. spouse), neighbor, coworker, and the like.
FIGS. 31a-31d illustrate just one of the many examples of how the security system 202 may be used to receive an audible instruction 3102 from a user 3100. As shown in FIGS. 31a and 31b , the user 3100 may audibly speak an instruction 3102, such as “Hi Max. Turn on entryway lights and turn on TV and set it to channel 11.” The audible instruction 3102 may be received by the security system 202, at which point it may transmit commands to various appliances. For example, the deactivated television 3106 a may become activated (activated television 3106 b) through a command sent via a wireless or wired connection to the television. Accordingly, the television 3106 b may set it's input channel to channel 11, in response to the user's audible instruction 3102. As well, the deactivated light 3104 a light may become illuminated 3104 b via the command. Accordingly, the security system 202 may also deactivate the television 3106 and light 3104 as shown in FIGS. 31c and 31 d.
As shown in FIGS. 31e and 31f , the security system 202 may trigger appliances located in different places throughout the house. For example, the security system 202 may receive a second audible instruction 3108, and in response to the instruction 3108, the security system 202 may activate an appliance, such as a light on the security system 202, within the same room, such as bedroom 3112, and also another appliance, such as living room light 3110, located in a different room. In this regard, the security system 202 may be configured to control multiple appliances simultaneously, all the while the appliances may be located in the same location or different locations. As long as the appliances are communicatively coupled to the security system 202, then the appliance can be located anywhere.
With reference to FIGS. 32a and 32b , the security system 202 a may be located within an enclosed interior portion 3210 or along an exterior portion of the building 3212. In this manner, the security system 202 may trigger appliances 3202, 3204 located within the interior portion 3210 or exterior portion of the building 3212. As well, the security system 202 itself may be located within the interior portion of the building 300 or along the exterior portion of the building 300. Generally, and regardless of where the security system 202 is located, the security system 202 may be configured to simultaneously trigger appliances located inside the building, while also triggering other appliances located outside of the building 300.
With reference to FIGS. 33a and 33b , the security system 202 may transmit commands to any of the appliances 3300 a, 3300 b via a wireless 230 or wired connection 304. For example, the security system 202 may use its communication module 262 to wirelessly 230 transmit the command to the selected appliance via one of Wi-Fi, Bluetooth, radio frequency, Near Field Communication, infrared, and any other wireless technology discussed in this disclosure.
As shown in FIG. 33b , security system 202 may use its communication module 262 to transmit the command to the appliance 3300 a, 3300 b via a wire 304 that is electrically and communicatively coupled to the security system 202. For example, the wired connection may comprise a copper wire located within the building 300. The copper wire may any type of traditional copper used for conducting electricity and WiFi throughout a building 300. However, it should be appreciated that the wired communication any type of wired technology as described in this disclosure, such as Ethernet, telephone, and the like.
Embodiments of the light socket surveillance system 202 can be used to determine how many visitors are present within a vicinity of the light socket surveillance system. In doing so, the light socket surveillance system 202 can make various determinations such as whether a party is occurring. For example, in response to the light socket surveillance system 202 determining that the party is occurring, a guardian may thereby receive an alert as to whether a predetermined number of visitors has been met or exceeded within the vicinity.
By determining the number of visitors present within a vicinity, the light socket surveillance system 202 can be used to assess threats such as how many perpetrators are present within the vicinity, as well as how many hostages are present within the vicinity. This information can be particular useful to police or military personnel to effectively assess threat levels.
The light socket surveillance system 202 can be located in any suitable location to thereby detect a number of visitors. In some embodiments the light socket surveillance system 202 can be located inside a home of a homeowner. Accordingly, the particular vicinity that the light socket surveillance 202 can monitor may be a room located inside the home. As well, the light socket surveillance system 202 can be located outside a home of a homeowner, and the vicinity can be an area of an outer premise where the home is located. Generally, it should be appreciated that the light socket surveillance system 202 can be located in any location whereby it would be useful to determine a number of visitors in a location.
The light socket surveillance system 202 can also determine an identity of any of the visitors located within a vicinity of the light socket surveillance system 202. In order to determine the identity of any of the visitors, the light socket surveillance system 202 can be implemented with facial recognition or any technology capable of determining visitor identity.
The light socket surveillance system 202 may also initiate a communication session with a remote computing device. The communication session can comprise any variety of information, such as the number of visitors located within the vicinity, the identity of any of the visitors, whether a party is occurring, etc. The remote computing device can be operated by a homeowner, a resident of the home, a guardian of a resident of the home, a neighbor, and the like.
The light socket surveillance system 202 can also be implemented with an infrared camera that can detect an infrared signature of a visitor. This can be useful if the vicinity is not adequately lit. The light socket surveillance system 202 can determine the presence of unique infrared signatures, which can indicate the number of visitors present within the vicinity of the light socket surveillance system 202.
1. A method for using a light socket surveillance system to enable a first party to communicate with a second party, wherein the light socket surveillance system includes an outer housing defining a proximal end, a distal end that is opposite the proximal end, and a sidewall that extends between the proximal end and the distal end, wherein the light socket surveillance system includes a detection system having a camera, a speaker, and a microphone, and wherein the light socket surveillance system includes a screw thread contact located adjacent the proximal end of the outer housing, the method comprising:
detecting, via the microphone, an audible notification from the first party; and
in response to detecting the audible notification from the first party, initiating a communication session with a remote computing device of the second party.
2. The method of claim 1, wherein the audible notification comprises a voice command instructing the light socket surveillance system to contact the second party, the method further comprising enabling, via the speaker and the microphone, the first party and the second party to audibly communicate with each other.
3. The method of claim 1, wherein the audible notification comprises a distress notification indicating that the first party requires assistance, and wherein the communication session comprises an indication of the distress notification.
recording a noise with the microphone;
recording an image with the camera; and
initiating a communication session with the remote computing device of the second party, wherein the communication session comprises an indication of at least one of the noise and image.
5. The method of claim 4, wherein the sidewall comprises a first portion and a second portion that is rotatable with respect to the first portion, wherein the camera is coupled to the second portion, the method further comprising:
determining whether the first party is located within a field of view of the camera;
in response to detecting the audible notification and in response to determining that the first party is not located within the field of view of the camera, automatically rotating the second portion until the first party is located within the field of view of the camera; and
in response to determining that the first party is located within the field of view of the camera, recording the image with the camera.
6. A method for using a light socket surveillance system comprising an outer housing defining a proximal end, a distal end that is opposite the proximal end, and a sidewall that extends between the proximal end and the distal end, wherein the light socket surveillance system includes a detection system having a camera, a speaker, and a microphone, and wherein the light socket surveillance system includes a screw thread contact located adjacent the proximal end of the outer housing, the method comprising:
detecting an indication suggestive of a visitor's presence; and
in response to detecting the indication suggestive of the visitor's presence, determining a number of visitors present within a vicinity of the light socket surveillance system.
7. The method of claim 6, wherein the light socket surveillance system is located inside a home of a homeowner, and wherein the vicinity is a room located inside the home.
8. The method of claim 6, further comprising wherein the light socket surveillance system is located outside a home of a homeowner, and wherein the vicinity is an area of an outer premise where the home is located.
9. The method of claim 6, wherein detecting an indication suggestive of a visitor's presence comprises detecting an infrared signature of the visitor, wherein the light socket surveillance system comprises an infrared camera, and wherein detecting the infrared signature of the visitor comprises detecting the infrared signature of the visitor with the infrared camera.
10. The method of claim 6, wherein in response to detecting the indication suggestive of the visitor's presence, the method further comprising:
recording, by the camera, at least one of a video and image of the visitor; and
initiating a communication session with a remote computing device, wherein the communication session comprises at least one of the video and image of the visitor.
11. The method of claim 10, further comprising determining an identity of a first visitor.
12. The method of claim 11, further comprising determining an identity of a second visitor.
13. The method of claim 12, further comprising initiating a communication session with a remote computing device, wherein the communication session comprises the identity of the first visitor and the identity of the second visitor.
14. The method of claim 13, wherein the communication session comprises the number visitors present within the vicinity of the light socket surveillance system.
15. The method of claim 14, wherein the remote computing device is operated by a party associated with a building in which the light socket surveillance system is coupled.
16. A light socket surveillance system, comprising:
an outer housing defining a proximal end, a distal end that is opposite the proximal end, and a sidewall that extends between the proximal end and the distal end;
a screw thread contact coupled to the proximal end of the outer housing, wherein the screw thread contact is rotatably attached to a light socket; and
a detection system coupled to the outer housing, wherein the detection system comprises a camera configurable to record images, a speaker configurable to emit noise, and a microphone configurable to detect sound.
17. The light socket surveillance system of claim 16, wherein the outer housing comprises a first outer housing and a second outer housing rotatable with respect to the first outer housing, and wherein the detection system is coupled to the second outer housing such that the detection system is rotatable with respect to the first outer housing.
18. The light socket surveillance system of claim 16, further comprising a motion detector coupled to the outer housing, wherein the motion detector is configured to detect an indication suggestive of a visitor's presence.
19. The light socket surveillance system of claim 16, wherein the light socket surveillance system is configurable to determine an identity of a visitor based upon the second noise as detected by the microphone.
20. The light socket surveillance system of claim 16, wherein the light socket surveillance system is configurable to detect a presence of a remote computing device, and wherein the light socket surveillance system is configured to determine an identity of a visitor associated with the remote computing device.
US15060282 2013-07-26 2016-03-03 Light socket surveillance systems Pending US20160261824A1 (en)
US201562129816 true 2015-03-07 2015-03-07
US14849513 Continuation-In-Part US20160134826A1 (en) 2013-07-26 2015-09-09 Light socket cameras
US15608825 Continuation-In-Part US20170263067A1 (en) 2013-07-26 2017-05-30 Smart lock systems and methods
US14861613 Continuation-In-Part US10044519B2 (en) 2013-07-26 2015-09-22 Doorbell communication systems and methods
US20160261824A1 true true US20160261824A1 (en) 2016-09-08
ID=56851127
US15060282 Pending US20160261824A1 (en) 2013-07-26 2016-03-03 Light socket surveillance systems
US (1) US20160261824A1 (en)