CLIAMS:We claim:
1. A method for enabling creation of a user snapshot for a user based on data collected from at least one User Equipment (UE), the method comprising
collecting information from at least one application present on the UE by a snapshot agent, wherein the snapshot agent is present on the UE;
creating a user snapshot by the snapshot agent based on the collected information;
syncing the user snapshot with a snapshot manager by the snapshot agent; and
maintaining a consolidated user snapshot for the user by the snapshot manager based on the user snapshot synced with the snapshot agent.
2. The method, as claimed in claim 1, wherein the method further comprises of the snapshot manager pushing the snapshot agent to the UE using the cloud.
3. The method, as claimed in claim 2, wherein the method further comprises of the snapshot manager pushing the snapshot agent to the UE, on the user registering with the snapshot manager.
4. The method, as claimed in claim 2, wherein the method further comprises of the snapshot manager pushing the snapshot agent to the UE, on the user connecting to the snapshot manager for the first time using the UE, wherein the user has previously registered with the snapshot manager.
5. The method, as claimed in claim 1, wherein the method further comprises of the snapshot agent updating the user snapshot at periodic intervals.
6. The method, as claimed in claim 1, wherein the method further comprises of the snapshot agent updating the user snapshot on at least one trigger event occurring.
7. The method, as claimed in claim 1, wherein syncing the user snapshot with the snapshot manager by the snapshot agent is done at periodic intervals.
8. The method, as claimed in claim 1, wherein syncing the user snapshot with the snapshot manager by the snapshot agent is done on at least one trigger event occurring.
9. The method, as claimed in claim 1, wherein the method further comprises of the snapshot manager cleaning duplicate data present in the snapshot.
10. The method, as claimed in claim 1, wherein maintaining the consolidated user snapshot for the user by the snapshot manager comprises
creating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is not present; and
updating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is present.
11. The method, as claimed in claim 1, wherein the method further comprises of the snapshot manager syncing the consolidated user snapshot with at least one other UE associated with the user.
12. The method, as claimed in claim 1, wherein the method further comprises of the snapshot manager exposing the consolidated user snapshot to at least one external entity.
13. The method, as claimed in claim 1, wherein the method further comprises of the snapshot manager exposing the consolidated user snapshot to at least one external entity, on the user providing permission.
14. A system for enabling creation of a user snapshot for a user based on data collected from at least one User Equipment (UE), the system comprising a snapshot agent present on the UE and a snapshot manager, the snapshot agent configured for
collecting information from at least one application present on the UE;
creating a user snapshot based on the collected information; and
syncing the user snapshot with the snapshot manager;
the snapshot manger configured for
maintaining a consolidated user snapshot for the user based on the use snapshot synced with the snapshot agent.
15. The system, as claimed in claim 14, wherein the snapshot manager is configured for pushing the snapshot agent to the UE using the cloud.
16. The system, as claimed in claim 15, wherein the snapshot manager is configured for pushing the snapshot agent to the UE, on the user registering with the snapshot manager.
17. The system, as claimed in claim 15, wherein the snapshot manager is configured for pushing the snapshot agent to the UE, on the user connecting to the snapshot manager for the first time using the UE, wherein the user has previously registered with the snapshot manager.
18. The system, as claimed in claim 14, wherein the snapshot agent is configured for updating the user snapshot at periodic intervals.
19. The system, as claimed in claim 14, wherein the snapshot agent is configured for updating the user snapshot on at least one trigger event occurring.
20. The system, as claimed in claim 14, wherein the snapshot agent is configured for syncing the user snapshot with the snapshot manager at periodic intervals.
21. The system, as claimed in claim 14, wherein the snapshot agent is configured for syncing the user snapshot with the snapshot manager on at least one trigger event occurring.
22. The system, as claimed in claim 14, wherein the snapshot manager is configured for cleaning duplicate data present in the snapshot.
23. The system, as claimed in claim 14, wherein the snapshot manager is configured for maintaining the consolidated user snapshot for the user by
creating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is not present; and
updating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is present.
24. The system, as claimed in claim 14, wherein the snapshot manager is configured for syncing the consolidated user snapshot with at least one other UE associated with the user.
25. The system, as claimed in claim 14, wherein the snapshot manager is configured for exposing the consolidated user snapshot to at least one external entity.
26. The system, as claimed in claim 14, wherein the snapshot manager is configured for exposing the consolidated user snapshot to at least one external entity, on the user providing permission.
27. A User Equipment (UE) comprising a snapshot agent, the UE further configured for
collecting information from at least one application present on the UE;
creating a user snapshot based on the collected information; and
syncing the user snapshot with a snapshot manager.
28. The UE, as claimed in claim 27, wherein the UE is configured for updating the user snapshot at periodic intervals.
29. The UE, as claimed in claim 27, wherein the UE is configured for updating the user snapshot on at least one trigger event occurring.
30. The UE, as claimed in claim 27, wherein the UE is configured for syncing the user snapshot with the snapshot manager at periodic intervals.
31. The UE, as claimed in claim 27, wherein the UE is configured for syncing the user snapshot with the snapshot manager on at least one trigger event occurring.
32. A snapshot manager connected to at least one User Equipment (UE), the UE comprising a snapshot agent, the snapshot manager configured for
syncing a user snapshot of a user of the UE with the snapshot agent; and
maintaining a consolidated user snapshot for the user based on the user snapshot synced with the snapshot agent.
33. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for pushing the snapshot agent to the UE using the cloud.
34. The snapshot manager, as claimed in claim 33, wherein the snapshot manager is configured for pushing the snapshot agent to the UE, on the user registering with the snapshot manager.
35. The snapshot manager, as claimed in claim 33, wherein the snapshot manager is configured for pushing the snapshot agent to the UE, on the user connecting to the snapshot manager for the first time using the UE, wherein the user has previously registered with the snapshot manager.
36. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for cleaning duplicate data present in the snapshot.
37. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for maintaining the consolidated user snapshot for the user by
creating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is not present; and
updating a consolidated user snapshot by the snapshot manager, if the consolidated user snapshot is present.
38. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for syncing the consolidated user snapshot with at least one other UE associated with the user.
39. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for exposing the consolidated user snapshot to at least one external entity.
40. The snapshot manager, as claimed in claim 32, wherein the snapshot manager is configured for exposing the consolidated user snapshot to at least one external entity, on the user providing permission.

Date: 21st May 2014

Signature:
Vikram Pratap Singh Thakur
,TagSPECI:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION

“Creation of a user snapshot based on data from multiple communication means”

APPLICANTS:

Name : HCL Technologies Limited

Nationality : Indian

Address : HCL Technologies Limited,
Vertex Tech park, 564,
Pattandur Agrahara Road,
Bangalore – 560066

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-

FIELD OF INVENTION
[001] This invention relates to user management and more particularly to creation of a user snapshot for a user based on data related to the user collected from a plurality of communication devices and/or applications.

BACKGROUND OF INVENTION
[002] Currently, users use a plurality of communication devices (such as a computer, laptop, smart phone, phone, PDA (Personal Digital Assistant), tablet and so on) using a plurality of communication applications (such as browsers, IP messaging media (such as Whatsapp, Viber, Google Talk, Snapchat, Yahoo Messenger, Facetime and so on), apps, mail clients, games, voice calls, SMSs (Short Messaging Services) and so on) on each of the devices. This usage may result in fragmentation of user data.
[003] Some sites/applications/devices may be able to tie the data together. For example, consider a user of an Android mobile device, which uses the Google ID of the user to identify the user and collect data about the user based on his actions on the mobile device and tied together using his Google ID. The Google ID may also be used to collect data about the user from a browser on a computer on which the user is logged in using his Google ID. In another example, browsers may use cookies to track the user across multiple websites.
[004] However, the above mentioned examples rely on the user logging in using his ID (such as a Google ID and so on) or the user enabling cookies which may be used to track him. If the user does not login using his ID, there is no way to tie the data collected regarding the user back to his snapshot. There is no method which enables tracing back of data collected from a plurality of devices and/or applications to a single user and a snapshot associated with that user.

OBJECT OF INVENTION
[005] The principal object of this invention is to propose a method and system configured to link multiple user communication means (user equipments and/or applications) and maintain a user snapshot, wherein the user snapshot is continuously updated and comprises of interests and patterns of the users.
[006] Another object of the invention is to propose a method and system which enables usage of the user snapshot for customized marketing targeted towards the user.

STATEMENT OF INVENTION
[007] Accordingly the invention provides a method for enabling creation of a user snapshot for a user based on data collected from at least one User Equipment (UE), the method comprising collecting information from at least one application present on the UE by a snapshot agent, wherein the snapshot agent is present on the UE; creating a user snapshot by the snapshot agent based on the collected information; syncing the user snapshot with a snapshot manager by the snapshot agent; and maintaining a consolidated user snapshot for the user by the snapshot manager based on the user snapshot synced with the snapshot agent.
[008] Also, provided herein is a system for enabling creation of a user snapshot for a user based on data collected from at least one User Equipment (UE), the system comprising a snapshot agent present on the UE and a snapshot manager, the snapshot agent configured for collecting information from at least one application present on the UE; creating a user snapshot based on the collected information; and syncing the user snapshot with the snapshot manager; the snapshot manger configured for maintaining a consolidated user snapshot for the user based on the use snapshot synced with the snapshot agent.
[009] Provided herein is a User Equipment (UE) comprising a snapshot agent, the UE further configured for collecting information from at least one application present on the UE; creating a user snapshot based on the collected information; and syncing the user snapshot with a snapshot manager.
[0010] Provided herein is a snapshot manager connected to at least one User Equipment (UE), the UE comprising a snapshot agent, the snapshot manager configured for syncing a user snapshot of a user of the UE with the snapshot agent; and maintaining a consolidated user snapshot for the user based on the user snapshot synced with the snapshot agent.
[0011]
[0012] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF FIGURES
[0013] This invention is illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0014] FIG. 1 depicts a communication system comprising of a plurality of User Equipments (UEs) connected to a server, according to embodiments as disclosed herein;
[0015] FIG. 2 illustrates a snapshot manager, according to embodiments as disclosed herein;
[0016] FIG. 3 illustrates a UE comprising of a snapshot agent, according to embodiments as disclosed herein; and
[0017] FIG. 4 is a flowchart illustrating the process of a user registering with the snapshot manager, according to embodiments as disclosed herein;
[0018] FIG. 5 is a flowchart illustrating the process of a user equipment collecting data and sharing data with the snapshot manager, according to embodiments as disclosed herein; and
[0019] FIG. 6 is a flowchart illustrating the process a snapshot manager receiving data from a user equipment and performing at least one operation on the data, according to embodiments as disclosed herein.

DETAILED DESCRIPTION OF INVENTION
[0020] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0021] The embodiments herein achieve a interlinked unique user snapshot system wherein all of user handles may be linked into a common snapshot. Referring now to the drawings, and more particularly to FIGS. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[0022] FIG. 1 depicts a communication system comprising of a plurality of User Equipments (UEs) connected to a server, according to embodiments as disclosed herein. The UEs may be any device which may enable a user to communicate with at least one external entity such as the internet, a Local Area Network (LAN) and so on such as a computer, laptop, smart phone, phone, PDA (Personal Digital Assistant), tablet and so on. A plurality of UEs 101 may be connected to a snapshot manager 102. The snapshot manager 102 may be a cloud provider. The snapshot manager 102 may be connected to at least one database 103. The snapshot manager 102 may store data received from the UE 101 in the database 103. The database 103 may be located internal to the snapshot manager 102. The database 103 may be located external to the snapshot manager 102 and may be connected to the snapshot manager 102 using a suitable wired and/or wireless means.
[0023] The snapshot manager 102 may enable a user to register using a UE 101. The snapshot manager 102 may enable the user to register using at least one user credential (such as a username and a password, an email address and a password, a username and password associated with another website (such as Facebook, Google, Microsoft, Yahoo, Linkedin and so on), a phone number and a password and so on). The snapshot manager 102 may enable the user to link multiple UEs being used by the user, by using his credentials. To link his UEs, the user may be required to enter his credentials on each one of his UEs. The user may have separate credentials for each of his UEs, wherein the snapshot manager 102 may use a suitable means to link the credentials so as to maintain a common user snapshot, irrespective of the credentials and/or the UEs being used by the user.
[0024] On a user registering or the user using his credentials for the first time from a UE 101, the snapshot manager 102 pushes a snapshot agent to the UE 101. The snapshot agent may be present in a memory internal to the snapshot manager 102. The snapshot agent may be present in the database 103 and may be fetched from the database 103 by the snapshot manager 102. The snapshot manager 102 may push the snapshot agent to the UE 101 through the cloud. The snapshot agent may send data regarding the user to the snapshot manager 102 at periodic intervals or on a specific trigger event occurring. The data may be a user snapshot created by the snapshot agent, based on the tasks performed by the user on the UE 101 or messages received/viewed by the user on the UE 101.
[0025] The snapshot manager 102, on receiving the data from the UE 101, may scan the received data to check the credentials to which the received data belongs. The snapshot manager 102 may check if duplicate data is present in the received data. The received data may be from one UE or from multiple UEs belonging to the same user. On detecting duplicate data, the snapshot manager 102 may clean the duplicate data. The snapshot manager 102 may further store the data. The snapshot manager 102 may update the consolidated user snapshot (already present with the snapshot manager 102), based on the data received from the UE 101. The snapshot manager 102 may create the consolidated user snapshot, if the user snapshot is present with the snapshot manager 102.
[0026] The snapshot manager 102 may expose the consolidated user snapshot to at least one external entity. The snapshot manager 102 may expose the consolidated user snapshot to the external entity, on receiving the requisite permissions from the user.
[0027] FIG. 2 illustrates a snapshot manager, according to embodiments as disclosed herein. The snapshot manager 102 comprises of a registration manager 201, a snapshot agent manager 202, a controller 203 and a communication interface 204. The communication interface 204 may be used by the snapshot manager 102 to communicate with an external device, such as the UE 101, the database 103, an external entity accessing a user snapshot and so on.
[0028] On a user connecting to the snapshot manager 102, the controller 203 may check if the user is a registered user. The user may connect to the snapshot manager 102 through an app present on the UE 101 or using a web based application or any other equivalent means. If the user is not a registered user, the controller 203 may inform the registration manager 201.
[0029] The registration manager 201 may enable a user to register. The registration manager 201 may enable the user to register using at least one user credential (such as a username and a password, an email address and a password, a username and password associated with another website (such as Facebook, Google, Microsoft, Yahoo, Linkedin and so on), a phone number and a password and so on). The registration manager 201 may enable the user to link multiple UEs being used by the user, by using his credentials. To link his UEs, the user may be required to enter his credentials on each one of his UEs. The user may have separate credentials for each of his UEs, wherein the registration manager 201 may use a suitable means to link the credentials so as to maintain a common user snapshot, irrespective of the credentials and/or the UEs being used by the user.
[0030] On a user registering or the user using his credentials for the first time from a UE 101, the controller 203 enables the snapshot agent manager 202 to push the snapshot agent to the UE 101. The snapshot agent manager 202 may fetch the snapshot agent from a memory internal to the snapshot manager 102. The snapshot agent manager 202 may fetch the snapshot agent from snapshot agent from the database 103. The snapshot agent manager 202 may push the snapshot agent to the UE 101 through the cloud using the communication interface 204.
[0031] The controller 203, on receiving the user snapshot from the UE 101 through the communication interface 204, may scan the received snapshot to check the credentials to which the received snapshot belongs. The controller 203 may further check if duplicate information is present in the received data by comparing the snapshot with the consolidated user snapshot already present with the controller 203 (if the consolidated user snapshot is present with the snapshot manager 102). The received snapshot may be from one UE or from multiple UEs belonging to the same user. On detecting duplicate information, the controller 203 may clean the duplicate information. The controller 203 may further store the consolidated user snapshot in a suitable location such as an internal memory, the database 103, an external memory and so on. If the consolidated user snapshot is already present, the controller 203 may update the consolidated user snapshot, based on the received snapshot.
[0032] The controller 203 may sync the consolidated user snapshot present in the snapshot manager 102 with all the UEs associated with the user. The controller 203 may sync at pre-defined intervals. The controller 203 may also sync on at least one trigger event occurring (such as a change in the consolidated user snapshot).
[0033] The controller 203 may expose the consolidated user snapshot to at least one external entity. The controller 203 may expose the consolidated user snapshot to the external entity, on receiving the requisite permissions from the user.
[0034] FIG. 3 illustrates a UE comprising of a snapshot agent, according to embodiments as disclosed herein. The UE 101 comprises of a snapshot agent 301, a communication interface 306 and a memory 307. The communication interface 306 may be used by the UE 101 to communicate with an external device, such as the snapshot manager 102, a communication network and so on. The memory 307 may comprise of volatile memory and/or non-volatile memory.
[0035] On a user registering with the snapshot manager 102 or accessing the snapshot manager 102 for the first time using the UE 101, the snapshot agent 301 gets pushed to the UE 101. The snapshot agent 301 may request the user for the requisite permissions in accessing data present in the UE, accessing data from various applications resident on the UE 101.
[0036] The snapshot agent 301 comprises of an identification module 302, a scanning module 303, a snapshot controller 304 and a synchronization module 305. The identification module 302 creates a user snapshot for the UE. The identification module 302 may also partition a storage area in the memory 306. This storage area may be used to locally store all the data extracted and processed by the snapshot agent 301. The snapshot agent 301 may plug itself with all the applications which are sources of user communication, such as browsers, IP messaging media (such as Whatsapp, Viber, Google Talk, Snapchat, Yahoo Messenger, Facetime and so on), apps, mail clients, games, voice calls, SMSs (Short Messaging Services) and so on).
[0037] The scanning module 303 may extract information from the applications resident on the UE 101. The scanning module 303 may extract the information at pre-determined intervals. The scanning module 303 may also extract information on at least one trigger event occurring, wherein examples of the trigger event may be opening a new application, closing an application, sending data by an application, receiving data by an application and so on. The pre-determined intervals and the trigger events may be defined by an authorized person and/or entity at the snapshot manager 102. The pre-determined intervals and the trigger events may be refreshed in real time and pushed to the UE 101 from the snapshot manager 102. Consider the example of a browser, the scanning module 303 may check if the browser is running and the scanning module 303 may extract the cookies from the browser in a continuous manner to extract updates from the browser. The scanning module 303 may also fetch the cookies from the browser, on detecting that the browser is being closed. Similarly for text messages and applications over IP, the scanning module 303 may use a selective network packet sniffing means to extract the text of the communication. For communication performed using a telecom communications network, prior approval is taken from the user for accessing text messages and/or voice data. For social networks (such as Facebook, Twitter, Instagram, Pinterest and so on) and so on, the scanning module 303 may user a web crawler to extract feeds, conversations and so on. Once the user provides the approval, the scanning module 303 records all outgoing SMS or calls. The scanning module 303 may store the recorded information in a text format.
[0038] The snapshot controller 304 monitors the information stored by the scanning module 303 in the storage area. The snapshot controller 304, on the information reaching a pre-defined level, creates a user snapshot. The pre-defined level may be defined in terms of a minimum number of fields or at least one specific type of data that has to be present. The user snapshot may comprise of the name of the user, user characteristics (such as personality, preferences in food, shopping, friends list and so on), current location of the user, recent topics of interest to the user, trending conversations (what the is user conversing most about), recent purchases, age group to which the user belongs, social media preferences of the user (trending topics, user subscriber groups and feeds) and so on. The snapshot controller 304 may monitor the information being stored in the storage area and may update the snapshot at pre-determined intervals. The snapshot controller 304 may also update the snapshot on at least one trigger event occurring, wherein examples of the trigger event may be the user changing locations, a new topic the user is showing interest and so on. The pre-determined intervals and the trigger events may be defined by an authorized person and/or entity at the snapshot manager 102. The pre-determined intervals and the trigger events may be refreshed in real time and pushed to the UE 101 from the snapshot manager 102.
[0039] At pre-defined intervals and/or a specific trigger even occurring (such as user snapshot being updated); the synchronization module 305 updates the user snapshot in the snapshot manager 102. The synchronization module 305 may sync the entire updated snapshot with the snapshot manager 102. The synchronization module 305 may sync only the change in the user snapshot with the snapshot manager 102.
[0040] FIG. 4 is a flowchart illustrating the process of a user registering with the snapshot manager, according to embodiments as disclosed herein. The user registers (401) with the snapshot manager 102. The user may register with snapshot manager 102 using at least one user credential (such as a username and a password, an email address and a password, a username and password associated with another website (such as Facebook, Google, Microsoft, Yahoo, Linkedin and so on), a phone number and a password and so on). The snapshot manager 102 checks (402) if the user wants to link multiple UEs by using his credentials, wherein the multiple UEs may be used by the user. If the user wants to link multiple UEs, the user enters (403) his credentials on each one of his UEs. The snapshot manager 102 links (404) the credentials and UEs so as to maintain a common user snapshot, irrespective of the credentials and/or the UEs being used by the user. On a user registering and linking one or more UEs, the snapshot manager 102 pushes (405) a snapshot agent to the UE(s) 101. The snapshot agent may be present in a memory internal to the snapshot manager 102. The snapshot agent may be present in the database 103 and may be fetched from the database 103 by the snapshot manager 102. The snapshot manager 102 may push the snapshot agent to the UE 101 through the cloud. The snapshot agent 301 creates (406) a user snapshot for the UE 101. The snapshot agent 301 also partitions (407) a storage area in the memory 306. This storage area may be used to locally store all the data extracted and processed by the snapshot agent 301. The snapshot agent 301 plugs itself (408) with all the applications which are sources of user communication, such as browsers, IP messaging media (such as Whatsapp, Viber, Google Talk, Snapchat, Yahoo Messenger, Facetime and so on), apps, mail clients, games, voice calls, SMSs (Short Messaging Services) and so on). The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
[0041] FIG. 5 is a flowchart illustrating the process of a user equipment collecting data and sharing data with the snapshot manager, according to embodiments as disclosed herein. The snapshot agent 301 extracts (501) information from the applications resident on the UE 101 and stores (502) the extracted information in the memory. The snapshot agent 301 may extract the information at pre-determined intervals. The snapshot agent 301 may also extract information on at least one trigger event occurring, wherein examples of the trigger event may be opening a new application, closing an application, sending data by an application, receiving data by an application and so on. The pre-determined intervals and the trigger events may be defined by an authorized person and/or entity at the snapshot manager 102. The pre-determined intervals and the trigger events may be refreshed in real time and pushed to the UE 101 from the snapshot manager 102. The snapshot agent 301 monitors (503) the information stored by the scanning module 303 in the storage area. The snapshot agent 301 checks (504) if the information has reached a pre-defined level. On the information reaching a pre-defined level, the snapshot agent 301 creates (505) a user snapshot. The user snapshot may comprise of the name of the user, user characteristics (such as personality, preferences in food, shopping, friends list and so on), current location of the user, recent topics of interest to the user, trending conversations (what the is user conversing most about), recent purchases, age group to which the user belongs, social media preferences of the user (trending topics, user subscriber groups and feeds) and so on. The snapshot agent 301 updates (506) the snapshot. The snapshot agent 301 may update the snapshot at pre-determined intervals, based on the information being stored in the storage area and may. The snapshot agent 301 may also update the snapshot on at least one trigger event occurring, wherein examples of the trigger event may be the user changing locations, a new topic the user is showing interest and so on. The pre-determined intervals and the trigger events may be defined by an authorized person and/or entity at the snapshot manager 102. The pre-determined intervals and the trigger events may be refreshed in real time and pushed to the UE 101 from the snapshot manager 102. At pre-defined intervals and/or a specific trigger even occurring (such as user snapshot being updated), the snapshot agent 301 syncs (507) the user snapshot with the snapshot manager 102. The snapshot agent 301 may sync the entire updated snapshot with the snapshot manager 102. The snapshot agent 301 may sync only the change in the user snapshot with the snapshot manager 102. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.
[0042] FIG. 6 is a flowchart illustrating the process a snapshot manager receiving data from a user equipment and performing at least one operation on the data, according to embodiments as disclosed herein. The snapshot manager 102, on receiving (601) the snapshot from the UE 101, scans (602) the received snapshot to identify the user to which the received snapshot belongs. The snapshot manager 102 further checks (603) if duplicate data is present in the received snapshot. The received data may be from one UE or from multiple UEs belonging to the same user. On detecting duplicate data, the snapshot manager 102 cleans (604) the duplicate data. The snapshot manager 102 further creates or updates (605) the consolidated user snapshot based on the received snapshot in a suitable location such as an internal memory, the database 103, an external memory and so on. The snapshot manager 102 checks (606) if there is more than one UE associated with the consolidated user snapshot present in the snapshot manager 102. If there is more than one UE associated with the user snapshot present in the snapshot manager 102, the snapshot manager 102 syncs (607) the consolidated user snapshot with all the UEs associated with the user. The snapshot manager 102 may sync at pre-defined intervals. The snapshot manager 102 may also sync on at least one trigger event occurring (such as a change in the consolidated user snapshot). The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.
[0043] Embodiments disclosed herein enable use of a snapshot agent resident on the UE to create a user snapshot and the UE sends only the user snapshot to an external entity (the snapshot manager herein). The information extracted from the applications resident on the UE are not transmitted or exposed to an external entity, hereby ensuring security and maintaining the privacy of the user and the information. Also, the bandwidth requirement is reduced, as merely the user snapshot is transmitted and not the entire set of information.
[0044] Embodiments disclosed herein provide a consolidated unified view of the user snapshot in a single location. Embodiments disclosed herein provide a central repository of all user data such as interests, behaviors, buying patterns direct from the applications and/or UEs that a user uses for communication. Embodiments disclosed herein provide a means for linking of all user communication channels to one common user snapshot, which ensures that data is not lost or random data is not being used. Embodiments disclosed herein make the search for analytical engines for user snapshots faster by providing all the required data in one common data structure. Embodiments disclosed herein uses standard plug-ins and interfaces to extract the data required to construct a user snapshot.
[0045] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

ABSTRACT
Creation of a user snapshot based on data from multiple communication means. This invention relates to user management and more particularly to creation of a user snapshot for user based on data related to the user collected from a plurality of communication devices and/or applications. The principal object of this invention is to propose a method and system configured to link multiple user communication means (communication devices and/or applications) and maintain a user snapshot, wherein the user snapshot is continuously updates and comprises of interests and patterns of the users. Another object of the invention is to propose a method and system which enables usage of the user snapshot for customized marketing targeted towards the user.
FIG. 1