Beacon-based privacy-enabling communication system for tracing of mobile device users

BEACON-BASED PRIVACY-PRESERVING COMMUNICATION SYSTEM FOR TRACING OF MOBILE DEVICE USERS

TECHNICAL FIELD

The present invention generally relates to tracking of mobile device users. More specifically, the invention relates to a beacon-based communication system with improved ability to trace mobile device users in a privacy-preserving manner. The invention also relates to an associated computerized method.

BACKGROUND

Mankind is inherently mobile. In the course of their everyday lives, most people move around to go to work or school, do shopping, use medical or cosmetic services, visit public places, socialize with family and friends, do physical exercise, enjoy performances or events in sports or culture, travel to distant places for work or pleasure, etc. The list is of course far from exhaustive.

From time to time, there may be a need to trace people’s movement in society. One example is contact tracing or disease spreading control in epidemic or pandemic times. It has been suggested in the prior art to do contact tracing by making use of people’s tendency of “always” bringing their mobile device (e.g. smartphone or smartwatch), in combination with the ability of mobile devices to communicate using short-range wireless beacon technology such as iBeacon or Bluetooth Low Energy, BLE. By intercepting beacon signals transmitted from other mobile devices nearby, it was suggested in the prior art to log the identities of such other mobile devices in local memory in the mobile device. When a situation occurs where another mobile device user is diagnosed, the user of the particular mobile device can be alerted, and the log in the mobile device could be used to trace whatever other mobile devices that the particular mobile device has encountered and evaluate the exposure risk of the user of the particular mobile device.

The present inventors have identified drawbacks and limitations with the prior art as referred to above. As a result, the present inventors have come up with an improved communication system and associated computerized method for tracing mobile device users in a privacy-preserving manner.

CF 054 SE

SUMMARY

It is accordingly an object of the invention to offer an improved beacon-based communication system and associated computerized method with improved ability to trace mobile device users in a privacy-preserving manner.

A first aspect of the present invention is a communication system as defined in the appended independent claim 1.

A second aspect of the present invention is a communication system as defined in the appended independent claim 2.

Some embodiments of these aspects are defined in the dependent claims 3-14.

A third aspect of the present invention is a computerized method as defined in the appended independent claim 15. The computerized method may comprise any or all of the functional features of the first or second aspects of the invention, or their embodiments as described in this document.

Other aspects, objectives, features and advantages of the disclosed embodiments will appear from the following detailed disclosure, from the attached dependent claims as well as from the drawings. Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein.

All references to a/an/the [element, device, component, means, step, etc] are to be interpreted openly as referring to at least one instance of the element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF DRAWINGS

Fig 1A illustrates a first embodiment of a communication system and associated computerized method according to the present invention.

Fig fB illustrates a second embodiment of a communication system and associated computerized method according to the present invention.

Fig 2A illustrates a third embodiment of a communication system and associated method according to the present invention.

Fig 2B illustrates a fourth embodiment of a communication system and associated method according to the present invention.

Fig 3 illustrates a mobile communication device according to embodiments of the present invention.

CF 054 SE

DETAILED DESCRIPTION

The disclosed embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

It is recalled that Fig 1A illustrates a first embodiment of a communication system and associated method according to the present invention. The communication system comprises a particular mobile device 10, embodiments of which are shown in more detail in Fig 3. The mobile device 10 has a short-range wireless communication interface 72 and a broadband communication interface 74. The communication system of the first embodiment further comprises a cloud-based data aggregation function 30. The mobile device 10 may, for instance, be a mobile phone, a smart phone, a tablet computer, a personal digital assistant, a portable computer, smart glasses, a smart watch, or a smart bracelet.

The mobile device 10 is configured for storing a cryptographic encryption key and a cryptographic decryption key. This can be seen at f02 in Fig fA. The cryptographic encryption key and the cryptographic decryption key may, for instance, be first and second cryptographic keys of a key pair for asymmetric encryption and decryption, wherein the cryptographic encryption key/first key in the pair may be a public key and the cryptographic decryption key/second key in the pair may be a private key. Alternatively, the cryptographic encryption key and the cryptographic decryption key may be one and the same single key for symmetric encryption and decryption. Hence, in this case, there is just one actual key which however plays two roles - as cryptographic encryption key and as cryptographic decryption key.

The cryptographic encryption and decryption keys (i.e. the key pair for asymmetric encryption and decryption or the single key for symmetric encryption and decryption, as the case may be) may be generated by software in the mobile device, and/or by downloading from a third-party service, as is known per se.

As can be seen in Fig 1A, as the mobile device 10 is carried around by a user who moves to different positions or locations, the mobile device 10 is configured for doing the following repeatedly:

CF 054 SE • receiving 108, 128, by the short-range wireless communication interface 72, a short-range wireless beacon signal from another mobile device 12, 14 when the devices are proximate to each other at a current position or location, • producing 110, 130 a data entry that at least comprises information from the short-range wireless beacon signal that identifies the other mobile device 12, 14 or a user thereof, • encrypting 112, 132 the data entry with the cryptographic encryption key (i.e. the public key in the key pair for asymmetric encryption and decryption, or the single key for symmetric encryption and decryption), and • transmitting 114, 134, by the broadband communication interface 74, the encrypted data entry to the cloud-based data aggregation function 30 over a wide-area communication network 20.

Hence, when a first other mobile device 12 is in proximity of the mobile device 10, the mobile device 10 can receive 108 a beacon signal transmitted by the first other mobile device 12 at 106, produce the encrypted data entry at 110-112 and transmit the encrypted data entry to the cloud-based data aggregation function 30 at 114. Correspondingly, when a second other mobile device 14 is in proximity of the mobile device 10, the mobile device 10 can receive 128 a beacon signal transmitted by the second other mobile device 14 at 126, produce the encrypted data entry at 130-132 and transmit the encrypted data entry to the cloud-based data aggregation function 30 at 134.

In reality, the steps 106-114 and 126-134 are repeated a large number of times for respective other mobile devices that the mobile device 10 may come across.

The other mobile devices 12, 14 may, for instance, be of any of the types exemplified above for the mobile device 10.

The beacon signal may generally be of any kind of signals used for proximity detection or short-range wireless communication. One example is the iBeacon technology from Apple, or more generally the Bluetooth Low Energy, BLE, standard, wherein the beacon signals are based on Generic Access Profile, GAP, advertising packets. Other examples are, for instance, AltBeacon, URIBeacon and Eddystone, without limitation.

The information from the short-range wireless beacon signal that identifies the other mobile device 12, 14 or a user thereof and that is included in the data entry produced by the mobile device 10 may hence comprise an identifier of the mobile device 12, 14 or its user. In some embodiments, the identifier may be a tokenized identifier, as will be understood by the skilled person.

CF 054 SE

In some embodiments, the mobile device 10 is configured for producing 110, 130 the data entry by including also information about a received signal strength for the received short-range wireless beacon signal from the other mobile device 12, 14. Such information about received signal strength may, for instance, be a Received Signal Strength Indication, RSSI, value. This may allow a more accurate determination of the distance between the receiving mobile device 10 and the transmitting device 12, 14 and hence a more sophisticated use of the data entry at a later stage (also see further below).

In some embodiments, the mobile device 10 is configured for producing 110, 130 the data entry by including also personal data about the user of the mobile device 10. Again, this may allow a more sophisticated use of the data entry at a later stage. The personal data about the user of the mobile device 10 may, for instance, include one or more of the following:

data that defines geographic locations visited by the mobile device 10;

a current date;

a current date and time;

data that defines an identity of the user of the mobile device 10;

data that defines an identity of the mobile device 10;

medical health data pertaining to the user of the mobile device 10; physical exercise data pertaining to the user of the mobile device 10; data about calendar events in the mobile device 10;

data about diary entries made by the user of the mobile device 10;

data that defines notes made by the user of the mobile device 10; and financial data pertaining to the user of the mobile device 10.

Including the current date and time is believed to be particularly beneficial in some embodiments of the invention. For instance, it may assist in determining a duration of the mobile device’s 10 (or its user’s) stay at a current position or location, and/or a duration of the mobile device’s 10 (or its user’s) exposure to another mobile device (user). It may also assist in co-locating data entries for the mobile device 10 and data entries for another device; these data entries will in effect share an association from the fact that they both indicate the same or essentially the same date and time.

As can also be seen in Fig 1 A, the cloud-based data aggregation function 30 is configured for repeatedly:

• receiving 116, 136 the encrypted data entry from the mobile device 10, and

CF 054 SE • storing 118, 138 the received encrypted data entry as aggregated encrypted data together with other encrypted data entries previously received from the mobile device 10.

Hence, when the first other mobile device 12 is in proximity of the mobile device 10, the cloud-based data aggregation function 30 will receive at 116 the encrypted data entry that has been transmitted from the mobile device 10 at 114, and store it among the aggregated encrypted data at 118, thereby recording the mobile device’s 10 encounter with the first other mobile device 12. Correspondingly, when the second other mobile device 14 is in proximity of the mobile device 10, the cloud-based data aggregation function 30 will receive at 136 the encrypted data entry that has been transmitted from the mobile device 10 at 134, and store it among the aggregated encrypted data at 138, thereby recording the mobile device’s 10 encounter with the second other mobile device 14.

As can be seen further in Fig 1A, the mobile device 10 is configured for receiving 142, 142’, 142” an access request. The access request can be generated by the cloud-based data aggregation function 30 itself, or by another cloud-based function 50, as can be seen in Fig 1 A. Alternatively, the access request may be generated locally in the mobile device 10 by the user thereof or by software executing in the mobile device 10.

In response to receiving 142, 142’, 142” the access request, the mobile device 10 is further configured for making the cryptographic decryption key available to allow decryption 144, 146 of the aggregated encrypted data of the mobile device 10, as stored by the cloud-based data aggregation function 30. This may typically involve the mobile device 10 releasing the cryptographic decryption key to the requesting entity (e.g. the cloud-based data aggregation function 30 itself, or the other cloud-based function 50), i.e. uploading the cryptographic decryption key via the wide area network 20. Alternatively, it may involve downloading the aggregated encrypted data to the mobile device 10 to do the data decryption locally.

The decrypted data may then be delivered to the requesting entity, i.e. the cloud-based data aggregation function 30, the other cloud-based function 50 or the mobile device 10 itself, as the case may be. This is seen at 148-150’ in Fig 1A.

The receiving entity may then process the decrypted data, as can be seen at 150, 150’ and 150” in Fig 1A. The processing may, for instance, be used for contact tracing or disease spreading control, which may be particularly beneficial in epidemic or pandemic times. Hence, the invention may be used as a tool to help assessing a risk of

CF 054 SE exposure for the individual user of the mobile device to a severe disease. The invention may however also be used as a tool for the public health authorities to map a general population of citizens in terms of geographic location, movement pattern, disease spreading patterns, etc. This is so, since not only the mobile device 10 may be operative to collect and store aggregated proximity data from interception of beacon signals from other mobile devices, but other mobile devices (e.g. devices 12, 14) may operate in the corresponding manner.

Another possible use is for locating missing people. Being able to trace how the user of the mobile device 10 has moved and what locations he or she has visited, and/or what people he or she has come across, may help in assessing current likely locations of the user.

Similarly, the invention may be used in criminal investigation, for instance as a tool for the user of the mobile device 10 to prove his or her innocence to a criminal charge by presenting evidence of his or her whereabouts (and, conversely, where he or she has not been).

Yet other possible beneficial uses of the present invention include medical analysis, physical exercise analysis, and verification of a person’s whereabouts.

These examples are non-exhaustive, as the skilled person will understand after having read the present description of the invention.

Hence, the invention and the embodiments thereof provide improvements over the prior art in the ability to trace mobile device users in a privacy-preserving and yet flexible manner. Many different possible uses are enabled thanks to the invention. Privacy will be preserved since the mobile device user is still in control of the cryptographic decryption key and therefore also in control of the decryption of the aggregated data. A multitude of beneficial uses cases are made available, subject to the user’s approval of decryption (i.e. making the cryptographic decryption key available). Privacy will even be improved, since the obtained proximity data (the aforementioned data entries) are not stored in the mobile device 10 but instead aggregated at the cloudbased aggregation function 30, for which vastly more sophisticated data protection measures may be taken than for an individual mobile device.

Other advantages of not storing aggregated proximity data in the mobile device include efficiency of resource usage (e.g. local memory capacity and local processing power), and data redundancy (if the aggregated proximity data were to be stored in the mobile device like in the prior art, the risk of data losses would be imminent if the mobile device was stolen, lost or destroyed).

CF 054 SE

Fig 2A illustrates a third embodiment which can be seen as an implementation example of the first embodiment described in Fig 1 A.

A second embodiment of the invention is illustrated in Fig IB. The second embodiment generally has the same advantages as the first embodiment, and elements in Fig IB which have the same reference numerals as elements in Fig 1A have the same or essentially the same structure and function as in Fig 1 A.

The main difference is that in the embodiment of Fig IB, a cloud-based escrow service function 40 has been added. The cloud-based escrow service function 40 is configured for storing 104 the cryptographic decryption key, which is therefore not stored in the mobile device 10 like it was in the first embodiment of Fig fA. The mobile device 10 still stores the cryptographic encryption key, like in the first embodiment of Fig fA.

In the embodiment of Fig IB, the mobile device 10 may be configured for uploading 102 the cryptographic decryption key to the cloud-based escrow service function 40.

Just like for Fig 1 A, the cryptographic encryption key and the cryptographic decryption key may, for instance, be first and second cryptographic keys of a key pair for asymmetric encryption and decryption, wherein the cryptographic encryption key/first key in the pair may be a public key and the cryptographic decryption key/second key in the pair may be a private key.

Alternatively, the cryptographic encryption key and the cryptographic decryption key may be one and the same single key for symmetric encryption and decryption. In this case, the mobile device 10 in the embodiment of Fig IB may beneficially be configured for storing a cryptographic signing key in addition to the key for symmetric encryption and decryption. This can be seen in Fig 3. The mobile device 10 may be configured for signing the key for symmetric encryption and decryption with the cryptographic signing key, and for uploading 102 the signed key for symmetric encryption and decryption to the cloud-based escrow service function 40.

Having a signed key for symmetric encryption and decryption will allow subsequent verification of the signed key for symmetric encryption and decryption when later being retrieved in conjunction with an access request. To this end, the cryptographic signing key may be a private key in a pair of keys for asymmetric encryption and decryption, and the subsequent verification of the signed key for symmetric encryption and decryption may be made by means of a corresponding public key in such a pair of keys for asymmetric encryption and decryption.

CF 054 SE

In Fig IB, the functionality in steps 106-138 is the same or essentially the same as in Fig 1 A.

In Fig IB, the access request is directed at the cloud-based escrow service function 40, as can be seen at 140, 140’ or 143 in Fig IB. To this end, the cloud-based escrow service function 40 is configured for • receiving 142, 142’, 142” an access request pertaining to the mobile device 10 or its user, and • in response making the cryptographic decryption key available to allow decryption 144, 146 of the aggregated encrypted data of the mobile device 10, as stored by the cloud-based data aggregation function 30.

For instance, the cloud-based escrow service function 40 may be configured to make the cryptographic decryption key available to allow decryption 144, 146 of the aggregated encrypted data by releasing the cryptographic decryption key to the cloudbased data aggregation function 30. The cloud-based data aggregation function 30 will then be configured for decrypting 146 the aggregated encrypted data by using the cryptographic decryption key released by the cloud-based escrow service function 40.

Alternatively, the cloud-based data aggregation function 30 may be configured for uploading the aggregated encrypted data to the cloud-based escrow service function 40. The cloud-based escrow service function 40 will then be configured for decrypting the aggregated encrypted data provided by the cloud-based data aggregation function 30 by using the stored cryptographic decryption key, and for delivering 148’ the decrypted data to the cloud-based data aggregation function 30.

Advantageously, the mobile device 10 is configured for transmitting 143, by the broadband communication interface 74, a confirmation to the cloud-based escrow service function 40 over the wide-area communication network 20. In such a case, the cloud-based escrow service function 40 is configured for making the cryptographic decryption key available to allow decryption 144, 146 of the aggregated encrypted data conditionally upon having received the confirmation from the mobile device 10. Hence, the user is given the ability to consent to the decryption 144, 146 of the aggregated encrypted data, which has a clear benefit in privacy preservation.

Another advantage of the second embodiment of Fig IB is that the aggregated data kept by the cloud-based data aggregation function 30 can be retrieved and decrypted even if the user is no longer in possession of the mobile device 10, or not even capable of acting anymore (he or she may even have passed away). In such cases, approval to the access to the cryptographic decryption key kept by the cloud-based

CF 054 SE escrow service function 40 may be given by the user’s next in kin, relatives, trusted friends, lawyer, the appropriate authorities, etc.

The second embodiment of Fig IB may generally be used for any or all of the same beneficial (but exemplifying) purposes as the first embodiment of Fig 1A.

Fig 2B illustrates a fourth embodiment which can be seen as an implementation example of the second embodiment described in Fig IB.

Fig 3 shows a schematic view of the general structure of a mobile communication device 100 that may implement the mobile device 10 in embodiments of the invention. The device 100 comprises a processing device or controller 70 which is responsible for the overall operation of the wireless communication device 100 and may be implemented by any commercially available CPU (Central Processing Unit), DSP (Digital Signal Processor) or any other electronic programmable logic device. The processing device 70 is configured to read instructions (software) from a memory 80 and execute these instructions to control the operation of the wireless communication device 100. The memory 80 may be implemented using any commonly known technology for computer-readable memories such as ROM, RAM, SRAM, DRAM, CMOS, FLASH, DDR, SDRAM or some other memory technology, including combinations of the above.

As can be seen in Fig 3, the memory 80 may store the aforementioned encryption key, decryption key and signing key, when applicable. Advantageously, they may be stored in or as a Secure Element. This applies in particular to the decryption key and to the signing key, for embodiments where one or both of these keys are stored locally in the mobile device 10.

The mobile communication device 100 may further comprise a user interface 60, including an input device 62 and an output device 64 (possibly jointly implemented as a touch-sensitive display), as is well known per se.

The mobile communication device 100 further comprises wireless communication means being adapted to allow the mobile communication device 100 to communicate with other devices through the use of different radio frequency technologies. More specifically, the wireless communication means comprises the aforementioned short-range wireless communication interface 72 which may, advantageously but not necessarily, be implemented as an iBeacon and/or Bluetooth Low Energy (BLE) and/or Bluetooth 4.0 compliant communication interface.

Moreover, the wireless communication means comprises the aforementioned broadband communication interface 74 for communicating with the entities 30, 50 (and

CF 054 SE possibly 50) via the wide-area communication network 20. Such communication typically occurs at a substantially higher bandwidth than the short-range wireless beacon broadcast messaging. The broadband communication interface 74 may, advantageously but not necessarily, be implemented as a communication interface compliant with IEEE 802.11, IEEE 802.15, ZigBee, WirelessHART, WiFi, Bluetooth®, WCDMA, HSPA, GSM, UTRAN, UMTS, and LTE, to name a few. It should be noted that, as is commonly known, the wireless communication means may be arranged to communicate according to more than one technology and many different combinations may therefore be available; for example, a smartphone is commonly arranged to communicate according to the Bluetooth® standard, the WiFi standard and the LTE standard.

The entities 30, 40 and 50 may generally be implemented by any suitable cloud-based computing resource, such as one or more server computers, or a cluster of such resources.

The invention has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.

CF 054 SE

CLAIMS