User registration and location management for mobile telecommunications systems

Description

Background of the Invention

[0001] This invention relates to user registration and location management for mobile telecommunications systems. In particular, it relates to Universal Mobile Telecommunications Service (UMTS) systems, when used to provide connectivity between an IP (Internet Protocol) capable end-device and an IP-based network.

[0002] When a UMTS user switches on his mobile terminal (MT), the user needs to be registered with the UMTS network. Similarly, when the user moves around the area covered by the network, location management procedures need to take place in order to allow the user to be provided with services.

[0003] The initial registration process normally involves requesting for registration on the network, authentication of the user by the network, registration of the user and informing the home location register (HLR) of the users current whereabouts. This takes place at the UMTS level.

[0004] At the IP (Internet Protocol) level, there are three scenarios to consider when the user switches on an IP capable terminal. These are:

(1) the user has a static home IP address,

(2) the user requires a dynamic home IP address from the UMTS operator, and

(3) the user requires a dynamic home IP address from a body outside the UMTS domain.

[0005] In any case, a mobile IP registration with the home agent (HA) and perhaps the foreign agent (FA) needs to take place before the user can successfully engage in a data transaction using the Internet Protocol.

[0006] The current solution for the registration of data (IP) users in UMTS with mobile IP relies on the use of two, subsequent, registrations, the first at the UMTS level and the second at the IP level. This is shown in Figure 1.

[0007] The user of a mobile terminal switches on his mobile terminal MT1 and requires registration with the UMTS network. He sends a message 2 requesting registration which passes through a radio network controller (RNC) 3 (which may also be the foreign agent (FA) for the IP protocol) to a switching centre with a visiting location register (VLR) 4. This in turn requests user information from any previous visiting location register 5 which the user may have last received service from, or from the user's home location register (HLR) 6. This sends back information concerning the user to the new VLR 4 and then an authentication request 7 and reply 8 are sent to and received from the mobile terminal 1. After this authentication, registration of the mobile terminal is complete and a register complete message 9 is sent to the terminal. Also, a message 10 is sent to the HLR informing the HLR of the new location of the terminal.

[0008] If IP registration is also required, then a further IP registration step also has to take place with conventional systems.

[0009] Once UMTS registration is complete, the mobile terminal 1 sets up a UMTS data channel 11. The mobile terminal 1 sends an FA router solicitation message 12 to the new RNC/FA 3 and this in turn sends an FA advertisement 13 back to the mobile terminal over the data channel. The mobile terminal then sends a registration request which passes through the RNC/FA 3 and onwards to the home agent 14. This then sends back a registration reply 15 to the mobile terminal and IP registration is complete. The foreign agent FA in IP is analogous to the VLR (visiting location register) in the UMTS domain.

[0010] Accordingly, two independent registration processes are necessary, first the UMTS registration and then the IP registration.

[0011] When a UMTS user moves around the area covered by the network, location management procedures need to take place in order to allow the user to be provided with services. Location management under a single radio network controller (RNC) does not affect the IP level. However, inter-RNC location updates have to involve IP level mobility as well as UMTS mobility. This is because it is assumed that mobile IP foreign agents (FA's) and RNC's are co-located.

[0012] Conventionally, an analogous process to the conventional method of registration has been done. Firstly UMTS location update is done and then, independently, a subsequent IP location update is done. This is shown in Figure 2.

[0013] The location update procedures are similar in principle to the registration updates of Figure 1, except that the location update 16 is required for both IP and UMTS, rather than register updates. Apart from this, the procedures involve similar steps, mutatis mutandis.

[0014] In both the user registration and location management scenarios, the complete separation of the two procedures for UMTS and IP bring inefficiencies in the usage of the air-interface, and delays to the overall registration or location update procedure.

[0015] The present invention arose in an attempt to reduce these inefficiencies and to reduce the time taken for the overall registration procedure or for the overall location update procedure.

[0016] It is known from the paper by Clapton A J et al entitled "UMTS - the mobile part of broadband communications for the next century", BT Technical Journal, GB, BT Laboratories, vol. 16, no. 2, 1 April 1998, pages 120-131, XP000750524 ISSN = 1358 - 3948 to provide a method for a mobile terminal in a UMTS and IP telecommunications network to register and/or update its location.

Brief Summary of the Invention

[0017] The present invention as in Claim 1, is characterised over the disclosure of the Clapton paper by using UMTS messages to transmit IP information for IP registration and/or IP location update.

[0018] Mobile-IP specifications allow for link-layer mechanisms to be used to discover a foreign agent (FA) or to detect a change in the sub-network. In a preferred embodiment of the invention, accordingly, the UMTS level mobility-management (link-layer) is used for FA discovery.

[0019] More specifically, the method may comprise using UMTS 'register request' and 'register complete' messages for detecting FA information.

[0020] Preferably, additional fields of information are sent with the 'register request' message and with the 'register complete' message.

[0021] The fields which may be sent with the 'register request' message are: (1) type of home address, (2) type of COA (care of address), (3) home IP address, (4) home agents address, and (5) last used COA.

[0022] The additional field for the 'register complete' messages may be (1) home address, (2) COA type and (3) COA.

[0023] In further embodiments relating to location management, the UMTS 'location update' and 'location update complete' messages may be used.

[0024] Preferably, extra fields of information are provided in one or both of these messages. The fields which may be attached to the 'location update' message are: (1) home address, (2) COA type and (3) COA.

[0025] The extra fields which may be attached to the 'location update complete' message may comprise any of (1) type and (2) COA.

Description of the Drawings

[0026] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

Figure 1 shows UMTS and IP registration procedures according to the prior art;

Figure 2 shows UMTS and IP location update procedures according to the prior art;

Figure 3 shows an integrated registration procedure according to the present invention; and

Figure 4 shows an integrated location update procedure according to the present invention.

Detailed Description of Preferred Embodiments of the Invention

[0027] Referring to Figure 3, in embodiments of the invention, the UMTS level mobility-management (link-layer) may be used for FA discovery. Accordingly, the UMTS 'register req' and 'register complete' messages are used for discovering the FA care-of-address (COA) or obtaining a co-located COA for a mobile terminal. Thus, in the Figure, when a mobile terminal 1 requires to register with a network, it sends out a modified register request message 30 with the addition of various IP related fields.

[0028] These fields are:

(1) type of home address

(2) type of COA

(3) home IP address (optional)

(4) home agents address (optional)

(5) last used COA (optional)

[0029] Note that if the mobile terminal 1 is not IP capable, then the additional fields are not used.

[0030] More particularly, the fields are the following:

(1) Type: this field identifies to the network if the mobile terminal 1 has a static address or requires a dynamic address from the UMTS operator, or requires a dynamic address from an entity outside the UMTS domain.

(2) Type of COA: this identifies if the mobile terminal is to use a co-located COA or a FA, the address in the COA field depends upon this setting.

(3) Home address: if the mobile is configured with a static home address, this field identifies that address. If the mobile does not have a statically configured home address, this field is omitted.

(4) Home agent: if the mobile has been configured statically with its home agent address, this field identifies it. Otherwise, this field is omitted.

(5) Last used COA: this field contains the mobile's last used COA, if any. Otherwise this field is omitted.

[0031] The 'register req', with attached IP fields is functionally similar to the FA router solicitation 12 of Figure 1.

[0032] The 'register complete' message is, from the IP perspective, the FA advertisement. The additional IP fields in the 'register complete' message are:

(1) home address: home address of the user

(2) type: the type of COA used at present, co-located or foreign agent (FA)

(3) COA: the COA.

[0033] If the user does not have a static address and the UMTS network could not obtain a home address for the user, then the user will be required to use IP level mechanisms to obtain one. The UMTS network will, however, issue the user with the address of the FA or the co-located COA.

[0034] Subsequent to the register complete message 32, the mobile then uses a UMTS data channel to send a mobile-IP registration message 33 to the FA (or direct to the HA in case of a co-located COA). This procedure takes place at the IP level, where a data channel 34 is set up over the UMTS radio interface for carrying IP control messages. The HA (or FA) then transmits a registration reply message 35.

[0035] Figure 4 shows an embodiment of the invention representing an integrated procedure for location management with mobile IP and UMTS. The procedure differs from that of the prior art in that the mobile terminal 40, in its 'location update request' transmission 41 also includes one or more extra fields. The fields are:

(1) home address: home address of the user

(2) type: the type of COA used at present, co-located or foreign agent (FA)

(3) COA: the COA.

[0036] An authentication routine then follows and, once the UMTS level location update is successfully completed, the RNC/FA checks whether a new COA needs to be issued. They can do this because of the information that was presented by the mobile terminal 40 in the 'location update request' message 41. If a new COA needs to be issued, it is attached to a "location update complete" message 42. The extra fields of information required within this message are (1) type and (2) COA. This message is used by the mobile terminal 40 at the IP level, as detection for mobile IP. A data channel is set up and the mobile terminal decides what it needs and whether it needs to do anything in relation to registering with a new FA and HA and this takes place at a registration request step 44. The mobile terminal registers either with a new RNC/FA 46 and with the home agent (HA) 47. If route optimisation is enabled, then the new FA will re-register the user at the old FA.

[0037] Embodiments of the invention accordingly allow a reduction in signalling messages that have to be transmitted across the air interface, during registration or during an inter-RNC location update, and minimise the delay required to complete such location updates. In effect, therefore, valuable network resources are saved and overhead is reduced.

[0038] Embodiments of the invention in general utilise UMTS signalling for detecting changes in the IP sub-network and integration of IP level signalling and UMTS level signalling. The invention may have wider use than the two specific scenarios described (user registration and location management) and may be applied to other scenarios where IP signalling is required.

[0039] Mobile IP information is sent during UMTS signalling for the reasons described above.

Claims

1. A method for a mobile terminal in a UMTS and IP telecommunications network to register and/or update its location characterised by using UMTS messages to transmit IP information for IP registration and/or IP location update.

2. A method according to Claim 1, in which the UMTS messages used to transmit IP information for IP registration are UMTS 'register request' and/or 'register complete' messages.

3. A method as claimed in Claim 2, wherein fields of information relevant to the IP domain are sent with the 'register request' message.

4. A method as claimed in Claim 3, wherein the fields in case the mobile terminal is IP capable are: 1) type of home address, 2) type of care of address COA, and, optionally, any of the following: 3) home IP address, 4) home agents HA address and 5) last used COA.

5. A method as claimed in Claim 4, wherein additional fields of information are sent with the 'register complete' message.

6. A method as claimed in Claim 5, wherein the additional fields comprise in case the mobile terminal is IP capable 1) home address, 2) COA type and 3) COA.

7. A method as claimed in Claim 1, comprising a method for the mobile terminal to update its location, wherein the method comprises using UMTS 'location update' and/or 'location update complete' messages to transmit IP information for IP location update.

8. A method as claimed in Claim 7, wherein fields of information relevant to the IP domain are sent with the 'location update' message.

9. A method as claimed in Claim 8, wherein the fields comprise in case the mobile terminal is IP capable 1) home address, 2) COA type and 3) COA.

10. A method as claimed in any of Claims 7 to 9, wherein additional fields are sent with the 'location update complete' message.

11. A method as claimed in Claim 10, wherein the additional fields comprise in case the mobile terminal is IP capable 1) type and 2) COA.

Ansprüche

1. Verfahren für einen mobilen Terminal in einem UMTS- und IP-Telekommunikationsnetz zum Registrieren und/oder Aktualisieren seines Aufenthaltsbereiches, dadurch gekennzeichnet, dass UMTS-Mitteilungen verwendet werden, um IP-Informationen zur IP-Registrierung und/oder zur IP-Aufenthaltsbereichsaktualisierung zu übertragen.

2. Verfahren nach Anspruch 1, bei welchem die verwendeten UMTS-Mitteilungen, um IP-Informationen zur IP-Registrierung zu übertragen, UMTS-Mitteilungen zur "Verzeichnisanforderung" und/oder zum "Verzeichnisabschluss" sind.

3. Verfahren nach Anspruch 2, wobei Informationsfelder bezüglich der IP-Domäne mit der Mitteilung zur "Verzeichnisanforderung" gesendet werden.

4. Verfahren nach Anspruch 3, wobei die Felder, falls der mobile Terminal IP-fähig ist, die folgenden sind: 1) Art der Heimatadresse, 2) Art der Careof-Adresse COA, und optional irgendeines der folgenden: 3) IP-Heimatadresse, 4) Adresse der Heimatagenten HA, und 5) zuletzt verwendete COA.

5. Verfahren nach Anspruch 4, wobei zusätzliche Informationsfelder mit der Mitteilung "Verzeichnisabschluss" gesendet werden.

6. Verfahren nach Anspruch 5, wobei die zusätzlichen Informationsfelder, falls der mobile Terminal IP-fähig ist, die folgenden umfassen: 1) Heimatadresse, 2) COA-Art und 3) COA.

7. Verfahren nach Anspruch 1, ein Verfahren für den mobilen Terminal zum Aktualisieren seines Aufenthaltsbereiches umfassend, wobei das Verfahren das Verwenden der UMTS-Mitteilungen "Aufenthaltsbereichsaktualisierung" und/oder "Abschluss der Aufenthaltsbereichsaktualisierung" umfasst, um IP-Informationen zur IP-Aufenthaltsbereichsaktualisierung zu übertragen.

8. Verfahren nach Anspruch 7, wobei die für die IP-Domäne relevanten Informationsfelder mit der Mitteilung "Aufenthaltsbereichsaktualisierung" gesendet werden.

9. Verfahren nach Anspruch 8, wobei die Felder, falls der mobile Terminal IP-fähig ist, die folgenden umfassen: 1) Heimatadresse, 2) COA-Art und 3) COA.

10. Verfahren nach einem der Ansprüche 7 bis 9, wobei zusätzliche Felder mit der Mitteilung "Abschluss der Aufenthaltsbereichsaktualisierung" gesendet werden.

11. Verfahren nach Anspruch 10, wobei die zusätzlichen Felder, falls der mobile Terminal IP-fähig ist, umfassen: 1) Art und 2) COA.

Revendications

1. Procédé pour un terminal mobile dans un réseau de télécommunications UMTS et IP en vue d'enregistrer et/ou de mettre à jour sa position, caractérisé par l'utilisation de messages UMTS pour transmettre des informations IP pour l'enregistrement IP et/ou la mise à jour de la position IP.

2. Procédé selon la revendication 1, dans lequel les messages UMTS utilisés pour transmettre des informations IP pour l'enregistrement IP sont des messages UMTS de type « demande d'enregistrement » et/ou « enregistrement terminé ».

3. Procédé selon la revendication 2, dans lequel des champs d'informations appropriés au domaine IP sont envoyés avec le message de type « demande d'enregistrement ».

4. Procédé selon la revendication 3, dans lequel les champs, dans le cas où le terminal mobile est compatible IP, sont : 1) le type d'adresse mère, 2) le type d'adresse temporaire COA, et, éventuellement l'une quelconque parmi : 3) l'adresse nominale IP, 4) l'adresse d'agents mères HA et 5) la dernière COA utilisée.

5. Procédé selon la revendication 4, dans lequel des champs d'informations supplémentaires sont envoyés avec le message de type « enregistrement terminé ».

6. Procédé selon la revendication 5, dans lequel les champs supplémentaires comprennent, dans le cas où le terminal est compatible IP : 1) l'adresse mère, 2) le type de COA et 3) la COA.

7. Procédé selon la revendication 1, comprenant un procédé permettant au terminal mobile de mettre à jour sa position, le procédé comprenant l'utilisation de messages UMTS de type « mise à jour de la position » et/ou « mise à jour de la position terminée » pour transmettre les informations IP pour la mise à jour de la position IP.

8. Procédé selon la revendication 7, dans lequel des champs d'information appropriés au domaine IP sont envoyés avec le message de type « mise à jour de la position ».

9. Procédé selon la revendication 8, dans lequel les champs comprennent, dans le cas où le terminal mobile est compatible IP 1) l'adresse mère, 2) le type de COA et 3) la COA.

10. Procédé selon l'une quelconque des revendications 7 à 9, dans lequel des champs supplémentaires sont envoyés avec le message de type « mise à jour de la position terminée ».

11. Procédé selon la revendication 10, dans lequel les champs supplémentaires comprennent, dans le cas où le terminal mobile est compatible IP 1) le type et 2) la COA.

Drawing