WO2002076121A1 - System for controlling access to data relating to the localization of geolocalizable devices - Google Patents
System for controlling access to data relating to the localization of geolocalizable devices Download PDFInfo
- Publication number
- WO2002076121A1 WO2002076121A1 PCT/FR2002/000910 FR0200910W WO02076121A1 WO 2002076121 A1 WO2002076121 A1 WO 2002076121A1 FR 0200910 W FR0200910 W FR 0200910W WO 02076121 A1 WO02076121 A1 WO 02076121A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- location data
- request
- access
- database
- authorization parameters
- Prior art date
Links
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
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/14—Delay circuits; Timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2072—Schedules, e.g. personal calendars
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
- H04M3/42068—Making use of the calling party identifier where the identifier is used to access a profile
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
Definitions
- the present invention relates to a system for protecting access to location data of a set of geolocatable devices.
- geolocatable device is understood here to mean a device allowing the determination of its geographic position and / or the description of its movements.
- the means for determining these positions and / or movements may belong to the device itself (for example a GPS receiver). They can also be remote to the device, by operating on the basis of signals emitted by the latter.
- a typical example of a geolocation device is a cellular radiotelephone.
- the cellular network infrastructure makes it possible to locate the radiotelephone on the basis of the cell where it is located. The location of such a device results from the position of the base station with which it is communicating, or from that which picks up a response to a terminal search command ("paging") when the device is not not communicating.
- the cellular network infrastructure can also employ known localization methods having a finer spatial resolution than that of cells.
- a tracking device consists for example of a degraded cellular radio communication terminal to allow its location as indicated above, but not the establishment of communications.
- An object of the present invention is to propose a technique allowing flexible and efficient control of access to location data from one or more user applications, in order to promote the development of various services using such data.
- the invention thus proposes a system for controlling access to location data of geolocatable devices, comprising:
- a database for containing authorization parameters defining access conditions, by at least one user application, to the location data of a set of geolocatable devices
- This system acts as an intermediary between the applications using location data, one or more location servers capable of providing this data and the access authorities.
- the system may belong, in whole or in part, to the same system as a location server.
- Location servers can also be external. In the latter case, this system can be linked to several location servers corresponding for example to different cellular operators, so that the system presents itself, for user applications, as a one-stop shop where location data can be obtained. access is allowed.
- the access authority can be the same for all user applications.
- This single access authority can in particular be the device itself, which allows its holder to control the conditions under which it can be located.
- the single authority can also be an information system of an organization operating a number of geolocatable devices (for example the system of supervision of a fleet of trucks).
- the access authority for a given geolocation device can also be different from one user application to another.
- the messages received by the second communication interface and analyzed by the filtering means typically carry requests for location data from user applications. They can also be response messages to such requests, passing through the access control system before being delivered to the applications concerned.
- the access control system offers great flexibility in access conditions which may be taken into account in the authorization database.
- These conditions may in particular relate to the application / device pair, the date and time of the request, the location of the device, data obtained from an external server to which the system is connected, etc.
- Each access authority of a device can modify the authorization profile defined by the parameters contained in the database.
- the updated parameters are then taken into account for the processing of requests for location data concerning the device.
- FIG. 1 is a block diagram of a system for controlling access to location data according to the invention
- FIG. 2 is a block diagram of a system for controlling access to location data according to the invention
- FIG. 2 is a block diagram of a system for controlling access to location data according to the invention
- FIG. 2 is a block diagram of a system for controlling access to location data according to the invention
- FIG. 2 is a block diagram of a system for controlling access to location data according to the invention
- FIG. 5 is a block diagram of an alternative embodiment of the system according to the invention.
- a location server 3 is for example managed by a cellular radio operator. Several location servers 3 are accessible when the system cooperates with several cellular operators or when an operator has several location servers;
- - access authorities 4 each having the capacity to define, for one or more geolocatable devices and one or more applications -conditions in which these applications can access the location data of these devices (module 14).
- the access authority is also empowered to modify or delete previously granted authorizations.
- the geolocatable device is a cellular radiocommunication terminal
- its access authority 4 may consist of the terminal itself.
- the access authority can also be a third party, for example the employer of the holder of a geolocatable device for professional use. Free access can still be specified for certain devices and / or certain user applications, in which case there is no access authority;
- One or more external servers 5 from which the system 1 can obtain possibly relevant information to validate or reject requests for location data (module 15).
- An example of such an external server 5 is a billing server of a cellular operator (for example, the validation of a request depends on the payment of the invoices by the holder of the geolocatable device).
- the interface modules 12 and 13 support, for example, the application programming interface (API) called "Mobile Location Query", specified in a LIF standard.
- API application programming interface
- the interface 12 thus receives standard requests for location data from user applications 2, each identifying one or more devices whose location data is requested.
- the interface 13 likewise transmits standard requests for location data to the location server or servers relevant for the device or devices concerned if the request received on the interface 12 is validated by a request filter 16 cooperating with a database. authorization data 18.
- the responses received from the location servers 3, for example on the “Mobile Location Query” API, are retransmitted, after possible processing by the filter 16, to the user application 2 via the interface 12.
- the interface modules 12 and 13 are advantageously connected to two separate local networks, for example of TCP / IP (“Transmission Control Protocol / Internet Protocol”) type.
- TCP / IP Transmission Control Protocol / Internet Protocol
- One of these local networks for example that located towards the location servers 3, can also be used for the connections to the external servers 5 by the interface module 15.
- the authorization interface module 14 comprises on the one hand a mail server and on the other hand a portal server.
- the messaging server for example voice and / or SMS (“Short Message Service”) type, allows a confirmation module 19 of the LDP system to communicate with the access authorities 4 to activate authorization parameters in the database 18 relating to one or more application / device pairs.
- the portal server for example of the Web type, WAP (“Wireless Application Protocol”) or voice, allows the access authorities 4 to dialogue with an authorization profile management module 20 to define and update certain parameters. authorization of the database 18.
- the LDP system 1 can be produced from two platforms of the RS 6000 type sold by the company IBM, one including interfaces 12, 13 and 15 and the request filter 16, and the other including the interface 14 as well as the authorization database 18, the modules 19, 20 for confirmation and management of profiles and a system administration module (not shown in Figure 1). These two platforms can communicate with each other via the same local network as that providing the links with the location servers 3 and the external servers 5.
- the two platforms are provided with programs, for example developed in C language / C ++, for the execution of access control procedures such as those described below.
- the purpose of the LDP system is to protect location data that one or more location servers 3 can provide against unauthorized access by user applications 2.
- the basic task is to examine each standard request from a user application 2 to determine whether it can be answered, in whole or in part.
- the LDP system can generate and return a refusal message directly to the application from which it originated.
- the request is transmitted to the location server (s) 3 concerned, after having undergone any processing in the LDP system.
- processing may for example consist in removing from the list of devices to be located according to the original request those for which authorization has not been granted.
- the processing can also include a referral of requests re-sent to several location servers (for example in the case where the location of the various devices listed is carried out by several distinct cellular operators). If the APIs supported by interfaces 12 and 13 are distinct (unlike the example considered above), processing can also include a translation of the request between the two API formats.
- the response returned by the location server (s) 3 can be transmitted directly to the requesting application 2, or it can be previously processed by the LDP system. In the latter case, the filter 16 can make some additional checks, in particular if authorization conditions defined in the database 18 relate to the actual location and / or movements of the device. If necessary, the response returned to the user application can be modified in order to remove the location data to which access is not authorized and / or to add information indicating the reasons why access was been refused.
- the protection mechanisms for location data are at two levels: the level of services implemented by user applications and the level of geolocatable devices.
- the protection mechanisms at the service level are based on known access control methods, using for example authentication methods using passwords or public keys. This ensures that only authorized and authenticated user applications can address their requests to the LDP system. These mechanisms are for example applied via the applications interface 12. It should be noted that they are optional: if they are not used, access to any user application is assumed to be authorized at the service level.
- the administration module of the LDP system (not shown in FIG. 1) configures the applications interface 12 for each new user application capable of being authorized to access the LDP system. This configuration concerns the following parameters:
- free requests - types of requests authorized unconditionally, called “free requests” (if such free requests are provided, they are transmitted directly from the interface 12 to the interface 13 without being processed by the request filter 16); - type of access authority and possibly description of its parameters
- the LDP system administrator can also modify the configuration of the interface 12 for any user application 2 and in particular delete the access rights of an application.
- the protection mechanisms at device level ensure that a user application 2 (where applicable already authorized at service level) can only access location data for geolocatable devices for which an authorization has been explicitly given.
- the service-level protection mechanism can be applied at the entry of the LDP system (on request from a user application), or at the exit of the LDP system (before responding to the user application), or at the same time at the entrance and at the exit.
- the protection mechanisms at device level are applied by the filter 16 in relation to the authorization database 18 and possibly the information coming from the external servers 5.
- the database 18 contains an authorization profile comprising a separate set of authorization restriction parameters for each user application 2 or each system provided with one or more user applications. These parameters describe conditions under which the application is authorized to access the location data of the device.
- these authorization restriction parameters are set to default values, which may depend on the application concerned.
- the access authority assigned to the geolocatable device can modify the values of these parameters by dialoguing with the profile management module 20 through the portal server of the interface 14.
- the module 20 saves the updated parameters in the authorization database 18.
- the authorization conditions defined by the profile parameters can relate to one or more of the following elements or their combinations:
- - authorization period during the day (for example from 8 am to 6 pm). These periods can be understood daily or be associated with a particular type of day (for example working day, weekend, ...);
- time interval during which access is suspended for the user application (for example from January 3, 2001, 6 p.m. to January 10, 2001, 8 a.m.).
- Such information relates for example to the level of service consumption of geolocalizable devices of the cell phone type or user applications, local weather, etc.
- the access authority can view and modify the authorization profiles using various types of technology (Web, Wap, SMS, voice server, etc.). In the absence of certain identification, this access to the profiles can be protected by passwords. Each authority 4 has its own password. If the same authority manages authorizations for several geolocatable devices, the same password can be used at the interface level 14.
- the authorization profile is very specific (based on specific logic of the service using location data), it can be managed directly by the system running the application in question.
- FIGS. 2 and 3 show examples of procedures applicable by the request filter 16 in connection with the interfaces 12, 13, 15 and with the authorization database 18 when receiving a message from request from a user application 2 and upon receipt of a response message from a location server 3, respectively.
- Step 21 represented in FIG. 2 corresponds to the reception of a standard request message on the applications interface 12, in accordance with the communication protocols supported by this interface.
- the interface 12 extracts from this message a certain number of parameters including a type of request specified in the message, a request number, the time of issue or reception of the request, an identifier and a signature of the application.
- user 2 where the message comes from (step 22).
- the application interface 12 examines whether the request carried by the message is a free request, that is to say one that does not require any specific authorization (test 23). If the request is free, it is directly transmitted to the location interface 13 to be sent to a location server 3 (step 24).
- the LDP system performs the authorization procedure at the service level while seeking to authenticate the application 2 from which the message originates (test 25).
- This authentication can relate to the identifier and the signature extracted from the message in step 22.
- the authentication process can include exchanges of additional messages with the user application.
- the application interface 12 returns a refusal message to the application 2 from which the request originates (steps 26 and 27).
- the request is decoded and, if necessary, decrypted by the filter 16 which extracts the list of identifiers of geolocatable devices for which the location data are requested (step 28).
- the filter 16 For each device k identified in the request, the filter 16 consults in the database 18 the authorization profile relating to the application which was identified in step 22, and examines whether each of the authorization conditions defined by this profile is met (test 29). The test is performed on the basis of comparisons relating to the current time (or that extracted from the request in step 22) as well as to various other attributes specified in the profile. Yes some of these authorization conditions relate to data available from an external server 5, the test 29 includes an interrogation of this server 5 through the interface 15 for retrieving the relevant data.
- the request is rejected with respect to this device (step 26).
- This rejection can consist simply in removing the identifier of the device k from the list of the request.
- this identifier can be marked by assigning it an authorization refusal indicator.
- the states of this indicator can possibly identify the cause of the refusal (for example, inadequate request time).
- the choice between the two rejection methods above can be configured by the LDP administrator.
- the devices k for which the request has been rejected can be indicated in a refusal message returned to the application 2 through the interface 12, possibly with the indicators identifying the causes of refusal.
- the request is validated (step 30) with respect to each device k for which access has been authorized by the filter 16 during the test 29.
- a secondary request transmitted by the location interface 13 This transmission is encrypted if encryption is provided on the link with the location server (s) 3. If applicable (if the same server 3 does not provide all the required data), the interface 13 ensures the formatting of several standard requests addressed to several location servers 3.
- the location interface 13 stores an association between the primary request from which it derives, extracted from the initial message in step 22, and this secondary request.
- the interface 13 finds the association of the secondary request with the corresponding primary request in order to allow the subsequent referral of the response to the application concerned (step 32).
- the response is then decoded and, if necessary, decrypted by the filter 16 which extracts the list of identifiers geolocatable devices concerned as well as the corresponding location data which have been supplied by the location server 3 (step 33). If the server 3 was unable to provide the location data of a device k from the list submitted to it (test 34), this failure to respond will be reported to the user application in the response returned by the intermediary. of the interface 12 in step 35. Otherwise, the filter 16 performs a comparison between the location data of the device k and the parameters of the corresponding authorization profile to verify whether the supply of this data to the application is authorized (test 36). If this supply is not authorized, the request is rejected with regard to device k (step 37 similar to step 26 above: deletion of the identifier of device k in the list or marking with an indicator identifying the cause refusal), and the refusal will be reported to the application in step 38.
- the location data to which access was authorized to test 36 are included in the response returned by the interface 12 in step 35, in association with the identifier of the corresponding device k.
- the response or refusal message returned to the application in step 35 or 38 can be encrypted if this is required on the interface 12.
- initial values are allocated to the authorization parameters of the new application / device pair, but the profile thus defined is not yet activated in the database 18.
- the allocation of these initial values can be carried out following the subscription of a subscription to a service rendered by this application relative to one or more geolocatable devices.
- the initial values are for example default values defined by the application concerned. They can also be agreed between the application manager and the subscriber to the service prior to subscription. These initial values can be recorded in the database 18 with a non-activation indicator, or in an annex database, under the control of the administration module of the LDP system or in response to a special request received on the applications interface 12 ; - Then, a confirmation is requested from the access authority 4 assigned to the new application / device pair by means of the confirmation module 19 and the messaging server of the interface 14. If a confirmation is received in response to this request , the module 19 activates the initial profile in the base 18. The profile activated in response to this confirmation may also have been modified beforehand by the access authority 4 via the portal server of the interface 14 and of the module profile management 20. To facilitate this interaction, the parameters of this profile are presented to the access authority 4 in the confirmation request message.
- This two-step procedure ensures flexible management of the implementation of services and facilitates careful control, by holders of geolocatable devices, of the conditions of access to their location data.
- Two non-exclusive methods can be used to trigger a request for confirmation of authorization from a user application 2 for access to the location data of a given geolocation device:
- the LDP system can ensure that permissions denied to a given application are not too frequent. It can thus build indicators of behavior of user applications, usable in the event of abuse (do not launch the confirmation procedure for devices that have already been the subject of a refusal, no longer respond to any request, publish the wrong ones behavioral indicators, etc.).
- a special confirmation request designating a list of devices an application 2 of which will require the location data is detected on the basis of the type of message indicated in the message received on the interface 12.
- This request is passed to the confirmation module 19 which generates the confirmation request and transmits it to the or the competent access authority (ies) via the messaging server of the interface 14.
- the responses are then examined to activate or maintain inactive the authorization profiles concerned in the database 18.
- FIG. 4 illustrates an example of a test procedure which can be executed in place of the test 29 of FIG. 2 and which incorporates a detection of the "new" devices for which confirmation must be requested.
- the request filter 16 first examines (step 41) whether an active authorization profile is active in the database 18 for the application / device pair identified in steps 22 and 28. If so, the different conditions d access described by the active profile are examined in relation to the parameters of the request during test 42, and according to the result of this examination, the request is either validated (step 43) or rejected by indicating the authorization condition (s) which have not been met (step 44).
- the filter 16 determines whether a profile which has not yet been activated has been defined for the application / device pair, that is to say whether an authorization confirmation is awaited for this pair (test 45). .
- the request is rejected, indicating to the application that it relates to a device not registered with it (step 46). If there is a profile not yet activated, the module 19 is warned to send a confirmation request to the access authority of the device (step 47), and the request for location data for the device in question can be either rejected, indicating the reason as represented by step 48, or put on standby for confirmation by the access authority.
- steps 28 to 30 of Figure 2 are not executed in response to the reception of a request message on the applications interface 12.
- the location data is requested from the server (s) 3 for all the devices identified in the primary request authorized at the service level, and the analysis of the authorization conditions for each device k is entirely carried out during test 36 of FIG. 3 (which therefore also relates to the conditions of test 29 of FIG. 2).
- This latter possibility is not very advantageous when the location data is obtained from one or more external servers 3, because it leads to a load on the location servers relative to data which will not be delivered.
- This possibility may however be suitable when the location data are obtained from a local source, such as the location database 6 of the LDP system 10 represented in FIG. 5.
- This variant 10 of the LDP system comprises a certain number of 'elements 12, 14, 18-20 similar to those bearing the same references in Figure 1 (the external interface 15, optional, is absent here).
- the requests for location data extracted from the messages received on the applications interface 12 are processed by a module 7 with regard in particular to the following functions: decoding / decryption of the requests; recovery of the location data of each device concerned in the local database 6; interrogation of the request filter 8 relative to each device concerned, by specifying its location data for the assessment of any conditions of a geographic type; collection of responses (validation / rejection) developed by the filter 8 using the relevant authorization profiles contained in the database 18; consolidation of these responses and reporting to the interface 12.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0103617A FR2822336A1 (en) | 2001-03-16 | 2001-03-16 | System for controlling access to localization data arising from mobile devices, such as mobile phones, such that different user applications have different access authorizations and phone user privacy is protected |
FR01/03617 | 2001-03-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2002076121A1 true WO2002076121A1 (en) | 2002-09-26 |
Family
ID=8861225
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/FR2002/000910 WO2002076121A1 (en) | 2001-03-16 | 2002-03-14 | System for controlling access to data relating to the localization of geolocalizable devices |
Country Status (2)
Country | Link |
---|---|
FR (1) | FR2822336A1 (en) |
WO (1) | WO2002076121A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5748148A (en) * | 1995-09-19 | 1998-05-05 | H.M.W. Consulting, Inc. | Positional information storage and retrieval system and method |
WO1998052379A1 (en) * | 1997-05-16 | 1998-11-19 | Telefonaktiebolaget Lm Ericsson | Integrity protection in a telecommunications system |
WO2000038467A1 (en) * | 1998-12-21 | 2000-06-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for transferring position data between terminals in wireless communications systems |
US6138003A (en) * | 1997-11-26 | 2000-10-24 | Ericsson Inc. | System and method for authorization of location services |
-
2001
- 2001-03-16 FR FR0103617A patent/FR2822336A1/en active Pending
-
2002
- 2002-03-14 WO PCT/FR2002/000910 patent/WO2002076121A1/en not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5748148A (en) * | 1995-09-19 | 1998-05-05 | H.M.W. Consulting, Inc. | Positional information storage and retrieval system and method |
WO1998052379A1 (en) * | 1997-05-16 | 1998-11-19 | Telefonaktiebolaget Lm Ericsson | Integrity protection in a telecommunications system |
US6138003A (en) * | 1997-11-26 | 2000-10-24 | Ericsson Inc. | System and method for authorization of location services |
WO2000038467A1 (en) * | 1998-12-21 | 2000-06-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for transferring position data between terminals in wireless communications systems |
Also Published As
Publication number | Publication date |
---|---|
FR2822336A1 (en) | 2002-09-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3863318A1 (en) | Use of geolocation to improve security while protecting privacy | |
US11387978B2 (en) | Systems and methods for securing access rights to resources using cryptography and the blockchain | |
US8862129B2 (en) | Systems and methods for encrypted mobile voice communications | |
EP2248295B1 (en) | System and method for wireless device based user authentication | |
US9324074B2 (en) | Mobile communication device monitoring systems and methods | |
US10045327B2 (en) | Mobile communication device monitoring systems and methods | |
EP2491735B1 (en) | Device and method for managing access rights to a wireless network | |
EP1683388B1 (en) | Method for managing the security of applications with a security module | |
US9572033B2 (en) | Systems and methods for encrypted mobile voice communications | |
US20060020816A1 (en) | Method and system for managing authentication attempts | |
US20180083943A1 (en) | Geolocation dependent variable authentication | |
FR2864289A1 (en) | Resource access controlling method, involves notifying comparison of biometric data and biometric references of user, to access terminal, by server that communicates simultaneously with terminal and access terminal | |
FR2895611A1 (en) | ARCHITECTURE AND METHOD FOR CONTROLLING INFORMATION TRANSFER BETWEEN USERS | |
FR2932639A1 (en) | TRAFFIC ABNORMALITY DETECTION ISSUED BY A MOBILE TERMINAL IN A RADIO COMMUNICATION NETWORK | |
US8345829B2 (en) | Authentication of a user to a telephonic communication device | |
EP2369780B1 (en) | Method and system for validating a transaction, and corresponding transactional terminal and programme | |
CN107995616B (en) | User behavior data processing method and device | |
EP2348763B1 (en) | Method for authenticating a mobile terminal to access an application server | |
CN106778334A (en) | The guard method of account information and mobile terminal | |
AU2013222127B2 (en) | Systems and methods for encrypted mobile voice communications | |
WO2002076121A1 (en) | System for controlling access to data relating to the localization of geolocalizable devices | |
WO2009132977A1 (en) | Reliable resource integrated in a biometric data control device ensuring inspection security and data security | |
FR2885753A1 (en) | COMMUNICATION METHOD FOR WIRELESS NETWORKS BY MANAGEMENT FRAMES COMPRISING AN ELECTRONIC SIGNATURE | |
EP2299667B1 (en) | Parental control of a mobile terminal | |
EP2489155A1 (en) | Management of a communication device via a telecommunications network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: CONSTATATION DE LA PERTE D UN DROIT CONFORMEMENT A LA REGLE 60(1) CBE |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |