Event entity monitoring network and method
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
exact text as granted — not AI-modified1 . 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.
2 . 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.
3 . A method as claimed in claim 2 , wherein the event entity is identified based upon the metadata.
4 . A method as claimed in claim 1 , including performing vector form extraction on the event data to provide the first level of detail.
5 . A method as claimed in claim 4 , wherein the first level of detail is a vector image representative of the event data.
6 . 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.
7 . 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.
8 . 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.
9 . A method as claimed in claim 1 , including assessing event data with location data, historical data and/or environmental conditions data.
10 . 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.
11 . A method as claimed in claim 1 , wherein outputting a notification includes implementing a predetermined course of action.
12 . A method as claimed in claim 11 , wherein the predetermined course of action is an alert, alarm, security response or tracking the event entity.
13 . 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.
14 . 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.
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.
16 . A monitoring data processing device as claimed in claim 15 , wherein the first level of detail is metadata describing properties of the event entity.
17 . A monitoring data processing device as claimed in claim 16 , wherein the event entity is identified based upon the metadata.
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.
19 . 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.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.