WO2007109995A1

WO2007109995A1 - Method for a terminal to quit a network and mobile communication system

Info

Publication number: WO2007109995A1
Application number: PCT/CN2007/000977
Authority: WO
Inventors: Jianjun Wu; Liang Gu; Jinsheng Cao
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-03-27
Filing date: 2007-03-27
Publication date: 2007-10-04

Abstract

A method for a terminal to quit a network and the mobile communication system related to are provided. The method for a terminal to quit a network comprises: when the terminal is going to quit the network, the data path related to the terminal is released and the context information related to the terminal is deleted by the entities on the network side. It is convenient, flexible and efficient to realize for a terminal to quit a network by using the network quiting method provided by the invention, and besides, saving the system resource by releasing the resource distributed to the terminal by network in time during the network quiting process.

Description

Terminal network retreat processing method and mobile communication system

The present invention relates to a radio access network technology, and in particular, to a method for processing a terminal retiring in a radio access network and a mobile communication system capable of implementing a terminal retiring. Background of the invention

With the rapid development of Internet (Internet) services and the widespread use of wireless networks, and with the increase in the number of mobile users and the increase in user demand, the general packet radio service (GPRS, General Packet Radio Service), the third generation is currently required. Wireless systems such as mobile communications (3G), Worldwide Interoperability Microwave Access (WiMAX), and 3G (B3G, Beyond 3G) can support a wide range of services, including large capacity, large data volumes, and different quality of service requirements. As a bridge between wireless users and existing wired networks or other service networks, the wireless access network is mainly used to provide packet forwarding or routing functions between the service providing network and mobile users.

However, existing radio access network standards do not provide any solution for terminal outbound technology. , the content of the invention

The object of the embodiments of the present invention is to provide a method for processing a terminal to retreat from the network and a mobile communication system that can implement the network retreat of the terminal, thereby solving the problem of the network retreating when the network is initiated by the terminal or the network is initiated by the network. .

An embodiment of the present invention provides a method for processing a terminal to retired the network, including: when the terminal is disconnected from the network, the network side entity performs a front-end of the terminal-related data channel and deletes the context information of the terminal. In the embodiment of the present invention, when the terminal is shut down, the user actively withdraws from the network, the network side resource is blocked, or the network side service policy is changed, the terminal is disconnected.

The above method further includes: requiring the IP address allocation entity to release the IP address of the terminal. The method of the embodiment of the present invention specifically includes: the terminal MS sends a de-registration request carrying the network-backing indication to the serving base station; the serving base station responds to the de-registration request, and sends a message carrying the network-backing indication to the anchor access service gateway to perform the terminal. Release of related data channels and contexts.

Or the method further includes: the serving base station sending a de-registration command message carrying the back-off indication to the MS before the MS sends the registration request.

After learning the terminal back-off indication, the anchor access service gateway sends a network-back response message to the serving base station; the base station returns a network-back confirmation message to the anchor access service gateway.

The above method may further comprise the serving base station replying to the registration command to the terminal. Before the MS sends the registration request to the serving base station, the method further includes: the terminal initiates a mobile IP deregistration process, and the external proxy and the home agent release the mobile IP registration information after receiving the mobile IP deregistration request.

The method of the embodiment of the present invention may specifically include: sending, by the monthly base station, a de-registration command carrying the network-backing indication to the terminal, and starting a network-backing timer; when the timer expires, the base station initiates a message carrying the network-backing indication The anchor accesses the service gateway to release the terminal-related data channel and context.

An embodiment of the present invention further provides a mobile communication system, including: a terminal, a service base station, and an anchor access service gateway, where

The terminal is configured to send a de-registration request carrying a network-backing indication to the serving base station; the serving base station is configured to send a de-registration command to the terminal, and send a message carrying a network-backing indication to the anchor access service. Gateway

The anchor access service gateway is configured to receive the message carrying the network return indication, and perform terminal related data channel and context release. The terminal retiring method provided by the present invention can implement the terminal retiring conveniently, flexibly, and efficiently, and release the resources configured by the network side for the terminal in the process of retiring the network, thereby saving system resources. BRIEF DESCRIPTION OF THE DRAWINGS

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

2 is a schematic flowchart of an embodiment of a method for processing a terminal to be retired in a CMIP mode initiated by a terminal according to Embodiment 1 of the present invention;

3 is a schematic flowchart of an embodiment of a method for processing a terminal to be retired in a CMIP mode initiated by a terminal according to Embodiment 2 of the present invention;

4 is a schematic flowchart of an embodiment of a method for processing a terminal to be retired in a PMIP mode initiated by a terminal according to Embodiment 3 of the present invention;

5 is a schematic flowchart of an embodiment of a method for processing a network in a CMIP mode initiated by a network side according to Embodiment 5 of the present invention;

6 is a schematic flowchart of an embodiment of a method for processing a network in a CMIP mode initiated by a network side according to Embodiment 6 of the present invention;

FIG. 3 is a schematic flowchart diagram of an embodiment of a method for processing a network in a PMIP mode initiated by a network side according to Embodiment 7 of the present invention. Mode for carrying out the invention

For convenience of description, the following embodiments are all described by taking a WiMAX network as an example. It should be noted that the method and system for retiring the terminal provided by the embodiment of the present invention are not limited to the application to the WiMAX system, and may be applied to any other wireless access technology.

Regardless of other internal devices in the access network, the WiMAX network architecture system is shown in Figure 1, which mainly includes the terminal (MS, Mobile Subscribe Station), and accesses the monthly service network (ASN, Access Service Network ) and the Connected Network (CSN) are three major parts. The functions of the various network elements of the WiMAX network architecture system shown in Figure 1 are explained as follows:

MS: The MS is a mobile user equipment, and the user uses the MS to access the WiMAX network.

ASN: ASN is a set of network functions that provide wireless access services for WiMAX terminals. The ASN includes base stations (BS, Base Station) and access service network gateway (ASN-GW, Access Service Network Gate Way) network elements. Among them, the functions of the BS include: providing layer 2 (L2) connection of BS and MS, radio resource management, measurement and power control, compression and encryption of air interface data, and the like. The functions of the ASN-GW include: Proxy function for MS authentication, authorization and accounting functions, Anchor Authenticator functional entity; Network discovery and selection for NSP; Layer 3 for MS (L3 M Relay function, such as Internet Protocol (IP, Internet Protocol) address allocation; and radio resource management, etc. In addition to the above functions, ASN-GW can also include the following optional functional entities: Switching control function in ASN Entity; MS paging and location management, such as paging controller (PC) functional entity; tunnel management function entity between ASN-CSN, equivalent to external proxy (FA) in mobile IP (MIP) technology, and anchor proxy MIP client (Anchor PMIP Client) functional entity; and visit location registration, anchor service flow authorization entity (Anchor SFA) functional entity.

The functional entities in the above ASN-GW, because of the movement of the MS, the timing of their respective trigger changes is different, which will result in the above functional entities serving a specific MS, such as Anchor Authenticator, FA, Anchor SFA, Anchor PMIP. Clients and the like may exist in different ASN-GWs, so in one activity, interactions between different ASN-GWs will be involved.

CSN: CSN is an IP connection service for WiMAX terminals. The main functions provided by CSN include: MS IP address allocation; Internet access; authentication, authentication and accounting (AAA) Proxy or AAA server (AAA server); user-based authorization control; ASN to CSN tunnel, equivalent to home agent (HA) in MIP technology; WiMAX user billing and inter-operator settlement; CSN in roaming case Tunneling between; ASN switching; various WiMA services such as: location-based services, multimedia multicast and broadcast services, IP multimedia subsystem services.

The embodiment of the present invention mainly solves the problem of the network retreat of the MS, including the network exit initiated by the MS and the network exit initiated by the network. The reason why the MS initiates the network retreat includes the shutdown operation and the user actively withdrawing from the network. The reason for the network side to initiate the network revocation is as follows: The network side captures the MS abnormal network drop, the network side resource is blocked, and the network side initiates the network exit according to the network side service policy. The network-side resource blocking of the network is triggered by the network-side functional entity that triggers the network-back-off according to the load state of the physical entity in which the network entity is located. The network side resource is blocked, and may occur in the physical entity where the FA is located, or the physical entity where the SFA is located, or the physical entity where the HA is located. When network resources are congested, that is, resources are insufficient, the network side may consider releasing resources occupied by those MSs with lower priority so that resources can be used by those users who need them. At this time, the network exit process will be initiated, and the MS will be temporarily unable to use the network. The network side service policy includes a network access provider NAP, a home network service provider H-NSP, and a service policy of the visited network service provider V-NSP, and the like, for example, may be an AAA server according to an operator (including NAP, The service policy of the H-NSP and/or the V-NSP is configured. The user is required to quit the network, and the MS owner voluntarily requests the network to be retired.

It should be noted that, in the case that the network side initiates the network retreat, the network side entity that initiates the network revocation includes the base station BS and the Serving ASN-G 7 Anchor ASN-GW. If the network entity that initiates the network revocation is the serving ASN-GW/Anchor ASN-GW, the trigger source may be one of the functional entities, including: a data channel function (DPF), a service stream licensor (SFA), an authenticator. ( Authenticator ), FA, Accounting Client (Accounting Client), Agent MIP client (PMIP Client), HA, Policy Server (PF), AAA server, etc.

In each of the above cases, whether the network initiated by the MS or the network initiated by the network, according to the MIP support, it can be divided into: MS outbound in the SIP (Simple IP) mode; PMIP The MS exits the network in the mode; and the MS in the client mobile IP (CMIP) mode exits the network. The main difference between the three modes is that there is no MIP release process in the SIP mode. The MIP signaling message in the PMIP mode is initiated by the network side. The MIP signaling message in the CMIP mode can be initiated by the MS or by the network side. initiate. Therefore, there are different MS exit processes corresponding to different modes.

The MS network retreat method provided by the embodiment of the present invention mainly includes: when the MS or the network side initiates the network retreat, the network side entity performs the network retreat operation, releases the data channel related to the MS, resources, etc., and deletes the saved data. MS related context information.

In addition, the method of the present invention further includes requiring the IP address allocation entity to release the IP address resource. For the release of IP address resources, it should be noted that the IP address release process differs according to the way IP addresses are allocated. Therefore, during the MS network retreat process, the IP address release process that needs to be performed is also different according to the allocation mode. For example, if the IP address is obtained during the MIP registration process (for example, by the HA;), the IP address can be released simultaneously during the MIP release process, and a separate IP release process is no longer needed. If the IP address is dynamically assigned (eg, by a Dynamic Host Configuration Protocol (DHCP) proxy/server), a separate DHCP signaling interaction procedure is required to release the IP address. If the IP address is assigned by the AAA, the Anchor Authenticator can interact with the AAA to release the IP address when the network is disconnected. If the IP address is assigned by another entity, it also needs to interact with the entity to release the IP address when the MS exits the network, and so on. In summary, regardless of the IP address allocation method, the MS will request to release the IP address resource when it exits the network. The method of releasing may be that the MS exchanges the signaling message with the entity responsible for allocating the IP address to release the IP, or the MS does not directly notify the Entity, IP lifetime that is notified by other entities on the network side or maintained by the entity itself

(Lifetime) expires to release the IP address.

Embodiments of the present invention will be further described below with reference to the accompanying drawings.

Embodiment 1: MS quit network initiated by MS in CMIP mode

FIG. 2 is a schematic diagram of a network ejecting process initiated by an MS in a CMIP mode according to an embodiment of the present invention, as shown in FIG. 2:

Step 201: Optionally, after the MS triggers the network retreat, the MS initiates a MIP to register the process. It should be noted that, in the embodiment, the foregoing step 201 includes:

2011: The MS encapsulates a complete MIP registration request message, which is sent to the FA. The MIP Registration Request message carries the life cycle Lifetime = 0 to indicate that the MIP registration process is initiated.

2012: The FA forwards the MIP Registration Request message carrying Lifetime = 0 to the HA;

2013: After receiving the MIP Registration Request message, the HA verifies the legality of the message, and after replying to the MIP registration reply message, the MIP registration reply message is sent to the FA;

In this step, if the HA itself does not have a PMN-HA key to verify the validity of the MIP Registration Request message, the HA needs to request AAA authentication;

2014: The FA forwards the MIP Registration Reply message to the MS, and the MIP goes to the registration process.

In the above process, the FA and the HA release the corresponding resources after receiving the MIP Registration Request message. If the IP address is allocated by the HA, the IP address resource can be released at the same time. Further, optionally, after receiving the MIP Registration Request message, the HA may notify the AAA to release the MS-related context.

Thereafter, optionally, if the IP address is dynamically allocated, the MS initiates an IP address release. Process. The IP address release process specifically includes: the MS sends a DHCP Release Request message to the DHCP server, initiates a DHCP release process, requests to release the dynamically assigned IP address, and the DHCP server releases the IP address dynamically allocated for the MS.

Step 202: The MS sends a network revocation request message to the serving base station (SBS) to request to leave the network, and the message may also carry a network retreat indication (for example, a shutdown indication).

In an embodiment of the present invention, the back-off request message may be a de-registration request message DREG__REQ, and the De-Registration Request Code=0 therein.

Step 203: After receiving the MSRP request message, the SBS initiates a data path release process related to the MS.

The data channel release process in this step specifically includes:

2031: The service ASN-GW to which the SBS is connected to the SBS, that is, Serving ASN-GW, . Send Data Channel Release Request Path De-registration Request ₀

The Path De-registration Request carries the MS ID and the back-off indication of the MS, and may further carry an Anchor Authenticator ID and an Accounting Client ID of the MS.

2032: The serving ASN-GW forwards the received Path De-registration Request to the Anchor ASN-GW where the FA is located.

The anchor access service gateway may also be an anchor access service gateway where the data function body (ADSL) is located, or an anchor access service gateway where the AnchorAuthenticator is located, or an anchor access service gateway where the Anchor SFA is located, or Anchor Accounting. The anchor where the client is located is connected to the service gateway.

At the same time, optionally, the SBS can also be placed at the time before the resource allocated to the MS and the reserved context, including the security context and state machine, the service flow context and the state machine, such as: the assigned air interface connection identifier (CID) ), resource scheduling queue state machine, service encryption key (TEK) state machine, authentication key (AK), and AK context, HMAC Digest, and so on. If the step 201 is not performed, the MIP can be used to initiate the registration process. The FA sends the MIP Registration Request message with the Lifetime = 0 to the HA to request the HA to release the related resources. For details, refer to steps 2012 and 2013.

In addition, after receiving the data channel release request of the MS, the Anchor ASN-GW may further initiate a context release process according to the network revocation indication, including: ASN of the anchor ASN-GW to the Anchor Authenticator of the MS. The GW sends an indication message for deleting the MS context, Delete MS context Indication; at this time, if the security context of the MS remains in the AAA, the Anchor Authenticator of the MS will notify the AAA to inform the MS to quit the network, and request to delete the security context information of the MS; The ASN-GW where the Anchor Authenticator is located is

The following reply message Delete MS context Ack.

If the current service is charging, the Anchor ASN-GW receives the data channel release request of the MS, and initiates the stop charging process according to the network revocation indication, including: Anchor ASN-GW or FA to the Accounting Client of the MS. The ASN-GW sends a termination charging request message. Further, the Accounting Client sends a stop charging message to the AAA, Account-Request/Sto. Then, the ASN-GW where the Accounting Client is located returns a termination charging response message to the Anchor ASN-GW. .

Optionally, the anchor ASN-GW where the anchor SFA is located initiates a location update request SFA-LU-Request to the policy server PF according to the network revocation indication. In the roaming scenario, the message may need to pass one or more visited PFs (V-PF). ) to get to the hometown PF (H-PF). The message carrying the MS's back-off indication can also carry the reason for the network retreat. The policy server PF deletes the MS context information it maintains according to the received notification message. At the same time, the policy server can record the reason for the network back. Optionally, the PF also needs to notify the AAA to release the MS-related context. It should be noted that the PF may be an independent entity or a functional entity within the AAA.

In addition, optionally, if the MS does not initiate the IP address release process, at this time, The FA notifies the DHCP agent to initiate an IP address release procedure.

2033: The FA in the Anchor ASN-GW releases the resource corresponding to the current MS, and the reply data channel releases the response Path De-Registration Response to the serving ASN-GW.

In this step, if the data channel is not established based on the BS, the FA needs to delete the data channel corresponding to the MSID according to the back-off indication; otherwise, the data channel does not need to be removed.

2034: Service ASN-GW replies to Path De-Registration Response to SBS. Step 204: The SBS replies to the MS quit message response message, indicating that the MS terminates all services with the current BS, and the MS quits the network.

In the embodiment of the present invention, the back-off response message is a de-registration instruction DREG_CMD, and the Action Code = 04 therein.

In particular, the foregoing step 204 can also be performed before step 203, so that the MS back-off time can be effectively shortened.

Step 205: The SBS replies with a retiring confirmation message to the serving ASN-GW.

In the embodiment of the present invention, the network confirmation message is a data channel release confirmation message Path De-Registration Ack.

Further, the SBS can also release the resources allocated before the MS and the reserved context at this time.

Step 206: The service ASN-GW replies with a network confirmation message to the Anchor ASN-GW where the FA is located.

If the MIP registration process or the IP address release process has not been performed before, the MIP registration process and the IP release process may be performed after the above steps are performed. Because the MIP registration process or the IP address release process needs to interact with the core network entity, the delay is large. Therefore, the MIP registration process or the IP address release process is performed at this time, which greatly reduces the network exit from the user's point of view. Delay.

Further optional, the IP address release process may not be performed by the DHCP server. The internal aging mechanism implements IP address release, that is, automatically releases the dynamically assigned IP address after the Lifetime of the IP address expires.

Example 2:

Embodiment 2 of the present invention provides another method for MS-originated MS quit in CMIP mode. The method considers that after the FA knows that the MIP of the MS is de-registered, the FA initiates the corresponding data channel of the MS. The process is released, and the network response message is sent to the MS, indicating that the MS is offline. The process is as shown in Figure 3.

Step 301: After the MS triggers the network retreat, the MS initiates a MIP registration process. For the specific process, refer to step 201 above. It should be noted that, in this embodiment, the step is a mandatory step.

At this time, optionally, the MS may also initiate an IP address release process.

Step 302: The FA initiates a data channel release process associated with the MS.

The data channel release process includes:

3021: The Anchor ASN-GW where the FA is located sends a Data Channel Release Request message. The Path De-registration Request is sent to the service ASN-GW. The message carries the MSID and the back-off indication and the Anchor Authenticator ID and Accounting Client ID that may be further carried.

3022: The service ASN-GW forwards the received data channel release request message to the SBS.

3023: BS reply data channel release response Path De-Registration Response to the service ASN-GW.

The service ASN-GW forwards the data channel release response. The Path De-Registration Response sends the FA in the Anchor ASN-GW where the FA is located, and the FA in the Anchor ASN-GW releases the resource corresponding to the current MS.

At this time, optionally, the Anchor ASN-GW receives the data channel release request of the MS. The context release process is initiated according to the back-off indication. For details, refer to the context release process provided in Embodiment 1.

Further, if the current service is charging, the Anchor ASN-GW receives the Data Path release request of the MS, and may initiate a stop charging process according to the network revocation indication. For the specific process, refer to Embodiment 1.

Optionally, if the MS does not initiate the IP address release process, the FA may notify the DHCP agent to initiate an IP address release process.

Step 303: The Anchor ASN-GW where the FA is located returns a network confirmation message to the service ASN-GW.

Step 304: The service ASN-GW replies to the retiring confirmation message to the SBS.

Step 305: The SBS replies to the network return response message to the MS, indicating that the MS terminates all services with the current BS, and the network is successfully retired.

In an embodiment of the present invention, the back-off response message is DREG-CMD, where

Action Code = 04.

Further, optionally, if the IP address release process is performed before, the FA may initiate an IP address release procedure for the dynamically assigned IP address. In addition, as described in Embodiment 1, the IP address release process may not be performed, and the IP address is released by the aging mechanism in the DHCP server, that is, the dynamically allocated IP address is automatically released after the Lifetime of the IP address expires.

Embodiment 3: MS-initiated MS network retreat process in PMIP mode:

In the PMIP mode, since the MS does not support the MIP signaling, the steps 201 and 301 described in Embodiments 1 and 2 do not exist, and other processes are similar to the retiring procedure described in Embodiment 1. In this embodiment, the MIP deregistration process should be performed during the release of the data channel. Line, you can use the following two ways:

Manner 1: The FA initiates the MS to initiate. The MIP goes to the registration, and the registration message is sent to the HA via FA, and the FA and HA release the MIP-related registration information.

Manner 2: The FA notifies the MS to release the MIP-related registration information, and the FA initiates the MIP to register the message, and the FA and the HA release the MIP-related registration information.

The MS-initiated retreat process in the PMIP mode is shown below. The specific process is shown in Figure 4, which mainly includes:

Step 401: The MS sends a network revocation request message to the SBS, requesting to leave the network, and the message may also carry the network retreat indication.

In this embodiment, the backoff request message may be a deregistration request message.

DREG REQ , and De-Registration Request Code=0.

Step 402: After receiving the MSRP request message, the SBS initiates a data channel release process related to the MS, including:

4021: SBS sends a data channel release request message. Path De-registration Request A service that connects to the SBS. The ASN-GW carries the MSID and the back-off indication. It may further carry the Anchor Authenticator ID and the Accounting Client ID.

4022: The serving ASN-GW forwards the received Path De-registration Request to the Anchor ASN-GW where the FA is located.

4023: The Anchor ASN-GW receives the Path De-registration Request of the MS, and sends an R3 session release request message to the ASN-GW where the Anchor PMIP Client of the MS is located according to the back-off indication. R3 Session Release Request

4024: After receiving the R3 Session Release Request, the Anchor PMIP Client finds the key information of the relevant PMN-HA of the MS, encapsulates a complete MIP registration request message MIP Registration Request, and carries Lifetime = 0 to indicate the MIP registration process. Send to Anchor ASN-GW where FA is located. 4025: The FA forwards the MIP Registration Request message to the HA.

4026: After receiving the HA, verify the validity of the message and reply to the MIP registration reply message MIP Registration Reply to FA.

4027: The FA forwards the MIP Registration Reply message to the Anchor PMIP Client. Through the above steps 4024 - 4027, FA and HA receive MIP Registration

After the Request message is released, the corresponding resource is released. If the IP address is allocated by the HA, the IP address resource can be released at the same time. Further, optionally, after receiving the MIP Registration Request message, the HA may also notify the AAA to release the MS-related context.

4028: The Anchor PMIP Client deletes some context information of the MS it retains; and replies to the R3 session release response message R3 Session Release Response to the FA.

4029: The FA receives the R3 Session Release Response message returned by the Anchor PMIP Client, indicating that the R3 link of the MS has been successfully released, releasing the resource corresponding to the MS locally, and replying to the data channel release response message Path De-Registration Response to the MS The service ASN-GW to which the current SBS is connected.

If the data channel is established based on the BS, the MS network does not need to be removed from the data channel. You only need to release the MS context and the corresponding resources. Otherwise, the FA needs to delete the data channel corresponding to the MSID according to the network exit indication.

Optionally, if the current service is charging, the Anchor ASN-GW/FA may initiate a stop charging process, that is, send a termination charging request message to the ASN-GW where the Accounting Client of the MS is located. Further, the accounting client sends a stop charging message Account-Request/Stop to the AAA, and then the ASN-GW where the Accounting Client is located returns a terminating charging response message to the Anchor ASN-GW.

4030: The serving ASN-GW replies to the Path De-Registration Response message to the SBS. Step 403: The SBS replies to the back-off response message to the MS, indicating that the MS terminates all services with the current BS, and the network is successfully retired. In the embodiment of the present invention, the back-off response message is a de-registration instruction DREG_CMD, and the Action Code = 04 therein. '

Step 404: The SBS replies with a retiring confirmation message to the serving ASN-GW.

At this time, the SBS can be used as the resource allocated before the MS and the reserved context, including the CID, the resource scheduling queue state machine, the TEK state machine, the AK and the AK context, the HMAC Digest, and the like.

Step 405: The service ASN-GW replies with a network confirmation message to the Anchor ASN-GW where the FA is located.

Optionally, the FA may send an R3 Session Release Ack message to notify the corresponding Authenticator of the MS to delete all corresponding context information of the MS. If the security context of the MS is retained in the AAA, the Anchor Authenticator of the MS can notify the AAA to inform the MS to quit the network, and request to delete the security context information of the MS. The FA can notify the Anchor SFA corresponding to the MS to delete all the corresponding contexts of the MS. information. The Anchor SFA can also send the SFA-LU-Request message carrying the network deletion indication to the PF for location update. The PF is required to delete the MS-related context information, including the SFID, FID, and the information such as the authorized service flow state machine. After that, the service flow authorization entity location update response message SFA-LU-Response will be returned to the Anchor SFA.

For the dynamically assigned IP address, the FA can notify the DHCP proxy to initiate the IP address release process, that is, send a DHCP Release Request message to the DHCP server. In addition, after the MS triggers the network retreat, the IP address release process is initiated by the MS before step 401. Alternatively, the IP address release process is implemented by the aging mechanism in the DHCP server without performing the IP address release process.

Embodiment 4: MS egress network initiated by MS in SIM mode In the SIP mode, there is no MIP release process described in Embodiments 1-3, and other processes are the same as those in Embodiments 1-3, and reference may be made to the above Embodiments 1-3, and details are not described herein again.

Embodiment 5: MS network revocation process initiated by the network side in CMIP mode

5 is a schematic diagram of a MS network revocation process initiated by a network side in a CMIP mode according to an embodiment of the present invention. As shown in FIG. 5, the method mainly includes:

Step 501: Optionally, when the network side entity triggers the MS to exit the network based on the network side resource blocking and/or the network side service policy, the SBS sends a network return response message carrying the network return indication to the MS, requesting the MS to exit the network. .

In this step, the back-off timer T1 can be further started. And the back-off response message may also carry the following information: a time indication or a time range indication, requiring the MS to access the network within a specified time within a specified time or within a specified time.

In an embodiment of the present invention, the back-off response message is a de-registration instruction DREG_CMD, and the Action Code=0.

Step 502: Optionally, the FA on the network side initiates a MIP to register the process.

The MIP deregistration process described in this embodiment includes:

5021: The FA sends a FA notification broadcast message FA advertisement to the MS, and the message carries Lifetime = 0;

5022: After receiving the FA advertisement of the FA, the MS sends a MIP Registration Request message to the FA, and the message carries Lifetime=0;

5023: The FA forwards the MIP Registration Request message to the HA;

5024: The HA verifies the validity of the message, and returns a MIP registration reply message after being verified to be legal. MIP Registration Reply to FA;

In this step, if the HA itself does not have the PMN-HA key to verify the validity of the MIP Registration Request message, the Bay ¹ J HA needs to request AAA authentication; 5025: The FA forwards the MIP Registration Reply message to the MS, and the MIP registration process is completed.

In the above process, the FA and HA release the corresponding resources after receiving the MIP Registration Request message. Further, optionally, after receiving the MIP Registration Request message, the HA needs to notify the AAA to release the MS-related context.

In the above process, the SBS can also delete the context information of the MS.

Optionally, if the IP address is not released during the MIP deregistration process, if the IP address is dynamically allocated, the MS may further initiate an IP address release process, that is, interact with the entity responsible for allocating the IP through the DHCP dry process. Release the IP address resource.

Step 503: Optionally, the MS sends a network revocation request message to the SBS, requesting to leave the network.

In an embodiment of the present invention, the back-off request message is a de-registration request message DREG_REQ, and the De-Registration Request Code=0 therein.

It should be noted that if the SBS is set to the timer T1 in the above step 501, the step may not be performed.

Step 504: When the SBS receives the MS network revocation request or the timer T1 times out, the data channel release process related to the MS is initiated.

The data channel release process described in this embodiment is the same as the above step 203, and will not be described again.

As described in Embodiment 1, if the MS has not initiated MIP registration before, the MIP may initiate a registration message by the FA at this time. In addition, if the IP address # is not previously placed, the DHCP agent can be notified by the FA to initiate the IP address release process.

In addition, in the MIP deregistration process, the anchor ASN-GW where the FA is located may also be one of the ASN-GW, the anchor SFA, the anchor DPF, and the Anchor Accounting Client where the anchor authenticator of the MS is located according to the back-off indication. A plurality of indication messages for deleting the MS context are sent, and one or more of the anchor authenticator, the anchor SFA, the anchor DPF, and the anchor accounting client respond to the message Delete all corresponding context information of the MS. Further, if the security context of the MS is retained in the AAA, the anchor authenticator and the anchor charging client of the MS may notify the AAA to inform the MS to leave the network, and carry the MS identifier, the network return indication, and/or the network exit. The reason is that the security context information of the MS is required to be deleted; the authentication authorization accounting server deletes the MS context information maintained by the authentication according to the received notification message. At the same time, you can record the reason for the MS to retreat. If the IP address of the MS is assigned by the AAA, the AAA also releases the IP address resource of the MS according to the received notification message.

In addition, optionally, the anchor ASN-GW where the anchor SFA is located initiates a location update request SFA-LU-Request to the policy server PF according to the network redirection indication. In the roaming scenario, the message may need to pass one or more visited PFs to reach. Hometown PF. The message carrying the MS's back-off indication may also carry the reason for the network retreat. The policy server PF deletes the MS context information it maintains according to the received notification message. At the same time, the policy server can record the reason for the network back. Optionally, the PF also needs to notify the AAA to release the MS-related context.

Step 505: The SBS sends a network cancellation confirmation message to the service ASN-GW.

At this time, after the SBS receives the network-back response message of the serving ASN-GW, if the step 501 is not executed before, the network response message is not sent to the MS, then the network sends a network response message to the MS. Requires a withdrawal.

In the embodiment of the present invention, the network acknowledgment confirmation message may be a Path De-Registration Ack message. At this time, the SBS may release the resources allocated before the MS and the reserved context, including the security context and state machine, the service flow context and the state machine, such as the allocated CID, the resource scheduling queue state machine, the TEK state machine, AK and AK context, Li AC Digest.

Step 506: The service ASN-GW forwards the network confirmation message to the Anchor ASN-GW where the FA is located.

Further, the FA may notify the Anchor SFA corresponding to the MS to delete at this time. All context information corresponding to the MS, such as the service flow state machine and the service flow context and state machine information corresponding to the MS. At the same time, the Anchor SFA sends an SFA-LU-Request message, where the message carries a network deletion indication, and the PF performs location update. The PF is required to delete the MS-related context information, such as the SFID, the FID, and the information such as the authorization service flow state machine. The PF will return an SFA-LU-Response message to the Anchor SFA after processing is complete.

In addition, if the MIP registration process has not been performed before, the MIP can be initiated by the FA to register the process. If the IP address has not been released before, the FA can notify the DHCP Proxy to initiate the IP address release process for the dynamically assigned IP address. In addition, as described in the previous embodiment, the IP address release process may not be performed, and the IP address is released by the aging mechanism in the DHCP server. Since the MIP registration process and the IP address release process need to interact with the core network entity, if the MIP registration and IP address release process are performed later, the network delay is greatly reduced from the user's point of view.

Example 6:

This embodiment provides another MS quit network initiated by the network side in the CMIP mode. The method considers that after the FA knows that the MIP of the MS is de-registered, the FA initiates the corresponding data channel dry-discharging process of the MS, and actively sends a network-back response message to the MS, indicating that the MS is retired, and the process is as follows. The main components shown in Figure 6 include:

Step 601: The FA on the network side initiates a MIP registration process, and the specific process is the same as step 502.

Step 602: The FA initiates a data channel release process related to the MS, and the specific process is the same as step 302.

Step 603: The Anchor ASN-GW where the FA is located returns a network confirmation message to the service ASN-GW.

In the embodiment of the present invention, the network confirmation message is a data channel release confirmation message Path De-Registration Ack:. Step 604: The serving ASN-GW replies to the retiring confirmation message to the SBS.

Step 605: The SBS replies to the network return response message to the MS, indicating that the MS terminates all services with the current BS, and the network is successfully retired.

In an embodiment of the invention, the back-off response message is DREG_CMD, where Action Code = 04.

Further, optionally, if the IP address release process is performed before, the FA may initiate an IP address release procedure for the dynamically assigned IP address. In addition, as described in Embodiment 1, the IP address release process may not be performed, and the IP address is released by the aging mechanism in the DHCP server, that is, the dynamically allocated IP address is automatically released after the Lifetime of the IP address expires. .

Embodiment 7: The MS network revocation process initiated by the network side in the PMIP mode:

In the PMIP mode, since the MS does not support MIP signaling, the steps 501 and 601 described in Embodiments 5 and 6 do not exist, and other processes are similar to the revocation process described in Embodiment 5 or 6. In this embodiment, the MIP deregistration process should be performed during the release of the data channel, and the following two methods can be used:

Method 1: The FA triggers the MS to initiate the MIP to register, and the registration message is sent to the HA via FA, and the FA and HA release the MIP-related registration information.

Figure Ί shows the MS network revocation process initiated by the network side in the PMIP mode according to the embodiment, which specifically includes:

Step 701: Optionally, after the network side triggers the MS to exit the network, the SBS sends a network return response message to the MS to initiate the MS network exit process.

In an embodiment of the present invention, the back-off response message is a de-registration instruction DREG_CMD, and the Action Code = 04 therein. Optionally, after the MS receives the network return response message, the IP address release process is initiated.

The above steps are an optional step. In the subsequent process, after receiving the Path De-Registration Ack message of the serving ASN-GW, the SBS sends a network return response message to the MS, requesting the MS to exit the network, that is, completing all data channel translation and resources on the network side. After the release process, the SBS notifies the MS to retire.

Step 702: The ASN-GW where the FA is located initiates a data channel release process.

The data channel release process includes:

7021: The Anchor ASN-GW/FA sends an R3 Session Release Request to the ASN-GW where the Anchor PMIP Client of the MS is located.

7022: The Anchor PMIP Client finds the key information of the relevant PMN-HA of the MS, encapsulates a complete MIP Registration Request message, carries Lifetime = 0, and sends it to the Anchor ASN-GW where the FA is located.

7023: The FA forwards the MIP Registration Request message to the HA.

7024: After receiving the HA, the certificate proves the validity of the message and returns a MIP Registration Reply message to the FA.

7025: The FA forwards the MIP Registration Reply message to the Anchor PMIP Client.

7026: The Anchor PMIP Client deletes some context information of the MS it retains; and replies to the R3 Session Release Response to the FA.

7027: The FA receives the R3 Session Release Response message of the Anchor PMIP Client, indicating that the R3 link of the MS has been successfully released, starts releasing the data channel associated with the MS, and sends a Path De-Registration Request message to the J-service ASN- GW.

7028: The service ASN-GW forwards the Path De-Registration Request message to the SBS.

7029: The SBS replies to the service ASN-GW with a Path De-Registration Response message. 7030: The serving ASN-GW further replies to the Path De-Registration Response message to the Anchor ASN-GW where the FA is located. Step 703: After receiving the Path De-Registration Response message, the Anchor ASN-GW releases the resource corresponding to the MS locally, and returns a network confirmation message to the service ASN-GW.

In this embodiment, the network confirmation message is a data channel release confirmation message Path De-Registration Ack:.

Optionally, if the current service is charging, the Anchor ASN-GW/FA sends a termination charging request message to the ASN-GW where the Accounting Client of the MS is located. Further, the Accounting Client sends a stop charging message to the AAA. Request/Stop; and then the charging response message.

Step 704: The service ASN-GW further forwards the network acknowledgment message to the SBS, and completes the three-way handshake process of the data channel release.

After the SBS receives the acknowledgment message of the service ASN-GW, if the SN is not executed, the network does not send the quit response message to the MS. .

This step is as described above. After all data channel hopping and resource release processes are completed on the network side, the SBS notifies the MS to quit the network.

In an embodiment of the present invention, the back-off response message is DREG_CMD, where Action Code=0.

Further, after replying to the Path De-Registration Ack, the FA notifies the Anchor Authenticator corresponding to the MS to delete all the context information of the corresponding MS. If the AAA retains the dynamic context information of the MS, the Anchor Authenticator further including the MS notifies the AAA to delete the dynamic security context information of the MS that it reserves, such as PMN-HAkey that can exist for MS.

Further, the FA sends an R3 Session Release Ack message to notify the anchor SFA corresponding to the MS to delete all the context information of the corresponding MS. At the same time, the Anchor SFA sends the service flow authorization entity location update message SFA-LU-Request, which carries the network removal indication to the PF for location update; the PF is required to delete the MS related context information, such as SFID, FID, including Authorizing the service flow state machine and other information; The PF will return an SFA-LU-Response message to the Anchor SFA after the processing is completed.

Optionally, for the dynamically assigned IP address, the FA may also notify the DHCP proxy to initiate an IP address release process in this step, and the DHCP proxy sends a DHCP Release Request message to the DHCP server. Optionally, the process of releasing the IP address is not performed, and is ensured by the aging mechanism in the DHCP server. After the lifetime of the IP address expires, it is automatically released. Embodiment 8: The MS network revocation process initiated by the network side in the SIP mode:

In the SIP mode, there is no MIP release process described in Embodiments 4-6, and other processes are the same as those in Embodiments 4-6. For details, refer to the above Embodiments 4-6.

It should be noted that, in each step of the foregoing embodiment, if there is no Anchor ASN-GW, the serving ASN-GW is the AnchorASN-GW of the current SBS, and the services ASN-GW and AnchorASN-GW mentioned above are used. The interaction process is not needed. At the same time, if the functional entities mentioned above are in the same physical entity, the interaction between them is an internal primitive.

In the process described in the foregoing embodiment, each network entity also releases the corresponding MS context and resources, such as a CID allocated by the MS for the MS, a reserved AK, an AK context, a SAID, a TEK, and the like, and an anchor information; Service flow identifier (SFID), flow identifier (FID) in the SFA or PF or AAA, paired master key PMK in the authenticator, authentication key AK, AK context, MIP, etc. All security contexts; Master Session Key (MSK), Extended Master Session Key (EMSK), Mobile IP Root Key (MIP-RK:), the key between the mobile node and the home agent (MN-HA-Key), the key between the mobile node and the external agent (MN-FA-Key), between the external agent and the home agent All security-related contexts such as the key (FA-HA-Key). However, it is not limited to the above functional entities.

Corresponding to the foregoing method for retiring the terminal, the embodiment of the present invention further provides a mobile communication system that can implement terminal backoff, and mainly includes: a terminal, an SBS, and an Anchor ASN-GW. The terminal is configured to send a deregistration request carrying the backoff indication to the SBS;

The SBS is configured to send a de-registration command to the terminal, and send a message carrying the network-backing indication to the Anchor ASN-GW, or further, after receiving the network-back response message, returning a network-return confirmation message to the Anchor ASN-GW;

The Anchor ASN-GW gateway is configured to receive the message carrying the network retreat indication, and perform the data channel and context release related to the terminal, or further used to send the network return response message after receiving the message carrying the network return indication. To SBS.

The mobile communication system of this embodiment may further include: a service ASN-GW connected to the SBS and the Anchor ASN-GW, configured to forward, by the SBS, a message carrying a network back indication to the Anchor ASN-GW.

In addition, in order to implement the MIP deregistration process when the terminal exits the network, the mobile communication system in this embodiment further includes an FA and an HA, which are used to release the MIP deregistration request after receiving the anchor Anchor ASN-GW. MIP registration information.

In order to further release the context information of the terminal when the terminal exits the network, the mobile communication system in this embodiment further includes: an anchor authenticator, an anchor service flow authenticator, and an anchor charging client, for receiving After the terminal ANO-GW sends the network back-off notification, the context information of the terminal is deleted. In addition to the anchor authenticator, the anchor service flow authenticator, and the anchor charging client, the mobile communication system may further include an authentication authorization charging server that stores terminal context information, since the HA receives the MIP registration request after receiving the MIP. , will send the terminal back to the network to notify The authentication authorization charging server; or because the anchor authenticator or the anchor charging client deletes the context information of the terminal, the sending terminal also sends a network outbound notification to the authentication and authorization charging server; After receiving the network exit notification from the home agent, anchor authenticator or anchor accounting client, the authorized accounting server will release the context information of the terminal.

In order to further release the IP address assigned to the terminal when the terminal exits the network, the mobile communication system in this embodiment may further include: an IP address allocation entity, configured to allocate an IP address to the terminal, and retreat at the terminal At the time of the network, the IP address assigned to the terminal is released.

Appropriate improvements in accordance with preferred embodiments of the present invention may be made in the specific implementation to suit the particular needs of the particular situation. Therefore, it is to be understood that the specific embodiments of the invention described herein are merely illustrative and are not intended to limit the scope of the invention.

Claims

Claim

A method for processing a terminal network retreat, comprising: releasing a network-side entity to perform release of the terminal-related data channel and deleting context information of the terminal when the terminal is disconnected from the network.

The method of claim 1, wherein the terminal is disconnected from the network when the terminal is shut down, the user actively withdraws from the network, the network side resource is blocked, or the network side service policy is changed.

3. The method according to claim 1, wherein the network side entity triggers the network retreat.

The method according to claim 3, wherein the performing the network retreating comprises: the serving base station sending a deregistration command message carrying the network redirection indication to the terminal.

The method according to claim 1 or 4, wherein the retiring of the terminal comprises: the terminal sending a deregistration request carrying the retiring indication to the serving base station.

The method according to claim 5, wherein before the terminal sends the registration request, the method further includes: the terminal initiates a mobile IP registration process, and the external agent and the home agent receive the mobile IP to register. Release the mobile IP registration information after the request.

The method according to claim 6, wherein the home agent notifies the authentication and authorization accounting server to release the context information related to the terminal after receiving the mobile IP deregistration request.

The method according to claim 5, wherein before the terminal sends the deregistration request, the method further includes: requiring the IP address allocation entity to release the IP address of the terminal.

9. The method of claim 8, wherein the releasing the IP address of the terminal comprises: the terminal initiating a dynamic host configuration protocol release request, requesting the IP address allocation entity to release the IP address of the terminal.

The method according to claim 5, after the terminal sends the deregistration request, the method further includes: the serving base station sending a message carrying the network retreat indication to the anchor access service gateway, performing the terminal related data channel and the context freed.

The method according to claim 10, wherein the message carrying the back-off indication sent by the serving base station is further sent to the anchor access service gateway through the service access network gateway, and the terminal-related data channel is The release of the context.

The method according to claim 10 or 11, further comprising: the anchor access service gateway notifying the anchor authenticator, the anchor service flow authorizer and/or the anchor accounting client to delete the terminal context information.

13. The method according to claim 5, further comprising: in the terminal mobile IP mode, the mobile IP deregistration process is initiated by the external agent, and the external agent and the home agent release the mobile IP registration information; or

In the proxy mobile IP mode, the external proxy triggers the proxy mobile IP client to initiate the registration of the mobile IP, and the external proxy and the home agent release the mobile IP registration information; or the external proxy notifies the proxy mobile IP client to release the mobile IP registration information and initiates The mobile IP registration withdrawal process, the foreign agent and the home agent release the mobile IP registration information.

The method according to claim 12, further comprising: the anchor authenticator/or anchor charging client notifying the authentication authorization accounting server terminal to exit the network, and the authentication authorization accounting server deleting The context information of the terminal.

The method according to claim 10 or 11, further comprising: after the terminal is retired, the anchor accessing the monthly service gateway sends a network return response message to the monthly service base station;

The base station returns a network revocation confirmation message to the anchor access service gateway.

The method according to claim 5, wherein after the terminal sends the deregistration request, the method further comprises: the serving base station replies to the registration command to the terminal.

17. The method according to claim 1, wherein the performing the network retreating comprises:

The monthly service base station sends a deregistration command carrying the network retreat indication to the terminal, and starts a network retirement timer;

When the timer expires, the base station initiates a message carrying the back-off indication to the anchor access service gateway to release the terminal-related data channel and the context.

18. The method according to claim 5 or 17, wherein the anchor service flow authority notifies the policy server terminal to exit the network, and the policy server deletes the context information of the terminal.

The method according to claim 18, wherein the policy server notifies the authentication and authorization accounting server to exit the network, and the authentication and authorization accounting server deletes the context information of the terminal.

The method according to claim 10 or 11, wherein the process of performing terminal-related data channel release comprises:

The serving base station sends a data channel release request to the service access network gateway to which it is connected, where the identifier of the terminal and the back-off indication are carried;

The service access network gateway forwards the received data channel release request to the anchor access service gateway;

The external agent in the anchor access service gateway releases the resource corresponding to the current terminal, and the response data channel release response is sent to the service access network gateway;

The serving access network gateway replies to the data channel release response to the serving base station.

The method according to claim 20, wherein the releasing the data channel associated with the terminal further comprises:

The serving base station replies with a data channel release confirmation message to the serving access network gateway; the serving access network gateway replies with a data channel release confirmation message to the anchor access service gateway.

22. The method according to claim 10 or 11, wherein said performing the final The process of releasing the associated data channel includes:

The anchor access service gateway sends a data channel release request message to the service access network gateway, where the identifier of the terminal and the network return indication are carried;

The serving access network gateway forwards the received data channel release request message to the serving base station; the serving base station replies with the data channel release response to the serving access network gateway; and the serving access network gateway forwards the data channel release response to the anchor Access service gateway;

The anchor access service gateway releases resources corresponding to the terminal.

The method according to claim 22, wherein the process of drying the data channel associated with the terminal further comprises:

The anchor access service gateway replies with a data channel release confirmation message to the service access network gateway;

The serving access network gateway replies to the data channel release acknowledgement message to the serving base station.

24. A mobile communication system, comprising: a terminal, a serving base station, and an anchor access service gateway, wherein:

The anchor access service gateway is configured to receive the message carrying the back-off indication, and perform terminal-related data channel and context release.

The mobile communication system according to claim 24, wherein the anchor access service gateway is further configured to send a back-off response message to the monthly service after receiving the message carrying the network-back indication Base station

The monthly service base station is further configured to: after receiving the network return response message, return a network return confirmation message to the anchor access service gateway.

The mobile communication system according to claim 24 or 25, further comprising: a service access network gateway connected to the serving base station and the anchor access service gateway, configured to: The sent message carrying the back-off indication is forwarded to the anchor access service gateway.

The mobile communication system according to claim 24 or 25, further comprising an external agent and a home agent for performing a mobile IP registration after receiving the mobile IP deregistration request of the anchor access service gateway. information.

The mobile communication system according to claim 24 or 25, further comprising: an anchor authenticator, an anchor service flow authenticator, and an anchor accounting client, configured to save context information of the terminal, And after receiving the network exit notification sent by the anchor access server, deleting the context information of the terminal.

The mobile communication system according to claim 27 or 28, further comprising: an authentication authorization charging server, configured to save context information of the terminal, and receive the authentication from the home agent and the anchor After the terminal retreat notification of the terminal or the anchor accounting client, the context information of the terminal is deleted.

The mobile communication system according to claim 24, further comprising: an IP address allocation entity, configured to allocate an IP address to the terminal, and release the terminal to be allocated when the terminal exits the network IP address.