Community-based security system

US11769395B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11769395-B2
Application numberUS-202217863282-A
CountryUS
Kind codeB2
Filing dateJul 12, 2022
Priority dateAug 31, 2018
Publication dateSep 26, 2023
Grant dateSep 26, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A server accesses a security system profile of a first security system. The security system profile identifies a plurality of sensors connected to the first security system. The server identifies a second security system based on at least a first sensor of the plurality of sensors coupled to the first security system. The server then generates a notification sharing profile for the first security system based on the security system profile. The notification sharing profile indicates that the second security system corresponds to the first sensor. A first event triggered by the first sensor causes a first notification to the second security system.

First claim

Opening claim text (preview).

what is claimed is: 1. A method comprising: detecting, at a server, an event generated by a first sensor that is externally coupled to a first security system; in response to detecting the event, identifying a second security system that is mapped to the first sensor; and generating, at the server, a message indicating the event wherein the first sensor is a water sensor, wherein the event indicates a water leak, wherein the first security system and the first sensor are located in a first geographical location, wherein the second security system is located in a second geographical location that is below the first geographical location. 2. The method of claim 1 , further comprising: mapping the first sensor to the second security system. 3. The method of claim 1 , further comprising: mapping an identification and a type of the first sensor to the second security system. 4. The method of claim 1 , further comprising: communicating the message to the second security system, the second security system configured to generate an alert based on the message. 5. The method of claim 1 , further comprising: communicating the message to a device registered with the second security system. 6. The method of claim 1 , further comprising: receiving, at the server, a remote command from the second security system in response to communicating the message to the second security system; and providing the remote command to the first security system. 7. The method of claim 1 , further comprising: accessing, at the server, a notification sharing profile of the first security system, the notification sharing profile comprising a mapping of the event, an identification of the first sensor, a type of the first sensor, and the second security system. 8. The method of claim 1 , further comprising: accessing, at the server, a notification sharing profile of the first security system, the notification sharing profile comprising a mapping of the event, an identification of a second sensor externally connected to the first security system, a type of the second sensor, and the second security system. 9. A server comprising: a processor; and a memory storing instructions that, when executed by the processor, configure the server to perform operations comprising: detecting an event generated by a first sensor that is externally coupled to a first security system; in response to detecting the event, identifying a second security system that is mapped to the first sensor; and generating a message indicating the event, wherein the first sensor is a water sensor, wherein the event indicates a water leak, wherein the first security system and the first sensor are located in a first geographical location, wherein the second security system is located in a second geographical location that is below the first geographical location. 10. The server of claim 9 , wherein the operations further comprise: mapping the first sensor to the second security system. 11. The server of claim 9 , wherein the operations further comprise: mapping an identification and a type of the first sensor to the second security system. 12. The server of claim 9 , wherein the operations further comprise: communicating the message to the second security system, the second security system configured to generate an alert based on the message. 13. The server of claim 9 , wherein the operations further comprise: communicating the message to a device registered with the second security system. 14. The server of claim 9 , wherein the operations further comprise: receiving a remote command from the second security system in response to communicating the message to the second security system; and providing the remote command to the first security system. 15. The server of claim 9 , wherein the operations further comprise: accessing a notification sharing profile of the first security system, the notification sharing profile comprising a mapping of the event, an identification of the first sensor, a type of the first sensor, and the second security system. 16. The server of claim 9 , wherein the operations further comprise: accessing a notification sharing profile of the first security system, the notification sharing profile comprising a mapping of the event, an identification of a second sensor that is externally connected to the first security system, a type of the second sensor, and the second security system. 17. A non-transitory computer-readable storage medium, the computer- readable storage medium including instructions that, when executed by a computer, cause the computer to perform operations comprising: detecting, at a server, an event generated by a first sensor that is externally coupled to a first security system; in response to detecting the event, identifying a second security system that is mapped to the first sensor; and generating, at the server, a message indicating the event wherein the first sensor is a water sensor, wherein the event indicates a water leak, wherein the first security system and the first sensor are located in a first geographical location, wherein the second security system is located in a second geographical location that is below the first geographical location.

Assignees

Inventors

Classifications

  • G08B27/003Primary

    Signalling to neighbouring houses · CPC title

  • central annunciator means of the sensed conditions, e.g. displaying or registering · CPC title

  • Alarm destination chosen according to type of event, e.g. in case of fire phone the fire service, in case of medical emergency phone the ambulance · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11769395B2 cover?
A server accesses a security system profile of a first security system. The security system profile identifies a plurality of sensors connected to the first security system. The server identifies a second security system based on at least a first sensor of the plurality of sensors coupled to the first security system. The server then generates a notification sharing profile for the first securi…
Who is the assignee on this patent?
Nortek Security & Control Llc
What technology area does this patent fall under?
Primary CPC classification G08B27/003. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 26 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 6 related publications on this page (citations in our corpus or others sharing the same primary CPC).