WO2010069272A1 - Method and apparatus for processing the resources in a network handover - Google Patents

Abstract

A method and apparatus for processing the resources in a handover are provided by the embodiment of the present invention, wherein one method includes that: during a process of a user terminal accessing a target side network, it is obtained that the service of the user terminal is restricted or the resource establishment is failed in the target side network, and first indication information is transmitted to a source side network or a packet data network gateway. And the other method includes that: the mobility restrict information of the user terminal is obtained, according to the mobility restrict information of the user terminal and the related information of the target side network, it is obtained that the service of the user terminal is restricted in the target side network; the resources in the source side network of the user terminal is released. The corresponding processing apparatus is also provided by the embodiment of the present invention. By the method and apparatus provided by the embodiment of the present invention, during the network handover process, after obtaining that the service of the user terminal is restricted or the resource establishment is failed in the target side network, the process of releasing the bear resources related to the source side network is initiated initiatively, thus the waste of the bear resources of the source side network is reduced.

Description

 Resource processing method and device for network switching

 This application claims priority to Chinese Patent Application No. 200810190632. 3, entitled "Resource Processing Method and Device for Network Switching" on December 20, 2008 and March 31, 2009 Priority is claimed on Chinese Patent Application No. 200910141320, the entire disclosure of which is incorporated herein by reference. TECHNICAL FIELD The present invention relates to a resource processing method and apparatus, and more particularly to a resource processing method and apparatus for network switching, and belongs to the field of communication technologies. Background Art In the current wireless communication network architecture, there are 3GPP (3rd Generation Partnership Project) networks and non-3GPP networks, and the UE needs to switch between the 3GPP network and the non-3GPP network. Before the handover is complete, the network that carries the UE service is called the source-side network. After the handover is complete, the network that carries the User Equipment (UE) service is called the target-side network. Taking the UE from the 3GPP network (source side network) to the non-3GPP network (target side network) as an example, after the handover is performed, the service of the UE is guaranteed to be continuous. The specific process is as follows: The UE is successfully attached to the target side network, and the target side network creates the bearer resource for the UE, and the UE carries the wireless resource of the bearer resource on the Packet Data Network Gateway (PGW) of the source network. The access type is changed to the radio access type of the target side network. When the PGW finds that the radio access type of the bearer resource of the source network changes, the PGW initiates a resource release process on the source side network, thereby deleting the UE. Resources of the source side network.

 Regardless of whether the UE is handed over from the 3GPP network to the non-3GPP network or from the non-3GPP network to the 3GPP network, the handover needs to be completed by the successful attachment of the UE to the target side network, but the source side network (3GPP network or non-3GPP in the prior art) The network cannot know whether the UE is restricted on the target side network (non-3GPP network or 3GPP network), and it is impossible to know whether the UE successfully attaches on the target side network. Therefore, if the UE is limited in the target side network (for example, the UE cannot find a suitable cell camping), the target side network only allows the UE to perform emergency services on the target side network, and may not perform other packet data service (PS) services. . Therefore, the UE cannot release resources on the source side network. As a result, the bearer resources of the source side network are wasted.

The UE is handed over from the 3GPP network to the non-3GPP network, or the UE is handed over from the non-3GPP network to the 3GPP network. In the prior art, after the UE successfully creates all the resources of the target side network (non-3GPP network or 3GPP network), the PGW The release of the source side resource will be initiated. If the UE is in the 3GPP and non-3GPP network handover process, the network resources of the UE on the target side are not all successfully created due to the lack of resources or the limitation of the device capability (ie, the UE successfully creates a part of resources on the target side network, or the UE is in the target). All the resources of the side network failed to be created. At this time, the PGW cannot release the resources of the UE on the source side network. Therefore, the UE cannot be released on the source side network. This results in waste of source-side network resources. Summary of the invention

 The embodiment of the invention provides a resource processing method and device for network switching, so as to control release of a bearer resource of a source side network.

 The embodiment of the invention provides a resource processing method for network switching, which includes:

 In the process of the user terminal accessing the target side network, the target side network learns that the user terminal has limited service or resource creation failure on the target side network, and sends the first indication information to the source side network or the packet data network gateway. The first indication information carries indication information for releasing resources of the source side network of the user terminal.

 The embodiment of the invention further provides a resource processing method for network switching, which includes:

 Obtaining mobility restriction information of the user terminal;

 Obtaining that the service of the user terminal on the target side network is limited according to the mobility restriction information of the user terminal and the related information of the target side network;

 The resources of the source side network of the user terminal are released.

 The embodiment of the invention further provides a resource processing device for network switching, including:

 The first determining unit is configured to: when the user terminal accesses the target side network, learn that the user terminal has limited service or resource creation failure on the target side network;

 And a first sending unit, configured to send first indication information to the source network or the packet data network gateway, where the first indication information carries indication information for releasing resources of the source side network of the user terminal.

 The embodiment of the invention further provides a resource processing device for network switching, including:

 a second acquiring unit, configured to acquire mobility restriction information of the user terminal;

 a third determining unit, configured to learn, according to the mobility restriction information of the user terminal and the related information of the target side network, that the service of the user terminal on the target side network is restricted, and send a source including the release user terminal to the second processing unit An instruction for indicating information of a side network resource;

 The second processing unit is configured to release the source side network resource of the user terminal according to the instruction sent by the third determining unit.

The network processing resource processing method and device provided by the embodiment of the present invention actively initiates the release of the source side network phase after the user terminal is informed that the service of the target network is limited or the resource creation fails. The process of carrying the resources, thereby controlling the release of the bearer resources of the source side network.

 The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic structural diagram of a 3GPP wireless evolved network system according to an embodiment of the present invention;

 2 is a flowchart of a resource processing method for network switching according to Embodiment 1 of the present invention;

 3 is a flowchart of a resource processing method for network switching according to Embodiment 2 of the present invention;

 4 is a signaling flowchart of a resource processing method for network handover according to Embodiment 3 of the present invention;

 FIG. 5 is a signaling flowchart of a resource processing method for network handover according to Embodiment 4 of the present invention;

 6 is a signaling flowchart of a resource processing method for network handover according to Embodiment 5 of the present invention;

 FIG. 7 is a signaling flowchart of a resource processing method for network handover according to Embodiment 6 of the present invention;

 8 is a signaling flowchart of a resource processing method for network handover according to Embodiment 7 of the present invention;

 9 is a signaling flowchart of a resource processing method for network handover according to Embodiment 8 of the present invention;

 10 is a signaling flowchart of a resource processing method for network handover according to Embodiment 9 of the present invention; FIG. 11 is a signaling flowchart of a resource processing method for network handover according to Embodiment 10 of the present invention; A signaling flow chart of a resource processing method for network handover provided in Example 11. 1 is a schematic structural diagram of a 3GPP (3rd Generation Partnership Project) wireless evolved network system according to an embodiment of the present invention. As shown in FIG. 1 , an evolved UMTS (Universal Radio Communication System) Terrestrial Radio Access Network (E-UTRAN) is used to implement all functions related to the evolved network radio; mobility Management entity (Mobility Management Entity, 匪E), responsible for control plane mobility management, including user context and mobility state management, assigning user temporary identity, etc.; Serving Gateway (SGW) is a 3GPP access network. The user plane anchor is the interface that terminates the E-TURAN. The Packet Data Network Gateway (PGW) is the user plane anchor between the 3GPP access network and the non-3GPP access network. In the embodiment of the present invention, the PGW is regarded as an entity shared by the 3GPP network and the non-3GPP network; the Policy and Charging Rule Function (Policy and Charging Rule Function) , abbreviated as PCRF) for policy control decision and flow charging control function;

The Home Subscriber Server (HSS) is used to store user subscription information. Authentication, Authorization and Accounting Server (Authentication, Authorization and Accounting Server, Referred to as AAA), it is used to perform access authentication, authorization, and accounting functions for the UE. The home network server and the authentication, authorization, and accounting server belong to the function entity of the operator for user management. If the home network of the UE is a 3GPP network, the home network server and the authentication, authorization, and accounting server corresponding to the UE are 3GPP networks. Entity, if the home network of the UE is a non-3GPP network, the home network server and the authentication, authorization, and accounting server corresponding to the UE are entities of the non-3GPP network. There is no restriction on the network attribution of the home network server and the authentication, authorization and accounting server in the embodiment of the present invention.

 For non-3GPP networks, there are mainly non-3GPP organizations defined networks, such as Wireless Local Area Network (WLAN), Worldwide Interoperability for Microwave Access (WiMAX), and CDMA (code division). Multiple access) 2000 and other networks. In the CDMA2000 network, the entities accessing the network part are High Rate Packet Data (HRPD AN) and HSGW (High Speed Packet Data Service Gateway), where the HSGW is the mobile access gateway (Mobile Access). Gateway (MAG) is equivalent to the SGW in the 3GPP network. The HSGW establishes a tunnel with the PGW to complete service data forwarding. The Evolved Packet Data Gateway (ePDG) is an intermediate connection entity in which the non-trusted non-3GPP access network part is connected to the PGW, and the S2b interface is adopted between the ePDG and the PGW. The UE can also access the PGW or the SGW through the trusted non-3GPP access network, and the trusted non-3GPP access network is connected to the SGW or the PGW through the S2a interface. In the WiMAX network, the entity accessing the network part is the Access Service Network GW (ASN GW), and the ASN GW is connected to the PGW. The S2 interface is used, and the S2a or S2b depends on the carrier's trustedness. The non-3GPP access network is also a non-trusted non-3GPP access network.

 Embodiment 1

 2 is a flowchart of a resource processing method for network switching according to Embodiment 1 of the present invention. As shown in FIG. 2, the method includes:

 Step 10: In the process of the user terminal accessing the target side network, the target network side learns that the user terminal has limited service or resource creation failure on the target side network, and sends a first indication to the source side network or the packet data network gateway. information. The first indication information carries indication information for releasing resources of the source side network of the user terminal. The first indication information is indication information for releasing the source side network resource of the user terminal, where the first indication information may be a Detach indication message, and a resource (Detach for non-3GPP) indication message that is released in the non-3GPP network. The information may also be the information carried in the indication information indicating that the user terminal is restricted on the target side network, or the value of the resource creation failure reason, etc., and those skilled in the art should understand that in the process of transmitting the information, the specific bearer form will be The specific information bearing form is different in this embodiment.

After the discovery of the user terminal service is restricted or the target side network discovers that the resource of the user terminal fails to be created, the target side network may initiate the release of the source side network resource by sending an indication message, thereby serving the user. The terminal controls the release of the source side network resources when the target side network service is limited or the user terminal fails to create the target side network resource.

 After the first indication information is sent by the target side network, the source side network or the packet data network gateway can perform the following operations:

 Step 11: The source side network or the packet data network gateway receives the first indication information sent by the target side network. Step 12: Release resources of the source side network of the user terminal. This step can be specifically as follows:

 The resources related to the user terminal in the source side network are deleted, and the resources mainly refer to resources such as PDN connections established on the source side network entity.

 The information related to the user terminal in the HSS and the AAA is updated, and the information mainly refers to an access point name (access point name) and PGW information related to the PDN connection of the user terminal on the source side network.

 The resource information of the source side network in the user terminal is deleted, and the resource information in the user terminal is mainly used to carry resources of the source side network of the service.

 The source side network may be a 3GPP network and a non-3GPP network. Similarly, the target side network may also be a 3GPP network and a non-3GPP network.

 In this embodiment, the entity that specifically receives the source side network of the first indication message may be an entity responsible for access control, and may be an MME for the 3GPP network. For non-3GPP networks, it can be a non-3GPP gateway or HRPD AN. The network entity that specifically receives the first indication message may also be a packet data network gateway.

 Step 10 above may be based on the types of the source-side network and the target-side network. The following situations may exist:

1) The source side network is a non-3GPP network, and the target side network is a 3GPP network. Step 10 may be specifically: The MME learns that the user terminal has limited service on the 3GPP network in the process of accessing the 3GPP network of the user terminal, and adopts HSS and AAA. Sending the first indication information to the non-3GPP gateway. Or the MME sends the first indication information to the packet data network gateway (PGW) via the HSS and/or the AAA, or the MME sends the first indication information to the PGW via the serving gateway SGW, or the MME directly sends the first indication information to the PGW.

 2) The source side network is a 3GPP network, and the target side network is a non-3GPP network. Step 10 may be specifically: the non-3GPP gateway accesses the non-3GPP network in the process of accessing the non-3GPP network, and the user terminal is limited in service of the non-3GPP network. The HSS and the AAA send the first indication information to the MME. Or the non-3GPP gateway sends the first indication information to the packet data network gateway (PGW) via the HSS and/or the AAA, or the non-3GPP gateway sends the first indication information to the PGW via the SGW, or the non-3GPP gateway sends the first indication information to the PGW.

 3) The source side network is a non-3GPP network CDMA2000 network, and the target side network is a 3GPP network. Step 10 may be specifically: The MME learns that the user terminal is limited in service or resource creation on the 3GPP network in the process of the user terminal accessing the 3GPP network. Failure; the MME sends the first indication information to the HRPD AN.

4) The source side network is a 3GPP network, and the target side network is a non-3GPP network CDMA2000 network, step 10 The HRPD AN may be configured to notify the user terminal that the service of the non-3GPP network is limited or the resource creation fails in the process of the user terminal accessing the non-3GPP network. The HRPD AN sends the first indication information to the MME.

 For the case where the user terminal has an emergency service in the source side network, the step 10 may be specifically: when the user side accesses the target side network in the target side network, the user terminal is informed that the service of the user terminal is limited or the resource is created on the target side network. The user terminal has an emergency service in the source side network; the emergency service resource is created on the target side network, and the first indication information is sent to the source side network.

 The above step 10 may be as follows according to the types of the source side network and the target side network:

1) The source side network is a non-3GPP network, and the target side network is a 3GPP network. Step 10 may be specifically: The MME learns that the user terminal is limited in service or resource creation on the 3GPP network in the process of accessing the 3GPP network by the user terminal, and There is emergency service on the source side network;

 Create resources for emergency services of the 3GPP network;

 The MME sends the first indication information to the non-3GPP gateway, and the MME may send the first indication information to the non-3GPP gateway through the HSS and the AAA, or may send the first indication information to the non-3GPP gateway through the SGW and the PGW.

 In addition, the foregoing step 10 may further include: the MME indicates that the SGW and/or the PGW user terminal service is limited or the resource creation fails, so that when the PMIP protocol is adopted between the SGW and the PGW, the SGW does not perform non-emergency services. Data forwarding for resource creation and non-emergency services. When the GTP protocol is adopted between the SGW and the PGW, the PGW does not perform resource creation for non-emergency services and data forwarding for non-emergency services.

 2) The source side network is a 3GPP network, and the target side network is a non-3GPP network. Step 10 may be specifically: The non-3GPP gateway learns that the user terminal is limited in service or resources on the non-3GPP network in the process of the user terminal accessing the non-3GPP network. Creation fails, and there is emergency service on the source side network;

 Create resources for emergency services other than 3GPP networks;

 The non-3GPP gateway sends a first indication message to the MME. The non-3GPP gateway may first send the first indication message to the PGW, and the PGW forwards the information to the SGW, and the SGW sends the first indication information to the MME. The non-3GPP gateway may also send the first indication information to the MME by using the first indication information through the HSS and the AAA.

 In addition, the foregoing step 10 may further include: the MME indicates that the SGW and/or the PGW user terminal service is limited or the resource creation fails, so that the SGW and/or the PGW no longer perform resource creation and data forwarding of the non-emergency service. .

 3) The source side network is a CDMA2000 network that is not a 3GPP network, and the target side network is a 3GPP network. Step 10 may be specifically:

 In the process of the user terminal accessing the 3GPP network, the MME learns that the service of the user terminal is limited or the resource creation fails on the 3GPP network, and the emergency service exists on the source network.

Create resources for emergency services of the 3GPP network; The MME sends the first indication information to the HRPD AN.

 4) The source side network is a 3GPP network, and the target side network is a non-3GPP network CDMA2000 network. Step 10 may be specifically:

 In the process of the user terminal accessing the non-3GPP network, the HRPD AN learns that the user terminal has limited service or resource creation failure on the non-3GPP network, and there is an emergency service on the source side network;

 Create resources for emergency services other than 3GPP networks;

 The HRPD AN sends the first indication information to the MME.

 In this embodiment, during the handover process of the 3GPP network and the non-3GPP network, when the UE attaches on the target side network, if the entity of the target side network finds that the service for the UE is restricted, generating a first indication information, And sending to the entity of the source side network or the packet data network gateway, thereby notifying the source side network or the packet data network gateway to release the network resources established for the UE. This reduces the waste of resources in the source side network caused by the target side network in the case where the resources cannot be normally created in the prior art.

 Embodiment 2

 FIG. 3 is a flowchart of a resource processing method for network switching according to Embodiment 2 of the present invention. As shown in FIG. 3, the method includes:

 Step 20: Obtain mobility restriction information of the user terminal. Before the network handover, the source side network acquires the mobility restriction information of the user terminal from the AAA or the HSS. The mobility restriction information may be used by the HSS and the AAA to transmit the mobility restriction information as the subscription data to the entity of the source side network when the UE performs location registration on the source side network. The mobility restriction information specifically refers to the areas in which the user terminal is limited in service. In addition, it should be noted that, in the embodiment of the present invention, the HSS and the AAA may be separately configured, or may be integrally configured as HSS/AAA. Among them, AAA includes AAA Proxy (AAA Proxy Server) and attribution AAA Server (AAA Server) in the roaming scenario.

 Step 21: The source side network learns that the service of the user terminal on the target side network is limited according to the mobility restriction information of the user terminal and the related information of the target side network. The related information of the target side network may be obtained by using an attach request message in the process of performing network switching. The related information of the target side network may be type information of the target side network, location area information of the target side network to be accessed, and the like. The mobility restriction information refers to service restriction information of the user terminal in certain areas, such as the service restriction of the user terminal in a specific location area, or the service restriction of the user terminal in a specific access network (e-UTRAN or CDMA). And other relevant information. The target side network information refers to the target side network information such as the location area identifier of the target side network or the access network type of the target side network accessed by the source side in the handover process. If the mobility restriction information is location area related information, the target side network information is location area information; if the mobility restriction information is access network side information, the target side network identifier is information such as the access network type. Combining the two information source side networks can determine whether the UE is limited in the target measurement network service.

Step 22: Release resources of the source side network of the user terminal. The source side network may be a 3GPP network and a non-3GPP network. Similarly, the target side network may also be a 3GPP network and a non-3GPP network.

 In this embodiment, the entity that specifically knows that the service of the source-side network of the user terminal in the target-side network is restricted may be the entity responsible for access control, and may be the MME for the 3GPP network. For non-3GPP networks, it can be a non-3GPP gateway or HRPD AN.

 The foregoing step 22 may be specifically: deleting resources related to the user terminal in the source side network; updating information related to the user terminal in the HSS and the AAA; and deleting resource information of the source side network in the user terminal.

 The preferred application of this embodiment is in the scenario of optimizing handover. According to different types of the source side network and the target side network in the optimized handover scenario, the following may exist:

 1) When the source side network is a CDMA2000 network in a non-3GPP network, and the target side network is a 3GPP network:

 Step 20 may be specifically: the HRPD AN acquires mobility restriction information of the user terminal from the AAA;

 Step 21 may be specifically: After the HRPD AN receives the attach request message attached by the user terminal to the 3GPP network, the HRPD AN learns that the service of the user terminal on the target side network is limited according to the mobility restriction information.

 2) The target side network is a CDMA2000 network that is not a 3GPP network, and the source side network is a 3GPP network: Step 20 may be specifically: The MME acquires mobility restriction information of the mobile terminal from the HSS;

 Step 21 may be specifically: after the MME receives the attach request message attached to the CDMA2000 network by the user terminal, the MME learns that the service of the user terminal on the target side network is restricted according to the mobility restriction information.

 In this embodiment, before the network handover, the entity of the source side network knows the mobility restriction information of the UE in the target side network. In this way, when the entity of the source side network learns that the network handover occurs, according to the mobility restriction information, it can directly determine whether the UE has a limited service on the target network side. If the result of the judgment is that the service on the target network side is limited, the process of releasing the bearer resource can be directly initiated on the source side network. This reduces the waste of the bearer resources on the source side network caused by the target side network in the case that the bearer resources cannot be created normally in the prior art. In addition, compared with the first embodiment, the target side network is not required to transmit the instruction information dedicated to releasing the network resources.

 Embodiment 3

 FIG. 4 is a signaling flowchart of a resource processing method for network handover according to Embodiment 3 of the present invention. The scenario shown in Figure 4 is: The UE switches to the 3GPP network in the non-3GPP network; the UE does not have emergency services in the non-3GPP network. As shown in Figure 4, the following steps are included:

 Step 101: The UE performs a service on a non-3GPP network, where the emergency service is not included.

Step 102: The UE discovers the 3GPP network access, and initiates a handover procedure from the non-3GPP network to the 3GPP network. The handover procedure is implemented by the UE initiating a Handover Attach procedure. Step 103: The UE sends an attach request (Attach Request) message, where an Attach Type is indicated as a Handover Attach.

 Step 104: Perform an authentication process between the UE, the MME, and the HSS/AAA. In this process, the MME determines that the UE does not currently have emergency services and the UE is currently limited in the 3GPP network, so the MME does not allow the UE to access the 3GPP network. The MME obtains the APN and PGW information of the currently performed service from the HSS/AAA. If the APN itself is the APN of the emergency service, the MME can directly identify that the service related to the APN is an emergency service.

 Step 105: The MME sends a notification request (Notify Request) message to the HSS/AAA, where the message carries a resource (Detach for non-3GPP) indication information for releasing the non-3GPP network, where the information is used to notify the HSS to initiate in the non-3GPP network. The bearer resource release (Detach) process of the UE deletes the network resources of the UE in the non-3GPP network. In addition to adding a resource for releasing a non-3GPP network (Detach for non-3GPP) indication information in the message, the UE may also instruct the HSS/AAA to initiate the UE in the non-3GPP network with a separate Detach indication message. The bearer resource release (Detach) process deletes the network resources of the UE in the non-3GPP network.

 Step 106: After receiving the resource (Detach for non-3GPP) indication information sent by the MME, the HSS sends a Detach indication message to the AAA. If the UE roams in the non-3GPP network, the AAA server of the home station sends a Detach indication message to the AAA Proxy (AAA Proxy), and the AAA Proxy sends a Detach indication message to the non-3GPP gateway. Shown in the non-roaming scenario). The non-3GPP gateway herein may be a non-3GPP IP access gateway such as MAG, ePDG, ASN GW, or the like. The above Detach process is applicable to both S2a (an interface between a non-3GPP IP access gateway and a PGW) and S2b (an interface between an ePDG and a PGW).

 If the S2c (interface between the UE and the PGW) scenario is adopted, the AAA server (non-roaming scenario) or the AAA Proxy (roaming scenario) of the home location sends a Session Termination message to the PGW, and the PGW is notified to delete the UE. The associated PDN connection is not shown in Figure 5.

 Step 107: After receiving the Detach Indication message sent by the AAA Server or the AAA Proxy, the non-3GPP gateway sends a Proxy Binding Update message carrying the Lifetime =0 and the access point name (access point). The name, abbreviated as APN, and the user identifier, the message is used to instruct the PGW to delete the PDN connection associated with the UE.

Step 108: After receiving the Proxy Binding Update message, the PGW does not immediately delete the PDN connection related to the UE established on the PGW, but sends an Update PDN GW Address message to the home AAA Server or The AAA Proxy sends the AAA Server (in the roaming scenario) to the home AAA Server to indicate that the AAA Server at the home station deletes the APN and PGW information in the PDN connection associated with the UE. After the AAA Server at the home site performs the deletion operation, the HSS is notified. Perform the appropriate delete operation. Recorded in the HSS After the UE-related PDN connection is deleted, the registration process of the UE in the HSS is completed. After the deletion is complete, HSS/AAA notifies the PGW.

 Step 109: The PGW deletes the bearer session resource associated with the PDN connection, sends a Proxy Binding Ack message to the non-3GPP gateway, carries Lifetime=0 and the user identifier, and identifies that the PDG has completed the deletion of the PDN connection.

 Step 110: The non-3GPP gateway deletes the bearer resource of the UE in the non-3GPP network, and then sends a Detach Ack message to the HSS/AAA.

 Step 111: After receiving the Detach Ack, the HSS/AAA learns that the UE's bearer resources in the non-3GPP network are all deleted, and sends a message notification response (Notify Response) or a Detach Answer (Detach Ack) message to notify the MME of the UE. The bearer resource deletion in the non-3GPP network is completed.

 Step 112: After receiving the notification response (Notify Response) or the Detach Answer (Detach Ack) message, the MME sends an Attach Reject message to the UE, and notifies the UE that the attach request in the 3GPP network is rejected. Carrying resource deletion indication information or UE service restriction indication information or other indication information that may instruct the UE to delete the bearer resource of the non-3GPP network established by the UE. The UE deletes all bearer resources on the non-3GPP network through the indication information carried in the Attach Reject message. The indication information indicating that the UE deletes the network resource on the UE may be carried by the Attach Reject message, or may be indicated by other specific messages.

 The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example, If the establishment of one or more PDN connections fails, or the bearer creation fails, the MME learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failures). In this scenario, the MME may send the indication information for notifying the release of the non-3GPP network resource to the non-3GPP gateway by using the HSS and/or the AAA, and the non-3GPP gateway initiates the process of deleting the source side resource according to the indication information, where the process is, for example, De-attachment process, bearer release process, or PDN connection release process.

 In this embodiment, when the UE does not have emergency services in the non-3GPP network, when the UE is in the handover process of the non-3GPP network to the 3GPP network, although the UE fails to attach in the 3GPP network, but through the 3GPP network, The MME determines the Detach for non-3GPP indication information generated by the MME to initiate the bearer resource release process of the source side network, thereby reducing the situation that the 3GPP network cannot properly create the bearer resources. Waste of bearer resources on non-3GPP networks.

Embodiment 4 FIG. 5 is a signaling flowchart of a resource processing method for network handover according to Embodiment 4 of the present invention. The scenario shown in FIG. 5 is: The UE switches to the non-3GPP network in the 3GPP network; the UE does not have emergency services in the 3GPP network. As shown in Figure 5, the following steps are included:

 Step 201: The UE performs a service on the 3GPP network, where the emergency service is not included.

 Step 202: The UE discovers a non-3GPP network access, and initiates a handover procedure to the non-3GPP network.

 Step 203: The UE and the non-3GPP gateway and the HSS/AAA perform an authentication and authentication process. The APN and PGW addresses are obtained from HSS/AAA during this process. In the roaming scenario, the AAA Proxy obtains the APN and PGW pairs from the HSS through the AAA server at the home. The non-3GPP gateway judges that the current service of the UE is limited, and there is no emergency service, so the authentication and authentication fail. The non-3GPP gateway may be a non-3GPP IP access gateway or a gateway such as an ePDG or other MAG.

 Step 204: The non-3GPP gateway sends a separation indication message to the PGW, and the PGW sends a separation indication to the HSS/AAA (if the UE is in the roaming state, first sends the message to the AAA Proxy, and the AAA Proxy sends the message to the AAA server of the home station). Detach indication), the message carrying the resource for releasing the 3GPP network (Detach for 3GPP) indication information, the AAA server instructing the HSS to initiate the detach procedure of the 3GPP network, thereby deleting the network resource of the UE in the 3GPP network or the non-3GPP gateway The detachment indication message is directly sent to the AAA and the HSS, and the message carries the resource (Detach for 3GPP) indication information for releasing the 3GPP network.

 Step 205: The HSS/AAA sends a Detach indication message to the MME to instruct the MME to initiate a Detach process.

 Step 206: The MME initiates deletion of the bearer resource of the UE in the 3GPP network, and after the resource is deleted, the UE notifies the HSS/AAA. Step 207: The HSS/AAA sends a Detach Ack message to the PGW, and the PGW notifies the non-3GPP gateway that the UE is not deleted in the 3GPP network or the HSS/AAA sends a Detach Ack message to the non-3GPP gateway. Non-3GPP gateway.

 Step 208: The non-3GPP gateway sends a resource deletion indication message to the UE, where the message may carry the resource deletion indication information or the UE service restriction indication information or other network that may instruct the UE to delete the established 3GPP on the UE. Information about the resource.

The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example, If one or more PDN connections fail to be established, or the bearer creation fails, the non-3GPP gateway learns that the UE's resource creation fails (including all resource creation failures or some resource creation failures). In this scenario, the same non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the MME through the HSS and/or the AAA. Or the non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the MME to the PGW and/or the HSS and/or the AAA, The MME deletes the source side resource according to the indication information initiation process, and the process is, for example, a detachment process, a bearer release process, or a PDN connection release process. .

 In this embodiment, in the case that the UE does not have emergency services in the 3GPP network, when the UE is in the handover process of the 3GPP network to the non-3GPP network, although the UE fails to attach in the non-3GPP network, but through the non-3GPP network After determining that the service of the UE is limited, the non-3GPP gateway generates the Detach for non-3GPP indication information, and initiates a bearer resource release procedure of the source side network, thereby reducing the situation that the 3GPP network cannot properly create the bearer resource. Waste of hosted resources on non-3GPP networks.

 Embodiment 5

 FIG. 6 is a signaling flowchart of a resource processing method for network handover according to Embodiment 5 of the present invention. The scenario shown in Figure 6 is: The UE switches to the 3GPP network in the non-3GPP network, and the UE has emergency services in the non-3GPP network.

 As shown in Figure 6, the following steps are included:

 Step 301: The UE performs services on a non-3GPP network, including emergency services and non-emergency services.

 Step 302: The UE initiates a handover process from a non-3GPP handover to a 3GPP according to the detection of the 3GPP network access, where the handover procedure is implemented by the UE initiating a handover attach procedure. The following step 303, step 317, is the Handover Attach process.

 Step 303: The UE sends an attach request (Attach Request) message to the MME, where the message carries information such as an Attach Type and an emergency call indication information, and an Attach type is a Handover Attach, and the emergency call indication information indicates that the UE is in the non-contact. There are emergency services in the 3GPP network.

 Step 304: Perform an authentication process between the UE, the MME, and the HSS. Since the UE currently has an emergency service, although the UE is currently limited in 3GPP network services, the 3GPP network still allows UE access.

 Step 305: The MME sends an Update Location message to the HSS/AAA server, and registers the address information of the MME to the HSS.

 Step 306: The HSS/AAA sends an Update Location Ack message to the MME, where the message carries the BiSI and the subscription data, and the subscription information includes the subscription data of the PDN connection of the UE in the non-3GPP network, including multiple For APN and PGW addresses, APNs and PGWs related to emergency calls are also included.

Step 307: The MME sends a default bearer creation request (Create Default Bearer Request) message to the SGW, where the message carries the APN and PGW information related to the emergency service, and the SGW forwards the message to the PGW related to the emergency service. The default bearer resource of the emergency PDN connection is created according to the APN and PGW information related to the emergency service, and the PGW is notified by the process that the UE service is restricted. The message carries the APN and PGW information related to the emergency call, the radio access type (RAT), the handover indication information, the service restriction indication information, the SGW address, and the tunnel identification ID (TEID). . Where RAT The Type (RAT Type) information is used to indicate that the PDN connection is currently in the 3GPP network. The Handover Indication information is used to indicate the handover procedure that is currently a non-3GPP handover to 3GPP. The APN and PGW information represents the APN and PGW information associated with the emergency call. The SGW address and the TEID indicate that the SGW is the data downlink address and tunnel identifier created by the PGW for the bearer.

 The scenario shown in the figure is a case where the SGW and the PGW are in the GTP (GPRS Tunneling Protocol) protocol, and the SGW forwards the default bearer creation request message to the PGW, and the PGW learns that the current service of the UE is restricted according to the service restriction indication information. Therefore, the PGW cannot initiate non-emergency service resource creation and/or data forwarding. In addition, if the situation between the SGW and the PGW is a PMIP (Proxy Mobile IP) protocol (not shown in the figure), the SGW learns that the current service of the UE is restricted according to the service restriction indication information sent by the MME, and therefore, the SGW does not initiate. Non-emergency business resource creation and/or data forwarding. This embodiment is described by using the GTP protocol between the SGW and the PGW.

 After the UE leaves the service restricted area, the MME sends an Update Bearer Request message or other message to the SGW or the PGW, and the message carries the indication information of the normal service, indicating that the SGW or the PGW can forward the non-emergency service data and can Create non-emergency business resources.

 Step 308: The PGW determines that the handover process is currently performed according to the handover indication information, and obtains a PCC (Policy and Accounting) rule from the PCRF, and the PCRF sends the PCC rule related to the UE to the PGW. This step is optional. The PGW can also use the rules configured by itself to initiate the following bearer creation.

 Step 309: The PGW initiates a dedicated bearer creation of the default bearer and the emergency call according to the PCC rule acquired from the PCRF. The PGW obtains the service restriction indication information in step 307, so that the PGW does not initiate the resource bearer creation of other services. . This process creates a bearer between the UE and the eNodeB and between the SGW and the PGW.

 Step 310: The MME sends an Update Bearer Request (Update Bearer Request) message to the SGW, where the message carries the eNodeB address and the TEID and the handover indication information created by the eNodeB in step 309.

 Step 311: The SGW sends a bearer update request message to the PGW according to the handover indication information in the step 310. The message carries the handover indication information, and the PGW is notified that the default bearer and the dedicated bearer can ensure that the data packet is transferred from the non-3GPP to the 3GPP side.

Step 312, PGW sends a bearer update response SGW (Update Bearer Response) ₀

Step 313, SGW transmits a bearer update response to the MME (Update Bearer Response) ₀

 Step 314: The MME sends a notification request (Notify Request) message to the HSS/AAA, and the message carries the resource (Detach for non_3GPP) indication information for releasing the non-3GPP network, indicating that the HSS initiates the non- The Detach flow of the 3GPP network, thereby releasing the bearer resources of the UE in the non-3GPP network.

Step 315: The HSS/AAA sends a Notify Response message to the MME, and notifies the MME to initiate a Detach process of the non-3GPP network. Step 316: The MME returns an Attach Accept message to the UE, and carries the temporary identifier and the tracking area identifier and the service restriction indication information allocated by the 3GPP network to the UE. After receiving the indication information, the UE deletes the bearer resources of the non-3GPP network established in the UE. This information can also be sent by the MME to the UE through other messages.

 Steps 314, 315 and step 316 do not have a chronological order. Step 316 can also be performed after step 321 .

 Step 317: After receiving the resource (Detach for non-3GPP) indication information sent by the MME, the HSS sends a Detach indication to the AAA server. If the UE roams on the non-3GPP network, the home location The AAA server sends a Detach indication message to the AAA Proxy, and the AAA Proxy sends a Detach indication message to the non-3GPP gateway (not shown in the figure), where the non-3GPP gateway may be a MAG, ePDG and so on. The above Detach process is the scenario of S2a (the interface between non-3GPP IP access and PGW) and S2b (interface between ePDG and PGW). In the S2c (interface between the UE and the PGW) scenario, the AAA Server (non-roaming scenario) or the AAA Proxy (Roaming Scenario) sends a Session Termination message to the PGW, informing the PGW to delete the PDN connection associated with the UE. When the PGW deletes the PDN connection, the PGW releases the network resources of the UE established on the PGW in the non-3GPP network. The radio access type of the emergency service-related bearer resource is EUTRAN (Evolved UMTS (Universal Mobile Telecommunications System) terrestrial radio access network), so the bearer resources of the PDN connection of the emergency service on the 3GPP network do not follow the non-3GPP. The Detach process of the network is deleted. Through the Detach process, all resources of the UE in the non-3GPP network are deleted, including emergency service resources and non-emergency service resources.

 Step 318: After receiving the Detach indication message sent by the AAA server or the AAA Proxy, the non-3GPP gateway sends a Proxy Binding Update message to the PGW, where the message carries the Lifetime =0 and the APN. User ID, this message instructs the PGW to delete the PDN connection associated with the UE.

 Step 319: The PGW sends an Update PDN GW Address message to the home AAA server or the AAA proxy to the home AAA server, and the home AAA server deletes the APN and PGW information related to the PDN connection. The home AAA server notifies the HSS to update the data. After all the non-emergency related PDN connections are deleted, only the emergency service related APN and PGW pairs remain in the HSS.

 Step 320: The PGW deletes all the bearer sessions associated with the PDN connection, and sends a Proxy Binding Ack message to the non-3GPP gateway, where the message carries Lifetime=0 and the user identifier, and the message identifies the PGW. The associated PDN connection has been removed. After receiving the message, the non-3GPP gateway deletes all bearer resources of non-emergency services established in the non-3GPP network.

Step 321: The HSS updates the latest APN and PGW information to the MME by using an Insert Subscriber Data process, and the MME deletes all PDN connection information related to the non-emergency service. The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example, If the establishment of one or more PDN connections fails, or the bearer creation fails, the MME learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failures). In this scenario, the MME may send the indication information for notifying the release of the non-3GPP network resource to the non-3GPP gateway by using the HSS and/or the AAA, and the non-3GPP gateway initiates the process of deleting the source side resource according to the indication information, where the process is, for example, De-attachment process, bearer release process, or PDN connection release process.

 The difference from the fourth embodiment and the fifth embodiment is that, since the UE has an emergency service on the non-3GPP network, after the handover, although the non-emergency service is restricted, the 3GPP network still needs to create related resources of the emergency service. The non-3GPP network is also notified to release the bearer resources of the non-emergency service by sending an indication. In this way, the normal establishment of the emergency service is ensured, and the bearer resources related to the non-emergency service of the UE in the non-3GPP network are released in time, thereby reducing the waste of the bearer resources in the non-3GPP network.

 Embodiment 6

 FIG. 7 is a signaling flowchart of a resource processing method for network handover according to Embodiment 6 of the present invention. The scenario shown in Figure 7 is: The UE switches to the 3GPP network in the non-3GPP network, and the UE has emergency services in the non-3GPP network.

 As shown in FIG. 7, the steps 401 to 413 of the embodiment are the same as the steps 301 to 313 of the fifth embodiment, and details are not described herein again.

 Step 414: After the emergency service resource is created, the MME sends an Attach Accept message to the UE.

Step 415: The PGW sends a Detach Indication message to the non-3GPP gateway according to the UE service restriction indication information obtained in step 407 (ie, step 307 in the sixth embodiment), where the message carries the resource for releasing the non-3GPP network. The indication information of the Detach for _n0 n-3GPP), by which the non-3GPP gateway can initiate the resource release procedure of the UE in the non-3GPP network. This step can also be performed after step 411 or step 412.

 Step 416 - Step 418, which is the same as Step 318 - Step 320 in Embodiment 6.

 Step 419: After the UE is completely released from the bearer resources of the non-3GPP network, the non-3GPP gateway sends a Detach Ack message to the PGW to notify the PGW UE that the resources in the non-3GPP are all released.

Step 420: The HSS/AAA and the MME directly execute the process of inserting the subscription data (Insert Subscriber Data), and the latest APN and PGW information is sent to the MME by the HSS/AAA, and the MME updates the APN and PGW information on the MME. Step 421: After receiving the APN and PGW update information sent by the HSS/AAA, the MME sends a release resource (Release Resource) message to the UE, where the message carries the indication information for releasing the non-3GPP resource release, and the UE receives the After the information, all bearer resources in the non-3GPP network established on the UE are released.

 The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example, If the establishment of one or more PDN connections fails, or the bearer creation fails, the MME learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failures). In this scenario, the MME sends indication information for notifying the release of the non-3GPP network resource to the PGW, and the PGW initiates the resource allocation deactivation process according to the indication information to delete the source side resource.

 The difference between this embodiment and the sixth embodiment is that, in the sixth embodiment, the MME first sends a Notify Request message to the HSS/AAA server, informing the HSS to initiate a Detach process of the non-3GPP network (step 314), and then by the HSS. The /AAA server sends a separation indication message to the non-3GPP gateway. In this embodiment, in step 407 (ie, step 307 in the sixth embodiment), the PGW receives a default bearer creation request (Create Default Bearer Request) message, where the message carries the service restriction indication information; 412 (ie, step 312 of the sixth embodiment), the PGW sends a bearer update response to the SGW, indicating that the PGW completes the emergency service resource creation; then in step 415, the PGW directly sends the separation indication information to the non-3GPP gateway, non-3GPP. The gateway initiates a resource release procedure in the non-3GPP network according to the separation indication information. With the technical solution of the embodiment, the normal establishment of the emergency service is ensured, and the bearer resources related to the non-emergency service of the UE in the non-3GPP network are released in time, thereby reducing the waste of the bearer resources in the non-3GPP network.

 The scenarios in the foregoing sixth embodiment and the seventh embodiment are all processing procedures for the UE to switch from the non-3GPP network to the 3GPP network. A similar technical solution can be adopted for the UE to switch from the 3GPP network to the non-3GPP network. That is, when the UE accesses the non-3GPP network, the PGW receives the Proxy Binding Update message, and the message carries the service restriction indication information. The PGW sends a binding update update response to the non-3GPP gateway, indicating that the PGW has completed the establishment of the emergency service resource; the PGW then sends the separation indication information to the MME of the 3GPP network through the SGW, and the MME initiates the resource in the 3GPP network according to the separation indication information. Release the process.

 Example 7

 FIG. 8 is a signaling flowchart of a resource processing method for network handover according to Embodiment 7 of the present invention. The scenario shown in FIG. 8 is: The UE switches to the 3GPP network in the non-3GPP network (the HRPD network in this embodiment) (optimizes the handover procedure), and the UE has emergency services in the non-3GPP network.

As shown in Figure 8, the following steps are included: Step 501: The UE performs a service on the HRPD network, where the emergency service is included.

 Step 502: The UE discovers the 3GPP network coverage, and initiates a handover process to the 3GPP network.

 Step 503: The UE sends a Message X (X message) to the HRPD AN, where the message includes an Attach Request message to be sent to the MME, where the Attach Request message includes emergency service indication information, and identifies that the UE currently has an emergency service.

 Step 504: The HRPD AN forwards the Message X directly to 匪 E.

 Step 505: The MME and the HSS authenticate the UE through the HRPD AN. Although the UE has limited service in the 3GPP network, the UE authenticates the UE by using the emergency service in the HRPD network.

 Step 506: Perform a process of updating the location and obtaining the subscription data between the MME and the HSS/AAA, register the MME address in the HSS, and download the subscription data of the UE and all the PDN connection data, including the emergency service related APN, from the HSS. And PGW address information.

 Step 507: The MME sends a default bearer creation request message to the SGW and the PGW, and the PGW sends a dedicated resource creation request message to the PCRF. Because the current non-emergency service of the UE is restricted, the MME initiates an emergency service-related PDN connection establishment, and sends an emergency service-related default bearer creation request message to the SGW and the PGW. At the same time, the MME notifies the SGW and the PGW of the service restriction indication information in the default bearer creation request message, and informs the SGW and the PGW that the current service of the UE is limited. Except for the emergency service, the dedicated bearer creation and/or data forwarding of other services are prohibited. The PGW obtains the PCC rule from the PCRF by sending a dedicated resource creation request message to the PCRF, and initiates an emergency call dedicated bearer creation, and changes the RAT of the bearer related to the emergency call on the PGW.

 Step 508: The MME directly forwards the message to the HRPD AN, where the directly forwarded message includes an Attach Accept message and a bearer setup request message. The Attach Accept message carries the UE service restriction indication information, and is used to notify the UE to delete. Bearer resources related to non-emergency services. This information may also be sent directly to the UE by the MME through separate messages or other messages.

 If the UE is handed over from the 3GPP network to the service restricted area of the HRPD network, the HRPD AN also needs to notify the UE to delete the network resources of the 3GPP network. The specific manner of notifying the UE may be included in the message format and the message described in this step. Information.

 Step 509: The HRPD AN sends the foregoing information to the UE by using a Message X message.

 Step 510: The UE switches to the 3GPP network, and performs a process of creating a dedicated bearer creation of the radio bearer and the emergency service.

 Step 511: The MME sends a bearer update request message to the SGW.

 Step 512: After completing the bearer update, the MME sends a bearer update response message to the SGW to notify the SGW that the resource establishment is completed, and data forwarding can be performed.

Step 513: The MME sends a handover completion (HO Complete) message to the HRPD AN, and the message carries the release non. The resources of the 3GPP network (Detach for non-3GPP) indicate information.

 If the UE is handed over from the 3GPP network to the service restricted area of the HRPD network, the HRPD AN may also notify the MME to initiate a resource release procedure of the UE in the 3GPP network in the HO Complete message, and the HO Complete message carries Detach for 3GPP. The MME initiates a Detach procedure in the 3GPP network, and the resources of the UE in the 3GPP network are all released.

 Step 514: The HRPD AN initiates a Detach process, and causes the HSGW to initiate a resource release procedure to delete the network resources of the UE on the PHD network in the HRPD network, and the PGW updates the PDN connection subscription data in the AAA server, that is, only the PDN connection related to the emergency service remains. Signing data. The AAA sends the updated PDN subscription data to the HSS, and the HSS sends an Insert Subscriber Data message to notify the MME to update the PDN subscription data and delete the PDN subscription data related to the non-emergency call.

 The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE is switched from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example, If the PDN connection fails to be established, or the bearer creation fails, the MME learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failure). In this scenario, the MME may also instruct the HRPD AN to initiate release of non-3GPP network resources, such as a detach process, a bearer release process, or a PDN connection release process.

 In this embodiment, when the UE has an emergency service in the HRPD network, when the UE is in the process of handover of the HRPD network to the 3GPP network, the related bearer resources of the emergency service are successfully created, and the default bearer is created and emergency. After the service-related dedicated bearer is created, the MME instructs the HRPD AN to initiate bearer resources of the HRPD network that are not related to the emergency service. Therefore, the waste of the bearer resources on the non-3GPP network caused by the 3GPP network failing to create the bearer resources is reduced.

 Example eight

 FIG. 9 is a signaling flowchart of a resource processing method for network handover according to Embodiment 8 of the present invention. The scenario shown in FIG. 9 is: the UE switches to the 3GPP network in the non-3GPP network (the HRPD network in this embodiment) (optimizes the handover process), the UE does not have emergency services in the non-3GPP network, and in this embodiment, the HRPD The AN obtains the mobility restriction information of the UE in the 3GPP network in advance.

 As shown in Figure 9, the following steps are included:

 Step 601: The UE performs a service on the HRPD network, and does not include an emergency service.

 Step 602: The UE discovers the 3GPP network coverage, and initiates a handover process to the 3GPP network.

Step 603: The UE sends a Message X to the HRPD AN, where the message includes an Attach Request message that needs to be sent to the MME. Step 604: The HRPD AN determines that the UE is limited in the 3GPP network according to the mobility restriction information of the UE and the 3GPP network information, and sends a resource release command (Resource Release Command) message to the UE, indicating the UE. A bearer resource release procedure of a 3GPP network related to the UE is initiated.

 Step 605: The UE initiates a resource release procedure, and releases the bearer resource of the 3GPP network related to the UE. In this embodiment, the mobility restriction information is stored in the HSS as subscription data. When the UE registers in the HRPD network, the HSS/AAA (AAA Proxy in the case of roaming) may use the mobility restriction information of the UE as a subscription. The data is sent to the HRPD AN. In this way, when the HRPD AN receives the attach request sent by the UE, it can determine whether the service of the UE in the 3GPP network is restricted according to the mobility restriction information and the target side network information (3GPP network information) acquired in the handover process. If restricted, the resource release command message is sent to the UE, indicating the UE network resource.

 In addition, the resource release procedure may be directly initiated by the HRPD AN to release the bearer resources of the UE-related HRPD network. After the resources on the network side are released, the HRPD AN notifies the UE to delete all related resources on the UE by using a separate new message or an existing message carrying service restriction indication information.

 The foregoing steps in this embodiment are a handover process when the UE switches from the HRPD network to the 3GPP network. If the UE switches from the 3GPP network to the HRPD network, the MME may perform the handover according to the mobility restriction information acquired from the HSS. It is determined that the UE is limited in the HRPD network service, so that the MME can also directly send a resource release command message to the UE, where the message carries the service restriction indication information, and indicates that the UE initiates the Detach process to release the network resources of the UE in the 3GPP network; or directly by the MME. The Detach process is initiated to release the bearer resources of the 3GPP network. After the MME sends the service restriction indication information to the UE to delete the resources on the UE.

 In this embodiment, the HRPD AN obtains the mobility restriction information of the UE on the 3GPP network side and the target side network information acquired during the handover process before the handover occurs, and the HRPD AN can directly determine the UE during the handover process. In the restricted case in the 3GPP network, the resource release procedure is initiated directly without the need for the entity of the 3GPP network to indicate. In this way, the waste of the bearer resources on the non-3GPP network caused by the 3GPP network failing to create the bearer resources is also reduced.

 Example nine

 FIG. 10 is a signaling flowchart of a resource processing method for network handover according to Embodiment 9 of the present invention. The scenario shown in FIG. 10 is: The UE switches to the non-3GPP network in the 3GPP network, and the UE has emergency services in the non-3GPP network.

 As shown in Figure 10, the following steps are included:

 Step 701: The UE performs a service on the 3GPP network, where the emergency service is included.

 Step 702: The UE discovers non-3GPP network coverage, and initiates handover to a non-3GPP network.

Step 703: The UE and the non-3GPP gateway and the HSS/AAA perform authentication and authentication. In this process, the non-3GPP gateway acquires the APN and the PGW address from the HSS/AAA. In the roaming scenario, the non-3GPP gateway obtains the APN and PGW pairs from the home AAA server through the AAA Proxy. Since it contains emergency services related APN and PGW, The non-3GPP gateway judges that although the current service of the UE is limited, since there is an emergency service, authentication and authentication are passed. The non-3GPP gateway may be a non-3GPP IP access gateway or other gateway such as ePDG or MAG.

 Step 704: The UE sends an Attach Trigger message to the non-3GPP gateway.

 Step 705: The non-3GPP gateway sends a Proxy Binding Update message to the PGW for the emergency call related PDN connection, where the message carries the UE identifier and the emergency service related APN and PGW information and access technology type (Access Technology Type) , referred to as ATT) value and Lifetime. Lifetime identifies the PMIP tunnel lifetime. The ATT value indicates that the PDN connection is already an access connection to a non-3GPP network. In addition to the above information, a service restriction indication information is carried, indicating that the PGW is not allowed to forward non-emergency service data.

 After the UE leaves the service restricted area, the non-3GPP gateway sends a Proxy Binding Update message or other message to the PGW, and the message carries the normal service indication information, indicating that the PGW can forward the non-emergency service data.

 Step 706: The PGW sends a Proxy Binding Ack message to the non-3GPP gateway. Step 707: The non-3GPP gateway sends an Attach Completion message to the UE.

 The message may also carry service restriction indication information or other indication information to instruct the UE to delete non-emergency service resources. This information can also be sent via a separate message. If the carrying service restriction indication information is sent to the UE in this step, the following step 712 can be omitted. In addition, step 707 and step 708 have no sequential relationship.

 Step 708: The non-3GPP gateway sends a separation indication message to the PGW, and the PGW sends the separation indication message to the HSS/AAA (the PGW first sends the AAA to the AAA, and the AAA sends the separation indication information to the HSS). The message carries the resources for releasing the 3GPP network (Detach). For 3GPP) indication information. The AAA server instructs the HSS to initiate the de-attachment process of the 3GPP network to release the bearer resources of the UE on the source side network or the non-3GPP gateway to send the separation indication message to the AAA and the HSS, where the message carries the resource (Detach for 3GPP) indication information for releasing the 3GPP network.

 Step 709: The HSS/AAA server sends a separation indication message to the MME.

 Step 710: The MME initiates a Detach process. The MME releases all resources in the 3GPP network. Emergency Services Related PDN connections to network resources on non-3GPP networks are not released because ATT is no longer EUTRAN. After the resource release is completed, the MME instructs the HSS to update the APN and PGW information associated with the UE.

 Step 711: The process of inserting the subscription data is performed between the HSS/AAA and the PGW. After the PDN subscription data in the HSS is changed, the subscription data in the AAA is updated, the AAA will update the information to the PGW, and the PGW updates the information to the non-3GPP gateway; or the HSS/AAA directly updates the information to the non-3GPP gateway.

 Step 712: The non-3GPP gateway sends a resource deletion indication (Resource Delete Indication) message to the UE, where the message carries the service restriction indication information or other indication information, and informs the UE to delete all the bearer resources in the 3GPP network established on the UE.

The method for deleting the source side resource can be applied to the above scenario (that is, the UE cuts from the source side where the service is not restricted). Switching to the target side where the service is restricted, optionally, the UE is performing emergency services. The method is also applicable to the scenario where the UE switches from the non-service-restricted source side to the non-service-restricted target side. Optionally, The resource creation failure of the UE in the target side network (including all resource creation failures or part of resource creation failures), for example, one or more PDN connection establishment failures, or bearer creation failure, the MME learns that the UE's resource creation fails (including all Resource creation failed or some resources failed to be created). In this scenario, the same non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the MME through the HSS and/or the AAA. Or the non-3GPP gateway may send the indication information for notifying the release of the 3GPP network resource to the MME to the PGW and/or the HSS/AAA, and the MME initiates the resource allocation deactivation process to delete the source side resource according to the indication information, where the process is, for example, detached. Process, bearer release process, or PDN connection release process.

 In this embodiment, the UE has an emergency service in the 3GPP network. In the process of handover to the non-3GPP network, the non-3GPP gateway normally establishes an associated bearer of the emergency service after receiving the attach request from the UE. The non-3GPP gateway determines that the UE is limited in service in the non-3GPP network, and the non-3GPP gateway instructs the MME to initiate the release of the relevant bearer resources of the UE in the 3GPP network through the HSS. In this way, the normal establishment of the emergency service is ensured, and the bearer resources related to the non-emergency service of the UE in the 3GPP network are released in time, thereby reducing the waste of the bearer resources in the 3GPP network.

 Example ten

 FIG. 11 is a signaling flowchart of a resource processing method for network handover according to Embodiment 10 of the present invention. The scenario shown in Figure 11 is: The UE switches to the 3GPP network with a service-limited non-3GPP network.

 As shown in Figure 11, the following steps are included:

 Step 801: The UE performs a service on a 3GPP network, and optionally includes an emergency service.

 Step 802: The UE moves to the non-3GPP network coverage, and initiates a handover procedure to the non-3GPP network.

 Step 803: The UE and the non-3GPP gateway and the HSS/AAA perform authentication and authentication. In this process, the non-3GPP gateway obtains the APN and PGW addresses from the HSS/AAA. In the roaming scenario, the non-3GPP gateway obtains the APN and PGW pairs from the AAA server at the home through the AAA Proxy. Optionally, the APN and the PGW related to the emergency service are included, and the non-3GPP gateway determines that the current service of the UE is limited. If there is an emergency service, the authentication and the authentication may pass. The non-3GPP gateway may be a non-3GPP IP access gateway (such as ePDG or a gateway such as an MAG or an HSGW). The limited service in the present invention means that the UE is in a limited service mode, for example, the UE cannot find a suitable one. The community is stationed.

 If the UE does not have emergency services on the original 3GPP network, step 804 - step 807 is omitted.

 Step 804: The UE sends an Attach Trigger message to the non-3GPP gateway.

Step 805, the step is optional. The non-3GPP gateway sends a Proxy Binding Update message to the PGW for the emergency call related PDN connection, optionally carrying a service restriction indication information, indicating that the PGW may not forward non-emergency service data, and may not perform non-emergency service resources. Create and modify. After the UE leaves the service restricted area, the non-3GPP gateway sends a Proxy Binding Update message or other message to the PGW, and the message carries the normal service indication information, indicating that the PGW can forward the non-emergency service data.

 Step 806: The PGW sends a Proxy Binding Ack message to the non-3GPP gateway. Step 807: The non-3GPP gateway sends an Attach Completion message to the UE.

 Optionally, the message may carry the service restriction indication information or other indication information to instruct the UE to delete the non-emergency service resource. This information can also be sent via a separate message. In addition, step 807 and step 808 have no sequential relationship.

 Step 808: The non-3GPP gateway sends a separation indication message to the HSS and/or the AAA, where the message is used to indicate that the HSS and/or the AAA initiate source-side resource release, and the present invention does not impose any restrictions on the message name. The message carries the indication information for notifying the release of the 3GPP network resource, and the indication information may be an Access Restricted, a Source Release indication, or a message for releasing the source side resource. The present invention does not impose any limitation on the indication information.

 Step 809: The HSS and/or the AAA send a separation indication message to the PGW. The message carries indication information (ie, the first indication information of the present invention) for notifying the release of the 3GPP network resource. The indication information is as described in step 808.

 Step 810: The PGW initiates a resource allocation deactivation process, and releases resources of the UE in the 3GPP network.

 The non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the PGW through the HSS and/or AAA in the manner of the above steps 808-809. Or the non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the SGW and/or the PGW, and the PGW initiates the resource allocation deactivation process according to the indication information to delete the source side resource. The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target-side scenario. Optionally, the UE fails to create resources on the target-side network (including all resource creation failures or part of resource creation failures), for example. The establishment of one or more PDN connections fails, or the bearer creation fails. The non-3GPP gateway learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failures). In this scenario, the same non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the PGW through the HSS and/or AAA in the manner of the foregoing steps 808-809. Or the non-3GPP gateway may send indication information for notifying the release of the 3GPP network resource to the SGW and/or the PGW, and the PGW initiates the resource allocation deactivation process according to the indication information to delete the source side network resource.

 Example ^ ^ one

FIG. 12 is a signaling flowchart of a resource processing method for network handover according to Embodiment 11 of the present invention. The scenario shown in FIG. 12 is: The UE switches to the 3GPP network with limited service in the non-3GPP network. As shown in Figure 12, the following steps are included:

 Step 901: The UE performs a service on a non-3GPP network, and optionally includes an emergency service.

 Step 902: The UE moves to the 3GPP network coverage, and initiates a handover procedure from the non-3GPP handover to the 3GPP. Step 903: The UE sends an attach request (Attach Request) message to the MME.

 Step 904: Perform an authentication process between the UE, the MME, and the HSS. Optionally, if the UE currently has an emergency service, the 3GPP network still allows the UE to access although the UE is currently limited in 3GPP network services. If the UE does not currently have emergency services, step 905 - step 914 is omitted. The limitation of service in the present invention means that the UE is in the restricted service mode Limited Service Mode, for example, the UE cannot find a suitable cell camping.

 Step 905: The MME sends an Update Location message to the HSS/AAA server, and registers the address information of the MME to the HSS.

 Step 906: The HSS/AAA sends an Update Location Ack message to the MME, where the message carries the BiSI and the subscription data, and the subscription information includes the subscription data of the PDN connection of the UE in the non-3GPP network, including multiple For APN and PGW addresses, optional APNs and PGWs containing emergency calls are also included.

 Step 907: The MME sends a default bearer creation request (Create Default Bearer Request) message to the SGW, where the message carries the APN and PGW information related to the emergency service, and the SGW forwards the message to the PGW related to the emergency service. The default bearer resource of the emergency PDN connection is created according to the APN and the PGW information related to the emergency service. Optionally, the carrying indication information is used to notify the PGW that the UE service is restricted.

 The scenario shown in the figure is a case where the SGW and the PGW are in the GTP (GPRS Tunneling Protocol) protocol, and the SGW forwards the default bearer creation request message to the PGW, and the PGW learns that the current service of the UE is restricted according to the service restriction indication information. Therefore, the PGW cannot initiate non-emergency service resource creation and/or data forwarding. In addition, if the scenario between the SGW and the PGW is a PMIP (Proxy Mobile IP) protocol (not shown in the figure), the SGW learns that the current service of the UE is restricted according to the indication information sent by the MME for informing the SGW that the UE is limited in service. Therefore, the SGW does not initiate non-emergency service resource creation and/or data forwarding. This embodiment is described by using the GTP protocol between the SGW and the PGW.

 After the UE leaves the service restricted area, the MME sends an Update Bearer Request message or other message to the SGW or the PGW, and the message carries the indication information of the normal service, indicating that the SGW or the PGW can forward the non-emergency service data and can Create non-emergency business resources.

 Step 908: The PGW determines that the handover process is currently performed according to the handover indication information, and obtains a PCC (Policy and Accounting) rule from the PCRF, and the PCRF sends the PCC rule related to the UE to the PGW. This step is optional. The PGW can also use the rules configured by itself to initiate the following bearer creation.

Step 909: The PGW initiates the creation of a dedicated bearer of the default bearer and the emergency call according to the PCC rule obtained from the PCRF. Optionally, the PGW does not cause the PGW according to the indication information of the UE service restriction obtained in step 907. Initiate resource bearer creation or data forwarding for other services. This process creates a bearer between the UE and the eNodeB and between the SGW and the PGW.

 Step 910: The MME sends a Update Bearer Request message to the SGW.

 Step 911: The SGW sends a bearer update request message to the PGW according to the handover indication information in the step 910. The message carries the handover indication information, and the PGW is notified that the default bearer and the dedicated bearer can ensure that the data packet is transferred from the non-3GPP to the 3GPP side.

Step 912, PGW sends a bearer update response SGW (Update Bearer Response) ₀

Step 913, SGW transmits a bearer update response to the MME (Update Bearer Response) ₀

 Step 914: After the emergency service resource is created, the MME sends an Attach Accept message to the UE.

 Step 915: The MME sends a separation indication message to the HSS and/or the AAA, where the message is used to indicate that the HSS and/or the AAA initiate source-side resource release, and the present invention does not impose any restrictions on the message name. The message carries indication information indicating that the non-3GPP network resource is released (that is, the first indication information of the present invention), and the indication information may be an Access Restricted, a Resource Release indication, or used for notification. The message released by the source side resource. The present invention does not impose any restrictions on the indication information.

 Step 916, the HSS, and/or the AAA send a separation indication message to the PGW. The message carries indication information for notifying the release of non-3GPP network resources. The indication information is the same as step 915.

 Step 917: The PGW initiates a resource allocation deactivation process, and releases resources of the UE in the non-3GPP network.

 The MME may send indication information indicating that the non-3GPP network resources are released to the PGW via the HSS and/or AAA in the manner of the foregoing steps 915 to 916. Or the MME may send indication information indicating that the non-3GPP network resource is released to the SGW and/or the PGW, and the PGW initiates the resource allocation deactivation process to delete the source side resource. The method for deleting the source side resource can be applied to the above scenario (that is, the UE switches from the non-service-restricted source side to the service-restricted target side, and optionally, the UE is performing emergency services), and the method is also applicable to The UE switches from the non-service-restricted source side to the non-service-restricted target side scenario. Optionally, the UE fails to create resources on the target side network (including all resource creation failures or part of resource creation failures), for example. If the establishment of one or more PDN connections fails, or the bearer creation fails, the MME learns that the resource creation of the UE fails (including all resource creation failures or part of resource creation failures). In this scenario, the same MME may send indication information indicating that the non-3GPP network resources are released to the PGW via the HSS and/or AAA in the manner of step 915 to step 916 described above. Or the MME may send indication information indicating that the non-3GPP network resource is released to the SGW and/or the PGW, and the PGW initiates the resource allocation deactivation process to delete the source side network resource.

 Example twelve

The resource processing apparatus for network handover provided by Embodiment 12 of the present invention includes a first determining unit and a first sending Unit. The first determining unit is configured to: when the user terminal accesses the target side network, learn that the service of the user terminal on the target side network is limited or that the resource creation of the user terminal on the target side network fails; the first sending unit, The first indication information is sent to the source side network or the packet data network gateway, where the first indication information carries indication information for releasing resources of the source side network of the user terminal.

 In addition, the processing apparatus of this embodiment may further include: a first notification unit, configured to notify the user that the terminal service is limited or the resource creation fails, and the user terminal deletes the resource information of the source side network stored by the user terminal.

 The processing device of this embodiment may further include: a second determining unit, configured to: when the user terminal accesses the target side network, knowing that the user terminal has an emergency service in the source side network; Create resources for emergency services. Through the second judging unit and the first processing unit, the completion of the service in the target network is restricted, and the corresponding emergency service is established.

 The processing device of this embodiment may further include: a first acquiring unit, configured to acquire an emergency service-related access point name and packet data network gateway information in a process of the user terminal accessing the target network, and send the information to the a first processing unit, where the first processing unit initiates creation of the resource of the emergency service according to the access point name and the packet data network gateway information.

 The processing device of this embodiment may be disposed on a network entity responsible for access control of the target side network, for example, a network element such as an MME or a non-3GPP gateway.

 With the processing device of this embodiment, during the handover, when the UE is limited to the target side network, the UE can release the bearer resources of the source network in time by receiving the first indication information sent by the target side network, which is reduced. The resources of the source side network are wasted.

 Example thirteen

 The network processing resource processing apparatus provided in Embodiment 11 of the present invention includes a second obtaining unit, a third determining unit, and a second processing unit. The second obtaining unit is configured to acquire the mobility restriction information of the user terminal, and the third determining unit is configured to learn, according to the mobility restriction information of the user terminal and the related information of the target side network, that the user terminal is in the target side network. The service is limited, and sends an instruction to the second processing unit to release the indication information of the source side network resource of the user terminal. The second processing unit releases the source side network resource of the user terminal according to the instruction issued by the third determining unit. . The second obtaining unit may be specifically configured to acquire mobility restriction information of the user terminal from the authentication, authorization, and accounting server or the home network server before the network switching.

 In addition, the processing apparatus provided in Embodiment 13 of the present invention may further include: a third acquiring unit, configured to acquire related information of the target side network by using an attach request message in a process of performing network switching.

The processing device of this embodiment may be located on an entity that controls access control in the source side network, such as HRPD AN. With the processing device of this embodiment, in the process of performing the handover, the UE is determined to be restricted by the target side network on the entity of the source side network, and if it is restricted, the bearer resource of the source side network is released, and the source side is reduced. network The resources of the network are wasted.

 It should be noted that the above embodiments are only intended to illustrate the technical solutions of the present invention and are not to be construed as limiting the embodiments of the present invention. The technical solutions of the present invention may be modified or equivalently substituted, and the modified technical solutions may not deviate from the spirit and scope of the technical solutions of the present invention.

Claims

Rights request A resource processing method for network switching, which is characterized in that:  In the process of the user terminal accessing the target side network, the target side network learns that the user terminal has limited service or resource creation failure on the target side network, and sends the first indication information to the source side network or the packet data network gateway. The first indication information carries indication information for releasing resources of the source side network of the user terminal.  The method according to claim 1, further comprising: after the source side network or the packet data network gateway receives the first indication information, releasing the source side network of the user terminal Resources.  The method according to claim 2, wherein the first indication information further carries a user identifier corresponding to the user terminal;  After the source side network or the packet data network gateway receives the first indication information, the resources of the source side network of the user terminal are released as follows:  After receiving the first indication information, the source side network or the packet data network gateway releases the resources of the source side network of the user terminal according to the user identifier.  The method according to claim 1, wherein, in the process of the user terminal accessing the target side network, the user terminal is also aware that the user terminal has an emergency service in the source side network, and the target side network The resources of the emergency service are further created.  The method according to claim 4, wherein the creating the emergency service resource in the target side network is specifically: acquiring an emergency service related access point in a process in which the user terminal accesses the target network The name and packet data network gateway information is used to create the emergency service related resource according to the emergency service related access point name and the packet data network gateway information.  The method according to claim 2, wherein the resource for releasing the source side network of the user terminal is specifically:  Deleting resources related to the user terminal on the source side network;  Updating information related to the user terminal in the home network server and the authentication, authorization, and accounting server. The method according to claim 1, wherein the method further comprises:  The target side network notifies that the user terminal service is limited or the resource creation of the user terminal fails, and the user terminal deletes resource information of the source side network stored by the user terminal. The method according to claim 1, wherein the source side network is a non-3GPP network, and the target side network is a 3GPP network; The target side network, in the process of the user terminal accessing the target side network, is configured to send the first indication information to the source side network, where the service of the user terminal is limited or the resource creation fails. Specifically, in the process of accessing the 3GPP network of the user terminal, the mobility management entity learns that the user terminal has limited service or resource creation in the 3GPP network, and passes the home network server and the authentication, authorization, and The charging server sends the first indication information to the non-3GPP gateway.  The method according to claim 1, wherein the source side network is a 3GPP network, and the target side network is a non-3GPP network;  The target side network, in the process of the user terminal accessing the target side network, is configured to send the first indication information to the source side network, where the service of the user terminal is limited or the resource creation fails. Specifically, in the process of the user terminal accessing the non-3GPP network, the non-3GPP gateway learns that the user terminal has limited service or resource creation failure in the non-3GPP network, and passes the home network server, and the authentication, authorization, and The charging server sends the first indication information to the mobility management entity.  The method according to claim 1, wherein the source side network is a non-3GPP network. a CDMA2000 network, where the target side network is a 3GPP network;  The target side network, in the process of the user terminal accessing the target side network, is configured to send the first indication information to the source side network, where the service of the user terminal is limited or the resource creation fails. Specifically, in a process in which the user terminal accesses the 3GPP network, the mobility management entity learns that the user terminal has limited service or resource creation in the 3GPP network;  The mobility management entity sends the first indication information to a high speed packet data access point.  The method according to claim 1, wherein the source side network is a 3GPP network, and the target side network is a CDMA2000 network of a non-3GPP network;  The target side network, in the process of the user terminal accessing the target side network, is configured to send the first indication information to the source side network, where the service of the user terminal is limited or the resource creation fails. Specifically, in the process of the user terminal accessing the non-3GPP network, the high-speed packet data access point is notified that the user terminal has limited service or resource creation failure in the non-3GPP network; The high speed packet data access point sends the first indication information to a mobility management entity. The method according to claim 4, wherein the source side network is a non-3GPP network, and the target side network is a 3GPP network;  In the process of the target side network accessing the target side network, the user terminal is informed that the service of the user terminal is limited or the resource creation fails on the target side network, and the user terminal is on the source side. An emergency service exists in the network. The resource of the emergency service is created on the target side network, and the first indication information is sent to the source network.  In the process of the user terminal accessing the 3GPP network, the mobility management entity learns that the user terminal has limited service or resource creation in the 3GPP network, and has an emergency service on the source side network; The resources of the emergency service of the 3GPP network;  The mobility management entity sends the first indication information to the non-3GPP gateway.  13. The method according to claim 12, further comprising:  The mobility management entity instructs the service gateway and/or the packet data network gateway that the user terminal service is limited or the resource creation fails, and the service gateway and/or the packet data network gateway performs the creation of the emergency service related resource, The creation of resources related to non-emergency services is not performed. .  The method according to claim 13, wherein the sending, by the mobility management entity, the first indication information to the non-3GPP gateway is:  The mobility management entity sends the first indication information to the non-3GPP gateway through a home network server and an authentication, authorization, and accounting server.  The method according to claim 9 or 14, wherein the sending the first indication information to the non-3GPP gateway by the home network server and the authentication, authorization, and accounting server is:  The mobility management entity sends a notification request message to the home network server, where the notification request message carries indication information for releasing resources of a non-3GPP network;  After receiving the notification request message, the home network server sends a separation indication message to the non-3GPP gateway to the authentication, authorization, and accounting server;  The authentication, authorization, and accounting server forwards the separation indication message to the non-3GPP gateway, where the separation indication message carries the first indication information.  The method according to claim 12, wherein the sending, by the mobility management entity, the first indication information to the non-3GPP gateway is: The mobility management entity sends the first indication information to the non-3GPP gateway through a serving gateway and a packet data network gateway. The method according to claim 16, wherein the mobility management entity sends the first indication information to the non-3GPP gateway by using a serving gateway and a packet data network gateway, specifically: the mobility management The entity indicates that the user equipment service of the packet data network gateway is limited or the resource creation fails, and the packet data network gateway sends a separation indication message to the non-3GPP gateway after the related resource of the emergency service is created, where the separation indication message carries The first indication information.  The method according to claim 4, wherein the source side network is a 3GPP network, and the target side network is a non-3GPP network;  In the process of the target side network accessing the target side network, the user terminal is informed that the service of the user terminal is limited or the resource creation fails on the target side network, and the user terminal is on the source side. An emergency service exists in the network. The resource of the emergency service is created on the target side network, and the first indication information is sent to the source network.  When the user terminal accesses the non-3GPP network, the non-3GPP gateway learns that the user terminal has limited service or resource creation failure on the non-3GPP network, and has an emergency service on the source side network; The resources of the emergency service of the non-3GPP network;  The non-3GPP gateway sends the first indication message to the mobility management entity.  The method according to claim 18, further comprising:  The non-3GPP gateway indicates that the user equipment service of the packet data network gateway is limited or resource creation fails. The method according to claim 18, wherein the non-3GPP gateway sends the first indication information to a mobility management entity by using a packet data network gateway and a serving gateway.  The method according to claim 20, wherein the sending, by the non-3GPP gateway, the first indication information to the mobility management entity by using the packet data network gateway and the serving gateway is:  The non-3GPP gateway instructs the packet data network gateway that the user terminal service is limited or the resource creation fails, and the packet data network gateway sends a separation indication message to the mobility management entity after the related resource of the emergency service is created, where The separation indication message carries the first indication information.  The method according to claim 18, wherein the non-3GPP gateway sends the first indication information to the mobility management entity by using a home network server and an authentication, authorization, and accounting server.  The method according to claim 9 or 22, wherein the first indication information is sent to the mobility management entity by the home network server and the authentication, authorization and accounting server:  The non-3GPP gateway sends a separation indication message to the authentication, authorization, and accounting server; The authentication, authorization, and accounting server forwards the separation indication message to the home network server; The home network server forwards the separation indication message to the mobility management entity, where the separation indication message carries the first indication information.  The method according to claim 4, wherein the source side network is a non-3GPP network a CDMA2000 network, where the target side network is a 3GPP network;  In the process of the user side accessing the target side network, the target side network learns that the user terminal has limited service or resource creation failure on the target side network. And the user terminal has an emergency service in the source side network; the resource of the emergency service is created on the target side network, and the first indication information is sent to the source side network, specifically:  In the process of the user terminal accessing the 3GPP network, the mobility management entity learns that the user terminal has limited service or resource creation in the 3GPP network, and has an emergency service on the source side network; The resources of the emergency service of the 3GPP network;  The mobility management entity sends the first indication information to a high speed packet data access point.  The method according to claim 4, wherein the source side network is a 3GPP network, and the target side network is a CDMA2000 network of a non-3GPP network;  In the process of the target side network accessing the target side network, the user terminal is informed that the service of the user terminal is limited or the resource creation fails on the target side network, and the user terminal is on the source side. An emergency service exists in the network. The resource of the emergency service is created on the target side network, and the first indication information is sent to the source network.  The high-speed packet data access point learns that the user terminal has limited service or resource creation failure on the non-3GPP network, and the emergency occurs on the source side network, in the process that the user terminal accesses the non-3GPP network. Business  Creating resources of the emergency service of the non-3GPP network;  The high speed packet data access point sends the first indication information to a mobility management entity.  The method according to claim 1, wherein the source side network is a non-3GPP network, and the target side network is a 3GPP network;  In the process of the user terminal accessing the target side network, the target side network learns that the user terminal service is limited or the resource creation fails, and the sending the first indication information to the packet data network gateway is specifically: The mobility management entity learns that the user terminal service is restricted or the mobility management entity learns that the user terminal resource creation fails, and sends the first to the packet data network gateway by using the home network server and/or the authentication, authorization, and accounting server. Instructions. The method according to claim 1, wherein the source side network is a non-3GPP network, and the target side network is a 3GPP network;  In the process of the user terminal accessing the target side network, the target side network learns that the user terminal service is limited or the resource creation fails, and the sending the first indication information to the packet data network gateway is specifically:  The mobility management entity learns that the user terminal service is restricted or the mobility management entity learns that the user terminal resource creation fails, and sends the first indication information to the packet data network gateway by using the serving gateway.  The method according to claim 1, wherein the source side network is a 3GPP network, and the target side network is a non-3GPP network;  In the process of the user terminal accessing the target side network, the target side network learns that the user terminal service is limited or the resource creation fails, and the sending the first indication information to the packet data network gateway is specifically:  The non-3GPP gateway learns that the user terminal service is restricted or the non-3GPP gateway learns that the user terminal resource creation fails, and sends the first indication information to the packet data network gateway by using the home network server and/or the authentication, authorization, and accounting server. .  The method according to claim 1, wherein the source side network is a 3GPP network, and the target side network is a non-3GPP network;  In the process of the user terminal accessing the target side network, the target side network learns that the user terminal service is limited or the resource creation fails, and the sending the first indication information to the packet data network gateway is specifically:  The non-3GPP gateway or the high speed packet data access point learns that the user terminal service is limited, or the non-3GPP gateway or the high speed packet data access point learns that the resource creation of the user terminal fails, and the packet gateway is used to the packet data network gateway. Sending the first indication information.  30. A resource processing method for network switching, which is characterized by:  Obtaining mobility restriction information of the user terminal;  Obtaining that the service of the user terminal on the target side network is limited according to the mobility restriction information of the user terminal and the related information of the target side network;  The resources of the source side network of the user terminal are released.  The method according to claim 30, wherein in the process of performing network handover, related information of the target side network is acquired by using an attach request message.  The method according to claim 30, wherein the resource for releasing the source side network of the user terminal is specifically: Deleting resources related to the user terminal on the source side network; Updating information related to the user terminal in the home network server and the authentication, authorization, and accounting server; deleting resource information of the source side network in the user terminal.  The method according to claim 30, wherein the acquiring the mobility restriction information of the user terminal is specifically:  Before the network handover, the mobility restriction information of the user terminal is obtained from the authentication, authorization, and accounting server or the home network server.  The method according to claim 33, wherein the source side network is a CDMA2000 network of a non-3GPP network, and the target side network is a 3GPP network;  The obtaining the mobility restriction information of the user terminal from the authentication, authorization, and accounting server or the home network server is specifically: the high-speed packet data access point acquires the mobility restriction information of the user terminal from the authentication, authorization, and accounting server;  The obtaining, according to the mobility restriction information of the user terminal and the related information of the target side network, that the service restriction of the user terminal on the target side network is specifically: when the high speed packet data access point receives the user terminal to the After the attached request message is attached to the 3GPP network, the high-speed packet data access point learns that the service of the user terminal on the target side network is limited according to the mobility restriction information and the related information of the target side network.  The method according to claim 33, wherein the target side network is a CDMA2000 network of a non-3GPP network, and the source side network is a 3GPP network;  The obtaining the mobility restriction information of the user terminal from the authentication, authorization, and accounting server or the home network server is specifically: the mobility management entity acquires the mobility restriction information of the mobile terminal from the home network server; The mobility restriction information and the related information of the target side network, and whether the service restriction of the user terminal on the target side network is specifically: when the mobility management entity receives the attachment request of the user terminal attaching to the CDMA2000 network After the message, the mobility management entity learns that the service of the user terminal on the target side network is limited according to the mobility restriction information and the related information of the target side network.  36. A network processing resource processing apparatus, comprising:  The first determining unit is configured to: when the user terminal accesses the target side network, learn that the user terminal has limited service or resource creation failure on the target side network;  And a first sending unit, configured to send first indication information to the source network or the packet data network gateway, where the first indication information carries indication information for releasing resources of the source side network of the user terminal.  37. The device according to claim 36, further comprising: a first notification unit, configured to notify the user terminal that the service is limited, and the user terminal deletes the user terminal Resource information of the stored source side network.  38. The device of claim 36, further comprising:  The second determining unit is configured to learn that the user terminal has an emergency service in the source side network during the process of accessing the target side network by the user terminal;  The first processing unit is configured to initiate a resource for creating the emergency service.  39. The device according to claim 38, further comprising:  a first acquiring unit, configured to acquire an emergency service-related access point name and packet data network gateway information in a process of accessing the target network by the user terminal, and send the information to the first processing unit;  The first processing unit initiates creation of the resource of the emergency service according to the access point name and packet data network gateway information.  40. A resource processing device for network switching, comprising:  a second acquiring unit, configured to acquire mobility restriction information of the user terminal;  a third determining unit, configured to learn, according to the mobility restriction information of the user terminal and the related information of the target side network, that the service of the user terminal on the target side network is restricted, and send a source including the release user terminal to the second processing unit An instruction for indicating information of a side network resource;  The second processing unit is configured to release the source side network resource of the user terminal according to the instruction sent by the third determining unit.  The device according to claim 40, further comprising:  And a third acquiring unit, configured to acquire related information of the target side network by using an attach request message in the process of performing network switching.  The device according to claim 40, wherein the second obtaining unit is specifically configured to acquire, after the network switching, the mobile terminal from the authentication, authorization, and accounting server or the home network server. Sexual restriction information.