Virtual partitioning of security systems

Abstract

A security system identifies sensors that communicate with the security system, and a partition attribute of each sensor is identified. The partition attribute of each sensor identifies one or more partitions of the security system. The security system forms partitions based on the partition attributes.

Description

[0001] Priority claim

[0002] This application claims priority to U.S. Non-Provisional Application No. 16 / 289,400, filed on February 28, 2019, entitled “Virtual Partition of a Security System” (Attorney Docket No. 5986.264US1) and is incorporated herein by reference in its entirety.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application is related to co-pending US Patent Application No. 16 / 289,437, entitled "Dynamic partition for security system" (Attorney Docket No. 5986.265US1) and is hereby incorporated by reference in its entirety. Background Art

[0005] Home security systems can be used to notify homeowners of intrusions and other alarms (e.g., a porch light left on all night). These security systems communicate with sensors placed throughout a facility (e.g., home, office). However, the hardware setup on these security systems limits the number of zones available. Therefore, a homeowner who wishes to add another zone to monitor his family's in-law unit may need to purchase another security system that can monitor both zones. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] To easily identify the discussion of any particular element or activity, the most significant digit(s) in a reference number refers to the figure number in which the element is first introduced.

[0007] Figure 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, in accordance with some example implementations.

[0008] Figure 2 is a block diagram illustrating an embodiment of a security system in accordance with one example implementation.

[0009] Figure 3 Components of a security system according to one example implementation are illustrated.

[0010] Figure 4 Components of a security system according to another example implementation are shown.

[0011] Figure 5 Components of a virtual partition module are illustrated in accordance with one example implementation.

[0012] Figure 6 An example of partitioning of a security system according to one example implementation is illustrated.

[0013] Figure 7 An example of partitioning of a security system according to another example implementation is shown.

[0014] Figure 8 is a block diagram illustrating the operation of a security system in accordance with one example implementation.

[0015] Fig. 9 is a flow chart illustrating a method for generating a user interface for each partition according to an embodiment implementation.

[0016] Fig.10 is a flow chart illustrating a method for providing a user interface for each partition to a control panel in accordance with an embodiment implementation.

[0017] Fig.11 is a flow chart illustrating a method for providing notifications to a control panel in accordance with one example implementation.

[0018] Fig.12 A routine according to one embodiment is illustrated.

[0019] Fig.13 is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein, according to an example implementation. DETAILED DESCRIPTION

[0020] "Component" refers to a device, physical entity or logic with boundaries defined by partitioned or modularized functions or subroutine calls, branch points, APIs or other technologies for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processes. A component can be a packaged functional hardware unit designed for use with other components and a part of a program that generally performs a specific function in a related function. A component can constitute a software component (e.g., a code embodied on a machine-readable medium) or a hardware component. "Hardware component" is a tangible unit that can perform certain operations and can be configured or arranged in a certain physical manner. In various embodiments, one or more computer systems (e.g., an independent computer system, a client computer system or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors 1004) can be configured by software (e.g., an application 916 or an application part) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. For example, a hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include a programmable logic or circuit system that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of the machine 1000) that is uniquely customized to perform the configured function, rather than a general-purpose processor 1004. It should be appreciated that the decision to implement the hardware component mechanically, in a dedicated and permanently configured circuit system, or in a temporarily configured circuit system (e.g., configured by software) can be driven by cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner or perform certain operations described herein. Considering an embodiment in which the hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as respectively different special-purpose processors (e.g., including different hardware components) at different times. The software thus configures one or more specific processors, for example, to constitute a specific hardware component at one time and to constitute different hardware components at different times. Hardware components are capable of providing information to other hardware components and receiving information from other hardware components. Thus, the described hardware components can be considered to be communicatively coupled.When multiple hardware components exist simultaneously, communication between or among two or more of the hardware components can be achieved by signal transmission (e.g., by appropriate circuits and buses). In embodiments where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing and retrieving information in a memory structure that multiple hardware components can access. For example, a hardware component can perform an operation and store the output of that operation in a memory device, to which the hardware component is communicatively coupled. Then, another hardware component can subsequently access the memory device to retrieve and process the stored output. The hardware component can also initiate communication with an input or output device, and can operate on a resource (e.g., a collection of information). The various operations of the embodiment methods described herein may be performed at least in part by one or more processors, which are temporarily configured (e.g., configured by software) or permanently configured to perform related operations. Whether temporarily or permanently configured, such processors may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described herein can be at least partially processor-implemented, wherein one or more specific processors are embodiments of hardware. For example, at least some of the operations of the method can be performed by one or more processors 1004 or components implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS). For example, at least some of the operations can be performed by a group of computers (as an embodiment of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). Some of the executions in the operations can be distributed among the processors, not only residing in a single machine, but also deployed across many machines. In some example embodiments, the processor or the component implemented by the processor can be located in a single geographical location (e.g., in a home environment, an office environment, or a server cluster). In other example embodiments, the processor or the component implemented by the processor can be distributed across many geographical locations.

[0021] "Communications network" means one or more portions of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a Plain Old Telephone Service (POTS) network, a cellular telephone network, a wireless network, The coupling may be a network, another type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless or cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this embodiment, the coupling may implement any of various types of data transfer technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other standards defined by various standards development organizations, other remote protocols, or other data transfer technologies.

[0022] "Machine storage medium" refers to a single or multiple storage devices and / or media (e.g., centralized or distributed databases, and / or associated caches and servers) that store executable instructions, routines, and / or data. The term should therefore be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific embodiments of machine storage media, computer storage media, and / or device storage media include non-volatile memory, including semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices as embodiments; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium", "device storage medium", and "computer storage medium" mean the same thing and are used interchangeably in this disclosure. The terms "machine storage medium", "computer storage medium", and "device storage medium" specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term "signal media".

[0023] A "processor" refers to any circuit or virtual circuit (a physical circuit simulated by logic executed on an actual processor) that manipulates data values ​​according to control signals (e.g., "commands," "opcodes," "machine codes," etc.) and produces corresponding output signals that are applied to operate a machine. A processor may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), or any combination thereof. A processor may also be a multi-core processor having two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously.

[0024] "Carrier signal" refers to any intangible medium that is capable of storing, encoding or carrying instructions for execution by a machine, and includes digital or analog communications signals or other intangible media used to facilitate communication of such instructions. Instructions may be transmitted or received over a network via a network interface device using a transmission medium.

[0025] "Signal media" refers to any intangible medium that is capable of storing, encoding or carrying instructions for execution by a machine, and includes digital or analog communication signals or other intangible media used to facilitate communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed so as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and are used interchangeably in this disclosure.

[0026] "Computer-readable media" refers to both machine storage media and transmission media. Thus, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable media," "computer-readable media," and "device-readable media" mean the same thing and are used interchangeably in this disclosure.

[0027] Embodiment methods and systems relate to the partitioning of security systems. The embodiments represent possible variations only. Unless otherwise expressly stated, components and functions are optional and may be combined or subdivided, and operations may be varied in sequence or combined or subdivided. In the following description, for the purpose of explanation, many specific details are set forth to provide a thorough understanding of the embodiment implementation. However, it will be apparent to those skilled in the art that the subject matter may be practiced without these specific details.

[0028] A homeowner (and user of a security system) may want two separate zones for their property: one for their house and another for their garage. In another example, a company may want dozens of zones to monitor the security of a row of locked cabinets in a laboratory. Some security systems may not dynamically increase or decrease the number of zones because those security systems are hardwired for a preset number of static zones.

[0029] The present application describes a method for dynamically partitioning a security system. In one example implementation, a security system identifies a plurality of sensors in communication with the security system; identifies a partition attribute for each of the plurality of sensors, the partition attribute indicating one or more partitions of the security system for a corresponding sensor of the plurality of sensors; and forms a plurality of partitions of the security system based on the partition attributes of the plurality of sensors. In another example implementation, a hardwired security system having a statically preset number of partitions can dynamically adjust the number of virtual partitions.

[0030] Figure 1 is a diagrammatic representation of a network environment 100 in which some example implementations of the present disclosure may be implemented or deployed.

[0031] One or more application servers 104 provide server-side functionality to networked user devices in the form of a security system 130 and client devices 106 of users 128 via the network 102. The security system 130 includes a control panel (not shown) connected to sensors in a home 132 of the user 128. A web client 110 (e.g., a browser) and a programmatic client 108 (e.g., an "app") are hosted and executed on the client device 106. The client device 106 can communicate with the security system 130 via the network 102 or communicate with the security system 130 via other wireless or wired means.

[0032] Application program interface (API) server 118 and web server 120 provide respective programming interfaces and web interfaces to application server 104. Particular application server 116 hosts remote security monitoring application 122 that operates with security system 130. In one embodiment, remote security monitoring application 122 receives alerts from sensors of security system 130, identifies the zone associated with the alert, and delivers the alert to a mobile device (or control panel) associated with the zone.

[0033] The web client 110 communicates with the remote security monitoring application 122 via a web interface supported by the web server 120. Similarly, the programmatic client 108 communicates with the remote security monitoring application 122 via a programmatic interface provided by an application program interface (API) server 118. For example, the third party application 114 can be a topology application that determines the topology of a factory (e.g., how many cabinets, rooms, which rooms contain valuables), a building, an apartment complex, or a community. The application server 116 is shown as being communicatively coupled to a database server 124, which facilitates access to an information repository or database 126. In an example embodiment, the database 126 includes a storage device that stores information to be published and / or processed by the remote security monitoring application 122.

[0034] Additionally, a third-party application 114 executing on the third-party server 112 is shown as being able to programmatically access the application server 116 via a programming interface provided by an application program interface (API) server 118. For example, the third-party application 114 can support one or more features or functions on a website hosted by a third party using information retrieved from the application server 116. In one embodiment, the third-party server 112 communicates with another remote control device (e.g., a smart door lock) located at the home 132. The third-party server 112 provides the door lock status to the security system 130, the client device 106, or the application server 116. In another embodiment, the security system 130, the client device 106, and the application server 116 are able to control the door lock via the third-party application 114.

[0035] Figure 2 2 is a block diagram illustrating an embodiment of a system 200 in a home according to an example implementation. Home 132 includes, for example, user 128 and security system 130. Security system 130 is connected to sensors and remote control devices. Sensors may include sensor devices (e.g., camera 202, temperature sensor 204) and remote control devices (e.g., door lock 206, speaker 208). One of ordinary skill in the art will recognize that other types of sensors (other than Figure 2 Sensors other than those shown) may be connected to the security system 130 .

[0036] The security system 130 (although hardwired to operate with one partition) can be partitioned to operate as two virtual security systems. For example, the security system 130 forms two partitions: partition A 210 and partition B 212. Partition A 210 includes a camera 202 and a temperature sensor 204. Partition B 212 includes a speaker 208 and a door lock 206. One of ordinary skill in the art will recognize that the partitions can include a combination of any of the sensors and devices. For example, partition B 212 can also include a temperature sensor 204 (which is also part of partition A 210).

[0037] The security system 130 can be configured to operate two partitions simultaneously by receiving sensor data from the corresponding sensors and controlling the sensors corresponding to the partitions. In another embodiment, the security system 130 can enable the user 128 to operate only the partition A 210 and enable another user to operate only the partition B 212 (based on the access rights of the user 128).

[0038] Figure 3 Components of a security system according to an example implementation are illustrated. The security system 130 includes a sensor interface 302, a virtual partition module 304, a user interface module 306, and a control panel 308. The security system 130 communicates with sensors 310 disposed in a physical facility (e.g., a home, a building, a factory, a campus) via the sensor interface 302. For example, the sensor interface 302 identifies the sensor 310 and accesses sensor data from the sensor 310. In one embodiment, the sensor 310 is registered with the security system 130.

[0039] In one example implementation, sensor interface 302 identifies a zone attribute for each of sensors 310. For example, a zone attribute for a sensor identifies one or more specific zones to which the sensor is assigned. In another example, a zone attribute for a security-related sensor (e.g., a smoke sensor) identifies all zones of security system 130. In another example, a zone attribute for a sensor may be set to identify all zones of security system 130 by default. In another example, a zone attribute for a sensor may be set to identify a zone of security system 130 based on the location of the sensor (e.g., a sensor at a home would be assigned to a home zone).

[0040] The virtual partition module 304 forms one or more partitions based on the partition attributes of the sensor 310. For example, the virtual partition module 304 forms a first partition for a first sensor and a second sensor in the sensor 310. The first sensor and the second sensor each include a partition attribute that identifies the first partition. The virtual partition module 304 forms a second partition based on a third sensor and a fourth sensor in the sensor 310. The second sensor and the third sensor each include a partition attribute that identifies the second partition.

[0041] The user interface module 306 generates a user interface for each zone based on the sensors identified in the corresponding zone. In one embodiment, the user interface can identify the name of the zone, a description of the zone, the sensors in the zone, the sensor status, and the authorized users who can access the zone (e.g., tenants who can access sensor data from sensors in their apartments and landlords who can access sensor data from sensors in the building). This allows both tenants and landlords to use a single security system 130 with different zones.

[0042] The control panel 308 includes a display and user inputs that enable the user 128 to control features of the security system 130 corresponding to the partitions. For example, the user 128 can use the control panel 308 to arm a first partition and disarm a second partition. In another embodiment, the control panel 308 identifies the user 128 and provides the user 128 with access to the corresponding partitions (e.g., one partition at a time or several partitions at a time). In another embodiment, the control panel 308 can be a virtual control panel accessed via the client device 106 or a computing device registered with the security system 130. For each partition, the control panel 308 receives a different user interface from the user interface module 306.

[0043] Figure 4 Components of a security system according to another embodiment are illustrated. The user interface module 306 generates a user interface for each zone based on the zone attributes of the sensor. The user interface module 306 delivers user interfaces corresponding to the control panel A 402 and the control panel B 404. The control panel A 402 and the control panel B 404 are external to the security system 130 and communicate with the security system 130. For example, the security system 130 may be located in the basement of an apartment building, while the control panel A 402 is located in the first apartment of the apartment building and the control panel B 404 is located in the second apartment of the apartment building.

[0044] In one example implementation, the user interface module 306 determines that the first user interface for the first partition refers to control panel A 402. The user interface module 306 then communicates the first user interface and the sensor data of the sensors of the partition corresponding to the first user interface to control panel A 402. The user interface module 306 determines that the second user interface for the second partition refers to control panel B 404. The user interface module 306 then communicates the second user interface and the sensor data of the sensors of the partition corresponding to the second user interface to control panel B 404.

[0045] Control panel A 402 includes a display and user inputs that enable a user at control panel A 402 to control features of security system 130. For example, a user may control features corresponding to a first zone at control panel A 402. Control panel B 404 includes a display and user inputs that enable a user at control panel B 404 to control features of security system 130. For example, a user may control features corresponding to a first zone at control panel A 402.

[0046] Figure 5 Components of a virtual partition module according to one embodiment are shown. The virtual partition module 304 includes a dynamic partition configurator 502 and a partition manager 504. The dynamic partition configurator 502 enables an administrator or installer of the security system 130 to define virtual partitions. Fig.10 The operation of an embodiment of the dynamic partition configurator 502 is further described. The partition manager 504 enables the security system 130 to relay sensor data to a control panel associated with a partition of a sensor corresponding to the sensor data. Fig.11 The operation of an embodiment of dynamic partition configurator 502 is further described.

[0047] Figure 6 An example of a partition of a security system according to an embodiment is illustrated. Sensors 310 include sensors s1 602, s2 604, s3 610, s4 608, and s5 606. Sensor interface 302 communicates with sensors 310. In one embodiment, sensor interface 302 accesses partition attributes and sensor data from sensors 310. The partition attributes identify the partition to which the corresponding sensor is assigned. For example, sensor s1 602 is assigned to partitions p1 and p4. Sensor s2 604 is assigned to partitions p2 and p4. Sensor s3 610 is assigned to partitions p1 and p2. Sensor s4 608 is assigned to partitions p2 and p4. Sensor s5 606 is assigned to partition p3.

[0048] Virtual partition module 304 uses partition attributes from sensors 310 to form partitions: Partition p1 includes data from sensors s1 602, s3 610. Partition p2 includes data from sensors s2 604, s3 610, and s4 608. Partition p3 includes data from sensor s5 606. Partition p4 includes data from sensors s1 602, s2 604, and s4 608.

[0049] The user interface module 306 generates user interfaces 612 for partitions p1, p2, and p4. The user interface module 306 generates a user interface 614 for partition p3. Control panel A 402 accesses user interface 612. Control panel B 404 accesses user interface 614. In one embodiment, each partition includes a corresponding user interface. In another embodiment, one or more partitions may share a user interface. Figure 6 In the embodiment of FIG. 6 , control panel A402 is able to access both user interface 614 and user interface 612 .

[0050] Figure 7 An example of a partition of a security system according to another embodiment implementation is illustrated. Although both control panel A 402 and control panel B 404 are connected to the same security system 130, each control panel may display a different status. For example, control panel A 402 detects a breach (e.g., a door opened) on one of its sensors (e.g., s1 702) and displays an intrusion alarm 714 notification. Control panel B 404 determines that the sensor data on its corresponding sensor for its partition indicates that all doors and windows are closed. Control panel B 404 displays a status normal 712 notification.

[0051] Figure 8 3 is a block diagram 300 illustrating a security system with zones in an apartment complex. Apartment complex 802 includes a security system 130 installed in a first floor of apartment complex 802. Each floor may include one or more apartment units: apartment 804, apartment 806, apartment 808, and apartment 818. Each apartment may be equipped with its own set of door and window sensors (not shown). A control panel may be installed in each apartment. For example, control panel 816 is located in apartment 818. Control panel 810 is located in apartment 804. Control panel 814 is located in apartment 806. Control panel 812 is located in apartment 808.

[0052] The control panels 816, 810, 814, 812 are connected to the security system 130. The security system 130 creates zones for each apartment so that each user can control and access security features associated with their apartment. For example, the user 128 can use the control panel 816 to arm or disarm sensors located in the apartment 818. In another example implementation, an administrator (e.g., a landlord) may be able to access all sensors and access controls in the apartment complex 802. For example, the landlord can use the security system 130 to remotely monitor which doors or windows (in the apartment complex 802) are open or closed.

[0053] Fig. 9 900 is a flowchart illustrating a method for generating a user interface for each partition according to an embodiment. The operations in method 900 may be performed by security system 130 using the above description of Figure 3 Therefore, the method 900 is described by way of example with reference to the security system 130. However, it should be appreciated that at least some of the operations of the method 900 may be deployed on various other hardware configurations or performed by similar components residing elsewhere.

[0054] At block 902, the security system 130 identifies sensors connected to the security system 130. At block 904, the security system 130 assigns a zone to each sensor. In another example implementation, the memory 1304 defines / forms the zones based on the zones identified in the zone attributes of each sensor. At block 906, the security system 130 generates a user interface corresponding to the zone. At block 908, the security system 130 provides the user interface to the control panel.

[0055] Fig.10 1 is a flow chart illustrating a method 1000 for providing a user interface for each partition to a control panel according to an embodiment. The operations in the method 1000 may be performed by the virtual partition module 304 using the above-described Figure 5 Therefore, method 1000 is described by way of example with reference to virtual partition module 304. However, it should be appreciated that at least some of the operations of method 1000 may be deployed on various other hardware configurations or performed by similar components residing elsewhere.

[0056] At block 1002, the dynamic partition configurator 502 receives a selection of connected sensors (e.g., a user identifies or selects which sensors are to be included in a partition). At block 1004, the dynamic partition configurator 502 forms a partition based on the selection of connected sensors. At block 1006, the dynamic partition configurator 502 forms a user interface corresponding to the partition. At block 1008, the dynamic partition configurator 502 receives a selection of a control panel for the partition. At block 1010, the dynamic partition configurator 502 provides a user interface to the selected control panel.

[0057] Fig.11 1100 is a flowchart illustrating a method for providing notifications to a control panel according to an embodiment. The operations in method 1100 may be performed by virtual partition module 304 using the above description of Figure 5 Therefore, method 1100 is described by way of example with reference to virtual partition module 304. However, it should be appreciated that at least some of the operations of method 1100 may be deployed on various other hardware configurations or performed by similar components residing elsewhere.

[0058] At block 1102, the partition manager 504 receives a sensor signal (e.g., a door open signal) from a sensor (e.g., a contact sensor). At block 1104, the partition manager 504 identifies which partition is associated with the sensor. At block 1106, the partition manager 504 identifies which control panel is associated with the partition. At block 1108, the partition manager 504 provides a notification to the identified control panel based on the sensor signal. At block 1110, the partition manager 504 provides a notification to a user associated with the identified control panel.

[0059] Fig.12 A routine according to one embodiment is illustrated. In block 1202, the routine 1200 identifies a plurality of sensors in communication with a security system. In block 1204, the routine 1200 identifies a partition attribute of each of the plurality of sensors, the partition attribute indicating one or more partitions of the security system for a corresponding sensor of the plurality of sensors. In block 1206, the routine 1200 forms a plurality of partitions of the security system based on the partition attributes of the plurality of sensors.

[0060] Fig.131300 within which instructions 1308 (e.g., software, programs, applications, applet, app, or other executable code) may be executed to cause the machine 1300 to perform any one or more of the methodologies discussed herein. For example, the instructions 1308 may cause the machine 1300 to perform any one or more of the methods described herein. The instructions 1308 transform the generally unprogrammed machine 1300 into a specific machine 1300 that is programmed to perform the functions described and illustrated in the manner described. The machine 1300 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1300 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1300 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a PDA, an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, web appliances, a network router, a network switch, a network bridge, or a computer capable of sequentially or otherwise executing instructions 1308 that specify actions to be taken by the machine 1300. In addition, while only a single machine 1300 is illustrated, the term "machine" should also be construed to include a collection of machines that individually or jointly execute instructions 1308 to perform any one or more of the methodologies discussed herein.

[0061] Machine 1300 may include a processor 1302, a memory 1304, and I / O components 1342 that may be configured to communicate with each other via a bus 1344. In example embodiments, processor 1302 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1306 that executes instructions 1308 and processor 1310. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.13 Multiple processors 1302 are shown, but the machine 1300 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0062] The memory 1304 includes a main memory 1312, a static memory 1314, and a storage unit 1316, all of which are accessible to the processor 1302 via the bus 1344. The main memory 1304, the static memory 1314, and the storage unit 1316 store instructions 1308 that embody any one or more of the methodologies or functionality described herein. During execution thereof by the machine 1300, the instructions 1308 may also reside, completely or partially, within the main memory 1312, within the static memory 1314, within the machine-readable medium 1318 within the storage unit 1316, within at least one of the processors 1302 (e.g., within a cache memory of the processor), or any suitable combination thereof.

[0063] I / O components 1342 may include a variety of components to receive input, provide output, generate output, transmit information, exchange information, capture measurements, etc. The specific I / O components 1342 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, whereas a headless server machine will most likely not include such a touch input device. It should be appreciated that I / O components 1342 may include Fig.13 1342. In various example embodiments, the I / O components 1342 may include output components 1328 and input components 1330. The output components 1328 may include visual components (e.g., displays such as plasma display panels (PDPs), light emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, and the like. The input components 1330 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, trackpads, trackballs, joysticks, motion sensors, or other pointing devices), tactile input components (e.g., physical buttons, touch screens that provide location and / or force of touch or touch gestures, or other tactile input components), audio input components (e.g., microphones), and the like.

[0064] In other example implementations, the I / O component 1342 may include a biometric component 1332, a motion component 1334, an environmental component 1336, or a position component 1338, as well as a number of other components. For example, the biometric component 1332 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1334 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. Environmental components 1336 include, for example, light sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors that detect hazardous gas concentrations for safety or that measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. Position components 1338 include position sensor components (e.g., GPS receiver components), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude can be derived), orientation sensor components (e.g., magnetometers), and the like.

[0065] A wide variety of technologies may be used to implement communications. I / O components 1342 further include a communication component 1340 operable to couple machine 1300 to network 1320 or device 1322 via coupling 1324 and coupling 1326, respectively. For example, communication component 1340 may include a network interface component or another suitable device for interfacing with network 1320. In further embodiments, communication component 1340 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Components (e.g., low power ), Components and other communication components that provide communication via other modalities. Device 1322 can be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0066] In addition, the communication component 1340 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 1340 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting a one-dimensional barcode, such as a universal product code (UPC) barcode, a multi-dimensional barcode, such as a Quick Response (QR) code, an Aztec code, a Data Matrix, a Dataglyph, a MaxiCode, a PDF417, an Ultra Code, a UCC RSS-2D barcode, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying a tag audio signal). In addition, various information can be derived via the communication component 1340, such as location via Internet Protocol (IP) geolocation, ... Signal triangulation derives location, derives location via detection of NFC beacon signals that can indicate a specific location, etc.

[0067] Various memories (e.g., memory 1304, main memory 1312, static memory 1314, and / or memory of processor 1302) and / or storage unit 1316 may store one or more sets of instructions and data structures (e.g., software) embodying any one or more of the methodologies or functions described herein or used by them. These instructions (e.g., instructions 1308) when executed by processor 1302, cause various operations to implement the disclosed embodiments.

[0068] Instructions 1308 may be transmitted or received over network 1320 using a transmission medium via a network interface device (e.g., a network interface component included in communication component 1340) and using any of a number of well-known transfer protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1308 may be transmitted or received to device 1322 via coupling 1326 (e.g., a peer-to-peer coupling) using a transmission medium.

[0069] Although the embodiments have been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Therefore, the description and the drawings should be viewed in an illustrative sense rather than a restrictive sense. The drawings forming a part thereof show specific embodiments in which the subject matter can be practiced by way of illustration and not limitation. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, this specific embodiment should not be considered to have a limiting meaning, and the scope of the various embodiments is limited only by the appended claims together with the full scope of equivalents given by such claims.

[0070] For convenience only, and without intending to voluntarily limit the scope of the present application to any single invention or inventive concept (if more than one is actually disclosed), such embodiments of the inventive subject matter may be referred to herein individually or collectively by the term "the present invention." Therefore, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may replace the specific embodiments shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. After reviewing the above description, the combination of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art.

[0071] The abstract of the specification of the present disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing detailed description, it can be seen that in order to make the present disclosure reasonable, various features are combined in a single embodiment. The disclosure method should not be interpreted as reflecting the intention that the claimed embodiment requires more features than the features explicitly recited in each claim. On the contrary, as reflected in the following claims, the subject matter of the invention lies in less than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the detailed description, wherein each claim stands alone as a separate embodiment.

[0072] Example

[0073] Embodiment 1 is a method comprising: identifying multiple sensors communicating with a security system; identifying a partition attribute of each of the multiple sensors, the partition attribute indicating one or more partitions of the security system for a corresponding sensor of the multiple sensors; and forming multiple partitions of the security system based on the partition attributes of the multiple sensors.

[0074] In embodiment 2, the subject matter of embodiment 1 further comprises: generating user interfaces for one or more partitions, each user interface providing status information of the one or more sensors associated with the corresponding partition.

[0075] In Example 3, the subject matter described in Example 1 further includes: providing the user interface of the one or more partitions to a control panel of the security system, the control panel being configured to display the user interface in a display of the control panel and control a portion of the settings of the security system, the portion of the settings being based on the one or more partitions.

[0076] In Example 4, the subject matter described in Example 1 further includes: identifying a first control panel associated with a first partition among the multiple partitions, the first control panel being remotely connected to the security system; identifying a second control panel associated with a second partition among the multiple partitions, the second control panel being remotely connected to the security system; providing a first user interface associated with the first partition to the first control panel; and providing a second user interface associated with the second partition to the second control panel.

[0077] In Example 5, the subject matter described in Example 1 further includes: at the security system, receiving a selection of one or more sensors from the multiple sensors; forming a first partition based on the selection of the one or more sensors from the multiple sensors; at the security system, receiving an identification of a first control panel for the partition; forming a first user interface based on the selection of one or more sensors and the first partition; and transmitting the first user interface to the first control panel.

[0078] In Example 6, the subject matter described in Example 1 further includes: accessing a sensor state of a sensor among the multiple sensors; identifying a partition associated with the sensor based on the partition attribute of the sensor; identifying a control panel corresponding to the partition; and providing the sensor state to the control panel.

[0079] In embodiment 7, according to the subject matter of embodiment 6, the control panel includes a user interface associated with the partition, the user interface configured to display the sensor status.

[0080] In Example 8, the subject matter described in Example 1 further includes: accessing the sensor status of a sensor among the multiple sensors; determining a destruction event based on the sensor status; identifying a partition associated with the sensor based on the partition attribute of the sensor; identifying a control panel corresponding to the partition; generating a notification identifying the destruction event and the corresponding sensor; and providing the notification of the destruction event and the corresponding sensor to the control panel.

[0081] In Example 9, the subject matter according to Example 1 further includes: receiving, at the security system, a first selection of one or more sensors from the plurality of sensors; receiving, at the security system, a second selection of one or more sensors from the plurality of sensors; forming a first partition based on the partition attributes of the one or more sensors of the first selection; forming a second partition based on the partition attributes of the one or more sensors of the second selection; forming a first user interface based on the first partition, the first user interface identifying the first partition; forming a second user interface based on the second partition, the second user interface identifying the second partition; and

[0082] The first user interface and the second user interface are communicated to a mobile device registered with the security system.

[0083] In Example 10, the subject matter of Example 1 further comprises: communicating the user interface to a remote security monitoring application registered with the security system.

Claims

1. A method for dynamically partitioning a security system, the method include: identifying a plurality of sensors in communication with the security system, wherein each of the sensors is initially associated with a physical partition or multiple physical partitions of the security system, the security system comprising a preset static number of physical partitions; responsive to administrator user input, updating a corresponding partition attribute of each of the plurality of sensors to assign each sensor to one or more user-selected virtual partitions of the security system, wherein the partition attribute identifies one or more specific partitions to which the sensor is assigned; forming a virtual security system based on the user-selected virtual partition and the updated partition attributes of the plurality of sensors; storing information about the virtual partition at the security system; and The virtual security system is independently operated according to the virtual partition.

2. The method for dynamically partitioning a security system according to claim 1, further comprising: include: User interfaces of one or more of the virtual partitions are generated, each user interface providing status information of the plurality of sensors associated with a corresponding virtual partition.

3. The method for dynamically partitioning a security system according to claim 1, further comprising: include: A corresponding user interface for each of the one or more virtual partitions is provided to a control panel of the security system, the control panel being configured to display each user interface in a display of the control panel and to control a portion of a setting of the security system, the portion of the setting being associated only with a particular displayed user interface for a particular virtual partition.

4. The method for dynamically partitioning a security system according to claim 1, further comprising: include: identifying a first control panel associated with a first one of the user-selected virtual partitions, the first control panel being remotely connected to the security system; identifying a second control panel associated with a second one of the user-selected virtual partitions, the second control panel being remotely connected to the security system; providing a first user interface associated with the first virtual partition to the first control panel; as well as A different second user interface associated with the second virtual partition is provided to the second control panel.

5. The method for dynamically partitioning a security system according to claim 1, further comprising: include: receiving, at the security system, a selection of one or more sensors from the plurality of sensors; forming a first virtual partition of the one or more user-selected virtual partitions based on a selection of the one or more sensors from the plurality of sensors; receiving, at the security system, an identification of a first control panel for the first virtual partition; as well as forming a first user interface based on the selection of one or more sensors and the first virtual partition; as well as The first user interface is communicated to the first control panel.

6. The method for dynamically partitioning a security system according to claim 1, further comprising: include: accessing a sensor state of a sensor of the plurality of sensors; identifying a virtual partition associated with the sensor based on a partition attribute of the sensor; identifying a control panel corresponding to the virtual partition; as well as The sensor status is provided to the control panel.

7. The method for dynamically zoning a security system according to claim 6, wherein the control panel includes a user interface specifically associated with the virtual partition, the user interface being configured to display the sensor status.

8. The method for dynamically partitioning a security system according to claim 1, further comprising: include: accessing a sensor state of a sensor of the plurality of sensors; determining a sabotage event based on the sensor status; identifying a virtual partition associated with the sensor based on a partition attribute of the sensor; identifying a control panel corresponding to the virtual partition; generating a notification identifying the sabotage event and the corresponding sensor; as well as A notification of the tampering event and the corresponding sensor is provided to the control panel.

9. The method for dynamically partitioning a security system according to claim 1, further comprising: include: receiving, at the security system, a first selection of one or more sensors from the plurality of sensors; receiving, at the security system, a second selection of one or more sensors from the plurality of sensors; forming a first virtual zone based on the zone attributes of the one or more sensors of the first selection; forming a second virtual zone based on the zone attributes of the one or more sensors of the second selection; forming a first user interface based on the first virtual partition, the first user interface identifying the first virtual partition; forming a second user interface based on the second virtual partition, the second user interface identifying the second virtual partition; as well as The first user interface and the second user interface are communicated to a mobile device registered with the security system.

10. The method for dynamically partitioning a security system according to claim 1, in, Each of the plurality of sensors is initially associated with all physical partitions of the security system, and wherein, in response to the administrator user input, updating the corresponding partition attributes includes: assigning each sensor to one or more user-selected virtual partitions in corresponding user-selected virtual partitions, wherein the corresponding user-selected virtual partitions include physical partitions that are less than all physical partitions of the security system.

11. The method for dynamically partitioning a security system according to claim 1, in, Updating the corresponding zone attribute of each sensor includes assigning at least one sensor to a plurality of virtual zones of the security system.

12. A computing device for dynamically partitioning a security system, the computing device include: processor; as well as a memory storing instructions that, when executed by the processor, configure the device to: identifying a plurality of sensors in communication with the security system, wherein each of the sensors is initially associated with a plurality of physical partitions of the security system, the security system comprising a preset static number of physical partitions; receiving, from an administrator user of the security system, corresponding partition attributes to assign each of the sensors to one or more user-selected virtual partitions of the security system, wherein the partition attributes identify one or more specific partitions to which the sensors are assigned; forming a virtual security system based on the user-selected virtual partition and corresponding partition attributes of the plurality of sensors; storing information about the virtual partition at the security system; and A corresponding virtual security system is independently operated according to the virtual partition.

13. The computing device for dynamically partitioning a security system of claim 12, wherein the instructions further configure the device to: User interfaces of one or more virtual partitions are generated, each user interface providing status information of the plurality of sensors associated with a corresponding virtual partition.

14. The computing device for dynamically partitioning a security system of claim 12, wherein the instructions further configure the device to: receiving, at the security system, a selection of one or more sensors from the plurality of sensors; forming a first virtual zone based on a selection of the one or more sensors from the plurality of sensors; receiving, at the security system, an identification of a first control panel for the first virtual partition; as well as forming a first user interface based on the selection of one or more sensors and the first virtual zone; as well as The first user interface is communicated to the first control panel.

15. The computing device for dynamically partitioning a security system of claim 12, wherein the instructions further configure the device to: accessing a sensor state of a sensor of the plurality of sensors; identifying a virtual partition associated with the sensor based on a partition attribute of the sensor; identifying a control panel corresponding to the virtual partition; and The sensor status is provided to the control panel.

16. The computing device for dynamically partitioning a security system of claim 12, wherein the instructions further configure the device to: accessing a sensor state of a sensor of the plurality of sensors; determining a sabotage event based on the sensor status; identifying a virtual partition associated with the sensor based on a partition attribute of the sensor; identifying a control panel corresponding to the virtual partition; generating a notification identifying the sabotage event and the corresponding sensor; as well as A notification of the tampering event and the corresponding sensor is provided to the control panel.

17. The computing device for dynamically partitioning a security system of claim 12, wherein the instructions further configure the device to assign at least one sensor of the plurality of sensors to physical partitions that are less than all of the physical partitions of the security system.

18. The computing device for dynamically partitioning a security system of claim 17, wherein the instructions further configure the device to assign at least one sensor of the plurality of sensors to a plurality of virtual partitions of the security system.

19. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations for dynamically partitioning a security system, the operations include: identifying a plurality of sensors in communication with the security system, wherein each of the sensors is initially associated with a plurality of physical partitions of the security system, the security system comprising a preset static number of physical partitions; receiving, from an administrator user of the security system, corresponding partition attributes to assign each of the sensors to one or more user-selected virtual partitions of the security system, wherein the partition attributes identify one or more specific partitions to which the sensors are assigned; forming a virtual security system based on the user-selected virtual partition and corresponding partition attributes of the plurality of sensors; storing information about the virtual partition at the security system; and A corresponding virtual security system is independently operated according to the virtual partition.

20. The computer-readable storage medium of claim 19, further comprising instructions that cause the computer to perform operations comprising assigning at least one sensor of the plurality of sensors to a plurality of virtual partitions of the security system.

Images