CN101051968A - Method and device for keeping terminal online forever - Google Patents

Abstract

The invention discloses a method and device for keeping a terminal always online, which is used to solve the problem that the terminal still uses the IP information allocated from the source network to carry out follow-up services after roaming from the source network to the destination network. The method of the present invention includes: A. After the terminal roams from the source-side network to the destination-side network, the source-side network carries the IP information allocated to the terminal in the source-side network in the message interacted with the destination-side network; B. The destination-side network Perform user plane routing update for the terminal by using the IP information carried in the interaction message. Through the implementation of the present invention, the terminal can remain online forever.

Description

Method and device for keeping terminal always online

technical field

The invention relates to the field of wireless communication, in particular to a method and a device for keeping a terminal always online.

Background technique

In the existing 3GPP network, if the terminal wants to perform data services, it must first attach to the network; after the Attach is successful, initiate an activation request to obtain an IP address; use the obtained IP address to perform related data services .

Combined with 3GPP network elements, that is, the terminal first initiates Attach, the SGSN in the 3GPP network will obtain the subscription data of the terminal from the home location register HLR, and then the SGSN will authenticate with the terminal on the wireless side. After the encrypted identity is confirmed, the terminal is allowed to attached. Next, if the terminal wants to perform data services, it sends an Active request to the SGSN through the wireless device; the SGSN encapsulates the corresponding information in the activation user context request, and sends it to the gateway GPRS support node GGSN; after the GGSN judges that the corresponding information is correct, send it to The terminal allocates an IP address, encapsulates the IP address in an activation success response message and sends it to the SGSN. In this way, after the terminal obtains the IP address, it can perform external network services.

In the SAE of the next generation network, there is also the concept of IP address, and it is also necessary to uniquely identify a terminal node through the IP address to perform corresponding services.

In the process of roaming from the 3GPP network to the SAE network (and vice versa), if the terminal roams from the attached state (without an IP address) to the SAE network, the subsequent IP address can be reassigned in the SAE network. Business. However, the terminal has been assigned an IP address in the source-side 3GPP network. When directly accessing the destination-side SAE network, should it obtain an IP address from the SAE network for services, or use the IP address assigned in the source-side 3GPP network? , there is no conclusion and corresponding implementation method yet.

However, it is obvious that the terminal has already been assigned an IP address in the 3GPP network on the source side. When directly accessing the SAE network on the destination side, if the terminal obtains an IP address from the SAE network to perform services, it will not be able to continue the previous services, and it will also cause The online interruption of the terminal increases the overhead of process and signaling interaction.

Contents of the invention

The present invention provides a method and device for keeping a terminal always online, so as to solve the problem that the terminal still uses the IP information allocated from the source network to carry out follow-up services after roaming from the source network to the destination network.

The inventive method comprises:

A. After the terminal roams from the source-side network to the destination-side network, the source-side network carries the IP information assigned to the terminal in the source-side network in the message interacted with the destination-side network;

B. The destination network uses the IP information carried in the interaction message to update the user plane route for the terminal.

Wherein, the source-side network is a 3GPP network, and the destination-side network is a system architecture evolution SAE network.

The 3GPP network carries the IP information in the user context transfer message sent to the SAE network.

After the SAE network receives the user context transfer message and before the terminal completes the registration, it updates the user plane route for the terminal. Or, after the SAE network registers the terminal, it updates the user plane route for the terminal.

Wherein, the source-side network is an SAE network, and the destination-side network is a system architecture evolution 3GPP network.

The SAE network carries the IP information in the user context transfer message sent to the 3GPP network.

After the 3GPP network receives the user context transfer message and before the terminal completes the registration, it updates the user plane route for the terminal. Or, after registering the terminal, the 3GPP network updates the user plane route for the terminal.

A device according to the present invention includes: an encapsulation unit, configured to encapsulate the terminal in the network where the device is located in the message exchanged between the network where the device is located and the network at the destination side when the terminal roams from the network where the device is located to the network where the device is located Assigned IP information.

Another device of the present invention includes: a parsing unit, configured to parse out, from the received message, the IP information allocated in the source-side network by the terminal roaming to the network where the device is located.

The beneficial effects of the present invention are as follows:

Since the terminal roams from the source-side network to the destination-side network, the source-side network will exchange messages with the destination-side network to complete network switching, so the method of the present invention carries this information in the message exchanged between the source-side network and the destination-side network The IP information assigned to the terminal in the source network, so that the destination network can know the IP information assigned to the terminal in the source network, and use the IP information to update the user plane route for the terminal for subsequent services . Therefore, after the terminal roams to the destination network, the destination network does not need to re-allocate the IP for the terminal, which obviously saves the IP allocation process of the destination network and the overhead of signaling interaction between the destination network and the terminal. During the roaming process, the terminal always uses the IP information allocated in the source-side network, and the network side also always uses this information to transmit services for the terminal, so the terminal can remain online forever.

In order to support the method of the present invention, the present invention further provides two devices, which are respectively used for encapsulating source-side network IP information and analyzing the encapsulated IP information.

Description of drawings

Fig. 1 is a flowchart of the method steps of the present invention;

FIG. 2 is a schematic diagram of a terminal roaming between a 3GPP network and an SAE network;

FIG. 3 is a handover flow chart of a terminal roaming from a 3GPP network to an SAE network;

Fig. 4 is a handover flowchart of a terminal roaming from an SAE network to a 3GPP network.

Detailed ways

In order to realize that after the terminal roams from the source-side network to the destination-side network, the IP information allocated from the source-side network is still used for subsequent services, so as to keep the terminal always online, the present invention provides a method for keeping the terminal always online, see As shown in Figure 1, it includes the following main steps:

S1. The terminal roams from the source-side network to the destination-side network.

S2. The source-side network carries the IP information assigned to the terminal in the source-side network in a message interacted with the destination-side network.

S3. The destination network uses the IP information carried in the interaction message to update the user plane route for the terminal.

S4. Carry out follow-up business.

Referring to Fig. 2, the present invention can be applied to a terminal roaming between a 3GPP network and an SAE network, and keep the terminal always online. The method of the present invention is applied to keep the terminal always online, and the roaming between other networks should also be within the protection scope of the present invention.

The method of the present invention is specifically described below through two examples.

Method example 1: a case where a terminal roams from a 3GPP network to an SAE network.

In the 3GPP network, there is a concept of IP address always online, that is, when the address pool is sufficient, after the terminal is assigned an IP address, the operator allows the terminal to occupy the IP in the 3GPP network without releasing it. In this way, when conducting business next time, relevant business can be directly carried out without re-allocating IP addresses, thereby reducing time delay. Likewise, this concept also applies to SAE networks.

After the terminal is successfully attached to the 3GPP network at the source side, it is activated to obtain an IP address for services. Within a period of time after the service ends, if the terminal does not initiate a new service, in order to save radio resources, the SGSN in the 3GPP network will send a message to the radio side to cancel the radio resource control RAB connection to release the radio connection, but keep IP information (including IP address and IP bearer parameters). That is, the terminal is in an idle IDLE state in which the IP address and bearer parameters are saved.

At this time, if the terminal with IP information roams to the SAE network on the destination side, the handover process is shown in Figure 3, including the following specific steps:

1. The terminal is in the IDLE state, roaming from the 3GPP network on the source side to the SAE network on the destination side. (1, AccessSystemReselection)

2. The terminal sends a network registration request message to the mobility management/user plane logical entity SAE MME/UPE in the SAE network, and the message carries the temporary identity (old temporary identity) used by the terminal in the 3GPP network. (2. Network Registration)

3. After receiving the network registration request message, the SAE MME/UPE extracts the temporary identifier from it, carries it in the corresponding message and sends it to the 2G/3G MME/UPE. (3. Send Temporary Identit)

4. The 2G/3G MME (that is, the SGSN) can correspond to the terminal according to the temporary identifier, and then encapsulate the IP information (including the IP address and IP bearer parameters) allocated to the terminal in the 2G/3G network in the user context transmission message ), sent to SAE MME/UPE. (4. Transfer UE Context)

5. The SAE MME/UPE obtains the subscription data of the terminal from the home subscription server HSS, and then interacts with the terminal to complete authentication. (5. Authentication)

6. The SAE MME/UPE initiates mobility management information registration to the HSS, which is used to migrate the mobility management right of the terminal to the SAE network. (6. Register MME)

7. After receiving the mobile management information registration message, the HSS interacts with the 2G/3G MME/UPE to delete the user context of the terminal in the 3GPP network. (7. Delete old UE contexts)

8. After the HSS finishes updating the subscription information of the terminal, it sends a registration confirmation message to the SAE MME/UPE, which confirms the management right of the terminal by the SAE network. (8. Confirm Registration)

9. The SAE MME/UPE sends a registration confirmation message to the terminal to complete the registration of the terminal on the SAE network. (9. Confirm Registration)

10. The SAE MME/UPE completes the routing update with the mobile anchor Inter AS Anchor, and also directly completes the user plane routing update with the terminal. (10.User Plane Route Update)

Afterwards, the SAE network assigns a new temporary identity (new temporary identity) to the terminal to conduct business.

The above step 10 can be performed after the registration is completed (this example); it can also be performed after step 4 and before step 9. That is, after the SAE network obtains the IP information allocated to the terminal in the 3GPP network, it can update the user plane route for the terminal.

Method example 2: the case where the terminal roams from the SAE network to the 3GPP network.

After the terminal successfully attaches to the SAE network on the source side, it will obtain a default IP address, which can be used as the called address. When there is no basic service (such as called service), the terminal is in an idle IDLE state in which the IP address and bearer parameters are saved.

At this time, if the terminal with IP information roams to the 2G/3G network on the destination side, the handover process is shown in Figure 4, including the following specific steps:

1. The terminal is in the IDLE state, roaming from the SAE network on the source side to the 2G/3G network on the destination side. (1, AccessSystemReselection)

2. The terminal sends a network registration request message to the mobility management/user plane logical entity 2G/3G MME (ie SGSN) in the 3GPP network. The message carries the temporary identity (old temporary identity) used by the terminal in the SAE network. (2. Network Registration)

3. After receiving the network registration request message, the 2G/3G MME/UPE extracts relevant information such as the temporary label from it, and carries it in the corresponding message and sends it to the SAE MME/UPE. (3. Send Temporary Identity)

4. SAE MME/UPE can correspond to the terminal according to the information in the received message; afterward, SAEMME/UPE encapsulates the IP information (including IP address and IP bearer) allocated by the terminal in the SAE network in the user context transmission message. parameter), send to 2G/3G MME/UPE. (4. Transfer UEContext)

5. The 2G/3G MME/UPE obtains the subscription data of the terminal from the home subscription server HSS, and then interacts with the terminal to complete authentication. (5. Authentication)

6. The 2G/3G MME/UPE initiates mobility management information registration to the HSS, which is used to migrate the mobility management right of the terminal to the 2G/3G network. (6. Register MME)

7. After receiving the mobile management information registration message, the HSS interacts with the SAE MME/UPE to delete the user context of the terminal in the SAE network. (7. Delete old UE contexts)

8. After the HSS finishes updating the subscription information of the terminal, it sends a registration confirmation message to the 2G/3G MME/UPE, which confirms the management right of the terminal by the 2G/3G network. (8. Confirm Registration)

9. The 2G/3G MME/UPE sends a registration confirmation message to the terminal to complete the registration of the terminal on the 2G/3G network. (9. Confirm Registration)

10. The 2G/3G MME/UPE completes the routing update with the mobile anchor Inter AS Anchor, and at the same time directly completes the user plane routing update with the terminal. (10.User Plane Route Update)

Afterwards, the 2G/3G network assigns a new temporary identity (new temporary identity) to the terminal, and the service can be performed.

The above step 10 can be performed after the registration is completed (this example); it can also be performed after step 4 and before step 9. That is, after the 2G/3G network obtains the IP information allocated to the terminal in the SAE network, it can update the user plane route for the terminal.

In order to support the method of the present invention, the present invention also provides a device, which includes an encapsulation unit for encapsulating The IP information assigned to the terminal in the network where the device is located.

In order to support the method of the present invention, the present invention further provides a device, which includes a parsing unit for parsing the IP information allocated in the source-side network by the terminal roaming to the network where the device is located, from the received message.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (12)

1. A method for keeping a terminal online forever, comprising the following steps: A. After the terminal roams from the source-side network to the destination-side network, the source-side network carries the IP information assigned to the terminal in the source-side network in the message interacted with the destination-side network; B. The destination network uses the IP information carried in the interaction message to update the user plane route for the terminal. 2. The method according to claim 1, wherein the source-side network is a 3GPP network, and the destination-side network is a System Architecture Evolution SAE network. 3. The method according to claim 2, wherein the 3GPP network carries the IP information in the user context transfer message sent to the SAE network. 4. The method according to claim 3, wherein the SAE network updates the user plane route for the terminal after receiving the user context transfer message and before the terminal completes registration. 5. The method according to claim 3, wherein after the SAE network registers the terminal, it updates the user plane route for the terminal. 6. The method according to claim 1, wherein the source-side network is an SAE network, and the destination-side network is a system architecture evolution 3GPP network. 7. The method according to claim 6, wherein the SAE network carries the IP information in the user context transfer message sent to the 3GPP network. 8. The method according to claim 7, wherein the 3GPP network updates the user plane route for the terminal after receiving the user context transfer message and before the terminal completes registration. 9. The method according to claim 7, wherein after the 3GPP network registers the terminal, it updates the user plane route for the terminal. 10. The method according to any one of claims 1 to 9, characterized in that the source-side network stores the IP information of the terminal, and when the terminal is in an idle state, roaming from the source-side network to the destination-side network . 11. A device, characterized in that it includes: an encapsulation unit, configured to encapsulate the information of the terminal in the device in the message exchanged between the network where the device is located and the network on the destination side when the terminal roams from the network where the device is located to the network on the destination side The IP information assigned in the network. 12. A device, characterized by comprising: a parsing unit, configured to parse out, from the received message, the IP information allocated in the source-side network by the terminal roaming to the network where the device is located.

Images