Battery powered image capture device

Abstract

The present disclosure provides a method. The method includes, in response to receiving a signal from a sensor of a device configured to detect motion within a field of view, energizing, by a controller of the device, at least one processor of the device different from the controller; analyzing, by the at least one processor, one or more images from an image sensor of the device to identify an image of a person; sending, by the at least one processor, a trigger to a base station in response to the identification of the image of the person; and starting, by the at least one processor, a multi-task operating system of the apparatus after sending the trigger to the base station.

Description

[0001] Cross Reference to Related Applications This application claims the benefit of U.S. Patent Application 18 / 472,907 (filed September 22, 2023), which claims the benefit of U.S. Provisional Patent Application 63 / 482,426 (filed January 31, 2023), both of which are hereby incorporated by reference in their entirety. TECHNICAL FIELD

[0002] Aspects of the technology described herein relate to security systems and methods, and more particularly, to battery-powered image capture devices. BACKGROUND

[0003] Some monitoring systems use one or more cameras to capture images of an area around or within a residential or commercial location. Such monitoring systems can process the images locally and transmit the captured images to a remote service. If motion is detected, the monitoring system can send an alert to one or more user devices. Using battery-powered cameras can increase various camera functionality such as availability during power outages and reduce installation costs by avoiding the need to extend electrical cables to the cameras. SUMMARY

[0004] Examples described herein relate to systems and methods that conserve power within a security device without inhibiting performance of monitoring and alert functionality. At least one example relates to a method. The method includes powering on, by a controller of a device, at least one processor of the device different from the controller in response to receiving a signal from a sensor of the device configured to detect motion within a field of view; analyzing, by the at least one processor, one or more images from an image sensor of the device to identify an image of a person; sending, by the at least one processor, a trigger to a base station in response to the identification of the image of the person; and initiating, by the at least one processor, a multitasking operating system of the device after sending the trigger to the base station.

[0005] Systems and computer-readable media including instructions to perform the methods described herein are also contemplated. BRIEF DESCRIPTION OF DRAWINGS

[0006] Additional examples of the disclosure, as well as features and advantages thereof, will be more fully understood by reference to the description and accompanying drawings, in which:

[0007] Figure 1 is a schematic diagram of a security system according to some examples described herein.

[0008] Figure 2 is a schematic diagram of a base station according to some examples described herein.

[0009] Figure 3is a schematic diagram of a keyboard according to some examples described herein.

[0010] Figure 4A is a schematic diagram of a security sensor according to some examples described herein.

[0011] Figure 4B is a schematic diagram of an image capture device according to some examples described herein.

[0012] Figure 4C is a schematic diagram of another image capture device according to some examples described herein.

[0013] Figure 5 is a schematic diagram of a data center environment, a monitoring center environment, and a customer device according to some examples described herein.

[0014] Figure 6 is a sequence diagram of a monitoring process according to some examples described herein.

[0015] Figure 7 is a sequence diagram of a process for operating a security system including a battery-powered image capture device according to some examples described herein.

[0016] Figure 8A and Figure 8B is a sequence diagram of a process for operating a battery-powered image capture device according to some examples described herein.

[0017] Figure 9 is a block diagram of a battery-powered image capture device according to some examples described herein.

[0018] Figure 10 is a flowchart of a security event handling process performed by a battery-powered image capture device according to some examples described herein.

[0019] Figure 11 is a schematic diagram of a computing device according to some examples described herein. DETAILED DESCRIPTION

[0020] Some battery-powered image capture devices utilize two power modes: a low power mode and a normal operating mode. The low power mode can be used to permit basic operations such as motion detection, while the normal operating mode can be used to perform additional functions including image processing, data communication with remote devices and services, and audio / video services. For example, in some image capture devices, after an event of interest is detected, other processing components are powered on and initiated. In these examples, the image capture device enters into a higher power operating mode that permits more extensive analysis and response to images captured by one or more imaging sensors or cameras. This binary approach to operation can enable the image capture device to utilize less power over time, depending on the characteristics of the environment monitored by the image capture device.

[0021] However, the above-described binary approach to operation can suffer from drawbacks in some situations. For example, switching between low power operation and normal operation can result in a delay that impacts critical initiation of, for example, a system-wide security alarm. For example, consider a situation in which a low power motion sensor within an image capture device, such as a passive infrared (PIR) sensor, detects motion within its field of view. In this situation, in response to the motion sensor reading, the image capture device can enter into a normal operating mode that enables the image capture device to determine whether the motion is an actual threat, and if so, acquire a recording of the camera field of view and upload the recording to a remote server for additional processing. Entering into this normal operating mode will therefore require the image capture device to initiate the threat detector (e.g., the camera and image analyzer), the communication circuitry (e.g., the transceiver and associated drivers), and any supporting infrastructure (e.g., operating system). The initiation of these functions takes time and power. However, if the threat detector determines that an actual threat does not exist, the time and power required to initiate at least the communication circuitry and associated infrastructure is wasted. Moreover, even if the threat detector determines that an actual threat does exist, initiating all of the features of the normal operating mode and the threat detector can introduce a delay in determining that an actual threat exists. This situation illustrates that utilizing only two power modes can actually result in excessive consumption of power if, for example, not all of the services enabled by the normal operating mode are required for proper response to the particular situation.

[0022] To this end, examples of the present disclosure provide a more tailored approach in which a real-time operating system is used to analyze images and trigger alarms before initiating a multi-tasking operating system for higher level functions such as uploading video to remote devices and services. These examples effectively consume power and reduce the amount of time required for an alarm event.

[0023] For example, in some examples, the image capture device is configured to conduct initial analysis of one or more images captured by an imaging sensor (e.g., a camera) in response to a positive motion detection result produced by a motion detection sensor (e.g., a PIR sensor). In conducting the initial analysis of the images, the image capture device operates in a computer vision (CV) mode. The initial analysis includes, for example, identifying a person in an image captured by the imaging sensor in response to the positive motion detection result. In the CV mode of operation, a high-level processor (e.g., a SoC processor) executes a real-time operating system (RTOS) that supports the functionality of the initial analysis, but does not necessarily support all of the functionality of the image capture device, such as uploading a video to other devices. The RTOS is a limited context execution environment that is event-driven (e.g., triggered by motion detected by the motion sensor) and can quickly launch (e.g., within approximately 5 seconds) upon receiving a motion detection signal from the motion sensor, which helps to balance power consumption with the ability to provide timely movement detection and / or threat notifications. By conducting the initial analysis of the images in the limited context of the RTOS, the image capture device can quickly react to motion detected by the motion sensor, such as by sending a motion trigger signal or event to other devices or sounding an audible alarm (e.g., siren) before conducting more computationally intensive actions, such as uploading a video. In these examples, the image capture device can be further configured to conduct additional, more computationally intensive functionality, such as uploading a video, by launching and operating in a virtual machine (VM) mode of operation as will be further described below. However, launching into the VM can take more time (e.g., 2.5 to 4 seconds) than launching into the RTOS. Thus, at least some of the examples described herein perform urgent operations via a provided RTOS that can support the urgent operations.

[0024] While various examples are described herein, it will be apparent to one of ordinary skill in the art that many more examples and implementations are possible. Consequently, the examples described herein are not the only examples and implementations possible. In addition, the advantages described above are not necessarily the only advantages and are not necessarily expected to be realized by every example.

[0025] For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the examples illustrated in the drawings, and specific language will be used to describe the examples. It will, nevertheless, be understood that no limitation of the scope of the examples described herein is intended by this specific language.

[0026] Figure 1 is a schematic diagram of a security system 100 configured to monitor locations that are different in geographic location, according to some examples. As Figure 1As shown, system 100 includes a monitored location 102A, a monitoring center environment 120, a data center environment 124, one or more client devices 122, and a communication network 118. The monitored location 102A, the monitoring center environment 120, the data center environment 124, the one or more client devices 122, and the communication network 118 include one or more computing devices (e.g., as described below with reference to Figure 11 The one or more client devices 122 are configured to host one or more client interface applications 132. The monitoring center environment 120 is configured to host one or more monitor interface applications 130. The data center environment 124 is configured to host a monitoring service 128 and one or more transport services 126. The location 102A includes image capture devices 104 and 110, a contact sensor assembly 106, a keyboard 108, a motion sensor assembly 112, a base station 114, and a router 116. The base station 114 hosts a monitoring client 136. The image capture device 110 hosts a camera agent 138. Security devices (e.g., devices 104, 106, 108, 110, 112, and 114) disposed at the location 102A can be referred to herein as location-based devices.

[0027] In some examples, the router 116 is a wireless router configured to communicate with the location-based devices via communications consistent with a communication standard, such as any of the various Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. As Figure 1 As shown, the router 116 is also configured to communicate with the network 118. It should be noted that the router 116 implements a local area network (LAN) within and proximate to the location 102A, by way of example only. Other networking technologies involving other computing devices are suitable for use within the location 102A. For example, in some examples, the base station 114 can receive and forward communication data packets transmitted by the image capture device 110 via a personal area network (PAN) protocol, such as BLUETOOTH. Additionally or alternatively, in some examples, the location-based devices communicate directly with one another using any of a variety of protocols suitable for point-to-point use, such as any of the IEEE 802.11 standards, PAN standards, and the like. In at least one example, the location-based devices can communicate with one another using a sub-GHz wireless networking standard, such as IEEE 802.11 ah, Z-WAVE, ZIGBEE, and the like. Other wired, wireless, and mesh network technologies and topologies will be apparent in light of this disclosure and are intended to fall within the scope of the examples disclosed herein.

[0028] Continuing Figure 1In examples, network 118 can include one or more public and / or private networks that support, for example, IP. Network 118 can include, for example, one or more LANs, one or more PANs, and / or one or more wide area networks (WANs). A LAN can include a wired or wireless network that supports various LAN standards, such as versions of IEEE 802.11, etc. A PAN can include a wired or wireless network that supports various PAN standards, such as BLUETOOTH, ZIGBEE, etc. A WAN can include a wired or wireless network that supports various WAN standards, such as a code division multiple access (CDMA) radio standard, a global system for mobile communications (GSM) radio standard, etc. Network 118 connects and enables data communication between computing devices within location 102A, monitoring center environment 120, data center environment 124, and customer device 122. In at least some examples, both monitoring center environment 120 and data center environment 124 include network equipment (e.g., similar to router 116) that is configured to communicate with network 118 and with computing devices collocated or proximate to the network equipment. It should be noted that, in some examples, network 118 and existing networks within location 102A support other communication protocols, such as MQTT or other IoT protocols.

[0029] Continuing Figure 1 In examples, data center environment 124 can include physical space, communication, cooling, and power infrastructure to support networked operation of computing devices. For example, the infrastructure can include rack space into which computing devices are mounted, uninterrupted power supply into which, cooling plenum and equipment, and networking devices. Data center environment 124 can be dedicated to security system 100; can be a non-dedicated, commercially available cloud computing service (e.g., MICROSOFT AZURE, AMAZON WEB SERVICES, GOOGLE CLOUD, etc.); or can include a hybrid configuration composed of dedicated and non-dedicated resources. Regardless of its physical or logical configuration, as shown in FIG. 1, data center environment 124 is configured to host monitoring service 128 and transmission service 126. Figure 1

[0030] Continuing Figure 1 In examples, monitoring center environment 120 can include multiple computing devices (e.g., desktop computers) and network equipment (e.g., one or more routers) connected to the computing devices and network 118. Customer device 122 can include a personal computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a smart phone, etc.) and network equipment (e.g., a router, a cellular modem, a cellular radio, etc.). As shown in FIG. 1, monitoring center environment 120 is configured to host monitor interface 130, and customer device 122 is configured to host customer interface 132. Figure 1

[0031] Continuing Figure 1 ​​of the devices 104, 106, 110, and 112 are configured to acquire analog signals via sensors incorporated into the devices; generate digital sensor data based on the acquired signals; and transmit the sensor data to the base station 114 (e.g., via a wireless link with the router 116). The types of sensor data generated and transmitted by these devices vary with the types of sensors included in the devices. For example, the image capture devices 104 and 110 can acquire ambient light; generate frames of image data based on the acquired light; and transmit the frames to the base station 114, the monitor interface 130, and / or the customer interface 132, although the pixel resolution and frame rate can vary according to the capabilities of the devices. In cases where the image capture devices 104 and 110 have sufficient processing capabilities and available power, the image capture devices 104 and 110 can process the image frames based on the content depicted in the image frames and transmit messages, as further described below. These messages can specify reportable events, and can be transmitted in place of image frames or in addition to image frames. Such messages can be sent directly to another location-based device (e.g., via sub-GHz networking) and / or indirectly to any device within the system 100 (e.g., via the router 116). As Figure 1 shown, the image capture device 104 has a field of view (FOV) that originates proximate the front door of the location 102A, and can acquire images of the walkway, the driveway, and the space between the location 102A and the driveway. The image capture device 110 has a FOV that originates proximate the bathroom of the location 102A, and can acquire images of the living room and dining area of the location 102A. The image capture device 110 can further acquire images of the outdoor area beyond the location 102A through the windows 117A and 117B on the right side of the location 102A.

[0032] Further, as Figure 1 shown, in some examples, the image capture device 110 is configured to communicate with the monitoring service 128, the monitor interface 130, and the customer interface 132 separately from the monitoring client 136 via execution of the camera agent 138. These communications can include sensor data generated by the image capture device 110 and / or commands to be executed by the image capture device 110 sent by the monitoring service 128, the monitor interface 130, and / or the customer interface 132. The commands can include, for example, a request for an interactive communication session in which a monitoring personnel and / or a customer interacts with the image capture device 110 via the monitor interface 130 and the customer interface 132. These interactions can include a request for the image capture device 110 to transmit additional sensor data and / or a request for the image capture device 110 to present output via a user interface (e.g., the user interface 412 of the image capture device 110). Figure 4B The output can include audio and / or video output.

[0033] ContinuingFigure 1 In the example of contact sensor assembly 106, the sensor can detect the presence or absence of a magnetic field generated by a magnet when the magnet is proximate to the sensor. When the magnetic field is present, contact sensor assembly 106 generates Boolean sensor data specifying a closed state. When the magnetic field is not present, contact sensor assembly 106 generates Boolean sensor data specifying an open state. In either case, contact sensor assembly 106 can transmit sensor data to base station 114 indicating whether the front door of location 102A is open or closed. Motion sensor assembly 112 can include an audio emitter that can radiate sound waves (e.g., ultrasonic waves) and an audio sensor that can acquire reflections of the waves. When the audio sensor detects a reflection, motion sensor assembly 112 generates Boolean sensor data specifying a quiescent state because there is no object in motion within the space monitored by the audio sensor. When the audio sensor does not detect a reflection, motion sensor assembly 112 generates Boolean sensor data specifying an alert state because there is an object in motion within the monitored space. In either case, motion sensor assembly 112 can transmit sensor data to base station 114. It should be noted that the particular sensing modes described above are not limiting of the present disclosure. For example, as one of many potential examples, motion sensor assembly 112 can base its operation on acquisition of changes in temperature rather than changes in reflected sound waves.

[0034] Continuing Figure 1 In the example of keyboard 108, keyboard 108 is configured to interact with a user and to interoperate with other location-based devices in response to the interaction with the user. For example, in some examples, keyboard 108 is configured to receive input from a user specifying one or more commands and to transmit the commands to one or more addressing processes. These addressing processes can include processes implemented by one or more of the location-based devices and / or one or more of monitor interface 130 or monitoring service 128. The commands can include, for example, a code authenticating the user as a resident of location 102A and / or a code requesting activation or deactivation of one or more of the location-based devices. Alternatively or additionally, in some examples, keyboard 108 includes a user interface (e.g., a tactile interface such as a set of physical buttons or a set of virtual buttons on a touch screen) configured to interact with a user (e.g., to receive input from the user and / or to present output to the user). Still further, in some examples, keyboard 108 can receive and respond to transmitted commands and present the response as visual or audio output via the user interface.

[0035] Continuing Figure 1In the example of FIG. 1, the base station 114 is configured to interoperate with other location-based devices to provide local command and control functionality and store-and-forward functionality via monitoring of the execution of the client 136. In some examples, to implement the store-and-forward functionality, the base station 114 receives sensor data by monitoring the execution of the client 136, packages the data for transmission, and stores the packaged sensor data in local memory for subsequent communication. Such communication of the packaged sensor data can include, for example, transmitting the packaged sensor data as a payload of a message to one or more of the transport services 126 when a communication link to the transport services 126 via the network 118 is operable. In some examples, packaging the sensor data can include filtering the sensor data and / or generating one or more summaries of a plurality of sensor readings (a maximum value, a minimum value, an average value, a change in value since a last communication, etc. of the plurality of sensor readings). To implement the local command and control functionality, the base station 114 performs a variety of programmed operations in response to various events under the control of the client 136. Examples of these events can include receiving a command from the keyboard 108 or the client interface application 132, receiving a command from one of the monitor interface 130 or the client interface application 132 via the network 118, or detecting the occurrence of a scheduled event. The programmed operations performed by the base station 114 under the control of the client 136 can include activation or deactivation of one or more of the devices 104, 106, 108, 110, and 112, sounding of an alarm, reporting of an event to the monitoring service 128, and transmitting location data to one or more of the transport services 126, to name a few operations. The location data can include data specifying sensor readings (sensor data), configuration data of any of the location-based devices, user input and commands received from a user (e.g., via the keyboard 108 or the client interface 132), or data derived from one or more of these data types (e.g., filtered sensor data, summaries of sensor data, event data specifying an event detected at the location via sensor data, etc.).

[0036] Continuing Figure 1In the example of FIG. 1, the transmission service 126 is configured to securely, reliably, and efficiently exchange messages between processes implemented by the location-based devices and processes implemented by other devices in the system 100. These other devices can include the customer devices 122, devices disposed in the data center environment 124, and / or devices disposed in the monitoring center environment 120. In some examples, the transmission service 126 is also configured to parse messages from the location-based devices to extract payloads included therein, and store the payloads and / or data derived from the payloads within one or more data stores hosted in the data center environment 124. The data housed in these data stores can then be accessed by, for example, the monitoring service 128, the monitor interface 130, and the customer interface 132.

[0037] In certain examples, the transmission service 126 exposes and implements one or more application programming interfaces (APIs) configured to receive, process, and respond to invocations from processes implemented by base stations (e.g., the base station 114) and / or processes implemented by other devices (e.g., the image capture device 110) (e.g., the monitoring client 136 and / or the camera agent 138). Individual instances of the transmission service within the transmission service 126 can be associated with and specific to certain make and model of location-based monitoring equipment (e.g., SIMPLISAFE equipment, RING equipment, etc.). The APIs can be implemented using a variety of architectural styles and interoperability standards. For example, in one example, the APIs are web service interfaces implemented using a representational state transfer (REST) architectural style. In this example, the API invocations are encoded in hypertext transfer protocol (HTTP) along with JavaScript Object Notation (JSON) and / or extensible markup language (XML). These API invocations are addressed to one or more uniform resource locators (URLs) that are API endpoints monitored by the transmission service 126. In some examples, portions of the HTTP communications are encrypted to increase security. Additionally or alternatively, in some examples, the APIs are implemented as MQTT brokers that receive messages and transmit response messages to MQTT clients hosted by the base stations and / or other devices. Alternatively or additionally, in some examples, the APIs are implemented using simple file transfer protocol commands. Thus, the transmission service 126 is not limited to a particular protocol or architectural style. It should be noted that, in at least some examples, the transmission service 126 can transmit one or more API invocations to a location-based device to request data from the location-based device or an interactive communication session with the location-based device.

[0038] Continuing Figure 1The monitoring service 128 is configured to control the overall logical setup and operation of the system 100. Thus, the monitoring service 128 can interoperate with the transport service 126, the monitor interfaces 130, the customer interface 132, and any of the location-based devices. In some examples, the monitoring service 128 is configured to monitor data from a variety of sources for reportable events (e.g., a break-in event), and to notify one or more of the monitor interfaces 130 and / or the customer interface 132 when a reportable event is detected. In some examples, the monitoring service 128 is also configured to maintain state information regarding the location 102A. This state information can indicate, for example, whether the location 102A is secure or threatened. In certain examples, the monitoring service 128 is configured to change the state information to indicate that the location 102A is secure only upon receiving a communication indicating an event that is not a problem (e.g., rather than making such a change in response to a non-consecutive reception of a break-in event). This feature can prevent a "ram and smash" robbery from being successfully executed. Additional example processes that the monitoring service 128 is configured to perform are described below with reference to Figure 5 and Figure 6 are described below.

[0039] Continuing Figure 1 In examples, each monitor interface 130 is configured to control interaction with a computing device of a monitoring personnel, and to perform a variety of programmed operations in response to the interaction. For example, in some examples, the monitor interface 130 controls its host device to provide information to the monitoring personnel regarding reportable events detected at a monitored location, such as the location 102A. Such events can include, for example, movement or alarm conditions generated by one or more of the location-based devices. Alternatively or additionally, in some examples, the monitor interface 130 controls its host device to interact with a user to configure features of the system 100. Additional example processes that the monitor interface 130 is configured to perform are described below with reference to Figure 6 are described below.

[0040] Continuing Figure 1For example, each client interface 132 is configured to control interaction with a client's computing device and to perform various programmed operations in response to that interaction. For instance, in some examples, client interface 132 controls its host device to provide the client with information about reportable events detected at a monitored location (such as location 102A). Such events may include, for example, alert conditions generated by one or more location-based devices. Alternatively or additionally, in some examples, client interface 132 is configured to process input received from the client to activate or deactivate one or more location-based devices. Furthermore, in some examples, client interface 132 configures features of system 100 in response to input from a user. Further example procedures that client interface 132 is configured to perform are referenced below. Figure 6 It has been described.

[0041] Now go to Figure 2 The example base station 114 is illustrated schematically. Figure 2 As shown, base station 114 includes at least one processor 200, volatile memory 202, non-volatile memory 206, at least one network interface 204, user interface 212, battery assembly 214, and interconnection mechanism 216. The non-volatile memory 206 stores executable code 208 and includes data storage 210. Figure 2 In some of the examples shown, the features of base station 114 listed above are incorporated into or are part of housing 218.

[0042] In some examples, the non-volatile (non-transitory) memory 206 includes: one or more read-only memory (ROM) chips; one or more hard disk drives or other magnetic or optical storage media; one or more solid-state drives (SSDs), such as flash drives or other solid-state storage media; and / or one or more hybrid magnetic and SSDs. In some examples, the code 208 stored in the non-volatile memory may include an operating system and one or more applications or programs configured to execute under the operating system. Alternatively or additionally, the code 208 may include specialized firmware and embedded software that are executable without relying on a commercially available operating system. In any case, the execution of the code 208 can be achieved Figure 1 The monitoring client 136 can generate manipulation data, which is part of the data storage 210.

[0043] continue Figure 2In examples of the base station 114, the processor 200 can include one or more programmable processors to execute one or more executable instructions, such as a computer program specified by the code 208, to control operation of the base station 114. As used herein, the term "processor" describes circuitry that performs a function, an operation, or a sequence of operations. The function, operation, or sequence of operations can be hard coded into the circuitry or soft coded by way of instructions held as a software program in a memory device, such as the volatile memory 202, and executed by the circuitry. In some examples, the processor 200 is a digital processor, but the processor 200 can be analog, digital, or mixed-signal. As such, the processor 200 can perform a function, operation, or sequence of operations using digital values and / or using analog signals. In some examples, the processor 200 can be embodied in one or more application specific integrated circuits (ASICs), microprocessors, digital signal processors (DSPs), graphics processing units (GPUs), neural processing units (NPUs), microcontrollers, field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), or multi-core processors. Examples of multi-core processors 200 can provide functionality for parallel, simultaneous execution of instructions, or for parallel, simultaneous execution of one instruction on more than one data.

[0044] Continuing Figure 2 In examples of the base station 114, the processor 200 can include one or more programmable processors to execute one or more executable instructions, such as a computer program specified by the code 208, to control operation of the base station 114. As used herein, the term "processor" describes circuitry that performs a function, an operation, or a sequence of operations. The function, operation, or sequence of operations can be hard coded into the circuitry or soft coded by way of instructions held as a software program in a memory device, such as the volatile memory 202, and executed by the circuitry. In some examples, the processor 200 is a digital processor, but the processor 200 can be analog, digital, or mixed-signal. As such, the processor 200 can perform a function, operation, or sequence of operations using digital values and / or using analog signals. In some examples, the processor 200 can be embodied in one or more application specific integrated circuits (ASICs), microprocessors, digital signal processors (DSPs), graphics processing units (GPUs), neural processing units (NPUs), microcontrollers, field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), or multi-core processors. Examples of multi-core processors 200 can provide functionality for parallel, simultaneous execution of instructions, or for parallel, simultaneous execution of one instruction on more than one data.

[0045] Through execution of the code 208, the processor 200 can control operation of the network interface 204. For example, in some examples, the network interface 204 includes one or more physical interfaces (e.g., radios, Ethernet ports, universal serial bus (USB) ports, etc.) and a software stack including drivers and / or other code 208 configured to communicate with the one or more physical interfaces to support one or more LAN, PAN, and / or WAN standard communication protocols. The communication protocols can include, for example, transmission control protocol (TCP), user datagram protocol (UDP), HTTP, and MQTT, among others. Thus, the network interface 204 enables the base station 114 to communicate over a computer network, such as a LAN established by the router 116, a PAN, and / or a WAN. Figure 1 Figure 1 ​The network interface 204 can be configured to access other computing devices (e.g., location-based devices) and communicate with the other computing devices using one or more wired and / or wireless communication protocols (e.g., Bluetooth®, Bluetooth Low Energy, ZigBee®, Wi-Fi®, WiMAX, cellular, etc.). For example, in at least one example, the network interface 204 accesses the network 118; PAN connections; sub-GHz wireless point-to-point network connections; etc. to transmit messages (e.g., wake-up messages, alert messages, etc.) to other computing devices. These messages can request sensor data streams, trigger alert states, or initiate other operations. The frequency bands in which the network interface 204 can be used for sub-GHz wireless networking include, for example, the 868 MHz frequency band and / or the 915 MHz frequency band. Using sub-GHz wireless networking can improve operable communication distances and / or reduce power consumed to communicate.

[0046] Through execution of the code 208, the processor 200 can control operation of the user interface 212. For example, in some examples, the user interface 212 includes user input and / or output devices (e.g., a keyboard, a mouse, a touchscreen, a display, a speaker, a camera, an accelerometer, a biometric scanner, an environmental sensor, etc.) and a software stack including drivers and / or other code 208 configured to communicate with the user input and / or output devices. For example, the user interface 212 can be implemented by the customer device 122 hosting the mobile application (e.g., the customer interface 132). The user interface 212 enables the base station 114 to interact with a user to receive input and / or present output. The presented output can include, for example, one or more graphical user interfaces (GUIs) including one or more controls configured to display output and / or receive input. The input can specify values to be stored in the data store 210. The output can indicate values stored in the data store 210. It should be noted that, in some examples, portions of the user interface 212 are accessible and / or visible as part of and / or through the housing 218. These portions of the user interface 212 can include, for example, one or more light-emitting diodes (LEDs). Alternatively or additionally, in some examples, the user interface 212 includes a 95 dB siren that the processor 200 sounds to indicate that a break-in event has been detected.

[0047] Continuing Figure 2In some examples, the interconnection mechanism 216 includes a communication bus. Additionally, in some examples, the battery assembly 214 is configured to supply operating power to the various features of the base station 114 described above. In some examples, the battery assembly 214 includes at least one rechargeable battery (e.g., one or more NiMH or lithium batteries). In some examples, the rechargeable battery has a runtime capacity sufficient to operate the base station 114 for 24 hours or more when the base station 114 is disconnected from or otherwise does not receive line power. Alternatively or additionally, in some examples, the battery assembly 214 includes power supply circuitry to receive, condition, and distribute line power to both operate the base station 114 and recharge the rechargeable battery. The power supply circuitry can include, for example, transformers and rectifiers to convert AC line power to DC device and recharging power, among other circuitry.

[0048] Turning now to Figure 3 , an example keyboard 108 is schematically illustrated. As Figure 3 shown, the keyboard 108 includes at least one processor 300, volatile memory 302, non-volatile memory 306, at least one network interface 304, a user interface 312, a battery assembly 314, and an interconnection mechanism 316. The non-volatile memory 306 stores executable code 308 and data storage 310. In some examples, illustrated by Figure 3 the above-listed features of the keyboard 108 are incorporated within or are part of a housing 318.

[0049] In some examples, the respective descriptions of the processor 200, volatile memory 202, non-volatile memory 206, interconnection mechanism 216, and battery assembly 214 with reference to the base station 114 can apply with reference to the processor 300, volatile memory 302, non-volatile memory 306, interconnection mechanism 316, and battery assembly 314 with reference to the keyboard 108. Accordingly, these descriptions will not be repeated.

[0050] Continuing Figure 3In examples, the processor 300 can control the operation of the network interface 304, through execution of the code 308. In some examples, the network interface 304 includes one or more physical interfaces (e.g., radios, Ethernet ports, USB ports, etc.) and a software stack including drivers and / or other code 308 configured to communicate with the one or more physical interfaces to support one or more LAN, PAN, and / or WAN standard communication protocols. These communication protocols can include, for example, TCP, UDP, HTTP, and MQTT, among others. Thus, the network interface 304 enables the keyboard 108 to access and communicate with other computing devices (e.g., location-based devices) via a computer network (e.g., a LAN established by the router 116; a PAN connection; a point-to-point sub-GHz wireless network connection; etc.).

[0051] Continuing Figure 3 In examples, the processor 300 can control the operation of the user interface 312, through execution of the code 308. In some examples, the user interface 312 includes user input and / or output devices (e.g., physical keys arranged as a keyboard, a touchscreen, a display, a speaker, a camera, a biometric scanner, an environmental sensor, etc.) and a software stack including drivers and / or other code 308 configured to communicate with the user input and / or output devices. Thus, the user interface 312 enables the keyboard 108 to interact with a user to receive input and / or present output. This presented output can include, for example, one or more GUIs including one or more controls configured to display output and / or receive input. This input can specify values to be stored in the data store 310. This output can indicate values stored in the data store 310. It should be noted that, in some examples, portions of the user interface 312 (e.g., one or more LEDs) are accessible and / or visible as part of or through the housing 318.

[0052] Turning now to Figure 4A , an example security sensor 422 is schematically illustrated. Figure 1 Particular configurations of the security sensor 422 (e.g., the image capture devices 104 and 110, the motion sensor assembly 112, and the contact sensor assembly 106) are illustrated in and described above. As shown in Figure 4A , the security sensor 422 includes at least one processor 400, volatile memory 402, non-volatile memory 406, at least one network interface 404, a battery assembly 414, an interconnect mechanism 416, and at least one sensor assembly 420. The non-volatile memory 406 stores executable code 408 and a data store 410. Some examples include a user interface 412. In Figure 4AIn certain examples of the display, the features of the safety sensor 422 listed above are incorporated within or are part of the housing 418.

[0053] In some examples, the respective descriptions of the processor 200, the volatile memory 202, the non-volatile memory 206, the interconnect mechanism 216, and the battery component 214 with reference to the base station 114 can apply to the processor 400, the volatile memory 402, the non-volatile memory 406, the interconnect mechanism 416, and the battery component 414 with reference to the safety sensor 422. Accordingly, these descriptions will not be repeated.

[0054] Continuing Figure 4A In examples, the processor 400, via execution of the code 408, can control operation of the network interface 404. In some examples, the network interface 404 includes one or more physical interfaces (e.g., radios (including antennas), Ethernet ports, USB ports, etc.) as well as a software stack including drivers and / or other code 408 configured to communicate with the one or more physical interfaces to support one or more LAN, PAN, and / or WAN standard communication protocols. The communication protocols can include, for example, TCP, UDP, HTTP, and MQTT, among others. Thus, the network interface 404 enables the safety sensor 422 to access and communicate with other computing devices (e.g., location-based devices) via computer networks (e.g., a LAN established by the router 116 and / or a point-to-point connection). For example, in at least one example, the processor 400, when executing the code 408, controls the network interface to stream sensor data acquired from the sensor component 420 (e.g., via UDP) to the base station 114. Alternatively or additionally, in at least one example, the processor 400, via execution of the code 408, can control the network interface 404 to enter a power conservation mode by turning off the 2.4 GHz radio and turning on the sub-GHz radio (both of which are included in the network interface 404). In this example, the processor 400, via execution of the code 408, can control the network interface 404 to enter a streaming or interactive mode by turning on the 2.4 GHz radio and turning off the sub-GHz radio, for example, in response to receiving a wake-up signal from the base station via the sub-GHz radio.

[0055] Continuing Figure 4AFor example, through the execution of code 408, processor 400 can control the operation of user interface 412. In some examples, user interface 412 includes user input and / or output devices (e.g., physical buttons, touchscreen, display, speaker, camera, accelerometer, bio-scanner, environmental sensor, one or more LEDs, etc.) and a software stack that includes drivers and / or other code 408 configured to communicate with the user input and / or output devices. Therefore, user interface 412 enables security sensor 422 to interact with the user to receive input and / or present output. The presented output may include, for example, one or more GUIs including one or more controls configured to display output and / or receive input. The input may specify a value to be stored in data storage 410. The output may indicate a value stored in data storage 410. It should be noted that in some examples, portions of user interface 412 are part of or accessible through housing 418.

[0056] continue Figure 4A For example, sensor component 420 may include one or more types of sensors (such as those mentioned above). Figure 1 The sensor assembly 420 may include the image capture devices 104 and 110, the motion sensor assembly 112, and the contact sensor assembly 106 (as described in the original text), or other types of sensors. For example, in at least one example, sensor assembly 420 includes an image sensor (e.g., a charge-coupled device or an active pixel sensor) and a temperature or thermal imaging sensor (e.g., a passive and / or active infrared (PIR) sensor). Regardless of the type of one or more sensors contained, processor 400 may (e.g., via execution of code 408) acquire sensor data from the contained sensors and stream the acquired sensor data to processor 400 for communication to a base station.

[0057] It should be noted that in some examples of devices 108 and 422, the operations performed by processors 300 and 400 under the corresponding control of codes 308 and 408 can be hard-coded and / or implemented in hardware, rather than as a combination of hardware and software. Furthermore, the execution of code 408 can achieve... Figure 1 The camera agent 138 can generate manipulation data, which is part of the data storage 410.

[0058] Now go to Figure 4B The example image capture device 500 is shown schematically. Figure 1 The image capture device 500 is shown and described above, with specific configurations (e.g., image capture devices 104 and 110) shown. Figure 4BAs shown, the image capture device 500 includes at least one processor 400, volatile memory 402, non-volatile memory 406, at least one network interface 404, a battery assembly 414, and an interconnect mechanism 416. The network interface 404 includes a radio frequency (RF) transceiver 404A. The transceiver 404A can be used to communicate with location-based devices via a sub-GHz network. These features of the image capture device are shown in dashed lines to indicate that they reside within a housing 418. The non-volatile memory 406 stores executable code 408 and data storage 410.

[0059] Some examples further include an image sensor assembly 450, a lamp 452, a speaker 454, a microphone 456, a wall mount 458, a magnet 460, and a motion sensor 462. The image sensor assembly 450 may include a lens and an image sensor. The lamp 452 may include a light-emitting diode (LED), such as a red-green-blue light-emitting LED. In some examples, the lamp 452 may also include an infrared light-emitting diode. The speaker 454 may include a transducer configured to emit a sound in the range of 60 dB to 80 dB or greater. Further, in some examples, the speaker 454 may include a siren configured to emit a sound in the range of 70 dB to 90 dB or greater. The PIR sensor 462 measures changes in the amount of ambient infrared (IR) light radiated from an object in the field of view; however, the PIR sensor 462 does not emit any light. Therefore, the PIR sensor 462 is used to detect motion, represented by changes in temperature over time, such as motion caused by a person, animal, or object moving through the field of view. The microphone 456 may include a microelectromechanical system (MEMS) microphone. The wall mount 458 may include a mounting bracket configured to accept screws or other fasteners for attaching the bracket to a wall, and a cover configured to be mechanically coupled to the mounting bracket. In some examples, the cover is made of a magnetic material such as aluminum or stainless steel to enable the magnet 460 to be magnetically coupled to the wall mount 458, thereby holding the image capture device 500 in place.

[0060] In some examples, the corresponding descriptions of the security sensor 422 with respect to the network interface 404, interconnection mechanism 416, and battery assembly 414 regarding the processor 400, volatile memory 402, network interface 404, non-volatile memory 406, and code 408 can be applied to these same features with respect to the image capture device 500. Therefore, these descriptions will not be repeated here.

[0061] continue Figure 4BFor example, through the execution of code 408, processor 400 can control the operation of image sensor assembly 450, lamp 452, speaker 454, and microphone 456. For example, in at least one example, when code 408 is executed, processor 400 controls image sensor assembly 450 to acquire sensor data in the form of image data for streaming to base station 114 via network interface 404 (or... Figure 1 (One of processes 130, 128, or 132). Alternatively or additionally, in at least one example, by executing code 408, processor 400 controls lamp 452 to emit light, such that image sensor assembly 450 collects sufficient reflected light to form image data. Further, in some examples, by executing code 408, processor 400 controls speaker 454 to emit sound. This sound may be generated locally (e.g., via a siren) or from base station 114 (or via network interface 404). Figure 1 The process 130, 128, or 132 is used for streaming (e.g., speech from a user or monitoring person). Furthermore, in some examples, through the execution of code 408, processor 400 controls microphone 456 to acquire sensor data in the form of sound for streaming to base station 114 via network interface 404. Figure 1 (One of processes 130, 128, or 132).

[0062] It should be recognized that, Figure 4B In the example, light 452, speaker 454, and microphone 456 are implemented Figure 4A An instance of the user interface 412. It should also be recognized that the image sensor assembly 450 and the lamp 452 implement... Figure 4A An example of sensor component 420. Therefore, Figure 4B The image capture device 500 shown is Figure 4A At least one example of the safety sensor 422 shown in the document.

[0063] Now go to Figure 4C This schematically illustrates another example image capture device 520. Figure 1 The image capture device 520 is shown and described above, with specific configurations (e.g., image capture devices 104 and 110) shown. Figure 4CAs shown, image capture device 520 includes at least one processor 400, volatile memory 402, non-volatile memory 406, at least one network interface 404 (including RF transceiver 404A), battery component 414, and interconnection mechanism 416. These features of image capture device 520 are shown in dashed lines to indicate that they reside within housing 418. Non-volatile memory 406 stores executable code 408 and data storage 410. Image capture device 520 further includes image sensor assembly 450, speaker 454, microphone 456, and motion sensor 462 as described above with reference to image capture device 500. Figure 4B

[0064] In some examples, image capture device 520 further includes lights 452A and 452B. Light 452A can include a light emitting diode (LED), such as a red-green-blue light emitting LED. Light 452B can also include an infrared light emitting diode to enable night vision in some examples.

[0065] It should be recognized that, in Figure 4C examples, lights 452A and 452B, speaker 454, and microphone 456 implement instances of user interface 412 of Figure 4A It should also be recognized that image sensor assembly 450 and lights 452 implement instances of sensor assembly 420 of Figure 4A Thus, image capture device 520 as shown in Figure 4C is at least one example of security sensor 422 as shown in Figure 4A Image capture device 520 can be a battery-powered indoor sensor configured to be installed and operated in an indoor environment, such as, for example, within a home, office, store, or other commercial or residential building.

[0066] Turning now to Figure 5 , aspects of data center environment 124 of Figure 1 , monitoring center environment 120 of Figure 1 , one of customer devices 122 of Figure 1 , network 118 of Figure 1 , and multiple monitored locations 102A-N (collectively, locations 102) of Figure 1 are schematically shown. As Figure 5 ​As shown, data center environment 124 hosts monitoring services 128 and transmission services 126 (collectively referred to as transmission services 126A to 126D). Monitoring service 128 includes location data storage 502, sensor data storage 504, artificial intelligence (AI) service 508, event listening service 510, and identity provider 512. Monitoring center environment 120 includes computing devices 518A to 518M (collectively referred to as computing devices 518) that host monitor interfaces 130A to 130M. Each location 102A to 102N includes base stations (e.g., hosting monitoring clients 136A to 136N (collectively referred to as monitoring clients 136)) that host monitoring clients 136A to 136N. Figure 1 The base station 114 (not shown) and the image capture device of the managed software camera agents 138A to 138N (collectively referred to as camera agent 138) (e.g., base station 114, not shown) and the image capture device of the managed software camera agents 138A to 138N (collectively referred to as camera agent 138) Figure 1 (Image capturing device 110, not shown).

[0067] like Figure 5 As shown, transport service 126 is configured to process incoming messages 516B from client interface 132A, monitoring client 136, camera agent 138, and / or monitor interface 130. Transport service 126 is also configured to process outgoing messages 516A addressed to client interface 132A, monitoring client 136, camera agent 138, and monitor interface 130. Location data storage 502 is configured to store location data associated with identifiers of clients monitoring their locations within multiple records. For example, location data may be stored in records having client identifiers and / or location identifiers to associate location data with clients and locations. Sensor data storage 504 is configured to store sensor data (e.g., one or more image data frames) within multiple records, which is associated with identifiers of the location and timestamp at which the sensor data was acquired.

[0068] continue Figure 5For example, AI service 508 is configured to process sensor data (e.g., images and / or image sequences) to identify movement, faces, and other features within the sensor data. Event listening service 510 is configured to scan location data transmitted via incoming message 516B for events and, if an event is identified, execute one or more event handlers to handle the event. In some examples, the event handler may include an event reporter configured to identify reportable events and transmit a message specifying the reportable event to one or more receiving processes (e.g., client interface 132 and / or monitor interface 130). In some examples, event listening service 510 may interoperate with AI service 508 to identify events within sensor data. Identity provider 512 is configured to receive authentication requests from monitoring client 136 or camera agent 138 including security credentials via transport service 126. When identity provider 512 can authenticate the security credentials in the request (e.g., via an authentication function, cross-reference lookup, or some other authentication process), identity provider 512 may transmit a security token in response to the request. The monitoring client 136 or camera agent 138 may receive, store, and include the security token in the subsequent incoming message 516B, enabling the transport service 126A to securely process (e.g., unpack / parse) the data packets included in the incoming message 516B to extract the location data before passing it to the monitoring service 128.

[0069] continue Figure 5 For example, transport service 126 is configured to receive incoming message 516B; verify the authenticity of message 516B; parse message 516B; and extract the location data encoded therein before transmitting the location data to monitoring service 128 for processing. This location data may include the information referenced above. Figure 1 Any of the location data. Each transmission service 126 can be configured to process incoming messages 516B generated by location-based monitoring devices of a specific manufacturer and / or model. Monitoring client 136 and camera agent 138 are configured to generate and transmit incoming messages 516B via network 118 to monitoring service 128, the incoming messages including data packets of location data based on sensor information received at location 102.

[0070] continue Figure 5For example, computing device 518 is configured to host monitor interface 130. In some examples, each monitor interface 130A to 130M is configured to present a GUI including one or more image frames and / or other sensor data. In some examples, client device 122 is configured to host client interface 132. In some examples, client interface 132 is configured to present a GUI including one or more image frames and / or other sensor data. Other features of monitor interface 130 and client interface 132 are referenced below. Figure 6 Further description was provided.

[0071] Now go to Figure 6 The monitoring process 600 is presented as a sequence diagram. In some examples, it may be handled by a security system (e.g., Figure 1 The safety system 100 executes process 600. More specifically, in some examples, at least a portion of process 600 is executed by a location-based device under the control of a device control system (DCS) code (e.g., code 308 or 408), which is controlled by at least one processor ( Figures 3-4C The DCS code may include, for example, a camera agent (e.g., ...). This can be implemented using any of the processors 300 or 400. Figure 1 The camera agent 138). At least a portion of process 600 is handled by the base station (e.g., Figure 1 Base station 114) in monitoring clients (e.g., Figure 1 The process 600 is executed under the control of the monitoring client 136. At least a portion of the process 600 is controlled by the monitoring center environment (e.g., Figure 1 The monitoring center environment 120) in the monitor interface (e.g., Figure 1 The process 600 is executed under the control of the monitor interface 130. At least a portion of the process 600 is controlled by the data center environment (e.g., Figure 1 The data center environment 124) in the monitoring service (e.g., Figure 1 Under the control of the monitoring service 128) or the transmission service (e.g., Figure 1 The process 600 is executed under the control of the transmission service 126. At least a portion of the process 600 is controlled by the client device (e.g., Figure 1 The client device 122) in the client interface (e.g., Figure 1 Executed under the control of the client interface 132).

[0072] like Figure 6 As shown, process 600 begins with monitoring client 136 exchanging one or more authentication requests and responses 604 with transport service 126 with identity provider (e.g., Figure 5The identity provider 512 performs authentication. More specifically, in some examples, the monitoring client 136 transmits an authentication request to the transport service 126 via one or more API calls to the transport service 126. In these examples, the transport service 126 parses the authentication request to extract security credentials from it and passes the security credentials to the identity provider for authentication. In some examples, if the identity provider authenticates the security credentials, the identity provider generates a security token and transmits the security token to the transport service 126. The transport service 126 then receives the security token and transmits it as a payload within the authentication response to the authentication request. In these examples, if the identity provider cannot authenticate the security credentials, the transport service 126 generates an error code and transmits the error code as a payload within the authentication response to the authentication request. Upon receiving the authentication response, the monitoring client 136 parses the authentication response to extract the payload. If the payload includes an error code, the monitoring client 136 may retry authentication and / or its user interface with its host device (e.g., Figure 2 The monitoring client 136 interoperates with the user interface 212 of base station 114 to present an output indicating authentication failure. If the payload includes a security token, the monitoring client 136 stores the security token for subsequent use in communications via location data from incoming messages. It should be noted that the security token may have a limited lifespan (e.g., 1 hour, 1 day, 1 week, 1 month, etc.), after which the monitoring client 136 may need to re-authenticate with the transport service 126.

[0073] Continuing process 600, one or more DCS 602 hosted by one or more location-based devices acquire 606 a described location (e.g., Figure 1 Sensor data at location 102A. The acquired sensor data can be of any type, as referenced above. Figure 1Discussed in relation to FIG. 4. In some examples, one or more of the DCSs 602 continuously acquire sensor data. In some examples, one or more of the DCSs 602 acquire sensor data in response to an event, such as expiration of a local timer (a push event) or receipt of an acquisition poll signal transmitted by the monitoring client 136 (a poll event). In certain examples, one or more of the DCSs 602 stream sensor data to the monitoring client 136, with minimal processing beyond acquisition and digitization. In these examples, the sensor data can constitute a sequence of vectors, with individual vector members comprising a sensor reading and a timestamp. Alternatively or additionally, in some examples, one or more of the DCSs 602 perform additional processing of the sensor data, such as generation of one or more summaries of multiple sensor readings. Still further, in some examples, one or more of the DCSs 602 perform complex processing of the sensor data. For example, if a security sensor comprises an image capture device, the security sensor can perform image processing routines, such as edge detection, motion detection, facial recognition, threat assessment, and reportable event generation.

[0074] Continuing with the process 600, the DCSs 602 transmit sensor data 608 to the monitoring client 136. As with sensor data acquisition, the DCSs 602 can transmit sensor data 608 continuously or in response to an event, such as a push event (originating from the DCSs 602) or a poll event (originating from the monitoring client 136).

[0075] Continuing process 600, monitoring client 136 monitors 610 the location by processing the received sensor data 608. For example, in some examples, monitoring client 136 executes one or more image processing routines. These image processing routines can include any of the image processing routines described above with reference to operation 606. By distributing at least some of the image processing routines between DCS 602 and monitoring client 136, some examples reduce the power consumed by the battery-powered device by offloading processing to the line-powered device. Further, in some examples, monitoring client 136 can execute an ensemble threat detection process that utilizes sensor data 608 from multiple different DCSs 602 as input. For example, in at least one example, monitoring client 136 will attempt to corroborate an open state received from a contact sensor, where motion and facial recognition processing of images of the scene include a window to which the contact sensor is affixed. If two or more of the three processes indicate the presence of an intruder, the threat score increases, and or a break-in event is declared, locally logged, and communicated. Other processing that monitoring client 136 can perform includes outputting local alerts (e.g., in response to detection of particular events and / or satisfaction of other criteria) and detecting maintenance conditions for the location-based device, such as the need to change or recharge a low battery and / or replace / maintain the device hosting DCS 602. Any of the processes described above within operation 610 can result in the creation of location data specifying the outcome of the process.

[0076] Continuing process 600, monitoring client 136 transmits location data 614 to monitoring service 128 via one or more incoming messages 612 to transmission service 126. As with the communication of sensor data 608, monitoring client 136 can transmit location data 614 continuously or in response to an event, such as a push event (originating from monitoring client 136) or a polling event (originating from monitoring service 128).

[0077] Continuing with process 600, monitoring service 128 processes 616 the received location data. For example, in some examples, monitoring service 128 executes one or more routines described above with reference to operations 606 and / or 610. Additionally or alternatively, in some examples, monitoring service 128 uses historical information associated with the location identified in the location data and / or other locations geographically proximate to that location (e.g., within the same ZIP code) to calculate a threat score or further refine an existing threat score. For example, in some examples, if multiple break-ins have been recorded for that location and / or other locations within the same ZIP code within a configurable time span including the current time, monitoring service 128 can increase the threat score calculated by DCS 602 and / or monitoring client 136. In some examples, monitoring service 128 determines whether the location data 614 includes any reportable events by applying a set of rules and criteria to the location data 614, and if so, transmits an event report 618A and / or 618B to monitor interface 130 and / or customer interface 132. The reportable events can be a certain type of event (e.g., a break-in) or a certain type of event that satisfies additional criteria (e.g., movement within a particular ZIP code combined with a threat score that exceeds a threshold). The event report 618A and / or 618B can have a priority based on the same criteria used to determine whether the event reported therein is reportable, or can have a priority based on a different set of criteria or rules.

[0078] Continuing with process 600, monitor interface 130 interacts 620 with the monitoring personnel through, for example, one or more GUIs. These GUIs can provide detailed information and context about one or more reportable events.

[0079] Continuing with process 600, customer interface 132 interacts 622 with the at least one customer through, for example, one or more GUIs. These GUIs can provide detailed information and context about one or more reportable events.

[0080] It should be noted that the processing of sensor data and / or location data described above with reference to operations 606, 610, and 616 can be performed by processors disposed within various portions of system 100. For example, in some examples, DCS 602 performs minimal processing of the sensor data (e.g., only acquisition and streaming), and the remaining processing described above is performed by monitoring client 136 and / or monitoring service 128. This approach can help to prolong battery runtime of the location-based devices. In other examples, DCS 602 performs as much of the sensor data processing as possible, leaving monitoring client 136 and monitoring service 128 to perform only processes that require sensor data across location-based devices and / or locations. This approach can help to increase the scalability of system 100 with respect to adding new locations.

[0081] Turning now to Figure 7 , the power control process 700 is shown as a sequence diagram. In some examples, the process 700 can be performed by a security system (e.g., the security system 100 of Figure 1 . More specifically, in some examples, at least a portion of the process 700 is performed by a location-based device under control of device control system (DCS) code (e.g., the code 308 or 408) implemented by at least one processor (e.g., any of the processors 300 or 400 of Figures 3-4C ). The DCS code can include, for example, a camera agent (e.g., the camera agent 138 of Figure 1 ). At least a portion of the process 700 is performed by a base station (e.g., the base station 114 of Figure 1 ) under control of a monitoring client (e.g., the monitoring client 136 of Figure 1 ). At least a portion of the processes 700, 800 is performed by a monitoring center environment (e.g., the monitoring center environment 120 of Figure 1 ) under control of a monitor interface (e.g., the monitor interface 130 of Figure 1 ). At least a portion of the processes 700, 800 is performed by a data center environment (e.g., the data center environment 124 of Figure 1 ) under control of a monitoring service (e.g., the monitoring service 128 of Figure 1 ) or under control of a transport service (e.g., the transport service 126 of Figure 1 ). At least a portion of the processes 700, 800 is performed by a client device (e.g., the client device 122 of Figure 1 ) under control of a client interface (e.g., the client interface 132 of Figure 1 ).

[0082] As discussed above, in examples, the image capture device 500 can acquire ambient light; generate image data frames based on the acquired light; and transmit the frames to the base station 114, the data center environment 124, the monitor interface 130, and / or the customer interface 132 of the customer device 122. In some examples, the sensor assembly 450 of the image capture device 500 is battery powered, such as powered by the battery assembly 414. The image capture device 500 includes a passive infrared (PIR) sensor 462 for detecting motion and at least one imaging sensor (e.g., a camera). The PIR sensor 462 measures changes in the amount of ambient infrared (IR) light radiating from objects in the field of view; however, the PIR sensor 462 does not emit any light. Thus, the PIR sensor 462 can be used to detect motion represented by changes in temperature over time, such as caused by a person, animal, or object moving through the field of view, but the PIR sensor 462 typically does not have sufficient resolution or processing capability to identify the object. Thus, the PIR sensor 462 is suitable for generating a trigger or event for notifying other processing functions of the image capture device 500 that motion was detected in the field of view of the PIR sensor. For example, the PIR sensor 462 can be used to turn on a motion-activated security light and / or cause another, higher resolution imaging sensor (such as in a thermal or visible light camera) to begin recording and processing video.

[0083] As Figure 7 shown, in some examples, the process 700 begins with the customer device 122 sending an arming system signal 704 to the data center environment 124 via, for example, WI-FI, and the data center environment 124 in turn sends a corresponding arming signal 706 to the base station 114 via, for example, WI-FI. In other examples, the process 700 begins with the keypad 108 sending an arming system signal 707 directly to the base station 114 via, for example, RF transmission (e.g., sub-GHz transmission). The signals can be encoded as events transmitted in messages. For example, a user can interact with the customer interface hosted by the customer device 122 (e.g., the customer interface 132 of Figure 1 and Figure 5 the customer interface 132) or the DCS hosted by the keypad 108 to request that a set of location-based devices be armed to provide security to a location.

[0084] Continuing in process 700, base station 114 sends a system armed signal 710 to one or more location-based devices (e.g., one or more security sensors 422, such as image capture device 500) operating in low-power mode 708. Signal 710 may be transmitted directly from the base station to one or more location-based devices via, for example, RF transmission (e.g., sub-GHz transmission). In response to receiving signal 710, one or more location-based devices (e.g., image capture device 500) enter an armed state, where the location-based devices monitor location and report detected events. In some examples, when in the armed state and operating in low-power mode, image capture device 500 keeps PIR sensor 462 and main control unit (MCU) 902 active and system-on-chip (SoC) processor 904 powered down. MCU 902 and SoC 904 are referenced below. Figure 9 Further description was provided.

[0085] Continuing with process 700, once the system is armed, the image capture device 500 initially operates in a first power operating mode (e.g., low-power mode 708). When operating in low-power mode, the image capture device 500 consumes a small amount of power, for example, approximately 1 mA, which increases the overall power efficiency of the image capture device 500. In low-power mode, the PIR sensor 462 within the image capture device 500 monitors motion within the sensor's field of view. For example, a change in object temperature exceeding a threshold sensed by the PIR sensor 462 can indicate motion of a person or object within the field of view. In some examples, the threshold can be adjusted by the user to increase or decrease the sensitivity of the PIR sensor 462 to sense changes in temperature.

[0086] Continuing process 700, the image capture device 500 is configured to detect motion trigger 712 caused by an object 702 (such as a person or object) in the field of view of the PIR sensor 462 when operating in low-power mode. Upon detecting motion trigger 712 caused by object 702, the image capture device 500 enters a second power mode (computer vision (CV) mode 714), which is tailored to enable the image capture device to determine whether object 702 is an actual threat (e.g., a person). In some examples, when entering CV mode 714, the PIR sensor 462 sends a motion detection signal to the MCU 902, which then causes the SoC processor 904 to boot 716 into CV or real-time operating system (RTOS) operating mode 714 and exit low-power mode 708. CV mode 714 is an operating mode in which limited operations are performed in real time, such as image processing (e.g., identifying objects or people in one or more images) and alarm triggering (e.g., generating alarm signals and transmitting alarm signals via radio to a receiving device such as a base station).

[0087] Continuing with process 700, in CV mode 714, SoC processor 904 causes the shutter of the imaging sensor in at least one sensor assembly 450 to open or otherwise activate the imaging sensor, thereby allowing the imaging sensor / camera to obtain one or more image frames (e.g., a video). SoC processor 904 uses an object identification process in CV mode 714 to analyze the one or more image frames to determine whether a person is in the image frames. If SoC processor 904 does not identify a person in the image frames, the imaging sensor / camera returns to an idle state and SoC processor 904 exits CV mode 714, thereby returning image capture device 500 to low power mode 708. However, if SoC processor 904 identifies a person in the image frames, SoC processor 904 notifies MCU 902. MCU 902, in turn, controls RF transceiver (e.g., RF transceiver 404A of Figure 4B and Figure 4C of base station 114 to transmit a motion trigger signal 718 directly to base station 114 (e.g., the motion trigger signal is not transmitted via a WI-FI transceiver or other network access point), which also includes the RF radio used to communicate with image capture device 500. Additionally, SoC processor 904 causes an audible alert 726 to sound via speaker 454 of image capture device 500.

[0088] Continuing with process 700, base station 114 transmits an alert notification 728 to data center environment 124 via the WI-FI transceiver for additional processing. For example, data center environment 124 can generate a notification 730 and transmit the notification to customer device 122. These notifications can be encoded as events within one or more messages. Additionally, in some examples, base station 114 communicates an in-system alert signal 724 to location-based devices installed at its monitored location (e.g., security sensor 422 and / or keyboard 108, if present), thereby placing all of the location-based devices in an alert state.

[0089] Continuing with process 700, if SoC processor 904 identifies a person in the image frames, SoC processor 904 initiates 722 a transition into a third operating mode, a Linux / virtual machine (VM) operating mode 720, which is a time-shared virtual machine executed by SoC processor 904. Time-shared virtual machine mode 720 differs from CV (RTOS) mode 714 in that the time-shared virtual machine non-real-time manages sharing of system resources with a scheduler, data buffers, or fixed task priority ordering in a multitasking or multiprogramming environment, whereas in CV mode 714, the operating system is event-driven and preemptive, meaning that the operating system executes tasks according to their priority rather than based on time.

[0090] Continuing with process 700, in VM mode 720, SoC processor 904 causes at least one image frame of the image frames that includes a person to be uploaded 732 to data center environment 124 via WI-FI transceiver. After the image frame is uploaded, imaging sensor / camera returns to idle state, and SoC processor 904 exits VM mode 720, returning image capture device 500 to low power mode 708. SoC processor 904 informs MCU 902 that SoC processor 904 is idle and that SoC processor 904 is powered down. After resuming low power mode 708, process 700 can end.

[0091] Now turning to Figure 8A and Figure 8B power control process 800 is shown as a sequence diagram. Process 800 can be performed, in some examples, by an image capture device (e.g., image capture device 500 of Figure 4B or image capture device 520 of Figure 4C under control of device control system (DCS) code (e.g., code 408 of Figure 4B or Figure 4C implemented by at least one processor (e.g., processor 400 of Figure 4B or Figure 4C DCS code can include, for example, a camera agent (e.g., camera agent 138 of Figure 1 ).

[0092] As shown in Figure 8A process 800 begins with the image capture device being initially set up 804 as part of its manufacture. For example, manufacturing personnel can interact with the image capture device to assemble, configure, and / or test its operation. As the manufacturing process nears completion, the image capture device can respond to receipt of an input of a designated shutdown request 806 by entering a shipping / transport mode 802. In some examples, the image capture device enters shipping / transport mode 802 by powering down all components and subsystems before they are packaged for shipping.

[0093] Continuing with process 800, the image capture device is removed from its packaging, installed at a monitored location (e.g., monitored location 102A of Figure 1 and set up 808 for operation. In some examples, as part of its setup, the image capture device exits shipping / transport mode 802, enters low power mode 708, and communicates with one or more other location-based devices at the monitored location, such as a base station (e.g., base station 104 of Figure 1The image capture device is paired with the base station 810 or otherwise connected to the base station 114. It should be noted that in some examples, to minimize the power required for device setup 808 and configuration 812, the image capture device communicates directly with the base station via a sub-GHz signal to pair with the base station 810. In these examples, the image capture device configures itself 812 for operation by: enabling human detection 820, enabling alarm triggering 818, and turning on the camera 816 (e.g., ...). Figure 4B or Figure 4C The shutter of the image sensor assembly 450, and the armament 814 itself via the PIR sensor ( Figure 4B or Figure 4C The PIR sensor 462 detects motion.

[0094] Continuing process 800, the image capture device places the camera in an idle state 822 until motion is detected 824 (e.g., via a PIR sensor). In response to motion detection, the image capture device initiates 826 into CV mode 714 and continues referencing... Figure 8B The initial video frame 828 is analyzed to determine whether the motion detected by 830 poses a real threat (e.g., a person). If the image capture device does not detect a person in the video frame, it resets the camera to an idle state 836 and returns to a low-power mode 708. If the image capture device detects a person in the video frame, it sends a trigger signal 832 (e.g., a security event) to the base station, activating an siren 840 (e.g., [missing information]). Figure 4B or Figure 4C The speaker 454), and started 834 into Linux / VM mode 720 where all features and functions of the image capture device are available.

[0095] Continuing process 800, the image capture device receives a system-wide alarm signal 838 from the base station. This alarm signal can be transmitted and received via a sub-GHz signal through a transceiver configured for this type of communication. In response to the reception of the alarm signal, the image capture device uploads video frames 842 to a remote device (e.g., in…). Figure 1 Within the data center environment 124) for subsequent processing (e.g., outlining / reducing and transmitting to client devices, such as Figure 1 (Client device 122). After the system alarm is resolved, the image capture device resets the camera 844 to the idle state, returns to the low power mode 708, and the process 800 can end.

[0096] Now go to Figure 9 A block diagram of a battery-powered image capture device 500 / 520 is shown. Figure 9 The device 500 / 520 shown includes Figure 4B orFigure 4C The sensor assembly 450 Figure 4B or Figure 4C The PIR sensor 462. Further, in this example, the device 500 / 520 further includes an MCU 902 and a SoC 904. In some examples, the MCU 902 is or includes a low-power microcontroller with multiple interrupts (e.g., an STM32 microcontroller available from STMicroelectronics in Geneva, Switzerland), which is configured to receive signals from, for example, the PIR sensor 462, a user interface (e.g., ...). Figure 4A The user interface 412) button or some other manually optional element, one or more wake signals of a locally implemented timer, or via a network interface (e.g., Figure 4B or Figure 4C The wake-up signal is received by the network interface 404. In some examples, the SoC 904 includes a system-on-a-chip (e.g., the Vi37M SoC available from iCatch in Hsinchu, Taiwan) with memory (e.g., 1 gigabyte or more) and one or more processing cores with processing power (e.g., speed of 1 GHz or more) sufficient to function as attributed to the processor 400 described herein. Figure 9 As shown, MCU 902 is configured to perform operations 810 and 816 in low-power mode 708. SoC 904 is then configured to perform operations 906 to 912, which are further described below.

[0097] As noted above, the PIR sensor 462 and the MCU 902 can operate in the low power mode 708, but can lack sufficient image resolution and image processing capabilities, respectively, to identify objects (such as people) in the field of view. Thus, the image capture device 500 / 520 includes additional components, such as the SoC processor 904, to perform object identification and other tasks. However, the SoC processor 904 consumes additional power when powered on and active. As noted above, in operation, the PIR sensor 462 can output a motion detection signal to the MCU 902 indicating that motion has been detected in response to a positive motion detection result. The signal from the PIR sensor 462 causes the MCU 902 to power on the SoC processor 904, which then initiates into the CV operating mode 714. During the CV mode 714, the image capture device 500 / 520 consumes more power than during the low power mode 708, but less power than during the Linux / VM mode 720. For example, in some examples, the image capture consumes approximately 250 mA when operating in the CV mode, at least in part because the SoC processor 904 is powered on and active in the CV mode 714, but is powered off and idle in the low power mode 708.

[0098] Continuing Figure 9 In the illustrated example, the SoC 904 is configured to determine 906 whether the CV mode 714 is enabled or disabled. For example, the SoC 904 can determine 906 that the CV mode 714 is enabled for execution by determining that a value of a configurable parameter stored in memory is set to a first value (e.g., a predetermined value), and can determine that the CV mode 714 is disabled by determining that the value is set to a second value (e.g., another predetermined value). If the SoC 904 determines 906 that the CV mode 714 is disabled, the SoC 904 initiates 914 into the VM mode 720, such that further processing of image data (e.g., person detection by code executing within a virtual machine or any of the VM mode processes described above) can be performed. If the SoC 904 determines 906 that the CV mode 714 is enabled, the SoC initiates into the CV mode 714, which allows for limited processing of video frames, and continues to operation 908.

[0099] Continuing Figure 9The example shown, SoC 904 is configured to analyze 908 an initial video frame to determine whether an image within the video frame depicts a threat (e.g., a person). For example, in some examples, SoC 904 applies a YOLO person detection process to the initial video frame to determine whether the image depicts a person. In some examples, SoC 904 is further configured to determine 910 whether operation 908 produces a positive threat assessment or a negative threat assessment. If SoC 904 determines that operation 908 produces a positive assessment, SoC 904 initiates into VM mode 720 so that further processing of the image data (e.g., threat detection by code executing within a virtual machine or any of the VM mode processes described above) can be performed. If SoC 904 determines that operation 908 produces a negative assessment, SoC 904 notifies MCU 902 that there is no threat and powers down, exiting CV mode 714 and entering low power mode 708.

[0100] Turning now to Figure 10 , a process 1000 for quickly and efficiently processing potential security events is shown as a flowchart. In some examples, process 1000 is performed by a battery-powered image capture device (e.g., image capture device 500 of Figure 4B or image capture device 520 of Figure 4C ) under the control of a camera agent (e.g., camera agent 138 of Figure 1 , or code 408 of Figure 4B or Figure 4C .

[0101] As shown in Figure 10 , process 1000 begins with the image capture device initiating 1002 a first mode of operation. For example, in some examples, the image capture device enters a low power mode of operation (e.g., low power mode 708 of Figure 7 ), in which the image capture device performs operations 808, 812, and 822 described above with reference to Figure 8A . As a result of these operations, the image capture device is installed, configured, and ready to monitor a field of view within a location (e.g., location 102A of Figure 1 ). As discussed above, when operating in the low power mode, the image capture device can consume 1 mA or less of battery power. In some examples, the low power mode is implemented using a microprocessor (e.g., MCU 902 of Figure 9 ) that monitors one or more wake-up signals from various potential sources, including a motion detector (e.g., PIR sensor 462 of Figure 4B or Figure 4C .

[0102] Continuing with process 1000, the image capture device detects 1004 motion within the field of view. For example, in some examples, a PIR sensor detects a change in infrared radiation originating from the field of view and, as a result, transmits a wake-up signal to the microprocessor.

[0103] Continuing with process 1000, the image capture device initiates 1006 a second operating mode. For example, in some examples, the image capture device enters a CV operating mode (e.g., CV mode 714 of FIG. 7) in which the image capture device executes an RTOS to support the execution of operations 1008-1016 and 1026 as described below. As discussed above, when operating in the CV mode, the image capture device can consume approximately 250 mA of battery power. In some examples, the CV mode is implemented using a SoC (e.g., SoC 904 of FIG. 9) that executes in a reduced power mode that is natively supported by the SoC. Figure 7 Figure 9

[0104] Continuing with process 1000, the image capture device acquires 1008 an image of the field of view of the image capture device. For example, in some examples, the image capture device acquires the image via an image sensor housed within an image sensor assembly (e.g., image sensor assembly 450 of FIG. 7). Figure 4B or Figure 4C

[0105] Continuing with process 1000, the image capture device analyzes 1010 the image to determine whether the image depicts a person. For example, in some examples, the SoC performs operation 908 described above with reference to FIG. 9. It should be noted that, within operation 1010, the SoC executes the process under the control of an RTOS rather than a multi-tasking operating system that implements one or more virtual machines. Figure 9

[0106] Continuing with process 1000, as a result of operation 1010, the image capture device determines 1012 whether a person was detected. For example, in some examples, the SoC makes this determination and, if a person was detected, proceeds to operation 1014. In these examples, if the SoC did not detect a person, the SoC proceeds to operation 1026. Within operation 1026, the image capture device returns to the first operating mode and proceeds to operation 1004. For example, in some examples, within operation 1026, the SoC returns the camera to an idle state and powers down the SoC.

[0107] Continuing with process 1000, the image capture device initiates 1014 a system-wide alert. For example, in some examples, the SoC directly transmits an alert to another location-based device (e.g., a PIR sensor of FIG. 1). Figure 1 ​​​​the base station 114) transmits the message. It should be noted that in some examples, such transmission occurs via a sub-GHz wireless channel, while the SoC is under control of an RTOS rather than a multi-tasking operating system. This is important in the context of a battery-operated image capture device, as the SoC boots up much faster under an RTOS than a multi-tasking operating system, and consumes less power while running an RTOS than when running a multi-tasking operating system. As a result, the transmission occurs faster, and consumes less power when performed under an RTOS than it would if performed under a multi-tasking operating system.

[0108] Continuing with the process 1000, the image capture device initiates 1016 a siren. For example, in some examples, the SoC causes the siren to sound via a speaker (e.g., Figure 4B or Figure 4C the speaker 454) incorporated into the image capture device.

[0109] Continuing with the process 1000, the image capture device initiates 1018 a third operating mode. For example, in some examples, the image capture device enters a VM operating mode (e.g., Figure 7 the VM mode 720) in which the image capture device executes a multi-tasking operating system to support performance of operations 1020-1024 as described below. As discussed above, when operating in the VM mode, the image capture device can consume approximately 350 mA of battery power. In some examples, the VM mode is implemented using the SoC (e.g., Figure 9 the SoC 904) that executes in a normal power mode natively supported by the SoC. It should be noted that such a normal power mode is specific to the SoC. The normal power mode of the SoC facilitates VM mode operation of the image capture device.

[0110] Continuing with the process 1000, the image capture device processes 1020 confirmation of the system-wide alert. For example, in some examples, the SoC receives a message (e.g., Figure 4B or Figure 4C the alert signal 724) from a different device (e.g., a location-based device or a remote device) via the network interface (e.g., Figure 7 the network interface 404) that confirms the system-wide alert initiated in operation 1014. In response to receipt of the message, the SoC can transmit a message via the network interface that confirms receipt of the message.

[0111] Continuing with the process 1000, the image capture device uploads 1022 a record that includes the image acquired in operation 1010 and other images acquired while the system-wide alert is ongoing. For example, in some examples, the SoC packages and transmits via the network interface to another location-based device or a remote device (e.g., Figure 1 the customer device 122 or the remote server 124) residing on a network (e.g., the network 130) to which the image capture device is coupled.Figure 1 The device in the monitoring center 120 transmits video files or other records including images.

[0112] Continuing process 1000, the image capture device returns to the first operating mode at 1024 and continues to operation 1004. For example, in some examples, within operation 1024, the SoC returns the camera to an idle state and shuts down the SoC.

[0113] Now go to Figure 11 The computing device 1100 is illustrated schematically. For example... Figure 11 As shown, the computing device includes at least one processor 1102, volatile memory 1104, one or more interfaces 1106, non-volatile memory 1108, and interconnect mechanism 1114. The non-volatile memory 1108 includes code 1110 and at least one data storage 1112.

[0114] In some examples, the non-volatile (non-transitory) memory 1108 includes: one or more read-only memory (ROM) chips; one or more hard disk drives or other magnetic or optical storage media; one or more solid-state drives (SSDs), such as flash drives or other solid-state storage media; and / or one or more hybrid magnetic and SSDs. In some examples, code 1110 stored in the non-volatile memory may include an operating system and one or more applications or programs configured to execute under the operating system. Alternatively or additionally, code 1110 may include specialized firmware and embedded software executable without relying on a commercially available operating system. In any case, execution of code 1110 may produce manipulation data, which may be stored in data storage 1112 as one or more data structures. The data structures may have fields associated through co-location within the data structures. Such associations can also be implemented by allocating storage for fields in locations within memory that pass associations between fields. However, other mechanisms may be used to establish associations between information in fields of a data structure, including by using pointers, tags, or other mechanisms.

[0115] continue Figure 11In examples, the processor 1102 can be one or more programmable processors to execute one or more executable instructions, such as a computer program designated by the code 1110, to control operations of the computing device 1100. As used herein, the term "processor" describes circuitry that performs a function, an operation, or a sequence of operations. The function, operation, or sequence of operations can be hard coded into the circuitry or soft coded by way of instructions saved in a memory device, such as the volatile memory 1104, that are executed by the circuitry. In some examples, the processor 1102 is a digital processor, but the processor 1102 can be analog, digital, or mixed-signal. Thus, the processor 1102 can perform a function, operation, or sequence of operations using digital values and / or using analog signals. In some examples, the processor 1102 can be embodied in one or more application specific integrated circuits (ASICs), microprocessors, digital signal processors (DSPs), graphics processing units (GPUs), neural processing units (NPUs), microcontrollers, field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), or multi-core processors. Examples of multi-core processors 1102 can provide functionality for parallel, simultaneous execution of instructions or for parallel, simultaneous execution of one instruction on more than one data.

[0116] Continuing Figure 11 In examples, prior to execution of the code 1110, the processor 1102 can copy the code 1110 from the non-volatile memory 1108 to the volatile memory 1104. In some examples, the volatile memory 1104 includes one or more static or dynamic random access memory (RAM) chips and / or cache memory (e.g., memory disposed on a silicon die of the processor 1102). The volatile memory 1104 can provide faster response times than a main memory, such as the non-volatile memory 1108.

[0117] Through execution of the code 1110, the processor 1102 can control operations of the interface 1106. The interface 1106 can include network interfaces. These network interfaces can include one or more physical interfaces (e.g., radios, Ethernet ports, USB ports, etc.) and a software stack including drivers and / or other code 1110 configured to communicate with the one or more physical interfaces to support one or more LAN, PAN, and / or WAN standard communication protocols. The communication protocols can include, for example, TCP and UDP, among others. Thus, the network interfaces enable the computing device 1100 to access and communicate with other computing devices via a computer network.

[0118] The interface 1106 can include a user interface. For example, in some examples, the user interface includes user input and / or output devices (e.g., a keyboard, a mouse, a touchscreen, a display, a speaker, a camera, an accelerometer, a biometric scanner, an environmental sensor, etc.) and a software stack including drivers and / or other code 1110 configured to communicate with the user input and / or output devices. Thus, the user interface enables the computing device 1100 to interact with a user to receive input and / or present output. The presented output can include, for example, one or more GUIs including one or more controls configured to display output and / or receive input. The input can specify values to be stored in the data store 1112. The output can indicate values stored in the data store 1112.

[0119] Continuing Figure 11 In examples of the computing device 1100 described above, various features can communicate with one another via the interconnection mechanism 1114. In some examples, the interconnection mechanism 1114 includes a communication bus.

[0120] Various inventive concepts can be embodied as one or more methods, of which an example has been provided. The acts performed as part of the method can be ordered in any suitable way. Accordingly, examples can be constructed in which acts are performed in an order different than illustrated, which can include performing some acts simultaneously, even though shown as being performed sequentially by virtue of being included in the same example.

[0121] Additional examples are described below. Other variations will be apparent to those of ordinary skill in the art based on the disclosure.

[0122] Example 1 is a method comprising: in response to receiving a signal from a sensor of a device configured to detect motion within a field of view, causing, by a controller of the device, at least one processor of the device different from the controller to power on; analyzing, by the at least one processor, one or more images from an image sensor of the device to identify an image of a person; in response to the identification of the image of the person, transmitting, by the at least one processor, a trigger to a base station; and initiating, by the at least one processor, a multi-tasking operating system of the device after transmitting the trigger to the base station.

[0123] Example 2 includes the subject matter of Example 1, and further includes initiating, by the at least one processor, a real-time operating system prior to receiving the one or more images; and uploading, by the at least one processor, the one or more images to a remote computing environment via the multi-tasking operating system.

[0124] Example 3 includes the subject matter of Example 2, wherein the one or more images are uploaded to the remote computing environment via a WI-FI transceiver after initiating the multi-tasking operating system.

[0125] Example 4 includes the subject matter of any one of Examples 1-3, and further comprising sounding an audible alarm by the at least one processor.

[0126] Example 5 includes the subject matter of any one of Examples 1-4, and further comprising transmitting, by the sensor, a signal to the controller while the apparatus is operating in a low power mode in which the at least one processor is powered off to conserve power.

[0127] Example 6 includes the subject matter of any one of Examples 1-5, and further comprising causing, by the controller, the image sensor to acquire one or more images in response to receiving the signal and while operating in the low power mode in which the at least one processor is powered off.

[0128] Example 7 includes the subject matter of any one of Examples 1-7, wherein transmitting the trigger comprises transmitting the trigger directly to the base station via a radio prior to starting the multi-tasking operating system.

[0129] Example 8 is an apparatus comprising: a motion sensor; an image sensor; at least one processor; and a controller different from the at least one processor and configured to power on the at least one processor in response to receiving a signal from the motion sensor, wherein the at least one processor is operably coupled to the controller and the image sensor and configured to: analyze one or more images from the image sensor to identify an image of a person, transmit a trigger to a base station in response to identifying the image of the person, and start a multi-tasking operating system of the apparatus after transmitting the trigger to the base station.

[0130] Example 9 includes the subject matter of Example 8, wherein the at least one processor is further configured to start a real-time operating system prior to receiving the one or more images; and upload the one or more images to a remote computing environment via the multi-tasking operating system.

[0131] Example 10 includes the subject matter of Example 9, wherein uploading comprises uploading to the remote computing environment via a WI-FI transceiver after starting the multi-tasking operating system.

[0132] Example 11 includes the subject matter of any one of Examples 8-10, wherein the at least one processor is further configured to sound an audible alarm.

[0133] Example 12 includes the subject matter of any one of Examples 8-11, wherein the motion sensor is configured to detect motion represented by a change in temperature over time within a field of view of the motion sensor.

[0134] Example 13 includes the subject matter according to any one of Examples 8 to 12, wherein the motion sensor is further configured to send a signal to the controller when the device is operating in a low-power mode where at least one of the processors is powered down to conserve power.

[0135] Example 14 includes the subject matter according to any one of Examples 8 to 13, wherein the controller is further configured to: in response to receiving a signal and when the device is operating in a low-power mode in which at least one of its processors is powered off, cause the image sensor to acquire one or more images.

[0136] Example 15 includes the subject matter described in any of Examples 8 to 14, wherein sending the trigger includes sending the trigger directly to the base station via radio before the multitasking operating system is started.

[0137] Example 16 includes the subject matter described in any one of Examples 8 to 15, wherein the motion sensor includes a passive infrared sensor.

[0138] Example 17 is a method comprising: detecting motion of an object by means of a battery-powered device; processing one or more images by means of the device in response to the detection of motion; providing a radio frequency (RF) signal by means of the device to a security system, the RF signal being configured to cause the security system to enter an alarm state; and activating the device's operating system after the RF signal is provided to the security system to enable the device to perform security operations.

[0139] Example 18 includes the subject matter described in Example 17, wherein processing one or more images includes using the images to identify objects as people.

[0140] Example 19 includes the subject matter described in Example 17 or Example 18, wherein the operating system includes a multitasking operating system.

[0141] Example 20 includes the subject matter described in any of Examples 17 through 19, wherein a secure operation includes uploading one or more images to a remote device.

[0142] The use of ordinal terms such as "first," "second," "third," etc., in claims to modify claim elements does not in itself imply any priority, precedence, or order of a claim element over another, or the chronological order of actions of a method. Such terms are merely labels to distinguish one claim element with a certain name from another element with the same name (but using ordinal terms).

[0143] The examples of the methods and systems discussed herein are not limited in application to the details of construction and the arrangement of components set forth in the following description or illustrated in the accompanying drawings. The methods and systems are capable of implementation in other examples and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, components, elements and features discussed in connection with any one or more examples are not intended to be excluded from a similar role in any other examples.

[0144] Moreover, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Any references to examples, components, elements or acts that are described in singular form are not intended to be limited to single instances but can encompass single or plural instances, unless otherwise indicated. References in this document to "one or more" examples, components, elements or acts, means that such examples, components, elements or acts can be implemented in, and are applicable to, a single instance or plurality of instances. The word "or" as used herein in a phrase such as "A or B" does not exclude the presence of A and B both. Additionally, the use of "including", "containing", "comprising", "having" and "involving" and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. References to "or" can be construed as inclusive so that any terms described using "or" can indicate a single, multiple or all of the described terms. In case of inconsistent usages of terms between this document and documents incorporated herein by reference, the term usage in the incorporated reference is

[0145] Having described several examples, one skilled in the art will be aware that modifications and variations are possible in light of the above teachings. Such modifications and variations are intended to fall within the scope of the disclosure. Accordingly, the foregoing description is by way of example only, and is not intended to be limiting.

Claims

1. A method comprising: In response to receiving a signal from a sensor configured to detect motion within the field of view, the controller of the device powers on at least one processor of the device that is different from the controller. The at least one processor analyzes one or more images from the image sensor of the device to identify images of people; In response to the identification of the image of the person, the at least one processor sends a trigger to the base station; as well as The multitasking operating system of the device is started by the at least one processor after sending the trigger to the base station.

2. The method of claim 1, further comprising: The real-time operating system is started by the at least one processor before receiving the one or more images; as well as The one or more images are uploaded to a remote computing environment by the at least one processor via the multitasking operating system.

3. The method according to claim 2, wherein after the multitasking operating system is started, the one or more images are uploaded to the remote computing environment via a Wi-Fi transceiver.

4. The method according to any one of claims 1 to 3, further comprising emitting an audible alarm by the at least one processor.

5. The method according to any one of claims 1 to 4, further comprising sending the signal from the sensor to the controller while the device is operating in a low-power mode in which the at least one processor is powered off to save power.

6. The method according to any one of claims 1 to 5, further comprising, in response to receiving the signal and when operating in a low-power mode in which the at least one processor is powered down, causing the image sensor to acquire the one or more images by the controller.

7. The method according to any one of claims 1 to 6, wherein sending the trigger comprises sending the trigger directly to the base station via radio before starting the multitasking operating system.

8. An apparatus comprising: Motion sensor; Image sensor; At least one processor; and A controller, distinct from the at least one processor and configured to power on the at least one processor in response to receiving a signal from the motion sensor, wherein the at least one processor is operatively coupled to the controller and the image sensor and configured to: Analyze one or more images from the image sensor to identify images of people. In response to the identification of the image of the person, a trigger is sent to the base station, and The device's multitasking operating system is started after the trigger is sent to the base station.

9. The apparatus of claim 8, wherein the at least one processor is further configured to: Start the real-time operating system before receiving the one or more images; and The one or more images are uploaded to a remote computing environment via the multitasking operating system.

10. The apparatus of claim 9, wherein uploading includes uploading to the remote computing environment via a Wi-Fi transceiver after the multitasking operating system is started.

11. The apparatus according to any one of claims 8 to 10, wherein the at least one processor is further configured to cause an audible alarm to sound.

12. The apparatus according to any one of claims 8 to 11, wherein the motion sensor is configured to detect motion within the field of view of the motion sensor, represented by a change in temperature over time.

13. The apparatus according to any one of claims 8 to 12, wherein the motion sensor is further configured to send the signal to the controller when the apparatus is operating in a low-power mode in which the at least one processor is powered off to save power.

14. The apparatus according to any one of claims 8 to 13, wherein the controller is further configured to: in response to receiving the signal and when the apparatus is operating in a low-power mode in which the at least one processor is powered off, cause the image sensor to acquire the one or more images.

15. The apparatus according to any one of claims 8 to 14, wherein sending the trigger comprises sending the trigger directly to the base station via radio before starting the multitasking operating system.

16. The apparatus according to any one of claims 8 to 15, wherein the motion sensor comprises a passive infrared sensor.

17. A method comprising: The movement of an object is detected by a battery-powered device; In response to the detection of the motion, the device processes one or more images; The device provides a radio frequency (RF) signal to the security system, the RF signal being configured to put the security system into an alarm state; as well as The device's operating system is activated after the device provides the RF signal to the security system, enabling the device to operate securely.

18. The method of claim 17, wherein processing the one or more images includes using the images to identify the object as a person.

19. The method of claim 17 or claim 18, wherein the operating system comprises a multitasking operating system.

20. The method according to any one of claims 17 to 20, wherein the security operation includes uploading the one or more images to a remote device.

Images