WO2009000197A1 - Procédé et équipement réseau pour établir et effacer des ressources - Google Patents

Procédé et équipement réseau pour établir et effacer des ressources Download PDF

Info

Publication number
WO2009000197A1
WO2009000197A1 PCT/CN2008/071400 CN2008071400W WO2009000197A1 WO 2009000197 A1 WO2009000197 A1 WO 2009000197A1 CN 2008071400 W CN2008071400 W CN 2008071400W WO 2009000197 A1 WO2009000197 A1 WO 2009000197A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network element
user equipment
3gpp
resource
Prior art date
Application number
PCT/CN2008/071400
Other languages
English (en)
French (fr)
Inventor
Wenfu Wu
Shanshan Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=40185196&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2009000197(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP16172080.0A priority Critical patent/EP3096583B1/en
Priority to JP2009551096A priority patent/JP5011396B2/ja
Priority to EP21181957.8A priority patent/EP3952601A1/en
Priority to EP18191044.9A priority patent/EP3442269B1/en
Priority to EP14150464.7A priority patent/EP2720509B1/en
Priority to EP08757809.2A priority patent/EP2104278B1/en
Publication of WO2009000197A1 publication Critical patent/WO2009000197A1/zh
Priority to US12/509,677 priority patent/US8638750B2/en
Priority to US14/104,753 priority patent/US10945261B2/en
Priority to US17/159,773 priority patent/US11997697B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/29—Control channels or signalling for resource management between an access point and the access point controlling device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/824—Applicable to portable or mobile terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method for creating a resource and a network device. Background technique
  • the system architecture is shown in Figure 1, including the evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network.
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • Serving GW Serving Gateway
  • PDN GW Packet Data network gateway entity
  • PDN GW Packet The Data Network Gateway
  • PPN Packet Data Network Gateway
  • UTRAN UMTS Terrestrial Radio Access Network
  • GWRAN GSM/EDGE Radio Access Network
  • SGSN Serving GPRS Supporting Node
  • Non-3GPP IP Access mainly access networks defined by non-3GPP organizations, such as Wireless Local Area Network (WLAN), Worldwide Interoperability for Microwave (Wimax) Access) and other networks.
  • WLAN Wireless Local Area Network
  • Wimax Worldwide Interoperability for Microwave
  • the AAA Server, Authentication, Authorization and Accounting Server is used to perform access authentication, 4 authorization, and accounting functions for the user equipment (UE, User Equipment).
  • UE User Equipment
  • One requirement of an evolved network is to implement a handover between a 3GPP access system (GERAN/UTRAN/E-UTRAN) and a non-3GPP access system (such as WLAN/Wimax, etc.).
  • the handover procedure is completed by the UE's Attach process in the new access system.
  • FIG. 2 is a flow chart of the non-3GPP to 3GPP system handover procedure. Includes the following steps:
  • the UE accesses the Non-3GPP access network through a non-3GPP (Non-3GPP) gateway and a PDN GW.
  • Non-3GPP Non-3GPP
  • the UE initiates a handover between the non-3GPP access system and the SAE access system.
  • the UE sends an Attach Request message to the MME.
  • the authentication process is performed between the UE, the MME, and the HSS/AAA Server.
  • the MME and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the MME acquires PDN GW address information used by the UE in the non-3GPP access system.
  • the MME sends a Create 7-Request message to the Serving GW.
  • the Serving GW sends a Create Default Bearer Request message to the PDN GW.
  • GTP GPRS Tunneling Protocol
  • the Serving GW sends a Proxy Binding Update message to the PDN GW.
  • PMIP Proxy Mobile Internet Protocol
  • the PDN GW If the interface between the Serving GW and the PDN GW uses the GTP protocol, the PDN GW returns a Create Default Bearer Response message to the Serving GW.
  • the PDN GW sends a Proxy Binding Ack message to the Serving GW.
  • Serving GW returns to create a default bearer response message to the MME.
  • the MME initiates a radio bearer setup procedure to establish a radio bearer and attach completion procedure corresponding to the default bearer.
  • the 3GPP system needs to recover the resources used by the UE in the non-3GPP access system in the 3GPP system, but now the non-3GPP to 3GPP There is no such mechanism in the system's switching process.
  • the 3GPP system In the normal 3GPP access procedure, the 3GPP system only creates the default bearer of the UE, and the 3GPP system needs to recover the resources of the UE in the non-3GPP system when switching from the non-3GPP to the 3GPP system. Therefore, the two access processing processes are different. The 3GPP system needs to distinguish between the two different processing modes. However, there is no corresponding mechanism in the current 3GPP system to distinguish the processing.
  • the processing in the access procedure in the existing 3GPP system is that the UE initiates the establishment of only one default bearer, that is, the MME can initiate a default bearer creation process only for one PDN GW. If the UE uses multiple PDN GWs in a non-3GPP access system, the existing mechanism cannot handle it.
  • the handover between the non-3GPP and 3GPP systems in the prior art is a "loosely coupled" handover, that is, the UE first disconnects from the source side system, and the handover is completed from the target side system through the access procedure.
  • This type of switching can result in a long service interruption and may result in service interruption.
  • How to optimize the handover between non-3GPP and 3GPP systems and reduce the time of UE service interruption there is no corresponding mechanism in the prior art for processing.
  • the non-3GPP access system allocates resources for the UE.
  • the resources allocated by the non-3GPP access system for the UE cannot be released.
  • the resources allocated by the non-3GPP access system for the UE need to be released, but there is no corresponding processing mechanism in the prior art. Summary of the invention
  • the embodiments of the present invention provide a resource creation method, a resource deletion method, and a network device, which implement an initial access process and a handover process of a user equipment, thereby performing corresponding resource processing.
  • the first network element When the user equipment switches or initiates an initial access request between the 3GPP partner 3GPP network and the non-3GPP network, the first network element notifies the second network element on the network side to create a processing type of the resource for the user equipment; The processing type of the resource, the second network element performs a process of creating a corresponding resource for the user equipment.
  • Another embodiment of the present invention discloses a resource recovery processing method when a heterogeneous network is switched, and a packet Steps:
  • the network side gateway device acquires the policy and charging control rules used by the user equipment in the target access system
  • the network side gateway device initiates a network side bearer establishment procedure in the target access system according to the policy and charging control rule.
  • the network side gateway may be a serving gateway, an anchor gateway, or a non-3GPP gateway device.
  • the embodiment of the invention further discloses a resource deletion method, including:
  • the first network element acquires the second network element address information; the first network element sends a message to notify the second network element to release the allocation. a resource to the user equipment; the second network element releases the resource allocated to the user equipment.
  • the method further includes the step of determining that the access request initiated by the user equipment is an initial access request.
  • Another embodiment of the present invention also discloses another resource deletion method, including:
  • the target access network element When the user equipment switches or initiates an initial access request between the 3GPP network and the non-3GPP network, the target access network element notifies the user that the anchor point does not initiate resource release processing of the source access network; After the network, the target access network element sends a message to the source access network element to notify the source network that the UE has switched to the target access network. After receiving the notification, the source network element initiates resource release processing of the source network.
  • the embodiment of the invention discloses a network device for processing network resources, comprising: an access request determining unit and a processing type notification unit; wherein:
  • An access request determining unit configured to determine that the access request initiated by the user equipment is an initial access request, or a handover request between the non-3GPP access system and the 3GPP access system; and send the determined result to the a processing type notification unit;
  • the processing type notification unit is configured to receive the result sent by the access request determining unit, determine a corresponding processing type for creating a resource for the user equipment, and notify the network side to create a corresponding network element for the user equipment.
  • the embodiment of the invention further discloses another network device for processing network resources, comprising: a parsing unit and a resource creation processing unit; wherein: a parsing unit, when the user equipment switches or initiates initial access between the 3GPP network and the non-3GPP network The request is used to receive a message from the peer network element, and parse out a processing type for creating a resource for the user equipment from the message; and notify the parsed processing type to the resource a source creation processing unit, configured to receive a processing type sent by the parsing unit, and perform a process of creating a corresponding resource for the user equipment.
  • a parsing unit when the user equipment switches or initiates initial access between the 3GPP network and the non-3GPP network The request is used to receive a message from the peer network element, and parse out a processing type for creating a resource for the user equipment from the message; and notify the parsed processing type to the resource a source creation processing unit, configured to receive a processing type sent by the parsing unit, and perform
  • the embodiment of the invention further discloses a device for releasing network resource processing, comprising: an initialization request determining unit, a network element address obtaining unit and a resource release notification unit; wherein: an initialization request determining unit, when the user equipment is in a 3GPP network and a non-3GPP When the network is switched, the access request initiated by the user equipment is used to initialize the access request; and the network element address obtaining unit is notified; the network element address obtaining unit is configured to acquire the anchor gateway used by the user equipment.
  • the address information of the network element is sent to the resource release notification unit, and the resource release notification unit is configured to send a resource release notification message to the anchor gateway network element according to the address information sent by the network element address obtaining unit. Requesting to release resources allocated to the user device.
  • the present invention further discloses a network device for network resource release processing, comprising: a resource release message parsing unit and a resource release execution unit; wherein: a resource release message parsing unit, when the user equipment is in a 3GPP network and a non-3GPP network The resource release notification message is parsed and sent to the resource release execution unit, and the resource release execution unit is configured to release the resource allocated to the user equipment.
  • the first network element notifies the second network element on the network side to create a processing type of the resource for the user equipment; the second network element performs the user equipment according to the processing type.
  • the creation of the corresponding resource Therefore, in the prior art, the network side gateway network element (ie, the second network element) cannot identify different access requests (that is, initialize the access request and the access request caused by the access system switching), and thus cannot be used for different connections. Into the request to create the corresponding resource.
  • the first network element obtains the second network element address information from the network element saved by the second network element address information, and the first network element sends a message to notify the second
  • the network element releases the resources allocated to the user equipment; the second network element releases the resources allocated to the user equipment.
  • FIG. 1 is a schematic diagram of a prior art evolved network system architecture
  • FIG. 3 is a flowchart of resource creation signaling interaction according to an embodiment of the present invention.
  • 4 is a flowchart of a resource creation signaling interaction according to Embodiment 2 of the present invention;
  • FIG. 5 is a flowchart of a resource creation signaling interaction according to Embodiment 3 of the present invention.
  • FIG. 6 is a flowchart of a resource creation signaling interaction according to Embodiment 4 of the present invention.
  • FIG. 7 is a flowchart of a resource creation signaling interaction according to Embodiment 5 of the present invention.
  • FIG. 8 is a flowchart of a resource creation signaling interaction according to Embodiment 6 of the present invention.
  • FIG. 9 is a flowchart of a resource creation signaling interaction according to Embodiment 7 of the present invention.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of resource deletion signaling interaction according to Embodiment 8 of the present invention.
  • FIG. 14 is a schematic structural diagram of three network devices according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a network device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS Embodiment 1
  • the first network element on the network side indicates to create a bearer (or create a PDP) when sending a default bearer request (or creating a default packet data protocol (PDP) context request) to a serving gateway (Serving GW)
  • the processing type of the context the Serving GW sends a create bearer request (or creates a default PDP context request) to the PDN GW with a flag bit indicating the type of processing.
  • the PDN GW performs different process processing according to the flag bit.
  • the specific process is shown in Figure 3, including:
  • the UE accesses the Non-3GPP access network through the Non-3GPP gateway and the PDN GW.
  • the UE initiates a handover between the non-3GPP access system and the 3GPP access system.
  • the UE sends an attach request message to the first network element on the network side to perform a handover procedure of the non-3GPP to 3GPP system.
  • SAE System Architecture Evolution
  • GPRS/UMTS GPRS/UMTS Support Node
  • the first network element on the network side may determine whether the received access request is a non-3GPP to 3GPP system handover request or a normal access request (also referred to as an initialization access request) according to the following method: 1) If the handover procedure of the non-3GPP to 3GPP system is also handled by the Attach procedure, the Attach Type field is added to the Attach Request message to indicate different access processing types (eg, for normal access, the Attach Type field is set to Initial Attach; For the handover access, the Attach Type field is set to Handover Attach. The first network element on the network side distinguishes different access procedures according to the Attach Type in the Attach Request message.
  • the PDN GW address to be used by the UE is saved in the UE when the 3GPP or the non-3GPP system accesses, the PDN GW address information is not carried in the Attach Request message in the normal access procedure, in the non-3GPP to 3GPP system.
  • the Attach Request message carries the PDN GW address information in the handover process.
  • the first network element on the network side determines whether the access request is a normal access request or an access request caused by the handover according to whether the PDN GW address information is carried in the message.
  • the handover process of the non-3GPP to 3GPP is processed through a separate process instead of the Attach process, such as the UE sends a non-3GPP to 3GPP handover procedure request (non-3 GPP to 3GPP Handover Request) message to the network side first network element
  • the MME is requested to perform handover procedure processing of a non-3GPP to 3GPP system.
  • the authentication process is performed between the UE, the first network element on the network side, and the HSS/AAA Server.
  • the first network element on the network side and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the first network element on the network side acquires the PDN GW address information used by the UE in the non-3GPP access system.
  • the first network element on the network side selects the PDN GW used by the UE according to the default APN (Access Point Name) in the user subscription data; A network element uses the PDN GW address that the UE uses in the non-3GPP access system.
  • the PDN GW address information can be obtained by the first network element on the network side from the HSS/AAA Server or the PDN GW address information saved by the HSS/AAA Server. Give the first network element on the network side). If the 3GPP system is the SAE system, the first network element on the network side sends a Create Default Bearer Request message to the Serving GW.
  • the first network element on the network side sends a Create Default PDP Context Request (Create Default PDP).
  • Context Request Message to Serving GW. Adding a flag to the message indicates the type of processing the bearer creates. The specific processing of the flag bit can be:
  • the Serving GW sends a Create Default Bearer Request message to the PDN GW; if the 3GPP system is GPRS/UMTS, the Serving GW sends the Create Missing The provincial PDP context request message is sent to the PDN GW.
  • the addition of a flag bit in the message indicates the type of processing the bearer creates. The specific processing of the flag can be:
  • the Serving GW adds an "Initial Indication” indication bit to indicate that the message was due to normal access. For the process of handover access, the Serving GW does not carry this indication bit.
  • the PDN GW determines the processing type information created by the bearer in the message, and performs different processing according to the processing type information created by the bearer:
  • the PDN GW queries whether the UE has a Policy and Charging Control (PCC) rule in the local gateway. If it exists, the PDN GW deletes the PCC rule existing by the UE, and notifies the PCRF to delete the saved PCC rule. At the same time, the PDN GW initiates the source of the source in the non-3GPP access network. The source release processing flow releases resources in the source non-3GPP access network.
  • PCC Policy and Charging Control
  • the PDN GW acquires the PCC rule saved by the UE in the gateway. It is determined whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW contacts the PCRF to obtain the modified PCC rule. At the same time, the PDN GW initiates a resource release processing procedure in the source non-3GPP access network, and releases the resources in the source non-3GPP access network.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW returns a Create Default Bearer Response message to the Serving GW.
  • the Serving GW returns to create a default bearer response message to the first network element on the network side.
  • the first network element on the network side initiates a radio bearer setup procedure to establish a radio bearer and an attach completion procedure corresponding to the default bearer.
  • the PDN GW initiates the network-side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule according to the saved or modified PCC rule, that is, the UE is created in the original non-3GPP access.
  • the resources used by the system are required in the 3GPP system.
  • the message between the GWs will be an internal message of the entity.
  • step 12 There is no sequential relationship between step 12 and step 9.
  • the PDN GW obtains the PCC rule in the PDN GW after receiving the message sent by the Serving GW, and the PDN GW according to the saved PCC rule or the modified PCC rule ( The PDN GW contacts the PCRF to obtain the modified PCC rule.
  • the initiating network-side dedicated bearer activation procedure establishes a dedicated bearer corresponding to the PCC rule, that is, creates a resource required by the UE in the original non-3GPP access system for the service in the 3GPP system.
  • the PDN GW initiates a resource release processing procedure in the source non-3GPP access network, and releases the resources in the source non-3GPP access network.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the first network element on the network side sends a default bearer request (or creates a default PDP context request) to the Serving GW to carry the flag bit, it indicates the processing type of creating a bearer (or creating a PDP context), and the Serving GW sends a proxy binding update.
  • the message carrying a flag to the PDN GW indicates the type of processing.
  • the PDN GW performs different process processing according to the flag bit. The specific process is shown in Figure 4, including: 1.
  • the UE accesses the Non-3GPP access network through the Non-3GPP gateway and the PDN GW.
  • the UE initiates a handover between the non-3GPP access system and the 3GPP access system.
  • the UE sends an attach request message to the first network element on the network side to perform a handover procedure of the non-3GPP to 3GPP system.
  • the first network element on the network side is the MME
  • the first network element on the network side is the SGSN.
  • the authentication process is performed between the UE, the first network element on the network side, and the HSS/AAA Server.
  • the first network element on the network side and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the first network element on the network side acquires the PDN GW address information used by the UE in the non-3GPP access system.
  • the first network element on the network side selects the PDN GW used by the UE according to the default APN (Access Point Name) in the user subscription data; A network element uses the PDN GW address that the UE uses in the non-3GPP access system.
  • the PDN GW address information can be obtained by the first network element on the network side from the HSS/AAA Server or the PDN GW address information saved by the HSS/AAA Server. Give the first network element on the network side). If the 3GPP system is the SAE system, the first network element on the network side sends a Create Default Bearer Request message to the Serving GW.
  • the first network element on the network side sends a Create Default PDP Context Request (Create Default PDP).
  • Context Request Message to Serving GW. Adding a flag to the message indicates the type of processing the bearer creates. The processing of the flag bits is the same as the processing in the first embodiment.
  • the Serving GW sends a Proxy Binding Update message to the PDN GW.
  • the flag in the message indicates the type of processing for the binding update.
  • the specific processing of the flag bit can be:
  • This step can also be handled as follows:
  • the Serving GW sends a recovery bearer request (when the 3GPP is a GPRS/UMTS system) or restores the PDP context request (when the 3GPP system is a SAE system) message to the PDN GW to inform the PDN GW to resume the bearer used by the UE.
  • a recovery bearer request when the 3GPP is a GPRS/UMTS system
  • restores the PDP context request when the 3GPP system is a SAE system
  • the PDN GW determines the processing type information of the binding update in the Proxy BU message or determines whether the recovery bearer request message is received, and performs the following according to the processing type information of the binding update or whether the recovery bearer request message is received.
  • the PDN GW queries whether the UE has PCC (Policy and Charging Control) in the PDN WG. rule. If it exists, the PDN GW deletes the PCC rule existing by the UE, and notifies the PCRF to delete the saved PCC rule. At the same time, the PDN GW initiates a resource release processing procedure in the source non-3GPP access network, and releases resources in the source non-3GPP access network.
  • PCC Policy and Charging Control
  • the processing type information of the binding update in the Proxy BU message is a binding update caused by handover access or a PDN GW receives a recovery bearer request (or a recovery PDP context request) message
  • the PDN GW acquires the UE at the local gateway.
  • PCC rules saved inside. It is determined whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW contacts the PCRF to obtain the modified PCC rule. At the same time, the PDN GW initiates a resource release processing procedure in the source non-3GPP access network, and releases the resources in the source non-3GPP access network.
  • the PDN GW returns a proxy binding acknowledgement message to the Serving GW.
  • the PDN GW If the PDN GW receives the Resume Bearer Request (or Recover PDP Context Request) message sent by the Serving GW in the previous step, the PDN GW returns a Resume Bearer Response (or Resume PDP Context Response) message to the Serving GW.
  • Resume Bearer Response or Resume PDP Context Response
  • the Serving GW returns a default bearer response message to the first network element on the network side.
  • the first network element on the network side initiates a radio bearer setup procedure to establish a radio bearer and an attach completion procedure corresponding to the default bearer.
  • the PDN GW sends a PCC rule providing message to the Serving GW to provide the saved or modified PCC rule to the Serving GW.
  • the Serving GW saves the received PCC rules and then returns the PCC rules to provide a confirmation message to the PDN GW.
  • the Serving GW initiates the establishment of a network-side dedicated bearer activation procedure according to the received PCC rules.
  • the dedicated bearer corresponding to the PCC rule that is, the service used to create the UE in the original non-3GPP access system is
  • the message between the GWs will be a message inside the entity.
  • step 12 There is no sequential relationship between step 12 and step 9.
  • the PDN GW If the processing type information of the bearer creation or the binding update is not carried, after the PDN GW receives the message sent by the Serving GW, if the UE finds that the PC has the PCC rule in the PDN GW, the PDN GW will save the saved PCC rule or modify it.
  • the PCC rule (the PDN GW contacts the PCRF to obtain the modified PCC rule) is notified to the Serving GW, and the Serving GW initiates the network-side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule according to the received PCC rule, that is, the UE is created in the original non-3GPP.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the non-3GPP (non-3 GPP) gateway network element carries a flag bit to indicate the type of processing when transmitting the proxy binding update message to the PDN GW. After receiving the message, the PDN GW performs different process processing according to the flag bit.
  • the specific process is shown in Figure 5, including:
  • the UE accesses the 3GPP access network through the Serving GW and the PDN GW.
  • the UE initiates a handover between the 3GPP access system and the non-3GPP access system.
  • the UE sends an access request message to the non-3GPP gateway network element to perform a handover procedure from the 3GPP to the non-3GPP system.
  • the non-3GPP gateway network element is an EPDG (Evolved Packet Data Gateway); for the Wimax system, the non-3GPP gateway network element is an ASN GW (Access Service Network Gateway, Access Service Network) Gateway); For CDMA systems, the non-3GPP gateway network element is AGW (Access Gateway, Access Gateway).
  • the non-3GPP gateway network element may determine whether the received access request is a 3GPP to non-3GPP system handover request or a normal access request (also called an initialization access request) according to the following method:
  • an Access Type field is added in the Access Request message to indicate different access processing types (eg, For normal access, the Access Type field is set to Initial Access; for handover access, the Access Type field is set to Handover Access), and the non-3GPP gateway network element distinguishes different access procedures according to the Access Type in the Access Request message. .
  • the UE accesses the PDN GW address used by the 3GPP or non-3GPP system, it is saved in the UE.
  • the Access Request message does not carry the PDN GW address information, and the Access Request message carries the PDN GW address information in the handover procedure from the 3GPP to the non-3GPP system.
  • the non-3GPP gateway network element determines whether the access request is a normal access request or an access request caused by the handover according to whether the message carries the PDN GW address information.
  • 3GPP to non-3GPP handover procedure processing is handled by a separate process instead of the access procedure, such as the UE sending a "3GPP to non-3GPP Handover Request" message to the non-3GPP gateway network element requesting the non-3GPP gateway network element to perform 3GPP to the non-3GPP to the non-3GPP gateway network element Handover process processing of the 3GPP system.
  • the non-3GPP gateway network element determines whether the received access request is a normal access request or a handover-induced access request.
  • the access authentication process is performed between the UE, the non-3GPP gateway network element, and the HSS/AAA Server.
  • the non-3GPP gateway network element obtains the PDN GW address information used by the UE.
  • the non-3GPP gateway network element selects the PDN GW used by the UE according to the default APN (Access Point Name) in the user subscription data.
  • the non-3GPP gateway network uses the PDN GW (PDN) used by the UE in the 3GPP access system.
  • PDN PDN GW
  • the server sends the saved PDN GW address information to the non-3GPP gateway network element. If the interface between the non-3GPP gateway network element and the PDN GW uses the PMIP protocol, the non-3GPP gateway network element sends a Proxy Binding Update message to the PDN GW. The addition of a flag bit in the message indicates the type of processing for the binding update. The specific processing of the flag is the same as that in the second embodiment.
  • the UE sends a Binding Update message to the PDN GW.
  • the addition of a flag bit in the message indicates the type of processing that is bound to the update.
  • the specific processing of the flag bit can be:
  • the non-3GPP gateway network element sends a recovery service request message to the PDN GW to notify the PDN GW to resume the UE used by the UE.
  • the PDN GW After receiving the Proxy BU or the BU message, the PDN GW determines the processing type information of the binding update in the message or whether the recovery service request message is received, and performs different according to the processing type information of the binding update or whether the recovery service request message is received. Processing:
  • the PDN GW queries whether the UE has a PCC in the GW (Policy and Charging Control, Policy and Charging) Control) rules. If it exists, the PDN GW deletes the PCC rule existing by the UE, and notifies the PCRF to delete the saved PCC rule. At the same time, the PDN GW initiates a resource release processing procedure in the source 3GPP access network, and releases resources in the source 3GPP access network.
  • the PDN GW acquires the PCC rule saved by the UE in the gateway. It is determined whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW contacts the PCRF to obtain the modified PCC rule. At the same time, the PDN GW initiates a resource release processing procedure in the source 3GPP access network, and releases resources in the source 3GPP access network.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW sends a Proxy Binding Ack message to the non-3GPP gateway network element.
  • the PDN GW sends a Binding Ack message to the UE.
  • the PDN GW receives the recovery service sent by the non-3GPP gateway network element in the previous step The request message, then the PDN GW returns a recovery service response message to the non-3GPP gateway network element.
  • the non-3GPP gateway network element returns an access accept message to the UE.
  • the PDN GW sends a PCC rule providing message to the non-3GPP gateway network element to provide the saved or modified PCC rule to the non-3GPP gateway network element.
  • the non-3GPP gateway network element saves the received PCC rules and then returns the PCC rules to provide an acknowledgment message to the PDN GW.
  • the non-3GPP gateway network element initiates the network side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule according to the received PCC rule, that is, the resource required for the service used by the UE in the original 3GPP access system in the non-3GPP access system is created. .
  • the message between the non-3GPP gateway network element and the PDN GW will be an internal internal message.
  • step 9 There is no sequential relationship between step 9 and step 7.
  • the PDN GW If the processing type information of the binding update is not carried, after the PDN GW receives the message sent by the non-3GPP gateway network element, if the UE finds that the PC has the PCC rule in the PDN GW, the PDN GW will save the saved PCC rule or modify it.
  • the PCC rule (the PDN GW contacts the PCRF to obtain the modified PCC rule) to notify the non-3GPP gateway network element, and the non-3GPP gateway network element initiates the network side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule according to the received PCC rule, It is to create the resources required by the UE in the original 3GPP access system for services in the non-3GPP system.
  • the first network element on the network side obtains the PDN GW address used by the UE, it sends a specific message to notify the Serving GW, and the Serving GW then notifies the PDN GW to perform different processing of the bearer.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the first network element on the network side sends a specific message to the Serving GW, and the Serving GW sends a specific message to the PDN GW, informing the PDN GW to restore the bearer corresponding to the service used by the UE.
  • the first network element on the network side sends a specific message to the PDN GW, and notifies the PDN GW to create a resource corresponding to the service used by the UE, where the message carries the Serving GW address information used by the UE.
  • the specific process is shown in Figure 6, including:
  • the UE accesses the Non-3GPP access network through the Non-3GPP gateway and the PDN GW.
  • the UE initiates a handover between the non-3GPP access system and the 3GPP access system.
  • the UE sends an attach request message to the first network element on the network side to perform non-3GPP to 3GPP system cutting. Change the process.
  • the first network element on the network side is the MME
  • the first network element on the network side is the SGSN.
  • the authentication process is performed between the UE, the first network element on the network side, and the HSS/AAA Server.
  • the first network element on the network side and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the first network element on the network side acquires the PDN GW address information used by the UE in the non-3GPP access system.
  • the first network element on the network side uses the PDN GW used by the UE in the non-3GPP access system (the PDN GW address information can be obtained by the first network element on the network side from the HSS/AAA Server or the HSS)
  • the AAA server sends the saved PDN GW address information to the first network element on the network side.
  • the first network element on the network side sends a message to restore the bearer request (or restore the PDP context request) to the PDN GW, and informs the PDN GW to create a resource corresponding to the service used by the UE.
  • the message carries the Serving GW address information used by the UE.
  • the bearer recovery request (or the recovery PDP context request) message is forwarded to the PDN GW through the Serving GW.
  • the first network element on the network side sends a resume bearer request (or restore PDP context request) message to the Serving GW, where the message carries a single PDN GW address information used by the UE.
  • the first network element on the network side sends a resume bearer request (or restore PDP context request) message to the Serving GW, where the message carries all PDN GW address information used by the UE.
  • the PDN GW obtains the Serving GW address information carried in the message after receiving the message of restoring the bearer request (or restoring the PDP context request). Subsequent resource processing procedures The PDN GW will send related messages to the Serving GW network element. The processing of the PDN GW is described in the previous embodiment. At the same time, the PDN GW initiates a resource release processing procedure in the source non-3GPP access network, and releases the resources in the source non-3GPP access network.
  • the PDN GW returns the bearer response (recover PDP context response) message to the first network element on the network side.
  • the message that the bearer response is restored (or the PDP context response is restored) is forwarded by the Serving GW to the first network element on the network side.
  • the access processing type is the access processing caused by the handover and the Serving GW and the PDN GW
  • the inter-interface uses the GTP protocol, and the PDN GW initiates the network-side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule according to the saved or modified PCC rule, that is, the resource required for the service used by the UE in the original non-3GPP access system.
  • the PDN GW sends a PCC rule providing message to the Serving GW to provide the saved or modified PCC rule to the Serving GW. .
  • the Serving GW saves the received PCC rules and then returns the PCC rules to provide a confirmation message to the PDN GW.
  • the Serving GW initiates a network-side dedicated bearer activation procedure according to the received PCC rule to establish a dedicated bearer corresponding to the PCC rule, that is, to create a resource required by the UE in the original non-3GPP access system for the service in the 3GPP system.
  • the message between the GWs will be a message inside the entity.
  • step 9 There is no sequential relationship between step 9 and step 8.
  • Embodiment 5 How the PDN GW passes the PCC rules to the Serving GW. This embodiment is not limited. Embodiment 5:
  • the source side network side network element sends a handover request message to the target side network side network element, and carries the anchor point gateway network element address information used by the UE in the source side system, and the target side network side network element acquires the anchor point gateway network element address. The information is then notified to these anchor gateway network elements for resource creation processing.
  • the specific process is shown in Figure 7, including:
  • the source side access system decides to initiate a handover and switches the UE to the target side access system.
  • the source side network side network element sends a handover request message to the target side network side network element, and the handover request message carries the anchor point gateway network element address information used by the UE in the source side access system (for example, the message carries the Anchor Gateway Address) List cell, including each anchor gateway network element address information used by the UE).
  • the handover request message carries the anchor point gateway network element address information used by the UE in the source side access system (for example, the message carries the Anchor Gateway Address) List cell, including each anchor gateway network element address information used by the UE).
  • the source side/target side network side network element is the SGSN; if the source side/target side access system is an SAE system, the source side/target side network side network If the source/target side access system is a WLAN system, the source side/target side network side network element is an EPDG (Evolved Packet Data Gateway); if the source side/target side access system For the Wimax system, the source side/target side network side network element is an ASN GW (Access Service Network Gateway); if the source side/target side access system is a CDMA system, The source side/target side network side network element is an AGW (Access Gateway, Access Gateway).
  • EPDG Evolved Packet Data Gateway
  • the target side network side network element obtains the anchor point gateway network element address information used by the UE in the source side access system from the handover request message, and then notifies the anchor gateway network element to perform resource creation processing, which is also called resource pre-requisite. Leave it for processing.
  • resource creation processing which is also called resource pre-requisite. Leave it for processing.
  • the network side of the target side returns the response message to the source side network element.
  • the source side network side NE notifies the UE to switch to the target side access system.
  • the UE switches to the target side access system.
  • the UE also initiates pre-registration or optimizes the handover procedure to the 3GPP access network through the non-3GPP network when camping on the non-3GPP network, and the first network element on the network side of the 3GPP access network sends a default bearer request (or creates a default).
  • a default bearer request (or creates a default).
  • Trust PDP Context Request) indicates the type of processing to create a bearer (or create a PDP context) when carrying the indicator bit to the Serving GW (pre-registration processing type or the type of optimized handover processing between the non-3GPP network and the 3GPP network), Serving GW After receiving the message, the resource creation process is performed according to the indication bit.
  • the specific process is shown in Figure 8, including:
  • the UE accesses the Non-3GPP access network through the Non-3GPP gateway and the PDN GW.
  • the UE initiates a pre-registration or optimized handover process of the 3GPP access system.
  • the UE sends an attach request message to the first network element on the network side through the non-3GPP access network to perform pre-registration or optimize the handover process of the 3GPP system.
  • the first network element on the network side is the MME
  • the first network element on the network side is the SGSN.
  • the UE may add an indication bit in the Attach Request message to indicate that the first network element on the network side, the Attach Request message, is caused by the pre-registration or optimized handover procedure of the UE.
  • the specific processing of the indicator bits can be:
  • the first network element on the network side determines that the received Attach Request message is sent from the non-3GPP access network, and the first network element on the network side It is considered that the received Attach Request message is caused by the UE's pre-registration or optimized handover procedure.
  • the authentication process is performed between the UE, the first network element on the network side, and the HSS/AAA Server.
  • the first network element on the network side and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the first network element on the network side acquires the PDN GW address information used by the UE in the non-3GPP access system.
  • the first network element on the network side selects the PDN GW used by the UE in the non-3GPP access system (the PDN GW address information can be obtained by the first network element on the network side from the HSS/AAA Server or the PDN saved by the HSS/AAA Server)
  • the GW address information is sent to the first network element on the network side. If the 3GPP system is the SAE system, the first network element on the network side sends a Create Default Bearer Request message to the Serving GW. If the 3GPP system is a GPRS/UMTS system, the first network element on the network side sends a Create Default PDP Context Request (Create Default PDP). Context Request ) Message to Serving GW. An indication in the message indicates the type of processing the bearer creates (pre-registration or optimized switch processing type). The specific processing of the indicator bits can be:
  • the Serving GW sends a Create Bearer Request or a Create PDP Context Request message to the PDN GW after receiving the above message.
  • the addition of an indication bit in the message indicates the type of processing the bearer creates (pre-registration or optimized handover processing type).
  • the specific processing of the indicator bits can be:
  • the "Pre-registration Indication” indicator is either the "Optimized Handover Indication” indicator. 8.
  • the PDN GW obtains the PCC rule saved by the UE in the gateway. It is determined whether the PCC rule is related to an IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW contacts the PCRF to obtain the modified PCC rule.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW When the PDN GW receives the bearer creation request message for optimal handover or pre-registration, the user plane path is not switched, that is, the downlink user plane path of the PDN GW is still to the non-3 GPP access network, and remains in the non-3GPP access network. resource of.
  • the PDN GW back creates a bearer response or creates a PDP context response message to the Serving GW.
  • the Serving GW sends the gateway control and QoS policy rule request message to the PCRF to obtain the UE used in the 3GPP access network after receiving the message sent in step 6.
  • PCC rules The PCRF returns a gateway control and quality of service policy rule response message to the Serving GW, which carries the PCC rules used by the UE in the 3GPP access network.
  • the Serving GW does not send a Proxy BU message to the PDN GW (ie, the Serving GW does not notify the PDN GW to switch the user plane path to the Serving GW).
  • Serving GW returns to create a default bearer response or create a default PDP context response message.
  • the MME returns an attach accept message to the UE.
  • the PDN GW sends a create dedicated bearer request message according to the saved or acquired PCC rule to the network side first network element to initiate a network side dedicated bearer activation procedure to establish a PCC rule.
  • the corresponding dedicated bearer that is, the resources required to create the UE in the original non-3GPP access system in the 3GPP network.
  • the Serving GW sends a Create Proprietary Bearer Request message to the network-side first network element to initiate a network-side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule.
  • the creation of a proprietary bearer request message may add an indication bit indicating the type of processing the bearer is established (pre-registration or optimized handover processing type).
  • the specific processing of the indicator bits can be:
  • Pre-registration Indication is the intended position or "Optimized Handover Indication”.
  • the first network element on the network side sends a bearer setup request message to the 3GPP access network element to request the 3GPP access network element to establish a bearer on the radio side. If the first network element on the network side finds that the bearer establishment on the radio side is caused by pre-registration or optimized handover, the first network element on the network side adds an indication bit in the bearer setup request message to indicate the processing type of the bearer establishment (pre-registration or optimization). Switch processing type).
  • the specific processing of the indicator bits can be:
  • the first network element on the network side sends a relocation request message to the 3GPP access network element to request the 3GPP access network element to establish a bearer on the radio side.
  • the 3GPP access network element After receiving the above message, the 3GPP access network element establishes bearer resources between the local network element and the Serving GW. If the 3GPP access network element finds that the bearer setup request is due to pre-registration or optimal handover, the 3GPP access is established. The network element does not notify the UE to establish a radio bearer (Radio Bearer) resource. Then, the 3GPP access network element returns a bearer setup response message to the first network element on the network side.
  • Radio Bearer Radio Bearer
  • the first network element on the network side creates a dedicated bearer response message to the Serving GW or the PDN GW.
  • the UE moves to the 3GPP access network, and sends a tracking area or routing area update request message to the network side.
  • the first network element indicates that the first network element UE on the network side has switched to the 3GPP access network (the UE may also use other messages.
  • the first network element UE on the network side is indicated to have switched to the 3GPP access network, such as a Service Request message.
  • the first network element on the network side sends a modify bearer request or modifies a PDP context request message to the Serving GW.
  • the first network element on the network side adds the indication bit information in the modify bearer request or modify the PDP context request message to indicate that the PDN GW does not initiate the resource release processing procedure of the UE in the source non-3GPP access network.
  • This indication bit can be an optimized handover or pre-registration indicator bit or a resource not release indicator bit.
  • the specific processing of the indicator bits can be:
  • the Serving GW sends a modify bearer request or modifies the PDP context request message to the PDN GW. If the interface between the Serving GW and the PDN GW uses the PMIP protocol, the Serving GW sends a proxy binding update message to the PDN GW.
  • the Serving GW adds the indication bit information in the modify bearer request or modify the PDP context request or the proxy binding update message to indicate that the PDN GW does not initiate the resource release processing procedure of the UE in the source non-3GPP access network.
  • This indication bit can be an optimized handover or pre-registration indicator or the resource does not release the indication bit.
  • the specific processing of the indicator bits can be:
  • the PDN GW After receiving the above message, the PDN GW obtains the PCC rule saved by the UE in the gateway. If the PDN GW receives the proxy binding update message sent by the Serving GW, the PDN GW determines whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type, and if relevant, the PDN GW sends The IP-CAN Session Modification Request message to the PCRF acquires the PCC rules used by the UE within the 3GPP access network. The PCRF returns an IP-CAN session modification confirmation message to the PDN GW, which carries the PCC rules used by the UE in the 3GPP access network.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW does not initiate the resource release processing procedure of the UE in the source non-3GPP access network (ie, The resource release process in the non-3GPP access network is not triggered by the PDN GW).
  • the PDN GW modifies the bearer response or modifies the PDP context response or the proxy binding acknowledgement message to the Serving GW.
  • the Serving GW returns to modify the bearer response or modify the PDP context response message to the first network element on the network side. 22.
  • the first network element on the network side returns to the tracking area or the routing area to update the accept message to the UE.
  • the first network element on the network side After the first network element on the network side receives the message that the UE has switched to the target access network, if the UE has already performed pre-registration or optimizes the handover process, the first network element on the network side switches the completion message to non- The network element of the 3GPP access network.
  • the UE sends a Binding Update message to the PDN GW.
  • the UE adds the indication bit information in the binding update message to indicate that the PDN GW does not initiate the resource release processing procedure of the UE in the source non-3GPP access network.
  • This indication bit can be an optimized handover or pre-registration indicator bit or a resource not release indicator bit.
  • the specific processing of the indicator bits can be:
  • the PDN GW After receiving the message, the PDN GW does not initiate the resource release processing procedure of the UE in the source non-3GPP access network (ie, the resource release processing in the non-3GPP access network is not triggered by the PDN GW).
  • the resources in the source non-3GPP access network in the PDN GW can be released in the following two ways:
  • PDN GW local release source The resources in the non-3GPP access network do not need to be released by the non-3GPP GW.
  • the PDN GW does not release the resources in the source non-3GPP access network and needs to be released by the non-3GPP GW.
  • the network element in the non-3GPP access network receives the handover complete message sent by the first network element on the network side, and then initiates the source non-3GPP.
  • the resource release processing procedure in the access network ie, the resource release processing in the non-3GPP access network is triggered by the access network element or the non-3GPP GW in the non-3GPP access network. If the resource release processing flow in the source non-3GPP access network is initiated by the access network element in the non-3GPP access network, the access network element in the non-3GPP access network is sent to the non-3GPP GW.
  • the message (such as the resource release request message, the specific message is determined by the specific non-3GPP access network) carries the indication bit information indicating that the resource release process is caused by the non-3GPP access network to the 3GPP access network handover.
  • Indication Bits may have the following specific treatment methods:
  • the non-3GPP GW sends a proxy binding update message to the PDN GW.
  • the proxy binding update message carries the indication bit information indicating that the proxy binding update message is caused by the handover of the non-3GPP access network to the 3GPP access network.
  • the indicator bits may have the following specific treatment methods:
  • the PDN GW After receiving the proxy binding update message, the PDN GW releases resources (such as Binding Cache entry) in the source non-3 GPP access network, and reserves resources in the target 3GPP access network (for example, The bearer resource in the 3GPP access network or the binding cache entry resource, the IP address assigned by the PDN GW to the UE, etc., and the PDN GW does not interact with the PCRF to indicate that the PCRF resource has been released.
  • resources such as Binding Cache entry
  • the target 3GPP access network for example, The bearer resource in the 3GPP access network or the binding cache entry resource, the IP address assigned by the PDN GW to the UE, etc.
  • the PDN GW returns a proxy binding acknowledgement message to the non-3GPP GW.
  • the non-3GPP GW returns a resource release response message to the access network element in the non-3GPP access network.
  • the message between the Serving GW and the PDN GW will be an internal message.
  • step 12 There is no sequence relationship between step 12 and step 13, and there is no sequential relationship between step 16 and step 25.
  • the PDN GW receives the message sent by the Serving GW, and if the UE finds that the PC has the PCC rule in the PDN GW, the PDN GW The stored PCC rule or the modified PCC rule (the PDN GW contacts the PCRF to obtain the modified PCC rule) initiates the network-side dedicated bearer activation procedure to establish a dedicated bearer corresponding to the PCC rule, that is, creates a service used by the UE in the original non-3GPP access system. Resources required in 3GPP systems.
  • the PDN GW initiates a resource release processing procedure in the source non-3GPP access network (ie, the resource release processing in the non-3GPP access network is triggered by the PDN GW), and releases the resources in the source non-3GPP access network.
  • the Serving GW obtains the PCC rule from the PCRF, and the Serving GW initiates the network-side dedicated bearer activation procedure to establish the resource corresponding to the PCC rule according to the acquired PCC rule, that is, the service used by the UE in the original non-3GPP access system is created in the 3GPP system. Resources needed.
  • the UE also initiates pre-registration or optimizes the handover procedure to the non-3 GPP access network element through the 3GPP network when the UE resides in the 3GPP network, and the non-3GPP access network element carries when creating the access request to the non-3GPP gateway network element.
  • the indication bit indicates the type of processing of the access request (pre-registration or the type of optimized handover processing between the non-3GPP network and the 3GPP network)
  • the non-3GPP gateway network element performs resource creation processing according to the indication bit after receiving the message.
  • the specific process is shown in Figure 9, including:
  • the UE is registered in the 3GPP access network.
  • the UE initiates a pre-registration or optimization handover process of the non-3GPP access system.
  • the UE performs a non-3GPP access network specific attach procedure, authentication, and authentication procedure through the 3GPP access network. If necessary, the UE performs an IPSec tunnel establishment procedure.
  • the Non-3GPP gateway in this step is an Evolved Packet Data Gateway (EPDG); for the Wimax system, the Non-3GPP gateway in this step is an ASN GW (Access Service Network). Gateway, Access Service Network Gateway); for the CDMA system, the Non-3GPP gateway in this step is an access gateway (AGW, Access Gateway); for the HRPD network, the Non-3GPP gateway in this step is packet data.
  • Service Node PDSN, Packet Data Serving Node).
  • the UE may carry the indication bit information in the message of this step to indicate that the execution of the step is caused by the inter-system optimized handover or pre-registration of the 3GPP access network to the non-3GPP access network, and the specific processing manner of the indication bit may be:
  • the network element in the non-3GPP access network If the UE does not carry the optimized handover or pre-registration indicator bit information in the message of this step, and the network element in the non-3GPP access network discovers that the message of this step is sent from the network-side first network element in the 3GPP access network, Then, the network element in the non-3GPP access network considers that the non-3 GPP access network specific attach procedure is caused by inter-system optimized handover or pre-registration of the 3GPP access network to the non-3GPP access network.
  • the access network element in the non-3GPP access network learns the access type (optimized handover or pre-registration) of the UE in this step, the access network element in the non-3GPP access network is sent to non-3GPP.
  • the message of the GW carries the indication bit information to indicate the access type of the UE.
  • the specific processing of the indicator bit can be:
  • the "Attach Type” field is added, and the access NE in the non-3GPP access network sets the value of this field to "Optimized Handover Attach” or "Pre-registration Attach".
  • the "Cause” field is added, and the access network element in the non-3GPP access network sets the value of this field to "Optimized Handover” or "Pre-registration”.
  • the non-3GPP GW sends a Gateway Control and Quality of Service Policy Rule Request message to the PCRF to obtain the PCC rules used by the UE in the non-3GPP access network.
  • the PCRF back gateway control and quality of service policy rule response message is sent to the non-3GPP GW, and the message carries the PCC rules used by the UE in the non-3GPP access network.
  • the UE triggers the layer 3 attach procedure in the non-3GPP access network through the 3GPP access network.
  • the UE may carry the indication bit information in the message of this step to indicate that the execution of the step is caused by the inter-system optimized handover or pre-registration of the 3GPP access network to the non-3GPP access network.
  • the indication bit For the specific processing manner of the indication bit, refer to step 2 Description in .
  • the network element in the non-3GPP access network If the UE does not carry the optimized handover or pre-registration indicator bit information in the message of this step, and the network element in the non-3GPP access network discovers that the message of this step is sent from the network-side first network element in the 3GPP access network, The network element in the non-3GPP access network considers that the non-3 GPP access network specific attach procedure is due to the inter-system optimized handover of the 3GPP access network to the non-3GPP access network or Pre-registration caused.
  • the access network element in the non-3GPP access network learns the access type (optimized handover or pre-registration) of the UE in this step, the access network element in the non-3GPP access network is sent to non-3GPP.
  • the message of the GW carries the indication bit information to indicate the access type of the UE. See the description in step 2 for the specific processing of the indicator bits.
  • the access network element in the non-3GPP GW or non-3GPP access network indicates that the UE layer 3 is attached.
  • the non-3GPP gateway network element sends a create resource request message according to the obtained PCC rule to the non-3GPP access network element to initiate a network side dedicated bearer activation procedure to establish a resource corresponding to the PCC rule.
  • the addition of an indication bit in the message indicates the type of processing the resource was created (pre-registration or optimized handover processing type).
  • the specific processing of the indicator position can be:
  • the non-3GPP access network element After receiving the above message, the non-3GPP access network element establishes resources between the local network element and the non-3GPP gateway network element. If the non-3GPP access network element finds that the resource establishment request is due to resource establishment due to pre-registration or optimization handover, the non-3GPP access network element does not notify the UE to establish a radio resource (Radio Resource). The non-3GPP access network element then creates a resource response message to the non-3GPP gateway network element.
  • Radio Resource Radio Resource
  • the non-3GPP GW does not receive the message in the layer 3 attach procedure.
  • the sending proxy binds the update message to the PDN GW (ie, does not notify the PDN GW to switch the downstream user plane path to the Serving GW).
  • the UE moves to the non-3 GPP access network, and the UE transmits the access message related to the non-3GPP access network to the non-3GPP GW through the access network element in the non-3 GPP access network.
  • the non-3GPP GW sends a proxy binding update message to the PDN GW.
  • the non-3GPP GW adds indicator bit information in the proxy binding update message to indicate that the PDN GW does not initiate The resource release processing procedure of the UE in the source 3GPP access network.
  • This indicator bit can be an optimized handover or pre-registration indicator bit or a resource not release indicator bit.
  • the specific processing of the indicator bits can be:
  • the PDN GW After receiving the above message, the PDN GW obtains the PCC rule saved by the UE in the gateway. Determine whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW sends an IP-CAN session modification request message to the PCRF to obtain the UE in the non-3 GPP interface. Enter the PCC rules used within the network. The PCRF returns an IP-CAN session modification confirmation message to the PDN GW, which carries the PCC rules used by the UE in the non-3GPP access network.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW does not initiate the resource release processing procedure of the UE in the source 3GPP access network (ie, 3GPP connection)
  • the resource release process in the incoming network is not triggered by the PDN GW).
  • the resources in the source 3GPP access network in the PDN GW can be released in the following two ways:
  • PDN GW local release source 3GPP accesses resources in the network without the need for Serving GW notification release.
  • the PDN GW does not release the resources in the source 3GPP access network, and needs to be released by the Serving GW. 11.
  • the PDN GW returns a proxy binding acknowledgement message to the non-3GPP GW.
  • the UE sends a Binding Update message to the PDN GW.
  • the UE adds the indication bit information in the binding update message to indicate that the PDN GW does not initiate the resource release processing procedure of the UE in the source 3GPP access network.
  • This indicator bit can be an optimized handover or pre-registration indicator bit or a resource not release indicator bit.
  • the specific processing manner of the indication bit refer to the description in Embodiment 6.
  • the PDN GW does not initiate the resource release processing procedure of the UE in the source 3GPP access network (ie, the resource release processing in the 3GPP access network is not triggered by the PDN GW).
  • the resources in the source 3GPP access network in the PDN GW (such as the Binding Cache entry or the bearer context resource in the source 3GPP access network) can be released in the following two ways:
  • PDN GW local release source 3GPP accesses resources in the network without the need for Serving GW notification release.
  • the PDN GW does not release the resources in the source 3GPP access network, and needs to be released by the Serving GW. 13. After receiving the above message, the PDN GW obtains the PCC rule saved by the UE in the gateway. Determine whether the PCC rule is related to the IP-CAN (IP-Connectivity Access Network) access type. If relevant, the PDN GW contacts the PCRF to obtain the modified PCC rule. For details, see the description in step 10.
  • IP-CAN IP-Connectivity Access Network
  • the PDN GW returns a binding confirmation message to the UE.
  • the access network element of the non-3GPP access network or the non-3GPP GW receives the message that the UE has switched to the target access network, if it finds that the UE has performed pre-registration or optimizes the handover process, the non-3GPP The access network element of the access network or the non-3GPP GW sends a handover complete message to the first network element on the network side of the 3GPP access network.
  • the first network element on the network side of the 3GPP access network receives the handover completion message sent by the access network element of the non-3GPP access network or the non-3GPP GW, and initiates a resource release processing process in the source 3GPP access network ( That is, the resource release processing in the 3GPP access network is triggered by the first network element on the network side of the 3GPP access network.
  • the first network element on the network side of the 3GPP access network sends a delete bearer request or deletes a PDP context request message to the Serving GW.
  • the bearer request or the delete PDP context request message carries the indication bit information indicating that the bearer deletion process is caused by the 3GPP access network switching to the non-3GPP access network.
  • the indicator bits may have the following specific treatment methods:
  • the delete bearer request message (the interface protocol between the Serving GW and the PDN GW uses the GTP protocol) or the proxy binding update message (the interface protocol between the Serving GW and the PDN GW uses the PMIP protocol) to the PDN GW.
  • the bearer request message or the bearer binding update message carries the indication bit information indicating that the bearer deletion process is caused by the 3GPP access network to the non-3GPP access network handover.
  • the indicator bits may have the following specific treatment methods:
  • the Serving GW sets the "Delete Type” or "Binding Type” indication bit to "inter RAT Handover from 3 GPP to non-3 GPP".
  • the PDN GW After receiving the above-mentioned delete bearer request or proxy binding update message, the PDN GW releases the resources in the source 3GPP access network (such as binding the cache entry resource (if the interface protocol between the Serving GW and the PDN GW uses the PMIP protocol) Or bear the context resource (if the interface protocol between Serving GW and PDN GW uses GTP)), retain the resources in the destination non-3GPP access network
  • the binding cache entry resource in the non-3GPP access network the IP address assigned by the PDN GW to the UE, etc.
  • the PDN GW does not interact with the PCRF to indicate that the PCRF resource has been released.
  • the PDN GW returns the bearer response or proxy binding acknowledgement message to the Serving GW.
  • the Serving GW returns the bearer response or deletes the PDP context response message to the first network element on the network side.
  • step 6 There is no sequence relationship between step 6 and step 7. There is no precedence relationship between step 9 and step 15.
  • the non-3GPP gateway network element If the processing type information of the registration request is not carried and the non-3GPP gateway network element obtains the PCC rule from the PCRF, the non-3GPP gateway network element initiates the network side dedicated bearer activation procedure according to the acquired PCC rule to establish a PCC rule.
  • Resources that is, resources needed to create services used by the UE in the original 3GPP access system in the non-3GPP system.
  • the PDN GW initiates a resource release processing procedure in the source 3GPP access network (ie, the resource release processing in the 3GPP access network is triggered by the PDN GW), and the source 3GPP is to be used.
  • the resources in the access network are released.
  • a schematic structural diagram of a network device 1 is attached. As shown in Figure 10, it includes:
  • the access request determining unit 701 is configured to determine that the access request initiated by the user equipment is an initial access request, or is a handover request between the non-3GPP access system and the 3GPP access system, and send the determined result to The processing type notification unit 702;
  • the processing type notification unit 702 is configured to receive the result sent by the access request determining unit 701, determine a corresponding processing type for creating a resource for the user equipment, and notify the network side to create a corresponding network element for the user equipment.
  • the above processing type notification unit 702 may further include: a first notification subunit 703 and/or a second notification subunit 704;
  • the first notification sub-unit 703 is configured to carry a flag bit in the sent bearer creation request message, the proxy binding update message, or the binding update message, indicating that the processing type of the bearer creation is the first/second creation type, or indicating that the binding is The processing type of the update is the first/second binding type;
  • the second notification sub-unit 704 is configured to send a specific message, indicating that it is required to create a resource required by the user equipment to access the service used in the system before the handover.
  • the above network device 1 may be integrated in the mobility management entity MME in the evolved network; or integrated in the serving GPRS support node SGSN; or integrated in the non-3GPP gateway; or integrated in the user equipment.
  • FIG. 11 is a schematic structural diagram of another network device 2, including: a parsing unit 801 and a resource creation processing unit 802; wherein:
  • the parsing unit 801 is configured to parse the processing type specified in the received message for the user equipment to create a resource; and notify the parsed processing type to the resource creation processing unit 802;
  • the resource creation processing unit 802 is configured to receive a processing type sent by the parsing unit 801, and perform a process of creating a corresponding resource for the user equipment.
  • the parsing unit 801 may further include: a first parsing subunit 803 and/or a second parsing subunit 804. among them:
  • a first parsing sub-unit 803 configured to parse a flag bit carried in the received bearer creation request message, the proxy binding update message, or the binding update message, and determine the first/second creation type or the first according to the flag bit a first/second binding type; and sending the parsed first/second creation type or the first/second binding type to the resource creation processing unit;
  • the second parsing sub-unit 804 is configured to parse the received specific message, where the specific message indicates that the resource required for the service used by the user equipment in the access system before the handover is required to be created; and the resource creation processing unit 802 is notified to the user.
  • the device creates a resource required for the service used in the access system before the handover; the resource creation processing unit 802, after receiving the first creation type or the first binding type sent by the first parsing sub-unit 803, creates a user equipment.
  • the resource creation processing unit 802 After the resource creation processing unit 802 receives the notification sent by the second creation type, the second binding type, or the second parsing sub-unit 804 sent by the first parsing sub-unit 803, the user equipment is created before the handover.
  • the resources required for the business used in the system are the resources required for the business used in the system.
  • the above network device 2 can be integrated in a packet data network gateway entity.
  • the first network element on the network side obtains the PDN GW address information used by the UE from the HSS, and then sends a message to notify the PDN GW to release the resources used by the UE. After receiving the message, the PDN GW releases the resources used by the UE.
  • the specific process is shown in Figure 12, including:
  • the UE sends an attach request message to the first network element on the network side to perform initialization access network processing.
  • the first network element on the network side is the MME
  • the first network element on the network side is the SGSN.
  • the authentication process is performed between the UE, the first network element on the network side, and the HSS/AAA Server.
  • the first network element on the network side and the HSS/AAA Server perform location update and subscription data acquisition processes.
  • the first network element on the network side acquires the PDN GW address information used by the UE in the non-3GPP access system.
  • the HSS/AAA Server sends the PDN GW address information used by the UE in the non-3GPP access system to the first network element on the network side.
  • the first network element on the network side obtains the PDN GW address information used by the UE from the HSS, and sends a resource release request message to the PDN GWs, requesting the PDN GWs to release the resources used by the UE.
  • the message carries the identity of the UE (such as the user's IMSI).
  • the resource release request message is forwarded to the PDN GW by the Serving GW.
  • the first network element on the network side sends a resource release request message to a selected Serving GW, where the message carries the PDN GW address information obtained by the first network element on the network side from the HSS.
  • the Serving GW then sends a resource release request message to each PDN GW.
  • the resource release request message carries the identity of the UE (such as the IMSI of the UE).
  • the PDN GW queries whether the UE has a PCC rule in the gateway. If it exists, then The PDN GW deletes the PCC rule of the saved UE, and notifies the PCRF to delete the saved PCC rule of the UE. For details, refer to the description in Embodiment 1.
  • the PDN GW returns a resource release response message to the first network element on the network side.
  • the resource release request message is forwarded to the first network element on the network side by the Serving GW.
  • the PDN GW sends a resource release request message to the non-3GPP gateway network element, requesting to release resources allocated by the non-3GPP network for the UE.
  • the non-3GPP gateway network element is EPDG; for the Wimax system, the non-3GPP gateway network element is the ASN GW; for the CDMA system, the non-3GPP gateway network element is the AGW.
  • the non-3GPP gateway device initiates a resource release procedure, and releases resources allocated by the non-3GPP network for the UE.
  • the non-3GPP gateway returns a resource release response message to the PDN GW.
  • the PDN GW releases the resources allocated for the UE.
  • the PDN GW initiates a resource release procedure to release resources allocated by the 3GPP network to the UE.
  • the PDN GW sends a resource release request message to the Serving GW to request the 3GPP network to release the resources allocated for the UE.
  • the Serving GW initiates a resource release procedure to release resources allocated by the 3GPP network to the UE.
  • Serving GW returns the resource release response to the PDN GW.
  • the PDN GW releases the resources allocated for the UE.
  • the message between the GWs will be an internal message within the entity.
  • step 7 There is no sequential relationship between step 7 and step 6.
  • the first network element on the network side obtains the PDN GW address information used by the UE from the HSS, and then sends a message to notify the PDN GW to release the resources used by the UE. After receiving the message, the PDN GW releases the resources used by the UE.
  • the specific process is shown in Figure 13, including: 1.
  • the UE sends an access request message to the non-3GPP gateway network element to perform a process of initializing access to the non-3GPP system.
  • the non-3GPP gateway network element is the EPDG
  • the non-3GPP gateway network element is the ASN GW
  • the non-3GPP gateway network element is the AGW.
  • the access authentication process is performed between the UE, the non-3GPP gateway network element, and the HSS/AAA Server.
  • the server sends the PDN GW address information used by the UE in the 3GPP access system to the non-3GPP gateway network element.
  • the non-3GPP gateway network element obtains the PDN GW address information used by the UE from the HSS, and then sends a resource release request message to the PDN GW to request the PDN GW to release the resources used by the UE.
  • the message carries the identity of the UE (such as the user's IMSI).
  • the PDN GW queries whether the UE has a PCC rule in the GW. If it exists, the PDN GW deletes the PCC rule existing by the UE, and notifies the PCRF to delete the saved PCC rule.
  • the PDN GW returns a resource release command to the non-3GPP gateway network element.
  • the PDN GW initiates a resource release procedure to release the resources allocated by the original network to the UE.
  • the PDN GW sends a resource release request message to the Serving GW to request the 3GPP network to release the resources allocated for the UE.
  • the Serving GW initiates a resource release procedure to release resources allocated by the 3GPP network to the UE.
  • Serving GW returns the resource release response to the PDN GW.
  • the PDN GW releases the resources allocated for the UE.
  • the PDN GW sends a resource release request message to the non-3GPP gateway device to request to release the resources allocated by the non-3GPP network for the UE.
  • the non-3GPP gateway network element is an EPDG (Evolved Packet Data Gateway); for the Wimax system, the non-3GPP gateway network element is an ASN GW (Access Service Network Gateway, Access Service Network Gateway)
  • the non-3GPP gateway network element is an AGW (Access Gateway, Access Gateway).
  • the non-3GPP gateway device initiates a resource release procedure, releasing the non-3GPP network to allocate the UE Resources.
  • the non-3GPP gateway returns a resource release response message to the PDN GW.
  • the PDN GW releases the resources allocated for the UE.
  • a schematic structural diagram of a network device 3 is as shown in FIG. 14, and includes: an initialization request determining unit 121, a network element address obtaining unit 122, and a resource release notification unit 123;
  • the initialization request determining unit 121 is configured to determine that the access request initiated by the user equipment is an initial access request; and notify the network element address obtaining unit 122;
  • the network element address obtaining unit 122 is configured to acquire the anchor point gateway network element address information used by the user equipment, and send the information to the resource release notification unit 123;
  • the resource release notification unit 123 is configured to send a resource release notification message to the anchor gateway network element according to the address information sent by the network element address obtaining unit 122, requesting to release the resource allocated to the user equipment.
  • the network element address obtaining unit 122 may further include: a first subunit 1221 and a second subunit 1222; wherein:
  • the first subunit 1221 is configured to obtain the anchor gateway address information used by the user equipment from the home network server HSS of the user equipment, and send the information to the second subunit 1222.
  • a second subunit 1222 storing and transmitting anchor gateway address information to the resource release notification unit
  • the resource release notification unit 123 may further include: a determination subunit 1231, a first transmission subunit 1232, and a second transmission subunit 1233; wherein:
  • the determining subunit 1231 is configured to determine whether an interface exists with the anchor gateway, and if there is an interface, notify the first sending subunit 1232 to send the resource release notification message to the anchor gateway; If the interface exists, the second sending sub-unit 1233 is notified to send the resource release notification message to the serving gateway, and the service gateway forwards the message to the anchor gateway;
  • the first sending sub-unit 1232 is configured to send the resource release notification message to the anchor gateway
  • the second sending sub-unit 1233 is configured to send the resource release notification message to the serving gateway.
  • a schematic structural diagram of a network device 4 is as shown in the figure
  • resource release message parsing unit 131 is configured to: parse the received resource release notification message, and send Giving the resource release execution unit 132;
  • the resource release execution unit 132 is configured to release resources allocated to the user equipment.
  • the network device 4 may further include a query unit 133 and a deleting unit 134; wherein:
  • the resource release message parsing unit 131 is further sent to the query unit 133 after parsing out the resource release notification message;
  • the query unit 133 is configured to query whether the policy and charging control rule of the user equipment is saved locally; if yes, notify the deleting unit 134;
  • the deleting unit 134 is configured to delete the policy and charging control rule of the locally saved user equipment, and notify the network side policy and charging rule function entity to delete and save the corresponding rule.
  • the network device 4 can be integrated in the anchor gateway PDN GW.
  • the resource creation method provided by the embodiment of the present invention, the first network element notifies the second network element on the network side to create a processing type of the resource for the user equipment, and the second network element is configured according to the processing type.
  • the user equipment performs a process of creating a corresponding resource.
  • a resource deletion method is proposed, in which the first network element on the network side obtains the second network element address information of the network side used by the UE from the network element that is saved by the second network element address information on the network side, and the first network element on the network side Sending a message to notify the acquired second network element on the network side to release the resource, and the second network element on the network side releasing the resource.
  • the network side gateway network element ie, the second network element in the prior art cannot identify different access requests (ie, initializing the access request and the access request caused by the access system switching;), and thus cannot be different for different The problem of access requests creating corresponding resources and the problem of resource deletion when initializing access.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • ROM read-only memory
  • RAM random access memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种资源创建方法、 资源删除方法及网络设备 技术领域
本发明涉及通信技术领域， 尤其涉及一种资源的创建方法及网络设备。 背景技术
3GPP为了增强未来网络的竟争能力， 正在研究一种全新的演进网络， 其系 统架构示意如附图 1 所示， 包括演进的通用移动通信系统（UMTS , Universal Mobile Telecommunications System )陆地无线接入网（ E-UTRAN, Evolved UMTS Terrestrial Radio Access Network ), 用于实现所有与演进网络无线有关的功能； 移动性管理实体（MME, Mobility Management Entity ), 负责控制面的移动性管 理， 包括用户上下文和移动状态管理， 分配用户临时身份标志等； 服务网关实 体（ Serving GW, Serving Gateway ), 是 3GPP接入系统间的用户面锚点， 终止 E-TURAN 的接口； 分组数据网络网关实体（PDN GW, Packet Data Network Gateway, 一般也称之为锚点网关）是 3GPP接入系统和非 3GPP接入系统之间 的用户面锚点， 终止和外部分组数据网络（ PDN, Packet Data Network )的接口。 策略和计费规则功能实体（ PCRF, Policy and Charging Rule Function )用于策略 控制决定和流计费控制功能。 归属网络服务器（HSS , Home Subscriber Server ) 用于存储用户签约信息。
UMTS陆地无线接入网（ UTRAN, UMTS Terrestrial Radio Access Network )、 GSM/EDGE无线接入网 ( GERAN, GSM/EDGE Radio Access Network ), 用于实 现所有与现有 GPRS/UMTS 网络中无线有关的功能。 服务通用分组无线业务支 持节点 （ SGSN, Serving GPRS Supporting Node ), 用于实现 GPRS/UMTS网络 中路由转发、 移动性管理、 会话管理以及用户信息存储等功能。
非 3GPP IP接入网络（ Non-3GPP IP Access ), 主要是一些非 3GPP组织定义 的接入网络， 如无线局域网 （WLAN, Wireless Local Area Network ), 微波存取 全球互通 ( Wimax, Worldwide Interoperability for Microwave Access )等网络。
认证、 4受权与计费月良务器 ( AAA Server, Authentication, Authorization and Accounting Server )用于对用户设备 ( UE, User Equipment )执行接入认证、 4受权 和计费功能。 演进网络的一个需求是实现 3GPP的接入系统（ GERAN/UTRAN/E-UTRAN ) 和非 3GPP接入系统（如 WLAN/Wimax等）之间的切换（ Handover )。 该切换 流程通过 UE在新接入系统中的附着 （Attach ) 流程来完成， 附图 2是非 3GPP 到 3GPP系统切换流程的流程图。 包括以下步骤：
1. UE通过非 3GPP ( Non-3GPP )网关和 PDN GW接入到 Non-3GPP接入 网络。
2. UE发起非 3GPP接入系统到 SAE接入系统之间的切换。
3. UE发送附着请求（ Attach Request ) 消息到 MME。
4. UE、 MME、 HSS/AAA Server之间执行鉴权流程。
5. MME与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流 程中 MME获取 UE在非 3GPP接入系统中使用的 PDN GW地址信息。
6. MME发送创建缺省 7 载请求消息到 Serving GW。
7a.如果 Serving GW与 PDN GW之间的接口使用 GPRS隧道协议（GTP, GPRS Tunneling Protocol ), 则 Serving GW发送创建缺省承载请求消息给 PDN GW。
7b.如果 Serving GW 与 PDN GW之间的接口使用代理移动因特网协议 ( PMIP, Proxy Mobile Internet Protocol ), 则 Serving GW发送代理绑定更新 ( Proxy Binding Update ) 消息给 PDN GW。
8a.如果 Serving GW与 PDN GW之间的接口使用 GTP协议，则 PDN GW返 回创建缺省承载响应消息给 Serving GW。
8b.如果 Serving GW与 PDN GW之间的接口使用 PMIP协议， 则 PDN GW 发送代理绑定确认 ( Proxy Binding Ack ) 消息给 Serving GW。
9. Serving GW返回创建缺省承载响应消息给 MME。
10. MME发起无线承载建立程序建立缺省承载对应的无线承载及附着完成 程序。
注： （ 1 )上述非 3GPP到 SAE以及其它 3GPP系统（如 GPRS/UMTS系统 ) 的切换流程可使用但不局限于 Attach流程来完成， 实际上它也可以通过其它的 流程来完成。
( 2 )如果 Serving GW和 PDN GW在一个实体上实现， 则 Serving GW和 PDN GW之间的消息就将是一个实体的内部的消息。 本发明人在实施本发明过程中发现， 上述现有技术中存在如下缺点：
1. 从非 3GPP到 3GPP系统的切换时为了保证 UE业务的连续性， 3GPP系 统需将 UE在 non-3GPP接入系统中的使用的资源在 3GPP系统中恢复出来， 但 是现在的非 3GPP到 3GPP系统的切换流程中还没有这样的机制。
2. 正常的 3GPP接入流程中 3GPP系统只创建 UE的缺省承载，而从非 3GPP 到 3GPP系统的切换接入时 3GPP系统需将 UE在非 3GPP系统中的资源恢复出 来。 所以对于这两种接入处理时是不一样的， 3GPP系统需要区分这两种不同的 处理方式， 但是现在的 3GPP系统中还没有相应的机制来区分处理。
3.现有 3GPP系统中的接入流程中的处理是 UE只发起一个缺省承载的建立， 也就是说 MME只能对一个 PDN GW发起缺省承载创建流程。如果 UE在非 3GPP 接入系统中使用了多个 PDN GW, 则现有机制无法处理。
4. 现有技术中非 3GPP和 3GPP系统之间的切换是一种 "松耦合" 的切换， 也就是 UE先从源侧系统中断开，从目标侧系统中通过接入流程来完成切换。这 种切换方式会造成业务中断的时间比较长， 有可能导致业务中断。 如何优化非 3GPP和 3GPP系统之间的切换， 减少 UE业务中断的时间， 现有技术中还没有 相应的机制来处理。
5. 当 UE在非 3GPP接入系统接入时， 非 3GPP接入系统为 UE分配资源。 当 UE异常关机或者异常掉网时， 非 3GPP接入系统为 UE分配的资源将不能被 释放掉。 当 UE重新在 3GPP接入系统接入时， 非 3GPP接入系统为 UE分配的 资源需要被释放掉， 但是现有技术中没有相应的处理机制。 发明内容
本发明实施例提供一种资源创建方法、 资源删除方法及网络设备， 实现区 分用户设备的初始化接入流程和切换流程， 从而执行相应的资源处理。
本发明实施例公开的一种资源创建方法， 包括步骤：
当用户设备在第三代合作伙伴计划 3GPP网络和非 3GPP网络之间切换或发 起初始化接入请求时， 由第一网元通知网络侧第二网元为用户设备创建资源的 处理类型； 根据所述资源的处理类型， 所述第二网元为所述用户设备进行相应 资源的创建处理。
本发明另一个实施例公开了一种异构网络切换时的资源恢复处理方法， 包 括步骤：
当用户设备在第三代合作伙伴计划 3GPP网络和非 3GPP网络之间切换或发 起初始化接入请求时， 网络侧网关设备获取用户设备在目标接入系统使用的策 略和计费控制规则；
网络侧网关设备根据所述的策略和计费控制规则在目标接入系统发起网络 侧承载建立程序。其中网络侧网关可以为服务网关、锚点网关或者非 3GPP网关 设备。
本发明实施例还公开了一种资源删除方法， 包括：
当用户设备在 3GPP 网络和非 3GPP 网络之间切换或发起初始化接入请求 时， 第一网元获取第二网元地址信息； 所述第一网元发送消息通知所述第二网 元释放分配给用户设备的资源； 所述第二网元释放分配给用户设备的资源。 还 可以包括确定出用户设备发起的接入请求为初始化接入请求的步骤。
本发明实施例还公开了另一种资源删除方法， 包括：
当用户设备在 3GPP 网络和非 3GPP 网络之间切换或发起初始化接入请求 时， 目标接入网络网元通知用户面锚点不发起源接入网络的资源释放处理； 在 UE切换到目标接入网络后， 目标接入网络网元向源接入网络网元发送消息， 通 知源网络 UE已经切换到目标接入网络；源网络网元收到所述通知后发起源网络 的资源释放处理。
相应地， 本发明实施例公开了一种网络资源处理的网络设备， 包括： 接入 请求确定单元和处理类型通知单元； 其中：
接入请求确定单元， 用于确定出用户设备发起的接入请求为初始化接入请 求， 或为非 3GPP接入系统与 3GPP接入系统之间的切换请求； 并将确定出的结 果发送给所述处理类型通知单元；
处理类型通知单元， 用于接收所述接入请求确定单元发送的结果， 确定出 为用户设备创建资源的对应处理类型， 并通知给网络侧为用户设备创建资源的 相应网元。
本发明实施例还公开了另一种处理网络资源的网络设备， 包括： 解析单元 和资源创建处理单元； 其中： 解析单元， 当用户设备在 3GPP网络和非 3GPP网 络之间切换或发起初始化接入请求时， 用于从对端网元接收消息， 并从消息中 解析出为用户设备创建资源的处理类型； 并将解析出的处理类型通知给所述资 源创建处理单元； 资源创建处理单元， 用于接收所述解析单元发送的处理类型， 为用户设备进行相应资源的创建处理。
本发明实施例还公开了一种网络资源释放处理的设备， 包括： 初始化请求 确定单元、 网元地址获取单元和资源释放通知单元； 其中： 初始化请求确定单 元， 当用户设备在 3GPP网络和非 3GPP网络之间切换时， 用于确定出用户设备 发起的接入请求为初始化接入请求； 并通知给所述网元地址获取单元； 网元地 址获取单元， 用于获取用户设备使用的锚点网关网元的地址信息， 并发送给所 述资源释放通知单元； 资源释放通知单元， 用于根据所述网元地址获取单元发 送的地址信息， 向所述锚点网关网元发送资源释放通知消息， 请求释放分配给 所述用户设备的资源。
本发明最后还公开了一种用于网络资源释放处理的网络设备， 包括： 资源 释放消息解析单元和资源释放执行单元； 其中： 资源释放消息解析单元， 当用 户设备在 3GPP网络和非 3GPP网络之间切换或发起初始化接入请求时，用于解 析出接收的资源释放通知消息， 并发送给所述资源释放执行单元； 资源释放执 行单元， 用于释放分配给用户设备的资源。
釆用本发明实施例提供的资源创建方案， 由第一网元通知网络侧第二网元 为用户设备创建资源的处理类型； 所述第二网元根据所述处理类型为所述用户 设备进行相应资源的创建处理。 从而解决现有技术中网络侧网关网元（即第二 网元） 不能识别不同的接入请求 （即初始化接入请求和由于接入系统切换导致 的接入请求 ), 因而不能针对不同的接入请求创建相应资源的问题。
釆用本发明实施例提供的资源删除方案， 由第一网元从第二网元地址信息 保存的网元中获取第二网元地址信息； 所述第一网元发送消息通知所述第二网 元释放分配给用户设备的资源； 所述第二网元释放分配给用户设备的资源。 使 得 UE异常关机或者异常掉网后，在后续初始化接入过程中， 实现删除锚点网关 上保存的 UE使用的 PCC规则及分配的资源。 附图说明
图 1为现有技术演进网络系统架构示意图；
图 2为现有技术中由非 3GPP系统到 3GPP系统的切换流程图；
图 3为本发明实施例一资源创建信令交互流程图。 图 4为本发明实施例二资源创建信令交互流程图；
图 5为本发明实施例三资源创建信令交互流程图；
图 6为本发明实施例四资源创建信令交互流程图；
图 7为本发明实施例五资源创建信令交互流程图；
图 8为本发明实施例六资源创建信令交互流程图；
图 9为本发明实施例七资源创建信令交互流程图；
图 10为本发明实施例网络设备一结构示意图；
图 11为本发明实施例网络设备二结构示意图；
图 12为本发明实施例八资源删除信令交互流程图；
图 13为本发明实施例九资源删除信令交互流程图；
图 14为本发明实施例网络设备三结构示意图；
图 15为本发明实施例网络设备四结构示意图。 具体实施方式 实施例一：
网络侧第一网元在发送创建缺省承载请求 （或者创建缺省分组数据协议 ( PDP, Packet Data Protocol )上下文请求）到服务网关 （ Serving GW ) 时携带 标志位时表明创建承载（或者创建 PDP上下文）的处理类型， Serving GW发送 创建缺省承载请求（或者创建缺省 PDP上下文请求 )到 PDN GW时携带标志位 表明处理类型。 PDN GW收到消息后根据标志位进行不同的流程处理。 具体流 程见附图 3 , 包括：
1、 UE通过 Non-3GPP 网关和 PDN GW接入到 Non-3GPP接入网络。
2、 UE发起非 3GPP接入系统到 3GPP接入系统之间的切换。
3、 UE发送附着请求消息到网络侧第一网元执行非 3GPP到 3GPP系统的切 换流程。 对于系统架构演进（ SAE, System Architecture Evolution ) 系统来说， 网络侧第一网元为 MME, 对于 GPRS/UMTS系统来说， 网络侧第一网元为服务 GPRS支持节点（ SGSN )。 网络侧第一网元可以根据如下方法来确定收到的接入 请求是非 3GPP到 3GPP系统的切换请求还是正常的接入请求（也称初始化接入 请求）： 1 )如果非 3GPP到 3GPP系统的切换流程也是通过 Attach流程来处理的话， 则在 Attach Request消息中增加 Attach Type字段来表明不同的接入处理类型（如 对于正常的接入， Attach Type字段设置为 Initial Attach; 对于切换接入， Attach Type字段设置为 Handover Attach ), 网络侧第一网元根据 Attach Request消息中 的 Attach Type来区分不同的接入流程。
2 )如果 UE在 3GPP或者非 3GPP系统接入时将使用的 PDN GW地址保存 到 UE中，则在正常的接入流程中 Attach Request消息中不携带 PDN GW地址信 息， 在非 3GPP到 3GPP系统的切换流程中 Attach Request消息中携带 PDN GW 地址信息。网络侧第一网元收到 Attach Request消息后根据消息中是否携带 PDN GW地址信息来判断接入请求是正常的接入请求还是切换导致的接入请求。
3 )如果非 3GPP到 3GPP的切换流程处理通过单独的流程而不是通过 Attach 流程处理， 如 UE发送非 3GPP 到 3GPP切换流程请求 （ non-3 GPP to 3GPP Handover Request ) 消息到网络侧第一网元请求 MME进行非 3GPP到 3GPP系 统的切换流程处理。
4、 UE、 网络侧第一网元、 HSS/AAA Server之间执行鉴权流程。
5、 网络侧第一网元与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流程中网络侧第一网元获取 UE在非 3GPP接入系统中使用的 PDN GW 地址信息。
6、对于正常接入的流程， 网络侧第一网元根据用户签约数据中的缺省 APN ( Access Point Name, 接入点名）选择 UE使用的 PDN GW; 对于切换接入的流 程， 网络侧第一网元使用 UE在非 3GPP接入系统中使用的 PDN GW ( PDN GW 地址信息可以由网络侧第一网元从 HSS/AAA Server 中获取或者 HSS/AAA Server将保存的 PDN GW地址信息下发给网络侧第一网元）。如果 3GPP系统为 SAE 系统， 网络侧第一网元发送创建缺省承载请求消息到 Serving GW; 如果 3GPP系统为 GPRS/UMTS系统， 网络侧第一网元发送创建缺省 PDP上下文请 求（ Create Default PDP Context Request ) 消息到 Serving GW。 消息中增加标志 位表明承载创建的处理类型。 标志位的具体处理方式可以有：
1 ) "Create Type" 标志位。 对于正常接入的流程， 其 "Create Type" 标志位 设置为 "Initial Create" ; 对于切换接入的流程， 其 "Create Type" 标志位设置为 "Handover Create"。 2 )"Cause"原因值。对于正常接入的流程，其" Cause"原因值设置为 "Initial" ; 对于切换接入的流程， 其 "Cause" 原因值设置为 "Handover"。
3 ) "Handover Indication" 指示位。 对于切换接入的流程， 网络侧第一网络 增加 "Handover Indication" 指示位以指示这个消息是由于切换接入导致的。 对 于正常接入的流程， 网络侧第一网元不携带这个指示位。
4 ) "Initial Indication" 指示位。 对于正常接入的流程， 网络侧第一网络增加 "Initial Indication"指示位以指示这个消息是由于正常接入导致的。 对于切换接 入的流程， 网络侧第一网元不携带这个指示位。
7、如果 Serving GW与 PDN GW之间的接口使用 GTP协议且 3GPP系统为 SAE系统， 则 Serving GW发送创建缺省承载请求消息给 PDN GW; 如果 3GPP 系统为 GPRS/UMTS,则 Serving GW发送创建缺省 PDP上下文请求消息给 PDN GW。 消息中增加标志位表明承载创建的处理类型。 标志位的具体处理方式可以 有：
1 ) "Create Type" 标志位， 对于正常接入的流程， 其 "Create Type" 标志位 设置为 "Initial Create" ; 对于切换接入的流程， 其 "Create Type" 标志位设置为 "Handover Create"。
2 )"Cause"原因值。对于正常接入的流程，其" Cause"原因值设置为 "Initial" ; 对于切换接入的流程， 其 "Cause" 原因值设置为 "Handover"。
3 ) "Handover Indication" 指示位。 对于切换接入的流程， Serving GW增加 "Handover Indication" 指示位以指示这个消息是由于切换接入导致的。 对于正 常接入的流程， Serving GW不携带这个指示位。
4 ) "Initial Indication"指示位。对于正常接入的流程， Serving GW增加 "Initial Indication" 指示位以指示这个消息是由于正常接入导致的。 对于切换接入的流 程， Serving GW不携带这个指示位。
8、 PDN GW收到消息后判断消息中的承载创建的处理类型信息， 根据承 载创建的处理类型信息进行不同的处理：
1 )如果承载创建的处理类型信息为正常接入导致的承载创建， 则 PDN GW 查询这个 UE在本网关中是否存在策略和计费控制 （PCC, Policy and Charging Control )规则。 如果存在， 则 PDN GW删除 UE存在的 PCC规则， 同时通知 PCRF删除保存的 PCC规则。 同时 PDN GW发起源 non-3GPP接入网络中的资 源释放处理流程， 将源 non-3GPP接入网络中的资源释放。
2 )如果承载创建的处理类型信息为切换接入导致的承载创建， 则 PDN GW 获取这个 UE在本网关内保存的 PCC规则。 判断 PCC规则是否与 IP-CAN ( IP 连通接入网络， IP-Connectivity Access Network )接入类型相关， 如果相关， 则 PDN GW联系 PCRF获取修改的 PCC规则。 同时 PDN GW发起源 non-3GPP接 入网络中的资源释放处理流程， 将源 non-3GPP接入网络中的资源释放。
9、 PDN GW返回创建缺省承载响应消息给 Serving GW。
10、 Serving GW返回创建缺省承载响应消息给网络侧第一网元。
11、 网络侧第一网元发起无线承载建立程序建立缺省承载对应的无线承载 及附着完成程序。
12、 如果接入处理类型为切换导致的接入处理， 则 PDN GW根据保存或者 修改后的 PCC规则发起网络侧专用承载激活程序建立 PCC规则对应的专用承 载， 也就是创建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资 源。
注：
1 )如果 Serving GW和 PDN GW在一个实体上实现，则 Serving GW和 PDN
GW之间的消息就将是一个实体的内部消息。
2 ) 步骤 12与步骤 9之间没有先后时序关系。
3 ) 如果承载创建的处理类型信息未携带，则 PDN GW收到 Serving GW发 送的消息后如果发现 UE在 PDN GW中保存有 PCC规则， 则 PDN GW根据保 存的 PCC规则或者修改后的 PCC规则（ PDN GW联系 PCRF获取修改后的 PCC 规则 )发起网络侧专用承载激活程序建立 PCC规则对应的专用承载， 也就是创 建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资源。同时 PDN GW发起源 non-3GPP接入网络中的资源释放处理流程 , 将源 non-3GPP接入网 络中的资源释放。
实施例二：
网络侧第一网元在发送创建缺省承载请求（或者创建缺省 PDP上下文请求 ) 到 Serving GW时携带标志位时表明创建承载（或者创建 PDP上下文 )的处理类 型， Serving GW发送代理绑定更新消息到 PDN GW时携带标志位表明处理类型。 PDN GW收到消息后根据标志位进行不同的流程处理。具体流程见附图 4,包括： 1、 UE通过 Non-3GPP 网关和 PDN GW接入到 Non-3GPP接入网络。
2、 UE发起非 3GPP接入系统到 3GPP接入系统之间的切换。
3、 UE发送附着请求消息到网络侧第一网元执行非 3GPP到 3GPP系统的切 换流程。 对于 SAE系统来说， 网络侧第一网元为 MME, 对于 GPRS/UMTS系 统来说， 网络侧第一网元为 SGSN。
4、 UE、 网络侧第一网元、 HSS/AAA Server之间执行鉴权流程。
5、 网络侧第一网元与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流程中网络侧第一网元获取 UE在非 3GPP接入系统中使用的 PDN GW 地址信息。
6、对于正常接入的流程， 网络侧第一网元根据用户签约数据中的缺省 APN ( Access Point Name, 接入点名）选择 UE使用的 PDN GW; 对于切换接入的流 程， 网络侧第一网元使用 UE在非 3GPP接入系统中使用的 PDN GW ( PDN GW 地址信息可以由网络侧第一网元从 HSS/AAA Server 中获取或者 HSS/AAA Server将保存的 PDN GW地址信息下发给网络侧第一网元）。如果 3GPP系统为 SAE 系统， 网络侧第一网元发送创建缺省承载请求消息到 Serving GW; 如果 3GPP系统为 GPRS/UMTS系统， 网络侧第一网元发送创建缺省 PDP上下文请 求（ Create Default PDP Context Request ) 消息到 Serving GW。 消息中增加标志 位表明承载创建的处理类型。 标志位的处理同实施例一中的处理。
7、如果 Serving GW与 PDN GW之间的接口使用 PMIP协议，则 Serving GW 发送代理绑定更新 （ Proxy Binding Update ) 消息给 PDN GW。 消息中增加标志 位表明绑定更新的处理类型。 标志位的具体处理方式可以有：
1 )增力。 "Binding Type" 标志位。 对于正常接入的流程， 其 "Binding Type" 标志位设置为 "Initial Binding" ; 对于切换接入的流程， 其 "Binding Type" 标志 位设置为 "Handover Binding"。
2 )"Cause"原因值。对于正常接入的流程，其" Cause"原因值设置为 "Initial" ; 对于切换接入的流程， 其 "Cause" 原因值设置为 "Handover"。
3 ) "Handover Indication" 指示位。 对于切换接入的流程， Serving GW增加 "Handover Indication" 指示位以指示这个消息是由于切换接入导致的。 对于正 常接入的流程， Serving GW不携带这个指示位。
4 ) "Initial Indication"指示位。对于正常接入的流程， Serving GW增加 "Initial Indication" 指示位以指示这个消息是由于正常接入导致的。 对于切换接入的流 程， Serving GW不携带这个指示位。
7a、 该步骤也可以如下处理：
对于 Proxy BU消息不作修改。 当切换接入时 Serving GW发送恢复承载请 求（当 3GPP为 GPRS/UMTS系统）或者恢复 PDP上下文请求（当 3GPP系统 为 SAE系统） 消息给 PDN GW通知 PDN GW恢复 UE使用的承载。
8、 PDN GW收到消息后判断 Proxy BU消息中的绑定更新的处理类型信息 或者判断是否收到恢复承载请求消息， 根据绑定更新的处理类型信息或者是否 收到恢复承载请求消息进行下述不同的处理：
1 )如果 Proxy BU消息中的绑定更新的处理类型信息为正常接入导致的绑 定更新， 则 PDN GW查询这个 UE在 PDN WG中是否存在 PCC (策略和计费控 制， Policy and Charging Control )规则。 如果存在， 则 PDN GW删除 UE存在的 PCC规则，同时通知 PCRF删除保存的 PCC规则。同时 PDN GW发起源 non-3GPP 接入网络中的资源释放处理流程， 将源 non-3GPP接入网络中的资源释放。
2 )如果 Proxy BU消息中的绑定更新的处理类型信息为切换接入导致的绑 定更新或者 PDN GW收到恢复承载请求（或者恢复 PDP上下文请求）消息， 则 PDN GW获取这个 UE在本网关内保存的 PCC规则。 判断 PCC规则是否与 IP-CAN ( IP连通接入网络， IP-Connectivity Access Network )接入类型相关， 如果相关， 则 PDN GW联系 PCRF获取修改的 PCC规则。 同时 PDN GW发起 源 non-3GPP接入网络中的资源释放处理流程， 将源 non-3GPP接入网络中的资 源释放。
9、 PDN GW回代理绑定确认消息给 Serving GW。
9a、如果 PDN GW在先前的步骤中收到 Serving GW发送的恢复承载请求（或 者恢复 PDP上下文请求 ) 消息， 则 PDN GW回恢复承载响应 （或者恢复 PDP 上下文响应） 消息给 Serving GW。
10、 Serving GW回创建缺省承载响应消息给网络侧第一网元。
11、 网络侧第一网元发起无线承载建立程序建立缺省承载对应的无线承载 及附着完成程序。
12、如果接入处理类型为切换导致的接入处理， 则 PDN GW发送 PCC规则 提供消息给 Serving GW将保存或者修改后的 PCC规则提供给 Serving GW。 Serving GW保存收到的 PCC规则，然后回 PCC规则提供确认消息给 PDN GW。 13、 Serving GW根据收到的 PCC规则发起网络侧专用承载激活程序建立
PCC规则对应的专用承载，也就是创建 UE在原非 3GPP接入系统使用的业务在
3GPP网络中需要的资源。
注：
1 )如果 Serving GW和 PDN GW在一个实体上实现，则 Serving GW和 PDN
GW之间的消息就将是一个实体内部的消息。
2 ) 步骤 12与步骤 9之间没有先后时序关系。
3 ) PDN GW如何将 PCC规则传递给 Serving GW本实施例不作限定。
4 )如果承载创建或者绑定更新的处理类型信息未携带， 则 PDN GW收到 Serving GW发送的消息后如果发现 UE在 PDN GW中保存有 PCC规则，则 PDN GW将保存的 PCC规则或者修改后的 PCC规则（ PDN GW联系 PCRF获取修改 后的 PCC规则）通知给 Serving GW, Serving GW根据收到的 PCC规则发起网 络侧专用承载激活程序建立 PCC规则对应的专用承载， 也就是创建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资源。
实施例三：
非 3GPP ( non-3 GPP ) 网关网元在发送代理绑定更新消息到 PDN GW时携 带标志位表明处理类型。 PDN GW收到消息后根据标志位进行不同的流程处理。 具体流程见附图 5 , 包括：
1、 UE通过 Serving GW和 PDN GW接入到 3GPP接入网络。
2、 UE发起 3GPP接入系统到非 3GPP接入系统之间的切换。
3、 UE发送接入请求消息到非 3GPP网关网元执行 3GPP到非 3GPP系统的 切换流程。 对于 WLAN系统来说， 非 3GPP网关网元为 EPDG (演进分组数据 网关， Evolved Packet Data Gateway ); 对于 Wimax系统来说， 非 3 GPP网关网 元为 ASN GW (接入业务网络网关， Access Service Network Gateway ); 对于 CDMA系统来说， 非 3GPP网关网元为 AGW (接入网关， Access Gateway )。 非 3GPP网关网元可以根据如下方法来确定收到的接入请求是 3GPP到非 3GPP系 统的切换请求还是正常的接入请求（也叫初始化接入请求）：
1 ) 如果 3GPP到非 3GPP系统的切换流程也是通过接入流程来处理的话， 则在 Access Request消息中增加 Access Type字段来表明不同的接入处理类型（如 对于正常的接入， Access Type字段设置为 Initial Access; 对于切换接入， Access Type字段设置为 Handover Access ), 非 3GPP网关网元才艮据 Access Request消息 中的 Access Type来区分不同的接入流程。
2 ) 如果 UE在 3GPP或者非 3GPP系统接入时将使用的 PDN GW地址保 存到 UE中。 在正常的接入流程中 Access Request消息中不携带 PDN GW地址 信息，在 3GPP到非 3GPP系统的切换流程中 Access Request消息中携带 PDN GW 地址信息。 非 3GPP网关网元收到 Access Request消息后根据消息中是否携带 PDN GW地址信息来判断接入请求是正常的接入请求还是切换导致的接入请 求。
3 ) 3GPP到非 3GPP的切换流程处理通过单独的流程而不是接入流程处理， 如 UE发送 "3GPP to non-3GPP Handover Request" 消息到非 3GPP网关网元请 求非 3GPP网关网元进行 3GPP到非 3GPP系统的切换流程处理。
非 3GPP 网关网元如何判断收到的接入请求是正常的接入请求还是切换导 致的接入请求本实施例不作限定。
4、 UE、 非 3GPP网关网元、 HSS/AAA Server之间执行接入鉴权流程。 在 这个流程中非 3GPP网关网元获取 UE使用的 PDN GW地址信息。
5a、 对于正常接入的流程， 非 3GPP 网关网元根据用户签约数据中的缺省 APN ( Access Point Name, 接入点名 )选择 UE使用的 PDN GW; 对于切换接入 的流程， 非 3GPP网关网元使用 UE在 3GPP接入系统中使用的 PDN GW ( PDN
Server将保存的 PDN GW地址信息下发给非 3GPP网关网元）。 如果非 3GPP网 关网元和 PDN GW之间接口使用 PMIP协议， 则非 3GPP网关网元发送代理绑 定更新 （ Proxy Binding Update ) 消息给 PDN GW。 消息中增加标志位表明绑定 更新的处理类型。 标志位的具体处理同实施例二中的处理。
5b、 如果 UE和 PDN GW之间接口使用 CMIP协议， 则 UE发送绑定更新 ( Binding Update )消息给 PDN GW。 消息中增加标志位表明绑定更新的处理类 型。 标志位的具体处理方式可以有：
1 )增力。 "Binding Type" 标志位， 对于正常接入的流程， 其 "Binding Type" 标志位设置为 "Initial Binding" ; 对于切换接入的流程， 其 "Binding Type" 标志 位设置为 "Handover Binding"。 2 )"Cause"原因值。对于正常接入的流程，其" Cause"原因值设置为 "Initial" ; 对于切换接入的流程， 其 "Cause" 原因值设置为 "Handover"。
3 ) "Handover Indication"指示位。对于切换接入的流程， UE增加 "Handover Indication" 指示位以指示这个消息是由于切换接入导致的。 对于正常接入的流 程， UE不携带这个指示位。
4 ) "Initial Indication" 指示位。 对于正常接入的流程， UE 增力。 "Initial Indication" 指示位以指示这个消息是由于正常接入导致的。 对于切换接入的流 程， UE不携带这个指示位。
5c、 这里也可以如下处理：
对于 Proxy BU或者 BU消息不作修改。 当切换接入时非 3GPP网关网元发 送恢复业务请求消息给 PDN GW通知 PDN GW恢复 UE使用的 UE。
6、 PDN GW收到 Proxy BU或者 BU消息后判断消息中的 绑定更新的处理 类型信息或者是否收到恢复业务请求消息， 根据绑定更新的处理类型信息或者 是否收到恢复业务请求消息进行不同的处理：
1 ) 如果 Proxy BU或者 BU消息中的绑定更新的处理类型信息为正常接入 导致的绑定更新， 则 PDN GW查询这个 UE在本 GW中是否存在 PCC (策略和 计费控制， Policy and Charging Control )规则。 如果存在， 则 PDN GW删除 UE 存在的 PCC规则， 同时通知 PCRF删除保存的 PCC规则。 同时 PDN GW发起 源 3GPP接入网络中的资源释放处理流程， 将源 3GPP接入网络中的资源释放。
2 ) 如果 Proxy BU或者 BU消息中的绑定更新的处理类型信息为切换接入 导致的绑定更新或者收到恢复业务请求消息， 则 PDN GW获取这个 UE在本网 关内保存的 PCC规则。 判断 PCC规则是否与 IP-CAN ( IP 连通接入网络， IP-Connectivity Access Network )接入类型相关， 如果相关， 则 PDN GW联系 PCRF获取修改的 PCC规则。 同时 PDN GW发起源 3GPP接入网络中的资源释 放处理流程， 将源 3GPP接入网络中的资源释放。
7a、如果非 3GPP网关网元和 PDN GW之间接口使用 PMIP协议 ,则 PDN GW 发送代理绑定确认（ Proxy Binding Ack ) 消息给非 3GPP网关网元。
7b、 如果 UE和 PDN GW之间接口使用 CMIP协议 , 则 PDN GW发送绑定 确认（ Binding Ack ) 消息给 UE。
7c、 如果 PDN GW在先前的步骤中收到非 3GPP网关网元发送的恢复业务 请求消息， 则 PDN GW回恢复业务响应消息给非 3GPP网关网元。
8、 非 3GPP网关网元回接入接受消息给 UE。
9、 如果接入处理类型为切换导致的接入处理， 则 PDN GW发送 PCC规则 提供消息给非 3GPP网关网元将保存或者修改后的 PCC规则提供给非 3GPP网 关网元。 非 3GPP网关网元保存收到的 PCC规则， 然后回 PCC规则提供确认消 息给 PDN GW。
10、 非 3GPP网关网元根据收到的 PCC规则发起网络侧专用承载激活程序 建立 PCC规则对应的专用承载， 也就是创建 UE在原 3GPP接入系统使用的业 务在非 3GPP接入系统中需要的资源。
说明：
1 ) 如果非 3GPP网关网元和 PDN GW在一个实体上实现， 则非 3GPP网 关网元和 PDN GW之间的消息就将是一个实体内内部的消息。
2 ) 步骤 9与步骤 7之间没有先后时序关系。
3 ) PDN GW如何将 PCC规则传递给非 3GPP网关网元本实施例不作限定。
4 )如果绑定更新的处理类型信息未携带， 则 PDN GW收到非 3GPP网关网 元发送的消息后如果发现 UE在 PDN GW中保存有 PCC规则， 则 PDN GW将 保存的 PCC规则或者修改后的 PCC规则 （ PDN GW联系 PCRF获取修改后的 PCC规则 )通知给非 3GPP网关网元， 非 3GPP网关网元根据收到的 PCC规则 发起网络侧专用承载激活程序建立 PCC规则对应的专用承载， 也就是创建 UE 在原 3GPP接入系统使用的业务在非 3GPP系统中需要的资源。
还可以如下解决： 网络侧第一网元获取 UE使用的 PDN GW地址后发送特 定消息通知 Serving GW,由 Serving GW再通知 PDN GW进行承载的不同处理。
实施例四：
网络侧第一网元发送特定消息给 Serving GW, Serving GW发送特定消息给 PDN GW, 通知 PDN GW恢复 UE使用的业务所对应的承载。 或者网络侧第一 网元发送特定消息给 PDN GW, 通知 PDN GW创建 UE使用的业务所对应的资 源， 消息中携带 UE使用的 Serving GW地址信息。 具体流程见附图 6, 包括：
1、 UE通过 Non-3GPP 网关和 PDN GW接入到 Non-3GPP接入网络。
2、 UE发起非 3GPP接入系统到 3GPP接入系统之间的切换。
3、 UE发送附着请求消息到网络侧第一网元执行非 3GPP到 3GPP系统的切 换流程。 对于 SAE系统来说， 网络侧第一网元为 MME, 对于 GPRS/UMTS系 统来说， 网络侧第一网元为 SGSN。
4、 UE、 网络侧第一网元、 HSS/AAA Server之间执行鉴权流程。
5、 网络侧第一网元与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流程中网络侧第一网元获取 UE在非 3GPP接入系统中使用的 PDN GW 地址信息。
6、 对于切换接入的流程， 网络侧第一网元使用 UE在非 3GPP接入系统中 使用的 PDN GW ( PDN GW地址信息可以由网络侧第一网元从 HSS/AAA Server 中获取或者 HSS/AAA Server将保存的 PDN GW地址信息下发给网络侧第一网 元）。 网络侧第一网元发送恢复承载请求 （或者恢复 PDP上下文请求） 消息给 PDN GW, 通知 PDN GW创建 UE使用的业务所对应的资源。 消息中携带 UE 使用的 Serving GW地址信息。
6a、 如果网络侧第一网元与 PDN GW之间没有接口， 则恢复承载请求 （或 者恢复 PDP上下文请求） 消息通过 Serving GW转发给 PDN GW。
1 )、 对 UE使用的每个 PDN GW, 网络侧第一网元都发送一条恢复承载请 求（或者恢复 PDP上下文请求） 消息给 Serving GW, 消息中携带 UE使用的单 个 PDN GW地址信息。
2 )、 对于 UE使用的所有 PDN GW, 网络侧第一网元发送一条恢复承载请 求（或者恢复 PDP上下文请求） 消息给 Serving GW, 消息中携带 UE使用的所 有 PDN GW地址信息。
7、 PDN GW收到恢复承载请求（或者恢复 PDP上下文请求）消息后获取 消息中携带的 Serving GW地址信息。 后续的资源处理流程 PDN GW将把相关 的消息发送到这个 Serving GW网元上。 PDN GW的处理参见前面实施例中的描 述。 同时 PDN GW发起源 non-3GPP接入网络中的资源释放处理流程， 将源 non-3GPP接入网络中的资源释放。
8、 PDN GW回恢复承载响应 （恢复 PDP上下文响应） 消息给网络侧第一 网元。
8a、 如果网络侧第一网元与 PDN GW之间没有接口， 则恢复承载响应 （或 者恢复 PDP上下文响应 ) 消息通过 Serving GW转发给网络侧第一网元。
9、 如果接入处理类型为切换导致的接入处理且 Serving GW与 PDN GW之 间接口使用 GTP协议， 则 PDN GW根据保存或者修改后的 PCC规则发起网络 侧专用承载激活程序建立 PCC规则对应的专用承载， 也就是创建 UE 在原非 3GPP接入系统使用的业务需要的资源。
10、如果接入处理类型为切换导致的接入处理且 Serving GW与 PDN GW之 间接口使用 PMIP协议， 则 PDN GW发送 PCC规则提供消息给 Serving GW将 保存或者修改后的 PCC规则提供给 Serving GW。 Serving GW保存收到的 PCC 规则， 然后回 PCC规则提供确认消息给 PDN GW。
11、 Serving GW根据收到的 PCC规则发起网络侧专用承载激活程序建立 PCC规则对应的专用承载，也就是创建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资源。
说明：
1 )如果 Serving GW和 PDN GW在一个实体上实现，则 Serving GW和 PDN
GW之间的消息就将是一个实体内部的消息。
2 ) 步骤 9与步骤 8之间没有先后时序关系。
3 ) PDN GW如何将 PCC规则传递给 Serving GW本实施例不作限定。 实施例五：
由源侧网络侧网元发送切换请求消息到目标侧网络侧网元，携带 UE在源侧 系统中使用的锚点网关网元地址信息， 目标侧网络侧网元获取这些锚点网关网 元地址信息， 然后通知这些锚点网关网元进行资源的创建处理。 具体流程见附 图 7, 包括：
1、 源侧接入系统决定发起切换， 将 UE切换到目标侧接入系统。
2、 源侧网络侧网元发送切换请求消息到目标侧网络侧网元， 切换请求消息 中携带 UE 在源侧接入系统中使用的锚点网关网元地址信息 （如消息中携带 Anchor Gateway Address List信元，包括 UE使用的每个锚点网关网元地址信息 )。 如果源侧 /目标侧接入系统为 GPRS/UMTS 系统， 则源侧 /目标侧网络侧网元为 SGSN; 如果源侧 /目标侧接入系统为 SAE 系统， 则源侧 /目标侧网络侧网元为 MME; 如果源侧 /目标侧接入系统为 WLAN系统 , 则源侧 /目标侧网络侧网元为 EPDG (演进分组数据网关， Evolved Packet Data Gateway ); 如果源侧 /目标侧接 入系统为 Wimax系统 , 则源侧 /目标侧网络侧网元为 ASN GW (接入业务网络网 关， Access Service Network Gateway );如果源侧 /目标侧接入系统为 CDMA系统， 则源侧 /目标侧网络侧网元为 AGW (接入网关， Access Gateway )。
3、 目标侧网络侧网元从切换请求消息中获取 UE在源侧接入系统中使用的 锚点网关网元地址信息， 然后通知锚点网关网元进行资源的创建处理， 也叫资 源的预留处理。 处理流程同上述实施例描述， 这里不再描述。
4、 目标侧网络侧网元回切换响应消息给源侧网络侧网元。
5、 源侧网络侧网元通知 UE切换到目标侧接入系统。
6、 UE切换到目标侧接入系统。
实施例六：
UE还驻留在 non-3GPP网络时通过 non-3GPP网络发起预注册或者优化切 换流程到 3GPP接入网络， 3GPP接入网络的网络侧第一网元在发送创建缺省承 载请求（或者创建缺省 PDP上下文请求 )到 Serving GW时携带指示位时表明创 建承载（或者创建 PDP上下文）的处理类型（预注册处理类型或者为 non-3GPP 网络和 3GPP网络之间的优化切换处理类型 ), Serving GW收到消息后根据指示 位进行资源的创建处理。 具体流程见附图 8 , 包括：
1、 UE通过 Non-3GPP 网关和 PDN GW接入到 Non-3GPP接入网络。
2、 UE发起 3GPP接入系统的预注册或者优化切换处理流程。
3、 UE通过 non-3GPP接入网络发送附着请求消息到网络侧第一网元执行 3GPP 系统的预注册或者优化切换处理流程。 对于 SAE 系统来说， 网络侧第一 网元为 MME, 对于 GPRS/UMTS系统来说， 网络侧第一网元为 SGSN。
UE 在 Attach Request 消息中可以增加指示位指示网络侧第一网元这个 Attach Request消息是由于 UE的预注册或者优化切换流程导致的。 指示位的具 体处理方式可以为：
1 ) 增加 "Attach Type"字段，且 UE将这个字段的值设置为 "Pre-registration Attach" 或者为 "Optimized Handover Attach"。
2) 增力口 "Pre-registration Indication" 或者 "Optimized Handover Indication" 指示位字段。
3 ) 增加 "Cause" 字段， 且 UE将这个字段的值设置为 "Pre-Registration" 或者为 " Optimized Handover"。
如果 UE在 Attach Request消息中未携带指示位， 网络侧第一网元判断收到 的 Attach Request消息是从 non-3GPP接入网络发送过来的， 则网络侧第一网元 认为收到的 Attach Request消息是由于 UE的预注册或者优化切换流程导致的。
4、 UE、 网络侧第一网元、 HSS/AAA Server之间执行鉴权流程。
5、 网络侧第一网元与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流程中网络侧第一网元获取 UE在非 3GPP接入系统中使用的 PDN GW 地址信息。
6、 网络侧第一网元选择 UE在非 3GPP接入系统中使用的 PDN GW ( PDN GW地址信息可以由网络侧第一网元从 HSS/AAA Server中获取或者 HSS/AAA Server将保存的 PDN GW地址信息下发给网络侧第一网元）。如果 3GPP系统为 SAE 系统， 网络侧第一网元发送创建缺省承载请求消息到 Serving GW; 如果 3GPP系统为 GPRS/UMTS系统， 网络侧第一网元发送创建缺省 PDP上下文请 求（ Create Default PDP Context Request ) 消息到 Serving GW。 消息中增加指示 位表明承载创建的处理类型 （预注册或者优化切换处理类型）。 指示位的具体处 理方式可以有：
1 ) "Create Type"指示位。 MME设置 "Create Type"指示位为 "Pre-registration 或者为 " Optimized Handover"。
2 ) "Cause" 原因值。 MME设置 "Cause" 原因值为 "Pre-registration" 或者 为 "Optimized Handover"。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位。
7、如果 Serving GW与 PDN GW之间的接口使用 GTP协议，则 Serving GW 收到上述消息后发送创建承载请求（ Create Bearer Request )或者创建 PDP上下 文请求（ Create PDP Context Request )消息给 PDN GW。 消息中增加指示位表明 承载创建的处理类型 （预注册或者优化切换处理类型）。 指示位的具体处理方式 可以有：
1 ) "Create Type" 指示位。 Serving GW设置 "Create Type" 指示位为 "Pre-registration" 或者为 "Optimized Handover"。
2 ) "Cause"原因值。 Serving GW设置 "Cause"原因值为 "Pre-registration" 或者为 " Optimized Handover"。
3 ) "Pre-registration Indication"指示位或者为 "Optimized Handover Indication" 指示位。 8、 PDN GW收到上述消息后获取这个 UE在本网关内保存的 PCC规则。判 断 PCC规则是否与 IP-CAN( IP连通接入网络， IP-Connectivity Access Network ) 接入类型相关， 如果相关， 则 PDN GW联系 PCRF获取修改的 PCC规则。
PDN GW收到优化切换或者预注册的承载创建请求消息时不进行用户面路 径的切换， 即 PDN GW的下行用户面路径还是到 non-3 GPP接入网络， 同时保 留 non-3GPP接入网络中的资源。
9、 PDN GW回创建承载响应或者创建 PDP上下文响应消息给 Serving GW。
10、如果 Serving GW和 PDN GW之间的接口使用 PMIP协议，则 Serving GW 收到步骤 6中发送的消息后发送网关控制和服务质量策略规则请求消息到 PCRF 获取 UE在 3GPP接入网络中使用的 PCC规则。 PCRF回网关控制和服务质量策 略规则响应消息给 Serving GW,消息中携带 UE在 3GPP接入网络中使用的 PCC 规则。 同时 Serving GW不发送 Proxy BU消息到 PDN GW (即 Serving GW不通 知 PDN GW切换用户面路径到 Serving GW )。
11、 Serving GW回创建缺省承载响应或者创建缺省 PDP上下文响应消息给
12、 MME回附着接受消息给 UE。
13、 如果 Serving GW和 PDN GW之间的接口使用 GTP协议， 则 PDN GW 根据保存或者获取的 PCC规则发送创建专有承载请求消息到网络侧第一网元发 起网络侧专用承载激活程序建立 PCC规则对应的专用承载（也就是创建 UE在 原非 3GPP接入系统使用的业务在 3GPP网络中需要的资源）。 如果 Serving GW 和 PDN GW之间的接口使用 PMIP协议， 则 Serving GW根据获取的 PCC规则 发送创建专有承载请求消息到网络侧第一网元发起网络侧专用承载激活程序建 立 PCC规则对应的专用承载。 创建专有承载请求消息可以增加指示位表明承载 建立的处理类型 （预注册或者优化切换处理类型）。 指示位的具体处理方式可以 有：
1 ) "Create Type" 指示位。 Serving GW或者 PDN GW设置 "Create Type" 才旨示位为 "Pre-registration" 或者为 "Optimized Handover"。
2 ) "Cause" 原因值。 Serving GW或者 PDN GW设置 "Cause" 原因值为 "Pre-registration" 或者为 "Optimized Handover"。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication"。 14、 网络侧第一网元发送承载建立请求消息到 3GPP接入网元请求 3GPP接 入网元建立无线侧的承载。 网络侧第一网元如果发现无线侧的承载建立是由于 预注册或者优化切换导致的， 则网络侧第一网元在承载建立请求消息中增加指 示位表明承载建立的处理类型 （预注册或者优化切换处理类型）。 指示位的具体 处理方式可以有：
1 ) "Setup Type" 指示位。 网络侧第一网元设置 "Setup Type" 指示位为 "Pre-registration" 或者为 "Optimized Handover"。
2 ) "Cause"原因值。网络侧第一网元设置 "Cause"原因值为 "Pre-registration" 或者为 " Optimized Handover"。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication"。 或者网络侧第一网元发送重定位请求消息给 3GPP接入网元请求 3GPP接入 网元建立无线侧的承载。
3GPP接入网元收到上述消息后建立本网元与 Serving GW之间的承载资源， 如果 3GPP接入网元发现这个承载建立请求是由于预注册或者优化切换导致的 承载建立， 则 3GPP接入网元不通知 UE建立无线承载（Radio Bearer ) 资源。 然后 3GPP接入网元回承载建立响应消息到网络侧第一网元。
15、网络侧第一网元回创建专有承载响应消息到 Serving GW或者 PDN GW。
16、 UE移动到 3GPP接入网络， 发送跟踪区或者路由区更新请求消息到网 络侧第一网元指示网络侧第一网元 UE已经切换到 3GPP接入网络（ UE也可以 通过其它的消息来指示网络侧第一网元 UE 已经切换到 3GPP接入网络， 如 Service Request消息 )。
17、 网络侧第一网元发送修改承载请求或者修改 PDP 上下文请求消息到 Serving GW。 网络侧第一网元在修改承载请求或者修改 PDP上下文请求消息中 增加指示位信息指示 PDN GW不发起 UE在源 non-3GPP接入网络中的资源释放 处理流程。 这个指示位可以为优化切换或者预注册指示位或者资源不释放指示 位。 指示位的具体处理方式可以有：
1 ) "Update Type" 指示位。 网络侧第一网元设置 "Update Type" 指示位为 "Pre-registration" 或者为 "Optimized Handover"。
2 ) "Cause"原因值。网络侧第一网元设置 "Cause"原因值为 "Pre-registration" 或者为 "Optimized Handover" 或者为 "Resource not Release"。 3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位或者 "Resource not Release Indication" 指示位。
18、如果 Serving GW和 PDN GW之间的接口使用 GTP协议，则 Serving GW 发送修改承载请求或者修改 PDP上下文请求消息到 PDN GW。如果 Serving GW 和 PDN GW之间的接口使用 PMIP协议，则 Serving GW发送代理绑定更新消息 到 PDN GW。 Serving GW在修改承载请求或者修改 PDP上下文请求或者代理绑 定更新消息中增加指示位信息指示 PDN GW不发起 UE在源 non-3GPP接入网络 中的资源释放处理流程。 这个指示位可以为优化切换或者预注册指示位或者资 源不释放指示位。 指示位的具体处理方式可以有：
1 ) "Update Type" 或者 "Binding Type" 指示位。 Serving GW设置 "Update Type " 或者 "Binding Type " 指示位为 "Pre-registration" 或者为 " Optimized Handover"。
2 ) "Cause"原因值。 Serving GW设置 "Cause"原因值为 "Pre-registration" 或者为 "Optimized Handover" 或者为 "Resource not Release" 指示位。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位或者 "Resource not Release Indication" 指示位。
19、 PDN GW收到上述消息后获取这个 UE在本网关内保存的 PCC规则。 如果 PDN GW收到 Serving GW发送的代理绑定更新消息则 PDN GW判断 PCC 规则是否与 IP-CAN ( IP连通接入网络， IP-Connectivity Access Network )接入 类型相关， 如果相关， 则 PDN GW发送 IP-CAN会话修改请求消息到 PCRF获 取 UE在 3GPP接入网络内使用的 PCC规则。 PCRF回 IP-CAN会话修改确认消 息到 PDN GW, 这个消息中携带 UE在 3GPP接入网络中使用的 PCC规则。 如 果 Serving GW发送的消息中指示 PDN GW不发起 UE在源 non-3GPP接入网络 中的资源释放处理流程，则 PDN GW不发起 UE在源 non-3GPP接入网络中的资 源释放处理流程（即 non-3GPP接入网络中的资源释放处理不是由 PDN GW触 发）。
20、 PDN GW回修改承载响应或者修改 PDP上下文响应或者代理绑定确认 消息到 Serving GW。
21、 Serving GW回修改承载响应或者修改 PDP上下文响应消息到网络侧第 一网元。 22、 网络侧第一网元回跟踪区或者路由区更新接受消息到 UE。
23、网络侧第一网元在收到 UE已经切换到目标接入网络的消息后如果发现 UE已经执行过预注册或者优化切换流程处理， 则网络侧第一网元回切换完成消 息到 non-3GPP接入网络的网元。
24、 如果 UE和 PDN GW之间使用 CMIP协议， 则 UE发送绑定更新消息 到 PDN GW。 UE在绑定更新消息中增加指示位信息指示 PDN GW不发起 UE 在源 non-3GPP接入网络中的资源释放处理流程。这个指示位可以为优化切换或 者预注册指示位或者资源不释放指示位。 指示位的具体处理方式可以有：
1 ) "Update Type" 或者 "Binding Type" 指示位。 UE设置 "Update Type" 或者 "Binding Type"指示位为 "Pre-registration"或者为 "Optimized Handover"。
2 ) "Cause" 原因值。 UE设置 "Cause" 原因值为 "Pre-registration" 或者为 "Optimized Handover" 或者为 "Resource not Release" 指示位。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位或者 "Resource not Release Indication" 指示位。
PDN GW收到这个消息后不发起 UE在源 non-3GPP接入网络中的资源释放 处理流程 (即 non-3GPP接入网络中的资源释放处理不是由 PDN GW触发）。 同 时 PDN GW中的源 non-3GPP接入网络中的资源（如源 non-3GPP接入网络中的 绑定緩存表项资源 （ Binding Cache entry ) )释放可以有如下两种处理方法：
1 ) PDN GW本地释放源 non-3GPP接入网络中的资源 , 无需 non-3GPP GW 通知释放。
2 ) PDN GW不释放源 non-3GPP接入网络中的资源 ,需 non-3GPP GW通知 释放。
25、 non-3GPP接入网络中的网元（ non-3GPP接入网络中的接入网元或者 non-3GPP GW )收到网络侧第一网元发送的切换完成消息后发起源 non-3GPP接 入网络中的资源释放处理流程 （即 non-3GPP接入网络中的资源释放处理由 non-3GPP接入网络中的接入网元或者 non-3GPP GW触发）。 如果源 non-3GPP 接入网络中的资源释放处理流程由 non-3GPP接入网络中的接入网元发起， 则 non-3GPP接入网络中的接入网元在发给 non-3GPP GW的消息 （如资源释放请 求消息， 具体消息由特定的 non-3GPP接入网络确定）中携带指示位信息指示这 个资源释放处理是由于 non-3GPP接入网络到 3GPP接入网络切换导致的。 指示 位可能有如下的具体处理方式：
1 ) "Release Type"。 non-3GPP接入网络中的接入网元设置 "Release Type" 指示位为 "inter RAT Handover from non-3 GPP to 3 GPP"。
2 ) "Cause" 原因值。 non-3GPP接入网络中的接入网元设置 "Cause" 原因 值为 "inter RAT Handover from non-3 GPP to 3 GPP"。
3 ) "ΓΝΗΙ ( Isomerous network Handover Indication )，， 指示位。
26、如果 PDN GW中的资源释放处理需要 non-3GPP GW通知 ,则 non-3GPP GW发送代理绑定更新消息给 PDN GW。 代理绑定更新消息中携带指示位信息 指示这个代理绑定更新消息是由于 non-3GPP接入网络到 3GPP接入网络切换导 致的。 指示位可能有如下的具体处理方式：
1 ) "Binding Type"„ non-3GPP GW设置 "Binding Type"指示位为 "inter RAT Handover from non-3 GPP to 3 GPP"。
2 )"Cause"原因值。 non-3GPP GW设置 "Cause"原因值为 "inter RAT Handover from non-3 GPP to 3 GPP"。
3 ) "ΓΝΗΙ ( Isomerous network Handover Indication )，， 指示位。
PDN GW收到上述的代理绑定更新消息后释放源 non-3 GPP接入网络中的 资源 （如绑定緩存表项资源 （Binding Cache entry ) ), 保留目标 3GPP接入网络 中的资源（如 3GPP接入网络中的承载资源或者绑定緩存表项资源 , PDN GW为 UE分配的 IP地址等 ),同时 PDN GW也不和 PCRF进行交互指示 PCRF资源已 经释放。
PDN GW回代理绑定确认消息给 non-3GPP GW。
27、 non-3GPP GW回资源释放响应消息给 non-3GPP接入网络中的接入网 元。
注：
1 )如果 Serving GW和 PDN GW在一个实体上实现，则 Serving GW和 PDN GW之间的消息就将是一个实体内部的消息。
2 )步骤 12与步骤 13之间没有先后时序关系， 步骤 16与步骤 25之间没有 先后时序关系。
3 )如果承载创建的处理类型信息未携带， 则 PDN GW收到 Serving GW发 送的消息后如果发现 UE在 PDN GW中保存有 PCC规则， 则 PDN GW根据保 存的 PCC规则或者修改后的 PCC规则（ PDN GW联系 PCRF获取修改后的 PCC 规则 )发起网络侧专用承载激活程序建立 PCC规则对应的专用承载， 也就是创 建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资源。同时 PDN GW发起源 non-3GPP接入网络中的资源释放处理流程 (即 non-3GPP接入网络 中的资源释放处理由 PDN GW触发）， 将源 non-3GPP接入网络中的资源释放。
或者 Serving GW从 PCRF中获取了 PCC规则， 则 Serving GW根据获取的 PCC规则发起网络侧专用承载激活程序建立 PCC规则对应的资源， 也就是创建 UE在原非 3GPP接入系统使用的业务在 3GPP系统中需要的资源。
实施例七：
UE还驻留在 3GPP网络时通过 3GPP网络发起预注册或者优化切换流程到 non-3 GPP接入网元， non-3GPP接入网元在发送创建接入请求到 non-3GPP网关 网元时携带指示位时表明接入请求的处理类型（预注册或者为 non-3GPP网络和 3GPP网络之间的优化切换处理类型）， non-3GPP网关网元收到消息后根据指示 位进行资源的创建处理。 具体流程见附图 9, 包括：
1、 UE注册在 3GPP接入网络。
2、 UE发起 non-3GPP接入系统的预注册或者优化切换处理流程。
3、 UE通过 3GPP接入网络执行 non-3GPP接入网络特定的附着程序， 鉴权 以及认证程序。 如果需要， 则 UE执行 IPSec隧道建立程序。 对于 WLAN系统 来说，本步骤所述 Non - 3GPP网关为演进分组数据网关（ EPDG, Evolved Packet Data Gateway );对于 Wimax系统来说，本步骤所述 Non - 3GPP网关为 ASN GW (接入业务网络网关 , Access Service Network Gateway );对于 CDMA系统来说， 本步骤所述 Non - 3GPP网关为接入网关（ AGW, Access Gateway ); 对于 HRPD 网络来说，本步骤所述 Non - 3GPP网关为分组数据服务节点（ PDSN, Packet Data Serving Node )。
UE 可以在这个步骤的消息中携带指示位信息指示本步骤的执行是由于 3GPP接入网络到 non-3GPP接入网络的系统间优化切换或者预注册导致的， 指 示位的具体处理方式可以为：
增加 "Attach Type"字段，且 UE将这个字段的值设置为 "Optimized Handover Attach" 或者为 "Pre-registration Attach"。
增力口 "Optimized Handover Indication" 或者 "Pre-registration Indication"指 示位字段。
增加 "Cause" 字段， 且 UE将这个字段的值设置为 "Optimized Handover" 或者为 "Pre-registration"。
如果 UE 在这个步骤的消息中未携带优化切换或者预注册指示位信息且 non-3GPP接入网络中的网元发现本步骤的消息从 3GPP接入网络中的网络侧第 一网元发送过来， 则 non-3GPP接入网络中的网元认为 non-3 GPP接入网络特定 的附着程序是由于 3GPP接入网络到 non-3GPP接入网络的系统间优化切换或者 预注册导致的。
如果 non-3GPP接入网络中的接入网元在这个步骤中获知 UE 的接入类型 (优化切换或者预注册）后则 non-3GPP接入网络中的接入网元在发给 non-3GPP GW的消息中携带指示位信息指示 UE的接入类型。指示位的具体处理方式可以 为：
增加 "Attach Type" 字段， 且 non-3GPP接入网络中的接入网元将这个字段 々值设置为 "Optimized Handover Attach" 或者为 "Pre-registration Attach"。
增力口 "Optimized Handover Indication" 或者 "Pre-registration Indication"指 示位字段。
增加 "Cause" 字段， 且 non-3GPP接入网络中的接入网元将这个字段的值 设置为 "Optimized Handover" 或者为 "Pre-registration"。
4、 non-3GPP GW发送网关控制和服务质量策略规则请求消息到 PCRF获取 UE在 non-3GPP接入网络中使用的 PCC规则。 PCRF回网关控制和服务质量策 略规则响应消息给 non-3GPP GW,消息中携带 UE在 non-3GPP接入网络中使用 的 PCC规则。
5、 UE通过 3GPP接入网络触发 non-3GPP接入网络中的层 3附着程序。 UE 可以在这个步骤的消息中携带指示位信息指示本步骤的执行是由于 3GPP接入网络到 non-3GPP接入网络的系统间优化切换或者预注册导致的， 指 示位的具体处理方式参见步骤 2中的描述。
如果 UE 在这个步骤的消息中未携带优化切换或者预注册指示位信息且 non-3GPP接入网络中的网元发现本步骤的消息从 3GPP接入网络中的网络侧第 一网元发送过来， 则 non-3GPP接入网络中的网元认为 non-3 GPP接入网络特定 的附着程序是由于 3GPP接入网络到 non-3GPP接入网络的系统间优化切换或者 预注册导致的。
如果 non-3GPP接入网络中的接入网元在这个步骤中获知 UE 的接入类型 (优化切换或者预注册）后则 non-3GPP接入网络中的接入网元在发给 non-3GPP GW的消息中携带指示位信息指示 UE的接入类型。指示位的具体处理方式参见 步骤 2中的描述。
6、 non-3GPP GW或者 non-3GPP接入网络中的接入网元指示 UE层 3附着 完成。
7、 non-3GPP 网关网元根据获取的 PCC 规则发送创建资源请求消息到 non-3GPP接入网元发起网络侧专用承载激活程序建立 PCC规则对应的资源。消 息中增加指示位表明资源建立的处理类型 （预注册或者优化切换处理类型）。 指 示位的具体处理方式可以有：
1 ) "Create Type" 指示位。 网络侧第一网元设置 "Create Type" 指示位为 "Pre-registration" 或者 "Optimized Handover"。
2 ) "Cause"原因值。网络侧第一网元设置 "Cause"原因值为 "Pre-registration" 或者为 " Optimized Handover"。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位。
non-3GPP接入网元收到上述消息后建立本网元与 non-3GPP网关网元之间 的资源。如果 non-3GPP接入网元发现这个资源建立请求是由于预注册或者优化 切换导致的资源建立， 则 non-3GPP接入网元不通知 UE建立无线资源 （Radio Resource )。然后 non-3GPP接入网元回创建资源响应消息到 non-3GPP网关网元。
8、如果 non-3GPP GW和 PDN GW之间接口使用 PMIP协议且 non-3GPP GW 发现 UE的接入类型为优化切换或者预注册， 则 non-3GPP GW收到层 3附着程 序中的消息时不发送代理绑定更新消息到 PDN GW (即不通知 PDN GW切换下 行用户面路径到 Serving GW )。
UE移动到 non-3 GPP接入网络， UE通过 non-3 GPP接入网络中的接入网元 发送 non-3GPP接入网络相关的接入消息到 non-3GPP GW。
9、 如果 non-3GPP GW和 PDN GW之间接口使用 PMIP协议， 则 non-3GPP GW发送代理绑定更新消息到 PDN GW。
non-3GPP GW在代理绑定更新消息中增加指示位信息指示 PDN GW不发起 UE在源 3GPP接入网络中的资源释放处理流程。 这个指示位可以为优化切换或 者预注册指示位或者资源不释放指示位。 指示位的具体处理方式可以有：
1 ) "Update Type"或者 "Binding Type"指示位。 non-3GPP GW设置 "Update Type " 或者 "Binding Type " 指示位为 "Pre-registration" 或者为 " Optimized Handover"。
2 ) "Cause"原因值。 non-3GPP GW设置 "Cause"原因值为 "Pre-registration" 或者为 "Optimized Handover" 或者为 "Resource not Release" 指示位。
3 ) "Pre-registration Indication"才旨示位或者 "Optimized Handover Indication" 指示位或者 "Resource not Release Indication" 指示位。
10、 PDN GW收到上述消息后获取这个 UE在本网关内保存的 PCC规则。 判断 PCC 规则是否与 IP-CAN ( IP 连通接入网络， IP-Connectivity Access Network )接入类型相关， 如果相关， 则 PDN GW发送 IP-CAN会话修改请求 消息到 PCRF获取 UE在 non-3 GPP接入网络内使用的 PCC规则。 PCRF回 IP-CAN 会话修改确认消息到 PDN GW,这个消息中携带 UE在 non-3GPP接入网络中使 用的 PCC规则。
如果 non-3GPP GW发送的消息中指示 PDN GW不发起 UE在源 3GPP接入 网络中的资源释放处理流程， 则 PDN GW不发起 UE在源 3GPP接入网络中的 资源释放处理流程（即 3GPP接入网络中的资源释放处理不是由 PDN GW触发）。 同时 PDN GW中的源 3GPP接入网络中的资源 （如源 3GPP接入网络中的绑定 緩存表项资源 （Binding Cache entry )或者承载上下文资源 )释放可以有如下两 种处理方法：
1 ) PDN GW本地释放源 3GPP接入网络中的资源， 无需 Serving GW通知 释放。
2 ) PDN GW不释放源 3GPP接入网络中的资源， 需 Serving GW通知释放。 11、 PDN GW回代理绑定确认消息到 non-3GPP GW。
12、 如果 UE和 PDN GW之间使用 CMIP协议， 则 UE发送绑定更新消息 到 PDN GW。
UE在绑定更新消息中增加指示位信息指示 PDN GW不发起 UE在源 3GPP 接入网络中的资源释放处理流程。 这个指示位可以为优化切换或者预注册指示 位或者资源不释放指示位。 指示位的具体处理方式参见实施例六中的描述。 PDN GW收到这个消息后不发起 UE在源 3GPP接入网络中的资源释放处理 流程（即 3GPP接入网络中的资源释放处理不是由 PDN GW触发）。同时 PDN GW 中的源 3GPP接入网络中的资源 （如源 3GPP接入网络中的绑定緩存表项资源 ( Binding Cache entry )或者承载上下文资源 )释放可以有如下两种处理方法：
1 ) PDN GW本地释放源 3GPP接入网络中的资源， 无需 Serving GW通知 释放。
2 ) PDN GW不释放源 3GPP接入网络中的资源， 需 Serving GW通知释放。 13、 PDN GW收到上述消息后获取这个 UE在本网关内保存的 PCC规则。 判断 PCC 规则是否与 IP-CAN ( IP 连通接入网络， IP-Connectivity Access Network )接入类型相关，如果相关，则 PDN GW联系 PCRF获取修改后的 PCC 规则。 具体处理参见步骤 10中的描述。
14、 PDN GW回绑定确认消息到 UE。
15、 non-3GPP接入网络的接入网元或者 non-3GPP GW在收到 UE已经切换 到目标接入网络的消息后如果发现 UE 已经执行过预注册或者优化切换流程处 理， 则 non-3GPP接入网络的接入网元或者 non-3GPP GW发送切换完成消息到 3GPP接入网络的网络侧第一网元。
16、 3GPP接入网络的网络侧第一网元收到 non-3GPP接入网络的接入网元 或者 non-3GPP GW发送的切换完成消息后发起源 3GPP接入网络中的资源释放 处理流程 (即 3GPP接入网络中的资源释放处理由 3GPP接入网络的网络侧第一 网元触发）。
3GPP接入网络的网络侧第一网元发送删除承载请求或者删除 PDP上下文 请求消息到 Serving GW。删除承载请求或者删除 PDP上下文请求消息中携带指 示位信息指示这个承载删除处理是由于 3GPP接入网络到 non-3GPP接入网络切 换导致的。 指示位可能有如下的具体处理方式：
1 ) "Delete Type"。 3GPP接入网络的网络侧第一网元设置 "Delete Type" 指 示位为 "inter RAT Handover from 3 GPP to non-3 GPP"。
2 ) "Cause" 原因值。 3GPP接入网络的网络侧第一网元设置 "Cause" 原因 值为 "inter RAT Handover from 3 GPP to non-3 GPP"。
3 ) "ΓΝΗΙ ( Isomerous network Handover Indication )，， 指示位。
17、 如果 PDN GW中的资源释放处理需要 Serving GW通知则 Serving GW 收到上述消息后发送删除承载请求消息（ Serving GW和 PDN GW之间的接口协 议使用 GTP协议）或者代理绑定更新消息 （Serving GW和 PDN GW之间的接 口协议使用 PMIP协议）到 PDN GW。 删除承载请求消息或者代理绑定更新消 息中携带指示位信息指示这个承载删除处理是由于 3GPP接入网络到 non-3GPP 接入网络切换导致的。 指示位可能有如下的具体处理方式：
1 ) "Delete Type" 或者 "Binding Type"。 Serving GW设置 "Delete Type" 或 者 "Binding Type" 指示位为 "inter RAT Handover from 3 GPP to non-3 GPP"。
2 ) "Cause"原因值。 Serving GW设置 "Cause"原因值为 "inter RAT Handover from 3 GPP to non-3 GPP"。
3 ) "ΓΝΗΙ ( Isomerous network Handover Indication )，， 指示位。
18、 PDN GW 收到上述的删除承载请求或者代理绑定更新消息后释放源 3GPP接入网络中的资源 （如绑定緩存表项资源 （如果 Serving GW和 PDN GW 之间的接口协议使用 PMIP协议）或者承载上下文资源（如果 Serving GW和 PDN GW之间的接口协议使用 GTP协议））， 保留目的 non-3GPP接入网络中的资源
(如 non-3GPP接入网络中的绑定緩存表项资源， PDN GW为 UE分配的 IP地 址等 ), 同时 PDN GW也不和 PCRF进行交互指示 PCRF资源已经释放。
PDN GW回删除承载响应或者代理绑定确认消息到 Serving GW。
19、 Serving GW回删除承载响应或者删除 PDP上下文响应消息到网络侧第 一网元。
注：
1 ) 步骤 6与步骤 7之间没有先后时序关系， 步骤 9与步骤 15之间没有先 后时序关系。
2 )如果注册请求的处理类型信息未携带且 non-3GPP网关网元从 PCRF中 获取了 PCC规则， 则 non-3GPP网关网元根据获取的 PCC规则发起网络侧专用 承载激活程序建立 PCC规则对应的资源， 也就是创建 UE在原 3GPP接入系统 使用的业务在 non-3GPP系统中需要的资源。
3 )如果注册请求的处理类型信息未携带到 PDN GW, 则 PDN GW发起源 3GPP接入网络中的资源释放处理流程 (即 3GPP接入网络中的资源释放处理由 PDN GW触发 ), 将源 3GPP接入网络中的资源释放。
根据本发明上述资源创建方法实施例， 一种网络设备一的结构示意图如附 图 10所示， 包括：
接入请求确定单元 701和处理类型通知单元 702; 其中：
接入请求确定单元 701 ,用于确定出用户设备发起的接入请求为初始化接入 请求， 或为非 3GPP接入系统与 3GPP接入系统之间的切换请求； 并将确定出的 结果发送给所述处理类型通知单元 702;
处理类型通知单元 702, 用于接收所述接入请求确定单元 701发送的结果， 确定出为用户设备创建资源的对应处理类型， 并通知给网络侧为用户设备创建 资源的相应网元。
上述处理类型通知单元 702进一步可包括： 第一通知子单元 703和 /或第二 通知子单元 704;
第一通知子单元 703 , 用于在发送的承载创建请求消息、代理绑定更新消息 或绑定更新消息中携带标志位，表明承载创建的处理类型为第一 /第二创建类型， 或者表明绑定更新的处理类型为第一 /第二绑定类型；
第二通知子单元 704 , 用于发送特定消息，表明要求创建用户设备在切换前 接入系统中使用的业务需要的资源。
上述网络设备一可以集成于演进网络中的移动性管理实体 MME中；或集成 于服务 GPRS支持节点 SGSN中； 或集成于非 3GPP网关中； 或集成于用户设备 中。
另一网络设备二的结构示意图如图 11所示， 包括： 解析单元 801和资源创 建处理单元 802; 其中：
解析单元 801 ,用于解析出接收消息中指明的为用户设备创建资源的处理类 型； 并将解析出的处理类型通知给所述资源创建处理单元 802;
资源创建处理单元 802, 用于接收所述解析单元 801发送的处理类型， 为用 户设备进行相应资源的创建处理。
解析单元 801可以进一步包括： 第一解析子单元 803和 /或第二解析子单元 804。 其中：
第一解析子单元 803 , 用于解析出接收的承载创建请求消息、代理绑定更新 消息或绑定更新消息中携带的标志位， 根据所述标志位确定出第一 /第二创建类 型或第一 /第二绑定类型；并将解析出的第一 /第二创建类型或第一 /第二绑定类型 发送给所述资源创建处理单元； 第二解析子单元 804, 用于解析出接收的特定消息， 所述特定消息表明要求 创建用户设备在切换前接入系统中使用的业务需要的资源； 并通知所述资源创 建处理单元 802为用户设备创建切换前接入系统中使用的业务需要的资源； 所述资源创建处理单元 802接收到所述第一解析子单元 803发送的第一创 建类型或第一绑定类型后， 为用户设备创建缺省承载；
所述资源创建处理单元 802接收到所述第一解析子单元 803发送的第二创 建类型、 第二绑定类型或第二解析子单元 804发送的通知后， 创建所述用户设 备在切换前接入系统中使用的业务需要的资源。
上述网络设备二可以集成于分组数据网络网关实体中。
实施例八：
初始化接入 3GPP系统时网络侧第一网元从 HSS中获取 UE使用的 PDN GW 地址信息后发送消息通知 PDN GW释放 UE使用的资源， PDN GW收到消息后 释放 UE使用的资源。 具体流程见附图 12, 包括：
1、 UE发送附着请求消息到网络侧第一网元执行初始化接入网络处理。 对 于 SAE系统来说 , 网络侧第一网元为 MME , 对于 GPRS/UMTS系统来说 , 网 络侧第一网元为 SGSN。
2、 UE、 网络侧第一网元、 HSS/AAA Server之间执行鉴权流程。
3、 网络侧第一网元与 HSS/AAA Server执行位置更新及签约数据获取流程。 在这个流程中网络侧第一网元获取 UE在非 3GPP接入系统中使用的 PDN GW 地址信息。 或者 HSS/AAA Server将 UE在非 3GPP接入系统中使用的 PDN GW 地址信息下发给网络侧第一网元。
4、 如果是初始化附着流程处理， 则网络侧第一网元从 HSS中获取到 UE使 用的 PDN GW地址信息后， 发送资源释放请求消息给这些 PDN GW, 请求这些 PDN GW释放 UE使用的资源。 消息中携带 UE的标识（如用户的 IMSI )。
4a、 如果网络侧第一网元与 PDN GW之间没有接口， 则资源释放请求消息 通过 Serving GW转发给 PDN GW。 网络侧第一网元发送资源释放请求消息给一 个选择的 Serving GW, 消息中携带网络侧第一网元从 HSS中获取的 PDN GW 地址信息。 Serving GW然后对每个 PDN GW发送资源释放请求消息。 资源释放 请求消息后携带 UE的标识（如 UE的 IMSI )。
5、 PDN GW查询这个 UE在本网关中是否存在 PCC规则。 如果存在， 则 PDN GW删除保存的 UE的 PCC规则，同时通知 PCRF删除保存的该 UE的 PCC 规则， 具体处理参见实施例 1中的描述。
6、 PDN GW返回资源释放响应消息给网络侧第一网元。
6a、 如果网络侧第一网元与 PDN GW之间没有接口， 则资源释放请求消息 通过 Serving GW转发给网络侧第一网元。
7、 如果 UE原来使用的网络为非 3GPP网络， 则 PDN GW发送资源释放请 求消息给非 3GPP网关网元， 请求释放非 3GPP 网络为 UE分配的资源。 对于 WLAN系统来说， 非 3GPP网关网元为 EPDG; 对于 Wimax系统来说， 非 3GPP 网关网元为 ASN GW; 对于 CDMA系统来说， 非 3GPP网关网元为 AGW。
8、 非 3GPP网关设备发起资源释放程序， 释放非 3GPP网络为 UE分配的 资源。
9、 非 3GPP网关返回资源释放响应消息给 PDN GW。 PDN GW释放为 UE 分配的资源。
10、如果 UE原来使用的网络为 3GPP网络且 Serving GW和 PDN GW之间 接口协议使用 GTP协议， 则 PDN GW发起资源释放程序释放 3GPP网络为 UE 分配的资源。
11、如果 UE原来使用的网络为 3GPP网络且 Serving GW和 PDN GW之间 接口协议使用 PMIP协议，则 PDN GW发送资源释放请求消息给 Serving GW请 求 3GPP网络释放为 UE分配的资源。
12、 Serving GW发起资源释放程序， 释放 3GPP网络为 UE分配的资源。
13、 Serving GW回资源释放响应给 PDN GW。 PDN GW释放为 UE分配的 资源。
说明：
1 )如果 Serving GW和 PDN GW在一个实体上实现，则 Serving GW和 PDN
GW之间的消息就将是一个实体内内部的消息。
2 ) 步骤 7与步骤 6之间没有先后时序关系。
实施例九：
初始化接入非 3GPP系统时，网络侧第一网元从 HSS中获取 UE使用的 PDN GW地址信息后发送消息通知 PDN GW释放 UE使用的资源， PDN GW收到消 息后释放 UE使用的资源。 具体流程见附图 13 , 包括： 1、 UE发送接入请求消息到非 3GPP网关网元执行初始化接入非 3GPP系统 的处理流程。 对于 WLAN系统来说， 非 3GPP网关网元为 EPDG; 对于 Wimax 系统来说， 非 3GPP网关网元为 ASN GW; 对于 CDMA系统来说， 非 3GPP网 关网元为 AGW。
2、 UE、 非 3GPP网关网元、 HSS/AAA Server之间执行接入鉴权流程。 在
Server将 UE在 3GPP接入系统中使用的 PDN GW地址信息下发给非 3GPP网关 网元。
3、 如果是初始化接入流程处理， 则非 3GPP网关网元从 HSS中获取到 UE 使用的 PDN GW地址信息后发送资源释放请求消息给这些 PDN GW请求这些 PDN GW释放 UE使用的资源。 消息中携带 UE的标识（如用户的 IMSI )。
4、 PDN GW查询这个 UE在本 GW中是否存在 PCC规则。 如果存在， 则 PDN GW删除 UE存在的 PCC规则， 同时通知 PCRF删除保存的 PCC规则。
5、 PDN GW回资源释放命令给非 3GPP网关网元。
6、 如果 UE原来使用的网络为 3GPP网络且 Serving GW和 PDN GW之间 接口协议使用 GTP协议， 则 PDN GW发起资源释放程序， 释放原网络为 UE分 配的资源。
7、 如果 Serving GW和 PDN GW之间接口协议使用 PMIP协议且 UE原来 使用的网络为 3GPP网络，则 PDN GW发送资源释放请求消息给 Serving GW请 求 3GPP网络释放为 UE分配的资源。
8、 Serving GW发起资源释放程序， 释放 3GPP网络为 UE分配的资源。
9、 Serving GW回资源释放响应给 PDN GW。 PDN GW释放为 UE分配的 资源。
10、 如果 UE原来使用的网络为非 3GPP网络， 则 PDN GW发送资源释放 请求消息给非 3GPP网关设备请求释放非 3GPP 网络为 UE分配的资源。 对于 WLAN系统来说，非 3GPP网关网元为 EPDG(演进分组数据网关， Evolved Packet Data Gateway ); 对于 Wimax系统来说， 非 3GPP网关网元为 ASN GW (接入业 务网络网关， Access Service Network Gateway );对于 CDMA系统来说，非 3 GPP 网关网元为 AGW (接入网关 , Access Gateway )。
11、 非 3GPP网关设备发起资源释放程序， 释放非 3GPP网络为 UE分配的 资源。
12、 非 3GPP网关回资源释放响应消息给 PDN GW。 PDN GW释放为 UE 分配的资源。
根据本发明上述资源删除方法实施例， 一种网络设备三的结构示意图如图 14所示， 包括： 初始化请求确定单元 121、 网元地址获取单元 122和资源释放 通知单元 123 ; 其中：
初始化请求确定单元 121 ,用于确定出用户设备发起的接入请求为初始化接 入请求； 并通知给所述网元地址获取单元 122;
网元地址获取单元 122 , 用于获取用户设备使用的锚点网关网元地址信息， 并发送给所述资源释放通知单元 123;
资源释放通知单元 123 ,用于根据所述网元地址获取单元 122发送的地址信 息， 向所述锚点网关网元发送资源释放通知消息， 请求释放分配给所述用户设 备的资源。
所述网元地址获取单元 122进一步可以包括： 第一子单元 1221和第二子单 元 1222; 其中：
第一子单元 1221 , 用于从用户设备的归属网络服务器 HSS中获取用户设备 使用的锚点网关地址信息， 发送给第二子单元 1222;
第二子单元 1222, 存储并发送锚点网关地址信息给所述资源释放通知单元
123。
所述资源释放通知单元 123进一步可以包括： 判断子单元 1231、 第一发送 子单元 1232和第二发送子单元 1233; 其中：
判断子单元 1231 , 用于判断与所述锚点网关之间是否存在接口， 若存在接 口， 则通知所述第一发送子单元 1232发送所述资源释放通知消息给所述锚点网 关； 若不存在接口， 则通知所述第二发送子单元 1233发送所述资源释放通知消 息给服务网关， 由所述服务网关转发给所述锚点网关；
第一发送子单元 1232 , 用于发送所述资源释放通知消息给所述锚点网关； 第二发送子单元 1233 , 用于发送所述资源释放通知消息给服务网关。
根据本发明上述资源删除方法实施例， 一种网络设备四的结构示意图如图
15所示， 包括： 资源释放消息解析单元 131和资源释放执行单元 132; 其中： 资源释放消息解析单元 131 , 用于解析出接收的资源释放通知消息， 并发送 给所述资源释放执行单元 132;
资源释放执行单元 132, 用于释放分配给用户设备的资源。
网络设备四还可以包括查询单元 133和删除单元 134; 其中：
资源释放消息解析单元 131 解析出资源释放通知消息后， 还发送给所述查 询单元 133;
所述查询单元 133 ,用于查询本地是否保存有用户设备的策略与计费控制规 则； 如果是， 通知给所述删除单元 134;
所述删除单元 134, 用于删除本地保存的用户设备的策略与计费控制规则， 并通知网络侧策略与计费规则功能实体 PCRF删除保存相应规则。
所述网络设备四可以集成于锚点网关 PDN GW中。 综上所述， 釆用本发明实施例提供的资源创建方法， 由第一网元通知网络 侧第二网元为用户设备创建资源的处理类型； 所述第二网元根据所述处理类型 为所述用户设备进行相应资源的创建处理。 同时提出一种资源删除方法， 由网 络侧第一网元从网络侧第二网元地址信息保存的网元中获取 UE使用的网络侧 第二网元地址信息， 所述网络侧第一网元发送消息通知所述获取的网络侧第二 网元释放资源， 所述网络侧第二网元释放资源。 从而解决现有技术中网络侧网 关网元（即第二网元） 不能识别不同的接入请求 （即初始化接入请求和由于接 入系统切换导致的接入请求；)， 因而不能针对不同的接入请求创建相应资源的问 题和初始化接入时资源删除的问题。
可以理解的是， 本领域普通技术人员可以理解实现上述实施例方法中的全 部或部分流程， 是可以通过程序来指令相关的硬件来完成， 所述的程序可存储 于一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的实施 例的流程。 其中， 所述的存储介质可为磁碟、光盘、 只读存储记忆体（Read-Only Memory, ROM )或随机存 己忆体 ( Radom Access Memory, RAM )等。 明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要求及 其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种资源创建方法， 其特征在于， 包括：
当用户设备在第三代合作伙伴计划 3GPP网络和非 3GPP网络之间切换或发 起初始化接入请求时， 由第一网元通知网络侧第二网元为用户设备创建资源的 处理类型；
根据所述资源的处理类型， 所述第二网元为所述用户设备进行相应资源的 创建处理。
2、 如权利要求 1所述的方法， 其特征在于， 所述由第一网元通知网络侧第 二网元为用户设备创建资源的处理类型为： 所述第一网元在发送的承载创建请 求消息中增加标志位， 用所述标志位表明承载创建的处理类型为第一创建类型 或第二创建类型；
所述第二网元为所述用户设备进行相应资源的创建处理为：
所述第二网元根据所述第一创建类型创建缺省承载； 或者
所述第二网元根据所述第二创建类型创建缺省承载以及所述用户设备在切 换前接入系统中使用的业务需要的资源。
3、 如权利要求 1所述的方法， 其特征在于， 所述由第一网元通知网络侧第 二网元为用户设备创建资源的处理类型为： 所述第一网元在发送的代理绑定更 新消息或绑定更新消息中增加标志位， 用所述标志位表明绑定更新的处理类型 为第一绑定类型或第二绑定类型；
所述第二网元为所述用户设备进行相应资源的创建处理为：
所述第二网元根据所述第一绑定类型创建缺省承载； 或者
所述第二网元根据所述第二绑定类型创建缺省承载以及所述用户设备在切 换前接入系统中使用的业务需要的资源。
4、 如权利要求 2或 3所述的方法， 其特征在于， 所述第一网元在发送承载 创建请求消息、 代理绑定更新消息或绑定更新消息前， 进一步包括：
当确定出接入请求为初始化接入请求时， 用所述标志位表明承载创建的处 理类型为第一创建类型； 或者用所述标志位表明绑定更新的处理类型为第一绑 定类型；
当确定出接入请求为所述切换请求时， 用所述标志位表明承载创建的处理 类型为第二创建类型； 或者用所述标志位表明绑定更新的处理类型为第二绑定 类型。
5、 如权利要求 4所述的方法， 其特征在于， 当所述用户设备向 3GPP接入 系统发起接入请求时， 所述第一网元发送携带标志位的承载创建请求消息到网 络侧服务网关；
当所述服务网关与所述第二网元之间的接口使用 GTP协议时， 所述服务网 关向所述第二网元发送所述携带标志位的承载创建请求消息；
当所述服务网关与所述第二网元之间的接口使用 PMIP协议时，所述服务网 关向所述第二网元发送所述携带标志位的代理绑定更新消息； 或者所述服务网 关向所述第二网元发送恢复承载请求消息， 通知第二网元恢复用户设备切换前 所使用的资源。
6、 如权利要求 4所述的方法， 其特征在于， 当所述用户设备向非 3GPP接 入系统发起接入请求时，由非 3GPP网关网元作为所述第一网元接收用户设备发 起的接入请求； 若所述非 3GPP网关网元与所述第二网元之间的接口使用 PMIP 协议，由所述非 3GPP网关网元发送携带标志位的代理绑定更新消息给所述第二 网元；
若所述用户设备与所述第二网元之间的接口使用 CMIP协议， 由所述用户 设备作为第一网元发送携带标志位的绑定更新消息给所述第二网元。
7、 如权利要求 4所述的方法， 其特征在于， 当所述标志位表明承载创建的 处理类型为第一创建类型， 或绑定更新的处理类型为第一绑定类型时， 所述第 二网元执行下列处理：
查询用户设备在本网元中是否存在策略和计费控制规则； 如果存在， 则删 除该用户设备对应的策略和计费控制规则， 并通知网络侧策略与计费规则功能 实体删除该用户设备对应的策略和计费控制规则；
当所述标志位表明承载创建的处理类型为第二创建类型， 或绑定更新的处 理类型为第二绑定类型时， 所述第二网元执行下列处理：
获取用户设备在本网元内保存的策略和计费控制规则；
当判断出用户设备的策略和计费控制规则与 IP连通接入网络类型相关时， 通知网络侧策略与计费规则功能实体根据用户设备的当前 IP 连通接入网络类 型， 修改用户设备使用的策略和计费控制规则； 接收并保存所述策略与计费规则功能实体返回的修改后的策略和计费控制 规则；
根据修改后的策略和计费控制规则， 创建所述用户设备在切换前接入系统 中使用的业务需要的资源。
8、 如权利要求 1所述的方法， 其特征在于， 当确定出用户设备的接入请求 为预注册请求时， 所述第一网元通知网络侧第二网元为用户设备创建资源或者 注册的处理类型为预注册处理类型；
当确定出用户设备的接入请求为优化切换请求时， 所述第一网元通知网络 侧第二网元为用户设备创建资源或者注册的处理类型为优化切换处理类型。
9、 如权利要求 8所述的方法， 其特征在于， 所述网络侧第二网元为用户面 锚点网元， 所述用户面锚点网元根据所述预注册或者优化切换处理类型执行下 列处理：
获取用户设备在目标接入网络中使用的策略和计费控制规则；
根据用户设备使用的策略和计费控制规则， 创建所述用户设备在切换前接 入系统中使用的业务需要的资源；
保留源接入网络的资源； 或者
所述网络侧第二网元为服务网关网元或者非 3GPP网关网元，所述服务网关 网元或者非 3GPP 网关网元根据所述预注册或者优化切换处理类型执行下列处 理：
通知 PCRF获取用户设备使用的策略和计费控制规则；
根据用户设备使用的策略和计费控制规则， 创建所述用户设备在切换前接 入系统中使用的业务需要的资源。
10、 如权利要求 1 所述的方法， 其特征在于， 当所述用户设备从源接入系 统切换到目标接入系统时， 由目标接入系统中的所述第一网元从所述第二网元 地址信息保存的网元中获取所述第二网元地址信息； 或者
由源接入系统将所述第二网元地址信息通知给目标接入系统中的所述第一 网元； 或者
由所述第二网元地址信息保存的网元将所述第二网元地址信息下发给目标 接入网络中的所述第一网元。
11、 一种异构网络切换时的资源恢复处理方法， 其特征在于， 包括： 当用户设备在第三代合作伙伴计划 3GPP网络和非 3GPP网络之间切换或发 起初始化接入请求时， 网络侧网关设备获取用户设备在目标接入系统使用的策 略和计费控制规则；
网络侧网关设备根据所述的策略和计费控制规则在目标接入系统发起网络 侧承载建立程序。
12、 如权利要求 11所述的方法， 其特征在于， 所述网络侧网关设备为锚点 网关；
所述锚点网关获取用户设备在目标接入系统使用的策略和计费控制规则具 体包括：
所述锚点网关获取所述用户设备在本网元内保存的策略和计费控制规则， 或者
所述锚点网关联系策略与计费规则功能实体获取修改的策略和计费控制规 则。
13、 如权利要求 11所述的方法， 其特征在于， 所述网络侧网关设备为服务 网关；
所述服务网关获取用户设备在目标接入系统使用的策略和计费控制规则具 体包括：
网络侧锚点网关获取用户设备在目标接入系统使用的策略和计费控制规 则；
所述锚点网关下发用户设备在目标接入系统使用的策略和计费控制规则给 所述的服务网关。
14、如权利要求 11所述的方法，其特征在于，所述网络侧网关设备为非 3GPP 网关；
所述非 3GPP 网关获取用户设备在目标接入系统使用的策略和计费控制规 则具体包括：
网络侧锚点网关获取用户设备在目标接入系统使用的策略和计费控制规 则；
所述锚点网关将用户设备在目标接入系统使用的策略和计费控制规则下发 给所述的非 3GPP网关。
15、 如权利要求 12、 13或 14所述的方法， 其特征在于， 所述锚点网关获 取用户设备在目标接入系统使用的策略和计费控制规则之前， 目标接入系统还 执行下列处理：
目标接入系统获取所述锚点网关地址信息并通知所述锚点网关进行资源的 创建处理。
16、 如权利要求 15所述的方法， 其特征在于， 所述目标接入系统通过代理 绑定更新消息、 恢复承载请求消息或者承载创建请求消息， 通知所述锚点网关 网元进行资源的创建处理。
17、 一种资源删除方法， 其特征在于， 包括：
当用户设备在 3GPP 网络和非 3GPP 网络之间切换或发起初始化接入请求 时， 第一网元获取第二网元地址信息；
所述第一网元发送消息通知所述第二网元释放分配给用户设备的资源； 所述第二网元释放分配给用户设备的资源。
18、 如权利要求 17所述的方法， 其特征在于， 所述第二网元为锚点网关网 元；
所述第一网元接收用户设备发送的附着请求消息后执行初始化接入网络处 理， 从用户设备的归属网络服务器 HSS中获取用户设备使用的锚点网关地址信 息；
所述第一网元发送资源释放请求消息给所述锚点网关， 请求释放分配给用 户设备的资源；
所述锚点网关释放分配给用户设备的资源。
19、 如权利要求 18所述的方法， 其特征在于， 如果所述第一网元与所述锚 点网关之间没有接口， 则通过服务网关转发所述资源释放请求消息给所述锚点 网关。
20、 一种资源删除方法， 其特征在于， 包括：
当用户设备在 3GPP 网络和非 3GPP 网络之间切换或发起初始化接入请求 时， 目标接入网络网元通知用户面锚点不发起源接入网络的资源释放处理； 在 UE切换到目标接入网络后，目标接入网络网元向源接入网络网元发送消 息， 通知源网络 UE已经切换到目标接入网络；
源网络网元收到所述通知后发起源网络的资源释放处理。
21、 如权利要求 20所述的方法， 其特征在于， 所述目标接入网络网元通知 用户面锚点不发起源接入网络的资源释放处理， 具体处理为：
所述目标接入网络网元在发给用户面锚点的消息中增加指示位信息， 指示 位信息指示用户面锚点不发起源接入网络的资源释放处理。
22、 如权利要求 21所述方法， 其特征在于， 所述指示位信息为优化切换指 示位信息、 预注册指示位信息或者为资源不释放指示位信息。
23、 如权利要求 20所述的方法， 其特征在于， 所述源接入网络的网元收到 所述通知后发起源接入网络的资源释放处理， 具体为：
所述源接入网络网元发送删除承载请求或者代理绑定更新消息到所述用户 面锚点网元；
所述删除承载请求或者代理绑定更新消息中携带指示位信息， 所述指示位 信息指示在 3GPP接入网络和非 3GPP接入网络之间发生切换；
所述用户面锚点网元收到所述指示位信息后删除源接入网络中的资源， 保 留目标接入网络中的资源。
24、 一种网络设备， 其特征在于， 包括： 接入请求确定单元和处理类型通 知单元； 其中：
接入请求确定单元， 用于确定出用户设备发起的接入请求为初始化接入请 求， 或为非 3GPP接入系统与 3GPP接入系统之间的切换请求； 并将确定出的结 果发送给所述处理类型通知单元；
处理类型通知单元， 用于接收所述接入请求确定单元发送的结果， 确定出 为用户设备创建资源的对应处理类型， 并通知给网络侧为用户设备创建资源的 相应网元。
25、 如权利要求 24所述的网络设备， 其特征在于， 所述处理类型通知单元 包括： 第一通知子单元和 /或第二通知子单元； 其中：
第一通知子单元， 用于在发送的承载创建请求消息、 代理绑定更新消息或 绑定更新消息中携带标志位， 表明承载创建的处理类型为第一 /第二创建类型， 或者表明绑定更新的处理类型为第一 /第二绑定类型；
第二通知子单元， 用于发送特定消息， 表明要求创建用户设备在切换前接 入系统中使用的业务需要的资源。
26、 一种网络设备， 其特征在于， 包括： 解析单元和资源创建处理单元； 其中：
解析单元， 当用户设备在 3GPP网络和非 3GPP网络之间切换或发起初始化 接入请求时， 用于从对端网元接收消息， 并从消息中解析出为用户设备创建资 源的处理类型； 并将解析出的处理类型通知给所述资源创建处理单元；
资源创建处理单元， 用于接收所述解析单元发送的处理类型， 为用户设备 进行相应资源的创建处理。
27、 如权利要求 26所述的网络设备， 其特征在于， 所述解析单元包括： 第 一解析子单元和 /或第二解析子单元； 其中：
第一解析子单元， 用于解析出接收的承载创建请求消息、 代理绑定更新消 息或绑定更新消息中携带的标志位， 根据所述标志位确定出第一 /第二创建类型 或第一 /第二绑定类型；并将解析出的第一 /第二创建类型或第一 /第二绑定类型发 送给所述资源创建处理单元；
第二解析子单元， 用于解析出接收的特定消息， 所述特定消息表明要求创 建用户设备在切换前接入系统中使用的业务需要的资源； 并通知所述资源创建 处理单元为用户设备创建切换前接入系统中使用的业务需要的资源；
所述资源创建处理单元接收到所述第一解析子单元发送的第一创建类型或 第一绑定类型后， 为用户设备创建缺省承载；
所述资源创建处理单元接收到所述第一解析子单元发送的第二创建类型、 第二绑定类型或第二解析子单元发送的通知后， 创建缺省承载以及所述用户设 备在切换前接入系统中使用的业务需要的资源。
28、 一种网络设备， 其特征在于， 包括： 初始化请求确定单元、 网元地址 获取单元和资源释放通知单元； 其中：
初始化请求确定单元，当用户设备在 3GPP网络和非 3GPP网络之间切换时， 用于确定出用户设备发起的接入请求为初始化接入请求； 并通知给所述网元地 址获取单元；
网元地址获取单元， 用于获取用户设备使用的锚点网关网元的地址信息， 并发送给所述资源释放通知单元；
资源释放通知单元， 用于根据所述网元地址获取单元发送的地址信息， 向 所述锚点网关网元发送资源释放通知消息， 请求释放分配给所述用户设备的资
29、 如权利要求 28所述的网络设备， 其特征在于， 所述网元地址获取单元 包括： 第一子单元和第二子单元； 其中：
第一子单元， 用于从用户设备的归属网络服务器 HSS中获取用户设备使用 的锚点网关地址信息， 发送给第二子单元；
第二子单元， 存储并发送锚点网关地址信息给所述资源释放通知单元。
30、 如权利要求 28或 29所述的网络设备， 其特征在于， 所述资源释放通 知单元包括： 判断子单元、 第一发送子单元和第二发送子单元； 其中：
判断子单元， 用于判断与所述锚点网关之间是否存在接口， 若存在接口， 则通知所述第一发送子单元发送所述资源释放通知消息给所述锚点网关； 若不 存在接口， 则通知所述第二发送子单元发送所述资源释放通知消息给服务网关， 由所述服务网关转发给所述锚点网关；
第一发送子单元， 用于发送所述资源释放通知消息给所述锚点网关； 第二发送子单元， 用于发送所述资源释放通知消息给服务网关。
31、 一种网络设备， 其特征在于， 包括： 资源释放消息解析单元和资源释 放执行单元； 其中：
资源释放消息解析单元， 当用户设备在 3GPP网络和非 3GPP网络之间切换 或发起初始化接入请求时， 用于解析出接收的资源释放通知消息， 并发送给所 述资源释放执行单元；
资源释放执行单元， 用于释放分配给用户设备的资源。
32、 如权利要求 31所述的网络设备， 其特征在于， 还包括查询单元和删除 单元； 其中：
所述资源释放消息解析单元解析出资源释放通知消息后， 还发送给所述查 询单元；
所述查询单元， 用于查询本地是否保存有用户设备的策略与计费控制规则； 如果是， 通知给所述删除单元；
所述删除单元， 用于删除本地保存的用户设备的策略与计费控制规则， 并 通知网络侧策略与计费规则功能实体 PCRF删除保存相应规则。
PCT/CN2008/071400 2007-06-22 2008-06-20 Procédé et équipement réseau pour établir et effacer des ressources WO2009000197A1 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
EP16172080.0A EP3096583B1 (en) 2007-06-22 2008-06-20 Method and network device for creating resources
JP2009551096A JP5011396B2 (ja) 2007-06-22 2008-06-20 リソースを作成、削除する方法およびネットワーク装置
EP21181957.8A EP3952601A1 (en) 2007-06-22 2008-06-20 Method and network device for creating resources
EP18191044.9A EP3442269B1 (en) 2007-06-22 2008-06-20 Method and network device for creating resources
EP14150464.7A EP2720509B1 (en) 2007-06-22 2008-06-20 Method and network device for creating resources
EP08757809.2A EP2104278B1 (en) 2007-06-22 2008-06-20 Method for establishing resource during handover
US12/509,677 US8638750B2 (en) 2007-06-22 2009-07-27 Method and network device for creating and deleting resources
US14/104,753 US10945261B2 (en) 2007-06-22 2013-12-12 Method and network device for creating and deleting resources
US17/159,773 US11997697B2 (en) 2007-06-22 2021-01-27 Method and network device for creating and deleting resources

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710126555 2007-06-22
CN200710126555.0 2007-06-22
CN200710159785.7 2007-12-21
CN200710159785.7A CN101330753B (zh) 2007-06-22 2007-12-21 一种资源创建方法、资源删除方法及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/509,677 Continuation US8638750B2 (en) 2007-06-22 2009-07-27 Method and network device for creating and deleting resources

Publications (1)

Publication Number Publication Date
WO2009000197A1 true WO2009000197A1 (fr) 2008-12-31

Family

ID=40185196

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071400 WO2009000197A1 (fr) 2007-06-22 2008-06-20 Procédé et équipement réseau pour établir et effacer des ressources

Country Status (6)

Country Link
US (3) US8638750B2 (zh)
EP (5) EP3096583B1 (zh)
JP (1) JP5011396B2 (zh)
KR (1) KR101044685B1 (zh)
CN (1) CN101330753B (zh)
WO (1) WO2009000197A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010161478A (ja) * 2009-01-06 2010-07-22 Sharp Corp 移動通信システム、移動局及び管理局
US20120033638A1 (en) * 2009-02-09 2012-02-09 Ntt Docomo, Inc. Mobile communication method, gateway apparatus and server apparatus
JP2015053706A (ja) * 2009-09-18 2015-03-19 日本電気株式会社 通信システムと通信制御方法
CN107666543A (zh) * 2016-07-29 2018-02-06 中国移动通信集团江苏有限公司 一种数据处理方法及装置

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431797B (zh) * 2007-05-11 2012-02-01 华为技术有限公司 一种注册处理方法、系统及装置
CN102695294B (zh) 2007-05-28 2015-01-21 华为技术有限公司 网络锚点的地址删除方法及通信系统
US8811338B2 (en) * 2008-08-22 2014-08-19 Qualcomm Incorporated Proxy mobile internet protocol (PMIP) in a multi-interface communication environment
US9002356B2 (en) 2009-05-04 2015-04-07 Qualcomm Incorporated Access mode-based access control
EP2317822A1 (en) * 2009-10-29 2011-05-04 Panasonic Corporation Enhancement of the attachement procedure for re-attaching a UE to a 3GPP access network
CN102056140B (zh) * 2009-11-06 2013-08-07 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102083144B (zh) * 2009-11-26 2014-01-01 中兴通讯股份有限公司 一种数据缓存单元区分网络链接类型的方法及系统
WO2011076254A1 (en) * 2009-12-21 2011-06-30 Telefonaktiebolaget L M Ericsson (Publ) Non-guaranteed bit rate bearer control in a mobile communication network
JP5052642B2 (ja) * 2010-04-21 2012-10-17 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム、ネットワーク装置及び移動通信方法
US8477730B2 (en) * 2011-01-04 2013-07-02 Cisco Technology, Inc. Distributed load management on network devices
CN103338526B (zh) * 2011-01-10 2014-08-20 华为技术有限公司 用户设备上下文相关资源的释放方法和设备
CN104540241B (zh) * 2011-01-10 2018-10-09 华为技术有限公司 用户设备上下文相关资源的释放方法和设备
CN102595534B (zh) * 2011-01-10 2014-12-03 华为技术有限公司 用户设备上下文相关资源的释放方法和设备
EP2670174B1 (en) * 2011-01-28 2020-03-25 Samsung Electronics Co., Ltd Device and method for controlling charging in a mobile communication system
GB2488167A (en) * 2011-02-18 2012-08-22 Nec Corp Handover procedure in a home base station connected to a home base station gateway
US20120230293A1 (en) * 2011-03-08 2012-09-13 Edward Grinshpun Method of performing an inter-technology handoff in a loosely coupled architecture
ES2883576T3 (es) * 2012-01-06 2021-12-09 Alcatel Lucent Reducir la carga debido al reporte de cambios de información a un controlador de política y/o carga en un sistema de comunicación móvil
EP2839714B1 (en) * 2012-04-16 2016-06-08 Telefonaktiebolaget LM Ericsson (publ) Method and radio network node for managing radio resources
CN103874240B (zh) * 2012-12-11 2018-09-11 中兴通讯股份有限公司 一种信令发起方法、装置及网关设备
CN103906138B (zh) * 2012-12-26 2017-04-26 财团法人工业技术研究院 用以执行流量卸载的瞬时切换通讯系统、移动管理实体、用户设备及其方法
EP2952056B1 (en) * 2013-02-01 2017-10-11 Telefonaktiebolaget LM Ericsson (publ) Mobile gateway selection using a direct connection between a pcrf node and a mobility management node
CN104185302B (zh) * 2013-05-27 2017-09-29 电信科学技术研究院 一种pdn连接管理方法和设备
CN104683934B (zh) * 2013-11-26 2019-12-06 中兴通讯股份有限公司 一种实现异构网络系统间信息交互的装置和方法
US10111148B2 (en) * 2014-08-20 2018-10-23 Nokia Technologies Oy Apparatus and method for interworking optimization in connection with cellular handover
WO2017062065A1 (en) * 2015-10-09 2017-04-13 Intel IP Corporation Network initiated packet data network connection
US9936430B1 (en) 2016-03-07 2018-04-03 Sprint Spectrum L.P. Packet gateway reassignment
CN108924931B (zh) * 2017-03-24 2024-05-07 中兴通讯股份有限公司 一种无线资源配置方法、装置及用户设备、网络节点
US10582561B2 (en) 2017-03-27 2020-03-03 Electronics And Telecommunications Research Institute Method for releasing context of user equipment in non-3GPP access network and network entity performing the same
CN109561473B (zh) * 2017-09-25 2021-01-15 华为技术有限公司 一种通信资源的释放方法及装置、非暂态计算机存储介质
US10542513B2 (en) 2017-11-21 2020-01-21 Electronics And Telecommunications Research Institute Deregistration method of user equipment in network and user equipment performing the same
CN109962959B (zh) * 2017-12-26 2021-10-26 中国移动通信集团辽宁有限公司 会话绑定方法、装置、设备及介质
CN110166984B (zh) * 2018-02-13 2021-09-24 维沃移动通信有限公司 业务处理方法、信息发送方法和相关设备
WO2019183846A1 (zh) * 2018-03-28 2019-10-03 Oppo广东移动通信有限公司 切换的方法、用户设备、网络设备及计算机存储介质
JP7130874B2 (ja) * 2018-12-19 2022-09-05 台湾積體電路製造股▲ふん▼有限公司 ネットワークアクセスサービスのシステムおよび方法
US11405795B2 (en) * 2020-03-27 2022-08-02 Rockwell Collins, Inc. Spectrum information fusion for dynamic spectrum access of heirarchical heterogeneous wireless networks

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1893721A (zh) * 2005-07-08 2007-01-10 华为技术有限公司 一种系统间的切换方法
CN1984162A (zh) * 2006-04-30 2007-06-20 华为技术有限公司 演进网络中终端在非3gpp接入系统注册方法及系统
CN101150838A (zh) * 2006-09-18 2008-03-26 大唐移动通信设备有限公司 一种在系统间切换的方法及系统

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6246874B1 (en) 1998-04-29 2001-06-12 Hughes Electronics Corporation Method and apparatus for predicting spot beam and satellite handover in a mobile satellite communication network
US7079499B1 (en) 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US6996081B1 (en) 2000-10-05 2006-02-07 Telefonaktiebolaget Lm Ericsson (Publ) Resource capacity reporting to control node of radio access network
US7483989B2 (en) * 2001-03-13 2009-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for establishing a protocol proxy for a mobile host terminal in a multimedia session
GB2381414A (en) 2001-10-18 2003-04-30 Ericsson Telefon Ab L M Mobile telecommunications networks
US20030114158A1 (en) 2001-12-18 2003-06-19 Lauri Soderbacka Intersystem handover of a mobile terminal
US7257403B2 (en) 2002-05-03 2007-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Service-based inter-system handover
KR101010806B1 (ko) 2002-06-21 2011-01-25 톰슨 라이센싱 Ｗｌａｎ-ｕｍｔｓ 인터워킹을 위한 ｕｍｔｓ 라우팅영역으로서 ｗｌａｎ의 등록
CN1505413A (zh) * 2002-12-03 2004-06-16 北京三星通信技术研究有限公司 双模移动台在cdma系统和gsm系统之间切换的方法
CN1549610A (zh) 2003-05-09 2004-11-24 北京三星通信技术研究有限公司 在公共接入信道中提供多级接入服务的方法
GB0315278D0 (en) 2003-06-30 2003-08-06 Nokia Corp A method for optimising handover between communication networks
WO2006000612A1 (en) 2004-06-24 2006-01-05 Nokia Corporation Transfer of packet data in system comprising mobile terminal, wireless local network and mobile network
WO2006012909A1 (en) 2004-08-02 2006-02-09 Telefonaktiebolaget L.M. Ericsson (Publ) Handover in a mobile communications network
EP1646189A1 (en) 2004-10-06 2006-04-12 Matsushita Electric Industrial Co., Ltd. WLAN radio access network to UMTS radio access network handover with network requested packet data protocol context activation
KR101119096B1 (ko) 2004-11-04 2012-09-05 엘지전자 주식회사 광대역 무선접속 시스템에서 핸드오버시 적용되는 데이터전송 방법
US8238326B2 (en) 2004-11-18 2012-08-07 Ruckus Wireless, Inc. Maintaining consistent network connections while moving through wireless networks
US8320326B2 (en) 2004-11-22 2012-11-27 Motorola Mobility Llc Method and system for inter-technology active handoff of a hybrid communication device
US8130718B2 (en) 2004-12-09 2012-03-06 Interdigital Technology Corporation Method and system for interworking of cellular networks and wireless local area networks
CN1878389A (zh) * 2005-06-10 2006-12-13 华为技术有限公司 下一代网络业务切换方法及其装置
EP1684536B1 (en) 2005-01-19 2015-04-01 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Control policy over uplink resources in a wireless network
KR101113860B1 (ko) * 2005-02-18 2012-03-02 엘지전자 주식회사 멀티모드 이동단말의 핸드오버 수행 후 링크 해제 방법 및그 이동단말
KR100770860B1 (ko) 2005-02-21 2007-10-26 삼성전자주식회사 이동통신망과 무선 랜간의 핸드오프 방법 및 장치
US20060221903A1 (en) 2005-03-30 2006-10-05 Nokia Corporation Communication connection control mechanism in a core network ordered access change scenario
EP2950583B1 (en) 2005-05-12 2020-06-03 Apple Inc. Using an access point name to select an access gateway node
WO2007001215A1 (en) * 2005-06-28 2007-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Means and methods for controlling network access in integrated communications networks
ATE510432T1 (de) 2005-07-08 2011-06-15 Huawei Tech Co Ltd Verfahren zum handover zwischen systemen
US8064400B2 (en) 2005-07-20 2011-11-22 Interdigital Technology Corporation Method and system for supporting an evolved UTRAN
EP1938518A4 (en) 2005-08-26 2013-08-14 Korea Electronics Telecomm APPARATUS AND METHOD FOR SERVICE CONTINUITY BETWEEN UMTS NETWORK AND WIRELESS LOCAL NETWORK
WO2007024116A1 (en) * 2005-08-26 2007-03-01 Electronics And Telecommunications Research Institute An apparatus and a method for service continuity between umts network and wlan
EP1938545B1 (en) 2005-09-27 2009-08-05 Telefonaktiebolaget LM Ericsson (publ) A network architecture and a method relating to access of user stations
EP1929815B1 (en) 2005-09-30 2018-05-30 Telefonaktiebolaget LM Ericsson (publ) Means and methods for improving the handover characteristics of integrated radio access networks
CN100536597C (zh) * 2005-11-01 2009-09-02 华为技术有限公司 演进的移动通信网及3gpp和非3gpp接入网之间移动性管理方法
CN100442747C (zh) * 2005-11-01 2008-12-10 华为技术有限公司 一种通用移动通信系统网络与演进网络互连的系统与方法
US7586878B2 (en) 2005-12-01 2009-09-08 Industrial Technology Research Institute Vertical handoff method and system in WLAN/3G integrated networks
AU2007226896B2 (en) 2006-03-20 2010-12-23 Qualcomm Incorporated Extended capability transfer between a user equipment and a wireless network
US8489096B2 (en) * 2006-06-01 2013-07-16 Nokia Corporation Inter-access handover with access specific policy control functions
CN100426777C (zh) * 2006-06-02 2008-10-15 华为技术有限公司 通过非3gpp技术接入3gpp演进网络的系统和方法
US8644247B2 (en) 2006-10-12 2014-02-04 Telefonaktiebolaget L M Ericsson (Publ) Inter-system handoffs in multi-access environments
US8086216B2 (en) * 2007-01-31 2011-12-27 Alcatel Lucent Mobility aware policy and charging control in a wireless communication network
WO2008094419A1 (en) 2007-01-31 2008-08-07 Interdigital Technology Corporation Method and apparatus for performing attachment procedures
MX2009013798A (es) * 2007-06-22 2010-02-10 Interdigital Tech Corp Metodo y aparato para la administracion de recursos en operaciones de transferencia.
JP2009050393A (ja) 2007-08-24 2009-03-12 Aruze Corp 遊技機
CN101822081B (zh) 2007-10-10 2013-03-27 捷讯研究有限公司 对多归属协议的支持
JP5138045B2 (ja) * 2007-11-16 2013-02-06 ノキア シーメンス ネットワークス オサケユキチュア システム間ハンドオーバのためのサービス品質のマッピング

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1893721A (zh) * 2005-07-08 2007-01-10 华为技术有限公司 一种系统间的切换方法
CN1984162A (zh) * 2006-04-30 2007-06-20 华为技术有限公司 演进网络中终端在非3gpp接入系统注册方法及系统
CN101150838A (zh) * 2006-09-18 2008-03-26 大唐移动通信设备有限公司 一种在系统间切换的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2104278A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010161478A (ja) * 2009-01-06 2010-07-22 Sharp Corp 移動通信システム、移動局及び管理局
US20120033638A1 (en) * 2009-02-09 2012-02-09 Ntt Docomo, Inc. Mobile communication method, gateway apparatus and server apparatus
JP2015053706A (ja) * 2009-09-18 2015-03-19 日本電気株式会社 通信システムと通信制御方法
US9143981B2 (en) 2009-09-18 2015-09-22 Nec Corporation Communication system and communication control method
US9544814B2 (en) 2009-09-18 2017-01-10 Nec Corporation Communication system, communication control method, and mobility management node
CN107666543A (zh) * 2016-07-29 2018-02-06 中国移动通信集团江苏有限公司 一种数据处理方法及装置

Also Published As

Publication number Publication date
EP3096583B1 (en) 2018-08-29
US8638750B2 (en) 2014-01-28
US11997697B2 (en) 2024-05-28
EP2104278B1 (en) 2014-04-30
KR101044685B1 (ko) 2011-06-28
KR20100003355A (ko) 2010-01-08
CN101330753B (zh) 2014-07-09
EP3442269A1 (en) 2019-02-13
US10945261B2 (en) 2021-03-09
CN101330753A (zh) 2008-12-24
EP2104278A1 (en) 2009-09-23
US20210153190A1 (en) 2021-05-20
EP2720509A2 (en) 2014-04-16
US20090285183A1 (en) 2009-11-19
EP3442269B1 (en) 2021-08-04
EP3096583A1 (en) 2016-11-23
JP2010519864A (ja) 2010-06-03
EP2720509B1 (en) 2018-08-22
JP5011396B2 (ja) 2012-08-29
EP3952601A1 (en) 2022-02-09
EP2104278A4 (en) 2010-07-14
EP2720509A3 (en) 2016-11-23
US20140098791A1 (en) 2014-04-10

Similar Documents

Publication Publication Date Title
WO2009000197A1 (fr) Procédé et équipement réseau pour établir et effacer des ressources
US11323921B2 (en) Method, system, and device for user detachment when a handover or change occurs in heterogeneous network
US9491665B2 (en) Data processing method and device
JP5044020B2 (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
US9913174B2 (en) Method, device and system for implementing optimized inter-rat handover
US8335512B2 (en) Method and device of network resource release processing
WO2008138259A1 (fr) Procédé et système et dispositif pour un procédé d'enregistrement
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2014121760A1 (zh) 切换过程中选择网络设备的方法和装置
US20130128816A1 (en) Method, Apparatus, and System for Setting Maximum Bandwidth
WO2009021431A1 (fr) Procédé et dispositif pour le transfert d'informations
EP2259657A1 (en) Method for indicating the bearer management of the service gateway
WO2009129748A1 (zh) 网络选择方法、移动终端、ip地址处理方法及系统
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
WO2012041073A1 (zh) 一种实现流迁移的方法及系统
WO2010069272A1 (zh) 一种网络切换的资源处理方法及装置
WO2009062392A1 (fr) Procédé de transfert de système, système de communication et entité pcrf
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
WO2012013103A1 (zh) 一种网关标识上报的方法及系统
WO2011137715A1 (zh) 单信道语音连续性实现方法及系统
WO2009082968A1 (fr) Procédé de traitement, appareil et système destinés à annuler le transfert de réseau
WO2012065293A1 (zh) 业务的接入控制方法、装置及用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08757809

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2809/KOLNP/2009

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2008757809

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009551096

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 20097023666

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE