WO2018068137A1 - Système et procédé de détection automatisée d'événement anormal et de libération sélective de données sur la base de ladite détection - Google Patents
Système et procédé de détection automatisée d'événement anormal et de libération sélective de données sur la base de ladite détection Download PDFInfo
- Publication number
- WO2018068137A1 WO2018068137A1 PCT/CA2017/051208 CA2017051208W WO2018068137A1 WO 2018068137 A1 WO2018068137 A1 WO 2018068137A1 CA 2017051208 W CA2017051208 W CA 2017051208W WO 2018068137 A1 WO2018068137 A1 WO 2018068137A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- data
- abnormal event
- occurrence
- user action
- 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.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2218/00—Aspects of pattern recognition specially adapted for signal processing
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- the present invention relates to the field of automatized event detection, data storage and selective data release. More particularly, it relates to a system for automatically detecting the occurrence of an abnormal event and, based on said detection, providing selective data release of stored personal user data to data recipient(s). It also relates to a method for performing the same.
- United States patent application no. 2015/0188993 describes a system and a method for storing and distributing data, upon the occurrence of an event.
- this document discloses that the initial user identifies one or more persons responsible for notifying the system of the occurrence of the event, when the event occurs.
- the system described in this document relies on the identified users to notify the system of the occurrence of the event, to subsequently initiate the process of distributing the data stored by the user of the system to the previously identified data recipient(s).
- a system for detecting an occurrence of an abnormal event and performing selective data release based on said detection comprises at least one electronic device used by a user to perform at least one predetermined digital user action representative of usage patterns of the at least one electronic device by the user.
- the performance of each one of the at least one predetermined digital user action generates user action data indicative of the performance of the corresponding digital user action by the user.
- the system also comprises a main system module.
- the main system module includes a storage medium configured to store personal user data relative to the user and digital user action preferences relative to the at least one predetermined digital user action.
- the digital user action preferences include identification of each one of the at least one predetermined digital user action and a maximal time delay for performing each repeated occurrence of the at least one predetermined digital user action.
- the main system module also includes an abnormal event detection module receiving the user action data and determining the occurrence of an abnormal event, based on the user action data and the digital user action preferences and a personal user data distribution module releasing the stored personal user data to at least one data recipient upon determination of the occurrence of the abnormal event by the abnormal event detection module.
- the personal user data distribution module is configured to upload the stored personal user data to an electronic device of the at least one data recipient upon determination of the occurrence of the abnormal event by the abnormal event detection module.
- the main system module further comprises an abnormal event validation module in data communication with the at least one electronic device used by the user.
- the abnormal event validation module is configured to transmit an electronic confirmation request to the at least one electronic device used by the user and receive user validation data therefrom for validating the occurrence of the abnormal event.
- the personal user data distribution module releases the stored personal user data to the at least one data recipient upon determination of the occurrence of the abnormal event by the abnormal event detection module and the validation of the occurrence of the abnormal event by the abnormal event validation module.
- the abnormal event validation module is in data communication with at least one electronic device used by at least one event validator.
- the abnormal event validation module is configured to transmit an electronic confirmation request to the at least one electronic device used by the at least one event validator and receive user validation data therefrom for validating the occurrence of the abnormal event.
- the personal user data distribution module releases the stored personal user data to the at least one data recipient upon determination of the occurrence of the abnormal event by the abnormal event detection module and the validation of the occurrence of the abnormal event by the abnormal event validation module.
- the at least one event validator includes the at least one data recipient.
- the main system module is installed on a main computing unit remote from the at least one electronic device used by the user to perform the at least one predetermined digital user action and is in data communication therewith over a network.
- the main computing unit and the at least one electronic device used by the user to perform the at least one predetermined digital user action are in data communication with at least one intermediate computing unit hosting a digital service related to one of the at least one predetermined digital user action.
- a computer implemented method for detecting the occurrence of an abnormal event for a user and the selective data release of personal user data of the user based on said detection comprises: storing the personal user data of the user on a storage medium; receiving and storing at least one digital user action performed by the user using an electronic device and representative of usage patterns of the electronic device by the user; defining a maximal time delay for each repeated occurrence of the at least one digital user action, non-performance of each one of the at least one digital user action within the associated maximal time delay being indicative of the occurrence of the abnormal event; generating digital user action data representative of the performance of the at least one digital user action by the user upon performance of the at least one digital user action; repeatedly processing the digital user action data to determine the occurrence of each one of the at least one digital user action within the maximal time delay associated therewith; identifying each one of the at least one digital user action as being in a failed state if no occurrence of the digital user action occurred within the maximal time delay associated
- the computer implemented method further comprises validating the occurrence of the abnormal event with the user, the step of releasing the stored personal user data to at least one data recipient being performed upon validation of the occurrence of the abnormal event with the user.
- validating the occurrence of the abnormal event with the user comprises sending an electronic confirmation request to the user and receiving user validation data therefrom.
- the computer implemented method further comprises additionally validating the occurrence of the abnormal event with at least one event validator, the step of releasing the stored personal user data to at least one data recipient being performed upon the additional validation of the occurrence of the abnormal event with the at least one event validator.
- validating the occurrence of the abnormal event with the at least one event validator comprises sending an electronic confirmation request to the at least one event validator and receiving user validation data therefrom.
- releasing the stored personal user data to at least one data recipient comprises uploading the personal user data to an electronic device of the user.
- a computer readable memory having recorded thereon statements and instructions for execution by a computer, with the statements and instructions comprising code for performing the steps of the computer implemented method for detecting the occurrence of an abnormal event for a user and the selective data release of personal user data of the user based on said detection.
- a computer program product comprising a computer readable memory storing computer executable instructions thereon that when executed by a computer perform the steps of the computer implemented method for detecting the occurrence of an abnormal event for a user and the selective data release of personal user data of the user based on said detection.
- Figure 1 is a graphical representation of a system for performing detection of an abnormal event and selective data release based on the detection.
- Figure 2 is a flow chart showing the general phases of a method for performing the detection of an abnormal event and the selective data release based on the detection, in accordance with an embodiment.
- Figure 3 is a flow chart showing the steps of a registering phase of the method of Figure 2, in accordance with an embodiment.
- Figure 4 is a flow chart showing the steps of an abnormal event occurrence validation phase of the method of Figure 2, in accordance with an embodiment.
- Figure 5 is a flow chart showing the phases of an abnormal event occurrence validation phase of the method of Figure 2, in accordance with an embodiment.
- Figure 5A is a flow chart showing the steps of a primary validation phase of the abnormal event occurrence validation phase of Figure 5, in accordance with an embodiment.
- Figure 5B is a flow chart showing the steps of a secondary validation phase of the abnormal event occurrence validation phase of Figure 5, in accordance with an embodiment.
- Figure 6 is a flow chart showing the steps of a data release phase of the method of Figure 2, in accordance with an embodiment.
- the system and method are designed to allow a user to store personal data to be automatically distributed to at least one data recipient upon the occurrence of an abnormal event, such as, for example and without being limitative, the death or the incapacitation of the user.
- the system and method are designed and configured to perform automated detection of the occurrence of the event, for example based on a lack of performance of user selected digital action(s), within a predetermined maximal time delay, as will be described in more details below.
- the automated detection of the occurrence of the event is performed though data communication with an electronic device associated to the user and used to perform the user selected digital action(s), to allow early detection of the occurrence of the abnormal event and a timely release of the personal user data to the data recipient(s) by the system.
- the term "user” is used to define an individual using the system or method for temporarily storing personal user data that is to be transmitted to data recipient(s) upon the detection of the occurrence of the abnormal event to the user.
- the term "personal user data" is used to define any user related information in electronic data form, which is to be temporarily stored, for subsequent release to the data recipient(s) (e.g. through grant of selective data access, data upload, data download, etc.) upon the detection of the occurrence of the abnormal event.
- the personal user data can include any information in electronic data form regarding insurance, financial, banking and savings information, such as identification of insurance contracts, bank accounts, trust accounts, investment accounts and/or interest of the user in real and/or personal property.
- the personal user data can also include identification and access codes for online resources, such as websites, web services, computer applications, social media sites, or the like.
- the personal user data can also include testamentary information, such as the identification of wills, trusts and other estate wishes and/or other related information or wishes or any personal messages to be passed-on following the death or incapacitation of the user.
- testamentary information such as the identification of wills, trusts and other estate wishes and/or other related information or wishes or any personal messages to be passed-on following the death or incapacitation of the user.
- data recipient(s) is used to define any individual identified by the user as a receiver (or beneficiary) of the personal user data in the case of the occurrence of the abnormal event.
- the term "electronic device” is used to define any device for storing and processing data, typically in binary form, according to instructions.
- the expression “electronic device” can include, but is not limited to, wireless communication devices, such as smartphones, electronic tablets, personal digital assistants, laptop computers and the like, and to other personal computer types such as desktop computers or the like and any variant or combinations thereof.
- the electronic device can include a display device, input device(s), a memory, at least one processor, and any other component required for proper functioning. As will be described in more details below, the electronic device can be used by the user to perform the digital user action(s).
- memory can include generally any tangible computer- readable medium including, for example, persistent memory such as magnetic and/or optical disks, ROM, and PROM and volatile memory such as RAM.
- storage medium is used to refer to any technology (including devices and components) used to receive, store, and retrieve data in digital form. It can refer to both primary storage (i.e. memory) and secondary storage such as hard disk drives (HDDs), solid-state drive (SSD) or the like and/or associated structures for accessing, managing and updating the data, such as databases.
- HDDs hard disk drives
- SSD solid-state drive
- digital user action is used to define actions performed by the user using an electronic device and which reflects usage patterns of the electronic device by the user (i.e. usage of the application available through the electronic device such as native application of the device, web application or other electronic applications that can be performed using the electronic device).
- digital user actions can include actions performed on social media (such as, without being limitative, a login into a social media site, a posting into a social media site, or a reaction on a social medial site (e.g. a "like", a "comment” or a “share” of a post on a social media site, etc.)), or other actions regarding communication medium, such as sending, forwarding, or responding to an email.
- the digital user actions can also include digital user actions relative to the native functions of an electronic device, such as, without being limitative, in an embodiment where the electronic device is a smartphone, making a phone call, sending a text message, stopping an alarm triggered by the smartphone, or the like.
- digital user actions are listed hereinabove and numerous other digital user actions which can be performed by the specific user, using an electronic device, could be included in the user action preferences selectable by the user as actions being considered as a sign of the non-occurrence of the abnormal event by the system.
- a system 10 for temporarily storing personal user data and for performing the detection of an abnormal event and the selective data release of the personal user data to data recipient(s), upon the detection of the occurrence of the abnormal event.
- the abnormal event can be, for example and without being limitative, the death of the user, or other events resulting in the incapacitation of the user, upon which the user wishes to automatically transmit the previously identified user data to one or more person(s) of its choice (i.e. the data recipient(s)).
- the system 10 includes a main system module 20.
- the main system module 20 is the module of the system 10 which substantially allows the required functionalities of the system 10 for receiving the personal user data, storing the personal user data, detecting the occurrence of the abnormal event and performing the selective data release of the personal user data to be implemented.
- the main system module 20 is at least partially installed on a main computing unit 30 having its own memory and processor and in data communication with at least one electronic device 50 used by a user, over a network 32.
- the network 32 can be any network allowing data communication between the main computing unit 30 and the at least one electronic device 50 (and any other intermediate computing unit 60 as will be described in more details below), such as, without being limitative, a local area network (LAN) or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- computing unit is used to define any type of computer to be used in an network and to host a digital service, such as, for example and without being limitative, an application server, a web server, a mail server, a text message (or SMS) server, an instant messaging server or the like.
- a computing unit can be either a single physical device or a plurality of physical devices operatively connected to (or in data communication with) one another, for example over a network (i.e. a plurality of devices distributed over a network).
- the main computing unit 30 can be a server (or group of servers in data communication with one another), such as an application server, a web server, or the like to be used in a "client-server" architecture, or any other computer or computer type that can be connected to a network.
- the main system module 20 can also be distributed between the main computing unit 30 and the at least one electronic device 50 used by the user, with portions of the main system module 20 being on each one of the main computing unit 30 and the at least one electronic device 50.
- the system 10 includes a user module 40.
- the user module 40 is in data communication with the main system module 20 and is configured to acquire, process and/or transmit the required user input(s) for proper functioning of the system 10, as will be described in more details below.
- the user module 40 is a module of the system 10 including instructions at least temporarily stored in a memory 51 of an electronic device 50 used by the user, to acquire, process and/or transmit the required user input(s).
- the user module 40 includes a user interface 42 which can be displayed on a display screen of the electronic device 50 of the user.
- the electronic device 50 is connected to a network, in order to access and download the data and instructions for the display and functioning of the user interface 42 of the user module 40, from a remote data source (such as a web server), with the data and instructions for the display and functioning of the user interface 42 of the user module 40 being temporarily downloaded by the electronic device 50 and stored in a memory 51 thereof.
- a remote data source such as a web server
- the electronic device 50 is in data communication with the main computing unit 30 onto which the main system module 20 is installed, such that data acquired through the user interface 42 can be transmitted to the main system module 20.
- the user interface 42 allows data communication between the electronic device 50 of the user and the main system module 20, for the user to input initial user data, data recipient data, event validator data and/or user action preferences (or selections), which is subsequently transmitted to the main system module 20 and stored on an associated storage medium.
- the user interface 42 also allows selection and upload of personal user data, by the user, using the electronic device 50, with the personal user data also being transmitted to the main system module 20 and stored on an associated storage medium.
- the initial user data includes the data required to initially identify the user (which can for example be collected during a registering step identified in the user interface) such as, without being limitative, the name, surname, contact information (e.g. email address, phone number and address of the user), or any other personal information which can be used to identify or contact the user.
- the initial user data can also include a username and a password which can be subsequently used to log into the system 10, through the user interface 42. More particularly, the username and password can allow connection to an associated account of the user in the system 10.
- the event validator data includes the data relative to the at least one individual which the user identifies to validate the occurrence of the abnormal event.
- the event validator data can include, for example and without being limitative, the name, surname, and contact information of the at least one event validator (e.g. email address, phone number and address, etc.).
- the data recipient data includes the data relative to the at least one individual to which the user wishes that the personal user data be transmitted upon the occurrence of the abnormal event.
- the data recipient data can include, for example and without being limitative, the name, surname, and contact information of the at least one data recipient (e.g. email address, phone number and address, etc.).
- the digital user action preferences include at least one digital user action, which the user is expected to perform repeatedly, using the electronic device 50, while the abnormal event has not occurred.
- at least one digital user action can be selected initially by the user, using the user interface 42 (for example, during the registering step), preferably favoring digital user action(s) which the user knows is/are performed frequently and recurrently.
- the user can also update its digital user action preferences subsequently (e.g. add new digital user action, modify or delete existing digital user action, etc.), using the user interface 42, to reflect its current user habits, at any point in time.
- the digital user action preferences also include, for each one of the selected digital user actions, a maximal time delay (or timeframe) for the performance of the digital user action.
- the digital user action preferences include a threshold value within which each one of the digital user actions is expected to be performed by the user, using an electronic device 50, while the abnormal event has not yet occurred.
- the maximal time delay is normally specific to each one of the digital user action, and should reflect a maximal frequency within which the user normally performs each specific digital user action, using an electronic device 50.
- non-performance of each one of the at least one digital user action, within the associated maximal time delay should be indicative of the occurrence of the abnormal event (i.e.
- the user interface 42 could also allow specific configurations (such as hold configurations) to be activated by the user and taken into account by the system 10, for non-conventional activity periods (such as, for example and without being limitative, during holidays of the user), where the user routine is modified and the specific maximal time delay may not be representative.
- specific configurations such as hold configurations
- the acquisition of the personal user data by the system 10 is performed through the upload of the desired personal user data from the electronic device 50 used by the user, to the main system module 20.
- Such upload of the desired personal user data can be performed by selecting the desired electronic data (i.e. the user information in digital form (e.g. text files, images, videos, etc. , containing the personal user data)) using the user interface 42 displayed on the electronic device 50 and subsequently uploading the data to the main system module 20 (i.e. transferring the data from the electronic device to the main computing unit 30 onto which the main module is installed over the network).
- the personal user data is securely stored by the main system module 20 onto an associated storage medium.
- the system 10 also includes the required security infrastructure, means and measures to prevent unlawful access, leaks, hacking, or other potential malicious actions which could lead to unwarranted theft of the initial user data, data recipient data, event validator data, digital user action preferences and personal user data.
- the main system module 20 also includes an abnormal event detection module 22 configured to repeatedly verify the occurrence of the at least one digital user action included in the digital user action preferences, within the associated specific maximal time delay, in order to determine whether the abnormal event has occurred.
- the abnormal event detection module 22 includes instructions to repeatedly verify that the user has used an electronic device 50 in data communication with the abnormal event detection module 22, to perform at least one of the digital user action(s) included in the digital user action preferences, within the associated maximum time delay. This recurrent verification is performed to confirm that the user is still active (as indicated by its normal use of the electronic device 50 to perform the at least one user action) and that, therefore, the abnormal event has not yet occurred.
- the abnormal event detection module 22 is therefore configured to communicate (i.e. is in data communication) with the at least one of the electronic device 50 used for performing the digital user action, in order to repeatedly verify the occurrence of the digital user action(s) included in the digital user action preferences.
- reference to the abnormal event detection module 22 being in data communication with the electronic device 50 can refer to the abnormal event detection module 22 being in direct data communication with the electronic device 50, or to the abnormal event detection module 22 being in data communication with an intermediate computing unit 60 in data communication with the electronic device 50 and associated to a digital service related to one of the selected digital user action (such as, for example, a web server associated to a user selected social media, a mail server, a text message (or SMS) server, an instant messaging server, or any other types of computers that can be used for hosting a digital service related to a selected digital action and onto which data regarding the occurrence of the digital user action(s) performed using the electronic device 50 of the user can be generated and/or stored in a memory).
- a single intermediate computing unit 60 is shown in Figure 1 , in an embodiment, more than one an intermediate computing unit 60 can be part of the system 10.
- the abnormal event detection module 22 is configured to receive and store digital user action data from the electronic device 50 (or from the intermediate computing unit 60 through which the abnormal event detection module 22 is operatively connected (i.e. in data communication) with the electronic device 50), upon performance of a digital user action by the user, to determine whether the abnormal event has occurred.
- digital user action data representative of the performance of the specific user action can be transmitted (pushed) to the abnormal event detection module 22, by a corresponding mail server (i.e. the intermediate computing unit 60 being a mail server) hosting the email service used by the user for sending, responding and/or transferring an email.
- a corresponding mail server i.e. the intermediate computing unit 60 being a mail server
- the user connects to a mail server (not shown) using the electronic device 50 (the electronic device 50 and mail server being in data communication) and the mail server transmits (push) the digital user action data representative of the performance of the specific user action to the abnormal event detection module 22 upon performance of the action (the mail server and the abnormal event detection module 22 being in data communication).
- the digital user action data representative of the performance of the specific user action can be transmitted to the abnormal event detection module 22, by a corresponding web server (i.e.
- the intermediate computing unit 60 being a web server) hosting the social media site and in data communication with the abnormal event detection module 22, the web server being accessed by the user with the electronic device 50 in communication therewith.
- the digital user action data representative of the performance of the specific user action can be transmitted (pushed) to the abnormal event detection module 22, by the electronic device 50 used for performing the digital user action upon performance of the digital user action by the user, using the electronic device 50.
- the digital user action data can also be stored on the electronic device 50 used for performing the digital user action and/or onto the intermediate computing unit 60 associated to the specific digital user action and in data communication with both the electronic device 50 and the abnormal event detection module 22 thereby allowing the abnormal event detection module 22 to access (or pull) the digital user action data when required, in order to verify the performance of the digital user action within the prescribed maximal time delay.
- the main system module 20 further includes an abnormal event validation module 24 configured to validate the occurrence of the abnormal event with the user and/or event validator(s) (i.e. one or more individuals previously identified as responsible to validate the occurrence of the event), upon determination of the occurrence of the abnormal event by the abnormal event detection module 22.
- an abnormal event validation module 24 configured to validate the occurrence of the abnormal event with the user and/or event validator(s) (i.e. one or more individuals previously identified as responsible to validate the occurrence of the event), upon determination of the occurrence of the abnormal event by the abnormal event detection module 22.
- the abnormal event validation module 24 is therefore configured to communicate (i.e. is in data communication) with the user and/or event validator(s), through the associated electronic devices 50 thereof, to confirm the occurrence of the abnormal event, following the determination of the occurrence of the abnormal event by the abnormal event detection module 22.
- the abnormal event validation module 24 uses the previously acquired contact information of the initial user data and/or event validator data, such as email address, phone number, or the like, to contact the user and/or the event validator(s), for example using an electronic confirmation request, such as, without being limitative an email, a text message, instant messaging, or the like.
- the choice of confirmation request type can be predetermined by the user.
- the abnormal event validation module 24 is configured to receive confirmation data from an electronic device 50 of the user or event validator(s), to confirm the occurrence or non/occurrence of the abnormal event, or to interpret the absence of confirmation data as a confirmation of the occurrence of the abnormal event.
- the abnormal event validation module 24 is configured to initially transmit the electronic confirmation request to the user following the determination of the occurrence of the abnormal event by the abnormal event detection module 22, to validate the occurrence/non-occurrence of the abnormal event with the user.
- the abnormal event validation module 24 Upon receipt of the electronic confirmation request, if the abnormal event has not indeed happened and the user is still active, the user can respond to the electronic confirmation request, using the electronic device 50, to deny the occurrence of the abnormal event.
- the abnormal event validation module 24 is in data communication with the electronic device 50 directly or indirectly.
- abnormal event validation module 24 being in data communication with the electronic device 50 can again refer to the abnormal event validation module 24 being in direct data communication with the electronic device 50, or to the abnormal event validation module 24 being in data communication with an intermediate computing unit 60 in data communication with the electronic device 50 and associated to a service used for the electronic confirmation request (such as, for example, a mail server, a text message (or SMS) server, an instant messaging server, etc. in data communication with the electronic device 50).
- a service used for the electronic confirmation request such as, for example, a mail server, a text message (or SMS) server, an instant messaging server, etc. in data communication with the electronic device 50.
- the abnormal event validation module 24 can send the email to a mail server (i.e. the intermediate computing unit 60 being a mail server) in communication therewith.
- the user can use the electronic device 50 in data communication with the mail server to retrieve the data of the email and respond to the email.
- the mail server can subsequently send user validation data representative of a response of the user to the abnormal event validation module 24.
- the user is expected to provide the user validation data within a predetermined validation delay. Once the validation delay has elapsed, the abnormal event validation module 24 is configured to interpret the lack of receipt of the user validation data as an indication of the occurrence of the abnormal event.
- the abnormal event validation module 24 is further configured to transmit an electronic confirmation request to the event validator(s) of the user if no user validation data indicative of the user still being active is received within the predetermined confirmation delay. This is meant to further validate the occurrence/non-occurrence of the abnormal event with the event validator(s), when no response is received to the electronic confirmation request sent to the user.
- the event validator(s) can confirm or deny the occurrence of the abnormal event by transmitting recipient validation data to the event validation module 24, through a response to the electronic confirmation request, using the electronic device 50.
- the abnormal event validation module 24 can be in data communication with the electronic device 50 of the event validator(s) directly or through an intermediate computing unit 60 in data communication with both the abnormal event validation module 24 and the electronic device 50 of the data recipient(s).
- the abnormal event validation module 24 can send the email to a mail server in communication therewith.
- the event validator(s) can use the electronic device 50 in data communication with the mail server to retrieve the data relative to the email and respond to the email.
- the mail server can subsequently send to the abnormal event validation module 24, recipient validation data representative of a response by the user either to confirm or infirm the occurrence of the abnormal event.
- the abnormal event detection module 22 can resume the detection of the occurrence of the digital user action(s) included in the digital user action preferences, to detect new possible occurrences of the abnormal event.
- the event validator identified by the user and stored in the main system module 20 to perform the additional validation can be the same individuals as the data recipient(s).
- the abnormal event validation module 24 can be used by the abnormal event validation module 24 as event validator.
- the main system module 20 further includes a personal user data distribution module 26 configured to perform the distribution of the stored personal user data to the data recipient(s), once the occurrence of the abnormal event is determined by the abnormal event detection module 22 and, in an embodiment, validated by the abnormal event validation module 24.
- a personal user data distribution module 26 configured to perform the distribution of the stored personal user data to the data recipient(s), once the occurrence of the abnormal event is determined by the abnormal event detection module 22 and, in an embodiment, validated by the abnormal event validation module 24.
- the personal user data distribution module 26 is in data communication with the electronic device 50 of the data recipient(s). In an embodiment, the personal user data distribution module 26 transmits access credentials to the data recipient(s), thereby allowing the data recipient(s) to access the personal user data stored by the main system module 20, using their electronic devices 50. In an alternative embodiment, the personal user data distribution module 26 can upload the personal user data temporarily stored by the main system module 20 to the electronic device 50 of the data recipient(s), in order to perform the selective distribution of the personal user data, at the appropriate time.
- the personal user data distribution module 26 transmits an electronic data access request to the data recipient(s).
- the electronic data access request can be an email, a text message, an instant message, or the like.
- the electronic data access request can include user credentials and instructions in order to log into the user account (for example in a read-only mode) and access the personal user data or to upload the personal user data temporarily stored by the main system module 20.
- the personal user data distribution module 26 can send the email to a mail server in communication therewith.
- the data recipient(s) can use the electronic device 50 in data communication with the mail server to retrieve the data of the email.
- the data recipient(s) can use the electronic device 50, to access the personal user data stored by the main system module 20 (for example through data communication with a web server or any other computer hosting a website or an application, using a read-only mode), initiate the upload of the personal user data temporarily stored by the main system module 20 to its electronic device 50, or perform any other process for transferring the personal user data stored by the main system module 20 to the electronic device 50 of the user.
- the main system module 20 for example through data communication with a web server or any other computer hosting a website or an application, using a read-only mode
- initiate the upload of the personal user data temporarily stored by the main system module 20 to its electronic device 50 or perform any other process for transferring the personal user data stored by the main system module 20 to the electronic device 50 of the user.
- the method for performing the detection of an abnormal event and the selective data release of personal user data based on the detection includes a registering phase 1 10, a digital user action occurrence monitoring phase 120; an abnormal event occurrence validation phase 140; and a data release phase 160.
- the registering phase 1 10 includes the step of acquiring and storing the initial user data (step 1 12), acquiring and storing the data recipient data (step 1 14), acquiring and storing digital user action preferences, and acquiring and storing the personal user data (step 1 16).
- the steps of the registering phase 1 10 are performed by a user, using a user interface 42 of the user module 40 displayed on a display screen of the electronic device 50 and connected to (or in data communication with) the main system module 20 over a network 32.
- the user can attend to his normal life activities, which includes performing the digital user action(s) included in the digital user action preferences and performed using the electronic device 50.
- the digital user action is registered as being performed through storage of digital user action data indicative of the performance of the action, on the electronic device 50 used by the user for performing the digital user action and/or on an intermediate computing unit 60 associated to the digital user action, as described above.
- the performance of the digital user action can also be registered through transmission of the digital user action data indicative of the performance of the digital user action to the main computing unit 30 onto which the main system module 20 is installed and/or storage of the digital user action data thereon (or on a storage medium in data communication therewith).
- the digital user action occurrence monitoring phase 120 includes steps for repeatedly verifying registered digital user actions, i.e. repeatedly acquiring and/or processing digital user action data representative of the performance of the digital user action(s) included in the digital user action preferences (for example the digital user action data stored on the main computing unit 30 onto which the main system module 20 is installed) and determining the occurrence of the abnormal event based on the processing of the digital user action data.
- the action occurrence monitoring phase 120 includes an initial step of verifying whether an occurrence of the digital user action has been registered (step 122), for each one of the digital user action included in the digital user action preferences.
- the occurrence verification step (step 122) is performed at a predetermined interval (which can be similar or different for each one of the digital user action included in the digital user action preferences).
- a digital user action can be registered upon performance of the digital user action by the user by storing or transferring digital user action data indicative of the performance of the digital user action
- the verification of whether an occurrence of the digital user action has been registered can be performed by retrieving, or receiving digital user action data from the electronic device 50 or the intermediate computing unit 60 associated to the digital user action, or by accessing the stored digital user action data.
- the action occurrence monitoring phase 120 further includes the step of determining whether the maximal time delay for performing the associated digital user action has elapsed (step 124). If the maximal time delay for performing the associated digital user action has elapsed, the action is considered as being in a failed state (i.e. not having been performed within the specified maximal time delay). If the maximal time delay for performing the associated digital user action has not elapsed, a new iteration of the occurrence verification step (step 122) is performed after the predetermined time interval has passed.
- time delay verification step is performed if the occurrence verification step (step 122) is performed repeatedly, at a frequency that is not substantially corresponding to the maximal time delay of the corresponding digital user action.
- the time delay verification step can be omitted.
- the occurrence verification step (step 122) and time delay verification step (step 124) can be combined in a single step, where a timer corresponding to the time delay is reinitiated every time an occurrence of the digital user action is registered (i.e. every time digital user action data indicative of the performance of the digital user action is acquired by (or transmitted to) the main system module 20 by the electronic device 50 of the user or the intermediate computing unit 60 associated to the user action, with the associated digital user action being considered in a failed state only once the timer runs out.
- the action occurrence monitoring phase 120 further includes a step of determining whether all the digital user actions included in the user action preferences are in the failed state (step 126). If all the digital user actions included in the user action preferences are in the failed state, the abnormal event is determined to have occurred and the abnormal event occurrence validation phase 140 can be performed. If not all the digital user actions included in the digital user action preferences are in the failed state, the occurrence verification step (step 122) and, in an embodiment, the time delay verification step (step 124) can be performed in loop for each one of the digital user action(s) included in the digital user action preferences, until all the digital user actions included in the digital user action preferences are in the failed state.
- the abnormal event occurrence validation phase 140 includes a primary validation phase 142 of the occurrence of the abnormal event with the user and a secondary validation phase 150 of the occurrence of the abnormal event with the event validator(s).
- the primary validation phase 142 includes sending an electronic confirmation request to the user (step 144) and determining whether the user responds to the electronic confirmation request within a predetermined confirmation delay (step 146). If the user responds to the electronic confirmation request within the predetermined confirmation delay, nonoccurrence of the abnormal event is assumed and the action occurrence monitoring phase 120 can be resumed. If the user does not respond to the electronic confirmation request within the predetermined confirmation delay, the primary validation phase 142 has failed and the secondary validation phase 150 can be performed. In an embodiment, a predetermined time delay is applied between the primary validation phase 142 and the secondary validation phase 150, in order to reduce the possibility of the occurrence of a "false alarm".
- the secondary validation phase 150 includes the step of sending an electronic confirmation request to the event validator(s) (step 152). If, in response to the electronic confirmation request, at least one of the event validator(s) confirms that the abnormal event has occurred (step 154), the data release phase 160 can be performed. If, in response to the electronic confirmation request, at least one of the event validator(s) confirms that the abnormal event has not occurred (step 156), the action occurrence monitoring phase 120 can be resumed.
- the primary validation phase 142 or the secondary validation phase 150 can be performed again after a time delay has elapsed.
- the time delay can be specified by the data recipient in a response to the electronic confirmation request.
- the data release phase 160 includes the step of sending a data release request to the data recipient(s) (step 162). For each data recipient, if, in response to the data release request, the data recipient confirms the desire to receive the personal user data (step 164), the data release phase 160 further includes the step of releasing the personal user data to the data recipient. In an embodiment, the step of releasing the personal user data to the data recipient includes uploading the personal user data from the main system module to the electronic device of the user.
- the above described computer implemented method for performing the detection of an abnormal event and the selective data release of personal user data based on the detection can be computer steps performed by a combination of the main computing unit 30 and the electronic device 50 and/or the intermediate computing unit 60, having instructions stored in a memory for performing the steps.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Life Sciences & Earth Sciences (AREA)
- Evolutionary Biology (AREA)
- Evolutionary Computation (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Artificial Intelligence (AREA)
- Information Transfer Between Computers (AREA)
Abstract
L'invention concerne un système permettant de détecter l'apparition d'un événement anormal et d'effectuer une libération sélective de données. Le système comprend au moins un dispositif électronique utilisé pour effectuer au moins une action d'utilisateur numérique prédéterminée représentant des motifs d'utilisation de celui-ci par un utilisateur et pour générer des données d'action d'utilisateur indiquant la réalisation de l'action d'utilisateur numérique. Le système comprend également un système principal comprenant un module de détection d'événement anormal recevant les données d'action d'utilisateur et déterminant l'apparition d'un événement anormal sur la base de celles-ci et un module de distribution de données personnelles d'utilisateur libérant les données personnelles d'utilisateur mémorisées vers au moins un destinataire de données lors de la détermination de l'apparition de l'événement anormal. L'invention concerne également un procédé mis en œuvre par ordinateur permettant de détecter l'apparition d'un événement anormal pour un utilisateur et la libération sélective de données de données personnelles d'utilisateur de l'utilisateur sur la base de ladite détection.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201662406662P | 2016-10-11 | 2016-10-11 | |
| US62/406,662 | 2016-10-11 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2018068137A1 true WO2018068137A1 (fr) | 2018-04-19 |
Family
ID=61905045
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CA2017/051208 Ceased WO2018068137A1 (fr) | 2016-10-11 | 2017-10-11 | Système et procédé de détection automatisée d'événement anormal et de libération sélective de données sur la base de ladite détection |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2018068137A1 (fr) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020028988A1 (en) * | 2000-03-14 | 2002-03-07 | Kabushiki Kaisha Toshiba | Wearable life support apparatus and method |
| US20150188993A1 (en) * | 2012-06-01 | 2015-07-02 | Mark Dibner | System and method of storing and distributing data |
| US9185095B1 (en) * | 2012-03-20 | 2015-11-10 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
| US20160021081A1 (en) * | 2014-07-15 | 2016-01-21 | Verizon Patent And Licensing Inc. | Mobile device user authentication based on user behavior information |
-
2017
- 2017-10-11 WO PCT/CA2017/051208 patent/WO2018068137A1/fr not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020028988A1 (en) * | 2000-03-14 | 2002-03-07 | Kabushiki Kaisha Toshiba | Wearable life support apparatus and method |
| US9185095B1 (en) * | 2012-03-20 | 2015-11-10 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
| US20150188993A1 (en) * | 2012-06-01 | 2015-07-02 | Mark Dibner | System and method of storing and distributing data |
| US20160021081A1 (en) * | 2014-07-15 | 2016-01-21 | Verizon Patent And Licensing Inc. | Mobile device user authentication based on user behavior information |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9785758B1 (en) | User content access management and control | |
| KR101703015B1 (ko) | 컴퓨팅 장치의 분실 모드를 원격으로 개시하는 시스템 및 방법 | |
| US10042999B2 (en) | Methods and apparatus to manage password security | |
| US9083624B2 (en) | Mobile device or computer theft recovery system and method | |
| CN106716972B (zh) | 半自动故障转移 | |
| US9037685B2 (en) | Intelligent migration between devices having different hardware or software configuration | |
| US9544396B2 (en) | Remote application installation and control for a mobile device | |
| US8015163B2 (en) | Detecting duplicative user data on computing device | |
| US9460591B2 (en) | Event notification | |
| US10371472B2 (en) | System and method for event triggered information distribution | |
| US11811770B2 (en) | Systems and methods for data access notification alerts | |
| CN109672645B (zh) | 一种身份认证方法、用户终端及认证管理服务器 | |
| WO2014130145A1 (fr) | Barrières géographiques publiques et privées | |
| CA2781251A1 (fr) | Methode de surveillance de securite personnelle et application mobile pour celle-ci | |
| US11405382B2 (en) | Systems, methods, and apparatuses for implementing a web-based life management platform with user created electronic communications triggered upon future events | |
| EP3808048B1 (fr) | Instrumentation d'essai pour les actions de remédiation par intrusion | |
| WO2016164210A1 (fr) | Plate-forme de dépôt fondé sur des preuves préemptives électroniques | |
| US20170091712A1 (en) | Apparatus and Method for Employee Time Entry and Accounting | |
| US20160180098A1 (en) | Text message management | |
| WO2018068137A1 (fr) | Système et procédé de détection automatisée d'événement anormal et de libération sélective de données sur la base de ladite détection | |
| EP3506566B1 (fr) | Procédé et dispositif pour la surveillance à distance d'objets connectés multiples | |
| US20150054644A1 (en) | Institutional alarm system and method | |
| US20140344330A1 (en) | System for a Monitored and Reconstructible Personal Rendezvous Session | |
| JP7465461B2 (ja) | 見守りプログラム | |
| CN115955506B (zh) | 微服务发布方法、装置、系统及计算机可读存储介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17861082 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 17861082 Country of ref document: EP Kind code of ref document: A1 |