WO2013177954A1

WO2013177954A1 - Method, terminal and network side for requesting ip supporting mobility

Info

Publication number: WO2013177954A1
Application number: PCT/CN2013/000849
Authority: WO
Inventors: 骆文
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-08-24
Filing date: 2013-07-15
Publication date: 2013-12-05
Also published as: CN103634853A

Abstract

A method, terminal and network side for requesting an Internet Protocol (IP) supporting mobility. The method comprises: an access router receiving a request message sent by a terminal and for requesting the access router to allocate an IP address or prefix for the terminal, and when the terminal has a capability of distinguishing IP addresses or prefixes that support mobility or do not support mobility, and the request message requests an IP address or prefix supporting mobility, the access router obtaining an IP address or prefix supporting mobility, and sending the IP address or prefix supporting mobility to the terminal. In embodiments of the present invention, traffic requiring alternative routing is greatly reduced, thereby alleviating the burden of a bearer network and the pressure of an anchor network element.

Description

Method, terminal and network side for requesting acquisition of IP supporting mobility

Technical field

The present invention relates to the field of mobile communications, and in particular, to a method, a terminal, and a network side for requesting acquisition of IP supporting mobility.

Background technique

As is well known, in the Internet, when a terminal wants to access the Internet, it must apply for an effective Internet Protocol (IP) address from the network. The IP address has a dual attribute that represents both the identity of the user and the location of the network topology in which the user is located. When a user obtains an IP address in a topology (for example, under an access gateway), the IP address can only be used in the topology (for example, it can only be used within the scope of one access gateway). ). This is of course no problem for fixed terminals, but for mobile terminals, the above IP address becomes an invalid address when the terminal moves from the scope of one access gateway to the scope of another access gateway. At this point, the terminal must re-acquire a new IP address from the new topology. In this way, the continuity of the IP-based upper layer service cannot be guaranteed. For example, when the end user is making an IP call, the call is broken.

In order to solve this problem, the industry has proposed a series of solutions. The more popular mobility management technologies include Mobile IP (MIP), Proxy MIP (PMIP), and Generic Tunnel Protocol (GTP). Wait. As shown in Figure 1, the common feature of these technologies is the introduction of a fixed anchor (Anchor) to achieve mobility management of mobile nodes. For example, MIP uses Home Agent (HA) as an anchor point, PMIP uses Local Mobility Anchor (LMA) as an anchor point, and GTP uses a General Packet Radio Service Gateway support node (Gateway GPRS Support Node, GGSN) as an anchor point. The common feature of these technologies is that when the terminal is attached to the access router (such as access router A shown in Figure 1), the access router sets a special route for the terminal, and the anchor network element of the access router itself and the terminal. A tunnel is established between them, and the anchor network element allocates an IP address to the terminal. In this way, all the IP packets sent to the terminal and the IP packets sent by the terminal to the outside are all routed through the tunnel. In the actual deployed network, according to relevant statistics, only a small number of applications require network mobility support (such as Voice over Internet Portocol (VoIP) and online games), and most mobile terminal applications. is not needed. In the related art, the mobility management technology does not distinguish the requirements of the terminal application, but uniformly provides the mobility management support for the terminal. At this time, for terminals that do not use the above applications that require network mobility support, the network does not need to provide mobility support for these terminals, otherwise it not only wastes system resources (for example, assigning anchor network elements to terminals). And establishing an unnecessary tunnel between the access router and the anchor network element, as shown in FIG. 1 , and returning the path of the IP packet sent and received by the terminal (that is, causing route detour), as shown in FIG. 1 , IP · ^艮文 must be forwarded through the anchor network element. On the one hand, routing detours increase the delay between sending and receiving IP data packets between the terminal and the peer end, which is not conducive to improving the user's service experience; on the other hand, it wastes the carrier's transmission bearer resources. For terminals that use both mobility support and applications that do not require mobility support, all data traffic must also bypass the anchor point, increasing the performance requirements for the anchor point, which is not conducive to cost savings. Summary of the invention

The embodiments of the present invention provide a method for requesting acquisition of a mobility IP, a terminal, and a network side, and solve the problem that the related technologies provide mobility support for all terminals, resulting in waste of resources.

An embodiment of the present invention provides a method for requesting acquisition of a mobility-enabled IP, including: after the access router receives a request message sent by the terminal requesting the access router to allocate an IP address or a prefix to the terminal, The terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility, and when the request message requests an IP address or a prefix that supports mobility, the access router acquires an IP that supports mobility. An address or prefix, and returning the IP address or prefix supporting the mobility to the terminal.

The above method may also have the following features, the method further comprising:

The access router carries attribute information to inform the terminal that the IP address or prefix is an IP address or prefix that supports mobility.

After the access router receives the request message, when the terminal has a differentiated support mobile And the ability to support mobility IP addresses or prefixes, and the request message requests an IP address or prefix that does not support mobility, the access router allocates mobility to the terminal. An IP address or prefix, and returning the IP address or prefix that does not support mobility to the terminal.

After the access router receives the request message, when the terminal does not have the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, the access router acquires an IP address supporting mobility. Or a prefix, and returning the IP address or prefix supporting the mobility to the terminal.

The above method can also have the following features.

The step of the access router determining whether the terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility includes:

Determining, by the access router, whether the terminal has an IP address or a prefix that supports the mobility and the IP address or prefix that does not support mobility, according to whether the request message carries an indication of the IP address or the prefix required by the terminal;

Whether the access router carries a preset capability indication, and determines whether the terminal has an IP address that supports mobility and does not support mobility, when the terminal requests the access router to obtain an IP address or a prefix for the first time. Or the ability to prefix;

The access router determines, according to the initial network access of the terminal, whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and determines whether the terminal has differentiated support mobility and does not support mobile. Sexual IP address or prefix capability;

The access router learns from the network element that stores the context information of the terminal whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility.

After the terminal is switched from the source access router to the target access router, the target access router acquires an IP address or a prefix currently used by the terminal, and determines whether the IP address or prefix currently used by the terminal supports mobility. If supported, the target access router interacts with the anchor network element of the terminal to update the mobility context of the terminal; if not, the target access router notifies the terminal to release the current The IP address or prefix used; or, The target access router sends a notification to the source access router, and the source access router notifies the terminal to release the currently used IP address or prefix.

The above method can also have the following features.

The step of the target access router determining whether the IP address or prefix currently used by the terminal supports mobility includes:

And obtaining, by the target access router, information about whether the IP address or the prefix currently used by the terminal supports mobility when acquiring the IP address or the prefix currently used by the terminal; or, the target access router is configured according to the local The information determines whether the IP address or prefix currently used by the terminal supports mobility.

The above method can also have the following features.

The step of the access router acquiring the IP address or prefix supporting the mobility includes: when the request message requests an IP address or a prefix that supports mobility, the access router interacts with an anchor network element. And receiving the IP address or prefix supporting the mobility allocated by the anchor network element to the terminal.

The above method can also have the following features.

The step of the access router acquiring the IP address or the prefix that supports the mobility includes: the access router assigning the IP address or prefix that supports the mobility to the terminal; the method further includes:

The access router sends the IP address of the terminal and the location information of the terminal to the location management server.

After the access router receives the data packet sent by the terminal to the peer end, when the peer end currently uses an IP address or a prefix that does not support mobility, the access router directly sends the data packet. When the peer end currently uses an IP address or a prefix that supports mobility, the access router sends the data packet by using a routing method based on the peer location.

After the terminal switches from the source access router to the target access router, the target The access router obtains an IP address or prefix currently used by the terminal, and determines whether the IP address or prefix currently used by the terminal supports mobility. If supported, the target access router updates the location management server to the location management server. The location information of the terminal; if not, the target access router notifies the terminal to release the currently used IP address or prefix; or the target access router sends a notification to the source access router, The source access router notifies the terminal to release the currently used IP address or prefix.

The above method can also have the following features.

When the access router is a gateway general packet radio service support node (GGSN): the access router acquires an IP address or prefix supporting mobility, and returns the IP address or prefix supporting the mobility to the terminal. The steps include:

The GGSN allocates the IP address or prefix supporting the mobility to the terminal, and returns the IP address or prefix supporting the mobility to the terminal by the SGSN;

The method further includes:

The GGSN sends the IP address or prefix supporting the mobility and the location information of the terminal to the location management server.

The GGSN carries attribute information to inform the SGSN that the IP address or prefix is an IP address or prefix that supports mobility;

The SGSN records the mobility-enabled IP address or prefix and the attribute information in Packet Data Protocol (PDP) context information of the terminal.

After the terminal switches from the SGSN to the target SGSN, and when the target SGSN or GGSN is the target GGSN selected by the terminal other than the GGSN, the target SGSN or the GGSN determines the IP address of the terminal. Or whether the prefix supports mobility;

For a mobility-enabled IP address or prefix, the target SGSN or the GGSN triggers the target GGSN to create a PDP context for the mobility-enabled IP address or prefix, and updates the terminal to the location management server location information; For an IP address or prefix that does not support mobility, the target SGSN or GGSN deactivates the PDP context corresponding to the IP address or prefix that does not support mobility.

After the terminal switches from the SGSN to the target SGSN, and when the target SGSN or the GGSN is the target GGSN selected by the terminal other than the GGSN, the target GGSN determines the IP address of the terminal. Or whether the prefix supports mobility;

For the IP address or prefix supporting mobility, the target GGSN updates the location information of the terminal to the location management server;

For the IP address or prefix that does not support mobility, the target GGSN deactivates the PDP context corresponding to the IP address or prefix that does not support mobility.

The above method can also have the following features.

The step of the target GGSN determining whether the IP address or prefix of the terminal supports mobility includes:

After receiving the Create PDP Context Request message sent by the target SGSN, the target GGSN sends a request to the GGSN to obtain context information related to the PDP context to be created; and receives a response message returned by the GGSN, where The response message carries an indication of whether the IP address or the prefix corresponding to the PDP context to be created supports the mobility; or the GGSN sends the context information to the SGSN after receiving the update PDP context request of the target SGSN. The target GGSN, the target GGSN receives the context information, where the context information carries an indication of whether the IP address or prefix currently used by the terminal supports mobility.

In the process of the terminal switching from the SGSN to the target SGSN, after receiving the redirect request sent by the SGSN, the target SGSN determines the IP address or prefix of the terminal carried in the redirect request. Whether to support mobility;

And the target SGSN interacts with the target radio network controller to establish a radio bearer resource for the PDP context corresponding to the IP address or the prefix supporting the mobility; For an IP address or prefix that does not support mobility, the target SGSN instructs the SGSN to deactivate the IP address or the PDP context corresponding to the prefix that does not support mobility.

In the process of the terminal switching from the SGSN to the target SGSN, the SGSN determines whether the IP address or the prefix of the terminal supports mobility before sending the redirection request to the target SGSN.

The SGSN sends the mobility-relevant IP address or the PDP context corresponding to the prefix to the target SGSN through the redirect request;

For an IP address or prefix that does not support mobility, the SGSN deactivates the IP address or the PDP context corresponding to the prefix that does not support mobility.

The above method can also have the following features.

When the access router is a packet data network gateway (P-GW):

The step of the access router acquiring the IP address or prefix supporting mobility and returning the IP address or prefix supporting the mobility to the terminal includes:

The P-GW allocates the IP address or prefix supporting the mobility to the terminal, and sends the mobility-enabled IP address or prefix to the mobility management entity (MME) through the serving gateway (S-GW). Returning, by the MME, the IP address or prefix that supports mobility to the terminal; the method further includes:

The P-GW sends the IP address or prefix supporting the mobility and the location information of the terminal to the location management server.

When the terminal initiates the handover, the MME of the terminal determines whether the IP address or the prefix of the terminal supports mobility;

For the IP address or prefix that does not support mobility, the MME deletes the packet data network (PDN) context corresponding to the IP address or prefix that does not support mobility;

For the IP address or prefix supporting mobility, the MME triggers a PDN context to be created for the IP address or prefix supporting the mobility at the target P-GW of the terminal, and to the location tube The server updates the location information of the terminal.

After the terminal switches from the S-GW to the target S-GW, and when the target S-GW or the P-GW is the target P-GW selected by the terminal, not the P-GW, Determining whether the target S-GW or the P-GW determines whether the IP address or prefix of the terminal supports mobility;

For the IP address or prefix supporting mobility, the target S-GW or the P-GW triggers the target P-GW to create a PDN context for the IP address or prefix supporting mobility, and manages the location to the location The server updates location information of the terminal;

For the IP address or prefix that does not support mobility, the target S-GW or the P-GW deletes the PDN context corresponding to the IP address or prefix that does not support mobility.

In the process of the terminal switching from the P-GW to the target P-GW, the target P-GW determines whether the IP address or prefix of the terminal supports mobility;

For the IP address or prefix that does not support mobility, the target P-GW deletes the PDN context corresponding to the IP address or prefix that does not support mobility;

The target P-GW updates the location information of the terminal to the location management server for an IP address or prefix supporting mobility.

The embodiment of the present invention further provides a network side, including: an access router, where the access router is configured to: receive a request from a terminal, and the access router allocates an Internet Protocol (IP) address to the terminal or After the prefix request message, when the terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility, and the request message requests an IP address or prefix that supports mobility, the support mobile is acquired. a sexual IP address or prefix, and returning the IP address or prefix supporting the mobility to the terminal.

The above network side can also have the following features.

The access router is further configured to: carry attribute information to inform the terminal that the IP address or prefix is an IP address or prefix that supports mobility.

The above network side can also have the following features. The access router is further configured to: after receiving the request message, when the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and the request message requests that is not supported When the IP address or prefix of the mobility is used, the terminal is assigned an IP address or prefix that does not support mobility, and the IP address or prefix that does not support mobility is returned to the terminal.

The above network side can also have the following features.

The access router is further configured to: after receiving the request message, when the terminal does not have the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, obtain an IP address supporting mobility or Prefixing, and returning the IP address or prefix supporting the mobility to the terminal.

The above network side can also have the following features.

The access router is configured to determine whether the terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility by:

Determining, according to the indication in the request message whether the IP address or the prefix is required by the terminal, whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility;

Whether the terminal carries a preset capability indication, and determines whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, when the terminal requests the access router to obtain an IP address or a prefix for the first time;

According to the initial network access of the terminal, whether it is stated that the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and determines whether the terminal has an IP address that distinguishes between mobility support and mobility. The ability to prefix; and

The network element storing the context information of the terminal knows whether the terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility.

The network side may also have the following features, where the network side further includes a target access router, where:

The target access router is configured to: after the terminal switches from the source access router to the target access router, obtain an IP address or prefix currently used by the terminal, and determine an IP address currently used by the terminal or Whether the prefix supports mobility, if supported, interacting with the anchor network element of the terminal, updating the mobility context of the terminal; if not, notifying the terminal Release the currently used IP address or prefix; or send a notification to the source access router; the access router is further configured to: notify the terminal to release the currently used IP address or prefix.

The above network side can also have the following features.

The target access router is configured to determine whether the IP address or prefix currently used by the terminal supports mobility in the following manner:

Obtaining information about whether the IP address or the prefix currently used by the terminal supports mobility when acquiring the IP address or prefix currently used by the terminal; or determining the IP address or prefix currently used by the terminal according to the local configuration information. Whether to support mobility.

The above network side can also have the following features.

The access router is configured to obtain the IP address or prefix supporting the mobility by:

And interacting with the anchor network element when the request message requests an IP address or prefix supporting mobility, and receiving the IP address or prefix supporting the mobility allocated by the anchor network element to the terminal .

The above network side can also have the following features.

Allocating the IP address or prefix supporting the mobility to the terminal;

The access router is further configured to: send an IP address of the terminal and location information of the terminal to a location management server.

The above network side can also have the following features.

The access router is further configured to: after receiving the data packet sent by the terminal to the peer end, when the peer end currently uses an IP address or a prefix that does not support mobility, the data packet is directly sent; When the peer end currently uses an IP address or a prefix that supports mobility, the data message is sent by using a routing method based on the peer location.

The network side may also have the following features, where the network side further includes a target access router, Medium:

The target access router is further configured to: after the terminal switches from the source access router to the target access router, obtain an IP address or a prefix currently used by the terminal, and determine an IP currently used by the terminal. Whether the address or the prefix supports mobility, if supported, updating the location information of the terminal to the location management server; if not, notifying the terminal to release the currently used IP address or prefix; or sending a notification Giving the source access router;

The access router is further configured to: notify the terminal to release the currently used IP address or prefix.

The above network side can also have the following features.

When the access router is a GGSN:

The GGSN is configured to: allocate the IP address or prefix supporting the mobility to the terminal, and send the mobility-enabled IP address or prefix to the SGSN; and send the support to the location management server a mobile IP address or prefix and location information of the terminal;

The SGSN is configured to: return the IP address or prefix supporting the mobility to the terminal. The network side may also have the following features, the network side further includes the SGSN, where: the GGSN is further configured to: carry attribute information to notify the SGSN that the IP address or prefix is an IP address supporting mobility. Or prefix;

The SGSN is further configured to: record the IP address or prefix supporting the mobility and the attribute information in Packet Data Protocol (PDP) context information of the terminal.

The above network side can also have the following features.

The GGSN is further configured to: after the terminal switches from the SGSN to the target SGSN, and when the target GGSN selected by the GGSN for the terminal is not the GGSN, determine whether the IP address or prefix of the terminal is supported. Mobility

And triggering, by the target GGSN, a PDP context for the mobility-enabled IP address or prefix, and updating the location information of the terminal to the location management server;

Deactivate the IP address that does not support mobility for an IP address or prefix that does not support mobility The PDP context corresponding to the address or prefix.

The above network side can also have the following features.

The target SGSN is configured to: after the terminal switches from the SGSN to the target SGSN, and when the target SGSN is the target GGSN selected by the terminal other than the GGSN, determine the IP address of the terminal or Whether the prefix supports mobility;

The IP address or prefix that does not support mobility is deactivated for the PDP context corresponding to the IP address or prefix that does not support mobility.

The network side may also have the following features: the network side further includes a target GGSN, where: the target GGSN is configured to: when the terminal switches from the SGSN to the target SGSN, the GGSN, determine the terminal Whether the IP address or prefix supports mobility;

Updating the location information of the terminal to the location management server for an IP address or prefix supporting mobility;

The above network side can also have the following features.

The target GGSN is configured to determine whether the IP address or prefix of the terminal supports mobility in the following manner:

After receiving the Create PDP Context Request message sent by the target SGSN, the target GGSN sends a request to the GGSN to obtain context information related to the PDP context to be created; and receives a response message returned by the GGSN, where The response message carries an indication of whether the IP address or prefix corresponding to the PDP context to be created supports mobility.

Or receiving the context information that is sent by the GGSN, where the context information carries an indication of whether the IP address or the prefix of the terminal supports mobility. The network side may also have the following feature, where the network side further includes a target SGSN, where: the target SGSN is further configured to: receive, in the process of the terminal switching from the SGSN to the target SGSN, After the redirect request sent by the SGSN, determining whether the IP address or prefix of the terminal carried in the redirect request supports mobility;

And interacting with the target radio network controller, and establishing a radio bearer resource for the PDP context corresponding to the IP address or the prefix supporting the mobility;

For the IP address or prefix that does not support mobility, the SGSN is instructed to deactivate the IP address or the PDP context corresponding to the prefix that does not support mobility.

The network side may also have the following features, the network side further includes an SGSN, where the SGSN is further configured to: send, in the process of the terminal switching from the SGSN to the target SGSN, to the target SGSN Before the redirection request, determining whether the IP address or the prefix of the terminal supports mobility;

Transmitting, by the redirect request, the PDP context corresponding to the IP address or the prefix supporting the mobility to the target SGSN;

The network side may also have the following features, where the network side further includes an MME, where, when the access router is a source P-GW:

The P-GW is configured to: allocate, to the terminal, the mobility-capable IP address or prefix, and send the mobility-enabled IP address or prefix to the MME by using a source S-GW; and, to a location The management server sends the IP address or prefix supporting the mobility and the location information of the terminal;

The MME is configured to: return the IP address or prefix supporting the mobility to the terminal. The above network side can also have the following features.

The MME is further configured to: when the terminal initiates the handover, determine whether the IP address or the prefix of the terminal supports mobility:

Deleting the IP address that does not support mobility for an IP address or prefix that does not support mobility Or a packet data network (PDN) context corresponding to the prefix;

For the IP address or prefix supporting mobility, the target P-GW at the terminal is triggered to create a PDN context for the IP address or prefix supporting the mobility, and the location information of the terminal is updated to the location management server.

The above network side can also have the following features.

The P-GW is further configured to: after the terminal switches from the S-GW to the target S-GW, and when the P-GW is the target P-GW selected by the terminal, not the P-GW Determining whether the IP address or prefix of the terminal supports mobility;

And triggering, by the target P-GW, a PDN context for the mobility-enabled IP address or prefix, and updating the location information of the terminal to the location management server;

For the IP address or prefix that does not support mobility, delete the IP address that does not support mobility or the PDN context corresponding to the prefix.

The network side may also have the following features, where the network side further includes a target S-GW, where: the target S-GW is further configured to: after the terminal switches from the S-GW to the target S-GW And determining, by the target S-GW that the target P-GW selected by the terminal is not the P-GW, whether the IP address or the prefix of the terminal supports mobility;

The network side may also have the following features, the network side further includes a target P-GW, where the target P-GW is configured to: process that the terminal switches from the P-GW to the target P-GW Determining whether the IP address or prefix of the terminal supports mobility;

Deleting the IP address or the PDN context corresponding to the prefix that does not support mobility for an IP address or a prefix that does not support mobility; The location information of the terminal is updated to the location management server for an IP address or prefix supporting mobility.

The embodiment of the invention further provides a terminal, which is configured to: send a request message to the access router, requesting the access router to allocate an IP address or prefix supporting mobility for the terminal.

In the embodiment of the present invention, when the terminal needs to obtain an IP address or a prefix supporting mobility from the network, the network requests the network. Only those applications that require mobility support will send and receive IP packets based on the above IP address or prefix, that is, only the traffic of these applications needs to bypass the anchor point, which greatly reduces the traffic required by the loop, thereby reducing The load of the bearer network and the pressure of the anchor network element. BRIEF abstract

FIG. 1 is a structural diagram of mobility management in the related art.

Figure 2 is a flow chart of the first embodiment of the present invention.

Figure 3 is a flow chart of a second embodiment of the present invention.

Figure 4 is a flow chart of a third embodiment of the present invention.

Figure 5 is a flow chart of a fourth embodiment of the present invention.

FIG. 6 is a structural diagram of identity location separation according to an embodiment of the present invention.

Figure 7 is a flow chart of a fifth embodiment of the present invention.

Figure 8 is a flow chart of a sixth embodiment of the present invention.

9 is a structural diagram of a 3G network according to an embodiment of the present invention;

Figure 10 is a flow chart of a seventh embodiment of the present invention.

Figure 11 is a flow chart of an eighth embodiment of the present invention.

Figure 12 is a flow chart of a ninth embodiment of the present invention.

Figure 13 is a flow chart of a tenth embodiment of the present invention.

Figure 14 is a flow chart showing an eleventh embodiment of the present invention.

FIG. 15 is a structural diagram of an LTE network according to an embodiment of the present invention.

Figure 16 is a flow chart showing a twelfth embodiment of the present invention. Figure 17 is a flow chart showing a thirteenth embodiment of the present invention.

Figure 18 is a flow chart showing a fourteenth embodiment of the present invention.

Figure 19 is a flow chart showing a fifteenth embodiment of the present invention. Preferred embodiment of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

The embodiment of the present invention provides a method for requesting acquisition of a mobile IP address, including: after the access router receives a request message sent by the terminal requesting the access router to allocate an IP address or a prefix to the terminal, The terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility, and when the request message requests an IP address or a prefix that supports mobility, the access router acquires an IP that supports mobility. An address or prefix, and returning the IP address or prefix supporting the mobility to the terminal.

The method further includes: the access router carrying attribute information to notify the terminal that the IP address or prefix is an IP address or prefix that supports mobility.

The method further includes: after the access router receives the request message, when the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and the request message requests Is an IP address or prefix that does not support mobility, the access router allocates an IP address or prefix that does not support mobility to the terminal, and returns the IP address or prefix that does not support mobility to the terminal.

The method further includes: after the access router receives the request message, when the terminal does not have the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, the access router Obtaining an IP address or prefix supporting mobility, and transmitting the IP address or prefix supporting mobility to the terminal.

The step of determining, by the access router, whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility includes:

Determining, by the access router, whether the terminal has an IP address or a prefix that is required by the terminal, and determining whether the terminal has an IP that supports mobility and does not support mobility. The ability to address or prefix;

Different implementations are available under different architectures.

In the fixed anchor architecture, the step of the access router acquiring the IP address or prefix supporting the mobility includes:

When the request message requests an IP address or a prefix that supports mobility, the access router interacts with an anchor network element, and receives the support mobility allocated by the anchor network element to the terminal. IP address or prefix.

The method further includes: after the terminal switches from the source access router to the target access router, the target access router acquires an IP address or prefix currently used by the terminal, and determines that the terminal is currently used. Whether the IP address or the prefix supports the mobility, if supported, the target access router interacts with the anchor network element of the terminal, and updates the mobility context of the terminal; if not, the target connection The ingress router notifies the terminal to release the currently used IP address or prefix; or the target access router sends a notification to the source access router, and the source access router notifies the terminal to release the current The IP address or prefix used.

The step of determining, by the target access router, whether the IP address or prefix currently used by the terminal supports mobility includes:

And obtaining, by the target access router, information about whether the IP address or the prefix currently used by the terminal supports mobility when acquiring the IP address or the prefix currently used by the terminal; or, the target access router is configured according to the local The information determines whether the IP address or prefix currently used by the terminal supports mobility. Of course, this method of judgment also applies to identity location separation architecture and LTE (Long Term Evolution, Long Term Evolution and 3G (The 3rd Generation, 3rd Generation) architecture. Under the identity location separation architecture,

The access router sends the IP address or prefix of the terminal and the location information of the terminal to the location management server.

The method further includes:

After the access router receives the data packet sent by the terminal to the peer end, the access router directly sends the data packet when the peer end currently uses an IP address or a prefix that does not support mobility. When the peer end currently uses an IP address or a prefix that supports mobility, the access router sends the data packet by using a routing method based on the peer location.

The method further includes:

After the terminal switches from the source access router to the target access router, the target access router acquires an IP address or prefix currently used by the terminal, and determines whether the IP address or prefix currently used by the terminal supports Mobility, if supported, the target access router updates the location information of the terminal to the location management server; if not, the target access router notifies the terminal to release the currently used IP address or prefix Or, the target access router sends a notification to the source access router, and the source access router notifies the terminal to release the currently used IP address or prefix.

If the identity location is separately applied to the 3G architecture, then

When the access router is a gateway general packet radio service support node (GGSN): the access router acquires an IP address or prefix supporting mobility, and returns the IP address or prefix supporting the mobility to the terminal The steps include:

Assigning, by the GGSN, the IP address or prefix supporting mobility to the terminal, the branch Returning, by the SGSN, the IP address or prefix that supports mobility to the terminal; the method further includes:

The method further includes:

The GGSN carries attribute information to inform the SGSN that the IP address or prefix is an IP address or prefix that supports mobility; the SGSN records the IP address or prefix supporting mobility and the attribute information in the The packet data protocol (PDP) context information of the terminal.

When the terminal switches, the IP address or the PDP context corresponding to the prefix that does not support mobility is deactivated, and a PDP context is created for the IP address or prefix supporting mobility. The specific triggering network element may be a target SGSN, a GGSN, a target GGSN, or the like.

The method further includes:

After the terminal switches from the SGSN to the target SGSN, and when the target GGSN selected by the SGSN or GGSN for the terminal is not the GGSN, the target SGSN or GGSN determines whether the IP address or prefix of the terminal is Support mobility;

For the IP address or prefix supporting mobility, the target SGSN or GGSN triggers the target GGSN to create a PDP context for the IP address or prefix supporting mobility, and updates the location information of the terminal to the location management server;

For an IP address or prefix that does not support mobility, the target SGSN or GGSN initiates deactivation of a PDP context corresponding to an IP address or prefix that does not support mobility.

The method further includes:

For the IP address or prefix that does not support mobility, the target GGSN deactivates the unsupported The mobility IP address or the PDP context corresponding to the prefix.

The step of determining, by the target GGSN, whether the IP address or the prefix of the terminal supports mobility includes:

Or, after receiving the update PDP context request of the target SGSN, the GGSN sends context information to the target GGSN, where the target GGSN receives context information, where the context information carries an IP address or a prefix of the terminal. Whether to support the indication of mobility.

The method further includes:

And the target SGSN interacts with the target radio network controller to establish a radio bearer resource for the PDP context corresponding to the IP address or the prefix supporting the mobility;

For an IP address or prefix that does not support mobility, the target SGSN instructs the SGSN to deactivate the IP address or the PDP context corresponding to the prefix that does not support mobility.

The method further includes:

In the process of the terminal switching from the SGSN to the target SGSN, before the SGSN sends a redirect request to the target SGSN, it is determined whether the IP address or prefix of the terminal supports mobility.

If the identity location is applied in the LTE architecture, then When the access router is a packet data network gateway (P-GW):

The step of the access router acquiring the IP address or prefix supporting the mobility and returning the IP address or prefix supporting the mobility to the terminal includes:

The P-GW allocates the IP address or prefix supporting the mobility to the terminal, and sends the IP address or prefix supporting the mobility to the mobility management entity (MME) through the serving gateway (S-GW), The MME returns the IP address or prefix supporting mobility to the terminal.

The method further includes:

Wherein, when the terminal switches, the IP address or the PDN context corresponding to the prefix that does not support mobility is deactivated, and a PDN context is triggered for the IP address or prefix supporting mobility. The specific trigger network element may be an MME, a target S-GW, a P-GW, a target P-GW, or the like.

The method further includes:

For the IP address or prefix supporting mobility, the MME triggers a PDN context to be created for the IP address or prefix supporting the mobility at the target P-GW of the terminal, and updates the terminal to the location management server location information.

The method further includes:

After the terminal switches from the S-GW to the target S-GW, and when the target S-GW or the P-GW is the target P-GW selected by the terminal other than the P-GW, the target The S-GW or the P-GW determines whether the IP address or the prefix of the terminal supports mobility;

For the IP address or prefix supporting mobility, the target S-GW or P-GW triggers the target P-GW to create a PDN context for the IP address or prefix supporting the mobility, and updates the location to the location management server The location information of the terminal; For the IP address or prefix that does not support mobility, the target S-GW or P-GW deletes the PDN context corresponding to the IP address or prefix that does not support mobility.

The method further includes:

The embodiment of the invention further provides a network side.

2 is a flowchart of a first embodiment of the present invention. When a terminal needs to use an IP address or a prefix that supports mobility, the terminal requests a network to support an IP address or a prefix that supports mobility. For example, when an end user starts using an application that requires mobility support (e.g., VoIP), the application requests (e.g., requests to the terminal's operating system) for an IP address that supports mobility. At this time, if the IP (or IP address or prefix) supporting the mobility is not configured on the terminal, the IP address or prefix supporting the mobility is requested from the network, and the following steps are specifically included.

Step 201: The terminal sends a request message to the access router to request the access router to allocate an IP address or a prefix to the terminal. At this time, the terminal carries an indication in the message to instruct the access router to allocate an IP address or prefix that supports mobility.

Step 202: After receiving the foregoing request message, when the access router views the foregoing indication (that is, when the received request message is a request message for requesting allocation of a mobile IP address or prefix), determining that the network is allocated to the terminal The anchor network element interacts with the anchor network element to establish a mobility context for the terminal. The anchor network element of the terminal assigns an IP address or prefix to the terminal, and returns the IP address or prefix to the access router.

It is worth noting that, based on the interaction between the access router and the anchor network element, the access router and The anchor network element establishes a special route for the terminal. For example, a tunnel (PMIP tunnel, MIP tunnel, GTP tunnel, etc.) is established between the access router and the anchor network element. When the IP packet sent by the terminal to the peer end based on the IP address or the prefix arrives at the access router, the access router sends the packet to the anchor network element through the tunnel, and then the anchor network element sends the packet to the peer end. When the IP packet to the IP address or prefix arrives at the anchor network element, the anchor network element sends the packet to the access router through the tunnel, and then the access router sends the packet to the terminal.

Step 203: The access router acquires an IP address or prefix that supports mobility assigned to the terminal by interacting with the anchor network element. The access router returns a response message to the terminal, carrying the above IP address or prefix. While carrying the IP address or prefix, it also carries a description of the attribute of the IP address or prefix to inform the terminal that the IP address or prefix is an IP address or prefix that supports mobility.

Through the method in the foregoing embodiment, when the terminal needs to obtain an IP address or prefix supporting mobility from the network, the network requests the network. In general, the terminal requests the mobile-enabled IP address or prefix from the network based on the needs of the application, such as the above, when the application requires mobility support. Only at this time, the network allocates anchor network elements to the terminal, establishes special routes, and the like. Moreover, only those applications that require mobility support can send and receive IP packets based on the above IP addresses or prefixes, and only the traffic of these applications needs to bypass the anchor point, which greatly reduces the traffic required by the loop, thereby reducing The load of the bearer network and the pressure of the anchor network element.

As described above, it is worth noting that if the application on the terminal does not require mobility support, the terminal may not carry the above indication when requesting the network to allocate an IP address or prefix (or carry another indication to indicate whether the request is not Supporting the mobility IP address or prefix), the access router directly assigns an IP address or prefix to the terminal (ie, does not support the mobility IP address or prefix) and returns it to the terminal. When the terminal sends and receives IP packets based on such an IP address or prefix, it can directly send and receive IP packets through the access router. It is also worth noting that in the above method, when the terminal itself is required to recognize whether the acquired IP address or prefix supports mobility, it is generally necessary to make changes to the existing terminal (e.g., software and hardware upgrade, etc.). There are several ways in which an access router can know whether a terminal has the ability to recognize both IP addresses or prefixes (i.e., IP addresses or prefixes that support mobility and do not support mobility).

One method is that when the terminal requests the access router to obtain an IP address, it is always in the request message. The access router explicitly indicates that the IP address or the prefix is required by the access router, and the access router determines that the terminal has the foregoing capability according to the foregoing indication. If the indication is not carried in the request message, the access router determines that the terminal does not have the foregoing capability.

Alternatively, when the terminal first requests the access router to obtain an IP address, the request message carries another indication to indicate that the two types of IP addresses or prefixes can be distinguished. If the indication is not carried, the access router determines that the terminal cannot distinguish between the two types of IP addresses or prefixes.

Alternatively, the terminal may also declare to the access router that it can distinguish between two IP addresses or prefixes when initially entering the network; when the terminal does not declare, the default terminal of the access router does not have this capability.

In another method, the terminal notifies the network element in the network that the context information of the terminal is saved, such as the access authentication server, by the ability to distinguish the two types of IP addresses or prefixes in the initial network access process. The NE saves this information. Optionally, the terminal having the foregoing capability carries an indication in the message sent to the network element that the user has the capability; otherwise, the terminal that does not have the capability does not carry the indication in the message sent to the network element, when When the network element finds that the above indication is not carried in the received message, it determines that the terminal does not have the ability to distinguish the two types of IP addresses or prefixes. In this way, the access router can learn from the network element that saves the context information of the terminal that the terminal has the ability to recognize the two IP addresses or prefixes.

Based on the foregoing method, if it is determined that the terminal does not have the capability of distinguishing the two types of IP addresses or prefixes, the access router requests the terminal to support the mobility IP address or prefix when receiving the message that the terminal requests to allocate the IP address or the prefix. And sending to the terminal; if it is determined that the terminal has the ability to distinguish the two types of IP addresses or prefixes, the terminal is allocated an IP address or prefix that supports or does not support mobility according to the method described in the above steps 201-203.

It is worth noting that when the terminal sends and receives IP packets based on the IP address or prefix that does not support mobility, the path is: terminal <-> access router <-> peer; when the terminal is based on IP address or prefix supporting mobility When sending and receiving IP 4 messages, the path is: Terminal <-> Access Router <-> Anchor Network Element <-> Peer.

Optionally, in step 201, the terminal sends a route collection to the access router (Router)

The Solicitation (RS) message is used to request an IP address or a prefix. The terminal carries the above indications in the message. The access router uses a Router Advertisement (RA) to answer the terminal and carries the IP address assigned to the terminal. Or a prefix, and a description of the attribute carrying the IP address or prefix. Embodiment 2

3 is a flowchart of a second embodiment of the present invention, and describes a scenario in which a terminal switches a currently attached access router due to mobility, for example, switching from a source access router to a target access router, specifically including the following step.

Step 301: The terminal switches from the source access router to the target access router. In general, the target access router can receive related messages originating from the network (e.g., source access router) or the terminal.

Step 302: The target access router acquires an IP address or prefix currently used by the terminal. In general, the target access router can obtain the IP address or prefix assigned to the terminal from the source access router or the above-mentioned network element that stores the terminal context information.

Steps 303-304: After obtaining the foregoing IP address or prefix, the target access router determines whether the IP address or the prefix supports mobility.

If the IP address or prefix is an IP address or prefix that supports mobility, the target access router interacts with the anchor network element of the terminal to update the mobility context of the terminal. Specifically, the special route described in step 202 is set for the IP address or prefix on the target access router, and the special route that has been set on the anchor network element is updated (for example, in the target access router and the anchor network element). Establish a tunnel for the IP address or prefix). If the IP address or prefix is an IP address or prefix that does not support mobility, the target access router notifies the terminal to release the IP address or prefix; or the target access router notifies the source access router that the source access router notifies The terminal releases the IP address or prefix.

It is worth noting that when the target access router obtains the IP address or prefix currently used by the terminal, for example, when the source access router or the network element storing the context information of the terminal obtains the IP address or prefix currently used by the terminal, Based on this information, the target access router can determine whether the IP address or prefix supports mobility. Or the target access router determines, according to the local configuration information, whether the IP address or the prefix is an IP that supports mobility. For example, an IP address or prefix that starts with 10 is for mobility, and a code that starts with 01 does not support mobility. Sexual. Step 305: After the terminal switches to the target access router, the target access router sends a message to the terminal to notify the terminal of the current IP address or the state of the prefix. At this time, the message carries the information of the IP address or prefix supporting the mobility to notify the terminal that the IP address or the prefix can continue to be used, and also carries the attribute information of the IP address or the prefix; the message may also carry the previously used by the terminal. The mobility IP address or prefix is not supported, and is invalidated, and then the terminal is notified to release the IP address or prefix. The message sent by the target access router to the terminal is the above RS message.

At this time, the session (Session) based on the IP address or prefix that does not support mobility will not be able to communicate with the peer. At this time, the sessions (or applications) may request a new IP address or prefix that does not support mobility to the terminal. As in the method described in Embodiment 1, the terminal requests the target access router to obtain an IP address that does not support mobility or Prefix).

Embodiment 3

4 is a flow chart of a third embodiment of the present invention, which assumes that the terminal requests an IP address from an access router using a Dynamic Host Configuration Protocol (DHCP). It is assumed that the access router serves as a DHCP server at the same time, and specifically includes the following steps.

Step 401: The terminal sends a DHCP Discover message to the access router to request an IP address or a prefix for itself. The terminal also carries the indication described in step 201 in the message to indicate that the request to assign an IP or prefix supporting mobility (or to indicate an IP address or prefix that does not support mobility).

Step 402: After receiving the foregoing message, the access router determines the IP address or prefix type requested by the terminal. If the terminal requests the mobility-enabled IP, the access router interacts with the anchor network element of the terminal, obtains the IP address or prefix assigned to the terminal from the anchor network element, and sets the terminal for the terminal, as described in step 202. Special route.

Step 403: The access router returns a DHCP Offer message to the terminal, where the IP address or prefix assigned to the terminal carries the attribute of the IP address or prefix (supporting mobility or not supporting mobility).

Step 404: The terminal sends a DHCP Request (DHCP Request) message to the access router, where the IP address or prefix allocated by the terminal is carried. Step 405: The access router returns a DHCP acknowledgement (DHCPACK) message carrying the assigned IP address or prefix.

It should be noted that, when receiving the DHCP Discover message, if the terminal requests to support the mobility IP address or prefix, when the access router interacts with the anchor network element to request the anchor network element to assign an IP address or prefix to the terminal, The access router and the anchor network element may also not set a special route (establishing a tunnel, etc.) for the terminal at this time. After receiving the DHCP Request message in step 404, the access router sends another message to the anchor network element to trigger itself and the anchor network element to set a special route for the terminal. It is also worth noting that if the terminal requests an IP address or a prefix that does not support mobility, the access router does not need to interact with the anchor network element, and directly assigns an IP address or prefix to the terminal.

Embodiment 4

Figure 5 is a flow chart of a fourth embodiment of the present invention. It is assumed that the terminal uses the DHCP protocol and switches from the source access router to the target access router due to the movement, which specifically includes the following steps.

Step 501: When the terminal switches to the target access router, the terminal sends a DHCP request to the target access router, and carries the previously assigned IP address or prefix, and carries the attribute of the IP address or prefix ( Support mobility or not support mobility).

Step 502: The target access router determines whether the IP address or prefix currently used by the terminal supports mobility. The target access router can make a judgment based on the attribute information carried in the above DHCP request.

Steps 503-504: If it is determined that the IP address or the prefix of the terminal supports the mobility, the target access router interacts with the anchor network element of the terminal, and as described in step 304, the special route that has been set on the anchor network element is updated. After the interaction, the target access router returns a DHCPACK message to the terminal, carrying the above IP address or prefix. At this point, the terminal can continue to use the IP address or prefix that supports mobility.

If it is judged that the IP address or prefix of the terminal does not support mobility, the target access router returns to the terminal.

The DHCP denied (DHCPNAK) message denies the terminal to continue using this IP address or prefix. At this time, the application based on the IP address or prefix that does not support mobility on the terminal will not be able to communicate normally with the peer. These applications can request a new IP address or prefix that does not support mobility to the terminal (as in the first embodiment). In the method described, the terminal requests the target access router to acquire an IP address or prefix that does not support mobility. It should be noted that, as described in the second embodiment, the target access router may also obtain the IP address or prefix currently used by the terminal from the source access router or the network element that saves the context information, and the IP address or prefix of the terminal. Attribute information. The target access router may also obtain the IP address or prefix information currently used by the terminal without relying on the DHCP request described in step 501. At this time, for the IP address or prefix supporting mobility, as in step 503 above, the target access router interacts with the anchor network element and updates the routing information. For an IP address or a prefix that does not support mobility, the packet may be discarded without being processed. When the IP packet received by the terminal based on the IP address or prefix that does not support mobility is received, the packet is directly discarded. To force the terminal to re-initiate the DHCP process to obtain an IP address or prefix.

In addition, it should be noted that the specific messages in Embodiments 3 and 4 are exemplified by the DHCPv4 protocol, and also applicable to the DHCPv6 protocol. Use DHCP Request message instead of DHCP Discover message, DHCP Advertise message instead of DHCP Offer message, and DHCP Reply message instead of DHCPACK and DHCPNAK message. The specific parameters in the DHCP Reply message are used to distinguish whether it is a positive response (corresponding to a DHCPACK message) or a negative response (corresponding to a DHCPNAK message). The other principles are the same.

In addition to the traditional mobility management technologies as described in the background art, the industry also has a mobility management technology based on identity location separation, and the corresponding architecture is shown in FIG. 6. In Figure 6, the access router and location management server are the core network elements of the mobility management technology. The main function of the access router is to be responsible for user access and assign an IP address to the user terminal. The role of the location management server is to record the relationship between the IP address of the user terminal and the current location information of the terminal, that is, to record the IP address-location of the user terminal. " Correspondence. The above location information is the IP address of the access router to which the terminal is currently connected. It is worth noting that the peer also needs to access the network through such an access router.

In this mobility management technology, when the data packet arrives at the access router of the opposite end (the access router-peer end shown in FIG. 6), the access router-peer determines the location of the terminal first. Assume that the current terminal is connected to access router A. The access router-peer end tunnels the data packet, sets the destination address of the tunnel to the address of access router A, and sends the data packet to access router A. After receiving the above packet, access router A releases the tunnel encapsulation and delivers the data packet to the terminal. When the terminal switches the access router currently serving it due to the movement, for example, from the access road The switch A is switched to the access router B. The access router A needs to update the current "IP address-location" correspondence of the terminal to the location management server, and updates the location information to the IP address of the access router B. The access router-the peer can also obtain the corresponding notification, so that the access router-peer will send the above data packet directly to the access router B, and then the access router B sends the packet to the terminal.

As mentioned above, only a small number of applications require network mobility support, and most mobile terminal applications do not. The above-mentioned mobility management scheme based on the identity location principle does not distinguish the requirements of the terminal, and always provides mobility services for the terminal. In this way, even if the terminal does not need mobility support, the network always maintains some mobility-related contexts for the terminal, for example, maintaining the terminal "IP address-location" correspondence in the location management server, and sending the IP to the terminal to the terminal. When the packet is received, the access router-the peer always uses the tunnel encapsulation method to deliver IP packets, which increases the network overhead. In fact, the method of the embodiment of the present invention can also be applied to such an identity-based location-based mobility management technology, which can reduce network overhead.

Embodiment 5

FIG. 7 is a flowchart of a fifth embodiment of the present invention. The embodiment is applied to the mobility management technology based on identity location separation, and specifically includes the following steps.

Step 701, the same step 201.

Step 702: When receiving the foregoing message, when the access router determines that the terminal requests the IP address or prefix supporting the mobility, the terminal allocates a mobility-capable IP address or prefix to the terminal, and simultaneously sends the terminal to the location management server. The IP address-location relationship is saved by the location management server. The location information of the terminal may be an IP address of the access router. If the access router determines that the terminal requests an IP address or a prefix that does not support mobility, as described in step 202, the access router allocates an IP address or prefix that does not support mobility to the terminal, and does not update the location management server. Location information of the terminal.

It is worth noting that in the mobility management technology based on identity location separation, the IP address of the mobility-enabled IP address or the beginning of the prefix can use a special value, for example, starting with 10, with an IP address that does not support mobility or The prefix is distinguished.

Step 703: The access router returns an allocated IP address or prefix to the terminal, as shown in step 203. As described, the attribute description of the IP address or prefix may also be carried.

Through the method of the foregoing embodiment, when the terminal needs to obtain an IP address or prefix supporting mobility from the network, the network requests acquisition from the network. It should be noted that, if the terminal obtains an IP address or a prefix that does not support mobility from the network, when the IP packet is sent or received based on the IP address, the peer sends an IP packet to the terminal, and the destination address is the above-mentioned non-supporting mobile terminal. Sexual IP address. When the IP address arrives at the access router-peer, the access router-peer can determine that the IP address does not support mobility (for example, an address that starts with a non-10), then use the ordinary routing method to directly IP packets are sent without having to tunnel. On the other hand, the terminal sends and receives IP packets based on the mobility-enabled IP address or prefix, and the destination address of the IP packet sent by the peer to the terminal is set to the above-mentioned mobility-capable IP address of the terminal. When the IP packet arrives at the access router-peer, the access router-peer can determine that the IP address supports mobility (for example, an address starting with 10), and directly uses the above location-based routing method to directly use the IP address. The message is sent, for example, using the tunnel mode (the destination address of the outer IP encapsulation is set to the location of the terminal, the source address is set to the IP address of the access router-peer; the destination of the inner IP encapsulation is set to the IP address of the terminal, The source address is set to the peer IP address) to send data, or to replace the destination IP address (replace the IP address of the terminal with the IP address representing the location information of the terminal, and replace it when the packet arrives at the access router of the terminal. )send data.

Similarly, in the mobility management technology based on identity location separation, the access router also needs to know whether the terminal has the ability to distinguish between two IP addresses (ie, IP addresses that support mobility and does not support mobility). The principle is the same as that described in the second embodiment, and details are not described herein again.

Optionally, in step 701, the terminal sends an RS message to the access router to request an IP address or a prefix, where the terminal carries the foregoing indications in the message; the access router uses the RA response terminal to carry the terminal to the terminal. The IP address or prefix, and a description of the attribute carrying the IP address or prefix.

Embodiment 6

FIG. 8 is a flowchart of a sixth embodiment of the present invention. In this embodiment, when the mobility management technology of the identity location separation is applied, the terminal switches the scenario of the currently attached access router due to the mobile, for example, from the source. The incoming router switches to the target access router, which includes the following steps. Step 801, the same as step 301.

Step 802, the same as step 302.

Steps 803-804, when obtaining the IP address or prefix currently used by the terminal, the target access router determines whether the IP address or prefix currently used by the terminal has mobility. When it is judged that the IP address or prefix currently used by the terminal supports mobility, the target access router uses its own IP address as the new location information of the terminal, and updates the "IP address-location" relationship of the terminal in the location management server. If it is determined that the IP address or prefix currently used by the terminal does not support the mobility IP address or prefix, the target access router or the source access router notifies the terminal to release the IP address or prefix as described in steps 303-304.

The method for the target access router to determine whether the IP address or the prefix of the terminal supports the mobility is as described in the second embodiment, and the method and principle are the same, and details are not described herein again.

It should be noted that when the method of the embodiment of the present invention is applied to the mobility management technology based on identity location separation, the terminal may use the DHCP protocol as described in Embodiments 3 and 4. The principles and methods are similar. The only difference is that when the source access router determines that the terminal requests a mobility-capable IP address or prefix, it assigns a mobility-capable IP address to the terminal, and sends the terminal's "IP address-location" correspondence to the location management. server. At the time of handover, when the target access router determines that the IP address or prefix currently used by the terminal is mobility-supporting, the location management server updates the "IP address-location" saved for the terminal. The rest of the principles are similar and will not be described here.

The foregoing mobility management technology based on identity location separation can also be applied to an existing 3G network, and its corresponding architecture is as shown in FIG. In Figure 9, the GGSN corresponds to the above-mentioned access router, and the GGSN and the access router-peer end tunnel the IP address of the interaction between the terminal and the peer. It should be noted that the access router-peer can also be another GGSN. As mentioned above, the application of the mobility management technology that separates the location of the location to the existing 3G network also has the above problems.

Example 7

FIG. 10 is a flowchart of a seventh embodiment of the present invention. In a 3G network, when a terminal needs to use an IP address or a prefix supporting mobility, the network requests to allocate an IP address supporting mobility. The address or prefix specifically includes the following steps.

Step 1001: When the terminal needs to configure an IP address or prefix that supports mobility, send an Activate PDP (Packet Data Protocol) context request to the currently connected SGSN, where the request carries a configuration IP address or prefix that supports mobility. Instructions.

Step 1002: After receiving the message, the SGSN selects a GGSN for the terminal, and sends a Create PDP Context Request message to the GGSN, where the indication is also carried.

Step 1003: When receiving the foregoing Create PDP Context Request message, when the GGSN finds that the message carries the indication that the terminal requests to allocate an IP address or prefix supporting mobility, the terminal allocates a mobility-capable IP address or prefix to the terminal. It is worth noting that IP addresses or prefixes can be divided into two categories: IP addresses or prefixes that support mobility and do not support mobility. Optionally, the IP address or the beginning of the prefix is used to distinguish between the two types. For example, an IP address or a prefix that starts with 10 is a mobility-supporting IP address or a prefix, and a code that starts with 01 does not support mobility.

When the GGSN allocates a mobility-capable IP address or prefix to the terminal, it also sends a message to the location management server for the terminal, carrying the IP address or prefix assigned to the terminal and the location information of the terminal, and the location management server saves the information. Optionally, the location information of the terminal is an IP address of the GGSN.

Step 1004: The GGSN returns a Create PDP Context Response message to the SGSN, and carries the above IP address or prefix allocated for the terminal. Optionally, the message further carries attribute information of the IP address or prefix to inform the SGSN that the IP address or prefix is an IP address or prefix that supports mobility.

Step 1005: After receiving the foregoing message, the SGSN needs to save the IP address or prefix allocated for the terminal locally. Specifically, the IP address or prefix is saved in the PDP context information of the terminal. Optionally, the SGSN also records the foregoing attribute information of the IP address or prefix locally, for example, using the PDP TYPE parameter field in the PDP context to record whether the IP address or prefix supports mobility or does not support mobility.

It is worth noting that the GGSN can save the attribute information of the IP address or prefix locally. Specifically, the GGSN also saves the attribute information of the IP address or the prefix in the PDP context. As described above, both the SGSN and the GGSN save the attribute information of the IP address or prefix in the PDP context of the terminal. If the IP address or prefix in the PDP context supports mobility, the PDP context is referred to as a PDP context supporting mobility; if the IP address or prefix in the PDP context does not support mobility, it is referred to as not supporting mobility. PDP context.

Step 1006: The SGSN returns an activated PDP context response message to the terminal, and carries the allocated IP address or prefix, and also carries the foregoing attribute information, to inform the terminal that the IP address or prefix is an IP address or prefix that supports mobility.

Through the method in the foregoing embodiment, when the terminal needs to obtain an IP address or a prefix that supports mobility, the device requests the acquisition from the 3G network. In general, the terminal is based on the needs of the application, that is, when there is an application requiring the network to provide mobility support, the terminal requests the network to support the mobility IP address or prefix. It should be noted that if the application on the terminal does not need mobility support, the terminal may not carry the above indication when requesting the network to allocate an IP address or a prefix (or carry another indication to indicate that the request is an IP that does not support mobility. The address or prefix), the GGSN allocates an IP address or prefix that does not support mobility to the terminal and returns it to the terminal. At this time, the GGSN does not need to interact with the location management server, and the location management server does not need to maintain an "IP address-location" relationship for the terminal.

When the peer sends an IP packet to the terminal, if the terminal is based on the IP address or prefix that supports mobility, the access router-peer sends the IP packet to the tunnel first according to the location information of the terminal. The GGSN of the terminal is de-encapsulated by the GGSN and then sent to the terminal. If the terminal is based on an IP address or prefix that does not support mobility, the access router-peer directly sends the IP packet, and the ordinary routing mechanism will Send the IP packet to the terminal. As described above, the access router-peer can determine whether the terminal is based on support mobility or not based on mobility, based on the IP address of the terminal or the beginning of the prefix.

It is also worth noting that, as described in the first embodiment, the GGSN needs to be able to determine whether the terminal has the ability to recognize both IP addresses or prefixes (i.e., IP addresses or prefixes that support mobility and do not support mobility). If the GGSN determines that the terminal does not have the ability to identify the two types of IPs, when the terminal requests to obtain an IP address or prefix, the terminal is always assigned an IP address or prefix that supports mobility. The GGSN can determine whether the terminal has the ability to recognize both IPs by the following means.

In one method, the terminal having the above capability sends a request message (for example, a PDP context activation request message) to the SGSN, and always carries an indication indicating which IP address or prefix is needed in the request message, and the indication is The SGSN is sent to the GGSN (eg, by creating a context please The GGSN can determine, according to the indication, that the terminal has the foregoing capability; if the foregoing message is not carried in the message, the GGSN terminal does not have the foregoing capability.

Another method is: when the terminal first requests to obtain an IP address, another request is sent in the request message (for example, a PDP context activation request) sent to the SGSN, so that the user can distinguish the two IP addresses or prefixes, and then It is sent by the SGSN to the GGSN. If the indication is not carried, the GGSN determines that the terminal cannot distinguish the two types of IP addresses or prefixes.

In another method, the terminal notifies the network element in the network that the context information of the terminal is saved in the initial network access process (for example, the home location register). , HLR), Home Subscriber Server (HSS) or SGSN, etc.) The information is saved by the network element. Optionally, the terminal having the foregoing capability carries an indication in the message sent to the network element to indicate that the terminal has the capability; otherwise, the terminal that does not have the foregoing capability does not carry the indication in the message sent to the network element, when When the network element finds that the above indication is not carried in the received message, the GGSN determines that the terminal does not have the capability of distinguishing the two types of IP addresses or prefixes. At this time, the GGSN can learn from the network element that saves the context information of the terminal that the terminal has the ability to recognize the two IP addresses or prefixes.

Example eight

FIG. 11 is a flowchart of an eighth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached SGSN by using a mobile device, and triggers a handover of the attached GGSN. Specifically, the source GGSN is switched to the target GGSN, and specifically includes the following. step.

Step 1101: The terminal negotiates with the current serving Radio Network Controller (RNC) to initiate a process of switching the serving RNC.

Step 1102: The current serving RNC (source RNC) sends a redirection request to the SGSN (source SGSN) connected to the terminal to trigger the handover.

Step 1103: The source SGSN selects another SGSN (target SGSN) for the terminal, and sends a handover redirection request to the target SGSN, and carries the PDP context information of the terminal. The PDP context information carries the IP address or prefix currently used by the terminal, and also carries attribute information (supporting mobility or not supporting mobility) of these IP addresses or prefixes. Step 1104: After receiving the foregoing message, based on the foregoing PDP context information, the target SGSN interacts with the target RNC (ie, the RNC selected by the terminal and served by the terminal after the handover) to establish a radio bearer resource for the terminal.

Step 1105: The target SGSN returns a handover redirect response message to the source SGSN.

Step 1106: The source SGSN sends a redirect command to the source RNC.

Step 1107: The source RNC sends a redirect commit message to the target RNC.

Step 1108: The target RNC sends a redirect discovery message to the target SGSN.

Step 1109: The target RNC interacts with the terminal for mobility information.

Step 1110: The target RNC sends a redirect complete message to the target SGSN.

Step 1111: The target SGSN selects a GGSN for the terminal, for example, selects the GGSN closest to its topology as the target GGSN of the terminal.

Step 1112, assuming that the target GGSN selected by the target SGSN is not the GGSN (ie, source GGSN) connected before the terminal handover, the target SGSN determines whether the IP address or prefix of the terminal supports mobility. If the determination is yes, steps 1113-1116 are performed, and if the determination is no, steps 1117-1118 are performed.

Step 1113: When the target SGSN determines that the IP address of the terminal or the prefix is a mobility-enabled IP, send a PDP context request message to the target GGSN for the IP address or prefix, and carry the PDP context information related to the IP address or the prefix. This carries the IP address or prefix. Optionally, an indication indicating that it is an IP address or prefix supporting mobility is also carried.

Step 1114: After receiving the foregoing message, the target GGSN determines that the IP address or prefix corresponding to the PDP context to be created is mobility-capable, and therefore interacts with the location management server to update the location information of the IP address or prefix of the terminal. The location information can be the IP address of the target GGSN. Optionally, the target GGSN determines that the IP address or prefix is mobility-supported according to the carried indication in step 1113; the target GGSN may also determine, according to the local configuration information, whether the IP address or the prefix supports mobile Sex, for example, as described above, if the IP address or prefix starts with 10, the IP address or prefix is an IP address or prefix that supports mobility.

Step 1115: The target GGSN interacts with the source GGSN, and obtains context information related to the foregoing IP address or prefix from the source GGSN. Step 1116, the target GGSN returns a Create PDP Context Response message to the target SGSN. Step 1117: When the target SGSN determines that the IP address of the terminal or the prefix is an IP that does not support mobility, the target SGSN deactivates the PDP context corresponding to the IP address or the prefix. The target SGSN sends a delete PDP context request to the source GGSN to clear the information related to the above IP stored on the source GGSN.

Step 1118: The target SGSN sends a deactivation PDP context request to the terminal to notify the terminal to release the IP address or prefix. At this point, all services based on the IP address or prefix running on the terminal will be interrupted. Of course, based on the service request, the terminal can initiate a request to the network to acquire a new IP address or prefix.

Step 1119, subsequent related processes.

It can be seen that, in the process of the terminal handover, the target SGSN can selectively process according to whether the IP address or the prefix in the PDP context information of the obtained terminal supports mobility. A PDP context is created on the target GGSN for those IPs that support mobility. At this time, after the handover is completed, the IP address or prefix can continue to be used by the terminal; and for the IP that does not support mobility, the corresponding PDP context is deactivated. The terminal is caused to release the IP address or prefix, that is, after the handover is completed, the IP address or prefix cannot be used continuously.

It is to be noted that, in step 1113, the target SGSN may first send an update PDP context request message to the source GGSN, and carry an indication indicating the IP support mobility corresponding to the PDP context; the source GGSN sends a context push message to the target GGSN again. The Context Push message carries the PDP context information corresponding to the IP address or the prefix and the foregoing indication. After receiving the foregoing message, the target GGSN determines that the IP address or prefix supports mobility, as described in step 1114, and the location. Manage server interactions and update the location information of the terminal.

Example nine

FIG. 12 is a flowchart of a ninth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached SGSN by using a mobile device, and triggers handover of a attached GGSN, specifically, a handover from a source GGSN to a target GGSN, specifically including the following step.

Step 1201 is the same as step 1101. Steps 1202-1210 are the same as steps 1102-1110.

Step 1211: The target SGSN selects the GGSN for the terminal, and selects the GGSN closest to its topology as the target GGSN of the terminal.

Step 1212: The target SGSN sends a PDP Context Request message to the target GGSN, and carries the PDP context information of the terminal (obtained from the source SGSN) saved by the target SGSN, where the IP address or prefix used by the terminal is included.

Step 1213: After receiving the Create PDP Context Request message, the target GGSN sends a request to the source GGSN to obtain context information related to the PDP context to be created.

Step 1214: The source GGSN returns a response message to the target GGSN, and carries the information of the target GGSN request, and carries an indication that the IP address or prefix corresponding to the PDP context supports or does not support mobility.

Step 1215, the target GGSN returns a create context response message to the target SGSN.

Step 1216: The target GGSN can determine whether the IP address or the prefix of the terminal supports mobility (that is, whether the PDP context of the terminal supports mobility) according to the foregoing indication returned in step 1214. If yes, go to step 1217; if not, go to steps 1218-1220.

Step 1217: When the target GGSN determines that the IP address or the prefix is a mobility-enabled IP, interact with the location management server to update the location information of the terminal, as described in step 1114.

Step 1218: When the target GGSN determines that the IP address or the prefix is an IP that does not support mobility, the target GGSN deactivates the PDP context corresponding to the IP address or the prefix. Specifically, the target GGSN sends a delete PDP context request to the target SGSN to trigger deactivation of the PDP context.

Step 1219, the same step 1118.

Step 1220: The target SGSN returns a delete PDP context response to the target GGSN.

Step 1221, follow-up process.

It is worth noting that, as described above, in step 1214, the target GGSN can learn from the source GGSN whether the IP address or prefix of the terminal supports mobility. At this time, if the IP address or the prefix of the terminal does not support the mobility, the response to the failure to create the PDP context may be returned to the target SGSN in step 1215, and the flow of deactivating the PDP context corresponding to the IP address or the prefix is initiated to the target SGSN. Process, as described in steps 1117-1118.

Example ten

FIG. 13 is a flowchart of a fourth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached SGSN by using a mobile device and triggers handover of a attached GGSN, specifically, a handover from a source GGSN to a target GGSN, specifically including the following step.

Step 1301, the same step 1101.

Steps 1302-1310, the same steps 1102-1110.

Step 1311: The target SGSN learns the GGSN (source GGSN) connected to the terminal according to the acquired PDP context, and sends an update PDP context request to the source GGSN.

Step 1312: The source GGSN determines that it is not suitable for continuing to serve the terminal, and then selects a new GGSN for the terminal, and sends a message to the target GGSN to push the context information of the terminal, including the PDP context information of the terminal. It contains the IP address or prefix currently used by the terminal, and also includes the attribute of the IP address or prefix (supporting or not supporting mobility).

In step 1313, the target GGSN returns a response message to the source GGSN.

Step 1315: The target GGSN may determine whether the IP address or prefix of the terminal supports mobility according to the foregoing indication (attribute) obtained in step 1312, or may determine whether the PDP context of the terminal supports mobility. If yes, go to step 1316; if not, execute 1317-1319.

Step 1316: When the target GGSN determines that the IP address or the prefix is a mobility-enabled IP, interact with the location management server to update the location information of the terminal, as described in step 1114.

Steps 1317-1319, when the target GGSN determines that the IP address or the prefix is an IP that does not support mobility, the same steps 1218-1220.

Step 1320, follow-up process.

It is worth noting that in step 1312, the source GGSN is pushing the terminal to the target GGSN.

Before the PDP context, first determine whether the IP address or prefix corresponding to the PDP context supports mobility. If yes, perform step 1312 and subsequent steps; if not, do not The PDP context is sent to the target GGSN, and the source GGSN initiates a process of deactivating the PDP context. The specific execution process is similar to steps 1317-1319, except that the initiator of the process is the source GGSN.

Embodiment 11

FIG. 14 is a flowchart of a fifth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached SGSN by a mobile device and triggers handover of a attached GGSN, specifically, a handover from a source GGSN to a target GGSN, specifically including the following step.

Step 1401, the same as step 1101.

Step 1402, the same as step 1102.

Step 1403: In the same step 1103, the source SGSN selects the target SGSN for the terminal, and sends a handover redirection request to the target SGSN, and carries the PDP context information of the terminal. The PDP context information carries the IP address or prefix currently used by the terminal, and also carries the type of the IP address or prefix (support mobility or does not support mobility).

Step 1404: The target SGSN selects a GGSN for the terminal, for example, selects the GGSN closest to its topology as the target GGSN of the terminal.

Step 1405: The target SGSN determines whether the attribute of the IP address or the prefix corresponding to the received PDP context supports mobility or does not support mobility. If it is determined that the IP or prefix supports mobility, the target SGSN interacts with the target RNC to establish a radio bearer resource for the PDP context of the terminal. It is also possible to determine whether the above IP or prefix supports mobility based on the local configuration.

Step 1406: The target SGSN returns a handover redirection response message to the source SGSN, and confirms the PDP context supporting mobility (ie, the IP address or prefix corresponding to the PDP context supports mobility); meanwhile, instructs the source SGSN to deactivate the mobility that does not support mobility. PDP context.

Step 1407: The source SGSN sends a redirect command to the source RNC. As described above, the source SGSN deactivates the PDP context that does not support mobility. The specific procedure is similar to steps 1117-1118, except that the initiator of the process is replaced by the source SGSN.

Steps 1408-1411, the same steps 1107-1110.

Step 1412: Create a PDP context for the terminal in the target GGSN according to the target GGSN selected by the target SGSN in the foregoing step. It is worth noting that the PDP context at this time supports mobile Sexual PDP context. The specific procedures are the same as those in the eighth, ninth, and tenth embodiments, and are not described here. It is also worth noting that before performing step 1403, the source SGSN can determine whether the PDP context of the terminal supports mobility, that is, whether the IP address or prefix corresponding to the PDP context supports mobility or does not support mobility. At this time, the source SGSN carries only those PDP contexts supporting mobility in the handover redirection request sent to the target SGSN; and deactivates those PDP contexts that do not support mobility. In this way, in the subsequent process, the PDP context of the terminal acquired by the target SGSN must be a PDP context supporting mobility. Subsequent operations are the same as above, and there is no essential difference.

The foregoing mobility management technology based on identity location separation can also be applied to an existing LTE network, and its corresponding architecture is as shown in FIG. In Figure 15, the P-GW corresponds to the access router, and the P-GW and the access router-the peer end tunnel the IP packets exchanged between the terminal and the peer. It should be noted that the access router-peer can also be another P-GW. As described above, the application of the mobility management technology of the identity location separation to the existing LTE network also has the above problems.

Example twelve

16 is a flowchart of a twelfth embodiment of the present invention. In an LTE network, when a terminal needs to use an IP address or a prefix that supports mobility, the terminal requests a network to support an IP address or a prefix that supports mobility, including The following steps.

Step 1601: Send an attach request to the base station (ie, the eNodeB) when the terminal initially accesses the network, and if the terminal wants to request the IP address or prefix supporting the mobility, the attach request carries an indication to request to configure the IP address or prefix supporting the mobility. .

Step 1602: The eNodeB sends the foregoing attach request to a Mobility Management Entity (MME), which also carries the foregoing indication.

Step 1603: Send a create session request to the S-GW, where the above indication is also carried. Step 1604: The S-GW selects a P-GW for the terminal, and then sends a Create Session Request message to the P-GW, where the indication is carried.

Step 1605, after receiving the above-mentioned session creation request message, when the P-GW discovers that the message is carried in the message When the above terminal requests to allocate an IP address or prefix that supports mobility, the terminal is assigned a mobility-capable IP address or prefix.

It is worth noting that, as described in step 1003, IP addresses or prefixes can be classified into two categories: IP addresses or prefixes that support mobility and do not support mobility. Optionally classify the two classes with an IP address or the beginning of the prefix. Similarly, as described in step 1003, when the P-GW allocates a mobility-capable IP address or prefix to the terminal, the terminal also sends a message to the location management server for the terminal, carrying the IP address or prefix assigned to the terminal, and the terminal. Location information, which is saved by the location management server. Optionally, the location information of the terminal is an IP address of the P-GW.

Step 1606: The P-GW returns a create session response message to the S-GW, and carries the above IP address or prefix assigned to the terminal. Optionally, the message further carries attribute information of the IP address or prefix to notify the S-GW that the IP address or prefix is an IP address or prefix that supports mobility.

Step 1607: The S-GW returns a create session response message to the MME, and also carries the foregoing IP address or prefix, and the foregoing attribute information.

Step 1608, the MME needs to save the above-mentioned IP address or prefix assigned to the terminal, for example, save the IP address or prefix in the PDN context of the terminal. Optionally, the MME also saves the attribute information of the IP address or the prefix in the PDN context, for example, using the PDN TYPE field to save the attribute information.

Steps 1609-1610, the MME returns an attach accept message to the eNodeB, where the IP address or prefix and the attribute information are carried. The eNodeB returns an attach accept message to the terminal, where the IP address or prefix and the attribute information are carried.

It is worth noting that the P-GW can store the attribute information of the IP address or the prefix locally. Specifically, the P-GW also stores the attribute information of the IP address or the prefix in the PDN context. As described above, the MME and the P-GW both store the attribute information of the IP address or the prefix in the PDN context of the terminal. If the IP address or prefix in the PDN context supports mobility, the PDN context is referred to as a PDN context supporting mobility; The IP address or prefix in the PDN context does not support mobility, so it is called PDN context that does not support mobility.

With the method of the foregoing embodiment, when the terminal needs to obtain an IP address or prefix supporting mobility, when the terminal initially accesses the network, the terminal requests the IP address or prefix supporting the mobility from the LTE network. It should be noted that, after the initial network access, the terminal requests the LTE network to allocate an IP address or a prefix (that is, an IP address or a prefix that supports mobility or does not support mobility), and may send a PDN connection request to the MME through the eNodeB. PDN Connectivity Request ) and carry the above instructions. With the above method in this embodiment, the message is sent to the S-GW, and the S-GW sends a message to the P-GW to allocate an IP address or prefix for the terminal request. In the same way, the P-GW allocates an IP address or prefix that supports mobility or does not support mobility to the terminal, and sends it to the MME. At this time, the MME uses the PDN Connectivity Accept message to allocate the IP address. Or the prefix and its attributes are sent to the terminal.

It should also be noted that, as described in the first embodiment, the P-GW needs to be able to determine whether the terminal has the same IP address or prefix (ie, IP address or prefix that supports mobility and does not support mobility). ability. If the P-GW determines that the terminal does not have the ability to recognize the two types of IPs, when the terminal requests to obtain an IP address or prefix, the terminal is always assigned an IP address or prefix that supports mobility. The P-GW can determine whether the terminal has the ability to recognize the two IPs by:

In one method, the terminal having the above capability sends a request message (for example, an attach request message, a PDN connection request message) to the MME, and always carries an indication indicating which IP address or prefix is required by the terminal in the request message. The indication is sent by the MME to the P-GW through the S-GW (eg, by creating a session request message), and the P-GW can determine, according to the indication, that the terminal has the foregoing capability; if the message does not carry the indication, then P- The GW determines that the terminal does not have the above capabilities.

Another method is: when the terminal first requests to obtain an IP address, another request is sent in the request message (for example, an attach request message) sent to the MME, so that the user can distinguish the two IP addresses or prefixes, and then The MME transmits to the P-GW through the S-GW. If the indication is not carried in the request message, the P-GW determines that the terminal cannot distinguish the two types of IP addresses or prefixes.

In another method, the terminal notifies the network element in the network that the context information of the terminal is saved (eg, HLR, HSS, MME, etc.) in the initial network access process. , the information is saved by the network element. Optionally, the terminal having the foregoing capability carries an indication in the message sent to the network element to indicate that the terminal has the capability; otherwise, the terminal that does not have the foregoing capability does not carry the indication in the message sent to the network element, when When the network element finds that the above indication is not carried in the received message, the P-GW determines that the terminal does not have the capability of distinguishing the two IP addresses or prefixes. At this time, when the P-GW can save the context information of the terminal from the above The network element knows whether the terminal has the ability to recognize the two IP addresses or prefixes.

Example thirteen

FIG. 17 is a flowchart of a thirteenth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached S-GW due to mobility, and triggers handover of an attached P-GW, specifically, switching from a source P-GW. To the target P-GW, the following steps are specifically included.

Step 1701: The eNodeB (source eNodeB) to which the terminal is currently attached and the eNodeB (target eNodeB) to which the terminal is to be handed over negotiate to decide to initiate a handover to the terminal.

Step 1702: The source eNodeB sends a handover request to the MME.

Step 1703: The MME determines whether the IP address or prefix currently used by the terminal supports mobility, that is, whether the PDN context of the terminal supports mobility. If not, step 1704 is performed. If yes, steps 1705-1714 are performed.

Step 1704: When the MME determines that the PDN context of the terminal does not support mobility, the MME deletes the PDN context (ie, performs PDN Disconnection). Specifically, the MME deletes the PDN context (ie, deletes the PDN connection) that does not support mobility by deleting the session request message to the S-GW (source S-GW) currently connected by the terminal.

Steps 1705-1706, when the MME determines that the PDN context of the terminal supports mobility, sends a create session request to the S-GW (target S-GW) to which the terminal is to be handed, where the PDN context information of the terminal is carried, including the IP of the terminal. The address or prefix, and carries the attribute of the IP address or prefix. The target S-GW returns a Create Session Reply message to the MME.

Step 1707: The MME and the target eNodeB exchange a handover request or a confirmation message.

In steps 1708-1709, the MME sends a handover command to the target eNodeB; the eNodeB sends a handover command to the terminal.

Step 1710: The terminal sends a handover confirmation message to the target eNodeB.

Step 1711: The target eNodeB sends a handover advertisement to the MME.

Step 1712: The MME sends a modify bearer request message to the target S-GW, where the MME carries the attribute of the IP address or prefix of the terminal. Step 1713: The target S-GW selects the P-GW as the target P-GW for the terminal, and sends a create session request to the target P-GW, carrying the PDN context, and indicating that the PDN context is a PDN context supporting mobility. The target P-GW requests the source P-GW (i.e., the P-GW to which the terminal attaches before the handover) to request other contexts associated with the terminal, while returning a Create Session Reply message to the target S-GW. And, since the PDN context is a PDN context supporting mobility, the target P-GW allocates new location information to the terminal and updates it to the location management server.

Step 1714: The target S-GW returns a modify bearer response message to the MME.

Step 1715, follow-up process.

It can be seen that, in the process of the terminal handover, the MME can selectively perform processing according to whether the IP address or the prefix in the PDN context information of the terminal supports mobility. Create a PDN context on the target P-GW for those IP triggers that support mobility. At this time, after the handover is completed, the IP address or prefix can continue to be used by the terminal; and for the IP that does not support mobility, the corresponding PDN context is deleted. , prompting the terminal to release the IP address or prefix, that is, after the handover is completed, the IP address or prefix cannot be used continuously.

Embodiment 14

FIG. 18 is a flowchart of a fourteenth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached S-GW due to movement, and triggers handover of an attached P-GW, specifically, switching from a source P-GW. To the target P-GW, the following steps are specifically included.

Steps 1801-1802, the same steps 1701-1702.

Step 1803: The MME sends a create session request message to the target S-GW, which carries the PDN context of the terminal, where the IP address or prefix currently used by the terminal is carried. Optionally, the PDN context also carries the attribute of the IP address or prefix (supporting mobility or not supporting mobility).

Step 1804: The target S-GW selects a P-GW as the target P-GW for the terminal. When the target P-GW is not the source P-GW used by the terminal, the target S-GW checks whether the IP address or prefix of the terminal supports the mobile. Sex. The target S-GW returns a create session response message to the MME. The Create Session Reply message instructs the MME to release the PDN context corresponding to the IP address or prefix that does not support mobility. Step 1805: The MME initiates deleting the corresponding PDN context according to the indication in the message returned by the target S-GW, as described in step 1704.

Steps 1806-1810, for supporting the mobility IP address or prefix, the target S-GW does not instruct the MME to release the corresponding PDN context. The MME performs the processing in accordance with the method described in steps 1707-1711.

Step 1811: The MME sends a modify bearer request to the target S-GW, where the IP address or prefix of the terminal and its attributes are carried.

It is to be noted that, in step 1803, the target S-GW may not process whether the IP address or the prefix of the terminal supports mobility, that is, the indication is not returned to the MME in step 1804 to instruct the MME to release the unsupported mobile. The IP address or the PDN context corresponding to the prefix. At this time, in this step, the above processing can be performed. That is, if the IP address or the prefix of the terminal does not support the mobility, the target S-GW may carry the foregoing indication in the modified bearer response message returned to the MME, and then the MME initiates release of the corresponding PDN context according to the indication.

Step 1812, as described in the above 1713.

Step 1813: The target S-GW returns a modify bearer response message to the MME.

Step 1814, the subsequent process.

Example fifteen

FIG. 19 is a flowchart of a fifteenth embodiment of the present invention, which describes a scenario in which a terminal switches a currently attached S-GW due to mobility, and triggers handover of an attached P-GW, specifically, switching from a source P-GW. To the target P-GW, the following steps are specifically included.

Steps 1901-1902, the same steps 1701-1702.

Steps 1903-1904, the MME sends a create session request message to the target S-GW, which carries the PDN context of the terminal, where the IP address or prefix currently used by the terminal is carried. Optionally, the PDN context also carries an attribute of the IP address or prefix. The target S-GW returns a Create Session Answer message to the MME.

Steps 1905-1909, the same steps 1707-1711.

Step 1910: The MME sends a modify bearer request to the target S-GW, where the IP address of the terminal is carried. The address or prefix, and its attributes.

Step 1911: The target S-GW selects a new P-GW (ie, the target P-GW) for the terminal, and sends a create bearer request message to the target P-GW, where the PDN context is carried, where the IP address of the terminal is included. The address or prefix, and its attributes.

Step 1912: The target P-GW interacts with the source P-GW to obtain context information of the terminal (for example, PDN context information saved by the P-GW). At this time, the source P-GW may inform whether the IP address or the prefix of the target P-GW terminal supports mobility, and therefore, in step 1911, the target S-GW may not notify the IP address or prefix of the target P-GW terminal. Attributes.

Steps 1913-1914, the target P-GW returns a create bearer reply message to the target S-GW; the target S-GW returns a modify bearer reply message to the MME.

Step 1915: The target P-GW determines whether the IP address or prefix of the terminal supports mobility. As described above, the target P-GW may determine according to the indication obtained from the target S-GW or the source P-GW; or the target P-GW may determine according to the local configuration information, for example, an IP starting with 10 The address or prefix is an IP address or prefix that supports mobility. The IP address or prefix that is not starting with 10 is an IP address or prefix that does not support mobility. When the determination is yes, step 1916 is performed, and if the determination is no, step 1917 is performed.

Step 1916: When the target P-GW determines that the IP address or prefix of the terminal supports mobility, the terminal updates the location information of the terminal to the location management server. The location information can be the IP address of the target P-GW.

Step 1917: When the target P-GW determines that the IP address or prefix of the terminal does not support mobility, the target P-GW initiates release of the PDN context corresponding to the IP address or the prefix. Specifically, the target P-GW triggers deletion of the corresponding PDN context (or deletes the PDN connection) by sending a delete bearer request message to the target S-GW.

Step 1918, follow-up process.

It should be noted that when the target P-GW determines that the IP address or prefix of the terminal does not support mobility, the target P-GW may also notify the source P-GW to trigger the deletion of the PND connection. For example, in step 1912, the target P-GW carries an indication in the response message to the source P-GW to obtain the context information, so that the source P-GW initiates the step of deleting the PND connection. Alternatively, the target P-GW requests the source P-GW to access the terminal. In the case of the text information, the source P-GW directly determines whether the IP address or the prefix of the terminal supports the mobility. When it is determined that the IP address is not supported, the source P-GW directly initiates the process of deleting the PDN context.

It should also be noted that, when receiving the modify bearer request message described in step 1910, the terminal may also perform the operation of switching to the target P-GW according to the following steps.

Step 1911a: The target S-GW sends a modify bearer request message to the source P-GW.

In step 1912a, when the source P-GW receives the above message, it selects a new P-GW for the terminal, that is, the target P-GW. At this time, the source P-GW determines whether the IP address or the prefix of the terminal supports the mobility. For the IP address or the prefix that does not support mobility, as described above, the source P-GW directly initiates the process of deleting the PDN context, so that the terminal does not release. The IP address or prefix supporting the mobility; For the IP address or prefix supporting mobility, the source P-GW sends the PDN context information to the target P-GW, and creates PDN context information for the terminal on the target P-GW.

Step 1913a: The source P-GW returns a modify bearer response message to the target S-GW.

Step 1914a, the target S-GW returns a modify bearer response message to the MME.

Step 1915a, follow-up process.

In the foregoing embodiments, the terminal may have multiple PDP contexts or PDN contexts,

When the PDN context supports mobility, each PDP context or PDN context is judged separately.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. Embodiments of the invention are not limited to any particular form of combination of hardware and software.

Industrial applicability

In the embodiment of the present invention, the traffic required by the loop is greatly reduced, thereby reducing the load of the bearer network and the pressure of the anchor network element.

Claims

Claim

A method for requesting access to an Internet Protocol (IP) supporting mobility, comprising: after an access router receives a request message sent by a terminal, the access router allocates an IP address or a prefix to the terminal, The terminal has the ability to distinguish between an IP address or a prefix that supports mobility and does not support mobility, and when the request message requests an IP address or a prefix that supports mobility, the access router acquires mobility support. An IP address or prefix, and returning the IP address or prefix supporting the mobility to the terminal.

2. The method of claim 1 further comprising:

3. The method of claim 1 further comprising:

After the access router receives the request message, the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and the request message requests an IP that does not support mobility. In the case of an address or a prefix, the access router allocates an IP address or prefix that does not support mobility to the terminal, and returns the IP address or prefix that does not support mobility to the terminal.

4. The method of claim 1 further comprising:

5. The method of claim 1, wherein

The access router requests the access router to obtain an IP address or Whether the prefix carries a preset capability indication, and determines whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility;

6. The method of claim 1 further comprising:

After the terminal is switched from the source access router to the target access router, the target access router acquires an IP address or a prefix currently used by the terminal, and determines whether the IP address or prefix currently used by the terminal supports mobility. If supported, the target access router interacts with the anchor network element of the terminal to update the mobility context of the terminal; if not, the target access router notifies the terminal to release the current The IP address or prefix used; or the target access router sends a notification to the source access router, and the source access router notifies the terminal to release the currently used IP address or prefix.

7. The method of claim 6, wherein

8. The method of claim 1, wherein

9. The method according to any one of claims 1 to 5, wherein The step of the access router acquiring the IP address or the prefix that supports the mobility includes: the access router assigning the IP address or prefix that supports the mobility to the terminal; the method further includes:

10. The method of claim 9 further comprising:

11. The method of claim 9 further comprising:

After the terminal is switched from the source access router to the target access router, the target access router acquires an IP address or prefix currently used by the terminal, and determines whether the IP address or prefix currently used by the terminal is Supporting mobility, if supported, the target access router updates the location information of the terminal to the location management server; if not, the target access router notifies the terminal to release the currently used IP Or an address or a prefix; or, the target access router sends a notification to the source access router, and the source access router notifies the terminal to release the currently used IP address or prefix.

12. The method according to any one of claims 1 to 5, wherein

The method further includes:

Sending, by the GGSN, the IP address or prefix supporting the mobility to the location management server and Location information of the terminal.

13. The method of claim 12, further comprising:

14. The method of claim 12, further comprising:

After the terminal switches from the SGSN to the target SGSN, and when the target SGSN or the GGSN is the target GGSN selected by the terminal other than the GGSN, the target SGSN or GGSN determines the IP address of the terminal. Or whether the prefix supports mobility;

For the IP address or prefix supporting mobility, the target SGSN or GGSN triggers the target GGSN to create a PDP context for the IP address or prefix supporting mobility, and updates the location information of the terminal to the location management server. ;

For an IP address or prefix that does not support mobility, the target SGSN or GGSN deactivates the PDP context corresponding to the IP address or prefix that does not support mobility.

15. The method of claim 12, further comprising:

16. The method of claim 15, wherein

The target GGSN receives the Create PDP Context Request message sent by the target SGSN. And sending a request to the GGSN to obtain the context information related to the PDP context to be created; and receiving the response message returned by the GGSN, where the response message carries the IP corresponding to the PDP context to be created. Whether the address or the prefix supports the indication of the mobility; or, after receiving the update PDP context request of the target SGSN, the GGSN pushes the context information to the target GGSN, where the target GGSN receives the context information, where The context information carries an indication of whether the IP address or prefix currently used by the terminal supports mobility.

17. The method of claim 12, further comprising:

18. The method of claim 12, further comprising:

For the IP address or prefix supporting mobility, the SGSN sends the PDP context corresponding to the mobility-enabled IP address or prefix to the target SGSN through the redirect request; for an IP address that does not support mobility or The prefix, the SGSN deactivates the PDP context corresponding to the IP address or prefix that does not support mobility.

19. The method according to any one of claims 1 to 5, wherein

When the access router is a packet data network gateway (P-GW):

The step of the access router acquiring an IP address or prefix supporting mobility and returning the IP address or prefix supporting the mobility to the terminal includes: The P-GW allocates the IP address or prefix supporting the mobility to the terminal, and sends the mobility-enabled IP address or prefix to the mobility management entity (MME) through the serving gateway (S-GW). Returning, by the MME, the IP address or prefix that supports mobility to the terminal; the method further includes:

20. The method of claim 19, further comprising:

21. The method of claim 19, further comprising:

For the IP address or prefix supporting mobility, the target S-GW or P-GW triggers the target P-GW to create a PDN context for the IP address or prefix supporting mobility, and updates to the location management server Location information of the terminal;

For the IP address or prefix that does not support mobility, the target S-GW or P-GW deletes the PDN context corresponding to the IP address or prefix that does not support mobility.

22. The method of claim 19, further comprising:

For the IP address or prefix that does not support mobility, the target P-GW deletes the unsupported move a dynamic IP address or a PDN context corresponding to the prefix;

23. A network side, comprising: an access router, where:

The access router is configured to: after receiving a request message from the terminal requesting the access router to allocate an Internet Protocol (IP) address or a prefix to the terminal, when the terminal has differentiated support mobility and does not support mobile a capability of a sexual IP address or a prefix, and the request message requests an IP address or prefix supporting mobility, obtains an IP address or prefix supporting mobility, and returns the mobility support to the terminal. IP address or prefix.

24. The network side of claim 23, wherein

25. The network side of claim 23, wherein

The access router is further configured to: after receiving the request message, when the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, and the request message requests that is not supported When the IP address or prefix of the mobility is used, the terminal is assigned an IP address or prefix that does not support mobility, and the IP address or prefix that does not support mobility is returned to the terminal.

26. The network side of claim 23, wherein

27. The network side of claim 23, wherein

Determining, according to the indication in the request message whether the IP address or the prefix is required by the terminal, whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility; Whether the terminal carries a preset capability indication, and determines whether the terminal has the capability of distinguishing between an IP address or a prefix that supports mobility and does not support mobility, when the terminal requests the access router to obtain an IP address or a prefix for the first time;

28. The network side of claim 23, the network side further comprising a target access router, where:

The target access router is configured to: after the terminal switches from the source access router to the target access router, obtain an IP address or prefix currently used by the terminal, and determine an IP address currently used by the terminal or Whether the prefix supports mobility, if supported, interacting with the anchor network element of the terminal, updating the mobility context of the terminal; if not, notifying the terminal to release the currently used IP address or prefix Or sending a notification to the source access router; the access router is further configured to: notify the terminal to release the currently used IP address or prefix.

29. The network side of claim 28, wherein

30. The network side of claim 23, wherein

When the request message requests an IP address or a prefix supporting mobility, interacting with an anchor network element, and receiving the IP address or the front of the mobility-supported IP address allocated by the anchor network element to the terminal Embellished.

31. The network side according to any one of claims 23 to 27, wherein

Allocating the IP address or prefix supporting the mobility to the terminal;

32. The network side according to claim 31, wherein

33. The network side of claim 28, the network side further comprising a target access router, where:

34. The network side according to any one of claims 23 to 27, wherein

When the access router is a GGSN:

The SGSN is configured to: return the IP address or prefix supporting the mobility to the terminal.

35. The network side of claim 34, the network side further comprising the SGSN, wherein: the GGSN is further configured to: carry attribute information, to inform the SGSN that the IP address or prefix is to support mobility IP address or prefix;

36. The network side of claim 34, wherein

37. The network side of claim 34, wherein:

The target SGSN is configured to: after the terminal switches from the SGSN to the target SGSN, and when the target SGSN is the target GGSN selected by the terminal other than the GGSN, determine the IP address of the terminal or Whether the prefix supports mobility:

38. The network side of claim 34, the network side further comprising a target GGSN, wherein: the target GGSN is configured to: when the terminal switches from the SGSN to the target SGSN, the GGSN, determine Whether the IP address or prefix of the terminal supports mobility; Updating the location information of the terminal to the location management server for an IP address or prefix supporting mobility;

39. The network side of claim 38, wherein

Or receiving the context information pushed by the GGSN, where the context information carries an indication of whether the IP address or the prefix of the terminal supports mobility.

40. The network side of claim 34, the network side further comprising a target SGSN, wherein: the target SGSN is further configured to: switch from the SGSN to the target at the terminal

In the process of the SGSN, after receiving the redirection request sent by the SGSN, determining whether the IP address or the prefix of the terminal carried in the redirection request supports mobility;

The network side of claim 34, the network side further includes an SGSN, wherein the SGSN is further configured to: when the terminal switches from the SGSN to the target SGSN, to the Before the target SGSN sends the redirection request, determining whether the IP address or the prefix of the terminal supports mobility;

Sending, to the target SGSN, the PDP context corresponding to the IP address or the prefix supporting the mobility, by using the redirect request to the target SGSN; For the IP address or prefix that does not support mobility, the IP address or the PDP context corresponding to the prefix that does not support mobility is deactivated.

The network side according to any one of claims 23 to 27, wherein the network side further includes an MME, where

When the access router is the P-GW:

The P-GW is configured to: allocate the IP address or prefix supporting the mobility to the terminal, and send the IP address or prefix supporting the mobility to the MME through an S-GW; and, to the location management Sending, by the server, the IP address or prefix supporting mobility and location information of the terminal;

The MME is configured to: return the IP address or prefix supporting the mobility to the terminal.

43. The network side of claim 42, wherein

Deleting the IP data address that does not support mobility or the packet data network (PDN) context corresponding to the prefix for an IP address or prefix that does not support mobility;

44. The network side of claim 42, wherein

The P-GW is further configured to: after the terminal switches from the S-GW to the target S-GW, and when the P-GW is the target P-GW selected by the terminal is not the P-GW, determine Whether the IP address or prefix of the terminal supports mobility;

45. The network side of claim 42, the network side further comprising a target S-GW, wherein: the target S-GW is further configured to: the terminal switches from the S-GW to the target S After the GW, and when the target P-GW selected by the target S-GW for the terminal is not the P-GW, determining whether the IP address or prefix of the terminal supports mobility;

The network side of claim 42, the network side further comprising a target P-GW, wherein the target P-GW is configured to: the terminal switches from the P-GW to the target P- In the process of the GW, determining whether the IP address or the prefix of the terminal supports mobility;

Deleting the IP address that does not support mobility or the PDN context corresponding to the prefix for an IP address or prefix that does not support mobility;

The location information of the terminal is updated to the location management server for an IP address or prefix supporting mobility.

47. A method for requesting access to an Internet Protocol (IP) address supporting mobility, comprising: a terminal sending a request message to an access router, requesting the access router to allocate a mobility-capable IP address or prefix to the terminal.

48. A terminal, configured to: send a request message to an access router, requesting the access router to allocate a mobility-capable IP address or prefix to the terminal.