[go: up one dir, main page]

EP4560599A1 - Sicherheitsüberwachungssysteme und -verfahren - Google Patents

Sicherheitsüberwachungssysteme und -verfahren Download PDF

Info

Publication number
EP4560599A1
EP4560599A1 EP23383199.9A EP23383199A EP4560599A1 EP 4560599 A1 EP4560599 A1 EP 4560599A1 EP 23383199 A EP23383199 A EP 23383199A EP 4560599 A1 EP4560599 A1 EP 4560599A1
Authority
EP
European Patent Office
Prior art keywords
event
installation
notification
premises
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23383199.9A
Other languages
English (en)
French (fr)
Inventor
Linnea AHLBECK
Russel MORGAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Verisure SARL
Original Assignee
Verisure SARL
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Verisure SARL filed Critical Verisure SARL
Priority to EP23383199.9A priority Critical patent/EP4560599A1/de
Priority to PCT/EP2024/083036 priority patent/WO2025109029A1/en
Publication of EP4560599A1 publication Critical patent/EP4560599A1/de
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/001—Alarm cancelling procedures or alarm forwarding decisions, e.g. based on absence of alarm confirmation
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/008—Alarm setting and unsetting, i.e. arming or disarming of the security system
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B29/00—Checking or monitoring of signalling or alarm systems; Prevention or correction of operating errors, e.g. preventing unauthorised operation
    • G08B29/18—Prevention or correction of operating errors

Definitions

  • the present invention relates to security monitoring systems and methods.
  • Security installations that are or include security monitoring systems for monitoring premises, often referred to as alarm systems, typically provide a means for detecting the presence and/or actions of people at the premises and reacting to detected events.
  • alarm systems typically provide a means for detecting the presence and/or actions of people at the premises and reacting to detected events.
  • Such systems include sensors to detect the opening and closing of doors and windows to provide a secure perimeter to the premises, creating one or more protected interior spaces, movement detectors to monitor spaces (both within and outside buildings) for signs of movement, microphones to detect sounds such as breaking glass, and image sensors to capture still or moving images of monitored zones, and optionally smoke and/or fire detectors.
  • Such systems may be self-contained, with alarm indicators such as sirens and flashing lights that may be activated in the event of an alarm condition being detected.
  • Such installations typically include a control unit (which may also be termed a central unit), generally mains powered, that is coupled to the sensors, detectors, cameras, etc. ("nodes"), and which processes received notifications and determines a response.
  • the central unit may be linked to the various nodes by wires, but increasingly is instead linked wirelessly, rather than by wires, since this facilitates installation and may also provide some safeguards against sensors/detectors effectively being disabled by disconnecting them from the central unit.
  • the nodes of such systems typically include an autonomous power source, such as a battery power supply, rather than being mains powered.
  • a security monitoring system may include an installation at a premises, domestic or commercial, that is linked to a remote Central Monitoring Station (CMS) or Alarm Receiving Centre (ARC) (the terms are interchangeable) where, typically, human operators manage the responses required by different alarm and notification types.
  • CMS Central Monitoring Station
  • ARC Alarm Receiving Centre
  • the central unit at the premises installation typically processes notifications received from the nodes in the installation and notifies the Central Monitoring Station of only some of these, depending upon the settings of the system and the nature of the detected events.
  • the central unit at the installation is effectively acting as a gateway between the nodes and the Central Monitoring Station.
  • the central unit may be linked by wires, or wirelessly, to the various nodes of the installation, and these nodes will typically be battery rather than mains powered.
  • the personnel of the CMS may raise an alarm with the police or other emergency services (such as a Fire Brigade, or a medical service) in the event that an alarm notification is received from the monitored premises.
  • emergency services such as a Fire Brigade, or a medical service
  • frequently penalties e.g. significant fines
  • a provider of a managed alarm service raises with the emergency service an alarm (or more than a certain number of alarms within a predetermined period) where the alarm(s) turn out to be false alarms.
  • a service provider may even be prohibited from reporting alarm events at all. Consequently, service providers try to ensure that alarm events are only notified to the emergency services once they have been confirmed in some way - for example by performing a visual check of feeds from cameras installed at the premises, or by listening to sounds (e.g.
  • Such security monitoring systems contribute to the safety and wellbeing of occupants of the protected premises, as well as safeguarding articles within the protected perimeter - which may of course not simply be limited to a house or dwelling but may also extend to the grounds of the house, protected by a boundary fence and gate, for example.
  • a centrally monitored security monitoring system only reports alarm events if the system is armed - with the possible exceptions of fire and smoke detection, SOS alerts or the triggering of a personal alarm of the type worn or carried by the elderly or infirm.
  • SOS alerts or the triggering of a personal alarm of the type worn or carried by the elderly or infirm.
  • the security monitoring system may be disarmed when children are home alone but a potential threat may be recognised in the presence of a person in the garden of the premises (although the same threat may also be recognised when the security monitoring system is in an "armed at home” mode).
  • the security monitoring system may be disarmed to allow a cleaner to perform cleaning duties within the protected premises but part of the premises may be "out of bounds", for example a home office, and thus detection of the presence of someone within the home office may be cause for alarm (again, the same threat may also be recognised when the security monitoring system is in an "armed at home” mode).
  • detection of a person, or of some other event may indicate the existence of a threat or cause for alarm even though the security monitoring system is disarmed. But of course the same events may be entirely innocent and non-threatening - it all depends upon their context.
  • Embodiments of the present invention seek to provide enhanced security monitoring systems, and corresponding applications, methods and other implementations that improve the ability of security monitoring systems for handling potential alarm events that are detected preferably while a premises security monitoring system is in a disarmed mode or optionally in an armed at home mode, as well as providing corresponding new functionality and methods.
  • a security monitoring system installation at premises protected by the installation and optionally a system back end remote from the premises comprising:
  • the detecting the occurrence of an event and the transmission of a notification in respect of the event may occur while the security monitoring system is in its disarmed mode.
  • the method of the first aspect may further comprise the step of reporting, prior to step ii), the occurrence of the event to a system back end remote from the premises, wherein the system back end performs either of steps ii) or iii).
  • the step of transmitting a notification in respect of the event to a user device is performed by the security monitoring installation, wherein the security monitoring installation performs either of steps ii) or iii), optionally wherein the installation comprises a controller, and the step of transmitting a notification in respect of the event to a user device is performed by the controller, and wherein the controller performs either of steps ii) or iii).
  • the notification in respect of the event may include at least one of:
  • the event may be at least one selected from:
  • whether the notification of step ii) is transmitted or not may depend upon at least one condition selected from: the time of day, day of the week, date, nature of the event, or some combination thereof.
  • the notification may further include context information, the context information distinct from the event data and complementing the event data, optionally wherein the context information includes one or more selected from: the arm state; occupation state of the premises; camera identity; status of other detectors at the premises.
  • a security monitoring installation at premises protected by the installation and optionally a system back end remote from the premises, the security monitoring installation having a plurality of arm states and being configured to report to a monitoring station remote from the premises, the method comprising:
  • a system that comprises a security monitoring installation at premises protected by the installation and a system back end remote from the premises, the security monitoring installation having a disarmed mode and at least one armed mode the security monitoring installation having a controller and a plurality of sensors configured to transmit event notifications to the controller, the controller being configured when the system is in an armed mode to report alarm events to a monitoring station remote from the premises, the controller having at least one operating mode in which it is configured to respond to receiving certain event notifications, optionally while the installation is in the disarmed mode, by transmitting an alert, in respect of the notification of an event, to the system back end remote from the premises, the system back end being configured to:
  • a security monitoring installation at premises protected by the installation having a disarmed mode and at least one armed mode
  • the installation comprising a controller and a plurality of sensors configured to transmit event notifications to the controller, the controller having at least one operating mode in which it is configured to respond to certain event notifications, optionally while the installation is in the disarmed mode, by:
  • the transmitted notification in respect of the event may include at least one of:
  • the event may be at least one selected from:
  • whether the notification of i) is transmitted or not may depend upon at least one condition selected from: the time of day, day of the week, date, nature of the event, or some combination thereof.
  • FIG. 1 shows a view of the front of a premises 100 protected by a security monitoring system according to an aspect of the present invention.
  • the premises here is in the form of a house, surrounded by a garden defined in part by a border fence 101 to the rear and sides of the property.
  • the house has at least one exterior door, here front door, 102.
  • the door gives access to a protected interior space.
  • the security monitoring system secures at least part of a perimeter to the premises 100, and the door constitutes an exterior closure 102 in the secure perimeter giving access to a protected interior space 201 of the premises.
  • a lock 104 on the exterior door is optionally electrically controlled so that it can be locked and unlocked remotely.
  • a first video camera in the form of a video doorbell 106 which looks out from the facade of the premises so that anyone approaching the door along the path 108 can be seen, and in particular when a visitor stands at the door their face should clearly be visible.
  • the video doorbell includes an actuator, e.g. a push button, for a visitor to indicate their presence at the closure.
  • the video doorbell also includes an audio interface to enable bidirectional audio communication with a visitor at the closure 102.
  • the video doorbell preferably includes an infrared light source to illuminate whatever or whoever is in front of the video doorbell.
  • the facade of the house also carries an external keypad, or access node, 110 by means of which a user can disarm the security monitoring system, and unlock the lock 104 if fitted, by entering an access code or by presenting a security tag, dongle, or suitably coded mobile device - for example using NFC.
  • an optional second video camera 112 which is coupled to a presence and/or movement detector 114.
  • the detector may optionally be a thermal detector, for example a PIR sensor.
  • the second video camera 112 may be arranged to capture video of the front of the house and the private area, e.g.
  • the second video camera is preferably provided with an audio interface 116 to enable bidirectional audio communication with anyone observed by the second video camera.
  • the first video camera is illustrated in the form of a video doorbell, the first video camera may additionally or alternatively have the features described above for the second video camera, whether or not plural video cameras are used.
  • a further video camera may also be provided to the rear and or side of the house to capture video of the side and/or rear of the house and the private area, e.g. the garden, to the side or rear of the house and to signal events to a controller of the security monitoring system.
  • the further video camera is preferably provided with an audio interface 116 to enable bidirectional audio communication with anyone observed by the further video camera.
  • the security monitoring system may provide the following arm state options:
  • FIG. 2 is a schematic part plan view of a premises 100 protected by security monitoring system according to an aspect of the invention, together with other elements of the system, corresponding generally to the premises of figure 1 .
  • the front door 102 with the optional electrically controlled lock 104, leads into an entrance hall 200 that is part of the protected interior space of the premises which also includes a study or home office 201.
  • Each of the windows 202, and external doors is fitted with a sensor 206 (e.g. contact switch) to detect when the door is opened.
  • Each of the sensors 206 preferably includes a radio transceiver to report events to a controller , or central unit, 208 of the security monitoring system.
  • a signal is sent to the central unit 208 which in turn may (typically depending upon that arm state of the security monitoring system) signal an alarm event to a remote central monitoring station 210.
  • the central unit 208 is preferably connected to the remote central monitoring station 210 via the Internet 211, via a wired or a wireless connection, or both.
  • the security monitoring installation at the premises is also coupled to a system back end 230 (typically comprising one or more servers with associated memory, programs and data storage) which may be functionally separate from the central monitoring station 210 or they may form part of a common back end function 240 - although of course whether or not the back end function and the central monitoring station form a common back end function, their hardware may be co-located or located at different geographical sites, and the human operators may be co-located with the relevant system hardware or access it through terminals that are themselves remote from the relevant hardware.
  • the central monitoring station 210 is able to call upon the emergency services (e.g. police, fire brigade, medical) 250.
  • emergency services e.g. police, fire brigade, medical
  • a control panel 227 may also be provided, for example within the protected space of the premises, for the arming and disarming of the security monitoring system.
  • These items, and the sensors 206 are preferably coupled to the central unit 208 using transceivers operating in the industrial scientific and medical (ISM) bandwidths, for example a sub-gigahertz bandwidth such as 868 MHz, and the communications are encrypted preferably using shared secret keys.
  • ISM industrial scientific and medical
  • the security monitoring system may also include other sensors within the protected interior space, such as an interior video camera 214 and associated movement detector 216 (which again may be integral with the camera 214), and each of the interior doors 218 may also be provided with a sensor 206 to detect the opening/closing of the door.
  • One or more fire and/or smoke detector nodes 252 may also be provided within the protected premises.
  • a user device 220 such as a smartphone
  • PLMN public land mobile network
  • the study 201 may include a stand-alone motion sensor, such as a PIR, 216' to detect presence or motion within the room.
  • the motion sensor may be a "smart" motion sensor such as one that uses artificial intelligence to help distinguish between the presence of an animal, such as a pet dog or pet cat, and a human.
  • Such sensors can distinguish reliably between movement of a pet animal and movement of a human who crawls along the floor, for example, and can readily distinguish between a standing or crouching human and a pet animal.
  • Such smart motion/presence sensors can contribute significantly to a reduction in the incidence of false alarms.
  • the study 201 may also include a camera, optionally a video camera, 214' which may include or be associated with a smart motion/presence sensing detector.
  • one or more cameras of the installation may be configured to capture images continuously or quasi continuously, the captured images then being shared with an image analysis system or arrangement that detects the existence of motion by analysing differences between images taken at different times.
  • the image analysis system or arrangement being arranged to provide a "motion detected" signal, for example to a controller of the installation, so that the detection of motion can be used as a trigger for further action. Examples of such an approach are described further with reference to figures 7 and 8 .
  • operation of the security monitoring system may be controlled by one or more of: the controller 208, the control panel 227, the remote monitoring station 210, and a security monitoring app installed on the user device 220.
  • the remote monitoring station 210 may receive one or more signals from any of the first camera and/or video doorbell 106, the second camera 112/212, the keypad 110, the sensors 206,252 .
  • the remote monitoring station 210 may transmit commands for controlling any one or more of: the arm state of the alarm system (e.g. armed or unarmed); commanding a tripped alarm state to be signalled by the alarm system (e.g. by triggering one or more sirens to generate alarm noise); commanding a lock state of the door lock 104 (e.g.
  • Communication with the remote monitoring station 210 may pass through the controller 208, as described above. In other embodiments without the remote monitoring station 210, or should communication with the remote monitoring station 210 be interrupted, operation of the alarm system may be controlled by the controller 208. In yet other embodiments, the controller 208 may be omitted, and the individual peripheral devices may communicate directly with the remote monitoring station 210 and/or system back end 230/240.
  • the security monitoring system app is installed on a user device 220, here shown as a smartphone, although of course it could be almost any kind of electronic device, such as a laptop or desktop computer, a tablet such as an iPad, a smart watch, or even a television
  • the security monitoring installation may be configured without a central unit 208, the various nodes/sensors/cameras of the installation instead working on an edge computing basis, either each communicating directly with the remote monitoring station 210, system back end 230, or common back end function 240 (or at least having the inbuilt capability to do this), or one or more of the nodes/sensors/cameras/control panels acting as a gateway for the other nodes/sensors/cameras/control panels.
  • at least the nodes/sensors/cameras/control panels that act(s) as the gateway may be powered from a mains power source (with battery back-up).
  • the nodes/sensors/cameras/control panels may form a self-organising system.
  • the security monitoring system may further comprise an audio interface to enable audio communication with a visitor at the closure 102, or at or within sight of any of the image capture devices (e.g. cameras or video cameras) of the installation, the controller 208 being configured to enable the remote monitoring centre 210 to use the audio interface to speak to the visitor (who may be a potential intruder).
  • the control panel 227 may include an audio interface to enable audio communication with the central monitoring station and optionally the user device (for example via the system back end 230/240).
  • the security monitoring system may be set instead to an armed at home state in which the periphery is secured so that later arrivals either need to disarm the system before opening an external access door, or the new arrival or one of the earlier arrivals needs to take appropriate action to avoid triggering an alarm event when an external access door has been opened - such as entering a code or presenting a security token to an internal control panel 227.
  • the children's parent(s) may be sufficiently concerned about the children's safety and wellbeing while they are home alone (i.e. without a responsible adult) that the parent(s) want to be alerted in the event that, for example, a human presence (or what could be a human presence) is detected in the vicinity of the home - for example in the back garden.
  • Human presence may be detected by a motion sensor, especially by a smart motion sensor - either freestanding or associated with (e.g. part of) an image capture device such as a camera or video camera.
  • Human presence may additionally or alternatively be sensed based on analysis of one or more images captured by a camera or video camera, for example using image analysis within or external of the image capture device.
  • the security monitoring system may be configured (e.g. programmed) to cause notifications to be sent to the parent(s) e.g. to one or more WTRU device associated with the parent(s) in the event that one or more sensors/nodes/cameras detects possible human presence within the monitored area.
  • notifications preferably contain information that provides a context of the event - for example that the house is occupied only by vulnerable people (one or more children, or another vulnerable person/people) or predominantly vulnerable people - something which may be determined by capturing identities of the person/people disarming the installation using tag/device identity or PIN identity (i.e. by using individual PINs for different authorised users).
  • the installation may allow one or more particular individuals to indicate that a responsible adult is now present, for example by entering a particular code or presenting a particular tag/dongle or mobile device, or choosing a different setting at a control panel for the installation, so that the sending of notifications in this way can be turned off when no longer appropriate.
  • An alarm event may only be determined to exist based on outputs of a combination of sensors - such as, in addition to an image capture device or motion sensor sensing potential human presence, a door/window sensor sensing vibration or shock if the detected person tries to open or attack a door or window, or a microphone capturing sounds indicative of a potential break-in (e.g. the sound of breaking glass).
  • sensors such as, in addition to an image capture device or motion sensor sensing potential human presence, a door/window sensor sensing vibration or shock if the detected person tries to open or attack a door or window, or a microphone capturing sounds indicative of a potential break-in (e.g. the sound of breaking glass).
  • protected premises may contain a room or other place from which the owner wants to exclude others - or at least to exclude unauthorised visitors - for example a home office or an art gallery or collection space with valuable or prized exhibits.
  • the owner may employ a cleaner or other support staff who are free to wander over the protected premises apart from such no-go areas.
  • FIG 3A illustrates schematically, at a high level, a method according to an aspect of the invention.
  • the premises installation 200 which may correspond to the installation described with reference to Figures 1 and 2 , is in a disarmed or armed at home state, for example following the return of young schoolchildren from school.
  • an event is detected by a sensor or node of the installation, for example a motion sensor associated with a camera, such as camera 212, overlooking the back garden is triggered.
  • the triggered sensor will send an event alert message to the central unit, and the central unit will then process the alert message at 302.
  • the event alert message/report preferably includes parameters of the event, the sensor's identity and if relevant the nature of the event detected.
  • camera 212 may be arranged to capture an image (e.g. a still image or a brief video clip) upon its associated (possibly internal) motion sensor being triggered, and then to send an event alert, optionally including the captured image, to the central unit.
  • the central unit determines that despite the arm state of the installation being disarmed, or merely armed at home, a user is to be notified of the event. Based on this determination, the central unit then reports to the back end system 230/240 the occurrence of an event at the premises 100.
  • a processor of the triggered sensor will at step 302 process the event data to determine how it should be handled. Based on the prevailing system settings the processor may determine that despite the arm state of the installation being disarmed, or merely armed at home, a user is to be notified of the event. Based on this determination, at step 304 the sensor's processor then reports to the back end system 230/240 the occurrence of an event at the premises 100, for example using a PLMN.
  • the event alert message/report preferably includes parameters of the event, the sensor's identity and if relevant the nature of the event detected.
  • the senor is a camera, such as camera 212, it may be arranged to capture an image upon its associated (possibly internal) motion sensor being triggered, and then to send an event alert, optionally including the captured image, to the back end system 230/240.
  • the back end system 230/240 processes the alert, determining the nature of the alert and identifying the installation from which the report was received, and based upon this identification determining relevant user contact details (such as SIP address, mobile device number, etc.) to be used for any user contact.
  • the back end system 230/240 transmits parameters of the event to a user device 220, for example in the form of a push notification.
  • the parameters transmitted at this stage may be the same as those received from the installation 200, for example if the received parameters comprise an image file or video clip the image file or video clip (optionally including both sound and visual components) is forwarded to the user device.
  • received image/video content may be labelled or tagged to identify the precise source of the image/video capture.
  • Additional or alternative parameters may be transmitted to the user device, for example a textual or graphical message may be composed to inform the user of the type of sensor (e.g. door or window sensor, shock sensor, smoke detector, fire detector, motion detector) and/or its location (e.g.
  • a graphical display format may be used to facilitate comprehension both of the location of the event (e.g. by including an outline map to indicate the location of the detected event with respect to an outline or plan of the protected premises, and/or by labelling the display with a name of the location) and the nature (motion detection, person detection, door/window sensor (+ type) triggered) and/or severity of the event.
  • the parameters received at the user device are displayed on a display of the device 220.
  • the user device 220 will typically host an app for the security monitoring system, to enable the user to view communications from the system back end 230/240, images/video from cameras at the installation (e.g. from a doorbell camera of the installation) and also optionally to enable a user to speak to someone at the video doorbell, or at other nodes of the installation.
  • the parameters are preferably sent in a push notification that will display on lock-screen or at least give rise to a user alert on the device to prompt the user to view the notification.
  • the notification may be an action notification that includes, for example, an action button or that permits a user to respond by clicking or "pushing" on the notification as a way to enter a response.
  • the received parameters include a video clip or image
  • the user may be able to indicate a part of the image - e.g. a person or a person's face, by "drawing" (i.e. annotating) on the display using a finger, finger nail, or stylus, for example, to enable the user to identity a person (or some other thing) - e.g. to indicate someone whose presence is unauthorised or otherwise problematic, so that personnel at the central monitoring station can take appropriate action.
  • the notification may include an icon or button for the user to indicate that there is no cause for alarm (e.g., an "all OK" button).
  • the app may be configured to communicate with the system backend 230/240 to inform the backend that the notification has been displayed. If the user is not concerned by the displayed event and its details they may choose to provide no response. In which case no response is sent to the system back end, and hence there is no escalation of the event to the remote monitoring station.
  • the notification may include an option for the user to respond to indicate the absence of any perceived threat/risk, in which case, at step 312 the user response is transmitted to the system backend 230/240. Again there is no escalation of the event to the remote monitoring station.
  • the system back end notifies the remote monitoring centre 210 - signifying the user's concern.
  • the remote monitoring centre 210 is also provided with access to the parameters of the event, together with any annotations or other input received from the user.
  • the parameters may be transmitted to the remote monitoring centre 210 by the system back end 230, or they may be made available in some other way - for example by being shared within the back end system 240, or a link provided to the remote monitoring centre 201 by means of which the parameters (such as any image capture or video content) may be downloaded or otherwise accessed by the remote monitoring centre 210.
  • the personnel in the remote monitoring centre 210 upon receiving notification of the event are made aware that a user was alarmed by the details of the event, based on the event context (e.g. the fact that the event occurred when children were home alone, and possibly the time of day) and the event data made available to the user (for example any image capture, video capture, audio, etc.).
  • the monitoring personnel are also able to review the event details and are further able to communicate with the monitoring installation, for example to request 316 access to further images or video from the relevant camera and also from any other cameras of the installation, and also to acquire audio from any microphones of the installation - all either via a central unit of the installation or directly with the relevant nodes if the installation does not include a central unit. Any requested captures or streams are provided by the installation to the remote monitoring centre 210 at step 318.
  • personnel in the remote monitoring centre 210 may for example be able to communicate orally with any intruder in the garden, for example by an audio interface in camera 212, hopefully to persuade them to leave the grounds of the premises, or the personnel may assess the situation and may report the incident to the emergency services or private security personnel if their involvement is required. Meanwhile, the personnel may liaise with the user via the user device, and optionally with those within the protected premises - for example via an audio interface in a control panel 227 of the installation.
  • Figure 3B corresponds generally to Figure 3A but illustrates a method in which the premises installation 200 is able to send notifications directly to the user device 220 rather than only via the system back end as in Figure 3A .
  • the premises installation 200 which may correspond to the installation described with reference to Figures 1 and 2 , is in a disarmed or armed at home state, for example following the return of young schoolchildren from school.
  • an event is detected by a sensor or node of the installation, for example a motion sensor associated with a camera, such as camera 212, overlooking the back garden is triggered.
  • the triggered sensor will send an event alert message to the central unit, and the central unit will then process the alert message at 322.
  • the event alert message/report preferably includes parameters of the event, the sensor's identity and if relevant the nature of the event detected.
  • camera 212 may be arranged to capture an image (e.g. a still image or a brief video clip) upon its associated (possibly internal) motion sensor being triggered, and then to send an event alert, optionally including the captured image, to the central unit. Based on the prevailing system settings the central unit determines that despite the arm state of the installation being disarmed, or merely armed at home, a user is to be notified of the event.
  • the central unit prepares a notification to report the event and its context to a user device whose contact details (e.g. SIP address or mobile phone number) may be stored in the central unit. Using these contact details the central unit pushes a notification to the user device at step 324.
  • contact details e.g. SIP address or mobile phone number
  • a processor of the triggered sensor will at step 322 process the event data to determine how it should be handled. Based on the prevailing system settings the processor may determine that despite the arm state of the installation being disarmed, or merely armed at home, a user is to be notified of the event. Based on this determination, at step 324 the sensor's processor then prepares a notification to reports the event and its context to a user device whose details may be stored in the relevant sensor, for example using a PLMN.
  • the event alert notification preferably includes parameters of the event, the sensor's identity and if relevant the nature of the event detected.
  • the sensor is a camera, such as camera 212, it may be arranged to capture an image upon its associated (possibly internal) motion sensor being triggered, and then to send an notification, optionally including the captured image, to the relevant user device 220.
  • the display of the notification on the display of the user device, at step 326, and the following steps 328 to 336 correspond generally to steps 310 to 318 of Figure 3A and the above description of these applies equally in respect of Figure 3B .
  • Figure 4 illustrates schematically a method 400 according to an aspect of the invention in which an event at the premises 100 is captured as an image capture or video.
  • a security monitoring installation at premises is in a disarmed state or in an armed at home state, and an event occurs at the protected premises leading to an image capture, for example as the result of a motion detector of or associated with a camera having been triggered.
  • the camera may, for example, be a camera such as camera 212 having a view of the back garden of the protected premises. Triggering of the motion sensor results in activation of the associated camera and an image capture of the event either as one or more still images or in the form of a video sequence.
  • the camera transmits the captured image to the system backend, preferably together with status information for the security monitoring installation such as arm state, occupant details or occupancy status (either in detail, e.g. with names of those determined to be present, or in terms of the presence of a least one "vulnerable" individual (e.g. a child or elderly or infirm person_ and the absence of a carer or responsible adult (e.g. possibly determined by the fact that no such person has touched in or entered the appropriate passcode or PIN)), and such other information as may be helpful in terms of giving a user context for the detected event.
  • these data may be transmitted from the triggered node (e.g. camera) over a Wi-Fi link to a Wi-Fi router of the premises and thence via the Internet to backend 230/240.
  • the camera may initially just provide a still image capture.
  • the camera may stream the video so that the back end receives a continuous or quasi-continuous video stream, or the camera may transmit a subset of the available video, in the form of one or more still images or video clips.
  • the capture may also include an audio channel which is also transmitted to the system backend 230/240.
  • the transmission(s) to the system backend 230/240 includes an identifier of some kind so that the backend knows from which security monitoring installation (and hence which premises) the event capture is being received.
  • the system backend includes a database that maps installations/premises with a user identity.
  • the system backend For each user identity the system backend preferably also stores contact details, including for example a SIP address, device phone number, other contact numbers and email addresses for each user identity, optionally in the same database that maps installations/premises with a user identity.
  • the system back end determines contact details for a user device to be contacted in case of alarm events.
  • the system backend pushes a notification to the relevant device at step 406.
  • the pushed notification includes the event capture (e.g. the image capture) and/or a link to any video stream, preferably together with an identifier or indication of the source of the event capture - e.g. a name assigned to the camera such as "Back Garden Camera", optionally also with an indication of the time and date of the event capture.
  • the user interacts with the user device to access the notification, causing the event capture (e.g. image capture) to be displayed on a display of the user device at step 408.
  • the event capture e.g. image capture
  • This may involve the user clicking on (or otherwise selecting) a link to a remote site from which the video may be downloaded or streamed.
  • the user views the image capture (image or video clip or stream) on the user device to determine whether or not the notified event raises any cause for concern. If the event doesn't give rise to any concerns, the user may click on an icon, button or the like to indicate that no issues arise - the icon or button optionally being labelled with a designation signifying that no issues arise - e.g.
  • a user may indicate a lack of concern, and hence no interest in the event being escalated to the remote monitoring centre, by failing to provide an active response - in which case the detected event will not be reported to the monitoring station as an alarm event (and in general my not be reported to the monitoring station at all, but may be logged as a "negative event” -i.e. one in response to which the user did not raise an alert) .
  • the app in the user device is preferably configured to signal to the system backend the fact of the event capture having been displayed.
  • the system backend may then set a timer at the expiry of which, if no active response has been received, it can be assumed that the user has no interest in escalating the event to the ARC.
  • This method of indicating user indifference may be used selectively, for example only for events that are perceived to be unlikely to be threatening - and that may be based on time of day, location of the relevant video camera, and whether other nodes of the installation have also been triggered.
  • the user may take an action to indicate that they wish the event to be flagged to the remote monitoring station 210.
  • Such an action may be to interact with an icon or button colour coded red, or labelled with a designation signifying that there is a problem or that the event notification causes the user alarm - e.g. "Escalate to ARC", “action required", “I don't like this", etc..
  • the user may be able to indicate concern by pressing on the display on which the event capture is being displayed.
  • the user may have the option to draw on the image capture (either in the form of a still or in the form of a video sequence) to draw around a feature of the displayed image or to add a label or tag, to indicate a person or some other feature of the displayed image (video) whose presence gives rise to concern - e.g. to indicate a stranger or a known person whose presence is unwelcome.
  • the drawing, tagging, or labelling may be captured in the form of a layer or overlay whose details may be transmitted to the system backend for sharing, by onward transmission or otherwise, with the remote monitoring centre 210.
  • the system backend determines the user reaction, optionally by receiving an indication of the perception of a threat or by receiving an indication that the event gives the user no cause for concern.
  • a user may also indicate that an event is not a cause for concern by not providing any overt response, with the system backend determining no cause for concern if no response is received from the user within a predetermined period.
  • the system back end ends the process at step 414 and does not escalate the event to the remote monitoring centre.
  • the system back end at step 416 shares the event details and context (e.g. installation status/occupation status, etc) and raises an alert with the remote monitoring centre.
  • the sharing of event details may involve the system backend transmitting the event capture (e.g. image capture or video capture) to the remote monitoring centre, particularly if the system backend 230 and the remote monitoring centre 210 are not integrated, but as an alternative the backend may simply share a link with the remote monitoring centre 210. If the system backend 230 and the remote monitoring centre 210 are integrated, the system may be so arranged that the remote monitoring centre 210 is able to access any image (e.g.
  • an escalation event which will typically include a unique identifier and/or an identifier for the premises installation together with a timestamp
  • the remote monitoring centre 210 also makes available the corresponding event parameters (e.g. video capture or video stream) and context.
  • the remote monitoring centre 210 reviews the event, based on the knowledge that the user is concerned by what they saw in the event capture (e.g. image capture or video), and makes any necessary escalation to emergency services, or calls in private security personnel as required.
  • the remote monitoring centre 210 preferably has the ability to command the central unit 208 of the installation to activate other cameras, microphones, speakers, etc., so that its personnel can obtain a fuller picture of the situation at the protected premises - enabling them to make better informed decisions about escalating an event to the emergency services. In this way the incidence of an event being escalated to the emergency services as the result of a false alarm is likely to be reduced.
  • FIG 5 illustrates schematically, at a high level, another method 500 according to an aspect of the invention.
  • a security monitoring installation controller such as the device 208 shown in Figure 2 .
  • the security monitoring installation was treated as an entity without further consideration of interaction between elements of the installation.
  • the nodes of the security monitoring installation may be configured as IoT terminals which communicate with each other and with the system backend, the installation being configured without a local control unit such as 208.
  • system back end 230 and the alarm receiving centre may be separate entities, or they may each form part of an integrated whole 240 within which event data and parameters received by the system back end 240 may be made available to the central monitoring station 210 without the need for an explicit transmission step.
  • a node of the security monitoring installation is triggered. This may happen irrespective of the arm state of the installation.
  • the node may for example be a video camera with an associated motion sensor (e.g. an internal or external PIR or radar sensor) such as camera 112, 212, 214, a door or window contact sensor such as 206, a shock sensor mounted on a window or door, a fire or smoke sensor 252, a keypad 110 or control panel 227, a movement detector 216, a video doorbell 106, a microphone, or some other device.
  • an associated motion sensor e.g. an internal or external PIR or radar sensor
  • the node may for example be a video camera with an associated motion sensor (e.g. an internal or external PIR or radar sensor) such as camera 112, 212, 214, a door or window contact sensor such as 206, a shock sensor mounted on a window or door, a fire or smoke sensor 252, a keypad 110 or control panel 227, a movement detector 216, a video
  • the system backend 230/240 processes the information received from the control unit of the installation.
  • the transmission to the system backend 230/240 includes an identifier of some kind so that the backend knows from which security monitoring installation (and hence which premises) the event capture is being received.
  • the system backend includes a database that maps installations/premises with a user identity. For each user identity the system backend also stores contact details, including for example SIP addresses, device phone numbers, other contact numbers and email addresses for each user identity, optionally in the same database that maps installations/premises with a user identity.
  • the system back end determines contact details for a user device to be contacted in case of alarm events.
  • the user interacts with the user device to access the notification, causing the video capture to be displayed on a display of the user device at step 512.
  • This may involve the user clicking on (or otherwise selecting) a link to a remote site from which a video may be downloaded or streamed.
  • the user views the event capture (image, video clip or stream) on the user device to determine whether or not the event capture raises any cause for concern. If the event capture doesn't give rise to any concerns, the user may click on an icon, button or the like to indicate that no issues arise - the icon or button optionally being labelled with a designation signifying that no issues arise - e.g.
  • a user may indicate a lack of concern, and hence no interest in the event being escalated to the remote monitoring centre, by failing to provide an active response. If this mode of providing an indication of indifference is supported the app in the user device is preferably configured to signal to the system backend the fact of the event parameters having been displayed. The system backend may then set a timer at the expiry of which, if no active response has been received, it can be assumed that the user has no interest in escalating the event to the ARC.
  • colour coded e.g. colour coded green for safe
  • the system backend determines the user reaction, optionally by receiving an indication of the perception of a threat or by receiving an indication that the event gives the user no cause for concern.
  • a user may also indicate that an event is not a cause for concern by not providing any overt response, with the system backend determining no cause for concern if no response is received from the user within a predetermined period.
  • the system back end ends the process and does not escalate the event to the remote monitoring centre 210.
  • the system back end at step 520 shares the event details and context and raises an alert with the remote monitoring centre.
  • the sharing of event details may involve the system backend transmitting an image or video capture to the remote monitoring centre, particularly if the system backend 230 and the remote monitoring centre 210 are not integrated, but as an alternative the backend may simply share a link with the remote monitoring centre 210.
  • the system may be so arranged that the remote monitoring centre 210 is able to access any image/video capture for which it receives a relevant identifier - so that the system backend, by raising an escalation event (which will typically include a unique identifier and/or an identifier for the premises installation together with a timestamp) with the remote monitoring centre 210 also makes available the corresponding event parameters (e.g. image/video capture or video stream).
  • an escalation event which will typically include a unique identifier and/or an identifier for the premises installation together with a timestamp
  • the remote monitoring centre 210 reviews the event, based on the knowledge that the user is concerned by what they saw in the event capture in association with the parameters provided for the captured event, and makes any necessary escalation to emergency services, or calls in private security personnel as required.
  • the remote monitoring centre 210 preferably has the ability to command the central unit 208 of the installation to activate other cameras, microphones, speakers, etc., so that its personnel can obtain a fuller picture of the situation at the protected premises - enabling them to make better informed decisions about escalating an event to the emergency services. In this way it is possible to escalate to the monitoring station an event occurring while the installation is disarmed or in an armed at home mode while minimising the incidence of events being escalated to the emergency services as the result of a false alarm.
  • FIG 6 is a flow chart corresponding generally to Figure 5 , illustrating a method 600 according to an aspect of the invention performed by a system including a security monitoring installation that includes a central unit, such as element 208 of Figure 2 .
  • a camera such as any one of cameras 112, 212, 214, is triggered by some kind of motion detector/sensor (e.g. PIR or radar sensor) that is either integral with the camera, or external to the camera but operatively associated with the camera.
  • some kind of motion detector/sensor e.g. PIR or radar sensor
  • an event is detected by a motion sensor of or associated with a camera such as camera 214' of Figure 2 .
  • the security monitoring installation is in a mode other than a fully armed mode, for example a disarmed mode or an armed at home mode.
  • domestic staff such as a cleaner
  • the out of bounds area could be any kind of room, space or zone.
  • the motion sensor that has been triggered is one associated with the camera 214' in the out of bounds study 201. The cleaner has, against his instructions, entered the study 201.
  • Triggering of the motion sensor activates the camera 214' which captures an image of the interior of the study 201.
  • the image capture is transmitted by the camera 214' to the central unit 208, for example over Wi-Fi of using a narrow bandwidth channel such as a channel of an ISM radio band.
  • the camera may continue to capture images/video after being triggered until commanded to stop (by the central unit, for example), or may continue to capture images for a predetermined time after movement was last detected.
  • the central unit 208 processes the reported event details based on the state of the installation and any stored rules.
  • the stored rules dictate that the triggering of a motion sensor in the study 201, when the installation is in a disarmed or armed at home mode, be reported to a (specified) user.
  • triggering of a motion sensor in the study 201 results in an alarm event being reported to the system backend 230/240 or to the remote monitoring station 210.
  • the central unit 208 transmits the event details, including the image capture, and context data to a (or the) relevant user device.
  • This transmission may be direct, for example using a 4G/5G transmitter (or transceiver) in the central unit to transmit a message by a suitable PLMN to the user device using address details stored by or accessible by the central unit.
  • the transmission may be via a system backend as described generally with reference to Figure 5 .
  • the user device 220 displays the image capture on the display of the device, preferably together with at least some of the supplied context (arm status, when the arm status was changed, by whom (if known from dongle/device ID or from the passcode's allocation if available).
  • the user device 220 receives a user input, for example in the form of a touch input on a touch sensitive display of the device, in response to the displayed image capture e.g. a force touch input to signify the user's desire to escalate the event to the remote monitoring station.
  • the notification received at the user device may include one or more "action elements" providing the user with predefined actions that can be invoked by interacting with the relevant action element.
  • the action elements may be icons or "buttons" with which the user may interact (by touching, force touching/pressing, or otherwise selecting) to select the relevant element to produce a corresponding action or to indicate a reaction.
  • the reaction may be one signifying that the user is unconcerned by the reported event, or one requesting that the event be escalated to (passed to) the remote monitoring station, or some other action such as connecting the user device to an audio interface at the installation - for example an audio interface of the camera 214', so that the user can speak to the cleaner while the cleaner is in the study, or via another audio interface if the cleaner has already left the study. So, for example, if the cleaner is new, the user can remind the cleaner that he is not supposed to clean the study. Conversely, the cleaner may be able to explain that they entered to study to retrieve the family cat that was mewing to be let out.
  • the action elements may also permit staged responses - such as an initial response in which the user can start a dialogue with the cleaner and then a follow up action in the event that the cleaner does not leave the study when asked, or is seen performing actions suggestive of theft or snooping - in which case the user may have the option to raise a high level alert with the remote monitoring station.
  • the system backend determines the user reaction based on any response received from the user device, or based on a lack of overt response, which indicates or is suggestive of indifference or a lack of perceived threat. If the user provides an active response indicating that no threat is perceived, or if user indifference can be inferred, for example by the lack of any timely active response, the system back end halts the process at 616 without reporting the event to the monitoring station.
  • the system backend at 618 shares the event capture (including the image capture and optionally any video), and raises an alert, based on the user's input, with the remote monitoring service, also providing any relevant context information.
  • the personnel of the remote monitoring service are preferably able to instruct the control unit of the installation to connect the monitoring station to the camera 214', any audio interface, and optionally any other camera of the installation so that the personnel are able to see and hear what is happening at the protected premises, and also to have a dialogue with the cleaner and anyone else at the premises in an attempt either to de-escalate the situation or to get the cleaner to leave the study. Failing which the monitoring service may involve the police or other security personnel.
  • Figures 7 and 8 correspond generally with figures 5 and 6 but in this was with off-site motion detection based on image analysis.
  • a camera such as study camera 214' or back garden camera 212 is arranged to capture 704 images on a continuous or quasi continuous (e.g. a capture every few seconds) basis.
  • the captured images are then passed 706 to an image (e.g. video) analysis system 702 for the detection of movement based on differences between images.
  • the image analysis system 702 may be internal to the camera (214' or 212), internal to the control unit 208, or provided by a hardware arrangement that is remote from the installation - optionally part of the system backend 230 or 240, or provided by some other entity.
  • the image analysis system 702 is located somewhere intermediate the camera and the system backend - for example either provided by the installation controller 208, or provided by an off-premises function somewhere.
  • the image analysis system 702 determines, based on differences between captured images, that there is movement at the premises. If the image analysis system is provided by an entity remote from the premises it will typically be arranged to provide the result of its analysis to the installation control unit 208 or to the relevant requesting node if the installation includes no intermediate control unit. If the image analysis system 702 is provided by the control unit, or if the control unit receives an output from the image analysis system 702 to the effect that movement has been detected, the control unit taking account of any stored rules for event handling, based on arm state of the installation, time of day, day of week etc. and any other status data as necessary, provides details of the detected event - for example including an image capture or video clip, etc.
  • the central unit may use an internal transceiver to transmit the notification to the user device, e.g. over a 4G or 5G PLMN, or it may send the relevant information to the system backend 230/240 for the backend to handle the provision of a notification to the user device.
  • Figure 7 assumes that latter approach but it will be understood that the direct approach may be used in other embodiments of the invention.
  • a message is sent to the system backend 230/240, optionally from a control unit 208 of the installation.
  • the message includes one or more relevant image captures and/or one or more video clips or a link to an image capture or video clip(s).
  • FIG 8 is a flow chart illustrating a method 800 in which the detection of motion based on analysis of repeated images of a scene is a trigger for action.
  • the method may be performed by a security monitoring installation in a domestic setting, such as at a home as illustrated in Figures 1 and 2 , or in a commercial setting such as a retail outlet (e.g. a restaurant or shop) or at some other kind of business, such as at an office.
  • the security monitoring installation may be in an arm state other than fully armed - e.g. disarmed or "armed at home”.
  • the camera may be surveying an out of bounds area, or may be surveying an open access area for detection of a potential threat under certain circumstances (for example in a commercial setting the installation may be used to alert to the arrival of potential customers or potential villains while the commercial enterprise is short-staffed, e.g. before or after the main operating hours).
  • a camera of the installation captures at least two images of a scene at the installation.
  • the camera may only be able to capture still images, or it may be configured to capture video with a frame rate high enough to generate a watchable video sequence.
  • the camera may be any one of the cameras shown in Figures 1 or 2 .
  • the camera may be a stills camera configured to capture still images periodically - for example every 10 to 20 seconds, or a few times each minute.
  • the camera may be a video camera configured to capture video with a frame rate of between several times a second and, for example, 20 to 24 frames per second.
  • images captured by the camera are analysed in an attempt to detect movement of image elements between an earlier image and a later image.
  • the analysis may be based on consecutive image captures or may be based on non-adjacent images from a sequence of image captures.
  • the image analysis may be performed on the camera that captures the images but may alternatively be performed by a processor remote from the camera, the camera images having been transmitted or otherwise sent directly or indirectly to the processor.
  • the camera may be configured to send image captures to a controller of the installation, e.g. controller 208, for processing on the controller or to a controller or other gateway for onward transmission by the controller/gateway (directly or indirectly) to another entity that will perform the image analysis.
  • the image analysis may be performed by a system backend, such as 230 or 240, remote from the installation.
  • the processor performing the image analysis detects movement based on differences between image captures made at different instants in time.
  • the processor may be programmed to react to any detected movement, or it may be programmed to ignore some categories of movement or only to respond to certain categories of movement or to respond only if certain feature types (e.g. humans and/or vehicles) are present.
  • Commercially available image analysis systems based on A.I. e.g. software packages, may be used to perform the image analysis.
  • a report is generated for notification of the detected motion to a user device.
  • the report may be in the form of the notification for the user device, or the report may be provided, directly or indirectly, to another entity (e.g. the installation controller or the system backend) for the preparation and despatch of the notification.
  • the report and notification if different, each both preferably include at least the later of the compared images, and preferably the object of interest whose movement has been detected is marked, annotated, or highlighted in some way so that the basis of the motion detection will be clear from the notification.
  • the notification may include two or more of the images from which motion was determined, or only one image (suitably annotated or marked) may be included. If the image analysis was performed on a video sequence, that video sequence or a relevant clip from that sequence may be included in the notification.
  • the notification is transmitted to the user device, e.g. device 220, at step 808, based on the identity of the installation and e.g. a database linking the installation to a relevant user device identifier.
  • the notification preferably also includes context data (for example arm state, occupancy, camera identity, other node sensing data, etc.) regarding the installation at the time of the relevant image captures.
  • the notification is displayed on a display of the user device in such a way as to provide the user with a clear indication of the basis for movement detection.
  • the notification may include textual information (e.g. labelling) and/or audio description to aid the user's understanding of the nature of the reported event - e.g. "person spotted in the back garden".
  • the notification may also include one or more "action elements” e.g. buttons or icons with which the user may interact to provide a response.
  • the user may provide a reaction - for example, if the notification is a cause for alarm, the user may interact with an actionable element such as a button or icon, or perform a deep touch, to indicate a desire to escalate the event to the remote monitoring centre.
  • the reaction from the user may indicate that no threat is perceived - either based on an action taken by the user ( interacting with a "not a threat” or “all OK" button, for example) or based on the lack of a request (within a predetermined period after notification) to escalate.
  • the user reaction is determined at a processing entity, such as the system backend 230/240 or the installation controller 208, based either on an overt response received from the user device or based on the lack of an overt response.
  • a processing entity such as the system backend 230/240 or the installation controller 208
  • Escalating to the remote monitoring centre includes making the relevant image capture(s) available to the remote monitoring centre and also providing any relevant information from the user's reaction (in particular that the user perceives the existence of a threat).
  • the personnel of the remote monitoring centre review the relevant captures and the contextual information, and if necessary instruct the installation to make available video feeds, provide a bidirectional audio channel, etc., so that the personnel are better able to determine the nature of any incident. If necessary, based on the captures, contextual information, and later gathered information, the personnel may decide to involve security personnel or the police, of others.
  • the processor/system used to determine motion based on image analysis, and/or the processor/system that decides whether or not to notify a user device based on any detected movement may use user feedback (e.g. escalations, "all OK" responses, and passive “responses”) in a machine learning approach to improving system performance.
  • user feedback e.g. escalations, "all OK" responses, and passive “responses

Landscapes

  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Alarm Systems (AREA)
EP23383199.9A 2023-11-22 2023-11-22 Sicherheitsüberwachungssysteme und -verfahren Pending EP4560599A1 (de)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23383199.9A EP4560599A1 (de) 2023-11-22 2023-11-22 Sicherheitsüberwachungssysteme und -verfahren
PCT/EP2024/083036 WO2025109029A1 (en) 2023-11-22 2024-11-20 Security monitoring systems and methods

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP23383199.9A EP4560599A1 (de) 2023-11-22 2023-11-22 Sicherheitsüberwachungssysteme und -verfahren

Publications (1)

Publication Number Publication Date
EP4560599A1 true EP4560599A1 (de) 2025-05-28

Family

ID=89119599

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23383199.9A Pending EP4560599A1 (de) 2023-11-22 2023-11-22 Sicherheitsüberwachungssysteme und -verfahren

Country Status (2)

Country Link
EP (1) EP4560599A1 (de)
WO (1) WO2025109029A1 (de)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022243449A1 (en) * 2021-05-20 2022-11-24 Verisure Sàrl Security monitoring system and method
US20230035710A1 (en) * 2021-08-02 2023-02-02 Ademco Inc. Systems and methods of monitoring alarms from third party devices

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022243449A1 (en) * 2021-05-20 2022-11-24 Verisure Sàrl Security monitoring system and method
US20230035710A1 (en) * 2021-08-02 2023-02-02 Ademco Inc. Systems and methods of monitoring alarms from third party devices

Also Published As

Publication number Publication date
WO2025109029A1 (en) 2025-05-30

Similar Documents

Publication Publication Date Title
US11527149B2 (en) Emergency alert system
US20230351872A1 (en) Video monitoring and alarm verification technology
US10217335B2 (en) Dynamic linking of security systems
US11423764B2 (en) Emergency communications using client devices that are associated with audio/video recording and communication devices
US9819911B2 (en) Home, office security, surveillance system using micro mobile drones and IP cameras
US10854058B2 (en) Emergency alert system
US9679455B2 (en) Security monitoring with programmable mapping
US6163257A (en) Security system having event detectors and keypads with integral monitor
CN116457851B (zh) 用于地产监控的系统和方法
EP2911125A1 (de) Sicherheitsüberwachungsanordnung und -verfahren mithilfe eines gemeinsamen sichtfelds
US20030117280A1 (en) Security communication and remote monitoring/response system
CN106157567A (zh) 共享或连接安全和家庭控制系统的系统和方法
TW200305115A (en) Monitoring system
EP3563359B1 (de) Verfahren und system zur bereitstellung von datenschutzkompatibler überwachung in einem gebäude
US9633533B2 (en) System and method for interacting with digital video recorders through networking applications
JP7792846B2 (ja) 情報処理システム及びプログラム
CN102098419B (zh) 使用安全系统中的疏耦合来过滤安全区域中的视频事件
EP4560599A1 (de) Sicherheitsüberwachungssysteme und -verfahren
EP4560600A1 (de) Sicherheitsüberwachungssysteme und -verfahren
EP2698773A1 (de) Einbruchmeldeanlage und Verfahren zur Scharfschaltung einer Einbruchmeldeanlage
JP2005182471A (ja) 監視装置の中央処理装置およびそのプログラム
EP4150597A1 (de) Sicherheitsüberwachungssystem und -verfahren
EP3598404B1 (de) Verfahren zum betrieb eines alarmsystems für ein gebäude, alarmsystem für ein gebäude und alarmanlage
US20240265700A1 (en) Security system having video analytics components to implement detection areas
JP2001236580A (ja) 施設内監視システム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR