+

WO2018106437A2 - Surveillance de rue - Google Patents

Surveillance de rue Download PDF

Info

Publication number
WO2018106437A2
WO2018106437A2 PCT/US2017/062620 US2017062620W WO2018106437A2 WO 2018106437 A2 WO2018106437 A2 WO 2018106437A2 US 2017062620 W US2017062620 W US 2017062620W WO 2018106437 A2 WO2018106437 A2 WO 2018106437A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
request
location
examples
house
Prior art date
Application number
PCT/US2017/062620
Other languages
English (en)
Other versions
WO2018106437A3 (fr
Inventor
Clint Huson Gordon-Carroll
Jungtaik Hwang
Alen Peacock
Douglas Barnett
Casey Baugh
Foster Watabe
Bryant Robertson
Original Assignee
Vivint, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/371,004 external-priority patent/US10522013B2/en
Application filed by Vivint, Inc. filed Critical Vivint, Inc.
Publication of WO2018106437A2 publication Critical patent/WO2018106437A2/fr
Publication of WO2018106437A3 publication Critical patent/WO2018106437A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/70—Information retrieval; Database structures therefor; File system structures therefor of video data
    • G06F16/78—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B13/00—Burglar, theft or intruder alarms
    • G08B13/18—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength
    • G08B13/189—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems
    • G08B13/194—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems
    • G08B13/196—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems using television cameras
    • G08B13/19678—User interface
    • G08B13/19682—Graphic User Interface [GUI] presenting system data to the user, e.g. information on a screen helping a user interacting with an alarm system
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B13/00—Burglar, theft or intruder alarms
    • G08B13/18—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength
    • G08B13/189—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems
    • G08B13/194—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems
    • G08B13/196—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems using television cameras
    • G08B13/19678—User interface
    • G08B13/19684—Portable terminal, e.g. mobile phone, used for viewing video remotely
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/01—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium
    • G08B25/08—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium using communication transmission lines
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/01—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium
    • G08B25/10—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium using wireless transmission systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal

Definitions

  • the present disclosure for example, relates to security and/or automation systems, and more particularly to networked security cameras and related automation.
  • Security and automation systems are widely deployed to provide various types of communication and functional features such as monitoring, communication, notification, and/or others. These systems may be capable of supporting communication with a user through a communication connection or a system management action. Some automated systems may be programmed to enable security cameras to send data to or receive data from a device linked in a network.
  • Multiple audio or video devices such as security cameras may be networked together to receive and transmit data related to the location and/or the association of the devices.
  • the network of devices may be created and maintained based on a predetermined proximity of the devices or a device to a location, such as devices associated with a house or houses in a neighborhood.
  • the network of devices may be based on each device's association with a group, such as a community network, or a group of devices running the same software application.
  • the devices may obtain and receive data related to the presence of people and/or objects or occurrence of events, obtain and receive data related to identifying the people, objects, and/or events, and make a determination as to whether an action should be taken.
  • the action may be an action related to user preferences at a home and the action may be a security action.
  • one device in a networked group may share the data, request data, and request initiation of actions with and to other devices in the networked group.
  • a first device may transmit a request for data from a second device.
  • the request for data may also include an inquiry related to presence of people and/or objects or occurrence of events and a category associated with the request.
  • the second device may obtain data related to the presence of people and/or objects or occurrence of events, based on the category associated with the request, and make a determination as to whether an action should be taken.
  • the action may be an action related to user preferences related to automated transmission of the obtained data and the action may be a security action.
  • one device in a networked group may share the data, request additional data, and request initiation of actions with and to other devices in the networked group.
  • the system and method may include receiving, from a first device at a first location, a request to access data associated with a time period from a second device at a second location, the data comprising at least one of audio data, visual data, or a combination thereof, receiving, from the first device, a category associated with the request, identifying a first set of data associated with the time period, the identified first set of data based at least in part on the request and the category, and/or automatically transmitting the first set of data to the first device based at least in part on the category.
  • the second device comprises a camera.
  • the system and method may further include obtaining from a third device, the data associated with the time period at the second device, wherein identifying the first set of data is based at least in part on the data obtained from the third device.
  • the method may include obtaining the data from a database associated with a pre-determined group of devices.
  • the system and method may include determining that the first device and the second device are part of the pre-determined group of devices operating in a network, wherein transmitting the first set of data is based at least in part on the
  • the pre-determined group of devices comprise a plurality of cameras.
  • the system and method may include defining the pre-determined group of devices based at least in part on a geographic proximity of each of the pre- determined group of devices to the first location, or the second location, or both, wherein the first location and the second location are in different physical structures.
  • the system and method may include receiving, from the first device, an inquiry associated with an object, or a person, or both and/or confirming an identity of the object, the person, or both based at least in part on the first set of data and the inquiry.
  • the system and method may include determining that the category satisfies a pre-determined threshold associated with the second device. In some examples, the system and method may include receiving a notification indicating the category based at least in part on the determination.
  • the pre-determined threshold is defined by a user associated with the second device.
  • the automatically transmitting the first set of data to the first device is based at least in part on the determination.
  • the system and method may include transmitting an instruction to adjust a first security action at the first location based at least in part on the first set of data and/or adjusting a second security action at the second location based at least in part on the first set of data.
  • the system and method may include determining that a first device at a first location and a second device at a second location are part of a pre-determined group of devices operating in a network, creating, at the first device, a request to access data associated with a time period, the data being captured by the second device, and the data comprising at least one of audio data, visual data, or a combination thereof, identifying a category associated with the request, and/or transmitting the request and the category associated with the request to the second device.
  • the system and method may include obtaining data from a first sensor at a first location, receiving identification data related to a person or an event at the first location, comparing the obtained data with the identification data, adjusting a first security action at the first location based at least in part on comparing the received data with the obtained data, and/or transmitting information to a second sensor at a second location different from the first location based at least in part on the determining, the second sensor being part of a predetermined group of devices.
  • the system and method may include detecting an event at the first location based on the obtained data, the received identification data, or both, classifying the event at the first location based on the detecting, and/or sending a request to a second device at the second location based at least in part on the classification.
  • the method may include determining an indication of occupancy at the first location and adjusting the first security action based on the indication of occupancy.
  • the system and method may include transmitting a first request to a device at the second location to determine an indication of occupancy at the second location, and/or transmitting a second request to adjust a second security action at the second location based at least in part on the determined indication of occupancy at the second location.
  • adjusting may include sending a request to a device at the second location to obtain data, sending a command to adjust a second security action at the second location based at least in part on the comparing at the first location, and/or adjusting the first security action at the first location based at least in part on a user profile associated with the first location.
  • system and method may include transmitting an instruction to variably adjust a second security action at the second location based at least in part on the adjustment of the first security action at the first location.
  • the transmitted information may include transmitting an instruction to variably adjust a second security action at the second location based at least in part on a user profile associated with the second location.
  • the system and method may include receiving identification data from a remote source, and determining an identity of the person based at least in part on the received identification data from the remote source and the comparing.
  • receiving data may include receiving identification data from a database associated with the predetermined group.
  • the method may include identifying the predetermined group of devices based on a user input.
  • system and method may include defining the predetermined group of devices based at least in part on a geographic proximity of the first location to the second location, wherein the first location and the second location are in different physical structures.
  • adjusting the first security action includes increasing a frequency of obtaining audio data or visual data, activating an internal light, or an external light, or an internal audio source, or an external audio source, or a lock, or some combination thereof.
  • the system and method may include sending an alert to a user device associated with the first location based at least in part on the received data, receiving an indication from the user based on the sent alert, and adjusting a security action at the first location based at least in part on the received indication.
  • FIG. 1 shows a block diagram relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2A shows a block diagram relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2B shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2C shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2D shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2E shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2F shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2G shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2H shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 21 shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 2 J shows an exemplary user interface relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 3A shows a communication flow diagram between multiple devices relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 3B shows a communication flow diagram between multiple devices relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 4 shows a block diagram relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 5 shows a block diagram relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 6 shows a block diagram of an apparatus relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 7 is a flow chart illustrating an example of a method relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 8 is a flow chart illustrating an example of a method relating to a security and/or an automation system, in accordance with various aspects of this disclosure
  • FIG. 9 is a flow chart illustrating an example of a method relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • FIG. 10 is a flow chart illustrating an example of a method relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • FIG. 11 is a flow chart illustrating an example of a method relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • the systems and methods described herein relate generally to receiving and transmitted identification and event data at an audio/video device, such as a security camera.
  • the identification and event data may be transmitted in response to a received request.
  • the identification and/or event data may be requested from a first member of a community networking group by a second member of the community networking group.
  • the device may be wirelessly networked with other devices within a predetermined distance or at a predetermined location.
  • the devices may be wirelessly networked with other devices that have opted-into the community networking group.
  • the members of the community networking group may be customers of the same security and automation solution provider.
  • the members of the community networking group may be customers of two or more different security and automation solution providers.
  • the devices may send commands to other devices to take an action, send an alert, perform other operations.
  • two or more security cameras may be associated with two or more locations, respectively.
  • One camera at one location may obtain and receive data related to identification of people, objects, and/or events occurring at or near the location.
  • the camera may be configured to automatically take snapshots upon detecting events at or near the location.
  • the first camera may share information, request information, take an action at the first location, and/or request or initiate an action at the second location.
  • a user associated with the first camera may review the data prior to sending it to a second camera.
  • the second camera at the second location may be configured to request for audio/video data (i.e. , data related to identification of people, objects, and/or events occurring at or near the location of the first camera) for a specified time period.
  • audio/video data i.e. , data related to identification of people, objects, and/or events occurring at or near the location of the first camera
  • a user associated with the second camera may also indicate a category of urgency.
  • the category of urgency may, in some examples, be an indication of a level of urgency of the request.
  • Information obtained may be analyzed to determine if a person, object, and/or event requires an alert and/or an action with regard to at least one of the locations.
  • FIG. 1 is an example of a communications system 100 in accordance with various aspects of the disclosure.
  • the communications system 100 may include one or more sensor units 110, local computing devices 115 and 120, network 125, server 155, control panel 135, and remote computing device 140, among other components.
  • One or more sensor units 110 may communicate via wired or wireless communication links 145 with one or more of the local computing devices 115 and 120, or network 125.
  • the network 125 may communicate via wired or wireless communication links 145 with the control panel 135 and the remote computing device 140 via server 155.
  • the network 125 may be integrated with any one of the local computing devices 115 and 120, server 155, or remote computing device 140, such that separate components are not required.
  • Local computing devices 115 and 120 and remote computing device 140 may be custom computing entities configured to interact with sensor units 110 via network 125, and in some examples, via server 155.
  • local computing devices 115 and 120 and remote computing device 140 may be general purpose computing entities such as a personal computing device, for example, a desktop computer, a laptop computer, a netbook, a tablet personal computer (PC), a control panel, an indicator panel, a multi-site dashboard, an iPod®, an iPad®, a smart phone, a smart watch, a fitness tracker, a mobile phone, a personal digital assistant (PDA), and/or any other suitable device operable to send and receive signals, store and retrieve data, and/or execute modules.
  • local computing devices 115 and 120 and/or remote computing device 140 may comprise or be coupled to internal and/or external sensors which are enabled to sense and capture data similar to or in the same manner as sensor units 110.
  • Control panel 135 may be a smart home system panel, for example, an interactive panel permanently or removably mounted on a wall in a user's home. Control panel 135 may be in direct communication via wired or wireless communication links 145 with the one or more sensor units 110, or may receive sensor data from the one or more sensor units 110 via local computing devices 115 and 120 and network 125, or may receive data via remote computing device 140, server 155, and network 125.
  • the local computing devices 115 and 120 may include memory, a processor, an output, a data input and a communication module.
  • the processor may be a general purpose processor, a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), and/or the like.
  • the processor may be configured to retrieve data from and/or write data to the memory.
  • the memory may be, for example, a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, a hard disk, a floppy disk, cloud storage, and/or so forth.
  • the local computing devices 115 and 120 may include one or more hardware-based modules (e.g. , DSP, FPGA, ASIC) and/or software-based modules (e.g.
  • the processor of the local computing devices 115 and 120 may be operable to control operation of the output of the local computing devices 115 and 120.
  • the output may be a television, a liquid crystal display (LCD) monitor, a cathode ray tube (CRT) monitor, speaker, tactile output device, and/or the like.
  • the output may be an integral component of the local computing devices 115 and 120. Similarly stated, the output may be directly coupled to the processor.
  • the output may be the integral display of a tablet and/or smart phone.
  • an output module may include, for example, a High Definition Multimedia InterfaceTM (HDMI) connector, a Video Graphics Array (VGA) connector, a Universal Serial BusTM (USB) connector, a tip, ring, sleeve (TRS) connector, and/or any other suitable connector operable to couple the local computing devices 115 and 120 to the output.
  • HDMI High Definition Multimedia Interface
  • VGA Video Graphics Array
  • USB Universal Serial BusTM
  • TRS sleeve
  • the remote computing device 140 may be a computing entity operable to enable a remote user to monitor the output of the sensor units 110.
  • the remote computing device 140 may be functionally and/or structurally similar to the local computing devices 115 and 120 and may be operable to receive data streams from and/or send signals to at least one of the sensor units 110 via the network 125.
  • the network 125 may be the Internet, an intranet, a personal area network, a local area network (LAN), a wide area network (WAN), a virtual network, a telecommunications network implemented as a wired network and/or wireless network, etc.
  • the remote computing device 140 may receive and/or send signals over the network 125 via wireless communication links 145 and server 155.
  • the one or more sensor units 110 may be sensors configured to conduct periodic, continuous, conditional, or otherwise ongoing automatic measurements related to determining the presence of at least one person in or at a location and/or determining data related to identifying the person determined to be present in the location.
  • the sensors may be configured to conduct periodic, continuous, conditional, or otherwise ongoing automatic measurements related to determining the occurrence of an event or a condition within a predetermined distance of the location or at the location. For example, the sensors may determine if a car is speeding by on the street in front of a home, if a person has entered into a house, if items are being removed from a house, etc.
  • Sensor units 110 may include or relate to, but are not limited to: proximity, motion, temperatures, humidity, sound level, smoke, structural features (e.g., glass breaking, door opening and/or closing, window opening and/or closing, window position, door position), time, geo-location data of a user and/or a device, distance, biometrics, weight, speed, direction, gait, height, size, preferences, light, darkness, weather, time, system performance, the status and/or the usage of an electronic device and/or a building feature, and/or other inputs that relate to a security and/or an automation system and/or an occupant of an area and/or a structure, such as a home.
  • structural features e.g., glass breaking, door opening and/or closing, window opening and/or closing, window position, door position
  • time geo-location data of a user and/or a device
  • distance biometrics
  • weight weight, speed, direction, gait, height, size
  • preferences light, darkness, weather, time, system performance
  • Each sensor unit 110 may be capable of sensing one or more environmental parameters, or alternatively, separate sensor units 110 may monitor separate environmental parameters.
  • one sensor unit 110 may measure ambient light level, while another sensor unit 110 (or, in some examples, the same sensor unit 110) may detect motion of an occupant. Such detecting motion may in some examples occur in relative darkness and/or involve wavelengths within and/or beyond those detectable by the human vision (e.g., near- infrared illumination, microwave radiation, ultrasonic waves, passive infrared radiation, tomographic motion).
  • One sensor unit 110 example may be a camera.
  • one or more sensor units 110 may additionally monitor alternate environmental parameters, such as the voice of an occupant.
  • Each sensor unit 110 may be capable of sensing multiple identification and/or event identifying parameters, or different sensor units 110 may be capable of sensing a specific identification and/or event parameter.
  • one sensor unit 110 may measure biometric data, while another sensor unit 110 (or, in some examples, the same sensor unit 110) may detect digital and/or electronic data, a physical characteristic of the person, or a location of a different person.
  • one or more sensor units 110 may additionally capture a snapshot upon sensing a specific identification of an event parameter (e.g., detect a motion, facial recognition).
  • one or more sensor units 110 may additionally monitor alternate environmental parameters, such as the date, time, and/or weather.
  • a user may input identification data directly at the local computing devices 115 and/or 120 or at remote computing device 140, such as an allowed and/or expected user entering or exiting a building associated with the networked devices.
  • Data gathered by the one or more sensor units 110 may be received by local computing devices 115 and 120, which may be, in some examples, a thermostat or other wall- mounted input/output smart home display.
  • local computing devices 115 and 120 may be a personal computer or portable electronic device such as a smart phone, tablet, and/or smartwatch.
  • the local computing devices 115 and 120 may process the data received from the one or more sensor units 110 to obtain presence data, identification data, and/or event data and to determine whether to store and/or share (e.g., with other networked devices or a third-party source) the data, respond to a request from a user, alert a user, and/or take an action in response to obtaining the data or otherwise receiving data related to presence, identification, and/or an event.
  • remote computing device 140 may process the data received from the one or more sensor units 110, via network 125 and server 155, to obtain presence, identification and/or event data. Data transmission may occur via, for example, frequencies appropriate for a personal area network (such as
  • BLUETOOTH® or IR communications or local or wide area network frequencies such as, but not limited to, radio frequencies specified by the IEEE 802.15.4 standard.
  • local computing devices 115 and 120 may communicate with remote computing device 140 or control panel 135 via network 125 and server 155.
  • networks 125 include cloud networks, local area networks (LAN), wide area networks (WAN), virtual private networks (VPN), wireless networks (using 802.11, for example), and/or cellular networks (using 3G and/or LTE, for example), etc.
  • the network 125 may include the Internet.
  • a user may access the functions of local computing devices 115 and/or 120 from remote computing device 140.
  • remote computing device 140 may include a mobile application that interfaces with one or more functions of local computing devices 115 and/or 120.
  • remote computing device 140 may be a personal computer (e.g.
  • remote computing device 140 may be a computing device associated with a business, public service, and/or database such as a news source, law enforcement, hospitals, schools, traffic cameras, Amber Alerts, criminal databases, etc.
  • the server 155 may be configured to communicate with the sensor units 110, the local computing devices 115 and 120, the remote computing device 140 and control panel 135. The server 155 may perform additional processing on signals received from the sensor units 110 or local computing devices 115 and 120, or may simply forward the received information to the remote computing device 140 and control panel 135.
  • Server 155 may be a computing device operable to receive data streams (e.g., from sensor units 110 and/or local computing devices 115 and 120 or remote computing device 140), store and/or process data, and/or transmit data and/or data summaries (e.g. , to remote computing device 140). For example, server 155 may receive a transmission of or a stream of identification data from any of a number of sensor units 110. In some examples, server 155 may "pull" the data, e.g., by querying the sensor units 110, the local computing devices 115 and 120, and/or the control panel 135. In some examples, the data may be "pushed" from the sensor units 1 10 and/or the local computing devices 115 and 120 to the server 155.
  • data streams e.g., from sensor units 110 and/or local computing devices 115 and 120 or remote computing device 140
  • server 155 may receive a transmission of or a stream of identification data from any of a number of sensor units 110.
  • server 155 may "pull" the data,
  • the sensor units 1 10 and/or the local computing devices 1 15 and 120 may be configured to transmit data as it is generated by or entered into that device.
  • the sensor units 1 10 and/or the local computing devices 115 and 120 may periodically transmit data (e.g. , as a block of data or as one or more data points).
  • the server 155 may include a database (e.g. , in memory) containing identification data received from the sensor units 110 and/or the local computing devices 1 15 and 120.
  • the database may also contain a log of events related to the sensor units 110 (e.g., door events, window events).
  • software e.g. , stored in memory
  • Such software may be operable to cause the server 155 to monitor, process, summarize, present, and/or send a signal associated with resource usage data.
  • sensor units 110 may be associated with at least two networked locations; for example, sensor units 1 10 may be security cameras located at a first house and a second house.
  • the sensor units 110 may, respectively, be in wireless communication with a control panel and local computing devices located at the first house and/or the second house, where the control panels and computing devices of each house are in communication with each other.
  • Remote computing device may be a computing device associated with law enforcement, a news source, or other information source from which sensor units 110 and local computing devices 1 15 and/or 120 may receive identification information. Based at least in part on what data the sensor units 1 10 obtain at the houses and the data received from other elements of the wireless communication system, actions at least one of the locations may be adjusted or initiated.
  • FIGs. 2A-2J show block diagrams relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • FIG. 2A shows an example residential neighborhood 200 having eight houses 210, 215, 220, 225, 230, 235, 240 and 245.
  • FIG. 2A shows an example residential neighborhood with houses located within a geographic area of one another, it should be understood that neighborhood 200 may be a residential area, a commercial area, a rural area, and/or a mixed use area.
  • the houses 210-245 may be any type of structures, and the structures need not be located next to one another, but rather may be located in different geographic locations separated by any contemplated distance (e.g.
  • any of the eight houses 210-245 may be coupled to at least one audio/video device, such as a security and/or doorbell camera in wireless communication with at least one audio/video device located at another house; however, not all the devices may be in wireless communication with each other.
  • Dotted line 205 shows a grouping of houses which are wirelessly networked to communicate with at least one other house located within the dotted line 205 by way of at least one audio/video device located at and/or associated with houses 215, 220, 225, 230, 235, 240, and/or 245.
  • the six houses that are in networked wireless communication with each other are shown to be next to one another, however, the networked houses need not be next to each other.
  • houses 215, 220, 240, and 245 may be wirelessly networked in another example.
  • any or some of the houses shown in within dotted line 205 may also be in wireless communication with a house (e.g., based on a device associated with and/or located at a house communicating with a device associated with a second house) that is not shown in FIG. 2.
  • the devices and/or houses may be part of a network based on proximity within a location; however, in other examples, the devices may be part of a network based on a specific association.
  • a community network may include a neighborhood-based social network, a social group network, an opt-in network that is not proximity based, an opt-in network that is proximity based, an automatically established network link based on location and proximity (e.g., portable electronic device running an application enters a building enabled to perform the methods described herein).
  • houses 215, 220, 225, 235, 240, and 245 may all be part of a homeowners' association, where houses 210 and 230 are not part of the same homeowners' association, even though houses 210 and 230 are located in the same neighborhood.
  • the devices and/or houses may be members of a street watch group.
  • the devices and/or houses may each be related to one or more street watch groups. The devices and/or houses may be capable of choosing members of their personal street watch group based on user input, location of potential users, geographic proximity of one or more objects to one or more objects or locations, other information, or some combination.
  • Each of the devices associated with the location of each of the houses may share any or all of the same capabilities as each other device.
  • a device associated with house 215 may be enabled to obtain data from a first sensor at house 215.
  • the sensor may be physically integrated as part of the device and/or may be in wired and/or wireless communication with the device.
  • the data obtained by the sensor may include: biometric and personal data such as fingerprints, retinal scans, facial scans, gait, height, weight, speed, cadence, hair color, hair length, presence of facial hair, tattoos, piercings, jewelry, clothing style, clothing color, voice recordings, personal identification numbers, radio frequency data related to a radio frequency identification (RFID) tag associated with a person, identification of an electronic device such as a smartphone, table, or wearable electronic device, and the like.
  • RFID radio frequency identification
  • the sensor may also obtain data related to animals, vehicles, environment, and non- tangible items, such car types, delivery vehicles, company logos, identification card data, rain, wind, sounds related to walking, running, talking, screaming, laughing, wind, glass breaking, doors opening and closing, sirens, alarms, etc. which are determined to be within a predetermined proximity of example house 215.
  • a first device may receive a request for sensor data for a specific time period from one or more other devices.
  • the first device may receive a category associated with the request. Based on the category, the first device may transmit data (e.g. , sensor data) to the second device. In some cases, the first device may automatically transmit data based on the category, such as the category meeting or exceeding a threshold (which may be based on user input, a system setting, other information, or some combination).
  • the device may also receive identification data related to a person or an event at or within a predetermined distance of example house 215.
  • the device may associate or compare the data obtained from the sensor with a plurality of user profiles associated with house 215 or past data.
  • the user profiles may be associated with other houses in the neighborhood which are in networked communication with one another.
  • the user profiles may be profiles of an allowed and/or expected users and/or guests at example house 215, or other networked houses.
  • the user profiles may be stored individually for each house and/or combined into a database for some and/or all of the networked devices. Some profiles, sensor data, determinations, comparisons, or other information may be shared with some devices with user permission or based on user preferences.
  • more profile data may be shared with more of the networked devices within the area indicated by dotted line 205.
  • a software application such as on a smartphone or a control panel
  • the software application may query the user on what, if any, information the user would like to share with the rest of the networked users.
  • Other identification data related to a person may include data received from transmissions from other devices (e.g., 220, 225, 235, 240, and/or 245).
  • other identification data related to a person may be received from remote and/or third-party databases and/or reports and/or broadcasts and/or publications. For example, identification data from a criminal database, missing child and/or persons database, newspaper articles, news broadcasts, radio broadcasts, television broadcasts, digital streaming broadcasts, and the like.
  • the device may associate the data obtained from the sensor with predetermined, pre-stored, and/or computer learning algorithmic determined elements related to one or more events.
  • the device may obtain information related to opening and closing a door, window, gate, garage door, blinds; a vehicle ignition starting, turning off, speeding, idling, swerving, crashing; weather data such as rain, wind, snow, hail; glass breaking; talking, screaming, laughing, etc., located within a predetermined distance of example house 215.
  • each device may learn the association between obtained data and/or identification data which may not have been previously predetermined or preprogrammed into the system.
  • the device may compare the data obtained with identification data received to determine if an event has occurred and/or if an identified or non-identified person is associated with the event.
  • the device may receive an inquiry related to an event and/or a person.
  • the device may device compare the data obtained with inquiry received to determine if an event has occurred and/or if a person is identified.
  • the person and/or the event may be allowed and/or expected, while in other examples, the person and/or the event may be unauthorized.
  • the person and/or event may not be able to be determined and/or identified; however, through computer learning algorithms and other input, over time, the device may be able to identify people and/or events over time.
  • the device may initiate an adjustment of an action related to the location and/or a user associated with the location.
  • the adjustment may be of a user preference (e.g. , turn on the lights, turn on music, set the thermostat to a specific temperature).
  • the adjustment may be to a security action.
  • the adjustment may be automatic (i.e., pre-programmed by a security company, law enforcement, the manufacturer), may be user-defined (i.e. , based on user preference), and/or may be dynamically adjusted and learned over time based on computer learning algorithms.
  • the device may send the obtained data, the identification data, the comparison data, data associated with the adjustment, etc., to at least one of the other devices in networked communication with the device at house 215.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface shows a map of an area proximate a user of the street watch application. This may be generated when a user signs up for a street watch program. The dots represent neighbors of the user, who are members of the street watch.
  • the user may sign up for a street watch, with his personal information (address, home phone number, social security number, mobile phone number). For example, a user may be new to a neighborhood and may be willing to be part of an existing street watch group.
  • the neighborhood may have multiple street watch groups.
  • the user may provide his address at sign up, and the security and automation provider may verify the address. Once the address is verified, the user may choose to be a member of an existing street watch group or the user may choose to create a new street watch group.
  • the user decides to create a street watch group, the user sends a request to his neighbors.
  • the request may be an introductory message and an invitation to be a member of the user's street watch group.
  • the recipient of the message could either accept the invitation or reject the invitation.
  • the first dot 202 (and other similar dots) may indicate a neighbor who has accepted the invitation and is a member of the user's personal street watch group.
  • the second dot 204 may indicate a neighbor who has not yet accepted the invitation or has been sent a request for an invitation, and is not yet in the user's personal street watch group. In some examples, the second dot 204 may also indicate a neighbor who has rejected the user's invitation and is not in the user's street watch group.
  • the user may select any member from the street watch to get more details, including various types of identifying information as shown in component 206. For example, in accordance with various aspects of the present disclosure, the user may have selected a member who is in the user's street watch group. The user may also invite some external contacts (not present on the map) using one or more pieces of identifying information in field 208 (e.g. , name, email phone).
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface describes a message thread of a member of a street watch group. This may be generated when a user selects a particular user as described with reference to FIG. 2B, among other actions.
  • the user may view details about a member 212 of the street watch group.
  • the selected member may have a message 214 sent or posted among other members of the street watch group.
  • Other members of the street watch group may choose to reply to the message 214. For example, one or more members may reply to message 214 in a message thread 216.
  • the user may remove the selected user from his street watch group or flag that the posted message is not relevant using one or more selections within menu 218. For example, if the user observes that the selected member is posting too often or is acting in a certain way, then the user may either choose to remove the person from his street watch group or flag that the message is irrelevant. In another example, if the user observes that the selected member is requesting personal information, the user may flag that the selected member may be a exhibiting suspicious behavior. This suspicious behavior may be identified by comparing one user's behavior to another, analyzing the types of information being requested by this user over time, analyzing the information being requested pertains to one or more locations, object, or people, or some combination thereof.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface described in FIG. 2D describes a map of an area related to a user of the street watch application. In some examples, this may be generated when a user is composing a request to access data (e.g. , audio data, video data, other data, a combination of different data types) from one or more users or user devices.
  • the dots and cameras represent users who are members of a street watch group.
  • the camera icon 222 may indicate a neighbor who is a member of the user's street watch group and has shared (or agreed to share upon approval) data related to one or more outdoor cameras (e.g., doorbell cameras, front porch cameras, backyard cameras).
  • the black dot 224 may indicate a neighbor who is part of the user's street watch group but has not shared their cameras (or do not have an outside camera available for sharing at the present time).
  • the shaded dot 226 may indicate a neighbor who is not a member in the user's street watch group. The user may select one or more members each with one or more shared outdoor cameras for requesting data.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated in response to user input (e.g. , a user's indication to compose a message).
  • the window 232 for composing a request may include the details 234 (e.g. , name, status, verification) of the requester (user composing the message).
  • the user interface may also indicate if the user composing the request, is a verified member of the street watch group.
  • the window 232 for composing a request may also allow the user to describe 235 an incident related to the request (or include an inquiry related to the request), select a category 236 associated with the request, request access 237 to doorbell cameras and request additional video footage 238 using one or more commands associated with one or more elements or buttons (whether physical or digital).
  • the user may describe 235 an incident related to the request.
  • the incident can be an inquiry related to an object or person or event.
  • the user composing the request may additionally select a category associated with the request.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated in response to a user's indication to compose a message.
  • the window for composing a request may include the name and details of the requester (user composing the message), a description 242 of an incident related to the request, and a category associated with the request.
  • the user may be prompted by the sensor linking module 415 to select a category.
  • a list of categories 244 may be presented to the user.
  • the list of category may include one or more phrases 246 describing a general category of the request.
  • the phrases can be vandalism, theft or missing item, other crime, lost pet, missing child and emergency.
  • the user interface may also include a visual representation 248 of each category that may be related to the request.
  • the visual representation may include a color-coded representation, a patterned representation, a numerical representation, or any other visual representation that described a level associated with the urgency of each category.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated in response to a user's indication to compose a message.
  • the window for composing a request may include the name and details of the requester (user composing the message), a description of an incident related to the request, and a category associated with the request.
  • the user may be prompted to select a time range associated with the request. For example, the user may request data (e.g. , video footage) from other members of the street watch group foo the selected time period.
  • the user composing the request may select a start time 254 and an end time 256 for the requested data.
  • the user composing the request may request video footage between 12:00 PM and 3:00 PM on May 17, 2016. After the time period selection, the user may request via element 252.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated at a receiver's user equipment (e.g. , control panel, smart phone, tablet computer, wearable device) in response to receiving a request to access one or more pieces of data.
  • the user interface described in FIG. 2H includes a notification 262 of the request message to the receiver.
  • the notification of the request message may include the sender's name, contents of the message, category associated with the message, and a visual representation of the category.
  • the user interface may also indicate if the sender of the request is a verified member of the street watch.
  • the user interface of the receiver includes an option for the receiver to view 264 the request or approve 266 the request.
  • the receiver may pre-approve requests from one or more users (e.g. , a particular trusted neighbor). In that case, the receiver or receiving device may not be notified before sending the approval, which may be automatic.
  • the receiver may have pre-approval for categories satisfying or exceeding a threshold. For example, the receiver settings may indicate approval to send requested data (e.g. , video footage) is not required from the receiver if the category associated with the request satisfies a threshold.
  • the pre-approval for categories may be based on one or more phrases, keywords, descriptions, or other information describing a general category of the request.
  • the phrases may include vandalism, theft or missing item, other crime, lost pet, missing child, help, injury, bleeding, blood, medical condition, and emergency.
  • the receiver of the request may indicate approval to send the requested data (e.g., video footage) if the phrase describing the request indicates that the request is related to a missing child or an emergency.
  • the receiver or receiving device may be notified before sending the approval.
  • the pre-approval for categories may be based on visual representations associated with the category of the request.
  • the visual representation may include a color- coded representation, a patterned representation, a numerical representation, or any other representation (e.g., a visual representation) that describes a level associated with the urgency of each category.
  • the receiver of the request may indicate pre-approval for sending the requested data (e.g., video footage), if the visual representation associated with the request indicates satisfies a threshold.
  • the receiver settings may indicate that the requested data (e.g., audio/video footage) may be automatically transmitted to the requestor, if the visual representation of the category of the request indicates that the request is related to an emergency.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated in response to a user's indication to view a received request.
  • the received request may be a request to access audio/video data from the receiver's camera for a specified time period.
  • the received request may be a request to access audio/video data from the receiver's camera without a specified time interval.
  • the window for viewing a request may include the name and details of the requester (user composing the message), a description of an incident related to the request, a category associated with the request, and a visual identifier of the category, among other information.
  • the receiver of the request may choose to allow 274 the sender to view the camera footage or deny 276 the sender to view the camera footage. Before transmitting the footage to the sender, the receiver of the request may view 272 the relevant camera footage.
  • the user interface may be generated by the sensor linking module 415, among other components or elements.
  • the user interface may be generated in response to user input (e.g. , a user's indication to view a camera footage) before sending the footage to the requester.
  • the camera footage may be associated with or based on a received request.
  • a first member of a street watch group may compose a request to access camera footage from a second member of the street watch group.
  • the recipient of the request may use the user interface to view the camera footage (e.g., audio/video footage) prior to transmitting the video to the requestor using one or more displays 282.
  • the user interface for viewing the camera footage may also include one or more elements 284 to allow the viewer to pause, play, rewind and/or replay the same video, and/or also allow to skip a current video footage and view a subsequent video footage.
  • the user interface for viewing the camera footage may also allow the viewer to take snapshots while viewing the data via one or more elements 286 and, alternatively or additionally, provide a subset of the requested data in response to the request.
  • the viewer may take a snapshot from the data 282 (e.g. , video and/or audio data) and may decide to send the snapshots to the requestor using one or more elements 289.
  • the user interface for viewing the camera footage may provide an indication that there may relevant footage outside the requested time period (e.g. , before/after the requested time period).
  • the requestor may request for camera footage between 12:00 PM and 3:00 PM on May 17, 2016, as described with reference to FIG. 2G.
  • the receiving device may determine that the request is an inquiry relating to a missing child (e.g. , the inquiry may include that the child was 5 years of age, wearing a red sweater and black jeans).
  • the receiver device may use facial recognition, among other techniques, to determine that the camera footage includes the missing child (i.e., description of the missing child in the inquiry matches the description of the child in the camera footage) at 11 :00 AM on May 17, 2016 (i.e. , prior to the requested time period).
  • the receiver device may provide an indication to the user of the receiver device, which may in some cases state that there may be relevant footage outside the requested time period .
  • the receiver device may seek approval from the user of the receiver device (via a device or otherwise) before transmitting the camera footage.
  • the receiver device may automatically transmit the relevant data to the requestor (based on pre-approval settings of the user).
  • the request may only include an inquiry related to a missing child and may not include the description associated with the missing child.
  • the receiver device may query a database to determine a description of a child associated with the requestor (e.g. , the database may include information about each family member of the requestor).
  • the receiver device may compare the description with the camera footage to determine if the camera footage includes data about the missing child associated with the requestor.
  • the receiver device may receive an inquiry and may transmit the inquiry to other devices that may be in network of the receiver device (e.g. , same
  • a second device in network of the receiver device may identify relevant footage (i.e. , camera footage relevant to the received inquiry) and may transmit the footage to the receiver device.
  • the transmission of the camera footage (e.g., audio/video footage) from the second device to the receiver device may be based on user settings associated with the second device.
  • the receiver device may transmit the footage to the requestor.
  • the receiver of the request may determine relevant portions of the data (e.g., video footage) and may only send a subset of those portions to the requestor.
  • the user interface for viewing the camera footage may also allow the viewer to view a summary or a high-level representation of the data.
  • the summary or high level representation may indicate portions 288 including important information (for example, when the camera detects human motion, identified color, identified object, other information, or some combination).
  • the receiver of the request may also send the high level representation of the video to the requestor,
  • FIG. 3A shows a communication flow diagram between multiple devices relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • house 215 and house 220 are located in the same neighborhood, and are located across the street from one another. Both house 215 and house 220 are associated with a networked group of devices that are in wireless communication with one another (e.g., as shown by the example area within dotted line 205 described with reference to FIG. 2).
  • House 215 may be associated with a security camera, such as a doorbell camera, an extemal security camera, or other monitoring device 215-a.
  • device 215-a may comprise internal sensors; however, in other examples, device 215-a may be communicatively and/or electrically coupled to extemal sensors.
  • house 220 may be associated with a device 220-a.
  • Devices 215-a and 220-a may be networked together in wireless communication— directly or indirectly.
  • both or either of device 215-a and/or device 220-a may communicate with a local and/or remote database 305.
  • device 215-a is an external camera located at house 215.
  • the device 215-a may have a wide field of view and is thus capable of capturing a wide area in front of and to the side of house 215, as well as across the streets and next door (e.g., the device 215-a may be configured to enable a 180+ degree view around the axis of the device lens).
  • device 215-a may have a full and/or partial view of at least some of the area in front of house 210, 230, 235, 240, 220, as well as the streets that intersect in the middle.
  • Device 215-a is in communication with a control panel and/or database 305.
  • Database 305 may be an example of a local database associated with house 215; for example, stored in memory on a control panel or other local computing device (e.g. , smartphone, desktop at the location, a remote server or account associated with house 215).
  • This local database may store information related to users associated with house 215 and each user's preferences. For example, there may be a father, mother, a daughter, a son, and a dog at house 215.
  • the database may store identification information about each user, including the dog, as well as information about schedules, vehicles, preferences (e.g. , lighting, sound, security levels).
  • database 305 may store identification information about frequency and/or allowed and/or expected guests (e.g. , extended family, friends, nanny, delivery people, neighbors).
  • database 305 may be a database associated with house 220, thus, device 215-a may also be in communication with a database associated with house 220, where the house 220 database stores similar information about the users associated with house 220.
  • houses 215 and 220 may have a shared database of similar information.
  • database 305 may be a remote database or a third- party database which stores and shares information related to events and identification, such as a news source, law enforcement, missing persons databases, criminal databases, emergency alert systems, weather databases, and the like.
  • device 215-a obtains data from one or more sensors located at house 215 (block 310).
  • the data obtained includes information indicating that the users of house 215 are scheduled to be out of the house based on their stored schedules (e.g. , schedule information, activity information), the dog out with the dog walker (e.g. , location information), a video of a woman approximately 5' 11" tall, dressed in black, and with blonde hair (e.g. , physical characteristics, identification information), the device has obtained the sound of glass breaking near the living room (e.g., interior environment information), and a blue car drove by slowly five minutes before the sound of glass breaking (e.g., exterior environment information).
  • schedule information e.g., schedule information, activity information
  • the dog out with the dog walker e.g. , location information
  • a video of a woman approximately 5' 11" tall, dressed in black, and with blonde hair e.g. , physical characteristics, identification information
  • the device has obtained the sound of glass breaking near the living room
  • device 215-a receives identification information from at least one of a plurality of sources.
  • the sources may be a database associated with house 215, a database associated with house 220, or a remote database 305.
  • the device 215-a queries a local database associated with device 215-a (i.e., associated with house 215) and determines that none of the allowed and/or expected users associated with house 215 are tall women with blonde hair.
  • the device may also request data (at block 315-b) from the database associated with house 220-a, as well as a shared database, and determine that none of the allowed and/or expected and/or expected visitors are tall women with blonde hair.
  • none of the associated databases indicate that any of the associated users have a blue car.
  • the device 215- a may request data (at block 315-a) from a remote database 305.
  • the remote database may automatically send out an alert and/or data to all devices enabled to receive identification and/or event data.
  • the remote database may provide the device 215-a with a news report related to a series of burglaries that have occurred within 15 miles of house 215. In addition, the police have published a picture and description of the suspect: a tall woman with blonde hair.
  • Device 215-a compares the data obtained from the sensor in block 310 to the identification data in block 315, and determine that the event occurring at house 215 is likely a burglary being committed by the suspect-at-large.
  • Device 215-a may also determine whether anyone (allowed and/or expected) is home. Determining occupancy may be performed using sensors inside and/or outside of the home that detect the presence of and identify who is located at the house. Based on whether someone is home or not, and/or based on a user preference or system settings, device 215-a may adjust an action (at block 330). If someone is determined to be home, the action may be different than if no one is determined to be home; for example, if someone is home, the device 215-a may only initiate a loud alarm to warn a user that someone unexpected or not allowed is in the home, but may not lock the doors in case the user needs to get away from the intruder.
  • house 215 may be occupied by a single man who is suspicious of any amount of detected activity or unknown visitors. The man has programmed his security systems and sensors to determine that any person and/or any vehicle which comes within a predetermined distance of his house is of the highest threat. The man at house 215 desires to be notified of every movement and every noise that is detected by device 215-a.
  • the man desires to be notified of all people coming and going at his nearby neighbors houses, and he wants to be notified of all cars driving by that do not explicitly belong to someone in the neighborhood.
  • the man's neighbors do not want to receive every single alert and action transmitted from device 215-a, lest they be inundated with alerts and security action adjustment requests.
  • the users at house 220 have set their system to receive all alerts and requests from devices at houses 225, 235, 240 and 245 as described in the previous example.
  • alerts from house 215 the users at house 220 have programmed their system to only receive alerts and requests from house 215 if the device 220-a receives the alert and/or data and determines that the threat level, alert, and/or request satisfies a predetermined threshold.
  • device 220-a may transmit an alert or take an action if the data and/or request received from device 215-a is indicative of a crime, but device 220-a may disregard an alert received from device 215-a if device 220-a determines the alert is related only to a person walking through the neighborhood that is unlikely to pose a threat.
  • device 220-a may transmit an alert or take an action if the data and/or request received from device 215-a is indicative of security alert (e.g. , a security status change, an arm or disarm event), but may not transmit an alert or take action based only on sensor data alone.
  • security alert e.g. , a security status change, an arm or disarm event
  • the actions may include predetermined settings based on the identification and/or the event.
  • the action may be programmed by or based on feedback or information relating to at least one of the users at house 215 and/or agreed upon by the networked group of users.
  • the networked group of users may collectively, separately, or each individually set a series of "threat levels," where each determined event is assigned to trigger or initiate a threat level with corresponding actions.
  • a low threat level may correspond to an allowed and/or expected guest arriving at the house or an expected delivery of a package, whereas a high threat level may be associated with identifying a prowler, a security alarm state change, or sounds associated with a crime or dangerous situation (e.g.
  • a threat level of a first home may be based on or the same as a threat level at a second home.
  • a group of devices within a predetermined proximity may elect or be automatically configured so that if a first home enters a first threat level based on sensor data or a user-initiated action, at least some or all of the devices in the group may also enter the same threat level or an elevated threat level based at least in part on the threat level of the first home.
  • This elevated threat level may trigger specified actions based on specified inputs and may be essentially more sensitive than a lower threat level (i.e. , requiring less unrecognized or abnormal input to trigger an alert or an event as compared to a lower threat level).
  • the device 215-a may send an alert to a user that something is happening at the house.
  • the alert may include information related to the data obtained from the sensor and/or the identification data.
  • the device 215-a may wait to take an action, or take a specific action, based on the user's response to the alert.
  • the device 215-a may increase the frequency of obtaining data in case more data is needed for a decision or for future reference.
  • the device 215-a may send an alert and/or data (at block 355) to device 220-a to alert the users at house 220 that a burglary is occurring within a proximity (e.g. , across the street, at house 215-a). Based on this information, the device 220-a may obtain sensor data, may receive identification data, may adjust actions, and/or may send alerts and data itself. In other examples, device 215-a may send a request to device 220-a to determine if anyone is home at house 220.
  • device 215-a may send a request to device 220-a to initiate a security action (at block 340), such as turning on a security camera at house 220 which has a view of house 215 across the street.
  • a security action such as turning on a security camera at house 220 which has a view of house 215 across the street.
  • device 215-a may obtain data from a sensor, such as data relating to or showing cars passing by, people walking by, two cars associated with the house leaving the garage, etc.
  • Device 215-a may also receive identification data related to people, vehicles, and cars associated with the neighborhood and/or networked devices.
  • device 215-a may receive an alert from device 220-a that the daughter that lives in house 220 is not at home and she is expected to be home.
  • Device 220-a may have adjusted security actions at house 220, and has sent a request to device 215-a to adjust security actions, such as increasing the frequency of capturing audio and video around the house, or querying other devices or databases for information related to the missing daughter.
  • this may allow a user associated with device 220-a to have a better chance of locating the daughter based on the additional querying and searching.
  • the databases or the information sources associated with device 215-a may be at least partially different from the databases or the information sources associated with device 220-a. Thus, by requesting that device 215-a initiate one or more actions, additional information can be gathered, compared, and evaluated within a predetermined period of time (e.g., less than one minute).
  • device 215-a obtained data that indicated the daughter was riding her bike down the street, and in fact, at the current time (or a past time), device 215-a is obtaining data indicating someone matching the daughter's description is located in the front yard of house 230. Thus, device 215-a sends an alert to device 220-a that the daughter is likely located at house 230, and thus does not adjust the security actions at house 215 based on the received data.
  • FIG. 3B shows a communication flow diagram between multiple devices relating to a security and/or an automation system, in accordance with various aspects of this disclosure.
  • house 215 and house 220 are located in the same neighborhood.
  • house 215 and house 220 are across the street from each other.
  • both house 215 and house 220 are associated with a networked group of devices that are in wireless communication with one another (e.g., as described with reference to FIG. 2).
  • House 215 may be associated with a security camera, such as a doorbell camera, an external security camera, or other monitoring device 215-b.
  • device 215-b may comprise internal sensors; in other examples, device 215-b may additionally or alternatively be communicatively and/or electrically coupled to external sensors.
  • house 220 may be associated with a device 220-b.
  • Device 215-b and device 220-b may be networked together in wireless communication— directly or indirectly.
  • both or either of device 215-b and/or device 220-b may communicate with a local and/or remote database 305-a, among other devices.
  • device 215-b is an external camera located at house 215.
  • the device 215-b may have a wide field of view (e.g., the device 215-b may be configured to enable a 180+ degree view around the axis of the device lens) and is thus capable of capturing a wide area in front of and to the side of house 215, as well as across the streets and next door.
  • device 215-b may have a full and/or partial view of at least some of the area in front of house 210, 230, 235, 240, 220, as well as the streets that intersect in the middle.
  • the device 215-b may be an external camera located at the backyard of house 215.
  • device 220-b is an external camera located at house 220.
  • the device 220-b may have a full and/or partial view of at least some of the area in front of house 210, 230, 235, 240, 220, as well as the streets that intersect in the middle.
  • the device 220-b may be an external camera located at the backyard of house 220.
  • the device 220-b may be coupled to a user device 120.
  • a user may request a video footage from device 215-b using or through device 220-b.
  • other devices could request a video footage (e.g.
  • a user of device 220-b may indicate a time period associated with the requested video footage (i.e. the user may identify the time period in the request and may request for the data (e.g. , video footage) during that time period),
  • device 215-b is in communication with a control panel located at one or more structures and/or database 305-a.
  • Database 305-a may be an example of a local database associated with house 215; for example, stored in memory on a control panel or other local computing device (e.g. , smartphone, desktop at the location, a stand-alone storage device or hard drive, a remote server or account associated with house 215).
  • This local database 305-a may be configured to store information related to users associated with houses in a neighborhood (e.g., house 215 and house 220). For example, there may be a father, mother, a daughter, a son, and a dog associated with a house (e.g. , house 215).
  • the database 305-a may store identification information about each user, including the dog, as well as information about schedules, vehicles, preferences (e.g. , lighting, sound, security levels), among other information.
  • the database 305-a may store audio/video data from devices associated with the houses (device 215-b and device 220-b).
  • the device 215-b may be configured to capture audio/video data in response to detecting motion and store the captured audio/video data in database 305-b.
  • a user associated with the device 215-b may configure the device 215-b to capture audio/video data based on one or more user preferences.
  • the user associated with the device 215-b could enter the preferences through a control panel at user location, one or more smartphones associated with the user, desktop at a location of the user, desktop at a location remote from the user, laptop at a location of the user, laptop at a location remote from the user tablet, etc.
  • the device 215-b may be configured to capture audio/video data in response to receiving a request from device 220-b, and may store the request and the data in database 305-a.
  • the device 220-b may be configured to capture audio/video data in response to receiving a request from device 215-b, and may store the request and the data in database 305-a.
  • the database 305-a may store identification information about frequency and/or allowed and/or expected guests (e.g. , extended family, friends, nanny, delivery people, neighbors).
  • the database may be configured to store identification data of neighbors of house 215 and house 220.
  • database 305-a may be a database associated with house 220, thus, device 215-b may also be in communication with a database 305-a associated with house 220, where the house 220 database stores similar information about the users associated with house 220.
  • houses 215 and 220 may have a shared database of similar information.
  • database 305-a may be a remote database or a third-party database which stores and shares information related to events and identification, such as a news source, law enforcement, missing persons databases, criminal databases, emergency alert systems, weather databases, and the like.
  • device 215-b obtains data from one or more sensors located at house 215 (block 355).
  • the data obtained may include information indicating that the users of house 215 are scheduled to be out of the house based on their stored schedules (e.g. , schedule information, activity information), the dog is not at the home and is out with the dog walker (e.g. , location information), a video of a child approximately 4' 4" tall, dressed in a red coat, and with brown hair and blue eyes (e.g., physical characteristics, identification information), and a child is riding a bike in the street in front of the house (e.g. , exterior environment information), some combination, or other information.
  • schedule information e.g. , schedule information, activity information
  • the dog is not at the home and is out with the dog walker (e.g. , location information)
  • a video of a child approximately 4' 4" tall, dressed in a red coat, and with brown hair and blue eyes e.g., physical characteristics, identification information
  • device 220-b obtains data from one or more sensors located at house 220 (not shown).
  • a device 215-b may receive instructions to obtain sensor data from a control panel at a location of device 215-b,a control panel remote from device 215-b, one or more smartphones associated with a user of device 215-b, a desktop at a location of the user of device 215-b, desktop at a location remote from device 215-b, a laptop, a tablet, etc.
  • a device 220-b may receive instructions to obtain sensor data from a control panel at a location of device 220-b,a control panel remote from device 220-b, one or more smartphones associated with a user of device 220-b, a desktop at a location of the user of device 220-b, desktop at a location remote from device 220-b, a laptop, a tablet, etc.
  • device 215-b receives request from at least one of a plurality of sources.
  • the sources may include a database associated with house 215, a database associated with house 220, a remote database 305, some combination, or other sources.
  • device 220-b receives the request from at least one of a plurality of sources, the plurality of sources including a database associated with house 215, a database associated with house 220, a remote database 305, some combination, or other sources.
  • the device 215-b receive the request at a control panel at a location of the device 215-b, one or more smartphones associated with the user of the device 215-b, desktop at a location of the device 215-b, desktop at a location remote from the device 215-b, a laptop, a tablet, etc.
  • the device 215-b queries a local database associated with device 215-b ⁇ i.e. , associated with house 215) and determines whether a child approximately 4' 4" tall, dressed in a red coat, and with brown hair and blue eyes (or a subset of these or other characteristics or related features) was seen near the house.
  • the device may also request data (at block 315-b) from the database associated with other houses, as well as a shared database, and determine whether any the cameras (or other devices, such as sensors) of any of the other houses have spotted the child approximately 4' 4" tall, dressed in a red coat, and with brown hair and blue eyes.
  • the device 215-b may request data (at block 315-a) from a remote database 305.
  • the remote database may automatically send out an alert and/or data to all devices enabled to receive identification and/or event data.
  • the remote database may provide the device 215-b with additional information (e.g. , news report) related to a series of kidnapping that have occurred in the community or within a predetermined distance of house 215.
  • device 215-b identifies or determines relevant data from the received data.
  • the sources for the data received by device 215-b may include a database associated with house 215, a database associated with house 220, a remote database 305, a combination thereof, or one or more other sources.
  • device 220-b may be configured to identify or determine relevant data from the received data, upon receiving a request for data from device 215-b.
  • the device 215-b identifies or determines relevant data at a one or more cameras (or other devices such as motion sensor, fire sensor, glass break sensor, earthquake sensor, etc.), at the control panel at a location of the device 215-b, one or more smartphones associated with the user of the device 215-b, desktop at a location of the device 215-b, desktop at a location remote from the device 215-b, a laptop, a tablet, etc.
  • the device 215-b queries a local database associated with device 215-b (i.e.
  • Device 215-b may also determine whether the child was seen anywhere within a specified geographic area (e.g. , based on the devices included in the street watch group, within a radius or a distance of one or more locations (e.g. , a location of device 215-b, a location of the last location where the child was captured on camera or detected, a location associated with the child such as his home), some combination, or other information.
  • a specified geographic area e.g. , based on the devices included in the street watch group, within a radius or a distance of one or more locations (e.g. , a location of device 215-b, a location of the last location where the child was captured on camera or detected, a location associated with the child such as his home), some combination, or other information.
  • the device 215-b queries a local database associated with other devices (i.e. , devices associated with houses in the same neighborhood watch group as house 215) and determines that a child approximately 4' 4" tall, dressed in a red coat, and with brown hair and blue eyes was seen near a particular house in the neighborhood.
  • the neighborhood watch group associated with house 215 may be different from the neighborhood watch group associated with house 220.
  • the device 215-b may be configured to query devices associated with both neighborhood watch groups.
  • device 215-b determines a category associated with the received request.
  • the category may include vandalism, theft, lost pet, missing child, other crimes, and emergency, among other examples.
  • one or more categories may be conveyed by or may include a visual representation of the category.
  • the category may be green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child missing child, and orange for emergency.
  • the device 215-b queries a local database associated with device 215-b (i.e. , associated with house 215) and determines a ranking associated with the categories.
  • Device 215-b may also determine whether the category included in the request is associated with a visual representation.
  • device 220-b may be configured to determine a category associated with the received request, upon receiving a request for data from device 215-b.
  • the device 215-b may adjust an action. Although it is shown that device 220-b adjusts an action, in some examples, device 220-b may be configured to adjust an action, upon receiving a request for data from device 215-b. In some examples, the device 215-b determine the action at a control panel at a location of the device 215-b, one or more smartphones associated with the user of the device 215-b, desktop at a location of the device 215-b, desktop at a location remote from the device 215-b, a laptop, a tablet, etc. If the device 215-b queries a local database associated with device 215-b (i.e.
  • the device 215-b may transmit the relevant data to device 220-b (at block 385).
  • device 220-b may transmit the relevant data if the data received from device 215-b is identified as being indicative of a crime, but device 220-b may disregard an alert if the data from device 215-b is related only to a person walking through the neighborhood that is not identified as a threat.
  • device 215-b may categorize data as indicative of a crime if the data (e.g. , video footage) includes footage that can be categorized as a threat.
  • the device 215-b may categorize the data as a crime based on objects (e.g., gun, knife), clothing item (e.g., masks) or people (e.g. , recognized as a criminal) identified in the footage.
  • a person walking down the street with a mask on, or a person walking down the street holding a knife may be classified as data indicative of threat.
  • the device 215-b may receive sounds related to tires screeching near house 220-b during afternoon.
  • the schedule preference for house 220-b may indicate that no member is scheduled to be home at that time of the day.
  • Device 215-b may further capture video footage of people wearing masks coming out of the car and may conclude that these footages indicate a burglary.
  • device 220-b may transmit an alert or take an action if the data and/or request received from device 215-b is identified as being indicative of a security alert (e.g., a security status change, an arm or disarm event), but may not transmit an alert or take action if the data received from device 215-b is not related to or correlated to the request 365-b received from device 220-b.
  • a security alert e.g., a security status change, an arm or disarm event
  • the device 215-b may send a request to device 220-b to initiate a security action (at block 390), such as turning on a security camera at house 220 which has a view of house 215 across the street.
  • the actions may be based on predetermined user settings.
  • the device 215-b may take an a security action based on the determined category.
  • the device 215-b may receive the user preferences from a user at a control panel at a location of the device 215-b, one or more smartphones associated with the user of the device 215-b, desktop at a location of the device 215-b, desktop at a location remote from the device 215-b, a laptop, a tablet, etc.
  • the action may be programmed by or based on feedback or information relating to at least one of the users at house 215, house 220 and/or agreed upon by the networked group of users.
  • the device 215-b may send an alert to a user that indicates that the device 215-b has retrieved data relevant to the received request.
  • the alert may include information related to the data obtained from the sensor and/or the identification data.
  • the device 215-b may wait to take an action, or take a specific action, based on the user's response to the alert.
  • the device 215-b may increase the frequency of obtaining data in case more data is needed for a decision or for future reference.
  • the device 215-b may automatically capture screenshots every motion is detected by device 215-b, a sensor, or another device (or when a device receives data from any other sensor at house 215).
  • the device 215-b may capture video footage from a camera upon detecting motion and may continue capturing the video for a threshold time period, after the motion has ceased to occur.
  • a control panel at requestor location a control panel at location associated with the receiver of the request, one or more smartphones associated with the requestor, one or more smartphones associated with the receiver, a desktop associated with the requestor, a desktop associated with the receiver, a laptop associated with the requestor, a laptop associated with the receiver, a tablet associated with the requestor, a tablet associated with the receiver, a smartwatch associated with the requestor, a smartwatch associated with the receiver etc.
  • FIG. 4 shows a block diagram 400 of a device 405 for use in wireless communication, in accordance with various examples.
  • the device 405 may be an example of one or more aspects of a control panel 105 described with reference to FIG. 1. It may also be an example of a sensor unit 110, local computing device 115 or 120, remote computing device 140 described with reference to FIG. 1.
  • sensor unit 110 may be a camera enabled to capture video and/or audio, in addition to other data as described previously.
  • device 405 may be an example device located at one of the example houses described with reference to FIG. 2.
  • the device 405 may include a receiver 410, a sensor linking module 415, and/or a transmitter 420.
  • the device 405 may also include a processor. Each of these components may be in communication with each other— directly and/or indirectly.
  • the components of device 405 may, individually or collectively, be implemented using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In other examples, other types of integrated circuits may be used (e.g. , Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art.
  • the functions of each module may also be implemented— in whole or in part— with instructions embodied in memory formatted to be executed by one or more general and/or application-specific processors.
  • the receiver 410 may receive information such as packets, user data, and/or control information associated with various information channels (e.g., control channels, data channels).
  • the receiver 410 may be configured to receive data from sensor units 110, a local computing device 115 or 120, a remote computing device 140, a server 155, a third-party database, one or more components of communication system 100, as well as data relating to a request from a user, time period associated with the received request, categories associated with the received request, the data related to user preferences related to the categories of the request, the identification of a person and/or an event, actions based on identification and/or user preferences, user profiles, data relating to home conditions and/or building features, data relating to environmental and geographic parameters and events, some combination, and/or other data and/or information.
  • information may be passed to the sensor linking module 415.
  • the sensor linking module 415 may be enabled to associate one device with at least one additional device in networked wireless communication.
  • the devices may be linked based on a predetermined proximity, such as within a predetermined distance, geofenced area, neighborhood, subdivision, city block, city, county, state, street, association, etc.
  • the devices may be automatically and initially linked based on automatic linking, but may be able to opt-out. For example, all houses which are located within a homeowners' association may be automatically networked.
  • the devices may be linked based on opting-in (e.g. , street watch, houses having a specific type of security system).
  • the devices may be linked based on an association, such as an interest group (e.g. , a book club), a community group (e.g., home owner association, school organization), or social network (e.g., Facebook, Twitter).
  • the devices may be linked based on user input (e.g., the user may add one or more contacts to an existing street watch group or the user may create a new street watch group with one or more contacts)
  • the devices may be linked based on user selection of specific devices; for example, from a list of possible devices, a user may select which of the devices will receive data from the device at house 215 and/or which device will send data to the device at house 215.
  • the devices the user selects may be different based on the current situation; for example, in an emergency situation (e.g.
  • the sensor linking module 415 may receive a request at house 215 from house 220, and may be configured to identify a category associated with the request.
  • the sensor linking module 415 may be configured to classify the request as "emergency" based on the category (e.g., if the request is categorized as missing child then the request is classified as emergency).
  • the category may be color coded differently for different situations (e.g., green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child missing child and orange for emergency).
  • the sensor linking module 415 may be configured to receive input from a user regarding which categories to identify as emergency. In a non-emergency situation, however, only the house making the request, may be selected to receive data; for example, the device at 215 may receive a request from the device at 220, for theft of a delivery item. In response to the request, the device at house 215 may recognize a delivery truck has dropped off a package at 215 instead of 220, and the device at house 215 sends a notification to the networked devices associated with 220 which have indicated house 215 mistakenly received the delivery item. In some examples, the device at house 215 may receive a request from the device at 220 and may identify a category associated with the request.
  • the device at 220 may request for a lost puppy and the category associated with it may be color coded to indicate that there is a lost pet.
  • the device at house 220 may include description of the lost puppy.
  • the device at house 215 may recognize that the lost puppy was seen near the front porch and may notify the user of house 215 with data related to the lost puppy (e.g., video footage of the puppy, snapshot of the puppy).
  • the sensor linking module 415 may receive request from one or more sources and initiate a number of actions based on the request.
  • sensor linking module 415 may receive a request from a security camera or doorbell camera from a first location or a device associated with the first location (e.g. , example house 220).
  • sensor linking module 415 is associated with and/or located a second location or a device associated with the second location (e.g. , example house 215) and receives the request from the first location or a device associated with the first location.
  • the request may include a request to access the cameras the second location (e.g., security camera or the doorbell camera at house 215) for a custom time period.
  • the user of the house 220 may input a time period and may request data from the cameras at house 215 for the time period.
  • a sensor linking module 415 at house 220 may request data at a sensor linking module 415 from house 215.
  • the request may be related to a missing child or a lost pet; for example, the request may include an inquiry about a missing child, description of the child, description of the clothes that the child was wearing when last seen, whether the child was riding a bike or may be associated with an object, if the child has any special physical or other features, etc.
  • the sensor linking module 415 may receive data related to sounds and/or movement and/or events occurring inside the house - either by way of a communicatively linked sensor (e.g.
  • the sensor linking module 415 may store the data (e.g., video footage of the location of detected motion). In some examples, after receiving the request, the sensor linking module 415 may automatically detect the missing child from the stored data. In some examples, the sensor linking module 415 may identify a category of the request and may determine one or more user preferences associated with the category. For example, a user of house 215 may enter a conditional user preference to initiate one or more actions. As one example, a conditional user preference may be or include to forward the stored video footage to the requesting device without the user's approval.
  • this conditional preference may be based on a category, a time period associated with the request, information indicated in the request, a source of the request (e.g. , a user, a location, an address, a device). For example, if the category associated with the request include a missing child or an emergency or is requested by a trusted person, the data may be forwarded automatically (e.g., absent user approval).
  • the houses located within the dotted line 205 from FIG. 2 may be part of a network, and may send and receive data to one another based on the descriptions provided in the present disclosure.
  • the sensor linking module 415 may be configured to recognize or predict suspicious behavior of person in a neighborhood or requesting information from others.
  • the sensor linking module 415 may be configured to monitor information related to the person requesting for audio/video data (e.g., frequency of request, time and/or duration of footage requested, profile of the user making the request, the details of the request including the identity or characteristics described in the request, other characteristics, some combination).
  • the sensor linking module 415 may determine that a particular person is requesting video footage between 4:00 pm to 6:00 pm for weekdays from a neighbor.
  • the system may determine that the requester is identifying a schedule when the a home occupant arrives home (or, alternatively or additionally, when one or more home occupants leave home).
  • this may be based on correlating sensor data inside and/or outside the home, location data of one or more occupants, request data, other information, or some combination.
  • the sensor linking module 415 may determine that this pattern of request behavior is unusual or abnormal, and may block the user from making further requests and/or notify one or more other users of this potentially abnormal behavior.
  • the sensor linking module 415 may determine that a particular person is new to the neighborhood and is requesting video footage from a neighbor.
  • the system may identify a profile associated with the requester and may determine that the requestor has a criminal background. In some cases, this may be based on receiving criminal identity data from a public database (e.g., police database) and comparing the identity of the requestor with the received data.
  • a public database e.g., police database
  • the sensor linking module 415 may determine that the person requesting footage from the neighbors, has a criminal background, and may block the person from making further requests and/or notify one or more other users of this potential threat to the neighborhood. In some examples, the sensor linking module 415 may determine that a particular user is requesting video footage from a neighbor, and the request includes an inquiry about a missing child. The system may identify that the requester does not have any child living in the house (e.g. , from database 305/305-a). In some cases, this may be based on sensor data from the location of the requestor, location data of one or more occupants, request data, other information, or some combination. The sensor linking module 415 may determine that this request is unusual or abnormal, and may notify one or more other users of this potentially abnormal request.
  • the sensor linking module 415 may receive data from a plurality of sources and initiate any number of actions based on the data.
  • sensor linking module 415 may receive data from a security camera or doorbell camera at example house 215 (e.g., sensor linking module 415 is associated with and/or located at example house 215).
  • Some or all of the house that are networked may transmit and/or receive data from sensors and computing devices associated with any, some, or all of the networked locations.
  • the data may be related to sounds and/or movement captured in front of the house; for example, people entering and exiting the house, people walking by, animals walking by, cars driving by, tree branches swaying the sound of wind and/or rain, the sound of a car colliding with another car, the sounds of shouting, etc.
  • the sensor linking module 415 may receive data related to sounds and/or movement and/or events occurring inside the house - either by way of a communicatively linked sensor (e.g. , another camera, a motion sensor, a microphone), or by way of data transmitted from an associated device in the house (e.g. , smartphone, control panel) to the device 405.
  • a communicatively linked sensor e.g. , another camera, a motion sensor, a microphone
  • an associated device in the house e.g. , smartphone, control panel
  • the device 405 may be the control panel inside and receives data from a device outside of the house.
  • sensor linking module 415 may receive data related to other devices associated in a networked and wireless communication with device 405.
  • the houses located within the dotted line 205 from FIG. 2 may be part of a network, and may send and receive data to one another based on the descriptions provided herein.
  • the sensor linking module 415 may analyze data relating to an identification and/or an event and/or a user and/or other data, and perform operations relating to transmitted data to another networked device and/or taking an action in response to the data. In some examples, the sensor linking module 415 may perform operations and/or actions related to at least: receiving an inquiry from a device and identifying an object and/or person from the inquiry; identifying a person inside, outside, and/or proximate a location; identifying events inside, outside, and/or proximate a location; and/or identifying a category of inquiry and transmitting the identification data to the device based at least in part on the category; and/or initiating an adjustment, adjustments, or a stream of adjustments of a security feature and/or other user preference based at least in part on the receiving and analyzing.
  • device 405 may obtain data from a sensor located at house 215.
  • the sensor may detect video, still images, sound, motion, temperature, vibration, infrared, frequencies, and/or any combination.
  • sensor linking module 415 may determine that a person has broken the glass of the front living room window of house 215 based on determining the presence of a person, the sound of glass breaking, the proximity of the person and the sound, and/or other data which indicates the front living room window being broken.
  • sensor linking module 415 may determine that a person has broken the glass of a window of house 235, which is located across the street from house 215.
  • sensor linking module 415 may determine that the front living room window of one of the houses has broken, but the presence of a person has not been detected, and thus the breaking of the glass may be for another reason, such as a misthrown baseball or a branch blowing in the wind.
  • obtained and/or received data may be stored in memory for future reference.
  • obtained and/or received data may trigger an adjustment or initiation of an action.
  • the obtained data may be stored without transmitting.
  • the sensor linking module 415 may also store a time stamp associated with the obtained data.
  • transmitter 420 may send the data to another device and/or send a notification and/or an alert and/or a command to another device based on the obtained data.
  • Sensor linking module 415 may also receive or obtain identification data related to a person and/or an event at house 215.
  • the sensor linking module 415 may obtain the identification data related to a person and/or an event at house 215 after receiving a request from house 220.
  • sensor linking module 415 may receive or obtain identification data related to a person and/or an event at another location.
  • a video camera may obtain a facial scan of the person who broke the window at house 220, but may also receive or obtain data from a local or remote database, such as a criminal database containing news photos and/or mugshots.
  • Sensor linking module 415 may then compare the data received (both locally and from a remote source) to make a determination as to who and what has occurred.
  • sensor linking module 415 may determine that a person matching a recent news report about burglaries has been identified at the porch of house 215 and is identified as the person that broke the window of house 220, thus sensor linking module 415 may determine a burglary is about to occur. [0128] Based on determining an identification of a person and/or an event, sensor linking module 415 may adjust a parameter associated with house 215 or take an action. The adjustment may be pre-programmed (e.g. , a user profile which establishes actions and reactions), or may be based on artificial intelligence and learning based on previous events and actions both at the location and based on events and actions at other networked locations. In some examples, the actions may be based on a category of the request.
  • a user may set up a preference that in response to a request, the sensor linking module 415 will be configured to send identification of the person and/or the event without user approval, if the category associated with the request satisfies a threshold.
  • an adjustment may be made automatically; however, in another example, the sensor linking module 415 may send a notification to a user to ask what the request adjustment should be based on the data and the comparison.
  • sensor linking module 415 may further determine which other linked devices are part of the network and/or whether each device wants to, expects to, and/or is enabled to receive communications from device 405. Sensor linking module 415 may thus transmit data to at least one of the other linked devices which are identified as being part of the network.
  • sensor linking module 415 may determine the event is not a burglary, but an accident, and thus the actions taken by sensor linking module 415 may be different based on determining a classification for the determined action.
  • sensor linking module 415 may determine that the video footage may be helpful in identifying the missing person and may transmit the inquiry to other linked devices, and thus the actions taken by sensor linking module 415 may be different.
  • FIG. 5 shows a block diagram 500 of a device 405-a for use in wireless communication, in accordance with various examples.
  • the device 405-a may be an example of one or more aspects of device 405 described with reference to FIG. 4.
  • the device 405-a may also be an example of a control panel 105 described with reference to FIG. 1. It may also be an example of a sensor unit 1 10, local computing device 115 or 120, remote computing device 140 described with reference to FIG. 1.
  • the device 405-a may include a receiver 410- a, a sensor linking module 415-a, and/or a transmitter 420-a, each of which may be an example of receiver 410, sensor linking module 415, and/or transmitter 420 described with reference to FIG. 4.
  • Sensor linking module 415-a may also include a request module 520, an identification module 505, a security action module 510, and/or an alert module 515.
  • the device 405-a may also include a processor. Each of these components may be in
  • the components of device 405-a may, individually or collectively, be implemented using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs application-specific integrated circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits may be used (e.g. , Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art.
  • the functions of each module may also be implemented— in whole or in part— with instructions embodied in memory formatted to be executed by one or more general and/or application-specific processors.
  • the receiver 410-a may receive information such as packets, user data, and/or control information associated with various information channels (e.g., control channels, data channels).
  • the receiver 410-a may be configured to receive data from sensor units 110, a local computing device 115 or 120, a remote computing device 140, a server 155, a third- party database, one or more components of communication system 100, as well as data relating to a request from a user, time period associated with the received request, categories associated with the received request, the data related to user preferences related to the categories of the request, the identification of a person and/or an event, actions based on identification and/or user preferences, user profiles, data relating to home conditions and/or building features, data relating to environmental and geographic parameters and events, some combination, and/or other data and/or information.
  • information may be passed to the sensor linking module 415-a.
  • Request module 520 may receive and/or compose a request associated with a time period.
  • the request module 520 at a first location may receive a request from another request module 520 at a second location.
  • the request may include an inquiry related to a person, an object, and/or an event.
  • request module 520 receives a request and identifies a category associated with the request.
  • the category associated with the request may be a phrase describing the type of request, a color code classifying the request, or a number identifying the category of the request, or any other representation describing or indicating a category of the request.
  • the category can include vandalism, theft, lost pet, missing child, other crimes, and emergency, and the visual representation of the category may be green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child and orange for emergency.
  • request module 520 may identify the requested time period and/or determine data related to identifying a person, an animal, an object and/or an event during the time period.
  • request module 520 may receive a request for access to one or more devices (e.g. , sensors, cameras) at or within a particular location or structure.
  • the request module 520 may identify that the requester is not a verified member of street watch group and may discard the request based at least in part on the identification.
  • the request module 520 may identify that the requester is not a verified member of street watch group and may send a notification to one or more street watch members to facilitate the non-member joining the group through one or more actions.
  • the request module 520 may create a request associated with a time period.
  • the request module 520 at a second location may compose a request.
  • the request module 520 at the second location may compose a request to access one or more security devices (e.g., cameras, sensors, and doorbell cameras) in communication with another request module 520 at a first location.
  • the request may include an inquiry related to a person, an object and/or an event.
  • request module 520 may query a user and receive user input while composing one or more aspects of the request.
  • the request module 520 may automatically compose a request based on an event.
  • one or more sensors of house 220 may detect glass breaking and may identifies movement of figure running toward house 215. Based at least in part on the detected data and/or potential identification of the figure, the request module 520 associated with the house 220 may automatically compose a request to view the security cameras of house 215 and transmit the request to the request module 520 associated with house 215.
  • request module 520 may include permission to access the security cameras at house 215 for a time period. In some cases, at least part of the time period may be based on the detected sensor or other data (i.e. , the start of the time range may be based on the first detection of the movement of the figure and/or the glass breaking information).
  • Identification module 505 may receive and/or determine identification of a person, an object and/or an event. In some examples, the identification module 505 may receive and/or identify data associated with a time period received in a request. In some examples, identification module 505 obtains data within a predetermined proximity of the device.
  • the device can be a sensor device, an outside camera, doorbell camera etc. Data may include pictures, video, audio, sub audio, vibrations, motion, wind, rain, snow, ice, colors, fabrics, fingerprints, retinal scans, voice capture, identification numbers, changes in temperature, quick response (QR) code data, barcode data, radio frequency identification data (RFID), wireless device identification data, etc.
  • QR quick response
  • RFID radio frequency identification data
  • the identification module 505 may determine whether a person is located at or within the house. Using similar methods, the identification module 505 may determine a person described in the request and may determine whether the person was located at or near the house.
  • identification module 505 may receive and/or determine data related to identifying a person, an animal, an object and/or an event.
  • the identification module 505 may receive and/or determine data related to identifying a person, an animal, an object and/or an event.
  • the identification module 505 may receive and/or determine data related to identifying a person, an animal, an object and/or an event.
  • identification data may be compared to the inquiry received and/or determined as described above in order to determine a specific identification.
  • Identification data may be stored in a device and/or in a database enabled to be accessed by the device, for example, a communal database shared by the networked devices.
  • identification data may be obtained and/or received from a remote source and/or a third-party database such as a news report, a flyer, a radio broadcast, an all-points bulletin, a missing child database, a criminal database, a database of user profiles associated with a networked group of users, etc.
  • identification module 505 may retrieve data related to the requested time period and may compare the requested inquiry with the retrieved data. In some examples, the retrieve data may be compared to the inquiry received and/or determined that the retrieved data does not include information related to the inquiry.
  • Security action module 510 may adjust security actions or other automation actions based on the received request and the identification of people, events, objects, and/or animals. In some examples, the security action module 510 may automatically transmit the identification data based at least in part on determining that the category associated with the request meets or exceeds a level of a user-defined threshold. In some examples, the security actions may be automatic and based on preprogrammed preferences (preferences related to a user profile, preferences related to a neighborhood street watch group itself, preferences related to a group of user profiles, and/or default preferences). In other examples, the security action may be based on an identify of the requestor and pre-programmed or default preferences. In some examples, the security action may be dynamic and/or based on user input or other data (e.g., sensor data) in real time (e.g., audio/video footage may be transmitted upon receiving approval from the user).
  • preprogrammed preferences preprogrammed preferences
  • the security action may be dynamic and/or based on user input or other data (e.g
  • adjustment of security actions in examples involving a lighting system, may be to the lighting system and any component(s) thereof.
  • Other adjustments may include, for example, adjustments to a television or system of televisions, a music system, relatedly a home theater system, a thermostat system, a humidifier system, and/or a water system, among others.
  • Other adjustments may be security actions and may include: locking and/or unlocking doors and/or windows; turning on or turning off internal and/or external lights; turning on, turning off, turning the volume up, turning the volume down on audio and/or video broadcasts; deactivating or activating sensors which indicate a door and/or window has been opened or closed; deactivating or activating alarms and sirens; increasing the frequency audio and/or video is captured at a security device; turning on or off electricity and/or circuit breakers and/or water lines; sending an alert to a user, a remote user, a networked device, law enforcement, a news source, an associated group, and the like.
  • the security action adjustment may be automatic and based on preprogrammed preferences. In other examples, the security action adjustment may be based on determining whether or not a user is located at the first and/or a second location. In some examples, the security action adjustment may be dynamic and/or based on user input in real time (e.g. , within 5 minutes of a user receiving an alert). In other examples, the security action adjustment may be based on who has been identified as being located at a second location and/or based on an event at a second location (e.g. , a burglary down the street).
  • Alert module 515 may transmit identification and event data to a user associated with the device at example house 215.
  • the alert may be sent to a control panel inside or outside of the house, a portable electronic device such as a smartphone, tablet, smartwatch, the alert may be broadcast through speakers inside or outside of the house and/or on a television screen and/or monitor.
  • the alert may similarly transmitted and broadcast to at least one other wireless networked device, such as the device located at house 245.
  • the alert may be sent to law enforcement, a news source, a share group database, and the like.
  • the alert module 515 may send an approval alert to the user associated with the device 215-b that a second device 220-b is requesting access to the data associated with device 215-b.
  • the alert module 515 may receive a category associated with the received request and may send a notification to the user of device 215-b indicating the category of the received request.
  • the option to select a security action adjustment associated with a category of a received request may be based on preprogrammed security action adjustment selections, or may be able to manually override automatic or scheduled security action adjustments.
  • the system may perform an automatic security action adjustment if a user does not provide input or a contrary instruction within a predetermined time (e.g. , the system automatically sends audio/video data to the requesting user if the system determines that the identified data at house 215 includes requested data).
  • the alert module 515 may send an alert to the user associated with the device that someone is determined to be present at the house and whether the person is identified, and if so, who the person is identified to be, and/or whether the person is allowed and/or expected.
  • the device may send an alert that a person is determined to be present at the house but the person is not identified.
  • the alert module 515 may send the user an alert which indicates an event has or is occurring; for example, a family member arriving home, a package being delivered, someone breaking in, a car accident in the front yard, a child napping, a pet running away, etc. Based on the alert, the user may be presented with options.
  • the options may be to select a security action adjustment based on preprogrammed security action adjustment selections, or may be able to manually override automatic or scheduled security action adjustments.
  • the system may perform an automatic security action adjustment if a user does not provide input or a contrary instruction within a predetermined time (e.g. , the system automatically arms the system and locks the doors if the user does not indicate otherwise).
  • the alert module 515 may alert other networked devices about the presence or non-presence of a person and/or the occurrence or non-occurrence of an event.
  • the alert module 515 may receive a request for a missing child, and upon receiving the request, the alert module 515 may transmit a missing child alert to other networked devices.
  • the alert sent to a networked device may be
  • the alert sent from the first location may be to request the device at the second location to adjust a security action or take another action.
  • the alert module 515 may receive an indication of the sound of glass breaking at house 215, and thus transmit an alert to a device associated with house 220 regarding a notification of the glass break.
  • the device associated with house 220 may have a preprogrammed action to initiate and/or adjust at house 220 based on data and alerts received from house 215.
  • the alert module 515 may send a request to a device at a second location to determine occupancy at the second location.
  • an identification module associated with a device at the second location may make the occupancy
  • the alert module 515 may send a request to the device at the second location to adjust a security action at the second location.
  • the adjustment of the security action at the second location will be effectuated based on receiving the alert.
  • the adjustment of the security action may be based on a determination of occupancy at the second location and/or based on user preferences or input at the first and/or second locations.
  • the transmitter 420-a may transmit the one or more signals received from other components of the device 405 -a.
  • the transmitter 420-a may transmit data relating to, for example, adjusting a home environment, including data relating to adjusting a device 130, including in some examples data relating to adjusting a component of a lighting system.
  • the transmitter 420-a may be collocated with the receiver 410-a in a transceiver module.
  • FIG. 6 shows a system 600 for networked security cameras and related automation, in accordance with various examples.
  • System 600 may include a device 405-b, which may be an example of the control panel 105, local computing devices 115 and/or 120, remote computing device 140, and/or sensor unit 1 10 described with reference to FIG.
  • the device 405-b may also be an example of one or more aspects of device 405 and/or 405-a of FIGs. 4 and 5.
  • Device 405-b may also include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications.
  • device 405-b may communicate bi-directionally with one or more of local computing devices 115-a, one or more sensor units 110-a, one or more of remote computing devices 140-a, and/or remote server 155-a.
  • This bi-directional communication may be direct (e.g. , device 405-b communicating directly with remote server 155-a) or indirect (e.g., device 405-b communicating indirectly with remote computing device 140-a through remote server 155-a).
  • Device 405-b may also include a processor 605, and memory 610 (including software/firmware code (SW) 615), an input/output controller module 620, a user interface 625, a transceiver 630, and one or more antennas 635 each of which may communicate— directly or indirectly— with one another (e.g. , via one or more buses 640).
  • the transceiver 630 may communicate bi-directionally— via the one or more antennas 635, wired links, and/or wireless links— with one or more networks or remote devices as described above.
  • the transceiver 630 may communicate bi-directionally with one or more of local computing devices 115-a, one or more sensor units 110-a, one or more of remote computing devices 140-a, and/or remote server 155-a.
  • the transceiver 630 may include a modem to modulate the packets and provide the modulated packets to the one or more antennas 635 for transmission, and to demodulate packets received from the one or more antenna 635.
  • a device e.g. , 405-b
  • the device may also have multiple antennas 635 capable of concurrently transmitting or receiving multiple wired and/or wireless transmissions.
  • one element of device 405-b may provide a direct connection to a remote server 155-a via a direct network link to the Intemet via a POP (point of presence).
  • one element of device 405-b e.g., one or more antennas 635, transceiver 630
  • CDPD Cellular Digital Packet Data
  • the signals associated with system 600 may include wireless communication signals such as radio frequency, electromagnetics, local area network (LAN), wide area network (WAN), virtual private network (VPN), wireless network (using 802.11, for example), 345 MHz, Z-WAVE®, cellular network (using 3G and/or LTE, for example), and/or other signals.
  • the one or more antennas 635 and/or transceiver 630 may include or be related to, but are not limited to, WW AN (GSM, CDMA, and WCDMA), WLAN (including BLUETOOTH® and Wi-Fi), WMAN (WiMAX), antennas for mobile communications, antennas for Wireless Personal Area Network (WPAN) applications (including RFID and UWB).
  • each antenna 635 may receive signals or information specific and/or exclusive to itself. In other examples, each antenna 635 may receive signals or information not specific or exclusive to itself.
  • one or more sensor units 110 may connect to some element of system 600 via a network using one or more wired and/or wireless connections.
  • the user interface 625 may include an audio device, such as an external speaker system, an external display device such as a display screen, and/or an input device (e.g. , remote control device interfaced with the user interface 625 directly and/or through I/O controller 620).
  • an audio device such as an external speaker system
  • an external display device such as a display screen
  • an input device e.g. , remote control device interfaced with the user interface 625 directly and/or through I/O controller 620.
  • One or more buses 640 may allow data communication between one or more elements of device 405-b (e.g., processor 605, memory 610, I/O controller 620, user interface 625).
  • the memory 610 may include random access memory (RAM), read only memory (ROM), flash RAM, and/or other types.
  • the memory 610 may store computer-readable, computer-executable software/firmware code 615 including instructions that, when executed, cause the processor 605 to perform various functions described in this disclosure (e.g., obtain data at a sensor, receive identification data, compare data, adjust security actions, transmit data).
  • the software/firmware code 615 may not be directly executable by the processor 605 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the computer-readable, computer-executable software/firmware code 615 may not be directly executable by the processor 605 but may be configured to cause a computer (e.g. , when compiled and executed) to perform functions described herein.
  • the processor 605 may include an intelligent hardware device, e.g., a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), etc.
  • CPU central processing
  • the memory 610 can contain, among other things, the Basic Input-Output system (BIOS) which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.
  • BIOS Basic Input-Output system
  • the sensor linking module 415 to implement the present systems and methods may be stored within the system memory 610.
  • Applications resident with system 600 are generally stored on and accessed via a non-transitory computer readable medium, such as a hard disk drive or other storage medium. Additionally, applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via a network interface (e.g. , transceiver 630, one or more antennas 635).
  • a network interface e.g. , transceiver 630, one or more antennas 635.
  • Many other devices and/or subsystems may be connected to, or may be included as, one or more elements of system 600 (e.g. , entertainment system, computing device, remote cameras, wireless key fob, wall mounted user interface device, cell radio module, battery, alarm siren, door lock, lighting system, thermostat, home appliance monitor, utility equipment monitor, and so on).
  • all of the elements shown in FIG. 6 need not be present to practice the present systems and methods.
  • the devices and subsystems may be interconnected in different ways from that shown in FIG. 6.
  • an aspect of some operation of a system such as that shown in FIG. 6, may be readily known in the art and are not discussed in detail in this application.
  • Code to implement the present disclosure may be stored in a non-transitory computer-readable medium such as one or more of system memory 610 or other memory.
  • the operating system provided on I/O controller module 620 may be iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the transceiver 630 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 635 for transmission and/or to demodulate packets received from the antennas 635. While the control panel and/or device and/or sensor (e.g. , 405-b) may include a single antenna 635, the control panel and/or device and/or sensor (e.g. , 405-b) may have multiple antennas 635 capable of concurrently transmitting and/or receiving multiple wireless transmissions.
  • the device 405-b may include a sensor linking module 415, which may perform the functions described above for the sensor linking module 415 of devices 405 and 405-a of FIGs. 4 and 5, respectively.
  • the device 405-b may also include an event determination module 645.
  • Event determination module 645 may compare data received with elements pre- associated with a plurality of known events to determine whether an event is occurring and classify what type of event is occurring (e.g., user returning home, delivery of a package, car accident in the front yard, burglary, fire, flood). In other examples, event determination module 645 may extrapolate to determine what and when an event is occurring based on data that is not pre-associated with an event.
  • the event determination module 645 may not have the event of a "burglary" stored, but may know about the sound of glass breaking and the sound of heavier footsteps of a person exiting the house as opposed to entering the house.
  • the event determination module 645 may thus use computer learning techniques and extrapolation, as well as considering other external data, to determine that these data indicate a burglary.
  • the device may query another device for additional data to make further determinations. For example, if the device determines the front living room glass has broken, the device may query the other networked devices for audio and/or video data within a predetermined time period, in order to determine if the glass breaking is a burglary or an accident. Based on a request received at the sensor linking module 415-b, the device may query another device for additional data to make one or more further determinations regarding the request. For example, if the device receives a request regarding a missing child, the device may identify a child riding a bike in front of house 215, and the device may query another device to confirm the identification and/or one or more characteristics of the child.
  • identifying, determining, or confirming one or more characteristics or related pieces of information related to the child may serve to confirm the child's identity or may eliminate the child as the child of interest. For example, if the missing child has blond hair (which may be input via user input or based on captured data using one or more sensors or devices), but the child on the bike has black hair, then the child on the bike may be identified as a child other than the missing child.
  • blond hair which may be input via user input or based on captured data using one or more sensors or devices
  • FIG. 7 is a flow chart illustrating an example of a method 700 for networked security cameras and related automation, in accordance with various aspects of the present disclosure.
  • the method 700 is described below with reference to aspects of one or more of the devices 405 described with reference to FIG. 4, and/or aspects of one or more of the devices described with reference to FIG. 5, and/or aspects of one or more of the sensor units 1 10 described with referenced to FIG. 1.
  • a process may execute one or more sets of codes to control the functional elements of device 405 and/or device 405-a and/or sensor unit 1 10 to perform the functions described below.
  • the processor may perform one or more of the functions described below using special-purpose hardware.
  • the method 700 may include obtaining data from a first sensor at a first location.
  • an image capture device such as a camera
  • the operation(s) at block 705 may be performed using the sensor linking module 415 and/or the identification module 505 described with reference to FIGs. 4 and 5, respectively.
  • the method 700 may include receiving identification data related to a person or an event at the first location.
  • Identification data may be related to a person's physical characteristics and/or anatomy, to information a user knows, actions, interactions with devices or areas or locations, environmental and temporal data, electronic data and information received from devices associated with a user, situational data, and the like.
  • Identification data may be retrieved from a local database, a user profile, and/or sensor data relating to one or more locations (e.g. , home, street, car, location of mobile device).
  • Identification data may also be retrieved from a third-party database such as a news report, a flyer, a radio broadcast, an all-points bulletin, a missing child database, a criminal database, a database of user profiles associated with a networked group of users, etc.
  • identification data may not be related to a person, but an animal and/or a vehicle.
  • Identification data may also be related to an event. For example, the sound of glass breaking, metal crunching, tires squealing, screaming, etc. , may indicate a robbery, a crash, a child napping, an accident, or another determined event, etc.
  • the operation(s) at block 710 may be performed using the sensor linking module 415 and/or the identification module 505 and/or the event determination module 645 described with reference to FIGs. 4, 5, and 6
  • the method 700 may include comparing the obtained data with the identification data. Based on the data obtained by the first device, and the identification data received, the device may compare the data to make a determination. For example, if it is detected that glass is breaking, but there is no person detected within a predetermined distance of the glass at the time of the breaking (e.g. , within a five foot radius), the device may determine the glass broke due to a branch hitting the glass or a baseball hitting the glass.
  • a predetermined distance of the glass at the time of the breaking e.g. , within a five foot radius
  • the device may determine this is an intruder breaking into this house.
  • the operation(s) at block 715 may be performed using the sensor linking module 415 and/or the identification module 505 and/or the event determination module 645 described with reference to FIGs. 4, 5, and 6 respectively.
  • the method 700 may include adjusting a first security action at the first location based at least on comparing the received data with the obtained data.
  • the security at the ingress and egress points may increase (e.g., doors and/or windows lock, curtains close, lights and/or sounds activate, alarms activate, law enforcement is notified, other networked users are notified, sprinklers are activated) or decrease (e.g. , security system tumed off, blinds raise, doors unlock).
  • the operation(s) at block 720 may be performed using the sensor linking module 415 and/or the security action module 510 described with reference to FIGs. 4 and 5, respectively.
  • the method 700 may include transmitting information to a second sensor at a second location different from the first location based at least in part on the determining, the second sensor being part of a predetermined group of devices.
  • the first device may share data related to the identification with another networked device.
  • the first device may share data with law enforcement, news sources, security companies, delivery companies, etc.
  • the operation(s) at block 725 may be performed using the sensor linking module 415 and/or the security action module 510 and/or the alert module 515 described with reference to FIGs. 4 and 5, respectively.
  • the method 700 may provide for networked security cameras and related automation. It should be noted that the method 700 is just one implementation and that the operations of the method 700 may be rearranged or otherwise modified such that other implementations are possible.
  • FIG. 8 is a flow chart illustrating an example of a method 800 for networked security cameras and related automation, in accordance with various aspects of the present disclosure.
  • the method 800 is described below with reference to aspects of one or more of the devices 405 described with reference to FIG. 4, and/or aspects of one or more of the devices described with reference to FIG. 5, and/or aspects of one or more of the sensor units 1 10 described with referenced to FIG. 1.
  • a process may execute one or more sets of codes to control the functional elements of device 405 and/or device 405-a and/or sensor unit 1 10 to perform the functions described below. Additionally or
  • the processor may perform one or more of the functions described below using special-purpose hardware.
  • the method 800 may include determining an indication of occupancy at the first location. For example, determining an indication of occupancy at the first location may include determining if an known or recognized user has arrived at home by way of presence detection and identification techniques.
  • the techniques may include: detection by motion sensor, a microphone detecting sound, sensors detecting vibrations, facial recognition, voice recognition, fingerprint scan, retinal scan, identification by way of wireless
  • the operation(s) at block 805 may be performed using the sensor linking module 415 and/or the identification module 505 and/or the event determination module 645 described with reference to FIGs. 4, 5, and 6 respectively.
  • the method 800 may include adjusting the first security action based on the indication of occupancy.
  • a security action may be determined and/or activated and/or initiated based on the determination of an event or identification (or non-identification) of a person and/or object.
  • the security at the ingress and egress points may increase (e.g. , doors and/or windows lock, curtains close, lights and/or sounds activate, alarms activate, law enforcement is notified, other networked users are notified, sprinklers are activated) regardless if an user is home or not.
  • the security action may be based on the fact a user was determined to be home or not or that a structure has been determined to be occupied or not. For example, in the case that a user is determined to be home, the security action may be to notify the user that someone suspicious is outside, or that a flagged event is happening outside (e.g. , a stolen car is identified as driving by). Because the user is home, the alert may be all that is desired and/or sufficient. However, if the user is determined not to be home, the security actions may be different. Because the user is not present to deal with the situation him or herself, the security actions may make the house more secure.
  • the security actions may activate instruments in the home to make it appear as if a user is home, even if he or she is not. For example, turning on lights or music.
  • the operation(s) at block 810 may be performed using the sensor linking module 415 and/or the security action module 510 described with reference to FIGs. 4 and 5, respectively.
  • the method 800 may transmitting a first request to a device at the second location to determine an indication of occupancy at the second location.
  • multiple devices may be networked together in wireless communication (e.g., a neighborhood, a group, a community network).
  • a device may determine that a person identified from the news as stealing a car is located at house 215.
  • the device associated with house 215 may be programmed to warn a user at the house within a predetermined area or proximity, such as a home down the street (e.g. , house 225), and thus sends a communication or an instruction to the device associated with house 225 to determine whether anyone is home at house 225.
  • the operation(s) at block 815 may be performed using the sensor linking module 415 and/or the security action module 510 and/or the alert module 515 described with reference to FIGs. 4 and 5, respectively.
  • the method 800 may include transmitting a second request to adjust a second security action at the second location based at least in part on the determined indication of occupancy at the second location. Based on determining whether a person is home or not at house 225, the device associated with house 215 may send a request to the device at house 225 to adjust a security action at house 225.
  • the security actions may be similar to those described previously.
  • the operation(s) at block 820 may be performed using the sensor linking module 415 and/or the security action module 510 and/or the alert module 515 described with reference to FIGs. 4 and 5, respectively.
  • the method 800 may provide for networked security cameras and related automation. It should be noted that the method 800 is just one implementation and that the operations of the method 800 may be rearranged or otherwise modified such that other implementations are possible.
  • FIG. 9 is a flow chart illustrating an example of a method 900 related to a request for information, in accordance with various aspects of the present disclosure.
  • the method 900 is described below with reference to aspects of one or more of the devices 405 described with reference to FIG. 4, and/or aspects of one or more of the devices described with reference to FIG. 5, and/or aspects of one or more of the sensor units 110 described with referenced to FIG. 1.
  • a process may execute one or more sets of codes to control the functional elements of device 405 and/or device 405 -a and/or sensor unit 110 to perform the functions described below.
  • the processor may perform one or more of the functions described below using special-purpose hardware.
  • the method 900 may include receiving from a first device at a first location, a request to access data associated with a time period from a second device at a second location, the data comprising at least one of audio data, visual data, or a combination thereof.
  • receiving from a first device at a first location, a request to access data associated with a time period from a second device at a second location may include receiving a request to access a camera at a first location.
  • a user at the second device e.g., house 220
  • the request may be related to vandalism, theft, lost pet, missing child, emergency, etc.
  • the operation(s) at block 905 may be performed using the sensor linking module 415 and/or the request module 520 described with reference to FIGs. 4, 5, and 6 respectively.
  • the method 900 may include receiving from the first device, a category associated with the request.
  • the category may include a phrase describing the urgency of the request and may also include a visual identifier.
  • the category may include vandalism, theft, lost pet, missing child, other crimes, and emergency, and the visual representation of the category may be green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child missing child and orange for emergency.
  • the operation(s) at block 910 may be performed using the sensor linking module 415 described with reference to FIGs. 4 and 5.
  • the method 900 may include identifying a first set of data associated with the time period, the identified first set of data based at least in part on the request and the category.
  • the operation(s) at block 915 may be performed using the sensor linking module 415 and/or the identification module 505 and/or the alert module 515 described with reference to FIGs. 4 and 5, respectively.
  • the method 900 may include automatically transmitting the first set of data to the first device based at least in part on the category. Based on determining whether the category satisfies a pre-determined threshold, the first set of data may be automatically transmitted.
  • the operation(s) at block 920 may be performed using the sensor linking module 415 and/or the described with reference to FIGs. 4 and 5.
  • the method 900 may provide for networked security cameras and related automation. It should be noted that the method 900 is just one implementation and that the operations of the method 900 may be rearranged or otherwise modified such that other implementations are possible.
  • FIG. 10 is a flow chart illustrating an example of a method 1000 related to a request for information, in accordance with various aspects of the present disclosure.
  • the method 1000 is described below with reference to aspects of one or more of the devices 405 described with reference to FIG. 4, and/or aspects of one or more of the devices described with reference to FIG. 5, and/or aspects of one or more of the sensor units 110 described with referenced to FIG. 1.
  • a process may execute one or more sets of codes to control the functional elements of device 405 and/or device 405 -a and/or sensor unit 110 to perform the functions described below.
  • the processor may perform one or more of the functions described below using special-purpose hardware.
  • the method 1000 may include receiving from a first device at a first location, a request to access data associated with a time period from a second device at a second location, the data comprising at least one of audio data, visual data, or a combination thereof.
  • the request may be a request to access camera footage during the time period at the second camera.
  • the operation(s) at block 1005 may be performed using the sensor linking module 415 and the request module 520 described with reference to FIGs. 4 and 5 respectively.
  • the method 1000 may include receiving from the first device, an inquiry associated with an object, or a person, or both.
  • a user associated with the first device may include an inquiry related to an object or an event or a person, within the request.
  • the operation(s) at block 1010 may be performed using the sensor linking module 415 and/or the request module 520 described with reference to FIGs. 4 and 5, respectively.
  • the method 1000 may include receiving from the first device, a category associated with the request.
  • the category may include a phrase describing the urgency of the request and may also include a visual identifier.
  • the category may include vandalism, theft, lost pet, missing child, other crimes, and emergency, and the visual representation of the category may be green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child missing child and orange for emergency.
  • the operation(s) at block 1015 may be performed using the sensor linking module 415 described with reference to FIGs. 4 and 5.
  • the method 1000 may include obtaining from a third device, the data associated with the time period at the second device.
  • the operation(s) at block 1020 may be performed using the sensor linking module 415 and/or the identification module 505 described with reference to FIGs. 4 and 5, respectively.
  • the method 1000 may include identifying a first set of data associated with the time period, the identified first set of data based at least in part on the request, the category and the data obtained from the third device.
  • the operation(s) at block 1025 may be performed using the sensor linking module 415 described with reference to FIGs. 4, 5, and 6
  • the method 1000 may include confirming an identity of the obj ect, the person, or both based at least in part on the first set of data and the inquiry.
  • the operation(s) at block 1030 may be performed using the sensor linking module 415 described with reference to FIGs. 4, 5, and 6.
  • the method 1000 may include transmitting the first set of data to the first device based at least in part on the category.
  • the operation(s) at block 1035 may be performed using the sensor linking module 415 described with reference to FIGs. 4, 5, and 6.
  • the method 1000 may provide for networked security cameras and related automation. It should be noted that the method 1000 is just one implementation and that the operations of the method 1000 may be rearranged or otherwise modified such that other implementations are possible.
  • FIG. 11 is a flow chart illustrating an example of a method 1 100 related to a request for information, in accordance with various aspects of the present disclosure.
  • the method 1100 is described below with reference to aspects of one or more of the devices 405 described with reference to FIG. 4, and/or aspects of one or more of the devices described with reference to FIG. 5, and/or aspects of one or more of the sensor units 110 described with referenced to FIG. 1.
  • a process may execute one or more sets of codes to control the functional elements of device 405 and/or device 405 -a and/or sensor unit 110 to perform the functions described below.
  • the processor may perform one or more of the functions described below using special-purpose hardware.
  • the method 1100 may include determining that a first device at a first location and a second device at a second location are part of a pre-determined group of devices operating in a network.
  • multiple devices may be networked together in wireless communication (e.g. , a neighborhood, a group, a community network).
  • determining that a first device at a first location and a second device at a second location are part of a pre-determined group of devices may include determining that the first device and the second device are members of the same street watch group.
  • the operation(s) at block 1105 may be performed using the sensor linking module 415 described with reference to FIGs. 4, 5, and 6.
  • the method 1100 may include creating at the first device, a request to access data associated with a time period, the data being captured by the second device, and the data comprising at least one of audio data, visual data, or a combination thereof.
  • a user associated with the first device house 220
  • may compose a request to access data at the second device house 215.
  • the operation(s) at block 1110 may be performed using the sensor linking module 415 and/or the request module 520 described with reference to FIGs. 4 and 5, respectively.
  • the method 1100 may include identifying a category associated with the request.
  • the category may include vandalism, theft, lost pet, missing child, other crimes, and emergency, and the visual representation of the category may be green for vandalism, blue for theft, yellow for other crimes, pink for lost pet, red for missing child missing child and orange for emergency.
  • the operation(s) at block 1115 may be performed using the sensor linking module 415 described with reference to FIGs. 4 and 5.
  • the method 1100 may include transmitting the request and the category associated with the request to the second device.
  • the request may be transmitted from a first member of a street watch group to a second member of the street watch group.
  • the operation(s) at block 1120 may be performed using the sensor linking module 415 and/or the request module 520 described with reference to FIGs. 4 and 5, respectively.
  • the method 1 100 may provide for networked security cameras and related automation. It should be noted that the method 1100 is just one implementation and that the operations of the method 1100 may be rearranged or otherwise modified such that other implementations are possible.
  • aspects from two or more of the methods 700, 800, 900, 1000, and 1100 may be combined and/or separated. It should be noted that the methods 700, 800, 900, 1000, and 1100 are just example implementations, and that the operations of the methods 700, 800, 900, 1000, and 1 100 may be rearranged or otherwise modified such that other implementations are possible. In some examples, aspects from two or more of the methods 700, 800, 900, 1000, and 1 100 may be combined and/or separated. It should be noted that the methods 700, 800, 900, 1000, and 1 100 are just example implementations, and that the operations of the methods 700, 800, 900, 1000, and 1 100 may be rearranged or otherwise modified such that other implementations are possible.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, and/or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, and/or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • the term "and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
  • the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
  • any disclosure of components contained within other components or separate from other components should be considered exemplary because multiple other architectures may potentially be implemented to achieve the same functionality, including incorporating all, most, and/or some elements as part of one or more unitary structures and/or separate structures.
  • Computer-readable media includes both computer storage media and
  • a storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • computer-readable media can comprise RAM, ROM, EEPROM, flash memory, CD-ROM, DVD, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general- purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
  • This disclosure may specifically apply to security system applications.
  • This disclosure may specifically apply to automation system applications.
  • the concepts, the technical descriptions, the features, the methods, the ideas, and/or the descriptions may specifically apply to security and/or automation system applications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Medical Informatics (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Theoretical Computer Science (AREA)
  • Library & Information Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Alarm Systems (AREA)

Abstract

La présente invention concerne des appareils, des techniques et des procédés destinés à un système de sécurité et/ou d'automatisation. Dans certains cas, les procédés peuvent comprendre la réception, d'un premier dispositif à un premier emplacement, d'une requête d'accès à des données associées à une période de temps d'un second dispositif à un second emplacement, les données comprenant des données audio et/ou des données visuelles, ou une combinaison de celles-ci, la réception, du premier dispositif, d'une catégorie associée à la requête, l'identification d'un premier ensemble de données associées à la période de temps, le premier ensemble de données étant identifié sur la base, au moins en partie, de la requête et de la catégorie, et la transmission automatique du premier ensemble de données au premier dispositif sur la base, au moins en partie, de la catégorie.
PCT/US2017/062620 2016-12-06 2017-11-20 Surveillance de rue WO2018106437A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15/371,004 2016-12-06
US15/371,004 US10522013B2 (en) 2016-05-20 2016-12-06 Street watch

Publications (2)

Publication Number Publication Date
WO2018106437A2 true WO2018106437A2 (fr) 2018-06-14
WO2018106437A3 WO2018106437A3 (fr) 2018-07-26

Family

ID=62492053

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/062620 WO2018106437A2 (fr) 2016-12-06 2017-11-20 Surveillance de rue

Country Status (1)

Country Link
WO (1) WO2018106437A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190304274A1 (en) * 2018-04-03 2019-10-03 Digital Monitoring Products, Inc. Security system with doorbell, camera and identification capability
WO2020107006A1 (fr) * 2018-11-21 2020-05-28 Frederick Newton Procédés et appareil pour un système de défense de zone publique
US11741807B2 (en) 2018-11-21 2023-08-29 Frederick Lee Newton Methods and apparatus for a public area defense system
US11879706B2 (en) 2019-01-28 2024-01-23 Frederick Lee Newton Methods and apparatus for non-lethal weapons comprising a power amplifier to produce a nonlethal beam of energy

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7202884B1 (en) * 2000-06-21 2007-04-10 8X8, Inc. Surveillance method and system
US7746378B2 (en) * 2004-10-12 2010-06-29 International Business Machines Corporation Video analysis, archiving and alerting methods and apparatus for a distributed, modular and extensible video surveillance system
US8749383B2 (en) * 2011-07-06 2014-06-10 Honeywell International Inc. Method of neighborhood watch implemented in-part with electronic surveillance system
US9041812B2 (en) * 2012-11-13 2015-05-26 International Business Machines Corporation Automated authorization to access surveillance video based on pre-specified events
US9392099B2 (en) * 2013-06-24 2016-07-12 Cellco Partnership Mobile surveillance system

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190304274A1 (en) * 2018-04-03 2019-10-03 Digital Monitoring Products, Inc. Security system with doorbell, camera and identification capability
WO2020107006A1 (fr) * 2018-11-21 2020-05-28 Frederick Newton Procédés et appareil pour un système de défense de zone publique
US11741807B2 (en) 2018-11-21 2023-08-29 Frederick Lee Newton Methods and apparatus for a public area defense system
US11879706B2 (en) 2019-01-28 2024-01-23 Frederick Lee Newton Methods and apparatus for non-lethal weapons comprising a power amplifier to produce a nonlethal beam of energy

Also Published As

Publication number Publication date
WO2018106437A3 (fr) 2018-07-26

Similar Documents

Publication Publication Date Title
US11183037B2 (en) Street watch
US10861305B2 (en) Drone enabled street watch
US9870694B2 (en) Networked security cameras and automation
US11196907B1 (en) Automatic greetings by outdoor IP security cameras
US11386285B2 (en) Systems and methods of person recognition in video streams
US10909833B2 (en) Geo-location services
US10986717B1 (en) Reduced false alarms for outdoor IP security cameras
US12230111B2 (en) Control access utilizing video analytics
US11256951B2 (en) Systems and methods of person recognition in video streams
US10630943B1 (en) Smart surveillance systems
US10657749B2 (en) Automatic system access using facial recognition
US10807563B1 (en) Premises security
US10255774B2 (en) System and methods for correlating sound events to security and/or automation system operations
US10235822B2 (en) Automatic system access using facial recognition
US20190317462A1 (en) Managing barrier and occupancy based home automation system
US11361060B1 (en) Home automation system supporting dual-authentication
US9728077B1 (en) eReceptionist and eNeighborhood watch system for crime prevention and/or verification
US10922935B2 (en) Detecting a premise condition using audio analytics
US10163329B1 (en) Home alarm system
US11523485B1 (en) Reduced false alarms for outdoor IP security cameras
WO2018106437A2 (fr) Surveillance de rue
WO2018222387A1 (fr) Systèmes et procédés de gestion de données de reconnaissance de personnes
US20170278363A1 (en) Emergency doorbell communicator

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17878478

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17878478

Country of ref document: EP

Kind code of ref document: A2

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载