WO2007006224A1

WO2007006224A1 - A method and system for realizing the r3 interface relocation

Info

Publication number: WO2007006224A1
Application number: PCT/CN2006/001620
Authority: WO
Inventors: Jianjun Wu; Yong Xie
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-07-09
Filing date: 2006-07-10
Publication date: 2007-01-18
Also published as: CN100455111C; CN1794869A

Abstract

A method for realizing the R3 interface relocation, which is applied to microwave access global communication WiMAX network, including: a. the access service network gateway ASN GW determines to relocate the R3 interface for the terminal it services and triggers the mobile IP client corresponding to the terminal for registration; b. the mobile IP client module requests for registration on the basis of the target R3 interface determined by the ASN GW, so as to relocate the R3 interface. A system for realizing the R3 interface relocation and the scheme for R3 interface relocation are also disclosed. The scheme solves the problems in the prior art as the R3 interface relocation is realized only in the case that MSS/SS causes the cell handing over.

Description

Method and system for realizing R3 interface migration

TECHNICAL FIELD The present invention relates to the field of wireless communication technologies, and more particularly to a method and system for implementing R3 interface migration. Background of the invention

IEEE 802.16 defines a wireless metropolitan area network standard for fixed broadband wireless access (BWA), which includes IEEE 802.16a, IEEE 802.16d, and IEEE 802.16e. WiMAX is the world's microwave access interoperability industry organization, which aims to promote the global promotion and application of the IEEE 802.16 series air interface protocol.

Currently, WiMAX provides an end-to-end reference model that includes mobile/user stations (MSS/SS), access service network (ASN), and connection service network (CSN). The MSS/SS is a user equipment, and the user accesses the WiMAX network by using the device.

The ASN is used to provide a set of network functions for wireless access services for WiMAX terminals. The ASN includes a base station (BS) and an ASN gateway (ASN GW). The ASN mainly provides connection with the MSS/SS, radio resource management, measurement, and power through the BS. Control, compression and encryption of air interface data; and provide proxy (proxy) function for authentication, authorization, and accounting of MSS/SS through ASN GW, support NSP network discovery and selection functions, and provide IP addresses such as IP addresses for MSS/SS L3 information relay function such as allocation; ASN can also provide other functions such as ASN internal handover, MSS/SS paging and location management, ASN-CSN tunnel management and visit location registration.

CSN is similar to the core network in mobile communication systems and is used to provide IP connection services for WiMAX terminals. It mainly provides IP address allocation, Internet access, AAA proxy or server functions of MSS/SS, and also provides user-based authorization control. ASN to CSN tunnel, WiMAX User billing and billing between operators.

Currently, WiMAX's draft on NMG PMIP Inter ASN Mobility for proxy mobile IP mode defines a scheme for triggering R3 interface migration due to MSS/SS mobility, ie if MSS/SS is between different BSs Move, it will trigger the R3 interface migration. The migration is shown in Figure 1. The ASN GW in the figure is the same device as the external agent (FA). The MSS/SS is originally located in the cell of the BS1, and the MSS/SS interacts with the home agent (HA) in the CSN through the BS1 and the ASN GW1. If the MSS/SS moves to the cell under the BS2, the MSS/SS needs to pass. BS2, ASN GW2 interacts with HA. It can be seen that the inter-cell handover of the MSS/SS results in air interface switching, R6 interface switching between the ASN GW and the BS, and the R3 interface between the HA and the FA is also migrated.

In the above migration, the MSS/SS movement may be the active movement of the MSS/SS due to user movement; or the MSS passive movement caused by the optimization of the network resources, that is, the network switches the MSS/SS to other resources based on resource optimization. Community. In fact, network resource optimization does not necessarily lead to inter-cell handover of MSS/SS. That is to say, resource optimization does not necessarily change the R6 interface between air interface and ASN GW and BS, but resource optimization usually needs to change FA and HA. The channel between the two, that is, the migration of the R3 interface between the FA and the HA. There is currently no migration plan for this situation. SUMMARY OF THE INVENTION In view of this, the main problem to be solved by the present invention is to provide a method and system for implementing R3 interface migration, so that the WiMAX network can implement R3 interface migration without causing MSS/SS inter-cell handover.

First, the present invention provides a method for implementing R3 interface migration, which is applicable to a WiMAX network, and the method includes:

a. Access service network gateway ASN GW determines to perform R3 interface on the terminal of its own service The migration, triggering the mobile IP client corresponding to the terminal to initiate registration;

b. The mobile IP client module initiates registration based on the target R3 interface determined by the ASN GW for R3 interface migration.

Preferably, the mobile IP client that triggers the terminal initiates the registration as: The ASN GW sends a message including the service information to be migrated and the target R3 interface information to the mobile IP client module of the terminal that needs to perform the R3 interface migration. Requesting to perform R3 interface migration; then, in step b, the mobile IP client initiates registration according to the received request.

Preferably, the request to initiate registration in step b is:

After receiving the request message, the mobile IP client module sends a registration request to the home agent HA.

The service information that needs to be migrated may be: information of a terminal that needs to perform R3 interface migration; or: information of a part of the session in the terminal that needs to perform R3 interface migration.

Preferably, when the ASN GW determines, according to its own resource management policy and the QoS guarantee policy of the user/service flow, that the QoS requirement of the user/service flow cannot be met or guaranteed, the step a is performed.

Preferably, the ASN GW determines the service information required for the R3 interface to be migrated according to the QoS requirements of the current service of the terminal and/or whether the terminal has an R4 interface connection.

Preferably, the step b further comprises:

The MIP client module returns a response message of successful migration to the ASN GW;

After receiving the response message of the successful migration, the ASN GW releases the data path information of the original R3 interface for migration.

The ASN GW may be an ASN GW corresponding to the original R3 interface or an ASN GW corresponding to the target R3 interface.

Preferably, the step b further includes: the ASN GW corresponding to the original R3 interface, the migrated service related information, the anchor data channel function information, and/or the anchor service flow authorization information, and / or anchor the dynamic host configuration protocol proxy or relay information, and / or anchor accounting client information, transfer to the ASN GW corresponding to the target R3 interface.

Preferably, the ASN GW corresponding to the target R3 interface sends a message to the ASN GW corresponding to the original R3 interface to request the information related to the migrated service;

Or the ASN GW corresponding to the original R3 interface actively sends a message carrying the information related to the migrated service to the ASN GW corresponding to the target 3 interface.

When the mobile IP type of the terminal is a proxy mobile IP, the mobile IP client module is a proxy mobile IP mode client;

When the mobile IP address of the terminal is the client mobile IP, the mobile IP client module is the terminal, and the ASN GW notifies the serving ASN GW to trigger the corresponding mobile foreign agent or the mobile access router to send a broadcast message to the terminal.

The present invention also provides a system for implementing R3 interface migration, which is applicable to a WiMAX network, and the system includes: an ASN GW and a mobile IP client module, where

The ASN GW is configured to perform R3 interface migration on the terminal that serves the service, and trigger the mobile IP client corresponding to the terminal to initiate registration.

The mobile IP client module is used to initiate registration of the R3 interface based on the target R interface determined by the ASN GW.

The system can further include:

The HA is configured to establish, according to the registration request from the mobile IP client module, the target R3 interface, a data path between the terminal corresponding to the mobile IP client and the HA based on the target R3 interface in the registration request.

The HA may be further configured to notify the mobile IP client of information indicating that the data path is successful; the mobile IP client module is further configured to send, according to information about success of establishing a data path from the HA, to the ASN GW. Information that the R3 interface migrates successfully; then the ASN GW is further used, according to the R3 from the mobile IP client module The information about successful interface migration releases the corresponding data path and context information.

The ASN GW is an ASN GW corresponding to the original R3 interface, or an ASN GW corresponding to the target R3 interface.

The solution of the present invention determines that the ASN GW determines to perform R3 interface migration on the terminal that serves the service, and triggers the mobile IP client corresponding to the terminal to initiate registration; the mobile IP client module initiates registration based on the target R3 interface determined by the ASN GW. The R3 interface migration makes up for the shortcomings of the prior art that the R3 interface can only be migrated when the MSS/SS performs inter-cell handover.

In addition, in the present invention, when the ASN GW determines that its own resource cannot meet the service requirements of its own service terminal, or initiates the R3 interface migration in the presence of the R4 interface, resource optimization is implemented.

The ASN GW that triggers the R3 interface migration may be the ASN GW corresponding to the original R3 interface, or may be the ASN GW corresponding to the target R3 interface, so that the solution of the present invention provides multiple implementations of trigger migration. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an effect diagram of current MSS/SS-based inter-cell handover triggering R3 interface migration; FIG. 2 is a flowchart of implementation of the scheme of the present invention;

3 is a timing diagram of a message flow according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of the R3 interface migration effect of the solution of the present invention

Figure 5 is a system structural diagram of the solution of the present invention. Mode for Carrying Out the Invention The solution of the present invention mainly implements interface migration of R3 by the ASN GW when the terminal (MSS/SS) does not perform cell handover. The solution of the present invention will be made below with reference to the accompanying drawings and specific embodiments. Further details.

The entity that specifically performs the R3 interface migration function in the ASN GW may be a resource management (RM) module that manages resources. The following takes the RM module to perform the R3 interface migration function as an example.

The implementation process of the solution of the present invention is shown in FIG. 2, which corresponds to the following steps:

Step 201: Predefine an R3 handover request message (R3_Relocate.request) for requesting to migrate the R3 interface, and an R3 handover response message (R3_Relocate.reply) for returning the migration result.

Step 202: The RM module triggers the R3 interface migration when the QoS module determines that its own resources cannot be met according to the QoS policy of the user and the service flow (user/service flow), or the QoS requirement of the user/service flow cannot be guaranteed. And selecting the MSS/SS for migrating the ASN GW service corresponding to the RM module, and determining the R3 interface corresponding to the target FA after the migration, and then sending the R3_Rdocate.request message to the mobile IP that completes the MIP function of the client specified by the MIP protocol. Client (MIP client) module.

When the mobile IP type of MSS/SS is PMIP, the above MIP Client is PMIP Client, then the following P Client is PMIP Cllient. When the mobile IP address of the MSS/SS is CMP, the MIP client is the MSS/SS, and the RM module sends a broadcast message to the MSS/SS through the corresponding mobile foreign agent or mobile access router.

The above process of determining the MSS/SS to be migrated is mainly determined according to the QoS requirements of the current service or session of the MSS/SS, or whether the MSS/SS has an R4 connection. For example, when the network is congested, the low-priority service or session is migrated to ensure the high-priority service or session; when the MSS/SS has the R4 interface connection, the MSS/SS anchor data channel function is migrated to the current service (Serving) ASN GW, to reduce the number of nodes through which the service passes, and improve QoS.

The above determination of the target FA may be the FA in the lightly loaded ASN GW in the network, or may be the FA in the current Serving ASN GW when there is an R4 interface connection. The RM module that triggers the R3 interface migration may be, for example, a data channel function/foreign agent (DPF/FA) entity. In addition, the RM module may be an RM module located in the anchor ASN GW connected to the HA, when anchoring the ASN GW. The RM module in the RM module triggers the R3 interface migration when it is confirmed that the ASN GW cannot meet the QoS requirements of the user/service flow; or the RM module in the service gateway device corresponding to the target R3 interface when the R4 interface exists, when the service gateway device The internal RM module triggers the R3 interface migration when it confirms that the current anchor ASN GW cannot meet the QoS requirements of the user/service flow. Of course, the RM module may also be located in a separate device capable of acquiring the anchor ASN GW or the serving ASN GW resource status.

The R3_Relocate.request message includes the MSS/SS information and the determined information of the R3 interface.

The R3_Relocate.request message may also include a transaction identifier for matching between messages in a subsequent interaction.

The information of the determined R3 interface is: Address information of the target FA after the migration.

In addition, when the RM selects the migrated MSS/SS, all the sessions in the MSS/SS can be migrated, or a part of the sessions in the MSS/SS can be migrated according to the QoS of the session. If it is the former case, the MSS/SS information contained in the R3_Relocate.request message sent by the RM module should be: MSS/SS identification information; if it is the latter case, the MSS/SS information should be It is: the identification information of the MSS/SS, and the information of the session that needs to be migrated, and the session information is usually: the ID of the session, the IP address, and the information of the HA that allocates the IP address.

Step 203: After receiving the R3_Relocate.request message, the P client module sends the registration request to the HA.

The MSS/SS information and R3 interface information are also included in the registration request sent.

Since the FA is usually also provided between the HA and the MIP client module, the registration request can be forwarded by the FA. Similarly, when the HA returns a response message, it can also be transferred by the FA. hair.

In addition, after receiving the R3_Relocate.request message, the MIP client module may also return a response message indicating that the migration process is being performed to the RM module. The response message may be the R3_Relocate.reply message preset in step 201, but the busy flag needs to be set in the message to indicate that the migration process is currently in progress.

Step 204: After receiving the registration request, the HA establishes a data path between the MSS/SS and the local HA based on the R3 interface, and creates a context of the data path, and then sends a corresponding registration response to the MIP client module. .

If the establishment is successful, the registration response message should carry the context information of the data path; otherwise, the response message should carry the information of the establishment failure.

Step 205: After receiving the registration response, the MIP client module returns a corresponding R3_Relocate.reply message to the RM module.

Similarly, if the establishment is successful, the R3_Relocate.reply message should carry the context information of the data path; otherwise, the R3_Relocate.reply message should carry the information of the establishment failure.

When the R3 interface is migrated to migrate the MSS/SS or part of the session to the ASN GW corresponding to the target R3 interface, the information from the ASN GW corresponding to the original R3 interface to the ASN GW corresponding to the target 3 interface includes migration. MSS/SS or migrated sessions: anchor DPF information, and/or anchor service flow authorization (SFA) information, and/or anchor Dynamic Host Configuration Protocol (DHCP) proxy or relay information, and/or anchors Set billing client information. Here, the access service network gateway corresponding to the target R3 interface sends a message to the information related to the service that the access service network gateway corresponding to the original R3 interface seeks to migrate; or the access service network gateway corresponding to the original R3 interface sends the information actively. The message carrying the information related to the migrated service is sent to the access service network gateway corresponding to the target R3 interface.

Step 206: After receiving the R3_Relocate.reply message, the RM module if the message If the Context information of the data path is carried, the migration is successful. After the migration is successful, the subsequent data packets related to the MSS/SS are forwarded to the ASN GW corresponding to the target R3 interface.

If it is determined in step 202 that all the sessions in the MSS/SS are migrated, after the migration is successful, the RM module can directly release the corresponding data path and context information of the R3 interface corresponding to the original FA; if only the MSS/SS is migrated In some sessions, the RM module cannot directly release the data path and context, and only the information of the session can be deleted from the context.

Through the above process, the migration of the R3 interface can be realized based on resource optimization.

In addition, in the foregoing process, when the R3_Relocate.request message is sent to the MIP client module, the RM module may directly send the message to the internal access service network mobility management (Intra ASN MM) module, The Intra ASN MM module forwards the message to the MIP client module. Correspondingly, when the MIP client module returns the R3_Relocate. reply message, it can also be transferred through the Intra ASN MM module.

In the solution of the present invention, the message flow sequence of the R3 interface migration based on the Intra ASN MM module transit is shown in FIG. 3 , where the FA and the ASN GW are located in the same device, and the MP client module and the Authenticator are located in the same device, because FIG. 2 The message flow has been clearly described and will not be described here.

The following takes the migration situation in FIG. 4 as an example to describe the result of implementing the migration based on the solution of the present invention. The FA and the ASN GW are located in the same device, and all sessions in the MSS/SS need to be migrated. The MSS/SS is initially connected to the HA through the BS1, the ASN GW2, and the ASN GW1, that is, the data path corresponding to the R6, R4, and R3 needs to be interacted with the HA. The ASN GW1 is the serving gateway, that is, the serving FA. After the RM determines that the MSS/SS needs to be migrated according to the resource optimization, it is determined that the ASN GW2 is the target gateway, that is, the target FA. Therefore, based on the solution of the present invention, the original R3 interface between the ASN GW1 and the HA is migrated to the ASN. GW2 R3 interface with HA. It can be seen that, based on the solution of the present invention, the data forwarding of the R4 interface in FIG. 4 is terminated, the R3 interface is redirected, the transmission route of the service is optimized, and the load of the network is adjusted.

The ASN GW and the MIP client module of the present invention constitute a system for implementing the R3 interface migration. The specific functions of the ASN GW can be performed by the RM module in the ASN GW. The following takes the RM module as an example. Further, HA may be included in the system of the present invention, as shown in FIG. The functions implemented by the various components in Figure 5 are as described above, and the functions implemented by these components are now briefly described:

The RM module is configured to determine the MSS/SS to be migrated, determine the R3 interface corresponding to the target FA after the migration, and send an R3 handover request message to the MlP client module according to the determined MSS/SS and R3 interfaces, and according to the MIP. The response message returned by the client module confirms that the data path based on the target R3 interface and the corresponding context are maintained after the migration is successful. The RM module can be further used to: when all the session information in the MSS/SS needs to perform the R3 interface migration, the data path and the context information corresponding to the R3 interface of the original FA are placed; the partial session information needs to be in the MSS/SS. When the R3 interface migration is performed, the information of the part of the session is deleted from the context information of the corresponding data path of the original FA R3 interface. The RM module determines the MSS/SS to be migrated according to the resource policy of the RM, and the RM module can be replaced with the ASN GW, and can be the ASN GW corresponding to the original R3 interface, or the ASN corresponding to the target R3 interface. GW.

The MIP client module is configured to send a registration request including the MSS/SS information and the R3 interface information to the HA, and send the registration response returned by the HA to the RM module. The MIP client module may be further configured to, after receiving the R3 handover request message, return a response message to the RM module indicating that the module is undergoing migration processing.

An HA, configured to establish, according to the registration request, a data path of the R3 interface sent by the MSS/SS and the HA based on the registration request, create a context of the data path, and construct the data path The context information of the data path is sent to the MIP clien by registering the response.

The system may further include: an Intra ASN MM module, configured to relay messages between the RM module and the MIP client module. It may further include: FA, for transiting HA and

Messages between MIP client modules.

The above description is mainly based on MIPv4, but the same applies to the MIPv6 protocol. At this time, there will be no FA, and the location of the FA is replaced by the access router (AR) to run the MIPv6 protocol.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are included in the present invention, should be included in the present invention. Within the scope of protection.

Claims

Claim

A method for implementing R3 interface migration, which is applicable to a microwave access global interworking WiMAX network, and the method includes:

The access service network gateway ASN GW determines to perform R3 interface migration on the terminal that is serving the same, and triggers the mobile IP client corresponding to the terminal to initiate registration;

The method of claim 1, wherein the triggering the mobile IP client corresponding to the terminal initiates registration as: ASN GW sends a mobile IP client module that needs to perform R3 interface migration to include The migrated service information and the message of the target R3 interface information are requested to perform R3 interface migration; then in step b, the mobile IP client initiates registration according to the received request.

The method according to claim 2, wherein the initiating registration request in the step b is:

The method according to claim 2, wherein the service information to be migrated is: information of a terminal that needs to perform R3 interface migration; or: information of a part of the session in the terminal that needs to perform R3 interface migration .

The method according to claim 1, wherein the ASN GW determines, according to its own resource management policy and the QoS guarantee policy of the user/service flow, that the QoS requirement of the user/service flow cannot be met or guaranteed. , perform the step a.

6. The method according to claim 1, wherein the ASN GW is based on The QoS requirements of the current service of the terminal and/or whether the terminal has an R4 interface connection determines the service information that needs to be migrated by the R3 interface.

The method according to claim 1, wherein the step b further comprises:

The mobile IP client module returns a response message of the successful migration to the ASN GW. After receiving the response message of the successful migration, the ASN GW releases the data path information of the original R3 interface for migration.

The method according to claim 1, wherein the ASN GW is an ASN GW corresponding to the original R3 interface, or an ASN GW corresponding to the target R3 interface.

The method according to claim 1, wherein the step b further comprises: the ASN GW corresponding to the original R3 interface to associate the migrated service, the anchor data channel function information, and/or the anchor service flow Authorization information, and/or anchor dynamic host configuration protocol proxy or relay information, and/or anchor accounting client information, to ASN corresponding to the target R3 interface

The method according to claim 9, wherein the ASN GW corresponding to the target R3 interface sends a message to the ASN GW corresponding to the original R3 interface to request the information related to the migrated service;

Or the ASN GW corresponding to the original R3 interface actively sends a message carrying the information related to the migrated service to the ASN GW corresponding to the target R3 interface.

The method according to claim 1, wherein when the mobile IP type of the terminal is a proxy mobile IP, the mobile IP client module is a proxy mobile IP mode client;

12. A system for implementing an R3 interface migration, which is applicable to a WiMAX network, and the system includes: an ASN GW and a mobile IP client module, where

The mobile IP client module is used to initiate registration of the R3 interface based on the target R3 interface determined by the ASN GW.

13. The system of claim 12, wherein the system further comprises:

The system according to claim 12, wherein the HA is further configured to notify the mobile IP client of information that the data path is successful; the mobile IP client module is further configured to The information about the successful establishment of the data path of the HA is sent to the ASN GW to send information about the successful migration of the R3 interface. The ASN GW is further configured to: release the corresponding information according to the information of the successful migration of the R3 interface from the mobile IP client module. Data path and context information.

The system according to any one of claims 12 to 14, wherein the ASN GW is an ASN GW corresponding to the original R3 interface, or an ASN GW corresponding to the target R3 interface.