WO2008119296A1

WO2008119296A1 - A method and device for performing mobility management protocol negotiation

Info

Publication number: WO2008119296A1
Application number: PCT/CN2008/070592
Authority: WO
Inventors: Hai Liu; Sihong Zhou; Wenruo Zhu; Liang Gu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-04-02
Filing date: 2008-03-26
Publication date: 2008-10-09
Also published as: CN101282287A; CN101282287B

Abstract

A method and device for performing mobility management protocol negotiation. In the method of the present invention, the netwok side receives the IP capability indicating information of a terminal which is sent from the terminal, wherein the IP capability indicating information indicates whether the terminal supports the client based mobility management protocol; the network side selects a corresponding mobility management protocol according to the capability indicating information, or selects a mobility management protocol according to the capability indicating information and information on the network side; if the network side has selected the network based mobility management protocol and the capability indicating information indicates that the terminal supports the client based mobility management protocol, the network side sends an instruction message to the terminal to instruct the terminal to stop the initiation of the flow of the client based mobility management protocol. With the present invention, it is possible that the terminal informs the network of the mobile IP capability in a explicit form and the network side informs the terminal of the selection of the mobility management protocol explicitly. Thus it is realized that the mobility management protocol is decided by the network side.

Description

Method and device for negotiating mobility management protocol

Technical field

The present invention relates to the field of communications, and in particular, to a method and apparatus for negotiating a mobility management protocol. Background technique

In order to ensure the competitiveness of the 3GPP (3rd Generation Partnership Project) system in the next 10 years and beyond, an access technology evolution is being carried out within the 3GPP organization. In particular, in order to enhance the ability of 3GPP systems to handle rapidly growing IP data services, the use of packet technology within 3GPP systems requires further enhancement. The most important parts of this type of technology evolution include: reduced latency, higher user data rates, increased system capacity and coverage, and lower overall carrier costs. Moreover, the evolved network structure is also an important indicator for the backward compatibility of existing networks.

The SAE (System Architecture Evolution) project has a goal to integrate access technologies defined by other non-3GPP organizations, such as WLAN (Wireless Local Area Network) and WiMAX (Worldwide Interoperability for Microwave Networks) technologies. Moreover, users need to roam and switch between different access technologies. To achieve this goal, the SAE project decided to adopt mobile IP technology for mobility management.

The basic principle of mobile IP technology is: When the terminal moves, it can not change its home address. When the terminal moves to a non-home network, it can get a care-of address belonging to the current network, and tie the care-of address and the home address of the terminal. When the packet is sent to the home address of the terminal, the home agent of the terminal sends the data packet to the care-of address to complete the routing.

Currently, there are two types of mobile IP technologies: CMIP (Client MIP, host-based mobile IP, which can be subdivided into CMIPv4 and CMIPv6 by IP version) and PMIP (Proxy MIP, proxy mobile IP, which can be subdivided by IP version. For PMIPv4 and PMIPv6). CMIP is a host-based mobile IP technology that requires terminals to participate in the mobile IP signaling process. PMIP is web based Mobile IP technology does not require the terminal to participate in the mobile IP process, and the network will initiate the mobile IP binding by the proxy terminal. DSMIP (dual stack MIP) can be classified into CMIP-class, and the principle is similar to CMIP, except that it can support mobile IP technology between IPv4 and IPv6 versions. At present, both types of technologies have their own advantages and disadvantages, and have been adopted by the SAE project.

Referring to FIG. 1 , it is a schematic diagram of a non-roaming architecture of a SAE system in the prior art.

As shown in Figure 1, the core network of the wireless evolved network mainly includes three logical function modules: MME (Mobility Management Entity), Serving SAE Gateway (service SAE gateway) and PDN SAE Gateway (shared data network SAE gateway). . The MME is a mobility management module responsible for mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, security functions, and the like. The Serving SAE Gateway directly faces the access of the 3GPP access system and is the user plane anchor between the 3GPP internal access systems. In the roaming scenario, the Serving SAE Gateway can serve as a local user between the non-3GPP access system and the 3GPP access system. Face anchor, a user can only have one Serving SAE Gateway in a period of time; PDN SAE Gateway is a user plane anchor between the 3GPP access system and the non-3GPP system in the SAE, providing users with PDN access, one user can simultaneously Have multiple PDN SAE Gateways. The function and presence of each interface in Figure 1 is still not finalized. In Figure 1, the Serving SAE Gateway and the PDN SAE Gateway form the SAE GW (SAE Gateway). How the MME, Serving SAE Gateway and PDN SAE Gateway modules are combined in the corresponding entity is also undetermined.

A way of partitioning non-3GPP networks by trusted non-3GPP networks and untrusted non-3GPP networks based on factors such as security characteristics of non-3GPP access networks. Untrusted non-3GPP networks must be connected through a network entity ePDG (evolved Packet Data Gateway). Currently, WLAN networks fall into the category of untrusted non-3GPP networks; WiMAX networks fall into the category of trusted non-3GPP networks.

WLAN is a widely-present wireless access system, and 3GPP has defined the interworking between WLAN and 3GPP systems. Referring to FIG. 2, it is a schematic diagram of an architecture of interworking between a WLAN system and a 3GPP system in the prior art. The SLF in the figure is Service Location Function, service location function; WAG is WLAN Access Gateway, WLAN access gateway; OCS is Online Charging System, online charging system; Offline Charging System is offline charging system. The architecture is applicable not only to WLAN access systems, but also to any IP-based access methods such as WiMAX and ADSL.

WiMAX is a wireless broadband access technology. In order to solve the mobility of terminals in WiMAX networks, WiMAX adopts mobile IP technology and is adopted by CMIP and PMIP technologies. Therefore, there is a problem of protocol identification in WiMAX. WiMAX currently provides a way to differentiate between CMIP and PMIP under the IPv4 version.

In a WiMAX system, the terminal first establishes a layer 2 connection to the WiMAX network. Whether the network uses PMIP or CMIP depends on whether the terminal initiates a DHCP (Dynamic Host Configuration Protocol) process. If the terminal initiates a DHCP process, the terminal does not have the mobile IP. Capabilities, network agents use PMIP for registration; otherwise CMIP registration.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: Only the CMIPv4 FA-CoA mode and the PMIPv4 mode can be distinguished. Because in CMIPv4 FA-CoA mode, the terminal's care-of address (CoA) is obtained through FA broadcast, not through the DHCP process. Therefore, in this case, it can be considered that a DHCP process requires a PMIP process, otherwise a CMIP process is required. However, in other cases, such as CMIPv4 CO-CoA mode and PMIPv4 mode, or CMIPv6 and PMIPv6, the terminal may obtain the address through DHCP. At this time, if there is a DHCP process to distinguish the PMIP process or the CMIP process, it is no longer It may be. Summary of the invention

An embodiment of the present invention provides a method for negotiating a mobility management protocol, so that the terminal explicitly notifies the mobility management protocol adopted by the network side, and the method includes the following steps:

The network side receives the mobile IP capability indication information of the terminal sent by the terminal; The capability indication information is: selecting a mobility management protocol corresponding to the capability indication information; or selecting the adopted mobility management protocol according to the capability indication information and the network side information.

Another embodiment of the present invention provides an apparatus for negotiating a mobility management protocol, the apparatus comprising:

a receiving module, configured to receive mobile IP capability indication information of the terminal sent by the terminal, and a selecting module, configured to select, according to the capability indication information received by the receiving module, a mobility management protocol corresponding to the capability indication information; Or, according to the capability indication information and the network side message, ^ select a mobility management protocol.

In the foregoing embodiment of the present invention, the mobile terminal is configured to send the mobile IP capability indication information to the network side, so that the network side can select the corresponding mobility management protocol according to the capability indication information, or select according to the capability indication information and the network side information. The appropriate mobility management protocol overcomes the limitation of the network in selecting and judging the mobility management protocol in the prior art, so that the network side selects the mobility management protocol according to the indication of the terminal, thereby interacting with the mobility management protocol process. The specific implementation is irrelevant and improves scalability. DRAWINGS

1 is a schematic diagram of a non-roaming architecture of a SAE system in the prior art;

2 is a schematic structural diagram of interworking between a WLAN system and a 3GPP system in the prior art; FIG. 3 is a schematic flowchart of a negotiated mobility management protocol according to an embodiment of the present invention;

4 is a flow chart of attaching a CMIP to a SAE network after negotiation according to the first embodiment of the present invention;

FIG. 5 is a flow chart of attaching a PMIP to a SAE network after negotiation according to the first embodiment of the present invention;

FIG. 6 is a flowchart of performing network switching by using CMIP after negotiation according to Embodiment 2 of the present invention; FIG. 7 is a flowchart of performing network switching by using PMIP after negotiation according to Embodiment 2 of the present invention; FIG. 8 is a flowchart of Embodiment 3 of the present invention; Negotiating the process of CMIP for SAE network attachment Figure

9 is a flow chart of attaching a PMIP to a SAE network after negotiation according to Embodiment 3 of the present invention;

FIG. 10 is a flowchart of performing network switching by using CMIP after negotiation according to Embodiment 4 of the present invention; FIG. 11 is a flowchart of performing network switching by using PMIP after negotiation according to Embodiment 4 of the present invention; FIG. 12 is a flowchart of Embodiment 5 of the present invention; Schematic diagram of the process of negotiating CMIP for network access;

13 is a schematic flowchart of network access by using a network-based mobility management protocol after negotiation in Embodiment 5 of the present invention;

14A and 14B are schematic diagrams showing the structure of an ePDG according to an embodiment of the present invention;

15A and 15B are schematic diagrams showing the structure of an AAA server according to an embodiment of the present invention. detailed description

The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

In an embodiment of the present invention, in a process before the mobility management protocol process is initiated, the terminal explicitly notifies the network entity of the mobility management protocol supported by the network entity, and the network entity can passively accept the capability of the terminal, that is, the terminal supports For some host-based mobility management protocol, the network entity also adopts this protocol, otherwise it adopts a network-based mobility management protocol.

As shown in FIG. 3, the process of negotiating a mobility management protocol in the embodiment of the present invention may also be as follows:

Step 1. The terminal explicitly informs its mobile IP capability in the process before the mobility management protocol process is initiated, for example, whether it can support the host-based mobility management protocol;

Step 2: The network entity makes a decision according to the mobile IP capability of the terminal and the network side information; Step 3: The network entity explicitly notifies the terminal of the mobility management protocol to be adopted; Step 4: Complete the mobile IP capability between the terminal and the network After the indication and negotiation, the terminal can initiate the corresponding mobility management protocol process, and the network can understand the process without ambiguity. Different embodiments of the present invention provide different implementations for the difference between the non-3GPP system and the non-trusted non-3GPP system.

In an untrusted non-3GPP network (such as WLAN), both the CMIP process and the PMIP process must access the SAE network through an intermediate entity ePDG. Therefore, when the terminal accesses the SAE from the network, it will first go to the ePDG. The IPsec tunnel establishment process and the authentication process initiated by the ePDG for this tunnel, the negotiation of the mobile IP capability can be completed in these two processes. In a trusted non-3GPP network (such as WiMAX), there will be an access authentication process before the MIP process, so the negotiation of mobile IP capabilities can be completed in this authentication process.

Embodiment 1

This embodiment describes a process in which a mobile terminal negotiates a mobile IP protocol with a network in the process of accessing an SAE network from an untrusted non-3GPP network.

Untrusted non-3GPP networks, such as WLANs, connect to the SAE network through an intermediate entity ePDG. The process of interworking between the WLAN and the 3GPP currently described in TS23.234 is as follows: 1. The terminal accesses the WLAN network;

2. The terminal uses the W-APN (Access Point Name) to perform a DNS (Domain Name Server) query to obtain the address of the ePDG.

3. The terminal initiates the establishment of an IPsec tunnel to the ePDG;

4. The ePDG and the AAA server complete the authentication of the tunnel establishment process and access the service network.

The difference between accessing the SAE from the WLAN and the current process is to complete the access to the SAE based on the Mobile IP protocol (formerly ordinary IP, not supporting mobility). Whether it is at the time of handover or attachment, the terminal-to-ePDG connection establishment process and the authentication process for the tunnel are an indispensable process and a prerequisite for mobile IP registration, so mobile IP can be performed in this process. Consultation of capabilities.

FIG. 4 is a schematic flowchart of a process for attaching an SAE network by using CMIP after negotiation according to the first embodiment of the present invention, and the specific steps include: Step 1. The terminal accesses the untrusted non-3GPP network (such as the WLAN attach procedure, including the terminal obtaining an internal address for transmission within the WLAN network, and possibly an access authentication process).

Step 2: The terminal initiates an IPsec tunnel establishment request to the ePDG. The parameters carried in the request include the supported mobile IP capabilities. For example, the implementation of the device is that the terminal indicates whether the CMIP capability is supported by parameters.

The indication parameter of the supported mobile IP capability is the newly added parameter in the request message in this embodiment. The parameter value can be "yes" and "no", respectively indicating support or not support CMIP.

Step 3: The ePDG initiates an authentication process to the AAA server. In the process, the ePDG can carry the mobile IP capability information of the terminal in the message and send the message to the AAA server.

Step 4. Perform mobile IP selection on the network side.

The mobile side selects the mobile IP protocol on the network side. There are two ways:

The first mode: The network side passively accepts the mobile IP support capability of the terminal. If the terminal indicates that CMIP is supported in the indication parameter of the mobile IP capability, the network side selects CMIP; otherwise, the network side selects PMIP.

The second way: The network side decides according to the mobile IP support capability of the terminal and the network side configuration, and selects a suitable mobile IP protocol. For example, the network side configuration may include an operator policy configuration, user subscription information, and current network resources, and these policy configurations may be selected and used in any combination when used.

The policy information can be configured on the network side. For example, if the policy information is PMIP, the network side selects PMIP according to the configuration policy information of the network side, regardless of whether the indication parameter of the mobile IP support capability of the terminal supports CMIP. When making a decision according to the current network resource situation, a threshold may be set, and PMIP is selected when the network resource usage reaches the threshold to save air interface resources.

In contrast, the second approach is more flexible and more responsive to system performance requirements or user requirements. Step 5: The network side notifies the terminal of the selected mobile IP protocol.

This step is optional. If the terminal can support CMIP and the network determines that the terminal does not use CMIP, you can use this step to instruct the terminal not to initiate the CMIP process.

Step 6: If the network decision uses the CMIP, the remote address carried by the ePDG in the tunnel establishment success response sent to the terminal may be the care-of address assigned by the ePDG, and the care-of address is the address that the CMIP needs to use, and is notified by assigning the care-of address. The protocol chosen by the terminal is CMIP.

Step 7. After the terminal obtains the care-of address and possible broadcast information, it initiates CMIP registration. Step 8. The SAE GW returns a registration response message.

In the process of this embodiment, if the network side needs to notify the terminal not to initiate the CMIP process after selecting the PMIP, the indication information may be added in the tunnel establishment success response message, and the terminal is not required to initiate the CMIP process.

FIG. 5 is a schematic flowchart of a process for attaching a SAE network by using PMIP after negotiation according to the first embodiment of the present invention, and the specific steps include:

Steps 1-5, the same as steps 1-5 in Figure 4, the difference is that the result of negotiating the mobile IP protocol between the terminal and the network side is to use PMIP instead of CMIP.

Step 6. After the ePDG receives the tunnel establishment request from the terminal, if the network and the terminal decide to use the PMIP for registration, the ePDG initiates proxy registration on behalf of the terminal. According to the network topology, the ePDG can directly register with the PDN SAE GW. If the network topology determines that there is a Serving SAE GW between the ePDG and the PDN SAE GW, the ePDG registers with the Serving SAE GW, and the Serving SAE GW registers. Register with the PDN SAE GW.

Step 7. The SAE GW returns a proxy registration response message. The assigned home address is included in the response message.

Step 8: The ePDG notifies the terminal that the tunnel establishment is completed, and the remote address brought to the terminal is the home address obtained in step 7.

Embodiment 2

This embodiment describes the process of switching from a source network to an untrusted non-3GPP network. The process of the terminal negotiating the mobile IP protocol with the network.

When switching from a source network (possibly a 3GPP network, such as LTE, GPRS, or non-3GPP networks) to an untrusted non-3GPP network (such as a WLAN), the mobile IP protocol is also used to complete the handover. So also face the question of how to choose a suitable mobile IP protocol to complete this handover. FIG. 6 is a schematic flowchart of a network switching performed by using CMIP after negotiation according to Embodiment 2 of the present invention, where specific steps include:

Step 1. Prepare for switching between the terminal and the source access network (which may also include the target access network WLAN). This process may include the selection process for ePDG.

Step 2: The terminal needs to access the SAE network to initiate an establishment request to the ePDG tunnel. The parameters carried in the request include NAI (Network Access Name), W-APN (Access Point Name), and whether to support the CMIP capability indication. This process is done by the IKEv2 protocol.

The indication parameter of whether to support the CMIP capability is a newly added parameter in the request message in this embodiment, and the parameter value may be "yes" and "no", respectively indicating that the CMIP is supported or not supported.

Step 3. The ePDG initiates an authentication and authorization process to the AAA server.

Step 4: The network side determines the mobile IP capability according to the terminal, and selects the mobile IP protocol according to the previously set policy.

The network side selects the mobile IP protocol according to the set policy. There are two ways: The first mode: The network side passively accepts the mobile IP support capability of the terminal. If the terminal indicates that the CMIP is supported in the indication parameter of the mobile IP capability, The network side selects CMIP; otherwise, the network side selects PMIP. In this way, in this step, the network side does not need to make decision decisions, and only needs to record the mobile IP capabilities supported by the terminal.

The second method: the network side makes a decision according to the mobile IP support capability of the terminal and the network side configuration, and selects a suitable mobile IP protocol. For example, the network side may make a decision according to the mobile IP support capability of the terminal, the operator policy configuration, the user subscription information, or the current network resource. The carrier policy configuration, the user subscription information, and the current network resource may be selected in any combination. use). The network side can also use CMIP or PMIP as the terminal in the source network. A decision factor for selecting the appropriate mobile IP protocol after reaching the target network. The network side can select the mobile IP protocol consistent with the source network, so that the terminal can adopt the same mobile IP protocol in the source network and the target network, so as to reduce possible conflicts or network interaction processes caused by different protocols.

Step 5: The network side notifies the terminal of the selected mobile IP protocol.

This step is optional. This step is not required if the network side does not make a protocol selection decision. If the terminal can support CMIP and the network is determined to require the terminal not to use CMIP, this step can be used to instruct the terminal not to initiate the CMIP process. If the terminal can support CMIP and the network decision is to use CMIP, you can also not initiate this step.

The remote address carried by the ePDG in the tunnel establishment success response sent by the ePDG may be the care-of address assigned by the ePDG.

Step 7. The terminal initiates registration after obtaining the care-of address and possible broadcast information. It is possible to register via the serving SAE GW visiting the network, or it may be registered through the PDN SAE GW of the home network.

Step 8. The SAE GW returns a registration response message.

After the registration is completed, if there is downlink data in the source access network cache, the cached data is forwarded to the current WLAN network.

FIG. 7 is a schematic diagram of a process for performing network switching by using PMIP after negotiation according to Embodiment 2 of the present invention, where specific steps include:

Steps 1-5, the same as steps 1-5 in Figure 6, the difference is that the result of negotiating the mobile IP protocol between the terminal and the network side is to use PMIP for handover.

Step 6. After the ePDG receives the tunnel establishment request from the terminal, if the network and the terminal decide to use the PMIP for registration, the ePDG initiates proxy registration on behalf of the terminal. It is possible to register via the visiting SAE GW of the visited network, or it may be registered through the PDN SAE GW of the home network.

Step 7. The SAE GW returns a proxy registration response message.

Step 8: The ePDG notifies the terminal that the tunnel is successfully established, and the remote address brought to the terminal is in step 7. Get the home address.

Embodiment 3

This embodiment describes a process in which a mobile terminal negotiates a mobile IP protocol with a network in a process of accessing a SAE network from a trusted non-3GPP network.

When accessing from a trusted non-3GPP network, such as WiMAX, unlike non-trusted non-3GPP network access: The terminal does not need to establish an IPSEC tunneling process to an intermediate entity. However, there is an authentication process to the AAA server before the terminal goes to the SAE network for mobile IP registration, and this authentication process can be used to complete the negotiation of the mobile IP protocol.

FIG. 8 is a schematic flowchart of a process for attaching a SAE network by using CMIP after negotiation according to Embodiment 3 of the present invention, where specific steps include:

Step 1. The SAE user initiates an access request from a trusted non-3GPP network (such as WiMAX), and the request carries an indication parameter indicating whether the CMIP capability is supported.

Step 2. The access network initiates an AAA request for authentication, and the request carries parameters, indicating the supported mobile IP capabilities. This authentication process uses the EAP protocol.

Step 3: The authentication process may involve the AAA server of the access network and act as an AAA proxy server. Forward the authentication request to the AAA server of the SAE network.

Step 4: The AAA server of the SAE network performs access authentication on the terminal, and returns a response message. Step 5. The network side selects the mobile IP protocol.

The second way: The network side makes decisions based on the mobile IP support capability and network side configuration of the terminal, and selects a suitable mobile IP protocol. For example, the network side can support mobile IP based on the terminal. Ability, as well as operator policy configuration, user subscription information, and current network resources to make decisions.

Step 6. The AAA proxy server forwards the authentication result, and may carry the selected mobile IP protocol parameter in the forwarded authentication result. If the terminal can support CMIP and the network determines that the terminal does not use CMIP, then this step can be used to instruct the terminal not to initiate the CMIP process.

Step 7. The access network forwards the authentication result to the terminal, and the authentication result may carry the selected mobile IP protocol parameter.

The following steps are the process of initiating CMIP or PMIP according to the selection result after selecting the mobile IP protocol to be used.

Step 8. The terminal initiates a DHCP process and requests the network to allocate an IP address.

Step 9. The access network forwards the DHCP request to the DHCP server accessing the network.

Step 10: The DHCP server accessing the network assigns an IP address to the terminal. This address may be globally routable and can serve as the care-of address of the terminal.

Step 11. The access network forwards the DHCP response to the terminal.

Step 12. The terminal confirms the DHCP response.

Step 13. The access network forwards the confirmation of the DHCP response.

Step 14. The terminal initiates registration.

Step 15. The SAE GW responds to the registration request.

In the process of this embodiment, if the network side needs to notify the terminal not to initiate the CMIP process after selecting the PMIP, the indication information may be added to the authentication result forwarded by the AAA proxy server to instruct the terminal not to initiate the CMIP process.

FIG. 9 is a schematic flowchart of a process for attaching a SAE network by using PMIP through negotiation in the third embodiment of the present invention, and the specific steps include:

Steps 1-7 are the same as steps 1-7 in Figure 8. The difference between the terminal and the network side to negotiate the Mobile IP protocol is to use PMIP.

Step 8. The terminal initiates a DHCP process and requests the network to allocate an IP address. Step 9. The access network forwards the DHCP request to the DHCP server accessing the network. Step 10. The Proxy Mobility Agent triggers proxy registration.

Step 11. The SAE GW responds to the registration, and the response carries an assigned home address. Step 12: The DHCP server of the access network generates a DHCP response, carrying the home address obtained in step 11.

Step 13. The access network forwards the DHCP response to the terminal.

Step 14. The terminal confirms the DHCP response.

Step 15. The access network forwards the confirmation.

Step 16. The DHCP server of the access network forwards the confirmation.

Embodiment 4

This embodiment describes the process in which the mobile terminal negotiates a mobile IP protocol with the network in the process of switching from the source network to the trusted non-3GPP network.

The process of switching from a source network (possibly a 3GPP network, such as LTE, GPRS, or possibly a non-3GPP network) to a trusted non-3GPP network (such as WiMAX) is different from the process of switching from a source network to an untrusted non-3GPP network. Yes: The terminal does not need to establish an IPsec tunnel to an intermediate entity. However, before the mobile IP registration of the terminal to the SAE network, there will be an authentication process to the AAA server, and the AAA server can be used to complete the negotiation and notification of the mobile IP protocol.

FIG. 10 is a schematic flowchart of a network switching performed by using CMIP after negotiation according to Embodiment 4 of the present invention, where specific steps include:

Step 1. The terminal and the source access network (and possibly the target network WiMAX) perform handover preparation, and simultaneously initiate access to the trusted non-3GPP network (such as WiMAX), and the parameters carried in the access request include Whether to support the indication parameters of CMIP capability.

Step 2: The WiMAX access network initiates an AAA request for authentication, and the request carries parameters that support the CMIP capability indication. Authentication may be an EAP process transmitted on AAA.

Step 3: The AAA server of the WiMAX access network acts as an AAA proxy server, and forwards the authentication request to the AAA server of the SAE. Whether the terminal supports the indication of CMIP capability The number may not be carried in the authentication request of the AAA server forwarded to the SAE network.

Step 4: The AAA server of the SAE performs access authentication on the terminal, and returns a response message. Step 5: The network side determines the mobile IP capability according to the terminal, and selects the mobile IP protocol according to the previously set policy.

The network side performs mobile IP protocol selection according to the set policy. There are two ways: The first mode: The network side passively accepts the mobile IP support capability of the terminal, if the terminal is moving

The indication parameter of the IP capability indicates that CMIP is supported, and the network side selects CMIP; otherwise, the network side selects PMIP. In this way, in this step, the network side does not need to make decision decisions, and only needs to record the mobile IP capabilities supported by the terminal.

The second way: The network side decides according to the mobile IP support capability of the terminal and the network side configuration, and selects a suitable mobile IP protocol. For example, the network side may make a decision according to the mobile IP support capability of the terminal, the operator policy configuration, the user subscription information, or the current network resource. The carrier policy configuration, the user subscription information, and the current network resource may be selected in any combination. use). The network side can also use CMIP or PMIP in the source network as a decision factor for selecting a suitable mobile IP protocol after reaching the target network. The network side can select the mobile IP protocol consistent with the source network, so that the terminal can adopt the same mobile IP protocol on the source network and the target network, so as to reduce possible conflicts or network interaction processes caused by different protocols.

Step 6. The AAA proxy server forwards the access network authentication result, and may carry the selected mobile IP protocol parameter in the forwarded authentication result. If the network does not make a protocol selection decision, the mobile IP protocol parameters may not be carried in the authentication result. If the terminal can support CMIP and the network determines that the terminal does not use CMIP, then this step can be used to instruct the terminal not to initiate the CMIP process. If the terminal can support CMIP and the network decision is also to use CMIP, the mobile IP protocol parameters may not be carried in the authentication result.

Step 7. The WiMAX access network forwards the authentication result to the terminal, and the authentication result may carry the selected mobile IP protocol parameter. Whether the mobile IP protocol parameter is carried depends on whether the authentication result in step 6 carries the mobile IP protocol parameter, and if the authentication result in step 6 carries the mobile IP protocol The parameter is forwarded to the terminal.

Step 9. The WiMAX access network forwards the DHCP request to the DHCP server accessing the network. Step 10: The WiMAX access network's DHCP server assigns an IP address to the terminal. This address may be globally routable and can serve as the care-of address of the terminal.

Step 11. The WiMAX access network forwards the DHCP response to the terminal.

Step 12. The terminal confirms the DHCP response.

Step 13. The WiMAX access network forwards the confirmation of the DHCP response.

Step 14. The terminal initiates registration.

Step 15. The SAE GW responds to the registration request.

After the registration is completed, if there is downlink data in the source access network cache, the cached data is forwarded to the current WiMAX network.

FIG. 11 is a schematic flowchart of a network switching performed by using PMIP after negotiation according to Embodiment 4 of the present invention, where specific steps include:

Steps 1-7 are the same as steps 1-7 in Figure 10. The difference between the terminal and the network side to negotiate the mobile IP protocol is to use PMIP.

Step 8. The terminal initiates a DHCP procedure to request an IP address.

Step 9. The WiMAX access network forwards the DHCP request to the DHCP server of the access network. Step 10. The Proxy Mobility Agent triggers proxy registration.

Step 11. The SAE GW responds to the registration, and the response carries an assigned home address. Step 12: The DHCP server of the WiMAX access network generates a DHCP response, where the carried IP address is the home address obtained in step 11.

Step 13. The WiMAX access network forwards the DHCP response to the terminal.

Step 14. The terminal confirms the DHCP response.

Step 15. The WiMAX access network forwards the acknowledgement.

Step 16. The DHCP server of the WiMAX access network forwards the acknowledgement. After the registration is completed, if there is downlink data in the source access network cache, the cached data is forwarded to the current WiMAX network.

Embodiment 5

This embodiment describes a process in which a mobile terminal negotiates a mobile IP protocol with a network in a process of accessing a SAE from a 3GPP access network.

Referring to FIG. 12, it is a schematic flowchart of a network access that is negotiated by using CMIP according to Embodiment 5 of the present invention, and specific steps include:

Step 1. The terminal initiates an access request from the 3GPP access network (including LTE and GPRS), and the parameters carried therein include an indication of whether to support the CMIP capability.

Step 2. The network entity MME (corresponding to the SGSN in the GPRS network) performs an authentication process with the HSS.

Step 3: The network side determines the mobile IP capability according to the terminal, and selects the mobile IP protocol according to the previously set policy.

The second way: The network side makes decisions based on the mobile IP support capability and network side configuration of the terminal, and selects a suitable mobile IP protocol. For example, the network side may make a decision according to the mobile IP support capability of the terminal, the operator policy configuration, the user subscription information, or the current network resource. The carrier policy configuration, the user subscription information, and the current network resource may be selected in any combination. use). The network side can also use CMIP or PMIP in the source network as a decision factor for selecting a suitable mobile IP protocol after reaching the target network. Network side can choose and source A consistent mobile IP protocol in the network, which enables the terminal to adopt the same mobile IP protocol in the source network and the target network, so as to reduce possible conflicts or network interaction processes caused by different protocols.

Step 4: The network side notifies the terminal that the access request has been accepted, and may also be accompanied by the mobile IP protocol parameters selected by the network.

If the terminal can support CMIP and the network determines that the terminal does not use CMIP, you can use this step to bring the mobile IP parameter to instruct the terminal not to initiate the CMIP process. If the terminal can support CMIP and the network decision is to use CMIP, this parameter may not be included.

Step 5. The terminal initiates registration after obtaining the care-of address and possible broadcast information.

Step 6. The SAE GW returns a registration response message.

Referring to FIG. 13, FIG. 13 is a schematic flowchart of a network-based mobility management protocol negotiated using a network-based mobility management protocol according to Embodiment 5 of the present invention, where specific steps include:

Steps 1-4, Steps 1-4 in Figure 12, the difference is that the result of negotiating the mobile IP protocol between the terminal and the network side is to use a network-based mobility management protocol (such as GTP protocol) for access.

Embodiment 6

This embodiment provides two types of ePDGs that have the function of negotiating a mobile IP protocol.

FIG. 14A is a schematic structural diagram of an ePDG according to an embodiment of the present invention. The ePDG is applicable to a process of passively accepting a mobile IP capability of a terminal without making a selection decision on a mobile IP protocol, including: a receiving module, a selecting module, and a proxy. Module.

a receiving module, configured to receive mobile IP capability indication information of the terminal sent by the terminal, where the capability indication information indicates whether the terminal supports a host-based mobile IP protocol;

a selection module, configured to determine, according to the capability indication information received by the receiving module, whether the terminal supports the host-based mobile IP protocol, and if supported, select a host-based mobile IP protocol; otherwise, select a proxy-based mobile IP protocol;

The proxy module is configured to, after the selecting module selects the proxy-based mobile IP protocol, proxy the terminal to initiate a mobile IP protocol process.

FIG. 14B is a schematic structural diagram of another ePDG according to an embodiment of the present invention, where the ePDG The process applicable to the selection decision of the mobile IP protocol according to the mobile IP capability of the terminal includes: a receiving module, a selecting module, a sending module, and a proxy module.

The receiving module is configured to receive the mobile IP capability indication information of the terminal sent by the terminal, and send a selection instruction, where the capability indication information indicates whether the terminal supports the host-based mobile IP protocol;

a selection module, configured to receive a selection instruction sent by the receiving module, and obtain network side information according to the instruction, and select the adopted mobile IP protocol according to the obtained network side information and the capability indication information received by the receiving module; and when selecting An agent-based mobile IP protocol, and the capability indication information indicates that the terminal sends an instruction when supporting the host-based mobile IP protocol;

a sending module, configured to receive an instruction sent by the selecting module, and send, according to the instruction, the indication information to the terminal, where the indication information indicates that the terminal is initiated to initiate a host-based mobile IP protocol process;

Example 7

This embodiment provides two AAA servers with the function of negotiating a mobile IP protocol.

FIG. 15A is a schematic structural diagram of an AAA server according to an embodiment of the present invention. The AAA server is applicable to a process of passively accepting a mobile IP capability of a terminal and not making a decision on a mobile IP protocol, including: a receiving module, a selecting module. And the agent module.

The proxy module is configured to start another mobile network entity to initiate the mobile ip protocol process after the selecting module selects the proxy-based mobile IP protocol.

FIG. 15B is a schematic structural diagram of another AAA server according to an embodiment of the present invention, where the AAA server is adapted to select a mobile IP protocol according to a mobile IP capability of the terminal. The process includes: a receiving module, a selecting module, a sending module, and a proxy module.

In summary, the embodiment of the present invention provides a display mode for the terminal to provide the mobile IP capability of the network, and the network can also display the mobile IP capability indicating whether the terminal should use the terminal. Compared with the implicit differentiation method currently used in WiMAX technology, it has the following advantages: It is not related to the implementation of CMIP and PMIP, and it does not work because of the difference in the implementation process of PMIP and CMIP. The scalability is very good; The method for distinguishing between PMIPv6 and CMIPv6 is not related to the IP version in the embodiment of the present invention. Therefore, the embodiment of the present invention can distinguish between PMIPv6 and CMIPv6; the network can also be displayed according to user subscription information, network resource status, and the like. The terminal is required to not initiate the CMIP process, and the network initiates the PMIP process, which is more beneficial for the operator to control the network resources, and is meaningful for saving air interface resources. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for negotiating a mobility management protocol, comprising:

The network side receives the mobile IP capability indication information of the terminal sent by the terminal;

The network side selects a mobility management protocol corresponding to the capability indication information according to the capability indication information, or selects the adopted mobility management protocol according to the capability indication information and the network side information.

The method according to claim 1, wherein the capability indication information indicates a mobility management protocol supported by the terminal, and the network side selects, according to the capability indication information, a correspondence with the capability indication information. Mobility management protocols, including:

The network side determines whether the terminal supports the host-based mobility management protocol according to the capability indication information. If supported, the network side adopts a host-based mobility management protocol; otherwise, the network-based mobility management protocol is adopted.

3. The method according to claim 1, wherein, when the network side selects a mobility management protocol according to the capability information and the network side information, if the network side selects a network-based mobility management protocol, The capability indication information indicates that the terminal supports the host-based mobility management protocol, and the network side sends the indication information to the terminal, where the indication information indicates that the suppression terminal initiates the host-based mobility management protocol procedure.

4. The method according to claim 1, wherein when the terminal accesses from an untrusted non-3GPP network, or switches to an untrusted non-3GPP network, an IP security tunnel is initiated to the packet data gateway. In the process of establishing and authenticating the tunnel, the capability indication information is sent to the network side, and the network side selects mobility management according to the capability indication information or according to the capability indication information and the network side information. protocol.

The method according to claim 4, wherein in the IP secure tunnel establishment and tunnel authentication process to the packet data gateway, the terminal sends a tunnel establishment request to the packet data gateway, where The capability indication information is carried in the request.

6. The method of claim 5, wherein if the network side is based on the energy Force indication information and the network side information, selecting a network-based mobility management protocol, and the capability indication information indicates that the terminal supports a host-based mobility management protocol, and the packet data gateway sends a tunnel to the terminal The establishment success message carries the indication information, and the indication information indicates that the terminal is inhibited from initiating the host-based mobility management protocol process.

The method according to claim 1, wherein when the terminal accesses from a trusted non-3GPP network or switches to a trusted non-3GPP network, the capability indication information is used in an authentication process. Sending to the verification authorization and accounting server directly or through a verification authorization and accounting server agent, and according to the capability indication information by the verification authorization and accounting server, or according to the capability indication information and the network side Information, select the mobility management protocol.

8. The method according to claim 7, wherein if the verification authorization and accounting server or proxy server selects a network-based mobility management protocol according to the capability indication information and the network side information, The capability indication information indicates that the terminal supports the host-based mobility management protocol, and the verification authorization and accounting server or the proxy server carries the indication in the authentication result of forwarding the verification authorization and the accounting server to the terminal. The indication information indicates that the suppression terminal initiates a host-based mobility management protocol procedure.

The method according to any one of claims 1-8, wherein the network side information comprises one of the following information or any combination of the following information:

Configuration information stored on the network side, where the configuration information indicates whether the network side selects a network-based mobility management protocol;

User subscription information stored on the network side;

Mobile IP capabilities supported by the network side;

Current resource usage on the network side.

10. An apparatus for negotiating a mobility management protocol, comprising:

a receiving module, configured to receive mobile IP capability indication information of the terminal sent by the terminal, and a selecting module, configured to select, according to the capability indication information received by the receiving module, a mobility management protocol corresponding to the capability indication information; Or according to the capability indication information and network Network side letter, choose mobility management protocol.

11. The apparatus of claim 10, wherein the apparatus further comprises a transmitting module for selecting a network-based mobility management protocol at the selection module, and the capability indication information indicates that the terminal supports host-based mobility In the case of the sex management protocol, the terminal sends the indication information to the terminal, where the indication information indicates that the terminal is initiated to initiate a host-based mobility management protocol procedure.

12. The device of claim 10, further comprising:

And a proxy module, configured to: after the selecting module selects a network-based mobility management protocol, proxy the terminal to initiate a mobility management protocol process, or initiate another network entity to proxy the terminal to initiate a mobility management protocol process.