DATA SHARING USING BODY COUPLED COMMUNICATION

Abstract

Method for sharing data (SD2) between users (11,12). The method comprises initiating body coupled communication (BCC) between first and second devices (21,22) and in response to the body coupled communication (BCC), sending a data request (Q1) from one or both of the devices (21,22) to a remote server (30). The data request (Q1,Q2) comprises first device data (ID1) and the second device data (ID2). The server (30) processes the data request (Q1) and determines shared data (SD2) based at least in part on both the first device data (ID1) and the second device data (ID2). The server sends a data response (R1) to the first device (21), wherein the data response (R1) comprises the shared data (SD2).

Claims

1. A method for sharing data, the method comprising: providing a first body coupled communication device for storing a first device data; providing a second body coupled communication device for storing a second device data; initiating a body coupled communication between the first and second devices; in response to the body coupled communication, sending a data request from one or both of the devices to a remote server, wherein the data request comprises the first device data and the second device data; processing the data request and determining a to-be-shared data based at least in part on both the first device data and the second device data; sending a data response from the remote server to the first device, wherein the data response comprises the to-be-shared data.

2. The method according to claim 1, wherein the first device data comprises a first identifier and the second device data comprises a second identifier; and wherein the processing of the data request by the remote server comprises: determining a data record associated with the second identifier; determining access rights associated with the first identifier; and determining a to-be-shared part of the data record based on the access rights; compiling the data response to the first device based on the to-be-shared part of the data record.

3. The method according to claim 1, wherein the second device sends the second device data via the body coupled communication to the first device, wherein the first device sends the data request to the remote server comprising device data of both the first and second devices.

4. The method according to claim 1, wherein each device sends a respective data request comprising at least the device data of the respective device.

5. The method according to claim 1, further comprising sending a second data response from the remote server to the second device, wherein the second data response comprises the to-be-shared data.

6. The method according to claim 1, wherein the processing of the data request by the remote server comprises: accessing a first data record associated with the first device data; accessing a second data record associated with the second device data; determining a to-be-shared part of the second data record based on a comparison between the first data record and the second data record; compiling the data response to the first device based on the to-be-shared part of the second data record.

7. The method according to claim 1, wherein the second device data sent from the second device to the remote server comprises a data record, and wherein the remote server determines a part of the data record to be shared based on the first device data.

8. The method according to claim 1, wherein the second device sends an encrypted data record via the body coupled communication to the first device, and wherein the data response sent from the remote server to the first device comprises a decryption key for decrypting the encrypted data record.

9. The method according to claim 1, wherein the second device transfers a data record via the body coupled communication to the first device in response to receiving the data response of the remote server.

10. The method according to claim 1, wherein the remote server provides the first device access to a data record for a specific window following reception of the data request while the first device is in proximity to a location device.

11. The method according to claim 1, wherein the remote server provides the first device access to a data record until the second device sends a message to the remote server revoking the access.

12. The method according to claim 1, wherein the second device sends the second device data in response to a confirmation entered on the second device.

13. A body-coupled communication device, comprising: a coupler arrangement configured to couple a signal between a first body-coupled communication device and a human body for performing a coupled communication via the body with a second body-coupled communication device; a transceiver configured to transmit and receive data to and from a remote server independent of the coupler arrangement; and a controller configured to: listen for the body coupled communication from the second device via the coupler arrangement; in response to the body coupled communication, transmit a data request to a remote server via the transceiver; and after sending the data request, listen for a data response from the remote server via the transceiver.

14. The communication device according to claim 13, wherein the device comprises a memory for storing first device data; and the controller is configured to receive second device data from the second device via the coupler arrangement, and transmit the data request comprising the first device data and the second device data to the remote server via the transceiver.

15. A computer server comprising a transceiver, a controller, and a memory for storing program instructions that when executed by the controller cause the controller to: control the transceiver to listen for one or more data request from a first and second device, wherein the one or more data requests comprises a first identifier and a second identifier; in response to receiving the one or more data requests, process the data requests to determine the first and second identifiers and determine a to-be-shared data based at least in part on both the first device data and the second device data; send a data response too the first device, wherein the data response comprises the to-be-shard data.

16. A non-transitory computer-readable medium having one or more executable instructions stored thereon, which when executed by a processor, cause the processor to perform a method for sharing data, the method comprising: providing a first body coupled communication device for storing a first device data; providing a second body coupled communication device for storing a second device data; initiating a body coupled communication between the first and second devices; in response to the body coupled communication, sending a data request from one or both of the devices to a remote server, wherein the data request comprises the first device data and the second device data; processing the data request and determining a to-be-shared data based at least in part on both the first device data and the second device data; sending a data response from the remote server to the first device, wherein the data response comprises the to-be-shared data.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] These and other features, aspects, and advantages of the apparatus, systems and methods of the present disclosure will become better understood from the following description, appended claims, and accompanying drawing wherein:

[0017] FIGS. 1A-1D illustrate a first embodiment of a method for data sharing between users;

[0018] FIGS. 2A-2D illustrate a second embodiment of a method for data sharing between users;

[0019] FIG. 3A illustrate a first embodiment for determining data sharing between users;

[0020] FIG. 3B illustrate a second embodiment for determining data sharing between users;

[0021] FIG. 4 illustrate an embodiment of a body-coupled communication device;

[0022] FIG. 5 illustrates an embodiment of a remote server.

DETAILED DESCRIPTION OF EMBODIMENTS

[0023] The present disclosure relates to body coupled communication (BCC) which allows data signals to travel via the capacitive field around the human body. This can improve the usability and intuitiveness of use cases and interacting with objects in situations. With BCC the user is able to touch an object or other users, while holding a mobile device or wearing a smart watch, and then start a direct data comparison to come up e.g. with recommendations or share specific data subsets. The system identifies the users or object, but does not need to disclose the data to those users or object to improve privacy.

[0024] Conventionally, it can sometimes be quite cumbersome e.g. to come up with a single multimedia playlist for multiple persons, or compare & grant access to multiple data sets (e.g. medical data) that are stored on local devices or in the cloud. The present disclosure provides an ad-hoc way to make this process more intuitive and very easy to use. It makes use of the principle that the BCC signal can travel through people, devices and objects—and a system that compares data real-time. The disclosure may further provide a way to compare local, or remote, data sets by making a physical connection between two or more users or objects. This improves security, and provides a way to compare these data sets without disclosing any data to the users.

[0025] Some embodiments may include one or more of the following aspects. Body coupled communication connection is established between two or more people (e.g. via touching, holding each other's hands). Each person has a device (e.g. mobile phone or wrist-based device) enabled with body coupled communication for this purpose. When the connection is established between the groups of people/objects an action is performed by sending specific data (based on use case) to a central server/system. A central system (server) compares the incoming datasets to see what is relevant and overlaps, and uses specific algorithms (based on use case) to provide specific recommendations for both users. The incoming datasets may include data from the cloud (e.g. unlocked via ID) or uploaded via the device(s). The central system sends the feedback (based on use case) to the user's smart devices by only disclosing the feedback, and NOT the data that was collected or used to come up with the, e.g., recommendation. This improves data security and privacy.

[0026] In some embodiments, two or more users may be identified through using body coupled communication (BCC). The personal data from each device may be compared or used without disclosing the full dataset or privacy sensitive data to the other users. The service could compare personal data such as multimedia, contacts, location or message and come up with useful suggestions like specific preferences, shared contacts or recommendations without disclosing the actual data. This helps the user to protect their privacy. In some embodiment the body coupled device may be a smart device (e.g. a smartphone or wearable) that has a BCC module and is in close proximity of the user's body; the user is able to communicate with other BCC modules embedded in other personal devices or BCC objects.

[0027] In one embodiment, the process is initiated by first activating one of the BCC devices into listening mode. Now the other devices can be discovered through body touch (e.g. shaking hands), over the body coupled communication channel. After this the data set of each device is used at the server-side to perform a comparison (e.g. compare their personal data such as multimedia, contacts, location and messages) or execute another algorithm (e.g. creating recommendations based on the data of the users). Either this data is uploaded for this purpose from each device, or is already stored in the cloud and is made accessible to the server for this purpose. After the execution of the server request, the results are send back to each device.

[0028] According to one embodiment, a process flow can be as follows. First, the process is initiated by activating one BCC device in listening mode. Then, other device(s) are discovered via the body communication channel. Then a server request is executed with a dataset of each device. Then, results are sent back to each device.

[0029] The invention is described more fully hereinafter with reference to the accompanying drawings. In the description and drawings, like numbers refer to like elements throughout. Relative terms (e.g. horizontal, vertical) as well as derivatives thereof should be construed to refer to the orientation as then described or as shown in the drawing under discussion. It will be understood that when an (electrical) connection between structures or components is described, this connection may be established directly or through intermediate structures or components unless specified otherwise.

[0030] FIGS. 1A-1D illustrate a first embodiment of a method for sharing data SD2 between users 11,12,

[0031] With reference to FIG. 1A, the embodiment of the method comprises providing a first device 21 and a second device 22. The first device 21 stores first device data ID1 associated with a first user 11. The second device 22 stored second device data ID2 associated with a second user 22. Both devices 21, 22 are capable of body coupled communication BCC. The method further comprises performing body coupled communication BCC between the first and second devices 21,22, e.g. via the bodies of the first and second users 11,12. In one embodiment, the first device data comprises a first identifier ID1 associated with a first user 11. In another or further embodiment, the second device data comprises a second identifier ID2 associated with a second user 12. Alternatively or in addition, the device data ID1 and/or ID2 may also comprise further user data, including data to be shared with the other user.

[0032] With reference to FIG. 1B, the embodiment of the method comprises in response to the body coupled communication BCC, sending a data request Q1 to a remote server 30. In the embodiment shown, the second device 22 may have sent the second device data ID2 via body coupled communication BCC to the first device 21. Accordingly the first device 21 may send the data request Q1 to the remote server 30 comprising device data ID1,ID2 of both the first and second devices 21,22.

[0033] With reference to FIG. 1C, the embodiment of the method comprises processing the data request Q1 at the remote server 30 and determining data to be shared SD2 based. Which data to share may be determined by the remote server 30 based on the first device data ID1 and the second device data ID2.

[0034] With reference to FIG. 1D, the embodiment of the method comprises sending a data response R1 from the remote server 30 to the first device 21. For example, the data response R1 comprises the shared data SD2.

[0035] In one embodiment, the second device 22 sends an encrypted data record via body coupled communication BCC to the first device 21. In another or further embodiment the data response R1 sent from the remote server 30 to the first device 21 comprises a decryption key for decrypting the encrypted data record.

[0036] In one embodiment, the second device 22 transfers a data record via body coupled communication BCC to the first device 21 in response to receiving the data response R1 of the remote server 30. In one embodiment, the remote server 30 provides the first device 21 access to a data record AD2 for a specific time period (window) following reception of the data request Q1 or following the BCC communication. In one embodiment, the remote server 30 provides the first device 21 access to a data record AD2 while the device 21 is in proximity to a specific location or device. For example, the data access can be cancelled when the first device 21 leaves the proximity of the second device 22 or a separate location indicator, e.g. WIFI network. The proximity may also be determined in relation to an absolute, e.g. GPS location. Also combinations are possible. In one embodiment, the remote server 30 provides the first device 21 access to a data record AD2 until the second device 22 sends a message to the remote server 30 revoking the access. In one embodiment, the second device 22 sends the second device data ID2 in response to a confirmation entered on the second device 22. In one embodiment, the confirmation comprises entering a security identification of the user 12, e.g. biometric and/or pin code.

[0037] FIGS. 2A-2D illustrate a second embodiment of a method for data sharing between users. The method is similar to the first embodiment, except, as shown in FIG. 2B, each device 21,22 sends a respective data request Q1,Q2 comprising at least the device data ID1,ID2 of the respective device 21,22. Accordingly, it is not necessary to share specific device ID1,ID2 data with the other device before sending the data requests.

[0038] In one embodiment, as shown in FIG. 2D, the method further comprises sending a second data response R2 from the remote server 30 to the second device 22. The second data response R2 comprises shared data SD1 which may be the same as the shared data SD2 sent to the first device 21, i.e. each device receives the same shared data. Alternatively, each device receives a response with different shared data, e.g. based on the data of the other user.

[0039] One example scenario may include comparing and matching social network contacts. For example two people meet each other during a business meeting and shake hands for the first time (FIG. 2A). Their personal smart devices, equipped with ADA, make a connection via the user's body. This connection is part of a central system that collects and accesses the users' data that is stored on the personal devices (FIG. 2B). The central system uses an algorithms to determine what contacts the users have in common or are interesting to share. This could be contacts that are stored locally in the address book of the device, but also social platforms such as LinkedIn or Facebook (FIG. 2C). The server sends a message to the users' smart devices with a list of friends/contacts that they have in common without disclosing all other contacts/friends to the other user (FIG. 2D).

[0040] Another example scenario may include music recommendations. For example two or more people would like to get a recommendation on a music playlist with music that they all have in common and can enjoy together. By holding hands and touching the audio system at the same time, a connection will be established between all personal devices (e.g. smartphone) and the sound system. This connection makes it possible for the system to determine the user's music preferences based on the music that is stored on these devices, or the music/playlists that are stored on (3rd party) services such as Spotify or Pandora. By using an algorithm the system should be able to determine what music the users have in common, and what genre would be suitable for the current situation. It interprets the data, and returns a list of songs to the audio system without disclosing any specific music titles or artists that are not relevant. The audio system receives the playlist and starts playing the music. The recommendation may also include recommendations of new or other music that is unknown to both people, but fits the combined musical taste, e.g. based on genre, artist, or other metadata of the multimedia collections.

[0041] Yet another example scenario may include safe health data sharing. For example, a patient has collected medical data using a health bracelet or other wearable health sensors. This data is stored in the cloud on a server. By touching with his or her hand an ADA device (e.g. tablet) of a medical doctor, a connection will be established between the patients' health device and the doctors' tablet. The identification of the user, coming from the bracelet via ADA, will be send to the ADA device (e.g. tablet) of the doctor. From a central server a subset of the medical health data is send to the ADA device (e.g. tablet) of the medical doctor. At the server the access rights of the medical doctor are checked to see if s/he is allowed to see the data of the patient and which part of the data is made accessible.

[0042] These and other scenarios can be extended with personal data encryption keys that are sent by both devices to be used to encrypt data for the purpose of the one-time access rights. One technique for this is using public-key cryptography, wherein one key is secret (or private) and one is public.

[0043] FIG. 3A illustrate a first embodiment for determining data sharing between users. In the embodiment, the processing of the data request Q1 comprises determining a data record AD2 of the second user associated with a second identifier ID2 and determining access rights of the first user 11 associated with a first identifier ID1. The data record can e.g. located on the remote server 30 processing the request, or another server. A shared part SD2 of the data record AD2 of the second user 12 is based on the access rights of the first user 11. The remote server may compile the data response R1 to the first device 21 based on the shared part SD2 of the data record AD2.

[0044] For example, the first user with associated identifier ID1 is a doctor and the second user with associated identifier ID2 is a patient. The data record AD2 may comprises a record of all stored information concerning the patient, e.g. including non-medical data. The doctor may access part SD2 of the patient information based on his access rights, e.g. only relevant medical data for the doctor is shared.

[0045] In one embodiment, the second device data ID2 (sent from the second device 22 to the remote server 30) comprises a data record AD2. In another or further embodiment, the remote server 30 determines a part SD2 of the data record AD2 to be shared with the first user 11 based on the first device data ID1, e.g. an identifier associated with the first user. Accordingly it is noted that the device data, sent to the server, may comprise one or both of an identifier associated with a specific user or device and/or a data record of a specific user or device to be partly or fully shared with another user. When the device data only comprises an identifier, a data record may be sent by the server when it is stored or accessible to the server. Alternatively the data record may be sent directly between the devices, e.g. when it is stored on the devices. The server may then mediate which part of the data is to be shared based on the identifiers.

[0046] It may be noted that in the embodiment of FIG. 3A, a single request Q1 is sent to the server and a single response given by the server. Alternatively, multiple requests e.g. from different devices may be sent to the server and the server may provide one or multiple responses to such multiple requests. Also other combinations are possible.

[0047] FIG. 3B illustrate a second embodiment for determining data sharing between users. In the embodiment, the processing of the data request Q1 comprises accessing a first data record AD1 associated with the first device data ID1 and accessing a second data record AD2 associated with the second device data ID2. A shared part SD2 of the second data record AD2 is based on a comparison between the first data record AD1 and the second data record AD2. The remote server may compile the data response R1 to the first device 21 based on the shared part SD2 of the data record AD2. In one embodiment, the comparison is based on metadata associated with the respective data records.

[0048] In one embodiment, the first data record AD1 comprises a first collection of multimedia content and the second data record AD2 comprises a second collection of multimedia content. The data response R1 comprises an indication of recommended multimedia content SD1,SD2 based on a comparison between the first and second collections of multimedia content. For example, the recommended multimedia content may be a list of multimedia content owned by both users according to their respective data records. The recommendation may also be more general, e.g. a common genre found in both multimedia collections. In one embodiment, two devices capable of multimedia playback are coupled via BCC and a playlist is recommended by a server upon request by one or both devices.

[0049] It may be noted that in the embodiment of FIG. 3B, multiple request Q1,Q2 are sent to the server and multiple responses given by the server. Alternatively, a single request e.g. from one of the devices may be sent to the server and the server may provide one or multiple responses to such single request. Also other combinations are possible.

[0050] FIG. 4 illustrate an embodiment of a body-coupled communication device 21, e.g. for use in the methods described herein. The device 21 comprises a coupler arrangement 1, a transceiver 2, and a controller 4.

[0051] In one embodiment, the coupler arrangement 1 is configured to couple signals between the device 21 and a human body 11 for performing body coupled communication BCC via the body 11 e.g. with a second body-coupled communication device 22. The coupler arrangement may comprise signal electronics configured to generate and/or process signals sent or received by the coupler arrangement.

[0052] In one embodiment, the transceiver 2 is configured to transmit data ID1 to a remote server 30 or other device 22 and optionally receive data SD2 from the remote server 30 or the second device. The data may e.g. be sent between the devices via a local peer to peer network e.g. via Bluetooth. In one embodiment, the transceiver 2 is independent of the coupler arrangement 1, e.g. providing wired or wireless non-body coupled communication. In one embodiment, the transceiver 5 comprises an antenna to transmit and receive wireless signals, e.g. radio waves. In another embodiment, the transceiver 5 comprises a wired communication device. The transceiver may comprise a separate transmitter and receiver or be integrated in a single device. The transceiver may comprise signal electronics configured to generate and/or process signals sent or received by the transceiver

[0053] In one embodiment, the controller 4 is configured to listen for body coupled communication BCC from the second device 22 via the coupler arrangement 1. In response to the body coupled communication BCC, the controller may transmit a data request Q1 to the remote server 30 via the transceiver 2. The transmission may be initiated e.g. as soon as body coupled communication is initiated and/or after a body-coupled communication channel between the devices 21,22 is negotiated. In one embodiment, the controller listens for a data response R1 from the remote server 30 via the transceiver 2, e.g. after transmitting the data request Q1.

[0054] In one embodiment, the device comprises a memory 3 storing first device data ID1. In another or further embodiment, the controller is configured to receive second device data ID2 from the second device 22 via the coupler arrangement 1, and transmit a data request Q1 comprising the first device data ID1 and the second device data ID2 to the remote server 30 via the transceiver 2. Alternatively, the device sends a data request with only the first device data ID1. For example a second device 22 may send its respective device data ID2.

[0055] In one embodiment, the body-coupled communication is established by body contact between the first and second users 11,12. Alternatively, or in addition, the communication may be established via intermediate conducting structures. Alternatively, or in addition, the communication may be established when two users simultaneously or sequentially contact one or more device capable of body coupled communication.

[0056] FIG. 5 illustrates an embodiment of a remote server 30, e.g. for use in the methods described herein.

[0057] In one embodiment, the computer server 30 comprises a transceiver 32, a controller 34, and a memory 33. In one embodiment, the memory 33 stores program instructions that can be executed by the controller 34 to provide one or more embodiments as described herein.

[0058] In one embodiment, the controller 34 controls the transceiver 32 to listen for one or more data request Q1,Q2 from a first and/or second device 21,22. The one or more data requests Q1,Q2 comprise a first identifier ID1 associated with a first user 11 and a second identifier ID2 associated with a second user 11.

[0059] In one embodiment, the controller 34 process the data requests Q1,Q2 to determine the first and second identifiers ID1,ID2, e.g. in response to receiving the one or more data requests Q1,Q2.

[0060] In one embodiment, the controller 34 determines a data record AD2 of the second user 12 associated with the second identifier ID2. In one embodiment, the controller 34 determines access rights of the first user 11 associated with the first identifier ID1. In one embodiment, the controller 34 determines a shared part SD2 of the data record AD2 of the second user 12 based on the access rights of the first user 11.

[0061] In one embodiment, the controller 34 compiles a data response R1 based on the shared part SD2 of the data record AD2. In one embodiment, the controller 34 controls the transceiver to send a data response R1 from the remote server 30 to the first device 21.

[0062] For the purpose of clarity and a concise description, features have been described herein as part of the same or separate embodiments, however, it will be appreciated that the scope of the invention may include embodiments having combinations of all or some of the features described. For example, while embodiments were shown for methods and devices for body coupled communication also alternative ways may be envisaged by those skilled in the art having the benefit of the present disclosure for achieving a similar function and result. For example electrical components and structures may be combined or split up into one or more alternative components. While the embodiments show two body coupled devices and one server, also further BCC devices and/or servers may be added. For example, data may be shared between more than two devices or users. For example data may be stored on different servers. Servers storing data may be separate from servers determining data sharing. The various elements of the embodiments as discussed and shown offer certain advantages, such as providing intuitive yet controllable data sharing. Of course, it is to be appreciated that any one of the above embodiments or processes may be combined with one or more other embodiments or processes to provide even further improvements in finding and matching designs and advantages. It is appreciated that this disclosure offers particular advantages to data sharing by body coupled communication, and in general can be applied for any application wherein body coupled communication is used to initiate data access via a remote server.

[0063] In interpreting the appended claims, it should be understood that the word “comprising” does not exclude the presence of other elements or acts than those listed in a given claim; the word “a” or “an” preceding an element does not exclude the presence of a plurality of such elements; any reference signs in the claims do not limit their scope; several “means” may be represented by the same or different item(s) or implemented structure or function; any of the disclosed devices or portions thereof may be combined together or separated into further portions unless specifically stated otherwise. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to advantage. In particular, all working combinations of the claims are considered inherently disclosed.