WO2007090353A1 - A method and device for a mobile station performing mobile internal protocol de-registration - Google Patents

Abstract

A method and device for a mobile station MS in idle mode performing MIP de-registration are disclosed, and the method comprises: upon receiving a de-registration request message, tearing down the R3 link set for the MS between the FA and the home agent HA; FA sends a deletion message for deleting the MS related record to the paging controller entity/location register PC/LR, and the PC/LR deletes the MS related record stored in itself. The method and device provided in the present invention realize the MIP de-registration process by the MS in idle mode.

Description

 Method and device for mobile station to perform mobile Internet protocol registration

Technical field

 The present invention relates to a mobile station (MS) in a communication system for performing Mobile Internet Protocol (MIP) deregistration technology, and more particularly to a method and apparatus for MS to perform MIP deregistration. Background of the invention

 When the MS in the communication system is not paged or does not initiate a call, the Idle Mode can be entered; when the MS in the communication system performs a service such as being paged or initiating a call, the non-Idle Mode can be entered. The following is a detailed description of the communication system for the Worldwide Interoperability for Microwave Access (WiMAX) network.

 FIG. 1 is a schematic structural diagram of a WiMAX network, where an WiMAX network includes an access service network (ASN) and a connection service network (CSN), wherein the ASN includes an MS, a base station (BS) to which the MS belongs, an authentication entity, and a field. Agent (FA), Relay Paging Control Entity (Relay PC), Anchor Paging Control Entity (ATM), Location Registrar (LR), and ASN Functional (ASN Functional) entities; the CSN includes a Local Agent (HA). In the Idle Mode, the Anchor PC and the LR can be integrated into one entity. The Anchor PC and the Relay PC are used to page the MS through the BS to which the MS belongs. Authentication is used to authenticate the MS, and the LR is used to register the MS. The ASN Functional entity is used to trigger traffic to the MS. HA and FA perform message interaction through the R3 link set for the MS, and between the FA and the Anchor PC/LR and between the Anchor PC/LR and the Authentication through the R4 link set for the MS. Here, it is also possible to refer to a PC without distinguishing between a Relay PC and an Anchor PC.

Currently, MS can transmit information over the Internet Protocol (IP) link. The Internet Working Group has developed a MIP. The MIP provides an IP routing mechanism for the MS to enable the MS to support the MIP. It can be connected to any link with the set MS ID. The MIP-capable MS can change the geographic location without interrupting the transmission of information over the link or without rebooting.

 There are two techniques that allow MS to support MIP. The first technology is called Client Mobile Internet Protocol (CMIP) technology, which integrates MIP functions into the MS. The MIP registration process of the MS is initiated by the MS. The second technology is called Proxy Mobile Internet Protocol (PMIP) technology, which sets the MIP function in the Proxy Mobile Node of the ASN to which the MS belongs, and the MIP registration/MIP of the MS. The deregistration process is initiated by the Proxy Mobile Node, which is typically integrated into the Authenticator entity.

 At present, the flow chart of the method for initiating MIP registration by the MS in the non-idle mode (Idle Mode) is as shown in FIG. 2, and the specific steps are as follows:

 Step 200: The ASN Functional entity triggers the service interruption of the MS, and sends a release R3 link request message to the Proxy Mobile Node of the ASN to which the MS belongs. The R3 link is a link established between the FA and the HA for the MS.

 Step 201: The Proxy Mobile Node sends a MIP registration request message to the FA, where the MIP lifetime (Lifetime) carried by the message is 0.

 When the MIP Lifetime carried in the MIP registration request message is 0, the MIP is actually sent to register the request message.

 Step 202: The FA forwards the received MIP registration request message with the MIP Lifetime 0 to the HA.

 Step 203: The HA removes the R3 link between the FA and the FA, and returns a MIP registration request response message to the FA.

Step 204: The FA returns a MIP registration request response message to the Proxy Mobile Node. Step gland 205, Proxy Mobile Node returns R3 to ASN Functional entity υ j J The link request is ringing, and the R3 link is removed.

 The flow chart of the method for initiating MIP registration by MS in non-Idle Mode using CMIP technology is shown in Figure 3. The specific steps are as follows:

 Step 300: The ASN Functional entity triggers the service interruption of the MS, and sends an Release R3 Link Request message to the FA.

 Step 301: The FA that receives the request message sends a response message to the ASN Functional entity.

 Step 302: The FA sends a Mobility Advertisement message to the MS, where the message carries the MIP Lifetime to 0.

 Step 303: The MS sends a MIP registration request message to the FA, where the message carries the MIP Lifetime to 0.

 Step 304: The FA forwards the received MIP registration request message with the MIP Lifetime 0 to the HA.

 Step 305: The HA removes the R3 link between the FA and the FA, and returns a MIP registration request response message to the FA.

 Step 306: The FA returns a MIP registration request response message to the MS.

 Step 307: The FA returns a release R3 link request response message to the ASN Functional entity, and the R3 link is removed. However, there is currently no MIP registration technology for MS in Idle Mode.

There is a lot of drawbacks in the MIP de-registration technology without MS in Idle Mode, such as the technology that does not trigger the deletion of related resources set by the WiMAX network side for the MS (including two cases, one for MS lost in Idle Mode, another The MS is not lost in the Idle Mode, such as removing the R3 link set up by the MS between the FA and the HA, which may result in waste of resources. The following cannot delete the WiMAX network after the MS is lost in the Idle Mode. The reason why the network side sets the relevant resources set by the MS is described in detail.

 When the MS is in Idle Mode, the WiMAX network side requires the MS to initiate the Location Updated procedure according to different Location Updated conditions, that is, the MS sends a Location Update Request to the Anchor PC/LR through the BS and Relay PC, Anchor PC/LR. Location Updated for MS. Different Location Updated conditions include: 1) Paging Group Update, when the MS detects in the Idle Mode that the Paging Group stored by itself is different from the current Paging Grou, Location Updated; 2) Timer Update (Timer Update), when the timer set by the MS in Idle Mode expires, the period is Updated; 3) Power Down Update, MS restarts after power down in Idle Mode, and performs Location Updated; 4) MAC Hash Skip Threshold Update, when MS performs MAC Hash Skip Threshold Update in Idle Mode

 When the FA receives the data packet of the MS sent by the HA, it can notify the Anchor PC/LR. When the Anchor PC/LR detects that the MS is in the Idle Mode, it initiates a paging procedure to the MS, pages to the MS, and sends a data packet to the MS. .

 Regardless of whether the WiMAX network side wants to perform Location Update or paging for the MS in the Idle Mode, the MS needs to be in the Idle Mode. If the MS is not in the Idle Mode, that is, the MS in the Idle Mode is lost, the WiMAX network will be caused. The problem that the Location Update cannot be performed due to the location update request sent by the MS in the timing period or the Paging process performed by the WiMAX network side for the MS fails, the Paging is less than the MS, and the data packet cannot be sent to the MS.

Although the WiMAX network side cannot be caused by the loss of the MS in the Idle Mode. The Location Updated or the WiMAX network side paging MS fails in the Idle Mode. However, the WiMAX network side also maintains the relevant settings for the MS. Resources, such as maintaining the R3 link set for the MS between the FA and HA, etc., which leads to WiMAX Waste of resources on the network side. Summary of the invention

 The embodiment of the invention provides a method and a device for performing MIP deregistration by the MS, which can implement the MIP deregistration by the MS in the Idle Mode.

 A mobile station MS performs a mobile Internet protocol MIP deregistration method, and the MS is in an idle mode Idle Mode, and the method includes:

 Receiving the MIP to register the request message, and disassembling the R3 link set between the FA and the local proxy HA for the MS;

 Paging Control Entity / Location Registrar The PC/LR deletes the MS related records stored by itself. A device for performing MIP deregistration by an MS in an Idle Mode, the device comprising a triggering module, configured to send a MIP to a FA to register a request message by using a trigger module.

 It can be seen from the foregoing solution that the method and the device provided by the embodiment of the present invention perform the MIP deregistration process by the ASN Function entity or the HA when the MS in the Idle Mode performs MIP registration, and remove the R3 link set for the MS. And the MS related record stored in the PC/LR is deleted, thereby realizing the MIP deregistration process of the MS in the Idle Mode. Further, when the MS in the Idle Mode is lost, the network entity associated with the MIP initiates the removal of the R3 link between the HA and the FA set for the MS, so that when the MS is lost in the Idle Mode, The communication system deletes related resources set for the MS to avoid waste of communication system resources. BRIEF DESCRIPTION OF THE DRAWINGS

 Figure 1 is a schematic structural diagram of a WiMAX network;

2 is a flow chart of a method for initiating MIP deregistration by a MS in a non-Idle Mode using a PMIP technology; 3 is a flow chart of a method for initiating MIP deregistration by an MS in a non-Idle Mode using a CMIP technology;

 4 is a flowchart of a method for MIP de-registration of an MS in an Idle Mode according to an embodiment of the present invention;

 FIG. 5 is a flowchart of a method for performing MIP de-registration on an MS in an Idle Mode according to an embodiment of the present invention;

 6 is a flowchart of a method for performing MIP de-registration on an MS in an Idle Mode according to an embodiment of the present invention;

 Figure 7 is a schematic view of the HA device of the present invention;

 FIG. 8 is a flowchart of a method for processing a WiMAX network side after the MS is lost in an Idle Mode according to an embodiment of the present invention;

 FIG. 9 is a flowchart of a second processing method on the WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention;

 10 is a flowchart of a processing method on a WiMAX network side after the MS is lost in the Idle Mode according to an embodiment of the present invention;

 FIG. 11 is a flowchart of a fourth processing method on the WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention. Mode for carrying out the invention

 The embodiment of the present invention is described by taking a communication system as a WiMAX network as an example.

When the MS is in Idle Mode, in some cases, there is also a need to perform MIP registration. For example, the MS in the Idle Mode does not receive the MS-initiated location update request (Location Update Request) in the set period of the communication system grid side or the set number of times the MS is set on the network side of the communication system. When the call still fails to page to the MS, it will be confirmed by the network side of the communication system that the MS is lost, in order to save the communication system. For network resources, MIP registration is required for the MS, and the R3 link set between the HA and the FA for the MS is removed.

 When the MIP deregistration method is applied to the MS in the Idle Mode by using the PMIP technology, the MSN deregistration process of the MS in the Idle Mode may be initiated by the ASN Function entity by referring to the method described in FIG. 2 in the prior art. The invention can also initiate the MIP deregistration process of the MS in the Idle Mode by the HA.

 Since the Anchor PC/LR stores MS related records when the MS is in Idle Mode, the MS related records stored in the Anchor PC/LR must be deleted when the MS in the Idle Mode performs the MIP deregistration method.

 When the MS is in the Idle Mode, if the MIP de-registration process is performed by using the CMIP technology, the ASN Function entity or the HA activates the MS to exit the Idle Mode according to the prior art, and then directly completes the MIP registration process by using the prior art, so The process is not within the scope of the embodiments of the present invention.

 In the embodiment of the present invention, the ASN Function entity or the HA initiates the MIP deregistration process of the MS in the Idle Mode, and the FA receives the MIP deregistration request message from the access device or the MIP deregistration request message from the HA, so the MIP The registration will be performed, the R3 link will be removed, and the MS related records stored in the Anchor PC/LR will be deleted. In the embodiment of the present invention, the access device may send a Proxy Mobile Node that sends the removed R3 link request message set by the MS to the ASN Functional entity.

 FIG. 4 is a flowchart of a method for performing MIP de-registration for an MS in an Idle Mode according to an embodiment of the present invention, where specific steps are as follows:

 Step 400: The FA receives the MIP to register the request message.

In the embodiment of the present invention, the MIP deregistration request message may be a MIP registration request message carrying a MIP Lifetime of 0, or may be a MIP registration request message, such as a MIP Registration Revocation Request message, of course. The MP deregistration request message may also be a message named by another name but capable of implementing the same function.

 When the MS in the Idle Mode is triggered by the ASN Functional entity to perform MIP deregistration using the PMIP technology, the MIP deregistration request message is a Proxy Mobile that receives the R3 link request message set for the MS by the ASN Functional entity. The MIP deregistration message is sent by the HA when the MS in the Idle Mode is triggered by the HA to perform MIP registration using the PMIP technology.

 Step 401: The FA sends a delete message to the Anchor PC/LR to delete the MS related record.

The MS related record is the MS identification (MS ID) or / and the paging identification (PCID).

 When the MS in the Idle Mode is triggered by the ASN Functional entity to perform MIP deregistration using the PMIP technology, before the step 401, the method further includes: the FA forwards the received MIP deregistration request message to the HA; and the HA receives the message according to the received message. Determining the MIP registration of the MS (when the MIP deregistration request message is a MIP registration request message carrying the MIP Lifetime 0), the MIP to be registered according to the carried MIP Lifetime is 0, and the MS will be set to be The R3 link between the FAs is removed, and a MIP registration request response message is returned to the FA.

 When the MS in the Idle Mode is triggered by the HA to perform the MIP deregistration by using the PMIP technology, the step 401 can be directly performed because the R3 link between the FA and the FA that is set for the MS is removed when the HA is triggered.

 The process of dismantling the R3 link between the FA and the FA that has been set by the HA at the time of triggering is: HA triggers the MIP of the MS to register, sends the MIP of the MS to the FA to register the request, and sets the MS between the FA and the HA. The R3 link is removed and the FA responds to the MIP of the MS sent by the HA to register the request.

Step 402: After the Anchor PC/LR that receives the deletion message deletes its own stored MS related record, it sends a record deletion response message to the FA. · Step 403: The FA returns a MIP to register the request response message.

 When the MS in the Idle Mode is triggered by the ASN Functional entity to perform MIP deregistration using the PMIP technology, the MIP deregistration request response message is returned to the Proxy Mobile Node, and then the Proxy Mobile Node returns to the Anchor PC/LR to release the R3 link request. Response message; when the MS triggered by the HA in the Idle Mode performs MIP deregistration using the PMIP technology, the MIP deregistration request response message is returned to the HA.

 In the step 402 of FIG. 4, the record deletion response message is sent to the FA and the step 403 is to respectively confirm the MIP deregistration process of the MS in the Idle Mode by the FA and the Proxy Mobile Node or the HA, and in the specific implementation, send.

 In the embodiment of the present invention, the Relay PC and the Anchor PC may not be distinguished, and is generally referred to as a PC, that is, the Anchor PC LR described in FIG. 4 may be a PC/LR.

 The embodiment of the present invention uses a WiMAX network as a communication system for example. The network entities in the WiMAX network side are all logical function entities. When other communication systems implement the embodiments of the present invention, logical function entities having corresponding functions may also be used. carry out.

 The following describes the process of MIP deregistration using the PMIP technology in the Idle Mode triggered by the Anchor PC/LR or HA.

 FIG. 5 is a flowchart of a method for performing MIP de-registration on an MS in an Idle Mode according to an embodiment of the present invention, where specific steps are as follows:

 Step 500: The ASN Functional entity triggers the service interruption of the MS, and sends an R3 link request message that is set to the MS to the Proxy Mobile Node of the ASN to which the MS belongs.

 Step 501: The Proxy Mobile Node sends a MIP to the FA to register the request message. The MIP deregistration request message may be a MIP registration request message carrying a MIP Lifetime of 0, or may be a registration request message for other MIPs. Of course, the MIP deregistration request message may also be a message named by another name but can achieve the same function. Message.

Step 502: The FA forwards the received MIP deregistration request message to the HA. 00451 Step 503: The HA determines to perform MIP deregistration of the MS according to the received message, and removes the R3 link between the FA and the FA set for the MS, and returns a MIP registration request response message to the FA.

 When the MIP registration request message is a MIP registration request message carrying MP Lifetime 0, the MIP registration of the MS may be determined according to the carried MIP Lifetime of 0.

 Step 504: The FA sends a delete message to the Anchor PC/LR to delete the MS related record. Step 505: After the Anchor PC/LR that receives the delete message deletes the MS related record stored by itself, sends a record deletion response message to the FA.

 Step 506: The FA returns a MIP to the Proxy Mobile Node to register the request response message. Step 507: Receive a MIP to register a request response to the Proxy Mobile Node to the ASN

The Functional entity returns the release R3 link request response message, and the MIP registration process of the MS in Idle Mode is completed.

 FIG. 6 is a flowchart of a method for performing MIP de-registration on an MS in an Idle Mode according to an embodiment of the present invention, where specific steps are as follows:

 Step 600: The HA sends a MIP to the FA to register the request message.

 The MIP registration request message may be a MIP registration request message carrying a MIP Lifetime of 0, or may be a registration request message for other MIPs, such as MIP Registration.

Revocation request message, of course, the MIP deregistration request message can also be a message named by another name but can implement the same function.

 Step 601: The FA sends a delete message to the Anchor PC/LR to delete the VIS related record. Step 602: After the Anchor PC LR that receives the deletion message deletes the MS-related record, it sends a record deletion response message to the FA. .

 Step 603: The FA returns a MIP to the HA to register the request response message.

The method provided by the embodiment of the present invention, when the MS is in the Idle Mode, triggers the MIP to register the process by the ASN Functional entity or the HA, and finally removes the R3 link set for the MS and The MS related records stored in the PC/LR are deleted, and the related resources of the MS in the communication system are completely deleted.

 An embodiment of the present invention further provides an apparatus for performing MIP deregistration by an MS in an Idle Mode. As shown in FIG. 7, the method includes a triggering module, configured to send, by using a trigger module, a MIP registration request message to the FA, and the MS in the Idle Mode. The MIP is sent to the registration request message when the MIP is registered.

 The apparatus further includes a deletion module for deleting the MS related record stored by itself. The device may be arranged in the HA or in the ASN Function entity. The MIP de-registration scheme provided by the embodiment of the present invention can be applied to the situation that when the MS is lost in the Idle Mode, the related resources set by the WiMAX network side for the MS cannot be deleted, thereby solving the waste of the communication system resources. Detailed instructions are given.

 When the Anchor PC/LR in the WiMAX network side detects the loss of the MS in the Idle Mode, first, the Anchor PC/LR notifies the MIP-related network entity through the MS resource release request message, and the MIP-related network entity to the WiMAX The HA in the network side initiates a MIP deregistration request message to the MS, and the message carries the R3 link information that is set to be set between the FA and the HA by the MS. Then, after receiving the MIP registration request message of the MS, the HA is removed. After the R3 link set between the FA and the HA, the MS returns a MIP registration response message to the MIP-related network entity. Finally, the MIP-related network entity receives the MIP registration response message and sends it to the WiMAX network side. The Anchor PC LR sends an MS Resource Release Response message, and the Anchor PC/LR deletes the relevant information stored for the UE. In this way, after the MS in the Idle Mode is lost, the WiMAX network side deletes the related resources set for the MS to avoid waste of WiMAX network resources.

In the embodiment of the present invention, the network entity associated with the MIP may be an FA, or may be a proxy mobile Internet Protocol client (PMIP Client), and may also be other MIP-related networks not involved in the embodiments of the present invention. entity. In the embodiment of the present invention, the network entity associated with the MIP may also delete the MS related resources stored by itself or/and notify other entities on the network side of the communication system to delete the MS related resources stored by itself, for example, when the network entity associated with the MIP is In the case of FA, the SFA can be notified to delete the service metric information (QoS Profile) of the MS.

 In the embodiment of the present invention, when the Anchor PC/LR in the WiMAX network side detects that the MS in the Idle Mode is lost, the R4 link between the Authentication and the Authentication set by the MS and the information about the Authentication deletion are notified. When the FA receives the MS resource release request message, the FA can also remove the R4 link between the PC and the LR, which is set up by the MS, so that the related resources set for the MS can be further deleted, thereby further avoiding waste of WiMAX network resources. .

 In the embodiment of the present invention, there are two methods for detecting the loss of the MS in the Idle Mode by the Anchor PC/LR in the WiMAX network side. The first one: detecting whether the MS in the Idle Mode is sent according to a preset period. Location Update Request, if yes, the MS in the Idle Mode is not lost; otherwise, the MS in the Idle Mode is lost; Secondly, the paging is not found in the set paging times when paging the MS Calling the MS in Idle Mode determines that the MS in Idle Mode is lost.

 The resource release request message (PC_PURGE_MS_REQ) and the resource release response message (PC_PURGE_MS_RSP) are messages defined in the embodiment of the present invention to prevent the WiMAX network side from being deleted as a related resource set by the MS and avoid waste of WiMAX network resources. PC—PURGE—MS—REQ can also carry the loss cause value, which can be: Location Updated or Paging failed.

 In the embodiment of the present invention, the M3 de-registration request message is removed. The R3 link information set by the MS between the FA and the HA may be: MIP lifetime (LifeTime) set to 0, that is, carrying the MIP Lifetime=0. The MIP goes to the registration request message.

FIG. 8 is a schematic diagram of the WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention. Processing method A flow chart, the specific steps are:

 Step 800: The Anchor PC/LR detects the MS loss in the Idle Mode; the Anchor PC/LR can detect the MS loss in the Idle Mode by the above two methods of the present invention.

 Step 801: The Anchor PC/LR sends the PC of the MS to the FA-PURGE-MS-RjEQ, and the request carries the identifier of the lost MS in the Idle Mode, and may also carry the loss cause value. Step 802: The FA initiates the MIP to the MS to the HA. Deregistering the request message, the MS is the MS having the identifier of the MS carried by the request, and the MIP LifeTime carried in the MIP deregistration request message is set to 0, that is, carrying Lifetime=0;

 Step 803: The HA receives the MIP deregistration request message, and determines, according to the MIP LifeTime that is set to 0, that the FA is to be removed as an R3 link set between the FA and the HA by the MS, and is removed between the FA and the FA. The R3 link sends a MIP to the FA to register the response message;

 Step 804: The FA sends the MS PC-PURGE-MS-RSP to the Anchor PC/LR, and the Anchor PC/LR deletes the related information saved by the MS, such as the SFIDs, associated CIDs or / and QoS context saved by the MS.

 In this step, the related resources of the MS are deleted by the PMIP technology, that is, the PMIP client, such as the Proxy Mobile Node, initiates the process of deleting the related resources set for the MS by the network side of the communication system, and three specific embodiments are given below. Be explained.

 FIG. 9 is a flowchart of a method for processing a WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention, and the specific steps are as follows:

 Step 900: The Anchor PC/LR detects that the MS is lost in the Idle Mode. Step 901: The Anchor PC/LR sends a PC-PURGE_MS_REQ to the FA, where the request carries the identifier of the lost MS in the Idle Mode, and can also carry Lost cause value;

Step 902: The FA sends an R3 link release request to the PMIP client (R3 Session). Release Request), the request carries the identifier of the lost MS in the Idle Mode, and can also carry the loss cause value;

 Step 903: The PMIP client sends a MIP deregistration request message to the MS to the FA, where the MS is the MS with the identifier of the MS that is received by the request, and the MIP LifeTime carried in the MIP deregistration request message is set to 0, that is, carrying Lifetime = 0;

 Step 904: The FA forwards the MIP deregistration request message to the MS to the HA, where the MS is the MS with the identifier of the MS carried by the request, and the MIP LifeTime carried by the MIP deregistration request message is set to 0, that is, carrying Lifetime=0. ;

 Step 905: The HA receives the MIP deregistration request message, determines, according to the MIP LifeTime that is set to 0, the R3 link to be set up between the FA and the HA, and removes the R3 set between the FA and the FA. Link, sending a MIP to the FA to register the response message;

 Step 906: The FA forwards the MIP to the PMIP Client to register the response message.

 Step 907: The PMIP client sends an R3 Session Release Request to the FA.

 Step 908: The FA sends the PC-PURGE-MS-RSP to the Anchor PC/LR, and the Anchor PC/LR deletes the related information saved by the MS, such as the SFIDs, associated CIDs, or/and QoS contexts saved by the MS.

 The difference between the method shown in FIG. 9 and the method in FIG. 8 is as follows: When the FA receives the PC-PURGE_MS_REQ sent by the Anchor PC LR, it sends an R3 session Release Request to the PMIP Client, and the PMIP Client initiates the MS resource. Delete the process.

 FIG. 10 is a flowchart of a method for processing a WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention, and the specific steps are as follows:

Step 1000: The Anchor PC/LR detects that the MS is lost in the Idle Mode; Step 1001, the Anchor PC/LR sends the PC to the FA—PURGE—MS—REQ, the request It is required to carry the identifier of the lost MS in the Idle Mode, and may also carry the loss cause value; Step 1002: The FA sends a mobile advertisement message to the PMIP Client (Mobility

Advertisement ), the MIP LifeTime carried in the message is set to 0, and the message can also carry the identifier of the MS lost in the Idle Mode;

 Step 1003: The PMIP client returns a MIP registration request message to the MS to the FA.

The MS is the MS with the identifier of the MS carried by the request, and the MIP LifeTime carried by the MIP deregistration request message is set to 0, that is, carrying Lifetime = 0;

 Step 1004: The FA forwards the MIP deregistration request message to the MS to the HA, where the MS is the MS having the identifier of the MS that is received by the request, and the MIP LifeTime carried in the MIP deregistration request message is set to 0.

 Step 1005: The HA receives the MIP to register the request message, according to the carried settings.

The MIP LifeTime of 0 determines that the R3 link set up between the FA and the HA is to be removed, the R3 link set up with the FA for the MS is removed, and the MIP is sent to the FA to register the response. Step 1006, FA to PMIP Client Forward the MIP to register the response message;

 Step 1007: The FA sends the PC-PURGE-MS-RSP to the Anchor PC/LR, and the Anchor PC/LR deletes the related information saved by the MS, such as the SFIDs, associated CIDs or / and QoS contexts saved by the MS.

 The difference between the method shown in FIG. 10 and the method in FIG. 8 is as follows: When the FA receives the PCJPURGE_MS__REQ sent by the Anchor PC/LR, it sends a Mobility Advertisement to the PMIP client, and the PMIP Client initiates the deletion process of the MS resource.

 FIG. 11 is a flowchart of a method for processing a WiMAX network side after the MS is lost in the Idle Mode according to the embodiment of the present invention, and the specific steps are as follows:

Step 1100: The Anchor PC/LR detects that the MS is lost in the Idle Mode; Step 1101, the Anchor PC/LR sends the PC-PUTRGE_MS_REQ to the PMIP Client, The request carries the identifier of the lost MS in the Idle Mode, and may also carry the loss cause value; Step 1102, the PMIP Client sends a MIP registration request message to the MS to the FA,

The MS is the MS having the identifier of the MS carried by the request, and the MIP LifeTime carried by the MIP deregistration request message is set to 0, that is, carrying Lifetime = 0;

 Step 1103: The FA forwards the MIP deregistration request message to the MS to the HA, where the MS is the MS having the identifier of the MS that is received by the request, and the MIP LifeTime carried in the MIP deregistration request message is set to 0.

 Step 1104: The HA receives the MIP registration request message, and according to the carried setting,

The MIP LifeTime of 0 determines that the R3 link set up between the FA and the HA is to be removed, the R3 link set up with the FA for the MS is removed, and the MIP is sent to the FA to register the response. Step 1105, FA to PMIP Client Forward the MIP to register the response message;

 Step 1106: The PMIP Client sends a PC-PURGE_MS_RSP to the Anchor PC/LR, and the Anchor PC/LR deletes the record information saved by the MS, such as the SFIDs, associated CIDs, or/and QoS contexts saved by the MS.

 The method shown in FIG. 11 directly sends PC-PURGE_MS-REQ to the PMIP Client by the Anchor PC LR, and the PMIP client initiates the deletion process of the MS resource. .

 In the embodiment of the present invention, the PC and the anchor PC may be referred to as a PC, that is, the Anchor PC/LR as shown in FIG. 8, FIG. 9, FIG. 10 or FIG. 11 may be a PC/LR.

 The PC-PURGE-MS-REQ and the PC-PURGE-MS-RSP used in FIG. 8, FIG. 9, FIG. 10 or FIG. 11 are only for describing an implementation of the MS resource dry request message and the MS resource release response message, respectively. For example, all other message definitions for implementing the MS resource release request message and the MS resource release response message function are within the scope of the present invention.

In the prior art, since the MS enters the Idle Mode, the MIP of the MS is registered. The MIP LifeTime of the message is set to the maximum value, so the presence detection of the MS is not performed for a long time. When the MS in the Idle Mode is within the set period, the period is smaller than the MIP of the MIP to register the message of the MS. The LifeTime value, the network side of the communication system cannot determine that the MS has been lost even if it does not receive the Location Update Request initiated by the MS, and continues to maintain the MS related resources, resulting in waste of communication system resources. In the embodiment of the present invention, when the MS in the Idle Mode does not receive the Location Update Request initiated by the MS, the MS is determined to be lost. The method removes MS related resources maintained by the communication system, thereby saving communication system resources.

 In addition, in the embodiment of the present invention, when the communication system performs the paging of the set number of times of the MS in the Idle Mode and still does not page to the MS, it is determined that the MS has been lost, and the method described in the embodiment of the present invention is used. The MS related resources maintained by the communication system are removed, thereby saving communication system resources.

 The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. It is understood that the foregoing description is only a specific embodiment of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim  A mobile station MS performs a mobile Internet protocol MIP deregistration method, wherein the MS is in an idle mode Idle Mode, and the method includes:  Receiving the MIP to register the request message, and disassembling the R3 link set between the FA and the local proxy HA for the MS;  Paging Control Entity / Location Registrar The PC/LR deletes the MS related records stored by itself. 2. The method according to claim 1, wherein before the PC/LR deletes the MS related record stored by itself, the method further includes:  The FA sends a delete message to the PC/LR to delete the MS related record.  The method according to claim 1 or 2, wherein when the MS in the Idle Mode is used to perform MIP deregistration by the access service network function ASN Functional entity, the MIP deregistration request message is received by The ASN Functional 'entity sends the removed proxy mobile node Proxy Mobile Node for the R3 link request message set by the MS;  When the MS in the Idle Mode is triggered by the HA to perform MIP deregistration, the MIP deregistration request message is sent by the HA.  The method according to claim 1 or 2, wherein when the MS in the Idle Mode is triggered by the ASN Functional entity to perform MIP deregistration, the R3 link set between the FA and the HA for the MS is removed. The process is:  The FA forwards the received MIP deregistration request message to the HA, and the HA determines to perform MIP registration of the MS according to the message, removes the R3 link between the FA and the HA set for the MS, and returns a MIP to the FA to register the request response message. . The method according to claim 1 or 2, wherein when the MS in the Idle Mode is triggered by the HA to perform MIP deregistration, the MIP receives the registration request message, and the MS is removed between the FA and the HA. The process of setting up the R3 link is: The HA triggers the MIP of the MS to register, sends the MIP of the MS to the FA to register the request, and the HA removes the R3 link set between the FA and the HA for the MS, and the FA responds to the MIP of the MS sent by the HA to register the request.  6. The method according to claim 2, wherein the method further comprises: 'PC/LR sending a record deletion response message to the FA;  The FA returns the MIP to register the request response message.  The method according to claim 6, wherein when the MSN in the Idle Mode is triggered by the ASN Functional entity to perform MIP deregistration, the MIP deregistration request response message is returned to the Proxy Mobile Node, and the Proxy Mobile Node returns. Release the R3 link request response message to the Anchor PC/LR;  When the MS in the Idle Mode is triggered by the HA to perform MIP registration, the MIP deregistration request response message is returned to the HA.  8. The method according to claim 1, 2 or 6, wherein the PC/LR is a relay paging control entity/location registrar Relay PC/LR or an anchor paging control entity/location registrar Anchor PC/LR.  The method according to claim 1 or 2, wherein the MS related record is an MS identifier MS ID or / and a paging identifier PCID.  The method according to claim 1 or 2, wherein the MIP deregistration request message is a MIP registration request message or a MIP registration revocation request message carrying a MIP lifecycle Lifetime of 0.  The method according to claim 1, wherein the process of receiving the MIP deregistration request message and dismantling the R3 link set between the FA and the HA for the MS is:  After detecting the MS loss in the Idle Mode, the PC/LR sends an MS resource release request message to the MIP-related network 'entity; The network entity associated with the MIP initiates a mobile Internet protocol MIP to the MS to the HA. The registration request message, the HA removes the R3 link set between the FA and the HA for the MS.  12. The method according to claim 11, wherein the method further comprises: The HA returns a MIP registration response message to the MIP-related network entity, and the MIP-related network entity sends an MS resource release response message to the PC/LR.  The method according to claim 12, wherein before the sending the MS resource release response message, the method further includes:  The network entity associated with the MIP deletes the MS related resources stored by itself or/and informs other entities on the network side of the communication system to delete the MS related resources stored by itself.  The method according to claim 12, wherein the process of initiating a MIP deregistration request message to the MS by the MIP-related network entity to the HA is:  The proxy mobile Internet protocol client PMIP Client initiates a MIP registration request message to the MS to the FA, and the FA forwards the MIP registration request message to the HA;  The process of returning the MIP to the MIP-related network entity to register the response message is: returning the MIP to the FA to register the response message, and the FA forwards the MIP to the PMIP Client to register the response message.  The method according to claim 11 or 14, wherein the method further comprises:  Remove the R4 link between the FA and the Anchor PC/LR set up for the MS.  16. The method according to claim 12, wherein the sending the MS resource release response message to the PC/LR is: After the PMIP client sends the R3 link release response to the FA, the FA sends an MS resource release response message PC_PURGE_MS_RSSP to the PC/LR; or the FA forwards the MIP registration response message sent by the HA to the FA. After the PMIP Client, the FA sends an MS resource release response message to the PC/LR PC_PURGE_MS_RSP; Or the PMIP Client sends the MS resource release response message PC_PURGE_MS-RSP directly to the PC/LR.  17. The method according to claim 11, wherein the PC/LR detects that the MS loss process in the Idle Mode is:  Check whether the MS in the Idle Mode sends the location update request according to the preset period. Location Update Request. If yes, the MS in the Idle Mode is not lost; otherwise, the MS in the Idle Mode is lost.  18. The method according to claim 11, wherein the PC/LR detects that the MS loss process in the Idle Mode is:  When paging the MS, it is not paged in the Idle Mode within the set number of paging times. MS, then determine the MS loss in Idle Mode.  The method according to claim 11, wherein after the PC/LR detects the MS loss in the Idle Mode, the method further includes: removing the information of the MS in the authentication entity Authenticator by the PC/LR and The R4 link between the MS and Authentication is set.  The method according to claim 11, wherein the MS resource release request message carries an identifier of the lost MS in the Idle Mode;  The MIP-related network entity determines, according to the identifier of the MS carried in the request message, the MS that initiates the MIP deregistration request message.  The method according to claim 11, wherein the MS resource release request message carries a loss cause value of the MS in the Idle Mode, and the loss cause value is a location update. The Location Updated failure or the paging failure. The method according to claim 11, wherein the message carrying the R3 link information set up between the FA and the HA is: setting a MIP deregistration request message, and the VIIP life time setting Is 0. The method according to claim 11, wherein the process of sending an MS resource release request message to a network entity related to the MIP is:  • After sending the MS resource release request message to the FA PC-PURGE_MS_REQ, the FA sends an R3 link release request to the PMIP Client or sends a mobile advertisement message Mobility Adertisement;  Or directly send the MS resource release request message PC_PURGE_MS_REQ to the PMIP Client.  24. A device for performing MIP deregistration by an MS in an Idle Mode, the device comprising a trigger module, configured to send a MIP to a FA through a trigger module to register a request cancellation. The apparatus according to claim 24, wherein the device sends a MIP deregistration request message when the MS in the Idle Mode performs MIP deregistration, and the deregistration request message is a MIP lifetime lifetime of 0. MIP registration request message or MIP registration 4 apology request MIP Registration Revocation request message.  The device according to claim 24, wherein the device further comprises a deletion module, configured to delete the MS related record stored by itself.