WO2012094989A1 - 用户设备上下文相关资源的释放方法和设备 - Google Patents

用户设备上下文相关资源的释放方法和设备 Download PDF

Info

Publication number
WO2012094989A1
WO2012094989A1 PCT/CN2012/070192 CN2012070192W WO2012094989A1 WO 2012094989 A1 WO2012094989 A1 WO 2012094989A1 CN 2012070192 W CN2012070192 W CN 2012070192W WO 2012094989 A1 WO2012094989 A1 WO 2012094989A1
Authority
WO
WIPO (PCT)
Prior art keywords
source
intermediate node
user equipment
node
network node
Prior art date
Application number
PCT/CN2012/070192
Other languages
English (en)
French (fr)
Inventor
张涛
蔺波
周铮
Original Assignee
华为技术有限公司
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP15183175.7A priority Critical patent/EP2966902B1/en
Priority to ES12734672.4T priority patent/ES2565386T3/es
Priority to JP2013547807A priority patent/JP5773376B2/ja
Priority to EP12734672.4A priority patent/EP2645774B1/en
Priority to PL12734672T priority patent/PL2645774T3/pl
Publication of WO2012094989A1 publication Critical patent/WO2012094989A1/zh
Priority to US13/934,731 priority patent/US9642045B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release

Definitions

  • the present application claims to be filed on January 10, 2011, the Chinese Patent Office, the application number is 201110004406.3, and the invention name is "user equipment context-related resources translation method and equipment” Chinese patent application Priority is hereby incorporated by reference in its entirety.
  • the present invention relates to the field of wireless communication technologies, and in particular, to a method and device for releasing a context-related resource of a user equipment.
  • a common network architecture is composed of a radio access network and a core network, and a wireless access network and a core network are connected through an interface.
  • the radio access network and the accessed terminal are connected through a wireless interface to provide services for the terminal.
  • This intermediate node acts as a proxy node between the access network node and the core network node: in the view of the core network, the intermediate node is functionally an access network node; in the view of the access network node, the intermediate node is functional Above is a core network node.
  • eNBs are connected to the mobility management entity through a gateway (Gateway; hereinafter referred to as GW).
  • Mobility Management Entity hereinafter referred to as: MME
  • MME Mobility Management Entity
  • eNBs are directly connected to the MME.
  • the eNB and the GW, the GW and the MME, and the logical interface between the eNB and the MME are the same, all of which are S1 interfaces.
  • the user equipment (User Equipment; hereinafter referred to as UE) can switch from the source eNB to the target eNB through the X2 interface, and the handover through the X2 interface is called X2 handover.
  • UE User Equipment
  • the foregoing eNB may be an ordinary macro base station, or may be some small base stations, including a home base. Station (Home enhanced NodeB; hereinafter referred to as HeNB/Home NodeB; hereinafter referred to as HNB) or relay station (Relay Node; hereinafter referred to as RN).
  • Home enhanced NodeB hereinafter referred to as HeNB/Home NodeB; hereinafter referred to as HNB
  • relay station Relay Node; hereinafter referred to as RN.
  • the X2 handover can be divided into the following five cases: (1) The source eNB and the target eNB are connected to the same GW;
  • the source eNB is connected to the GW, and the target eNB is connected to the MME;
  • the source eNB is connected to the MME, and the target eNB is connected to the GW;
  • the source eNB is connected to one GW, and the target eNB is connected to another GW; (5) Both the source eNB and the target eNB are connected to the MME.
  • the target eNB sends a UE context release message to the source eNB through the X2 interface after the X2 handover, and the source eNB will switch to the target eNB after receiving the UE context release message.
  • the context-related resource of the UE includes all resources used by the source eNB for the UE on the user plane and the control plane.
  • the source GWs in cases (2) and (4) also have context-related resources of the UE that has switched to the target eNB, if provided by the prior art. If the scheme of the UE context is translated, the source GW does not notice that the UE has left the jurisdiction of the source GW during and after the X2 handover, which may cause the UE context-related resources on the source GW not to be translated, and the context is related.
  • the resources include all the resources used by the source GW on the user plane and the control plane for the UE, which may result in the new networked UE not being able to access smoothly and the resources being exhausted.
  • the embodiments of the present invention provide a method and a device for downloading context-related resources of a user equipment, so as to implement user equipment context-related resources in the intermediate node of the translation source.
  • An embodiment of the present invention provides a method for releasing a user equipment context-related resource, including: a source intermediate node receiving a control message, where the control message carries an identifier of a user equipment that is handed over to a target access network node; The source intermediate node translates the user equipment context-related resource corresponding to the identifier of the user equipment.
  • the embodiment of the present invention further provides a method for releasing a user equipment context-related resource, including: determining, by the source access network node, that the user equipment is handed over by the source access network node to a target access network node;
  • the source access network node sends a control message to the source intermediate node, where the control message carries an identifier of the user equipment that is switched to the target access network node, so that the source intermediate node translates the identifier of the user equipment.
  • the control message carries an identifier of the user equipment that is switched to the target access network node, so that the source intermediate node translates the identifier of the user equipment.
  • the embodiment of the present invention further provides a method for releasing a user equipment context-related resource, including: the core network node sends a control message to the source intermediate node, where the control message carries the identifier of the user equipment that is switched to the target access network node, Translating, by the source intermediate node, a user equipment context-related resource corresponding to the identifier of the user equipment;
  • the core network node receives a response to the control message sent by the source intermediate node.
  • the embodiment of the present invention further provides a method for downloading user equipment context-related resources, including: the intermediate node monitoring data transmission of data and/or signaling of the user equipment served by the intermediate node;
  • the intermediate node translates the transmission of the data and/or signaling to a user equipment context-related resource that meets predetermined conditions.
  • the embodiment of the invention further provides an intermediate node device, including:
  • a first receiving module configured to receive a control message, where the control message carries an identifier of the user equipment that is switched to the target access network node device;
  • the translation module is configured to: according to the identifier of the user equipment carried in the control message received by the first receiving module, the user equipment context-related resource corresponding to the identifier of the user equipment.
  • the embodiment of the invention further provides a source access network node device, including:
  • a first determining module configured to determine that the user equipment is switched by the source access network node to the target interface Incoming network node
  • a third sending module configured to: after the first determining module determines that the user equipment is handed over to the target access network node by the source access network node by using the handover, sending a control message to the source intermediate node device, where the control The message carries an identifier of the user equipment that is switched to the target access network node device, so that the source intermediate node device releases the user equipment context-related resource corresponding to the identifier of the user equipment.
  • the embodiment of the invention further provides a core network node device, including:
  • a fourth sending module configured to send a control message to the source intermediate node device, where the control message carries an identifier of the user equipment that is switched to the target access network node device, so that the source intermediate node device is translated into the user equipment Identify corresponding user equipment context-related resources;
  • a fourth receiving module configured to receive a response sent by the source intermediate node device for the control message.
  • the embodiment of the invention further provides an intermediate node device, including:
  • a monitoring module configured to monitor transmission of data and/or signaling of the user equipment under the intermediate node device; and a resource release module, configured to release the user equipment that meets the predetermined condition for transmitting data and/or signaling monitored by the monitoring module Context-sensitive resources.
  • the source intermediate node After the source intermediate node receives the control message carrying the identifier of the user equipment that is switched to the target access network node, the source intermediate node decrypts the user equipment context-related resource corresponding to the identifier of the user equipment, thereby implementing the translation source.
  • the user equipment context-related resources in the intermediate node can further enable the newly-entered user equipment to access smoothly and save resources.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 2 is a flowchart of Embodiment 2 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 4 is a flowchart of Embodiment 4 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 4 is a flowchart of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 6 is a flowchart of Embodiment 6 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 6 is a flowchart of Embodiment 6 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 7 is a flowchart of Embodiment 7 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 9 is a flowchart of Embodiment 9 of a method for downloading context-related resources of a user equipment according to the present invention
  • FIG. 10 is a flowchart of a method for downloading context-related resources of a user equipment according to the present invention
  • Embodiment 1 is a schematic structural diagram of Embodiment 1 of an intermediate node device according to the present invention.
  • Embodiment 2 is a schematic structural diagram of Embodiment 2 of an intermediate node device according to the present invention.
  • Embodiment 13 is a schematic structural diagram of Embodiment 1 of a source access network node device according to the present invention.
  • Embodiment 2 of a source access network node device according to the present invention.
  • Embodiment 15 is a schematic structural diagram of Embodiment 1 of a core network node device according to the present invention.
  • Embodiment 16 is a schematic structural diagram of Embodiment 2 of a core network node device according to the present invention.
  • FIG. 17 is a schematic structural diagram of Embodiment 3 of an intermediate node device according to the present invention.
  • FIG. 18 is a schematic structural diagram of Embodiment 4 of an intermediate node device according to the present invention.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for downloading context-related resources of a user equipment according to the present invention.
  • the method for downloading context-related resources of the user equipment may include:
  • Step 101 The source intermediate node receives a control message, where the control message carries an identifier of the user equipment that is switched to the target access network node.
  • Step 102 The source intermediate node releases the user equipment context-related resource corresponding to the identifier of the user equipment.
  • control message may be a user equipment context release request message or a reset message
  • receive control message may be used by the source intermediate node to receive the user equipment context release request sent by the source access network node. Message or reset message.
  • the user equipment context release request message or the reset message may carry a termination identifier, where the user equipment context release request message or the termination identifier in the reset message indicates that the source intermediate node does not need to translate the user equipment context
  • the request message is sent to the core network node.
  • the source intermediate node may further send the received user equipment context release request message or reset message to the core network node, and then receive the core network.
  • User equipment context release command message or reset confirmation message sent by the node.
  • the source intermediate node may further release the received user equipment context release command.
  • the message or the reset confirmation message is sent to the source access network node; then, the source intermediate node may receive the user equipment context release completion message or the reset confirmation message sent by the source access network node.
  • the source intermediate node may further send the received user equipment context release completion message or a reset confirmation message to the core network node.
  • the source intermediate node receives the user equipment context release request message or resets Before the message, the source access network node may further send the intermediate node information of the source access network node to the target access network node, and receive the intermediate node information of the target access network node sent by the target access network node; The source access network node may determine, according to the intermediate node information of the source access network node and the intermediate node information of the target access network node, that the source access network node is connected to the source intermediate node, and the target access network node is connected. On the target intermediate node or the core network node; next, the source access network node may send the foregoing user equipment context release request message or reset message to the source intermediate node.
  • the intermediate node information of the source access network node may include whether the source access network node is connected with an intermediate node, and when the source access network node is connected with an intermediate node, the intermediate node information of the source access network node is further The identifier of the source intermediate node connected to the source access network node may be included; the identifier of the source intermediate node may be before the source access network node sends the information of the intermediate node of the source access network node to the target access network node, And the intermediate node information of the target access network node may include whether the target access network node is connected with an intermediate node, and when the target access network node is connected with an intermediate node, The intermediate node information of the target access network node may further include an identifier of the target intermediate node connected to the target access network node; the identifier of the target intermediate node may be an intermediate node of the target access network node to the target access network node. Before the information is sent to the source access network node, it is sent by the target
  • the source intermediate network node when the access network node that is not connected to the same intermediate node cannot share the tracking area identifier, the source intermediate network node receives the user equipment context release request message or the reset message before the source intermediate node receives the user equipment context release request message or the reset message.
  • the tracking area identifier of the source access network node may be sent to the target access network node, and the tracking area identifier of the target access network node sent by the target access network node is received; then, the source access network node may Determining, according to the tracking area identifier of the source access network node and the tracking area identifier of the target access network node, that the source access network node is connected to the source intermediate node, and the target access network node is connected to the target intermediate node or the core network node; Next, the source access network node may send the foregoing user equipment context release request message to the source intermediate node or Reset the message.
  • control message may be a user equipment context release command message or a reset message.
  • the receiving control message may be: the source intermediate node receives the user equipment context release command message sent by the core network node. Or reset the message.
  • the user equipment context release command message or the reset message may carry a termination identifier, where the user equipment context release command message or the termination identifier in the reset message indicates that the source intermediate node does not need to translate the user equipment context
  • the command message is sent to the source access network node.
  • the source intermediate node may further send the received user equipment context release command message or reset message to the source access network node;
  • the intermediate node may receive a user equipment context release completion message or a reset confirmation message sent by the source access network node.
  • the source intermediate node may further send the received user equipment context release completion message or a reset confirmation message to the core network node.
  • the core network node may receive and save the intermediate node identifier of the intermediate node sent by the intermediate node and the intermediate node identifier corresponding to the intermediate node identifier, where the intermediate node identifier may indicate that the node type that sends the intermediate node identifier is the middle.
  • the above intermediate node identifier uniquely identifies an intermediate node in a network.
  • the intermediate node identifier may be a number, an alphabet, a character string, or the like, which may uniquely identify an intermediate node.
  • the specific form of the intermediate node identifier is not limited in the embodiment of the present invention; likewise, the intermediate node identifier may also be a number or a letter. Or a string or the like may indicate a flag of a node type that sends the intermediate node flag.
  • the specific form of the intermediate node flag is not limited in the embodiment of the present invention.
  • the core network node may determine, according to the identifier of the source side node and the target side node corresponding to the user equipment, and the correspondence between the intermediate node identifier and the intermediate node identifier, whether the source side node is the source intermediate node, and the target side Whether the node is the target intermediate node; when the source side node is the source intermediate node, the target side node is the target intermediate node, and the identifier of the source side node is When the identifiers of the target side nodes are different, or when the source side node is the source intermediate node and the target side node is not the target intermediate node, the core network node may send the foregoing user equipment context release command message or reset message to the source intermediate node.
  • the core network node may receive the identifier of the user equipment that is sent by the target access network node and is switched to the target access network node, and receive the handover to a path switching request sent by the target side node corresponding to the user equipment of the target access network node; the identifier of the user equipment is allocated by the core network node when the user equipment accesses the network, and when the X2 handover is performed,
  • the source access network node sends the target access network node to the target access network node; and then, the core network node performs a search according to the identifier of the user equipment, and the corresponding relationship between the identifier of the saved user equipment and the identifier of the source side node corresponding to the user equipment, Obtaining an identifier of the source side node corresponding to the user equipment; and obtaining an identifier of the target side node corresponding to the user equipment according to the saved correspondence between the path of
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the source side node, and if the identifier of the source side node is the same, If the intermediate node identifier is used, the core network node may determine, according to the intermediate node identifier corresponding to the intermediate node identifier, that the source side node is the source intermediate node; if the intermediate node identifier that is the same as the identifier of the source side node is not found, then the identifier may be determined. The source side node is not the source intermediate node.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the target side node. If the intermediate node identifier is the same as the identifier of the target side node, the core network node may determine the target side node as the target intermediate node according to the intermediate node identifier corresponding to the intermediate node identifier; If the target side node has the same intermediate node identifier, you can It is determined that the target side node is not the target intermediate node.
  • the core network node may send the user equipment context translation to the source intermediate node. Command message or reset message.
  • the core network node may also receive and save the intermediate node identifier sent by the intermediate node and the tracking area identifier corresponding to the intermediate node identifier.
  • the node type corresponding to the set to which the tracking area identifier is sent by the intermediate node is an intermediate node.
  • the intermediate node identifier uniquely identifies an intermediate node in a network; then, the core network node may according to the identifiers of the source side node and the target side node corresponding to the user equipment obtained in advance, and the correspondence between the tracking area identifier and the intermediate node identifier.
  • the core network node may send the user equipment context release command message or the reset message to the source intermediate node device.
  • the core network node may receive the identifier of the user equipment that is sent by the target access network node and is switched to the target access network node, and receive the handover to a path switching request sent by the target side node corresponding to the user equipment of the target access network node; the identifier of the user equipment is allocated by the core network node when the user equipment accesses the network, and when the X2 handover is performed,
  • the source access network node sends the target access network node to the target access network node; and then, the core network node performs a search according to the identifier of the user equipment, and the corresponding relationship between the identifier of the saved user equipment and the identifier of the source side node corresponding to the user equipment, Obtaining an identifier of the source side node corresponding to the user equipment; and obtaining an identifier of the target side node corresponding to the user equipment according to the saved correspondence between the path of
  • an intermediate node and an access network node may be set to use different types of nodes. Track the collection of area IDs.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the source side node, and if the identifier of the source side node is found, If the same intermediate node identifier is used, the core network node may determine, according to the node type corresponding to the set of the tracking area identifier corresponding to the intermediate node identifier, that the source side node is the source intermediate node; if the identifier of the source side node is not found, The intermediate node identifier may determine that the source side node is not the source intermediate node; similarly, after obtaining the identifier of the target side node corresponding to the user equipment, the core network no
  • the core network node may determine the target side according to the node type corresponding to the set of the tracking area identifier corresponding to the intermediate node identifier. The node is the target intermediate node; if it is not found If the target side node has the same intermediate node identifier, it can be determined that the target side node is not the target intermediate node.
  • the core network node may send the foregoing user equipment context release command message or reset message to the source intermediate node.
  • the access network node may be a node with an access function, for example, a base station, etc., where the base station may include an eNB, and the eNB may be an ordinary macro base station, or may be a small base station, including a HeNB/HNB. Or RN, etc.; the core network node may be a node providing core network functions, for example: a mobility management entity, etc.; the intermediate node may provide protocol conversion, routing, data exchange, etc. between the access network node and the core network node.
  • the base station may include an eNB
  • the eNB may be an ordinary macro base station, or may be a small base station, including a HeNB/HNB. Or RN, etc.
  • the core network node may be a node providing core network functions, for example: a mobility management entity, etc.
  • the intermediate node may provide protocol conversion, routing, data exchange, etc. between the access network node and the core network node.
  • the network compatible function node for example, a gateway or a donor base station (Donor eNB; hereinafter referred to as DeNB), etc.; however, the specific form of the access network node, the intermediate node, and the core network node is not limited in the embodiment of the present invention.
  • control message is used as a user equipment context release request message, a user equipment context release command message, or a reset message.
  • the embodiment of the present invention is not limited thereto.
  • the message format is not limited, and the control message may also be Any one of the user equipment context translation request message, the user equipment context release command message, and the reset message, as long as the user equipment that the source intermediate node carries to switch to the target access network node according to the control message can be implemented.
  • the identity of the user equipment context-related resources can be translated.
  • the source intermediate node decrypts the user equipment context-related resource corresponding to the identifier of the user equipment; User equipment context-related resources in the node, which can enable the newly-entered user equipment to access smoothly and save resources.
  • an access network node is an eNB
  • an intermediate node is a GW
  • a core network node is an MME
  • a control message is a UE context translation.
  • the request message is described as an example.
  • the method for translating the user equipment context-related resources may include:
  • Step 201 the source GW sends the GW identifier to the source eNB.
  • Step 202 Optionally, the source eNB exchanges GW information with the target eNB.
  • the source eNB may send the GW information of the source eNB to the target eNB, and receive the GW information of the target eNB sent by the target eNB.
  • the GW information of the source eNB may include whether the source eNB is connected to the GW.
  • the GW information of the source eNB may further include an identifier of the source GW to which the source eNB is connected.
  • the GW information of the target eNB may also include the identifier of the target GW to which the target eNB is connected when the eNB is connected to the GW.
  • Step 203 The UE switches to the target eNB by the source eNB through X2 handover.
  • Step 204 The target eNB sends a UE context release message to the source eNB.
  • Step 205 The source eNB translates the UE context-related resources.
  • Step 206 the source eNB determines, according to the GW information of the source eNB and the GW information of the target eNB, that the source eNB is connected to the source GW, and the target eNB is connected to the target GW or the MME. on.
  • Step 207 The source GW receives the UE context release request message sent by the source eNB, where the UE context release request message carries the identifier of the UE that is handed over to the target eNB.
  • the UE context release request message may further carry a termination identifier, where the termination identifier indicates that the source GW does not need to send the UE context release request message to the MME.
  • Step 208 The source GW releases the UE context-related resource corresponding to the identifier of the UE.
  • the source eNB may determine that the source eNB is connected to the source GW according to the Tracking Area Identifier (hereinafter referred to as TAI) of the source GW and the target GW, and the target eNB is connected to the target GW or On the MME. Specifically, the eNBs that are not connected to the same GW cannot share the TAI, so that when the eNBs that are not connected to the same GW cannot share the TAI, the source eNB may send the TAI of the source eNB to the target eNB, and receive the target eNB.
  • TAI Tracking Area Identifier
  • the source eNB may determine that the source eNB is connected to the source GW according to the TAI of the source eNB and the TAI of the target eNB, and the target eNB is connected to the target GW or the MME; A UE context release request message is sent to the source GW.
  • the source GW may release the UE context-related resource corresponding to the identifier of the UE;
  • the UE context-related resources in the source GW can further enable the newly-entered UE to access smoothly and save resources.
  • FIG. 3 is a flowchart of Embodiment 3 of a method for downloading context-related resources of a user equipment according to the present invention.
  • an access network node is an eNB
  • an intermediate node is a GW
  • a core network node is an MME
  • the control message is a UE context translation.
  • the command message is described as an example.
  • the method for translating the user equipment context-related resources may include:
  • the source GW sends a GW identifier and a GW identifier corresponding to the GW identifier to the MME.
  • the GW flag may indicate that the node type that sends the GW flag is GW.
  • the GW identifier uniquely identifies a GW in a network. .
  • the GW identifier can be
  • the GW flag may also be a number, a letter, a string, or the like, and may be used to indicate that the GW flag is sent, and the GW flag may be a number, a letter, or a string.
  • the specific type of the GW flag is not limited in the embodiment of the present invention.
  • Step 302 The UE switches to the target eNB by the source eNB through X2 handover.
  • Step 303 The target eNB sends a path switch request message to the MME.
  • Step 304 The MME sends a path switch response message to the target eNB.
  • Step 305 The target eNB sends a UE context release message to the source eNB.
  • Step 306 The source eNB translates the UE context-related resources.
  • Step 307 the MME determines, according to the identifiers of the source-side node and the target-side node that are corresponding to the UE, and the corresponding relationship between the GW flag and the GW identifier, whether the source-side node is the source GW, and whether the target-side node is Target GW.
  • the MME may receive the identifier of the UE that is handed over to the target eNB by the target eNB, and receive a path switch request sent by the target side node corresponding to the UE that is switched to the target eNB; the identifier of the UE is accessed by the MME in the UE.
  • the UE is allocated to the UE, and is sent by the source eNB to the target eNB when the X2 handover is performed.
  • the MME may correspond to the identifier of the source-side node corresponding to the UE according to the identifier of the UE.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the source-side node, and if the GW identifier that is the same as the identifier of the source-side node is found, the MME
  • the source side GW may be determined to be the source GW according to the GW flag corresponding to the GW identifier. If the GW identifier is the same as the source side node identifier, the source side node may not be the source GW. Similarly, the UE is obtained.
  • the GW may perform a search according to the identifier of the target side node, and if the GW identifier that is the same as the identifier of the target side node is found, the GW may be based on the GW corresponding to the GW identifier.
  • the flag determines that the target side node is the target GW; if the same GW identifier as the target side node is not found, it may be determined that the target side node is not the target GW.
  • the step 307 is performed after the step 303; the step 307 and the step 304, the step 305, or the step 306 may be performed in sequence, or may be performed in parallel, which is not limited in this embodiment.
  • Step 308 The MME sends a UE context release command message to the source GW, where the UE context translation command message carries the identifier of the UE that is handed over to the target eNB.
  • the MME may be the source GW, the target side node is the target GW, and the identifier of the source side node is different from the identifier of the target side node, or when the source side node is the source GW, and the target side node is not the target GW.
  • the UE context release command message is sent to the source GW.
  • the UE context release command message may further carry a termination identifier, where the termination identifier indicates that the source GW does not need to send the UE context release command message to the source eNB.
  • Step 309 The source GW releases the UE context-related resource corresponding to the identifier of the UE.
  • the MME may also determine, according to the TAI, whether the source side node is the source GW, and whether the target side node is the target GW; specifically, different types of nodes may be set to use different TAI sets at the source GW.
  • the MME may receive the identifier of the UE that is handed over to the target eNB by the target eNB, and receive the path switch request sent by the target side node corresponding to the UE that is handed over to the target eNB; the identifier of the UE is determined by the MME.
  • the UE is allocated to the UE when the UE accesses the network, and is sent by the source eNB to the target eNB when performing the X2 handover.
  • the MME according to the identifier of the UE, saves the identifier of the UE and the source side node corresponding to the UE. Searching for the corresponding relationship of the identifiers, obtaining the identifier of the source side node corresponding to the UE; and obtaining the target side node corresponding to the UE according to the stored correspondence between the path of receiving the path switching request and the identifier of the target side node Identification; wherein, the foregoing UE corresponds to The source side node and the target side node are directly connected to the MME.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the source-side node, and if the GW identifier that is the same as the identifier of the source-side node is found, The MME may determine that the source side node is the source GW according to the node type corresponding to the set of the TAI to which the GW identifier belongs; if the GW identifier that is the same as the identifier of the source side node is not found, the source side node may be determined to be not the source.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the target side node, and if the GW with the same identifier as the target side node is found, The MME may determine that the target side node is the target GW according to the node type corresponding to the set of the TAI to which the GW identifier belongs. If the GW identifier that is the same as the identifier of the target side node is not found, the target side may be determined. The node is not the target GW.
  • the source GW may release the UE context-related resource corresponding to the identifier of the UE;
  • the UE context-related resources in the GW can further enable the newly-entered UE to access smoothly and save resources.
  • an access network node is an eNB
  • an intermediate node is a GW
  • a core network node is an MME
  • a control message is a UE context translation.
  • the command message is described as an example.
  • the method for translating the user equipment context-related resources may include:
  • Step 401 the source GW sends the GW identifier and the GW identifier corresponding to the GW identifier to the MME.
  • the GW flag may indicate that the node type that sends the GW flag is GW.
  • the GW identifier uniquely identifies a GW in a network. .
  • the GW identifier may be a number, a letter, a character string, or the like, which may uniquely identify a GW.
  • the specific form of the GW identifier is not limited in the embodiment of the present invention; likewise, the GW flag may also be a number, a letter, or a character.
  • the string or the like may indicate the flag of the node type that sends the GW flag.
  • the specific form of the GW flag is not limited in the embodiment of the present invention.
  • Step 402 The UE switches to the target eNB by the source eNB through X2 handover.
  • Step 403 The target eNB sends a path switch request message to the MME.
  • Step 404 The MME sends a path switch response message to the target eNB.
  • Step 405 Optionally, the target eNB sends a UE context release message to the source eNB.
  • Step 407 the MME determines, according to the identifiers of the source-side node and the target-side node that are corresponding to the UE, and the corresponding relationship between the GW flag and the GW identifier, whether the source-side node is the source GW, and whether the target-side node is Target GW.
  • the MME may receive the identifier of the UE that is handed over to the target eNB by the target eNB, and receive a path switch request sent by the target side node corresponding to the UE that is switched to the target eNB; the identifier of the UE is accessed by the MME in the UE.
  • the UE is allocated to the UE, and is sent by the source eNB to the target eNB when the X2 handover is performed.
  • the MME may correspond to the identifier of the source-side node corresponding to the UE according to the identifier of the UE.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the source-side node, and if the GW identifier that is the same as the identifier of the source-side node is found, the MME
  • the source side GW may be determined to be the source GW according to the GW flag corresponding to the GW identifier. If the GW identifier is the same as the source side node identifier, the source side node may not be the source GW. Similarly, the UE is obtained.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the target side node, and if the GW identifier that is the same as the identifier of the target side node is found, the MME The target side node may be determined as the target GW according to the GW flag corresponding to the GW identifier. If the same GW identifier as the target side node identifier is not found, the target side node may be determined not to be the target GW.
  • the step 407 is performed after the step 403; the step 407 and the step 404, the step 405 or the step 406 may be performed in sequence, or may be performed in parallel, which is not limited in this embodiment.
  • Step 408 The MME sends a UE context release command message to the source GW, where the UE context translation command message carries the identifier of the UE that is handed over to the target eNB.
  • the MME may be the source GW, the target side node is the target GW, and the identifier of the source side node is different from the identifier of the target side node, or when the source side node is the source GW, and the target side node is not the target GW.
  • the UE context release command message is sent to the source GW.
  • Step 409 The source GW sends the UE context release command message to the source eNB, where the UE context release command message carries the identifier of the UE that is handed over to the target eNB.
  • Step 410 the source eNB releases the UE context-related resource corresponding to the identifier of the UE.
  • step 410 and step 406 are mutually exclusive, that is, only two of the two steps may exist in any one of the implementations.
  • Step 411 The source eNB sends a UE context release completion message to the source GW, where the UE context release completion message carries the identifier of the UE that is handed over to the target eNB.
  • Step 412 The source GW releases the UE context-related resource corresponding to the identifier of the UE.
  • the source GW sends a UE context release completion message to the MME.
  • the MME may also determine, according to the TAI, whether the source side node is the source GW, and whether the target side node is the target GW; specifically, different types of nodes may be set to use different TAI sets at the source GW.
  • the MME may receive the identifier of the UE that is handed over to the target eNB by the target eNB, and receive the path switch request sent by the target side node corresponding to the UE that is handed over to the target eNB; the identifier of the UE is determined by the MME.
  • the UE is allocated to the UE when it accesses the network, and is sent by the source eNB to the target eNB when performing the X2 handover; and then, according to the identifier of the UE, the MME saves the identifier of the UE and the source side node corresponding to the UE. And performing the search in the corresponding relationship of the identifier to obtain the identifier of the source side node corresponding to the UE; and obtaining the identifier of the target side node corresponding to the UE according to the corresponding relationship between the path of the received path switching request and the identifier of the target side node.
  • the source side node and the target side node corresponding to the UE are directly connected to the MME.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the source-side node, and if the GW identifier that is the same as the identifier of the source-side node is found, The MME may determine that the source side node is the source GW according to the node type corresponding to the set of the TAI to which the GW identifier belongs; if the GW identifier that is the same as the identifier of the source side node is not found, the source side node may be determined to be not the source.
  • the MME may perform a search in the GW identifier saved by the MME according to the identifier of the target side node, and if the GW with the same identifier as the target side node is found, The MME may determine that the target side node is the target GW according to the node type corresponding to the set of the TAI to which the GW identifier belongs. If the GW identifier that is the same as the identifier of the target side node is not found, the target side may be determined. The node is not the target GW.
  • the source GW may send the UE context release command message to the source eNB, and then the source GW may receive the source eNB.
  • the UE context translation completion message is sent, and then the source GW can release the UE context-related resource corresponding to the identifier of the UE that is switched to the target eNB carried in the UE context release completion message; Resources, in turn, enable new UEs to access the network smoothly and save resources.
  • the access network node is the eNB
  • the intermediate node is the GW
  • the core network node is the MME
  • the control message is the UE context translation request message.
  • the method for translating the user equipment context-related resources may include:
  • Step 501 the source GW sends a GW identifier to the source eNB.
  • Step 502 Optionally, the source eNB exchanges GW information with the target eNB.
  • the source eNB may send the GW information of the source eNB to the target eNB, and receive the GW information of the target eNB sent by the target eNB.
  • the GW information of the source eNB may include whether the source eNB is connected to the GW.
  • the GW information of the source eNB may further include an identifier of the source GW to which the source eNB is connected.
  • the GW information of the target eNB may also include the identifier of the target GW to which the target eNB is connected when the eNB is connected to the GW.
  • Step 503 The UE switches to the target eNB by the source eNB through the X2 handover.
  • Step 504 The target eNB sends a UE context release message to the source eNB.
  • Step 505 The source eNB translates the UE context-related resources.
  • Step 506 the source eNB determines, according to the GW information of the source eNB and the GW information of the target eNB, that the source eNB is connected to the source GW, and the target eNB is connected to the target GW or the MME.
  • Step 507 The source GW receives the UE context release request message sent by the source eNB, where the UE context release request message carries the identifier of the UE that is handed over to the target eNB.
  • Step 508 The source GW sends the foregoing UE context release request message to the MME, where the UE context release request message carries the identifier of the UE that is handed over to the target eNB.
  • Step 509 The MME sends a UE context release command message to the source GW, where the UE context translation command message carries the identifier of the UE that is handed over to the target eNB.
  • Step 510 The source GW releases the UE context-related resource corresponding to the identifier of the UE.
  • the source eNB may also be based on the tracking area of the source GW and the target GW.
  • the Tracking Area Identifier (hereinafter referred to as TAI) determines that the source eNB is connected to the source GW, and the target eNB is connected to the target GW or the MME. Specifically, the eNBs that are not connected to the same GW cannot share the TAI, so that when the eNBs that are not connected to the same GW cannot share the TAI, the source eNB may send the TAI of the source eNB to the target eNB, and receive the target eNB.
  • TAI Tracking Area Identifier
  • the source eNB may determine that the source eNB is connected to the source GW according to the TAI of the source eNB and the TAI of the target eNB, and the target eNB is connected to the target GW or the MME; A UE context release request message is sent to the source GW.
  • the source GW may send the UE context release request message to the MME, and receive the UE context translation sent by the MME.
  • the command message is sent, and then the source GW can release the UE context-related resource corresponding to the identifier of the UE that is switched to the target eNB that is carried in the UE context release command message, so that the UE context-related resources in the source GW can be implemented.
  • the newly-entered UE can be successfully accessed and resources are saved.
  • FIG. 6 is a flowchart of Embodiment 6 of a method for downloading context-related resources of a user equipment according to the present invention.
  • an access network node is an eNB
  • an intermediate node is a GW
  • a core network node is an MME
  • the control message is a UE context translation.
  • the request message is described as an example.
  • the user equipment context-related resource translation method may include:
  • Step 601 the source GW sends a GW identifier to the source eNB.
  • Step 602 Optionally, the source eNB exchanges GW information with the target eNB.
  • the source eNB may send the GW information of the source eNB to the target eNB, and receive the GW information of the target eNB sent by the target eNB.
  • the GW information of the source eNB may include whether the source eNB is connected to the GW.
  • the GW information of the source eNB may further include an identifier of the source GW to which the source eNB is connected.
  • the eNB may include a target eNB, and when the target eNB is connected to the GW, the GW information of the target eNB may further include the target eNB. The identity of the connected target GW.
  • Step 603 The UE switches from the source eNB to the target eNB by using the X2 handover.
  • Step 604 The target eNB sends a UE context release message to the source eNB.
  • Step 605 Optionally, the source eNB releases the UE context-related resource.
  • Step 606 optionally, the source eNB according to the GW information of the source eNB and the target eNB
  • the GW information determines that the source eNB is connected to the source GW, and the target eNB is connected to the target GW or MME.
  • Step 607 The source GW receives the UE context release request message sent by the source eNB, where the UE context release request message carries the identifier of the UE that is handed over to the target eNB.
  • Step 608 The source GW sends the foregoing UE context release request message to the MME, where the UE context release request message carries the identifier of the UE that is handed over to the target eNB.
  • Step 609 The MME sends a UE context release command message to the source GW, where the UE context translation command message carries the identifier of the UE that is handed over to the target eNB.
  • Step 610 The source GW sends the foregoing UE context release command message to the source eNB, where the UE context release command message carries the identifier of the UE that is handed over to the target eNB.
  • Step 611 Optionally, the source eNB releases the UE context-related resource corresponding to the identifier of the UE.
  • step 611 and step 605 are mutually exclusive, that is, only two of the two steps exist in any one of the implementations.
  • Step 612 The source eNB sends a UE context release completion message to the source GW, where the UE context translation command message carries the identifier of the UE that is handed over to the target eNB.
  • Step 613 The source GW releases the UE context-related resource corresponding to the identifier of the UE.
  • Step 614 the source GW sends a UE context release completion message to the MME.
  • the source eNB may determine that the source eNB is connected to the source according to the Tracking Area Identifier (hereinafter referred to as TAI) of the source GW and the target GW.
  • TAI Tracking Area Identifier
  • the target eNB On the GW, the target eNB is connected to the target GW or MME. Specifically, it may be specified that no connection is made.
  • the eNBs on the same GW cannot share the TAI, so that when the eNBs that are not connected to the same GW cannot share the TAI, the source eNB can send the TAI of the source eNB to the target eNB, and receive the TAI of the target eNB sent by the target eNB.
  • the source eNB may determine that the source eNB is connected to the source GW according to the TAI of the source eNB and the TAI of the target eNB, and the target eNB is connected to the target GW or the MME; then, the source eNB may send the UE context release to the source GW. Request message.
  • the source GW may send the UE context release request message to the MME, and receive the UE context translation sent by the MME.
  • the command message is sent, and then the source GW may send the UE context release command message to the source eNB, and receive the UE context release complete message sent by the source eNB, and then the source GW may release the handover to the target carried in the UE context release completion message.
  • the UE context-related resource corresponding to the identifier of the UE of the eNB can be implemented, so that the UE context-related resources in the source GW can be implemented, and the newly-entered UE can be successfully accessed, and resources are saved.
  • FIG. 7 is a flowchart of Embodiment 7 of a method for downloading context-related resources of a user equipment according to the present invention. As shown in FIG. 7, the method for downloading context-related resources of the user equipment may include:
  • Step 701 The intermediate node monitors transmission of data and/or signaling of the user equipment served by the intermediate node.
  • Step 702 The intermediate node releases the data of the foregoing data and/or signaling to meet the predetermined condition of the user equipment context-related resource.
  • the foregoing predetermined condition may include: at least: a pause time of transmission of data and/or signaling of the user equipment exceeds a predetermined length of time; or, the intermediate node receives an end tag data packet for the user equipment; or, a distance intermediate node The time interval at which the last time the heartbeat data block for the user equipment is received is exceeded for a predetermined time interval.
  • the intermediate node may further send a user equipment context release request message or a reset message to the core network node, and receive a user equipment context release command message or a reset confirmation message sent by the core network node.
  • the embodiment of the present invention is not limited thereto, and the intermediate node may further send any message except the user equipment context release request message and the reset message to the core network node, as long as the intermediate node can be monitored by the intermediate node.
  • the transmission of the data and/or signaling of the user equipment of the service may be performed on the context-related resource of the user equipment that meets the predetermined condition, and the embodiment of the present invention applies the intermediate node to the core network node.
  • the specific form of the sent message is not limited.
  • the core network node may be a node that provides a core network function, for example: a mobility management entity, etc.; the intermediate node may provide protocol conversion, routing, data exchange, etc. between the access network node and the core network node.
  • a network-compatible function node for example: the intermediate node may be a gateway or a DeNB; the access network node may be a node having an access function, such as a base station, etc., where the base station may include an eNB, and the eNB may be an ordinary macro base station.
  • the specific embodiments of the access network node, the intermediate node, and the core network node are not limited in this embodiment of the present invention.
  • the intermediate node may monitor the data and/or signaling transmission of the user equipment served by the intermediate node, and then release the user equipment context-related resources that meet the predetermined condition by transmitting the foregoing data and/or signaling;
  • the user equipment context-related resources in the intermediate node of the source and the source can be implemented, and the user equipment of the newly-connected network can be smoothly accessed, and resources are saved.
  • FIG. 8 is a flowchart of Embodiment 8 of a method for downloading context-related resources of a user equipment according to the present invention.
  • an access network node is an eNB
  • an intermediate node is a GW
  • a core network node is an MME
  • the method for releasing the user equipment context-related resource may include: Step 801:
  • the UE is handed over by the source eNB to the target eNB by using the X2 handover.
  • Step 802 Optionally, the target eNB sends a UE context release message to the source eNB.
  • Step 804 The source GW monitors data and/or signaling of the user equipment served by the source GW. Transmission, discovery of data and/or signaling transmission of user equipment that meets predetermined conditions.
  • the predetermined condition may be one or a combination of the following:
  • the data and/or signaling of the UE for example, the pause time of the transmission of the Tracking Area Update (TAU) signaling exceeds a predetermined length of time;
  • the source GW receives an end marker (End Marker) data packet for the UE; wherein the end marker data packet indicates that the core network does not send the data packet of the UE to the source eNB;
  • End Marker End Marker
  • Step 805 Optionally, the source GW sends a UE context release request message to the MME.
  • Step 806 Optionally, the MME sends a UE context release command message to the source GW.
  • Step 807 The source GW decodes the data and/or the signaling to transmit the user equipment context-related resources that meet the predetermined condition.
  • the source GW may also send a reset message to the MME.
  • the MME may send a reset confirmation message to the source GW in step 806.
  • the source GW may monitor the transmission of data and/or signaling of the UE served by the source GW, and then release the UE context-related resources that meet the predetermined conditions for the transmission of the foregoing data and/or signaling;
  • the UE context-related resources in the source GW are translated, and the newly-entered UE can be successfully accessed, and resources are saved.
  • FIG. 9 is a flowchart of Embodiment 9 of a method for downloading context-related resources of a user equipment according to the present invention.
  • the method for downloading context-related resources of the user equipment may include:
  • Step 901 The source access network node determines that the user equipment is handed over by the source access network node to the target access network node.
  • Step 902 The source access network node sends a control message to the source intermediate node, where the control message carries Switching to the identifier of the user equipment of the target access network node, so that the source intermediate node translates the user equipment context-related resources corresponding to the identifier of the user equipment.
  • the source access network node determines that the source access network node can access the source node before the user equipment switches to the target access network node by using the handover.
  • the intermediate node information is sent to the target access network node, and receives the intermediate node information of the target access network node sent by the target access network node; before the source access network node sends the control message to the source intermediate node, the source access network
  • the node may determine, according to the intermediate node information of the source access network node and the intermediate node information of the target access network node, that the foregoing control message needs to be sent to the source intermediate node.
  • the source access network node may send the above control message to the source intermediate node.
  • the intermediate node information of the source access network node includes whether the source access network node is connected with an intermediate node.
  • the intermediate node information of the source access network node further includes the source connection.
  • the intermediate node information of the target access network node includes whether the target access network node is connected with an intermediate node, and when the target access network node is connected with the intermediate node, the intermediate node information of the target access network node further includes the target access network.
  • the source access network node determines that the user equipment is not connected to the same intermediate node before being switched by the source access network node to the target access network node by using the handover.
  • the source access network node may send the tracking area identifier of the source access network node to the target access network node, and receive the target sent by the target access network node.
  • the tracking area identifier of the access network node before the source access network node sends the control message to the source intermediate node, the source access network node may track the tracking area identifier of the source access network node and the target access network node The area identifier determines that the above control message needs to be sent to the source intermediate node.
  • the source access network node may send the above control message to the source intermediate node.
  • the present embodiment is not limited to the foregoing two implementation manners, and the source access network node may determine whether it is necessary to send a control message to the source intermediate node by using other criteria, which is not limited in this embodiment.
  • the source access network node may send the handover to the target access network node to the source intermediate node.
  • the control message of the identifier of the user equipment so that after receiving the control message, the source intermediate node can release the user equipment context-related resource corresponding to the identifier of the user equipment; thereby realizing the user equipment context in the source node of the translation source Related resources, in turn, enable the user equipment of the new network to access smoothly and save resources.
  • the method for downloading context-related resources of the user equipment may include: Step 1001: A core network node to a source intermediate node And sending a control message, where the control message carries an identifier of the user equipment that is switched to the target access network node, so that the source intermediate node releases the user equipment context-related resource corresponding to the identifier of the user equipment.
  • Step 1002 The core network node receives a response sent by the source intermediate node for the foregoing control message.
  • the core network node may receive and save the intermediate node identifier of the intermediate node and the intermediate node corresponding to the intermediate node identifier sent by the intermediate node.
  • the intermediate node flag indicates that the node type that sends the intermediate node identifier is an intermediate node, and the intermediate node identifier uniquely identifies an intermediate node in a network; at this time, the core network node according to the source side node corresponding to the user equipment obtained in advance And the identifier of the target side node, and the correspondence between the intermediate node identifier and the intermediate node identifier, determining that the foregoing control message needs to be sent to the source intermediate node.
  • the core network node may receive the identifier of the user equipment that is sent by the target access network node and is switched to the target access network node, and receive the user equipment that is handed over to the target access network node.
  • a path switching request sent by the corresponding target side node the identifier of the user equipment is allocated by the core network node when the user equipment accesses the network, and is sent by the source access network node to the target when the X2 handover is performed.
  • the access network node is configured to perform a search according to the identifier of the user equipment, and the corresponding relationship between the identifier of the user equipment and the identifier of the source side node corresponding to the user equipment, and obtain the source side corresponding to the user equipment.
  • the identifier of the node is obtained, and the identifier of the target side node corresponding to the user equipment is obtained according to the saved correspondence between the path of receiving the path switching request and the identifier of the target side node; wherein the source side node and the target side corresponding to the user equipment
  • the node is directly connected to the core network node.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the source side node, and if the identifier of the source side node is the same, If the intermediate node identifier is used, the core network node may determine, according to the intermediate node identifier corresponding to the intermediate node identifier, that the source side node is the source intermediate node; if the intermediate node identifier that is the same as the identifier of the source side node is not found, then the identifier may be determined. The source side node is not the source intermediate node.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the target side node. If the same intermediate node identifier as the target side node is found, then The core network node may determine that the target side node is the target intermediate node according to the intermediate node identifier corresponding to the intermediate node identifier; if the intermediate node identifier that is the same as the identifier of the target side node is not found, the target side may be determined. The node is not the target intermediate node.
  • the core network node may receive and save the intermediate node identifier sent by the intermediate node and the tracking area identifier corresponding to the intermediate node identifier;
  • the node type corresponding to the set of the tracking area identifier sent by the intermediate node is an intermediate node, and the intermediate node identifier uniquely identifies an intermediate node in a network.
  • the core network node may be based on the source side node corresponding to the user equipment obtained in advance. And determining, by the identifier of the target side node, and the correspondence between the tracking area identifier and the intermediate node identifier, determining that the foregoing control message needs to be sent to the source intermediate node.
  • the core network node may receive the identifier of the user equipment that is sent by the target access network node and is switched to the target access network node, and receive the user equipment that is handed over to the target access network node.
  • a path switching request sent by the corresponding target side node the identifier of the user equipment is allocated by the core network node when the user equipment accesses the network, and is sent by the source access network node to the target when the X2 handover is performed.
  • the access network node is configured to perform a search according to the identifier of the user equipment, and the corresponding relationship between the identifier of the user equipment and the identifier of the source side node corresponding to the user equipment, and obtain the source side corresponding to the user equipment.
  • the identifier of the node is obtained, and the identifier of the target side node corresponding to the user equipment is obtained according to the saved correspondence between the path of receiving the path switching request and the identifier of the target side node; wherein the source side node and the target side corresponding to the user equipment
  • the node is directly connected to the core network node.
  • different types of nodes may be set to use different tracking area identifier sets.
  • the two types of nodes, the intermediate node and the access network node may be set to use different tracking area identifier sets.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the source side node, and if the identifier of the source side node is found, Same intermediate node identifier, then The core network node may determine, according to the node type corresponding to the set of the tracking area identifier corresponding to the intermediate node identifier, that the source side node is the source intermediate node; if the same intermediate node identifier is not found, the identifier may be determined.
  • the source side node is not the source intermediate node.
  • the core network node may perform the search in the intermediate node identifier saved by the core network node according to the identifier of the target side node. If the intermediate node identifier is the same as the identifier of the target side node, the core network node may determine the target side node as the target intermediate node according to the node type corresponding to the tracking area identifier corresponding to the intermediate node identifier; If the same intermediate node identifier as the target side node is found, it can be determined that the target side node is not the target intermediate node.
  • the core network node may send a control message to the source intermediate node.
  • the present embodiment is not limited to this, and the core network node may determine whether it is necessary to send a control message to the source intermediate node by using other manners, which is not limited in this embodiment.
  • the core network node sends a control message carrying the identifier of the user equipment that is switched to the target access network node to the source intermediate node, so that after receiving the control message, the source intermediate node can translate the user equipment.
  • the corresponding user equipment context-related resources are identified; the user equipment context-related resources in the intermediate node of the source and the source can be implemented, and the user equipment of the newly-connected network can be smoothly accessed, and resources are saved.
  • FIG. 11 is a schematic structural diagram of Embodiment 1 of an intermediate node device according to the present invention.
  • the inter-node device may implement the process of the embodiment shown in FIG. 1 of the present invention.
  • the intermediate node device may include: a first receiving module 1101 and a decoding module 1102;
  • the first receiving module 1101 is configured to receive a control message, where the control message carries an identifier of the user equipment that is switched to the target access network node device.
  • the translation module 1102 is configured to: according to the identifier of the user equipment carried in the control message received by the first receiving module 1101, the user equipment context-related resource corresponding to the identifier of the user equipment.
  • the intermediate node device in this embodiment may be a node device that provides network compatibility functions such as protocol conversion, routing, and data exchange between the access network node device and the core network node device, such as: a gateway or a DeNB, etc.; but the present invention The embodiment does not limit the specific form of the intermediate node device.
  • the control message in this embodiment may be a user equipment context release request message, a user equipment context release command message or a reset message, but the embodiment of the present invention is not limited thereto, and the specific message form of the control message in the embodiment of the present invention
  • the control message may also be any message other than the user equipment context release request message, the user equipment context release command message, and the reset message, as long as the source intermediate node can perform the handover according to the control message.
  • the corresponding user equipment context-related resources may be translated.
  • the translation module 1102 releases the user equipment context-related resource corresponding to the identifier of the user equipment;
  • the user equipment context-related resources in the source node device can be translated, and the newly-entered user equipment can be smoothly accessed, and resources are saved.
  • FIG. 12 is a schematic structural diagram of Embodiment 2 of an intermediate node device according to the present invention. Compared with the intermediate node device shown in FIG. 11, the difference is that, in an implementation manner, the intermediate node device shown in FIG.
  • the control message received by the receiving module 1101 may be a source access network node device.
  • the transmitted user equipment context deciphers the request message or resets the message.
  • the intermediate node device in this implementation manner may further include: a first sending module
  • the user equipment context release request message or the reset message that is received by the first receiving module 1101 is sent to the core network node device.
  • the first receiving module 1101 may also receive the user equipment context sent by the core network node device. Decode the command message or reset the confirmation message.
  • the first sending module 1103 may further send the received user equipment context release command message or reset confirmation message to the source access network node device; the first receiving module 1101 may further receive the source access network node device.
  • the sent user equipment context release completion message or reset confirmation message Further, the first sending module 1103 may further send the user equipment context release completion message or the reset confirmation message received by the first receiving module 1101 to the core network node device.
  • control message received by the first receiving module 1101 may be a user equipment context release command message or a reset message sent by the core network node device.
  • the intermediate node device in this implementation manner may further include: a second sending module
  • the first receiving module 1101 may further receive the source access network node device to send User device context release completion message or reset confirmation message.
  • the second sending module 1104 may further send the user equipment context release completion message or the reset confirmation message received by the first receiving module 1101 to the core network node device.
  • the foregoing intermediate node device can implement the user equipment context-related resources in the source intermediate node device, thereby enabling the newly-entered user equipment to smoothly access and saving resources.
  • FIG. 13 is a schematic structural diagram of Embodiment 1 of a source access network node device according to the present invention.
  • the source access network node device may include: a first determining module 1301 and a third sending module 1302;
  • the first determining module 1301 is configured to determine that the user equipment is handed over by the source access network node to the target access network node;
  • the third sending module 1302 is configured to: after the first determining module 1301 determines that the user equipment is handed over to the target access network node by the source access network node by using the handover, send a control message to the source intermediate node device, where the control message carries the switch to the target An identifier of the user equipment of the network node device is accessed, so that the source intermediate node device releases the user equipment context-related resource corresponding to the identifier of the user equipment.
  • the source access network node device in this embodiment may be a node device with an access function, for example, a base station, etc., where the base station may include an eNB, and the eNB may be an ordinary macro base station or some small base stations, including HeNB/HNB or RN, etc.; however, the specific form of the source access network node device is not limited in the embodiment of the present invention.
  • the control message in this embodiment may be a user equipment context release request message or a reset message, but the embodiment of the present invention is not limited thereto.
  • the specific message form of the control message is not limited in the embodiment of the present invention, and the control message may also be used.
  • the source intermediate node can perform the identifier of the user equipment that is switched to the target access network node according to the control message, the corresponding User device context-related resources are sufficient.
  • the source access network node device can implement the translation of the user equipment context related resources in the source intermediate node device, thereby enabling the newly accessed user equipment to smoothly access and saving resources.
  • FIG. 14 is a schematic structural diagram of Embodiment 2 of a source access network node device according to the present invention. Compared with the source access network node device shown in FIG. 13, the difference is that the source access network node device shown in FIG. The method may include: a second receiving module 1303;
  • the third sending module 1302 is further configured to send the intermediate node information of the source access network node device to the target access network node device, and the second receiving module 1303 is configured to receive the target connection sent by the target access network node device.
  • the first determining module 1301 may further determine, according to the intermediate node information of the source access network node device and the intermediate node information of the target access network node device received by the second receiving module 1303.
  • the third sending module 1302 is required to send a control message to the source intermediate node device.
  • the source access network node device in this embodiment may further include: a third receiving module 1304;
  • the third sending module 1302 may further send the tracking area identifier of the source access network node device to the target access network node when the access network node device that is not connected to the same intermediate node device cannot share the tracking area identifier.
  • the third receiving module 1304 can receive the tracking area identifier of the target access network node device sent by the target access network node device.
  • the first determining module 1301 can also track the source node device according to the source access network.
  • the area identifier and the tracking area identifier of the target access network node device received by the third receiving module 1304 determine that the third sending module 1302 needs to send a control message to the source intermediate node device.
  • the source access network node device can implement the translation of the user equipment context related resources in the source intermediate node device, thereby enabling the newly accessed user equipment to smoothly access and saving resources.
  • FIG. 15 is a schematic structural diagram of Embodiment 1 of a core network node device according to the present invention.
  • the core network node device may include: a fourth sending module 1501 and a fourth receiving module 1502.
  • the fourth sending module 1501 is configured to send, to the source intermediate node device, a control message, where the control message carries an identifier of the user equipment that is switched to the target access network node device, so that the source intermediate node device translates the user equipment. And identifying a corresponding user equipment context-related resource; the fourth receiving module 1502 is configured to receive a response sent by the source intermediate node device for the foregoing control message.
  • the control message in this embodiment may be a user equipment context release command message or a reset message, but the embodiment of the present invention is not limited thereto.
  • the specific message format of the control message is not limited in the embodiment of the present invention, and the control message may also be used.
  • the source intermediate node can perform the identifier of the user equipment that is switched to the target access network node according to the control message, the corresponding User device context-related resources are sufficient.
  • the core network node device in this embodiment may be a node device that provides a core network function, for example, a mobility management entity, and the like; Limited.
  • the core network node device can implement the context-related resources of the user equipment in the intermediate node device of the source, and the user equipment of the newly-connected network can be smoothly accessed, and resources are saved.
  • FIG. 16 is a schematic structural diagram of Embodiment 2 of a core network node device according to the present invention, and is different from the core network node device shown in FIG. 15 in that, in an implementation manner of this embodiment, the core shown in FIG.
  • the network node device may further include: a second determining module 1503;
  • the fourth receiving module 1502 may further receive and save an intermediate node identifier of the intermediate node device and an intermediate node identifier corresponding to the intermediate node identifier, where the intermediate node identifier indicates that the intermediate node identifier is sent.
  • the type of the node device is an intermediate node device, and the intermediate node identifier uniquely identifies an intermediate node device in a network.
  • the second determining module 1503 may determine that the fourth sending module 1501 needs to be the source according to the identifiers of the source side node device and the target side node device corresponding to the user equipment and the correspondence between the intermediate node identifier and the intermediate node identifier.
  • the intermediate node device sends a control message.
  • the core network node device shown in FIG. 16 may further include: a fifth receiving module 1504, configured to receive and save an intermediate node identifier sent by the intermediate node device and corresponding to the intermediate node identifier.
  • the tracking area identifier configured to receive and save an intermediate node identifier sent by the intermediate node device and corresponding to the intermediate node identifier.
  • the tracking area identifier ; wherein, the node device type corresponding to the set to which the tracking area identifier is sent by the intermediate node device is an intermediate node device, and the intermediate node identifier uniquely identifies an intermediate node device in a network.
  • the second determining module 1503 may further determine that the fourth sending module 1501 needs to be determined according to the identifiers of the source side node device and the target side node device corresponding to the user equipment and the correspondence between the tracking area identifier and the intermediate node identifier.
  • the source intermediate node device sends a control message.
  • the core network node device can implement the context-related resources of the user equipment in the intermediate node device of the source, and the user equipment of the newly-connected network can be smoothly accessed, and resources are saved.
  • the intermediate node device may include: a monitoring module 1701 and a resource translation module 1702;
  • the monitoring module 1701 is configured to monitor data and/or signaling transmission of the user equipment under the intermediate node device;
  • the resource translation module 1702 is configured to release the user equipment context-related resources of the foregoing data and/or signaling monitored by the monitoring module 1701 according to a predetermined condition.
  • the intermediate node device in this embodiment may be a node device that provides network compatibility functions such as protocol conversion, routing, and data exchange between the access network node device and the core network node device, such as: a gateway or a DeNB, etc.; but the present invention The embodiment does not limit the specific form of the intermediate node device.
  • the monitoring module 1701 can monitor the data and/or signaling transmission of the user equipment served by the intermediate node device, and then the resource decoding module 1702 can translate the data and/or signaling transmission to meet the predetermined schedule.
  • the user equipment context-related resources of the condition can be implemented, so that the user equipment context-related resources in the source intermediate node device can be translated, and the newly-entered user equipment can be smoothly accessed, and resources are saved.
  • FIG. 18 is a schematic structural diagram of Embodiment 4 of the intermediate node device according to the present invention.
  • the intermediate node device shown in FIG. 18 may further include: a message sending module 1703, which is different from the intermediate node device shown in FIG. Sending a user equipment context release request message or a reset message to the core network node device; specifically, the message sending module 1703 may monitor the data and/or signaling transmission of the user equipment under the intermediate node device after the monitoring module 1701
  • the release module 1702 sends a user equipment context release request message or a reset message to the core network node device before releasing the data and/or signaling transmission of the foregoing user equipment context-related resources.
  • the message receiving module 1704 is configured to receive a user equipment context release command message or a reset confirmation message sent by the core network node device.
  • the message receiving module 1704 receives the user sent by the core network node device. After the device context deciphers the command message or resets the acknowledgment message, the resource release module 1702 may release the user equipment context-related resources of the data and/or signaling that meet the predetermined conditions.
  • the message sending module 1703 may further send any message except the user equipment context release request message and the reset message to the core network node device, as long as the monitoring module 1701 can monitor the After the data and/or signaling of the user equipment served by the intermediate node is transmitted, the resource translation module 1702 may release the context-related resource of the user equipment that meets the predetermined condition by transmitting the data and/or signaling, and the present invention implements
  • the specific form of the message sent by the message sending module 1703 to the core network node is not limited.
  • the foregoing intermediate node device can implement the user equipment context-related resources in the source intermediate node device, thereby enabling the newly-entered user equipment to smoothly access and saving resources.
  • modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the embodiment, or may be correspondingly changed in one or more apparatuses different from the embodiment.
  • the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

Abstract

本发明实施例提供一种用户设备上下文相关资源的释放方法和设备,所述用户设备上下文相关资源的释放方法包括:源中间节点接收控制消息,所述控制消息携带切换到目标接入网节点的用户设备的标识;所述源中间节点释放所述用户设备的标识对应的用户设备上下文相关资源。本发明实施例可以实现释放源中间节点中的用户设备上下文相关资源,进而可以使新入网的用户设备顺利接入,并节省了资源。

Description

用户设备上下文相关资源的释放方法和设备 本申请要求于 2011 年 01 月 10 日提交中国专利局、 申请号为 201110004406.3、发明名称为 "用户设备上下文相关资源的译放方法和设备" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及无线通讯技术领域, 具体涉及一种用户设备上下文相关资 源的释放方法和设备。
背景技术 在无线通信网络中, 通常的网络架构由无线接入网和核心网组成, 无 线接入网和核心网之间通过接口进行连接。 无线接入网和接入的终端通过 无线接口连接, 为终端提供服务。
随着技术的发展, 出现了一种新的网络架构, 就是在接入网节点和核 心网节点之间引入一个中间节点。 这个中间节点在接入网节点和核心网节 点之间充当代理节点: 在核心网看来, 该中间节点在功能上是一个接入网 节点; 在接入网节点看来, 该中间节点在功能上是一个核心网节点。
以长期演进(Long Term Evolution; 以下简称: LTE ) 系统为例, LTE 系统中有些基站 ( enhanced NodeB; 以下简称: eNB ) 是通过一个网关 ( Gateway; 以下简称: GW )连接到移动性管理实体( Mobility Management Entity; 以下简称: MME )上的, 而有些 eNB是直接连接到 MME上的。 eNB和 GW, GW和 MME, 以及 eNB和 MME之间的逻辑接口相同, 均为 S1接口; eNB之间可能存在直连的逻辑接口, 称为 X2接口。 与 S1接口相 比, 用户设备 ( User Equipment; 以下简称: UE )可以通过 X2接口更快地 从源 eNB切换到目标 eNB, 通过 X2接口完成的切换称为 X2切换。
上述 eNB可以是普通的宏基站, 也可以是一些小型基站, 包括家庭基 站( Home enhanced NodeB; 以下简称: HeNB/Home NodeB; 以下简称: HNB )或中继站(Relay Node; 以下简称: RN )等等。
根据源 eNB和目标 eNB的拓朴关系, X2切换可以分为以下五种情况: ( 1 ) 源 eNB和目标 eNB连接在同一个 GW上;
( 2 ) 源 eNB连接在 GW上, 目标 eNB连接在 MME上;
( 3 ) 源 eNB连接在 MME上, 目标 eNB连接在 GW上;
( 4 ) 源 eNB连接在一个 GW上, 目标 eNB连接在另外一个 GW上; ( 5 ) 源 eNB和目标 eNB都连接在 MME上。
现有技术中, 无论上述哪种情况, X2切换后目标 eNB会通过 X2接口向 源 eNB发送一条 UE上下文译放消息, 源 eNB在接收到该 UE上下文释放消息 后会译放已切换到目标 eNB的 UE的上下文相关资源, 该上下文相关资源包 括源 eNB在用户面和控制面所有用于该 UE的资源。
但是, 与情况( 1 )、 ( 3 )和( 5 )相比, 情况( 2 )和( 4 ) 中源 GW也 具有已切换到目的 eNB的 UE的上下文相关资源, 若采用现有技术提供的 译放 UE上下文的方案, 则在 X2切换之中和之后, 源 GW不会觉察到 UE 已经离开该源 GW的管辖范围, 这会导致源 GW上的 UE上下文相关资源 不能译放,该上下文相关资源包括源 GW在用户面和控制面所有用于该 UE 的资源, 这会导致新入网的 UE不能顺利接入和资源枯竭。
发明内容 本发明实施例提供一种用户设备上下文相关资源的译放方法和设备, 以实现译放源中间节点中的用户设备上下文相关资源。
本发明实施例提供一种用户设备上下文相关资源的译放方法, 包括: 源中间节点接收控制消息 , 所述控制消息携带切换到目标接入网节点 的用户设备的标识; 所述源中间节点译放所述用户设备的标识对应的用户设备上下文相关 资源。
本发明实施例还提供一种用户设备上下文相关资源的译放方法, 包括: 源接入网节点确定用户设备由所述源接入网节点切换到目标接入网节 点;
所述源接入网节点向源中间节点发送控制消息, 所述控制消息携带切 换到所述目标接入网节点的用户设备的标识, 以使所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源。
本发明实施例还提供一种用户设备上下文相关资源的译放方法, 包括: 核心网节点向源中间节点发送控制消息, 所述控制消息携带切换到目 标接入网节点的用户设备的标识, 以使所述源中间节点译放所述用户设备 的标识对应的用户设备上下文相关资源;
所述核心网节点接收所述源中间节点发送的针对所述控制消息的响 应。
本发明实施例还提供一种用户设备上下文相关资源的译放方法, 包括: 中间节点监测所述中间节点所服务的用户设备的数据和 /或信令的传 输;
所述中间节点译放所述数据和 /或信令的传输符合预定条件的用户设备 上下文相关资源。
本发明实施例还提供一种中间节点设备, 包括:
第一接收模块 , 用于接收控制消息 , 所述控制消息携带切换到目标接 入网节点设备的用户设备的标识;
译放模块, 用于根据所述第一接收模块接收的控制消息所携带的用户 设备的标识, 译放所述用户设备的标识对应的用户设备上下文相关资源。
本发明实施例还提供一种源接入网节点设备, 包括:
第一确定模块, 用于确定用户设备由所述源接入网节点切换到目标接 入网节点;
第三发送模块, 用于在所述第一确定模块确定用户设备通过切换由所 述源接入网节点切换到目标接入网节点之后, 向所述源中间节点设备发送 控制消息, 所述控制消息携带切换到所述目标接入网节点设备的用户设备 的标识, 以使所述源中间节点设备译放所述用户设备的标识对应的用户设 备上下文相关资源。
本发明实施例还提供一种核心网节点设备, 包括:
第四发送模块 , 用于向源中间节点设备发送控制消息 , 所述控制消息 携带切换到目标接入网节点设备的用户设备的标识, 以使所述源中间节点 设备译放所述用户设备的标识对应的用户设备上下文相关资源;
第四接收模块, 用于接收所述源中间节点设备发送的针对所述控制消 息的响应。
本发明实施例还提供一种中间节点设备, 包括:
监测模块,用于监测中间节点设备下用户设备的数据和 /或信令的传输; 资源释放模块, 用于释放所述监测模块监测到的数据和 /或信令的传输 符合预定条件的用户设备上下文相关资源。
通过本发明实施例, 源中间节点接收到携带切换到目标接入网节点的用户 设备的标识的控制消息之后, 译放该用户设备的标识对应的用户设备上下 文相关资源; 从而可以实现译放源中间节点中的用户设备上下文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对 实施例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见地, 下面描述中的附图是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。 图 1为本发明用户设备上下文相关资源的译放方法实施例一的流程图; 图 2为本发明用户设备上下文相关资源的译放方法实施例二的流程图; 图 3为本发明用户设备上下文相关资源的译放方法实施例三的流程图; 图 4为本发明用户设备上下文相关资源的译放方法实施例四的流程图; 图 5为本发明用户设备上下文相关资源的译放方法实施例五的流程图; 图 6为本发明用户设备上下文相关资源的译放方法实施例六的流程图; 图 7为本发明用户设备上下文相关资源的译放方法实施例七的流程图; 图 8为本发明用户设备上下文相关资源的译放方法实施例八的流程图; 图 9为本发明用户设备上下文相关资源的译放方法实施例九的流程图; 图 10 为本发明用户设备上下文相关资源的译放方法实施例十的流程 图;
图 11为本发明中间节点设备实施例一的结构示意图;
图 12为本发明中间节点设备实施例二的结构示意图;
图 13为本发明源接入网节点设备实施例一的结构示意图;
图 14为本发明源接入网节点设备实施例二的结构示意图;
图 15为本发明核心网节点设备实施例一的结构示意图;
图 16为本发明核心网节点设备实施例二的结构示意图;
图 17为本发明中间节点设备实施例三的结构示意图;
图 18为本发明中间节点设备实施例四的结构示意图。
具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本 发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描 述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创造性劳动的前 提下所获得的所有其他实施例, 都属于本发明保护的范围。
图 1为本发明用户设备上下文相关资源的译放方法实施例一的流程图, 如图 1所示, 该用户设备上下文相关资源的译放方法可以包括:
步骤 101 , 源中间节点接收控制消息, 该控制消息携带切换到目标接入 网节点的用户设备的标识。
步骤 102,源中间节点译放上述用户设备的标识对应的用户设备上下文 相关资源。
在本实施例的一种实现方式中, 该控制消息可以为用户设备上下文释 放请求消息或重置消息, 则接收控制消息可以为源中间节点接收源接入网 节点发送的用户设备上下文译放请求消息或重置消息。
可选地, 该用户设备上下文译放请求消息或重置消息中可以携带终结 标识, 该用户设备上下文译放请求消息或重置消息中的终结标识表示源中 间节点无需再将该用户设备上下文译放请求消息发送给核心网节点。
进一步地, 在译放上述用户设备的标识对应的用户设备上下文相关资 源之前, 源中间节点还可以将接收的用户设备上下文译放请求消息或重置 消息发送给核心网节点, 然后接收该核心网节点发送的用户设备上下文释 放命令消息或重置确认消息。
进一步地, 在接收核心网节点发送的用户设备上下文译放命令消息之 后, 译放上述用户设备的标识对应的用户设备上下文相关资源之前, 源中 间节点还可以将接收到的用户设备上下文译放命令消息或重置确认消息发 送给源接入网节点; 然后, 该源中间节点可以接收源接入网节点发送的用 户设备上下文译放完成消息或重置确认消息。
进一步地, 在译放上述用户设备的标识对应的用户设备上下文相关资 源之后, 源中间节点还可以将接收到的用户设备上下文译放完成消息或重 置确认消息发送给上述核心网节点。
本实现方式中, 源中间节点接收用户设备上下文译放请求消息或重置 消息之前, 源接入网节点还可将该源接入网节点的中间节点信息发送给目 标接入网节点, 并接收目标接入网节点发送的该目标接入网节点的中间节 点信息; 然后, 该源接入网接点可以根据该源接入网节点的中间节点信息 与该目标接入网节点的中间节点信息, 确定源接入网节点连接在源中间节 点上, 目标接入网节点连接在目标中间节点或核心网节点上; 接下来, 源 接入网节点可以向源中间节点发送上述用户设备上下文译放请求消息或重 置消息。
其中, 上述源接入网节点的中间节点信息可以包括该源接入网节点是 否连接有中间节点, 当该源接入网节点连接有中间节点时, 该源接入网节 点的中间节点信息还可以包括该源接入网节点连接的源中间节点的标识; 该源中间节点的标识可以是在源接入网节点将该源接入网节点的中间节点 信息发送给目标接入网节点之前, 由源中间节点发送给源接入网节点的; 上述目标接入网节点的中间节点信息可以包括该目标接入网节点是否 连接有中间节点, 当该目标接入网节点连接有中间节点时, 该目标接入网 节点的中间节点信息还可以包括目标接入网节点连接的目标中间节点的标 识; 该目标中间节点的标识可以是在目标接入网节点将该目标接入网节点 的中间节点信息发送给源接入网节点之前, 由目标中间节点发送给目标接 入网节点的。
另外, 本实现方式中, 当不连接在同一中间节点上的接入网节点不能 共享跟踪区域标识时, 在源中间节点接收用户设备上下文译放请求消息或 重置消息之前, 源接入网节点也可以将该源接入网节点的跟踪区域标识发 送给目标接入网节点, 并接收该目标接入网节点发送的该目标接入网节点 的跟踪区域标识; 然后, 源接入网节点可以根据源接入网节点的跟踪区域 标识与目标接入网节点的跟踪区域标识, 确定源接入网节点连接在源中间 节点上, 目标接入网节点连接在目标中间节点或核心网节点上; 接下来, 源接入网节点可以向源中间节点发送上述用户设备上下文译放请求消息或 重置消息。
本实施例的另一种实现方式中, 该控制消息可以为用户设备上下文释 放命令消息或重置消息; 则接收控制消息可以为: 源中间节点接收核心网 节点发送的用户设备上下文译放命令消息或重置消息。
可选地, 该用户设备上下文译放命令消息或重置消息中可以携带终结 标识, 该用户设备上下文译放命令消息或重置消息中的终结标识表示源中 间节点无需再将该用户设备上下文译放命令消息发送给源接入网节点。
进一步地, 在译放上述用户设备的标识对应的用户设备上下文相关资 源之前, 源中间节点还可以将接收的用户设备上下文译放命令消息或重置 消息发送给源接入网节点; 然后, 源中间节点可以接收源接入网节点发送 的用户设备上下文译放完成消息或重置确认消息。
进一步地, 译放上述用户设备的标识对应的用户设备上下文相关资源 之后, 源中间节点还可以将接收的用户设备上下文译放完成消息或重置确 认消息发送给上述核心网节点。
本实现方式中, 核心网节点可以接收并保存中间节点发送的该中间节 点的中间节点标识和该中间节点标识对应的中间节点标志, 该中间节点标 志可以标示发送该中间节点标志的节点类型为中间节点, 上述中间节点标 识在一个网络中唯一标识一个中间节点。 其中, 该中间节点标识可以为数 字、 字母或字符串等可以唯一标识一个中间节点的标识, 本发明实施例对 中间节点标识的具体形式不作限定; 同样, 该中间节点标志也可以为数字、 字母或字符串等可以标示发送该中间节点标志的节点类型的标志, 本发明 实施例对中间节点标志的具体形式不作限定。
这时, 该核心网节点可以根据预先获得的用户设备对应的源侧节点和 目标侧节点的标识, 以及中间节点标志与中间节点标识的对应关系, 确定 源侧节点是否为源中间节点, 目标侧节点是否为目标中间节点; 当源侧节 点为源中间节点, 目标侧节点为目标中间节点, 且上述源侧节点的标识与 上述目标侧节点的标识不同时, 或者当源侧节点为源中间节点, 目标侧节 点不是目标中间节点时, 核心网节点可以向源中间节点发送上述用户设备 上下文译放命令消息或重置消息。
具体地, 在源中间节点接收用户设备上下文译放命令消息或重置消息 之前, 核心网节点可以接收目标接入网节点发送的切换到目标接入网节点 的用户设备的标识, 以及接收切换到目标接入网节点的用户设备对应的目 标侧节点发送的路径切换请求; 上述用户设备的标识由核心网节点在该用 户设备接入网络时为该用户设备分配, 并在进行 X2切换时, 由源接入网节 点发送给目标接入网节点; 然后, 该核心网节点根据上述用户设备的标识, 在保存的用户设备的标识与用户设备对应的源侧节点的标识的对应关系中 进行查找, 获得该用户设备对应的源侧节点的标识; 并根据保存的接收上 述路径切换请求的路径与目标侧节点的标识的对应关系, 获得上述用户设 备对应的目标侧节点的标识; 其中, 上述用户设备对应的源侧节点和目标 侧节点与核心网节点直接连接。
获得用户设备对应的源侧节点的标识之后, 核心网节点可以根据该源 侧节点的标识, 在该核心网节点保存的中间节点标识中进行查找, 若查找 到与该源侧节点的标识相同的中间节点标识, 则该核心网节点可以根据该 中间节点标识对应的中间节点标志, 确定源侧节点为源中间节点; 若未查 找到与该源侧节点的标识相同的中间节点标识, 则可以确定该源侧节点不 是源中间节点; 同理, 获得用户设备对应的目标侧节点的标识之后, 核心 网节点可以根据该目标侧节点的标识, 在该核心网节点保存的中间节点标 识中进行查找, 若查找到与该目标侧节点的标识相同的中间节点标识, 则 该核心网节点可以才艮据该中间节点标识对应的中间节点标志 , 确定目标侧 节点为目标中间节点; 若未查找到与该目标侧节点的标识相同的中间节点 标识, 则可以确定该目标侧节点不是目标中间节点。
这样, 当源侧节点为源中间节点, 目标侧节点为目标中间节点, 且上 述源侧节点的标识与上述目标侧节点的标识不同时, 或者当源侧节点为源 中间节点, 目标侧节点不是目标中间节点时, 核心网节点可以向源中间节 点发送上述用户设备上下文译放命令消息或重置消息。
另外, 该核心网节点也可以接收并保存中间节点发送的中间节点标识 和该中间节点标识对应的跟踪区域标识; 其中, 该中间节点发送的跟踪区 域标识所属的集合对应的节点类型为中间节点, 该中间节点标识在一个网 络中唯一标识一个中间节点; 然后, 该核心网节点可以根据预先获得的用 户设备对应的源侧节点和目标侧节点的标识, 以及跟踪区域标识和中间节 点标识的对应关系, 确定源侧节点是否为源中间节点, 目标侧节点是否为 目标中间节点; 当源侧节点为源中间节点, 目标侧节点为目标中间节点, 且源侧节点的标识与目标侧节点的标识不同时, 或者当源侧节点为源中间 节点, 目标侧节点不是目标中间节点时, 该核心网节点可以向源中间节点 设备发送用户设备上下文译放命令消息或重置消息。
具体地, 在源中间节点接收用户设备上下文译放命令消息或重置消息 之前, 核心网节点可以接收目标接入网节点发送的切换到目标接入网节点 的用户设备的标识, 以及接收切换到目标接入网节点的用户设备对应的目 标侧节点发送的路径切换请求; 上述用户设备的标识由核心网节点在该用 户设备接入网络时为该用户设备分配, 并在进行 X2切换时, 由源接入网节 点发送给目标接入网节点; 然后, 该核心网节点根据上述用户设备的标识, 在保存的用户设备的标识与用户设备对应的源侧节点的标识的对应关系中 进行查找, 获得该用户设备对应的源侧节点的标识; 并根据保存的接收上 述路径切换请求的路径与目标侧节点的标识的对应关系, 获得上述用户设 备对应的目标侧节点的标识; 其中, 上述用户设备对应的源侧节点和目标 侧节点与核心网节点直接连接。
本实现方式中, 可以设定不同类型的节点使用不同的跟踪区域标识集 合, 例如: 可以设定中间节点和接入网节点这两种类型的节点使用不同的 跟踪区域标识集合。 这样, 获得用户设备对应的源侧节点的标识之后, 核 心网节点可以根据该源侧节点的标识, 在该核心网节点保存的中间节点标 识中进行查找, 若查找到与该源侧节点的标识相同的中间节点标识, 则该 核心网节点可以根据该中间节点标识对应的跟踪区域标识所属集合对应的 节点类型, 确定源侧节点为源中间节点; 若未查找到与该源侧节点的标识 相同的中间节点标识, 则可以确定该源侧节点不是源中间节点; 同理, 获 得用户设备对应的目标侧节点的标识之后, 核心网节点可以根据该目标侧 节点的标识, 在该核心网节点保存的中间节点标识中进行查找, 若查找到 与该目标侧节点的标识相同的中间节点标识, 则该核心网节点可以根据该 中间节点标识对应的跟踪区域标识所属集合对应的节点类型, 确定目标侧 节点为目标中间节点; 若未查找到与该目标侧节点的标识相同的中间节点 标识, 则可以确定该目标侧节点不是目标中间节点。
这样, 当源侧节点为源中间节点, 目标侧节点为目标中间节点, 且上 述源侧节点的标识与上述目标侧节点的标识不同时, 或者当源侧节点为源 中间节点, 目标侧节点不是目标中间节点时, 核心网节点可以向源中间节 点发送上述用户设备上下文译放命令消息或重置消息。
本实施例中, 接入网节点可以为具有接入功能的节点, 例如: 基站等, 其中该基站可以包括 eNB, 该 eNB可以为普通的宏基站, 也可以是一些小 型基站, 包括 HeNB/ HNB或 RN等等; 核心网节点可以为提供核心网功能 的节点, 例如: 移动性管理实体等; 中间节点可以为在接入网节点与核心 网节点之间提供协议转换、 路由选择、 数据交换等网络兼容功能的节点, 例如: 网关或施主基站 (Donor eNB; 以下简称: DeNB )等; 但本发明实 施例对接入网节点、 中间节点和核心网节点的具体形式不作限定。
本实施例以控制消息为用户设备上下文译放请求消息、 用户设备上下 文译放命令消息或重置消息为例进行说明; 但本发明实施例并不仅限于此, 本发明实施例对控制消息的具体消息形式不作限定, 该控制消息也可以为 除用户设备上下文译放请求消息、 用户设备上下文译放命令消息和重置消 息之外的任意一种消息, 只要可以实现源中间节点根据该控制消息携带的 切换到目标接入网节点的用户设备的标识, 译放相应的用户设备上下文相 关资源即可。
上述实施例中, 源中间节点接收到携带切换到目标接入网节点的用户 设备的标识的控制消息之后, 译放该用户设备的标识对应的用户设备上下 文相关资源; 从而可以实现译放源中间节点中的用户设备上下文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 2为本发明用户设备上下文相关资源的译放方法实施例二的流程图 , 本实施例以接入网节点为 eNB , 中间节点为 GW , 核心网节点为 MME , 控 制消息为 UE上下文译放请求消息为例进行说明。如图 2所示,该用户设备 上下文相关资源的译放方法可以包括:
步骤 201 , 可选地, 源 GW向源 eNB发送 GW标识。
步骤 202, 可选地, 源 eNB与目标 eNB交换 GW信息。
具体地, 源 eNB可以将该源 eNB的 GW信息发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 GW信息;
其中, 源 eNB的 GW信息可以包括该源 eNB是否连接有 GW, 当该源 eNB连接有 GW时, 该源 eNB的 GW信息还可以包括该源 eNB连接的源 GW的标识; 目标 eNB的 GW信息可以包括该目标 eNB是否连接有 GW , 当该目标 eNB连接有 GW时,该目标 eNB的 GW信息还可以包括目标 eNB 连接的目标 GW的标识。
步骤 203 , UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 204 , 目标 eNB向源 eNB发送 UE上下文译放消息。
步骤 205 , 源 eNB译放 UE上下文相关资源。
步骤 206, 可选地, 源 eNB根据该源 eNB的 GW信息与目标 eNB的 GW信息,确定源 eNB连接在源 GW上,目标 eNB连接在目标 GW或 MME 上。
步骤 207, 源 GW接收源 eNB发送的 UE上下文译放请求消息, 该 UE 上下文译放请求消息携带切换到目标 eNB的 UE的标识。
可选地,该 UE上下文译放请求消息中还可以携带一个终结标识,该终 结标识表示源 GW无需再将该 UE上下文译放请求消息发送给 MME。
步骤 208 , 源 GW译放该 UE的标识对应的 UE上下文相关资源。
另夕卜, 本实施例中, 源 eNB也可以根据源 GW和目标 GW的跟踪区域 标识(Tracking Area Identifier; 以下简称: TAI ) , 确定源 eNB连接在源 GW上, 目标 eNB连接在目标 GW或 MME上。 具体地, 可以规定不连接 在同一 GW上的 eNB不能共享 TAI, 这样当不连接在同一 GW上的 eNB 不能共享 TAI时, 源 eNB可以将该源 eNB的 TAI发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 TAI; 然后, 源 eNB可以根据该源 eNB 的 TAI与该目标 eNB的 TAI, 确定源 eNB连接在源 GW上, 目标 eNB连 接在目标 GW或 MME上; 于是, 源 eNB可以向源 GW发送 UE上下文释 放请求消息。
上述实施例中, 在接收到源 eNB发送的携带切换到目标 eNB的 UE的 标识的 UE上下文释放请求消息之后,源 GW可以译放该 UE的标识对应的 UE上下文相关资源; 从而可以实现译放源 GW中的 UE上下文相关资源, 进而可以使新入网的 UE顺利接入, 并节省了资源。
图 3为本发明用户设备上下文相关资源的译放方法实施例三的流程图, 本实施例以接入网节点为 eNB , 中间节点为 GW , 核心网节点为 MME , 控 制消息为 UE上下文译放命令消息为例进行说明。如图 3所示,该用户设备 上下文相关资源的译放方法可以包括:
步骤 301 , 可选地, 源 GW向 MME发送 GW标识和该 GW标识对应 的 GW标志; 其中, 该 GW标志可以标示发送该 GW标志的节点类型为 GW; GW标识在一个网络中唯一标识一个 GW。 其中, 该 GW标识可以为 数字、字母或字符串等可以唯一标识一个 GW的标识,本发明实施例对 GW 标识的具体形式不作限定; 同样, 该 GW标志也可以为数字、 字母或字符 串等可以标示发送该 GW标志的节点类型的标志, 本发明实施例对 GW标 志的具体形式不作限定。
步骤 302, UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 303 , 目标 eNB向 MME发送路径切换请求消息。
步骤 304, MME向目标 eNB发送路径切换响应消息。
步骤 305 , 目标 eNB向源 eNB发送 UE上下文译放消息。
步骤 306 , 源 eNB译放 UE上下文相关资源。
步骤 307, 可选地, MME根据预先获得的 UE对应的源侧节点和目标 侧节点的标识, 以及上述 GW标志与 GW标识的对应关系, 确定源侧节点 是否为源 GW, 目标侧节点是否为目标 GW。
具体地, MME可以接收目标 eNB发送的切换到目标 eNB的 UE的标 识, 以及接收切换到目标 eNB的 UE对应的目标侧节点发送的路径切换请 求; 上述 UE的标识由 MME在该 UE接入网络时为该 UE分配, 并在进行 X2切换时 , 由源 eNB发送给目标 eNB; 然后 , 该 MME可以根据上述 UE 的标识,在保存的 UE的标识与该 UE对应的源侧节点的标识的对应关系中 进行查找,获得该 UE对应的源侧节点的标识; 并根据保存的接收上述路径 切换请求的路径与目标侧节点的标识的对应关系,获得上述 UE对应的目标 侧节点的标识; 其中, 上述 UE对应的源侧节点和目标侧节点与 MME直接 连接。
获得 UE对应的源侧节点的标识之后 , MME可以根据该源侧节点的标 识, 在该 MME保存的 GW标识中进行查找, 若查找到与该源侧节点的标 识相同的 GW标识, 则该 MME可以根据该 GW标识对应的 GW标志, 确 定源侧节点为源 GW; 若未查找到与该源侧节点的标识相同的 GW标识, 则可以确定该源侧节点不是源 GW; 同理, 获得 UE对应的目标侧节点的标 识之后, ΜΜΕ可以根据该目标侧节点的标识, 在该 ΜΜΕ保存的 GW标识 中进行查找,若查找到与该目标侧节点的标识相同的 GW标识, 则该 ΜΜΕ 可以根据该 GW标识对应的 GW标志, 确定目标侧节点为目标 GW; 若未 查找到与该目标侧节点的标识相同的 GW标识, 则可以确定该目标侧节点 不是目标 GW。
本实施例中,步骤 307在步骤 303之后执行即可;步骤 307与步骤 304、 步骤 305或步骤 306可以先后执行, 也可以并行执行, 本实施例对此不作 限定。
步骤 308 , MME向源 GW发送 UE上下文释放命令消息 , 该 UE上下 文译放命令消息携带切换到目标 eNB的 UE的标识。
具体地 , MME可以当源侧节点为源 GW , 目标侧节点为目标 GW , 且 源侧节点的标识与目标侧节点的标识不同时, 或者当源侧节点为源 GW , 目标侧节点不是目标 GW时,向源 GW发送上述 UE上下文译放命令消息。
可选地,该 UE上下文译放命令消息中还可以携带一个终结标识,该终 结标识表示源 GW无需再将该 UE上下文译放命令消息发送给源 eNB。
步骤 309, 源 GW译放该 UE的标识对应的 UE上下文相关资源。
另夕卜,本实施例中 , MME也可以根据 TAI确定源侧节点是否为源 GW, 目标侧节点是否为目标 GW; 具体地, 可以设定不同类型的节点使用不同 的 TAI集合,在源 GW接收 UE上下文译放命令消息之前, MME可以接收 目标 eNB发送的切换到目标 eNB的 UE的标识, 以及接收切换到目标 eNB 的 UE对应的目标侧节点发送的路径切换请求; 上述 UE的标识由 MME在 该 UE接入网络时为该 UE分配, 并在进行 X2切换时, 由源 eNB发送给目 标 eNB; 然后 , 该 MME根据上述 UE的标识, 在保存的 UE的标识与 UE 对应的源侧节点的标识的对应关系中进行查找,获得该 UE对应的源侧节点 的标识; 并根据保存的接收上述路径切换请求的路径与目标侧节点的标识 的对应关系, 获得上述 UE对应的目标侧节点的标识; 其中, 上述 UE对应 的源侧节点和目标侧节点与 MME直接连接。
由于不同类型的节点使用不同的 TAI集合,例如:可以设定 GW和 eNB 这两种类型的节点使用不同的 TAI集合。 这样, 获得 UE对应的源侧节点 的标识之后 , MME可以根据该源侧节点的标识 , 在该 MME保存的 GW标 识中进行查找, 若查找到与该源侧节点的标识相同的 GW标识, 则该 MME 可以根据该 GW标识对应的 TAI所属集合对应的节点类型, 确定源侧节点 为源 GW; 若未查找到与该源侧节点的标识相同的 GW标识, 则可以确定 该源侧节点不是源 GW; 同理, 获得 UE对应的目标侧节点的标识之后, MME可以根据该目标侧节点的标识,在该 MME保存的 GW标识中进行查 找, 若查找到与该目标侧节点的标识相同的 GW标识, 则该 MME可以根 据该 GW标识对应的 TAI所属集合对应的节点类型, 确定目标侧节点为目 标 GW; 若未查找到与该目标侧节点的标识相同的 GW标识, 则可以确定 该目标侧节点不是目标 GW。
上述实施例中, 在接收到 MME发送的携带切换到目标 eNB的 UE的 标识的 UE上下文释放命令消息之后,源 GW可以译放该 UE的标识对应的 UE上下文相关资源; 从而可以实现译放源 GW中的 UE上下文相关资源, 进而可以使新入网的 UE顺利接入, 并节省了资源。
图 4为本发明用户设备上下文相关资源的译放方法实施例四的流程图 , 本实施例以接入网节点为 eNB , 中间节点为 GW , 核心网节点为 MME , 控 制消息为 UE上下文译放命令消息为例进行说明。如图 4所示,该用户设备 上下文相关资源的译放方法可以包括:
步骤 401 , 可选地, 源 GW向 MME发送 GW标识和该 GW标识对应 的 GW标志; 其中, 该 GW标志可以标示发送该 GW标志的节点类型为 GW; GW标识在一个网络中唯一标识一个 GW。 其中, 该 GW标识可以为 数字、字母或字符串等可以唯一标识一个 GW的标识,本发明实施例对 GW 标识的具体形式不作限定; 同样, 该 GW标志也可以为数字、 字母或字符 串等可以标示发送该 GW标志的节点类型的标志, 本发明实施例对 GW标 志的具体形式不作限定。
步骤 402, UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 403 , 目标 eNB向 MME发送路径切换请求消息。
步骤 404, MME向目标 eNB发送路径切换响应消息。
步骤 405 , 可选地, 目标 eNB向源 eNB发送 UE上下文译放消息。 步骤 406, 可选地, 源 eNB译放 UE上下文相关资源。
步骤 407 , 可选地, MME根据预先获得的 UE对应的源侧节点和目标 侧节点的标识, 以及上述 GW标志与 GW标识的对应关系, 确定源侧节点 是否为源 GW, 目标侧节点是否为目标 GW。
具体地, MME可以接收目标 eNB发送的切换到目标 eNB的 UE的标 识, 以及接收切换到目标 eNB的 UE对应的目标侧节点发送的路径切换请 求; 上述 UE的标识由 MME在该 UE接入网络时为该 UE分配, 并在进行 X2切换时 , 由源 eNB发送给目标 eNB; 然后 , 该 MME可以根据上述 UE 的标识,在保存的 UE的标识与该 UE对应的源侧节点的标识的对应关系中 进行查找,获得该 UE对应的源侧节点的标识; 并根据保存的接收上述路径 切换请求的路径与目标侧节点的标识的对应关系,获得上述 UE对应的目标 侧节点的标识; 其中, 上述 UE对应的源侧节点和目标侧节点与 MME直接 连接。
获得 UE对应的源侧节点的标识之后 , MME可以根据该源侧节点的标 识, 在该 MME保存的 GW标识中进行查找, 若查找到与该源侧节点的标 识相同的 GW标识, 则该 MME可以根据该 GW标识对应的 GW标志, 确 定源侧节点为源 GW; 若未查找到与该源侧节点的标识相同的 GW标识, 则可以确定该源侧节点不是源 GW; 同理, 获得 UE对应的目标侧节点的标 识之后 , MME可以根据该目标侧节点的标识, 在该 MME保存的 GW标识 中进行查找,若查找到与该目标侧节点的标识相同的 GW标识, 则该 MME 可以根据该 GW标识对应的 GW标志, 确定目标侧节点为目标 GW; 若未 查找到与该目标侧节点的标识相同的 GW标识, 则可以确定该目标侧节点 不是目标 GW。
本实施例中,步骤 407在步骤 403之后执行即可;步骤 407与步骤 404、 步骤 405或步骤 406可以先后执行, 也可以并行执行, 本实施例对此不作 限定。
步骤 408 , MME向源 GW发送 UE上下文释放命令消息 , 该 UE上下 文译放命令消息携带切换到目标 eNB的 UE的标识。
具体地 , MME可以当源侧节点为源 GW , 目标侧节点为目标 GW , 且 源侧节点的标识与目标侧节点的标识不同时, 或者当源侧节点为源 GW , 目标侧节点不是目标 GW时,向源 GW发送上述 UE上下文译放命令消息。
步骤 409, 源 GW将上述 UE上下文释放命令消息发送给源 eNB, 该 UE上下文译放命令消息携带切换到目标 eNB的 UE的标识。
步骤 410, 可选地, 源 eNB释放该 UE的标识对应的 UE上下文相关资 源。
本实施例中, 步骤 410和步骤 406互斥, 即这两个步骤在任一个实现 中只存在其一即可。
步骤 411 , 源 eNB向源 GW发送 UE上下文译放完成消息, 该 UE上 下文译放完成消息携带切换到目标 eNB的 UE的标识。
步骤 412 , 源 GW译放该 UE的标识对应的 UE上下文相关资源。
步骤 413 , 可选地, 源 GW向 MME发送 UE上下文译放完成消息。 另夕卜,本实施例中 , MME也可以根据 TAI确定源侧节点是否为源 GW, 目标侧节点是否为目标 GW; 具体地, 可以设定不同类型的节点使用不同 的 TAI集合,在源 GW接收 UE上下文译放命令消息之前, MME可以接收 目标 eNB发送的切换到目标 eNB的 UE的标识, 以及接收切换到目标 eNB 的 UE对应的目标侧节点发送的路径切换请求; 上述 UE的标识由 MME在 该 UE接入网络时为该 UE分配, 并在进行 X2切换时, 由源 eNB发送给目 标 eNB; 然后 , 该 MME根据上述 UE的标识, 在保存的 UE的标识与 UE 对应的源侧节点的标识的对应关系中进行查找,获得该 UE对应的源侧节点 的标识; 并根据保存的接收上述路径切换请求的路径与目标侧节点的标识 的对应关系, 获得上述 UE对应的目标侧节点的标识; 其中, 上述 UE对应 的源侧节点和目标侧节点与 MME直接连接。
由于不同类型的节点使用不同的 TAI集合,例如:可以设定 GW和 eNB 这两种类型的节点使用不同的 TAI集合。 这样, 获得 UE对应的源侧节点 的标识之后 , MME可以根据该源侧节点的标识 , 在该 MME保存的 GW标 识中进行查找, 若查找到与该源侧节点的标识相同的 GW标识, 则该 MME 可以根据该 GW标识对应的 TAI所属集合对应的节点类型, 确定源侧节点 为源 GW; 若未查找到与该源侧节点的标识相同的 GW标识, 则可以确定 该源侧节点不是源 GW; 同理, 获得 UE对应的目标侧节点的标识之后, MME可以根据该目标侧节点的标识,在该 MME保存的 GW标识中进行查 找, 若查找到与该目标侧节点的标识相同的 GW标识, 则该 MME可以根 据该 GW标识对应的 TAI所属集合对应的节点类型, 确定目标侧节点为目 标 GW; 若未查找到与该目标侧节点的标识相同的 GW标识, 则可以确定 该目标侧节点不是目标 GW。
上述实施例中, 在接收到 MME发送的携带切换到目标 eNB的 UE的 标识的 UE上下文释放命令消息之后,源 GW可以将该 UE上下文释放命令 消息发送给源 eNB, 然后源 GW可以接收源 eNB发送的 UE上下文译放完 成消息, 然后源 GW可以译放 UE上下文译放完成消息中携带的切换到目 标 eNB的 UE的标识对应的 UE上下文相关资源;从而可以实现释放源 GW 中的 UE上下文相关资源, 进而可以使新入网的 UE顺利接入, 并节省了资 源。
图 5为本发明用户设备上下文相关资源的译放方法实施例五的流程图, 本实施例以接入网节点为 eNB , 中间节点为 GW , 核心网节点为 MME , 控 制消息为 UE上下文译放请求消息为例进行说明。如图 5所示,该用户设备 上下文相关资源的译放方法可以包括:
步骤 501 , 可选地, 源 GW向源 eNB发送 GW标识。
步骤 502, 可选地, 源 eNB与目标 eNB交换 GW信息。
具体地, 源 eNB可以将该源 eNB的 GW信息发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 GW信息;
其中, 源 eNB的 GW信息可以包括该源 eNB是否连接有 GW, 当该源 eNB连接有 GW时, 该源 eNB的 GW信息还可以包括该源 eNB连接的源 GW的标识; 目标 eNB的 GW信息可以包括该目标 eNB是否连接有 GW , 当该目标 eNB连接有 GW时,该目标 eNB的 GW信息还可以包括目标 eNB 连接的目标 GW的标识。
步骤 503 , UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 504 , 目标 eNB向源 eNB发送 UE上下文译放消息。
步骤 505 , 源 eNB译放 UE上下文相关资源。
步骤 506, 可选地, 源 eNB根据该源 eNB的 GW信息与目标 eNB的 GW信息,确定源 eNB连接在源 GW上,目标 eNB连接在目标 GW或 MME 上。
步骤 507, 源 GW接收源 eNB发送的 UE上下文译放请求消息, 该 UE 上下文译放请求消息携带切换到目标 eNB的 UE的标识。
步骤 508,源 GW将上述 UE上下文译放请求消息发送给 MME,该 UE 上下文译放请求消息携带切换到目标 eNB的 UE的标识。
步骤 509, MME向源 GW发送 UE上下文释放命令消息 , 该 UE上下 文译放命令消息携带切换到目标 eNB的 UE的标识。
步骤 510 , 源 GW译放该 UE的标识对应的 UE上下文相关资源。
另夕卜, 本实施例中, 源 eNB也可以根据源 GW和目标 GW的跟踪区域 标识(Tracking Area Identifier; 以下简称: TAI ) , 确定源 eNB连接在源 GW上, 目标 eNB连接在目标 GW或 MME上。 具体地, 可以规定不连接 在同一 GW上的 eNB不能共享 TAI, 这样当不连接在同一 GW上的 eNB 不能共享 TAI时, 源 eNB可以将该源 eNB的 TAI发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 TAI; 然后, 源 eNB可以根据该源 eNB 的 TAI与该目标 eNB的 TAI, 确定源 eNB连接在源 GW上, 目标 eNB连 接在目标 GW或 MME上; 于是, 源 eNB可以向源 GW发送 UE上下文释 放请求消息。
上述实施例中, 在接收到源 eNB发送的携带切换到目标 eNB的 UE的 标识的 UE上下文释放请求消息之后,源 GW可以将该 UE上下文释放请求 消息发送给 MME,接收 MME发送的 UE上下文译放命令消息 ,然后源 GW 可以译放该 UE上下文译放命令消息中携带的切换到目标 eNB的 UE的标 识对应的 UE上下文相关资源;从而可以实现译放源 GW中的 UE上下文相 关资源, 进而可以使新入网的 UE顺利接入, 并节省了资源。
图 6为本发明用户设备上下文相关资源的译放方法实施例六的流程图 , 本实施例以接入网节点为 eNB , 中间节点为 GW , 核心网节点为 MME , 控 制消息为 UE上下文译放请求消息为例进行说明。如图 6所示,该用户设备 上下文相关资源的译放方法可以包括:
步骤 601 , 可选地, 源 GW向源 eNB发送 GW标识。
步骤 602, 可选地, 源 eNB与目标 eNB交换 GW信息。
具体地, 源 eNB可以将该源 eNB的 GW信息发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 GW信息;
其中, 源 eNB的 GW信息可以包括该源 eNB是否连接有 GW, 当该源 eNB连接有 GW时, 该源 eNB的 GW信息还可以包括该源 eNB连接的源 GW的标识; 目标 eNB的 GW信息可以包括该目标 eNB是否连接有 GW , 当该目标 eNB连接有 GW时,该目标 eNB的 GW信息还可以包括目标 eNB 连接的目标 GW的标识。
步骤 603 , UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 604 , 目标 eNB向源 eNB发送 UE上下文译放消息。
步骤 605 , 可选地, 源 eNB译放 UE上下文相关资源。
步骤 606, 可选地, 源 eNB根据该源 eNB的 GW信息与目标 eNB的
GW信息,确定源 eNB连接在源 GW上,目标 eNB连接在目标 GW或 MME 上。
步骤 607, 源 GW接收源 eNB发送的 UE上下文译放请求消息, 该 UE 上下文译放请求消息携带切换到目标 eNB的 UE的标识。
步骤 608,源 GW将上述 UE上下文译放请求消息发送给 MME,该 UE 上下文译放请求消息携带切换到目标 eNB的 UE的标识。
步骤 609, MME向源 GW发送 UE上下文释放命令消息 , 该 UE上下 文译放命令消息携带切换到目标 eNB的 UE的标识。
步骤 610, 源 GW将上述 UE上下文释放命令消息发送给源 eNB, 该 UE上下文译放命令消息携带切换到目标 eNB的 UE的标识。
步骤 611 , 可选地, 源 eNB译放该 UE的标识对应的 UE上下文相关资 源。
本实施例中, 步骤 611和步骤 605互斥, 即这两个步骤在任一个实现 中只存在其一即可。
步骤 612, 源 eNB向源 GW发送 UE上下文译放完成消息, 该 UE上 下文译放命令消息携带切换到目标 eNB的 UE的标识。
步骤 613 , 源 GW译放该 UE的标识对应的 UE上下文相关资源。
步骤 614, 可选地, 源 GW向 MME发送 UE上下文译放完成消息。 另夕卜, 本实施例中, 源 eNB也可以根据源 GW和目标 GW的跟踪区域 标识(Tracking Area Identifier; 以下简称: TAI ) , 确定源 eNB连接在源
GW上, 目标 eNB连接在目标 GW或 MME上。 具体地, 可以规定不连接 在同一 GW上的 eNB不能共享 TAI, 这样当不连接在同一 GW上的 eNB 不能共享 TAI时, 源 eNB可以将该源 eNB的 TAI发送给目标 eNB, 并接 收目标 eNB发送的该目标 eNB的 TAI; 然后, 源 eNB可以根据该源 eNB 的 TAI与该目标 eNB的 TAI, 确定源 eNB连接在源 GW上, 目标 eNB连 接在目标 GW或 MME上; 于是, 源 eNB可以向源 GW发送 UE上下文释 放请求消息。
上述实施例中, 在接收到源 eNB发送的携带切换到目标 eNB的 UE的 标识的 UE上下文释放请求消息之后,源 GW可以将该 UE上下文释放请求 消息发送给 MME,接收 MME发送的 UE上下文译放命令消息 ,然后源 GW 可以将该 UE上下文释放命令消息发送给源 eNB, 接收源 eNB发送的 UE 上下文释放完成消息, 接下来源 GW可以释放该 UE上下文译放完成消息 中携带的切换到目标 eNB的 UE的标识对应的 UE上下文相关资源; 从而 可以实现译放源 GW中的 UE上下文相关资源, 进而可以使新入网的 UE 顺利接入, 并节省了资源。
图 7为本发明用户设备上下文相关资源的译放方法实施例七的流程图 , 如图 7所示, 该用户设备上下文相关资源的译放方法可以包括:
步骤 701, 中间节点监测该中间节点所服务的用户设备的数据和 /或信 令的传输。
步骤 702, 中间节点译放上述数据和 /或信令的传输符合预定条件的用 户设备上下文相关资源。
其中, 上述预定条件至少可以包括: 用户设备的数据和 /或信令的传输 的暂停时间超过预定的时间长度; 或者, 中间节点接收到针对上述用户设 备的结束标记数据包; 或者, 距离中间节点最后一次接收到针对上述用户 设备的心跳数据块的时刻的时间间隔超过预定的时间间隔。
本实施例中, 中间节点监测该中间节点所服务的用户设备的数据和 /或 信令的传输之后, 译放上述数据和 /或信令的传输符合预定条件的用户设备 的上下文相关资源之前, 该中间节点还可以向核心网节点发送用户设备上 下文译放请求消息或重置消息, 并接收核心网节点发送的用户设备上下文 释放命令消息或重置确认消息。 当然, 本发明实施例并不仅限于此, 该中 间节点还可以向核心网节点发送除用户设备上下文译放请求消息和重置消 息之外的任意一条消息, 只要可以实现中间节点监测该中间节点所服务的 用户设备的数据和 /或信令的传输之后, 译放上述数据和 /或信令的传输符合 预定条件的用户设备的上下文相关资源即可, 本发明实施例对中间节点向 核心网节点发送的消息的具体形式不作限定。
本实施例中, 核心网节点可以为提供核心网功能的节点, 例如: 移动 性管理实体等; 中间节点可以为在接入网节点与核心网节点之间提供协议 转换、 路由选择、 数据交换等网络兼容功能的节点, 例如: 该中间节点可 以为网关或 DeNB;接入网节点可以为具有接入功能的节点,例如:基站等, 其中该基站可以包括 eNB, 该 eNB可以为普通的宏基站, 也可以是一些小 型基站, 包括 HeNB/ HNB或 RN等等; 但本发明实施例对接入网节点、 中 间节点和核心网节点的具体形式不作限定。
上述实施例中, 中间节点可以监测该中间节点所服务的用户设备的数 据和 /或信令的传输, 然后译放上述数据和 /或信令的传输符合预定条件的用 户设备上下文相关资源; 从而可以实现译放源中间节点中的用户设备上下 文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 8为本发明用户设备上下文相关资源的译放方法实施例八的流程图, 本实施例以接入网节点为 eNB, 中间节点为 GW,核心网节点为 MME为例 进行说明。 如图 8所示, 该用户设备上下文相关资源的译放方法可以包括: 步骤 801 , 可选地, UE通过 X2切换由源 eNB切换到目标 eNB。
步骤 802 , 可选地, 目标 eNB向源 eNB发送 UE上下文译放消息。 步骤 803 , 可选地, 源 eNB译放 UE上下文相关资源。
步骤 804, 源 GW监测该源 GW所服务的用户设备的数据和 /或信令的 传输, 发现数据和 /或信令的传输符合预定条件的用户设备。
其中, 该预定条件可以为以下之一或组合:
( 1 )UE的数据和 /或信令,例如:跟踪区域更新( Tracking Area Update; 以下简称: TAU )信令的传输的暂停时间超过预定的时间长度;
( 2 ) 源 GW接收到针对上述 UE的结束标记( End Marker )数据包; 其中, 该结束标记数据包表示核心网之后不会将该 UE 的数据包发送给源 eNB;
( 3 )距离源 GW最后一次接收到针对上述 UE的心跳数据块( Heart Beat Chunk ) 的时刻的时间间隔超过预定的时间间隔; 其中, 接收到针对上述 UE的心跳数据块表示该 UE仍在接收该源 GW的服务。
步骤 805 , 可选地 , 源 GW向 MME发送 UE上下文释放请求消息。 步骤 806 , 可选地 , MME向源 GW发送 UE上下文译放命令消息。 步骤 807, 源 GW译放数据和 /或信令的传输符合预定条件的用户设备 上下文相关资源。
另外, 本实施例步骤 805中, 源 GW也可以向 MME发送重置消息, 这样 , 步骤 806中 , MME可以向源 GW发送重置确认消息; 本实施例对此 不作限定。
上述实施例中, 源 GW可以监测该源 GW所服务的 UE的数据和 /或信 令的传输, 然后译放上述数据和 /或信令的传输符合预定条件的 UE上下文 相关资源; 从而可以实现译放源 GW中的 UE上下文相关资源, 进而可以 使新入网的 UE顺利接入, 并节省了资源。
图 9为本发明用户设备上下文相关资源的译放方法实施例九的流程图 , 如图 9所示, 该用户设备上下文相关资源的译放方法可以包括:
步骤 901 ,源接入网节点确定用户设备由源接入网节点切换到目标接入 网节点。
步骤 902, 源接入网节点向源中间节点发送控制消息, 该控制消息携带 切换到目标接入网节点的用户设备的标识, 以使该源中间节点译放上述用 户设备的标识对应的用户设备上下文相关资源。
本实施例的一种实现方式中, 源接入网节点确定用户设备通过切换由 源接入网节点切换到目标接入网节点之前, 该源接入网节点可以将该源接 入网节点的中间节点信息发送给目标接入网节点, 并接收目标接入网节点 发送的目标接入网节点的中间节点信息; 则在源接入网节点向源中间节点 发送控制消息之前, 源接入网节点可以根据该源接入网节点的中间节点信 息与目标接入网节点的中间节点信息, 确定需要向源中间节点发送上述控 制消息。
具体地, 当根据该源接入网节点的中间节点信息与目标接入网节点的 中间节点信息, 确定源接入网节点连接在源中间节点上, 目标接入网节点 连接在目标中间节点或核心网节点上时, 源接入网节点可以向源中间节点 发送上述控制消息。
其中, 上述源接入网节点的中间节点信息包括源接入网节点是否连接 有中间节点, 当源接入网节点连接有中间节点时, 上述源接入网节点的中 间节点信息还包括源接入网节点连接的源中间节点的标识; 其中, 源中间 节点的标识可以是在源接入网节点将源接入网节点的中间节点信息发送给 目标接入网节点之前, 由源中间节点发送给源接入网节点的;
上述目标接入网节点的中间节点信息包括目标接入网节点是否连接有 中间节点, 当目标接入网节点连接有中间节点时, 上述目标接入网节点的 中间节点信息还包括目标接入网节点连接的目标中间节点的标识; 其中, 目标中间节点的标识可以是在目标接入网节点将目标接入网节点的中间节 点信息发送给源接入网节点之前, 由目标中间节点发送给目标接入网节点 的。
本实施例的另一种实现方式中, 源接入网节点确定用户设备通过切换 由源接入网节点切换到目标接入网节点之前, 当不连接在同一中间节点上 的接入网节点不能共享跟踪区域标识时 , 该源接入网节点可以将源接入网 节点的跟踪区域标识发送给所述目标接入网节点, 并接收目标接入网节点 发送的该目标接入网节点的跟踪区域标识; 则在源接入网节点向源中间节 点发送控制消息之前, 源接入网节点可以根据该源接入网节点的跟踪区域 标识与目标接入网节点的跟踪区域标识, 确定需要向源中间节点发送上述 控制消息。
具体地, 当根据该源接入网节点的跟踪区域标识与目标接入网节点的 跟踪区域标识, 确定源接入网节点连接在源中间节点上, 目标接入网节点 连接在目标中间节点或核心网节点上时, 源接入网节点可以向源中间节点 发送上述控制消息。
但本实施例并不仅限于上述两种实现方式, 源接入网节点也可以通过 其他判断标准来确定是否需要向源中间节点发送控制消息, 本实施例对此 不作限定。
上述实施例中, 源接入网节点确定用户设备通过切换由源接入网节点 切换到目标接入网节点之后, 源接入网节点可以向源中间节点发送携带切 换到目标接入网节点的用户设备的标识的控制消息, 这样, 接收到该控制 消息之后, 源中间节点就可以译放上述用户设备的标识对应的用户设备上 下文相关资源; 从而可以实现译放源中间节点中的用户设备上下文相关资 源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 10 为本发明用户设备上下文相关资源的译放方法实施例十的流程 图, 如图 10所示, 该用户设备上下文相关资源的译放方法可以包括: 步骤 1001 , 核心网节点向源中间节点发送控制消息, 该控制消息携带 切换到目标接入网节点的用户设备的标识, 以使该源中间节点译放上述用 户设备的标识对应的用户设备上下文相关资源。
步骤 1002, 核心网节点接收源中间节点发送的针对上述控制消息的响 应。 本实施例的一种实现方式中, 核心网节点向源中间节点发送控制消息 之前, 该核心网节点可以接收并保存中间节点发送的该中间节点的中间节 点标识和该中间节点标识对应的中间节点标志, 该中间节点标志标示发送 该中间节点标志的节点类型为中间节点, 该中间节点标识在一个网络中唯 一标识一个中间节点; 这时, 核心网节点根据预先获得的用户设备对应的 源侧节点和目标侧节点的标识, 以及中间节点标志与中间节点标识的对应 关系 , 确定需要向源中间节点发送上述控制消息。
具体地, 在向源中间节点发送控制消息之前, 核心网节点可以接收目 标接入网节点发送的切换到目标接入网节点的用户设备的标识, 以及接收 切换到目标接入网节点的用户设备对应的目标侧节点发送的路径切换请 求; 上述用户设备的标识由核心网节点在该用户设备接入网络时为该用户 设备分配, 并在进行 X2切换时, 由源接入网节点发送给目标接入网节点; 然后, 该核心网节点根据上述用户设备的标识, 在保存的用户设备的标识 与用户设备对应的源侧节点的标识的对应关系中进行查找, 获得该用户设 备对应的源侧节点的标识; 并根据保存的接收上述路径切换请求的路径与 目标侧节点的标识的对应关系, 获得上述用户设备对应的目标侧节点的标 识; 其中, 上述用户设备对应的源侧节点和目标侧节点与核心网节点直接 连接。
获得用户设备对应的源侧节点的标识之后, 核心网节点可以根据该源 侧节点的标识, 在该核心网节点保存的中间节点标识中进行查找, 若查找 到与该源侧节点的标识相同的中间节点标识, 则该核心网节点可以根据该 中间节点标识对应的中间节点标志, 确定源侧节点为源中间节点; 若未查 找到与该源侧节点的标识相同的中间节点标识, 则可以确定该源侧节点不 是源中间节点; 同理, 获得用户设备对应的目标侧节点的标识之后, 核心 网节点可以根据该目标侧节点的标识, 在该核心网节点保存的中间节点标 识中进行查找, 若查找到与该目标侧节点的标识相同的中间节点标识, 则 该核心网节点可以才艮据该中间节点标识对应的中间节点标志 , 确定目标侧 节点为目标中间节点; 若未查找到与该目标侧节点的标识相同的中间节点 标识, 则可以确定该目标侧节点不是目标中间节点。
本实施例的另一种实现方式中, 核心网节点向源中间节点发送控制消 息之前, 该核心网节点可以接收并保存中间节点发送的中间节点标识和该 中间节点标识对应的跟踪区域标识; 其中, 中间节点发送的跟踪区域标识 所属的集合对应的节点类型为中间节点, 中间节点标识在一个网络中唯一 标识一个中间节点; 这时, 核心网节点可以根据预先获得的用户设备对应 的源侧节点和目标侧节点的标识, 以及跟踪区域标识和中间节点标识的对 应关系, 确定需要向源中间节点发送上述控制消息。
具体地, 在向源中间节点发送控制消息之前, 核心网节点可以接收目 标接入网节点发送的切换到目标接入网节点的用户设备的标识, 以及接收 切换到目标接入网节点的用户设备对应的目标侧节点发送的路径切换请 求; 上述用户设备的标识由核心网节点在该用户设备接入网络时为该用户 设备分配, 并在进行 X2切换时, 由源接入网节点发送给目标接入网节点; 然后, 该核心网节点根据上述用户设备的标识, 在保存的用户设备的标识 与用户设备对应的源侧节点的标识的对应关系中进行查找, 获得该用户设 备对应的源侧节点的标识; 并根据保存的接收上述路径切换请求的路径与 目标侧节点的标识的对应关系, 获得上述用户设备对应的目标侧节点的标 识; 其中, 上述用户设备对应的源侧节点和目标侧节点与核心网节点直接 连接。
本实现方式中, 可以设定不同类型的节点使用不同的跟踪区域标识集 合, 例如: 可以设定中间节点和接入网节点这两种类型的节点使用不同的 跟踪区域标识集合。 这样, 获得用户设备对应的源侧节点的标识之后, 核 心网节点可以根据该源侧节点的标识, 在该核心网节点保存的中间节点标 识中进行查找, 若查找到与该源侧节点的标识相同的中间节点标识, 则该 核心网节点可以根据该中间节点标识对应的跟踪区域标识所属集合对应的 节点类型, 确定源侧节点为源中间节点; 若未查找到与该源侧节点的标识 相同的中间节点标识, 则可以确定该源侧节点不是源中间节点; 同理, 获 得用户设备对应的目标侧节点的标识之后, 核心网节点可以根据该目标侧 节点的标识, 在该核心网节点保存的中间节点标识中进行查找, 若查找到 与该目标侧节点的标识相同的中间节点标识, 则该核心网节点可以根据该 中间节点标识对应的跟踪区域标识所属集合对应的节点类型, 确定目标侧 节点为目标中间节点; 若未查找到与该目标侧节点的标识相同的中间节点 标识, 则可以确定该目标侧节点不是目标中间节点。
本实施例中, 当通过上述两种实现方式确定源侧节点为源中间节点, 目标侧节点为目标中间节点, 且上述源侧节点的标识与所述目标侧节点的 标识不同时, 或者当源侧节点为源中间节点, 目标侧节点不是目标中间节 点时, 核心网节点可以向源中间节点发送控制消息。 但本实施例并不仅限 于此, 核心网节点也可以通过其他判断方式来确定是否需要向源中间节点 发送控制消息, 本实施例对此不作限定。
上述实施例中, 核心网节点向源中间节点发送携带切换到目标接入网 节点的用户设备的标识的控制消息, 这样, 接收到该控制消息之后, 源中 间节点就可以译放上述用户设备的标识对应的用户设备上下文相关资源; 从而可以实现译放源中间节点中的用户设备上下文相关资源, 进而可以使 新入网的用户设备顺利接入, 并节省了资源。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步 骤可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机 可读取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序 代码的介质。
图 11为本发明中间节点设备实施例一的结构示意图, 本实施例中的中 间节点设备可以实现本发明图 1所示实施例的流程, 如图 11所示, 该中间 节点设备可以包括: 第一接收模块 1101和译放模块 1102;
其中, 第一接收模块 1101 , 用于接收控制消息, 该控制消息携带切换 到目标接入网节点设备的用户设备的标识;
译放模块 1102,用于根据第一接收模块 1101接收的控制消息所携带的 用户设备的标识, 译放上述用户设备的标识对应的用户设备上下文相关资 源。
本实施例中的中间节点设备可以为在接入网节点设备与核心网节点设 备之间提供协议转换、 路由选择、 数据交换等网络兼容功能的节点设备, 例如: 网关或 DeNB等; 但本发明实施例对中间节点设备的具体形式不作 限定。
本实施例中的控制消息可以为用户设备上下文译放请求消息、 用户设 备上下文译放命令消息或重置消息, 但本发明实施例并不仅限于此, 本发 明实施例对控制消息的具体消息形式不作限定, 该控制消息也可以为除用 户设备上下文译放请求消息、 用户设备上下文译放命令消息和重置消息之 外的任意一种消息, 只要可以实现源中间节点根据该控制消息携带的切换 到目标接入网节点的用户设备的标识, 译放相应的用户设备上下文相关资 源即可。
上述中间节点设备, 第一接收模块 1101接收到携带切换到目标接入网 节点的用户设备的标识的控制消息之后, 译放模块 1102译放该用户设备的 标识对应的用户设备上下文相关资源; 从而可以实现译放源中间节点设备 中的用户设备上下文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 12为本发明中间节点设备实施例二的结构示意图, 与图 11所示的 中间节点设备相比, 不同之处在于, 在一种实现方式中, 图 12所示的中间 节点设备中, 第一接收模块 1101接收的控制消息可以为源接入网节点设备 发送的用户设备上下文译放请求消息或重置消息。
进一步地, 本实现方式中的中间节点设备还可以包括: 第一发送模块
1103 , 用于将第一接收模块 1101接收的用户设备上下文译放请求消息或重 置消息发送给核心网节点设备; 这时, 第一接收模块 1101还可以接收核心 网节点设备发送的用户设备上下文译放命令消息或重置确认消息。
本实现方式中, 第一发送模块 1103还可以将接收到的用户设备上下文 释放命令消息或重置确认消息发送给源接入网节点设备; 第一接收模块 1101还可以接收源接入网节点设备发送的用户设备上下文译放完成消息或 重置确认消息。进一步地,第一发送模块 1103还可以将该第一接收模块 1101 接收到的用户设备上下文译放完成消息或重置确认消息发送给核心网节点 设备。
本实施例的另一种实现方式中, 第一接收模块 1101接收的控制消息可 以为核心网节点设备发送的用户设备上下文释放命令消息或重置消息。
进一步地, 本实现方式中的中间节点设备还可以包括: 第二发送模块
1104, 用于将第一接收模块 1101接收的用户设备上下文译放命令消息或重 置消息发送给源接入网节点设备; 这时, 第一接收模块 1101还可以接收源 接入网节点设备发送的用户设备上下文译放完成消息或重置确认消息。 进 一步地, 第二发送模块 1104还可以将第一接收模块 1101接收的用户设备 上下文译放完成消息或重置确认消息发送给核心网节点设备。
上述中间节点设备可以实现译放源中间节点设备中的用户设备上下文 相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 13为本发明源接入网节点设备实施例一的结构示意图, 如图 13所 示, 该源接入网节点设备可以包括: 第一确定模块 1301 和第三发送模块 1302;
其中, 第一确定模块 1301 , 用于确定用户设备由源接入网节点切换到 目标接入网节点; 第三发送模块 1302,用于在第一确定模块 1301确定用户设备通过切换 由源接入网节点切换到目标接入网节点之后, 向源中间节点设备发送控制 消息, 该控制消息携带切换到目标接入网节点设备的用户设备的标识, 以 使源中间节点设备译放上述用户设备的标识对应的用户设备上下文相关资 源。
本实施例中的源接入网节点设备可以为具有接入功能的节点设备, 例 如: 基站等, 其中该基站可以包括 eNB, 该 eNB可以为普通的宏基站, 也 可以是一些小型基站, 包括 HeNB/ HNB或 RN等等; 但本发明实施例对源 接入网节点设备的具体形式不作限定。
本实施例中的控制消息可以为用户设备上下文译放请求消息或重置消 息, 但本发明实施例并不仅限于此, 本发明实施例对控制消息的具体消息 形式不作限定, 该控制消息也可以为除用户设备上下文译放请求消息和重 置消息之外的任意一种消息, 只要可以实现源中间节点根据该控制消息携 带的切换到目标接入网节点的用户设备的标识, 译放相应的用户设备上下 文相关资源即可。
上述源接入网节点设备可以实现译放源中间节点设备中的用户设备上 下文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 14为本发明源接入网节点设备实施例二的结构示意图, 与图 13所 示的源接入网节点设备相比, 不同之处在于, 图 14所示的源接入网节点设 备还可以包括: 第二接收模块 1303;
其中, 第三发送模块 1302还用于将上述源接入网节点设备的中间节点 信息发送给目标接入网节点设备; 第二接收模块 1303 , 用于接收目标接入 网节点设备发送的目标接入网节点设备的中间节点信息; 这时, 第一确定 模块 1301 还可以根据源接入网节点设备的中间节点信息与第二接收模块 1303接收的目标接入网节点设备的中间节点信息, 确定需要第三发送模块 1302向源中间节点设备发送控制消息。 进一步地, 本实施例中的源接入网节点设备还可以包括: 第三接收模 块 1304;
具体地, 第三发送模块 1302还可以当不连接在同一中间节点设备上的 接入网节点设备不能共享跟踪区域标识时, 将源接入网节点设备的跟踪区 域标识发送给目标接入网节点设备; 然后, 第三接收模块 1304可以接收目 标接入网节点设备发送的该目标接入网节点设备的跟踪区域标识; 这时, 第一确定模块 1301还可以根据源接入网节点设备的跟踪区域标识与第三接 收模块 1304接收的目标接入网节点设备的跟踪区域标识, 确定需要第三发 送模块 1302向源中间节点设备发送控制消息。
上述源接入网节点设备可以实现译放源中间节点设备中的用户设备上 下文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 15为本发明核心网节点设备实施例一的结构示意图, 如图 15所示, 该核心网节点设备可以包括: 第四发送模块 1501和第四接收模块 1502。
其中, 第四发送模块 1501 , 用于向源中间节点设备发送控制消息, 该 控制消息携带切换到目标接入网节点设备的用户设备的标识, 以使该源中 间节点设备译放上述用户设备的标识对应的用户设备上下文相关资源; 第四接收模块 1502, 用于接收源中间节点设备发送的针对上述控制消 息的响应。
本实施例中的控制消息可以为用户设备上下文译放命令消息或重置消 息, 但本发明实施例并不仅限于此, 本发明实施例对控制消息的具体消息 形式不作限定, 该控制消息也可以为除用户设备上下文译放命令消息和重 置消息之外的任意一种消息, 只要可以实现源中间节点根据该控制消息携 带的切换到目标接入网节点的用户设备的标识, 译放相应的用户设备上下 文相关资源即可。
本实施例中的核心网节点设备可以为提供核心网功能的节点设备, 例 如: 移动性管理实体等; 本发明实施例对核心网节点设备的具体形式不作 限定。
上述核心网节点设备可以实现译放源中间节点设备中的用户设备上下 文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 16为本发明核心网节点设备实施例二的结构示意图, 与图 15所示 的核心网节点设备相比, 不同之处在于, 本实施例的一种实现方式中, 图 16所示的核心网节点设备还可以包括: 第二确定模块 1503;
本实施例中, 第四接收模块 1502还可以接收并保存中间节点设备发送 的该中间节点设备的中间节点标识和该中间节点标识对应的中间节点标 志, 该中间节点标志标示发送上述中间节点标志的节点设备的类型为中间 节点设备, 该中间节点标识在一个网络中唯一标识一个中间节点设备。
这时, 第二确定模块 1503可以根据预先获得的用户设备对应的源侧节 点设备和目标侧节点设备的标识, 以及中间节点标志和中间节点标识的对 应关系, 确定需要第四发送模块 1501向源中间节点设备发送控制消息; 具 体确定方式可参考本发明图 10所示实施例中的描述, 在此不再贅述。
本实施例的另一种实现方式中, 图 16所示的核心网节点设备还可以包 括: 第五接收模块 1504, 用于接收并保存中间节点设备发送的中间节点标 识和该中间节点标识对应的跟踪区域标识; 其中, 中间节点设备发送的跟 踪区域标识所属的集合对应的节点设备类型为中间节点设备, 中间节点标 识在一个网络中唯一标识一个中间节点设备。
这时, 第二确定模块 1503还可以根据预先获得的用户设备对应的源侧 节点设备和目标侧节点设备的标识, 以及跟踪区域标识和中间节点标识的 对应关系, 确定需要第四发送模块 1501向源中间节点设备发送控制消息; 具体确定方式可参考本发明图 10所示实施例中的描述, 在此不再贅述。
上述核心网节点设备可以实现译放源中间节点设备中的用户设备上下 文相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
图 17为本发明中间节点设备实施例三的结构示意图, 本实施例中的中 间节点设备可以实现本发明图 7所示实施例的流程, 如图 17所示, 该中间 节点设备可以包括: 监测模块 1701和资源译放模块 1702;
其中, 监测模块 1701 , 用于监测中间节点设备下用户设备的数据和 /或 信令的传输;
资源译放模块 1702, 用于释放监测模块 1701监测到的上述数据和 /或 信令的传输符合预定条件的用户设备上下文相关资源。
本实施例中的中间节点设备可以为在接入网节点设备与核心网节点设 备之间提供协议转换、 路由选择、 数据交换等网络兼容功能的节点设备, 例如: 网关或 DeNB等; 但本发明实施例对中间节点设备的具体形式不作 限定。
上述中间节点设备中, 监测模块 1701可以监测该中间节点设备所服务 的用户设备的数据和 /或信令的传输,然后资源译放模块 1702可以译放上述 数据和 /或信令的传输符合预定条件的用户设备上下文相关资源; 从而可以 实现译放源中间节点设备中的用户设备上下文相关资源, 进而可以使新入 网的用户设备顺利接入, 并节省了资源。
图 18为本发明中间节点设备实施例四的结构示意图, 与图 17所示的 中间节点设备相比,不同之处在于,图 18所示的中间节点设备还可以包括: 消息发送模块 1703 , 用于向核心网节点设备发送用户设备上下文译放 请求消息或重置消息; 具体地, 消息发送模块 1703 可以在监测模块 1701 监测中间节点设备下用户设备的数据和 /或信令的传输之后, 资源释放模块 1702译放上述数据和 /或信令的传输符合预定条件的用户设备上下文相关 资源之前, 向核心网节点设备发送用户设备上下文译放请求消息或重置消 息;
消息接收模块 1704, 用于接收核心网节点设备发送的用户设备上下文 释放命令消息或重置确认消息;
本实施例中, 在消息接收模块 1704接收到核心网节点设备发送的用户 设备上下文译放命令消息或重置确认消息之后, 资源释放模块 1702可以释 放上述数据和 /或信令的传输符合预定条件的用户设备上下文相关资源。
当然, 本发明实施例并不仅限于此, 消息发送模块 1703还可以向核心 网节点设备发送除用户设备上下文译放请求消息和重置消息之外的任意一 条消息, 只要可以实现监测模块 1701监测该中间节点所服务的用户设备的 数据和 /或信令的传输之后, 资源译放模块 1702译放上述数据和 /或信令的 传输符合预定条件的用户设备的上下文相关资源即可, 本发明实施例对消 息发送模块 1703向核心网节点发送的消息的具体形式不作限定。
上述中间节点设备可以实现译放源中间节点设备中的用户设备上下文 相关资源, 进而可以使新入网的用户设备顺利接入, 并节省了资源。
本领域技术人员可以理解附图只是一个优选实施例的示意图, 附图中 的模块或流程并不一定是实施本发明所必须的。
本领域技术人员可以理解实施例中的装置中的模块可以按照实施例描 述进行分布于实施例的装置中, 也可以进行相应变化位于不同于本实施例 的一个或多个装置中。 上述实施例的模块可以合并为一个模块, 也可以进 一步拆分成多个子模块。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修 改, 或者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不 使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权利要求书
1、 一种用户设备上下文相关资源的译放方法, 其特征在于, 包括: 源中间节点接收控制消息 , 所述控制消息携带切换到目标接入网节点 的用户设备的标识;
所述源中间节点译放所述用户设备的标识对应的用户设备上下文相关 资源。
2、 根据权利要求 1所述的方法, 其特征在于, 所述控制消息包括用户 设备上下文译放请求消息或重置消息;
所述源中间节点接收控制消息包括:
所述源中间节点接收源接入网节点发送的所述用户设备上下文译放请 求消息或重置消息。
3、 根据权利要求 2所述的方法, 其特征在于, 所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源之前, 还包括:
所述源中间节点将接收的所述用户设备上下文译放请求消息或所述重 置消息发送给核心网节点;
所述源中间节点接收所述核心网节点发送的用户设备上下文译放命令 消息或重置确认消息。
4、 根据权利要求 3所述的方法, 其特征在于, 所述源中间节点接收所 述核心网节点发送的用户设备上下文译放命令消息或重置确认消息之后, 所述源中间节点译放所述用户设备的标识对应的用户设备上下文相关资源 之前, 还包括:
所述源中间节点将接收到的所述用户设备上下文译放命令消息或所述 重置消息发送给所述源接入网节点;
所述源中间节点接收所述源接入网节点发送的用户设备上下文译放完 成消息或重置确认消息。
5、 根据权利要求 4所述的方法, 其特征在于, 所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源之后, 还包括: 所述源中间节点将接收到的所述用户设备上下文译放完成消息或所述 重置确认消息发送给所述核心网节点。
6、 根据权利要求 1所述的方法, 其特征在于, 所述控制消息包括用户 设备上下文译放命令消息或重置消息;
所述源中间节点接收控制消息包括:
所述源中间节点接收核心网节点发送的所述用户设备上下文译放命令 消息或重置消息。
7、 根据权利要求 6所述的方法, 其特征在于, 所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源之前, 还包括:
所述源中间节点将接收的所述用户设备上下文译放命令消息或重置消 息发送给所述源接入网节点;
所述源中间节点接收所述源接入网节点发送的用户设备上下文译放完 成消息或重置确认消息。
8、 根据权利要求 7所述的方法, 其特征在于, 所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源之后, 还包括:
所述源中间节点将接收的所述用户设备上下文译放完成消息或所述重 置确认消息发送给所述核心网节点。
9、 根据权利要求 2所述的方法, 其特征在于, 所述用户设备上下文译 放请求消息或重置消息中携带终结标识, 所述用户设备上下文译放请求消 息或重置消息中的终结标识表示所述源中间节点无需再将所述用户设备上 下文译放请求消息或重置消息发送给核心网节点。
10、 根据权利要求 6所述的方法, 其特征在于, 所述用户设备上下文 释放命令消息或重置消息中携带终结标识, 所述用户设备上下文译放命令 消息或重置消息中的终结标识表示所述源中间节点无需再将所述用户设备 上下文译放命令消息或重置消息发送给所述源接入网节点。
11、 一种用户设备上下文相关资源的译放方法, 其特征在于, 包括: 源接入网节点确定用户设备由所述源接入网节点切换到目标接入网节 点;
所述源接入网节点向源中间节点发送控制消息, 所述控制消息携带切 换到所述目标接入网节点的用户设备的标识, 以使所述源中间节点译放所 述用户设备的标识对应的用户设备上下文相关资源。
12、 根据权利要求 11所述的方法, 其特征在于, 所述源接入网节点确 定用户设备由所述源接入网节点切换到目标接入网节点之前, 还包括: 所述源接入网节点将所述源接入网节点的中间节点信息发送给所述目 标接入网节点, 并接收所述目标接入网节点发送的所述目标接入网节点的 中间节点信息;
所述源接入网节点向源中间节点发送控制消息之前, 还包括: 所述源接入网节点根据所述源接入网节点的中间节点信息与所述目标 接入网节点的中间节点信息 , 确定需要向所述源中间节点发送所述控制消 息。
13、 根据权利要求 12所述的方法, 其特征在于, 所述源接入网节点的 中间节点信息包括所述源接入网节点是否连接有中间节点, 当所述源接入 网节点连接有中间节点时, 所述源接入网节点的中间节点信息还包括所述 源接入网节点连接的源中间节点的标识;
所述目标接入网节点的中间节点信息包括所述目标接入网节点是否连 接有中间节点, 当所述目标接入网节点连接有中间节点时, 所述目标接入 网节点的中间节点信息还包括所述目标接入网节点连接的目标中间节点的 标识。
14、 根据权利要求 13所述的方法, 其特征在于,
所述源中间节点的标识是在所述源接入网节点将所述源接入网节点的 中间节点信息发送给所述目标接入网节点之前, 由所述源中间节点发送给 所述源接入网节点的;
所述目标中间节点的标识是在所述目标接入网节点将所述目标接入网 节点的中间节点信息发送给所述源接入网节点之前, 由所述目标中间节点 发送给所述目标接入网节点的。
15、 根据权利要求 11所述的方法, 其特征在于, 所述源接入网节点确 定用户设备由所述源接入网节点切换到目标接入网节点之前, 还包括: 当不连接在同一中间节点上的接入网节点不能共享跟踪区域标识时, 所述源接入网节点将所述源接入网节点的跟踪区域标识发送给所述目标接 入网节点, 并接收所述目标接入网节点发送的所述目标接入网节点的跟踪 区域标识;
所述源接入网节点向源中间节点发送控制消息之前, 还包括: 所述源接入网节点根据所述源接入网节点的跟踪区域标识与所述目标 接入网节点的跟踪区域标识, 确定需要向所述源中间节点发送所述控制消 息。
16、 一种用户设备上下文相关资源的译放方法, 其特征在于, 包括: 核心网节点向源中间节点发送控制消息, 所述控制消息携带切换到目 标接入网节点的用户设备的标识, 以使所述源中间节点译放所述用户设备 的标识对应的用户设备上下文相关资源;
所述核心网节点接收所述源中间节点发送的针对所述控制消息的响 应。
17、 根据权利要求 16所述的方法, 其特征在于, 所述核心网节点向源 中间节点发送控制消息之前, 还包括:
所述核心网节点接收并保存中间节点发送的所述中间节点的中间节点 标识和所述中间节点标识对应的中间节点标志, 所述中间节点标志标示发 送所述中间节点标志的节点类型为中间节点, 所述中间节点标识在一个网 络中唯一标识一个中间节点;
所述核心网节点根据预先获得的所述用户设备对应的源侧节点和目标 侧节点的标识, 以及所述中间节点标志与所述中间节点标识的对应关系, 确定需要向所述源中间节点发送所述控制消息。
18、 根据权利要求 16所述的方法, 其特征在于, 所述核心网节点向源 中间节点发送控制消息之前, 还包括:
所述核心网节点接收并保存中间节点发送的中间节点标识和所述中间 节点标识对应的跟踪区域标识; 其中, 所述中间节点发送的跟踪区域标识 所属的集合对应的节点类型为中间节点, 所述中间节点标识在一个网络中 唯一标识一个中间节点;
所述核心网节点根据预先获得的所述用户设备对应的源侧节点和目标 侧节点的标识, 以及所述跟踪区域标识和所述中间节点标识的对应关系, 确定需要向所述源中间节点发送所述控制消息。
19、 根据权利要求 17或 18所述的方法, 其特征在于, 所述核心网节 点向源中间节点发送控制消息包括:
当所述源侧节点为源中间节点, 所述目标侧节点为目标中间节点, 且 所述源侧节点的标识与所述目标侧节点的标识不同时, 或者当所述源侧节 点为源中间节点, 所述目标侧节点不是目标中间节点时, 所述核心网节点 向源中间节点发送控制消息。
20、 一种用户设备上下文相关资源的译放方法, 其特征在于, 包括: 中间节点监测所述中间节点所服务的用户设备的数据和 /或信令的传 输;
所述中间节点译放所述数据和 /或信令的传输符合预定条件的用户设备 上下文相关资源。
21、 根据权利要求 20所述的方法, 其特征在于, 所述中间节点监测所 述中间节点所服务的用户设备的数据和 /或信令的传输之后, 所述中间节点 译放所述数据和 /或信令的传输符合预定条件的用户设备上下文相关资源之 前, 还包括:
所述中间节点向核心网节点发送用户设备上下文译放请求消息或重置 消息; 所述中间节点接收所述核心网节点发送的用户设备上下文译放命令消 息或重置确认消息。
22、 根据权利要求 20或 21所述的方法, 其特征在于, 所述预定条件 至少包括: 所述用户设备的数据和 /或信令的传输的暂停时间超过预定的时 间长度; 或者,
所述中间节点接收到针对所述用户设备的结束标记数据包; 或者, 距离所述中间节点最后一次接收到针对所述用户设备的心跳数据块的 时刻的时间间隔超过预定的时间间隔。
23、 一种中间节点设备, 其特征在于, 包括:
第一接收模块 , 用于接收控制消息 , 所述控制消息携带切换到目标接 入网节点设备的用户设备的标识;
译放模块, 用于根据所述第一接收模块接收的控制消息所携带的用户 设备的标识, 译放所述用户设备的标识对应的用户设备上下文相关资源。
24、 根据权利要求 23所述的中间节点设备, 其特征在于, 所述第一接 收模块接收的所述控制消息具体为源接入网节点设备发送的用户设备上下 文译放请求消息或重置消息。
25、 根据权利要求 24所述的中间节点设备, 其特征在于, 所述设备还 包括:
第一发送模块, 用于将所述第一接收模块接收的所述用户设备上下文 释放请求消息或所述重置消息发送给核心网节点设备;
所述第一接收模块, 还用于接收所述核心网节点设备发送的用户设备 上下文译放命令消息或重置确认消息。
26、 根据权利要求 25所述的中间节点设备, 其特征在于,
所述第一发送模块, 还用于将接收到的所述用户设备上下文译放命令 消息或所述重置消息发送给所述源接入网节点设备;
所述第一接收模块, 还用于接收所述源接入网节点设备发送的用户设 备上下文译放完成消息或重置确认消息。
27、 根据权利要求 26所述的中间节点设备, 其特征在于,
所述第一发送模块, 还用于将所述第一接收模块接收到的所述用户设 备上下文译放完成消息或所述重置确认消息发送给所述核心网节点设备。
28、 根据权利要求 23所述的中间节点设备, 其特征在于, 所述第一接 收模块接收的所述控制消息具体为核心网节点设备发送的用户设备上下文 释放命令消息或重置消息。
29、 根据权利要求 28所述的中间节点设备, 其特征在于, 所述设备还 包括:
第二发送模块, 用于将所述第一接收模块接收的所述用户设备上下文 释放命令消息或所述重置消息发送给源接入网节点设备;
所述第一接收模块, 还用于接收所述源接入网节点设备发送的用户设 备上下文译放完成消息或重置确认消息。
30、 根据权利要求 29所述的中间节点设备, 其特征在于,
所述第二发送模块, 还用于将所述第一接收模块接收的所述用户设备 上下文译放完成消息或所述重置确认消息发送给所述核心网节点设备。
31、 一种源接入网节点设备, 其特征在于, 包括:
第一确定模块, 用于确定用户设备由所述源接入网节点切换到目标接 入网节点;
第三发送模块, 用于在所述第一确定模块确定用户设备通过切换由所 述源接入网节点切换到目标接入网节点之后, 向所述源中间节点设备发送 控制消息, 所述控制消息携带切换到所述目标接入网节点设备的用户设备 的标识, 以使所述源中间节点设备译放所述用户设备的标识对应的用户设 备上下文相关资源。
32、 根据权利要求 31所述的源接入网节点设备, 其特征在于, 所述设 备还包括: 第二接收模块;
所述第三发送模块, 还用于将所述源接入网节点设备的中间节点信息 发送给所述目标接入网节点设备; 所述第二接收模块, 用于接收所述目标接入网节点设备发送的所述目 标接入网节点设备的中间节点信息;
所述第一确定模块, 还用于根据所述源接入网节点设备的中间节点信 息与所述第二接收模块接收的目标接入网节点设备的中间节点信息, 确定 需要所述第三发送模块向所述源中间节点设备发送所述控制消息。
33、 根据权利要求 31所述的源接入网节点设备, 其特征在于, 所述设 备还包括: 第三接收模块;
所述第三发送模块, 还用于当不连接在同一中间节点设备上的接入网 节点设备不能共享跟踪区域标识时, 将所述源接入网节点设备的跟踪区域 标识发送给所述目标接入网节点设备;
所述第三接收模块, 用于接收所述目标接入网节点设备发送的所述目 标接入网节点设备的跟踪区域标识;
所述第一确定模块, 还用于根据所述源接入网节点设备的跟踪区域标 识与所述第三接收模块接收的目标接入网节点设备的跟踪区域标识, 确定 需要所述第三发送模块向所述源中间节点设备发送所述控制消息。
34、 一种核心网节点设备, 其特征在于, 包括:
第四发送模块 , 用于向源中间节点设备发送控制消息 , 所述控制消息 携带切换到目标接入网节点设备的用户设备的标识, 以使所述源中间节点 设备译放所述用户设备的标识对应的用户设备上下文相关资源;
第四接收模块, 用于接收所述源中间节点设备发送的针对所述控制消 息的响应。
35、 根据权利要求 34所述的设备, 其特征在于, 所述设备还包括: 第 二确定模块;
所述第四接收模块, 还用于接收并保存中间节点设备发送的所述中间 节点设备的中间节点标识和所述中间节点标识对应的中间节点标志, 所述 中间节点标志标示发送所述中间节点标志的节点设备的类型为中间节点设 备, 所述中间节点标识在一个网络中唯一标识一个中间节点设备; 所述第二确定模块, 用于根据预先获得的用户设备对应的源侧节点设 备和目标侧节点设备的标识, 以及所述中间节点标志和所述中间节点标识 的对应关系, 确定需要所述第四发送模块向所述源中间节点设备发送所述 控制消息。
36、 根据权利要求 35所述的设备, 其特征在于, 所述设备还包括: 第五接收模块, 用于接收并保存中间节点设备发送的中间节点标识和 所述中间节点标识对应的跟踪区域标识; 其中, 所述中间节点设备发送的 跟踪区域标识所属的集合对应的节点设备类型为中间节点设备, 所述中间 节点标识在一个网络中唯一标识一个中间节点设备;
所述第二确定模块, 还用于根据预先获得的用户设备对应的源侧节点 设备和目标侧节点设备的标识, 以及所述跟踪区域标识和所述中间节点标 识的对应关系, 确定需要所述第四发送模块向所述源中间节点设备发送所 述控制消息。
37、 根据权利要求 35或 36所述的设备, 其特征在于, 所述第四发送 模块具体用于当所述源侧节点设备为源中间节点设备, 所述目标侧节点设 备为目标中间节点设备, 且所述源侧节点设备的标识与所述目标侧节点设 备的标识不同时, 或者当所述源侧节点设备为源中间节点设备, 所述目标 侧节点设备不是目标中间节点设备时, 向源中间节点设备发送控制消息。
38、 一种中间节点设备, 其特征在于, 包括:
监测模块,用于监测中间节点设备下用户设备的数据和 /或信令的传输; 资源释放模块, 用于释放所述监测模块监测到的数据和 /或信令的传输 符合预定条件的用户设备上下文相关资源。
39、 根据权利要求 38所述的设备, 其特征在于, 所述设备还包括: 消息发送模块, 用于向核心网节点设备发送用户设备上下文译放请求 消息或重置消息;
消息接收模块, 用于接收所述核心网节点设备发送的用户设备上下文 释放命令消息或重置确认消息。
PCT/CN2012/070192 2011-01-10 2012-01-10 用户设备上下文相关资源的释放方法和设备 WO2012094989A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP15183175.7A EP2966902B1 (en) 2011-01-10 2012-01-10 Method and device for releasing context-related resource of user equipment
ES12734672.4T ES2565386T3 (es) 2011-01-10 2012-01-10 Métodos y dispositivos para la liberación de recursos relativos al contexto de un equipo de usuario
JP2013547807A JP5773376B2 (ja) 2011-01-10 2012-01-10 ユーザ機器のコンテキストに関連するリソースを解放するための方法およびデバイス
EP12734672.4A EP2645774B1 (en) 2011-01-10 2012-01-10 Methods and devices for releasing context related resources of user equipment
PL12734672T PL2645774T3 (pl) 2011-01-10 2012-01-10 Sposoby i urządzenia do uwalniania zasobów kontekstowych sprzętu użytkownika
US13/934,731 US9642045B2 (en) 2011-01-10 2013-07-03 Method and device for releasing context-related resource of user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110004406.3A CN102595534B (zh) 2011-01-10 2011-01-10 用户设备上下文相关资源的释放方法和设备
CN201110004406.3 2011-01-10

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/934,731 Continuation US9642045B2 (en) 2011-01-10 2013-07-03 Method and device for releasing context-related resource of user equipment

Publications (1)

Publication Number Publication Date
WO2012094989A1 true WO2012094989A1 (zh) 2012-07-19

Family

ID=46483627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070192 WO2012094989A1 (zh) 2011-01-10 2012-01-10 用户设备上下文相关资源的释放方法和设备

Country Status (8)

Country Link
US (1) US9642045B2 (zh)
EP (2) EP2966902B1 (zh)
JP (2) JP5773376B2 (zh)
CN (1) CN102595534B (zh)
ES (1) ES2565386T3 (zh)
HU (1) HUE027868T2 (zh)
PL (1) PL2645774T3 (zh)
WO (1) WO2012094989A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2488167A (en) * 2011-02-18 2012-08-22 Nec Corp Handover procedure in a home base station connected to a home base station gateway
US9357580B2 (en) * 2013-02-07 2016-05-31 Industrial Technology Research Institute Method for switching communication connection mode, communication system, base station, transmitter and receiver
WO2015140504A1 (en) * 2014-03-21 2015-09-24 British Telecommunications Public Limited Company Mobile handover
CN105813052A (zh) * 2014-12-31 2016-07-27 中兴通讯股份有限公司 用户面路径的更新方法、装置及系统
WO2016167212A1 (ja) * 2015-04-17 2016-10-20 京セラ株式会社 基地局及び通信制御方法
TWI616078B (zh) * 2016-03-30 2018-02-21 財團法人工業技術研究院 用於d2d通訊的通訊系統、通訊裝置及其方法
CN107295589A (zh) * 2016-04-05 2017-10-24 中兴通讯股份有限公司 一种对核心网标识资源的管理方法及相关装置
EP3340670B1 (en) * 2016-12-23 2020-02-19 SafeDrivePod International B.V. Anti-tampering mechanisms for a mobile device lock
WO2019033945A1 (zh) * 2017-08-14 2019-02-21 电信科学技术研究院有限公司 一种ue和网络状态不匹配的处理方法及装置
CN109548109B (zh) 2017-08-14 2021-03-09 电信科学技术研究院 一种ue和网络状态不匹配的处理方法及装置、存储介质
CN109548079A (zh) * 2017-09-22 2019-03-29 中兴通讯股份有限公司 一种指示通信系统的用户平面功能管理资源的方法及装置
CN110446230B (zh) * 2018-05-02 2021-09-14 中国移动通信有限公司研究院 网络侧设备间接口添加方法及网络侧设备
CN109831533A (zh) * 2019-03-19 2019-05-31 上海沐桦科技有限公司 一种网络节点查找方法及装置
WO2023021713A1 (ja) * 2021-08-20 2023-02-23 富士通株式会社 モバイルコアネットワークシステム、センタモバイルコアネットワークシステム、プロキシモバイルコアネットワークシステムおよび無線通信方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040051329A (ko) * 2002-12-12 2004-06-18 엘지전자 주식회사 무선랜망과 이동통신망간의 핸드 오버 방안
CN1627756A (zh) * 2003-12-10 2005-06-15 华为技术有限公司 地面无线接入网与核心网之间接口连接的管理方法
CN1708141A (zh) * 2004-06-08 2005-12-14 华为技术有限公司 媒体网关中终端资源释放方法
CN101478795A (zh) * 2008-04-30 2009-07-08 华为技术有限公司 资源处理的方法、通信系统和移动性管理网元
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100621188B1 (ko) 2004-07-01 2006-09-08 주식회사 미래텍 전원장치를 이용한 엘이디 전구
JP4718496B2 (ja) * 2007-01-05 2011-07-06 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム、移動通信方法、アクセス装置及びゲートウェイ情報記憶装置
CN101330753B (zh) 2007-06-22 2014-07-09 华为技术有限公司 一种资源创建方法、资源删除方法及网络设备
US8467356B2 (en) * 2007-08-10 2013-06-18 Mitsubishi Electric Corporation Wireless communication system and base station
KR100943078B1 (ko) * 2007-12-14 2010-02-18 한국전자통신연구원 Ip 기반의 진화된 이동 통신망에서의 베어러 제어 및관리방법
CN101933350B (zh) * 2008-01-31 2016-01-20 日本电气株式会社 无线通信系统、基站、网关和无线通信方法
JP5169366B2 (ja) * 2008-03-25 2013-03-27 富士通株式会社 移動通信システムの位置登録制御方法
CN101686520A (zh) * 2008-09-24 2010-03-31 三星电子株式会社 支持家用基站上下文管理的方法
EP2361484B1 (en) 2008-11-21 2013-07-17 Telefonaktiebolaget L M Ericsson (publ) Gateway configured to provide a handover, converting and routing function
CN102349329A (zh) * 2009-03-12 2012-02-08 交互数字专利控股公司 用于执行特定于分量载波的重配置的方法和设备
KR101308864B1 (ko) 2009-04-20 2013-09-16 닛본 덴끼 가부시끼가이샤 게이트웨이 장치, 통신 제어 방법, 및 통신 제어 프로그램을 저장하는 비일시적인 컴퓨터 판독가능 매체
JP5168408B2 (ja) 2009-04-23 2013-03-21 日本電気株式会社 基地局装置が中継装置の識別情報をブロードキャストする無線通信システム
JP5038350B2 (ja) 2009-04-27 2012-10-03 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム
CN104936242B (zh) * 2009-09-29 2019-07-05 北京三星通信技术研究有限公司 处理无线链路失败报告的方法
GB2488167A (en) * 2011-02-18 2012-08-22 Nec Corp Handover procedure in a home base station connected to a home base station gateway

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040051329A (ko) * 2002-12-12 2004-06-18 엘지전자 주식회사 무선랜망과 이동통신망간의 핸드 오버 방안
CN1627756A (zh) * 2003-12-10 2005-06-15 华为技术有限公司 地面无线接入网与核心网之间接口连接的管理方法
CN1708141A (zh) * 2004-06-08 2005-12-14 华为技术有限公司 媒体网关中终端资源释放方法
CN101478795A (zh) * 2008-04-30 2009-07-08 华为技术有限公司 资源处理的方法、通信系统和移动性管理网元
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法

Also Published As

Publication number Publication date
US20130295936A1 (en) 2013-11-07
EP2966902B1 (en) 2020-03-11
CN102595534A (zh) 2012-07-18
JP2015130687A (ja) 2015-07-16
JP2014506423A (ja) 2014-03-13
HUE027868T2 (en) 2016-11-28
US9642045B2 (en) 2017-05-02
EP2645774B1 (en) 2016-01-06
CN102595534B (zh) 2014-12-03
EP2966902A1 (en) 2016-01-13
EP2645774A4 (en) 2013-11-06
JP5773376B2 (ja) 2015-09-02
PL2645774T3 (pl) 2016-06-30
ES2565386T3 (es) 2016-04-04
JP5910840B2 (ja) 2016-04-27
EP2645774A1 (en) 2013-10-02

Similar Documents

Publication Publication Date Title
WO2012094989A1 (zh) 用户设备上下文相关资源的释放方法和设备
JP6972023B2 (ja) 無線通信システムの端末の方法、無線通信システムの基地局の方法、端末、及び基地局
WO2022257549A1 (zh) 网络切片方法、设备及存储介质
WO2008092408A1 (en) Method, device and system for establishing s1 signaling connection in evolved network
WO2010048868A1 (zh) 一种网络切换的方法、系统和装置
WO2009024094A1 (fr) Système de communication, procédé et appareil de processus de transfert de réseau
WO2012097708A1 (zh) 一种lipa连接切换准备过程的执行方法及装置
WO2013107346A1 (zh) 一种基站间接口连接建立方法及装置
KR20070024346A (ko) 이동통신 시스템에서의 트래픽 전송경로 재설정 방법
WO2011147370A1 (zh) 一种切换准备方法和装置
WO2015188357A1 (zh) 一种控制承载切换的设备和控制方法
WO2015161575A1 (zh) 用户终端位置上报方法、基站、移动管理实体及系统
WO2013044713A1 (zh) 自组织网络信息传输方法、系统和设备
WO2015154345A1 (zh) 一种封闭成员组身份状态更新的方法、系统及基站
WO2012062147A1 (zh) 一种中继节点小区参数的配置方法及装置
WO2017193555A1 (zh) 小区切换的方法和系统
WO2014177075A1 (zh) 连接建立方法与装置、系统、存储介质
JP5256129B2 (ja) 基地局制御装置および無線パケット処理装置
WO2012155656A1 (zh) 一种宿主基站、中继节点设备及增强路径转换的方法
WO2012155681A1 (zh) 一种csg信息的传输方法和设备
CN116458190A (zh) 用于增强新空口集成接入回程网络的方法和设备
WO2020032767A1 (ko) 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치
WO2014022974A1 (zh) 数据发送的方法、设备及系统
WO2012146131A1 (zh) 一种网关的选择方法及系统
WO2019119236A1 (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: 12734672

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012734672

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2013547807

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE