ABNORMAL EVENT AND SELECTIVE DATA RELEASE BASED ON

SAID DETECTION

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit under 35 U.S.C. § 1 19(e) of United States provisional patent application no. 62/406,662 which was filed on October 1 1 , 2016. The entirety of the aforementioned application is herein incorporated by reference.

TECHNICAL FIELD OF THE INVENTION

[0002] 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.

BACKGROUND

[0003] It is known that personal information such as, without being limitative insurance, financial, banking and savings information, identification and access codes for online resources, such as websites, web services, computer applications, social media sites or any other private information of an individual, are often lost following the death or incapacitation of the individual. In many cases, this is due to a simple lack of knowledge of the personal information of an individual by members of his/her family, his/her friends or other persons of confidence of his/her entourage.

[0004] Hence, there is known in the art systems and methods for storing personal information and subsequently transmitting the information to previously selected individuals, upon occurrence of an abnormal event (such as, for example and without being limitative, the death or the incapacitation of the individual for which the personal information has been stored).

[0005] For example, United States patent application no. 2015/0188993 describes a system and a method for storing and distributing data, upon the occurrence of an event. Concerning the determination of the occurrence of the 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. Subsequently, 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).

[0006] Such reliance on a notification by the identified user of the occurrence of the event brings uncertainty into the event detection process and has several drawbacks. For example, it is undesirable as it can lead to delays in the notification of the occurrence of the event to the system by the identified users, a lack of notification of the occurrence of the event by the identified users, or other situations which hamper the release of the data to the data recipient(s) upon occurrence of the event, as a result of the system not being promptly notified of the occurrence of the event. Therefore, it would be advantageous if the detection of the occurrence of the abnormal event could be automated, i.e. could be determined automatically by a computer system, rather than relying on notification by an individual.

[0007] In view of the above, there is a need for an improved system and method for storing and automatically distributing data, upon the occurrence of an event, which would be able to overcome or at least minimize some of the above-discussed prior art concerns.

BRIEF SUMMARY OF THE INVENTION

[0008] In accordance with a first general aspect, there is provided a system for detecting an occurrence of an abnormal event and performing selective data release based on said detection. The system 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.

[0009] In an embodiment, 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.

[0010] In an embodiment, 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.

[0011] In an embodiment, 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.

[0012] In an embodiment, the at least one event validator includes the at least one data recipient.

[0013] In an embodiment, 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.

[0014] In an embodiment, 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.

[0015] In accordance with another general aspect, there is also provided 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. The method 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 therewith; determining the occurrence of the abnormal event if each one of the at least one digital user action is in a failed state; releasing the stored personal user data to at least one data recipient upon determination of the occurrence of the abnormal event.

[0016] In an embodiment, 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.

[0017] The computer implemented method of claim 9, wherein 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.

[0018] In an embodiment, 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. [0019] In an embodiment, 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.

[0020] In an embodiment, 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.

[0021] In accordance with another general aspect, there is further provided 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.

[0022] In accordance with another general aspect, there is further provided 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.

BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Other objects, advantages and features will become more apparent upon reading the following non-restrictive description of embodiments thereof, given for the purpose of exemplification only, with reference to the accompanying drawings in which:

[0024] Figure 1 is a graphical representation of a system for performing detection of an abnormal event and selective data release based on the detection. [0025] 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.

[0026] Figure 3 is a flow chart showing the steps of a registering phase of the method of Figure 2, in accordance with an embodiment.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

DETAILED DESCRIPTION

[0032] In the following description, the same numerical references refer to similar elements. The embodiments, geometrical configurations, materials mentioned and/or dimensions shown in the figures or described in the present description are embodiments only, given solely for exemplification purposes.

[0033] In addition, although the embodiments, as illustrated in the accompanying drawings, consist of several components and although the associated method includes steps as explained and illustrated herein, not all of these components, configurations and steps are essential and thus should not be taken in their restrictive sense. It is to be understood, as also apparent to a person skilled in the art, that other suitable components and cooperation thereinbetween, as well as other suitable configurations, organizations and/or architectures may be used for the system and method for detecting the occurrence of an abnormal event and proceeding to the selective data release of stored data based on said detection, as will be briefly explained herein and as can be easily inferred herefrom, by a person skilled in the art, without departing from the scope of the invention.

[0034] Broadly described, 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.

[0035] In the course of the present document, it will be understood that 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.

[0036] 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. For example and without being limitative, 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. In an embodiment, 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. In an embodiment, 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. One skilled in the art will understand that the above information is given as example and numerous other information can be included in the personal user data, in accordance with the desires of the user.

[0037] The term "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.

[0038] The term "electronic device" is used to define any device for storing and processing data, typically in binary form, according to instructions. For example and without being limitative, 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).

[0039] One skilled in the art will also understand that, in the course of the present document, the term "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. The term "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.

[0040] The term "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). For example and without being limitative, 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. Moreover, 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. One skilled in the art will understand that, only a few examples of 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.

[0041] Referring generally to Figure 1 , in accordance with one embodiment, there is provided 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. As mentioned above, 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)).

[0042] In the embodiment shown, 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.

[0043] In an embodiment, 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. One skilled in the art will understand that 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). One skilled in the art will understand that, in the course of the present description, the term, "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). For example and without being limitative, 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. One skilled in the art will understand that, in an alternative embodiment, 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.

[0044] In an embodiment, 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).

[0045] In an embodiment, 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. In an embodiment, 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.

[0046] In an embodiment, 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. In other words, 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.

[0047] In an embodiment, 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. In an embodiment, 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.

[0048] 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.).

[0049] 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.).

[0050] 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. [0051] One skilled in the art will understand that, in an embodiment, 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. In an embodiment, 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.

[0052] In an embodiment, 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. In other words, 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. One skilled in the art will understand that 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. In other words, 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. should be indicative that something has resulted in an unhabitual change in the habits of the user regarding the corresponding digital actions). It will be understood that, in an embodiment, 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.

[0053] In an embodiment, 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). Once uploaded, the personal user data is securely stored by the main system module 20 onto an associated storage medium.

[0054] One skilled in the art will understand that, in an embodiment, 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.

[0055] Still referring to Figure 1 , 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. In other words, 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.

[0056] 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. In the following description, it will be understood that 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). One skilled in the art will understand that, even though 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.

[0057] In an embodiment, 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.

[0058] For example and without being limitative, in an embodiment where one digital user action included in the digital user action preferences is directed to the sending, response and/or transfer of an email by the user, 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. In other words, 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). Similarly, in an embodiment where one digital user action included in the digital user action preferences include actions performed on social media, 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. In an alternative embodiment, 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.

[0059] In another alternative embodiment, 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.

[0060] In an embodiment, 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.

[0061] In an embodiment, 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. In an embodiment, 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. In an embodiment, the choice of confirmation request type can be predetermined by the user. Following the transmission of the electronic confirmation request, 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.

[0062] For example, in an embodiment, 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. 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. Hence, the abnormal event validation module 24 is in data communication with the electronic device 50 directly or indirectly. Indeed, it will be understood that reference to the 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).

[0063] For example and without being limitative, in an embodiment where email is used as electronic confirmation request (i.e. the electronic confirmation request is of the email type), 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.

[0064] 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.

[0065] In an embodiment, following the above described user driven confirmation phase of the abnormal event validation module 24, 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. Upon receipt of the corresponding electronic confirmation request, 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.

[0066] Once again, 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). Hence, for example and without being limitative, in an embodiment where email is used as electronic confirmation request (i.e. the electronic confirmation request is of the email type), 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.

[0067] In the event that the occurrence of the abnormal event is denied by at least one of the user or the event validator(s) (in response to the corresponding electronic confirmation request), 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.

[0068] One skilled in the art will understand that, in an embodiment, the event validator identified by the user and stored in the main system module 20 to perform the additional validation (i.e. the validation subsequent to the user validation), through their corresponding electronic device 50, can be the same individuals as the data recipient(s). Moreover, in an embodiment where multiple data recipients are selected, only one or a subset of the data recipients can be used by the abnormal event validation module 24 as event validator.

[0069] Still referring to Figure 1 , 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.

[0070] 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.

[0071] In an embodiment, following the validation of the occurrence of the abnormal event by the abnormal event validation module 24 (i.e. when the user validation data and/or the recipient validation data received by the abnormal even validation module 26 is representative of a confirmation of the occurrence of the abnormal event), the personal user data distribution module 26 transmits an electronic data access request to the data recipient(s). For example and without being limitative, the electronic data access request can be an email, a text message, an instant message, or the like. For example and without being limitative, 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. [0072] Therefore, for example and without being limitative, in an embodiment where email is used as electronic data access request (i.e. the electronic data access request is of the email type), 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. Following the receipt 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.

[0073] The system 10 for the detection of an abnormal event and the selective data release based on the detection having been described above, a computer implemented method for performing the detection of an abnormal event and the selective data release of personal user data based on the detection, will now be described in more details below.

[0074] Referring to Figure 2, in an embodiment, 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.

[0075] Referring to Figure 3, in an embodiment 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). As mentioned above, in an embodiment, 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.

[0076] Following the registering phase 1 10, 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. In an embodiment, every time a digital user action is performed, 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. In an alternative embodiment, 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).

[0077] Referring to Figure 4, in an embodiment, 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.

[0078] In the embodiment shown, 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). Given that, as mentioned above, in an embodiment, 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.

[0079] In the embodiment shown, if no occurrence of the digital user action is detected during the occurrence verification step (step 122), 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. One skilled in the art will understand that, such a time delay verification step (step 124) 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. In an embodiment where the occurrence verification step (step 122) is performed only at a frequency corresponding substantially to the maximal time delay of the corresponding digital user action, the time delay verification step (step 124) can be omitted.

[0080] In an alternative embodiment (not shown), 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.

[0081] Given that the digital user action preferences can include more than one digital user action, in an embodiment, 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.

[0082] Referring to Figure 5, in an embodiment, 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).

[0083] Referring to Figure 5A, in an embodiment, 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".

[0084] Referring to Figure 5B, in an embodiment, 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. If, in response to the electronic confirmation request, at least one of the event validator(s) confirms that the abnormal event has not yet occurred, but that the user is currently at least temporarily incapacitated, or indicates that he/she is unsure if the abnormal event occurred and requires more time to investigate (step 158), the primary validation phase 142 or the secondary validation phase 150 can be performed again after a time delay has elapsed. In an embodiment, the time delay can be specified by the data recipient in a response to the electronic confirmation request.

[0085] It will be understood that, in an embodiment, at any time during the primary validation phase 142 or secondary validation phase 150, if a user action is registered, the user is understood to be active and the user action occurrence monitoring phase 120 can be resumed.

[0086] Referring to Figure 6, in an embodiment, 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.

[0087] One skilled in the art will understand that 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.

[0088] In view of the above, it will be understood that, in an embodiment, there can be provided computer readable memories of distributed devices having recorded thereon statements and instructions for execution by computers in data communication over a network, with the statements and instructions comprising code for performing the above-describe steps of the described computer implemented method. In another embodiment, there can also be provided a computer program product comprising computer readable memories of distributed devices storing computer executable instructions thereon that when executed by computers in data communication over a network, perform the method steps of the above described computer implemented method.

[0089] Several alternative embodiments and examples have been described and illustrated herein. The embodiments of the invention described above are intended to be exemplary only. A person skilled in the art would appreciate the features of the individual embodiments, and the possible combinations and variations of the components. A person skilled in the art would further appreciate that any of the embodiments could be provided in any combination with the other embodiments disclosed herein. It is understood that the invention may be embodied in other specific forms without departing from the central characteristics thereof. The present examples and embodiments, therefore, are to be considered in all respects as illustrative and not restrictive, and the invention is not to be limited to the details given herein. Accordingly, while specific embodiments have been illustrated and described, numerous modifications come to mind without significantly departing from the scope of the invention as defined in the appended claims.