Patent Application
20090172711
This invention relates generally to security systems having a global communication system interface. In particular, this invention relates to a security system interface, accessible by developers external to the security system, that coordinates displays from the security system with displays from external systems.
As web connectivity, graphical information and security applications converge on the home of the future, challenges exist in providing proper solutions that balance all needs. By way of example, a security system that is internet connected can serve as a household internet appliance. Such a system offers an all-in-one approach to its customers, providing both local security panel control, and broad internet content. Users of this system can obtain not only information about the status of the areas protected by the security system, but also general information from the internet, such as news, weather, sports scores, etc. This functionality is provided by a routine in the security system that gathers all content and renders all of this content to the security system. In this approach, the security system routine maintains control of all aspects of data collection and dissemination, to ensure proper handling of any and all security events.
Some security systems permit interaction with a graphics system. Priority logic is handled by the security system software regarding what is to be displayed and when it will be displayed. This priority logic is typically built into the security system. Moreover, data from external news feeds, for example, can be given to the security system in a closed-loop, controlled environment. In this situation, the security system controls data content as well as when the data can be displayed.
Among the problems of the aforementioned systems is the lack of a device or component, such as a centralized rules manager, to maintain control of all of the information sent to the security system's display. Without such a rules manager, it is quite likely that non-life safety events and activities could override those more critical events that a person may need to see and react to immediately. Therefore, there is a need for a rules manager functioning to police events and maintain high priority for life safety functions when needed while allowing other applications, distinct from the security system, to coexist peacefully with the security system.
The present invention advantageously provides a device, such as a software based priority and/or rules manager, for a security system that facilitates total freedom of development for application developers of internet sessions, enabling development and deployment of applications displaying information unrelated to the security system data on a security system graphical display. At the same time, the inventive manager allows the security system security panel to have priority to properly and effectively take control of its graphical displays for purposes of handling life/safety on premise situations either requiring notification on the display, or accepting input by a user through a touch screen portion of the display. The solution includes at least two key elements, an application program interface and a set of table parameters or rules.
The inventive system and method for enabling external applications to display data in the security system has a table with a plurality of rules and an interface for processing the external application data for display, such that when an alert occurs in the security system, one of the rules defines a response to the alert and the device performs the response. This system and method protects the integrity of the security system in addition to allowing the display of data by external applications.
The foregoing and other objects, aspects, features, advantages of the invention will become more apparent from the following description and from the claims.
The invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting illustrative embodiments of the invention, in which like reference numerals represent similar parts throughout the drawings. As should be understood, however, the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
An inventive solution is presented to the need for a device or component in a security system that enables applications distinct from the security system to access the security system display devices, yet the component still maintains all the other features and benefits attributed to highly protected, impregnable security systems. The component can be either hardware or software or a combination of both.
In another embodiment, shown in
The interface 18 portion of the component 14 can be an Application Program Interface (API) that establishes a remote server application from an application server 24. The interface 18 provides tools to permit proper rendering to the security system display device 12. More than one display size and/or format for the display device 12 can be offered, and the interface 18 itself can be an API. As discussed above, various interfaces 18 can reside throughout the security system 10 as well as in the remote server application.
The table 16 of the component 14 empowers the security system 10 to have priority to properly and effectively take control of the display of the security system display device 12 for purposes of handling the life and/or safety on premise situations encountered by the security system 10. Situations requiring either notification on the display 12, or accepting input by a user at a touch screen display (not shown) need priority over programs or applications merely displaying their general information over the display device 12.
A set of table parameters 20 that describe the behavior of the system in time of conflict is stored in the table 16 of the component 14. A conflict is defined as how the display device 12 will behave for various situations or alarm conditions of the security system 10. These conditions can be established in cooperation with both the security system developers and the system's users. Examples of alarm conditions include fire alarm, burglar alarm, panic, trouble indicators, loss of air conditioning and/or heat, etc. This is not an exhaustive list, but is meant for illustrative purposes only.
Each conflict is associated with a form 22. The specific parameters 20 in the table 16 indicate what form 22 takes priority based on an event or alarm condition, and where to find that form 22, such as on the internet, on a local site, or stored within the security system 10. Other technical aspects regarding the security system and/or form implementation can also be included in a form 22. Specific parameters 20 in the table 16 can include event type (Event), Form, a location (Location) as to where to get the form, such as an address on a server, a persistence field (Persistence) that tells the system how that form 22 will behave and provides requirements to be satisfied to complete the form 22. Additional parameters 20 can be Event Priority, indicating, for example, that there is no higher priority event that could override this form 22 until satisfied, and Next Action that provides instructions regarding the next form 22 to implement. These instructions can be either directions to return to the previous form 22 that was on display immediately before the current form 22 became active, or a name of a specific form 22 that is to be displayed after satisfying all of the requirements in the Persistence parameter of the present form 22.
An example is provided for illustrative purposes. A fire alarm occurs in a residence having the inventive security system 10. Prior to the fire alarm, the display device 12 had been displaying a message from an application, e.g. a cable provider, indicating the top five movies available for special price on-demand viewing that night. The specific parameters 20 that control the behavior of the display device 12 are as follows. Event is “Fire Alarm”; Form is “fire.frm”, Location is “AlarmNet.com/customer-A” and Persistence is “Until code entry”. The Event Priority is “Event can disrupt”, and Next Action is “Return to form”. In this example, the form 22 will stay persistent until a proper code entry is made at the display.
The embodiments described above are illustrative examples and it should not be construed that the present invention is limited to these particular embodiments. Thus, various changes and modifications may be effected by one skilled in the art without departing from the spirit or scope of the invention as defined in the appended claims.
