Abstract:
Systems and methods for take-over protection for a system are provided. Methods can include a module of the system storing, in a memory device of the module, a control panel identifier of a control panel of the system, the module requesting that the control panel communicates the control panel identifier to the module, the module receiving the control panel identifier from the control panel, the module comparing the control panel identifier received from the control panel with the control panel identifier stored in the memory device, and the module initiating communications with the control panel when the control panel identifier received from the control panel matches the control panel identifier stored in the memory device.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation of and claims the benefit of the filing date of U.S. application Ser. No. 14/557,733 filed Dec. 2, 2014. 
     
    
     FIELD 
       [0002]    The application pertains to regional monitoring or control systems. More particularly, the application pertains to security or ambient condition monitoring systems, wherein system components, detectors, or control elements limit their communications to known or pre-determined system control units. 
       BACKGROUND 
       [0003]    Security dealers provide security systems to protect people&#39;s lives and property. There are various segments to the security business market ranging from high end installations to basic, low-cost solutions. The basic, low-cost solution is usually offered to the consumer at a cost lower than the cost of the security equipment with the expectation that the cost will be recovered via a monthly monitoring fee. Problems arise when a competing security dealer offers the consumer a lower monthly monitoring fee and “takes over” the installed security equipment. 
         [0004]    “Taking over” a security system saves the competitor the time and expense of installing the security system. The process of “taking over” a security system involves removing the existing control panel, installing a new control panel, and configuring the control panel to accept signals from the existing security sensors. Hence, the savings are realized by the reuse of the existing sensors that were provided by the original security dealer. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0005]      FIG. 1  is a block diagram of a system in accordance herewith; and 
           [0006]      FIG. 2  is a flow diagram in accordance herewith. 
       
    
    
     DETAILED DESCRIPTION 
       [0007]    While disclosed embodiments can take many different forms, specific embodiments hereof are shown in the drawings and will be described herein in detail with the understanding that the present disclosure is to be considered as an exemplification of the principles hereof, as well as the best mode of practicing the same, and is not intended to limit the claims hereof to the specific embodiment illustrated. 
         [0008]    In embodiments hereof, the problem is solved by pairing members of a plurality of system modules, such as security sensors, control elements, or ambient condition detectors, with a system control panel or system control circuits. In a disclosed embodiment, the modules, for example, the sensors, control elements, or detectors, without limitation, will only communicate with the system control circuits provided by the security dealer that installed the entire system. 
         [0009]    Should a competing dealer try to “take over” the system by removing the control circuits or panel, the existing modules, whether they be implemented as sensors, ambient condition detectors, or control elements, will not communicate with the new control system or panel. Therefore, the entire system (panel and modules) will need to be replaced to take over the system. 
         [0010]    In one aspect hereof, only an authorized user can remove a sensor, detector, or peripheral from the security system and reuse the removed module with a different security system. 
         [0011]    An authorized user can be the dealer, installer, or other person assigned by the dealer (perhaps the end user). There are many ways to determine if a user is “authorized”, such as the use of an authorized user code, biometric identifier, password, etc. Once the user is authenticated, the removal and reuse of the respective module is permitted. 
         [0012]    In a disclosed embodiment, two-way RF modules are coupled to an integral RF modular network identifier (ID). The network ID is derived from, for example, a MAC address that is stored in the control panel. This MAC address is unique to the control panel and in the domain of MAC addresses. Other identifiers can be used without departing from the spirit and scope hereof. 
         [0013]    When a module is enrolled into the control panel, the control panel provides the network ID to that module. The network ID is stored in non-volatile memory in the module. Whenever the module communicates with the control panel, the module verifies the network ID of the panel. If the received ID does not match the pre-stored ID, then the module will cease communications with that panel. 
         [0014]      FIG. 1  illustrates a monitoring system  10  that has a local control unit  12 . A plurality of modules  14  can be in bidirectional wired or wireless RF communications with the control unit  12 . Members of the plurality  14 , such as  14   a,    14   b  . . .  14   n,  can be installed throughout a region R of interest. Members of the plurality  14  can include, without limitation, motion detectors, position detectors, glass break detectors, smoke detectors, flame detectors, gas detectors, thermal detectors, door access control modules, and authorizing modules. 
         [0015]    The control unit  12  and members  14   a,    14   b  . . .  14   n  of the plurality of modules  14  can be in bidirectional communication as would be understood by those of skill in the art. The communications medium  18  can be wired or wireless, without limitation. 
         [0016]    The control unit or panel  12  can include control circuits  20  that can be implemented, at least in part, with one or more programmable processors  20   a  and associated executable control software or instructions  20   b.    
         [0017]    A unique network identifier  20   c  can be assigned to the system  10  and stored in non-volatile storage  20   c.  An input/output wired or wireless interface  20   d  can also be coupled to the control circuits  20 . 
         [0018]    The module  14   a  is representative of the members of the plurality  14 . A discussion of module  14   a  will also suffice for a discussion of the remaining members of the plurality  14 . 
         [0019]    The module  14   a  includes a housing  28 , which can be mounted to a wall, ceiling, floor, or the like, without limitation, depending on the characteristic thereof. The particular mounting arrangement is not a limitation hereof. 
         [0020]    The housing  28  can carry control circuits  30 , which can be implemented, at least in part, with one or more programmable processors  30   a  in combination with pre-stored, executable control instructions  30   b.  The control circuits  30  are coupled to comparison circuits  30   c  and to a non-volatile network identification storage unit  30   d.  The control circuits  30  are also coupled to a wired or wireless communications interface  30   e  to implement bidirectional communications with the unit  12  via the medium  18 . 
         [0021]    The control circuits  30  are also coupled to one or more sensors  32  and/or one or more input/output devices  34 . The devices  32 ,  34  can be selected from a class which includes at least motion detectors, position detectors, glass break detectors, smoke detectors, flame detectors, gas detectors, thermal detectors, door access control modules, solenoid modules, and authorizing modules, all without limitation. 
         [0022]      FIG. 2  illustrates aspects of a method  100  of operating the system  10 . The various modules  14  can be initially installed in a region R as required, as at  102 . The method  100  is representative of processing in connection with a group of modules  14  in an initial system installation or replacement of a single module after installation. 
         [0023]    Each of the modules  14  acquires and locally stores a network identifier obtained from the control unit  12  and stored locally at the unit  30   c,  as at  104 . When an event occurs that causes communications to occur between one more members of the plurality  14  and the control unit  12 , as at  106 , each respective module requests that the control unit  12  transmit a copy of the system identifier stored, for example, at the storage element  20   c,  as at  108 . 
         [0024]    The system identifier received at the module  14   a  from the control unit  12  is compared to the pre-stored identifier at  30   d  using the comparison circuits  30   c,  as at  112 . If the pre-stored identifier from the unit  30   c  corresponds to or is the same as the received identifier, as at  112 , then the communications proceed, as at  114 . If not, then communications are either not initiated or terminated, as at  116 . It will be understood that neither the details as to how the pre-stored identifier is represented at the unit  14   a  nor the exact details of the comparison with the pre-stored identifier and the received identifier are limitations hereof. 
         [0025]    As those of skill in the art will understand, there will be various ways for the installer to manage the network ID so that sensors can be removed, replaced, or repurposed. However, this capability will only be available via secure communications by the dealer that installed the equipment. 
         [0026]    Alternate methods may achieve the goal of pairing a module or sensor with a security system and only allowing authorized users to repurpose a sensor. Such other systems or methods that achieve the same result come within the spirit and scope hereof. 
         [0027]    In summary, the sensors or detectors are manufactured in a default state. This state enables the sensor to be enrolled with any compatible security system. Once the sensor has been enrolled with a panel, the sensor is no longer in the default state and will only work with the panel with which the sensor has been enrolled. To repurpose, that is, to enroll the sensor with a different panel, the sensor will need to be reset to the default state. Only authorized users can reset the sensor into the default state. 
         [0028]    During implementation, for example, during the first 24 hours after enrollment, the enrolled sensors can be defaulted at the system control panel by anyone, not just an authorized user. This feature provides a way to deal with enrollment mistakes, such as when a sensor is enrolled with the wrong control panel. 
         [0029]    Panel replacement, for example, if the control panel malfunctions and needs to be replaced, is a process available for an authorized user to replace the control panel, and all of the sensors will change their allegiance to the new panel. 
         [0030]    From the foregoing, it will be observed that numerous variations and modifications may be effected without departing from the spirit and scope of the invention. It is to be understood that no limitation with respect to the specific apparatus illustrated herein is intended or should be inferred. It is, of course, intended to cover by the appended claims all such modifications as fall within the scope of the claims. 
         [0031]    Further, logic flows depicted in the figures do not require the particular order shown or sequential order to achieve desirable results. Other steps may be provided, or steps may be eliminated from the described flows, and other components may be added to or removed from the described embodiments.