WO2009097772A1 - 一种资源释放控制方法及通讯***以及相关设备 - Google Patents

一种资源释放控制方法及通讯***以及相关设备 Download PDF

Info

Publication number
WO2009097772A1
WO2009097772A1 PCT/CN2009/070159 CN2009070159W WO2009097772A1 WO 2009097772 A1 WO2009097772 A1 WO 2009097772A1 CN 2009070159 W CN2009070159 W CN 2009070159W WO 2009097772 A1 WO2009097772 A1 WO 2009097772A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
management network
original
bearer
system management
Prior art date
Application number
PCT/CN2009/070159
Other languages
English (en)
French (fr)
Inventor
Weihua Hu
Yanping Zhang
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=40829357&utm_source=***_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2009097772(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 EP09708079.0A priority Critical patent/EP2187687B2/en
Publication of WO2009097772A1 publication Critical patent/WO2009097772A1/zh
Priority to US12/779,655 priority patent/US8325682B2/en
Priority to US13/182,274 priority patent/US8144665B2/en
Priority to US13/660,613 priority patent/US8830962B2/en

Links

Classifications

    • 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
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers

Definitions

  • the present invention relates to the field of communications, and in particular, to a resource release control method, a communication system, and related devices.
  • the core network of the wireless evolution network namely System Architecture Evolution (SAE), mainly includes Mobility Management Entity (MME), Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW). , Packet data network Gateway ) Three functions are also included.
  • SAE System Architecture Evolution
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • Three functions are also included.
  • the MME is responsible for non-access stratum (NAS, Non-Access Stadium) signaling encryption, roaming, tracking, etc., assigning user temporary identity, security functions, etc., which corresponds to the current universal mobile communication system (UMTS, Universal Mobile Telecommunications).
  • NAS non-access stratum
  • UMTS Universal Mobile Telecommunications
  • the control plane part of the System Internal Service GPRS Support Node (SGSN);
  • the S-GW is responsible for the local mobility anchor and the mobility anchor and lawful interception information within the 3GPP (Third Generation Partnership Projects) system; the P-GW is responsible for policy enforcement and billing and lawful interception. Related features.
  • the Home Subscriber Server (HSS) is used to store user subscription information.
  • ISR Idle mode signaling reduction
  • the original MME Under the dual registration mechanism, after the original MME establishes an ISR mechanism with the SGSN, if the UE moves to a new MME or SGSN, it will initiate a Tracking Area Update (TAU) or Routing Area Update (RAU). Process. If the MME or the SGSN of the target side does not support the ISR, the MME or the SGSN of the target side does not carry the ISR activation indication when updating the bearer information to the S-GW, and the S-GW deletes its own bearer context after receiving the bearer update request. And request the original The MME or SGSN on the side deletes the bearer context.
  • TAU Tracking Area Update
  • RAU Routing Area Update
  • the version attribute of the MME or the SGSN on the target side indicates that it does not support interaction with the S-GW, and does not support the ISR
  • the target MME or the SGSN cannot exchange signaling with the S-GW. Therefore, the S-GW cannot be controlled to delete the bearer context on the primary MME or the SGSN according to the prior art scheme.
  • the embodiment of the present invention provides a resource release control method, a communication system, and a related device, which can enable the target-side management network element to delete the original-side heterogeneous system management network without supporting interaction with the S-GW and not supporting the ISR. Bear on the yuan.
  • the method includes: obtaining version information of the target management network element; if the version information indicates that the target management network element does not interact with the serving gateway S-GW, and If the ISR is not supported, the bearer in the original system management NE is deleted.
  • the communication system provided by the embodiment of the present invention includes: a primary side management system network element, configured to be activated
  • the version information of the target management network element is obtained. If the version information indicates that the target management network element does not interact with the S-GW, and does not support the ISR, And sending a bearer deletion message; the original system management network element is configured to receive the bearer deletion message, and delete the bearer according to the bearer deletion message.
  • the mobility management network element is connected to the radio access network, and is configured to manage the mobile state of the user, and includes: an acquiring unit, configured to obtain version information of the peer management network element; and a determining unit, configured to: Determining, according to the version information of the peer management network element obtained by the obtaining unit, whether the indication does not support the interaction with the S-GW, and does not support the ISR; the bearer deletion control unit, if the judgment result of the determining unit is not the peer management network element Supports interaction with the S-GW and does not support ISR.
  • the bearer deletion process is performed.
  • the gateway device provided by the embodiment of the present invention is connected to the radio access network and the packet data network, and is configured to carry user data transmission between the radio access network and the packet data network, and includes: a receiving unit, configured to receive the same side system
  • the bearer deletion message sent by the management network element is deleted.
  • the deletion control unit is configured to: according to the bearer deletion message, instruct the original side different system management network element to delete the bearer on the original side different system management network element.
  • the target side management network element after obtaining the version information of the target-side management network element, determining that the version information indicates that the target-side management network element does not interact with the serving gateway S-GW, and does not support the idle signaling mode ISR.
  • the bearer in the original system management network element may be deleted according to the version information. Therefore, in the embodiment of the present invention, the target side management network element can also delete the original side without supporting the interaction with the S-GW and not supporting the ISR. The bearer on the different system management network element.
  • FIG. 1 is a flowchart of a first embodiment of a resource release control method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a second embodiment of a resource release control method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a third embodiment of a resource release control method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a fourth embodiment of a resource release control method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a fifth embodiment of a resource release control method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a sixth embodiment of a resource release control method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a seventh embodiment of a resource release control method according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of an embodiment of a communication system according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an embodiment of a mobility management network element according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an embodiment of a gateway device according to an embodiment of the present invention.
  • the embodiment of the present invention provides a resource release control method, a communication system, and a related device, which are used to enable the target side management network element to delete the original side different system management without supporting the S-GW interaction and not supporting the ISR.
  • the bearer context on the NE is used to enable the target side management network element to delete the original side different system management without supporting the S-GW interaction and not supporting the ISR.
  • the user equipment of the ISR is switched from the primary network to the target network, and the version information of the target management network element is obtained.
  • the bearer in the original-side different-system management network element is deleted.
  • the bearer in the original system management network element may be deleted. It should be noted that, in the following embodiments, deleting the bearer in the original system management network element refers to deleting the bearer context in the original system management network element.
  • the target-side management network element can also delete the bearer context on the original-side heterogeneous system management network element without supporting the interaction with the S-GW and not supporting the ISR.
  • the primary side different system management network element refers to the original user's original location.
  • the MME the original system management network element refers to the SGSN that establishes the ISR mechanism with the original MME.
  • the target side management network element refers to the SGSN where the user moves.
  • the original side different system management network element, the original side with the system management network element, and the target side management network element may also be other situations.
  • the target side management network element is the MME
  • the original The remote system management network element is the SGSN
  • the original system management network element is the MME.
  • the original side is managed by the same system management network element and the target side management network.
  • the message so that the original side system deletes its own bearer context.
  • the UE sends a RAU Request message to the target side management network element.
  • the UE After the UE moves to the coverage range of other MMEs or SGSNs, the UE sends a packet temporary mobile subscriber identity (P-TMSI, Packet Temporary Mobile Subscriber Identity) and a globally unique temporary identifier (GUTI, Globally Unique Temporary) to the target side management network element.
  • P-TMSI Packet Temporary Mobile Subscriber Identity
  • GUI globally unique temporary identifier
  • the target-side management NE sends a Context Request message to the original system management network element. After receiving the RAU Request message sent by the UE, the target-side management NE sends a Context Request message to the original system management network element to request context information.
  • the target side management network element performs protocol version detection with the original system management network element, and the original system management network element can learn the general wireless packet service of the target side management network element.
  • the version of the GTP version is displayed in the lower version, such as GTP V0 or GTP V1
  • the original system management NE can know the version of the target management NE.
  • the information is in the Pre-Rel-8 version. That is, the target-side management network element does not support the interaction with the S-GW, and does not support the ISR.
  • Pre-Rel-8 is used as an example for description. It can be understood that, in practical applications, Other types do not support interaction with S-GW and do not support ISR versions.
  • the foregoing describes the case where the original side management network element learns the version information of the target side management network element through the detection of the GTP information. It can be understood that the target side management network element can also use the Context Request message in step 102 to set its own The version information is sent to the original system to manage the network element.
  • the specific method may be to extend a field in the Context Request message to indicate the version information of the target side management network element, or to add an identifier to the existing field for indicating Version information, or other means of indication.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR.
  • the original side and the system management network element send a Context Response message to the target side management network element, and return the mobile phone context information.
  • the target-side management network element sends a Context Ack message to the original system management network element to the original system.
  • the target-side management network element can report the target-side management to the original system management network element through the Context Request message in step 102.
  • the version information of the network element may be sent to the original system management network element by using the Context Ack message in step 104.
  • the specific sending mode is the same as the manner of sending the message through the Context Request message. I will not repeat them here.
  • the target side management network element sends a message update bearer context to the P-GW.
  • the original system and the system management network element send a bearer deletion message to the S-GW, and the bearer deletion message instructs the S-GW to delete the bearer.
  • S - The GW deletes its own bearer, which means that the S-GW deletes its own bearer context and releases the bearer. Resources.
  • the S-GW After receiving the bearer deletion message sent by the original system with the system management NE, the S-GW deletes its own bearer context and releases the bearer resource.
  • the original side and the system management network element notify the original system management network element to delete the context.
  • the original side management system network element passes the GTP information, or the step 102
  • the Context Request message, or the Context Ack message in step 104 has obtained the version information of the target side management network element obtained from the target side management network element, so the original side system management network element can be notified to delete its bearer context.
  • the original side and the system management network element and the original side different system management network element mutually store the other party information, such as control plane information, and the control plane information includes the address information of the peer end.
  • the original system and the system management network element can obtain the address information of the original system management network element according to the pre-stored information, and send a bearer deletion message to the original system management network element according to the address information.
  • the reason for carrying the delete bearer is: "The target-side management NE does not support ISR.”
  • the target-side management network element may select an appropriate timing to perform, for example, the timer expires, that is, after the Context ACK message is received, the execution still does not occur within the preset time.
  • the target-side management network element may select an appropriate timing to perform, for example, the timer expires, that is, after the Context ACK message is received, the execution still does not occur within the preset time.
  • the original side different system management network element deletes the local and UE related bearers.
  • the original side system management network element After receiving the bearer message, the original side system management network element deletes the local bearer context associated with the UE.
  • the original inter-system management network element may also notify the S-GW to delete the bearer.
  • the meaning of the S-GW delete bearer is the same as the meaning of the S-GW delete bearer in step 107, that is, the same This includes deleting the bearer context on the S-GW and releasing the bearer resources.
  • the step 107 and the step 109 can be implemented in combination to delete the bearer context on the S-GW and completely release the related bearer resources.
  • the S-GW can allocate bearer resources between the S-GW and the original system management network element.
  • the S-GW The bearer resource may also be allocated between the original system and the original system management network element. If the bearer deletion request in step 107 only requires the S-GW to release the bearer resource between the S-GW and the original system management network element, the step is 109, the original side system also needs to notify the S-GW to delete the bearer context, and release the bearer resources between the S-GW and the original side different system management network element.
  • the S-GW is The bearer resource is not allocated between the original system, and in step 107, the S-GW has deleted its own bearer context according to the indication, and releases the bearer between the S-GW and the original system management network element. In step 109, the original heterogeneous system management network element may not notify the S-GW to delete the bearer.
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the host side saves the bearer deletion message according to the locally saved address information to the corresponding original system management network element, so that the original The system management network element of the remote system deletes its own bearer context.
  • the original system management network element can also delete the bearer context of the original system management network element by using the S-GW.
  • the original system management network element after the original system management network element obtains the version information of the target side management network element, the original side sends a bearer deletion message to the S-GW, and the S-GW controls the original side. The system management network element deletes its bearer context.
  • the UE sends a RAU Request message to the target side management network element.
  • the UE After the UE moves to the coverage of other MMEs or SGSNs, the UE sends a RAU Request message carrying the P-TMSI and the GUTI cell to the target side management network element to request registration in the target side management network element.
  • the target-side management network element sends a Context Request message to the original system management network element to the original system. After receiving the RAU Request message sent by the UE, the target-side management network element sends a Context Request message to the original system management network element to request context information.
  • the target side management network element performs the protocol version detection between the original system management network element and the original system management network element, and the original system management network element can obtain the GTP version of the target side management network element.
  • the GTP version is displayed in a lower version, such as GTP V0 or GTP V1
  • the original system management NE can know that the version information of the target management NE is Pre-Rel-8, that is, the target management NE.
  • the interaction with the S-GW is not supported, and the ISR is not supported.
  • Pre-Rel-8 is used as an example for description. It can be understood that in the actual application, other types of unsupported and The S-GW interacts and does not support the version of the ISR.
  • the foregoing describes the case where the original side management system network element learns the version information of the target side management network element through the detection of the GTP information. It can be understood that the target side management network element can also go through step 202.
  • the Context Request message in the Context Request message is used to inform the original side of the same system management network element.
  • the specific manner may be to extend a field in the Context Request message to indicate the version information of the target side management network element, or in the existing Add an identifier to the field to indicate version information, or other means of indication.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR.
  • the original system management network element sends a Context Response message to the target side management network element, and returns a mobile phone context information.
  • the target-side management network element sends a Context Ack message to the original system management network element to the original system.
  • the target-side management network element can report the target-side management to the original system management network element through the Context Request message in step 202.
  • the version information of the network element may be sent to the original system management network element by using the Context Ack message in step 204.
  • the specific sending mode is the same as the manner of sending the message through the Context Request message. I will not repeat them here.
  • the target side management network element sends a message update bearer context to the P-GW.
  • the primary side and the system management network element send a bearer deletion message to the S-GW, and the S-GW deletes its own bearer context according to the bearer deletion message and releases the bearer resource.
  • the S-GW notifies the original side different system management network element to delete the context.
  • the original side cooperates with the system management network element to pass the GTP information, or
  • the Context Request message, or the Context Ack message in the step 204 has obtained the version information of the target side management network element obtained from the target side management network element, so in the step 207, the original side and the system management network element delete the bearer sent to the S-GW.
  • the message indicates that the S-GW deletes its own bearer, and also indicates that the S-GW controls the original side different system management network element to delete its bearer context.
  • the S-GW sends a 7-load deletion message to the original system-specific management network element according to the address information in the S-GW, and the S-GW sends the message to the original system.
  • the meta deletes its 7-load context.
  • the original side system management network element After receiving the bearer message, the original side system management network element deletes the local bearer context associated with the UE.
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the bearer deletion message sent by the original system with the system management network element to the S-GW defaults to request the S-GW to control the original system management network element to delete the bearer context. It can be understood that, in practical applications, the original application The same system management network element can also notify the S-GW to control the original system-specific network management network element to delete its bearer context in an explicit manner.
  • the device After the original system and the system management network element obtain the version information of the target side management network element, the device sends a bearer deletion message including the control cell to the S-GW, where the control information element is used to indicate that the original side system is controlled by the S-GW.
  • the management NE deletes its bearer context.
  • the UE sends a RAU Request message to the target side management network element.
  • the UE After the UE moves to the coverage of other MMEs or SGSNs, the UE sends a RAU Request message carrying the P-TMSI and the GUTI cell to the target side management network element to request registration in the target side management network element.
  • the target-side management network element sends a Context Request message to the original system management network element. After receiving the RAU Request message sent by the UE, the target-side management network element sends a Context Request message to the original system management network element to request context information.
  • the target side management network element performs the protocol version detection between the original system management network element and the original system management network element, and the original system management network element can obtain the GTP version of the target side management network element.
  • the GTP version is displayed in a lower version, such as GTP V0 or GTP V1
  • the original system management NE can know that the version information of the target management NE is Pre-Rel-8, that is, the target management NE.
  • the interaction with the S-GW is not supported, and the ISR is not supported.
  • Pre-Rel-8 is used as an example for description. It can be understood that in the actual application, other types of unsupported and The S-GW interacts and does not support the version of the ISR.
  • the foregoing describes the case where the original side management network element learns the version information of the target side management network element through the detection of the GTP information. It can be understood that the target side management network element can also use the Context Request message in step 302 to set its own The version information is sent to the original system to manage the network element.
  • the specific method may be to extend a field in the Context Request message to indicate the version information of the target side management network element, or to add an identifier to the existing field for indicating Version information, or other means of indication.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR.
  • the original side and the system management network element send a Context Response message to the target side management network element, and return the mobile phone context information.
  • the target-side management network element sends a Context Ack message to the original system management network element to the original system.
  • the target-side management network element can report the target-side management to the original system management network element through the Context Request message in step 302.
  • the version information of the network element may be sent to the original system management network element by using the Context Ack message in step 304.
  • the specific sending mode is the same as the manner of sending the message through the Context Request message. I will not repeat them here.
  • the target side management network element sends a message update bearer context to the P-GW.
  • the original side and the system management network element send a bearer deletion message including the control cell to the S-GW.
  • the S-GW deletes its own bearer context according to the bearer deletion message and releases the bearer resource.
  • the original side management system network element knows that the version information of the target side management network element indicates that the target side management network element does not support interaction with the S-GW, and does not support the ISR, and carries the bearer deletion message sent to the S-GW.
  • a control cell the control cell is used to instruct the S-GW to delete the local bearer, and
  • the Zhiyuan side different system management network element deletes its bearer context.
  • the S-GW notifies the original side different system management network element to delete the context
  • the original side management system network element receives the GTP information, or the Context Request message in step 302, or the Context Ack message in step 304 has been obtained from the target side management network element.
  • the version information so the control information carried in the bearer deletion message sent by the original system with the system management network element to the S-GW in step 307 instructs the S-GW to notify the original system management network element to delete its bearer context.
  • the S-GW sends a 7-load deletion message to the original system-specific management network element according to the address information in the S-GW, and the S-GW sends the message to the original system.
  • the meta deletes its context.
  • the original side system management network element After receiving the bearer message, the original side system management network element deletes the local bearer context associated with the UE.
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the original side and the system management network element notify the S-GW in an explicit manner to control the original system management network element to delete the context.
  • the original side and the system management network element send a bearer deletion message to the original system management network element through the preset address information. It can be understood that, in actual applications, the address information can also be used in the original application.
  • the same system management network element is obtained through other methods. The following describes two situations:
  • the primary side and the system management network element instruct the S-GW to feed back the address of the original system management network element in the process of interacting with the S-GW. And sending a bearer deletion message to the corresponding original system management network element according to the obtained address information.
  • the UE sends a RAU Request message to the target side management network element.
  • the UE After the UE moves to another MME or SGSN coverage range, the UE sends a RAU Request message carrying the P-TMSI and the GUTI cell to the target side management network element to request registration in the target side management network element. 402.
  • the target-side management network element sends a Context Request message to the original system management network element to the original system.
  • the target-side management network element After receiving the RAU Request message sent by the UE, the target-side management network element sends a Context Request message to the original system management network element to request context information.
  • the target side management network element performs the protocol version detection between the original system management network element and the original system management network element, and the original system management network element can obtain the GTP version of the target side management network element.
  • the GTP version is displayed in a lower version, such as GTP V0 or GTP V1
  • the original system management NE can know that the version information of the target management NE is Pre-Rel-8, that is, the target management NE.
  • the interaction with the S-GW is not supported, and the ISR is not supported.
  • Pre-Rel-8 is used as an example for description. It can be understood that in the actual application, other types of unsupported and The S-GW interacts and does not support the version of the ISR.
  • the foregoing describes the case where the original system management network element learns the version information of the target side management network element through the detection of the GTP information. It can be understood that the target side management network element can also use the Context Request message in step 402 to set its own The version information is sent to the original system to manage the network element.
  • the specific method may be to extend a field in the Context Request message to indicate the version information of the target side management network element, or to add an identifier to the existing field for indicating Version information, or other means of indication.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR.
  • the original system management network element sends a Context Response message to the target side management network element, and returns a mobile phone context information.
  • the target-side management network element sends a Context Ack message to the original system management network element to the original system.
  • the target-side management network element can report the target-side management to the original system management network element through the Context Request message in step 402.
  • the version information of the network element may be sent to the original system management network element by using the Context Ack message in step 404.
  • the specific transmission mode is the same as the manner of sending the message through the Context Request message. This No longer praise.
  • the target side management network element sends a message update bearer context to the P-GW.
  • the original system and the system management network element send a bearer deletion message to the S-GW, and carry an indication in the bearer deletion message, which is used to instruct the S-GW to feed back the original system management to the original system management network element.
  • Control plane information of the network element is used to instruct the S-GW to feed back the original system management to the original system management network element.
  • the S-GW After receiving the bearer deletion message sent by the original system with the system management NE, the S-GW deletes its own bearer context and releases the bearer resource.
  • the S-GW obtains the control plane information of the original system management network element that is saved by the S-GW, and includes the address information, and carries the control plane information when the original side and the system management network element feed back the bearer deletion response.
  • the original system and the system management network element notify the original system management network element to delete the context.
  • the original side management system network element passes the GTP information, or the step 402
  • the Context Request message, or the Context Ack message in the step 404 has obtained the version information of the target side management network element obtained from the target side management network element, so the original side system management network element can be notified to delete its bearer context.
  • the original side and the system management network element obtain the address information of the original system management network element from the bearer deletion response fed back by the S-GW.
  • the original system and the system management network element can send a bearer deletion message to the original system management network element according to the obtained address information of the original system management network element, and the reason for carrying the deletion bearer in the bearer deletion message is: "The target side management NE does not support ISR.”
  • the target-side management network element may select an appropriate timing to perform, for example, the timer expires, that is, after the Context ACK message is received, the execution still does not occur within the preset time.
  • the target-side management network element may select an appropriate timing to perform, for example, the timer expires, that is, after the Context ACK message is received, the execution still does not occur within the preset time.
  • the original side system management network element After receiving the bearer message, the original side system management network element deletes the local bearer context associated with the UE.
  • the original inter-system management network element may further notify the S-GW to delete the bearer.
  • step 407 and the step 408 can be implemented in combination to delete the bearer context on the S-GW and completely release the related bearer resources, for example, between the S-GW and the original system management network element.
  • the bearer resource may be allocated.
  • the bearer resource may be allocated between the S-GW and the original system management network element. If the bearer deletion request in step 407 only requires the S-GW to release the S-GW and the original system management network.
  • the original side different system also needs to notify the S-GW to delete the bearer context, and release the bearer resources between the S-GW and the original side different system management network element, which is understandable If the S-GW does not allocate bearer resources between the S-GW and the original system, and in step 407, the S-GW has deleted its own bearer context according to the indication, and releases the S-GW and the original system management network. In the step 408, the original side different system management network element may not notify the S-GW to delete the bearer.
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the original system and the system management network element obtain the address information of the original system management network element by using the S-GW, so that the bearer deletion message can be sent to the corresponding original system management network element by using the address information. It is understood that the original side and the system management network element can also obtain the address information of the original system management network element from the other network element. For details, refer to FIG. 5, in the fifth embodiment of the resource release control method in the embodiment of the present invention, The original side and the system management network element obtain the address information of the original system management network element from the HSS.
  • the UE sends a RAU Request message to the target side management network element.
  • the UE After the UE moves to the coverage of other MMEs or SGSNs, the UE sends a RAU Request message carrying the P-TMSI and the GUTI cell to the target side management network element to request registration in the target side management network element.
  • the target-side management network element sends a Context Request message to the original system management network element to the original system. After receiving the RAU Request message sent by the UE, the target-side management network element sends a Context Request message to the original system management network element to request context information.
  • the target side management network element performs the protocol version detection between the original system management network element and the original system management network element, and the original system management network element can obtain the GTP version of the target side management network element.
  • the GTP version information is displayed in a lower version, such as GTPV0 or GTP V1
  • the original system management NE can know that the version information of the target management NE is Pre-Rel-8, that is, the target management NE does not. Supports interaction with the S-GW, and does not support ISR, this embodiment and subsequent implementation
  • Pre-Rel-8 is used as an example. It can be understood that in the actual application, other types of versions that do not support interaction with the S-GW and do not support ISR may be used.
  • the foregoing describes the case where the original side management network element learns the version information of the target side management network element through the detection of the GTP information. It can be understood that the target side management network element can also use the Context Request message in step 502 to set its own The version information is sent to the original system to manage the network element.
  • the specific method may be to extend a field in the Context Request message to indicate the version information of the target side management network element, or to add an identifier to the existing field for indicating Version information, or other means of indication.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR.
  • the original side and the system management network element send a Context Response message to the target side management network element, and return the mobile phone context information.
  • the target-side management network element sends a ContextAck message to the original system management network element to the original system.
  • the target-side management network element can feed the target-side management network to the original system management network element through the Context Request message in step 502.
  • the version information of the element may be sent to the original system management network element by using the Context Ack message in step 504.
  • the specific transmission mode is the same as the manner of sending the message through the Context Request message. No longer praise.
  • the target side management network element sends a message update bearer context to the P-GW.
  • the target side management network element sends a location update request message Update Location Request message to the HSS.
  • the target-side management NE sends the version information of the target-side management NE to the HSS by using the Update Location Request message.
  • the specific manner may be to extend a field in the Update Location Request message to indicate the target.
  • the version information of the management NE may be to extend a field in the Update Location Request message to indicate the target.
  • the HSS sends a Cancel Location message to the original system management network element.
  • the HSS learns that the Update Location Request message carries the version information of the target-side management NE, the HSS is triggered to send the control plane information of the original-side different-system management NE to the original system management network element.
  • the method may be extended in the Cancel Location message to store control plane information (including address information) of the original system management network element.
  • the original system management network element may also add an interaction signaling, such as an ISR Information Request, in the signaling, indicating that the HSS feeds back the control plane information of the original system management network element.
  • an interaction signaling such as an ISR Information Request
  • the HSS After receiving the signaling, the HSS obtains the control plane information of the original system management network element, and carries the information in the ISR Information Response to the original system management network element.
  • the HSS sends an Update Location Ack message to the target side management network element.
  • the original side and the system management network element notify the S-GW to delete the bearer.
  • the original system and the system management network element send a bearer deletion message to the S-GW, and the bearer deletion message instructs the S-GW to delete the bearer.
  • the S-GW deletes the bearer. It means that the S-GW deletes its own bearer context and releases the bearer resources.
  • the S-GW After receiving the bearer deletion message sent by the original system with the system management NE, the S-GW deletes its own bearer context and releases the bearer resource.
  • the original system and the system management network element notify the original system management network element to delete the context.
  • the original system management network element passes the GTP information, or the step 502
  • the Context Request message, or the Context Ack message in the step 504 has obtained the version information of the target side management network element obtained from the target side management network element, so the original side system management network element can be notified to delete the bearer context.
  • the original side and the system management network element obtain the address information of the original side different system management network element from the information fed back by the HSS.
  • the original system and the system management network element can send a bearer deletion message to the original system management network element according to the obtained address information of the original system management network element, and the reason for carrying the deletion bearer in the bearer deletion message is: "The target side management NE does not support ISR.”
  • the target-side management network element may select an appropriate timing to perform, for example, the timer expires, that is, after the Context ACK message is received, the execution is still not triggered within a preset time. The next step.
  • the original side different system management network element deletes the local and UE related bearers.
  • the original side different system management network element deletes the local bearer context associated with the UE after receiving the delete bearer message.
  • the original heterogeneous system management network element may further notify the S-GW to delete the bearer context.
  • the step 509 and the step 511 can be implemented in combination to delete the bearer context on the S-GW and completely release the related bearer resources.
  • the S-GW and the original system management network element can allocate bearer resources.
  • the bearer resource may be allocated between the S-GW and the original system management network element. If the bearer deletion request in step 509 only requires the S-GW to release the bearer between the S-GW and the original system management network element.
  • the original side different system also needs to notify the S-GW to delete the bearer context, and release the bearer resource between the S-GW and the original side different system management network element. It can be understood that if the S-GW The bearer resource is not allocated between the original system and the original system.
  • the S-GW has deleted its own bearer context according to the indication, and releases the bearer between the S-GW and the original system management network element. Then, in step 511, the original side different system management network element may not notify the S-GW to delete the bearer.
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the original side and the system management network element obtain the address information of the original system management network element through the HSS, so that the original side different system management network element can send the 7-load deletion message.
  • the RAU process is taken as an example for description. In the actual application, other processes may be used. The following is an example of switching the HANDOVER process.
  • FIG. 6 the resource release control in the embodiment of the present invention is shown.
  • the original side different system management network element can determine that the target side management network element does not support interaction with the S-GW, and the original side different system management network element can obtain the version information of the target side management network element. If the ISR is not supported, the original system management NE can delete its own bearer context.
  • the source eNodeB sends a relocation request to the original inter-system management NE.
  • the original remote system management network element sends a forward relocation request message to the target side management network element.
  • the target side management network element is directed to the target radio network controller (RNC, Radio Network) Controller) sends a relocation request to request allocation of radio resources;
  • RNC Radio Network Controller
  • the target-side management NE returns the forward relocation response to the original-side heterogeneous system management NE.
  • the Forward Relocation Response message sent by the target-side management network element to the original-side heterogeneous system management network element carries the target-side management NE version information
  • the specific carrying manner may be that the Forward Relocation Response message is extended in a field for carrying the Version information, or add this version information to an existing field.
  • the original side different system management network element sends a relocation command Relocation Command message to the source eNodeB.
  • the target-side management NE sends a Forward Relocation Complete message to the original-side heterogeneous system management NE.
  • the target side management network element sends the version information of the target side management network element to the original side different system management network element by using the Forward Relocation Response message.
  • the target side The management network element may also send the version information of the target side management network element to the original side different system management network element by using the Forward Relocation Complete message, and the specific sending manner is consistent with the manner in the foregoing step 604.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element may also indicate its own version information in an implicit manner. For example, the target side management network element does not carry the "version" in the signaling sent to the original system management network element or the original side different system management network element. If the field, or the value in the field is empty, the default means that the target-side management NE does not support interaction with the S-GW and does not support ISR. .
  • the original system management network element After receiving the message, the original system management network element sends a forward relocation complete Acknowledge message to the target side management network element.
  • the target side management network element sends a message to the PDN GW to update the bearer information.
  • the original side different system management network element deletes the context.
  • the original side different system management network element obtains the version information of the target side management network element through step 604 or 607, and learns that the version information indicates that the target side management network element does not support and If the S-GW does not support the ISR, the original system management network element deletes the local bearer context and notifies the S-GW to delete the local bearer. Then, the S-GW deletes itself after receiving the indication of the original system management network element. Host the context and release the bearer resources.
  • the original side different system management network element may select an appropriate timing to perform, for example, between the presets after receiving the Forward Relocation Complete message.
  • the message triggers the execution of the next process, and the bearer context is deleted.
  • the original-side heterogeneous system management network element obtains the version information of the target-side management network element from the target-side management network element, and therefore determines that the version information indicates that the target-side management network element does not support interaction with the S-GW.
  • the local bearer context is deleted after the ISR is not supported.
  • the original system management network element acquires the version information of the target side management network element, and sends a bearer deletion message to the original side different system management network element. Or send a bearer deletion message to the original heterogeneous system management network element through the S-GW.
  • the source RNC sends a relocation request to the original system management network element to the original side.
  • the original system management network element sends a forward relocation request message to the target side management network element.
  • the target-side management NE sends a relocation request to the target RNC to request to allocate the radio resource. 704. The target-side management NE sends the forward relocation response to the original system management NE.
  • the Forward Relocation Response message sent by the target-side management NE to the original system management network element carries the target-side management NE version information
  • the specific carrying manner may be that the Forward Relocation Response message is extended in a field for carrying the Version information, or add this version information to an existing field.
  • the target side management network element indicates its own version information by means of explicit cells (ie, does not support interaction with the S-GW, and does not support ISR), it can be understood that the target The side management network element can also indicate its own version information in an implicit manner.
  • the target side management network element does not carry the version in the signaling sent to the original system management network element or the original side different system management network element.
  • This field, or the value in this field is blank, by default, the target-side management NE does not support interaction with the S-GW, and does not support ISR.
  • the UE sends a RAU request to the target side management network element.
  • the specific RAU process may be: the target side management network element interacts with the HSS to perform location update; the HSS interacts with the original system management network element to cancel the registration of the original system management network element in the HSS.
  • the original side can send a bearer deletion message to the original system management network element, and obtain the address information of the original system management network element.
  • the method of obtaining the address information, or obtaining the address information from the S-GW, or obtaining the address information from the HSS is similar to the obtaining manner in the foregoing embodiment, and details are not described herein again.
  • the original system management network element may also indicate that the S-GW deletes the bearer context of the original system management network element.
  • the specific processing manner is similar to the indication manner in the foregoing embodiment, and details are not described herein. .
  • the target side management network element sends a RAU Accept message to the UE.
  • the UE sends a RAU Complete message to the target side management network element.
  • the original side may send a bearer deletion message to the original side different system management network element, or send the message to the original side different system management network element through the S-GW. Host delete message.
  • the S-GW needs to delete the local bearer, that is, delete the self-bearing context, and release the bearer resource.
  • the specific deletion process is similar to the deletion process in the foregoing embodiment, and is not mentioned here.
  • the version information is determined to indicate that the target side management network element does not cooperate with the service gateway S.
  • the GW is in the same mode, and the bearer context is not supported in the idle mode.
  • the bearer context in the original system management network element may be deleted according to the version information. Therefore, the target side management network element in the embodiment of the present invention is not supported.
  • the S-GW interacts and does not support ISR, the original side can also be deleted. Manage the bearer context on the NE.
  • the embodiment of the communication system in the embodiment of the present invention includes:
  • the original side is the same as the system management network element 801, and is used to determine the version information of the target side management network element when the user equipment that activates the ISR is switched from the primary side network to the target side network, and if the determination result indicates the target side management network
  • the element does not interact with the S-GW, and does not support the ISR, and sends a bearer deletion message.
  • the original heterogeneous system management network element 802 is configured to receive the bearer deletion message, and delete its own bearer context according to the bearer deletion message.
  • the original side management system network element 801 after the original system management network element 801 obtains the version information of the target side management network element, the original side management system network element can be directly managed according to the address information of the original original system management network element 802.
  • the 802 sends a bearer deletion message, and the original heterogeneous system management network element 802 deletes the local bearer context.
  • the original side system management network element 801 can also obtain the address information of the original side different system management network element 802 through the S-GW or the HSS, and the corresponding original system management network according to the obtained address information.
  • the element 802 sends a bearer deletion message, and the original side different system management network element 802 deletes the local bearer context.
  • the original system management network element 801 can also send a bearer deletion to the original system management network element 802 through the S-GW, except that the original system management network element 801 sends a bearer deletion message to the original system management network element 802.
  • the communication system embodiment in this embodiment may further include: a service gateway 803, configured to receive a bearer deletion message sent by the original side with the system management network element 801, and delete the bearer context of the bearer according to the bearer deletion message. And releasing the bearer resource, and sending the bearer deletion message to the original side different system management network element 802.
  • the bearer deletion message received by the service gateway 803 from the original side and the system management network element 801 may further include a control cell, which is used to instruct the service gateway 803 to notify the original side different system management network element 802 to delete 7
  • the first embodiment of the mobility management network element in the embodiment of the present invention includes: an obtaining unit 901, configured to obtain version information of a peer management network element;
  • the determining unit 902 is configured to determine, according to the version information of the peer management network element that is obtained by the obtaining unit 901, whether the indication does not support the interaction with the S-GW, and does not support the ISR;
  • the bearer deletion control unit 903 performs a bearer deletion process if the judgment result of the determining unit 902 is that the peer management network element does not support the S-GW interaction and does not support the ISR.
  • the peer management network element refers to the target side management network element.
  • the bearer deletion control unit 903 can be divided into two cases according to specific implementations:
  • the bearer deletion control unit 903 includes:
  • the address obtaining unit 9031 is configured to obtain the address information of the original system management network element, and the deletion indication unit 9032 sends a delete message to the corresponding original system management network element according to the version information and the address information.
  • the bearer delete message is used to instruct the original side different system management network element to delete its own bearer context.
  • bearer deletion control unit 903 includes:
  • the bearer deleting unit 9033 is configured to delete its own bearer context according to the version information.
  • the mobility management network element may be a primary-side heterogeneous system management network element.
  • the address obtaining unit 9031 in this embodiment includes at least one of the following units:
  • the first address obtaining unit 90311 is configured to obtain the address information second address obtaining unit 90312 of the original original system management network element, and configured to acquire the address information of the original side different system management network element from the S-GW.
  • the third address obtaining unit 90313 is configured to acquire address information of the original side different system management network element from the HSS.
  • an embodiment of a gateway device in this embodiment of the present invention includes:
  • the receiving unit 1001 is configured to receive a bearer deletion message sent by the original system and the system management network element, where the deletion execution unit 1002 is configured to delete the bearer context of the bearer according to the bearer deletion message and release the bearer resource.
  • the deletion control unit 1003 is configured to send a bearer deletion message to the original inter-system management network element, to indicate that the original inter-system management network element deletes the bearer context.
  • the deletion execution unit 1002 in this embodiment is an optional unit.
  • the user equipment of the ISR switches from the primary side network to the target side network.
  • the bearer in the original-side different-system management network element is deleted.
  • the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Description

一种资源释放控制方法及通讯***以及相关设备 本申请要求于 2008 年 1 月 31 日提交中国专利局、 申请号为 200810006802.8, 发明名称为 "一种资源释放控制方法及通讯***以及相关设 备" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通讯领域，尤其涉及一种资源释放控制方法及通讯***以及相 关设备。
背景技术
无线演进网络的核心网， 即***架构演进 ( SAE , System Architecture Evolution )主要包含移动管理实体（MME, Mobility Management Entity ), 服 务网关（S-GW, Serving Gateway )、 分组数据网络网关 ( P-GW, Packet data network Gateway )三个還辑功能体。
其中， MME负责非接入层（ NAS， Non-Access Stadium )信令加密以及漫 游、 跟踪等功能， 分配用户临时身份标识、 安全功能等， 它对应于当前通用移 动通信***（ UMTS , Universal Mobile Telecommunications System ) ***内部 服务 GPRS支持节点 （ SGSN, Serving GPRS Supporting Node ) 的控制平面部 分；
S-GW 负责本地的移动性锚点和第三代伙伴组织计划 （3GPP , Third Generation Partnership Projects ) ***内部的移动性锚点及合法监听相关信息； P-GW负责策略执行和计费以及合法监听相关功能。
归属用户服务器（HSS， Home Subscriber Server )用于存储用户签约信息。 为了节约信令开销， 目前有一种空闲模式下节约信令（ISR, Idle mode Signaling Reduction )方案 , 这种方案下用户设备 ( UE , User Equipment )在两 个不同的接入网络都注册， HSS保存两种接入技术核心网元的信息。
在双注册机制下， 原侧 MME与 SGSN建立 ISR机制后， 若 UE移动到了 新的 MME或 SGSN, 将会发起跟踪区域更新（TAU, Tracking Area Update ) 或路由区域更新（ RAU, Routing Area Update )流程。若目标侧的 MME或 SGSN 不支持 ISR，则目标侧的 MME或 SGSN在向 S-GW更新承载信息时不携带 ISR 激活指示，则 S-GW收到该承载更新请求后删除自身的承载上下文， 并请求原 侧的 MME或 SGSN删除承载上下文。
但是， 在上述技术方案中， 若目标侧的 MME或 SGSN的版本特性（如 Pre-Rel-8版本）指示其不支持与 S-GW交互， 且不支持 ISR, 则当 UE移动到 目标侧的 MME或 SGSN的覆盖范围下时， 由于目标侧 MME或 SGSN无法与 S-GW交互信令， 因此无法按照现有技术的方案控制 S-GW删除原侧 MME或 SGSN上的承载上下文。
发明内容
本发明实施例提供了一种资源释放控制方法及通讯***以及相关设备，能 够使得目标侧管理网元在不支持与 S-GW交互且不支持 ISR的情况下同样能够 删除原侧异***管理网元上的承载。
本发明实施例提供的资源释放控制方法， 当激活空闲模式节约信令机制
ISR的用户设备从原侧网络切换到目标侧网络时， 包括： 获取目标侧管理网元 的版本信息；若所述版本信息指示所述目标侧管理网元不与服务网关 S-GW交 互， 且不支持 ISR, 则删除原侧异***管理网元中的承载。
本发明实施例提供的通讯***， 包括： 原侧同***管理网元， 用于当激活
ISR的用户设备从原侧网络切换到目标侧网络时，获取目标侧管理网元的版本 信息， 若所述版本信息指示所述目标侧管理网元不与 S-GW 交互， 且不支持 ISR, 则发送承载删除消息； 原侧异***管理网元， 用于接收承载删除消息， 并根据所述承载删除消息删除自身的承载。
本发明实施例提供的移动性管理网元， 与无线接入网相连， 用于对用户移 动状态进行管理， 包括： 获取单元， 用于获取对端管理网元的版本信息； 判断 单元，用于根据获取单元获取到的对端管理网元的版本信息判断是否指示不支 持与 S-GW交互， 且不支持 ISR; 承载删除控制单元， 若所述判断单元的判断 结果为对端管理网元不支持与 S-GW交互， 且不支持 ISR, 则执行承载删除流 程。
本发明实施例提供的网关设备， 与无线接入网和分组数据网相连， 用于承 载无线接入网和分组数据网之间的用户数据传输， 包括： 接收单元， 用于接收 原侧同***管理网元发送的承载删除消息； 删除控制单元， 用于根据所述承载 删除消息指示原侧异***管理网元删除所述原侧异***管理网元上的承载。 从以上技术方案可以看出， 本发明实施例具有以下优点：
本发明实施例中， 获取到目标侧管理网元的版本信息之后， 确定该版本信 息指示所述目标侧管理网元不与服务网关 S-GW交互，且不支持空闲模式下节 约信令 ISR, 则可以根据所述版本信息删除原侧异***管理网元中的承载， 因 此本发明实施例中目标侧管理网元在不支持与 S-GW交互且不支持 ISR的情况 下同样能够删除原侧异***管理网元上的承载。
附图说明
图 1为本发明实施例中资源释放控制方法第一实施例流程图；
图 2为本发明实施例中资源释放控制方法第二实施例流程图；
图 3为本发明实施例中资源释放控制方法第三实施例流程图；
图 4为本发明实施例中资源释放控制方法第四实施例流程图；
图 5为本发明实施例中资源释放控制方法第五实施例流程图；
图 6为本发明实施例中资源释放控制方法第六实施例流程图；
图 Ί为本发明实施例中资源释放控制方法第七实施例流程图；
图 8为本发明实施例中通讯***实施例示意图；
图 9为本发明实施例中移动性管理网元实施例示意图；
图 10为本发明实施例中网关设备实施例示意图。
具体实施方式
本发明实施例提供了一种资源释放控制方法及通讯***以及相关设备，用 于使得目标侧管理网元在不支持与 S-GW交互且不支持 ISR的情况下同样能够 删除原侧异***管理网元上的承载上下文。
本发明实施例中的资源释放控制方法包括：
当激活空闲模式节约信令机制 ISR的用户设备从原侧网络切换到目标侧 网络时， 获取目标侧管理网元的版本信息；
若所述版本信息指示所述目标侧管理网元不与服务网关 S-GW交互，且不 支持 ISR, 则删除原侧异***管理网元中的承载。
本发明实施例中， 获取到目标侧管理网元的版本信息之后， 确定该版本信 息指示所述目标侧管理网元不与服务网关 S-GW交互，且不支持空闲模式下节 约信令 ISR, 则可以根据所述版本信息删除原侧异***管理网元中的承载上下 文， 需要说明的是， 在后续各个实施例中， 删除原侧异***管理网元中的承载 即是指删除原侧异***管理网元中的承载上下文。
因此本发明实施例中目标侧管理网元在不支持与 S-GW交互且不支持 ISR 的情况下同样能够删除原侧异***管理网元上的承载上下文。
在本实施例以及后续实施例中，原侧异***管理网元是指用户原先所处的
MME, 原侧同***管理网元是指与原侧 MME建立了 ISR机制的 SGSN, 目 标侧管理网元是指用户移动后所处的 SGSN。
可以理解的是， 在实际应用中， 原侧异***管理网元， 原侧同***管理网 元以及目标侧管理网元还可以是其他的情况，例如目标侧管理网元若为 MME, 则原侧异***管理网元为 SGSN, 原侧同***管理网元为 MME。
为便于理解， 下面结合附图对本发明实施例进行伴细说明， 请参阅图 1， 本发明实施例中资源释放控制方法第一实施例中，原侧同***管理网元在与目 标侧管理网元交互的过程中获取目标侧管理网元的版本信息，之后根据原侧同 ***管理网元本地保存的原侧异***管理网元的地址信息向对应的原侧异系 统管理网元发送承载删除消息， 从而使得原侧异***删除自身的承载上下文。
本发明实施例中资源释放控制方法第一实施例具体包括：
101、 UE向目标侧管理网元发 RAU Request消息；
当 UE移动到其他 MME或 SGSN覆盖的范围后， UE向目标侧管理网元 发送携带分组临时移动用户身份标识 （ P-TMSI , Packet Temporary Mobile Subscriber Identity )以及全球唯一临时标识（ GUTI , Globally Unique Temporary Identity )信元的 RAU Request消息以请求在目标侧管理网元中进行注册。
102、 目标侧管理网元向原侧同***管理网元发送 Context Request消息； 目标侧管理网元接收到 UE发送的 RAU Request消息之后 ,向原侧同*** 管理网元发送 Context Request消息以请求上下文信息。
本实施例中，在步骤 102之前， 目标侧管理网元会与原侧同***管理网元 之间进行协议版本探测，原侧同***管理网元可以获知目标侧管理网元的通用 无线分组业务隧道协议（ GTP, General Packet Radio Service Tunneling Protocol ) 的版本， 若该 GTP版本信息显示为较低版本， 比如 GTP V0或者 GTP V1 , 则 原侧同***管理网元可以获知目标侧管理网元的版本信息为 Pre-Rel-8版本， 即目标侧管理网元不支持与 S-GW交互， 且不支持 ISR, 本实施例以及后续实 施例中以 Pre-Rel-8为例进行说明， 可以理解的是， 在实际应用中还可以是其 他类型的不支持与 S-GW交互， 且不支持 ISR的版本。
上述介绍了原侧同***管理网元通过 GTP信息的检测获知目标侧管理网 元的版本信息的情况， 可以理解的是， 目标侧管理网元还可以通过步骤 102 中的 Context Request消息将自身的版本信息告知原侧同***管理网元， 具体 的方式可以为在 Context Request消息中扩展一个字段用于指示目标侧管理网 元的版本信息，或者是在现有的字段中增添一个标识用于指示版本信息，或是 其他指示手段均可。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带"版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
103、 原侧同***管理网元向目标侧管理网元发送 Context Response消息 返回手机上下文信息；
104、 目标侧管理网元向原侧同***管理网元发送 Context Ack消息； 本实施例中， 目标侧管理网元除了在步骤 102中可以通过 Context Request 消息向原侧同***管理网元反馈目标侧管理网元的版本信息之夕卜，还可以在步 骤 104中通过 Context Ack消息向原侧同***管理网元发送目标侧管理网元的 版本信息， 具体的发送方式与通过 Context Request消息发送的方式一致， 此 处不再赘述。
105、 目标侧管理网元向 P-GW发送消息更新承载上下文；
106、 执行 RAU其他相关流程；
107、 原侧同***管理网元通知 S-GW删除^载；
本实施例中，原侧同***管理网元向 S-GW发送承载删除消息，该承载删 除消息指示 S-GW删除自身承载， 需要说明的是，在本实施例以及后续各个实 施例中， S-GW删除自身承载是指 S-GW删除自身的承载上下文并且释放承载 资源。
S-GW在接收到原侧同***管理网元发送的承载删除消息之后，删除自身 的承载上下文， 并释放承载资源。
108、 原侧同***管理网元通知原侧异***管理网元删除^载上下文； 本实施例中， 由于原侧同***管理网元通过 GTP信息， 或步骤 102中的
Context Request消息， 或步骤 104中的 Context Ack消息已经从目标侧管理网 元获取到的目标侧管理网元的版本信息，所以可以通知原侧异***管理网元删 除其承载上下文。
本实施例中，在 ISR激活时，原侧同***管理网元和原侧异***管理网元 互相保存对方信息， 例如控制面信息， 控制面信息中包含对端的地址信息。
则原侧同***管理网元可以根据预先保存的信息获取到原侧异***管理 网元的地址信息 , 并根据该地址信息向原侧异***管理网元发送承载删除消 息， 在承载删除消息中可以携带删除承载的原因值为： "目标侧管理网元不支 持 ISR"。
需要说明的是， 本步骤 108可以在收到目标侧管理网元发送 Context ACK 消息后选择合适的时机执行， 例如计时器超时， 即接收到 Context ACK消息之 后在预置的时间内仍然没有触发执行下一步流程。
109、 原侧异***管理网元删除本地和 UE相关的承载；
原侧异***管理网元接收到删除承载消息后删除本地和该 UE相关的承载 上下文。
本实施例中，原侧异***管理网元还可以通知 S-GW删除承载， 需要说明 的是， 此处 S-GW删除承载的含义与步骤 107中 S-GW删除承载的含义一致， 即同样包括删除 S-GW上的承载上下文， 并释放承载资源。
步骤 107和步骤 109可以结合实现， 以删除 S-GW上的承载上下文， 并完 全释放相关承载资源，例如 S-GW与原侧同***管理网元之间可以分配承载资 源，同样， S-GW与原侧异***管理网元之间也可以分配承载资源，若步骤 107 中的承载删除请求仅要求 S-GW释放 S-GW与原侧同***管理网元之间的承载 资源， 则在步骤 109中， 原侧异***还需要通知 S-GW删除承载上下文， 且释 放 S-GW与原侧异***管理网元之间的承载资源，可以理解的是，若 S-GW与 原侧异***之间并未分配承载资源， 且在步骤 107中， S-GW已经按照指示删 除了自身的承载上下文， 并释放了 S-GW与原侧同***管理网元之间的承载， 则步骤 109中， 原侧异***管理网元可以不再通知 S-GW删除承载。
110、 目标侧管理网元向 UE发送 RAU Accept消息；
111、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中，由于原侧同***管理网元获取到目标侧管理网元的版本信息 之后 ,根据本地保存的地址信息向对应的原侧异***管理网元发送承载删除消 息， 所以能使得原侧异***管理网元删除自身的承载上下文， 可以理解的是， 原侧同***管理网元还可以通过 S-GW删除原侧异***管理网元的承载上下 文， 具体请参阅图 2, 本发明实施例中资源释放控制方法第二实施例中， 原侧 同***管理网元获取到目标侧管理网元的版本信息之后，向 S-GW发送承载删 除消息， 后续由 S-GW控制原侧异***管理网元删除其承载上下文。
本发明实施例中资源释放控制方法第二实施例具体包括：
201、 UE向目标侧管理网元发 RAU Request消息；
当 UE移动到其他 MME或 SGSN覆盖的范围后， UE向目标侧管理网元 发送携带 P-TMSI以及 GUTI信元的 RAU Request消息以请求在目标侧管理网 元中进行注册。
202、 目标侧管理网元向原侧同***管理网元发送 Context Request消息； 目标侧管理网元接收到 UE发送的 RAU Request消息之后 ,向原侧同*** 管理网元发送 Context Request消息以请求上下文信息。
本实施例中，在步骤 202之前， 目标侧管理网元会与原侧同***管理网元 之间进行协议版本探测，原侧同***管理网元可以获知目标侧管理网元的 GTP 的版本， 若该 GTP版本信息显示为较低版本， 比如 GTP V0或者 GTP V1 , 则 原侧同***管理网元可以获知目标侧管理网元的版本信息为 Pre-Rel-8版本， 即目标侧管理网元不支持与 S-GW交互， 且不支持 ISR, 本实施例以及后续实 施例中以 Pre-Rel-8为例进行说明， 可以理解的是， 在实际应用中还可以是其 他类型的不支持与 S-GW交互， 且不支持 ISR的版本。
上述介绍了原侧同***管理网元通过 GTP信息的检测获知目标侧管理网 元的版本信息的情况， 可以理解的是， 目标侧管理网元还可以通过步骤 202 中的 Context Request消息将自身的版本信息告知原侧同***管理网元， 具体 的方式可以为在 Context Request消息中扩展一个字段用于指示目标侧管理网 元的版本信息，或者是在现有的字段中增添一个标识用于指示版本信息，或是 其他指示手段均可。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带"版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
203、 原侧同***管理网元向目标侧管理网元发送 Context Response消息 返回手机上下文信息；
204、 目标侧管理网元向原侧同***管理网元发送 Context Ack消息； 本实施例中， 目标侧管理网元除了在步骤 202中可以通过 Context Request 消息向原侧同***管理网元反馈目标侧管理网元的版本信息之夕卜，还可以在步 骤 204中通过 Context Ack消息向原侧同***管理网元发送目标侧管理网元的 版本信息， 具体的发送方式与通过 Context Request消息发送的方式一致， 此 处不再赘述。
205、 目标侧管理网元向 P-GW发送消息更新承载上下文；
206、 执行 RAU其他相关流程；
207、 原侧同***管理网元通知 S-GW删除^载；
本实施例中， 原侧同***管理网元向 S-GW发送承载删除消息， S-GW根 据该承载删除消息删除自身的承载上下文并且释放承载资源。
208、 S-GW通知原侧异***管理网元删除^载上下文；
本实施例中， 由于原侧同***管理网元通过 GTP信息， 或步骤 202中的
Context Request消息， 或步骤 204中的 Context Ack消息已经从目标侧管理网 元获取到的目标侧管理网元的版本信息，所以步骤 207中原侧同***管理网元 在向 S-GW发送的承载删除消息既指示 S-GW删除自身承载，也指示 S-GW控 制原侧异***管理网元删除其承载上下文。 由于 S-GW中保存有原侧异***管理网元的控制面信息，则 S-GW根据其 中的地址信息向原侧异***管理网元发送 7 载删除消息 ,用于指示原侧异*** 管理网元删除其 7 载上下文。
原侧异***管理网元接收到删除承载消息后删除本地和该 UE相关的承载 上下文。
209、 目标侧管理网元向 UE发送 RAU Accept消息；
210、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中，原侧同***管理网元向 S-GW发送的承载删除消息默认请求 S-GW控制原侧异***管理网元删除其承载上下文， 可以理解的是， 在实际应 用中，原侧同***管理网元还可以通过明示的方式告知 S-GW控制原侧异*** 管理网元删除其承载上下文， 具体请参阅图 3 , 本发明实施例中资源释放控制 方法第三实施例中，原侧同***管理网元获取到目标侧管理网元的版本信息之 后， 向 S-GW发送包含控制信元的承载删除消息，该控制信元用于指示后续由 S-GW控制原侧异***管理网元删除其承载上下文。
本发明实施例中资源释放控制方法第三实施例具体包括：
301、 UE向目标侧管理网元发 RAU Request消息；
当 UE移动到其他 MME或 SGSN覆盖的范围后， UE向目标侧管理网元 发送携带 P-TMSI以及 GUTI信元的 RAU Request消息以请求在目标侧管理网 元中进行注册。
302、 目标侧管理网元向原侧同***管理网元发送 Context Request消息； 目标侧管理网元接收到 UE发送的 RAU Request消息之后 ,向原侧同*** 管理网元发送 Context Request消息以请求上下文信息。
本实施例中，在步骤 302之前， 目标侧管理网元会与原侧同***管理网元 之间进行协议版本探测，原侧同***管理网元可以获知目标侧管理网元的 GTP 的版本， 若该 GTP版本信息显示为较低版本， 比如 GTP V0或者 GTP V1 , 则 原侧同***管理网元可以获知目标侧管理网元的版本信息为 Pre-Rel-8版本， 即目标侧管理网元不支持与 S-GW交互， 且不支持 ISR, 本实施例以及后续实 施例中以 Pre-Rel-8为例进行说明， 可以理解的是， 在实际应用中还可以是其 他类型的不支持与 S-GW交互， 且不支持 ISR的版本。 上述介绍了原侧同***管理网元通过 GTP信息的检测获知目标侧管理网 元的版本信息的情况， 可以理解的是， 目标侧管理网元还可以通过步骤 302 中的 Context Request消息将自身的版本信息告知原侧同***管理网元， 具体 的方式可以为在 Context Request消息中扩展一个字段用于指示目标侧管理网 元的版本信息，或者是在现有的字段中增添一个标识用于指示版本信息，或是 其他指示手段均可。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带 "版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
303、 原侧同***管理网元向目标侧管理网元发送 Context Response消息 返回手机上下文信息；
304、 目标侧管理网元向原侧同***管理网元发送 Context Ack消息； 本实施例中， 目标侧管理网元除了在步骤 302中可以通过 Context Request 消息向原侧同***管理网元反馈目标侧管理网元的版本信息之夕卜，还可以在步 骤 304中通过 Context Ack消息向原侧同***管理网元发送目标侧管理网元的 版本信息， 具体的发送方式与通过 Context Request消息发送的方式一致， 此 处不再赘述。
305、 目标侧管理网元向 P-GW发送消息更新承载上下文；
306、 执行 RAU其他相关流程；
307、 原侧同***管理网元通知 S-GW删除^载；
本实施例中，原侧同***管理网元向 S-GW发送包含控制信元的承载删除 消息。
S-GW根据该承载删除消息删除自身的承载上下文并且释放承载资源。 原侧同***管理网元在获知目标侧管理网元的版本信息指示该目标侧管 理网元不支持与 S-GW交互， 且不支持 ISR之后， 在发送给 S-GW的承载删 除消息中携带一个控制信元，该控制信元用于指示 S-GW删除本地承载，并通 知原侧异***管理网元删除其承载上下文。
308、 S-GW通知原侧异***管理网元删除^载上下文；
本实施例中， 由于原侧同***管理网元通过 GTP信息， 或步骤 302中的 Context Request消息， 或步骤 304中的 Context Ack消息已经从目标侧管理网 元获取到的目标侧管理网元的版本信息，所以步骤 307中原侧同***管理网元 在向 S-GW发送的承载删除消息中携带的控制信元指示 S-GW通知原侧异*** 管理网元删除其承载上下文。
由于 S-GW中保存有原侧异***管理网元的控制面信息，则 S-GW根据其 中的地址信息向原侧异***管理网元发送 7 载删除消息 ,用于指示原侧异*** 管理网元删除其^载上下文。
原侧异***管理网元接收到删除承载消息后删除本地和该 UE相关的承载 上下文。
309、 目标侧管理网元向 UE发送 RAU Accept消息；
310、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中，原侧同***管理网元通过明示的方式告知 S-GW控制原侧异 ***管理网元删除其^载上下文。
上述第一实施例中，原侧同***管理网元通过自身预置的地址信息向原侧 异***管理网元发送承载删除消息， 可以理解的是， 在实际应用中， 该地址信 息同样可以由原侧同***管理网元通过其他方式获取得到， 下面介绍两种情 况：
请参阅图 4， 本发明实施例中资源释放控制方法第四实施例中， 原侧同系 统管理网元在与 S-GW交互的过程中指示 S-GW反馈原侧异***管理网元的地 址信息 ,并根据获得到的地址信息向对应的原侧异***管理网元发送承载删除 消息。
本发明实施例中资源释放控制方法第四实施例具体包括：
401、 UE向目标侧管理网元发 RAU Request消息；
当 UE移动到其他 MME或 SGSN覆盖的范围后， UE向目标侧管理网元 发送携带 P-TMSI以及 GUTI信元的 RAU Request消息以请求在目标侧管理网 元中进行注册。 402、 目标侧管理网元向原侧同***管理网元发送 Context Request消息； 目标侧管理网元接收到 UE发送的 RAU Request消息之后 ,向原侧同*** 管理网元发送 Context Request消息以请求上下文信息。
本实施例中，在步骤 402之前， 目标侧管理网元会与原侧同***管理网元 之间进行协议版本探测，原侧同***管理网元可以获知目标侧管理网元的 GTP 的版本， 若该 GTP版本信息显示为较低版本， 比如 GTP V0或者 GTP V1 , 则 原侧同***管理网元可以获知目标侧管理网元的版本信息为 Pre-Rel-8版本， 即目标侧管理网元不支持与 S-GW交互， 且不支持 ISR, 本实施例以及后续实 施例中以 Pre-Rel-8为例进行说明， 可以理解的是， 在实际应用中还可以是其 他类型的不支持与 S-GW交互， 且不支持 ISR的版本。
上述介绍了原侧同***管理网元通过 GTP信息的检测获知目标侧管理网 元的版本信息的情况， 可以理解的是， 目标侧管理网元还可以通过步骤 402 中的 Context Request消息将自身的版本信息告知原侧同***管理网元， 具体 的方式可以为在 Context Request消息中扩展一个字段用于指示目标侧管理网 元的版本信息，或者是在现有的字段中增添一个标识用于指示版本信息，或是 其他指示手段均可。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带 "版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
403、 原侧同***管理网元向目标侧管理网元发送 Context Response消息 返回手机上下文信息；
404、 目标侧管理网元向原侧同***管理网元发送 Context Ack消息； 本实施例中， 目标侧管理网元除了在步骤 402中可以通过 Context Request 消息向原侧同***管理网元反馈目标侧管理网元的版本信息之夕卜，还可以在步 骤 404中通过 Context Ack消息向原侧同***管理网元发送目标侧管理网元的 版本信息， 具体的发送方式与通过 Context Request消息发送的方式一致， 此 处不再赞述。
405、 目标侧管理网元向 P-GW发送消息更新承载上下文；
406、 执行 RAU其他相关流程；
407、 原侧同***管理网元通知 S-GW删除^载；
本实施例中，原侧同***管理网元向 S-GW发送承载删除消息， 并在该承 载删除消息中携带指示，用于指示 S-GW向原侧同***管理网元反馈原侧异系 统管理网元的控制面信息。
S-GW在接收到原侧同***管理网元发送的承载删除消息之后，删除自身 的承载上下文， 并释放承载资源。
S-GW获取自身保存的原侧异***管理网元的控制面信息， 其中包含地址 信息， 并向原侧同***管理网元反馈承载删除响应时携带该控制面信息。
408、 原侧同***管理网元通知原侧异***管理网元删除^载上下文； 本实施例中， 由于原侧同***管理网元通过 GTP信息， 或步骤 402中的
Context Request消息， 或步骤 404中的 Context Ack消息已经从目标侧管理网 元获取到的目标侧管理网元的版本信息，所以可以通知原侧异***管理网元删 除其承载上下文。
本实施例中，原侧同***管理网元从 S-GW反馈的承载删除响应中获取原 侧异***管理网元的地址信息。
则原侧同***管理网元可以才 据获取到的原侧异***管理网元的地址信 息向原侧异***管理网元发送承载删除消息 ,在承载删除消息中可以携带删除 承载的原因值为： "目标侧管理网元不支持 ISR"。
需要说明的是， 本步骤 408可以在收到目标侧管理网元发送 Context ACK 消息后选择合适的时机执行， 例如计时器超时， 即接收到 Context ACK消息之 后在预置的时间内仍然没有触发执行下一步流程。
原侧异***管理网元接收到删除承载消息后删除本地和该 UE相关的承载 上下文。
本实施例中， 原侧异***管理网元还可以通知 S-GW删除承载。
需要说明的是， 步骤 407和步骤 408可以结合实现， 以删除 S-GW上的承 载上下文，并完全释放相关承载资源，例如 S-GW与原侧同***管理网元之间 可以分配承载资源， 同样， S-GW与原侧异***管理网元之间也可以分配承载 资源，若步骤 407中的承载删除请求仅要求 S-GW释放 S-GW与原侧同***管 理网元之间的承载资源，则在步骤 408中，原侧异***还需要通知 S-GW删除 承载上下文，且释放 S-GW与原侧异***管理网元之间的承载资源，可以理解 的是，若 S-GW与原侧异***之间并未分配承载资源，且在步骤 407中， S-GW 已经按照指示删除了自身的承载上下文，并释放了 S-GW与原侧同***管理网 元之间的承载，则步骤 408中，原侧异***管理网元可以不再通知 S-GW删除 承载。
409、 目标侧管理网元向 UE发送 RAU Accept消息；
410、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中，原侧同***管理网元通过 S-GW获取原侧异***管理网元的 地址信息 ,所以可以通过该地址信息向对应的原侧异***管理网元发送承载删 除消息， 可以理解的是，原侧同***管理网元还可以从其他网元获取原侧异系 统管理网元的地址信息， 具体请参阅图 5, 本发明实施例中资源释放控制方法 第五实施例中， 原侧同***管理网元从 HSS从获取原侧异***管理网元的地 址信息。
本发明实施例中资源释放控制方法第五实施例具体包括：
501、 UE向目标侧管理网元发 RAU Request消息；
当 UE移动到其他 MME或 SGSN覆盖的范围后， UE向目标侧管理网元 发送携带 P-TMSI以及 GUTI信元的 RAU Request消息以请求在目标侧管理网 元中进行注册。
502、 目标侧管理网元向原侧同***管理网元发送 Context Request消息； 目标侧管理网元接收到 UE发送的 RAU Request消息之后 ,向原侧同*** 管理网元发送 Context Request消息以请求上下文信息。
本实施例中，在步骤 502之前， 目标侧管理网元会与原侧同***管理网元 之间进行协议版本探测，原侧同***管理网元可以获知目标侧管理网元的 GTP 的版本， 若该 GTP版本信息显示为较低版本， 比如 GTPV0或者 GTP V1 , 则 原侧同***管理网元可以获知目标侧管理网元的版本信息为 Pre-Rel-8版本， 即目标侧管理网元不支持与 S-GW交互， 且不支持 ISR, 本实施例以及后续实 施例中以 Pre-Rel-8为例进行说明， 可以理解的是， 在实际应用中还可以是其 他类型的不支持与 S-GW交互， 且不支持 ISR的版本。
上述介绍了原侧同***管理网元通过 GTP信息的检测获知目标侧管理网 元的版本信息的情况， 可以理解的是， 目标侧管理网元还可以通过步骤 502 中的 Context Request消息将自身的版本信息告知原侧同***管理网元， 具体 的方式可以为在 Context Request消息中扩展一个字段用于指示目标侧管理网 元的版本信息，或者是在现有的字段中增添一个标识用于指示版本信息，或是 其他指示手段均可。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带"版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
503、 原侧同***管理网元向目标侧管理网元发送 Context Response消息 返回手机上下文信息；
504、 目标侧管理网元向原侧同***管理网元发送 ContextAck消息； 本实施例中， 目标侧管理网元除了在步骤 502中可以通过 Context Request 消息向原侧同***管理网元反馈目标侧管理网元的版本信息之夕卜，还可以在步 骤 504中通过 Context Ack消息向原侧同***管理网元发送目标侧管理网元的 版本信息， 具体的发送方式与通过 Context Request消息发送的方式一致， 此 处不再赞述。
505、 目标侧管理网元向 P-GW发送消息更新承载上下文；
506、 目标侧管理网元向 HSS 发送位置更新请求消息 Update Location Request消息；
本实施例中 , 步骤 506中， 目标侧管理网元通过 Update Location Request 消息将目标侧管理网元的版本信息发送至 HSS , 具体的方式可以为在 Update Location Request消息中扩展一个字段用于指示目标侧管理网元的版本信息。
507、 HSS向原侧同***管理网元发送 Cancel Location消息； 本实施例中， HSS获知 Update Location Request消息中携带有目标侧管理 网元的版本信息时， 则触发 HSS将原侧异***管理网元的控制面信息发送至 原侧同***管理网元，具体的方式可以为在 Cancel Location消息中扩展一个字 段用于存放原侧异***管理网元的控制面信息（包括地址信息）。
除上述的触发方式之外，原侧同***管理网元还可以通过新增一条交互信 令， 例如 ISR Information Request, 在该信令中指示 HSS反馈原侧异***管理 网元的控制面信息， 则 HSS在接收到该信令后， 获取原侧异***管理网元的 控制面信息， 携带于 ISR Information Response中反馈给原侧同***管理网元。
508、 HSS向目标侧管理网元发送 Update Location Ack消息；
509、 原侧同***管理网元通知 S-GW删除承载；
本实施例中，原侧同***管理网元向 S-GW发送承载删除消息，该承载删 除消息指示 S-GW删除自身承载， 需要说明的是， 在本实施例中， S-GW删除 自身承载是指 S-GW删除自身的承载上下文并且释放承载资源。
S-GW在接收到原侧同***管理网元发送的承载删除消息之后，删除自身 的承载上下文， 并释放承载资源。
510、 原侧同***管理网元通知原侧异***管理网元删除^载上下文； 本实施例中， 由于原侧同***管理网元通过 GTP信息， 或步骤 502中的
Context Request消息， 或步骤 504中的 Context Ack消息已经从目标侧管理网 元获取到的目标侧管理网元的版本信息，所以可以通知原侧异***管理网元删 除其承载上下文。
本实施例中， 原侧同***管理网元从 HSS反馈的信息中获取原侧异*** 管理网元的地址信息。
则原侧同***管理网元可以才 据获取到的原侧异***管理网元的地址信 息向原侧异***管理网元发送承载删除消息 ,在承载删除消息中可以携带删除 承载的原因值为： "目标侧管理网元不支持 ISR"。
需要说明的是， 本步骤 510可以在收到目标侧管理网元发送 Context ACK 消息后选择合适的时机执行， 例如计时器超时， 即接收到 Context ACK消息之 后在预置的时间内仍然没有触发执行下一步流程。
511、 原侧异***管理网元删除本地和 UE相关的承载； 原侧异***管理网元接收到删除承载消息后删除本地和该 UE相关的承载 上下文。
本实施例中， 原侧异***管理网元还可以通知 S-GW删除承载上下文。 需要说明的是， 步骤 509和步骤 511可以结合实现， 以删除 S-GW上的承 载上下文，并完全释放相关承载资源，例如 S-GW与原侧同***管理网元之间 可以分配承载资源， 同样， S-GW与原侧异***管理网元之间也可以分配承载 资源，若步骤 509中的承载删除请求仅要求 S-GW释放 S-GW与原侧同***管 理网元之间的承载资源， 则在步骤 511中，原侧异***还需要通知 S-GW删除 承载上下文，且释放 S-GW与原侧异***管理网元之间的承载资源，可以理解 的是，若 S-GW与原侧异***之间并未分配承载资源，且在步骤 507中， S-GW 已经按照指示删除了自身的承载上下文，并释放了 S-GW与原侧同***管理网 元之间的承载， 则步骤 511中，原侧异***管理网元可以不再通知 S-GW删除 承载。
512、 目标侧管理网元向 UE发送 RAU Accept消息；
513、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中， 原侧同***管理网元通过 HSS获取原侧异***管理网元的 地址信息 , 所以能够向原侧异***管理网元发送 7 载删除消息。
上述的五个实施例中均以 RAU流程为例进行说明， 在实际应用中还可以 是其他的流程， 下面以切换 HANDOVER流程为例进行说明， 请参阅图 6, 本 发明实施例中资源释放控制方法第六实施例中，由原侧异***管理网元自身获 取到目标侧管理网元的版本信息，则原侧异***管理网元可以判断目标侧管理 网元不支持与 S-GW交互， 且不支持 ISR, 则原侧异***管理网元可以删除自 身的承载上下文。
本发明实施例中资源释放控制方法第六实施例具体包括：
601、 源演进基站 Source eNodeB向原侧异***管理网元发送重定位请求
Relocation Required;
602、原侧异***管理网元向目标侧管理网元发送前向重定位请求 Forward Relocation Request消息；
603、 目标侧管理网元向目标无线网络控制器 （ RNC , Radio Network Controller )发送重定位请求， 以请求分配无线资源；
604、目标侧管理网元向原侧异***管理网元反馈前向重定位响应 Forward Relocation Response消息；
本实施例中， 目标侧管理网元向原侧异***管理网元反馈的 Forward Relocation Response消息携带目标侧管理网元版本信息 , 具体的携带方式可以 为在 Forward Relocation Response消息扩展一个字段用于携带该版本信息， 或 在现有的字段中增添该版本信息。
605、 原侧异***管理网元向 Source eNodeB发送重定位命令 Relocation Command消息；
606、 执行 Relocation的其他流程；
607、 Relocation完成后， 目标侧管理网元向原侧异***管理网元发送前向 重定位完成 Forward Relocation Complete消息；
本实施例中，除了在步骤 604中， 目标侧管理网元通过 Forward Relocation Response消息将目标侧管理网元的版本信息发送至原侧异***管理网元之外， 在本步骤 607中， 目标侧管理网元还可以通过 Forward Relocation Complete消 息将目标侧管理网元的版本信息发送至原侧异***管理网元，具体的发送方式 与前述步骤 604中的方式一致
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带"版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。。
608、 收到消息后， 原侧异***管理网元向目标侧管理网元发送前向重定 位完成确认 Forward Relocation Complete Acknowledge消息；
609、 目标侧管理网元发送消息到 PDN GW更新承载信息；
610、 原侧异***管理网元删除^载上下文。
本实施例中，由于原侧异***管理网元通过步骤 604或 607获取到了目标 侧管理网元的版本信息， 并获知该版本信息指示目标侧管理网元不支持与 S-GW交互， 且不支持 ISR， 则原侧异***管理网元删除本地承载上下文并通 知 S-GW删除本地承载，则 S-GW在接收到原侧异***管理网元的指示后删除 自身的承载上下文， 并且释放承载资源。
本步骤 610 中， 原侧异***管理网元可以在收到目标侧管理网元的 Forward Relocation Complete 消息后， 选择合适的时机执行， 例如在收到 Forward Relocation Complete消息之后的预置之间内没有消息触发执行下一步 流程， 则删除承载上下文。
本实施例中，原侧异***管理网元自身从目标侧管理网元获取到目标侧管 理网元的版本信息， 所以在判断该版本信息指示目标侧管理网元不支持与 S-GW交互， 且不支持 ISR之后删除本地承载上下文。
下面介绍另外一种在 HANDOVER流程下的实现方式：
请参阅图 7, 本发明实施例中资源释放控制方法第七实施例中， 原侧同系 统管理网元获取目标侧管理网元的版本信息，并自身向原侧异***管理网元发 送承载删除消息， 或者通过 S-GW向原侧异***管理网元发送承载删除消息。
本发明实施例中资源释放控制方法第七实施例具体包括：
701、源 RNC向原侧同***管理网元发送重定位请求 Relocation Required;
702、原侧同***管理网元向目标侧管理网元发送前向重定位请求 Forward Relocation Request消息；
703、目标侧管理网元向目标 RNC发送重定位请求，以请求分配无线资源； 704、目标侧管理网元向原侧同***管理网元反馈前向重定位响应 Forward
Relocation Response消息；
本实施例中， 目标侧管理网元向原侧同***管理网元反馈的 Forward Relocation Response消息携带目标侧管理网元版本信息 , 具体的携带方式可以 为在 Forward Relocation Response消息扩展一个字段用于携带该版本信息， 或 在现有的字段中增添该版本信息。
上述描述的为显式指示的情况，即目标侧管理网元通过显式信元的方式指 示自身的版本信息（即不支持与 S-GW交互， 且不支持 ISR ), 可以理解的是， 目标侧管理网元还可以通过隐式的方式指示自身的版本信息，例如目标侧管理 网元在发送给原侧同***管理网元或原侧异***管理网元的信令中不携带"版 本"字段，或该字段中的数值为空，则默认表示目标侧管理网元不支持与 S-GW 交互， 且不支持 ISR。
705、 执行 Relocation其他流程；
706、 UE向目标侧管理网元发送 RAU请求；
707、 执行 RAU其他流程；
本实施例中 , 具体的 RAU其他流程可以为： 目标侧管理网元与 HSS交互 进行位置更新； HSS 与原侧同***管理网元交互取消原侧同***管理网元在 HSS中的注册。
708 - 710, 删除原侧异***管理网元中的承载上下文；
本实施例中， 原侧同***管理网元获取到目标侧管理网元的版本信息之 后，可以向原侧异***管理网元发送承载删除消息， 则获取原侧异***管理网 元的地址信息可以使用预置的地址信息，或从 S-GW获取地址信息，或从 HSS 获取地址信息， 具体的获取方式与前述实施例中的获取方式类似，此处不再赘 述。
除此之外，原侧同***管理网元还可以指示 S-GW删除原侧异***管理网 元的承载上下文，具体的处理方式也与前述实施例中的指示方式类似，此处不 再赘述。
711、 目标侧管理网元向 UE发送 RAU Accept消息；
712、 UE向目标侧管理网元发送 RAU Complete消息。
本实施例中， 原侧同***管理网元获取目标侧管理网元的版本信息之后， 可以自身向原侧异***管理网元发送承载删除消息，或者通过 S-GW向原侧异 ***管理网元发送承载删除消息。
本实施例中， S-GW需要删除本地承载， 即删除自身承载上下文， 并释放 承载资源， 具体的删除流程与前述实施例中的删除流程类似， 此处不再赞述。
上述各个实施例中，原侧同***管理网元或原侧异***管理网元获取到目 标侧管理网元的版本信息之后，确定该版本信息指示所述目标侧管理网元不与 服务网关 S-GW交互， 且不支持空闲模式下节约信令 ISR, 则可以根据所述版 本信息删除原侧异***管理网元中的承载上下文，因此本发明实施例中目标侧 管理网元在不支持与 S-GW交互且不支持 ISR的情况下同样能够删除原侧异系 统管理网元上的承载上下文。
下面介绍本发明实施例中的通讯***实施例， 请参阅图 8， 本发明实施例 中的通讯***实施例包括：
原侧同***管理网元 801， 用于当激活 ISR的用户设备从原侧网络切换到 目标侧网络时，对目标侧管理网元的版本信息进行判断， 若判断结果指示所述 目标侧管理网元不与 S-GW交互， 且不支持 ISR, 则发送承载删除消息； 原侧异***管理网元 802， 用于接收承载删除消息， 并根据所述承载删除 消息删除自身的承载上下文。
上述的实施例中，原侧同***管理网元 801获取到目标侧管理网元的版本 信息之后，可以直接根据预置的原侧异***管理网元 802的地址信息向原侧异 ***管理网元 802发送承载删除消息，则原侧异***管理网元 802删除本地的 承载上下文。
可以理解的是， 原侧同***管理网元 801还可以通过 S-GW或 HSS获取 原侧异***管理网元 802的地址信息，并根据获取到的地址信息向对应的原侧 异***管理网元 802发送承载删除消息，则原侧异***管理网元 802删除本地 的承载上下文。
除了原侧同***管理网元 801自身向原侧异***管理网元 802发送承载删 除消息之外，原侧同***管理网元 801还可以通过 S-GW向原侧异***管理网 元 802发送承载删除消息， 则本实施例中的通讯***实施例还可以包括： 服务网关 803， 用于接收所述原侧同***管理网元 801发送的承载删除消 息， 根据所述承载删除消息删除自身的承载上下文， 释放承载资源， 并向所述 原侧异***管理网元 802发送所述承载删除消息。
具体的，服务网关 803从原侧同***管理网元 801接收到的承载删除消息 中还可以包括一个控制信元，用于指示该服务网关 803通知原侧异***管理网 元 802删除 7|载上下文。
请参阅图 9, 本发明实施例中的移动性管理网元第一实施例包括： 获取单元 901 , 用于获取对端管理网元的版本信息；
判断单元 902， 用于根据获取单元 901获取到的对端管理网元的版本信息 判断是否指示不支持与 S-GW交互， 且不支持 ISR; 承载删除控制单元 903， 若所述判断单元 902的判断结果为对端管理网元 不支持与 S-GW交互， 且不支持 ISR, 则执行承载删除流程。
本实施例中， 对端管理网元是指目标侧管理网元。
本实施例中 , 承载删除控制单元 903根据具体的实现可以分为两种情况： 承载删除控制单元 903包括：
地址获取单元 9031 , 用于获取原侧异***管理网元的地址信息； 删除指示单元 9032， 根据所述版本信息以及所述地址信息向对应的原侧 异***管理网元发送 载删除消息，该^载删除消息用于指示原侧异***管理 网元删除自身的承载上下文。
在该方式下， 该移动性管理网元可以为原侧同***管理网元。 或 承载删除控制单元 903包括：
承载删除单元 9033 , 用于根据所述版本信息删除自身的承载上下文。 在该方式下， 该移动性管理网元可以为原侧异***管理网元。
本实施例中的地址获取单元 9031包括以下单元中的至少一个：
第一地址获取单元 90311， 用于获取预置的原侧异***管理网元的地址信 第二地址获取单元 90312， 用于从 S-GW获取所述原侧异***管理网元的 地址信息；
第三地址获取单元 90313，用于从 HSS获取所述原侧异***管理网元的地 址信息。
请参阅图 10， 本发明实施例中网关设备实施例包括：
接收单元 1001 , 用于接收原侧同***管理网元发送的承载删除消息； 删除执行单元 1002， 用于根据所述承载删除消息删除自身的承载上下文 并释放承载资源；
删除控制单元 1003 , 用于向原侧异***管理网元发送承载删除消息， 用 于指示所述原侧异***管理网元删除承载上下文。
本实施例中的删除执行单元 1002为可选单元。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤 是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可 读存储介质中， 该程序在执行时， 包括如下步骤：
当激活空闲模式节约信令机制 ISR的用户设备从原侧网络切换到目标侧 网络时，
获取目标侧管理网元的版本信息；
若所述版本信息指示所述目标侧管理网元不与服务网关 S-GW交互，且不 支持 ISR, 则删除原侧异***管理网元中的承载。
上述提到的存储介质可以是只读存储器， 磁盘或光盘等。
以上对本发明所提供的一种资源释放控制方法及通讯***以及相关设备 进行了详细介绍， 对于本领域的一般技术人员， 依据本发明实施例的思想， 在 具体实施方式及应用范围上均会有改变之处， 综上所述，本说明书内容不应理 解为对本发明的限制。

Claims

权 利 要 求
1、 一种资源释放控制方法， 其特征在于， 当激活空闲模式节约信令机制 ISR的用户设备从原侧网络切换到目标侧网络时， 包括：
获取目标侧管理网元的版本信息；
若所述版本信息指示所述目标侧管理网元不与服务网关 S-GW交互，且不 支持 ISR, 则删除原侧异***管理网元中的承载。
2、 根据权利要求 1所述的方法， 其特征在于， 所述获取目标侧管理网元 的版本信息的步骤包括：
原侧同***管理网元接收所述目标侧管理网元发送的指示所述目标侧管 理网元的版本的消息。
3、 根据权利要求 1所述的方法， 其特征在于， 所述获取目标侧管理网元 的版本信息的步骤包括：
原侧同***管理网元与所述目标侧管理网元进行消息交互获取所述目标 侧管理网元的通用无线分组业务隧道协议 GTP版本信息；
若所述 GTP版本为 GTP V0或 GTP V1 , 则确定所述目标侧管理网元不与 服务网关 S-GW交互， 且不支持 ISR。
4、 根据权利要求 1至 3中任一项所述的方法， 其特征在于， 所述删除原 侧异***管理网元中的承载的步骤包括：
原侧同***管理网元才 据预置的原侧异***管理网元的地址信息向对应 的原侧异***管理网元发送删除承载消息；
所述原侧异***管理网元根据所述删除承载消息删除自身的承载。
5、 根据权利要求 1至 3中任一项所述的方法， 其特征在于， 所述删除原 侧异***管理网元中的承载的步骤包括：
原侧同***管理网元接收 S-GW或归属用户服务器 HSS发送的原侧异系 统管理网元的地址信息；
根据所述地址信息向对应的原侧异***管理网元发送删除承载消息； 所述原侧异***管理网元根据所述删除承载消息删除自身的承载。
6、 根据权利要求 1至 3中任一项所述的方法， 其特征在于， 所述删除原 侧异***管理网元中的承载的步骤包括： S-GW接收原侧同***管理网元发送的删除承载消息；
S-GW删除自身承载， 并向原侧异***管理网元发送承载删除消息； 所述原侧异***管理网元根据所述删除承载消息删除自身的承载。
7、 根据权利要求 1至 3中任一项所述的方法， 其特征在于， 所述删除原 侧异***管理网元中的承载的步骤包括：
S-GW接收原侧同***管理网元发送的携带控制信元的删除承载消息， 所 述控制信元用于指示 S-GW向原侧异***管理网元发送承载删除消息；
S-GW删除自身承载， 并根据所述控制信元向原侧异***管理网元发送承 载删除消息；
所述原侧异***管理网元根据所述删除承载消息删除自身的承载。
8、 根据权利要求 1所述的方法， 其特征在于， 所述获取目标侧管理网元 的版本信息的步骤包括：
原侧异***管理网元接收所述目标侧管理网元发送的指示所述目标侧管 理网元版本信息的上下文请求消息、上下文确认消息、前向重定位响应或前向 重定位完成消息。
9、 根据权利要求 8所述的方法， 其特征在于， 所述删除原侧异***管理 网元中的承载的步骤包括：
原侧异***管理网元删除自身的承载。
10、 一种通讯***， 其特征在于， 包括：
原侧同***管理网元，用于当激活 ISR的用户设备从原侧网络切换到目标 侧网络时，获取目标侧管理网元的版本信息， 若所述版本信息指示所述目标侧 管理网元不与 S-GW交互， 且不支持 ISR, 则发送承载删除消息；
原侧异***管理网元， 用于接收承载删除消息， 并根据所述承载删除消息 删除自身的承载。
11、 根据权利要求 10所述的通讯***， 其特征在于， 所述原侧同***管 理网元还用于，
获取预置的原侧异***管理网元的地址信息 ,向对应的原侧异***管理网 元发送所述承载删除消息；
或 从服务网关或归属用户服务器获取原侧异***管理网元的地址信息 ,根据 所述地址信息向对应的原侧异***管理网元发送所述承载删除消息。
12、 根据权利要求 10所述的通讯***， 其特征在于， 所述通讯***还包 括：
服务网关， 用于接收所述原侧同***管理网元发送的承载删除消息，根据 所述承载删除消息删除自身的承载，并向所述原侧异***管理网元发送所述承 载删除消息。
13、 一种移动性管理网元， 与无线接入网相连， 用于对用户移动状态进行 管理， 其特征在于， 包括：
获取单元， 用于获取对端管理网元的版本信息；
判断单元，用于根据获取单元获取到的对端管理网元的版本信息判断是否 指示不支持与 S-GW交互， 且不支持 ISR;
承载删除控制单元，若所述判断单元的判断结果为对端管理网元不支持与
S-GW交互， 且不支持 ISR, 则执行承载删除流程。
14、 根据权利要求 13所述的移动性管理网元， 其特征在于， 所述承载删 除控制单元包括：
地址获取单元， 用于获取原侧异***管理网元的地址信息；
删除指示单元，根据所述版本信息以及所述地址信息向对应的原侧异*** 管理网元发送承载删除消息。
15、 根据权利要求 14所述的移动性管理网元， 其特征在于， 所述地址获 取单元包括以下单元中的至少一个：
第一地址获取单元， 用于获取预置的原侧异***管理网元的地址信息； 第二地址获取单元，用于从 S-GW获取所述原侧异***管理网元的地址信 第三地址获取单元， 用于从 HSS获取所述原侧异***管理网元的地址信
16、 根据权利要求 13所述的移动性管理网元， 其特征在于， 所述承载删 除控制单元包括：
承载删除单元， 用于根据所述版本信息删除承载。
17、 一种网关设备， 与无线接入网和分组数据网相连， 用于承载无线接入 网和分组数据网之间的用户数据传输， 其特征在于， 包括：
接收单元， 用于接收原侧同***管理网元发送的承载删除消息； 删除控制单元，用于根据所述承载删除消息指示原侧异***管理网元删除 所述原侧异***管理网元上的承载。
18、 根据权利要求 17所述的网关设备， 其特征在于， 所述网关设备还包 括：
删除执行单元 , 用于根据所述承载删除消息删除自身的承载。
PCT/CN2009/070159 2008-01-31 2009-01-15 一种资源释放控制方法及通讯***以及相关设备 WO2009097772A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP09708079.0A EP2187687B2 (en) 2008-01-31 2009-01-15 Control method, communication system and relative device for resource release
US12/779,655 US8325682B2 (en) 2008-01-31 2010-05-13 Resource release control method, communication system and device
US13/182,274 US8144665B2 (en) 2008-01-31 2011-07-13 Resource release control method, communication system and device
US13/660,613 US8830962B2 (en) 2008-01-31 2012-10-25 Method, communication system and device for controlling resource release

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810006802.8 2008-01-31
CN2008100068028A CN101472312B (zh) 2008-01-31 2008-01-31 一种资源释放控制方法及通讯***以及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/779,655 Continuation US8325682B2 (en) 2008-01-31 2010-05-13 Resource release control method, communication system and device

Publications (1)

Publication Number Publication Date
WO2009097772A1 true WO2009097772A1 (zh) 2009-08-13

Family

ID=40829357

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070159 WO2009097772A1 (zh) 2008-01-31 2009-01-15 一种资源释放控制方法及通讯***以及相关设备

Country Status (5)

Country Link
US (3) US8325682B2 (zh)
EP (2) EP2187687B2 (zh)
CN (1) CN101472312B (zh)
PT (1) PT2187687E (zh)
WO (1) WO2009097772A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011081384A2 (en) * 2009-12-29 2011-07-07 Lg Electronics Inc. Method for determining isr deactivation in mobile communications system

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101365230B (zh) 2007-08-07 2010-08-11 华为技术有限公司 异构网络切换/改变时的用户分离方法、***及装置
CN101472312B (zh) 2008-01-31 2010-07-07 华为技术有限公司 一种资源释放控制方法及通讯***以及相关设备
CN101610576B (zh) * 2008-06-18 2013-01-30 上海华为技术有限公司 限制信令下的信息处理方法及相关设备
US8787362B2 (en) * 2009-04-01 2014-07-22 Qualcomm Incorporated Fall back using mobile device assisted terminating access domain selection
US8711822B2 (en) * 2009-04-08 2014-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Mobility management in a communications system
US8441985B2 (en) * 2009-10-21 2013-05-14 Lg Electronics Inc. Method for determining ISR activation in mobile communications system
WO2011097813A1 (zh) * 2010-02-11 2011-08-18 华为技术有限公司 去激活isr的方法、修改承载参数的方法和网络***
US8774207B2 (en) * 2010-07-31 2014-07-08 Motorola Solutions, Inc. Methods for bearer reservation, maintenance, and use in a communication system
WO2012040937A1 (zh) * 2010-09-30 2012-04-05 华为技术有限公司 一种消息发送方法、***以及移动管理网元
US8838156B2 (en) 2010-10-22 2014-09-16 Motorola Solutions, Inc. Multi-bearer rate control for transporting user plane data
KR101746668B1 (ko) * 2010-12-21 2017-06-13 한국전자통신연구원 접속해제 상태의 사물통신 디바이스를 위한 데이터 전송 방법 및 이를 이용하는 이동통신 시스템
CN102892153B (zh) * 2011-07-22 2017-08-01 中兴通讯股份有限公司 一种中继节点切换中释放用户终端信息的方法和***
US20130039287A1 (en) 2011-08-12 2013-02-14 Venkata Ratnakar Rao Rayavarapu Simplified ue + enb messaging
EP2557889B1 (en) 2011-08-12 2019-07-17 BlackBerry Limited Simplified ue + enb messaging
US9247575B2 (en) 2012-03-27 2016-01-26 Blackberry Limited eNB storing RRC configuration information at another network component
US9247528B2 (en) 2012-10-12 2016-01-26 Cisco Technology, Inc. System and method for reducing paging in UTRAN/GERAN/E-UTRAN networks when idle signaling reduction is active
CN107211455B (zh) * 2015-05-28 2020-10-30 广州配天通信技术有限公司 一种寻呼方法及基站、核心网设备、用户设备
EP4109968A1 (en) * 2017-03-20 2022-12-28 Huawei Technologies Co., Ltd. Inter-communications-system handover
CN109803390B (zh) * 2017-11-17 2023-05-02 中兴通讯股份有限公司 消息、策略发送方法及装置，存储介质，处理器

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1756427A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 一种***间切换的方法
CN101001460A (zh) * 2006-01-11 2007-07-18 华为技术有限公司 异构网络中实现切换处理的方法
CN101068442A (zh) * 2002-04-11 2007-11-07 高通股份有限公司 Cdma***内具有不同协议修订版本的基站间的切换
CN201004704Y (zh) * 2006-03-08 2008-01-09 美商内数位科技公司 用于在基于单隧道gprs的无线通信***中支持路由区域更新过程的设备
CN101282582A (zh) * 2008-05-16 2008-10-08 中兴通讯股份有限公司 一种跨无线接入技术的切换方法
CN101330751A (zh) * 2007-06-19 2008-12-24 华为技术有限公司 释放源网络资源的方法、网关实体以及网络设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE272301T1 (de) 2000-05-16 2004-08-15 Siemens Ag Verfahren zum umlegen eines tunnels zwischen knoten eines gprs-systems
CN1595863A (zh) * 2003-09-13 2005-03-16 华为技术有限公司 通用分组无线业务服务支持节点之间位置更新的方法
CN100362815C (zh) * 2004-07-21 2008-01-16 华为技术有限公司 检测支持gtp协议端点设备间接口联通性的方法
CN100466842C (zh) * 2006-06-09 2009-03-04 华为技术有限公司 宽带码分多址***中的软切换方法
CN101355792B (zh) * 2007-07-25 2011-11-23 华为技术有限公司 承载删除控制方法及归属用户服务器以及相关设备
WO2009083529A1 (en) * 2007-12-27 2009-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Auto configuration of mobility entity
CN101494882B (zh) 2008-01-24 2012-07-11 华为技术有限公司 切换过程中实现isr的方法、网元设备及网络***
CN101472312B (zh) 2008-01-31 2010-07-07 华为技术有限公司 一种资源释放控制方法及通讯***以及相关设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068442A (zh) * 2002-04-11 2007-11-07 高通股份有限公司 Cdma***内具有不同协议修订版本的基站间的切换
CN1756427A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 一种***间切换的方法
CN101001460A (zh) * 2006-01-11 2007-07-18 华为技术有限公司 异构网络中实现切换处理的方法
CN201004704Y (zh) * 2006-03-08 2008-01-09 美商内数位科技公司 用于在基于单隧道gprs的无线通信***中支持路由区域更新过程的设备
CN101330751A (zh) * 2007-06-19 2008-12-24 华为技术有限公司 释放源网络资源的方法、网关实体以及网络设备
CN101282582A (zh) * 2008-05-16 2008-10-08 中兴通讯股份有限公司 一种跨无线接入技术的切换方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011081384A2 (en) * 2009-12-29 2011-07-07 Lg Electronics Inc. Method for determining isr deactivation in mobile communications system
WO2011081384A3 (en) * 2009-12-29 2011-11-17 Lg Electronics Inc. Method for determining isr deactivation in mobile communications system
US8855091B2 (en) 2009-12-29 2014-10-07 Lg Electronics Inc. Method for determining ISR deactivation in mobile communications system
KR101733486B1 (ko) 2009-12-29 2017-05-24 엘지전자 주식회사 이동통신 시스템에서의 ｉｓｒ 비활성화 결정 방법

Also Published As

Publication number Publication date
US20100220689A1 (en) 2010-09-02
EP2187687A1 (en) 2010-05-19
US8144665B2 (en) 2012-03-27
CN101472312B (zh) 2010-07-07
EP2595447A3 (en) 2013-07-24
EP2187687B1 (en) 2013-03-20
PT2187687E (pt) 2013-05-22
US20130044732A1 (en) 2013-02-21
CN101472312A (zh) 2009-07-01
EP2187687A4 (en) 2011-01-12
US8325682B2 (en) 2012-12-04
EP2187687B2 (en) 2017-05-10
EP2595447A2 (en) 2013-05-22
US8830962B2 (en) 2014-09-09
US20110261780A1 (en) 2011-10-27

Similar Documents

Publication Publication Date Title
WO2009097772A1 (zh) 一种资源释放控制方法及通讯***以及相关设备
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
JP5021772B2 (ja) トラッキングエリアの更新或いは切替プロセスにおいてリソースが誤ってリリースされることを防ぐ方法
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2009000197A1 (fr) Procédé et équipement réseau pour établir et effacer des ressources
WO2013010415A1 (zh) 一种实现ip地址属性通知的方法、***和sgw
WO2010003374A1 (zh) 一种关联关系更新的实现方法及相应终端
US8837355B2 (en) Bearer processing method and mobile management device
WO2011098040A1 (zh) 回退到2g/3g网络的方法和相关设备及通信***
WO2010037321A1 (zh) 移动性管理方法、相关设备及通信***
WO2010031353A1 (zh) 服务请求的处理方法、装置及***
WO2011153750A1 (zh) 一种用户数据的同步方法和***
WO2009046662A1 (fr) Procédé, système et dispositif de traitement de mise à jour de position de terminal mobile
EP2296418B1 (en) Processing method, system and apparatus for mobility management
WO2018059401A1 (zh) 网络切换方法、装置及***，网络接入方法及装置
WO2009138032A1 (zh) 承载处理方法
WO2017167153A1 (zh) 移动通讯***及寻呼方法
WO2008154783A1 (fr) Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service
WO2009152760A1 (zh) 网络间切换、位置区更新、建立isr的方法和***、设备
WO2018010583A1 (zh) 网络***
WO2010000167A1 (zh) Isr去激活方法及移动性管理单元
WO2009076814A1 (zh) 一种pcc规则更新方法和设备
WO2017028637A1 (zh) 网关的恢复处理方法及装置
WO2011157100A1 (zh) 一种数据缓存的方法和***
WO2013000289A1 (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: 09708079

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 503/KOLNP/2010

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2009708079

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE