Patent Publication Number: US-2020279473-A1

Title: Virtual partition of a security system

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is related to co-pending U.S. patent application Ser. No. ______, entitled “Dynamic partition for security system” (Attorney Docket No. 5986.265US1) and is incorporated herewith in its entirety. 
    
    
     BACKGROUND 
     Home security system can be used to notify the homeowner of intrusions and other alerts (e.g., porch light left on all night). These security systems communicate with sensors placed throughout a facility (e.g., home, office). However, the hardware settings on these security system limits the number of available zones. Thus, a homeowner wishing to add another zone to monitor an in-law unit of his home may need to purchase another security system that is capable of monitoring two zones. 
    
    
     
       BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS 
       To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. 
         FIG. 1  is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, in accordance with some example embodiments. 
         FIG. 2  is a block diagram illustrating an example of a security system in accordance with one example embodiment. 
         FIG. 3  illustrates components of a security system in accordance with one example embodiment. 
         FIG. 4  illustrates components of a security system in accordance with another example embodiment. 
         FIG. 5  illustrates components of a virtual partition module in accordance with one example embodiment. 
         FIG. 6  illustrates an example of partitions of a security system in accordance with one example embodiment. 
         FIG. 7  illustrates an example of partitions of a security system in accordance with another example embodiment. 
         FIG. 8  is a block diagram illustrating an operation of a security system in accordance with one example embodiment. 
         FIG. 9  is a flow diagram illustrating a method for generating a user interface for each partition in accordance with one example embodiment. 
         FIG. 10  is a flow diagram illustrating a method for providing a user interface for each partition to a control panel in accordance with one example embodiment, 
         FIG. 11  is a flow diagram illustrating a method for providing a notification to a control panel in accordance with one example embodiment 
         FIG. 12  illustrates a routine in accordance with one embodiment. 
         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 embodiment. 
     
    
    
     DETAILED DESCRIPTION 
     “Component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone 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 ) may be configured by software (e.g., an application 916 or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry 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, hardware components become specific machines (or specific components of a machine  1000 ) uniquely tailored to perform the configured functions and are no longer general-purpose processors  1004 . It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations. Accordingly, the phrase “hardware component”(or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors  1004  or processor-implemented components. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations. 
     “Communication Network” refers to one or more portions of a network that 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, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a 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 types of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, 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, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology. 
     “Machine-Storage Medium” refers to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions, routines and/or data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; 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,” “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.” 
     “Processor” refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be 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 further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. 
     “Carrier Signal” refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device. 
     “Signal Medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure. 
     “Computer-Readable Medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. The terms “machine-readable medium,” “computer-readable medium” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure. 
     Example methods and systems are directed to partitioning of security systems. Examples merely typify possible variations. Unless explicitly stated otherwise, components and functions are optional and may be combined or subdivided, and operations may vary in sequence or be combined or subdivided. In the following description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of example embodiments. It will be evident to one skilled in the art, however, that the present subject matter may be practiced without these specific details. 
     A homeowner (and user of a security system) may want to two separate partitions for their property: one for their house and one for their garage. In another example, a company may want dozens of partitions to monitor the security of a row of locked cabinets in a lab. Some security systems may not dynamically increase or decrease the number of partitions because those security systems are already hardwired for a preset number of static partitions. 
     The present application describes a method for dynamically partitioning a security system. In one example embodiment, a security system identifies a plurality of sensors in communication with a security system; identifies a partition attribute for each sensor 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 embodiment, a hardwired security system with a static preset number of partitions may dynamically adjust a number of virtual partitions. 
       FIG. 1  is a diagrammatic representation of a network environment  100  in which some example embodiments of the present disclosure may be implemented or deployed. 
     One or more application servers  104  provide server-side functionality via a network  102  to a networked user device, in the form of a security system  130  and a client device  106  of the user  128 . The security system  130  includes a control panel (not shown) connected to sensors in a household  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 execute on the client device  106 . The client device  106  can communicate with the security system  130  via the network  102  or via other wireless or wired means with security system  130 . 
     An Application Program Interface (API) server  118  and a web server  120  provide respective programmatic and web interfaces to application servers  104 . A specific application server  116  hosts a remote security monitoring application  122  that operates with the security system  130 . In one example, the remote security monitoring application  122  receives an alert from a sensor of the security system  130 , identifies a partition associated with the alert, and communicates the alert to a mobile device (or a control panel) associated with the partition. 
     The web client  110  communicates with the remote security monitoring application  122  via the web interface supported by the web server  120 . Similarly, the programmatic client  108  communicates with the remote security monitoring application  122  via the programmatic interface provided by the Application Program Interface (API) server  118 . The third-party application  114  may, for example, be a topology application that determines the topology of a factory (e.g., how many cabinets, rooms, which rooms contain valuable items), building, apartment complex, or neighborhood. The application server  116  is shown to be communicatively coupled to database servers  124  that facilitates access to an information storage repository or databases  126 . In an example embodiment, the databases  126  includes storage devices that store information to be published and/or processed by the remote security monitoring application  122 . 
     Additionally, a third-party application  114  executing on a third-party server  112 , is shown as having programmatic access to the application server  116  via the programmatic interface provided by the Application Program Interface (API) server  118 . For example, the third-party application  114 , using information retrieved from the application server  116 , may supports one or more features or functions on a website hosted by the third party. In one example, the third-party server  112  communicates with another remote controlled device (e.g., smart door lock) located at the household  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 example, the security system  130 , the client device  106 , and the application server  116  can control the door lock via the third-party application  114 . 
       FIG. 2  is a block diagram of a system  200  illustrating an example of a security system in a household in accordance with one example embodiment. The household  132  includes, for example, the user  128  and the security system  130 . The security system  130  is connected to sensors and remotely controlled devices. The sensors may include sensor devices (e.g., camera  202 , a temperature sensor  204 ) and remotely controlled devices (e.g., a door lock  206 , a speaker  208 ). Those of ordinary skills in the art will recognize that other types of sensors (besides the ones illustrated in  FIG. 2 ) may be connected to the security system  130 . 
     The security system  130  (although hardwired to operate with one partition) may 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 camera  202  and temperature sensor  204 . Partition B  212  includes speaker  208  and door lock  206 . Those of ordinary skill in the art will recognize that partitions may include a combination of any of the sensors and devices. For example, Partition B  212  can also include temperature sensor  204  (which is also part of Partition A  210 ). 
     The security system  130  can be configured to operate both partitions as the same time by receiving sensor data from the corresponding sensors and controlling the sensors corresponding to the partitions. In another example, the security system  130  may enable the user  128  to operate only Partition A  210  and another user to operate only Partition B  212  (based on the access rights of the user  128 ). 
       FIG. 3  illustrates components of a security system in accordance with one example embodiment. 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, via the sensor interface  302 , with sensors  310  disposed in a physical facility (e.g., a home, a building, a factory, a campus). For example, the sensor interface  302  identifies the sensors  310  and accesses sensor data from the sensors  310 . In one example, the sensors  310  are registered with the security system  130 . 
     In one example embodiment, the sensor interface  302  identifies a partition attribute for each sensor of sensors  310 . For example, the partition attribute of a sensor identifies one or more specific partitions to which the sensor is assigned to. In another example, the partition attribute of a safety related sensor (e.g., smoke sensor) identifies all partitions of the security system  130 . In another example, the partition attribute of a sensor may be set to identify all partitions of the security system  130  by default. In another example, the partition attribute of a sensor may be set to identify a partition of the security system  130  based on a location of the sensor (e.g., sensors at home are to be assigned to home partition). 
     The virtual partition module  304  forms one or more partitions based on the partition attributes of the sensors  310 . For example, the virtual partition module  304  forms a first partition for a first and second sensor of sensors  310 . The first and second sensors each include a partition attribute that identifies the first partition. The virtual partition module  304  forms a second partition based on a third and fourth sensor of sensors  310 . The second and third sensors each include a partition attribute that identifies the second partition. 
     The user interface module  306  generates a user interface for each partition based on the sensors identified in the corresponding partition. In one example, the user interface may identify a name of the partition, a description of the partition, sensors in the partition, sensor status, and authorized users having access to the partition (e.g., renters having access to sensor data from sensors in their apartment, and landlord having access to sensor data of sensors from a building). This allows both the renters and landlord to use the single security system  130  with different partitions. 
     The control panel  308  includes a display and user input that enables the user  128  to control the features of the security system  130  corresponding to a partition. For example, the user  128  may arm a first partition and disarm a second partition using the control panel  308 . In another example, the control panel  308  identifies the user  128  and provides the user  128  with access to the corresponding partition (e.g., one partition at a time or several partitions at a time). In another example, the control panel  308  may be a virtual control panel that is accessed via a client device  106  or a computing device registered with the security system  130 . The control panel  308  receives the different user interfaces from the user interface module  306  for each partition. 
       FIG. 4  illustrates components of a security system in accordance with another example embodiment. The user interface module  306  generates a user interface for each partition based on the partition attributes of the sensors. The user interface module  306  communicates user interfaces corresponding to the control panel A  402  and control panel B  404 . The control panel A  402  and 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 a basement of an apartment building while the control panel A  402  is located in a first apartment of the apartment building and the control panel B  404  is located in a second apartment of the apartment building. 
     In one example embodiment, the user interface module  306  determines that a first user interface for a first partition refers to the control panel A  402 . The user interface module  306  then communicates the first user interface and sensor data of the sensors corresponding to the partition of the first user interface to the control panel A  402 . The user interface module  306  determines that a second user interface for a second partition refers to the control panel B  404 . The user interface module  306  then communicates the second user interface and sensor data of the sensors corresponding to the partition of the second user interface to the control panel B  404 . 
     The control panel A  402  includes a display and user input that enables a user at the control panel A  402  to control the features of the security system  130 . For example, the user may control features corresponding to a first partition at control panel A  402 . The control panel B  404  includes a display and user input that enables a user at the control panel B  404  to control the features of the security system  130 . For example, the user may control features corresponding to a first partition at control panel A  402 . 
       FIG. 5  illustrates components of a virtual partition module in accordance with one example embodiment. 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. An example operation of the dynamic partition configurator  502  is described further below with respect to  FIG. 10 . The partition manager  504  enables the security system  130  to relay the sensor data to the control panel associated with the partition corresponding to the sensor of the sensor data. An example operation of the dynamic partition configurator  502  is described further below with respect to  FIG. 11 . 
       FIG. 6  illustrates an example of partitions of a security system in accordance with one example embodiment. Sensors  310  includes sensors s 1   602 , s 2   604 , s 3   610 , s 4   608 , and s 5   606 . The sensor interface  302  communicates with the sensors  310 . In one example, the sensor interface  302  accesses partition attributes and sensor data from the sensors  310 . The partition attributes identify the partition to which a corresponding sensor is assigned to. For example, sensor s 1   602  is assigned to partitions p 1  and p 4 . Sensor s 2   604  is assigned to partitions p 2  and p 4 . Sensor s 3   610  is assigned to partitions p 1  and p 2 . Sensor s 4   608  is assigned to partitions p 2  and p 4 . Sensor s 5   606  is assigned to partitions p 3 . 
     The virtual partition module  304  uses the partition attributes from the sensors  310  to form the partitions: partition p 1  includes data from sensors s 1   602 , s 3   610 . Partition p 2  includes data from sensors s 2   604 , s 3   610 , and s 4   608 . Partition p 3  includes data from sensor s 5   606 . Partition p 4  includes data from sensors s 1   602 , s 2   604 , and s 4   608 . 
     The user interface module  306  generates a user interface  612  for partitions p 1 , p 2 , and p 4 . The user interface module  306  generates a user interface  614  for partition p 3 . The control panel A  402  accesses the user interface  612 . The control panel B  404  accesses the user interface  614 . In one example, each partition includes a corresponding user interface. In another example, one or more partitions may share a user interface. In the example of  FIG. 6 , the control panel A  402  can access both the user interface  614  and user interface  612 . 
       FIG. 7  illustrates an example of partitions of a security system in accordance with another example embodiment. 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, the control panel A  402  detects a breach (e.g., door open) on one of its sensors (e.g., s 1   702 ) and displays an intrusion alert  714  notification. The control panel B  404  determines that the sensor data on its corresponding sensors of its partition indicate that all doors and windows are closed. The control panel B  404  displays status ok  712  notification. 
       FIG. 8  is a block diagram  300  illustrating a security system with partitions in an apartment complex. The apartment complex  802  includes one security system  130  installed in a first floor of the 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 windows and doors 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 . 
     The control panels  816 ,  810 ,  814 ,  812  are connected to the security system  130 . The security system  130  creates a partition for each apartment such that each user can control and access security features related to its apartment. For example, user  128  can arm or disarm sensors located in apartment  818  using control panel  816 . In another example embodiment, an administrator (e.g., landlord) may have access to all sensors and access controls in the apartment complex  802 . For example, the landlord can remotely monitor which door or window (in the apartment complex  802 ) is open or close using the security system  130 . 
       FIG. 9  is a flow diagram illustrating a method for generating a user interface for each partition in accordance with one example embodiment. Operations in the method  900  may be performed by the security system  130 , using components (e.g., modules, engines) described above with respect to  FIG. 3 . Accordingly, the method  900  is described by way of example with reference to the security system  130 . However, it shall be appreciated that at least some of the operations of the method  900  may be deployed on various other hardware configurations or be performed by similar components residing elsewhere. 
     At block  902 , the security system  130  identifies sensors connected to the security system  130 . At block  904 , the security system  130  assigns a partition to each sensor. In another example embodiment, the memory  1304  defines/forms partitions based on the partition identified in the partition attribute of each sensor. At block  906 , the security system  130  generates a user interface for the corresponding partition(s). At block  908 , the security system  130  provides the user interface to the control panel(s). 
       FIG. 10  is a flow diagram illustrating a method  1000  for providing a user interface for each partition to a control panel in accordance with one example embodiment. Operations in the method  1000  may be performed by the virtual partition module  304 , using components (e.g., modules, engines) described above with respect to  FIG. 5 . Accordingly, the method  1000  is described by way of example with reference to the virtual partition module  304 . However, it shall be appreciated that at least some of the operations of the method  1000  may be deployed on various other hardware configurations or be performed by similar components residing elsewhere. 
     At block  1002 , the dynamic partition configurator  502  receives a selection of connected sensors (e.g., a user identifies or selects which sensors 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 partition. At block  1010 , the dynamic partition configurator  502  provides the user interface to the selected control panel. 
       FIG. 11  is a flow diagram illustrating a method for providing a notification to a control panel in accordance with one example embodiment. Operations in the method  1100  may be performed by the virtual partition module  304 , using components (e.g., modules, engines) described above with respect to  FIG. 5 . Accordingly, the method  1100  is described by way of example with reference to the virtual partition module  304 . However, it shall be appreciated that at least some of the operations of the method  1100  may be deployed on various other hardware configurations or be performed by similar components residing elsewhere. 
     At block  1102 , the partition manager  504  receives a sensor signal (e.g., door open signal) from a sensor (e.g., 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. 
       FIG. 12  illustrates a routine in accordance with one embodiment. In block  1202 , routine  1200  identifies a plurality of sensors in communication with a security system. In block  1204 , routine  1200  identifies a partition attribute for each sensor 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 , routine  1200  forms a plurality of partitions of the security system based on the partition attributes of the plurality of sensors. 
       FIG. 13  is a diagrammatic representation of the machine  1300  within which instructions  1308  (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine  1300  to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions  1308  may cause the machine  1300  to execute any one or more of the methods described herein. The instructions  1308  transform the general, non-programmed machine  1300  into a particular machine  1300  programmed to carry out the described and illustrated functions 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 in the capacity of 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 comprise, but not be 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 telephone, 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, a web appliance, a network router, a. network switch, a network bridge, or any machine capable of executing the instructions  1308 , sequentially or otherwise, that specify actions to be taken by the machine  1300 . Further, while only a single machine  1300  is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions  1308  to perform any one or more of the methodologies discussed herein. 
     The machine  1300  may include processors  1302 , memory  1304 , and I/O components  1342 , which may be configured to communicate with each other via a bus  1344 . In an example embodiment, the processors  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, a processor  1306  and a processor  1310  that execute the instructions  1308 . The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although  FIG. 13  shows multiple processors  1302 , 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 multiples cores, or any combination thereof. 
     The memory  1304  includes a main memory  1312 , a static memory  1314 , and a storage unit  1316 , both accessible to the processors  1302  via the bus  1344 . The main memory  1304 , the static memory  1314 , and storage unit  1316  store the instructions  1308  embodying any one or more of the methodologies or functions described herein. The instructions  1308  may also reside, completely or partially, within the main memory  1312 , within the static memory  1314 , within machine-readable medium  1318  within the storage unit  1316 , within at least one of the processors  1302  (e.g., within the processor&#39;s cache memory), or any suitable combination thereof, during execution thereof by the machine  1300 . 
     The I/O components  1342  may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components  1342  that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components  1342  may include many other components that are not shown in  FIG. 13 . 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., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components  1330  may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like. 
     In further example embodiments, the I/O components  1342  may include biometric components  1332 , motion components  1334 , environmental components  1336 , or position components  1338 , among a wide array of other components. For example, the biometric components  1332  include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components  1334  include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components  1336  include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), 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 to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components  1338  include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. 
     Communication may be implemented using a wide variety of technologies. The I/O components  1342  further include communication components  1340  operable to couple the machine  1300  to a network  1320  or devices  1322  via a coupling  1324  and a coupling  1326 , respectively. For example, the communication components  1340  may include a network interface component or another suitable device to interface with the network  1320 . In further examples, the communication components  1340  may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth®Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices  1322  may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB). 
     Moreover, the communication components  1340  may detect identifiers or include components operable to detect identifiers. For example, the communication components  1340  may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components  1340 , such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth. 
     The various memories (e.g., memory  1304 , main memory  1312 , static memory  1314 , and/or memory of the processors  1302 ) and/or storage unit  1316  may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions  1308 ), when executed by processors  1302 , cause various operations to implement the disclosed embodiments. 
     The instructions  1308  may be transmitted or received over the network  1320 , using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components  1340 ) and using any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions  1308  may be transmitted or received using a transmission medium via the coupling  1326  (e.g., a peer-to-peer coupling) to the devices  1322 . 
     Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated 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, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. 
     Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, dill be apparent to those of skill in the art upon reviewing the above description. 
     The Abstract of the 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 various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 
     EXAMPLES 
     Example 1 is a method comprising: identifying a plurality of sensors in communication with a security system; identifying a partition attribute for each sensor 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 forming a plurality of partitions of the security system based on the partition attributes of the plurality of sensors. 
     In example 2, the subject matter of example 1, further comprises: generating a user interface for one or more partitions, each user interface providing status information of the one or more sensors associated with the corresponding partition. 
     In example 3, the subject matter of example 1, further comprises: providing the user interface for the one or more partitions to a control panel of the security system, the control panel configured to display the user interface in a display of the control panel, and to control a portion of settings of the security system, the portion of settings being based on the one or more partitions. 
     In example 4, the subject matter of example 1, further comprises: identifying a first control panel associated with a first partition of the plurality of partitions, the first control panel remotely connected to the security system; identifying a second control panel associated with a second partition of the plurality of partitions, the second control panel 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. 
     In example 5, the subject matter of example 1, further comprises: receiving, at the security system, a selection of one or more sensors from the plurality of sensors; forming a first partition based on the 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 partition; forming a first user interface based on the selection of one or more sensors and the first partition; and communicating the first user interface to the first control panel. 
     In example 6, the subject matter of example 1, further comprises: accessing a sensor status of a sensor of the plurality of 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 status to the control panel. 
     In example 7, the subject matter of example 6, wherein the control panel includes a user interface associated with the partition, the user interface configured to display the sensor status. 
     In example 8, the subject matter of example 1, further comprises: accessing a sensor status for a sensor of the plurality of sensors; determining a breach 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 breach event and the corresponding sensor; and providing the notification of the breach event and the corresponding sensor to the control panel. 
     In example 9, the subject matter of example 1, further comprises: 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 
     communicating the first user interface and the second user interface to a mobile device registered with the security system. 
     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.