Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/22—Indexing; Data structures therefor; Storage structures
  • G06F16/2228—Indexing structures
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/29—Geographical information databases
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/60—Protecting data
  • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
  • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
  • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
  • G06F21/6254—Protecting personal data, e.g. for financial or medical purposes by anonymising data, e.g. decorrelating personal data from the owner's identification
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
  • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
  • H04L67/5683—Storage of data provided by user terminals, i.e. reverse caching
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
  • H04W4/029—Location-based management or tracking services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
  • H04W52/02—Power saving arrangements
  • H04W52/0209—Power saving arrangements in terminal devices
  • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
  • H04W52/0254—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity detecting a user operation or a tactile contact or a motion of the device
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
  • H04W52/02—Power saving arrangements
  • H04W52/0209—Power saving arrangements in terminal devices
  • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
  • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
  • H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/60—Context-dependent security
  • H04W12/69—Identity-dependent
  • H04W12/75—Temporary identity
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

• the present invention relates to a method for processing geolocation data.
• Modern mobile terminals of the smartphone type have geolocation capabilities, allowing for example the navigation on a map, "check-in”, that is to say the publication of the position of a user on social networks, as well as many other features.
• the geolocation data is transmitted to a trusted server, which returns to the terminal processed data corresponding to different levels of associated accuracy possible (for example, if the user geolocates in an airport, the different levels can from the precise number of the airport door in which the user is, to the general indication of the region in which the airport is located), for selection by the user and transmission to a or multiple application servers for one or more check-ins.
• This process can slightly reduce the consumption to the extent that some treatments are deported.
• check-ins are a small part of energy consumption for geolocation purposes. Indeed, it is the mechanisms of "tracking" (French tracking) that consume the most battery mobile. Tracking consists of the repeated sending (for example every thirty seconds) of the user's position so as to allow dynamic functionalities, for example the sending of a notification if the user passes close to a predetermined position (a center of interest, a known person, a sign, etc.).
• Tracking consists of the repeated sending (for example every thirty seconds) of the user's position so as to allow dynamic functionalities, for example the sending of a notification if the user passes close to a predetermined position (a center of interest, a known person, a sign, etc.).
• a proposal that has been made to reduce the energy consumption related to tracking is the forced reduction in the frequency of updating geolocation data, which can affect the operation of certain applications.
• Document US 201 1/0159884 also discloses a solution in which a server storing the position of the terminal serves as an interface for the various application servers, the terminal not transmitting its position to the server intermediate only if it moves significantly. This solution therefore makes it possible to reduce the energy consumption of the terminal only in the case of reduced mobility.
• the present invention thus relates to a geolocation data processing method comprising the implementation by data processing means of a server of steps of:
• a trusted server to respond to requests sent by the application servers makes it easy to anonymize the geolocation data and to rationalize the solicitation of the geolocation means of the mobile terminals: if several applications require these data, it just transmit them once to the server, and it is the latter that processes multiple requests.
• this method requires only the implementation of a lightweight module on the terminal and facilitates the development of new applications using geolocation, as long as it is sufficient to contact a single server, which can handle complex queries offering advanced features (for example, notification request if a certain event occurs).
• advanced features for example, notification request if a certain event occurs.
• Said unique identifier is an anonymous identifier generated by the mobile terminal and received by the data processing means of the server during step (a);
• Said unique identifier is an anonymous identifier generated in step (b) by the data processing means of the server and sent to the mobile terminal;
• Said unique identifier received by the mobile terminal is sent to the application server if the user authorizes the application server to access his geolocation data;
• the geolocation data are also associated in said database with temporal data relating to the moment of their reception in step (b);
• the method comprises a step (e1) of transmitting a new first request, receiving updated geolocation data from the mobile terminal and then updating the database stored on the data storage means;
• the method comprises the repetition of steps (d) and (e), wherein step (e1) being implemented following each step (d) if the data processing means of the server determine according to associated rules the application server that issued the second request that the geolocation data be updated;
• step (e1) being repeated at a frequency depending on the frequencies at which the sequence of steps (d) and (e) is repeated for an application server and / or at least one rule associated with the application server;
• the response generated in step (e) comprises a degraded version of the geolocation data associated with the unique identifier in said database
• the second request received in step (d) comprises reference geolocation data, according to a rule associated with the application server the step (e) comprises comparing the geolocation data associated with the unique identifier in said database with the reference geolocation data, the generated response being a function of the result of said comparison.
• the invention relates to a geolocation data processing server connected to at least one mobile terminal comprising geolocation means and to at least one application server, the server comprising data storage means and means data processing configured to implement:
• a second module for receiving a second geolocation request sent by the application server, the second request comprising said unique identifier associated with the mobile terminal;
• the invention relates to a system comprising: at least one mobile terminal comprising geolocation means; at least one application server;
• At least one server according to the second aspect.
• the mobile terminal implements a module for managing the rules associated with each application server.
• the invention relates to a computer program product comprising code instructions for executing a method according to the first aspect of the geolocation data processing invention; and computer readable storage means on which a computer program product comprises code instructions for executing a method according to the first aspect of the geolocation data processing invention.
• FIG. 1 represents an architecture for implementing the method according to the invention.
• One or more mobile terminals 1a, 1b are connected to a communication network 20 (in particular a mobile telephone network).
• a communication network 20 in particular a mobile telephone network.
• Each mobile terminal 1a, 1b may be any device capable of connecting to the communication network 20. It may for example act as a smartphone, a touch pad, etc.
• Each mobile terminal 1a, 1b comprises geolocation means 10, which can implement one of the many geolocation techniques implemented on mobile terminals (GPS, GSM positioning, RFID, etc.). It will be understood that the preceding method is not limited in any way to obtain on the mobile terminal 1a, 1b location data, and that the means 10 can take any form (physical and / or software).
• a server 2 is connected to the communication network 20. It is a “trusted” server, in particular a server of the network operator 20. It conventionally comprises a data processing module 21 (a processor) and a data storage module 22 (for example a hard disk).
• a data processing module 21 a processor
• a data storage module 22 for example a hard disk
• This server 2 is itself connected for example via the Internet network 30 to one or more application servers 3a, 3b. They are servers involved in the operation of an application (for example one or more servers of a social network), at the origin of geolocation data requests sent to the terminals 1 a, 1 b.
• application servers 3a, 3b are servers involved in the operation of an application (for example one or more servers of a social network), at the origin of geolocation data requests sent to the terminals 1 a, 1 b.
• the Applicant has noticed that it is now common that several applications simultaneously use the geolocation data of a mobile terminal, especially in tracking mode. For example, it is possible that the user is using a first application of type "map" displaying a map on which the position of the user is displayed, while in the background some applications, designed by example to send a notification if the user is near a friend, a restaurant, etc., works.
• the application server of each of these applications "tracks" the position of the user, that is to say that he requires (possibly at regular intervals) the location data of his mobile terminal 1 a, 1 b.
• the present method thus proposes a way of avoiding any redundancy in the management of the geolocation data, thanks to the trusted server 2.
• the present server 2 instead of operating in a "push” mode in which it is the terminal 1a, 1b that decides when to send geolocation data to the server (it “pushes” the data), the present server 2 implements a so-called “pull” mode of operation in which it explicitly asks for the terminal position when appropriate (the server "pulls” the data), the latter simply replying.
• the intelligence (with regard to the management of the geolocation) of the terminal 1a, 1b is at least partially moved to the trusted server 2.
• the server 2 operates only in push mode.
• a first step (a) the data processing means 21 of the server 2 transmit to the mobile terminal a first geolocation request (this is the pull request).
• these data processing means 21 receive from the mobile terminal 1a, 1b geolocation data (obtained by the geolocation means 10).
• This sending has the particularity of not being implemented in response to a request from an application. It just aims to provide this data to the server 2 for storage.
• this first request can follow, or on the contrary precede, a second request coming from an application server 3a, 3b.
• these data are associated in a database stored on the data storage means 22 of the server 2, with a unique identifier itself associated with the mobile terminal 1a, 1b.
• the geolocation data are also associated in this database with time data (typically time) relative to the moment of their reception in step (b).
• the database of the server 2 consists of triplets of type (identifier, geolocation data, time). Many terminals 1a, 1b can be managed within a single database.
• This unique identifier is an anonymous identifier that can be either generated by the data processing means 21 of the server 2 and sent to the mobile terminal 1 a, 1 b (during the step (b)), or generated by the mobile terminal. 1 a, 1 b, which directly sends the pair (identifier, data) to the server 2 in step (b).
• the unique identifier makes it possible to anonymize the geolocation data by preventing the latter from being referenced via data enabling the terminal 1a, 1b or its user to be directly identified.
• the trusted server 2 Only the trusted server 2 is possibly able to link a unique identifier to the real identity of the user, which guarantees the confidentiality of the geolocation data.
• the terminal 1a, 1b which generates (and changes) the identifier it is possible to make the server 2 is not able to bind the old and the new identifier, since it receives directly a new pair (identifier, data), which it can interpret as representing a new terminal. This increases the confidentiality, but it may be desirable to avoid it if, for example, an application uses past positions of the terminal 1a, 1b.
• the unique identifier can be changed (that is to say regenerated by the server 2 / the terminal 1a, 1b) at regular intervals, for example every hour.
• the "current" unique identifier of the mobile terminal 1 a, 1 b is sent to the application server 3a, 3b (so that the latter can designate the terminal 1a, 1b) if the user authorizes the application server 3a , 3b to access its geolocation data.
• This authorization can be given via a software module implemented on the terminal 1a, 1b (which will be described in more detail below).
• the sending can be done either by the terminal 1a, 1b, or by the server 2.
• the server 2 can receive in a step (d) a second geolocation request sent by the application server 3a, 3b, the second request comprising said unique identifier associated with the mobile terminal 1a, 1b ( as well as additional data that will be described later). It is note that step (d) may optionally precede one or more of steps (a) to (c). Indeed step (d) and steps (a) to (c) are independent and server 2 does not control the arrival time of the second requests.
• the data processing means 21 of the server 2 will then generate and send to the application server 3a, 3b (in a step (e)) a response to the second request according to the geolocation data associated with the unique identifier in said base data, and rules associated with the application server 3a, 3b.
• Steps (d) and (e) occur as many times as second requests are sent to server 2. As will be seen later, each second request may or may not give rise to the updating of geolocation data (in other words the sending of a first request).
• the trusted server 2 that receives the second requests and responds to them. None of the second requests is transmitted to the terminal 1 a, 1 b. The latter only sees the first requests (which are in practice much less numerous than the second queries thanks to the intelligence of the server 2) and is thus not solicited excessively.
• All exchanges between terminals and trusted server, application servers and trusted server
• a single sending of geolocation data by the terminal 1a, 1b can be exploited by a plurality of application servers 3a, 3b, the energy cost of generating a response per request being reported on the server 2
• the present precedes provides a one-stop service to the applications, allowing the mobile terminal 1a, 1b to send only once its geographical position, this information being available for all applications.
• Energy consumption linked to geolocation becomes independent of the number of active applications; o on the other hand the terminal 1 a, 1 b is solicited to the strict minimum thanks to the filtering done intelligently by the server which transforms a large number of second requests into a small number of first requests, or takes the initiative of the first queries when this is timely.
• the geolocation data associated with a particular mobile terminal 1 a, 1 b in the database are quickly obsolete, since the user continues to move. It is therefore necessary to update them regularly, especially if an application operates in tracking mode (and therefore the associated application server 3a, 3b must receive updates at regular intervals).
• the method thus advantageously comprises a step (e1) of transmitting a new first request, receiving updated geolocation data from the mobile terminal 1a, 1b and updating the database stored on the means. 22.
• the step (e1) is equivalent to a repetition of the steps (a) to (c), that is to say, the issuance of a new first request.
• this update is not necessarily a replacement of previously stored data. If the geolocation data is associated with a time parameter, it is possible to create a new entry in the database. In general, this will be the most recent entry for a given unique identifier that will be used (although as explained one can imagine that the knowledge of old geolocation data could be interesting for some applications).
• Step (e1) can take place before or after step (e).
• step (d) each time a second request is received (step (d)), the server 2 determines whether an implementation of step (e1) is necessary, according to rules associated with each application server 3a, 3b and parameters such as "age" data. These rules can, for example, define a time threshold beyond which data are considered outdated and must be updated, or a consecutive number of second requests. In other words, at each second request, the server 2 responds directly (no implementation of step (e1)) if it can (the information is there), or goes back to the source if necessary (the information is absent or obsolete). In this embodiment, each possible implementation of step (e1) is interposed between steps (d) and (e).
• the server 2 has the initiative and can independently of the reception of the second requests update the geolocation data (implementation of the step (e1) after step (e) and before a possible step (d)).
• a sign wants to be notified when potential customers are near its stores; it is then the server 2 which notifies the application server 3a, 3b when it is the case.
• he can query the mobile on his own initiative (pull request), when for example the historical data makes him think that such potential customer must be close to such store.
• the second requests are sent at a given frequency (tracking frequency), in other words the frequency at which the sequence of steps (d) and (e) is repeated for at least one application server. 3a, 3b.
• the updating frequency can be set by the server 2 and defined as that fixed by the most restrictive application: instead of using rules and / or reacting to each reception of a second request , step (e1) is repeated at a frequency equivalent to the highest frequency among the frequencies at which the sequence of steps (d) and (e) is repeated for an application server 3a, 3b.
• the actual frequency may alternatively depend on other criteria such as the time or the position of the mobile , according to user-defined access rules (see below).
• an application A requires a precision of 50 m on the location of the terminal 1 a, 1 b and an application B an accuracy of 500 m
• the position will be sent with an accuracy of 50 m to ensure the good operation of application A, and the update will be requested as soon as the current position differs by more than 50 m from the last position sent.
• the different data update modes mentioned above can be implemented in turn or in combination depending on the different application servers 3a, 3b requiring geolocation.
• the geolocation means 10 never transmit useless updates (ie that can not be exploited by an application) in order to preserve as much as possible the battery of the mobile terminal 1 a, 1 b.
• the frequency can therefore be continuously optimized by the data processing means 21 of the server 2.
• the generation of the responses may be a function of other rules associated with the application servers 3a, 3b, these rules being moreover able to be managed at the mobile terminal 1a, 1b by a specific module.
• this module allows for each application to first define an authorization or not to access the geolocation data. If the authorization is given, the server 2 can transmit to the application server associated with the unique identifier of the terminal 1a, 1b (which makes possible the receipt and processing of requests by the server 2).
• this module defines the rules, which can be seen generally as management rules, that is to say modulations on the level of access to geolocation data, and on possible additional treatments, to be compared. the rules related to updating the data (step (e1)).
• a management rule may allow an application to access these data only with a certain temporal and spatial precision, this level of precision being able to be a function of the time and the position of the mobile terminal 1 a, 1 b.
• the server 2 can then take care of "degrading" the data by adding a hazard to the exact position and the moment at which this position has been recorded.
• a maximum frequency of the requests of the application can also be defined.
• step (e) may include the comparison by the data processing means 21 of the server 2 of the associated geolocation data. to the unique identifier in said database with the reference geolocation data, the generated response being a function of the result of said comparison (for example it is a response to "the terminal is less than 100 meters from such a position?").
• the use of the trusted server 2 thus makes it possible to consider responding directly to complex requests, which facilitates the work of the developers (possibility of "pre-processing" in the server 2, with elaborate answers obtained at the end of step (e), which can be directly used in the applications), while increasing the level of confidentiality (possibility of directly responding to the complex requests of the application servers 3a, 3b without ultimately disclosing the real position of the user ).
• the software module can be implemented in the operating system of the mobile terminal 1 a, 1 b or as an independent application, which can be activated by the applications using the geolocation data.
• the management module can play an additional role.
• a user can indeed call on servers 2 that are active at the same time (with updates for each server) or alternatively: the software module can, by notifying the applications, change server 2 or request a change of identifier unique to enhance the anonymity of the user's data.
• There may be a default trusted server 2 for example, managed by the OS manufacturer), configurable by the user.
• the invention also relates to the trusted server 2 for the implementation of the previously described method.
• This server 2 is therefore connected to at least one mobile terminal 1a, 1b including geolocation means 10 and at least one application server 3a, 3b. It comprises data storage means 22 and data processing means 21.
• a module for associating said geolocation data in a database stored on the data storage means 22 with a unique identifier itself associated with the mobile terminal 1 a, 1 b (this module also enabling the generation of the unique identifier, and where applicable the update of the geolocation data in the database);
• a second module for receiving a second geolocation request sent by the application server 3a, 3b, the second request comprising said unique identifier associated with the mobile terminal 1a, 1b; a module for generating and sending to the application server 3a, 3b a response to the second request according to the geolocation data associated with the unique identifier in said database, and rules associated with the application server 3a, 3b .
• the invention furthermore relates to the system which comprises this server 2, at least one mobile terminal 1a, 1b comprising the geolocation means 10 and at least one application server 3a, 3b.
• the mobile terminal (s) 1 a, 1 b advantageously implement (via own means of data processing) a management module of the rules associated with each application server 3 a, 3 b (which also optionally allows the activation / disabling access rights to geolocation data for application servers 3a, 3b, and commands related to server 2 such as the possibility of regenerating a unique identifier).
• a management module of the rules associated with each application server 3 a, 3 b which also optionally allows the activation / disabling access rights to geolocation data for application servers 3a, 3b, and commands related to server 2 such as the possibility of regenerating a unique identifier.
• the invention relates to a computer program product comprising code instructions for the execution (in particular on the data processing module 21 of the server 2) of a method according to the first aspect. of the invention of data processing of geolocation, as well as storage means readable by a computer equipment (for example a data storage module 22 of the server 2) on which this computer program product is found.

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Theoretical Computer Science (AREA)
• Databases & Information Systems (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Bioethics (AREA)
• General Health & Medical Sciences (AREA)
• Health & Medical Sciences (AREA)
• Computer Security & Cryptography (AREA)
• Software Systems (AREA)
• Data Mining & Analysis (AREA)
• Computer Hardware Design (AREA)
• Medical Informatics (AREA)
• Remote Sensing (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=50137724

Family Applications (1)

Country Status (4)

Families Citing this family (13)

Family Cites Families (15)

• 2013
  • 2013-07-26 FR FR1357423A patent/FR3009159B1/fr active Active
• 2014
  • 2014-07-28 US US14/907,508 patent/US20160162706A1/en not_active Abandoned
  • 2014-07-28 EP EP14744556.3A patent/EP3025481A2/de not_active Withdrawn
  • 2014-07-28 WO PCT/EP2014/066206 patent/WO2015011296A2/fr active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events