# US 2021/0343136 A1 · Event entity monitoring network and method > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0343136 A1 - Document ID: US20210343136A1 - Status: Published application - Kind: A1 - Application number: 17/376,427 - Filed: 2021-07-15 - Published: 2021-11-04 - Earliest claimed: 2018-07-04 - Assignees: Seechange Technologies Limited - Applicants: Seechange Technologies Limited - Inventors: Jason SOULOGLOU - Web page: https://patentgrep.com/patent/US20210343136A1 ## CPC - G08B 21/18: Status alarms (G08B21/02 takes precedence) - G06F 16/56: having vectorial format - G06F 16/58: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually - G06V 20/41: {Higher-level, semantic clustering, classification or understanding of video scenes, e.g. detection, labelling or Markovian modelling of sport events or news items (segmenting video sequences G06V20/49)} - G06V 20/52: Surveillance or monitoring of activities, e.g. for recognising suspicious objects (recognising microscopic objects G06V20/69) - G08B 19/00: Alarms responsive to two or more different undesired or abnormal conditions, e.g. burglary and fire, abnormal temperature and abnormal rate of flow - H04W 4/38: for collecting sensor information - G06V 20/44: {Event detection} - G08B 13/19613: {Recognition of a predetermined image pattern or behaviour pattern indicating theft or intrusion} - G08B 31/00: Predictive alarm systems characterised by extrapolation or other computation using updated historic data - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06V: IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method of monitoring for the presence of an event entity in a monitored region comprising receiving, at a first level of detail, first event data from at least one data processing device configured to monitor at least a portion of a monitored region, the first event data indicative of an event entity occurring in the monitored region and being an anonymized compression of raw information data collected by said at least one data processing device; processing the first event data to determine the presence of an event entity indicated by the event data; requesting, at a second level of detail, second event data, wherein the second level of detail is more detailed than the first level of detail; and receiving a notification comprising the second event data having the second level of detail. The second level of detail is requested in response to the event entity matching a notification event, and a recognition server has authorization to access the second event data having the second level of detail. Alternatively, the second level of detail is requested in response to the event entity matching a notification event, and a recognition server has a policy to access the second event data having the second level of detail. ## Claims ### Claim 1 A method of monitoring for the presence of an event entity in a monitored region comprising: receiving, at a first level of detail, first event data from at least one data processing device configured to monitor at least a portion of a monitored region, the first event data indicative of an event entity occurring in the monitored region and being an anonymized compression of raw information data collected by said at least one data processing device; processing the first event data to determine the presence of an event entity indicated by the event data; requesting, at a second level of detail, second event data, wherein the second level of detail is more detailed than the first level of detail; and receiving a notification comprising the second event data having the second level of detail, wherein the second level of detail is requested in response to the event entity matching a notification event, and wherein a recognition server has authorisation to access the second event data having the second level of detail; or wherein the second level of detail is requested in response to the event entity matching a notification event, and wherein a recognition server has a policy to access the second event data having the second level of detail. ### Claim 2 (depends on 1) A method as claimed in claim 1, wherein the first level of detail of first event data comprises metadata describing properties of the event entity. ### Claim 3 (depends on 2) A method as claimed in claim 2, wherein the event entity is identified based upon the metadata. ### Claim 4 (depends on 1) A method as claimed in claim 1, including performing vector form extraction on the event data to provide the first level of detail. ### Claim 5 (depends on 4) A method as claimed in claim 4, wherein the first level of detail is a vector image representative of the event data. ### Claim 6 (depends on 1) A method as claimed in claim 1, including communicating the event data to a recognition server and wherein the recognition server comprises a scenario identifier in communication with a decision module for determining a course of action associated with the notification. ### Claim 7 (depends on 6) A method as claimed in claim 6, wherein the recognition server comprises a scenario identifier in communication with a vector event data store, a vector scenario data store and a vector environment data store for comparing the vector image with one or more of the data stores. ### Claim 8 (depends on 6) A method as claimed in claim 6, including a predictive event generator module for analysing the scenario identifier and making a prediction on a likely outcome of a future event. ### Claim 9 (depends on 1) A method as claimed in claim 1, including assessing event data with location data, historical data and/or environmental conditions data. ### Claim 10 (depends on 1) A method as claimed in claim 1, including obtaining event data from a plurality of sensors, at least one sensor being one of embedded IoT devices, image sensors, sound sensors, brightness sensors, odour sensors, temperature sensors, humidity sensors and proximity sensors, fitness trackers, PIR motion detectors and mobile phones. ### Claim 11 (depends on 1) A method as claimed in claim 1, wherein outputting a notification includes implementing a predetermined course of action. ### Claim 12 (depends on 11) A method as claimed in claim 11, wherein the predetermined course of action is an alert, alarm, security response or tracking the event entity. ### Claim 13 (depends on 1) A method as claimed in claim 1, the policy including one or more of: recording images and/or sound, recording at different levels of detail or abstraction than the first level of detail, outputting a notification. ### Claim 14 (depends on 1) A method as claimed in claim 1, including automatically implementing the policy based upon predetermined criteria and, optionally, dynamically setting the policy to increase or decrease a level of abstraction. ### Claim 15 A monitoring data processing device to monitor an event entity comprising: a data processor for generating first event data at a first level of detail used to identify the event entity, the first event data being an anonymized compression of raw information data collected by a sensor; wherein the monitoring data processing device is operable to receive a request to monitor an event entity at a second level of detail to generate second event data, wherein the second level of detail is more detailed than the first level of detail; and wherein the monitoring data processing device is operable to output the second event data comprising a notification to a data processing device being authorised to access the second event data having the second level of detail; or wherein the monitoring data processing device is operable to output the second event data comprising a notification to a data processing device having a policy to access the second event data having the second level of detail. ### Claim 16 (depends on 15) A monitoring data processing device as claimed in claim 15, wherein the first level of detail is metadata describing properties of the event entity. ### Claim 17 (depends on 16) A monitoring data processing device as claimed in claim 16, wherein the event entity is identified based upon the metadata. ### Claim 18 A recognition server to monitor an event entity comprising: input circuitry for receiving, at a first level of detail, first event data from at least one processing device in a monitored region, the first event data being an anonymized compression of raw information data collected by the least one data processing device; a processor for processing the first event data to identify the event entity inferred by the event data; responsive to the event entity matching a notification event, following a request, the input circuitry to receive, at a second level of detail, second event data from the at least one data processing device, wherein the second level of detail is more detailed than the first level of detail, and the recognition server to output a notification comprising the second event data having the second level of detail; and wherein outputting a notification comprising the event data having the second level of detail comprises a notification to a data processing device having authorisation to access the event data having the second level of detail; or wherein outputting a notification comprising the event data having the second level of detail comprises a notification to a data processing device having a policy to access the event data having the second level of detail. ### Claim 19 (depends on 18) A recognition server as claimed in claim 18, wherein the first level of detail of first event data is metadata describing properties of the event entity.