METHOD FOR SHARING POSITION DATA BETWEEN A USER'S SOURCE DEVICE AND A THIRD PARK'S DESTINATION DEVICE, CORRESPONDING SERVER, THIRD PARK'S DESTINATION DEVICE AND COMPUTER PROGRAM

Description

1. Field of the invention

[0001] The field of invention is that of geolocation.

[0002] More specifically, the present invention provides a solution for sharing location data, in particular allowing a third party recipient device, authorized by a user's source device, to access the location data of the user's source device.

[0003] For example, the user's source device is a connected watch, communicating with a third-party recipient device such as a smartphone implementing an application dedicated to sharing location data.

[0004] The present invention finds applications in particular in all fields requiring the geolocation of an individual, for example in the field of sport. 2. Prior art

[0005] In the sports field, it is known to use watches equipped with a geolocation module. Such watches allow the user's position and the time taken to complete their route to be determined, and are therefore used by athletes to understand, and potentially improve, their performance.

[0006] One drawback of these watches is that they do not allow location sharing with third parties. Therefore, during a marathon, for example, the runner's family cannot track the runner's location in real time.

[0007] There is therefore a need for a new solution for sharing location data that does not have this drawback of the prior art.

[0008] Document US 2010 / 0325194 describes a method for sharing location data from a user's terminal with another user's terminal. 3. Statement of the invention

[0009] An object of the present invention is to provide a solution for sharing location data allowing third parties authorized by the user to access the user's location data.

[0010] Another object of the present invention is to propose a solution allowing the user to temporarily authorize third parties to access his geolocation information.

[0011] Yet another object of the present invention is to provide a solution for temporary storage of location data. According to a first aspect, there is provided a method for managing location data sharing according to claim 1.

[0012] Such a method according to this embodiment, implemented in a server remote from the user's source device and the third party's recipient device, makes it possible to manage the access authorizations to the location data of the user's source device.

[0013] For example, the user of the user's source device can select, from their contacts, those they authorize to access their location data. Similarly, the user of the user's source device can select, from their contacts, those they do not authorize, or no longer authorize, to access their location data. For each of the selected contacts, a first identifier of the recipient device of the third party associated with this contact, such as their telephone number, is transmitted to the server, which can thus manage a correspondence table between a first identifier of the user's source device and the first identifier of the recipient device of the third party associated with each selected contact.In particular, the server may add or remove from the correspondence table the first identifier of the third party's recipient device, depending on whether or not it is authorized by the user of the user's source device to access its location data.

[0014] The method according to this embodiment therefore allows the user of the user's source device to temporarily authorize users of the recipient devices to access his geolocation information.

[0015] When the third party's recipient device wishes to access the location data of the user's source device, it sends a request for transmission of location data of the user's source device to the server, with a second identifier of the user's source device, corresponding to the first identifier of the user's source device, and a second identifier of the third party's recipient device. If the first identifier and second identifier of the third party's recipient device match (for example, are identical or correlated), and therefore the first identifier of the third party's recipient device is associated with the first identifier of the user's source device in the correspondence table, the server can transmit the location data of the user's source device to the third party's recipient device.

[0016] For example, the first and second identifiers of the user's source device are a telephone number associated with the user's source device, and the first and second identifiers of the third party's recipient device are a telephone number associated with the third party's recipient device. According to a particular embodiment, the management method also comprises receiving a validity period applicable to the location data of the user's source device.

[0017] Such a validity period makes it possible in particular to define a storage time for the location data of the user's source device on the server.

[0018] For example, the management process includes: the activation of a timer having a value equal to the validity period, the storage in memory of the location data of the user's source device intended to be transmitted to the third party's destination device during the timer, the deletion of the stored location data after expiry of the timer.

[0019] In this example, the location data of the user's source device may be temporarily stored on the server, for a time defined by the validity period, and then deleted from the server.

[0020] This ensures that the location data from the user's source device is not stored and then used for unintended or unauthorized purposes. In other words, no location data history is retained.

[0021] According to another aspect, there is provided a location data sharing management server according to claim 4.

[0022] Such a server is particularly suitable for implementing the location data sharing management method described above.

[0023] This server may of course include the various characteristics relating to the proposed management method, which may be combined or taken in isolation. Thus, the characteristics and advantages of this server are the same as those of the management method.

[0024] Such a server is particularly suitable for exchanging data with the user's source device and the third party's destination device.

[0025] For example, such a server is operated by a telecommunications operator, the processor being configured to communicate with the source and destination devices by transmitting / receiving data in the operator's network.

[0026] According to a second aspect, there is provided a method of sharing location data according to claim 7.

[0027] Such a method according to this embodiment also makes it possible to manage the access authorizations to the location data of the user's source device. In particular, it makes it possible to define the recipient devices authorized or not to access the location data of the user's source device, and to inform the server and the recipient devices accordingly.

[0028] Such a sharing method is advantageously well suited for exchanging data with a remote server implementing the location data sharing management method described above.

[0029] This sharing process may of course include the various characteristics relating to the proposed management process, which may be combined or taken in isolation. Thus, the characteristics and advantages of this sharing process are the same as those of the management process.

[0030] According to a particular embodiment, the sharing method also comprises the transmission, to the remote server, of a validity period applicable to the location data of the user's source device.

[0031] As previously indicated, such a validity period makes it possible in particular to define a storage time for the location data of the user's source device on the server.

[0032] In particular, the validity period may be pre-configured and stored in a memory of the user's source device. For example, such information may be entered by the user of the user's source device, via a user interface.

[0033] According to a particular embodiment, the access information message (transmitted from the user's source device to the third party's recipient device) comprises a dynamic link, configured to open a dedicated application if it is installed on the third party's recipient device or to offer the third party's recipient device the option of downloading the dedicated application otherwise.

[0034] This simplifies the implementation of location data sharing between users.

[0035] According to a particular embodiment, the access information message and the authorization message indicate that the third party's recipient device is authorized to obtain location data from the user's source device, or, conversely, that the third party's recipient device is not authorized to obtain location data from the user's source device.

[0036] According to another aspect, there is provided a system according to claim 8.

[0037] The system comprises a user source device which is particularly suitable for implementing the location data sharing method described above.

[0038] This user source device may of course include the various characteristics relating to the proposed sharing method, which may be combined or taken in isolation. Thus, the characteristics and advantages of this device are the same as those of the sharing method.

[0039] For example, such a device is a watch, further comprising: a geolocation module, a communication module.

[0040] Such a watch thus has means of communication, for example cellular, allowing it to communicate with the remote server and with recipient devices.

[0041] According to a third aspect, there is provided a method of accessing location data of a source device of a user according to claim 5.

[0042] In particular, the second user source device identifier corresponds to the first user source device identifier transmitted by the user source device to the server.

[0043] Such a method according to this embodiment allows a recipient device of the third party to access the location data of the source device of the user, if authorized.

[0044] In particular, it allows requests to be sent to the server to receive the location data of the user's source device. For example, at each request, or periodically, the server checks whether the third party's recipient device is authorized to access the location data of the user's source device. If so, the server transmits the location data of the user's source device to it.

[0045] This access method may of course include the various characteristics relating to the proposed management and sharing methods, which may be combined or taken in isolation. Thus, the characteristics and advantages of this access method are the same as those of the management and sharing methods.

[0046] According to another aspect, there is provided a third party recipient device according to claim 6.

[0047] Such a third-party recipient device is particularly suitable for implementing the method of accessing location data described above.

[0048] This user source device may of course include the various characteristics relating to the proposed access method, which may be combined or taken in isolation. Thus, the characteristics and advantages of this device are the same as those of the access method.

[0049] For example, such a device is user equipment such as a personal computer, smartphone, tablet, etc., comprising a communication module configured to communicate at least with the remote server.

[0050] Such a device thus has means of communication, for example cellular, allowing it to communicate with the remote server and with the user's source device.

[0051] Another aspect relates to one or more computer programs comprising instructions for implementing a method for managing location data sharing and / or a method for sharing location data and / or a method for accessing location data as described above when this or these programs are executed by at least one processor.

[0052] According to yet another aspect, there is provided one or more non-transitory recording media readable by a computer, and comprising instructions of one or more computer programs comprising instructions for implementing a method of managing location data sharing and / or a method of sharing location data and / or a method of accessing location data as described above. 4. List of figures

[0053] Other characteristics and advantages of the invention will appear more clearly on reading the following description of a particular embodiment, given as a simple illustrative and non-limiting example, and the appended drawings, among which: there figure 1 presents the various devices proposed for sharing location data according to one embodiment; the figure 2illustrates the various methods proposed for sharing location data according to one embodiment; figures 3 to 5 respectively illustrate the simplified structure of a user source device, a third party recipient device and a server according to a particular embodiment for implementing the proposed methods. 5. Description of an embodiment

[0054] The proposed solution allows a user to share his location with authorized third parties.

[0055] According to a particular embodiment, the sharing of location data is implemented between a source device of the user and one or more recipient devices, via at least one remote server. As illustrated in figure 1 , the user's source device 11 wishes to share its location data with one or more recipient devices 12, via a remote server 13.

[0056] For example, the source device of the user 11 is a watch W1 of a user A, the recipient device of the third party 12 is a smartphone SMPH of a user B, and the server 13 is a server SER hosted by a telecommunications operator and capable of communicating with other nodes of the operator's infrastructure. The watch W1 comprises a communication module for communicating with the server SER via a programming interface (API, "Applications Programming Interface"), in particular for transmitting its location data to the server. The smartphone SMPH is adapted to implement an application dedicated to sharing location data, also called a companion application. The server SER is capable of communicating with the companion application when it is executed on the smartphone SMPH, via a programming interface (API) specific to the companion application.The SMPH smartphone thus runs a companion application for the W1 watch, which includes a user interface capable of displaying on a screen location data of the W1 watch received from the SER server.

[0057] More generally, the user's source device comprises, among other things, a geolocation module, making it possible in particular to obtain location data from the user's source device, a communication module, for example of the cellular type, making it possible in particular to transmit location data to a server and to transmit an access information message to a recipient device of the third party, a memory, making it possible for example to store identifiers of the recipient devices (contacts of the user of the user's source device), and a processor. The user's source device may in particular be equipped with a Subscriber Identity Module (SIM) unit (in the form of a SIM card, a SIM module attached to the device or integrated into it (eSIM module, embedded SIM"), typically used in mobile telephony to store subscriber-specific information on a mobile network, and thus be associated with a telephone number via the SIM unit. The geolocation module receives, for example, location data from the American satellite positioning system GPS (Global Positioning System) or the European Galileo. It can also receive or update location data from one or more sensors, for example, accelerometers or gyrometers.

[0058] Such a user source device can therefore be a connected watch, or any other type of connected geolocation beacon (animal tags, geolocation modules for bicycles, etc.).

[0059] Similarly, more generally, the third party's recipient device comprises, among other things, a communication module, for example of the cellular type, making it possible in particular to receive location data from a server and to receive an access information message from a source device of the user, a memory and a processor. The third party's recipient device may in particular be equipped with a SIM card. It is in particular configured to run the companion application dedicated to sharing location data.

[0060] Such a third-party recipient device can therefore be a smartphone, a tablet or any other connected equipment.

[0061] The following is described in relation to the figure 2, an example of implementation of the methods according to one or more embodiments. For example, it is considered that the method for sharing location data is implemented in a source device of the user of the watch type W1, that the method for managing the sharing of location data is implemented in a server SER, and that the method for accessing the location data is implemented in a recipient device of the third party of the smartphone type SMPH, as described above.

[0062] For example, we consider a list of contacts stored in a memory of the watch W1. Each contact (corresponding for example to the name of a person) is associated with a first identifier (corresponding for example to a telephone number of this person), also called the first identifier of the recipient device of the third party, or first subscriber identifier.

[0063] A first identifier of the third party's recipient device IDd1 is selected (111), from the set of recipient device identifiers stored in the watch W1, corresponding for example to the smartphone SMPH. This selection can be made by the user of the watch W1 from a user interface. In other words, the user of the watch W1 selects a contact from the contact list (or equivalently a first identifier of the third party's recipient device from the set of recipient device identifiers) to identify a person (or equivalently a third party's recipient device) to whom the user of the watch W1 wishes to open his or her geolocation, i.e. with whom the user of the watch W1 wishes to share his or her location data.

[0064] The watch W1 transmits (112), to the remote server SER: a first identifier of the watch, also called first identifier of the user's source device (IDs1), corresponding for example to a telephone number of the user of the watch (such as the telephone number associated with the SIM unit of the watch W1 in the case where the latter integrates a SIM unit as described above), the first identifier of the third party's recipient device (IDd1) and an authorization message (message A) indicating whether this third party's recipient device is authorized to obtain location data from the watch W1.

[0065] According to a particular embodiment, the authorization message carries the first identifier of the user's source device and / or the first identifier of the third party's recipient device.

[0066] The SER server therefore receives (131) from the user's source device a first identifier of the user's source device (IDs1), the first identifier of the third party's destination device (IDd1) and the authorization message (message A).

[0067] Upon receipt of this information, the server SER constructs or updates (132) a correspondence table (of the LUT type for example) associating the first identifier of the user's source device with the first identifier of the third party's recipient device. Depending on the content of the authorization message, the first identifier of the third party's recipient device may be added to the list of recipient devices authorized to receive location data from the watch W1, in the correspondence table, or deleted from the list. Alternatively, the first identifier of the third party's recipient device may be associated with a code in the correspondence table, indicating whether or not it is authorized to receive location data from the watch W1.For example, in the correspondence table or in another table, the first identifier of the recipient device of the third party IDd1 is associated with a value '0' if it is not authorized to receive location data from the watch W1, or with a value '1' if it is authorized to receive location data.

[0068] According to this embodiment, it is thus possible to determine, from a list of contacts or identifiers of recipient devices, the people (or recipient devices) with whom the user of the user's source device wishes to start sharing their location data, or conversely the people (or recipient devices) with which the user of the user's source device no longer wishes to share their location data.

[0069] The W1 watch also transmits (113), to the SMPH smartphone associated with the first identifier of the third party's recipient device (IDd1): a second identifier of the watch, also called second identifier of the user's source device (IDs2), corresponding to the first identifier of the user's source device (IDs1), for example a telephone number of the user of the watch, an access information message (IA message) informing the smartphone SMPH whether it is authorized to obtain location data from the watch W1.

[0070] According to a particular embodiment, the access information message carries the second identifier of the user's source device.

[0071] The SMPH smartphone therefore receives (121) from the user's source device a second identifier of the user's source device (IDs2) and the access information message (IA message). According to this embodiment, in order to be able to access the location data of the watch W1, the user of the SMPH smartphone, or equivalently the first identifier of the recipient device of the third party associated with the SMPH smartphone, must therefore be in the contact list of the user of the watch W1 stored in the watch W1, or equivalently in the identifiers of recipient devices stored in the watch W1.

[0072] For example, this access information message is transmitted in the form of an SMS, an email, etc. Such an access information message may, according to a particular embodiment, also carry a dynamic link, configured to open the dedicated companion application if it is installed on the third party's recipient device, or to offer the third party's recipient device the option of downloading the dedicated companion application otherwise.

[0073] In other words, according to this example, the dynamic link carried by the access information message works as follows: if the companion application dedicated to sharing location data is not installed on the device receiving the access information message from the third party (SMPH smartphone), the link redirects it to an application distribution platform, and more specifically to the companion application page, so that it can download it; if the companion application dedicated to sharing location data is installed on the device receiving the access information message from the third party, the link allows the application to be opened directly, from which it can receive and display the location data from the user's source device that are shared with this third party's recipient device.

[0074] According to a particular embodiment, since the watch W1 has directly contacted the third party's recipient device by sending the access information message, the watch W1 appears, in the user interface of the companion application, in the list of "visible" source devices, i.e. source devices for which the third party's recipient device can request access to the location data. The companion application can thus be updated with the watch W1.

[0075] After these operations, we can consider that the W1 watch and the SMPH smartphone are paired.

[0076] When the user of the SMPH smartphone wishes to access the location data of the watch W1, it transmits (122) to the server SER, from a user interface, a request for transmission of location data of the watch W1. Such a request sent by the SMPH smartphone comprises an identifier of the SMPH smartphone or of the companion application, called the second identifier of the recipient device of the third party (IDd2). For example, such an identifier is the telephone number of the SMPH smartphone, the name of the user of the SMPH smartphone, etc. In one or more embodiments, the request sent by the SMPH smartphone further comprises an identifier of the source device of the user, in the example considered an identifier of the W1 watch, called the second identifier of the source device of the user (IDs2).For example, such a second identifier is the identifier of the W1 watch from which the SMPH smartphone received the access information message, for example a phone number of the W1 watch.

[0077] The SER server receives (133) the request for transmission of location data from the watch W1 sent by the third party's recipient device and comprising the second identifier of the third party's recipient device as well as the second identifier of the user's source device.

[0078] Because the second user source device identifier matches the first user source device identifier used to construct or update the lookup table associating the first user source device identifier with the first third party recipient device identifier, the server can determine, using the second user source device identifier and the lookup table, whether the first and second third party recipient device identifiers match.

[0079] For example, the SER server analyzes (134), on the basis of the second identifier of the user's source device, on the one hand the first identifier of the third party's recipient device, stored in the correspondence table if the third party's recipient device is authorized to receive location data from the user's source device or associated with a code indicating whether it is authorized to receive location data from the user's source device, and on the other hand the second identifier of the third party's recipient device.

[0080] If the first identifier of the third party's recipient device and the second identifier of the third party's recipient device match, for example if they are identical, or if they are associated with the same person, this means that the third party's recipient device, i.e. the SMPH smartphone, is authorized to receive location data from the user's source device, i.e. the W1 watch.

[0081] The watch W1 can therefore transmit (114) its location data to the SER server, either continuously or upon request from the server. For example, an application embedded in the watch W1 retrieves the position of the watch W1 by querying a geolocation module of the watch W1, then transmits this data to the SER server so that the user of the watch W1 can temporarily share his geolocation with the third-party user of the smartphone SMPH. In one or more embodiments, the watch W1 can be configured to transmit its location data to the SER server as soon as it has sent an access information message authorizing access to its location data to at least one recipient device of the third party.

[0082] According to a particular embodiment, the location data are sent to the SER server with information of the validity period (val) type of the location data. For example, the watch W1 sends a message to the SER server comprising the location data of the watch W1 as well as a validity period of this data.

[0083] According to this particular embodiment, the validity period is a parameter that can be stored in the W1 watch, and configured by the user of the W1 watch. For example, the validity period can be chosen to be equal to a value between one hour and one week.

[0084] The SER server can thus receive (135) the location data from the W1 watch, either continuously or in response to a request from the server.

[0085] Optionally, according to the particular embodiment presented above, the location data of the watch W1 can be associated with information of the validity period type. According to this particular embodiment, upon receipt of the location data of the watch W1, the server SER triggers a timer whose value is equal to the validity period received with the location data.

[0086] The SER server can then transmit (136) to the SMPH smartphone the location data of the W1 watch, if the first and second identifiers of the third party's recipient device match.

[0087] The SER server consults, for example, the correspondence table associating a first identifier of the watch W1 with the first identifier of each recipient device of the third party authorized by the user of the watch W1 to receive the location data of the watch W1, and transmits this location data to this(these) recipient device(s) of the third party(ies).

[0088] According to the particular embodiment presented above, the SER server can transmit to the SMPH smartphone the location data of the W1 watch during the timeout. After the timeout expires, corresponding to the end of the validity period of the location data, the SER server deletes this location data and keeps no trace of it. It is therefore no longer possible to transmit it to the third party's recipient device.

[0089] The SMPH smartphone can thus receive (123), from the server, the location data of the W1 watch, and the user of the SMPH smartphone can view the location, for example the geolocation coordinates, of the W1 watch.

[0090] It has been described in relation to the figures 1 And 2 , in a simplified manner, the implementation of the proposed methods in a source device of the user, a server, and a recipient device of the third party. Of course, several source devices, several servers, and / or several recipient devices can be implemented. In this case, the operations described above are implemented for each source device of the user, server, and / or recipient device of the third party considered.

[0091] For example, if several source devices are considered, the server(s) manage one or more correspondence tables, associating, for each source device of the user, a first identifier of the source device of the user with the first identifiers of the destination devices authorized by the source device of the user considered. The server(s) can therefore manage a plurality of source devices and / or a plurality of destination devices.

[0092] Depending on the embodiment, the identifier of the user's source device transmitted to the server (first identifier of the user's source device) and to the recipient device(s) (second identifier of the user's source device) may take different forms, such as for example that of an email address or a telephone number associated with the user's source device and / or its user.

[0093] If a third party recipient device is authorized to receive location data from multiple source devices, it may display, in the companion application user interface, the list of “visible” source devices, i.e. source devices for which the third party recipient device can request access to location data.

[0094] If multiple recipient devices are considered, the server(s) transmit, for each user's source device, the location data of the user's source device in question to the companion application running on each recipient device of the third party authorized by the user's source device in question.

[0095] According to the embodiments presented above, the user of the user's source device can therefore choose to whom he sends his location data. In particular, he can authorize the user of a third-party recipient device to access his location data only for a specific time period (for example, the time of a race). In addition, the user's source device does not transmit his location data to authorized recipient devices via the server continuously, but only upon request from a third-party recipient device, after verification by the server that the third-party recipient device is still authorized to receive the location data from the user's source device.

[0096] It is noted that the operations mentioned above can be implemented in a different order. For example, the transmission of the access information message I to the smartphone SMPH can be implemented before the transmission to the server of the first identifier of the third party's recipient device and of the message A. Similarly, the transmission of the location data of the watch W1 to the server can be implemented continuously, or only upon request from the server. The comparison of the first identifier of the third party's recipient device and the second identifier of the third party's recipient device can be implemented before or after the server receives the location data.

[0097] It should also be noted that in order to secure data exchanges, messages exchanged between the server and the third party's recipient device (via the companion application dedicated to sharing location data) can be done using the secure communication protocol HTTPS (for HyperText Transfer Protocol Secure).

[0098] In order to secure data exchanges between the server and the third party's recipient device, a registration phase of the application with the server is implemented. The user of the companion application dedicated to sharing location data creates a user account with the server. During this account creation, the application transmits to the server an identifier of the third party's recipient device configured to run the application, also called the second identifier of the third party's recipient device, corresponding for example to the telephone number of the user of the third party's recipient device. The server transmits in response a message to the third party's recipient device (for example an SMS message, to the telephone number). This message includes in particular an authentication code.This authentication code is used to verify that the person using the third party's recipient device is actually authorized, as this person must enter the received authentication code into the companion application. Then, all exchanges between the third party's recipient device and the server, via the application, are made using an authentication header composed of a token including the second identifier of the third party's recipient device and the received authentication code.

[0099] During operation, the application sends HTTPS requests of the "REST" type to the server, using the token. In particular, the application sends the server a request for transmission of location data from the user's source device to receive the location data it can access.

[0100] Upon receipt of a request for transmission of location data from the user's source device issued by the application, the server extracts the second identifier of the third party's recipient device from the request (for example, a telephone number), then compares it to the first identifiers of the recipient devices that it received from the user's source device, stored in a correspondence table. If the second identifier of the third party's recipient device matches a first identifier of the third party's recipient device, the server checks in the correspondence table whether this third party's recipient device is authorized to access the location data of the user's source device. In other words, the server looks in correspondence tables which source devices the second identifier of the third party's recipient device (for example, a telephone number) has access to the location data.The server performs this verification based on the first identifier of the third party's recipient device (e.g., a phone number) that it received from the user's source device.

[0101] If the third party's recipient device is authorized to access the location data of the user's source device, the server transmits the location data to the third party's recipient device.

[0102] Note that a similar protocol can also be implemented to secure data exchanges between the server and the user's source device.

[0103] In relation to the figures 3 to 5 respectively, the structure of a user source device, a third-party recipient device and a server are presented, according to an exemplary embodiment. Only the main elements relating to the implementation of the proposed technique are illustrated.

[0104] As illustrated in figure 3 , the user's source device comprises a memory 31, a processing unit 32, equipped for example with a processor P, and controlled by an application or a computer program 33, configured for the implementation of one or more embodiments of the proposed location data sharing method.

[0105] Upon initialization, the code instructions of the computer program 33 are for example loaded into a RAM memory before being executed by the processor of the processing unit 32. The processor of the processing unit 32 is configured to implement the method for sharing location data according to at least one embodiment, according to the instructions of the computer program 33, to select a first identifier of the recipient device of the third party, from among a set of identifiers of recipient devices stored in the source device of the user, transmit to a remote server a first identifier of the source device of the user, the first identifier of the recipient device of the third party and an authorization message indicating whether this recipient device of the third party is authorized to obtain location data from the source device of the user,transmitting to the third party's recipient device a second identifier of the user's source device corresponding to the first identifier of the user's source device and an access information message informing it whether it is authorized to obtain location data from the user's source device, and transmitting location data from the user's source device to the remote server.,

[0106] The user's source device may be a watch, a geolocation beacon, an electronic component, or other apparatus comprising a geolocation module, a communication module, and a processor operably coupled to a memory, as well as, depending on the embodiment selected, other associated hardware elements such as a network interface and a media reader for reading and writing to a removable storage medium (not shown in the figure). The removable storage medium may be, for example, a compact disc (CD), a digital video / versatile disc (DVD), a flash drive, a USB flash drive, etc.Depending on the embodiment, the memory or the removable storage medium contains instructions which, when executed by the processing unit 32, cause this processing unit 32 to select recipient devices authorized to receive location data and / or exchange data with the server and / or a recipient device of the third party according to at least one mode of implementation of the proposed location data sharing method.

[0107] Furthermore, the proposed location data sharing method may be implemented in software form, as described above, in which case it takes the form of a program executable by a processor, or in hardware form, such as an application-specific integrated circuit (ASIC, “Application-specific Integrated Circuit” ), a system on a chip (SOC, "System On Chip"), or in the form of a combination of hardware and software elements, such as for example a software program intended to be loaded and executed on a component of the programmable logic circuits type (FPGA, " Field Programmable Gate Array » ). SOCs are embedded systems that integrate all the components of an electronic system into a single chip. A ASIC is a specialized electronic circuit that combines tailor-made features for a given application. ASICs are generally configured during manufacturing and can only be simulated by the user. FPGA are user-reconfigurable electronic circuits.

[0108] A method for sharing location data as proposed may also use hybrid architectures, such as CPU+FPGA, GPU (“ Graphics Processing Unit ”) or an MPPA (“ Multi-Purpose Processor Array » ).

[0109] As illustrated in figure 4, the third party's recipient device comprises a memory 41, a processing unit 42, equipped for example with a processor P, and controlled by an application, in particular the companion application dedicated to sharing location data, or a computer program 43, configured for the implementation of one or more embodiments of the proposed method of accessing location data.

[0110] Upon initialization, the code instructions of the computer program 43 are for example loaded into a RAM memory before being executed by the processor of the processing unit 42. The processor of the processing unit 42 is configured to implement the method for accessing the location data according to at least one embodiment, according to the instructions of the computer program 43, to receive a second identifier of the source device of the user and an access information message informing the recipient device of the third party whether it is authorized to obtain location data from the source device of the user, transmit to a remote server a request for transmission of location data from the source device of the user, the request comprising a second identifier of the recipient device of the third party, and receive, from the server, location data from the source device of the user in response to the request.

[0111] The third party's recipient device may be a mobile phone, for example a smartphone, a computer, an electronic component, or another device comprising a communication module and a processor operatively coupled to a memory, as well as, depending on the embodiment chosen, other associated hardware elements such as a network interface and a media reader for reading and writing to a removable storage medium (not shown in the figure). The removable storage medium may be, for example, a compact disc (CD), a digital video / versatile disc (DVD), a flash drive, a USB stick, etc.Depending on the embodiment, the memory or the removable storage medium contains instructions which, when executed by the processing unit 42, cause this processing unit 42 to exchange data with the server and / or the source device of the user according to at least one mode of implementation of the proposed method of accessing the location data.

[0112] Furthermore, the proposed method for accessing location data may be implemented in software form, as described above, in which case it takes the form of a program executable by a processor, or in hardware form, such as an application-specific integrated circuit (ASIC), a system-on-chip (SOC), or in the form of a combination of hardware and software elements, such as, for example, a software program intended to be loaded and executed on an FPGA-type component. A proposed method for accessing location data may also use hybrid architectures, such as, for example, CPU+FPGA, GPU, or MPPA-based architectures.

[0113] As illustrated in Figure 5, the server comprises a memory 51, a processing unit 52, equipped for example with a processor P, and controlled by an application or a computer program 53, configured for the implementation of one or more embodiments of the proposed location data sharing management method.

[0114] Upon initialization, the code instructions of the computer program 53 are for example loaded into a RAM memory before being executed by the processor of the processing unit 52. The processor of the processing unit 52 is configured to implement the location data sharing management method according to at least one embodiment, according to the instructions of the computer program 53, to receive from the source device of the user a first identifier of the source device of the user, a first identifier of the recipient device of the third party and an authorization message indicating whether the recipient device of the third party is authorized to obtain location data from the source device of the user, construct or update a correspondence table associating the first identifier of the source device of the user with the first identifier of the recipient device of the third party,receiving location data from the user's source device, receiving a request for transmission of location data from the user's source device, the request comprising a second identifier of the user's source device, corresponding to the first identifier of the user's source device, and a second identifier of the third party's destination device, determining, using the second identifier of the user's source device and the correspondence table, whether the first and second identifiers of the third party's destination device match, and transmitting to the third party's destination device the location data of the user's source device, in response to the request, when the first and second identifiers of the third party's destination device match.,

[0115] The server may be a computer or a network of computers, or another apparatus comprising a processor operatively coupled to a memory, and, depending on the embodiment, other associated hardware such as a network interface and a media reader for reading and writing to a removable storage medium (not shown in the figure). The removable storage medium may be, for example, a compact disc (CD), a digital video / versatile disc (DVD), a flash drive, a USB flash drive, etc. Depending on the embodiment, the memory or the removable storage medium contains instructions which, when executed by the processing unit 52, cause this processing unit 52 to exchange data with the source device of the user and / or the destination device of the third party according to at least one embodiment of the proposed location data sharing management method.

[0116] Furthermore, the proposed location data sharing management method may be implemented in software form, as described above, in which case it takes the form of a program executable by a processor, or in hardware form, such as an application-specific integrated circuit (ASIC), a system-on-chip (SOC), or in the form of a combination of hardware and software elements, such as, for example, a software program intended to be loaded and executed on an FPGA-type component. A location data sharing management method as proposed may also use hybrid architectures, such as, for example, CPU+FPGA, GPU, or MPPA-based architectures.

[0117] Depending on the embodiment selected, certain acts, actions, events, or functions of each of the methods described herein may be performed or occur in a different order than they were described, or may be added, merged, or may not be performed or occur, as the case may be. In addition, in some embodiments, certain acts, actions, or events are performed or occur concurrently and not successively.

Claims

1. Method for managing sharing of location data between a source device (11) of a user and a destination device (12) of a third party, said method being implemented by a server which is remote from said source device (11) of a user and from said destination device (12) of a third party, said method comprising the following steps: - receiving (131), from the source device of the user, a first identifier of the source device of the user, a first identifier of the destination device of the third party, and an authorization message indicating whether the destination device of the third party is authorized to obtain location data from the source device of the user, - constructing or updating (132) a lookup table associating the first identifier of the source device of the user with the first identifier of the destination device of the third party, - receiving (135) location data from the source device of the user, - receiving, from a companion application dedicated to sharing location data and executed by said destination device (12) of the third party, an identifier of the destination device of the third party, referred to as the second identifier of said destination device of the third party, said second identifier of said destination device of the third party being received during the creation of a user account with said server by a user of the companion application, - transmitting, in response to said receiving of said second identifier of the destination device of the third party, a message to said destination device of the third party, said message comprising an authentication code, - receiving (133), from the destination device of the third party, a request to transmit location data from the source device of the user, the receiving of the request using a token comprising the second identifier of the destination device of the third party and said authentication code, said request further comprising a second identifier of the source device of the user corresponding to the first identifier of the source device of the user, - verifying, using the authentication code, that said user of said destination device of the third party is authorized, - determining (134), using the second identifier of the source device of the user and the lookup table, whether the first identifier and second identifier of the destination device of the third party match, and - transmitting (136), to the destination device of the third party, the location data from the source device of the user, in response to the request, when the first identifier and second identifier of the destination device of the third party match.

2. Management method according to Claim 1, also comprising receiving a validity period which is applicable to the location data from the source device of the user.

3. Management method according to Claim 2, further comprising: - activating a timeout having a value which is equal to the validity period, - storing the location data from the source device of the user in memory during the timeout, - deleting the stored location data after the timeout has expired.

4. Server for managing sharing of location data between a source device of a user and a destination device of a third party, comprising a processor operationally coupled to a memory, and configured to implement a data sharing management method according to any one of Claims 1 to 3.

5. Method for accessing location data from a source device of a user, said method being implemented in a destination device of a third party, said method comprising the following steps: - receiving (121), from the source device of the user, an identifier of the source device of the user, referred to as the second identifier of the source device of the user, and an access information message informing the destination device of the third party whether it is authorized to obtain location data from the source device of the user, - a user of a companion application dedicated to sharing location data and executed by said destination device of the third party creating a user account with a server which is remote from said source device, - the companion application transmitting, to said remote server, during said creation of the user account, an identifier of the destination device of the third party, referred to as the second identifier of the destination device of the third party, - receiving, in response to said transmission of said second identifier of the destination device of the third party, from said remote server, a message comprising an authentication code, - the user of the destination device of the third party entering said authentication code into said companion application, - transmitting (122), to said remote server, a request to transmit location data from the source device of the user, the request comprising the second identifier of the source device of the user and being transmitted using a token comprising said second identifier of the destination device of the third party and said authentication code, and - receiving (123), in response to the request to transmit location data from the source device of the user, location data from the source device of the user.

6. Destination device of a third party configured to access location data from a source device of a user, comprising a processor operationally coupled to a memory, and configured to implement the method for accessing location data from a source device of the user according to Claim 5.

7. Method comprising the steps of the method for managing sharing of location data according to one of Claims 1 to 3, said method further comprising the steps of the method for accessing location data from the source device of the user (11) according to Claim 5, the method further comprising the following steps implemented in the source device of the user: - selecting (111) the first identifier of the destination device of the third party, from a set of identifiers of destination devices of at least one third party which are stored in the source device of the user, - transmitting (112), to the remote server, the first identifier of the source device of the user, the first identifier of the destination device of the third party and the authorization message indicating whether the destination device of the third party is authorized to obtain location data from the source device of the user, - transmitting (113), to the destination device of the third party, the second identifier of the source device of the user matching the first identifier of the source device of the user, and the access information message informing it whether it is authorized to obtain location data from the source device of the user, and - transmitting (114) the location data from the source device of the user to the remote server.

8. System comprising a source device of a user, a destination device of a third party and a remote server, said system being configured to implement the method according to Claim 7.

9. System according to Claim 8, according to which the source device is a watch, further comprising: - a geolocation module, - a communication module.

10. Computer program comprising instructions which, when the program is executed by a processor, lead said processor to implement the method according to any one of Claims 1 to 3 or Claim 5.

11. Computer-readable non-transitory storage medium on which the computer program according to Claim 10 is stored.