[go: up one dir, main page]

WO2008154856A1 - Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau - Google Patents

Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau Download PDF

Info

Publication number
WO2008154856A1
WO2008154856A1 PCT/CN2008/071321 CN2008071321W WO2008154856A1 WO 2008154856 A1 WO2008154856 A1 WO 2008154856A1 CN 2008071321 W CN2008071321 W CN 2008071321W WO 2008154856 A1 WO2008154856 A1 WO 2008154856A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
network
resource release
source network
entity
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2008/071321
Other languages
English (en)
Chinese (zh)
Inventor
Yanglai Shuai
Weisheng Jin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Priority claimed from CN200710147343.0A external-priority patent/CN101330751B/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2008154856A1 publication Critical patent/WO2008154856A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the present invention relates to the field of communications, and in particular, to a method for releasing source network resources, a gateway entity, and a network device.
  • the Evolved Packet Core (EPC) in the wireless evolution network is the next generation wireless core network.
  • the evolved packet core network mainly includes a Mobility Management Entity (MME), a Serving Gateway between different access systems in the 3GPP (3rd Generation Partnership Project), and a 3GPP connection in the EPS system.
  • MME Mobility Management Entity
  • PDN GW Three logical function modules of the data gateway (PDN Gateway, PDN GW) between the system and the non-3GPP access system.
  • the 3GPP is a wireless communication network in which the terminal establishes IP connectivity to the data gateway through the serving gateway under the control of the mobility management entity; the non-3GPP is the IP connectivity established by the terminal to the data gateway under the control of the border access gateway.
  • the border access gateway and the data gateway are a wireless communication network directly connected through a tunnel.
  • the mobility management entity is responsible for the mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, security functions, etc., which corresponds to the current universal mobile communication system (Universal Mobile Telecommunications System) UMTS)
  • the control plane part of the internal GPRS service support node (SGSN) of the system; the service gateway directly faces the access of the 3GPP access system and is the user plane anchor point between the 3GPP internal access systems.
  • the serving gateway can serve as a local user plane anchor between the non-3GPP access system and the 3GPP access system.
  • a user can only have one serving gateway in a time period, that is, the serving gateway may occur.
  • the data gateway is a user plane anchor between the 3GPP access system and the non-3GPP system in the Evolved Packet System (EPS), providing users with packet data network (PDN) access, and a user can have multiple data at the same time.
  • EPS Evolved Packet System
  • the service gateway and the data gateway form an Evolved Packet System GW (EPS GW).
  • EPS GW Evolved Packet System GW
  • some methods of performing network handover in an evolved packet core network are provided, which may be between trusted non-3GPP and 3GPP, and untrusted between 3GPP and 3GPP. Referring to FIG. 3, it is a switching process of S2a and S5 based on proxy mobile IP ( ⁇ ) in a non-roaming scenario:
  • Step 301 The terminal completes the bearer establishment in the 3GPP, and accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway.
  • Step 302 The terminal discovers a trusted non-3GPP IP access system, and initiates a handover (HO).
  • Step 304 Perform an Extensible Authentication Protocol ( ⁇ ) authentication
  • Step 305 trigger layer 3 attach process
  • Step 306 Send the proxy binding update information to the data gateway, where the information carries parameters such as ⁇ - ⁇ , IP address, and the like;
  • Step 307 Return the binding information carrying the IP address.
  • Step 308 The terminal switches from 3GPP to non-3GPP, and completes bearer establishment.
  • Step 309 Layer 3 attachment is completed.
  • the inventor has found that the above-mentioned existing method for performing network switching in the evolved packet core network has at least the following problems: After the handover is completed, the source bearer resources are not released in time, resulting in waste of resources.
  • Network switching includes switching between homogeneous networks and switching between heterogeneous networks.
  • Switching between homogeneous networks such as switching between 3GPPs, is connected between the control plane entity mobility management entities of the two networks or the GPRS service support nodes.
  • the target network mobility management entity or the GPRS service support node releases the resources through the mobility management entity of the source network or the GPRS service support node; but the handover of the heterogeneous network is as shown in FIG. 3 above.
  • Switching between 3GPP and non-3GPP is more complicated than homogeneous networks.
  • For the switching between heterogeneous networks there is no direct interface between the control plane entities of the two networks. After the terminal successfully switches from the source network to the target network, the bearer of the source network is always idle and is not released in time. Waste of resources and reduce the efficiency of resource use.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method for releasing source network resources, a gateway entity, and a network device, which can timely and effectively release source network resources and improve network resource usage efficiency.
  • a method for releasing source network resources including: determining whether a handover from a source network to a target network has been completed; and when determining that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • a method for releasing source network resources including: after switching to a target network, the source network receives a resource release message initiated by the target network gateway entity; and the source network releases the resource after receiving the resource release message.
  • Providing a gateway entity comprising: a determining unit, a first sending unit, and a first receiving unit, wherein the determining unit is configured to determine whether a handover from the source network to the target network has been completed; the first sending unit is configured to be in the When the determining unit determines that the handover has been completed, the resource release message releasing the source network resource is sent to the source network.
  • a network device including a second receiving unit and a resource releasing unit, where the second receiving unit is configured to receive a resource release message initiated by a source network, where the resource release unit is configured to receive, at the second receiving unit, The resource of the target network is released after the message is described.
  • a network device including a third receiving unit and a second sending unit, where the third receiving unit is configured to receive a resource release message initiated by a target network, and the second sending unit is configured to receive, at the third receiving unit After the message is received, the trigger source network releases the resource.
  • the resource release message and the resource release completion response message exchanged between the target network and the source network are specifically provided.
  • the target network gateway entity After the switch to the target network, the target network gateway entity initiates a resource release operation to the source network, and implements the function of releasing the source bearer resources in time after switching between the networks. Improve the technical effect of source network resource usage efficiency.
  • FIG. 1 is a schematic structural diagram of an evolved network in a non-roaming scenario in the prior art
  • FIG. 2 is a schematic structural diagram of an evolved network in a roaming scenario of the prior art
  • FIG. 6 is a flowchart of a third embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 7 is a flow chart of a fourth embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 8 is a flowchart of a fifth embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 9 is a flowchart of a sixth embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 10 is a flowchart of a seventh embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 11 is a flowchart of an eighth embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 12 is a flowchart of a ninth embodiment of a method for releasing source network resources according to the present invention.
  • FIG. 13 is a schematic block diagram of a first embodiment of a gateway entity of the present invention.
  • FIG. 14 is a schematic block diagram of a first embodiment of a network device according to the present invention.
  • Figure 15 is a schematic block diagram of a second embodiment of the network device of the present invention.
  • Embodiments of the present invention provide a plurality of methods for releasing source network resources after completion of handover between networks, so as to improve usage efficiency of source network resources.
  • the target network of the handover may be 3GPP, and mainly includes a data gateway, a mobility management entity, a service gateway, and the like.
  • the present invention provides a basic implementation manner of a method for releasing source network resources, including the following steps: Step A: determining whether a handover from a source network to a target network has been completed;
  • Step B When it is judged that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • the resource release message and the resource release response message mechanism that are exchanged between the target network and the source network are specifically provided. After the switch to the target network is completed, the resource release operation to the source network is initiated by the target network gateway entity after the handover, and the function of releasing the source network resources in time after the network switch is implemented, thereby improving the source.
  • step B after the terminal switches to the target network, the data release process to the source network gateway entity may be initiated by the data gateway of the target network, and the initiated manner includes:
  • the data gateway directly sends a resource release message to the gateway entity of the source network, such as sending a message to: a service gateway or an Evolved Packet Data Gateway (ePDG) or an untrusted 3GPP gateway entity;
  • ePDG Evolved Packet Data Gateway
  • the data gateway sends a resource release message to the gateway entity of the source network through the AAA server/home subscriber server.
  • the inter-network handover may be a handover from a source non-3GPP to a target 3GPP, or may be switched from a source 3GPP to a target non-3GPP.
  • the non-3GPP includes: trusted non-3GPP and untrusted non-3GPP.
  • the source network gateway entity may be: a mobility management entity, a serving gateway, or a non-3GPP gateway entity.
  • the non-3GPP gateway entity may include an untrusted non-3GPP gateway entity, such as an evolved packet data gateway, or a trusted non-3GPP access gateway. If the 3GPP is UTRAN, the resources released by the GPRS source network may be bearer resources, and the bearer resources may include wireless or non-radio bearer resources, and may include wireless and non-radio bearer resources, and may also include wireless and/or S1.
  • Bearer resources (between the base station and the serving gateway).
  • the resource release message may be a resource release request (Release Release Request), a location update (Update Location), a location cancellation (Cancel Location), or any newly defined message, etc., for directly or indirectly informing the source network to perform a resource release operation;
  • the resource release completion response message may be a Resource Release Respone, a Cancel Location Ack, an Update Location Ack, or any newly defined message.
  • the location update and location fetch message is referred to as a resource release notification message, or a first resource release notification, a second resource release notification message; further, the resource release message sent to the source network may be
  • the trigger message for initiating the resource release process may also be a related message requesting release of the resource, such as a handover completion notification requesting release of the resource.
  • the target non-3GPP data gateway After the terminal completes the handover from the source 3GPP to the target non-3GPP, the target non-3GPP data gateway directly interacts with the source 3GPP service gateway, and releases the source 3GPP bearer resource; 2) After the terminal completes the handover from the source 3GPP to the target non-3GPP, the target non-3GPP data gateway passes the target non-3GPP AAA server, the source 3GPP home subscriber server, and the source 3GPP mobility management entity or the GPRS service support node. Interacting, releasing the bearer resources of the source 3GPP;
  • the data gateway of the target 3GPP directly interacts with the source non-3GPP gateway entity to release the bearer resources of the source non-3GPP;
  • the data gateway of the target 3GPP interacts with the source non-3GPP gateway entity through the AAA server, and releases the bearer resources of the source non-3GPP;
  • the mobility management entity or the GPRS service support node of the target 3GPP sends a message to the source non-3GPP gateway entity through the home subscriber server and the AAA server, and requests to release the bearer in the non-3GPP.
  • the target 3GPP service gateway directly connects with the source non-3GPP gateway. Entity interaction, releasing source non-3GPP bearer resources;
  • the target 3GPP service gateway passes the AAA proxy and the source non- The 3GPP gateway entity interacts to release the bearer resources of the source other than 3GPP;
  • the target 3GPP data gateway passes the source non-3GPP
  • the serving gateway interacts with the source non-3GPP gateway entity to release the bearer resources of the source non-3GPP;
  • the target non-3GPP data gateway sends a handover completion notification requesting release of the resource to the serving gateway of the source 3GPP, and the service gateway forwards the handover of the required release resource. Notifying, or reconstructing, a new bearer release notification to the mobility management entity or the GRPS service support node, through which the resource release procedure of the source network is initiated by the mobility management entity or the GPRS service support node.
  • FIG. 4 it is a first embodiment of a method for releasing source network resources in a handover process of the present invention.
  • the implementation manner is that after the terminal completes the handover from the source 3GPP to the target non-3GPP, the target non-3GPP The data gateway directly sends a resource release message to the serving gateway of the source 3GPP.
  • the premise that the terminal first releases the source bearer resource is: switching from the source 3GPP to the target non-3GPP, and the stage includes the following steps 401 and 402.
  • Step 401 The terminal completes bearer establishment in the 3GPP, and the terminal performs service data access by using the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 402 The terminal switches from 3GPP to non-3GPP, Complete the bearer establishment, and access the service data through the established bearer;
  • the bearer established in non-3GPP needs to pass through the serving gateway.
  • Step 403 Determine whether the handover from the source network to the target network has been completed.
  • Step 404 When it is determined that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • Switching from source 3GPP to target non-3GPP is a switch between heterogeneous networks.
  • the data gateway sends a resource release message, such as a bearer release request message, to the serving gateway, and initiates a radio and/or S1 bearer release procedure through the serving gateway to release the source 3GPP wireless and/or S1 carries resources.
  • a resource release message such as a bearer release request message
  • the following information is included in the bearer release request message: a Home of address (HOA) or/and a User Equipment ID of the terminal that completes the handover. Use this parameter to determine which resources need to be released.
  • HOA Home of address
  • User Equipment ID User Equipment ID
  • the source 3GPP receives a bearer release request from the data gateway.
  • Step 405 The source network releases the bearer resource.
  • the serving gateway of the source network initiates the process of releasing the radio and S1 bearers, releasing the radio bearers and/or S1 bearers in the 3GPP.
  • Step 406 The serving gateway of the source network returns a response message that the resource release is complete, such as a bearer release response message to the data gateway of the target network.
  • the serving gateway of the source network After the bearer is released, the serving gateway of the source network returns a bearer release response message to the data gateway, notifying that the data gateway bearer release is complete.
  • the data gateway of the target network receives the response message of the resource release completion returned from the source network, and completes release of the source network bearer resource.
  • FIG. 5 it is a second embodiment of a method for releasing source network resources in a handover process of the present invention.
  • the implementation manner is that after the terminal completes the handover from the source 3GPP to the target non-3GPP, the target non-3GPP The data gateway sends a resource release message to the source 3GPP mobility management entity through the AAA server and the home subscriber server.
  • the premise that the terminal first releases the source bearer resource is: switching from the source 3GPP to the target non-3GPP, and the stage includes the following steps 501 and 502.
  • Step 501 The terminal completes the bearer setup in the 3GPP, and the terminal accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 502 The terminal switches from 3GPP to non-3GPP, Complete the bearer establishment, and access the service data through the established bearer;
  • the bearer established in non-3GPP needs to pass through the serving gateway.
  • Step 503 Determine whether the handover from the source network to the target network has been completed.
  • Step 504 Upon determining that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • Switching from source 3GPP to target non-3GPP is a switch between heterogeneous networks.
  • the gateway entity of the target network such as the data gateway, sends a resource release message, such as a bearer release request, to the AAA server/home subscriber server.
  • the AAA server If the AAA server is not integrated with the home subscriber server, the AAA server sends a resource release message, such as a resource release notification message, to the home subscriber server.
  • a resource release message such as a resource release notification message
  • the following parameters are included in the resource release message: a home address or / and a user equipment identifier. Use this parameter to determine which resources need to be released.
  • Step 505 The home subscriber server sends another bearer release notification message to the mobile 3GPP mobile mobility management entity or the GPRS service support node.
  • the home subscriber server sends another bearer release notification to the source 3GPP's mobility management to implement a wireless and/or S1 bearer release procedure to release the source 3GPP's wireless and/or S1 bearer resources.
  • the bearer notification message may be an existing location cancel Cancel Location message carrying a home address or/and a user equipment identifier, or may be a newly defined message.
  • the source 3GPP mobility management entity receives a bearer release request from the data gateway.
  • Step 506 The source network releases the bearer resource.
  • the mobility management entity of the source network initiates a wireless and/or S1 bearer release procedure, releasing 3GPP Corresponding radio bearers and/or S1 bearers, this bearer release procedure is described in detail in existing protocols.
  • Step 507 The mobility management entity returns a response message that the resource release is completed to the home user service crying o
  • the response message of the completion of the resource release may be an existing location cancellation response Cancel Location Ack message, or may be a newly defined message.
  • Step 508 The home subscriber server/AAA server returns a response message that the resource release is completed to the data gateway of the target network, and notifies the data gateway that the bearer release is complete; and the data gateway receives the response message that the resource release completes returned from the source network.
  • the home subscriber server is required to send a response message that the resource release is complete to the AAA server, and the AAA server sends another resource release completion response message to the data gateway of the target network.
  • FIG. 6 a third embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the data gateway of the target 3GPP directly sends the resource release message to the source non-3GPP.
  • the premise that the terminal releases the source bearer resource first is: switching from the source non-3GPP to the target 3GPP, and the stage includes the following steps 601 and 602.
  • Step 601 The terminal completes the bearer setup in the non-3GPP, and accesses the service data by using the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 602 The terminal switches from the non-3GPP to the 3GPP. Complete the bearer establishment, and access the service data through the established bearer;
  • Step 603 Determine whether the handover from the source network to the target network has been completed.
  • Step 604 When determining that the handover is completed, the target network gateway entity sends a resource release message to the source network, and the source network receives a resource release message initiated by the target network gateway entity.
  • the gateway entity of the target 3GPP such as the data gateway, sends a resource release message, such as a bearer release request message, to the source non-3GPP gateway entity, and releases the source non-3GPP through the source non-3GPP bearer release procedure.
  • a resource release message such as a bearer release request message
  • the source non-3GPP gateway entity receives the bearer release request initiated by the data gateway of the target 3GPP.
  • Step 605 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • Step 606 The source network returns a response message that the resource release is complete, such as a bearer release response message to the data gateway of the target network, to complete release of the source network bearer resource.
  • the source non-3GPP gateway entity sends a bearer release response message to the data gateway of the target network, notifying that the data gateway bearer has been released.
  • FIG. 7 a fourth embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the data gateway of the target 3GPP sends a resource release message to the source non-3GPP through the AAA server.
  • the premise that the terminal first releases the source bearer resource is: switching from the source non-3GPP to the target 3GPP, and the stage includes the following steps 701 and 702.
  • Step 701 The terminal completes bearer setup in the non-3GPP, and accesses the service data by using the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 702 The terminal switches from non-3GPP to 3GPP. Complete the bearer establishment, and access the service data through the established bearer;
  • Step 703 Determine whether the handover from the source network to the target network has been completed.
  • Step 704 When it is determined that the handover is completed, the target network gateway entity sends a resource release message to the source network, where the source network receives a resource release message initiated by the target network gateway entity.
  • the data gateway of the target 3GPP sends a resource release message, such as a bearer release request message, to the source non-3GPP AAA server.
  • a resource release message such as a bearer release request message
  • the following parameters are included in the bearer release request message: a home address or/and a user equipment identifier, by which resources that need to be released are determined.
  • Step 705 The AAA server sends a bearer release notification message to the source non-3GPP gateway entity.
  • the radio and/or non-3GPP related bearer resources in the non-3GPP are released by the source non-3GPP bearer release procedure.
  • Step 706 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • the following steps 707 and 708 are the process in which the source network returns a resource release completion response message to the data gateway of the target 3GPP, and completes the release of the source network bearer resource:
  • Step 707 The source non-3GPP gateway entity returns a response message that the resource release is complete, such as a bearer release response message to the AAA server.
  • Step 708 The AAA server returns a resource release completion response message to the target 3GPP data gateway, and notifies the data gateway bearer release completion.
  • FIG. 8 a fifth embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the mobility management entity or the GPRS service support node sends the resource release message to the source non-3GPP gateway entity through the home subscriber server and the AAA server, and requests to release the source non-3GPP.
  • the premise that the terminal releases the source bearer resource first is: switching from the source non-3GPP to the target 3GPP, and the stage includes the following steps 801 and 802.
  • Step 801 The terminal completes the bearer setup in the non-3GPP, and the terminal accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 802 The terminal switches from the source non-3GPP to Target 3GPP, complete bearer establishment, and perform service data access through the established bearer;
  • Step 803 Determine whether the handover from the source network to the target network has been completed.
  • Step 804 When it is determined that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • the mobility management entity of the target 3GPP when determining that the handover is completed, sends a resource release notification to the AAA server/home subscriber server, and includes the following parameters in the notification: Home address or / And user equipment identification, through which parameters are determined to be released.
  • the resource release notification may be an existing location update Update Location message or a newly defined message.
  • Step 805 This step is optional. If the home subscriber server and the AAA server are integrated devices, this step is not required. If not, the home subscriber server sends another resource release notification to the AAA server after receiving the resource release notification.
  • the resource release notification sent by the home subscriber server may be an existing location cancel Cancel Location message, or may be a newly defined message. Moreover, the resource release notifications received and sent by the home subscriber server may be the same or different.
  • Step 806 The AAA server sends a resource release message, such as a resource release request, to a source non-3GPP gateway entity, and requests to release the source non-3GPP resources.
  • This resource release request message can be either an existing message or a newly defined message.
  • Step 807 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • the following steps 808 ⁇ 810 are responses to receive the release of the resource returned from the source network:
  • Step 808 If the home subscriber server and the AAA server are unified, after the resource release is completed, the information is sent to the AAA server/home subscriber server.
  • the source non-3GPP gateway entity returns a response resource Release Response message to the AAA server.
  • the response message for completion of this resource release may be an existing message or a newly defined message.
  • Step 809 This step is an optional step. If the home subscriber server and the AAA server are unified, the step is not needed. If the home subscriber server and the AAA server are separated, the AAA server returns a response release Cancel Location Ack message to the home. User server. This message can be either an existing message or a newly defined message.
  • Step 810 The home subscriber server returns a resource release completion response Update Location Ack message to the target 3GPP mobility management entity, notifying the mobility management entity source that the non-3GPP completes the release of the resource.
  • the mobility management entity of the target 3GPP receives the returned resource release completion response cancellation Interest.
  • FIG. 9 a sixth embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the implementation is in the roaming scenario of the S8 interface (the roaming interface between the data gateway and the serving gateway), that is, in the interface roaming scenario between the serving gateway and the data gateway, after the terminal switches from the source non-3GPP to the target 3GPP, the terminal visits When the local service gateway does not change, the resource is sent by the visited service gateway.
  • the premise that the terminal releases the source bearer resource is: switching from the source non-3GPP to the target 3GPP, and the following steps include the following steps 901 and 902. .
  • Step 901 The terminal completes the bearer setup in the non-3GPP, and the terminal accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 902 The terminal switches from the source non-3GPP to Target 3GPP, complete bearer setup, and perform service data access through the established bearer; in the handover process, the visited service gateway remains unchanged, that is, after handover, the 3GPP accesses the same visited service gateway as the source non-3GPP;
  • Step 903 Determine whether the handover from the source network to the target network has been completed.
  • Step 904 When it is determined that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • the target serving gateway of the target 3GPP sends a resource release message, such as a bearer release request message, to the gateway entity of the source non-3GPP; the following information is included in the bearer release request message: the home address or/and User equipment identity, by which wireless and/or non-radio resources that need to be released are determined;
  • the source non-3GPP gateway entity receives the resource release message initiated by the visited service gateway.
  • Step 905 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • Step 906 The source network returns a response message that the resource release is complete, such as a bearer release response message to the visited service gateway, to complete release of the source network bearer resource.
  • the gateway entity of the source non-3GPP returns a bearer release response message, and notifies the visited service gateway that the bearer release has been completed.
  • the visited service gateway receives the returned resource release completion response message.
  • FIG. 10 a seventh embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the implementation is in the S8 interface roaming scenario, that is, in the interface roaming scenario between the serving gateway and the data gateway, after the terminal switches from the source non-3GPP to the target 3GPP, the visited service gateway does not occur any more.
  • the premise that the terminal first releases the source bearer resource is: switching from the source non-3GPP to the target 3GPP, and the stage includes the following steps 1001 and 1002.
  • Step 1001 The terminal completes the bearer setup in the non-3GPP, and the terminal accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 1002 The terminal switches from the source non-3GPP to Target 3GPP, complete bearer setup, and perform service data access through the established bearer; in the handover process, the visited service gateway remains unchanged, that is, after handover, the 3GPP accesses the same visited service gateway as the source non-3GPP;
  • Step 1003 Determine whether the handover from the source network to the target network has been completed.
  • Step 1004 After determining that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • the visited service gateway of the target 3GPP initiates a resource release message, such as a bearer release request, to the visited network AAA proxy.
  • a resource release message such as a bearer release request
  • the following parameters are included in the message: the home address or / and the user equipment identifier, and the resources that need to be released are determined by this parameter;
  • Step 1005 The AAA proxy sends a resource release notification message to the source non-3GPP gateway entity.
  • the source non-3GPP gateway entity receives the bearer release request initiated by the visited service gateway.
  • Step 1006 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • the following steps 1007 and 1008 are the response messages from the source network returning the resource release completion to the target.
  • the visited service gateway of the 3GPP completes the process of releasing the source network bearer resources.
  • Step 1007 The source non-3GPP gateway entity returns a response message that the resource release is complete, such as a bearer release response message to the AAA proxy.
  • Step 1008 The AAA proxy sends another response message that the resource release is completed to the visited place.
  • the service gateway notifies the visited service gateway that the bearer release is complete.
  • an eighth embodiment of a method for releasing source network resources in a handover process of the present invention is shown.
  • the S8 interface roaming scenario that is, in the interface roaming scenario between the serving gateway and the data gateway, after the terminal switches from the source non-3GPP to the target 3GPP, when the visited serving gateway is replaced, the data gateway sends the resource.
  • the premise that the terminal releases the source bearer resource first is: switching from the source non-3GPP to the target 3GPP, and the stage includes the following steps 1101 and 1102.
  • Step 1101 The terminal completes the bearer setup in the non-3GPP, and accesses the service data by using the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 1102 The terminal switches from the source non-3GPP to Target 3GPP, complete bearer setup, and perform service data access through the established bearer; in the handover process, 3GPP accesses from the newly visited service gateway, that is, after the handover, the visited service gateway is replaced;
  • Step 1103 Determine whether the handover from the source network to the target network has been completed.
  • Step 1104 When it is determined that the handover is completed, the target network gateway entity sends a resource release message to the source network.
  • the data gateway of the target 3GPP sends a resource release message, such as a bearer release request message, to the visited service gateway of the source non-3GPP access, and includes the following parameters in the bearer release request message: / and user equipment identification, through which parameters are determined to be released;
  • Step 1105 The visited service gateway sends another bearer release message to the gateway entity of the source non-3GPP.
  • the source non-3GPP gateway entity receives the bearer release request initiated by the data gateway.
  • Step 1106 The source network releases the bearer resource.
  • Source non-3GPP releases wireless and/or non-3GPP related bearer resources, which may be released using techniques not specified by 3GPP.
  • the following steps 1107 and 1108 are the source network returning a bearer release response message to the target network.
  • the data gateway completes the process of releasing the source network bearer resources.
  • Step 1107 The gateway entity of the source non-3GPP sends a response message that the resource release is completed, such as a bearer release response message to the visited service gateway.
  • Step 1108 The visited service gateway returns a bearer release response message to the data gateway of the source network.
  • FIG. 12 it is a ninth embodiment of a method for releasing source network resources in a handover process of the present invention.
  • the target non-3GPP data gateway sends a bearer release notification to the source 3GPP mobility management entity through the serving gateway.
  • the premise that the terminal first releases the source bearer resource is: switching from the source 3GPP to the target non-3GPP, and the stage includes the following steps 1201 and 1202.
  • Step 1201 The terminal completes the bearer setup in the 3GPP, and the terminal accesses the service data through the established bearer, and the uplink and downlink data is transmitted between the terminal and the data gateway by using the bearer;
  • Step 1202 The terminal switches from 3GPP to non-3GPP, Complete the bearer establishment, and access the service data through the established bearer;
  • bearers established in non-3GPP may need to pass through the serving gateway.
  • Step 1203 Determine whether the handover from the source network to the target network has been completed.
  • Step 1204 When it is determined that the handover is completed, the target network data gateway entity sends a handover completion notification (carrying an IP address) requesting to release the resource to the mobility management entity through the serving gateway.
  • the message is sent through the two segments of the network, and the segment network is Another network between the target network data gateway and the service gateway is between the service gateway and the mobility management entity.
  • the two pieces of messages may be based on the same or different protocols, may be a handover completion notification carrying the required release resource identifier, or may be a simple handover completion notification, and the mobility management entity receives the message and follows the target network.
  • the service gateway can transparently transmit the message sent by the data gateway.
  • the message sent by the data gateway can also be processed, and a new message is reconstructed and sent to the mobility management entity;
  • Step 1205 The mobility management entity sends a delete bearer request message (bringing the tunnel endpoint identifier TEID, Teardown lnd parameter) to the serving gateway and the data gateway, and requests to delete the bearer.
  • This step includes the mobility management entity sending a delete bearer request message to the serving gateway, and the serving gateway sending a delete bearer request message to the data gateway.
  • Two messages can be based on different protocols, and the service gateway can also To reconstruct a new message to the data gateway based on the received message. Teardown lnd is an optional parameter. If you need to delete all bearers with the same IP address as this TEID at one time, you need to set the Teardown Ind to 1.
  • Step 1206 The data gateway and the serving gateway return a bearer response message to the mobility management entity, and notify the bearer release completion.
  • This step may also include two pieces of messages, which may also be constructed based on different protocols;
  • Step 1207 The mobility management entity sends a bearer release message to the NodeB, and requests the NodeB to release related resources about the terminal.
  • Step 1208 The mobility management entity or the GPRS service support node returns, by using the service gateway, the handover completion response message indicating that the resource release is completed, notifying that the data gateway resource release is completed, and the data gateway of the target network receives the return.
  • the switch completes the response message.
  • This step is an optional step. If the data gateway knows in the previous delete bearer message that the mobility management entity has initiated the process of releasing the bearer, this step can be omitted.
  • the present invention further provides a tenth embodiment of the method for releasing source network resources, including the following steps:
  • the source network after switching to the target network, the source network receives a resource release message initiated by the target network gateway entity;
  • step 2) it may further comprise:
  • the source network returns the release complete response message to the target network gateway entity.
  • the foregoing embodiment is a method for releasing source bearer resources in different scenarios, but the method for releasing source bearer resources is not limited to the above examples.
  • the process of releasing the resource may be performed after switching between non-3GPP and non-3GPP.
  • the storage medium referred to herein is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like.
  • the present invention also provides a first embodiment of a gateway entity.
  • the gateway entity includes: The determining unit 1310 is configured to determine whether the handover from the source network to the target network has been completed.
  • the first sending unit 1320 is configured to: when the determining unit determines that the handover has been completed, send a resource release message that releases the source network resource to Source network.
  • the gateway entity of the present embodiment is specifically proposed, and the determining unit 1310 determines whether The switching between the networks has been completed.
  • the first sending unit 1320 and the first receiving unit 1330 respectively provide a resource release message and a response message mechanism for completing the resource release interaction between the target network and the source network.
  • the first sending unit 1320 of the gateway entity initiates a resource release message, which implements the function of releasing the source bearer resources after the network switching, thereby improving the use efficiency of the source network bearer resources.
  • a resource release message which implements the function of releasing the source bearer resources after the network switching, thereby improving the use efficiency of the source network bearer resources.
  • the gateway entity further includes a first receiving unit 1330, configured to receive a bearer release response message returned after the source network completes resource release.
  • the gateway entity is a data gateway
  • the first sending unit may be specifically configured to:
  • the gateway entity may also be a mobility management entity, and the first sending unit may be specifically configured to:
  • the gateway entity may also be a serving gateway, where the first sending unit may be specifically configured to: send a resource release request to a source non-3GPP gateway entity, to trigger the resource release process; or
  • the present invention further provides a first implementation manner of a network device, including:
  • the second receiving unit 1410 is configured to receive a resource release message initiated by the target network.
  • the resource release unit 1420 is configured to release the resource of the source network after the second receiving unit 1410 receives the message.
  • the network device of the present embodiment is specifically proposed by using the second receiving unit 1410 because the technical problem of the source bearer resource cannot be released in time after the network is switched between the networks.
  • Receiving the resource release message and the resource release completion response message mechanism, after switching to the target network at an appropriate time, receiving the resource release message and using the resource release unit 1420 to release the resource, specifically releasing the source bearer resource after the network switchover The function achieves the technical effect of improving the efficiency of using the source network to carry resources.
  • the network device may be a serving gateway, a mobility management entity, a GPRS service support node, an evolved packet data gateway, or a trusted non-3GPP access gateway.
  • the response unit 1430 may be further included, configured to return a response message of the completion of the resource release to the source network after the resource release unit 1420 completes the resource release.
  • the present invention further provides a second implementation manner of a network device, including:
  • the third receiving unit 1510 is configured to receive a resource release message initiated by the target network.
  • the second sending unit 1520 is configured to trigger the release of the resource by the target network after the third receiving unit 1510 receives the message.
  • the network device may be a serving gateway, an AAA server/home subscriber server, a GPRS monthly support node or an AAA proxy.
  • the foregoing network device implementation manner can assist the bearer release request initiated by the target network after the inter-network handover, and can release the source bearer related resources, improve the use efficiency of the source network bearer resources, and reduce resource waste.
  • the foregoing determining unit 1310, the first sending unit 1320, and the first receiving unit 1330 in the first embodiment of the gateway entity of the present invention may be integrated into one processing module.
  • the units in the mode can also be integrated in one processing module. It can be implemented in the form of hardware, and the software-implemented part can also be implemented in the form of software function modules. Accordingly, embodiments of the invention may be sold or used as separate products, and the software implementable portions may also be stored in a computer readable storage medium for sale or use.
  • the present invention can at least produce the following technical effects:
  • the source network bearer resources can be released in time to improve the use efficiency of the source network bearer resources and reduce resource waste.
  • the method of releasing the source bearer can be applied to the scenario of switching between various networks, and the operability is good; the step/device for increasing the release of the source bearer by using the original system/protocol can be controlled at a lower cost.
  • the method, the gateway entity, and the network device for releasing the source network resources in the handover process provided by the present invention are described in detail by using specific embodiments. The foregoing description of the embodiments is only used to help understand the method and the idea of the present invention; In the meantime, the present invention is not limited by the scope of the present invention.

Landscapes

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

Abstract

L'invention concerne un procédé, une entité de passerelle et un dispositif de réseau servant à libérer des ressources de réseau. Ledit procédé servant à libérer des ressources de réseau consiste à : juger si le transfert intercellulaire du réseau source au réseau de destination se produit, l'entité de passerelle du réseau de destination envoyant au réseau source un message de libération des ressources au moment où le transfert intercellulaire est exécuté ; recevoir le message de réponse du réseau source, ledit message répondant à l'exécution de la libération des ressources.
PCT/CN2008/071321 2007-06-19 2008-06-16 Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau Ceased WO2008154856A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710111962.4 2007-06-19
CN200710111962 2007-06-19
CN200710147343.0A CN101330751B (zh) 2007-06-19 2007-08-21 释放源网络资源的方法、网关实体以及网络设备
CN200710147343.0 2007-08-21

Publications (1)

Publication Number Publication Date
WO2008154856A1 true WO2008154856A1 (fr) 2008-12-24

Family

ID=40155910

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071321 Ceased WO2008154856A1 (fr) 2007-06-19 2008-06-16 Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau

Country Status (1)

Country Link
WO (1) WO2008154856A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101932058A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 释放承载资源的方法及设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005067179A1 (fr) * 2004-01-08 2005-07-21 Sk Telecom Co., Ltd. Systeme de service de paquets de donnees dans un reseau mixte de transmission asynchrone et de transmission synchrone et procede de commutation associe
WO2006057925A2 (fr) * 2004-11-22 2006-06-01 Motorola, Inc. Procede et systeme pour transfert actif inter-technologie de dispositif de communications hybride
WO2007004846A2 (fr) * 2005-07-05 2007-01-11 Lg Electronics Inc. Procede de support d'un transfert independant de medias avec fonction de gestion de ressources dans un systeme de communications mobiles

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005067179A1 (fr) * 2004-01-08 2005-07-21 Sk Telecom Co., Ltd. Systeme de service de paquets de donnees dans un reseau mixte de transmission asynchrone et de transmission synchrone et procede de commutation associe
WO2006057925A2 (fr) * 2004-11-22 2006-06-01 Motorola, Inc. Procede et systeme pour transfert actif inter-technologie de dispositif de communications hybride
WO2007004846A2 (fr) * 2005-07-05 2007-01-11 Lg Electronics Inc. Procede de support d'un transfert independant de medias avec fonction de gestion de ressources dans un systeme de communications mobiles

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; technical specification group services And system aspects; feasibility study of mobility between 3GPP-WLAN Interworking and 3GPP Systems (Release 8)", 3GPP TR 23.937 V0.0.2, 11 April 2007 (2007-04-11), XP050282061, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/archive/23_series/23.937/23937-002.zip> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101932058A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 释放承载资源的方法及设备

Similar Documents

Publication Publication Date Title
TWI713341B (zh) 5g會話管理狀態映射的方法及使用者設備
CN112400341B (zh) 处理多址协议数据单元会话的方法及其用户设备
JP5827254B2 (ja) 相異なるワイヤレス通信アーキテクチャ間のモビリティのための資源管理
US8855045B2 (en) Method and system for controlling establishment of local IP access
TW201944840A (zh) 處理qos 流的方法及使用者設備
CN105307222B (zh) 释放源网络资源的方法、网关实体以及网络设备
TW202021411A (zh) 無效協定資料單元會話之處理方法及其使用者設備
CN101272576B (zh) 一种用户信令跟踪方法及通讯系统以及用户设备
CN101848443B (zh) 通信业务切换处理方法、网络系统与互通功能实体
WO2011079634A1 (fr) Procédé de délestage de trafic, entité fonctionnelle de délestage de trafic et système de délestage de trafic
WO2014056445A1 (fr) Procédé, système et contrôleur pour transfert de routage
WO2010017747A1 (fr) Procédé, dispositif et système servant à obtenir des informations d’une zone de localisation dans un transfert de réseau hétérogène
TWI792590B (zh) 協定資料單元會話建立接受處理方法及使用者設備
JP2018510586A (ja) ユーザー・プレーンベアラの確立を制御する方法及び装置
WO2012171403A1 (fr) Procédé et système prenant en charge la communication à plusieurs interfaces et connexions multiples
JP7507144B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2014029065A1 (fr) Procédé et dispositif d&#39;affichage de nom de réseau
WO2011143997A1 (fr) Procédé et dispositif de routage
WO2011011945A1 (fr) Procédé d&#39;envoi de message et nœud de support gprs de desserte
WO2015100661A1 (fr) Procédé, dispositif et système pour sélectionner un centre d&#39;appel d&#39;urgence
US20130058312A1 (en) Method, apparatus and system for processing local address in shunt connection
CN108990124A (zh) 语音通话与数据业务切换方法及装置
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
TW202044874A (zh) 協作後之特性支援增強技術
WO2011020418A1 (fr) Procédé d&#39;activation de connexion pour changer une passerelle de desserte tandis qu&#39;un terminal est converti à un état de connexion, et système correspondant

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: 08757732

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08757732

Country of ref document: EP

Kind code of ref document: A1