+

WO2003001818A2 - Systemes de telecommunication - Google Patents

Systemes de telecommunication Download PDF

Info

Publication number
WO2003001818A2
WO2003001818A2 PCT/GB2002/002624 GB0202624W WO03001818A2 WO 2003001818 A2 WO2003001818 A2 WO 2003001818A2 GB 0202624 W GB0202624 W GB 0202624W WO 03001818 A2 WO03001818 A2 WO 03001818A2
Authority
WO
WIPO (PCT)
Prior art keywords
les
location
request
mtl
network
Prior art date
Application number
PCT/GB2002/002624
Other languages
English (en)
Other versions
WO2003001818A3 (fr
Inventor
Leanne Beavis
Paul Strickland
Adrian Razey
Patrick Slaats
Original Assignee
Vodafone Group Plc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vodafone Group Plc filed Critical Vodafone Group Plc
Priority to AU2002345152A priority Critical patent/AU2002345152A1/en
Publication of WO2003001818A2 publication Critical patent/WO2003001818A2/fr
Publication of WO2003001818A3 publication Critical patent/WO2003001818A3/fr

Links

Classifications

    • 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
    • H04W8/10—Mobility data transfer between location register and external networks

Definitions

  • the invention relates to a telecommunication system having a plurality of mobile terminals.
  • the invention also relates to a mobile telecommunications system, comprising a plurality of mobile telephone networks and a plurality of mobile terminals, each mobile terminal being registered with one of the networks ("home network”) and being able to roam to another of the networks (“visited network”).
  • a telecommunication system embodying the invention enables access to or by a user of the system to be controlled and the privacy of the user within the system to be protected.
  • the system may be a mobile telecommunications or telephone system, particularly a system comprising networks operated by different network operators and between which a user may roam.
  • the system as first set forth above is characterised by including authenticating means responsive to a request ("location request") coming from a third party outside the system and relating to the location of a specified one of the mobile te ⁇ ninals for authenticating the allowability of the location request against a plurality of pretermined criteria, and location determining means responsive to receipt of the location request after authentication by the authentication means ("authenticated location request") for initiating determination of the location of the specified mobile terminal, the authentication means and the location determining means being functionally separate within the system.
  • authenticating means responsive to a request (“location request") coming from a third party outside the system and relating to the location of a specified one of the mobile te ⁇ ninals for authenticating the allowability of the location request against a plurality of pretermined criteria
  • location determining means responsive to receipt of the location request after authentication by the authentication means ("authenticated location request") for initiating determination of the location of the specified mobile terminal, the authentication means and the location determining means being functionally separate within the system.
  • the system as second set forth above is characterised by a respective authentication means in each network responsive to a request ("location request") coming from a third party outside the system and relating to the location of a specified one of the mobile terminals registered with that network for authenticating that location request according to predetermined criteria, and location determining means in each network responsive to receipt of an authenticated location request for at least initiating determination of the location of the specified mobile terminal, in which a location request in respect of a specified one of the mobile terminals roaming in a visited network (“visiting mobile terminal”) is sent to the authentication means of the home network of the visiting mobile terminal for authentication there in accordance with the predetermined criteria, and the location determining means in the visited network is responsive to the authenticated location request.
  • location request a request coming from a third party outside the system and relating to the location of a specified one of the mobile terminals registered with that network for authenticating that location request according to predetermined criteria
  • location determining means in each network responsive to receipt of an authenticated location request for at least initiating determination of the location of
  • the system as second set forth above is characterised by a respective authentication means in each network responsive to an authentication request coming from a third party outside the system and relating to a specified one of the mobile terminals registered with that network for authenticating that request according to predetermined criteria, in which an authentication request received by the authentication means of one of the networks with which the mobile terminal is not registered is passed to the authentication means of the network with which the mobile terminal is registered for authentication in accordance with the predetermined criteria, and including means associated with each authentication means for registering the identity or identities of the other authentication means in the system, and in which each authentication means is only responsive to an authentication request received from another authentication means if that other authentication means is registered with it.
  • Figure 1 is a schematic diagram of one of the systems; and Figure 2 is a schematic diagram of another of the systems.
  • the system to be described with reference to Figure 1 comprises a mobile telephone system enabling services to be provided to or in respect of a user in the system in dependence on the physical location of the user.
  • the term "user” normally involves an individual in physical possession of a mobile terminal (a mobile telephone handset) but includes a mobile terminal apparatus mounted in a moving vehicle. Examples of the types of service which could be provided to such a user are as follows:-
  • services specifically requested by the user such as information advising the user of the nearest restaurant, or the nearest restaurant of a particular type, to their present location, the nearest retail outlet of a particular type or belonging to a particular chain of retail outlets, or the nearest cinema showing a particular film;
  • ASP application service provider
  • the user will have registered with a particular ASP for provision of the particular service.
  • a user may have registered with a particular ASP in order to be provided with information informing them of the nearest restaurant of a particular type.
  • the user may activate the service by a specific request to the ASP.
  • the ASP could automatically provide the information to the user each time the user was in the region of a particular restaurant or of a restaurant of a particular type or within a particular group.
  • the user would register with an ASP providing such a service and would provide the ASP with a list of their particular friends, and could then at any time make an active request for the location of the friends on the list.
  • the user would have registered with a particular ASP, asking to be provided with information on discount offers provided by particular types of retail outlet.
  • the ASP might be operated directly by the fleet operator who would be able to initiate requests for the location of the vehicles in the fleet.
  • the ASP In order to perform these services, the ASP requires information concerning the physical location of the relevant user or users. This information is known to and can thus be provided to the ASP by the network operator. However, two important factors, at least, must be taken into account. First, the provision of location information relating to a user involves privacy considerations - the user's location should not be divulged in an uncontrolled manner; and, secondly, the user's location is valuable information and the network operator may wish to levy a charge for its provision. In a manner now to be described, the network incorporates a location enabling server (LES) which controls the provision of user location infonnation.
  • LES location enabling server
  • FIG. 1 shows in diagrammatic form a mobile telephone network 10 in which mobile users MT are located, of which one is shown (MTl).
  • the network is assumed to be of the GSM or 3G type having a home location register HLR, base station controllers (BSCs), of which one is shown by way of example, which are associated with respective cells of the network and transmit information to and receive information from MTs in that cell.
  • BSCs base station controllers
  • the BSCs are arranged in groups each controlled by a respective MSC, the current location of each MTs being stored in the HLR.
  • an application service provider ASP1 can be accessed from the network 10 via the internet through a suitable gateway G/Wl (e.g. a WAP gateway) provided by the network 10.
  • G/Wl e.g. a WAP gateway
  • ASP1 could provide a friends-finding service to which the MTl user has subscribed. If MTl wishes to initiate this service, MTl will access ASP 1 through gateway G/Wl .
  • ASP1 will need to be provided with the physical location of MTl.
  • Network 10 includes a location server LSI which, when activated, accesses the HLR and obtains the necessary information. In a manner now to be described, however, the provision of the location information is controlled by a location enabling server LES1.
  • the ASP In order to be able to request location information of a particular MT, the ASP must clearly be able to identify the MT to the network 10. Such identification could be provided using the telephone number (MSISDN or IMSI) of the MT. However, the network operator 10 may wish to restrict divulgation of the MSISDN to the ASP (because the ASP could use the MSISDN to obtain direct access to the MS). Therefore, if MTl in this example accesses ASP1 via gateway G/Wl, the gateway will convert the user's MSISDN into a "session ID" (SID), which may be an encrypted form of the MSISDN. It will be the SID which will be therefore received by the ASP 1. In this case, the user may be required to log in in a suitable way with ASPl which will thus be able to identify the user - that is, at least sufficiently to identify the user to establish that the user is a subscriber to the friends finding service (in this example).
  • SID session ID
  • the user may access ASPl using the MSISDN.
  • a different gateway such as gateway G/W2 which is not a gateway maintained by the operator of network 10
  • G/W2 will access ASPl using the MSISDN of MTl.
  • ASPl now transmits a request for the location of MTl to network 10. This request is transmitted to LES1.
  • the location request may identify the user by means of the SID (normally if the initial enquiry has been received via G/Wl) or in terms of the user's MSISDN (normally if the initial request has been received by another gateway such as G/W2). In either case, LES1 will be able to identify the user; if the initial request received by ASPl is based on the SID, the user's MSISDN will be known to LES1 because this information will be available within network 10.
  • LES1 now subjects the location request to an analysis and checking process to determine whether to authenticate the request.
  • a location request in principle has a number of key attributes which are used in the processes carried out in LES1, as follows :-
  • the location request in relation to a particular user, the location request is considered to be "active" when it has been initiated by the action of that user - such as when the user requests information on the nearest restaurant or when the user requests the location of the "friends" on their list in a friend-finder service; and is considered to be “passive” when, in relation to that user, the request has been initiated other than by that user - such as by a third party, for example the user is on the "friends" list of the third party who has initiated a friend-finder service, or the request has been initiated as part of a fleet management service.
  • Anonymity the request may be "open” in that it is based on the user's MSISDN (or IMSI) or may be "private” if it is based on a SID.
  • (c) Service the request will be in respect of a particular service provided by a particular ASP and for each such service it may be specified whether for a particular user the request is permitted to be active or passive (or both), and open or private (or both).
  • LESl refers to a table (Table 1, Figure 1) which lists ASPs, which are authorised to make location requests and to receive location information, and the services which they operate. Entries in Table 1 are controlled by the operator of network 10 and subject to commercial agreement between the network operator and each ASP. These agreements will include provisions and safeguards relating to user privacy and confidentiality and also limitations on the use which the ASP may make of the location information. Table 1 not only includes entries in respect of each ASP but may have different entries for different services which may be provided by the ASP, and the entries will identify users for which the ASP may request location information.
  • Table 1 thus carries out an initial level of "filtering" on the location request received from ASPl .
  • LESl responds to the location request from ASPl by checking in Table 1 that ASPl is an authorised ASP and, then, checking that the service in respect of which the location request is made by ASPl is also authorised by means of an entry in Table 1.
  • the entries in Table 1 may indicate whether the service is used in active or passive mode.
  • the second level of filtering is a more detailed privacy check which is carried out on the basis of entries in a privacy table, Table 2.
  • Table 2 has privacy entries (to be explained in more detail below) for each service entry in Table 1.
  • LESl In response to the location request, LESl now checks the appropriate entries in Table 2. Thus, for example, there could be four different sub-sets of entries as follows for each service or ASP for a particular user:
  • the LESl establishes whether, in relation to a particular location request for the location of a particular user in respect of a particular service, the request is to be authenticated and accepted.
  • Authentication of the location request in relation to a particular user by LESl may also be subject to further checks.
  • the user may be able to apply different privacy conditions at different times of day or week.
  • a particular user could ensure that location requests were only accepted during working hours.
  • LESl determines, after carrying out all the necessary checks as outlined above, that the request is authenticated and is to be accepted, it instructs the location server LSI accordingly. LSI then obtains the location information from the network and transmits this information back to ASPl, which can then initiate or provide the requested service.
  • LSI may, however, be subject to overall control by entries, in relation to each of the users, in the HLR. Thus, a particular user could advise the network that no location requests at all were to be accepted (e.g. permanently, or temporarily). Any such settings in the HLR would also be checked by LSI before acceding to the location request.
  • the location enabling server LESl and the location server LSI are functionally separate. In this way, therefore, the location enabling servers can be produced as separate standardised entities and then used within networks having different types of location servers to which the location enabling servers would be inter-connected using appropriate interfaces.
  • FIG. 2 shows the network 10 of Figure in simplified form, which is assumed to be the "home" network of user MTl. As shown in Figure 2, MTl is roaming into a visited network 10A. It will initially be assumed that user MTl wishes to use a service provided by ASPl (which will be assumed to be an ASP registered with network 10, the home network).
  • MTl may access ASPl through the Internet gateway H/G/W of the home network 10 or may set up such access through a different gateway such as gateway V/G/W of the visited network 10A.
  • gateway H/GW the location request received by ASPl will be based on a SID which will be generated by the gateway.
  • the request will be based on the MSISDN.
  • ASPl will know from the SID or MSISDN that the requesting user MTl is registered with network 10, and will therefore generate a location request, for the location of user MTl, which will be passed to the location enabling server H/LES of the home network 10.
  • Table 2 will contain an additional set of entries.
  • the set of entries in Table 2 described above with reference to Figure 1 relates to the case where the ASP (ASPl) is registered with the home network and the user (MTl) is located within the home network.
  • Table 2 would include an additional set of entries relating to the case shown in Figure 2 - where ASPl is registered with the home network 10 and the user MTl is roaming. Therefore, the user could set up particular privacy settings applicable to the case numbering described with reference to Figure 2.
  • H/LES determines, after carrying out all the necessary checks, that the location request can be accepted, the request is passed to the location server LS in the home network. This request will identify the user by their MSISDN. If the location request as issued by ASPl is in terms of a SID, this will be converted into the MSISDN by the H/LES.
  • the location server H/LS will be advised by the network (by the HLR) that the identified user is roaming in a different network, and the response will identify the visitor location register of the network where the user is roaming - this will, of course, be V/VLR in network 10A.
  • the response issued to H/LS may also include the address of the cell where MTl is currently located H/LS will pass this information to H/LES.
  • any user privacy settings held as part of the user's profile in the HLR will also be checked.
  • the settings may indicate that the user has decided to refuse all location requests at that time or has decided to refuse location requests of a type including the current location request. If this is the case, H LS will advise H/LES and H/LES will terminate the location request and inform ASPl accordingly.
  • the H/LES will now pass the location request to the LES (V/LES) in the visited network 10A - that H/LES will be able to identify V/LES as the LES which is to be addressed because the latter' s identity can be derived from the address of the VLR which will be advised to H/LES by H/LS.
  • V/LES LES
  • the location request passed to V LES will include the MSISDN of MTl and the VLR address in network 10A and, where available, the identity of the relevant cell.
  • V/LES in the visited network will not, normally, contain any privacy information relating to user MTl.
  • each LES in the system will store the identities of other LESs which have been pre-approved for location requests.
  • the identities (IP addresses) of "approved" LESs may be stored as part of Table 1 for LES 1, corresponding to Table 1 shown in Figure 1. Therefore, in the present example, V/LES merely has to check that H/LES is included in this list. Because H/LES is on the "approved" list held by V/LES, V/LES can assume that the necessary privacy checks have been carried out.
  • V/LES now passes the location request to the location service V/LS in the visited network 10 A, this request being based on the MSISDN of MTl and will also include the appropriate address in the VLR.
  • the VLR will carry out its own privacy check - to check whether MTl has indicated that no location requests are to be accepted (or that this particular type of location request is not to be accepted). If no such privacy block has been made, the location details are obtained by V/LS and passed back to V/LES and then to H/LES in network 10, via the internet. H/LES associates the response with the original request and the information is then returned to ASPl .
  • the location request is an "active" request - that is, it originated from action by MTl .
  • a "passive" location request is made in respect of user MTl.
  • This location request may originate in a number of ways - for example, it may originate from another MT which wishes to initiate a friend-finding service in respect of its list of friends which includes MTl.
  • ASPl will thus issue a location request in respect of MTl, which will normally be based on a SID for MTl.
  • This request will be sent to the LES in the home network 10 via gateway H/GW.
  • the form of the SID will ensure that the location request is directed to network 10.
  • the SID will be converted into MTl's MSISDN and passed to H/LES
  • the privacy settings for MTl will be checked in H LES in the manner already described. If these settings are such that the location request is prohibited, an appropriate response will be returned to ASPl. If the location request is accepted, however, it will be passed to H/LS. In response to this request, the HLR will advise that MTl is roaming in network 10A and will provide the VLR address of MTl . This information is passed back to the H/LES by H/LS. H/LES now passes on the location request to V/LES in the visited network 10A.
  • the location of MTl is then obtained from the VLR by the VLS (assuming that the privacy settings for MTl in the VLR are not blocking the request), and the location of MTl is then passed back to ASPl via V/LES and H LES.
  • the location request is an active request generated by MTl in respect of a service provided by ASP2.
  • This request will be passed to ASP2 via gateway V/G/W in the visited network or perhaps by gateway H/G/W in the home network.
  • the request may be passed to ASP2 on the basis of a SID which will be generated by the gateway.
  • ASP2 After carrying out its own check in respect of the location request, ASP2 passes the location request to the visited V/LES - because ASP2 is registered with network 10 A. V/LES will check its Table 1 to ensure that ASP2 is properly registered with network 10 A. If the request is based on a SID generated by V/G/W, then V/LES will be able to translate the SID into the MSISDN of user MTl. If the SID is generated by encryption of the user's MSISDN by means of an algorithm known to both H/G/W and V/G/W, then V/LES will be able to translate the SID into the MSISDN of user MTl if the SID has been generated by V/G/W or if it has been generated by H/G/W.
  • H/G/W will not convert the user's MSISDN into a SID.
  • V/LES will know the MSISDN of MTl .
  • V/LES will be aware, from the MSISDN, that MTl is registered with network 10, and will now pass the location request to H/LES in the home network 10. The request will be passed to H LES with additional information, including information identifying ASP2. From its Table 1, H/LES will be able to check the authenticity of V/LES in the visited network 10A. H/LES, the privacy settings in respect of user MTl will be checked in the manner already described. If the settings are such that the location request is to be rejected, an appropriate response will be sent back to V/LES in the visited network 10 A and thence to ASP2.
  • the location request is to be accepted, it will be passed by H LES to H/LS in the home network 10.
  • the HLR will confirm that MTl is roaming in network 10A and will provide the relevant address in the VLR in the visited network 10 A. This information will be passed back to H/LES by H LS.
  • V/LES On receipt of the location request and the associated information from H/LES, V/LES passes the request to V/LS in the visited network which accesses the appropriate address in the VLR. Again, any privacy settings set in the VLR by MTl are checked. If these do not prohibit the location request, the location details of MTl are obtained by V/LS and passed back to V/LES. These location details are then passed by V/LES to H/LES in the home network 10. H LES in the home network now sends the location request back to V/LES in the visited network where it is associated with the original request. The location details are now passed back to ASP2. At this stage, the MSISDN may be translated back to the original SID.
  • ASP2 will thus issue a location request in respect of MTl, which will normally be based on a SID for MTl .
  • This request will be sent to V LES in the visited network 10 because ASP2 is registered with network 10A.
  • V LES will first check that ASP2 is in fact registered with it. It will then decide from the form of the SID that MTl is registered with the home network 10 and will pass the request to H/LES.
  • Gateway H/G/W will convert the SID into MTl's MSISDN. The privacy settings for MTl will be checked in H/LES in the manner already described.
  • V/LES If these settings are such that the location request is prohibited, an appropriate response will be returned to ASP2 via V/LES. If the location request is accepted, however, it will be passed to H/LS. In response to this request, the HLR will advise that MTl is roaming in network 10A and will provide the VLR address of MTl . This information is passed back to the H/LES. H/LES now returns the location request to V/LES in the visited network 10A together with the associated information identifying the relevant VLR address. In the manner already described, the location of MTl is then obtained from the VLR by V/LS (assuming that the privacy settings for MTl in the VLR are not blocking the request), and the location of MTl is then passed back to V/LES. V/LES now passes this information to H/LES which returns it to V/LES so that it can be associated with the original request and V/LES then passes the authenticated request to ASP2.
  • the receiving LES merely has to confirm that the transmitting LES is already registered with it. It can then trust the received information.
  • the system shown in Figure 2 may also be used for carrying out authentication requests not related to the location of the user MTl but instead relating to some non-location based characteristic.
  • ASPl or ASP2 may request information relating to the credit rating of user MTl.
  • the request will initially be passed by ASPl to H/LES or by ASP2 to V/LES.
  • V/LES will identify MTl as being registered with the home network and will pass the request to H LES.
  • H LES will subject the request to the privacy checks described above with reference to Figure 1 and, for example, Table 2 A, using privacy settings applicable to the user in respect of which the authentication request is made and to the other criteria already described.
  • the receiving LES merely has to confirm that the transmitting LES is already registered with it. It can then trust the received information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention se rapporte à un système de téléphonie mobile comportant un réseau (10) qui fait office de réseau principal d'un terminal mobile (MT1) qui se déplace dans un réseau visité (10A). Un fournisseur de services d'applications (ASP1) enregistré dans le réseau principal (10) envoie une demande d'emplacement portant sur l'emplacement du terminal mobile visiteur (NT1) à un serveur d'autorisation d'emplacement (H/LES) dans le réseau principal (10). A ce moment-là, l'authenticité de l'ASP est vérifiée. Ensuite, l'autorisation de la demande d'emplacement est vérifiée par le serveur d'autorisation d'emplacement (H/LES) en fonction de plusieurs critères prédéterminés comportant des paramètres de confidentialité installés par ou selon le terminal mobile particulier (MT1). Si ces critères sont satisfaisants, la demande d'emplacement authentifiée est transmise vers un serveur d'emplacement (H/LS) dans le réseau principal (10) qui détermine le réseau (10A) dans lequel le terminal se déplace ainsi que l'adresse correspondante dans le VRL de ce réseau (10A). La demande d'emplacement authentifiée, au moyen de l'adresse VLR, est ensuite transmise vers le serveur d'autorisation d'emplacement (V/LES) dans le réseau visité (10A) puis vers le serveur d'emplacement (V/LS) dans ce réseau qui obtient l'emplacement du terminal. Cette demande est ensuite renvoyée vers le fournisseur de services d'application (ASP1). Chaque serveur d'autorisation d'emplacement tient à jour un registre des identités des autres serveurs d'autorisation d'emplacement dans le système afin de lui permettre d'authentifier les demandes d'emplacement reçues depuis ces serveurs. Lesdits serveurs d'autorisation d'emplacement (H/LES ; V/LES) sont fonctionnellement séparés des serveurs d'emplacement (H/LS ; V/LS).
PCT/GB2002/002624 2001-06-21 2002-05-31 Systemes de telecommunication WO2003001818A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002345152A AU2002345152A1 (en) 2001-06-21 2002-05-31 Telecommunications systems

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0115206.5 2001-06-21
GB0115206A GB2376846B (en) 2001-06-21 2001-06-21 Telecommunication systems and methods

Publications (2)

Publication Number Publication Date
WO2003001818A2 true WO2003001818A2 (fr) 2003-01-03
WO2003001818A3 WO2003001818A3 (fr) 2003-05-08

Family

ID=9917094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2002/002624 WO2003001818A2 (fr) 2001-06-21 2002-05-31 Systemes de telecommunication

Country Status (3)

Country Link
AU (1) AU2002345152A1 (fr)
GB (1) GB2376846B (fr)
WO (1) WO2003001818A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004089004A1 (fr) * 2003-04-02 2004-10-14 Huawei Technologies Co., Ltd. Procede de protection d'informations relatives a la localisation dans un service de localisation
KR101181598B1 (ko) 2006-06-09 2012-09-10 삼성전자주식회사 목표단말기의 주기적 위치 정보 제공 방법 및 시스템

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5329573A (en) * 1991-11-27 1994-07-12 At&T Bell Laboratories Arrangement for obtaining authentication key parameters in a cellular mobile telecommunications switching network
US6138003A (en) * 1997-11-26 2000-10-24 Ericsson Inc. System and method for authorization of location services
SE513773C2 (sv) * 1999-03-19 2000-11-06 Ericsson Telefon Ab L M Metod och system för elektronisk handel
GB2350971A (en) * 1999-06-07 2000-12-13 Nokia Mobile Phones Ltd Security Architecture

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004089004A1 (fr) * 2003-04-02 2004-10-14 Huawei Technologies Co., Ltd. Procede de protection d'informations relatives a la localisation dans un service de localisation
KR101181598B1 (ko) 2006-06-09 2012-09-10 삼성전자주식회사 목표단말기의 주기적 위치 정보 제공 방법 및 시스템

Also Published As

Publication number Publication date
AU2002345152A1 (en) 2003-01-08
GB2376846A (en) 2002-12-24
GB2376846B (en) 2005-08-03
WO2003001818A3 (fr) 2003-05-08
GB0115206D0 (en) 2001-08-15

Similar Documents

Publication Publication Date Title
EP1446978B1 (fr) Systeme de telecommunications et procede de controle de la confidentialite
CA2290356C (fr) Protection de l'integrite dans un systeme de telecommunications
US7289805B2 (en) Method and system for providing a temporary subscriber identity to a roaming mobile communications device
US7280820B2 (en) System and method for authentication in a mobile communications system
KR100559284B1 (ko) 이동국에 대한 포지셔닝을 인증하기 위한 원격 통신 시스템 및 방법
JP4777314B2 (ja) 位置情報を提供する方法
EP1166497B1 (fr) Acces internet mobile
KR20020044088A (ko) 모빌 유닛이 로밍하고 있을 때 콜 수신을 제한하는 방법및 장치
US20100056102A1 (en) Open to all prepaid roaming systems and methods
US6363151B1 (en) Method and system for subscriber authentification and/or encryption of items of information
EP1188287B1 (fr) Determination de la position d'un terminal mobile
US7636845B2 (en) System for preventing IP allocation to cloned mobile communication terminal
JP3854148B2 (ja) 識別確認情報を選択する方法及び装置
US7369860B2 (en) Data protection for position-dependent services
WO2003001818A2 (fr) Systemes de telecommunication
RU2282952C2 (ru) Способ запроса для получения согласия на определение местоположения мобильного устройства радиосвязи и соответствующая сеть мобильной связи
EP1413160A1 (fr) Systeme, procede et carte a puce d'acces a une pluralite de reseaux
EP1856936A1 (fr) Procede et systeme de communication
MXPA02002502A (es) Metodo y proceso para validar el servicio roaming de usuarios celulares internacionales.

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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: A2

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
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

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

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载